Completed Planning Practice Tables

Transcription

1 Appendix F Completed Planning Practice Tables Chapter 1 Table 1-3 Design Review Design Goal The design requires the number of entries in a router s routing table to be reduced. The design calls for the use of a distancevector routing protocol. Identify the two approaches that a distance-vector routing protocol can use to prevent loops. (2) The design calls for the use of a link-state routing protocol. (2) The design calls for IPv6 traffic to travel from a source IPv6 address to the nearest device of multiple devices assigned the same destination IPv6 address. The design calls for the use of an NBMA network. Identify design issues that might be encountered when using EIGRP or OSPF. (2) The design calls for the use of Hot Standby Router Protocol (HSRP). Identify the condition that can be created when return traffic flows through a standby HSRP router. The design needs to mitigate a global synchronization condition (where all TCP flows simultaneously enter TCP slow start). The design requires a network to be migrated to a different routing protocol. (2) Possible Implementation Choices Covered in This Chapter Summarization. Split Horizon. Poison Reverse. Use OSPF. Use IS-IS. Use anycast. Issue with EIGRP: Split Horizon. Issue with OSPF: Designated router. Asymmetric routing (or unicast flooding). Use WRED. Configure both routing protocols, and use Administrative Distance (AD) to control which routing protocol is being used. Use route redistribution as you migrate individual sections of the network.

2 4 CCNP Routing and Switching ROUTE Official Cert Guide Design Goal The design requires that you virtualize multiple routers inside of physical routers and carry traffic for the virtual networks between those physical routers. Possible Implementation Choices Covered in This Chapter Use Cisco Easy Virtual Networking (EVN). Table 1-4 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question The plan requires that Split Horizon be disabled for the hub router in a hub-andspoke topology. Describe the purpose of Split Horizon. The plan requires the use of EIGRP as the routing protocol. Provide a brief description of EIGRP. The plan calls for the use of both IPv4 and IPv6. What network traffic types do IPv4 and IPv6 have in common, and what traffic types are different? The plan calls for the use of Hot Standby Router Protocol (HSRP). What can you do to prevent an asymmetric routing issue, where traffic is forwarded from a subnet using the active HSRP router, and some of the return traffic returns using the standby HSRP router (because of load balancing)? The design calls for the transmission of interactive voice and video over a network. What Layer 4 protocols are typically used to transmit voice and data media? (2) The plan requires that a network migrate from IPv4 to IPv6. Identify three strategies of a successful IPv6 migration. (3) Answers Split Horizon is a feature that prevents a route learned on one interface from being advertised back out of that same interface. Enhanced Interior Gateway Routing Protocol (EIGRP) is classified as an advanced distancevector routing protocol. It was Ciscoproprietary until early 2013, but is now open to other vendors. EIGRP uses the Diffusing Update Algorithm (DUAL) to make its path selection decisions. Both IPv4 and IPv6 use unicasts and multicasts. However, IPv4 can use broadcasts, while IPv6 cannot. Also, IPv6 supports anycasts, while IPv4 does not. Ideally, you should not span a VLAN across more than one access layer switch. However, if you must span a VLAN across multiple access layer switches, you can adjust the HSRP router s ARP timer to be equal to or less than the CAM aging time. The Real-time Transport Protocol (RTP) is a Layer 4 protocol that carries voice and video media. RTP is encapsulated inside of User Datagram Protocol (UDP), which is another Layer 4 protocol. Check existing equipment for IPv6 compatibility. Run IPv4 and IPv6 concurrently. Check the ISP s support for IPv6.

3 Appendix F: Completed Planning Practice Tables 5 Question The plan calls for the use of Virtual Routing and Forwarding (VRF). Identify two approaches to configuring VRF. (2) Answers A traditional way to configure VRF on Cisco routers is an approach called VRF-Lite. A newer approach to virtualized network configuration, called Cisco Easy Virtual Network (EVN), dramatically simplifies the relatively complex configuration required by VRF-Lite. Chapter 2 Table 2-2 Design Review Design Goal The design requires that routers at remote sites appear as adjacent to one another, and they are interconnected over an MPLS network. The design requires customer edge (CE) routers at each enterprise site to communicate over an MPLS network and to form neighborships with provider edge (PE) routers to which they connect. The design requires that multicast, broadcast, and unicast IP traffic between sites be secured within a VPN. The design requires that spokes in a hub-and-spoke VPN topology be able to dynamically form GRE tunnels between themselves. The design requires that a single GRE tunnel interface support multiple GRE tunnels. The design requires that spoke routers in a huband-spoke VPN design be able to query the hub to determine the IP address of a physical interface corresponding to the far side of a tunnel. The design requires that you provide confidentiality, data integrity, authentication, and antireplay protection for unicast traffic flowing over a VPN. Possible Implementation Choices Covered in This Chapter Use a Layer 2 MPLS VPN. Use a Layer 3 MPLS VPN. Encapsulate the multicast, broadcast, and unicast IP traffic inside of a GRE tunnel, and then encapsulate the GRE packets inside of an IPsec tunnel. Use Dynamic Multipoint VPN (DMVPN). Use multipoint GRE (mgre). Use NHRP. Use IPsec.

