Home > HP > Printer > HP 5500 Ei 5500 Si Switch Series Configuration Guide

HP 5500 Ei 5500 Si Switch Series Configuration Guide

Add to Favourites
    Download as PDF Print this page Share this page

    Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    View all the pages
    Page
    of 2513
    Add page 711 to Favourites
    image text
    Enable zoom 
    							 22 
•  Suppress timer —Defines how long a RIP route stays in suppr essed state. When the metric of a route 
is 16, the route enters the suppressed state. In su ppressed state, only routes coming from the same 
neighbor and whose metric is less than 16 will be  received by the router to replace unreachable 
routes. 
•   Garbage-collect timer — D efi n es  t h e  i nte r va l  fro m  wh e n  t h e  m e t ric  of  a  ro u te  b e c o mes  16  to  wh e n  i t  
is deleted from the routing table. During the gar bage-collect timer length, RIP advertises the route 
with the routing metric set to 16. If no update is announced for that route after the garbage-collect 
timer expires, then the route is deleted from the routing table. 
Routing loops prevention 
RIP is a distance vector routing protocol. Because  a RIP router advertises its own routing table to 
neighbors, routing loops may occur. 
RIP uses the following mechanisms to prevent routing loops: 
•   Counting to infinity —The metric value of 16 is defined as unreachable. When a routing loop occurs, 
the metric value of the route will increment to 16. 
•   Split horizon —A router does not send routing information back to the neighboring router the 
information came from, preventing routing loops and saving bandwidth. 
•   Po i so n  reve r s e —A router sets the metric of routes received from a neighbor to 16 and sends back 
these routes to the neighbor to help delete such information from the neighbor’s routing table. 
•   Triggered updates —A router advertises updates once the metric of a route is changed instead of 
after the update period expires to speed up network convergence. 
RIP operation 
The following procedure describes how RIP works: 
1.  After RIP is enabled, the router sends request messages to neighboring routers. Neighboring 
routers return response messages, including information about their routing tables. 
2. After receiving this information, the router updat es its local routing table, and sends triggered 
update messages to its neighbors.  All routers on the network do this to keep the latest routing 
information.  
3.  By default, a RIP router sends its routing table to neighbors every 30 seconds. 
4. RIP ages out routes by adopting an agin g mechanism to keep only valid routes. 
RIP versions 
RIP has RIPv1 and RIPv2. 
RIPv1, a classful routing protocol, supports message advertisement through broadcast only. RIPv1 
protocol messages do not carry mask information, so  it can only recognize routing information of natural 
networks such as Class A, B, and C. For this re ason, RIPv1 does not support discontiguous subnets. 
RIPv2 is a classless routing protocol and  has the following advantages over RIPv1. 
•   Supports route tags, which are used in routing policies to flexibly control routes. 
•   Supports masks, route summarization, and Classless Inter-Domain Routing (CIDR). 
•   Supports designated next hops to select the best ones on broadcast networks. 
•   Supports multicasting routing updat es to reduce resource consumption. Only RIPv2 routers can 
receive these update messages.
    Add page 712 to Favourites
    image text
    Enable zoom 
    							 23 
•  Supports simple authentication and MD5 authentication to enhance security.   
  NOTE: 
RIPv2 has two types of messa
ge transmission: broadcast and multicast. Multicast is the default type using
224.0.0.9 as the multicast address. The interface oper ating in the RIPv2 broadcast mode can also receive
RIPv1 messages. 
 
RIP message format 
A RIP message consists of a header and up to 25 rout e entries. (A RIPv2 authentication message uses the 
first route entry as the authentication entry, leaving 24 available.) 
RIPv1 message format 
Figure 6  RIPv1 message format 
 
 
•  Command —Type of message. 1 indicates request, which is used to request all or part of the routing 
information from the neighbor; 2 indicates response, which contains all or part of the routing 
information. A response message consis ts of up to 25 route entries.  
•   Version —Version of RIP, 0x01 for RIPv1. 
•   Must be zero —This field must be zero 
•   AFI—Address Family Identifier, 2 for IP. 
•   IP address —Destination IP address of the route that can be a natural network, subnet, or a host 
address. 
•   Metric —Cost of the route. 
RIPv2 message format 
The format of RIPv2 message is similar to RIPv1.  
Figure 7  RIPv2 Message Format
    Add page 713 to Favourites
    image text
    Enable zoom 
    							 24 
