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 <replace> <size size> <files number> <no-stamp>
<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 seperately on an interface. However, without a multicast routing protocol (for example, PIM), IGMP does not function. PIM is needed on upstream IGMP interfaces to enable multicast routing protocol, in this case PIM-SM, to distribute IGMP group memberships into the multicast routing domain. PIM also performs reverse path forwarding (RPF) for multicast data packets and populates the multicast forwarding table for upstream interfaces. Because PIM is generally not needed on IGMP downstream interfaces (an interface that receives IGMP memberships; for example, interfaces that connect to a subscriber access client), in order to reduce memory and execution overhead when large numbers of IGMP interfaces are created, configuring PIM on an IGMP interface is optional. Instead of creating a seperate PIM interface for each IGMP downstream interface, only one "pseudo PIM interface" is created to represent all IGMP downstream (IGMP only) interfaces on the router.

This chapter describes the following tasks for configuring IGMP:

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