why are the OSPF routers stuck in Init state?

— Exhibit —
Mar 16 17:54:51.930726 OSPF periodic xmit from 172.14.10.1 to 224.0.0.5 (IFL 69 area 0.0.0.0)
Mar 16 17:54:55.566920 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:54:56.152585 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:54:56.152721 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state
QUIET->GEN_PENDING
Mar 16 17:54:56.153271 OSPF trigger router LSA 0x156d0f0 build for area 0.0.0.0 lsa-id
192.168.2.1
Mar 16 17:54:56.157854 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state
GEN_PENDING->QUIET
Mar 16 17:54:56.157971 OSPF built router LSA, area 0.0.0.0, link count 2
Mar 16 17:54:56.158300 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.0)
Mar 16 17:54:56.158380 Version 2, length 44, ID 192.168.2.1, area 0.0.0.0
Mar 16 17:54:56.158435 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:54:56.158485 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:54:56.158949 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:54:56.159276 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.0)
Mar 16 17:54:56.159331 Version 2, length 44, ID 192.168.2.1, area 0.0.0.0
Mar 16 17:54:56.159401 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:54:56.159563 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:54:56.168108 OSPF DR is 192.168.2.1, BDR is 0.0.0.0

Mar 16 17:54:58.237416 OSPF rcvd Hello 172.14.10.2 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.0)
Mar 16 17:54:58.237540 Version 2, length 44, ID 192.168.2.1, area 0.0.0.0
Mar 16 17:54:58.237623 checksum 0x0, authtype 0
Mar 16 17:54:58.237698 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:54:58.237751 dead_ivl 40, DR 172.14.10.2, BDR 0.0.0.0
— Exhibit —
Click the Exhibit button.
Looking at the traceoptions output in the exhibit, why are the OSPF routers stuck in Init state?

— Exhibit —
Mar 16 17:54:51.930726 OSPF periodic xmit from 172.14.10.1 to 224.0.0.5 (IFL 69 area 0.0.0.0)
Mar 16 17:54:55.566920 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:54:56.152585 ospf_trigger_build_telink_lsas : No peer found
Mar 16 17:54:56.152721 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state
QUIET->GEN_PENDING
Mar 16 17:54:56.153271 OSPF trigger router LSA 0x156d0f0 build for area 0.0.0.0 lsa-id
192.168.2.1
Mar 16 17:54:56.157854 ospf_set_lsdb_statE. Router LSA 192.168.2.1 adv-rtr 192.168.2.1 state
GEN_PENDING->QUIET
Mar 16 17:54:56.157971 OSPF built router LSA, area 0.0.0.0, link count 2
Mar 16 17:54:56.158300 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.0)
Mar 16 17:54:56.158380 Version 2, length 44, ID 192.168.2.1, area 0.0.0.0
Mar 16 17:54:56.158435 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:54:56.158485 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:54:56.158949 OSPF DR is 192.168.2.1, BDR is 0.0.0.0
Mar 16 17:54:56.159276 OSPF sent Hello 172.14.10.1 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.0)
Mar 16 17:54:56.159331 Version 2, length 44, ID 192.168.2.1, area 0.0.0.0
Mar 16 17:54:56.159401 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:54:56.159563 dead_ivl 40, DR 172.14.10.1, BDR 0.0.0.0
Mar 16 17:54:56.168108 OSPF DR is 192.168.2.1, BDR is 0.0.0.0

Mar 16 17:54:58.237416 OSPF rcvd Hello 172.14.10.2 -> 224.0.0.5 (ge-0/0/1.0 IFL 69 area
0.0.0.0)
Mar 16 17:54:58.237540 Version 2, length 44, ID 192.168.2.1, area 0.0.0.0
Mar 16 17:54:58.237623 checksum 0x0, authtype 0
Mar 16 17:54:58.237698 mask 255.255.255.0, hello_ivl 10, opts 0x2, prio 128
Mar 16 17:54:58.237751 dead_ivl 40, DR 172.14.10.2, BDR 0.0.0.0
— Exhibit —
Click the Exhibit button.
Looking at the traceoptions output in the exhibit, why are the OSPF routers stuck in Init state?

A.
There is an MTU mismatch.

B.
There are duplicate router IDs.

C.
The routers are in different areas.

D.
No BDR has been elected.



Leave a Reply 0

Your email address will not be published. Required fields are marked *