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 701 to Favourites
    image text
    Enable zoom 
    							 12 
# Configure a default route on Switch A. 
 system-view 
[SwitchA] ip route-static 0.0.0.0 0.0.0.0 1.1.4.2 
# Configure two static routes on Switch B. 
 system-view 
[SwitchB] ip route-static 1.1.2.0 255.255.255.0 1.1.4.1 
[SwitchB] ip route-static 1.1.3.0 255.255.255.0 1.1.5.6 
# Configure a default route on Switch C. 
 system-view 
[SwitchC] ip route-static 0.0.0.0 0.0.0.0 1.1.5.5 
3. Configure the hosts: 
Configure the default gateways of hosts A, B, and C as 1.1.2.3,  1.1.6.1, and 1.1.3.1. (Details 
not shown.) 
4.  Display the configuration: 
# Display the IP routing table on Switch A. 
[SwitchA] display ip routing-table 
Routing Tables: Public 
         Destinations : 7       Routes : 7 
 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
 
0.0.0.0/0           Static 60   0            1.1.4.2         Vlan500 
1.1.2.0/24          Direct 0    0            1.1.2.3         Vlan300 
1.1.2.3/32          Direct 0    0            127.0.0.1       InLoop0 
1.1.4.0/30          Direct 0    0            1.1.4.1         Vlan500 
1.1.4.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 
# Display the IP routing table on Switch B. 
[SwitchB] display ip routing-table 
Routing Tables: Public 
         Destinations : 10       Routes : 10 
 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
 
1.1.2.0/24          Static 60   0            1.1.4.1         Vlan500 
1.1.3.0/24          Static 60   0            1.1.5.6         Vlan600 
1.1.4.0/30          Direct 0    0            1.1.4.2         Vlan500 
1.1.4.2/32          Direct 0    0            127.0.0.1       InLoop0 
1.1.5.4/30          Direct 0    0            1.1.5.5         Vlan600 
1.1.5.5/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 
1.1.6.0/24          Direct 0    0            1.1.6.1         Vlan100 
1.1.6.1/32          Direct 0    0            127.0.0.1       InLoop0 
# Use the ping  command on Host B to test the reachability of Host A (assuming Windows XP runs 
on the two hosts).
    Add page 702 to Favourites
    image text
    Enable zoom 
    							 13 
C:\Documents and Settings\Administrator>ping 1.1.2.2 
 
Pinging 1.1.2.2 with 32 bytes of data: 
 
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255 
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255 
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255 
Reply from 1.1.2.2: bytes=32 time=1ms TTL=255 
 
Ping statistics for 1.1.2.2: 
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
    Minimum = 1ms, Maximum = 1ms, Average = 1ms 
# Use the tracert command on Host B to test the reachability of Host A. 
C:\Documents and Settings\Administrator>tracert 1.1.2.2 
 
Tracing route to 1.1.2.2 over a maximum of 30 hops 
 
  1
    Add page 703 to Favourites
    image text
    Enable zoom 
    							 14 
# Configure a static route on Switch S. 
 system-view 
[SwitchS] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2 
[SwitchS] ip route-static 4.4.4.4 32 vlan-interface 100 12.12.12.2 prefe\
rence 65 
# Configure a static route on Switch D. 
 system-view 
[SwitchD] ip route-static 1.1.1.1 32 vlan-interface 200 13.13.13.1 
[SwitchD] ip route-static 1.1.1.1 32 vlan-interface 101 24.24.24.2 prefe\
rence 65 
# Configure a static route on Switch A. 
 system-view 
