Nokia Lab | LAB 2 OSPF |
Introduction
Hello everyone!
It's my second Nokia lab. I've tried to cover the main scope of OSPF questions. Lets lab!
Please check my first lab for input information.
Topology example
Lab tasks and questions:
- Basic OSPF (Backbone area)
- configure OSPF area 0 (R1 and R2, use P2P interface type, add “system” interface to OSPF)
- configure BFD and authentication on interfaces
- examine BFD session
- check neighbors state
- examine the connection between OSPF adjacency and BFD session
- How can you break adjacency? Try it. What factors can influence adjacency?
- examine LSDB
- What LSA types do you see?
- examine every LSA in detail
- examine route table
- What is the default preference of OSPF routes?
- Multi-area OSPF(Area 0, Area 1 TNSSA, Area 2 Normal, Area 3 Totally Stub)
- configure area 1 as a Totally NSSA area
- run debug OSPF hello packets between R1 and R3
- examine hello packets
- Does it contain special bits?
- What is the difference between NSSA and Totally NSSA areas?
- create additional loopback interface on R3
- export it to OSPF by policy
- What router type is R3?
- examine LSDB on R3 - especially check NSSA external LSA
- Does it contain special bits? Describe purpose of them
- examine LSDB on R1
- How does R1 propagate external routes to backbone area from NSSA area?
- configure area 2 as a Normal area (R1 <--> R5, R2 <--> R5)
- examine Router LSA from R1 and R2 in area 2
- Does it have a special bit? What does it mean?
- examine LSDB on R5
- What LSA types does LSDB contain?
- Does LSDB contain LSA with additional addresses from R3(loopback interfaces)?
- examine route table on R5
- Do you have IP reachability between R3 and R5 "system" addresses?
- How to resolve this issue? Do it.
- configure additional loopback interface on R5
- export it to OSPF by policy
- examine R1, R2, R3, and R5 LSDB
- examine Router LSA from R5
- Does it have a special bit? What does it mean?
- examine summary LSA from R1 and R2
- describe main prupose and flooding behaviors of Summary LSAs
- describe OSPF loop avoidance mechanism
- examine AS external LSA from R5
- Does R3 LSDB contain this LSA? Why?
- What is the area number of these LSA?
- Describe AS external LSA metric types
- check reachability between R3 and R5 loopback interfaces
- Describe control plane process
- LSA propagation between R3 and R5
- Route table manager actions
- configure area 3 as a Totally Stub area
- What is the difference between Stub and Totally Stub areas?
- examine LSDB on R4
- What LSA types does LSDB contain? Any AS external LSAs?
- configure three loopback interfaces(address from the same subnet) on R4 and add them to OSPF as passive
- summarize prefixes (from area 3)
- Where is the summarization point?
- Describe summarization rules and behavior
- check reachability between R3 and R4 loopback interfaces
- Describe control plane process
- describe LSA propagation between R3 and R4
- describe route table manager actions
- Multi-area OSPFv3 (the same topology)
- check that all routers have ipv6 configuration("system" interface, P2P interfaces, and so on)
- create the same setup as for OSPF (area 0, area 1 - TNSSA, area 2 - Normal, area 3 Totally Stub)
- Area 0
- examine LSDB on R1
- What is the main difference between OSPF LSDB and OSPFv3 LSDB?
- Does LSDB contain Link LSA?
- Examine Link LSA
- Area 1
- configure additional loopback interface(ipv6) on R3
- export it to OSPF by policy
- examine LSDB on R3
- Does it have NSSA LSA?
- Area 2
- configure additional loopback interface(ipv6) on R5
- export it to OSPF by policy
- examine LSDB on R5
- What LSA types does LSDB have?
- check connectivity between R3 loopback and R5 loopback
- Describe control plane process
- describe LSA propagation between R3 and R5
- describe route table manager actions
Github project
Useful debug commands
show router ospf neighbors
show router ospf database {detail}
show router ospf3 neighbors
show router ospf3 database {detail}
show router ospf database {detail}
show router ospf3 neighbors
show router ospf3 database {detail}
show router ospf3 interface {name} database {detail}
Just virtual link is missed.
ReplyDelete