|
|
Multi-area configuration
Network types
Broadcast, Point-to-Point, Multipoint, and NBMA
Authentication
Stub and not-so-stubby areas
Address summarization and filtering between areas
Virtual links
Policy
Route redistribution
Route tagging
RIP configuration
Metrics, timers, and various other "knobs"
This chapter details various JNCIP-level OSPF configuration scenarios, and provides examples of the verification methods that can be used to confirm the proper operation of the OSPF protocol. I'm assuming that your configurations are currently based on the case study criteria presented at the end of Chapters 1 and 2. You will now be adding the OSPF protocol to your test bed. If you are unsure as to the state of your routers, you should compare your configuration against those provided at the end of Chapters 1 and 2, and verify that all of your router interfaces are operational before proceeding.
Proper Interior Gate Protocol (IGP) operation is a critical factor in the JNCIP exam. Many of the product features and capabilities you will be expected to configure throughout the exam rely on your IGP for routing within your Autonomous System (AS). Internal Border Gateway Protocol (IBGP) peering is a common example of how a protocol or service can depend on the correct operation of your IGP. Because the IGP provides the information needed to route between loopback addresses, IBGP peering between loopback interfaces can only succeed when your IGP is operational.
Tip | Because IGP problems can produce operational problems in wide-ranging and numerous aspects of your configuration, the rapid and effective isolation of IGP problems is a critical lab skill that a successful JNCIP candidate must master. For example, you can differentiate between IGP and IBGP problems by conducting ping tests between the loopback addresses of the routers in question. By taking care to source the pings from each router's loopback address, you can confirm that the IGP is, or is not, providing the routing services needed to establish your loopback-based IBGP peering sessions. Assuming that these tests fail, the realization that you are dealing with an IGP connectivity problem will ensure that you will not waste valuable time chasing down nonexistent IBGP problems. |
|
|