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 1091 to Favourites
    image text
    Enable zoom 
    							 402 
BGP checks routing loops by examining AS numbers. When EBGP is used, the MCE advertises routing 
information carr ying the local AS number to the site and then receives routing updates from the site. The 
routing updates carry the AS number of the MCE, so  the MCE discards them to avoid routing loops. To 
enable the MCE to receive such routes, configure the MCE to allow routing loops. 
Routes redistributed from OSPF to BGP on the MCE have their OSPF attributes removed. To enable BGP 
to distinguish routes redist ributed from different OSPF domains, yo u must enable the redistributed routes 
to carry the OSPF domain ID by configuring the  domain-id command in OSPF view. The domain ID is 
added to BGP VPN routes as an extended community attribute. 
BGP runs in a BGP VPN instance in the same way as it runs in a normal network.  
2.  Configure a VPN site:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number  N/A 
3.  Configure the MCE as the 
EBGP peer.  peer 
{ group-name |  ip-address } 
as-number  as-number  N/A 
4.
  Redistribute the IGP routes of 
the VPN.  import-route 
protocol [ process-id  ] 
[ med  med-value  | route-policy  
route-policy-name  ] *  Optional. 
A VPN site must advertise the VPN 
network addresses it can reach to 
the connected MCE. 
 
Configuring IBGP beween MCE and VPN site 
If IBGP is used for exchanging routing information between an MCE and VPN sites, you must configure 
a BGP peer for each VPN instance respectively, and re
d i s t ri bu te  t h e  I G P  ro u tes  of  e ach  V P N  i n s ta nc e  o n 
the VPN sites. 
1.  Configure the MCE:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number  N/A 
3.  Enter BGP-VPN instance view.  ipv4-family vpn-instance
 
vpn-instance-name   N/A 
4.
  Configure an IBGP peer.  peer 
{ group-name  | ip-address  } 
as-number  as-number  N/A 
5.
  Configure the system to be the 
RR and specify the peer as the 
client of the RR.  peer 
{ group-name  | ip-address  } 
reflect-client  Optional. 
By default, no RR or RR client is 
configured. 
6.
  Redistribute remote site routes 
advertised by the PE.  import-route 
protocol [ process-id  
|  all-processes  ] [ med  med-value  | 
route-policy route-policy-name ] *  By default, no route redistribution 
is configured. 
7.
  Configure a filtering policy to 
filter the routes to be 
advertised.  filter-policy {
 acl-number | 
ip-prefix  ip-prefix-name  } export 
[ direct  | isis  process-id  | ospf  
process-id  | rip process-id  | static ]
 
Optional. 
By default, BGP does not filter the 
routes to be advertised.
    Add page 1092 to Favourites
    image text
    Enable zoom 
    							 403 
Step Command Remarks 
8.  Configure a filtering policy to 
filter the received routes.  filter-policy 
{ acl-number  | 
ip-prefix ip-prefix-name  } import Optional. 
By default, BGP does not filter the 
received routes. 
 
 
NOTE: 
After you configure a VPN site as an IBGP peer of the MCE, the MCE does not advertise the BGP routes 
learned from the VPN site to other IBGP peers, incl uding VPNv4 peers. Only when you configure the VPN
site as a client of the RR (the MCE), does the MCE adv ertise routes learned from it to other IBGP peers.
  
2. Configure a VPN site:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number  N/A 
3.  Configure the MCE as the 
IBGP peer.  peer 
{ group-name |  ip-address } 
as-number  as-number  N/A 
4.
  Redistribute the IGP routes of 
the VPN.  import-route 
protocol [ process-id  ] 
[ med  med-value  | route-policy  
route-policy-name  ] *  Optional. 
A VPN site must advertise the VPN 
network addresses it can reach to 
the connected MCE. 
 
Configuring routing between MCE and PE 
MCE-PE routing configuration includes these tasks: 
•
  Bind the MCE-PE interfaces to VPN instances 
•   Perform route configurations 
•   Redistribute VPN routes into the routing pr otocol running between the MCE and the PE. 
Configuring static routing between MCE and PE 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A
    Add page 1093 to Favourites
    image text
    Enable zoom 
    							 404 
