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.
5 hands-on Redistribution scenarios you build in your own Cisco Modeling Labs instance and grade against the answer key. Redistribution configuration and troubleshooting practice for 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
Looking for something else? Browse the full lab archive, narrow it to self-standing labs, or see today's daily lab.