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 721 to Favourites
    image text
    Enable zoom 
    							 32 
Step Command Remarks 
3.  Configure a default metric for 
redistributed routes.  default cost 
value  Optional. 
The default metric of a redistributed 
route is 0. 
4.
  Redistribute routes from 
another protocol.  import-route 
protocol [  process-id  
|  all-processes  | allow-ibgp  ] [ cost 
cost  |  route-policy 
route-policy-name  | tag  tag ] *   By default, no redistribution is 
configured. 
 
Tuning and optimizing RIP networks 
Before you tune and optimize RIP networks, complete the following tasks: 
•
  Configure IP addresses for interfaces, and make sure that all neighboring nodes can reach each 
other. 
•   Configure RIP basic functions. 
Configuring RIP timers 
You can change the RIP network convergence speed by adjusting RIP timers. Based on network 
performance, make RIP timers of RIP routers identical to each other to avoid unnecessary traffic or route 
oscillation. 
To  c o n fig u re  RI P  t i m e rs : 
 
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 values for RIP 
timers.  timers 
{ garbage-collect 
garbage-collect-value |  suppress  
suppress-value |  timeout 
timeout-value  | update  
update-value  } *  Optional. 
The default update timer, timeout 
timer, suppress timer, and 
garbage-collect timer are 30s, 
180s, 120s and 120s 
respectively. 
 
Configuring split horizon and poison reverse 
The split horizon and poison reverse functions can avoi
d routing loops. If both split horizon and poison 
reverse are configured, only the poison reverse function takes effect. 
Enabling split horizon 
The split horizon function disables an interface from  sending routes received from the interface to prevent 
routing loops betwee n adjacent routers. 
To enable split horizon:
    Add page 722 to Favourites
    image text
    Enable zoom 
    							 33 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface
 interface-type 
interface-number  N/A 
3.
  Enable split horizon. 
rip split-horizon  Optional. 
Enabled by default. 
 
Enabling poison reverse 
The poison reverse function allows an interface to advertise the routes received from it, but the metric of 
these routes is set to 16, making them unreachable. This can avoid routing loops between neighbors.  
To enable poison reverse: 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Enter interface view.  interface
 interface-type 
interface-number  N/A 
3.
  Enable poison reverse. 
rip poison-reverse  Disabled by default. 
 
Configuring the maximum number of ECMP routes 
Perform this task to implement load sharing over ECMP routes.  
To configure the maximum number of ECMP routes: 
 
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 maximum 
number of ECMP routes.  maximum load-balancing
 number Optional. 
8 by default. 
 
Enabling zero field check on incoming RIPv1 messages 
Some fields in the RIPv1 message must be zero. These fields are called zero fields. You can enable zero 
field check on received RIPv1 messages. If such a fiel d contains a non-zero value, the RIPv1 message will 
not be processed. If you are certain that all messages  are trustworthy, then disable zero field check to 
save CPU resources. 
This feature does not apply to RIPv2 packets, because they have no zero fields.  
To enable zero field check on incoming RIPv1 messages: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A
    Add page 723 to Favourites
    image text
    Enable zoom 
    							 34 
Step Command Remarks 
2.  Enter RIP view.  rip
 [ process-id  ] [ vpn-instance  
vpn-instance-name  ]  N/A 
3.
  Enable zero field check on 
received RIPv1 messages.  checkzero  Optional. 
Enabled by default. 
 
Enabling source IP address check on incoming RIP updates 
You can enable source IP address check on incoming RIP updates.  
For a message received on an Ethernet interface, RI
P compares the source IP address of the message with 
the IP address of the interface. If they are not in th e same network segment, RIP discards the message.  
 
 IMPORTANT: 
Disable the source IP address check feature if
 the RIP neighbor is not directly connected. 
 
To enable source IP address check on incoming RIP updates:  
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 source IP address 
check on incoming RIP 
messages.  validate-source-address 
Optional. 
Enabled by default.
 
 
Configuring RIPv2 message authentication 
In a network requiring high security, configure this task to implement RIPv2 message validity check and 
authentication. This feature does not apply to RIPv1 because RIPv1 does not support authentication. 
Although you can specify an authentication mode for RIPv1 in interface view, the configuration does not 
take effect. 
RIPv2 supports simple authentication and MD5 authentication. 
To configure RIPv2 message authentication: 
 
Step Command 
1.  Enter system view. 
system-view 
2.  Enter interface view. 
interface interface-type interface-number 
3.   Configure RIPv2 
authentication.  rip authentication-mode 
{ md5  { rfc2082  [ cipher ] key-string  key-id  |  
rfc2453  [ cipher ] key-string  } |  simple  [ cipher  ] password  } 
 