The differences between RIPv1 and RIPv2 messages are stated as follows: 
•   Version –Version of RIP. For RIPv2 the value is 0x02. 
•   Route tag. 
•   IP address —Destination IP address. It can be a natural network address, subnet address, or host 
address. 
•   Subnet mask —Mask of the destination address. Unlike RIPv1, RIPv2 can carry subnet information. 
•   Next hop —If set to 0.0.0.0, it indicates that the originator of the route is the best next hop. 
Otherwise, it indicates a next hop better than the originator of the route. 
RIPv2 authentication message format 
RIPv2 sets the AFI field of the first route entry to 0xFFFF to identify authentication information.  
Figure 8  RIPv2 authentication message 
 
 
•  Authentication Type —A value of 2 represents simple authentication. A value of 3 represents MD5. 
RFC 1723 only defines simple authentication. For more information about MD5 authentication, see 
RFC 2453,  RIP Version 2 . 
•   Authentication —Authentication data, including password information when simple authentication 
is adopted or including key ID, MD5 authenticati on data length and sequence number when MD5 
authentication is adopted. 
 
  NOTE: 
Even thougn with RIPv1, you can configure the authen tication mode in interface view, the configuration 
will not take effect because RIPv1 does not support authentication.   
Supported RIP features 
The current implementation supports the following RIP features: 
•  RIPv1 and RIPv2 
•   RIP support for multi-VPN-instance 
•   RIP FRR 
•   BFD 
RIP periodically sends route update requests to neighbors. If no route update response for a route is 
received within the specified interval, RIP considers  the route unreachable. This mechanism cannot detect 
link faults quickly. After BFD is configured for RIP, and BFD detects a broken link, RIP can quickly age out 
the unreachable route, thus avoiding interference to other services.  
Command
0xFFFF
Authentication (16 octets)
VersionUnused
Authentication type
071
531
    Add page 714 to Favourites
    image text
    Enable zoom 
    							 25 
Protocols and standards 
•  RFC 1058,  Routing Information Protocol  
•   RFC 1723,  RIP Version 2 - Carrying Additional Information  
•   RFC 1721,  RIP Version 2 Protocol Analysis  
•   RFC 1722,  RIP Version 2 Protocol Applicability Statement  
•   RFC 1724,  RIP Version 2 MIB Extension  
•   R FC  2 082,   RIPv2 MD5 Authentication  
•   RFC 2453,  RIP Version 2  
RIP configuration task list 
 
Task Remarks 
Configuring RIP basic functions  Required 
Configuring RIP route 
control Configuring an additional routing metric 
Optional 
Configuring RIPv2 route summarization Optional 
Disabling host route reception Optional 
Advertising a default route Optional 
Configuring inbound or outbound route filtering Optional 
Configuring a priority for RIP Optional 
Configuring RIP route redistribution Optional 
Tuning and optimizing 
RIP networks Configuring RIP timers 
Optional 
Configuring split horizon and poison reverse Optional 
Configuring the maximum number of ECMP routes Optional 
Enabling zero field check on incoming RIPv1 
messages Optional 
Enabling source IP address check on incoming RIP 
updates Optional 
Configuring RIPv2 message authentication 
Optional 
Specifying a RIP neighbor Optional 
Configuring RIP-to-MIB binding Optional 
Configuring the RIP packet sending rate Optional 
Configuring RIP FRR  Optional 
Configuring BFD for RIP Single-hop detection in BFD echo packet mode 
Optional Bidirectional detection in BFD control packet mode Optional
    Add page 715 to Favourites
    image text
    Enable zoom 
    							 26 
Configuring RIP basic functions 
Configuration prerequisites 
Before you configure RIP basic functions, complete the following tasks: 
•  Configure the link layer protocol. 
•   Configure IP addresses for interfaces, and make sure that all neighboring routers can reach each 
other. 
Enabling RIP and a RIP interface 
Follow these guidelines when you enable RIP: 
•  RIP configurations made in interface view before enabling RIP take effect after RIP is enabled. 
•   RIP runs only on the interfaces residing on the specified networks. Specify the network after 
enabling RIP to validate RIP on a specific interface. 
•   You can enable RIP on all interfaces using the command  network 0.0.0.0. 
•   If a physical interface is attached to multiple  networks, you cannot advertise these networks in 
different RIP processes. 
To  e n ab l e  R I P : 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enable a RIP process and 
enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  Disabled by default. 
3.
  Enable RIP on the interface 
attached to the specified 
network.  network 
network-address  Disabled by default. 
 
