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 931 to Favourites
    image text
    Enable zoom 
    							 242 
 Attribute value : MED 0, pref-val 0, pre 255 
 State           : valid, external, best, 
 Not advertised to any peers yet 
 
The route 9.1.1.0/24 is not available in the routing table of Switch C. 
BGP route reflector configuration 
Network requirements 
In Figure 94 , all s witches run BGP.  
•   Between Switch A and Switch B is an EBGP co nnection; between Switch C and Switch B, and 
between Switch C and Switch D are IBGP connections. 
•   Switch C is a route reflector with clients Switch B and D. 
•   Switch D can learn route 1.0.0.0/8 from Switch C. 
Figure 94  Network diagram 
 
 
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure BGP connections: 
# Configure Switch A. 
 system-view 
[SwitchA] bgp 100 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 192.1.1.2 as-number 200 
# Inject network 1.0.0.0/8 to the BGP routing table. 
[SwitchA-bgp] network 1.0.0.0 
[SwitchA-bgp] quit 
# Configure Switch B. 
 system-view 
[SwitchB] bgp 200 
[SwitchB-bgp] router-id 2.2.2.2 
[SwitchB-bgp] peer 192.1.1.1 as-number 100 
[SwitchB-bgp] peer 193.1.1.1 as-number 200 
[SwitchB-bgp] peer 193.1.1.1 next-hop-local 
[SwitchB-bgp] quit
    Add page 932 to Favourites
    image text
    Enable zoom 
    							 243 
# Configure Switch C. 
 system-view 
[SwitchC] bgp 200 
[SwitchC-bgp] router-id 3.3.3.3  
[SwitchC-bgp] peer 193.1.1.2 as-number 200 
[SwitchC-bgp] peer 194.1.1.2 as-number 200 
[SwitchC-bgp] quit 
# Configure Switch D. 
 system-view 
[SwitchD] bgp 200 
[SwitchD-bgp] router-id 4.4.4.4 
[SwitchD-bgp] peer 194.1.1.1 as-number 200 
[SwitchD-bgp] quit 
3. Configure the route reflector: 
# Configure Switch C. 
[SwitchC] bgp 200 
[SwitchC-bgp] peer 193.1.1.2 reflect-client 
[SwitchC-bgp] peer 194.1.1.2 reflect-client 
[SwitchC-bgp] quit 
4. Verify the configuration: 
# Display the BGP routing table on Switch B. 
[SwitchB] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 200.1.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 Path/O\
gn 
 
 *>  1.0.0.0        192.1.1.1       0                     0       100i 
# Display the BGP routing table on Switch D. 
[SwitchD] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 200.1.2.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 Path/O\
gn 
 
   i 1.0.0.0        193.1.1.2       0          100        0       100i 
Switch D has learned route 1.0.0.0/8 from Switch C.
    Add page 933 to Favourites
    image text
    Enable zoom 
    							 244 
BGP confederation configuration 
Network requirements 
In Figure 95 , to reduce IBGP connections in AS 200, split it into three sub-ASs: AS65001, AS65002, and 
AS65003. Switches in AS65001 are fully meshed. 
Figure 95  Network diagram 
 
Device Interface IP address Device Interface IP address 
Switch A  Vlan-int100  200.1.1.1/24 Switch D Vlan-int200 10.1.5.1/24 
 Vlan-int200 10.1.1.1/24  Vlan-int400  10.1.3.2/24 
 Vlan-int300 10.1.2.1/24 Switch E Vlan-int200 10.1.5.2/24 
 Vlan-int400 10.1.3.1/24  Vlan-int500 10.1.4.2/24 
 Vlan-int500  10.1.4.1/24 Switch F Vlan-int100  200.1.1.2/24 
Switch B  Vlan-int200  10.1.1.2/24  Vlan-int600 9.1.1.1/24 
Switch C  Vlan-int300  10.1.2.2/24     
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure BGP confederation: 
# Configure Switch A. 
 system-view 
[SwitchA] bgp 65001 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] confederation id 200 
[SwitchA-bgp] confederation peer-as 65002 65003 
[SwitchA-bgp] peer 10.1.1.2 as-number 65002 
[SwitchA-bgp] peer 10.1.1.2 next-hop-local 
[SwitchA-bgp] peer 10.1.2.2 as-number 65003 
[SwitchA-bgp] peer 10.1.2.2 next-hop-local 
[SwitchA-bgp] quit 
# Configure Switch B. 
 system-view 