Specifying a RIP neighbor 
Usually, RIP sends messages to broadcast or multic ast addresses. On non-broadcast or multicast links, 
you must manually specify RIP neighbors.
    Add page 724 to Favourites
    image text
    Enable zoom 
    							 35 
Follow these guidelines when you specify a RIP neighbor: 
•  Do not use the  peer ip-address  command when the neighbor is directly connected because the 
neighbor may receive both the unicast and multicast (or broadcast) of the same routing information. 
•   If a specified neighbor is not directly connected, then disable the source address check on incoming 
updates. 
To specify a RIP neighbor: 
 
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 RIP neighbor. 
peer ip-address  N/A 
4.  Disable source address check 
on incoming RIP updates.  undo validate-source-address 
Not disabled by default. 
 
Configuring RIP-to-MIB binding 
This task allows you to enable a specific RIP process to receive SNMP requests.  
To bind RIP to MIB: 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Bind RIP to MIB. 
rip mib-binding process-id   Optional. 
By default, MIB is bound to RIP 
process 1. 
 
Configuring the RIP packet sending rate 
RIP periodically sends routing information in RIP packets to RIP neighbors.  
Sending large numbers of RIP packets at the same time may affect device performance and consume 
large network bandwidth. To solve this problem, specify the maximum number of RIP packets that can be 
sent at the specified interval.  
To configure the RIP packet sending rate: 
 
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  ]  N/A 
3.
  Configure the maximum 
number of RIP packets that 
can be sent at the specified 
interval.  output-delay 
time count  count  Optional. 
By default, an interface sends up to 
three RIP packets every 20 
milliseconds.
    Add page 725 to Favourites
    image text
    Enable zoom 
    							 36 
Configuring RIP FRR 
When a link in a RIP network fails, the traffic is interrupted until RIP completes routing convergence based 
on the new network topology.  
You can enable RIP fast reroute (FRR) to reduce traffic recovery time.  
Figure 9 Network diagram for RIP FRR 
 
 
In Figure 9 , after you enable FRR on Router B, RIP designates a backup next hop using a routing policy 
when a network failure is detected. Packets are directed  to the backup next hop to reduce traffic recovery 
time. At the same time, RIP calculates the shortest  path based on the new network topology, and forwards 
packets over the path after network convergence.  
Configuration prerequisites 
You need to specify a next hop by using the  apply fast-reroute backup-interface command in a routing 
policy and reference the routing policy with RIP  FRR. For more information about routing policy 
configuration, see  Configuring routing policies . 
Configuration guidelines 
•  RIP FRR is only effective for non-recursive RIP routes (that are learned from directly connected 
neighbors). 
•   Do not use RIP FRR and BFD (for RIP) at the same  time; otherwise, RIP FRR may fail to take effect. 
Configuration procedure 
To  c o n fig u re  RI P  F R R :    
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure the source address 
of echo packets.  bfd echo-source-ip 
ip-address Not configured by default. 
3.  Enter RIP view.   rip
 [ process-id  ] [ vpn-instance 
vpn-instance-name  ]
  N/A
 
4.  Enable RIP FRR and reference 
a routing policy to designate 
a backup next hop.  fast-reroute route-policy 
route-policy-name
  Disabled by default. 
 
Configuring BFD for RIP 
BFD for RIP provides the following link detection modes:
    Add page 726 to Favourites
    image text
    Enable zoom 
    							 37 
•  Single-hop detection in BFD echo packet mode for  a directly connected neighbor. In this mode, a 
BFD session is established only when the neighbor has route information to send. 
•   Bidirectional detection in BFD control packet mode  for an indirectly connected neighbor. In this 
mode, a BFD session is established only when both  ends have routes to send and BFD is enabled 
on the receiving interface. 
For more information about BFD, see  High Availability Configuration Guide .  
Single-hop detection in BFD echo packet mode 
To configure BFD for RIP (single-hop detection in BFD echo packet mode):  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure the source IP 
address of BFD echo packets.  bfd echo-source-ip 
ip-address By default, no source IP address is 
configured for BFD echo packets. 
3.
  Enter interface view.  interface
 interface-type 
interface-number   N/A 
4.
  Enable BFD on the RIP 
interface.  rip bfd enable 
Disabled by default. 
 
