This manual chiefly focuses on the IP multicast technology and device operations.
Unless otherwise stated, the term “multicast” in this document refers to IP multicast.
1.1 Introduction to Multicast
As a technique coexisting with unicast and broadcast, the multicast technique
effectively addresses the issue of point-to-multipoint data transmission. By allowing
high-efficiency point-to-multipoint data transmission over a network, multicast greatly
saves network bandwidth and reduces network load.
With the multicast technology, a network operator can easily provide new value-added
services, such as live Webcasting, Web TV, dist ance learning, telemedi cine, Web ra dio,
real-time videoconferencing, and other bandwidth- and time-critical information
services.
1.1.1 Comparison of Information Transmission Techniques
I. Unicast
In unicast, the information source sends a separate copy of information to each host
that needs the information, as shown in
Assume that Hosts B, D and E need this information. The information source
establishes a separate transmission channel for each of these hosts.
In unicast transmission, the traffic over the network is proportional to the number of
hosts that need the information. If a large number of users need the information, the
information source needs to send a copy of the same information to each of these users.
This means a tremendous pressure on the information source and the network
bandwidth.
As we can see from the information transmission process, unicast is not suitable for
batch transmission of information.
II. Broadcast
In broadcast, the information source sends information to all h osts on the network, even
if some hosts do not need the information, as shown in
Assume that only Hosts B, D, and E need the information. If the information source
broadcasts the information, Hosts A and C also receive it. In addition to information
security issues, this also causes traffic flooding on the same network.
Therefore, broadcast is disadvantageous in transmitting data to specific hosts;
moreover, broadcast transmission is a significant usage of network resources.
III. Multicast
As discussed above, the unicast and broadcast techniques are unable to provide
point-to-multipoint data transmissions with the minimum network consumption.
The multicast technique has solved this problem. When some hosts on the network
need multicast information, the multicast source (Source in the figure) sends only one
copy of the information. Multicast distribution threes are built for the multicast packets
through multicast routing protocols, and the packets are replicated only on nodes
where the trees branch, as shown in
Assume that Hosts B, D and E need the information. To receive the information
correctly, these hosts need to join a receiver set, which is known as a multicast group.
The routers on the network duplicate and forward the information based on the
distribution of the receivers in this set. Finally, the information is correctly delivered to
Hosts B, D, and E.
To sum up, multicast has the following advantages:
zOver unicast: As multicast traffic flows to the node the farthest possible from the
source before it is replicated and distributed, an increase of the number of hosts
will not remarkably add to the network load.
zOver broadcast: As multicast data is sent only to the receivers that need it,
multicast uses the network bandwidth reasonably and brings no waste of network
resources, and enhances network security.
1.1.2 Roles in Multicast
The following roles are involved in multicast transmission:
z An information sender is referred to as a Multicast Source (“Source” in Figure 1-3).
z Each receiver is a Multicast Group Member (“Receiver” in Figure 1-3).
z All receivers interested in the same information form a Multicast Group. Multicast
groups are not subject to geographic restrictions.
zA router that supports Layer 3 multicast is called multicast router or Layer 3
multicast device. In addition to providing the multicast routing function, a multicast
router can also manage multicast group members.
zAny other point-to-multiple-point data distribution application.
1.2 Multicast Models
Based on how the receivers treat the multicast sources, there are two multicast models:
I. ASM model
In the ASM model, any sender can send information to a multicast group as a multicast
source, and numbers of receivers can join a multicast group identified by a group
address and obtain multicast information addressed to that multicast group. In this
model, receivers are not aware of the position of multicast sources in advance.
However, they can join o r leave the multicast group at any time.
II. SSM model
In the practical life, users may be interested in the multicast data from only certain
multicast sources. The SSM model provides a transmission service that allows users to
specify the multicast sources they are interested in at the client side.
The radical difference between the SSM model and the ASM model is that in the SSM
model, receivers already know the locations of the multicast sources by some other
means. In addition, the SSM model uses a multicast address range that is differe nt from
that of the ASM model, and dedicated multicast forwarding paths are established
between receivers and the specified multicast sources.
1.3 Multicast Architecture
IP multicast addresses the following questions:
z Where should the multicast source transmit information to? (multicast addressing)
z What receivers exist on the network? (host registration)
z Where is the multicast source from which the receivers need to receive multicast
data? (multicast source discovery)
zHow should information be transmitted to the receivers? (multicast routing)
IP multicast falls in the scope of end-to-end service. The multicast architectu re involves
the following four parts:
1) Addressing mechanism: Information is sent from a multicast source to a group of
receivers through a multicast address.
2) Host registration: Receiver hosts are allowed to join and leave multicast groups
dynamically. This mechanism is the basis for group membership management.
3) Multicast routing: A multicast distribution tree (namely a forwarding path tree for
multicast data on the network) is constructed for delivering multicast data from a
multicast source to receivers.
4) Multicast applications: A software system that supports multicast applications,
such as video conferencing, must be installed on multicast sources and receiver
hosts, and the TCP/IP stack must support reception and transmission of multicast
data.
1.3.1 Multicast Addresses
To allow communication between multicast sources and multicast group members,
network-layer multicast addresses, namely, multicast IP addresses must be provided.
In addition, a technique must be available to map multicast IP addresses to link-layer
multicast MAC addresses.
I. IPv4 multicast addresses
Internet Assigned Numbers Authority (IANA) assigned the Class D address space
(224.0.0.0 to 239.255.255.255) for IPv4 multicast. The specific address blocks and
usages are shown in
Table 1-2 Class D IP address blocks and description
Address block Description
Table 1-2.
224.0.0.0 to 224.0.0.255
224.0.1.0 to 238.255.255.255
239.0.0.0 to 239.255.255.255
Reserved permanent group addresses. The IP
address 224.0.0.0 is reserved, and other IP
addresses can be used by routing protocols and for
topology searching, protocol maintenance, and so
on. Commonly used permanent group addresses
are listed in
Table 1-3. A packet destined for an
address in this block will not be forwarded beyond
the local subnet regardless of the Time to Live
(TTL) value in the IP header.
Globally scoped group addresses. This block
includes two types of designated group addresses:
z 232.0.0.0/8: SSM group addresses, and
z 233.0.0.0/8: Glop group addresses; for details,
see RFC 2770.
Administratively scoped multicast addresses.
These addresses are considered to be locally
rather than globally unique, and can be reused in
domains administered by different organizations
without causing conflicts. For details, refer to RFC
z 0xFF: 8 bits, indicating that this address is an IPv6 multicast address.
z Flags: 4 bits, of which the high-order flag is reserved and set to 0; the definition
and usage of the second bit can be found in RFC 3956; and definition and usage
of the third bit can be found in RFC 3306; the low-order bit is the Transient (T) flag.
When set to 0, the T flag indicates a permanently-assigned multicast address
assigned by IANA; when set to 1, the T flag indicates a transient, or dynamically
assigned multicast address.
zScope: 4 bits, indicating the scope of the IPv6 internetwork for which the multicast
traffic is intended. Possible values of this field are given in
z Reserved: 80 bits, all set to 0 currently.
z Group ID: 112 bits, identifying the multicast group. For details about this field, refer
Table 1-4.
to RFC 3306.
Table 1-4 Values of the Scope field
Value Meaning
0, 3, F Reserved
1 Node-local scope
2 Link-local scope
4 Admin-local scope
5 Site-local scope
6, 7, 9 through D Unassigned
8 Organization-local scope
E Global scope
III. Ethernet multicast MAC addresses
When a unicast IP packet is transmitted over Ethernet, the destination MAC address is
the MAC address of the receiver. When a multicast p acket is transmitted over Ethernet,
however, the destination address is a multicast MAC address because the packet is
directed to a group formed by a number of receivers, rather than to one specific
receiver .
1) IPv4 multicast MAC addresses
As defined by IANA, the high-order 24 bits of an IPv4 multicast MAC address are
0x01005e, bit 25 is 0x0, and the low-order 23 bits are the low-order 23 bits of a
multicast IPv4 address. The IPv4-to-MAC mapping relation is shown in
Figure 1-5.
Figure 1-5 IPv4-to-MAC address mapping
The high-order four bits of a multicast IPv4 address are 1110, indicating that this
address is a multicast address, and only 23 bits of the remaining 2 8 bits are mapped t o
a MAC address, so five bits of the multicast IPv4 address are lost. As a result, 32
multicast IPv4 addresses map to the same MAC address. Therefore, in Layer 2
multicast forwarding, a device may receive some multicast data addressed for other
IPv4 multicast groups, and such redundant data n eeds to be filtered by the upper layer.
2) IPv6 multicast MAC addresses
The high-order 16 bits of an IPv6 multicast MAC address are 0x3333, and the low-order
32 bits are the low-order 32 bits of a multicast IPv6 address.
Figure 1-6 shows an
example of mapping an IPv6 multicast address, FF1E::F30E:0101, to a MAC address.
Figure 1-6 An example of IPv6-to-MAC address mapping
z Generally, we refer to IP multicast working at the network layer as Layer 3 multicast
and the corresponding multicast protocols as Layer 3 multicast protocols, which
include IGMP/MLD, PIM/IPv6 PIM, and MSDP; we refer to IP multicast working at
the data link layer as Layer 2 multicast and the corresponding multicast protocols as
Layer 2 multicast protocols, which include IGMP Snooping/MLD Snooping, and
multicast VLAN/IPv6 multicast VLAN.
zIGMP Snooping, IGMP, multicast VLAN, PIM and MSDP are for IPv4, MLD
Snooping, MLD, IPv6 multicast VLAN, and IPv6 PIM are for IPv6.
This section provides only general descriptions about appli cations and function s of the
Layer 2 and Layer 3 multicast protocols in a network. For details of these protocols,
refer to the respective chapters.
I. Layer 3 multicast protocols
Layer 3 multicast protocols include multicast group management protocols and
multicast routing protocols.
Figure 1-7 describes where these multicast protocols are in
a network.
Figure 1-7 Positions of Layer 3 multicast protocols
1) Multicast management protocols
Typically, the internet group management protocol (IGMP) or multicast listener
discovery protocol (MLD) is used between host s and Layer 3 multicast devices di rectly
connected with the hosts. These protocols define the mechanism of establishing and
maintaining group memberships between hosts and Layer 3 multicast devices.
2) Multicast routing protocols
A multicast routing proto col runs on Layer 3 multicast devices to esta blish and maintain
multicast routes and forward multicast packets correctly and ef ficiently . Multicast routes
constitute a loop-free data transmission path from a data source to multiple receivers,
namely, a multicast distribution tree.
In the ASM model, multicast routes come in intra-domain routes and inter-domain
routes.
zAn intra-domain multicast routing protocol is used to discover multicast sources
and build multicast distribution trees within an AS so as to deliver multicast data to
receivers. Among a variety of mature intra-domain multicast routing protocols,
protocol independent multicast (PIM) is a popular one. Based on the forwarding
mechanism, PIM comes in two modes – dense mode (often referred to as PIM-DM)
and sparse mode (often referred to as PIM-SM).
zAn inter-domain multicast routing protocol is used for delivery of multicast
information between two ASs. So far, mature solutions include multicast source
discovery protocol (MSDP).
For the SSM model, multicast routes are not divided into inter-domain routes and
intra-domain routes. Since receivers know the position of the multicast source,
channels established through PIM-SM are suff icient for multicast information transport.
II. Layer 2 multicast protocols
Layer 2 multicast protocols include IGMP Snooping/MLD Snooping and multicast
VLAN/IPv6 multicast VLAN.
Figure 1-8 shows where these protocols are in the
network.
Source
ReceiverReceiver
Multicast VLAN
/IPv6 Multicast VLAN
IGMP Snooping
/MLD Snooping
IPv4/IPv6 multicast packets
Figure 1-8 Position of Layer 2 multicast protocols
1) IGMP Snooping/MLD Snooping
Running on Layer 2 devices, Internet Group Management Protocol Snooping (IGMP
Snooping) and Multicast Listener Discovery Snooping (MLD Snooping) are multicast
constraining mechanisms that manage and control multicast groups by listening to and
analyzing IGMP or MLD messages exchanged between the hosts and Layer 3
multicast devices, thus effectively controlling the flooding of multicast dat a i n a L ayer 2
network.
2) Multicast VLAN/IPv6 multicast VLAN
In the traditional multicast-on-demand mode, when users in differen t VLANs on a Layer
2 device need multicast information, the upstream Layer 3 device needs to forward a
separate copy of the multicast data to each VLAN of the Layer 2 device. With the
multicast VLAN or IPv6 multicast VLAN feature enabled on the Layer 2 device, the
Layer 3 multicast device needs to send only one copy of multicast to the multicast
VLAN or IPv6 multicast VLAN on the Layer 2 device. This avoids waste of network
bandwidth and extra burden on the Layer 3 device.
1.4 Multicast Packet Forwarding Mechanism
In a multicast model, a multicast source sends information to the host group identified
by the multicast group address in the destination address field of IP multicast packets.
Therefore, to deliver multicast packets to receivers located in different parts of the
network, multicast routers on the forwarding path usually need to forward multicast
packets received on one incoming interface to multiple outgoing interfaces. Compared
with a unicast model, a multicast model is more complex in the following aspect s.
zTo ensure multicast packet transmission in the network, unicast routing tables or
multicast routing tables specially provided for multicast must be used as guidance
for multicast forwarding.
zTo process the same multicast information from different peers received on
different interfaces of the same device, every multicast packet is subject to a
reverse path forwarding (RPF) check on the incoming interface. The result of the
RPF check determines whether the packet will be forwarded or discarded. The
RPF check mechanism is the basis for most multicast routing protocols to
implement multicast forwarding.
Note:
For details about the RPF mechanism, refer to RPF Mechanism.
When configuring IGMP Snooping, go to the following sections for information you are
interested in:
z IGMP Snooping Overview
z IGMP Snooping Configuration Task List
z Displaying and Maintaining IGMP Snooping
z IGMP Snooping Configuration Examples
z Troubleshooting IGMP Snooping Configuration
2.1 IGMP Snooping Overview
Internet Group Management Protocol Snooping (IGMP Snooping) is a multicast
constraining mechanism that runs on Layer 2 devices to manage and control multicast
groups.
2.1.1 Principle of IGMP Snooping
By analyzing received IGMP messages, a Layer 2 device running IGMP Snooping
establishes mappings between ports and multicast IP addresses and forwards
multicast data based on these mappings.
As shown in
packets are broadcast to all devices at Layer 2. When IGMP Snooping is running on the
switch, multicast packets for known multicast groups are multicast to the receivers,
rather than broadcast to all hosts, at Layer 2.
Figure 2-1, when IGMP Snooping is not running on the switch, multicast
Figure 2-1 Before and after IGMP Snooping is enabled on the Layer 2 device
2.1.2 Basic Concepts in IGMP Snooping
Multicast packet transmission
when IGMP Snooping runs
Source
Host A
Receiver
Host B
Multicast router
Layer 2 switch
Host C
Receiver
I. IGMP Snooping related ports
As shown in Figure 2-2, Router A connects to the multicast source, IGMP Snooping
runs on Switch A and Switch B, Host A and Ho st C are receiver hosts (namely, multicast
group members).
zRouter port: A router port is a port on the Ethernet switch that leads switch towards
the Layer 3 multicast device (DR or IGMP querier). In the figure, Ethernet 1/0/1 of
Switch A and Ethernet 1/0/1 of Switch B are router ports. The switch registers all
its local router ports (including static and dynamic router ports) in its router port list .
zMember port: A member port is a port on the Ethernet switch that leads switch
towards multicast group members. In the figure, Ethernet 1/0/2 and Ethernet 1/0/3
of Switch A and Ethernet 1/0/2 of Switch B are member ports. The swit ch registers
all the member ports (including static and dynamic member ports) on the local
device in its IGMP Snooping forwarding table.
Note:
z Whenever mentioned in this document, a router port is a port on the switch that
leads the switch to a Layer 3 multicast device, rather than a port on a router.
zAn IGMP-snooping-enabled switch deems that all its ports on which IGMP general
queries with the source address other than 0.0.0.0 or PIM hello messages are
received to be router ports.
II. Aging timers for dynamic ports in IGMP Snooping and related messages
and actions
Table 2-1 Aging timers for dynamic ports in IGMP Snooping and related messages and
actions
Timer Description
For each router
port, the switch
Router port aging
timer
sets a timer
initialized to the
aging time of the
route port.
Message before
expiry
IGMP general
query of which the
source address is
not 0.0.0.0 or PIM
hello
Action after
expiry
The switch
removes this port
from its router port
list.
When a port joins
Member port aging
timer
a multicast group,
the switch sets a
timer for the port,
which is initialized
to the member port
aging time.
IGMP membership
report
The switch
removes this port
from the multicast
group forwarding
table.
The port aging mechanism of IGMP Snooping works only for dynamic ports; a static
port will never age out.
2.1.3 Work Mechanism of IGMP Snooping
A switch running IGMP Snooping performs different actions when it receives different
IGMP messages, as follows:
I. When receiving a general query
The IGMP querier periodically sends IGMP general queries to all hosts and routers
(224.0.0.1) on the local subnet to find out whether active multicast group members
exist on the subnet.
Upon receiving an IGMP general query, the switch forwards it through all ports in the
VLAN except the receiving port and performs the following to the receiving port:
zIf the receiving port is a router port existing in its router port list, the switch resets
the aging timer of this router port.
zIf the receiving port is not a router port existing in its router port list, the switch adds
it into its router port list and sets an aging timer for this router port.
II. When receiving a membership report
A host sends an IGMP report to the multicast router in the following circumstances:
zUpon receiving an IGMP query, a multicast group member host responds with an
IGMP report.
zWhen intended to join a multicast group, a host sends an IGMP report to the
multicast router to announce that it is interested in the multicast information
addressed to that group.
Upon receiving an IGMP report, the switch forwards it through all the router po rts in the
VLAN, resolves the address of the reported multicast group, and performs the
following:
zIf no forwarding table entry exists for the reported group, the switch creates an
entry, adds the port as member port to the outgoing port list, and starts a member
port aging timer for that port.
zIf a forwarding table entry exists for the reported group, but the port is not included
in the outgoing port list for that group, the switch adds the port as a member port to
the outgoing port list, and starts a member port aging timer for that port.
zIf a forwarding table entry exists for the reported group and the port is included in
the outgoing port list, which means that this port is already a member port, the
switch resets the member port aging timer for that port.
Note:
A switch does not forward an IGMP report through a non-router port. The reason is as
follows: Due to the IGMP report suppression mechanism, if the switch forwards a report
message through a member port, all the attached hosts listening to the reported
multicast address will suppress their own reports upon hea ring thi s repo rt, and this will
prevent the switch from knowing whether any hosts attached to that port are still active
members of the reported multicast group.
For the description of IGMP report suppression mechanism, refer to
of IGMPv1
.
Work Mechanism
III. When receiving a leave group message
When an IGMPv1 host leaves a multicast group, the host does not send an IGMP leave
group message, so the switch cannot know immediately that the host has left the
multicast group. However , as the ho st stop s sending IGMP report s as soo n as it leaves
a multicast group, the switch deletes the forwarding entry for the member port
corresponding to the host from the forwarding table when its aging timer expires.
When an IGMPv2 or IGMPv3 host leaves a multicast group, the host sends an IGMP
leave group message to the multicast router.
When the switch hears a group-specific IGMP leave g roup message on a member port,
it first checks whether a forwarding table entry for that group exists, and, if one exists,
whether its outgoing port list contains that port.
zIf the forwarding table entry does not exist or if its outgoing port list does not
contain the port, the switch discards the IGMP leave group message instead of
forwarding it to any port.
zIf the forwarding table entry exists and its outgoing port list contains the port, the
switch forwards the leave group message to all router ports in the VLAN. Because
the switch does not know whether any other hosts attached to the port are still
listening to that group address, the switch does not immediately removes the port
from the outgoing port list of the forwarding table entry for that group; instead, it
resets the member port aging timer for the port.
Upon receiving the IGMP leave group message from a host, the IGMP querier resolves
from the message the address of the multicast group that the host just left and sends an
IGMP group-specific query to that multicast group through the port that received the
leave group message. Upon hearing the IGMP group-specific query, the switch
forwards it through all its router ports in the VLAN and all member ports for that
multicast group, and performs the following:
zIf any IGMP report in response to the group-specific query is heard on a member
port before its aging timer expires, this means that some host attached to the port
is receiving or expecting to receive multicast data for that multicast group. The
switch resets the aging timer of the member port.
zIf no IGMP report in response to the group-specific query is heard on a member
port before its aging timer expires, this means that no hosts attached to the port
are still listening to that group address: the switch removes the port from the
outgoing port list of the forwarding table entry for that multicast group when the
aging timer expires.
2.1.4 Processing of Multicast Protocol Messages
With Layer 3 multicast routing enabled, an IGMP Snooping switch processes multicast
protocol messages differently under different conditions, specifically as follows:
1) If only IGMP is enabled, or both IGMP and PIM are enabled on the switch, the
switch handles multicast protocol messages in the normal way.
2) In only PIM is enabled on the switch:
z The switch broadcasts IGMP messages as unknown messages in the VLAN.
z Upon receiving a PIM hello message, the switch will maintain the corresponding
router port.
3) When IGMP is disabled on the switch, or when IGMP forwarding entries are
cleared (by using the reset igmp group command):
zIf PIM is disabled, the switch clears all its Layer 2 multicast entries and router
ports.
zIf PIM is enabled, the switch clears only its Layer 2 multicast entries without
deleting its router ports.
4) When PIM is disabled on the switch:
z If IGMP is disabled, the switch clears all its router ports.
z If IGMP is enabled, the switch maintains all its Layer 2 multicast entries and router
ports.
2.1.5 Protocols and Standards
IGMP Snooping is documented in:
zRFC 4541: Considerations for Internet Group Management Protocol (IGMP) and
z Configurations made in IGMP Snooping view are effective for all VLANs, while
configurations made in VLAN view are effective only for ports belonging to the
current VLAN. For a given VLAN, a configuration made in IGMP Snooping view is
effective only if the same configuration is not made in VLAN view.
zConfigurations made in IGMP Snooping view are effective for all ports;
configurations made in Ethernet port view are effective only for the current port;
configurations made in manual port group view are effective only for all the ports in
the current port group; configurations made in aggregation group view are effective
only for the master port. For a given port, a configuration made in IGMP Snooping
view is effective only if the same configuration is not made in Ethernet port view or
port group view.
2.3 Configuring Basic Functions of IGMP Snooping
2.3.1 Configuration Prerequisites
Before configuring the basic functions of IGMP Snooping, complete the following task:
zConfigure the corresponding VLANs.
Before configuring the basic functions of IGMP Snooping, prepare the following data:
z IGMP Snooping must be enabled globally before it can be enabled in a VLAN.
z After enabling IGMP Snooping in a VLAN, you cannot enable IGMP and/or PIM on
the corresponding VLAN interface, and vice versa.
zWhen you enable IGMP Snooping in a specified VLAN, this function takes effect for
Ethernet ports in this VLAN only.
2.3.3 Configuring the Version of IGMP Snooping
By configuring an IGMP Snooping version, you actually configure the version of IGMP
messages that IGMP Snooping can process.
zIGMP Snooping version 2 can process IGMPv1 and IGMPv2 messages, but not
IGMPv3 messages, which will be flooded in the VLAN.
zIGMP Snooping version 3 can process IGMPv1, IGMPv2 and IGMPv3 messages.
Follow these steps to configure the version of IGMP Snooping:
To do... Use the command... Remarks
Enter system view
Enter VLAN view
system-view
vlan vlan-id
Configure the version of
IGMP Snooping
igmp-snooping version
version-number
—
—
Optional
Version 2 by default
Caution:
If you switch IGMP Snooping from version 3 to version 2, the system will clear all IGMP
Snooping forwarding entries from dynamic joins, and will:
z Keep forwarding entries for version 3 static (*, G) joins;
z Clear forwarding entries from version 3 static (S, G) joins, which will be restored
when IGMP Snooping is switched back to version 3.
For details about static joins, Refer to
Configuring Static Ports.
2.4 Configuring IGMP Snooping Port Functions
2.4.1 Configuration Prerequisites
Before configuring IGMP Snooping port functions, complete the following t asks:
zEnable IGMP Snooping in the VLAN or enable IGMP on the desired VLAN
interface
zConfigure the corresponding port groups.
Before configuring IGMP Snooping port functions, prepare the following data:
z Aging time of router ports,
z Aging timer of member ports, and
z Multicast group and multicast source addresses
2.4.2 Configuring Aging Timers for Dynamic Ports
If the switch receives no IGMP general queries or PIM hello messages on a dynamic
router port, the switch removes the port from the router port list when the aging timer of
the port expires.
If the switch receives no IGMP reports for a multi cast group on a dynamic member port,
the switch removes the port from the outgoing port list of the forwarding table entry for
that multicast group when the aging timer of the port for that group expires.
If multicast group memberships change frequently, you can set a relatively small value
for the member port aging timer , and vice versa.
I. Configuring aging timers for dynamic ports globally
Follow these steps to configure aging timers for dynamic ports globally:
To do... Use the command... Remarks
Enter system view
system-view
Enter IGMP Snooping
view
Configure router port
aging time
Configure member port
aging time
igmp-snooping
router-aging-time
interval
host-aging-time interval
—
—
Optional
105 seconds by default
Optional
260 seconds by default
II. Configuring aging timers for dynamic ports in a VLAN
Follow these steps to configure aging timers for dynamic ports in a VLAN:
If all the hosts attached to a port are interested in the multicast data addressed to a
particular multicast group or the multicast data that a particular multica st source sends
to a particular group, you can configure static (*, G) or (S, G) joining on that port,
namely configure the port as a group-specific or source-and-group-specific static
member port.
You can configure a port of a switch to be a st atic rout er p ort, thro ugh which the swit ch
can forward all the multicast traffic it received.
Follow these steps to configure static ports:
To do... Use the command... Remarks
Enter system view
Enter the
corresponding
view
system-view
Enter Ethernet
port view
Enter port
group view
igmp-snooping
host-aging-time interval
interface interface-type
interface-number
port-group { manual
port-group-name |
aggregation agg-id }
Optional
260 seconds by default
—
Use either
command.
igmp-snooping
Configure the port(s) as static
member port(s)
Configure the port(s) as static
router port(s)
static-groupgroup-address
[ source-ip
source_address ] vlan
vlan-id
igmp-snooping
static-router-port vlan
vlan-id
Required
Disabled by
default
Required
Disabled by
default
Note:
z The static (S, G) joining function is available only if a valid multicast source address
is specified and IGMP Snooping version 3 is currently running on th e switch.
zA static member port does not respond to queries from the IGMP querier; when
static (*, G) or (S, G) joining is enabled or disabled on a port, the port does not send
an unsolicited IGMP report or an IGMP leave group message.
zStatic member ports and static router ports never age out. To remove such a port,
you need to use the corresponding command.
2-11
Loading...
+ 186 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.