Step Command Remarks 
2.  Configure a static route for a 
VPN instance. 
• ip  route-static  dest-address  { mask | 
mask-length  } { gateway-address  | 
interface-type interface-number  
[ gateway-address  ] | vpn-instance 
d-vpn-instance-name  gateway-address } 
[  preference  preference-value  ] [ tag tag-value  ] 
[ description  description-text  ] 
• ip route-static  vpn-instance  
s-vpn-instance-name&  dest-address  
{  mask  | mask-length  } { gateway-address  
[ public  ] | interface-type interface-number 
[ gateway-address  ] | vpn-instance 
d-vpn-instance-name gateway-address } 
[  preference  preference-value  ] [ tag tag-value  ] 
[ description  description-text  ]  Use either 
command. 
3.
  Configure the default 
precedence for static routes.  ip route-static default-preference
 
default-preference-value  Optional. 
60 by default.
 
 
Configuring RIP between MCE and PE 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Create a RIP process for 
a VPN instance and 
enter RIP view.  rip 
[ process-id  ] vpn-instance  
vpn-instance-name   N/A 
3.
  Enable RIP on the 
interface attached to 
the specified network.  network 
network-address   By default, RIP is disabled on 
an interface. 
4.
  Redistribute the VPN 
routes.  import-route 
protocol [  process-id  ] 
[  allow-ibgp  ] [ cost cost |  route-policy  
route-policy-name  | tag  tag ] *   By default, no route of any 
other routing protocol is 
redistributed into RIP. 
5.
  Configure the default 
cost value for the 
redistributed routes.  default cost 
value  Optional. 
0 by default. 
 
Configuring OSPF between MCE and PE 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Create an OSPF process 
for a VPN instance and 
enter OSPF view.  ospf
 [ process-id  | router-id 
router-id  | vpn-instance 
vpn-instance-name  ] *  N/A
    Add page 1094 to Favourites
    image text
    Enable zoom 
    							 405 
Step Command Remarks 
3.  Disable routing loop 
detection.  vpn-instance-capability simple  Disabled by default. 
You must disable routing loop 
detection for a VPN OSPF process on 
the MCE. Otherwise, the MCE 
cannot receive OSPF routes from the 
PE. 
4.
  Configure the OSPF 
domain ID.  domain-id 
domain-id [ secondary ] Optional. 
0 by default. 
5.  Redistribute the VPN 
routes.  import-route 
protocol [ process-id  | 
allow-ibgp  ] [ cost  cost  | type  type  | 
tag  tag  | route-policy 
route-policy-name  ] *
  By default, no route of any other 
routing protocol is redistributed into 
OSPF.
 
6.  Configure a filtering policy 
to filter advertised routes.  filter-policy 
{ acl-number  | ip-prefix  
ip-prefix-name  } export  [ protocol 
[ process-id  ] ]
  Optional. 
By default, advertised routes are not 
filtered.
 
7.  Configure the default 
parameters for 
redistributed routes (cost, 
route number, tag, and 
type).  default 
{ cost  cost  | limit  limit  | tag  
tag  | type  type } *
  Optional. 
The default cost is 1, the default 
maximum number of routes 
redistributed per time is 1000, the 
default tag is 1, and default type of 
redistributed routes is Type-2.
 
8.  Create an OSPF area and 
enter OSPF area view.  area
 area-id   By default, no OSPF area is created. 
9.  Enable OSPF on the 
interface attached to the 
specified network in the 
area.  network 
ip-address wildcard-mask  By default, an interface neither 
belongs to any area nor runs OSPF.
 
 
Configuring IS-IS between MCE and PE 
 
Step Command Remarks 
1.
  Enter system view. 
system-view  N/A 
2.  Create an IS-IS process 
for a VPN instance and 
enter IS-IS view.  isis
 [ process-id  ] vpn-instance  
vpn-instance-name   N/A 
3.
  Configure a network 
entity title.  network-entity 
net  Not configured by default. 
4.  Redistribute the VPN 
routes.  import-route { isis
 [ process-id ] |  ospf  
[ process-id  ] | rip  [ process-id  ] |  bgp  
[  allow-ibgp  ] | direct | static  } [ cost  cost  
|  cost-type  { external |  internal } | 
[ level-1  | level-1-2  | level-2  ] | 
route-policy  route-policy-name  | tag 
tag  ] *  Optional. 
By default, IS-IS does not 
redistribute routes of any other 
routing protocol. 
If you do not specify the route level 
in the command, the command will 
redistribute routes to the level-2 
routing table by default.
    Add page 1095 to Favourites
    image text
    Enable zoom 
    							 406 
