OSPF 邻居关系不能正常建立的原因和解决方法

《OSPF 邻居关系不能正常建立的原因和解决方法》由会员分享，可在线阅读，更多相关《OSPF 邻居关系不能正常建立的原因和解决方法（8页珍藏版）》请在人人文库网上搜索。

1、稍微对ospf的trouble shooting总结了一下，有参考也有自己的心得。接口上没有激活ospf就是在network语句的时候没有匹配清楚，比如配置了错误的反掩码不对，在show ipospf interface的 时候不会显示你希望激活的接口使用 show ip ospf interface 来验证这时候的邻居表是空的R2#show ip ospf neighborR2#物理层或者是数据链路层协议down.使用 show ip int brief 或者是 show int type nomber会导致ospf packet封装失败。建立邻居的接口被passive掉R2#show ip

2、 ospf interface Ethernet 0 Ethernet0 is up, line protocol is up Internet Address 131.108.1.2/24, Area 0Process ID 1, Router ID 131.108.1.2, Network TypeBROADCAST, Cost: 10Transmit Delay is 1 sec, State DR, Priority 1Designated Router (ID) 131.108.1.2, Interface address 131.108.1.2No backup designate

3、d router on this network Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5No Hellos (Passive interface)Neighbor Count is 0, Adjacent neighbor count is 0Suppress hello for 0 neighbor(s)(4)OSPF 的 hello 组播地址被 ACL BlockR1#interface Ethernet0ip address 131.108.1.1 255.255.255.0ip acces

4、s-group 100 in !access-list 100 permit tcp any anyaccess-list 100 permit udp any anyaccess-list 101 permit ip 131.108.1.0 0.0.0.255 host224.0.0.5R2#interface Ethernet0ip address 131.108.1.2 255.255.255.0ip access-group 100 in !access-list 100 permit tcp any anyaccess-list 100 permit udp any anyacces

5、s-list 101 permit ip 131.108.1.0 0.0.0.255 host224.0.0.5R2#debug ip packet 101 detailIP packet debugging is on (detailed) for access list 101IP: s=131.108.1.2 (Ethernet0), d=224.0.0.5, len 68, access denied, proto=89这时候的邻居关系是INITR2#show ip ospf neighborNeighborIDPri StateDead TimeAddressInterface131

6、.108.2.11 INIT/-00:00:33131.108.1.1Ethernet0#p#R1#show access-list 101 Extended IP access list 101 permit ip 131.108.1.0 0.0.0.3 host 224.0.0.5 (8 matches)R1#debug ip packet 101 detailIP packet debugging is on (detailed) for access list 101 R1#IP: s=131.108.1.1 (local), d=224.0.0.5 (Ethernet0), len

7、60, sending broad/multicast, proto =89IP: s=131.108.1.2 (Ethernet0), d=224.0.0.5, len 82, access denied, proto=89IP: s=131.108.1.1 (local), d=224.0.0.5 (Ethernet0), len 60, sending broad/multicast, proto =89IP: s=131.108.1.2 (Ethernet0), d=224.0.0.5, len 82,access denied, proto=89在broadcast链路上的子网掩码不

8、匹配Hello/dead间隔不匹配认证方式或者是认证密码不匹配使用debug ip ospf adj来查看，可以自己使用不同的情况来验证两台路由器处于不同的AREAOSPF adjacency events debugging is onR1#OSPF： Rcv pkt from 131.108.1.2, Ethernet0, area0.0.0.0mismatch area 0.0.0.1 in the headerR2#show log%OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area

9、must bevirtual-link but not found from 131.108.1.1, Ethernet0(9)Stub/transit/NSSA区域类型不匹配这个是常常不小心会被忘记的。R1#debug ip ospf adjOSPF adjacency events debugging is onR1#OSPF: Rcv hello from 131.108.0.1 area 1 fromEthernet0 131.108.1.2OSPF: Hello from 131.108.1.2 with mismatchedStub/Transit area option bit

10、R1#debug ip ospf adjOSPF adjacency events debugging is onR1#OSPF: Rcv hello from 131.108.0.1 area 1 fromEthernet0 131.108.1.2OSPF: Hello from 131.108.1.2 with mismatched NSSA option bit(10)使用 secondary IP 来建立 OSPF adjacencyR2#interface FastEthernet0/0ip address 131.108.1.2 255.255.255.0 secondaryip

