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 167
In the following example, one new class is added to define server port 2, then an IP address is
associated with the new class:
This example was performed with Internet Systems Consortium DHCP Server, version 3.0.4
******CLASS******
# in this class I have defined a switch in chassis with ID
# 55:53:45:36:33:35:31:4d:34:36:00:00:00:00:00:00
# placed in slot 1 and blade server is connected in port 2
class "chass_a _sw_1_port_2"
{
match if option agent.circuit-id =
55:53:45:36:33:35:31:4d:34:36:00:00:00:00:00:00
and option agent.remote-id = 01:0:0:0:02; }
******Range for that class*********
# for class chass_a _sw_1_port_2 only one IP
# is defined (10.70.70.10)
subnet 10.70.70.0 netmask 255.255.255.0 {
pool
{
allow members of " chass_a _sw_1_port_2"; range 10.70.70.10; }
}