Mailing List Archive

Hi Martin,

The PIM Assert is used by PIM routers to know who on a same broadcast domain
(in your case a VLAN) is the 'Master' - when multiple routers are connected
to same network/subnet/VLAN in order to avoid duplicate traffic.

Have you check if this is not duplicate traffic by comparing received and
sent packets?

Regards, Fabian.

-----Original Message-----
From: extreme-nsp-bounces@puck.nether.net
[mailto:extreme-nsp-bounces@puck.nether.net] On Behalf Of Marcin Kuczera
Sent: jeudi 2 octobre 2008 21:39
To: extreme-nsp@puck.nether.net
Subject: [e-nsp] multicasts, cont..

hello,

to remind - I have some little packet loss and some "out of order"
packets (1 packet every 530/540 seconds).
- I have upgraded soft to 6.1.3.3

what is strange for me:
Oct 2 12:36:59: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:36:59: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4

Oct 2 12:37:02: [0002]: %PIM-7-PROTO: (10.200.200.194,239.239.1.1)
assert timer expired on primary oif multicast1(0x10000002)
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send v2
(10.200.200.194,239.239.1.1) assert, metric [0/1/0/10.200.180.1]
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send Assert on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 46
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: (10.200.200.195,239.239.1.30)
assert timer expired on primary oif multicast1(0x10000002)
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send v2
(10.200.200.195,239.239.1.30) assert, metric [0/1/0/10.200.180.1]
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send Assert on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 46
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: (10.200.200.26,239.239.0.11)
assert timer expired on primary oif multicast1(0x10000002)
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send v2
(10.200.200.26,239.239.0.11) assert, metric [0/1/0/10.200.180.1]


Oct 2 12:37:52: [0002]: %PIM-7-PKT: Receive 58B PIM pak
10.200.16.5-->224.0.0.13 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:52: [0002]: %PIM-7-PROTO: Received Hello on downstream
2/4:1023:63/1/2/9 10.200.16.5 --> 224.0.0.13 len 38
Oct 2 12:37:52: [0002]: %PIM-7-PROTO: Opt #bytes:34, Nbr
hdtime:105(s), DR prio 1, unknown opt type 65004


is there anything in above that could cause packet loss/packet reordering ?


Regards,
Marcin



