[f-nsp] Multicast is being switched by LP CPU on MLXe?
Alexander Shikoff
minotaur at crete.org.ua
Tue Dec 20 05:57:54 EST 2016
Hi!
On Mon, Dec 19, 2016 at 04:14:28PM -0700, Eldon Koyle wrote:
> For IGMP snooping to work, there must be an L3 device acting as an
> IGMP querier on your L2 domain (typically a router). This device is
> in charge of keeping track of which IGMP clients have asked for which
> multicast groups, and periodically asking if they still want it. The
> MLX would not need to be the querier, but there has to be one in that
> VLAN.
>
> If there is no IGMP querier, your only real option would be to flood
> all the multicast (unless you are connecting a group of routers that
> are speaking PIM, then pim snooping might be able to help you).
There IS one querier:
telnet at lsr1-gdr.ki#show ip multicast vlan 450
----------+-----+---------+---------------+-----+-----+------
VLAN State Mode Active Time (*, G)(S, G)
Querier Query Count Count
----------+-----+---------+---------------+-----+-----+------
450 Ena Passive 192.168.210.1 119 1 1
----------+-----+---------+---------------+-----+-----+------
Router ports: 12/8 (11s)
Flags- R: Router Port, V2|V3: IGMP Receiver, P_G|P_SG: PIM Join
1 (*, 239.32.4.130) 00:34:48 NumOIF: 1 profile: none
Outgoing Interfaces:
e9/5 vlan 450 ( V2) 00:34:48/40s
1 (91.238.195.1, 239.32.4.130) in e11/2 vlan 450 00:34:48 NumOIF: 1 profile: none
Outgoing Interfaces:
TR(e9/5,e7/1) vlan 450 ( V2) 00:34:48/0s
FID: 0xa0a9 MVID: None
--
MINO-RIPE
More information about the foundry-nsp
mailing list