4 6 CCNP Routing and Switching ROUTE Official Cert Guide Table 2-3 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question The plan requires that an MPLS VPN technology be used to interconnect remote sites. What broad categories of MPLS VPNs could you choose from? (Choose two.) The plan mandates the use of a Layer 3 MPLS VPN. What routing protocol will the service provider probably use to propagate route information from a customer edge (CE) router at one site to a CE router at another site? The plan calls for the use of a GRE tunnel. What protocols can you send over a GRE tunnel? The plan calls for the use of a Dynamic Multipoint VPN (DMVPN). What VPN technologies are required to support a DMVPN? (Choose three.) The plan requires a hub router in a hub-and-spoke topology to have four GRE tunnels out to remote sites. If you use mgre, how many tunnel interfaces need to be configured on the hub router to support the four GRE tunnels? The plan calls for the use of NHRP in a hub-andspoke VPN topology. What router, or routers, in the topology will hold the NHRP database? The plan requires the use of IPsec. What are IPsec s modes of operation? (Choose two.) Answer Layer 2 MPLS VPNs, Layer 3 MPLS VPNs Multiprotocol BGP (MP-BGP) A GRE tunnel supports any Layer 3 protocol (including IP unicast, broadcast, and multicast traffic). Multipoint GRE (mgre), Next Hop Resolution Protocol (NHRP), IPsec One The hub router Transport Mode, Tunnel Mode Table 2-4 Implementation Plan Configuration Memory Drill Feature Create a GRE virtual tunnel interface (in global configuration mode). Assign an IP address to a GRE tunnel (in interface configuration mode). Specify the source of a GRE tunnel (in interface configuration mode). Specify the destination of a GRE tunnel (in interface configuration mode). Configuration Commands/Notes interface tunnel id ip address ip_address subnet_mask tunnel source {interface_id ip_address} tunnel destination ip_address

5 Appendix F: Completed Planning Practice Tables 7 Table 2-5 Verification Plan Memory Drill Information Needed Verify the interface status and encapsulation of a GRE tunnel. Verify that a router sees the far side of a GRE tunnel as a single hop away, even though multiple routers might need to be transited to reach the far side of the tunnel. Command(s) show interface tunnel id trace route ip_address_of_far_side_of_ tunnel Chapter 3 Table 3-14 Design Review Design Goal An IPv6 design suggests that all client hosts should dynamically learn their IPv6 addresses. Which tools can be used? (2) A plan shows the use of stateless autoconfiguration. What functions should we expect the IPv6 DHCP server to perform? Possible Implementation Choices Covered in This Chapter Stateful DHCP Stateless autoconfig To supply the DNSv6 server s IPv6 addresses Table 3-15 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question An implementation plan states that router IPv6 addresses should be assigned as obvious values, using the lowest numbers in the range per each assigned prefix. What configuration methods could be used to configure these low address values? A plan calls for the use of stateless autoconfig for client hosts. What must be configured on the routers to support this process? A RIPng implementation plan lists two neighboring routers with unicast IPv6 addresses 2000::1/64 and 2001::2/64, respectively. Will this cause a neighborship issue? Answers Statically configure the entire address with the ipv6 address command. Configure the MAC address to a low number, and configure the address with the ipv6 address eui-64 command. Routers must respond to Router Solicitation messages with Router Advertisement (RA). To do so, a router must have IPv6 routing enabled and a unicast IPv6 address configured on the interface in which the RS is received. No; RIPv6 does not use the concept of neighbors, but it also does not prevent routes from being exchanged.

6 8 CCNP Routing and Switching ROUTE Official Cert Guide Table 3-16 Implementation Plan Configuration Memory Drill Feature Globally enable the routing of IPv6 unicast traffic. Globally enable Cisco Express Forwarding (CEF) for IPv6. Configure flow-label marking in 1280-byte or larger packets sent by the router. Configure the full global unicast address on an interface. Configure the unicast IPv6 prefix on an interface, and let the router add the interface ID. Configure an interface to find its unicast IPv6 address using stateless autoconfig. Configure an interface to enable IPv6 and use another interface s IPv6 address as needed. Enable IPv6 on an interface and do not configure a unicast IPv6 address. Configure the link-local address of an interface. Assuming that IPv6 routing and IPv6 addresses have already been configured, configure RIPng. Configuration Commands/Notes ipv6 unicast-routing ipv6 cef ipv6 flowset interface type number ipv6 address address/prefix-length interface type number ipv6 address address/prefix-length eui-64 interface type number ipv6 address autoconfig interface type number ipv6 unnumbered type number interface type number ipv6 enable interface type number ipv6 address address link-local ipv6 router rip process-name interface type number ipv6 rip process-name enable (Repeat previous two commands for each interface.) Table 3-17 Verification Plan Memory Drill Information Needed All IPv6 routes A single line per IPv6 address Detailed information about IPv6 on an interface, including multicast addresses The MAC address used by an interface Commands show ipv6 route show ipv6 interface brief show ipv6 interface [type number] show interfaces [type number]

7 Appendix F: Completed Planning Practice Tables 9 Information Needed The MAC addresses of neighboring IPv6 hosts The information learned from another router in an RA message All RIP-learned IPv6 routes All next-hop IPv6 addresses used by RIP routes The interfaces on which RIP is enabled Commands show ipv6 neighbors show ipv6 router show ipv6 route rip show ipv6 rip next-hops show ipv6 protocols Chapter 4 Table 4-5 Design Review Design Goal Improve EIGRP convergence. Implement EIGRP on each router so that neighborships are formed (2). Limit neighborship formation on interfaces matched with an EIGRP network command (3). Possible Implementation Choices Covered in This Chapter Tune EIGRP Hold and Hello Timers so that neighbor failures are recognized more quickly. Discover neighbors using multicasts as a result of matching an interface with the EIGRP network command, in router EIGRP configuration mode. Allow only specific neighbors on an interface by configuring the neighbor command in router EIGRP configuration mode. Use EIGRP authentication to allow only neighbors with the correct keys. Prevent all neighborships on an interface by making the interface passive. Allow only specific neighbors on an interface by configuring a static neighbor. Table 4-6 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question What happens on a router interface on which an EIGRP network command matches the interface? (2) Answer EIGRP attempts to discover EIGRP neighbors by sending and receiving multicast EIGRP Hellos. EIGRP advertises about the subnet on the connected interface.

