Routing
Reply
Contributor
chrisp
Posts: 44
Registered: ‎01-07-2009
0
Accepted Solution

OSPF Adjacency fails following full establishment between Cisco IOS router and MX240

Hi,

 

I’ve configured OSPF on a Cisco router and MX240 (logical-system). The OSPF adjacency establishes, DR/DBR are elected and DB exchanges, hello’s are then sent however after 40secs or so the neighbour relationship goes back to INIT state and starts over again.

 

The Cisco router debug OSPF shows “Cannot see ourself in hello from 83.166.164.2 on FastEthernet0/0.703, state INIT” 

 

The MX240 trace shows “RPD_OSPF_NBRDOWN: OSPF neighbor 83.166.172.246 (realm ospf-v2 ge-1/0/9.703 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: neighbor was inactive and declared dead)” 

 

The Cisco debugs show OSPF hello’s receive and sent, however the MX240 only shows sent hello’s. 

 

If I connect the Cisco router to another Cisco router I do not experience the same issues. 

 

Can anyone help identify the cause of the problem? 

 

Thanks,

Chris 

 

Cisco IOS Router Config
!
interface FastEthernet0/0.703
 encapsulation dot1Q 703
 ip address 83.166.172.246 255.255.255.252
 ip ospf cost 5
!
router ospf 1
 router-id 83.166.172.246
 log-adjacency-changes
 auto-cost reference-bandwidth 10000
 redistribute connected subnets
 redistribute static subnets
network 0.0.0.0 255.255.255.255 area 0.0.0.0
!

MX240 Config

[edit logical-systems N4-TRANSIT protocols ospf]
root@N4-DRY-MX240-02# show
traceoptions {
    file N4-TRANSIT-osfp-log size 1m files 5 world-readable;
    flag error;
    flag event detail;
    flag general;
    flag lsa-ack;
    flag hello detail;
}
export N4-TRANSIT-OSPF-EXPORT;
reference-bandwidth 10g;
area 0.0.0.0 {
    interface all {
        passive;
    }
    interface ge-1/0/9.703 {
        metric 5;
    }
}

