OSPF RID lab??? Didn't go as planned.....

Hi guys...I set up 5 routers on an ethernet segment in order to test out OSPF behavior....I set all ip addresses in the 192.168.15.0/24 network and advertised those into OSPF....After full convergence,my RID for each router was the ip address of the interface(s)...So I went back and MANUALLY set my RID to be the newly created loopbacks I made AFTER convergence. I know that the processes have to be cleared in order to take effect,so if I went to my switch and shut every switchport connecting my OSPF segments,wouldn't that be the same as clearing the processes(tearing down neighbor relationship). And I no shut the interfaces,BUT the RID for my OSPF didn't change. It's my understanding that even if your highest configed interface(loopback in this case) isn't being advertised into OSPF,it will become the RID for that segment.....What am I missing???

Find more posts tagged with

Comments

ande0255

Have you tried 'debug ip ospf neighbor' when you shut down the interface and bring it back up to see what happens to the relationship?

iwannaknowIT

No.....What good are the tools for troubleshooting if I don't use them?? Great suggestion...it slipped my mind.....About to run it now......Thanks

iwannaknowIT

My results after shutdown of the switch....
R1#debug ip ospf adj
OSPF adjacency events debugging is on
R1#
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
01:29:49: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.2 on FastEthernet0/0 from FULL to DOWN, Neighbor Down: Interface down or detached
01:29:49: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000011
01:29:49: OSPF: Build net LSA for area 1, router ID 192.168.15.1, seq 0x8000000c
01:29:49: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.3 on FastEthernet0/0 from FULL to DOWN, Neighbor Down: Interface down or detached
01:29:49: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000012
01:29:49: OSPF: Build net LSA for area 1, router ID 192.168.15.1, seq 0x8000000d
01:29:49: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.4 on FastEthernet0/0 from FULL to DOWN, Neighbor Down: Interface down or detached
01:29:49: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000012
01:29:49: OSPF: Build net LSA for area 1, router ID 192.168.15.1, seq 0x8000000e
01:29:49: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.5 on FastEthernet0/0 from FULL to DOWN, Neighbor Down: Interface down or detached
01:29:49: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000012
01:29:49: OSPF: No full nbrs to build Net Lsa for interface FastEthernet0/0
01:29:49: OSPF: DR/BDR election on FastEthernet0/0
01:29:49: OSPF: Elect BDR 0.0.0.0
01:29:49: OSPF: Elect DR 0.0.0.0
01:29:49: OSPF: Elect BDR 0.0.0.0
01:29:49: OSPF: Elect DR 0.0.0.0
01:29:49: DR: none BDR: none
01:29:49: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000012
01:29:49: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000012
R1#

ande0255 wrote: »

Have you tried 'debug ip ospf neighbor' when you shut down the interface and bring it back up to see what happens to the relationship?

iwannaknowIT

Didn't have full screen of no sh,but here's the partial.......