[SwitchA] ip route-static 4.4.4.4 32 vlan-interface 101 24.24.24.4 
[SwitchA] ip route-static 1.1.1.1 32 vlan-interface 100 12.12.12.1 
2. Configure static route FRR: 
# Configure Switch S.  
[SwitchS] bfd echo-source-ip 1.1.1.1 
[SwitchS] ip ip-prefix abc index 10 permit 4.4.4.4 32 
[SwitchS] route-policy frr permit node 10 
[SwitchS-route-policy] if-match ip-prefix abc 
[SwitchS-route-policy] apply fast-reroute backup-interface vlan-interfac\
e 100 
backup-nexthop 12.12.12.2 
[SwitchS-route-policy] quit 
[SwitchS] ip route-static fast-reroute route-policy frr 
# Configure Switch D.  
[SwitchD] bfd echo-source-ip 4.4.4.4 
[SwitchD] ip ip-prefix abc index 10 permit 1.1.1.1 32 
[SwitchD] route-policy frr permit node 10 
[SwitchD-route-policy] if-match ip-prefix abc 
[SwitchD-route-policy] apply fast-reroute backup-interface vlan-interfac\
e 101 
backup-nexthop 24.24.24.2 
[SwitchD-route-policy] quit 
[SwitchD] ip route-static fast-reroute route-policy frr 
3. Verify the configuration: 
# Display route 4.4.4.4/32 on Switch S to view the backup next hop information.  
[SwitchS] display ip routing-table 4.4.4.4 verbose 
Routing Table : Public 
Summary Count : 1 
 
  Destination: 4.4.4.4/32 
     Protocol: Static          Process ID: 0 
   Preference: 60                    Cost: 0 
 IpPrecedence:                    QosLcId: 
      NextHop: 13.13.13.2       Interface: vlan 200 
    BkNextHop: 12.12.12.2     BkInterface: vlan 100 
  RelyNextHop: 0.0.0.0          Neighbor : 0.0.0.0 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Active Adv             Age: 00h01m27s
    Add page 704 to Favourites
    image text
    Enable zoom 
    							 15 
          Tag: 0 
# Display route 1.1.1.1/32 on Switch D to view the backup next hop information.  
[SwitchD] display ip routing-table 1.1.1.1 verbose 
Routing Table : Public 
Summary Count : 1 
 
  Destination: 1.1.1.1/32 
     Protocol: Static          Process ID: 0 
   Preference: 60                    Cost: 0 
 IpPrecedence:                    QosLcId: 
      NextHop: 13.13.13.1       Interface: vlan 200 
    BkNextHop: 24.24.24.2     BkInterface: vlan 101 
  RelyNextHop: 0.0.0.0          Neighbor : 0.0.0.0 
    Tunnel ID: 0x0                  Label: NULL 
  BKTunnel ID: 0x0                BKLabel: NULL 
        State: Active Adv             Age: 00h01m27s 
          Tag: 0 
BFD for static routes configuration example (direct session) 
Network requirements 
As shown in Figure 4, configure static routes to subnet 120.1.1.0/24 on Switch A, static routes to subnet 
121.1.1. 0 / 2 4  o n  S w i t c h  B ,  a n d  s t a t i c  r o u t e s  t o  s u b n e t s  12 0 .1.1. 0 / 2 4  a n d  121.1.1. 0 / 2 4  o n  S w i t c h  C .   
Enable BFD so that when the link between Switch A and Switch B through the Layer 2 switch fails, BFD 
can detect the failure immediately and Switch A  and Switch B can communicate through Switch C. 
Figure 4  Network diagram 
 
Device Interface IP address Device Interface IP address 
Switch A  Vlan-int10  12.1.1.1/24 Switch B Vlan-int10 12.1.1.2/24 
 Vlan-int11 10.1.1.102/24   Vlan-int13 13.1.1.1/24 
Switch C  Vlan-int11  10.1.1.100/24    
 Vlan-int13 13.1.1.2/24     
Configuration procedure 
1. Configure IP addresses for the in terfaces. (Details not shown.) 
2. Configure BFD: 
# Configure static routes on Switch A and enabl e BFD control packet mode for the static route 
through the Layer 2 switch.
    Add page 705 to Favourites
    image text
    Enable zoom 
    							 16 
 system-view 