Step Command Remarks 
5.  Configure a filtering 
policy to filter 
advertised routes.  filter-policy { acl-number
 | ip-prefix  
ip-prefix-name  | route-policy  
route-policy-name  } export [  isis 
process-id  | ospf  process-id  | rip 
process-id  | bgp  | direct |  static ]  Optional. 
By default, IS-IS does not filter 
advertised routes. 
6.
  Return to system view. 
quit  N/A 
7.  Enter interface view. 
interface interface-type interface-number N/A 
8.  Enable the IS-IS process 
on the interface.  isis enable
 [ process-id  ]  Disabled by default. 
 
Configuring EBGP between MCE and PE 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number  N/A 
3.  Enter BGP-VPN instance 
view.  ipv4-family vpn-instance
 vpn-instance-name N/A 
4.   Configure the PE as the 
EBGP peer.  peer 
{ group-name  | ip-address  } as-number  
as-number   N/A 
5.
  Redistribute the VPN 
routes of the VPN site.  import-route 
protocol [ process-id  | 
all-processes  ] [ med  med-value  | 
route-policy route-policy-name ] *  By default, no route 
redistribution is configured. 
6.
  Configure a filtering 
policy to filter the routes 
to be advertised.  filter-policy {
 acl-number |  ip-prefix 
ip-prefix-name  } export [ direct | isis  
process-id  | ospf  process-id  | rip process-id  
|  static  ]  Optional. 
By default, BGP does not filter 
the routes to be advertised. 
7.
  Configure a filtering 
policy to filter the 
received routes.  filter-policy 
{ acl-number  | ip-prefix 
ip-prefix-name  } import  Optional. 
By default, BGP does not filter 
the received routes. 
 
 
NOTE: 
BGP runs within a VPN in the same way as it runs within a public network.  
 
Configuring IBGP between MCE and PE 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number  N/A 
3.  Enter BGP-VPN instance 
view.  ipv4-family vpn-instance
 
vpn-instance-name   N/A 
4.
  Configure the PE as the IBGP 
peer.  peer 
{ group-name |  ip-address } 
as-number  as-number  N/A
    Add page 1096 to Favourites
    image text
    Enable zoom 
    							 407 
Step Command Remarks 
5.  Redistribute the VPN routes 
of the VPN site.  import-route 
protocol [ process-id  | 
all-processes  ] [ med  med-value  | 
route-policy route-policy-name ] *  By default, no route 
redistribution is configured. 
6.
  Configure the egress router 
of the site as a client of the 
route reflector.  peer 
{ group-name |  ip-address } 
reflect-client  Optional. 
By default, no route reflector or 
client is configured. 
7.
  Enable route reflection 
between clients.  reflect 
between-clients  Optional. 
Enabled by default. 
If the clients are fully meshed, 
you do not need to enable 
route reflection. 
8.
  Specify a cluster ID for the 
route reflector.   reflector cluster-id 
cluster-id  Optional. 
By default, each RR in a cluster 
uses its own router ID as the 
cluster ID. 
If more than one RR exists in a 
cluster, use this command to 
configure the same cluster ID 
for all RRs in the cluster to 
avoid routing loops.
 
9.  Configure a filtering policy 
to filter the routes to be 
advertised.  filter-policy {
 acl-number |  ip-prefix 
ip-prefix-name  } export [ direct  | isis  
process-id  | ospf  process-id  | rip 
process-id  | static  ]  Optional. 
By default, BGP does not filter 
the routes to be advertised. 
10.
 Configure a filtering policy 
to filter the received routes.  filter-policy 
{ acl-number  | ip-prefix 
ip-prefix-name  } import  Optional. 
By default, BGP does not filter 
the received routes. 
 
Resetting BGP connections 
When BGP configuration changes, you can use the soft reset function or reset BGP connections to make 
new configurations take effect. Soft reset requires that BGP peers have route refreshment capability 
(supporting Route-Refresh messages). 
 
Step Command Remarks 
1.
  Soft reset the BGP connections 
in a specified VPN instance.  refresh bgp vpn-instance
 
vpn-instance-name  { ip-address |  
all  |  external  | group  
group-name  } { export |  import }  Available in user view 
2.
  Reset BGP connections of a 
VPN instance.  reset bgp vpn-instance 
vpn-instance-name 
{ as-number  | 
ip-address | all  | external | group 
group-name  }  Available in user view
    Add page 1097 to Favourites
    image text
    Enable zoom 
    							 408 
