IGMP Configuration Guidelines

[Contents] [Prev] [Next] [Index] [Report an Error]

To configure the Internet Group Management Protocol (IGMP), include the igmp statement:




igmp {

accounting;



interface interface-name {

accounting;

disable;

group-policy;

immediate-leave;

no-accounting;

promiscuous-mode;

ssm-map ssm-map-name;



static {



group group {

source source;
}


}



version version; 
}



query-interval seconds; 

query-last-member-interval seconds; 

query-response-interval seconds; 

robust-count number; 



traceoptions {
file filename <files number> <size size> <world-readable |
no-world-readable>;
flag flag <flag-modifier> <disable>;
}


}

You can include this statement at the following hierarchy levels:

[edit protocols]
[edit logical-systems logical-system-name protocols]

For an overview of logical systems and a detailed example of logical system configuration, see the logical systems chapter of the JUNOS Feature Guide.

By default, IGMP is automatically enabled on all interfaces on which you configure Protocol Independent Multicast (PIM) and broadcast interfaces on which you configure the Distance Vector Multicast Routing Protocol (DVMRP).

Note: You can configure IGMP on an interface without configuring PIM. PIM is generally not needed on IGMP downstream interfaces. Therefore, only one “pseudo PIM interface” is created to represent all IGMP downstream (IGMP-only) interfaces on the router. This reduces the amount of router resources, such as memory, that are consumed. You must configure PIM on upstream IGMP interfaces to enable multicast routing, perform reverse path forwarding for multicast data packets, populate the multicast forwarding table for upstream interfaces, and in the case of PIM sparse mode, to distribute IGMP group memberships into the multicast routing domain.

This chapter describes the following tasks for configuring IGMP:

[Contents] [Prev] [Next] [Index] [Report an Error]