bgp status stuck in active

That's great, as for your question on why you don't see a response when you telnet to AWS endpoint on port 179. Remember we use TCP MD5 Signature to encrypt the BGP session and as such, when you try to send a telnet on port 179, the TCP SYN packet doesn't have the MD5 option, and based on TCP protocol rules, it won't respond nor send a TCP RST simply to as a protection mechanism, therefore, you feel the far end isn't responsive. I hope that answers your question.

Hi, can you post the output of the command "show logs" on your CGW? Also can you run packets capture to see what's happening? You can do so in ASR platform by running these commands: monitor capture capture-name interface interface-name both monitor capture capture-name start ###keep it running for a couple of minutes and then run: monitor capture capture-name stop monitor capture capture-name export file-location/file-name

Hello,

Check if the DX connection is UP or not. Post that, check if the DX-VIF is in available state.

Once verified, there must be connectivity between the BGP peer IPs on both your end and the AWS end. Basically, the TCP connection is not getting established in this case.

Check and verify the configuration on your Direct Connect router The IP addresses of the local and remote BGP peers, local and remote BGP Autonomous System Numbers (ASN), and the BGP MD5 password must be configured with the downloaded Direct Connect configuration file from the Direct Connect console. Verify that the Direct Connect router or any other device is not blocking ingress or egress from TCP port 179 and other appropriate ephemeral ports. BGP peers can't be more than one hop away from each other because external BGP (EBGP) multi-hop is disabled on the AWS end.

If this does not help, to get the connection checked internally, you might have to open up a case with the Direct connect team using your account and support plan.

Hope this helps !!