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 6: RSTP and MSTP 125
Multiple Spanning Tree Protocol
IEEE 802.1s Multiple Spanning Tree extends the IEEE 802.1w Rapid Spanning Tree Protocol
through multiple Spanning Tree Groups. MSTP maintains up to 32 spanning-tree instances, that
correspond to STP Groups 1-32.
For more information about Spanning Tree Protocol, see “Spanning Tree Protocol” on page 109.
In Multiple Spanning Tree Protocol (MSTP), several VLANs can be mapped to each Spanning-Tree
instance. Each Spanning-Tree instance is independent of other instances. MSTP allows frames
assigned to different VLANs to follow separate paths, each path based on an independent
Spanning-Tree instance. This approach provides multiple forwarding paths for data traffic, enabling
load-balancing, and reducing the number of Spanning-Tree instances required to support a large
number of VLANs.
By default, the spanning tree on the management ports is turned off in both STP/PVST+ mode and
in MSTP/RSTP mode.
MSTP Region
A group of interconnected bridges that share the same attributes is called an MST region. Each
bridge within the region must share the following attributes:
Alphanumeric name
Revision number
VLAN-to STG mapping scheme
MSTP provides rapid re-configuration, scalability and control due to the support of regions, and
multiple Spanning-Tree instances support within each region.
Common Internal Spanning Tree
The Common Internal Spanning Tree (CIST) provides a common form of Spanning Tree Protocol,
with one Spanning-Tree instance that can be used throughout the MSTP region. CIST allows the
switch to interoperate with legacy equipment, including devices that run IEEE 802.1D (STP).
CIST allows the MSTP region to act as a virtual bridge to other bridges outside of the region, and
provides a single Spanning-Tree instance to interact with them.
CIST port configuration includes Hello time, Edge port enable/disable, and Link Type. These
parameters do not affect Spanning Tree Groups 1–128. They apply only when the CIST is used.