JN0-691 · Question #88
Referring to the exhibit, which two OSPF adjacency problems are present? (Choose two.) May 20 22:27:04.010297 OSPF rcvd Hello 192.168.0.2 -> 224.0.0.5 (ge- 1/1/2.0 IFL 343 area 0.0.0.0) May 20…
The correct answer is B. duplicate router ID D. area number mismatch. See the full explanation below for the reasoning.
Question
Referring to the exhibit, which two OSPF adjacency problems are present? (Choose two.) May 20 22:27:04.010297 OSPF rcvd Hello 192.168.0.2 -> 224.0.0.5 (ge- 1/1/2.0 IFL 343 area 0.0.0.0) May 20 22:27:04.010320 Version 2, length 44, ID 10.10.10.1, area 0.0.0.1 May 20 22:27:04.010342 checksum 0x166d, authtype 0 May 20 22:27:04.010365 mask 255.255.255.252, hello_ivl 10, opts 0x12, prio 128 May 20 22:27:04.010387 dead_ivl 40, DR 192.168.0.2, BDR 0.0.0.0 May 20 22:27:07.891698 OSPF periodic xmit from 192.168.0.1 to 224.0.0.5 (IFL 2684276180 area 0.0.0.0) May 20 22:27:12.749988 OSPF packet ignored: area mismatch (0.0.0.1) from 192.168.0.2 on intf ge-1/1/2.0 area 0.0.0.0 May 20 22:27:12.750071 OSPF rcvd Hello 192.168.0.2 -> 224.0.0.5 (ge- 1/1/2.0 IFL 343 area 0.0.0.0) May 20 22:27:12.750095 Version 2, length 44, ID 10.10.10.1, area 0.0.0.1 May 20 22:27:12.750116 checksum 0x166d, authtype 0 May 20 22:27:12.750139 mask 255.255.255.252, hello_ivl 10, opts 0x12, prio 128 May 20 22:27:12.750161 dead_ivl 40, DR 192.168.0.2, BDR 0.0.0.0 May 20 22:27:14.393182 OSPF rcvd Hello 192.168.0.2 -> 224.0.0.5 (ge- 1/1/2.0 IFL 343 area 0.0.0.0) May 20 22:27:14.393262 Version 2, length 44, ID 10.10.10.1, area 0.0.0.0 May 20 22:27:14.393284 checksum 0x0, authtype 0 May 20 22:27:14.393307 mask 255.255.255.252, hello_ivl 50, opts 0x12, prio 128 May 20 22:27:14.393368 dead_ivl 200, DR 0.0.0.0, BDR 0.0.0.0 May 20 22:27:14.393399 OSPF packet ignored: our router ID received from 192.168.0.2 on intf ge-1/1/2.0 area 0.0.0.0
Options
- Ahello interval mismatch
- Bduplicate router ID
- Carea type mismatch
- Darea number mismatch
How the community answered
(41 responses)- A7% (3)
- B76% (31)
- C17% (7)
Community Discussion
No community discussion yet for this question.