My virtual interface BGP status For Direct Connect is down in the AWS console. What should I do?
Last updated: 2022-06-17
My virtual interface BGP status for AWS Direct Connect is down in the AWS console. How can I troubleshoot this issue?
Your virtual interface status might be down because of configuration issues with the OSI Layer 2 or Border Gateway Protocol (BGP).
OSI Layer 2 configuration
Verify that your OSI layer 2 is configured correctly by confirming the following:
- You configured the correct VLAN ID with dot1Q encapsulation on your device—such as a router or switch—as displayed in the Direct Connect console.
- The peer IP addresses' configuration is identical on your device and in the Direct Connect console.
- All the intermediate devices along the path are configured for dot1Q VLAN tagging with correct VLAN ID, and VLAN-tagged traffic is preserved on the AWS side of Direct Connect device.
Note: Some network providers might also use Q-in-Q tagging, which can alter your tagged VLAN. AWS Direct Connect service doesn't support Q-in-Q tagging.
- Your device is learning the media access control (MAC) address of the AWS Direct Connect device for the configured VLAN ID from the Address Resolution Protocol (ARP) table.
- Your device can ping the Amazon peer IP sourcing from your peer IP.
For more information, see Troubleshooting layer 2 (data link) issues.
If the OSI layer 2 configuration looks good, then confirm the BGP configuration on your device by verifying the following:
- The local ASN and remote ASN, as provided in the Downloaded configuration file.
- The neighbor IP address and BGP MD5 password, as provided in the Downloaded configuration file.
- Your device isn't blocking ingress or egress traffic on TCP port 179 and other appropriate ephemeral ports.
- Your device isn't advertising more than 100 prefixes to AWS by BGP. By default, AWS only accepts up to 100 prefixes using a BGP session on AWS Direct Connect. For more information, see Direct Connect quotas.
After confirming these configurations, your virtual interface BGP status is now up.
For more information, see How can I troubleshoot BGP connection issues over Direct Connect?