|
SYSTEM ADMINISTRATOR GUIDE 24/1543-CRA 119 1170/1-V1 Uen A | |
Copyright
© Copyright Ericsson AB 2009. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.
Trademark List
| SmartEdge | is a registered trademark of Telefonaktiebolaget L M Ericsson. | |
| NetOp | is a trademark of Telefonaktiebolaget L M Ericsson. |
| 1 | Overview |
2 | Configuration and Operations Tasks |
| 2.1 | Configuring RIP |
| 2.2 | Configuring RIPng |
| 2.3 | RIP and RIPng Operations |
3 | Configuration Examples |
RIP is a distance-vector protocol that uses a hop count as its metric. Relatively old, RIP is still commonly used, especially in small homogeneous networks. Our implementation supports RIP Version 2 and provides for multiple RIP instances. Each instance maintains its own routing table and set of interfaces. Each interface can only be assigned to, at most, one RIP instance.
RIP is documented in RFC 1058, Routing Information Protocol, and RFC 1723,RIP Version 2, Carrying Additional Information.
RIP next generation (RIPng) is an enhanced version of RIP that supports IP Version 6 (IPv6)-based network routing. RIPng is documented in RFC 2080, RIPng for IPv6. For a description of IPv6 addressing and the types of IPv6 addresses, see RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture.
The sections that follow describe how to configure RIP.
To configure a RIP routing instance, perform the tasks described in Table 1. Enter all commands in RIP router configuration mode, unless otherwise noted.
|
Task |
Root Command |
Notes |
|---|---|---|
Configure an instance of the RIP routing process and enter RIP router configuration mode. |
Enter this command in context configuration mode. | |
Inject the default route (0.0.0.0) into the RIP instance. |
— | |
Set the default metric for the RIP instance. |
The default value is used when a route with incompatible metrics is received into the RIP instance; for example, when a route from a different routing domain is imported into RIP. | |
Modify the administrative distance for the RIP instance. |
Administrative distance specifies how desirable a route obtained from RIP is compared to the same route obtained from another protocol. The lower the value for the distance argument in comparison to other routes obtained from other protocols, the more desirable the RIP route becomes. | |
Apply a prefix list to RIP packets. |
— | |
Modify the minimum interval between consecutive RIP flash updates. |
Each flash update contains only those routes that have been changed since the most recent update. | |
Modify the number of multiple equal-cost RIP routes that can be used as the best paths for load balancing outgoing traffic packets. |
The SmartEdge® router enables load balancing among these RIP paths if, in the routing table, they are the best paths among paths provided by all running routing protocols. | |
Configure a RIP offset list. |
A RIP offset list adds to the cost metric of inbound or outbound routes learned or advertised by RIP. | |
Add a delay time between packets sent in multipacket RIP updates. |
This feature is useful for situations where a high-speed router is sending updates to a low-speed router. | |
Redistribute routes learned through protocols other than RIP into the RIP instance. |
You must enter multiple redistribute commands to redistribute routes from several different kinds of routing protocols into the RIP routing instance. | |
Modify RIP timers for the specified RIP instance. |
— |
To configure a RIP interface, perform the tasks described in Table 2. Enter all commands in RIP interface configuration mode, unless otherwise noted.
|
Task |
Root Command |
Notes |
|---|---|---|
Enable an interface to both send and receive RIP packets, and to access RIP interface configuration mode. |
Enter this command in RIP router configuration mode. | |
Enable authentication and specify the authentication scheme for the RIP interface. |
— | |
Configure the RIP interface to originate the default route (0.0.0.0). |
— | |
Modify the cost value of an interface. |
The cost value is used by RIP as a metric for route selection. The lower the cost, the more likely an interface is to be used to forward data traffic. | |
Enable an interface to receive and process RIP packets. |
— | |
Enable RIP split-horizon processing on an interface. |
Simple split-horizon processing is enabled by default. | |
Summarize routes in RIP update packets on the specified interface. |
— | |
Enable an interface to send RIP packets. |
— | |
Modify RIP timers for the specified interface. |
— |
To configure RIP, perform the tasks described in the sections that follow.
To configure a RIPng routing instance, perform the tasks described in Table 3. Enter all commands in RIPng router configuration mode, unless otherwise noted.
|
Task |
Root Command |
Notes |
|---|---|---|
Create an instance of the RIPng routing process and enter RIPng router configuration mode. |
Enter this command in context configuration mode. | |
Inject the default route (::/0) into the RIPng instance. |
— | |
Set the default metric for the RIPng instance. |
The default value is used when a route with incompatible metrics is received into the RIPng instance; for example, when a route from a different routing domain is imported into RIPng. | |
Modify the administrative distance for the RIPng instance. |
Administrative distance specifies how desirable a route obtained from RIPng is compared to the same route obtained from another protocol. The lower the value for the distance argument in comparison to other routes obtained from other protocols, the more desirable the RIP route becomes. | |
Apply a prefix list to RIPng packets. |
— | |
Modify the minimum interval between consecutive RIPng flash updates. |
Each flash update contains only those routes that have been changed since the most recent update. | |
Modify the number of multiple equal-cost RIPng routes that can be used as the best paths for load balancing outgoing traffic packets. |
The SmartEdge router enables load balancing among these RIPng paths if, in the routing table, they are the best paths among paths provided by all running routing protocols. | |
Add a delay time between packets sent in multipacket RIPng updates. |
This feature is useful for situations where a high-speed router is sending updates to a low-speed router. | |
Redistribute routes learned through protocols other than RIPng into the RIPng instance. |
You must enter multiple redistribute commands to redistribute routes from several different kinds of routing protocols into the RIPng routing instance. | |
Modify RIPng timers for the specified RIPng instance. |
— |
To configure a RIPng interface, perform the tasks described in Table 4. Enter all commands in RIPng interface configuration mode, unless otherwise noted.
|
Task |
Root Command |
Notes |
|---|---|---|
Enable an interface to both send and receive RIP packets, and to enter RIPng interface configuration mode. |
Enter this command in RIPng router configuration mode. | |
Configure the RIPng interface to originate the default route (::/0). |
— | |
Modify the cost value of an interface. |
The cost value is used by RIPng as a metric for route selection. The lower the cost, the more likely an interface is to be used to forward data traffic. | |
Enable an interface to receive and process RIPng packets. |
— | |
Enable RIPng split-horizon processing on an interface. |
Simple split-horizon processing is enabled by default. | |
Summarize routes in RIPng update packets on the specified interface. |
— | |
Enable an interface to send RIPng packets. |
— | |
Modify RIPng timers for the specified interface. |
— |
To manage RIP and RIPng functions, perform the appropriate tasks described in Table 5. Enter the show commands in any mode; enter the debug command (in exec mode).
|
Task |
Root Command |
|---|---|
Enable the generation of RIP debug messages. |
|
Display the current RIP configuration for the current context. |
|
Display enabled RIP debug settings. |
|
Display information for all RIP instances, or only for a particular RIP instance. |
|
Display information for all RIP interfaces, or only for interfaces within a particular RIP instance. |
|
Display Routing Information Protocol next generation (RIPng) information. |
|
Display information about all RIP routes, or only for routes within a particular RIP instance. |
The following example configures one RIP instance, adjusts the maximum number of equal-cost paths to 4, originates a default route, and redistributes static routes into RIP with metric of 10. It then enables RIP on interface fe1:
[local]Redback#configure [local]Redback(config)#context local [local]Redback(config-ctx)#router rip edge [local]Redback(config-rip)#maximum-paths 4 [local]Redback(config-rip)#default-information originate [local]Redback(config-rip)#redistribute static metric 10 [local]Redback(config-rip)#interface fe1 [local]Redback(config-rip-if)#end
The following example configures two RIP instances in the local context. Next, it enables one RIP instance edge and a RIP instance backbone on interface fe1. An IP prefix list, prefixList1, is also applied on the outbound updates on interface fe1:
[local]Redback#configure [local]Redback(config)#context local [local]Redback(config-ctx)#router rip edge [local]Redback(config-rip)#redistribute static metric 10 [local]Redback(config-rip)#interface fe1 [local]Redback(config-rip-if)#exit [local]Redback(config-rip)#exit [local]Redback(config-ctx)#router rip backbone [local]Redback(config-rip)#distribute-list prefixList1 out fe1 [local]Redback(config-rip)#interface fe1 [local]Redback(config-rip-if)#end