CCNP ROUTE Lab Experiences

clip_image016When I first studied ROUTE last year, I went through a good portion of the official lab manual, but I don’t feel like I was as serious about it at that time as I am now. This time around, in addition to completing the entire lab manual, I thought I would write about my experiences, or takeaways, from the material as a reminder to myself of the knowledge I’ve learned for when I take the exam. Before, I read and took notes from The Official Cert Guide. This time, I read the Foundation Learning Guide and found that the lab manual perfectly coincides with the layout of the book. Very nice.

  • Lab 2.1 EIGRP Configuration, Bandwidth and Adjacencies:
    The most important thing I took was the reminder that when a neighbor goes down on a multi-access segment (such as routers connected together with a switch), the routing protocols must time out first because the link itself is still active. Use BFD to alleviate this situation
  • Lab 2.2 EIGRP Load Balancing:
    Use show ip eigrp topology prefix/length to view details about the metrics of the route.
  • Lab 2.3 EIGRP Summarization and Default Network Advertisement:
    Nothing new learned from this lab; just a reminder that summarization decreases routing tables and limits EIGRP query domains (and potentially increases network stability)
  • Lab 2.4 EIGRP Frame Relay Hub-and-Spoke – Router Used as a Frame Relay Switch:
    This lab demonstrates the effects of split-horizon on distance-vector routing protocols. It also demonstrates the effects of statically configuring neighbors on an interface. Upon static neighbor configuration, EIGRP sends a goodbye message to the neighbors and the adjacency is lost until manually configured on both ends of the link.
  • Lab 2.5 EIGRP Authentication and Timers:
    I consider this lab nothing more than a CCNA review.
  • Lab 2.6 EIGRP Challenge:
    Same thing.
  • Lab 2.7 EIGRP Troubleshooting:
    I could immediately see that all of the issues were directly related to misconfigured IP addresses.
  • Lab 3.1 Single-Area OSPF Link Costs and Interface Priorities:
    Suddenly, all of the routers in the reading material and lab manual are encompassed within various circles 🙂 CCNA-level review
  • Lab 3.2 Multi-Area OSPF with Stub Areas and Authentication:
    This lab shows that when converting an area from regular to stubby, the neighborships are reset. However, changing from stubby to totally-stubby does not force a reset.
  • Lab 3.3 OSPF Virtual Links and Area Summarization:
    No surprises here.
  • Lab 3.4 OSPF over Frame Relay:
    OSPF network type point-to-multipoint treats each connection as a point-to-point link and installs host routes to the routing table
  • Lab 3.5 OSPF Challenge:
    Provided a reminder that the OSPF router ID is set automatically by the highest IP loopback interface. Also a reminder that adjusting the hello-timer automatically adjusts the dead timer. OSPF virtual links are defined by OSPF router-id, not by interface IP address.
  • Lab 3.6 OSPF Troubleshooting:
    Troubleshooting was slightly more involved this time. Though some of the issues were due to misconfigured IPs, other issues such as the loopbacks missing the ip ospf network point-to-point command were present, as well as the router-id of the virtual link endpoints being wrong (as I discovered in the previous lab). Also OSPF network type nonbroadcast requires neighbors to be set manually.
  • Lab 3.7 OSPF Case Study:
    Very similar to 3.6.
  • Lab 4.1 Redistribution Between RIP and OSPF:
    This lab demonstrated to me the fact that when adding a distribute list to filter routes, the old routes must time out (or be cleared) before being cleared from the neighbor routing table, and that RIP has an extremely slow convergence time.
  • Lab 4.2 Redistribution Between EIGRP and OSPF:
    A reminder to use the interface range command when applying the same configuration on multiple consecutive interfaces (in this case, ip ospf network point-to-point on the loopbacks). Redistributing RIP and EIGRP requires a seed metric, whereas OSPF does not.
  • Lab 4.3 Manipulating Administrative Distances:
    Demonstrated the ability to change administrative distances in both entire routing protocols as well as individual routes
  • Lab 4.4 EIGRP and OSPF Case Study:
    An instruction such as “Redistribute OSPF into EIGRP” aids in the logical thought process when actually implementing the commands. OSPF is going into EIGRP, which lets you know the configuration is happening under the EIGRP process.
  • Lab 5.1 Configuring and Verifying Path Control:
    Define ACL, define route-map, apply route-map to incoming interface with ip policy route-map route-map-name, verify with debug ip policy and traceroute
  • Lab 5.2 Configure IP SLA Tracking and Path Control:
    Define an IP SLA probe, schedule it, verify with show ip sla statistics, track the IP SLA
  • Lab 6.1 Configuring BGP with Default Routing:
    Nothing too big here; outlines a scenario with a primary ISP and a backup ISP
  • Lab 6.2 Using the AS_PATH Attribute:
    Demonstrated removing private AS_PATH attributes from the route and filtering the sending of routes from regex-matched ASNs
  • Lab 6.3 Configuring iBGP and eBGP Sessions, Local Preference and MED:
    Just as it says 🙂
  • Lab 6.4 BGP Route Reflectors and Route Filters:
    Demonstration of route-reflector-client and aggregate-address
  • Lab 6.5 BGP Case Study:
    This lab provided a reminder that EIGRP does not form neighborships on links that reside in different ASes. This lab also reminded me that the MED value default is 0, so you need to make the outbound MED value higher on the less-preferred paths into the AS.
  • Lab 7.1 Configuring Routing Facilities to the Branch Office:
    Probably the most important thing this lab detailed was the fact that when using an IPsec site-to-site VPN with NAT, you need to create an ACL that denies the IPsec traffic from passing through the NAT
  • Lab 8.1 Configuring OSPF for IPv6:
    This lab demonstrates that to ping a link-local address (FE80::) you must specify the outgoing interface because link-local addresses do not appear in the routing table.
  • Lab 8.2 Using Manual IPv6 Tunnels with EIGRP for IPv6:
    This lab demonstrates that when configuring EIGRP for IPv6, the routing protocol is shutdown by default, and you must issue ipv6 router eigrp ASN —> no shutdown before neighborships are formed.
  • Lab 8.3 Configuring 6to4 Tunnels:
    Very similar to the previous lab, just using static routing instead
  • Lab 8.4 IPv6 Challenge:
    When configuring a /64 on an interface, I accidentally forgot to include eui-64 and the router informed me that the address is an anycast subnet address. I was also reminded that on an IPv6-only router, OSPF will not work unless you manually configure a router-id.
  • Lab 8.5 IPv6 Troubleshooting:
    Nothing really special about this one.