CCNP Route Control: A Second Boundary and the Distance Trap
Add a second boundary router for resilience, then stop it from routing the acquired site's routes the long way round.
51 hands-on CCNP scenarios you build in your own Cisco Modeling Labs instance and grade against the answer key. CCNP configuration and troubleshooting practice for CCNA and CCNP.
Included with a subscription
Add a second boundary router for resilience, then stop it from routing the acquired site's routes the long way round.
Mark the partner extranet so HQ can tell it apart: give it its own metric, external type and tag as it enters OSPF.
The acquired site is leaking its vendor test bench into HQ. Let only its production subnets into OSPF.
Set one seed metric for every route entering EIGRP, and carry EIGRP routes into OSPF as type 1 externals.
HQ runs OSPF and the company it bought runs EIGRP. Join them at the boundary router so both sites reach each other.
Free with an account
HQ and the branch came back from a provider change unable to reach each other. Bring the overlay back to its design.
Put the internet circuit in its own routing table. The tunnel still rides it, but the global table never sees the internet.
The tunnel works, but static routes won't scale. Run OSPF across it, and size its packets so nothing gets dropped.
Two sites, and a provider that won't carry private routes. Build a tunnel between the sites and route each LAN through it.
Static routes don't scale. Give each tenant its own OSPF process, so its routes are learned instead of typed.
The tenant services moved to a core router. Carry both tenants over one cable and route each to its own services.
Two tenants share one edge router. Give each its own routing table, so both can use the same service address.
Free with an account
Advanced CCNP VRRP lab: standardize the VRRP advertisement interval to 3 seconds on a shared user VLAN. Two IOS routers (R1, R2) and two hosts connect to a single access switch on VLAN 10 (10.0.10.0/24). Both routers share VRRP group 1 and the same virtual IP 10.0.10.254 so hosts keep one default gateway. R1 is the master via priority 110; both routers explicitly set 'vrrp 1 timers advertise 3' to enforce a consistent master advertisement rate and backup master-down detection window. Verify with 'show vrrp' (Advertisement interval 3.000 sec) and host pings to the VIP.
Configure VRRP with interface object tracking so the virtual gateway fails over when the active router loses its upstream link, avoiding black-holing. The site LAN (VLAN 10) uses a single virtual default gateway (10.0.10.254) shared by two IOS routers (R1, R2). A separate access switch (SW) bridges the LAN. Both routers uplink via Ethernet0/1 to a second switch (CORE) on VLAN 99 to represent the upstream path. R1 is the intended VRRP master (priority 110). You will create a track object that monitors R1's uplink (Ethernet0/1) and decrements its VRRP priority by 20 if the link fails, allowing R2 to preemptively take over as master. The lab grades the deterministic VRRP configuration: common group and virtual IP on both routers, R1 priority 110, the global track object, and the 'vrrp 1 track 1 decrement 20' tie-in on R1.
Advanced CCNP BGP policy lab focusing on inbound AS-path filtering at the edge. You will build a simple eBGP chain (AS 65003 — AS 65002 — AS 65001), originate prefixes from the two upstream routers, confirm that the edge learns multiple routes, then enforce a policy on the edge (R1) to accept only routes originated by its directly connected eBGP neighbor (AS 65002) while rejecting routes that transited AS 65003. Verification relies entirely on R1’s BGP table and AS-path regular-expression queries.
In this advanced CCNP BGP lab, you will steer a single router's outbound path choice using Cisco's Weight attribute, the very first BGP best-path tiebreaker. R1 (AS 65001) peers eBGP with two ISPs (R2 in AS 65002 and R3 in AS 65003). Both ISPs advertise the same prefix 172.16.50.0/24. Your job is to make R1 prefer the R3 path using the neighbor weight command and verify the outcome using IOS and Linux tools.
In this CCNP-level lab (BGP Fundamentals Lab 4/10), you will build a small, realistic transit-AS scenario: an external route learned by R1 via eBGP from AS 65003 must be carried across iBGP to R2 inside AS 65001. You will intentionally encounter the classic iBGP next-hop problem (R2 sees an unreachable next-hop for 172.16.30.0/24) and fix it on R1 with neighbor next-hop-self. iBGP peering runs over Loopback0 addresses with reachability provided by OSPF area 0 between R1 and R2. Two hosts validate end-to-end data-plane reachability and routing control-plane state.
Deploy eBGP between two routers and precisely control which locally-originated networks are advertised to a neighbor using an outbound prefix-list. R1 originates four /24 loopback routes but advertises only two to R2. Verify using IOS show commands and basic host reachability checks.
Advanced BGP capstone, run as a fault hunt. The hub lost its upstream service route overnight and the branch cannot see hub prefixes either. Sessions are not all down, which is what makes it interesting: one peering never establishes, one establishes and carries nothing, and one prefix is never originated at all. You get symptoms and the required end state — no fault list. Faults span all three routers, and one of them is not in BGP at all.
Advanced CCNP BGP lab: Build parallel eBGP sessions between two ASes over primary and backup /30 links. Originate a service prefix from AS 65001 and influence AS 65002's inbound path by applying outbound AS-path prepending on the backup session only. Validate best-path selection and next-hop on the neighbor, and confirm reachability from hosts.
Configure eBGP between two routers and originate select connected /24s using the exact-match 'network ... mask' command. Verify that only the intended prefixes are advertised and learned by the neighbor, and use host-based tests to confirm reachability to the advertised networks. This beginner CCNP lab reinforces that the BGP network statement only advertises a route if an exact match exists in the RIB, and that the 'mask' keyword is mandatory for non-classful advertisements.
Build your first external BGP (eBGP) peering between two routers in different autonomous systems over a /30 point-to-point link and exchange one /24 prefix from each side using Loopback0. The topology is intentionally small yet realistic, with two edge routers (AS 65001 and AS 65002) and three Alpine hosts for basic reachability checks and operator context. You will configure deterministic BGP neighbors, originate prefixes with exact-match network statements, and validate reachability and route installation using standard IOS and Linux tools. This is Lab 1 of 10 in the CCNP-aligned BGP Fundamentals series and sets the foundation for later labs on iBGP, route filtering, and path selection.
Free with an account
Build an internal BGP (iBGP) peering between two IOS routers in the same AS over stable Loopback0 addresses, with OSPF providing loopback reachability. Each router originates a /24 from Loopback1 into BGP, and next-hop/peering behavior is validated from end hosts. This lab emphasizes the deterministic neighbor configuration (remote-as, update-source Loopback0, router-id) and exact-match network origination, supported by a minimal, secure OSPF core.
Advanced EIGRP capstone, run as a fault hunt. The branch LAN has disappeared from the network, one router sees only half its neighbours, and the routing process looks healthy on every device. Nothing was recorded. You get symptoms and the required end state — no fault list. Faults span all three routers, and two of them leave EIGRP running perfectly while doing nothing useful.
Looking for something else? Browse the full lab archive, narrow it to self-standing labs, or see today's daily lab.