Quantcast
Channel: PowerConnect Forum - Recent Threads
Viewing all articles
Browse latest Browse all 2954

Issue with missing , delayed multicast packets

$
0
0

Hi

I have an OSPF networking over VLAN19. I had quite a few networking issues as the OSPF network flaps due to neighbors dying, because of lost heartbeats

This is what got me looking at it. DCFW1 is the asa 5520 stack, its looking at the MAN vlan19 network

TRIGGER -> DCFW1

Sep 24 08:16:01 dcfw1 %ASA-7-711001: #012OSPF: Rcv hello from 10.32.255.9 area 0.0.0.0 from ybman19 10.31.19.133

Sep 24 08:16:30 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:5 l:144 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f59 from ybman19

Sep 24 08:16:31 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:1 l:80 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f5a from ybman19

Sep 24 08:16:31 dcfw1 %ASA-7-711001: #012OSPF: Rcv hello from 10.32.255.9 area 0.0.0.0 from ybman19 10.31.19.133

Sep 24 08:17:11 dcfw1 %ASA-7-711001: #012OSPF: 10.32.255.9 address 10.32.255.9 on ybman19 is dead

Sep 24 08:17:11 dcfw1 %ASA-7-711001: #012OSPF: 10.32.255.9 address 10.32.255.9 on ybman19 is dead, state DOWN

Sep 24 08:17:11 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:5 l:44 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f5f from ybman19

Sep 24 08:17:12 dcfw1 %ASA-7-711001: #012OSPF: Rcv Update Type 5, LSID 10.32.255.9, Adv rtr 10.34.255.2, age 1, seq 0x80000001

Sep 24 08:17:12 dcfw1 %ASA-7-711001: #012OSPF: Do not schedule partial SPF - type 5 id 10.32.255.9 adv rtr 10.34.255.2, INTRA/INTER spf scheduled

 

The above triggered loss of networking as the OSPF network re evaled

 

 

This is what was sent out off TESTRTR1 (this is a RouterOS Virtual VM, it’s the same os as the mikrotek boxes)

SEND FOR TESTRTR1 (Test is running on gshost2 - vmnic3,vmnic2,vmnic1,vmnic0)

Sep 24 08:16:00 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:16:10 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:16:20 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:16:30 testrtr1 route,ospf,debug testrtr1: SEND: Link State Acknowledgement 10.31.19.133 -> 224.0.0.6 on MAN

Sep 24 08:16:30 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:16:40 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:16:50 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:17:00 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:17:10 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:17:11 testrtr1 route,ospf,debug testrtr1: SEND: Link State Acknowledgement 10.31.19.133 -> 224.0.0.6 on MAN

Sep 24 08:17:13 testrtr1 route,ospf,debug testrtr1: SEND: Link State Acknowledgement 10.31.19.133 -> 224.0.0.6 on MAN

Sep 24 08:17:19 testrtr1 route,ospf,debug testrtr1: SEND: Link State Update 10.31.19.133 -> 224.0.0.6 on MAN

Sep 24 08:17:20 testrtr1 route,ospf,debug testrtr1: SEND: Hello 10.31.19.133 -> 224.0.0.5 on MAN

Sep 24 08:17:24 testrtr1 route,ospf,debug testrtr1: SEND: Link State Update 10.31.19.133 -> 224.0.0.6 on MAN

 

 

 

This is a list of the received packets on the other ROS vm’s on MAN VLAN19

ROS recieved

Sep 24 08:16:01 simrtr1 route,ospf,debug simrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.130)

Sep 24 08:16:01 gsrtr2 route,ospf,debug gsrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.4)

Sep 24 08:16:01 uatrtr1 route,ospf,debug uatrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.129)

Sep 24 08:16:01 gsrtr1 route,ospf,debug gsrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.3)

Sep 24 08:16:01 prodrtr1 route,ospf,debug prodrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.131)

Sep 24 08:16:01 alcrtr1 route,ospf,debug alcrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.66)

