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
236 Chapter 14: High Availability BMD00113, September 2009
Server Link Failure Detection
Server Link Failure Detection (SFD) allows the switch to monitor specific downlink ports to detect
server link failures. When all of the server links in the Link to Monitor (LtM) fail, the switch
enables the crosslink ports.
To use SFD, configure the following groups of ports:
Link to Monitor (LtM)
The Link to Monitor group consists of server downlink ports, or one trunk group that contains
only downlink ports. The switch monitors the LtM for link failure.
Link to Enable (LtE)
The Link to Enable group consists of one or more crosslink ports (17-18), or a trunk group that
contains only crosslink ports.
When all of the links in the LtM fail, the switch automatically enables the crosslink ports in the LtE.
When at least one link in the LtM returns to service, the switch automatically disables the crosslink
ports in the LtE.
The following figure shows a basic SFD configuration, with a Link to Monitor (LTM) that consists
of downlink port for Server 1 and Server 2. When all links in the LtM fail, the switch enables the
crosslink ports in the LtE. Data traffic bypasses the servers via the crosslink.
Figure 30 Server Link Failure Detection
Switch 1
Clients
Switch 2
Internet
BladeSystem Chassis
NIC 1
NIC 2
NIC 1
NIC 2
Server
1
Server
2
Downlink
Ports (LtM)
Uplink
Ports
Interconnect
Ports (LtE)