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 5: Spanning Tree Protocol 119
Configuring Fast Uplink Convergence
Use the following CLI commands to enable Fast Uplink Convergence on uplink ports.
Hot Links
For network topologies that require Spanning Tree to be turned off, Hot Links provides basic link
redundancy with fast recovery.
Hot Links consists of up to five triggers. A trigger consists of a pair of layer 2 interfaces, each
containing an individual port, trunk, or LACP adminkey. One interface is the Master, and the other
is a Backup. While the Master interface is set to the active state and forwards traffic, the Backup
interface is set to the standby state and blocks traffic until the Master interface fails. If the Master
interface fails, the Backup interface is set to active and forwards traffic. Once the Master interface is
restored, it transitions to the standby state and blocks traffic until the Backup interface fails.
You may select a physical port, static trunk, or an LACP adminkey as a Hot Link interface. Only
cross-connect ports and uplink ports can be members of a Hot Links trigger interface.
Forward Delay
The Forward Delay timer allows Hot Links to monitor the Master and Backup interfaces for link
stability before selecting one interface to transition to the active state. Before the transition occurs,
the interface must maintain a stable link for the duration of the Forward Delay interval.
For example, if you set the Forward delay timer to 10 seconds
(/cfg/l2/hotlink/trigger <x>/fdelay 10), the switch will select an interface to
become active only if a link remained stable for the duration of the Forward Delay period. If the link
is unstable, the Forward Delay period starts again.
Pre-emption
You can configure the Master interface to resume the active state whenever it becomes available.
With Hot Links preemption enabled (/cfg/l2/hotlink/trigger <x>/preempt ena),
the Master interface transitions to the active state immediately upon recovery. The Backup interface
immediately transitions to the standby state. If Forward Delay is enabled, the transition occurs when
an interface has maintained link stability for the duration of the Forward Delay period.
>> # /cfg/l2/upfast ena (Enable Fast Uplink convergence)
>> Layer 2# apply (Make your changes active)
>> Layer 2# save (Save for restore after reboot)