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
BMD00113, September 2009 177
CHAPTER 10
Routing Information Protocol
In a routed environment, routers communicate with one another to keep track of available routes.
Routers can learn about available routes dynamically using the Routing Information Protocol (RIP).
BLADE OS software supports RIP version 1 (RIPv1) and RIP version 2 (RIPv2) for exchanging
TCP/IP route information with other routers.
Distance Vector Protocol
RIP is known as a distance vector protocol. The vector is the network number and next hop, and the
distance is the cost associated with the network number. RIP identifies network reachability based
on metric, and metric is defined as hop count. One hop is considered to be the distance from one
switch to the next, which typically is 1.
When a switch receives a routing update that contains a new or changed destination network entry,
the switch adds 1 to the metric value indicated in the update and enters the network in the routing
table. The IP address of the sender is used as the next hop.
Stability
RIP includes a number of other stability features that are common to many routing protocols. For
example, RIP implements the split horizon and hold-down mechanisms to prevent incorrect routing
information from being propagated.
RIP prevents routing loops from continuing indefinitely by implementing a limit on the number of
hops allowed in a path from the source to a destination. The maximum number of hops in a path is
15. The network destination network is considered unreachable if increasing the metric value by 1
causes the metric to be 16 (that is infinity). This limits the maximum diameter of a RIP network to
less than 16 hops.
RIP is often used in stub networks and in small autonomous systems that do not have many
redundant paths.