03-11-2012 04:49 AM - edited 03-04-2019 03:37 PM
Hi Mates,
Bit confussed for some of the routes get the timer period changed . show ip ospf output provided below:
WANEDGE-#sh ip route 10.107.4.245 …………………..
Routing entry for 10.107.0.0/16
Known via "ospf 300", distance 110, metric 1, type extern 2, forward metric 1
Last update from 10.120.105.34 on GigabitEthernet1/0/11, 1d00h ago
Routing Descriptor Blocks:
* 10.120.106.230, from 10.130.240.62, 1d00h ago, via GigabitEthernet1/0/12
Route metric is 1, traffic share count is 1
10.120.105.34, from 10.130.240.62, 1d00h ago, via GigabitEthernet1/0/11
Route metric is 1, traffic share count is 1
**************************
WANEDGE-#sh ip route 10.136.118.0 ……………….
Routing entry for 10.136.118.0/24
Known via "ospf 300", distance 110, metric 1
Tag 65527, type extern 2, forward metric 1
Last update from 10.120.105.34 on GigabitEthernet1/0/11, 1d00h ago
Routing Descriptor Blocks:
* 10.120.106.230, from 10.130.240.62, 1d00h ago, via GigabitEthernet1/0/12
Route metric is 1, traffic share count is 1
Route tag 65527
10.120.105.34, from 10.130.240.62, 1d00h ago, via GigabitEthernet1/0/11
Route metric is 1, traffic share count is 1
Route tag 65527
Does it mean that the Ospf routes has been got flushed for the mention destinaion network. Need a small help for my understanding and what may be reason to get those timer value reset again.
03-11-2012 07:05 AM
The route time that you're seeing is how long the route has been valid in the table. If it's dropping from say, 20 days to 1 day, then the route is dropping out of the table somehow. You can go to the router in question and do a 'show ip ospf neighbor
' to see how long the neighbors have been up to verify which neighbor it's having a problem with.Neighbor 10.124.0.12, interface address 10.124.0.12
In the area 4 via interface FastEthernet0/1
Neighbor priority is 1, State is FULL, 6 state changes
DR is 10.124.0.4 BDR is 10.124.0.12
Options is 0x52
LLS Options is 0x1 (LR)
Dead timer due in 00:00:36
Neighbor is up for 23:40:49
Index 1/2, retransmission queue length 0, number of retransmission 4
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 4 msec
03-11-2012 01:10 PM
Hi J,
Am too much thankful for the provided clarification.
regards// Sanjay
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide