556
C
HAPTER
42: IGMP S
NOOPING
C
ONFIGURATION
When receiving a membership report
A host sends an IGMP report to the multicast router in the following
circumstances:
■
Upon receiving an IGMP query, a multicast group member host responds with
an IGMP report.
■
When 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 ports
in the VLAN, resolves the address of the reported multicast group, and performs
the following:
■
If 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.
■
If 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.
■
If 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.
n
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 hearing this
report, 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 “Work
Mechanism of IGMPv1” on page 613.
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 host stops sending IGMP reports as soon
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 group 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.
■
If 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.
Summary of Contents for 4800G Series
Page 26: ...26 CHAPTER NETWORKING APPLICATIONS ...
Page 30: ...30 CHAPTER 1 LOGGING IN TO AN ETHERNET SWITCH ...
Page 62: ...62 CHAPTER 3 LOGGING IN THROUGH TELNET ...
Page 70: ...70 CHAPTER 5 LOGGING IN THROUGH WEB BASED NETWORK MANAGEMENT SYSTEM ...
Page 72: ...72 CHAPTER 6 LOGGING IN THROUGH NMS ...
Page 82: ...82 CHAPTER 8 CONTROLLING LOGIN USERS ...
Page 98: ...98 CHAPTER 9 VLAN CONFIGURATION ...
Page 108: ...108 CHAPTER 10 VOICE VLAN CONFIGURATION ...
Page 119: ...GVRP Configuration Examples 119 DeviceB display vlan dynamic No dynamic vlans exist ...
Page 120: ...120 CHAPTER 11 GVRP CONFIGURATION ...
Page 160: ...160 CHAPTER 17 PORT ISOLATION CONFIGURATION ...
Page 172: ...172 CHAPTER 19 LINK AGGREGATION CONFIGURATION ...
Page 196: ...196 CHAPTER 22 DLDP CONFIGURATION ...
Page 240: ...240 CHAPTER 23 MSTP CONFIGURATION ...
Page 272: ...272 CHAPTER 27 RIP CONFIGURATION ...
Page 364: ...364 CHAPTER 29 IS IS CONFIGURATION ...
Page 426: ...426 CHAPTER 31 ROUTING POLICY CONFIGURATION ...
Page 442: ...442 CHAPTER 33 IPV6 RIPNG CONFIGURATION ...
Page 466: ...466 CHAPTER 35 IPV6 IS IS CONFIGURATION ...
Page 488: ...488 CHAPTER 36 IPV6 BGP CONFIGURATION ...
Page 498: ...498 CHAPTER 37 ROUTING POLICY CONFIGURATION ...
Page 540: ...540 CHAPTER 40 TUNNELING CONFIGURATION ...
Page 552: ...552 CHAPTER 41 MULTICAST OVERVIEW ...
Page 604: ...604 CHAPTER 43 MLD SNOOPING CONFIGURATION ...
Page 628: ...628 CHAPTER 46 IGMP CONFIGURATION ...
Page 700: ...700 CHAPTER 48 MSDP CONFIGURATION ...
Page 812: ...812 CHAPTER 57 DHCP SERVER CONFIGURATION ...
Page 822: ...822 CHAPTER 58 DHCP RELAY AGENT CONFIGURATION ...
Page 834: ...834 CHAPTER 61 BOOTP CLIENT CONFIGURATION ...
Page 850: ...850 CHAPTER 63 IPV4 ACL CONFIGURATION ...
Page 856: ...856 CHAPTER 64 IPV6 ACL CONFIGURATION ...
Page 860: ...860 CHAPTER 65 QOS OVERVIEW ...
Page 868: ...868 CHAPTER 66 TRAFFIC CLASSIFICATION TP AND LR CONFIGURATION ...
Page 888: ...888 CHAPTER 69 PRIORITY MAPPING ...
Page 894: ...894 CHAPTER 71 TRAFFIC MIRRORING CONFIGURATION ...
Page 904: ...904 CHAPTER 72 PORT MIRRORING CONFIGURATION ...
Page 930: ...930 CHAPTER 74 UDP HELPER CONFIGURATION ...
Page 990: ...990 CHAPTER 79 FILE SYSTEM MANAGEMENT CONFIGURATION ...
Page 1000: ...1000 CHAPTER 80 FTP CONFIGURATION ...
Page 1020: ...1020 CHAPTER 82 INFORMATION CENTER CONFIGURATION ...
Page 1038: ...1038 CHAPTER 84 SYSTEM MAINTAINING AND DEBUGGING ...
Page 1046: ...1046 CHAPTER 85 DEVICE MANAGEMENT ...
Page 1129: ...SSH Client Configuration Examples 1129 SwitchB ...
Page 1130: ...1130 CHAPTER 88 SSH CONFIGURATION ...
Page 1160: ...1160 CHAPTER 90 RRPP CONFIGURATION ...
Page 1180: ...1180 CHAPTER 91 PORT SECURITY CONFIGURATION ...
Page 1192: ...1192 CHAPTER 92 LLDP CONFIGURATION ...
Page 1202: ...1202 CHAPTER 93 POE CONFIGURATION ...
Page 1218: ...1218 CHAPTER 96 HTTPS CONFIGURATION ...