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
BMD00113, September 2009 Chapter 14: High Availability 233
Configuration Guidelines
This section provides important information about configuring Layer 2 Failover.
Note – Auto Monitor and Manual Monitor are mutually exclusive. They cannot both be configured
on the switch.
Auto Monitor Guidelines
Any specific failover trigger may monitor static trunks only or LACP trunks only, but not both.
All uplink ports in all static or LACP trunks added to any specific failover trigger must belong
to the same VLAN.
A maximum of two LACP keys can be added per trigger.
When VLAN Monitor is on, the following additional guidelines apply:
All uplink ports in all static or LACP trunks added to a specific failover trigger must
belong to the same VLAN and have the same PVID.
Different triggers are not permitted to operate on the same VLAN.
Different triggers are not permitted to operate on the same downlink port.
For each port in each trunk in a specific failover trigger, the trigger will monitor the STP
state on only the default PVID.
Manual Monitor Guidelines
A Manual Monitor can monitor only uplink ports.
Any specific failover trigger can monitor uplink ports only, static trunks only, or LACP trunks
only. The different types cannot be combined in the same trigger.
A maximum of two LACP keys can be added per trigger.
Port membership for different triggers should not overlap. Any specific port should be a
member of only one trigger.