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 2: Ports and Trunking 73
Link Aggregation Control Protocol
LACP Overview
Link Aggregation Control Protocol (LACP) is an IEEE 802.3ad standard for grouping several
physical ports into one logical port (known as a dynamic trunk group or Link Aggregation group)
with any device that supports the standard. Please refer to IEEE 802.3ad-2002 for a full description
of the standard.
The 802.3ad standard allows standard Ethernet links to form a single Layer 2 link using the Link
Aggregation Control Protocol (LACP). Link aggregation is a method of grouping physical link
segments of the same media type and speed in full duplex, and treating them as if they were part of
a single, logical link segment. If a link in a LACP trunk group fails, traffic is reassigned
dynamically to the remaining link/s of the dynamic trunk group.
Note – LACP implementation in BLADE OS does not support the Churn machine, an option used
to detect if the port is operable within a bounded time period between the actor and the partner. Only
the Marker Responder is implemented, and there is no marker protocol generator.
A port’s Link Aggregation Identifier (LAG ID) determines how the port can be aggregated. The
Link Aggregation ID (LAG ID) is constructed mainly from the system ID and the port’s admin key,
as follows:
System ID is an integer value based on the switch’s MAC address and the system priority
assigned in the CLI.
Admin key. A port’s Admin key is an integer value (1 - 65535) that you can configure in the
CLI. Each GbE2c port that participates in the same LACP trunk group must have the same
admin key value. The Admin key is local significant, which means the partner switch does not
need to use the same Admin key value.
For example, consider two switches, an Actor (the GbE2c) and a Partner (another switch), as shown
in Table 8.
Table 8 Actor vs. Partner LACP configuration
Actor Switch Partner Switch 1 Partner Switch 2
Port 20 (admin key = 100) Port 1 (admin key = 50)
Port 21 (admin key = 100) Port 2 (admin key = 50)
Port 22 (admin key = 200) Port 3 (admin key = 60)
Port 23 (admin key = 200) Port 4 (admin key = 60)