static (IGMP Snooping)

Syntax

Statically define multicast groups for IGMP snooping on a Layer 2 (L2) interface.

You might use this statement to configure an L2 interface to statically join a particular multicast group in cases such as the following:

In a network that doesn't include Layer 3 (L3) multicast. You can't establish a static IGMP state at L3, but you can create a static join state on an interface for multicast forwarding at L2.
To enable static IGMP join states with more granularity in a network with L2 and L3 multicast elements.
For example, consider that you have Layer 2 interfaces in a VLAN associated with an IRB interface for Layer 3 multicast routing. You have two options to establish a static join state on an interface at the two different levels:
- Assign a static group membership on an individual Layer 2 interface in the VLAN associated with the IRB interface:
  
  In this case, the device creates IGMP and PIM join states for the static group at L3 on the IRB interface. However, with IGMP snooping enabled and the group membership established only on that individual L2 interface, the device forwards traffic for the group only on that interface.
- Assign a static group membership only on the IRB interface itself at L3:
  
  In this case, without enabling IGMP snooping, the device creates creates IGMP and PIM join states for the group at L3 on the IRB interface, pulls multicast traffic, and floods it on all L2 ports in the VLAN. With IGMP snooping enabled, the device pulls multicast traffic for the group, but doesn't forward it on the VLAN (because you didn't configure any particular L2 ports to join that multicast group).

The remaining statement is explained separately. See CLI Explorer.

No multicast groups are statically defined.

routing—To view this statement in the configuration.routing-control—To add this statement to the configuration.

Statement introduced in Junos OS Release 9.1.