Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

OSPF Trubleshooting

Hello All,

I have a problem with one of my OSPF router and the problem is that is the connected router is lost the neighbor relation after 50sec exactlly and back online again  and the switch show below

"*Apr 15 09:53:59.789: %OSPF-5-ADJCHG: Process 1, Nbr 56.6.6.6 on GigabitEthernet1/0/8 from LOADING to FULL, Loading Done"

Note that the status of the neighbor is full as below

Neighbor ID     Pri   State           Dead Time   Address         Interface

56.6.6.6          0   FULL/DROTHER    00:00:33    10.21.8.4       GigabitEthernet1/0/8

I did debuge ip ospf adj and it shows

*Apr 15 09:55:59.771: OSPF: Cannot see ourself in hello from 56.6.6.6 on GigabitEthernet1/0/8, state INIT

*Apr 15 09:55:59.771: OSPF: Neighbor change Event on interface GigabitEthernet1/0/8

*Apr 15 09:55:59.771: OSPF: DR/BDR election on GigabitEthernet1/0/8

*Apr 15 09:55:59.771: OSPF: Elect BDR 0.0.0.0

*Apr 15 09:55:59.771: OSPF: Elect DR 192.168.168.2

*Apr 15 09:55:59.771:        DR: 192.168.168.2 (Id)   BDR: none

*Apr 15 09:55:59.771: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.771: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.771: OSPF: Rcv DBD from 56.6.6.6 on GigabitEthernet1/0/8 seq 0x0 opt 0x42 flag 0x7 len 32  mtu 1500 state INIT

*Apr 15 09:55:59.771: OSPF: 2 Way Communication to 56.6.6.6 on GigabitEthernet1/0/8, state 2WAY

*Apr 15 09:55:59.771: OSPF: Neighbor change Event on interface GigabitEthernet1/0/8

*Apr 15 09:55:59.780: OSPF: DR/BDR election on GigabitEthernet1/0/8

*Apr 15 09:55:59.780: OSPF: Elect BDR 0.0.0.0

*Apr 15 09:55:59.780: OSPF: Elect DR 192.168.168.2

*Apr 15 09:55:59.780:        DR: 192.168.168.2 (Id)   BDR: none

*Apr 15 09:55:59.780: OSPF: Send DBD to 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB5E opt 0x52 flag 0x7 len 32

*Apr 15 09:55:59.780: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.780: OSPF: First DBD and we are not SLAVE

*Apr 15 09:55:59.780: OSPF: Rcv DBD from 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB5E opt 0x42 flag 0x0 len 792  mtu 1500 state EXSTART

*Apr 15 09:55:59.788: OSPF: NBR Negotiation Done. We are the MASTER

*Apr 15 09:55:59.788: OSPF: Send DBD to 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB5F opt 0x52 flag 0x3 len 792

*Apr 15 09:55:59.788: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.788: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.788: OSPF: Send LS REQ to 56.6.6.6 length 12 LSA count 1

*Apr 15 09:55:59.788: OSPF: Rcv DBD from 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB5F opt 0x42 flag 0x0 len 32  mtu 1500 state EXCHANGE

*Apr 15 09:55:59.788: OSPF: Send DBD to 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB60 opt 0x52 flag 0x1 len 32

*Apr 15 09:55:59.788: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.788: OSPF: Rcv LS UPD from 56.6.6.6 on GigabitEthernet1/0/8 length 76 LSA count 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Send with youngest Key 1

*Apr 15 09:55:59.797: OSPF: Rcv DBD from 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB60 opt 0x42 flag 0x0 len 32  mtu 1500 state EXCHANGE

*Apr 15 09:55:59.805: OSPF: Exchange Done with 56.6.6.6 on GigabitEthernet1/0/8

*Apr 15 09:55:59.805: OSPF: Synchronized with 56.6.6.6 on GigabitEthernet1/0/8, state FULL

*Apr 15 09:55:59.805: %OSPF-5-ADJCHG: Process 1, Nbr 56.6.6.6 on GigabitEthernet1/0/8 from LOADING to FULL, Loading Done

*Apr 15 09:56:00.233: OSPF: Send with youngest Key 1

*Apr 15 09:56:00.317: OSPF: Send with youngest Key 1

*Apr 15 09:56:00.719: OSPF: Rcv LS UPD from 56.6.6.6 on GigabitEthernet1/0/8 length 76 LSA count 1

*Apr 15 09:56:00.719: OSPF: Send with youngest Key 1

*Apr 15 10:01:09.789: OSPF: Neighbor change Event on interface GigabitEthernet1/0/8

*Apr 15 10:01:09.789: OSPF: DR/BDR election on GigabitEthernet1/0/8

*Apr 15 10:01:09.789: OSPF: Elect BDR 0.0.0.0

*Apr 15 10:01:09.789: OSPF: Elect DR 192.168.168.2

*Apr 15 10:01:09.789:        DR: 192.168.168.2 (Id)   BDR: none

*Apr 15 10:01:09.823: OSPF: Rcv LS UPD from 56.6.6.6 on GigabitEthernet1/0/8 length 76 LSA count 1

Is there any budy has any idea about this problem and how can i solve

Thank in advance for all of you

1 REPLY

Re: OSPF Trubleshooting

Hi,

look at the options:

Rcv DBD from 56.6.6.6 on GigabitEthernet1/0/8 seq 0x0 opt 0x42 flag 0x7 len

Send DBD to 56.6.6.6 on GigabitEthernet1/0/8 seq 0xB5E opt 0x52 flag 0x7 len

The local router has the L-bit (Link-Local Signaling) set,the neighbor 56.6.6.6 not (I assume that's a non-Cisco router?).

To fix this, you can disable LLS on a per-interface basis with the command ip ospf lls disable. (There is also a global setting under the ospf process: [no] capability lls.)

Useful Cisco Document: OSPF Per-Interface Link-Local Signaling

Hope that helps

Rolf

From RFC 5613:

2.1.  L-Bit in Options Field

A new L-bit (L stands for LLS) is introduced into the OSPF Options  field (see Figures 2a and 2b).  Routers set the L-bit in Hello and DD  packets to indicate that the packet contains an LLS data block.  In other words, the LLS data block is only examined if the L-bit is set.

+---+---+---+---+---+---+---+---+

| * | O | DC| L |N/P| MC| E | * |

+---+---+---+---+---+---+---+-+-+

Figure 2a: OSPFv2 Options Field

2092
Views
0
Helpful
1
Replies
CreatePlease login to create content