01:37:08: OSPF: end of Wait on interface FastEthernet0/0
01:37:08: OSPF: DR/BDR election on FastEthernet0/0
01:37:08: OSPF: Elect BDR 192.168.15.5
01:37:08: OSPF: Elect DR 192.168.15.5
01:37:08: DR: 192.168.15.5 (Id) BDR: 192.168.15.5 (Id)
01:37:08: OSPF: Send DBD to 192.168.15.5 on FastEthernet0/0 seq 0x4253 opt 0x00 flag 0x7 len 32
01:37:08: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000016
01:37:08: OSPF: Rcv DBD from 192.168.15.5 on FastEthernet0/0 seq 0x49fa opt 0x00 flag 0x7 len 32 mtu 1500 state EXSTART
01:37:08: OSPF: NBR Negotiation Done. We are the SLAVE
01:37:08: OSPF: Send DBD to 192.168.15.5 on FastEthernet0/0 seq 0x49fa opt 0x00 flag 0x2 len 152
01:37:08: OSPF: DR/BDR election on FastEthernet0/0
01:37:08: OSPF: Elect BDR 192.168.15.5
01:37:08: OSPF: Elect DR 192.168.15.5
01:37:08: DR: 192.168.15.5 (Id) BDR: 192.168.15.5 (Id)
01:37:08: OSPF: Rcv DBD from 192.168.15.5 on FastEthernet0/0 seq 0x49fb opt 0x00 flag 0x3 len 152 mtu 1500 state EXCHANGE
01:37:08: OSPF: Send DBD to 192.168.15.5 on FastEthernet0/0 seq 0x49fb opt 0x00 flag 0x0 len 32
01:37:08: OSPF: Rcv DBD from 192.168.15.5 on FastEthernet0/0 seq 0x49fc opt 0x00 flag 0x1 len 32 mtu 1500 state EXCHANGE
01:37:08: OSPF: Send DBD to 192.168.15.5 on FastEthernet0/0 seq 0x49fc opt 0x00 flag 0x0 len 32
01:37:08: Exchange Done with 192.168.15.5 on FastEthernet0/0
01:37:08: OSPF: Database request to 192.168.15.5
01:37:08: OSPF: sent LS REQ packet to 192.168.15.5, length 12
01:37:08: OSPF: Send DBD to 192.168.15.5 on FastEthernet0/0 seq 0x49fc opt 0x00 flag 0x0 len 32
01:37:08: Synchronized with with 192.168.15.5 on FastEthernet0/0, state FULL
01:37:08: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.5 on FastEthernet0/0 from LOADING to FULL, Loading Done
01:37:08: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000016
01:37:08: OSPF: DR/BDR election on FastEthernet0/0
01:37:08: OSPF: Elect BDR 192.168.15.5
01:37:08: OSPF: Elect DR 192.168.15.5
01:37:08: DR: 192.168.15.5 (Id) BDR: 192.168.15.5 (Id)
01:37:08: OSPF: DR/BDR election on FastEthernet0/0
01:37:08: OSPF: Elect BDR 192.168.15.1
01:37:08: OSPF: Elect DR 192.168.15.5
01:37:08: OSPF: Elect BDR 192.168.15.1
01:37:08: OSPF: Elect DR 192.168.15.5
01:37:08: DR: 192.168.15.5 (Id) BDR: 192.168.15.1 (Id)
01:37:08: OSPF: Send DBD to 192.168.15.3 on FastEthernet0/0 seq 0x5ae0 opt 0x00 flag 0x7 len 32
01:37:08: OSPF: Send DBD to 192.168.15.4 on FastEthernet0/0 seq 0x5005 opt 0x00 flag 0x7 len 32
01:37:08: OSPF: Send DBD to 192.168.15.2 on FastEthernet0/0 seq 0x26d5 opt 0x00 flag 0x7 len 32
01:37:08: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000017
01:37:08: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000017
01:37:08: OSPF: DR/BDR election on FastEthernet0/0
01:37:08: OSPF: Elect BDR 192.168.15.1
01:37:08: OSPF: Elect DR 192.168.15.5
01:37:08: DR: 192.168.15.5 (Id) BDR: 192.168.15.1 (Id)
01:37:13: OSPF: Send DBD to 192.168.15.2 on FastEthernet0/0 seq 0x26d5 opt 0x00 flag 0x7 len 32
01:37:13: OSPF: Send DBD to 192.168.15.4 on FastEthernet0/0 seq 0x5005 opt 0x00 flag 0x7 len 32
01:37:13: OSPF: Send DBD to 192.168.15.3 on FastEthernet0/0 seq 0x5ae0 opt 0x00 flag 0x7 len 32
01:37:13: OSPF: Rcv DBD from 192.168.15.3 on FastEthernet0/0 seq 0x50c4 opt 0x00 flag 0x7 len 32 mtu 1500 state EXSTART
01:37:13: OSPF: NBR Negotiation Done. We are the SLAVE
01:37:13: OSPF: Send DBD to 192.168.15.3 on FastEthernet0/0 seq 0x50c4 opt 0x00 flag 0x2 len 152
01:37:13: OSPF: Rcv DBD from 192.168.15.3 on FastEthernet0/0 seq 0x50c5 opt 0x00 flag 0x3 len 172 mtu 1500 state EXCHANGE
01:37:13: OSPF: Send DBD to 192.168.15.3 on FastEthernet0/0 seq 0x50c5 opt 0x00 flag 0x0 len 32
01:37:13: OSPF: Rcv DBD from 192.168.15.3 on FastEthernet0/0 seq 0x50c6 opt 0x00 flag 0x1 len 32 mtu 1500 state EXCHANGE
01:37:13: OSPF: Send DBD to 192.168.15.3 on FastEthernet0/0 seq 0x50c6 opt 0x00 flag 0x0 len 32
01:37:13: Exchange Done with 192.168.15.3 on FastEthernet0/0
01:37:13: OSPF: Database request to 192.168.15.3
01:37:13: OSPF: sent LS REQ packet to 192.168.15.3, length 12
01:37:13: OSPF: Send DBD to 192.168.15.3 on FastEthernet0/0 seq 0x50c6 opt 0x00 flag 0x0 len 32
01:37:13: Synchronized with with 192.168.15.3 on FastEthernet0/0, state FULL
01:37:13: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.3 on FastEthernet0/0 from LOADING to FULL, Loading Done
01:37:13: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000017
01:37:18: OSPF: DR/BDR election on FastEthernet0/0
01:37:18: OSPF: Elect BDR 192.168.15.1
01:37:18: OSPF: Elect DR 192.168.15.5
01:37:18: DR: 192.168.15.5 (Id) BDR: 192.168.15.1 (Id)
01:37:18: OSPF: Rcv DBD from 192.168.15.2 on FastEthernet0/0 seq 0x6312 opt 0x00 flag 0x7 len 32 mtu 1500 state EXSTART
01:37:18: OSPF: NBR Negotiation Done. We are the SLAVE
01:37:18: OSPF: Send DBD to 192.168.15.2 on FastEthernet0/0 seq 0x6312 opt 0x00 flag 0x2 len 152
01:37:18: OSPF: Rcv DBD from 192.168.15.4 on FastEthernet0/0 seq 0x3afb opt 0x00 flag 0x7 len 32 mtu 1500 state EXSTART
01:37:18: OSPF: NBR Negotiation Done. We are the SLAVE
01:37:18: OSPF: Send DBD to 192.168.15.4 on FastEthernet0/0 seq 0x3afb opt 0x00 flag 0x2 len 152
01:37:18: OSPF: Rcv DBD from 192.168.15.2 on FastEthernet0/0 seq 0x6313 opt 0x00 flag 0x3 len 172 mtu 1500 state EXCHANGE
01:37:18: OSPF: Send DBD to 192.168.15.2 on FastEthernet0/0 seq 0x6313 opt 0x00 flag 0x0 len 32
01:37:18: OSPF: DR/BDR election on FastEthernet0/0
01:37:18: OSPF: Elect BDR 192.168.15.1
01:37:18: OSPF: Elect DR 192.168.15.5
01:37:18: DR: 192.168.15.5 (Id) BDR: 192.168.15.1 (Id)
01:37:18: OSPF: Rcv DBD from 192.168.15.4 on FastEthernet0/0 seq 0x3afc opt 0x00 flag 0x3 len 172 mtu 1500 state EXCHANGE
01:37:18: OSPF: Send DBD to 192.168.15.4 on FastEthernet0/0 seq 0x3afc opt 0x00 flag 0x0 len 32
01:37:18: OSPF: DR/BDR election on FastEthernet0/0
01:37:18: OSPF: Elect BDR 192.168.15.1
01:37:18: OSPF: Elect DR 192.168.15.5
01:37:18: DR: 192.168.15.5 (Id) BDR: 192.168.15.1 (Id)
01:37:18: OSPF: Rcv DBD from 192.168.15.2 on FastEthernet0/0 seq 0x6314 opt 0x00 flag 0x1 len 32 mtu 1500 state EXCHANGE
01:37:18: OSPF: Send DBD to 192.168.15.2 on FastEthernet0/0 seq 0x6314 opt 0x00 flag 0x0 len 32
01:37:18: Exchange Done with 192.168.15.2 on FastEthernet0/0
01:37:18: OSPF: Database request to 192.168.15.2
01:37:18: OSPF: sent LS REQ packet to 192.168.15.2, length 12
01:37:18: OSPF: Send DBD to 192.168.15.2 on FastEthernet0/0 seq 0x6314 opt 0x00 flag 0x0 len 32
01:37:18: OSPF: Rcv DBD from 192.168.15.4 on FastEthernet0/0 seq 0x3afd opt 0x00 flag 0x1 len 32 mtu 1500 state EXCHANGE
01:37:18: OSPF: Send DBD to 192.168.15.4 on FastEthernet0/0 seq 0x3afd opt 0x00 flag 0x0 len 32
01:37:18: Exchange Done with 192.168.15.4 on FastEthernet0/0
01:37:18: OSPF: Database request to 192.168.15.4
01:37:18: OSPF: sent LS REQ packet to 192.168.15.4, length 12
01:37:18: OSPF: Send DBD to 192.168.15.4 on FastEthernet0/0 seq 0x3afd opt 0x00 flag 0x0 len 32
01:37:18: Synchronized with with 192.168.15.2 on FastEthernet0/0, state FULL
01:37:18: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.2 on FastEthernet0/0 from LOADING to FULL, Loading Done
01:37:18: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000017
01:37:18: Synchronized with with 192.168.15.4 on FastEthernet0/0, state FULL
01:37:18: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.15.4 on FastEthernet0/0 from LOADING to FULL, Loading Done
01:37:18: OSPF: Build router LSA for area 1, router ID 192.168.15.1, seq 0x80000017