Bidirectional detection in BFD control packet mode 
This feature only works for RIP neighbors that are directly connected (one hop away from each other). 
To configure BFD for RIP (bidirectional detection in BFD control packet mode): 
 
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, RIP is disabled. 
3.
  Specify a RIP neighbor. 
peer ip-address   By default, RIP does not unicast 
updates to any peer. 
4.
  Enter interface view.  interface
 interface-type 
interface-number   N/A 
5.
  Enable BFD on the RIP 
interface.  rip bfd enable 
Disabled by default. 
 
 NOTE: 
Because the  undo peer command does not remove the neighbor relationship at once, executing the 
command cannot bring down the BFD session at once.  
 
Displaying and maintaining RIP
    Add page 727 to Favourites
    image text
    Enable zoom 
    							 38 
Task Command Remarks 
Display RIP current status and 
configuration information. display rip
 [ process-id  | 
vpn-instance  vpn-instance-name  ] 
[ |  { begin |  exclude | include } 
regular-expression  ]   Available in any view 
Display all active routes in RIP 
database.  display rip process-id 
database [ | 
{  begin |  exclude | include  } 
regular-expression  ]   Available in any view
 
Display RIP interface information.  display rip process-id
 interface 
[  interface-type interface-number  ] 
[ |  { begin |  exclude | include } 
regular-expression  ]   Available in any view
 
Display routing information about 
a specified RIP process.  display rip process-id
 route 
[  ip-address  { mask | mask-length  } 
|  peer  ip-address |  statistics ] [ | 
{  begin |  exclude | include  } 
regular-expression  ]  Available in any view
 
Reset a RIP process.  reset rip process-id process  Available in user view  
Clear the statistics of a RIP process.  reset rip process-id statistics Available in user view 
 
RIP configuration examples 
Configuring RIP version 
Network requirements 
As shown in Figure 10, ena ble RIPv2 on all interfaces on Switch A and Switch B. 
Figure 10  Network diagram 
 
 
Configuration procedure 
1. Configure an IP address for each  interface. (Details not shown.) 
2. Configure basic RIP functions: 
# Configure Switch A. 
[SwitchA] rip 
[SwitchA-rip-1] network 192.168.1.0 
[SwitchA-rip-1] network 172.16.0.0 
[SwitchA-rip-1] network 172.17.0.0 
# Configure Switch B. 
[SwitchB] rip 
[SwitchB-rip-1] network 192.168.1.0
    Add page 728 to Favourites
    image text
    Enable zoom 
    							 39 
[SwitchB-rip-1] network 10.0.0.0 
# Display the RIP routing table of Switch A. 
[SwitchA] display rip 1 route 
 Route Flags: R - RIP, T - TRIP 
              P - Permanent, A - Aging, S - Suppressed, G - Garbage-coll\
ect 
 -----------------------------------------------------------------------\
----- 
 Peer 192.168.1.2  on Vlan-interface100 
      Destination/Mask        Nexthop     Cost    Tag   Flags   Sec 
         10.0.0.0/8        192.168.1.2      1       0    RA      11 
The output shows that RIPv1 uses a natural mask. 
3. Configure RIP version: 
# Configure RIPv2 on Switch A. 
[SwitchA] rip 
[SwitchA-rip-1] version 2 
[SwitchA-rip-1] undo summary 
# Configure RIPv2 on Switch B. 
[SwitchB] rip 
[SwitchB-rip-1] version 2 
[SwitchB-rip-1] undo summary 
# Display the RIP routing table on Switch A. 
[SwitchA] display rip 1 route 
 Route Flags: R - RIP, T - TRIP 
              P - Permanent, A - Aging, S - Suppressed, G - Garbage-coll\
ect 
 -----------------------------------------------------------------------\
----- 
 Peer 192.168.1.2  on Vlan-interface100 
      Destination/Mask        Nexthop     Cost    Tag   Flags   Sec 
         10.0.0.0/8        192.168.1.2      1       0    RA      50 
         10.2.1.0/24       192.168.1.2      1       0    RA      16 
         10.1.1.0/24       192.168.1.2      1       0    RA      16 
The output shows that RIPv2 uses classless subnet mask.  
  NOTE: 
