Amazon Virtual Private Cloud
Network Administrator Guide

Troubleshooting Generic Device Customer Gateway Connectivity Using Border Gateway Protocol

The following diagram and table provide general instructions for troubleshooting a customer gateway that uses Border Gateway Protocol for devices other than those listed in this guide.


When troubleshooting problems, you might find it useful to enable the debug features of your gateway device. Consult your gateway device vendor for details.

					Flow chart for troubleshooting generic customer

Determine if an IKE Security Association exists.

An IKE security association is required to exchange keys that are used to establish the IPsec Security Association.

If no IKE security association exists, review your IKE configuration settings. You must configure the encryption, authentication, perfect-forward-secrecy, and mode parameters as listed in the customer gateway configuration.

If an IKE security association exists, move on to IPsec.

Determine if an IPsec Security Association exists.

An IPsec security association is the tunnel itself. Query your customer gateway to determine if an IPsec Security Association is active. Proper configuration of the IPsec SA is critical. You must configure the encryption, authentication, perfect-forward-secrecy, and mode parameters as listed in the customer gateway configuration.

If no IPsec Security Association exists, review your IPsec configuration.

If an IPsec Security Association exists, move on to the tunnel.

Confirm that the required firewall rules are set up (for a list of the rules, see Configuring a Firewall Between the Internet and Your Customer Gateway Device). If they are, move forward.

Determine if there is IP connectivity via the tunnel.

Each side of the tunnel has an IP address as specified in the customer gateway configuration. The virtual private gateway address is the address used as the BGP neighbor address. From your customer gateway, ping this address to determine if IP traffic is being properly encrypted and decrypted.

If the ping isn't successful, review your tunnel interface configuration to make sure that the proper IP address is configured.

If the ping is successful, move on to BGP.

Determine if the BGP peering is active.

For each tunnel, do the following:

  • On your customer gateway, determine if the BGP status is Active or Established. It may take approximately 30 seconds for a BGP peering to become active.

  • Ensure that the customer gateway is advertising the default route ( to the virtual private gateway.

If the tunnels are not in this state, review your BGP configuration.

If the BGP peering is established, you are receiving a prefix, and you are advertising a prefix, your tunnel is configured correctly. Make sure that both tunnels are in this state, and you're done.


Make sure that your virtual private gateway is attached to your VPC. Your integration team does this with the AWS Management Console.

For general testing instructions applicable to all customer gateways, see How to Test the Customer Gateway Configuration.

If you have questions or need further assistance, please use the Amazon VPC forum.