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 10: Routing Information Protocol 181
RIP Configuration Example
Note – An interface RIP disabled uses all the default values of the RIP, no matter how the RIP
parameters are configured for that interface. RIP sends out RIP regular updates to include an UP
interface, but not a DOWN interface.
1. Add VLANs for routing interfaces.
2. Add IP interfaces to VLANs.
3. Turn on RIP globally and enable RIP for each interface.
Use the /maint/route/dump command to check the current valid routes in the routing table of
the switch.
For those RIP learnt routes within the garbage collection period, that are routes phasing out of the
routing table with metric 16, use the /info/l3/rip/routes command. Locally configured
static routes do not appear in the RIP Routes table.
>> Main# /cfg/l2/vlan 2/ena (Enable VLAN 2)
>> VLAN 2# add 21 (Add port 21 to VLAN 2)
Port 21 is an UNTAGGED port and its current PVID is 1.
Confirm changing PVID from 1 to 2 [y/n]: y
>> VLAN 2# /cfg/l2/vlan 3/ena (Enable VLAN 3)
>> VLAN 3# add 22 (Add port 22 to VLAN 3)
Port 22 is an UNTAGGED port and its current PVID is 1.
Confirm changing PVID from 1 to 3 [y/n]: y
>> VLAN 3# /cfg/l3/if 2/ena (Enable interface 2)
>> IP Interface 2# addr 102.1.1.1 (Define IP address for interface 2)
>> IP Interface 2# vlan 2 (Add interface 2 to VLAN 2)
>> IP Interface 2# /cfg/l3/if 3/ena (Enable interface 3)
>> IP Interface 3# addr 103.1.1.1 (Define IP address for interface 3)
>> IP Interface 3# vlan 3 (Add interface 3 to VLAN 3)
>> IP Interface 3# /cfg/l3/rip/on (Turn on RIP globally)
>> Routing Information Protocol# if 2/ena (Enable RIP on IP interface 2)
>> RIP Interface 2# ..
>> Routing Information Protocol# if 3/ena (Enable RIP on IP interface 3)
>> RIP Interface 3# apply (Apply your changes)
>> RIP Interface 3# save (Save the configuration)