[j-nsp] Problem with IGMP on MX480 10.4R7
Jerzy Pawlus
Jerzy.Pawlus at cyf-kr.edu.pl
Wed Nov 2 05:16:54 EDT 2011
Hi,
I have a problem with explicit joining of a multicast group if such
group is already created on the switch. MX seems to reject IGMP joins
and only after router igmp query to "all host" this group can be joined.
There is no problem if the group does not exist yet.
1. There is no 239.239.2.2 and the group can be joined:
09:36:20.969250 IP 10.202.71.229 > 239.239.2.2: igmp v2 report 239.239.2.2
Group: 239.239.2.2
Source: 10.200.200.203/32
Upstream interface: ge-5/1/4.0
Session description: Organization-Local Scope
Statistics: 454 kBps, 337 pps, 7845 packets
Next-hop ID: 0
Upstream protocol: PIM
Route state: Active
Forwarding state: Pruned
Cache lifetime/timeout: 360 seconds
Wrong incoming interface notifications: 0
2. When the group 239.239.2.1 exists:
Group: 239.239.2.1
Source: (null)/0
Upstream interface: ge-5/1/4.0
Downstream interface list:
xe-4/1/0.0
Session description: Organization-Local Scope
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 1048926
Upstream protocol: MVPN
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 6
Group: 239.239.2.1
Source: 10.200.200.203/32
Upstream interface: ge-5/1/4.0
Downstream interface list:
xe-4/1/0.0
Session description: Organization-Local Scope
Statistics: 637 kBps, 474 pps, 350407 packets
....
09:39:55.236311 IP 10.202.71.229 > 239.239.2.1: igmp v2 report 239.239.2.1
09:39:55.236311 IP 10.202.71.229 > 239.239.2.1: igmp v2 report 239.239.2.1
above joins are ignored and the:
"Wrong incoming interface notifications: 6" counter is increased.
3. When the MX sends
09:41:15.136068 IP 10.202.71.225 > 224.0.0.1: igmp query v3
and the host responds with:
09:41:24.071645 IP 10.202.71.229 > 224.0.0.22: igmp v3 report, 4 group record(s)
239.239.2.1 is joined
Group: 239.239.2.1
Source: (null)/0
Upstream interface: ge-5/1/4.0
Downstream interface list:
ge-5/0/0.797 xe-4/1/0.0
Session description: Organization-Local Scope
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 1048806
Upstream protocol: MVPN
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 6
Group: 239.239.2.1
Source: 10.200.200.203/32
Upstream interface: ge-5/1/4.0
Downstream interface list:
ge-5/0/0.797 xe-4/1/0.0
Session description: Organization-Local Scope
Statistics: 637 kBps, 948 pps, 6602 packets
Next-hop ID: 1048807
Upstream protocol: MVPN
Route state: Active
Can you help?
Jurek
More information about the juniper-nsp
mailing list