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
38 Chapter 1: Accessing the Switch BMD00113, September 2009
Client IP Address Agents
BOOTP Relay Agent
BOOTP Relay Agent Overview
The GbE2c can function as a Bootstrap Protocol relay agent, enabling the switch to forward a client
request for an IP address up to two BOOTP servers with IP addresses that have been configured on
the switch.
When a switch receives a BOOTP request from a BOOTP client requesting an IP address, the
switch acts as a proxy for the client. The request is then forwarded as a UDP Unicast MAC layer
message to two BOOTP servers whose IP addresses are configured on the switch. The servers
respond to the switch with a Unicast reply that contains the default gateway and IP address for the
client. The switch then forwards this reply back to the client.
Figure 1 shows a basic BOOTP network example.
Figure 1 BOOTP Relay Agent Configuration
The use of two servers provide failover redundancy. The client request is forwarded to both BOOTP
servers configured on the switch. However, no health checking is supported.
BOOTP Relay Agent Configuration
To enable the GbE2c to be the BOOTP forwarder, you need to configure the BOOTP server IP
addresses on the switch, and enable BOOTP relay on the interface(s) on which the BOOTP requests
are received.
Generally, you should configure the command on the switch IP interface that is closest to the client,
so that the BOOTP server knows from which IP subnet the newly allocated IP address should come.
BOOT Client
asks for IP from
BOOTP server
BLADE switch acts as
BOOTP Relay Agent
BOOTP Server
Boston Raleigh
20.1.1.1
10.1.1.2
Blade Chassis
Blade Chassis