Sep 24 08:16:01 alcrtr2 route,ospf,debug alcrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.67)

 

Sep 24 08:16:10 simrtr1 route,ospf,debug simrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.130)

Sep 24 08:16:10 gsrtr2 route,ospf,debug gsrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.4)

 

Sep 24 08:16:20 simrtr1 route,ospf,debug simrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.130)

Sep 24 08:16:20 gsrtr2 route,ospf,debug gsrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.4)

 

Sep 24 08:16:30 gsrtr2 route,ospf,debug gsrtr2: RECV: Link State Acknowledgement <- 10.31.19.133 on MAN (10.31.19.4)

Sep 24 08:16:30 gsrtr1 route,ospf,debug gsrtr1: RECV: Link State Acknowledgement <- 10.31.19.133 on MAN (10.31.19.3)

Sep 24 08:16:30 simrtr1 route,ospf,debug simrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.130)

Sep 24 08:16:30 gsrtr2 route,ospf,debug gsrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.4)

 

Sep 24 08:16:31 uatrtr1 route,ospf,debug uatrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.129)

Sep 24 08:16:31 prodrtr1 route,ospf,debug prodrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.131)

Sep 24 08:16:31 alcrtr1 route,ospf,debug alcrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.66)

Sep 24 08:16:31 alcrtr2 route,ospf,debug alcrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.67)

 

Sep 24 08:16:40 simrtr1 route,ospf,debug simrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.130)

Sep 24 08:16:40 gsrtr2 route,ospf,debug gsrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.4)

Sep 24 08:16:41 uatrtr1 route,ospf,debug uatrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.129)

 

Sep 24 08:16:51 simrtr1 route,ospf,debug simrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.130)

Sep 24 08:16:51 gsrtr2 route,ospf,debug gsrtr2: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.4)

Sep 24 08:16:51 uatrtr1 route,ospf,debug uatrtr1: RECV: Hello <- 10.31.19.133 on MAN (10.31.19.129)

 

There was quite a lot missing, there should be 7 on each 10’s heartbeat

 

 

This is again what DCFW1 saw

dcfw1

Sep 24 08:16:01 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:1 l:80 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f56 from ybman19

Sep 24 08:16:01 dcfw1 %ASA-7-711001: #012OSPF: Rcv hello from 10.32.255.9 area 0.0.0.0 from ybman19 10.31.19.133

Sep 24 08:16:30 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:5 l:144 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f59 from ybman19

Sep 24 08:16:31 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:1 l:80 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f5a from ybman19

Sep 24 08:16:31 dcfw1 %ASA-7-711001: #012OSPF: Rcv hello from 10.32.255.9 area 0.0.0.0 from ybman19 10.31.19.133

Sep 24 08:17:11 dcfw1 %ASA-7-711001: #012OSPF: 10.32.255.9 address 10.32.255.9 on ybman19 is dead

Sep 24 08:17:11 dcfw1 %ASA-7-711001: #012OSPF: 10.32.255.9 address 10.32.255.9 on ybman19 is dead, state DOWN

Sep 24 08:17:11 dcfw1 %ASA-7-711001: #012OSPF: rcv. v:2 t:5 l:44 rid:10.32.255.9#012      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x44f5f from ybman19

Sep 24 08:17:12 dcfw1 %ASA-7-711001: #012OSPF: Rcv Update Type 5, LSID 10.32.255.9, Adv rtr 10.34.255.2, age 1, seq 0x80000001

Sep 24 08:17:12 dcfw1 %ASA-7-711001: #012OSPF: Do not schedule partial SPF - type 5 id 10.32.255.9 adv rtr 10.34.255.2, INTRA/INTER spf scheduled

 

 You can see missing packets, but they seem to turn up late some 30 - 40s late

The only thing I can find is the below old article,

I am on a later version of the firmware.


Viewing all articles
Browse latest Browse all 2954

Trending Articles