8 10 CCNP Routing and Switching ROUTE Official Cert Guide Question What configuration settings prevent EIGRP neighbor discovery on an EIGRPenabled interface? (2) What configuration settings prevent any neighborships on an EIGRP-enabled interface? What settings do potential neighbors check before becoming EIGRP neighbors? (5) What settings that you might think would impact EIGRP neighbor relationships actually do not prevent neighborship? (3) Answer Static configuration of at least one neighbor on that interface. Configuring the interface as passive. Configuring the interface as passive. Whether the neighbor s IP address is in the same primary subnet as the local router. EIGRP authentication failure. ASN in router eigrp asn commands must match. The interfaces cannot be passive. The configured K-values must match. Mismatched Hello and Hold Timer settings. Duplicate Router IDs. IP MTU mismatch. Table 4-7 Implementation Plan Configuration Memory Drill Feature Enabling EIGRP on interfaces Setting Hello and Hold Timers Passive interfaces Static EIGRP neighbors K-values EIGRP router ID Configuration Commands/Notes router eigrp autonomous-system network network-number [wildcard-mask] ip hello-interval eigrp as-number timer-value ip hold-time eigrp as-number timer-value passive-interface type number passive-interface default no passive-interface type number neighbor a.b.c.d interface metric weights 0 k1 k2 k3 k4 k5 eigrp router-id a.b.c.d

9 Appendix F: Completed Planning Practice Tables 11 Table 4-8 Verification Plan Memory Drill Information Needed Routes that have been added to the IP routing table by EIGRP. All routes in a router s routing table. The specific route for a single destination address or subnet. A listing of all (both statically configured and dynamically discovered) EIGRP neighbors. Notation as to whether a neighbor was dynamically discovered or statically configured. A listing of statistics regarding the numbers of EIGRP messages sent and received by a router. A listing of interfaces on which EIGRP has been enabled (by virtue of the EIGRP network command). A listing of the number of EIGRP peers known through a particular interface. The elapsed time since a neighborship was formed. The parameters of any EIGRP network commands. The configured Hello timer for an interface. The configured Hold Timer for an interface. The current actual Hold Timer for a neighbor. A router s EIGRP ASN. A list of EIGRP passive interfaces. A list of nonpassive EIGRP interfaces. A listing of EIGRP K-values. A listing of traffic statistics about EIGRP. A router s EIGRP Router ID. Command show ip route eigrp show ip route show ip route ip-address [mask] show ip eigrp neighbors show ip eigrp neighbors detail show ip eigrp neighbors detail show ip eigrp traffic show ip eigrp interfaces show ip eigrp interfaces detail show ip eigrp interfaces show ip eigrp interfaces detail show ip eigrp interfaces type number show ip protocols show ip eigrp neighbors [detail] show ip protocols show ip eigrp interfaces detail [type number] None show ip eigrp neighbor [detail] show ip protocols show ip eigrp traffic show ip eigrp accounting show ip protocols show ip eigrp interfaces [detail] show ip protocols show ip eigrp traffic show ip eigrp topology show ip eigrp accounting

10 12 CCNP Routing and Switching ROUTE Official Cert Guide Chapter 5 Table 5-8 Design Review Design Goal Limit consumption of IP subnets in Frame Relay WAN design. In a relatively slow Frame Relay WAN, protect against consuming too much bandwidth with overhead EIGRP traffic. Plan to change bandwidth from 1X CIR to 2X CIR on all Frame Relay subinterfaces. Plan to set bandwidth to values other than actual interface speeds to manipulate EIGRP metrics. A goal of ensuring all remote routers secondary EIGRP routes do not require queries for convergence. What tools can we use to meet the design goal of fast convergence? (four items) R1 and R2 will advertise the same summary route; ensure that R1 is the preferred EIGRP path for that summary. Prevent the edge routers in sites for one division of the company from knowing routes for subnets in another division. Always ensure that the shortest path is taken with each route. Possible Implementation Choices Covered in This Chapter Use multipoint subinterfaces, with more than two routers sharing the same WAN subnet. Use the EIGRP WAN bandwidth control feature to limit the amount of bandwidth consumed by EIGRP. Adjust metrics with delay as well, to ensure the correct best routes are chosen plus backup routes are feasible successors where possible. Ask whether the design could use delay instead. Tune metrics using delay or offset lists such that secondary routes are FS routes. Tune metrics so that feasible successor routes exist. Make appropriate routers EIGRP stubs. Use unequal cost multipath to add multiple routes to the routing table. Use route summarization to limit query scope. Tune EIGRP metrics so that all R2 s metrics for the subordinate routes are higher than the metric of R1 s best subordinate route. Use EIGRP route filtering (distribution lists). Avoid the use of summary routes.

