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 9: Basic IP Routing 173
Switch Name Identifiers
In the following examples, consider a switch named “BladeS1”. Depending on the port type, the
dhcpd.conf configuration might appear as follows.
Using DHCP Option 61 Client Identifiers
For non-trunked ports 1 and 7:
For ports in static trunk 3:
For ports in an LACP trunk with admin key 16:
Note – The \000 in front of the switch name is the octal “type” byte required in the client
identifier.
group {
host BntHost1 {
option dhcp-client-identifier "\000BladeS1-1";
fixed-address 172.31.160.161;
}
host BntHost7 {
option dhcp-client-identifier "\000BladeS1-7";
fixed-address 172.31.160.167;
}
}
host BntTrunk3 {
option dhcp-client-identifier "\000BladeS1-t3";
fixed-address 172.31.160.153;
}
host BntLacp16 {
option dhcp-client-identifier "\000BladeS1-k16";
fixed-address 172.31.160.156;
}