Configure Inter-AS VPN connectivity by defining a static route to an ASBR peer

Updated: June 17, 2026

Want to summarize with AI?

Outlines steps for establishing Inter-AS VPN connectivity by configuring a static route to an ASBR peer, including CLI procedures for directing traffic toward remote autonomous systems.

Define a static route that directs traffic intended for the ASBR peer, facilitating Inter-AS VPN connectivity within your network.

Use this task when you need to manually specify a static route to an ASBR peer, typically as part of configuring or troubleshooting Inter-AS VPN connections on a router.

Before you begin

Identify the ASBR peer prefix (destination network) and the next-hop IP address for the static route.
Ensure you have appropriate privileges to access and configure router settings through the CLI.

Procedure

Configure a static route to an ASBR peer.

Example:

Router# configure
Router(config)# router static
Router(config-static)# address-family ipv4 unicast
Router(config-static-afi)# 10.10.10.10/32 10.9.9.9
Router(config-static-afi)# commit

The static route to the ASBR peer is configured once the route is committed. Traffic destined for the ASBR peer will now be routed according to your specification.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.