[SwitchB] bgp 65002 
[SwitchB-bgp] router-id 2.2.2.2 
Switch F
Switch A Switch D
Switch E
AS 200
AS 100
Vlan-int600
Switch B
Switch C
AS 65002 AS 65003
Vlan-int100
Vlan-int100
AS 65001
Vlan-int200Vla
n-int30
0Vlan-int400
Vlan-int500 Vlan-int400
Vlan-int500 Vlan-int200
Vlan-int200
Vlan-int300
Vlan-int200
    Add page 934 to Favourites
    image text
    Enable zoom 
    							 245 
[SwitchB-bgp] confederation id 200 
[SwitchB-bgp] confederation peer-as 65001 65003 
[SwitchB-bgp] peer 10.1.1.1 as-number 65001 
[SwitchB-bgp] quit 
# Configure Switch C. 
 system-view 
[SwitchC] bgp 65003 
[SwitchC-bgp] router-id 3.3.3.3 
[SwitchC-bgp] confederation id 200 
[SwitchC-bgp] confederation peer-as 65001 65002 
[SwitchC-bgp] peer 10.1.2.1 as-number 65001 
[SwitchC-bgp] quit 
3. Configure IBGP connections in AS65001: 
# Configure Switch A. 
[SwitchA] bgp 65001 
[SwitchA-bgp] peer 10.1.3.2 as-number 65001 
[SwitchA-bgp] peer 10.1.3.2 next-hop-local 
[SwitchA-bgp] peer 10.1.4.2 as-number 65001 
[SwitchA-bgp] peer 10.1.4.2 next-hop-local 
[SwitchA-bgp] quit  
# Configure Switch D. 
 system-view 
[SwitchD] bgp 65001 
[SwitchD-bgp] router-id 4.4.4.4 
[SwitchD-bgp] confederation id 200 
[SwitchD-bgp] peer 10.1.3.1 as-number 65001 
[SwitchD-bgp] peer 10.1.5.2 as-number 65001 
[SwitchD-bgp] quit 
# Configure Switch E. 
 system-view 
[SwitchE] bgp 65001 
[SwitchE-bgp] router-id 5.5.5.5 
[SwitchE-bgp] confederation id 200 
[SwitchE-bgp] peer 10.1.4.1 as-number 65001 
[SwitchE-bgp] peer 10.1.5.1 as-number 65001 
[SwitchE-bgp] quit 
4. Configure the EBGP connection between AS100 and AS200: 
# Configure Switch A. 
[SwitchA] bgp 65001 
[SwitchA-bgp] peer 200.1.1.2 as-number 100 
[SwitchA-bgp] quit 
# Configure Switch F. 
 system-view 
[SwitchF] bgp 100 
[SwitchF-bgp] router-id 6.6.6.6 
[SwitchF-bgp] peer 200.1.1.1 as-number 200 
[SwitchF-bgp] network 9.1.1.0 255.255.255.0
    Add page 935 to Favourites
    image text
    Enable zoom 
    							 246 
[SwitchF-bgp] quit 
5. Verify the configuration: 
# Display the 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 Path/Ogn \
 
 *>i  9.1.1.0/24        10.1.1.1       0         100       0       (650\
01) 100i 
[SwitchB] display bgp routing-table 9.1.1.0 
 
 BGP local router ID : 2.2.2.2 
 Local AS number : 65002 
 Paths:   1 available, 1 best 
 
 BGP routing table entry information of 9.1.1.0/24: 
 From            : 10.1.1.1 (1.1.1.1) 
 Relay Nexthop   : 0.0.0.0 
 Original nexthop: 10.1.1.1 
 AS-path         : (65001) 100 
 Origin          : igp 
 Attribute value : MED 0, localpref 100, pref-val 0, pre 255 
 State           : valid, external-confed, best, 
 Not advertised to any peers yet 
# Display the BGP routing table on Switch D. 
[SwitchD] display bgp routing-table 
 
 Total Number of Routes: 1 
 
 BGP Local router ID is 4.4.4.4 
 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 
 
 *>i  9.1.1.0/24        10.1.3.1      0          100      0       100i 
[SwitchD] display bgp routing-table 9.1.1.0 
 
 BGP local router ID : 4.4.4.4 
 Local AS number : 65001 
 Paths:   1 available, 1 best 
 
 BGP routing table entry information of 9.1.1.0/24:
    Add page 936 to Favourites
    image text
    Enable zoom 
    							 247 
 From            : 10.1.3.1 (1.1.1.1) 
 Relay Nexthop   : 0.0.0.0 
 Original nexthop: 10.1.3.1 
 AS-path         : 100 
 Origin          : igp 
 Attribute value : MED 0, localpref 100, pref-val 0, pre 255 
 State           : valid, internal, best, 
 Not advertised to any peers yet 