11、address 131.108.4.2 255.255.255.0R1#interface Ethernet0ip address 131.108.1.1 255.255.255.0R2#debug ip ospf adjOSPF adjacency events debugging is onR2#OSPF: Rcv pkt from 131.108.1.1, FastEthernet0/0, area 0.0.0.1 : src not on the same network#p#OSPF网络类型不匹配(P-TO-P和P-TO-M网络类型在hello时间间隔相同的情况下可以建立full关系

12、，但是会缺少一条路由)可以做一下相关使用验证NBMA (Frame Relay, X.25, SMDS, and so on)网络类型上没有手动指定 neighbor ip 地址邻居一直都是ATTEMPT状态在 Router 两边的 frame-relay map/dialer map 语句声明中缺少了 broadcast 参数这个就不要多说了吧。接口两边的MTU不匹配在cisco ios 12.0.3中加入了对mtu的检测，而低于这个版本的ios会忽略mtu检测，需要查看router的 ios version，debug ip ospf adj 的结果是发现有大量的dbd重传，出现loadi

13、ng的原因就是一边的router需要对mtu进行检测，而一边忽略。OSPF adjacency events debugging is onR2#OSPF： Retransmitting request to 131.108.2.1 onSerial0OSPF: Database request to 131.108.2.1OSPF: sent LS REQ packet to 131.108.1.1, length 12OSPF: Retransmitting request to 131.108.2.1 on Serial0解决方法是接口命令：mtu 4470而不是：ip mtu 4470

14、这时候的状态是loading 。R2#show ip ospf neighborNeighborIDPri StateDead TimeAddressInterface131.108.2.11 LOADING/-00:00:37131.108.1.1Serial0还有一种mtu不匹配的情况是邻居关系是EXSTART,因为两边的mtu都需要检测，而mtu大小又不匹配.R2#show ip ospf neighborNeighbor IDPri StateDead TimeAddressInterface1 EXSTART/- 00:00:33Serial0R1#debug ip ospf adj

15、OSPF: Retransmitting DBD to 131.108.1.2 on Serial0.1OSPF: Send DBD to 131.108.1.2 on Serial0.1 seq 0 x1E55 opt 0 x2 flag 0 x7 len 32 OSPF: Rcv DBD from 131.108.1.2 on Serial0.1 seq 0 x22AB opt 0 x2 flag 0 x7 len 32 mtu 1500 state EXSTARTOSPF： Nbr 131.108.1.2 has larger interface MTU在broadcast网络上需要选举

16、dr,而这时候两边的优先级又都是0在 Asynchronous Interfaces 上的 OSPF 邻居关系R1#interface Async1description ASYNC LINE TO R2 ip address 131.108.1.1 255.255.255.0 encapsulation ppp async mode dedicated dialer in-banddialer map ip 131.108.1.2 name Router2 broadcast dialer-group 1 ppp authentication chap R2# interface Async

17、1description ASYNC LINE TO R1 ip address 131.108.1.2 255.255.255.0 encapsulation ppp async mode dedicated dialer in-banddialer map ip 131.108.1.1 name Router2 broadcast dialer-group 1 ppp authentication chap解决方法是在两个使用async default routing或者asyn dynamic routing接口命令(15)两个路由器的Router id相同，ospf的master和sl

18、ave关系不能确定R2#debug ip ospf adjOSPF: Retransmitting DBD to 131.108.2.1 on Serial0OSPF: Send DBD to 131.108.2.1 on Serial0 seq 0 x793 opt 0 x2 flag 0 x7 len 32OSPF: Rcv DBD from 131.108.2.1 on Serial0 seq 0 x25F7opt 0 x2 flag 0 x7 len 32 mtu 0 stateEXSTARTOSPF： First DBD and we are not SLAVE(16)因为router接口的物理问题而导致的ospf packet checksum错误，接着就重传的问题。R2#show log %OSPF-4-ERRRCV: Received invalid packet: Bad Checksum from 131.108.1.1, Serial0 %OSPF-4-ERRRCV: Received invalid packet: Bad