Configuring the interface behavior  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Disable an or all interfaces 
from sending routing updates 
(the interfaces can still receive 
updates).  silent-interface { interface-type 
interface-number
 | all }  Optional. 
By default, all interfaces can send 
routing updates. 
4.
  Return to system view. 
quit  N/A 
5.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
6.
  Enable the interface to receive 
RIP messages.  rip input  Optional. 
Enabled by default.
    Add page 716 to Favourites
    image text
    Enable zoom 
    							 27 
Step Command Remarks 
7.  Enable the interface to send 
RIP messages.  rip output  Optional. 
Enabled by default.
 
 
Configuring a RIP version 
You can configure a RIP version in RIP view or  interface view under the following conditions. 
•   If neither global nor interface RIP version is co nfigured, the interface sends RIPv1 broadcasts and 
can receive the following packets: RIPv1 broadcast, RIPv1 unicast, RIPv2 broadcast, RIPv2 multicast, 
and RIPv2 unicast. 
•   If an interface has no RIP version configured, it uses the global RIP version; otherwise it uses the RIP 
version configured on it. 
•   With RIPv1 configured, an interface sends RIPv1 broadcasts, and can receive RIPv1 broadcasts 
and RIPv1 unicasts. 
•   With RIPv2 configured, a multicast interface sends RIPv2 multicasts and can receive RIPv2 unicasts, 
broadcasts, and multicasts. 
•   With RIPv2 configured, a broadcast interface sends RIPv2 broadcasts and can receive RIPv1 
unicasts and broadcasts, and RIPv2 broadcasts, multicasts, and unicasts. 
To configure a RIP version: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Specify a global RIP version. 
version { 1 | 2 }  Optional. 
By default, if an interface has a RIP 
version specified, the version takes 
precedence over the global one. If 
no RIP version is specified for an 
interface, the interface can send 
RIPv1 broadcasts, and receive 
RIPv1 broadcasts and unicasts, 
and RIPv2 broadcasts, multicasts, 
and unicasts.
 
4.  Return to system view. 
quit  N/A 
5.  Enter interface view.  interface
 interface-type 
interface-number  N/A 
6.
  Specify a RIP version for the 
interface.  rip version
 { 1 | 2 [ broadcast  | 
multicast  ] }  Optional. 
By default, if an interface has no 
RIP version specified, the global 
version takes effect. If no global RIP 
version is specified, the interface 
can send RIPv1 broadcasts, and 
receive RIPv1 broadcasts and 
unicasts, and RIPv2 broadcasts, 
multicasts, and unicasts.
    Add page 717 to Favourites
    image text
    Enable zoom 
    							 28 
Setting the DSCP value for RIP packets 
An IPv4 packet header contains an 8-bit Type of Service (ToS) field. As defined in RFC 2474, the first six 
bits set the Differentiated Services Code Point (DSCP) value, and the last two bits are reserved. Network 
devices use the DSCP value as a reference to determine the packet priority for transmission.  
You can set the DSCP value for RIP packets. 
To set the DSCP value for RIP packets: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Create a RIP process and 
enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  By default, no RIP process is 
created. 
3.
  Set the DSCP value for RIP 
packets.  dscp
 dscp-value   Optional. 
By default, the DSCP value in RIP 
packets is 48. 
 
Configuring RIP route control 
In complex networks, you must configure advanced RIP features. 
Before you configure RIP routing feature, complete the following tasks: 
•
  Configure IP addresses for interfaces, and make sure that all neighboring routers can reach each 
other. 
•   Configure RIP basic functions. 
Configuring an additional routing metric 
An additional routing metric (hop count) can be added to the metric of an inbound or outbound RIP 
route. 
The outbound additional metric is added to the metric of a sent route, and the route’s metric in the routing 
table is not changed. 
The inbound additional metric is added to the metric  of a received route before the route is added into 
the routing table, and the route’s metric is changed. If the sum of the additional metric and the original 
metric is greater than 16, the metric of the route will be 16. 
To configure additional routing metrics: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface
 interface-type 
interface-number  N/A 
3.
  Define an inbound additional 
routing metric.  rip metricin
 [ route-policy 
route-policy-name  ] value   Optional. 
0 by default. 
4.
  Define an outbound 
additional routing metric.  rip metricout
 [ route-policy 
route-policy-name  ] value   Optional. 
1 by default.
    Add page 718 to Favourites
    image text
    Enable zoom 
    							 29 
 
