[ 永远的UNIX::UNIX技术资料的宝库 ]

首页 > 网管技术 > 路由技术 > 正文
 

Cisco IOS OSPF邻居关系不能正常建立的原因和解决方法(2)

来源:不详 (2006-06-07 12:19:14)

【导读】本文概述总结了Cisco IOS OSPF 邻居关系不能正常建立的原因和解决方法
(10)使用secondary IP来建立OSPF adjacency

R2#

interface FastEthernet0/0

ip address 131.108.1.2 255.255.255.0 secondary

ip address 131.108.4.2 255.255.255.0



R1#

interface Ethernet0

ip address 131.108.1.1 255.255.255.0

R2#debug ip ospf adj

OSPF adjacency events debugging is on

R2#

OSPF: Rcv pkt from 131.108.1.1, FastEthernet0/0, area 0.0.0.1 : src not on the same network

(11)OSPF网络类型不匹配(P-TO-P 和P-TO-M网络类型在hello时间间隔相同的情况下可以建立full关系,但是会缺少一条路由可以做一下相关使用验证

(12)NBMA (Frame Relay, X.25, SMDS, and so on)网络类型上没有手动指定neighbor ip 地址 邻居一直都是ATTEMPT状态

(13)在Router 两边的frame-relay map/dialer map语句声明中缺少了broadcast参数

(14)接口两边的MTU 不匹配

在cisco ios 12.0.3中加入了对mtu的检测,而低于这个版本的ios会忽略mtu检测,需要查看router 的ios version,debug ip ospf adj的结果是发现有大量的dbd重传,出现loading的原因就是一边的router需要对mtu进行检测,而一边忽略。

R2#debug ip ospf adj

OSPF adjacency events debugging is on

R2#

OSPF: Retransmitting request to 131.108.2.1 on Serial0

OSPF: Database request to 131.108.2.1

OSPF: sent LS REQ packet to 131.108.1.1, length 12

OSPF: Retransmitting request to 131.108.2.1 on Serial0

解决方法是接口命令:mtu 4470

而不是:ip mtu 4470

这时候的状态是 loading 。

R2#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

131.108.2.1 1 LOADING/- 00:00:37 131.108.1.1 Serial0

还有一种mtu不匹配的情况是邻居关系是EXSTART,因为两边的mtu都需要检测,而mtu大小又不匹配.

R2#show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface

131.108.2.1 1 EXSTART/- 00:00:33 131.108.1.1 Serial0

R1#debug ip ospf adj

OSPF: Retransmitting DBD to 131.108.1.2 on Serial0.1

OSPF: Send DBD to 131.108.1.2 on Serial0.1 seq 0x1E55 opt 0x2 flag 0x7 len 32

OSPF: Rcv DBD from 131.108.1.2 on Serial0.1 seq 0x22AB opt 0x2 flag 0x7 len 32 mtu 1500

state EXSTART

OSPF: Nbr 131.108.1.2 has larger interface MTU

(15)在broadcast网络上需要选举dr,而这时候两边的优先级又都是0

(16)在Asynchronous Interfaces上的OSPF邻居关系

R1#

interface Async1

description ASYNC LINE TO R2

ip address 131.108.1.1 255.255.255.0

encapsulation ppp

async mode dedicated

dialer in-band

dialer map ip 131.108.1.2 name Router2 broadcast

dialer-group 1

ppp authentication chap

R2#

interface Async1

description ASYNC LINE TO R1

ip address 131.108.1.2 255.255.255.0

encapsulation ppp

async mode dedicated

dialer in-band

dialer 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和slave关系不能确定

R2#debug ip ospf adj

OSPF: Retransmitting DBD to 131.108.2.1 on Serial0

OSPF: Send DBD to 131.108.2.1 on Serial0 seq 0x793 opt 0x2 flag 0x7 len 32

OSPF: Rcv DBD from 131.108.2.1 on Serial0 seq 0x25F7 opt 0x2 flag 0x7 len 32 mtu 0 state

EXSTART

OSPF: 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 Checksum from 131.108.1.1, Serial0



R2#debug ip ospf adj

OSPF adjacency events debugging is on

R2#

OSPF: Retransmitting request to 131.108.2.1 on Serial0

OSPF: Database request to 131.108.2.1

OSPF: sent LS REQ packet to 131.108.1.1, length 12

OSPF: Retransmitting request to 131.108.2.1 on Serial0



(http://www.fanqiang.com)



 
 相关文章

 

★  感谢所有的作者为我们学习技术知识提供了一条捷径  ★
www.fanqiang.com