Table of Contents
Expand all | Collapse all
IGMP
IGMP routing protocol configuration parameter differences
between legacy and advanced routing engine.
There are parameter setting differences between legacy and advanced routing engines when
configuring Internet Group Management Protocol (IGMP) settings.
Migration Exception:
- During migration, each entry in the access list is replaced with a sequence number.
- The advanced routing engine does not apply group permissions directly to specific interfaces.
LEGACY ROUTING ENGINE | ADVANCED ROUTING ENGINE |
---|---|
A legacy routing engine refers
to group permissions by name. This
applies to IGMPv1, IGMPv2, and IGMPv3 entries. | The advanced routing engine uses extended access lists as filters. Each entry in
these access lists uses a sequence number instead of a name. As a
result, the entry names are lost and are replaced with a sequence
number in the access list during the migration. |
A legacy routing engine
can
apply
group permissions
directly
to specific interfaces. | The advanced routing engine
applies
group permissions
per interface
but
does not apply group permissions directly to the
interfaces.
Instead, the advanced routing engine creates an access list ( Logical Routers Multicast IGMP Dynamic Group Filter |
IGMP Version Support
Migration Exception:
LEGACY ROUTING ENGINE | ADVANCED ROUTING ENGINE |
---|---|
IGMPv1 supports only two messages: membership query and membership reply. There isn't a separate
message supported to announce when a host unsubscribes from a
multicast group. Because there is not an explicit leave message,
multicast streams can flood a specific segment even when there
are no subscribers. | The advanced routing engine
supports only IGMPv2 and IGMPv3—support for IGMPv1 is
deprecated. However, IGMPv2 is backward compatible and can
process IGMPv1 packets. |
Differences between IGMPv1 and IGMPv2
FEATURE | IGMPv1 | IGMPv2 |
---|---|---|
Default Query Interval (in seconds) | 60 | 125 |
Max Response Time (in seconds) | 10 seconds (fixed) | Range is 0 to 25 seconds (configurable) |
Leave Messages | No | Yes |
IP Address for Leave Messages | — | 224.0.0.2 |
Support for Group-Specific Query | No | Yes |
Querier Election Mechanism | None (depends on PIM) | Router with the lowest IP address on the
subnet. |
IGMP Timers
The IGMP timer configuration
range varies between legacy and advanced routing engines.
Migration Exception:
- If the IGMP timer configured in the legacy routing engine is a decimal value, then—during migration—it is rounded to the nearest integer value within the valid advanced routing range. This exception impacts theMax Query Response TimeandLast Member Query Interval.
- If the IGMP timer configured in the legacy routing engine is an integer value or is migrated to an integer value that exceeds the advanced routing engine configuration range, then this value is changed to a value supported by the advanced routing engine.
CONFIGURED IN (LEGACY ROUTING ENGINE) | LEGACY ROUTING ENGINE | MIGRATED TO (ADVANCED ROUTING ENGINE) | ADVANCED ROUTING ENGINE |
---|---|---|---|
Network Virtual Router Multicast Interfaces IGMP | Supports deciseconds value for few parameters. The legacy routing engine also supports extended
ranges for some IGMP parameters.
| Network Routing Routing Profiles Multicast Multicast IPv4 IGMP Interface Query Profiles | Supports the following IGMP timer configurations:
|
IGMP Group Permission
Migration Exception:
CONFIGURED IN (LEGACY ROUTING ENGINE) | LEGACY ROUTING ENGINE | ADVANCED ROUTING ENGINE |
---|---|---|
Network Virtual Router Multicast Interfaces Group Permissions | Supports the ability to restrict client access to specific groups or specific sources associated
with a specific group. These group permissions
lists identify each entry by a name and applies to both
source-specific and non-source-specific (any source)
entries. | Supports extended access lists
that restrict access to specific groups or sources associated
with a specific group. The advanced routing engine can apply
separate access lists to each IGMP-enabled interface. These
access lists are defined in the Filters
routing profile section of the configuration. |