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 941 to Favourites
    image text
    Enable zoom 
    							 252 
Figure 98 Network diagram 
 
Device  Interface  IP address  Device  Interface  IP address 
Switch A  Vlan-int100  3.0.1.1/24 Switch C Vlan-int101 3.0.2.2/24 
 Vlan-int200 2.0.1.1/24  Vlan-int201 2.0.2.2/24 
Switch B  Vlan-int100  3.0.1.2/24  Switch D  Vlan-int200  2.0.1.2/24 
 Vlan-int101 3.0.2.1/24  Vlan-int201 2.0.2.1/24  
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure OSPF to make sure that Switch A and Sw itch C are reachable to each other. (Details not 
shown.) 
3.  Configure BGP on Switch A:  
# Establish two IBGP connections be tween Switch A and Switch C.  
 system-view 
[SwitchA] bgp 100 
[SwitchA-bgp] peer 3.0.2.2 as-number 200 
[SwitchA-bgp] peer 2.0.2.2 as-number 200 
[SwitchA-bgp] quit 
# When the two links between Switch A and Switch  C are both up, Switch C adopts the link Switch 
ASwitch BSwitch C to exchange packets  with network 1.1.1.0/24. (Set a higher MED 
value for route 1.1.1.0/24 sent  to peer 2.0.2.2 on Switch A.) 
{ Create ACL 2000 to permit 1.1.1.0/24 to pass.  
[SwitchA] acl number 2000 
[SwitchA-acl-basic-2000] rule permit source 1.1.1.0 24 
[SwitchA-acl-basic-2000] quit 
{ Create two route policies, apply_med_50  and apply_med_100 . Policy apply_med_50  sets the 
M E D  f o r  r o u t e  1.1.1. 0 / 2 4  t o  5 0 .  P o l i c y   apply_med_100 sets that to 100.  
[SwitchA] route-policy apply_med_50 permit node 10 
[SwitchA-route-policy] if-match acl 2000 
[SwitchA-route-policy] apply cost 50 
[SwitchA-route-policy] quit
    Add page 942 to Favourites
    image text
    Enable zoom 
    							 253 
[SwitchA] route-policy apply_med_100 permit node 10 
[SwitchA-route-policy] if-match acl 2000 
[SwitchA-route-policy] apply cost 100 
[SwitchA-route-policy] quit 
{ Apply routing policy apply_med_50  to routes outgoing to peer 3.0.2.2, and apply routing 
policy  apply_med_100  to routes outgoing to peer 2.0.2.2.  
[SwitchA] bgp 100 
[SwitchA-bgp] peer 3.0.2.2 route-policy apply_med_50 export 
[SwitchA-bgp] peer 2.0.2.2 route-policy apply_med_100 export 
# Configure BFD over the link to peer 3.0.2.2 so that when the link Switch ASwitch 
BSwitch C fails, BFD can quickly detect the failure and notify it to BGP, and then the link 
Switch ASwitch DSwitch C takes effect immediately.  
[SwitchA-bgp] peer 3.0.2.2 bfd 
[SwitchA-bgp] quit 
4. Configure BGP on Switch C:  
 system-view 
[SwitchC] bgp 100 
[SwitchC-bgp] peer 3.0.1.1 as-number 200 
[SwitchC-bgp] peer 3.0.1.1 bfd 
[SwitchC-bgp] peer 2.0.1.1 as-number 200 
[SwitchC-bgp] quit 
5. Configure BFD parameters (you can us e default BFD parameters instead): 
# Configure Switch A.  
[SwitchA] bfd session init-mode active 
[SwitchA] interface vlan-interface 100 
{  Configure the minimum interval for transmitting BFD control packets as 500 milliseconds.  
[SwitchA-Vlan-interface100] bfd min-transmit-interval 500 
{ Configure the minimum interval for receiving BFD control packets as 500 milliseconds.  
[SwitchA-Vlan-interface100] bfd min-receive-interval 500 
{ Configure the detect multiplier as 7.  
[SwitchA-Vlan-interface100] bfd detect-multiplier 7 
{ Configure the BFD authentication mode as plain-text authentication, and set the authentication 
key to  ibgpbfd .  
[SwitchA-Vlan-interface100] bfd authentication-mode simple 1 ibgpbfd 
[SwitchA-Vlan-interface100] quit 
# Configure Switch C.  
[SwitchC] bfd session init-mode active 
[SwitchC] interface vlan-interface 101 
[SwitchC-Vlan-interface101] bfd min-transmit-interval 500 
[SwitchC-Vlan-interface101] bfd min-receive-interval 500 
[SwitchC-Vlan-interface101] bfd detect-multiplier 7 
[SwitchC-Vlan-interface101] bfd authentication-mode simple 1 ibgpbfd 
[SwitchC-Vlan-interface101] return 
6. Verify the configuration: 
The following operations are made on Switch C. Op erations on Switch A are similar. (Details not 
shown.)
    Add page 943 to Favourites
    image text
    Enable zoom 
    							 254 
# Display detailed BFD session information.  
 display bfd session verbose 
 
 Total Session Num: 1            Init Mode: Active 
 
 IP Session Working Under Ctrl Mode: 
 
     Local Discr: 17                  Remote Discr: 13 
       Source IP: 3.0.2.2           Destination IP:  3.0.1.1 
   Session State: Up                     Interface: Vlan-interface101 
 Min Trans Inter: 500ms            Act Trans Inter: 500ms 
  Min Recv Inter: 500ms           Act Detect Inter: 3000ms 
    Recv Pkt Num: 57                  Send Pkt Num: 53 
       Hold Time: 2200ms              Connect Type: Indirect 
  Running Up for: 00:00:06               Auth mode: Simple 
        Protocol: BGP6 
       Diag Info: No Diagnostic 
The output shows that a BFD session is established between Switch A’s  VLAN-interface 100 and 
Switch C’s VLAN-interface 101 and that BFD runs properly.  
# Display BGP peer information on Switch C, an d you can see that Switch C has established two 
BGP neighborships with Switch A.  
 display bgp peer 
 
 BGP local router ID : 1.1.1.1 
 Local AS number : 200 
 Total number of peers : 2                 Peers in established state : \
2 
 
  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  Sta\
te 
 
  2.0.1.1                200        7       10    0       0 00:01:05 Est\
ablished 
  3.0.1.1                200        7       10    0       0 00:01:34 Est\
ablished 
# Display route 1.1.1.0/24 on Switch C, an d you can see that Switch A and Switch C 
communicate through Switch B.  
 display ip routing-table 1.1.1.0 24 verbose 
Routing Table : Public 
Summary Count : 2 
 
  Destination: 1.1.1.0/24 
     Protocol: BGP             Process ID: 0 
   Preference: 0                     Cost: 50 
      NextHop: 3.0.1.1          Interface: Vlan-interface101 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 3.0.2.1          Neighbor : 3.0.1.1 
    Tunnel ID: 0x0                  Label: NULL 
        State: Active Adv             Age: 00h08m54s 
          Tag: 0 
 
  Destination: 1.1.1.0/24
    Add page 944 to Favourites
    image text
    Enable zoom 
    							 255 
     Protocol: BGP             Process ID: 0 
   Preference: 0                     Cost: 100 
      NextHop: 2.0.1.1          Interface: Vlan-interface201 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 2.0.2.1          Neighbor : 2.0.1.1 
    Tunnel ID: 0x0                  Label: NULL 
        State: Invalid Adv             Age: 00h08m54s 
          Tag: 0 
The output shows that Switch C has two routes to reach network 1.1.1.0/24: Switch CSwitch 
BSwitch A, which is the active route; Switch CSwitch DSwitch A, which is the 
backup route.  
# Enable BFD debugging on Switch C.  
 debugging bfd scm 
 debugging bfd event 
 debugging bgp bfd 
 terminal monitor 
 terminal debugging 
# The following debugging informat ion shows that: when the link between Switch A and Switch B 
fails, Switch C can quickly detect the link failure.  
%Nov  5 11:42:24:172 2009 SwitchC BFD/5/BFD_CHANGE_FSM: Sess[3.0.2.2/3.0\
.1.1, 
13/17,VLAN101,Ctrl], Sta: UP->DOWN, Diag: 1 
%Nov  5 11:42:24:172 2009 SwitchC BGP/5/BGP_STATE_CHANGED:  3.0.1.1 state is changed 
from ESTABLISHED to IDLE. 
*Nov  5 11:42:24:187 2009 SwitchC RM/6/RMDEBUG: BGP_BFD: Recv BFD DOWN msg, Src IP 
3.0.2.2, Dst IP  3.0.1.1, Instance ID 0. 
*Nov  5 11:42:24:187 2009 SwitchC RM/6/RMDEBUG: BGP_BFD: Reset BGP session  3.0.1.1 
for BFD session down. 
*Nov  5 11:42:24:187 2009 SwitchC RM/6/RMDEBUG: BGP_BFD: Send DELETE msg\
 to BFD, 
Connection type DIRECT, Src IP 3.0.2.2, Dst IP  3.0.1.1, Instance ID 0. \
# Display route 1.1.1.0/24 on Switch C, an d you can see that Switch A and Switch C 
communicate through Switch D.  
 display ip routing-table 1.1.1.0 24 verbose 
Routing Table : Public 
Summary Count : 1 
 
  Destination: 1.1.1.0/24 
     Protocol: BGP             Process ID: 0 
   Preference: 0                     Cost: 100 
      NextHop: 2.0.1.1          Interface: Vlan-interface201 
    BkNextHop: 0.0.0.0        BkInterface: 
  RelyNextHop: 2.0.2.1          Neighbor : 2.0.1.1 
    Tunnel ID: 0x0                  Label: NULL 
        State: Active Adv             Age: 00h09m54s 
          Tag: 0 
The output shows that Switch C has one route Switch CSwitch DSwitch A to reach 
network 1.1.1.0/24.
    Add page 945 to Favourites
    image text
    Enable zoom 
    							 256 
Troubleshooting BGP 
BGP peer relationship not established 
Symptom 
Display BGP peer information by using the display bgp peer command. The state of the connection to a 
peer cannot become  established.  
Analysis 
To become BGP peers, any two routers must establish a TCP session using port 179 and exchange Open 
messages successfully. 
Solution 
1. Use the  display current-configuration  command to check that the peer’s AS number is correct. 
2. Use the  display bgp peer command  to check that the peer’s IP address is correct. 
3. If a loopback interface is used, check that  the loopback interface is specified with the  peer 
connect-interface  command. 
4. If the peer is a non-direct EBGP peer, check that the  peer ebgp-max-hop command is configured. 
5. Check that a valid route to the peer is available. 
6. Use the  ping command to check the connectivity to the peer. 
7. Use the  display tcp status  command to check the TCP connection. 
8. Check whether an ACL disabling TCP port 179 is configured.
    Add page 946 to Favourites
    image text
    Enable zoom 
    							 257 
Configuring IPv6 static routing 
Hardware compatibility 
The HP 5500 SI Switch Series does not support VPN-related parameters.  
Overview 
Static routes are manually configured. They work well in simple networks. Proper configuration and use 
can improve network performance and ensure enough bandwidth for important applications. 
However, static routes also have limitations. An y topology changes require manual configuration and 
modification to the relevant static routes. 
The term router in this chapter refers to both routers and Layer 3 switches. 
IPv6 static routes features 
Similar to IPv4 static routes, IPv6 static routes  work well in simple IPv6 network environments. 
Their major difference lies in the destination and  next hop addresses. IPv6 static routes use IPv6 
addresses, whereas IPv4 static routes use IPv4 addresses.  
Default IPv6 route 
An IPv6 static route with a destination prefix of ::/0   is a default IPv6 route. The default route is used to 
forward packets that match no specific routes in the routing table.  
Configuring an IPv6 static route 
In small IPv6 networks, IPv6 static routes can be used to forward packets. In comparison to dynamic 
routes, it helps to save network bandwidth. 
Before you configure an IPv6 static route, complete the following tasks: 
•   Configure parameters for the related interfaces.  
•   Configure link layer attributes for the related interfaces. 
•   Enable IPv6 packet forwarding. 
•   Make sure that the neighboring nodes can reach each other. 
To configure an IPv6 static route: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A
    Add page 947 to Favourites
    image text
    Enable zoom 
    							 258 
Step Command Remarks 
2.  Configure an IPv6 static route.  
• Approach 1:  
ipv6 route-static i pv6-address prefix-length  
{  interface-type interface-number  
[ next-hop-address  ] | next-hop-address  | 
vpn-instance  d-vpn-instance-name 
nexthop-address  } [ preference 
preference-value  ] 
• Approach 2: 
ipv6 route-static  vpn-instance 
s-vpn-instance-name & ipv6-address 
prefix-length  { interface-type 
interface-number  [ next-hop-address  ] | 
nexthop-address  [ public ] | vpn-instance  
d-vpn-instance-name nexthop-address  } 
[ preference  preference-value  ]  Use either approach. 
 
The default 
preference of IPv6 
static routes is 60. 
 
 
NOTE: 
If you specify a broadcast interface, such as an Ethe rnet interface or a VLAN interface, as the output 
interface for a static route, you must specify the next hop address. 
 
Displaying and maintaining IPv6 static routes 
 
Task Command Remarks 
Display IPv6 static route 
information.  display ipv6 routing-table
 protocol  
static  [ inactive |  verbose ] [ | 
{  begin |  exclude | include  } 
regular-expression  ]  Available in any view
 
Remove all IPv6 static routes.  delete ipv6 
[ vpn-instance  
vpn-instance-name  ] static-routes 
all  Available in system view
 
 
To delete a single IPv6 static route, use the undo ipv6 route-static  command. To delete all IPv6 static 
routes, including the default route, use the  delete ipv6 static-routes all command. 
For more information about the  display ipv6 routing-table protocol static  [  inactive  | verbose  ] [ | { begin  
|  exclude  | include  } regular-expression  ] command, see Layer 3—IP Routing Command Reference . 
IPv6 static routing configuration example 
Network requirements 
As shown in Figure 99, c onfigure IPv6 static routes so that hosts can reach one another.
    Add page 948 to Favourites
    image text
    Enable zoom 
    							 259 
Figure 99 Network diagram 
 
 
Configuration procedure 
1. Configure the IPv6 addresses for all VL AN interfaces. (Details not shown.) 
2. Configure IPv6 static routes: 
# Configure a default IPv6 static route on Switch A. 
 system-view 
[SwitchA] ipv6 
[SwitchA] ipv6 route-static :: 0 4::2 
# Configure two IPv6 static routes on Switch B. 
 system-view 
[SwitchB] ipv6 
[SwitchB] ipv6 route-static 1:: 64 4::1 
[SwitchB] ipv6 route-static 3:: 64 5::1 
# Configure a default IPv6 static route on Switch C. 
 system-view 
[SwitchC] ipv6 
[SwitchC] ipv6 route-static :: 0 5::2 
3. Configure the IPv6 addresses and gateways for hosts: 
Configure the IPv6 addresses for all the hosts based  on the network diagram, configure the default 
gateway of Host A as 1::1, Host  B as 2::1, and Host C as 3::1. 
4. Verify the configuration: 
# Display the IPv6 routing table of Switch A. 
[SwitchA] display ipv6 routing-table 
Routing Table : 
         Destinations : 5        Routes : 5 
 
 Destination  : ::                                   Protocol     : Stat\
ic 
 NextHop      : 4::2                                 Preference   : 60 
 Interface    : Vlan-interface200                    Cost         : 0 
 
 Destination  : ::1/128                              Protocol     : Dire\
ct 
 NextHop      : ::1                                  Preference   : 0 
 Interface    : InLoop0                              Cost         : 0
    Add page 949 to Favourites
    image text
    Enable zoom 
    							 260 
 
 Destination  : 1::/64                               Protocol     : Dire\
ct 
 NextHop      : 1::1                                 Preference   : 0 
 Interface    : Vlan-interface100                    Cost         : 0 
 
 Destination  : 1::1/128                             Protocol     : Dire\
ct 
 NextHop      : ::1                                  Preference   : 0 
 Interface    : InLoop0                              Cost         : 0 
 
 Destination  : FE80::/10                            Protocol     : Dire\
ct 
 NextHop      : ::                                   Preference   : 0 
 Interface    : NULL0                                Cost         : 0 
# Verify the connectivity with the ping command. 
[SwitchA] ping ipv6 3::1 
  PING 3::1 : 56  data bytes, press CTRL_C to break 
    Reply from 3::1 
    bytes=56 Sequence=1 hop limit=254  time = 63 ms 
    Reply from 3::1 
    bytes=56 Sequence=2 hop limit=254  time = 62 ms 
    Reply from 3::1 
    bytes=56 Sequence=3 hop limit=254  time = 62 ms 
    Reply from 3::1 
    bytes=56 Sequence=4 hop limit=254  time = 63 ms 
    Reply from 3::1 
    bytes=56 Sequence=5 hop limit=254  time = 63 ms 
 
  --- 3::1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 62/62/63 ms
    Add page 950 to Favourites
    image text
    Enable zoom 
    							 261 
Configuring RIPng 
Hardware compatibility 
The HP 5500 SI Switch Series does not support VPN-related parameters.  
Introduction to RIPng 
RIP next generation (RIPng) is an extension of RIP-2 for IPv4. Most RIP concepts are applicable in RIPng. 
The term router in this chapter refers to both routers and Layer 3 switches. 
RIPng for IPv6 has the following basic differences from RIP: 
•   UDP port number —RIPng uses UDP port 521 for sending and receiving routing information. 
•   Multicast address —RIPng uses FF02:9 as the link-local-router multicast address. 
•   Destination Prefix —128-bit destination address prefix. 
•   Next hop —128-bit IPv6 address. 
•   Source address —RIPng uses FE80::/10 as the link-local source address. 
RIPng working mechanism 
RIPng is a routing protocol based on the distance  vector (D-V) algorithm. RIPng uses UDP packets to 
exchange routing information through port 521.  
RIPng uses a hop count to measure the distance to a de stination. The hop count is the metric or cost. The 
hop count from a router to a directly connected  network is 0. The hop count between two directly 
connected routers is 1. When the hop count is greater than or equal to 16, the destination network or host 
is unreachable. 
By default, the routing update is sent every 30 second s. If the router receives no routing updates from a 
neighbor within 180 seconds, the routes learned from the neighbor are considered unreachable. If no 
routing update is received within an other 240 seconds, the router removes these routes from the routing 
table. 
RIPng supports split horizon and poison reverse to  prevent routing loops and route redistribution. 
Each RIPng router maintains a routing database,  which includes route entries of all reachable 
destinations. A route entry contains the following information: 
•   Destination address —IPv6 address of a host or a network. 
•   Next hop address —IPv6 address of a neighbor along the path to the destination. 
•   Egress interface —Outbound interface that forwards IPv6 packets. 
•   Metric —Cost from the local router to the destination. 
•   Route time —Time elapsed since a route entry is last changed. Each time a route entry is modified, 
the routing time is set to 0. 
•   Route tag —Identifies the route used in a routing policy to control routing information. For more 
information about routing policy, see  Configuring routing policies.
    All HP manuals Comments (0)

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