11 Appendix F: Completed Planning Practice Tables 13 Table 5-9 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question A Frame Relay multipoint interface, with 20 PVCs attached, has a configuration for 10 percent of the bandwidth to be used for EIGRP. How much is allocated per PVC? A configuration lists the no ip split-horizon command. When would that matter? The plan calls for setting all EIGRP K-values to 1. What negative effect could this have on routes in the IP routing table? The configuration uses offset lists. Will that impact the calculation of FD and/or RD? The plan lists a sample configuration migrating an interface from delay 20 to delay 200. How much will the metric go up? The plan shows extensive use of Class C private networks inside a large enterprise. What effect might EIGRP auto-summary have? The plan shows a sample configuration of the ip summary-address eigrp command on Router R1. What routes should I see on R1? What will their administrative distance be? The plan shows the use of the variance 4 command. What must be configured to add other routes to a routing table? (two items) The plan calls for filtering /26 and /26, but not /24. What tools can be used? Answer Cisco IOS first divides the subinterface bandwidth by 20 (the number of PVCs) and then takes 10% (per the configuration). This command influences RIP s use of Split Horizon, not EIGRP s, so consider the routing protocol in use. Route flapping. Both. The delay interface subcommand and the metric formula both use a unit of tens-of microseconds. In this case, the delay is 180 more, and then multiplied by 256, for a total of (Note: Don t worry if your answer wasn t as detailed in this case.) Auto-summary will cause EIGRP to advertise a summary for a Class C network when advertising out an interface in a different Class C network, resulting in many summary routes. R1 will list /18 as a summary route, AD 5, with outgoing interface null0, if at least one subordinate route exists. R1 will also have routes for all the subordinate subnets in the range. Other routers will just see a summary route, with the same EIGRP AD (90) as for other internal routes. Check that the number of maximum-paths is high enough for all the routes you want to include. Configure metrics such that the alternative routes are feasible successors. EIGRP distribution lists, with a prefix-list or route-map that refers to a prefix-list for matching. An ACL can also be used, matching each prefix explicitly.

12 14 CCNP Routing and Switching ROUTE Official Cert Guide Table 5-10 Implementation Plan Configuration Memory Drill Feature Enabling EIGRP on interfaces Enabling or disabling Split Horizon for EIGRP Setting the bandwidth consumed by EIGRP on an interface Setting an interface s logical bandwidth Setting an interface s logical delay K-values Configuring an EIGRP offset list that matches a prefix Configuring an EIGRP offset list that matches a prefix and prefix length Configuring a summary route Enabling or disabling auto-summary Configuring unequal-cost load balancing Configuring an EIGRP stub router Filtering EIGRP routes using numbered ACLs Configuration Commands/Notes router eigrp autonomous-system network network-number [wildcard-mask] [no] ip split-horizon eigrp asn ip bandwidth-percent eigrp asn percent bandwidth value delay value metric weights tos k1 k2 k3 k4 k5 1) Create an IP ACL to match routes (various; considered prerequisite). 2) In EIGRP configuration mode, configure: offset-list {access-list-number access-list-name} {in out} offset [interface-type interface-number] The same as the previous row of the table, except that you create an extended IP ACL that matches the prefix with the ACL source IP address parameter, and the mask with the destination IP address field. In interface mode: ip summary-address eigrp asn prefix subnetmask [admin-distance] (EIGRP configuration mode.) [no] auto-summary maximum-paths value variance value Tune metrics to ensure feasible successor routes. eigrp stub [[connected] [summary] [static] [redistributed]] [receive-only]] access-list {1-99} {permit deny} subnet-number wildcard-mask router eigrp asn distribute-list acl-number {in out} [interfacetype number]

