Real World Application & Core Knowledge
If you’ve completed Lab 8-5 – Configuring EIGRP Timers and Lab 7-3 – Configuring RIP Timers then you should know that the routing protocol timers are the lively hood of a routing protocol. It is what the routing protocol does to maintain a neighbor relationship and ensure routes are propagated correctly.
By default the timers on a broadcast network which include ethernet, point-to-point and point-to-multipoint are 10 seconds hello and 40 seconds dead. The timers on a non-broadcast network are 30 seconds hello 120 seconds dead.
The Hello and Dead timers must match to form a neighbor relationship in OSPF. Also when combining different OSPF network types such as point-to-point and point-to-multipoint you must adjust the timers to match as point-to-multipoint is 30/120 by default and point-to-point is 10/40 by default.
The dead-timer is typically four times the amount of the hello timer to give time for packet loss/drops due to network issues and/or quality of service policies.
In this lab you will configure the OSPF hello and dead on the point to point link between R2 and R3 to 1 second hello and 4 second dead. The commands to configure the timers statically are executed under interface configuration mode and is done on a per-interface basis.
To configure the hello timer, you’d use the ip ospf hello-interval # whereas # is a number between 1 and 65535 seconds.
To configure the dead timer you’ll use the ip ospf dead-interval # whereas # is a number between 1 and 65535 seconds.
To verify the OSPF timers on a particular interface you’ll use the show ip ospf interface interfacename#/#.
Familiarize yourself with the following new command(s);
ip ospf hello-interval # – This command is executed in interface configuration mode to statically set the hello-interval timer for OSPF hello packets exiting the specified interface.
ip ospf dead-interval # – This command is executed in interface configuration mode to statically set the dead-interval timer for OSPF which is the amount of time a router will go waiting for a hello packet before declaring a particular neighbor down and executing the SPF algorithm to reconverge.
The following logical topology shown below is used in labs found through out Section 9 – Configuring OSPF;
Lab Prerequisites
• If you completed lab 9-6 you can start where you’ve left off or you can load the Free CCNA Workbook GNS3 topology; start and establish a console session with R1, R2, R3, R4, R5 and SW1 then load their initial configurations included below by copying the config from the textbox and pasting it into the routers console.
Initial Configurations
Lab Objectives
• Configure the interfaces on the point-to-point link between R2 and R3 to send OSPF hello’s every 1 second and declare the neighboring router down if a hello is not received within 4 seconds.
• Verify the OSPF hello and dead timers on both R2 and R3.
Lab Instruction
Objective 1. – Configure the interfaces on the point-to-point link between R2 and R3 to send OSPF hello’s every 1 second and declare the neighboring router down if a hello is not received within 4 seconds.
R2>enable |
R3>enable |
Objective 2. – Verify the OSPF hello and dead timers on both R2 and R3.
R2#show ip ospf interface Serial1/2 |
R3#show ip ospf interface Serial1/1
Serial1/1 is up, line protocol is up
Internet Address 10.1.23.2/30, Area 3
Process ID 1, Router ID 3.3.3.3, Network Type POINT_TO_POINT, Cost: 64
Transmit Delay is 1 sec, State POINT_TO_POINT
Timer intervals configured, Hello 1, Dead 4, Wait 4, Retransmit 5
oob-resync timeout 40
Hello due in 00:00:00
Supports Link-local Signaling (LLS)
Cisco NSF helper support enabled
IETF NSF helper support enabled
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 4 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 2.2.2.2
Suppress hello for 0 neighbor(s)
R3#
0 komentar:
Posting Komentar
Silahkan isi kesan hati anda di sini !!!