Configuring RIPv2 route summarization 
Route summarization means that subnets in a natural network are summarized into a natural network that 
is sent to other networks. This feature can reduce the size of routing tables. 
After route summarization, the smallest metric among all the summarized routes is used as the metric of 
the summary route.  
Enabling RIPv2 route automatic summarization 
You can disable RIPv2 route automatic summarization if you want to advertise all subnet routes. 
To enable RIPv2 route automatic summarization:  
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.
  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Enable RIPv2 automatic route 
summarization.  summary  Optional. 
Enabled by default. 
If the subnet routes in the routing 
table are not consecutive, disable 
automatic route summarization to 
avoid black hole routing.  
 
Advertising a summary route 
Disable RIPv2 route automatic summarization before
 advertising a summary route on an interface. 
To configure RIPv2 to advertise a summary route on the specified interface: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Disable RIPv2 automatic route 
summarization.  undo summary 
Enabled by default. 
4.  Return to system view. 
quit  N/A 
5.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
6.
  Advertise a summary route.  rip summary-address
 ip-address 
{  mask  | mask-length  }  N/A 
 
Disabling host route reception 
Perform this task to disable RIPv2 from receiving host routes from the same network and save network 
resources. This feature does not apply to RIPv1. 
To disable RIP from receiving host routes:
    Add page 719 to Favourites
    image text
    Enable zoom 
    							 30 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Disable RIP from receiving 
host routes.  undo host-route 
Enabled by default. 
 
Advertising a default route 
Under the following conditions, you can configure RIP to  advertise a default route with a specified metric 
to RIP neighbors: 
•   In RIP view, you can configure all the interfaces of the RIP process to advertise a default route; in 
interface view, you can configure a RIP interface of  the RIP process to advertise a default route. The 
interface view takes precedence over on the interface. 
•   If a RIP process is enabled to advertise a default  route, to disable an interface of the RIP process 
from default route advertisement, you can use the rip default-route no-originate  command on the 
interface. 
To configure RIP to advertise a default route: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Enable RIP to advertise a 
default route.  default-route { 
only | originate  } 
[ cost  cost  ]  Optional. 
Not enabled by default. 
4.
  Return to system view. 
quit  N/A 
5.  Enter interface view.  interface
 interface-type 
interface-number   N/A 
6.
  Configure the RIP interface to 
advertise a default route.  rip default-route
 { { only | 
originate  } [  cost  cost ] | 
no-originate  }  Optional. 
By default, a RIP interface can 
advertise a default route if the RIP 
process is configured with default 
route advertisement. 
 
 
NOTE: 
The router enabled to advertise a default route does  not receive default routes from RIP neighbors. 
 
Configuring inbound or outbound route filtering 
The device supports route filtering. You can filter routes by configuring the inbound and outbound route 
filtering policies by referencing an ACL or IP prefix  list. You can also configure the router to receive only 
routes from a specified neighbor.
    Add page 720 to Favourites
    image text
    Enable zoom 
    							 31 
To configure route filtering:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Configure the filtering of 
incoming routes.  filter-policy { acl-number 
| 
gateway  ip-prefix-name  | ip-prefix 
ip-prefix-name  [ gateway 
ip-prefix-name  ] } import 
[ interface-type interface-number  ] Not configured by default. 
The 
filter-policy import command 
filters incoming routes. Routes not 
passing the filtering will be neither 
installed into the routing table nor 
advertised to neighbors. 
4.   Configure the filtering of 
outgoing routes.  filter-policy { acl-number
 | 
ip-prefix  ip-prefix-name  } export 
[  protocol  [ process-id  ] | 
interface-type interface-number  ]  Not configured by default. 
The 
filter-policy export  command 
filters outgoing routes, including 
routes redistributed with the 
import-route command. 
 
Configuring a priority for RIP 
Multiple IGP protocols can run in a router. If you want RIP routes to have a higher priority than those 
learned by other routing protocols, then assign RIP  a smaller priority value to influence optimal route 
selection. 
To configure a priority for RIP: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Configure a priority for RIP.  preference 
[ route-policy 
route-policy-name  ] value   Optional. 
100 by default. 
 
Configuring RIP route redistribution 
If a router runs RIP and other routing protocols, you 
can configure RIP to redistribute OSPF, IS-IS, BGP, 
static, or direct routes.  
Only active routes can be redistributed.  To display route state information, use the  display ip 
routing-table  protocol  command. 
To configure RIP route redistribution: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A
    All HP manuals Comments (0)

    Related Manuals for HP 5500 Ei 5500 Si Switch Series Configuration Guide