13 Appendix F: Completed Planning Practice Tables 15 Feature Filtering EIGRP routes using prefix lists Enabling filtering EIGRP routes using route maps Configure a default route using ip default-network Configure a default route using static routes Configuration Commands/Notes ip prefix-list [seq sequence-no] list-name [seq seq-value] {deny permit prefix/prefix-length} [ge ge-value] [le le-value] router eigrp asn distribute-list prefix prefix-list-name {in out} [interface-type number] (Create route map.) router eigrp asn distribute-list route-map route-map-name {in out} [interface-type number] ip default-network net-id ip route outgoing-interface Table 5-11 Verification Plan Memory Drill Information Needed The composite metric values for all EIGRP prefixes. Display EIGRP Split Horizon settings. Calculate the maximum bandwidth EIGRP will consume on a physical or point-topoint subinterface. Calculate the maximum bandwidth EIGRP will consume per PVC on a multipoint Frame Relay subinterface. Display the increase in RD after implementing an EIGRP offset list. Command show ip eigrp topology prefix/length show running-config show interfaces to find the interface bandwidth show running-config to find the EIGRP bandwidth percentage show interfaces to find the interface bandwidth show running-config to find the EIGRP bandwidth percentage show frame-relay pvc interface number type to find the number of active PVCs associated with the interface Calculate (interface bandwidth/# pvcs) * percentage show ip route show ip eigrp topology show ip eigrp topology prefix/length

14 16 CCNP Routing and Switching ROUTE Official Cert Guide Information Needed Display interface bandwidth and delay settings. List EIGRP K-values. Find the number of successor and feasible successor routes. Find all routes, including nonsuccessors. Determine whether the local router is a stub router. Determine whether a neighboring router is a stub router. Display a summary IP route. On summarizing router, display EIGRP topology info on a summary route. On summarizing router, display IP routes for a summary route and its subordinate routes. On summarizing router, display the administrative distance of the null route. Display the current auto-summary setting. Find the current settings of variance and maximum-paths. Display messages each time EIGRP suppresses a prefix advertisement because of Split Horizon. Display prefix lists. Display route maps. Determine whether a prefix in the EIGRP topology table has been flagged as a candidate default route. Determine whether an IP route has been flagged as a candidate default route. Display a router s preferred default route. Command show ip eigrp topology show ip eigrp topology prefix/length show ip protocols show ip eigrp topology show ip eigrp topology prefix/length show ip eigrp topology all-links show ip eigrp topology all-links prefix/ length show running-config show ip protocols show ip eigrp neighbors detail show ip route show ip eigrp topology prefix/length show ip route prefix mask longer-prefixes show ip route prefix mask show ip protocols show ip protocols debug eigrp packet show ip prefix-list show route-maps show ip eigrp topology prefix/length Look for the exterior flag setting. show ip route Look for the asterisk beside the route. show ip route Look for the gateway of last resort setting.

15 Appendix F: Completed Planning Practice Tables 17 Chapter 6 Table 6-5 Design Review Design Goal Support the routing of IPv6 routes on a network currently using EIGRP for IPv4. A router currently has a complex EIGRP configuration, with multiple EIGRP-related commands under various interfaces, in addition to multiple EIGRP commands under router configuration mode. This configuration needs to be simplified so that it becomes easier to understand and troubleshoot. Possible Implementation Choices Covered in This Chapter Configure EIGRP for IPv6, which allows the network to continue using EIGRP. Replace the router s traditional EIGRP configuration with a Named EIGRP configuration, which consolidates all of a router s EIGRP commands under a single hierarchical structure. Table 6-6 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question Some documentation refers to EIGRP for IPv4 as EIGRPv4 and to EIGRP for IPv6 as EIGRPv6. Does this mean there is a version 5 of EIGRP? If the EIGRP configuration on corporate routers is migrated from a traditional EIGRP configuration to a Named EIGRP configuration, will network technicians and help desk staff need to learn a new set of verification and troubleshooting commands? Answer No. Documentation that refers to EIGRP for IPv6 as EIGRPv6 does so because of its relationship to IPv6, not because it is the sixth generation of EIGRP. No. Even though Named EIGRP has a significantly different configuration than a traditional EIGRP configuration, the verification commands (for example, the show commands) remain the same. Table 6-7 Implementation Plan Configuration Memory Drill Feature Enable IPv6 routing. Configuration Commands/Notes ipv6 unicast-routing Enable EIGRP for IPv6. ipv6 router eigrp { } Enable IPv6 on an interface, causing a router to derive a link-local address for the interface. Configure an IPv6 address on an interface. Enable EIGRP for IPv6 on an interface. ipv6 enable ipv6 address address/prefix-length [eui-64] ipv6 eigrp asn

16 18 CCNP Routing and Switching ROUTE Official Cert Guide Feature Configure a router ID for EIGRP for IPv6. Create a Named EIGRP virtual instance. Specify an address family along with an autonomous system number. Enter Address-Family-Interface configuration mode. Enter Address-Family-Topology configuration mode for the base topology. Configuration Commands/Notes eigrp router-id rid router eigrp virtual-instance-name address-family {ipv4 ipv6} autonomoussystem asn af-interface {default interface-id} topology base Table 6-8 Verification Plan Memory Drill Information Needed Show all EIGRP-learned IPv4 routes. Show all EIGRP-learned IPv6 routes. Show the variance configured for an EIGRP for IPv4 autonomous system. Show the variance configured for an EIGRP for IPv6 autonomous system. Show the Hello Interval for an EIGRP for IPv4 autonomous system. Show the Hello Interval for an EIGRP for IPv6 autonomous system. Display the EIGRP topology table for an EIGRP for IPv4 autonomous system. Display the EIGRP topology table for an EIGRP for IPv6 autonomous system. Display sent and received updates for an EIGRP for IPv4 autonomous system. Display sent and received updates for an EIGRP for IPv6 autonomous system. Command(s) show ip route show ipv6 route show ip protocols show ipv6 protocols show ip eigrp interfaces detail show ipv6 eigrp interfaces detail show ip eigrp topology [all-links] show ipv6 eigrp topology [all-links] debug ip eigrp notifications debug ipv6 eigrp notifications

17 Appendix F: Completed Planning Practice Tables 19 Chapter 7 Table 7-7 Design Review Design Goal Improve OSPF convergence. Implement OSPF on each router so that neighborships are formed (2). Limit neighborship formation on OSPFenabled interfaces (2). The design shows branch routers with WAN interfaces in area 0 and LAN interfaces in different areas for each branch. What LSDB information do you expect to see in the branch routers? A merger design plan shows two companies with OSPF backbone areas. How can the two area 0s be connected? (2) Possible Implementation Choices Covered in This Chapter Tune OSPF Hello and Dead intervals so that neighbor failures are recognized more quickly. Discover neighbors using multicasts as a result of matching an interface with the OSPF network command, in router OSPF configuration mode. Instead of the OSPF network command, use the ip ospf process-id area area-id interface subcommand to enable OSPF on an interface. Use OSPF authentication to allow only neighbors with the correct keys. Prevent all neighborships on an interface by making the interface passive. The branch routers, traditionally less expensive, less powerful, with less memory, will need to hold the area 0 LSDB, which can become large given the design. Physical links between routers in the two area 0s. A virtual link. Table 7-8 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question What happens on a router interface on which an OSPF network command matches the interface? (2) What configuration settings prevent OSPF neighbor discovery on an OSPF-enabled interface? Answers OSPF attempts to discover OSPF neighbors by sending and receiving multicast OSPF Hellos. OSPF advertises about the subnet on the connected interface. Configuring the interface as passive.

18 20 CCNP Routing and Switching ROUTE Official Cert Guide Question What settings do potential neighbors check before becoming OSPF neighbors? (7) What settings that many CCNP candidates might think would impact OSPF neighbor relationships actually do not prevent a neighborship from forming? A design shows one main site and 100 branches, with OSPF and MPLS VPNs. How many OSPF neighborships over the WAN do you expect to see on the central-site router? A design shows one main site and 100 branches, with one Frame Relay PVC between the main site and each branch. How many OSPF neighborships over the WAN do you expect to see on the central-site router? A design shows six routers connected to the same VLAN and subnet. How many OSPF fully adjacent neighborships over this subnet do you expect each router to have? A design shows one main site and 100 branches, each connected with a VPWS service. The configuration shows that the central-site router uses a separate VLAN subinterface to connect to each branch, but the branch routers do not have a VLAN connecting to other branches. How many OSPF fully adjacent neighborships over the WAN do you expect to see on the central site router? Answers Whether the neighbor s IP address is in the same primary subnet as the local router. OSPF authentication failure. The interfaces cannot be passive. Must be in the same area. Hello and Dead intervals must match. Unique RIDs. IP MTUs must match. Mismatched process IDs on the router ospf commands. One. Each router becomes neighbors with the provider edge (PE) router inside the MPLS VPN service The central site router forms a neighborship with each branch router. The DR and BDR will be fully adjacent with each other and with all four of the other routers. The other four routers will be fully adjacent with only two routers: the DR and BDR The central site s subinterface for each VLAN acts like a separate logical interface. A DR and BDR will be used, but in this design, 100 such instances exist, and the central site will become fully adjacent with all 100 branches.

19 Table 7-9 Implementation Plan Configuration Memory Drill Feature Enabling OSPF on interfaces traditional method Enabling OSPF on interfaces using interface subcommands Setting Hello and Dead intervals Passive interfaces, with router subcommands OSPF router ID Create a virtual link through transit area X Appendix F: Completed Planning Practice Tables 21 Configuration Commands/Notes router ospf process-id network network-number wildcard-mask area area-id router ospf process-id interface type number ip ospf process-id area area-id ip ospf hello-interval timer-value ip ospf dead-interval timer-value passive-interface type number passive-interface default no passive-interface type number router-id a.b.c.d router ospf process-id area X virtual-link neighbor-rid Table 7-10 Verification Plan Memory Drill Information Needed Which routes have been added to the IP routing table by OSPF? All routes in a router s routing table The specific route for a single destination address or subnet A list of all (both static and dynamically discovered) OSPF neighbors List interfaces on which OSPF has been enabled List the number of OSPF neighbors and fully adjacent neighbors known through a particular interface Command show ip route ospf show ip route show ip route ip-address [mask] show ip ospf neighbor show ip ospf neighbor detail show ip ospf interface show ip ospf interface brief show ip protocols (if enabled with the ip ospf area interface subcommand) show ip ospf interface show ip ospf interface brief show ip ospf interface type number

20 22 CCNP Routing and Switching ROUTE Official Cert Guide Information Needed The elapsed time since a neighborship was formed The configured Hello timer for an interface The configured Dead interval timer for an interface The current actual Dead timer for a neighbor A router s RID A list of OSPF passive interfaces List traffic statistics about OSPF Display the name and status of a virtual link Command show ip protocols show ip ospf neighbor [detail] show ip ospf interface [type number] show ip ospf interface [type number] show ip ospf neighbor [detail] show ip ospf show ip ospf database show ip ospf statistics show ip protocols show ip ospf statistics show ip ospf virtual-links show ip ospf neighbor [detail] Chapter 8 Table 8-6 Design Review Design Goal The design sets specific limits to the number of Type 1 and 2 LSAs in each area. Describe how to predict the number of each type of LSA. How could you tune OSPF metrics to favor 10-Gbps links over 1-Gbps and 1-Gig over 100-Mbps? (2) The design shows one physical path from ABR1 to core subnet 1 inside area 0, and one longer area 1 path to the same subnet. What can be done to ensure that both paths can be used? Possible Implementation Choices Covered in This Chapter Add one Type 1 per internal router in that area. Add one Type 1 per ABR. Add one Type 2 per subnet in which a DR should be elected, and for which two such routers exist in that subnet. Configure all routers with an auto-cost reference bandwidth command, in router ospf configuration mode, of at least 10,000. Manually configure OSPF interface costs with the ip ospf cost cost interface subcommand. Nothing ABR1, like all ABRs, ignores Type 3 LSAs (like the LSA for subnet 1) learned in a nonbackbone area (such as area 1).

21 Appendix F: Completed Planning Practice Tables 23 Table 8-7 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question What conditions must be true for a router to create/flood a Type 2 LSA? (2) The plan shows Frame Relay with all pointto-point subinterfaces. By default, will a DR/ BDR be elected? The plan shows a reference bandwidth change planned for all routers with highspeed links, but not all other routers. What is the impact? (2) The plan shows many different WAN links speeds but with the interface bandwidths not matching the actual speed. All OSPF cost changes are made explicitly with the ip ospf cost interface subcommand. Do the incorrect bandwidths cause any OSPF problems? Answer At least two routers must be neighbors and have elected a DR. The router creating the LSA must be the DR. This is the case where, on Frame Relay, the default point-to-point OSPF network type works fine. No DR/BDR will be elected. This plan breaks the recommendation to use the same value throughout the network. Potential impacts: 1. The setting on one router changes only that router s OSPF costs. 2. It can result in poor route choices. No problem for OSPF, which uses the interface cost per ip ospf cost if it is configured. Table 8-8 Implementation Plan Configuration Memory Drill Feature Tune metrics by changing the formula for calculating OSPF cost based on interface bandwidth. Tune metrics by changing interface bandwidth. Change metrics by setting cost directly. Set the number of equal-cost OSPF routes allowed in a router s routing table. Influence the choice of DR on a LAN. (2) Configuration Commands/Notes router ospf process-id auto-cost reference-bandwidth ref-bw interface type number bandwidth bandwidth interface type number ip ospf cost cost router ospf process-id maximum-paths number Configure ip ospf priority value on the interface. Set the OSPF router ID, using either the router-id value router subcommand, creating a loopback interface with a high IP address, or another interface with a high IP address.

22 24 CCNP Routing and Switching ROUTE Official Cert Guide Table 8-9 Verification Plan Memory Drill Information Needed Display a summary of the OSPF database. Display all Type 1 Router LSAs known to a router. Display the details of a particular Type 1 Router LSA. Display all Type 2 Network LSAs known to a router. Display the details of a particular Type 2 Router LSA. Command(s) show ip ospf database show ip ospf database router show ip ospf database router lsid show ip ospf database network show ip ospf database network lsid Display all Type 3 Summary LSAs known to a router. show ip ospf database summary Display the details of a particular Type 3 Router LSA. Display a list of OSPF-enabled interfaces on a router. Determine on which interfaces a router has formed at least one OSPF neighborship. Determine the number of fully adjacent neighbors on an interface. Determine which transit networks connect to a Type 1 LSA. Determine the router that created and flooded a Type 3 LSA. Determine the router that created and flooded a Type 2 LSA. Determine the router that created and flooded a Type 1 LSA. Display the IP address of the current DR and BDR on a LAN. show ip ospf database summary lsid show ip ospf interface show ip ospf interface brief show ip ospf interface type number show ip protocols show ip ospf interface show ip ospf interface brief show ip ospf interface type number show ip ospf interface show ip ospf interface brief show ip ospf interface type number show ip ospf neighbor show ip ospf neighbor detail show ip ospf database router [lsid] show ip ospf database show ip ospf database summary show ip ospf database show ip ospf database network show ip ospf database show ip ospf database router show ip ospf neighbor [detail] show ip ospf interface type number

23 Appendix F: Completed Planning Practice Tables 25 Information Needed Display the OSPF interface cost (metric). Display all OSPF-learned routes. Display statistics about the number of SPF algorithm runs. Command(s) show ip ospf database router show ip ospf interface [brief] show ip route ospf show ip ospf [statistics] Chapter 9 Table 9-5 Design Review Design Goal When using OSPF, prevent the routers in sites for one division of the company from knowing IP routes for subnets in another division. (3) The design shows an enterprise that uses only OSPF. It lists a goal of keeping the LSDBs and routing tables in each area small. (3) The design lists a goal of extremely small LSDBs and IP routing tables on branch office routers. Which stub area types work best? (2) The design calls for the flooding of a domainwide default route to draw traffic toward Internet-connected routers. The design requires the routing of both IPv4 and IPv6 networks. (2) Possible Implementation Choices Covered in This Chapter Type 3 LSA filtering on ABRs. Type 5 LSA filtering on ASBRs. Filtering routes added by OSPF to the IP routing table. Use manual route summarization on ABRs. Use Type 3 LSA filtering. Use stub areas. Totally stubby areas. Totally NSSA areas. Use the default-information originate command on the Internet routers. You could configure two OSPF processes, an OSPFv2 process to support the routing of IPv4 networks and an OSPFv3 process (configured in the traditional fashion) to support the routing of IPv6 networks. Alternately, you could configure a single OSPFv3 Address Family hierarchy that included two Address Families, one for IPv4 and one for IPv6.

24 26 CCNP Routing and Switching ROUTE Official Cert Guide Table 9-6 Notable Questions from This Chapter to Consider During an Implementation Plan Peer Review Question The plan shows a design with area 0, with different ABRs connecting area 0 to areas 1, 2, and 3. The configurations show Type 3 LSA filtering into the nonbackbone areas but not in the opposite direction. Could this configuration filter subnets in area 1 from being seen in area 2? The design shows the configuration of Type 3 LSA filtering on an internal router in area 1. Could the filter have any effect? The plan shows the configuration of the area range command on an ABR. What is the metric for the summary route, and in what conditions will the ABR advertise the summary? The plan shows the configuration of the area 1 stub command for an area mostly located on the west coast of the United States. The company just bought another company whose sites are also on the west coast. What issues exist if you add links from the acquired company into area 1? The plan shows the configuration of the default-information originate always command on the one router to which Internet links connect. What happens to the default route when the Internet link fails, and what happens to packets destined for the Internet during this time? The plan calls for the routing of both IPv4 and IPv6 networks. What new, or renamed, LSA types might appear in an area s linkstate database? Answer Type 3 LSA filtering only filters subnets whose Type 3 LSAs would be created by that ABR. So, if the area 1 area 0 ABR created an LSA for an area 1 subnet, flooding that LSA into area 0, the area 0 area 2 ABR would not attempt to filter that subnet with Type 3 LSA filtering. No. The filtering only has effect on ABRs, for Type 3 LSAs created on that ABR. The metric, if not listed in with the cost parameter on the area range command, is the lowest cost among all subordinate routes. The ABR advertises only the summary if at least one subordinate subnet exists as an intra-area route. As a stubby area, the area will not allow the redistribution of external routes. The acquired company s routes might at least initially need to be redistributed into OSPF. This command makes the router always advertise a default route, even if that router s default route pointing toward the Internet fails. As such, all packets destined outside the enterprise will still pass through the enterprise to this router and then be discarded. With OSPFv3, the Type 3 LSAs have been renamed to Interarea prefix LSAs for ABRs. The Type 4 LSAs have been renamed to Interarea router LSAs for ASBRs. Also, two new LSAs have been introduced: the Type 8 Link LSAs and Type 9 Intra-area prefix LSAs.

25 Table 9-7 Implementation Plan Configuration Memory Drill Feature Filter Type 3 LSAs from being sent into an area. Filter the OSPF routes calculated on one router from being added to that one router s routing table. Configure route summarization on ABRs. Configure route summarization on ASBRs. Configure the OSPF domain-wide advertisement of a default route. Configure stubby or totally stubby areas. Configure NSSAs or totally NSSAs. Start an OSPFv3 process, using the traditional configuration approach. Instruct an interface to participate in an OSPFv3 area, using the traditional configuration approach. Start an OSPFv3 process, using the Address Family configuration approach. Instruct an interface to participate in an OSPFv3 area, using the Address Family configuration approach. Appendix F: Completed Planning Practice Tables 27 Configuration Commands/Notes (Create an IP prefix list) router ospf process-id area area-number filterlist prefix listname {in out} (Create an IP prefix list) router ospf process-id distribute-list prefix list-name in router ospf process-id area area-id range ip-address mask [cost cost] router ospf process-id summary-address {ip-address mask prefix mask} router ospf process-id default-information originate [always] [cost metric] [metric-type type] router ospf process-id area area-number stub (stubby areas and totally stubby areas on non-abrs) area area-number stub no-summary (totally stubby areas on ABRs only) area area-num default-cost cost (optional) router ospf process-id area area-number nssa (NSSAs and totally NSSAs on non-abrs) area area-number nssa no-summary (totally NSSAs on ABRs only) area area-num default-cost cost (optional) ipv6 router ospf process-id ipv6 ospf process-id area area_number router ospfv3 process-id ospfv3 process-id {ip4 ipv6}

26 28 CCNP Routing and Switching ROUTE Official Cert Guide Table 9-8 Verification Plan Memory Drill Information Needed Display all IP routes for subnets in a range, regardless of prefix length. Display the contents of an IP prefix list. Display details of all Type 3 LSAs known to a router. Display details of all Type 5 external LSAs known to a router. Display the metric advertised in a summary route created by the area range command. Display the metric advertised in a summary route created by the summary-address command. Discover whether a router resides in a stubby area, and if so, which kind. Confirm stubby area concepts by looking at the numbers of Type 3 and Type 5 LSAs known to a router. List the interfaces participating in a traditional OSPFv3 configuration. Display neighbors in a traditional OSPFv3 configuration. Display the contents of a router s linkstate database using a traditional OSPFv3 configuration. List the interfaces participating in an IPv4 and/or IPv6 OSPFv3 routing process configured with the OSPFv3 Address Family configuration approach. Display IPv4 and/or IPv6 neighbors configured with the OSPFv3 Address Family configuration approach. Display the contents of a router s link-state database, containing entries for IPv4 and/or IPv6 networks, using the OSPFv3 Address Family configuration approach. Command(s) show ip route subnet mask longer-prefixes show ip prefix-list [name] show ip ospf database summary show ip ospf database external show ip ospf database summary [lsid] show ip ospf database external [lsid] show ip ospf show ip ospf database database-summary show ipv6 ospf interface brief show ipv6 ospf neighbors show ipv6 ospf database show ospfv3 interface brief show ospfv3 neighbor show ospfv3 database

27 Appendix F: Completed Planning Practice Tables 29 Chapter 10 Table Design Review Design Goal A design shows Router R1 as being connected to both an EIGRP and OSPF routing domain, with all external EIGRP routes using a particular set of component EIGRP metrics. How can these metrics be set? (3) A design shows Router R1 as being connected to two different EIGRP domains, with redistribution planned. Can the design cause the routers to calculate metrics based on both the metric assigned when redistributing and the internal EIGRP topology? The same design as in the previous row is shown, except describe whether the design can cause the routers to calculate metrics based solely on the metric components assigned when redistributing. A design shows Router R1 as being connected to two different OSPF domains, with redistribution planned, and all routes calculated by including internal and external OSPF distance. The same design as in the previous row is shown, except that all external route metrics are based solely on external metrics. Filter routes when redistributing. (2) Set different metrics for different routes redistributed from one routing source. Set some OSPF routes as E1 and some as E2, when redistributed from one routing source. Possible Implementation Choices Covered in This Chapter Set the metrics on the redistribute command. Use the default-metric command. Set the metric inside a route map referenced by the redistribute command. No special action is required; this behavior occurs for all routes redistributed into EIGRP. The behavior is not supported by EIGRP. Routes must be distributed as E1 routes, using redistribute... metric-type 1. Routes must be distributed as E2 routes, using redistribute... metric-type 2, or by omitting the metric-type keyword on the redistribute command. Refer to a route map on the redistribute command. Use a distribute-list command that refers to the routing source. Use the redistribute... route-map option. Use the redistribute... route-map option, with the set metric-type command.