Displaying and maintaining MCE 
 
Task Command  Remarks 
Display information about the 
routing table associated with a 
VPN instance. display ip routing-table vpn-instance 
vpn-instance-name
 [ verbose ] [ verbose  ] 
[ |  { begin  | exclude |  include } 
regular-expression  ]  Available in any view
 
Display information about a 
specific VPN instance or all VPN 
instances.  display ip vpn-instance
 [ instance-name 
vpn-instance-name  ] [ | { begin |  exclude | 
include  } regular-expression ]  Available in any view
 
Display information about the FIB 
of a VPN instance.  display fib
 vpn-instance  vpn-instance-name  
[  acl  acl-number  | ip-prefix ip-prefix-name  ] 
[ |  { begin |  exclude | include } 
regular-expression  ]  Available in any view 
Display information about the FIB 
of a VPN instance that matches the 
specified destination IP address.  display
 fib vpn-instance  vpn-instance-name 
ip-address [ mask  | mask-length ] [ |  
{  begin |  exclude | include  } 
regular-expression  ]  Available in any view 
Display information about a 
specific peer group or all BGP 
VPNv4 peer groups.  display bgp vpnv4 
vpn-instance 
vpn-instance-name  group  [ group-name  ] 
[ |  { begin |  exclude | include } 
regular-expression  ]  Available in any view
 
Display information about BGP 
VPNv4 routes injected into a 
specific VPN instance or all VPN 
instances.  display bgp vpnv4 
vpn-instance 
vpn-instance-name  network  [ | { begin | 
exclude  | include  } regular-expression ]  Available in any view
 
Display BGP VPNv4 AS path 
information.  display bgp vpnv4 
vpn-instance 
vpn-instance-name  paths  
[ as-regular-expression  | { | { begin | 
exclude  | include  } regular-expression  } ]  Available in any view
 
Display information about BGP 
VPNv4 peers.  display bgp vpnv4 
vpn-instance 
vpn-instance-name  peer [ group-name  
log-info  | ip-address  { log-info  | verbose  } 
|  verbose  ] [ | { begin | exclude | include  } 
regular-expression  ]  Available in any view
    Add page 1098 to Favourites
    image text
    Enable zoom 
    							 409 
Task Command  Remarks 
Display the BGP VPNv4 routing 
information of a specific VPN 
instance. display bgp vpnv4 vpn-instance
 
vpn-instance-name  routing-table 
[ [ network-address  [ {  mask  | mask-length  } 
[ longer-prefixes  ] ] | as-path-acl 
as-path-acl-number  | cidr  | community 
[  aa:nn ]& [  no-advertise | 
no-export  | no-export-subconfed  ] * 
[ whole-match  ] | community-list 
{  basic-community-list-number  
[ whole-match  ] | 
adv-community-list-number  }& | 
dampened  | dampening parameter  | 
different-origin-as  | flap-info  
[ network-address  [ { mask  | mask-length  } 
[ longer-match  ] ] | as-path-acl 
as-path-acl-number  ] | peer  ip-address  
{  advertised-routes  | received-routes } | 
statistic  ] [ | { begin |  exclude | include  } 
regular-expression  ] | [ flap-info ] 
regular-expression  as-regular-expression  ]
 
