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
196 Chapter 12: OSPF BMD00113, September 2009
OSPF Implementation in BLADE OS
BLADE OS supports a single instance of OSPF and up to 4K routes on the network. The following
sections describe OSPF implementation in BLADE OS:
“Configurable Parameters” on page 196
“Defining Areas” on page 197
“Interface Cost” on page 199
“Electing the Designated Router and Backup” on page 199
“Summarizing Routes” on page 199
“Default Routes” on page 200
“Virtual Links” on page 201
“Router ID” on page 201
“Authentication” on page 202
Configurable Parameters
In BLADE OS, OSPF parameters can be configured through the Command Line Interfaces
(CLI/ISCLI), Browser-Based Interface (BBI), or through SNMP. For more information, see
“Accessing the Switch” on page 23.”
The CLI supports the following parameters: interface output cost, interface priority, dead and hello
intervals, retransmission interval, and interface transmit delay.
In addition to the above parameters, you can also specify the following:
OSPF traps–Traps produce messages upon certain events or error conditions, such as missing a
hello, failing a neighbor, or recalculating the SPF.
Link-State Database size—The size of the external LSA database can be specified to help
manage the memory resources on the switch.
Shortest Path First (SPF) interval—Time interval between successive calculations of the
shortest path tree using the Dijkstra’s algorithm.
Stub area metric—A stub area can be configured to send a numeric metric such that all routes
received via that stub area carry the configured metric to potentially influence routing decisions.
Default routes—Default routes with weight metrics can be manually injected into transit areas.
This helps establish a preferred route when multiple routing devices exist between two areas. It
also helps route traffic to external networks.
Passive—When enabled, the interface sends LSAs to upstream devices, but does not otherwise
participate in OSPF protocol exchanges.
Point-to-Point—For LANs that have only two OSPF routing agents (the GbE2c and one other
device), this option allows the switch to significantly reduce the amount of routing information
it must carry and manage.