The output shows the following:  
{ Switch F can send route information to Switch B and Switch C through the confederation by 
establishing only an EBGP connection with Switch A.  
{ Switch B and Switch D are in the same confederation, but belong to different sub ASs. They 
obtain external route information from Switch  A and generate the same BGP route entries; it 
seems like they reside in the same AS although they have no direct connection in between.  
BGP path selection configuration 
Network requirements 
In  Figure 96 , all s witches run BGP. Between Switch A and Switch B, and between Switch A and Switch 
C are EBGP connections. Between Switch B and Switch D, and between Switch D and Switch C are IBGP 
connections. OSPF is the IGP protocol in AS 200. 
Configure routing policies, making Switch D use the route 1.0.0.0/8 from Switch C as the optimal. 
Figure 96  Network diagram 
 
Device Interface IP address Device Interface IP address 
Switch A  Vlan-int101  1.0.0.0/8  Switch D  Vlan-int400  195.1.1.1/24 
 Vlan-int100 192.1.1.1/24  Vlan-int300 194.1.1.1/24 
 Vlan-int200 193.1.1.1/24 Switch C Vlan-int400 195.1.1.2/24 
Switch B  Vlan-int100  192.1.1.2/24    Vlan-int200  193.1.1.2/24 
 Vlan-int300 194.1.1.2/24     
Configuration procedure 
1. Configure IP addresses for inte rfaces. (Details not shown.) 
2. Configure OSPF on Switch B, C, and D: 
# Configure Switch B. 
 system-view 
Switch AAS 100
Vlan-int101
Switch CAS 200
Vlan-int200
Switch B
Switch D
Vlan-int100
Vlan-int200 Vlan-int400Vlan-int400
Vlan-int300
Vlan-int300
Vlan-int100
    Add page 937 to Favourites
    image text
    Enable zoom 
    							 248 
[SwitchB] ospf 
[SwitchB-ospf] area 0 
[SwitchB-ospf-1-area-0.0.0.0] network 192.1.1.0 0.0.0.255 
[SwitchB-ospf-1-area-0.0.0.0] network 194.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 
[SwitchC-ospf] area 0 
[SwitchC-ospf-1-area-0.0.0.0] network 193.1.1.0 0.0.0.255 
[SwitchC-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 
[SwitchC-ospf-1-area-0.0.0.0] quit 
[SwitchC-ospf-1] quit 
# Configure Switch D. 
 system-view 
[SwitchD] ospf 
[SwitchD-ospf] area 0 
[SwitchD-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255 
[SwitchD-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255 
[SwitchD-ospf-1-area-0.0.0.0] quit 
[SwitchD-ospf-1] quit 
3. Configure BGP connections: 
# Configure Switch A. 
 system-view 
[SwitchA] bgp 100 
[SwitchA-bgp] peer 192.1.1.2 as-number 200 
[SwitchA-bgp] peer 193.1.1.2 as-number 200 
# Inject network 1.0.0.0/8 to the BGP routing table on Switch A. 
[SwitchA-bgp] network 1.0.0.0 8 
[SwitchA-bgp] quit 
# Configure Switch B. 
[SwitchB] bgp 200 
[SwitchB-bgp] peer 192.1.1.1 as-number 100 
[SwitchB-bgp] peer 194.1.1.1 as-number 200 
[SwitchB-bgp] quit 
# Configure Switch C. 
[SwitchC] bgp 200 
[SwitchC-bgp] peer 193.1.1.1 as-number 100 
[SwitchC-bgp] peer 195.1.1.1 as-number 200 
[SwitchC-bgp] quit 
# Configure Switch D. 
[SwitchD] bgp 200 
[SwitchD-bgp] peer 194.1.1.2 as-number 200 
[SwitchD-bgp] peer 195.1.1.2 as-number 200 
[SwitchD-bgp] quit
    Add page 938 to Favourites
    image text
    Enable zoom 
    							 249 
4.
 
Configure attributes for route 1.0.0.0/8, making Switch D give priority to the route learned from 
Switch C: 
{  Method I 
Configure a higher MED value for the route 1. 0.0.0/8 advertised from Switch A to peer 
192.1.1.2. 
# Define an ACL numbered 2000 to permit route 1.0.0.0/8. 
[SwitchA] acl number 2000 
[SwitchA-acl-basic-2000] rule permit source 1.0.0.0 0.255.255.255 
[SwitchA-acl-basic-2000] quit 
# Define two routing policies, apply_med_50 , which sets the MED for route 1.0.0.0/8 to 50, 
and apply_med_100 , which sets the MED for route 1.0.0.0/8 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 
[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 the route advertised to peer 193.1.1.2 (Switch C), 
and apply_med_100  to the route advertised to  peer 192.1.1.2 (Switch B). 
[SwitchA] bgp 100 
[SwitchA-bgp] peer 193.1.1.2 route-policy apply_med_50 export 
[SwitchA-bgp] peer 192.1.1.2 route-policy apply_med_100 export 
[SwitchA-bgp] quit 
# Display the BGP routing table on Switch D. 
[SwitchD] display bgp routing-table 
 
 Total Number of Routes: 2 
 
 BGP Local router ID is 194.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 Path/O\
gn 
 
 *>i 1.0.0.0         193.1.1.1      50         100        0       100i 
 * i                 192.1.1.1      100        100        0       100i 
Route 1.0.0.0/8 is the optimal. 
{ Method II 
Configure different local preferences on Switch B and C for route 1.0.0.0/8, making Switch 
D give priority to the route from Switch C. 
# Define an ACL numbered 2000 on Rout er C, permitting route 1.0.0.0/8. 
[SwitchC] acl number 2000 
[SwitchC-acl-basic-2000] rule permit source 1.0.0.0 0.255.255.255 
[SwitchC-acl-basic-2000] quit
    Add page 939 to Favourites
    image text
    Enable zoom 
    							 250 
# Configure a routing policy named localpref on Switch C, setting the local preference of route 
1.0.0.0/8 to 200 (the default is 100).  
[SwitchC] route-policy localpref permit node 10 
[SwitchC-route-policy] if-match acl 2000 
[SwitchC-route-policy] apply local-preference 200 
[SwitchC-route-policy] quit 
# Apply routing policy localpref to routes from peer 193.1.1.1. 
[SwitchC] bgp 200 
[SwitchC-bgp] peer 193.1.1.1 route-policy localpref import 
[SwitchC-bgp] quit 
# Display the routing table on Switch D. 
[SwitchD] display bgp routing-table 
 
 Total Number of Routes: 2 
 
 BGP Local router ID is 194.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 Path/O\
gn 
 
 *>i 1.0.0.0          193.1.1.1     0          200        0       100i 
 * i                  192.1.1.1     0          100        0       100i 
Route 1.0.0.0/8 from Switch D to Switch C is the optimal. 
BGP GR configuration 
Network requirements 
All switches run BGP in Figure 97 . Between Switch A and Switch B is  an EBGP connection. Switch B and 
Switch C are connected over an IBGP connection. Enable GR capability for BGP so that the 
communication between Switch A and Switch C is not  affected when a master/slave switchover occurs 
on Switch B.  
Figure 97  Network diagram 
 
 
Configuration procedure 
1. Configure Switch A: 
# Configure IP addresses for interfaces. (Details not shown.)  
# Configure the EBGP connection.  
 system-view
    Add page 940 to Favourites
    image text
    Enable zoom 
    							 251 
[SwitchA] bgp 65008 
[SwitchA-bgp] router-id 1.1.1.1 
[SwitchA-bgp] peer 200.1.1.1 as-number 65009 
# Inject network 8.0.0.0/8 to the BGP routing table.  
[SwitchA-bgp] network 8.0.0.0 
# Enable GR capability for BGP.  
[SwitchA-bgp] graceful-restart 
2. Configure Switch B: 
# Configure IP addresses for interfaces. (Details not shown.)  
# Configure the EBGP connection.  
 system-view 
[SwitchB] bgp 65009 
[SwitchB-bgp] router-id 2.2.2.2 
[SwitchB-bgp] peer 200.1.1.2 as-number 65008 
# Configure the IBGP connection.  
[SwitchB-bgp] peer 9.1.1.2 as-number 65009 
# Inject networks 200.1.1.0/24 and 9. 1.1.0/24 to the BGP routing table.  
[SwitchB-bgp] network 200.1.1.0 24 
[SwitchB-bgp] network 9.1.1.0 24 
# Enable GR capability for BGP.  
[SwitchB-bgp] graceful-restart 
3. Configure Switch C: 
# Configure IP addresses for interfaces. (Details not shown.)  
# Configure the IBGP connection.  
 system-view 
[SwitchC] bgp 65009 
[SwitchC-bgp] router-id 3.3.3.3 
[SwitchC-bgp] peer 9.1.1.1 as-number 65009 
# Enable GR capability for BGP.  
[SwitchC-bgp] graceful-restart 
4.  Verify the configuration: 
Ping Switch C on Switch A. Meanwhile, perform a  master/slave switchover on Switch B. The ping 
operation is successful during the whole switchover process.  
Configuring BFD for BGP 
Network requirements 
As shown in  Figure 98,  
•   C
onfigure OSPF as the IGP in AS 200. 
•   Establish two IBGP connections between Switch A  and Switch C. When both links are working, 
Switch C adopts the link Switch ASwitch BSwitch C to exchange packets with network 
1.1.1.0/24. Configure BFD over the link. Then if the link fails, BFD can quickly detect the failure and 
notify it to BGP. Then the link Switch ASw itch DSwitch C takes effect immediately.
    All HP manuals Comments (0)

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