Available in any view  
Clear the route flap dampening 
information of a VPN instance.  reset bgp vpn-instance 
vpn-instance-name 
dampening  [ network-address [  mask | 
mask-length  ]  Available in user view 
Clear route flap history information 
about a BGP peer of a VPN 
instance.  reset bgp vpn-instance 
vpn-instance-name 
ip-address  flap-info 
reset bgp vpn-instance  vpn-instance-name 
flap-info  [ ip-address  [ mask | 
mask-length ] | as-path-acl 
as-path-acl-number  | regexp 
as-path-regexp  ]  Available in user view 
 
For commands to display information about a routing table, see 
Layer 3—IP Routing Command 
Reference . 
MCE configuration examples 
Using OSPF to advertise VPN routes to the PE 
Network requirements 
As shown in  Figure 129, the MCE device is connected to VPN 1 through VL AN -inter face 10 and to VPN 
2 through VLAN-interface 20. RIP runs in VPN 2. 
Configure the MCE device to separate routes from different VPNs and advertise the VPN routes to PE 1 
through OSPF.
    Add page 1099 to Favourites
    image text
    Enable zoom 
    							 410 
Figure 129 Network diagram 
 
 
Configuration procedure 
Assume that the system name of the MCE device is MCE, the system names of the edge devices of VPN 
1 and VPN 2 are VR1 and VR2, respectively, and the system name of PE 1 is PE1. 
1. Configure the VPN instances on the MCE and PE 1: 
# On the MCE, configure VPN instances  vpn1 and  vpn2, and specify an RD and route targets for 
each VPN instance.  
 system-view 
[MCE] ip vpn-instance vpn1 
[MCE-vpn-instance-vpn1] route-distinguisher 10:1 
[MCE-vpn-instance-vpn1] vpn-target 10:1 
[MCE-vpn-instance-vpn1] quit 
[MCE] ip vpn-instance vpn2 
[MCE-vpn-instance-vpn2] route-distinguisher 20:1 
[MCE-vpn-instance-vpn2] vpn-target 20:1 
[MCE-vpn-instance-vpn2] quit 
# Create VLAN 10, add port GigabitEthernet 1/0/ 1 to VLAN 10, and create VLAN-interface 10. 
[MCE] vlan 10 
[MCE-vlan10] port gigabitethernet 1/0/1 
[MCE-vlan10] quit 
[MCE] interface vlan-interface 10 
# Bind VLAN-interface 10 with VPN instance vpn1, and configure an IP address for 
VLAN-interface 10. 
[MCE-Vlan-interface10] ip binding vpn-instance vpn1
    Add page 1100 to Favourites
    image text
    Enable zoom 
    							 411 
[MCE-Vlan-interface10] ip address 10.214.10.3 24  
# Configure VLAN 20, add port GigabitEthernet 1/0/2 to VLAN 20, bind VLAN-interface 20 with 
VPN instance  vpn2, and specify an IP address for VLAN-interface 20.  
[MCE-Vlan-interface10] quit 
[MCE] vlan 20 
[MCE-vlan20] port gigabitethernet 1/0/2 
[MCE-vlan20] quit 
[MCE] interface vlan-interface 20 
[MCE-Vlan-interface20] ip binding vpn-instance vpn2 
[MCE-Vlan-interface20] ip address 10.214.20.3 24 
[MCE-Vlan-interface20] quit 
# On PE 1, configure VPN instances  vpn1 and vpn2 , specify an RD and route targets for each VPN 
instance. 
 system-view 
[PE1] ip vpn-instance vpn1 
[PE1-vpn-instance-vpn1] route-distinguisher 30:1 
[PE1-vpn-instance-vpn1] vpn-target 10:1 
[PE1-vpn-instance-vpn1] quit 
[PE1] ip vpn-instance vpn2 
[PE1-vpn-instance-vpn2] route-distinguisher 40:1 
[PE1-vpn-instance-vpn2] vpn-target 20:1 
[PE1-vpn-instance-vpn2] quit 
2.  Configure routing between the MCE and VPN sites: 
The MCE is connected to VPN 1 directly, and no routing protocol is enabled in VPN 1. Therefore, 
you can configure static routes. 
# On VR 1, assign IP addre ss 10.214.10.2/24 to the inte rface connected to MCE and 
192.168.0.1/24 to the interface connected to VPN 1.  Add ports to VLANs correctly. (Details not 
shown.) 
# On VR 1, configure a default route with the next hop as 10.214.10.3. 
 system-view 
[VR1] ip route-static 0.0.0.0 0.0.0.0 10.214.10.3 
# On the MCE, configure a static route to 192. 168.0.0/24, specify the next hop as 10.214.10.2, 
and bind the static route with VPN instance  vpn1. 
[MCE] ip route-static vpn-instance vpn1 192.168.0.0 24 10.214.10.2 
# On the MCE, display the routing info rmation maintained for VPN instance vpn1. 
[MCE] display ip routing-table vpn-instance vpn1 
Routing Tables: vpn1 
         Destinations : 5        Routes : 5 
Destination/Mask    Proto  Pre  Cost         NextHop         Interface 
10.214.10.0/24      Direct 0    0            10.214.10.3     Vlan10 
10.214.10.3/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 
192.168.0.0/24      Static 60   0            10.214.10.2     Vlan10 
The output shows that the MCE has a static route for VPN instance  vpn1.
    All HP manuals Comments (0)

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