this is full debug:
Oct 2 12:36:59: %PIM-7-PPA: Wait for signal to update MFIB
Oct 2 12:36:59: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:36:59: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:36:59: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:36:59: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:36:59: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:36:59: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: (10.200.200.194,239.239.1.1)
assert timer expired on primary oif multicast1(0x10000002)
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send v2
(10.200.200.194,239.239.1.1) assert, metric [0/1/0/10.200.180.1]
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send Assert on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 46
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: (10.200.200.195,239.239.1.30)
assert timer expired on primary oif multicast1(0x10000002)
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send v2
(10.200.200.195,239.239.1.30) assert, metric [0/1/0/10.200.180.1]
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send Assert on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 46
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: (10.200.200.26,239.239.0.11)
assert timer expired on primary oif multicast1(0x10000002)
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send v2
(10.200.200.26,239.239.0.11) assert, metric [0/1/0/10.200.180.1]
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Send Assert on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 46
Oct 2 12:37:02: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:02: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:02: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:03: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:03: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:03: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:03: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:03: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:03: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:07: [0002]: %PIM-7-PROTO: Send PIM Hello on interface multicast1
Oct 2 12:37:07: [0002]: %PIM-7-PROTO: Send Hello on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 54
Oct 2 12:37:07: [0002]: %PIM-7-PROTO: Send PIM Hello on interface downstream
Oct 2 12:37:07: [0002]: %PIM-7-PROTO: Send Hello on downstream
2/4:1023:63/1/2/9 10.200.16.6 --> 224.0.0.13 len 54
Oct 2 12:37:22: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:22: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:22: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:22: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:22: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:22: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:22: [0002]: %PIM-7-PKT: Receive 58B PIM pak
10.200.16.5-->224.0.0.13 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:22: [0002]: %PIM-7-PROTO: Received Hello on downstream
2/4:1023:63/1/2/9 10.200.16.5 --> 224.0.0.13 len 38
Oct 2 12:37:22: [0002]: %PIM-7-PROTO: Opt #bytes:34, Nbr
hdtime:105(s), DR prio 1, unknown opt type 65004
Oct 2 12:37:35: [0002]: %PIM-7-MRTE: JOIN_TIMER for (*, 239.239.2.113)
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build join/prune message for
239.239.2.113 group
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (*, 239.239.2.113) S-bit
primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (10.200.200.200,
239.239.2.113) S-bit primary join (rpf:downstream)
pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-MRTE: JOIN_TIMER for (*, 239.239.1.1)
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build join/prune message for
239.239.1.1 group
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (*, 239.239.1.1) S-bit
primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (10.200.200.194,
239.239.1.1) S-bit primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (10.200.200.195,
239.239.1.1) S-bit primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Aggregate J/P msg to 10.200.16.5
for 239.239.1.1, len 98, cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-MRTE: JOIN_TIMER for (*, 239.239.2.149)
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build join/prune message for
239.239.2.149 group
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (*, 239.239.2.149) S-bit
primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (10.200.200.207,
239.239.2.149) S-bit primary join (rpf:downstream)
pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Aggregate J/P msg to 10.200.16.5
for 239.239.2.149, len 126, cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-MRTE: JOIN_TIMER for (*, 239.239.1.30)
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build join/prune message for
239.239.1.30 group
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (*, 239.239.1.30) S-bit
primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Build (10.200.200.195,
239.239.1.30) S-bit primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Aggregate J/P msg to 10.200.16.5
for 239.239.1.30, len 154, cct:2/4:1023:63/1/2/9
Oct 2 12:37:35: [0002]: %PIM-7-PROTO: Send Join/Prune on downstream
2/4:1023:63/1/2/9 10.200.16.6 --> 224.0.0.13 len 154
Oct 2 12:37:36: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:36: [0002]: %PIM-7-PKT: Receive 44B IGMP pak
10.200.200.20-->224.0.0.2 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:36: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:36: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:36: [0002]: %PIM-7-PROTO: Received PIMv1 RP-reachability
from 10.200.200.20
Oct 2 12:37:36: [0002]: %PIM-7-PROTO: Unknown PIMv1 message code 4
Oct 2 12:37:37: [0002]: %PIM-7-PROTO: Send PIM Hello on interface multicast1
Oct 2 12:37:37: [0002]: %PIM-7-PROTO: Send Hello on multicast1
2/4:1023:63/1/2/8 10.200.180.1 --> 224.0.0.13 len 54
Oct 2 12:37:37: [0002]: %PIM-7-PROTO: Send PIM Hello on interface downstream
Oct 2 12:37:37: [0002]: %PIM-7-PROTO: Send Hello on downstream
2/4:1023:63/1/2/9 10.200.16.6 --> 224.0.0.13 len 54
Oct 2 12:37:46: [0002]: %PIM-7-MRTE: JOIN_TIMER for (*, 239.239.0.11)
Oct 2 12:37:46: [0002]: %PIM-7-PROTO: Build join/prune message for
239.239.0.11 group
Oct 2 12:37:46: [0002]: %PIM-7-PROTO: Build (*, 239.239.0.11) S-bit
primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:46: [0002]: %PIM-7-PROTO: Build (10.200.200.26,
239.239.0.11) S-bit primary join (rpf:downstream) pak->cct:2/4:1023:63/1/2/9
Oct 2 12:37:46: [0002]: %PIM-7-PROTO: Send Join/Prune on downstream
2/4:1023:63/1/2/9 10.200.16.6 --> 224.0.0.13 len 62
Oct 2 12:37:52: [0002]: %PIM-7-PKT: Receive 58B PIM pak
10.200.16.5-->224.0.0.13 on downstream circuit 2/4:1023:63/1/2/9
Oct 2 12:37:52: [0002]: %PIM-7-PROTO: Received Hello on downstream
2/4:1023:63/1/2/9 10.200.16.5 --> 224.0.0.13 len 38
Oct 2 12:37:52: [0002]: %PIM-7-PROTO: Opt #bytes:34, Nbr
hdtime:105(s), DR prio 1, unknown opt type 65004




_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp

_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp