Web Management Guide-R07
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- Introduction
- Key Features
- Description of Software Features
- Configuration Backup and Restore
- Authentication
- Access Control Lists
- Port Configuration
- Rate Limiting
- Port Mirroring
- Port Trunking
- Storm Control
- Static MAC Addresses
- IP Address Filtering
- IEEE 802.1D Bridge
- Store-and-Forward Switching
- Spanning Tree Algorithm
- Virtual LANs
- IEEE 802.1Q Tunneling (QinQ)
- Traffic Prioritization
- Quality of Service
- IP Routing
- Address Resolution Protocol
- Multicast Filtering
- Link Layer Discovery Protocol
- System Defaults
- Introduction
- Web Configuration
- Using the Web Interface
- Basic Management Tasks
- Displaying System Information
- Displaying Hardware/Software Versions
- Configuring Support for Jumbo Frames
- Displaying Bridge Extension Capabilities
- Managing System Files
- Setting the System Clock
- Configuring the Console Port
- Configuring Telnet Settings
- Displaying CPU Utilization
- Configuring CPU Guard
- Displaying Memory Utilization
- Resetting the System
- Using Cloud Management
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Quality of Service
- VoIP Traffic Configuration
- Security Measures
- AAA (Authentication, Authorization and Accounting)
- Configuring User Accounts
- Web Authentication
- Network Access (MAC Address Authentication)
- Configuring HTTPS
- Configuring the Secure Shell
- Access Control Lists
- Filtering IP Addresses for Management Access
- Configuring Port Security
- Configuring 802.1X Port Authentication
- DoS Protection
- DHCP Snooping
- IPv4 Source Guard
- ARP Inspection
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Power over Ethernet
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- Setting Community Access Strings
- Configuring Local SNMPv3 Users
- Configuring Remote SNMPv3 Users
- Specifying Trap Managers
- Creating SNMP Notification Logs
- Showing SNMP Statistics
- Remote Monitoring
- Switch Clustering
- Setting a Time Range
- LBD Configuration
- Smart Pair Configuration
- Multicast Filtering
- Overview
- Layer 2 IGMP (Snooping and Query for IPv4)
- Configuring IGMP Snooping and Query Parameters
- Specifying Static Interfaces for a Multicast Router
- Assigning Interfaces to Multicast Services
- Setting IGMP Snooping Status per Interface
- Filtering IGMP Query Packets and Multicast Data
- Displaying Multicast Groups Discovered by IGMP Snooping
- Displaying IGMP Snooping Statistics
- Filtering and Throttling IGMP Groups
- MLD Snooping (Snooping and Query for IPv6)
- Filtering and Throttling MLD Groups
- Filtering MLD Query Packets on an Interface
- IP Tools
- IP Configuration
- General IP Routing
- Unicast Routing
- Overview
- Configuring the Routing Information Protocol
- Configuring General Protocol Settings
- Clearing Entries from the Routing Table
- Specifying Network Interfaces
- Specifying Passive Interfaces
- Specifying Static Neighbors
- Configuring Route Redistribution
- Specifying an Administrative Distance
- Configuring Network Interfaces for RIP
- Displaying RIP Interface Settings
- Displaying Peer Router Information
- Resetting RIP Statistics
- IP Services
- Appendices
- Glossary
Chapter 14
| Multicast Filtering
Layer 2 IGMP (Snooping and Query for IPv4)
– 421 –
Parameters
These parameters are displayed:
◆ IGMP Snooping Status – When enabled, the switch will monitor network
traffic to determine which hosts want to receive multicast traffic. This is referred
to as IGMP Snooping. (Default: Disabled)
When IGMP snooping is enabled globally, the per VLAN interface settings for
IGMP snooping take precedence (see “Setting IGMP Snooping Status
per Interface” on page 428).
When IGMP snooping is disabled globally, snooping can still be configured per
VLAN interface, but the interface settings will not take effect until snooping is
re-enabled globally.
◆ Proxy Reporting Status – Enables IGMP Snooping with Proxy Reporting.
(Default: Disabled)
When proxy reporting is enabled with this command, the switch performs
“IGMP Snooping with Proxy Reporting” (as defined in DSL Forum TR-101, April
2006), including last leave, and query suppression.
Last leave sends out a proxy query when the last member leaves a multicast
group, and query suppression means that specific queries are not forwarded
from an upstream multicast router to hosts downstream from this device.
When proxy reporting is disabled, all IGMP reports received by the switch are
forwarded natively to the upstream multicast routers.
◆ TCN Flood – Enables flooding of multicast traffic if a spanning tree topology
change notification (TCN) occurs. (Default: Disabled)
When a spanning tree topology change occurs, the multicast membership
information learned by switch may be out of date. For example, a host linked to
one port before the topology change (TC) may be moved to another port after
the change. To ensure that multicast data is delivered to all receivers, by
default, a switch in a VLAN (with IGMP snooping enabled) that receives a Bridge
Protocol Data Unit (BPDU) with TC bit set (by the root bridge) will enter into
“multicast flooding mode” for a period of time until the topology has stabilized
and the new locations of all multicast receivers are learned.
If a topology change notification (TCN) is received, and all the uplink ports are
subsequently deleted, a time out mechanism is used to delete all of the
currently learned multicast channels.
When a new uplink port starts up, the switch sends unsolicited reports for all
currently learned channels out the new uplink port.
By default, the switch immediately enters into “multicast flooding mode” when
a spanning tree topology change occurs. In this mode, multicast traffic will be
flooded to all VLAN ports. If many ports have subscribed to different multicast
groups, flooding may cause excessive packet loss on the link between the
switch and the end host. Flooding may be disabled to avoid this, causing
multicast traffic to be delivered only to those ports on which multicast group