[edit logical-systems N4-TRANSIT interfaces]
root@N4-DRY-MX240-02# show
ge-1/0/9 {
    unit 703 {
        vlan-id 703;
        family inet {
            address 83.166.172.245/30;

 

 

Cisco OSPF Debugs

*May 13 16:52:06.838: OSPF: Rcv hello from 83.166.164.2 area 0.0.0.0 from FastEthernet0/0.703 83.166.172.245
*May 13 16:52:06.838: OSPF: End of hello processing
*May 13 16:52:09.802: OSPF: Send hello to 224.0.0.5 area 0.0.0.0 on FastEthernet0/0.703 from 83.166.172.246
*May 13 16:52:16.054: OSPF: Rcv hello from 83.166.164.2 area 0.0.0.0 from FastEthernet0/0.703 83.166.172.245
*May 13 16:52:16.054: OSPF: End of hello processing
*May 13 16:52:19.802: OSPF: Send hello to 224.0.0.5 area 0.0.0.0 on FastEthernet0/0.703 from 83.166.172.246
*May 13 16:52:24.178: OSPF: Rcv hello from 83.166.164.2 area 0.0.0.0 from FastEthernet0/0.703 83.166.172.245
*May 13 16:52:24.178: OSPF: End of hello processing
*May 13 16:52:28.986: OSPF: Rcv hello from 83.166.164.2 area 0.0.0.0 from FastEthernet0/0.703 83.166.172.245
*May 13 16:52:28.986: OSPF: Cannot see ourself in hello from 83.166.164.2 on FastEthernet0/0.703, state INIT
*May 13 16:52:28.986: OSPF: Neighbor change Event on interface FastEthernet0/0.703
*May 13 16:52:28.986: OSPF: DR/BDR election on FastEthernet0/0.703
Then DR/BDR election and full adjacency

 

 

*** N4-TRANSIT/N4-TRANSIT-osfp-log ***
May 13 16:56:24.117779 OSPF periodic xmit from 83.166.172.245 to 224.0.0.5 (IFL 82 area 0.0.0.0)
May 13 16:56:24.762604 OSPF periodic xmit from 83.166.164.18 to 224.0.0.5 (IFL 108 area 0.0.0.0)
May 13 16:56:24.970223 OSPF hello from 83.166.164.17 (IFL 108, area 0.0.0.0) absorbed
May 13 16:56:28.525486 OSPF hello from 83.166.164.37 (IFL 104, area 0.0.0.0) absorbed
May 13 16:56:28.941291 OSPF hello from 83.166.164.42 (IFL 96, area 0.0.0.0) absorbed
May 13 16:56:30.447492 OSPF periodic xmit from 83.166.164.41 to 224.0.0.5 (IFL 96 area 0.0.0.0)
May 13 16:56:32.222145 OSPF periodic xmit from 83.166.164.38 to 224.0.0.5 (IFL 104 area 0.0.0.0)
May 13 16:56:32.222272 OSPF periodic xmit from 83.166.172.245 to 224.0.0.5 (IFL 82 area 0.0.0.0)
May 13 16:56:33.082875 OSPF hello from 83.166.164.17 (IFL 108, area 0.0.0.0) absorbed
May 13 16:56:34.457708 OSPF periodic xmit from 83.166.164.18 to 224.0.0.5 (IFL 108 area 0.0.0.0)
May 13 16:56:37.041249 OSPF hello from 83.166.164.42 (IFL 96, area 0.0.0.0) absorbed
May 13 16:56:37.709496 OSPF hello from 83.166.164.37 (IFL 104, area 0.0.0.0) absorbed
May 13 16:56:39.058822 OSPF periodic xmit from 83.166.164.41 to 224.0.0.5 (IFL 96 area 0.0.0.0)
May 13 16:56:40.010636 OSPF periodic xmit from 83.166.172.245 to 224.0.0.5 (IFL 82 area 0.0.0.0)
May 13 16:56:41.447146 OSPF hello from 83.166.164.17 (IFL 108, area 0.0.0.0) absorbed
May 13 16:56:41.707298 OSPF periodic xmit from 83.166.164.38 to 224.0.0.5 (IFL 104 area 0.0.0.0)
May 13 16:56:41.973283 OSPF periodic xmit from 83.166.164.18 to 224.0.0.5 (IFL 108 area 0.0.0.0)
May 13 16:56:45.587536 RPD_OSPF_NBRDOWN: OSPF neighbor 83.166.172.246 (realm ospf-v2 ge-1/0/9.703 area 0.0.0.0) state changed from Full to Down due to InActiveTimer (event reason: neighbor was inactive and declared dead)
May 13 16:56:45.587775 Interface ge-1/0/9.703 area 0.0.0.0 event NeighborChange
May 13 16:56:45.587798 OSPF DR is 83.166.164.2, BDR is 0.0.0.0
May 13 16:56:45.587822 OSPF sent Hello 83.166.172.245 -> 224.0.0.5 (ge-1/0/9.703 IFL 82 area 0.0.0.0)
May 13 16:56:45.587832   Version 2, length 44, ID 83.166.164.2, area 0.0.0.0
May 13 16:56:45.587841   mask 255.255.255.252, hello_ivl 10, opts 0x2, prio 128
May 13 16:56:45.587848   dead_ivl 40, DR 83.166.172.245, BDR 0.0.0.0

Super Contributor
AntonD
Posts: 111
Registered: ‎11-07-2007
0

Re: OSPF Adjacency fails following full establishment between Cisco IOS router and MX240

Try monitoring the traffic on the interface to see what is coming in and out of the router.


monitor traffic interface ge-1/0/9.703 size 1700

You can also write this information to a file and analyse it using Wireshark.


monitor traffic interface ge-1/0/9.703 size 1700  write-file ospf.pcap

Hopefully that give you some more answers. Ideally, you should try and capture the packets on the wire itself by placing some sort of sniffer in the middle.

Contributor
chrisp
Posts: 44
Registered: ‎01-07-2009
0

Re: OSPF Adjacency fails following full establishment between Cisco IOS router and MX240

Hi,

 

Thanks for your reponse.

 

As it happens I've already tried wireshark and I can see hello's in both directions. I replaced the Cisco with a J4350 and experinaced the same issues. I was using a Cisco 2950 switch to connect the J and MX. I removed this and connected them direct, this fixed the issue. I therefore put the Cisco router back (which only has a 100Mbs port) and connected it to the MX (1Gb port) through a Cisco 3560 switch. OSPF then worked fine.

 

So it was the C2950 causing the OSPF issue but I have no idea why. Regardless I've resolved the issue now.

 

Chris

Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.