ande0255

So are all routers connected to the switch interfaces on the same network? Edited my crappy text pic out of this post cause its not posting right, but does every router have one interface connected to the switch, so essentially 5 routers in one broadcast domain?

networker050184

You need to restart the entire ospf process, not just reform neighbors. Sometimes even that doesn't work.

iwannaknowIT

ande0255 wrote: »

So are all routers connected to the switch interfaces on the same network? Edited my crappy text pic out of this post cause its not posting right, but does every router have one interface connected to the switch, so essentially 5 routers in one broadcast domain?

That's correct....5 FA0/0 ports connected from FA0/1-5 on the switch.....I thought disabling the ports would simulate a "clear ip ospf process" since trying to do it one by one would defeat my purpose.....DAMN THESE CBT NUGGETS MAKING ME LEARN!! Lol..

Danielh22185

networker050184 wrote: »

You need to restart the entire ospf process, not just reform neighbors. Sometimes even that doesn't work.

^^ This.

OSPF is still running on the routers, just because you tear down the neighbor adjacencies doesn't mean new RIDs will be leared. The routers will essenctially re-use the old RID. You MUST restart the OSPF process completly to flush any old information. It would be best to do it on all routers running OSPF.

EdTheLad

Yes as stated, the ospf RID will not change unless the the ospf process is restarted manually or due to reload. Another test you can do is, remove the loopbacks, reset ospf process and watch highest physical interface become RID. Reload the process, RID stays as highest physical. Disconnect the physical on RID interface, you will see even with the interface down the RID will stay the same. I used to wonder why bother with the loopbacks for stability? Now reload the router or ospf process and you will see the RID change. So its best to use a loopback, just in case the RID interface goes down and the ospf process reloads.

iwannaknowIT

Ok guys.....Thanks for the directions/advice.....Defenitely gonna lab out OSPF to gain the full understanding of the reactions of it's actions.........This is what our network runs,via hub and spoke topology......