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
238 Chapter 14: High Availability BMD00113, September 2009
2. Assign crosslink ports to enable when a server link failure occurs.
3. Turn on SFD.
When a link failure or Spanning Tree blocking occurs on server port 1 and server port 2, Switch 1
enables crosslink ports 17 and 18.
Configuring SFD on Switch 2
1. Assign downlink ports to be monitored for link failure.
2. Assign crosslink ports to enable when a server link failure occurs.
3. Turn on SFD.
When a link failure or Spanning Tree blocking occurs on server port 1 and server port 2, Switch 1
enables crosslink ports 17 and 18.
>> Server Link Failure Detection# lte (Select Link to Enable menu)
>> Link to Enable# addport 17
>> Link to Enable# addport 18
>> Link to Enable# ..
>> Server Link Failure Detection#
>> Server Link Failure Detection# on
>> Server Link Failure Detection # apply
>> Server Link Failure Detection # save
>> Main# /cfg/sfd/ltm (Select SFD Link to Monitor menu)
>> Link to Monitor# addport 1
>> Link to Monitor# addport 2
>> Link to Monitor# ..
>> Server Link Failure Detection#
>> Server Link Failure Detection# lte
(Select Link to Enable menu)
>> Link to Enable# addport 17
>> Link to Enable# addport 18
>> Link to Enable# ..
>> Server Link Failure Detection#
>> Server Link Failure Detection# on
>> Server Link Failure Detection # apply
>> Server Link Failure Detection # save