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 921 to Favourites
    image text
    Enable zoom 
    							 232 
 
BGP local router ID : 3.3.3.3 
 Local AS number : 65009 
 Total number of peers : 1                 Peers in established state : \
1 
 
  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  Sta\
te 
 
  2.2.2.2              65009        2        2    0       0 00:00:13 Est\
ablished 
The output shows that Switch C has established an IBGP peer relationship with Switch B. 
3. Configure EBGP: 
{  The EBGP peers, Switch A and Switch B (usually  belong to different carriers), are located in 
different ASs. Typically, their loopback interfaces  are not reachable to each other, so directly 
connected interfaces are used fo r establishing BGP sessions.  
{ To enable Switch C to access the network 8.1.1.0/24 connected directly to Switch A, inject 
network 8.1.1.0/24 to the BGP routing table of Switch A.  
# Configure Switch A. 
 system-view 
[SwitchA] bgp 65008 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 3.1.1.1 as-number 65009 
[SwitchA-bgp] network 8.1.1.1 24 
[SwitchA-bgp] quit 
# Configure Switch B. 
[SwitchB] bgp 65009 
[SwitchB-bgp] peer 3.1.1.2 as-number 65008 
[SwitchB-bgp] quit 
# Display BGP peer information on Switch B. 
[SwitchB] display bgp peer 
 
BGP local router ID : 2.2.2.2 
 Local AS number : 65009 
 Total number of peers : 2                 Peers in established state : \
2 
 
  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  Sta\
te 
 
  3.3.3.3              65009        4        4    0       0 00:02:49 Est\
ablished 
  3.1.1.2              65008        2        2    0       0 00:00:05 Est\
ablished 
The output shows that Switch B has established an  IBGP peer relationship with Switch C and an 
EBGP peer relationship with Switch A. 
# Display the BGP routing table on Switch A. 
[SwitchA] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 1.1.1.1 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale
    Add page 922 to Favourites
    image text
    Enable zoom 
    							 233 
               Origin : i - IGP, e - EGP, ? - incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
 *>  8.1.1.0/24         0.0.0.0         0                     0       i \
# Display the BGP routing table on Switch B. 
[SwitchB] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 2.2.2.2 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
 *>  8.1.1.0/24         3.1.1.2         0                     0       65\
008i 
# Display the BGP routing table on Switch C. 
[SwitchC] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 3.3.3.3 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
   i 8.1.1.0/24         3.1.1.2         0          100        0       65\
008i 
The outputs show that Switch A has learned no route to AS65009, and Switch C has learned 
network 8.1.1.0 but the next hop 3.1.1.2 is  unreachable, so the route is invalid. 
4. Redistribute direct routes: 
Configure BGP to redistribute direct  routes on Switch B, so that Switch A can obtain the route to 
9.1.1.0/24 and Switch C can obtain the route to 3.1.1.0/24.  
# Configure Switch B. 
[SwitchB] bgp 65009 
[SwitchB-bgp] import-route direct 
# Display the BGP routing table on Switch A. 
[SwitchA] display bgp routing-table 
 
 Total Number of Routes: 4 
 
 BGP Local router ID is 1.1.1.1 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale
    Add page 923 to Favourites
    image text
    Enable zoom 
    							 234 
               Origin : i - IGP, e - EGP, ? – incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
 *>  2.2.2.2/32         3.1.1.1         0                     0       65\
009? 
 *   3.1.1.0/24         3.1.1.1         0                     0       65\
009? 
 *>  8.1.1.0/24         0.0.0.0         0                     0       i \
 *>  9.1.1.0/24         3.1.1.1         0                     0       65\
009? 
Two routes 2.2.2.2/32 and 9.1.1.0/24 have been added in Switch A’s routing table.  
# Display the BGP routing table on Switch C. 
[SwitchC] display bgp routing-table 
 
 Total Number of Routes: 4 
 
 BGP Local router ID is 3.3.3.3 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
   i 2.2.2.2/32         2.2.2.2         0          100        0       ? \
 *>i 3.1.1.0/24         2.2.2.2         0          100        0       ? \
 *>i 8.1.1.0/24         3.1.1.2         0          100        0       65\
008i 
 * i 9.1.1.0/24         2.2.2.2         0          100        0       ? \
The output shows that the route 8.1.1.0 becomes valid with the next hop as Switch A. 
5. Verify the configuration: 
# Ping 8.1.1.1 on Switch C. 
[SwitchC] ping 8.1.1.1 
  PING 8.1.1.1: 56  data bytes, press CTRL_C to break 
    Reply from 8.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=2 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=3 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=5 ttl=254 time=2 ms 
  --- 8.1.1.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 2/2/2 ms 
BGP and IGP synchronization configuration 
Network requirements 
As shown in  Figure 91, all de vices of company A belong to AS 65008, and all devices of company B 
belong to AS 65009. AS 65008 and AS 65009 are  connected through Switch A and Switch B. Switch
    Add page 924 to Favourites
    image text
    Enable zoom 
    							 235 
A  m u s t  b e  a b l e  t o  a c c e s s  n e t w o r k  9.1. 2. 0 / 24  i n  A S  65 0 0 9,  a n d  Sw i t c h  C  m u s t  a c c e s s  n e t w o r k  8 .1.1. 0 / 24  
in AS 65008.  
Figure 91 Network diagram 
 
 
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure OSPF:  
Enable OSPF in AS 65009, so that Switch  B can obtain the route to 9.1.2.0/24.  
# Configure Switch B.  
 system-view 
[SwitchB] ospf 1 
[SwitchB-ospf-1] area 0 
[SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0 
[SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 
[SwitchB-ospf-1-area-0.0.0.0] quit 
[SwitchB-ospf-1] quit 
# Configure Switch C.  
 system-view 
[SwitchC] ospf 1 
[SwitchC-ospf-1] import-route direct 
[SwitchC-ospf-1] area 0 
[SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255 
[SwitchC-ospf-1-area-0.0.0.0] quit 
[SwitchC-ospf-1] quit 
3.  Configure the EBGP connection: 
Configure the EBGP connection and inject network 8.1.1.0/24 to the BGP routing table of Switch 
A, so that Switch B can obtain the route to 8.1.1.0/24.  
# Configure Switch A. 
 system-view 
[SwitchA] bgp 65008 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 3.1.1.1 as-number 65009 
[SwitchA-bgp] network 8.1.1.0 24 
[SwitchA-bgp] quit 
# Configure Switch B. 
[SwitchB] bgp 65009 
[SwitchB-bgp] router-id 2.2.2.2 
[SwitchB-bgp] peer 3.1.1.2 as-number 65008
    Add page 925 to Favourites
    image text
    Enable zoom 
    							 236 
4.
 
Configure BGP and IGP synchronization: 
{  Configure BGP to redistribute routes from OSPF on Switch B, so that Switch A can obtain the 
ro u t e  t o  9.1. 2.0 / 24 .   
{ Configure OSPF to redistribute routes from BGP on Switch B, so that Switch C can obtain the 
r o u t e  t o  8 .1.1. 0 / 2 4 .   
# Configure BGP to redistribute ro utes from OSPF on Switch B. 
[SwitchB-bgp] import-route ospf 1 
[SwitchB-bgp] quit 
[SwitchB] ospf 1 
[SwitchB-ospf-1] import-route bgp 
[SwitchB-ospf-1] quit 
# Display the BGP routing table on Switch A. 
[SwitchA] display bgp routing-table 
 
Total Number of Routes: 3 
 
 BGP Local router ID is 1.1.1.1 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
 *>  3.3.3.3/32         3.1.1.1         1                     0       65\
009? 
 *>  8.1.1.0/24         0.0.0.0         0                     0       i \
 *>  9.1.2.0/24         3.1.1.1         1                     0       65\
009? 
# Display the routing table on Switch C. 
[SwitchC] display ip routing-table 
Routing Tables: Public 
         Destinations : 9        Routes : 9 
 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
 
2.2.2.2/32          OSPF   10   1            9.1.1.1         Vlan300 
3.3.3.3/32          Direct 0    0            127.0.0.1       InLoop0 
8.1.1.0/24          O_ASE  150  1            9.1.1.1         Vlan300 
9.1.1.0/24          Direct 0    0            9.1.1.2         Vlan300 
9.1.1.2/32          Direct 0    0            127.0.0.1       InLoop0 
9.1.2.0/24          Direct 0    0            9.1.2.1         Vlan400 
9.1.2.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 
5. Verify the configuration: 
# Use ping for verification. 
[SwitchA] ping -a 8.1.1.1 9.1.2.1 
  PING 9.1.2.1: 56  data bytes, press CTRL_C to break 
    Reply from 9.1.2.1: bytes=56 Sequence=1 ttl=254 time=15 ms
    Add page 926 to Favourites
    image text
    Enable zoom 
    							 237 
    Reply from 9.1.2.1: bytes=56 Sequence=2 ttl=254 time=31 ms 
    Reply from 9.1.2.1: bytes=56 Sequence=3 ttl=254 time=47 ms 
    Reply from 9.1.2.1: bytes=56 Sequence=4 ttl=254 time=46 ms 
    Reply from 9.1.2.1: bytes=56 Sequence=5 ttl=254 time=47 ms 
 
  --- 9.1.2.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 15/37/47 ms 
[SwitchC] ping -a 9.1.2.1 8.1.1.1 
  PING 8.1.1.1: 56  data bytes, press CTRL_C to break 
    Reply from 8.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=2 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=3 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms 
    Reply from 8.1.1.1: bytes=56 Sequence=5 ttl=254 time=2 ms 
 
  --- 8.1.1.1 ping statistics --- 
    5 packet(s) transmitted 
    5 packet(s) received 
    0.00% packet loss 
    round-trip min/avg/max = 2/2/2 ms 
BGP load balancing configuration 
Network requirements 
As shown in Figure 92, all the s witches run BGP. Switch A resides in AS 65008, Switch B and Switch C 
in AS 65009. Between Switch A and Switch B,  Switch A and Switch C are EBGP connections, and 
between Switch B and Switch C is an IBGP connection.  Two routes are configured on Switch A for load 
balancing. 
Figure 92  Network diagram
    Add page 927 to Favourites
    image text
    Enable zoom 
    							 238 
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure BGP connections: 
{  On Switch A, establish EBGP connections with Switch B and Switch C; configure BGP to 
advertise network 8.1.1.0/24 to Switch B and Sw itch C, so that Switch B and Switch C can 
access the internal network connected to Switch A.  
{  On Switch B, establish an EBGP connection with Switch A and an IBGP connection with Switch 
C; configure BGP to adver tise network 9.1.1.0/24 to Switch A, so that Switch A can access the 
intranet through Switch B; configure a static ro ute to interface loopback 0 on Switch C (or use 
a routing protocol like OSPF) to establish the IBGP connection.  
{  O n  Sw i t c h  C ,  e s t a b l i s h  a n  E B G P  c o n n e c t i o n  w i t h  Sw i t c h  A  a n d  a n  I B G P  c o n n e c t i o n  w i t h  Sw i t c h  
B; configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the 
intranet through Switch C; configure a static ro ute to interface loopback 0 on Switch B (or use 
another protocol like OSPF) to establish the IBGP connection. 
# Configure Switch A. 
 system-view 
[SwitchA] bgp 65008 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 3.1.1.1 as-number 65009 
[SwitchA-bgp] peer 3.1.2.1 as-number 65009 
[SwitchA-bgp] network 8.1.1.1 24 
[SwitchA-bgp] quit 
# Configure Switch B. 
 system-view 
[SwitchB] bgp 65009 
[SwitchB-bgp] router-id 2.2.2.2 
[SwitchB-bgp] peer 3.1.1.2 as-number 65008 
[SwitchB-bgp] peer 3.3.3.3 as-number 65009 
[SwitchB-bgp] peer 3.3.3.3 connect-interface loopback 0 
[SwitchB-bgp] network 9.1.1.0 255.255.255.0 
[SwitchB-bgp] quit 
[SwitchB] ip route-static 3.3.3.3 32 9.1.1.2 
# Configure Switch C. 
 system-view 
[SwitchC] bgp 65009 
[SwitchC-bgp] router-id 3.3.3.3 
[SwitchC-bgp] peer 3.1.2.2 as-number 65008 
[SwitchC-bgp] peer 2.2.2.2 as-number 65009 
[SwitchC-bgp] peer 2.2.2.2 connect-interface loopback 0 
[SwitchC-bgp] network 9.1.1.0 255.255.255.0 
[SwitchC-bgp] quit 
[SwitchC] ip route-static 2.2.2.2 32 9.1.1.1 
# Display the BGP routing table on Switch A. 
[SwitchA] display bgp routing-table 
 
 Total Number of Routes: 3
    Add page 928 to Favourites
    image text
    Enable zoom 
    							 239 
 BGP Local router ID is 1.1.1.1 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? – incomplete 
 
     Network            NextHop         MED        LocPrf     PrefVal Pa\
th/Ogn 
 
 *>  8.1.1.0/24         0.0.0.0         0                     0       i \
 *>  9.1.1.0/24         3.1.1.1         0                     0       65\
009i 
 *                      3.1.2.1         0                     0       65\
009i 
{ T h e  o u t p u t  s h o w s  t w o  v a l i d  r o u t e s  t o  d e s t i n a t i o n  9 .1.1. 0 / 2 4 :  t h e  r o u t e  w i t h  n e x t  h o p  3 .1.1.1  i s  
marked with a greater-than sign (>), indicating it is the best route (because the ID of Switch B 
is smaller) ; the route with next hop 3.1.2.1  is marked with only an asterisk (*) , indicating it is a 
valid route, but not the best.  
{ By using the  display ip routing-table  command, you can find only one route to 9.1.1.0/24 with 
next hop 3.1.1.1 and outbound interface VLAN-interface 200.  
3.  Configure loading balancing: 
Since Switch A has two routes to reach AS 65009, configuring load balancing over the two BGP 
routes on Switch A can improve link utilization.  
# Configure Switch A. 
[SwitchA] bgp 65008 
[SwitchA-bgp] balance 2 
[SwitchA-bgp] quit 
4. Verify the configuration:  
# Display the BGP routing table on Switch A. 
[SwitchA] display bgp routing-table 
 
 Total Number of Routes: 3 
 
 BGP Local router ID is 1.1.1.1 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
      Network            NextHop        MED        LocPrf    PrefVal Pat\
h/Ogn 
 
 *>  8.1.1.0/24         0.0.0.0         0                     0       i \
 *>   9.1.1.0/24         3.1.1.1        0                    0       650\
09i 
 *>                      3.1.2.1        0                    0       650\
09i 
{  T h e  r o u t e  9 .1.1. 0 / 2 4  h a s  t w o  n e x t  h o p s  3 .1.1.1  a n d  3 .1. 2 .1,  b o t h  o f  w h i c h  a r e  m a r k e d  w i t h  a  
greater-than sign (>), indicating they are the best routes. 
{ By using the  display ip routing-table  c o m m a n d,  yo u  c a n  f i n d  t wo  ro u t e s  t o  9.1.1.0 / 24 :  o n e  wi t h  
next hop 3.1.1.1 and outbound interface VLAN-interface 200, the other with next hop 3.1.2.1 
and outbound interface VLAN-interface 300.
    Add page 929 to Favourites
    image text
    Enable zoom 
    							 240 
BGP community configuration 
Network requirements 
As shown in Figure 93, Switch B establishes EBGP connections with Switch A and C. Configure 
No_Export community attribute on Switch A to make routes from AS 10 not advertised by AS 20 to any 
other AS. 
Figure 93  Network diagram 
 
 
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure EBGP: 
# Configure Switch A. 
 system-view 
[SwitchA] bgp 10 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 200.1.2.2 as-number 20 
[SwitchA-bgp] network 9.1.1.0 255.255.255.0 
[SwitchA-bgp] quit 
# Configure Switch B. 
 system-view 
[SwitchB] bgp 20 
[SwitchB-bgp] router-id 2.2.2.2 
[SwitchB-bgp] peer 200.1.2.1 as-number 10 
[SwitchB-bgp] peer 200.1.3.2 as-number 30 
[SwitchB-bgp] quit 
# Configure Switch C. 
 system-view 
[SwitchC] bgp 30 
[SwitchC-bgp] router-id 3.3.3.3  
[SwitchC-bgp] peer 200.1.3.1 as-number 20 
[SwitchC-bgp] quit 
# Display the BGP routing table on Switch B. 
[SwitchB] display bgp routing-table 9.1.1.0 
 
 BGP local router ID : 2.2.2.2
    Add page 930 to Favourites
    image text
    Enable zoom 
    							 241 
 Local AS number : 20 
 Paths:   1 available, 1 best 
 
BGP routing table entry information of 9.1.1.0/24: 
 From            : 200.1.2.1 (1.1.1.1) 
 Original nexthop: 200.1.2.1 
 AS-path         : 10 
 Origin          : igp 
 Attribute value : MED 0, pref-val 0, pre 255 
 State           : valid, external, best, 
 Advertised to such 1 peers: 
    200.1.3.2 
Switch B advertised routes to Switch C in AS30. 
# Display the routing table on Switch C. 
[SwitchC] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 3.3.3.3 
 Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped, 
               h - history,  i - internal, s - suppressed, S - Stale 
               Origin : i - IGP, e - EGP, ? - incomplete 
      Network            NextHop        MED        LocPrf    PrefVal Pat\
h/Ogn 
 
 *>   9.1.1.0/24        200.1.3.1       0                    0       20 \
10i 
Switch C has learned route 9.1.1.0/24 from Switch B. 
3. Configure BGP community:  
# Configure a routing policy. 
[SwitchA] route-policy comm_policy permit node 0 
[SwitchA-route-policy] apply community no-export 
[SwitchA-route-policy] quit 
# Apply the routing policy. 
[SwitchA] bgp 10 
[SwitchA-bgp] peer 200.1.2.2 route-policy comm_policy export 
[SwitchA-bgp] peer 200.1.2.2 advertise-community 
# Display the routing table on Switch B. 
[SwitchB] display bgp routing-table 9.1.1.0 
 BGP local router ID : 2.2.2.2 
 Local AS number : 20 
 Paths:   1 available, 1 best 
 
 BGP routing table entry information of 9.1.1.0/24: 
 From            : 200.1.2.1 (1.1.1.1) 
 Original nexthop: 200.1.2.1 
 Community       : No-Export 
 AS-path         : 10 
 Origin          : igp
    All HP manuals Comments (0)

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