BLADE OS™ Application Guide HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Version 5.1 Advanced Functionality Software
Table Of Contents
- Contents
- Figures
- Tables
- Preface
- Part 1: Basic Switching
- Accessing the Switch
- The Management Network
- Local Management Using the Console Port
- The Command Line Interface
- Remote Management Access
- Client IP Address Agents
- Securing Access to the Switch
- Setting Allowable Source IP Address Ranges
- RADIUS Authentication and Authorization
- TACACS+ Authentication
- LDAP Authentication and Authorization
- Secure Shell and Secure Copy
- Configuring SSH/SCP Features on the Switch
- Configuring the SCP Administrator Password
- Using SSH and SCP Client Commands
- SSH and SCP Encryption of Management Messages
- Generating RSA Host and Server Keys for SSH Access
- SSH/SCP Integration with Radius Authentication
- SSH/SCP Integration with TACACS+ Authentication
- End User Access Control
- Ports and Trunking
- Port-Based Network Access Control
- VLANs
- Spanning Tree Protocol
- RSTP and MSTP
- Link Layer Discovery Protocol
- Quality of Service
- Accessing the Switch
- Part 2: IP Routing
- Basic IP Routing
- Routing Information Protocol
- IGMP
- OSPF
- OSPF Overview
- OSPF Implementation in BLADE OS
- OSPF Configuration Examples
- Remote Monitoring
- Part 3: High Availability Fundamentals
- High Availability
- Layer 2 Failover
- Server Link Failure Detection
- VRRP Overview
- Failover Methods
- BLADE OS Extensions to VRRP
- Virtual Router Deployment Considerations
- High Availability Configurations
- High Availability
- Part 4: Appendices
- Index
BLADE OS 5.1 Application Guide
184 Chapter 11: IGMP BMD00113, September 2009
IGMP Snooping
IGMP Snooping allows the switch to forward multicast traffic only to those ports that request it.
IGMP Snooping prevents multicast traffic from being flooded to all ports. The switch learns which
server hosts are interested in receiving multicast traffic, and forwards it only to ports connected to
those servers.
IGMP Snooping conserves bandwidth. With IGMP Snooping, the switch learns which ports are
interested in receiving multicast data, and forwards multicast data only to those ports. In this way,
other ports are not burdened with unwanted multicast traffic.
The switch can sense IGMP Membership Reports from attached clients and act as a proxy to set up
a dedicated path between the requesting host and a local IP Multicast router. After the pathway is
established, the switch blocks the IP Multicast stream from flowing through any port that does not
connect to a host member, thus conserving bandwidth.
The client-server path is set up as follows:
An IP Multicast Router (Mrouter) sends Membership Queries to the switch, which forwards
them to all ports in a given VLAN.
Hosts that want to receive the multicast data stream send Membership Reports to the switch,
which sends a proxy Membership Report to the Mrouter.
The switch sets up a path between the Mrouter and the host, and blocks all other ports from
receiving the multicast.
Periodically, the Mrouter sends Membership Queries to ensure that the host wants to continue
receiving the multicast. If a host fails to respond with a Membership Report, the Mrouter stops
sending the multicast to that path.
The host can send a Leave Report to the switch, which sends a proxy Leave Report to the
Mrouter. The multicast path is terminated immediately.
A maximum of 8 VLANs can be configured for IGMP Snooping. The switch can learn up to 16
multicast routers, and supports up to 64 multicast groups.