Web Management Guide-R04
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- 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
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Layer 2 Queue Settings
- Layer 3/4 Priority Settings
- Setting Priority Processing to IP Precedence/DSCP or CoS
- Mapping Ingress DSCP Values to Internal DSCP Values
- Mapping CoS Priorities to Internal DSCP Values
- Mapping Internal DSCP Values to Egress CoS Values
- Mapping IP Precedence Values to Internal DSCP Values
- Mapping IP Port Priority to Internal DSCP Values
- 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
- DHCPv4 Snooping
- DHCPv6 Snooping
- IPv4 Source Guard
- IPv6 Source Guard
- ARP Inspection
- Application Filter
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting Community Access Strings
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- 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
- Ethernet Ring Protection Switching
- OAM Configuration
- Connectivity Fault Management
- Configuring Global Settings for CFM
- Configuring Interfaces for CFM
- Configuring CFM Maintenance Domains
- Configuring CFM Maintenance Associations
- Configuring Maintenance End Points
- Configuring Remote Maintenance End Points
- Transmitting Link Trace Messages
- Transmitting Loop Back Messages
- Transmitting Delay-Measure Requests
- Displaying Local MEPs
- Displaying Details for Local MEPs
- Displaying Local MIPs
- Displaying Remote MEPs
- Displaying Details for Remote MEPs
- Displaying the Link Trace Cache
- Displaying Fault Notification Settings
- Displaying Continuity Check Errors
- OAM Configuration
- UDLD Configuration
- 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)
- Multicast VLAN Registration for IPv4
- Multicast VLAN Registration for IPv6
- Basic IP Functions
- IP Configuration
- General IP Routing
- IP Services
- Appendices
- Glossary
Chapter 14
| Multicast Filtering
Layer 2 IGMP (Snooping and Query for IPv4)
– 577 –
switches in the local network segment, IGMP Snooping is the only service required
to support multicast filtering.
When using IGMPv3 snooping, service requests from IGMP Version 1, 2 or 3 hosts
are all forwarded to the upstream router as IGMPv3 reports. The primary
enhancement provided by IGMPv3 snooping is in keeping track of information
about the specific multicast sources which downstream IGMPv3 hosts have
requested or refused. The switch maintains information about both multicast
groups and channels, where a group indicates a multicast flow for which the hosts
have not requested a specific source (the only option for IGMPv1 and v2 hosts
unless statically configured on the switch), and a channel indicates a flow for which
the hosts have requested service from a specific source. For IGMPv1/v2 hosts, the
source address of a channel is always null (indicating that any source is acceptable),
but for IGMPv3 hosts, it may include a specific address when requested.
Only IGMPv3 hosts can request service from a specific multicast source. When
downstream hosts request service from a specific source for a multicast service,
these sources are all placed in the Include list, and traffic is forwarded to the hosts
from each of these sources. IGMPv3 hosts may also request that service be
forwarded from any source except for those specified. In this case, traffic is filtered
from sources in the Exclude list, and forwarded from all other available sources.
Note:
When the switch is configured to use IGMPv3 snooping, the snooping
version may be downgraded to version 2 or version 1, depending on the version of
the IGMP query packets detected on each VLAN.
Note:
IGMP snooping will not function unless a multicast router port is enabled on
the switch. This can accomplished in one of two ways. A static router port can be
manually configured (see “Specifying Static Interfaces for a Multicast Router” on
page 582). Using this method, the router port is never timed out, and will continue
to function until explicitly removed. The other method relies on the switch to
dynamically create multicast routing ports whenever multicast routing protocol
packets or IGMP query packets are detected on a port.
Note:
A maximum of up to 1023 multicast entries can be maintained for IGMP
snooping. Once the table is full, no new entries are learned. Any subsequent
multicast traffic not found in the table is dropped if unregistered-flooding is
disabled (default behavior) and no router port is configured in the attached VLAN,
or flooded throughout the VLAN if unregistered-flooding is enabled (see
“Configuring IGMP Snooping and Query Parameters” on page 578).
Static IGMP Router Interface – If IGMP snooping cannot locate the IGMP querier,
you can manually designate a known IGMP querier (i.e., a multicast router/switch)
connected over the network to an interface on your switch (page 582). This
interface will then join all the current multicast groups supported by the attached
router/switch to ensure that multicast traffic is passed to all appropriate interfaces
within the switch.
Static IGMP Host Interface – For multicast applications that you need to control
more carefully, you can manually assign a multicast service to specific interfaces on