RIPv1 routing information has a long aging time, so it will exist until it a
ges out after RIPv2 is configured. 
Configuring RIP route redistribution 
Network requirements 
In the following figure, two RIP processes are running on Switch B, which communicates with Switch A 
through RIP 100 and with Switch C through RIP 200. 
Configure route redistribution on Switch B to make RI P 200 redistribute direct routes and routes from RIP 
100. Switch C can then learn routes destined for 10.2.1.0/24 and 1 1.1.1. 0 / 2 4 ,  a n d  S w i t c h  A  c a n n o t  l e a r n  
routes destined for 12.3.1.0/24 and 16.4.1.0/24. 
Configu re  a fi lteri ng  pol icy on Swi tch B  to  fi l ter  out the  route  10 .2.1.1 /24  from RI P  100 , mak i ng  the route  
not advertised to Switch C.
    Add page 729 to Favourites
    image text
    Enable zoom 
    							 40 
Figure 11 Network diagram 
 
 
Configuration procedure 
1. Configure an IP address for each  interface. (Details not shown.) 
2. Configure basic RIP functions: 
# Enable RIP 100 and specify RIP version 2 on Switch A. 
 system-view 
[SwitchA] rip 100 
[SwitchA-rip-100] network 10.0.0.0 
[SwitchA-rip-100] network 11.0.0.0 
[SwitchA-rip-100] version 2 
[SwitchA-rip-100] undo summary 
[SwitchA-rip-100] quit 
# Enable RIP 100 and RIP 200 and specify RIP version 2 on Switch B. 
 system-view 
[SwitchB] rip 100 
[SwitchB-rip-100] network 11.0.0.0 
[SwitchB-rip-100] version 2 
[SwitchB-rip-100] undo summary 
[SwitchB-rip-100] quit 
[SwitchB] rip 200 
[SwitchB-rip-200] network 12.0.0.0 
[SwitchB-rip-200] version 2 
[SwitchB-rip-200] undo summary 
[SwitchB-rip-200] quit 
# Enable RIP 200 and specify RIP version 2 on Switch C. 
 system-view 
[SwitchC] rip 200 
[SwitchC-rip-200] network 12.0.0.0 
[SwitchC-rip-200] network 16.0.0.0 
[SwitchC-rip-200] version 2 
[SwitchC-rip-200] undo summary 
# Display the routing table of Switch C. 
[SwitchC] display ip routing-table 
Routing Tables: Public 
         Destinations : 6        Routes : 6 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
12.3.1.0/24         Direct 0    0            12.3.1.2        Vlan200 
12.3.1.2/32         Direct 0    0            127.0.0.1       InLoop0 
16.4.1.0/24         Direct 0    0            16.4.1.1        Vlan400
    Add page 730 to Favourites
    image text
    Enable zoom 
    							 41 
16.4.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0 
3.  Configure route redistribution: 
# On Switch B, configure RIP 200 to redistribute direct routes and routes from RIP 100. 
[SwitchB] rip 200 
[SwitchB-rip-200] import-route rip 100 
[SwitchB-rip-200] import-route direct 
[SwitchB-rip-200] quit 
# Display the routing table of Switch C. 
[SwitchC] display ip routing-table 
Routing Tables: Public 
         Destinations : 8        Routes : 8 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
10.2.1.0/24         RIP    100  1            12.3.1.1        Vlan200 
11.1.1.0/24         RIP    100  1            12.3.1.1        Vlan200 
12.3.1.0/24         Direct 0    0            12.3.1.2        Vlan200 
12.3.1.2/32         Direct 0    0            127.0.0.1       InLoop0 
16.4.1.0/24         Direct 0    0            16.4.1.1        Vlan400 
16.4.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0 
4.  Configure an filtering policy  to filter redistributed routes: 
# Define ACL 2000 and reference it to a filtering policy to filter routes redistributed from RIP 100 
on Switch B, making the route not advertised to Switch C. 
[SwitchB] acl number 2000 
[SwitchB-acl-basic-2000] rule deny source 10.2.1.1 0.0.0.255 
[SwitchB-acl-basic-2000] rule permit 
[SwitchB-acl-basic-2000] quit 
[SwitchB] rip 200 
[SwitchB-rip-200] filter-policy 2000 export rip 100 
# Display the routing table of Switch C. 
[SwitchC] display ip routing-table 
Routing Tables: Public 
         Destinations : 7        Routes : 7 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
11.1.1.0/24         RIP    100  1            12.3.1.1        Vlan200 
12.3.1.0/24         Direct 0    0            12.3.1.2        Vlan200 
12.3.1.2/32         Direct 0    0            127.0.0.1       InLoop0 
16.4.1.0/24         Direct 0    0            16.4.1.1        Vlan400 
16.4.1.1/32         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.0/8         Direct 0    0            127.0.0.1       InLoop0 
127.0.0.1/32        Direct 0    0            127.0.0.1       InLoop0
    All HP manuals Comments (0)

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