[SwitchA] interface vlan-interface10 
[SwitchA-vlan-interface10] bfd min-transmit-interval 500 
[SwitchA-vlan-interface10] bfd min-receive-interval 500 
[SwitchA-vlan-interface10] bfd detect-multiplier 9 
[SwitchA-vlan-interface10] quit 
[SwitchA] ip route-static 120.1.1.0 24 vlan-interface 10 12.1.1.2 bfd co\
ntrol-packet 
[SwitchA] ip route-static 120.1.1.0 24 vlan-interface 11 10.1.1.100 pref\
erence 65 
[SwitchA] quit 
# Configure static routes on Switch B and enable BFD control packet mode for the static route 
through the Layer 2 switch.  
 system-view 
[SwitchB] interface vlan-interface10 
[SwitchB-vlan-interface10] bfd min-transmit-interval 500 
[SwitchB-vlan-interface10] bfd min-receive-interval 500 
[SwitchB-vlan-interface10] bfd detect-multiplier 9 
[SwitchB-vlan-interface10]] quit 
[SwitchB] ip route-static 121.1.1.0 24 vlan-interface 10 12.1.1.1 bfd co\
ntrol-packet 
[SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 prefer\
ence 65 
[SwitchB] quit 
# Configure static routes on Switch C. 
 system-view 
[SwitchC] ip route-static 120.1.1.0 24 vlan-interface 13 13.1.1.1 
[SwitchC] ip route-static 121.1.1.0 24 vlan-interface 11 10.1.1.102 
3.  Verify the configuration: 
The following operations are performed on Switch  A. The operations on Switch B are similar.  
# Display BFD sessions on Router A. 
 display bfd session 
 
 Total Session Num: 1            Init Mode: Active 
 
 Session Working Under Ctrl Mode: 
 
 LD/RD         SourceAddr      DestAddr        State Holdtime Interface \
 4/7           12.1.1.1        12.1.1.2        Up    2000ms   Vlan10 
# Display static routes on Switch A.  
 display ip routing-table protocol static 
Public Routing Table : Static 
Summary Count : 2 
 
Static Routing table Status : < Active> 
Summary Count : 1 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 60   0            12.1.1.2        Vlan10 
 
Direct Routing table Status :  
Summary Count : 1
    Add page 706 to Favourites
    image text
    Enable zoom 
    							 17 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 65   0            10.1.1.100      Vlan11 
# Enable BFD debugging on Switch A. When the link between Switch A and Layer 2 switch fails, 
Switch A can detect the failure. 
 debugging bfd event 
 debugging bfd scm 
 terminal debugging 
%Jul 27 10:18:18:672 2007 SwitchA BFD/4/LOG:Sess[12.1.1.1/12.1.1.2, Vlan\
10,Ctrl], 
Sta: UP->DOWN, Diag: 1 
*Jul 27 10:18:18:672 2007 SwitchA BFD/7/EVENT:Send sess-down Msg, 
[Src:12.1.1.1,Dst:12.1.1.2, Vlan10,Ctrl], instance:0, protocol:STATIC 
*Jul 27 10:18:19:172 2007 SwitchA BFD/7/EVENT:Receive Delete-sess, 
[Src:12.1.1.1,Dst:12.1.1.2, Vlan10,Ctrl], Direct, Instance:0x0, Proto:ST\
ATIC 
*Jul 27 10:18:19:172 2007 SwitchA BFD/7/EVENT:Notify driver to stop rece\
iving bfd 
control packet 
# Display the static route information on Switch A again. Switch A communicates with Switch B 
over the static route passing Switch C now.  
 display ip routing-table protocol static 
Public Routing Table : Static 
Summary Count : 2 
Static Routing table Status : < Active> 
Summary Count : 1 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 65   0            10.1.1.100      Vlan11 
Static Routing table Status : < Inactive> 
Summary Count : 1 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 60   0            12.1.1.2        Vlan10 
BFD for static routes configuration example (indirect session) 
Network requirements 
As shown in Figure 5 , Switch A has a route to interface Loo pback1 (2.2.2.9/32) on Switch B, with 
outbound interface VLAN-interface 10. Switch B has a route to interface Loopback1 (1.1.1.9/32) on 
Switch A, with outbound interface VLAN-interface 12. Switch D has a route to 1.1.1.9/32, with outbound 
interface VLAN-interface 10, and a route to 2.2.2.9/ 32, with outbound interface VLAN-interface 12.  
Co n fig u re  s t a t ic  rou t es  t o  s ub n e t  12 0 .1.1.0 / 24  o n  Swi tch A ,  s t a t ic  ro u tes  t o  s u b n e t  121.1.1.0 / 24  o n  Swi t ch 
B, and static routes to subnets 120.1.1.0/24 and 121. 1.1.0/24 on both Switch C and Switch D. Enable BFD 
so that when the link between Switch A and Switch B through Switch D fails, BFD can detect the failure 
immediately and Switch A and Switch  B can communicate through Switch C.
    Add page 707 to Favourites
    image text
    Enable zoom 
    							 18 
Figure 5 Network diagram 
 
Device  Interface  IP address Device  Interface  IP address 
Switch A  Vlan-int10  12.1.1.1/24 Switch B Vlan-int12 11.1.1.1/24 
 Vlan-int11 10.1.1.102/24  Vlan-int13 13.1.1.1/24 
 Loop1 1.1.1.9/32   Loop1 2.2.2.9/32 
Switch C  Vlan-int11  10.1.1.100/24 Switch D Vlan-int10 12.1.1.2/24 
 Vlan-int13 13.1.1.2/24  Vlan-int12 11.1.1.2/24  
Configuration procedure 
1. Configure IP addresses for the in terfaces. (Details not shown.) 
2. Configure BFD: 
# Configure static routes on Switch A and enabl e BFD control packet mode for the static route 
through Switch D.  
 system-view 
[SwitchA] interface loopback 1 
[SwitchA-LoopBack1] bfd min-transmit-interval 500 
[SwitchA-LoopBack1] bfd min-receive-interval 500 
[SwitchA-LoopBack1] bfd detect-multiplier 9 
[SwitchA-LoopBack1] quit 
[SwitchA] ip route-static 120.1.1.0 24 2.2.2.9 bfd control-packet bfd-so\
urce 1.1.1.9 
[SwitchA] ip route-static 120.1.1.0 24 vlan-interface 11 10.1.1.100 pref\
erence 65 
[SwitchA] quit 
# Configure static routes on Switch B and enabl e BFD control packet mode for the static route 
through Switch D. 
 system-view 
[SwitchB] interface loopback 1 
[SwitchB-LoopBack1] bfd min-transmit-interval 500 
[SwitchB-LoopBack1] bfd min-receive-interval 500 
[SwitchB-LoopBack1] bfd detect-multiplier 9 
[SwitchB-LoopBack1] quit 
[SwitchB] ip route-static 121.1.1.0 24 1.1.1.9 bfd control-packet bfd-so\
urce 2.2.2.9 
[SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 prefer\
ence 65 
[SwitchB] quit 
# Configure static routes on Switch C. 
 system-view 
[SwitchC] ip route-static 120.1.1.0 24 vlan-interface 13 13.1.1.1 
Switch A Switch B
Switch C
BFD
Vlan-int10
Vlan-int1
1
Vlan-int11 Vlan-int13
Vlan-int1
3
Vlan-int10
121.1.1.0/24
120.1.1.0/24
Switch D
Vlan-int12
Vlan-int12
Loop1
1.1.1.9/32
Loop1
2.2.2.9/32
    Add page 708 to Favourites
    image text
    Enable zoom 
    							 19 
[SwitchC] ip route-static 121.1.1.0 24 vlan-interface 11 10.1.1.102 
# Configure static routes on Switch D. 
 system-view 
[SwitchD] ip route-static 120.1.1.0 24 vlan-interface 12 11.1.1.1 
[SwitchD] ip route-static 121.1.1.0 24 vlan-interface 10 12.1.1.1 
3. Verify the configuration: 
The following operations are performed on Switch  A. The operations on Switch B are similar and 
not shown. 
# Display BFD sessions on Switch A. 
 display bfd session 
 
 Total Session Num: 1            Init Mode: Active 
 
 Session Working Under Ctrl Mode: 
 
 LD/RD         SourceAddr      DestAddr        State Holdtime Interface \
 4/7           1.1.1.9         2.2.2.9         Up    2000ms   Loop1 
# Display the static route information on Switch A.  
 display ip routing-table protocol static 
Public Routing Table : Static 
Summary Count : 2 
 
Static Routing table Status : < Active> 
Summary Count : 1 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 60   0            2.2.2.9         Vlan10 
 
Static Routing table Status :  
Summary Count : 1 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 65   0            10.1.1.100      Vlan11 
# Enable BFD debugging on Switch A. When the link  between Switch A and Switch D fails, Switch 
A can detect the failure. 
 debugging bfd event 
 debugging bfd scm 
 terminal debugging 
%Oct 10 10:18:18:672 2010 SwitchA BFD/4/LOG:Sess[1.1.1.9/2.2.2.9, Loop1,Ctrl], Sta: 
UP->DOWN, Diag: 1 
* Oct 10 10:18:18:672 2010 SwitchA BFD/7/EVENT:Send sess-down Msg, 
[Src:1.1.1.9,Dst:2.2.2.9, Loop1,Ctrl], instance:0, protocol:STATIC 
# Display the static route information on Switch A again. Switch A communicates with Switch B 
over the static route passing Switch C now.  
 display ip routing-table protocol static 
Public Routing Table : Static 
Summary Count : 2 
Static Routing table Status : < Active> 
Summary Count : 1
    Add page 709 to Favourites
    image text
    Enable zoom 
    							 20 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 65   0            10.1.1.100      Vlan11 
Static Routing table Status : < Inactive> 
Summary Count : 1 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
120.1.1.0/24        Static 60   0            2.2.2.9
    Add page 710 to Favourites
    image text
    Enable zoom 
    							 21 
Configuring RIP 
Hardware compatibility 
The HP 5500 SI Switch Series does not support VPN and BFD related parameters or FRR. 
Overview 
RIP is a simple interior gateway protocol (IGP), mainly used in small-sized networks, such as academic 
networks and simple LANs. It is not applicable to complex networks. 
RIP has been widely used because it is easy to implement, configure, and maintain. 
The term router in this chapter refers to both routers and Layer 3 switches. 
Understanding RIP 
RIP is a distance vector (D-V) routing protocol, using UDP packets for exchanging information through 
port 520. 
RIP uses a hop count to measure the distance to a dest ination. The hop count from a router to a directly 
connected network is 0. The hop count from a router to a directly connected router is 1. To limit 
convergence time, the RIP metric value is in the range of 0 to 15. A metric value of 16 (or greater) is 
considered infinite, which means the destination network is unreachable. Because of this, RIP is not 
suitable for large-sized networks. 
RIP prevents routing loops by  implementing the split horizon and poison reverse functions. 
RIP routing table 
A RIP router has a routing table containing routing entries of all reachable destinations, and each routing 
entry contains the following elements: 
•  Destination address —IP address of a host or a network. 
•   Next hop —IP address of the adjacent routers interface to reach the destination. 
•   Egress interface —Packet outgoing interface. 
•   Metric —Cost from the local router to the destination. 
•   Route time —Time elapsed since the last routing entry updat e. The time is reset to 0 every time the 
routing entry is updated. 
•   Route tag —Identifies a route. Route tags are used in a  routing policy to flexibly control routes. For 
more information about routing policy, see  Configuring routing policies. 
RIP timers 
RIP employs the following timers: 
•   Update timer —Defines the interval  between routing updates. 
•   Timeout timer —Defines the route aging time . If no update for a route is received within the aging 
time, the metric of the route is set to 16 in the routing table.
    All HP manuals Comments (0)

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