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 1111 to Favourites
    image text
    Enable zoom 
    							 422 
Configuring OSPFv3 between IPv6 MCE and VPN site 
An OSPFv3 process belongs to the public network or a single IPv6 VPN instance. If you create an 
OSPFv3 process without binding it to an IPv6 VPN in stance, the process belongs to the public network. 
By configuring OSPFv3 process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of 
different IPv6 VPNs to be exchanged between the  IPv6 MCE and the sites through different OSPFv3 
processes, ensuring the separation and security of IPv6 VPN routes. 
To configure OSPFv3 between IPv6 MCE and VPN site: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Create an OSPFv3 process for 
a VPN instance and enter 
OSPFv3 view.  ospfv3
 [ process-id  ] vpn-instance 
vpn-instance-name   Perform this configuration on the 
IPv6 MCE. On a VPN site, 
configure normal OSPFv3. 
3.
  Set the router ID. 
router-id router-id   N/A 
4.  Redistribute remote site routes 
advertised by the PE..  import-route 
protocol [ process-id 
|  allow-ibgp  ] [ cost  value  | 
route-policy  route-policy-name  | 
type  type  ] *
  By default, no route of any other 
routing protocol is redistributed 
into OSPFv3.
 
5.  Return to system view. 
quit  N/A 
6.
  Enter interface view.  interface
 interface-type 
interface-number   N/A 
7.
  Enable OSPFv3 on the 
interface.  ospfv3 
process-id  area  area-id  
[ instance  instance-id
 ]
  By default, OSPFv3 is disabled on 
an interface. 
 
 
NOTE: 
Deleting a VPN instance also deletes all re lated OSPFv3 processes at the same time. 
 
Configuring IPv6 IS-IS between IPv6 MCE and VPN site 
An IPv6 IS -IS process belongs to the public network or a single IPv6 VPN instance. If you create an IPv6 
IS-IS process without binding it to an IPv6 VPN in stance, the process belongs to the public network. 
By configuring IPv6 IS-IS process-to-IPv6 VPN instance bindings on an IPv6 MCE, you allow routes of 
different IPv6 VPNs to be exchanged between the IP v6 MCE and the sites through different IPv6 IS-IS 
processes, ensuring the separation and security of IPv6 VPN routes. 
To configure IPv6 IS-IS between IPv6 MCE and VPN site: 
 
Step Command Remarks 
1.   Enter system view. 
system-view  N/A 
2.  Create an IPv6 IS-IS process 
for a VPN instance and enter 
IS-IS view.  isis
 [ process-id  ] vpn-instance  
vpn-instance-name   Perform this configuration on the 
IPv6 MCE. On a VPN site, 
configure normal IPv6 IS-IS. 
3.
  Configure a network entity 
title for the IS-IS process.  network-entity 
net  Not configured by default.
    Add page 1112 to Favourites
    image text
    Enable zoom 
    							 423 
Step Command Remarks 
4.  Enable the IPv6 capacity for 
the IPv6 IS-IS process.  ipv6 enable 
Disabled by default. 
5.  Redistribute remote site routes 
advertised by the PE.  ipv6 import-route 
protocol 
[ process-id  ] [ allow-ibgp  ] [ cost 
cost | [  level-1 | level-1-2  | 
level-2  ] | route-policy 
route-policy-name  | tag  tag ] *  Optional. 
By default, no routes from any 
other routing protocol are 
redistributed to IPv6 IS-IS. 
If you do not specify the route level 
in the command, redistributed 
routes are added to the level-2 
routing table by default. 
6.
  Return to system view. 
quit  N/A 
7.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
8.
  Enable the IPv6 IS-IS process 
on the interface.  isis ipv6 enable
 [ process-id ]  Disabled by default. 
 
Configuring EBGP between IPv6 MCE and VPN site 
To use EBGP for exchanging routing information between an IPv6 MCE and IPv6 VPN sites, you must 
configure a BGP peer for each IPv6 VPN instance on the IPv6 MCE, and redistribute the IGP routes of 
each VPN instance on the IPv6 VPN sites. 
If EBGP is used for route exchange, you also can config ure filtering policies to filter the received routes 
and the routes to be advertised. 
1.  Configure the IPv6 MCE:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enter BGP view. 
bgp as-number  N/A 
3.  Enter IPv6 BGP-VPN instance 
view.  ipv6-family vpn-instance
 
vpn-instance-name   N/A 
4.
  Specify an IPv6 BGP peer in 
an AS.  peer 
ipv6-address  as-number 
as-number   N/A 
5.
  Redistribute remote site routes 
advertised by the PE.  import-route 
protocol [ process-id  
[ 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 {
 acl6-number  | 
ipv6-prefix  ip-prefix-name  } export 
[ direct  | isisv6  process-id  | ripng  
process-id  | static  ]  Optional. 
By default, the IPv6 MCE does not 
filter the routes to be advertised. 
7.
  Configure a filtering policy to 
filter the received routes.  filter-policy 
{ acl6-number  | 
ipv6-prefix ip-prefix-name  } import
 
Optional. 
By default, the IPv6 MCE does not 
filter the received routes.
    Add page 1113 to Favourites
    image text
    Enable zoom 
    							 424 
 NOTE: 
After you configure an IPv6 BGP VPN instance, the IPv6 BGP  route exchange for the IPv6 VPN instance is
the same with the normal IPv6 BGP VPN route exchange.  
 
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.  Enter IPv6 address family 
view.  ipv6-family 
N/A 
4.  Configure the IPv6 MCE as 
the EBGP peer.  peer 
ipv6-address  as-number 
as-number   N/A 
5.
  Redistribute the IGP routes of 
the VPN.  import-route 
protocol [ process-id  
[ med  med-value  |  route-policy 
route-policy-name  ] * ]  Optional. 
By default, no route redistribution 
is configured. 
A VPN site must advertise the IPv6 
VPN network addresses it can 
reach to the connected IPv6 MCE.
 
 
Configuring routing between IPv6 MCE and PE 
IPv6 MCE-PE routing configuration includes these tasks: 
•
  Bind the IPv6 MCE-PE interfaces to IPv6 VPN instances 
•   Perform routing configurations 
•   Redistribute IPv6 VPN routes into the routing pr otocol running between the IPv6 MCE and the PE. 
Configuring IPv6 static routing between IPv6 MCE and PE 
To configure IPv6 static routing between IPv6 MCE and PE:  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Configure an IPv6 static 
route for an IPv6 VPN 
instance. 
• ipv6 route-static  ipv6-address prefix-length 
{  interface-type  interface-number 
[ next-hop-address  ] | next-hop-address  | 
vpn-instance  d-vpn-instance-name 
nexthop-address  } [ preference preference-value  ] 
• 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  ] User either 
command.
    Add page 1114 to Favourites
    image text
    Enable zoom 
    							 425 
Configuring RIPng between IPv6 MCE and PE 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Create a RIPng process for an 
IPv6 VPN instance and enter 
RIPng view.  ripng [ process-id 
] vpn-instance  
vpn-instance-name   N/A 
3.
  Redistribute the VPN routes.  import-route 
protocol [  process-id  ] 
[  allow-ibgp  ] [ cost cost | 
route-policy route-policy-name  ] *  By default, no route of any other 
routing protocol is redistributed 
into RIPng. 
4.
  Configure the default cost 
value for the redistributed 
routes.  default cost 
value  Optional. 
0 by default. 
5.
  Return to system view. 
quit  N/A 
6.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
7.
  Enable the RIPng process on 
the interface.  ripng
 process-id  enable  Disabled by default. 
 
Configuring OSPFv3 between IPv6 MCE and PE 
 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Create an OSPFv3 process for 
an IPv6 VPN instance and 
enter OSPFv3 view.  ospfv3
 [ process-id  ] vpn-instance 
vpn-instance-name   N/A 
3.
  Set the router ID. 
router-id router-id   N/A 
4.  Redistribute the VPN routes.  import-route 
protocol [ process-id 
|  allow-ibgp  ] [ cost  value  | 
route-policy  route-policy-name  | 
type  type  ] *
  By default, no route of any other 
routing protocol is redistributed 
into OSPFv3.
 
5.  Configure a filtering policy to 
filter the redistributed routes.  filter-policy { acl6-number
 | 
ipv6-prefix  ipv6-prefix-name  } 
export  [ bgp4+  | direct  | isisv6 
process-id  | ospfv3  process-id  |  
ripng  process-id  | static ]
  Optional. 
By default, redistributed routes are 
not filtered.
 
6.  Return to system view. 
quit  N/A 
7.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
8.
  Enable the OSPFv3 process 
on the interface.  ospfv3 
process-id  area  area-id  
[ instance  instance-id
 ]  Disabled by default. 
 
Configuring IPv6 IS-IS between IPv6 MCE and PE
    Add page 1115 to Favourites
    image text
    Enable zoom 
    							 426 
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Create an IS-IS process for an 
IPv6 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.  Enable the IPv6 capacity for 
the IS-IS process.  ipv6 enable 
Disabled by default. 
5.  Redistribute the VPN routes.  ipv6 import-route 
protocol 
[ process-id  ] [ allow-ibgp  ] [ cost 
cost | [  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. 
6.
  Configure a filtering policy to 
filter the redistributed routes.  ipv6 filter-policy
 { acl6-number | 
ipv6-prefix ipv6-prefix-name  | 
route-policy  route-policy-name  } 
export [ protocol  [ process-id ] ]  Optional. 
By default, IPv6 IS-IS does not filter 
redistributed routes. 
7.
  Return to system view. 
quit  N/A 
8.  Enter interface view.  interface 
interface-type 
interface-number   N/A 
9.
  Enable IPv6 for the IS-IS 
process on the interface.  isis ipv6 enable
 [ process-id ]  Disabled by default. 
 
Configuring EBGP between IPv6 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 IPv6 BGP-VPN 
instance view.  ipv6-family vpn-instance
 vpn-instance-name N/A 
4.   Configure the PE as the 
EBGP peer.  peer 
ipv6-address  as-number as-number  N/A 
5.  Redistribute the VPN 
routes.  import-route 
protocol [ process-id  [ 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 {
 acl6-number  | ipv6-prefix  
ip-prefix-name  } export [ direct  | isisv6  
process-id  | ripng  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 
{ acl6-number  | ipv6-prefix 
ip-prefix-name  } import  Optional. 
By default, BGP does not filter 
the received routes.
    Add page 1116 to Favourites
    image text
    Enable zoom 
    							 427 
 NOTE: 
IPv6 BGP runs within a VPN in the same wa y as it runs within a public network.  
 
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). 
Use the following commands to hard reset or soft reset BGP connections: 
 
Step Command Remarks 
1.  Soft reset the IPv6 BGP 
connections in a VPN 
instance.  refresh bgp ipv6 vpn-instance
 
vpn-instance-name  { ipv6-address 
|  all  | external  } { export | import  }
 
Available in user view 
2.  Hard reset the IPv6 BGP 
connections of a VPN 
instance.  reset bgp ipv6 vpn-instance
 
vpn-instance-name  { as-number  | 
ipv6-address |  all |  external  }  Available in user view
 
 
Displaying information about IPv6 MCE 
 
Task Command  Remarks 
Display information about a 
specific 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 IPv6 
FIB of a VPN instance.  display ipv6 fib
 vpn-instance  
vpn-instance-name  [ acl6 acl6-number  | 
ipv6-prefix  ipv6-prefix-name  ] [ | { begin | 
exclude  | include  } regular-expression  ]  Available in any view 
Display a VPN instance’s FIB 
entries that match the specified 
destination IPv6 address.  display
 ipv6  fib vpn-instance  
vpn-instance-name  ipv6-address 
[ prefix-length ] [ |  { begin | exclude | 
include  } regular-expression  ]  Available in any view 
Display information about BGP 
VPNv6 peers established between 
PEs.  display bgp vpnv6 all peer 
[ ipv4-address 
verbose  | verbose  ] [ | { begin  | exclude  | 
include  } regular-expression  ]  Available in any view 
Display information about IPv6 
BGP peers established between the 
PE and CE in a VPN instance.  display bgp vpnv6 
vpn-instance 
vpn-instance-name  peer [ ipv6-address 
verbose  | verbose  ] [ | { begin  | exclude  | 
include  } regular-expression  ]  Available in any view 
Display all BGP VPNv6 routing 
information.  display bgp vpnv6 
all routing-table  
[ network-address prefix-length  
[ longer-prefixes  ] | peer ip-address 
{  advertised-routes  | received-routes } 
[  statistic  ] | statistic  ] [ | { begin  | exclude  
|  include  } regular-expression  ]  Available in any view
    Add page 1117 to Favourites
    image text
    Enable zoom 
    							 428 
Task Command  Remarks 
Display the BGP VPNv6 routing 
information of a specified RD. display bgp vpnv6 route-distinguisher
 
route-distinguisher  routing-table  
[  network-address prefix-length  ] [ | { begin  
|  exclude  | include  } regular-expression  ]
 
Available in any view 
Display the BGP VPNv6 routing 
information of a VPN instance.  display bgp vpnv6 vpn-instance
 
vpn-instance-name  routing-table 
[ network-address prefix-length  
[ longer-prefixes  ] | peer ipv6-address  
{  advertised-routes  | received-routes  } ] [ | 
{  begin |  exclude | include  } 
regular-expression  ]  Available in any view 
 
For commands that display information about a routing table, see 
Layer 3—IP Routing Command 
Reference . 
IPv6 MCE configuration examples 
Using IPv6 ISIS to advertise VPN routes to the PE 
Network requirements 
As shown in  Figure 131, the IPv6 MCE device is connected to VPN 1 through VL AN-interface 10 and to 
VPN 2 through VLAN-interface 20. RIPng is used in VPN 2. 
Configure the IPv6 MCE to separate routes from differ ent VPNs and advertise VPN routes to PE 1 through 
OSPFv3.
    Add page 1118 to Favourites
    image text
    Enable zoom 
    							 429 
Figure 131 Network diagram 
 
 
Configuration procedure 
Assume that the system name of the IPv6 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 a 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 
CE
VPN 1Site 2
CE
VPN 2
Site 1 
PE 1 PE 3
PE 2
VPN 2
2012::/64 VR 2
VPN 1 
2012:1::/64
VR 1 MCE
GE1/0/1
Vlan-int10
2001:1::1/64 GE1/0/1
Vlan-int30: 30::2/64
Vlan-int40: 40::2/64
GE1/0/3
Vlan-int30: 30::1/64
Vlan-int40: 40::1/64
GE1/0/2
Vlan-int20
2002:1::1/64
Vlan-int10
2001:1::2/64
Vlan-int20
2002:1::2/64
Vlan-int11
2012:1::2/64
Vlan-int21
2012::2/64
    Add page 1119 to Favourites
    image text
    Enable zoom 
    							 430 
[MCE-vlan10] quit 
# Bind VLAN-interface 10 with VPN instance vpn1, and configure an IPv6 address for the VLAN 
interface. 
[MCE] interface vlan-interface 10 
[MCE-Vlan-interface10] ip binding vpn-instance vpn1 
[MCE-Vlan-interface10] ipv6 address 2001:1::1 64 
[MCE-Vlan-interface10] quit 
# Configure VLAN 20, add port GigabitEthernet 1/0/ 2 to VLAN 20, bind VLAN-interface 20 with 
VPN instance  vpn2, and assign an IPv6 address to VLAN-interface 20.  
[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] ipv6 address 2002:1::1 64 
[MCE-Vlan-interface20] quit 
# On PE 1, configure VPN instances  vpn1 and vpn2 , and 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 with VPN 1 directly, and no ro uting protocol is enabled in VPN 1. Therefore, 
you can configure IPv6 static routes. 
# On VR 1, assign IP address 2001:1::2/64  to the interface connected to the MCE and 
2012:1::2/64 to the interface connected to VPN 1.  Add ports to VLANs. (Details not shown.) 
# On VR 1, configure a default route,  specifying the next hop as 2001:1::1. 
 system-view 
[VR1] ipv6 route-static :: 0 2001:1::1 
# On the MCE, configure an IPv6 static route  to 2012:1::/64, specify the next hop as 2001:1::2, 
and bind the static route with VPN instance  vpn1. 
[MCE] ipv6 route-static vpn-instance vpn1 2012:1:: 64 vpn-instance vpn1 \
2001:1::2 
# Run RIPng in VPN 2. Configure RIPng process 20 for VPN instance  vpn2 on the MCE, so that the 
MCE can learn the routes of VPN 2 and add th em to the routing table of VPN instance vpn2. 
# Configure RIPng process 20, binding it with VPN instance  vpn2. 
[MCE] ripng 20 vpn-instance vpn2 
# Advertise subnet 2002:1::/64 through RIPng.
    Add page 1120 to Favourites
    image text
    Enable zoom 
    							 431 
[MCE] interface vlan-interface 20 
[MCE-Vlan-interface20] ripng 20 enable  
[MCE-Vlan-interface20] quit 
# On VR 2, assign IPv6 address 2002:1::2/64 to the interface connected to the MCE and 
2012::2/64 to the interface connected to VPN 2. (Details not shown.)  
# Configure RIPng, and advertise subnets 2012::/64 and 2002:1::/64.  
 system-view 
[VR2] ripng 20 
[VR2-ripng-20] quit 
[VR2] interface vlan-interface 20 
[VR2-Vlan-interface20] ripng 20 enable 
[VR2-Vlan-interface20] quit 
[VR2] interface vlan-interface 21 
[VR2-Vlan-interface21] ripng 20 enable 
[VR2-Vlan-interface21] quit 
# On MCE, display the routing tables of VPN instances  vpn1 and  vpn2. 
[MCE] display ipv6 routing-table vpn-instance vpn1 
 Routing Table : vpn1 
         Destinations : 5        Routes : 5 
 
Destination: ::1/128                                     Protocol  : Dir\
ect 
NextHop    : ::1                                         Preference: 0 
Interface  : InLoop0                                     Cost      : 0 
 
Destination: 2001:1::/64                                 Protocol  : Dir\
ect 
NextHop    : 2001:1::1                                   Preference: 0 
Interface  : Vlan10                                      Cost      : 0 
 
Destination: 2001:1::1/128                               Protocol  : Dir\
ect 
NextHop    : ::1                                         Preference: 0 
Interface  : InLoop0                                     Cost      : 0 
 
Destination: 2012:1::/64                                 Protocol  : Sta\
tic 
NextHop    : 2001:1::2                                   Preference: 60 \
Interface  : Vlan10                                      Cost      : 0 
 
Destination: FE80::/10                                   Protocol  : Dir\
ect 
NextHop    : ::                                          Preference: 0 
Interface  : NULL0                                       Cost      : 0 
 
[MCE] display ipv6 routing-table vpn-instance vpn2 
Routing Table : vpn2 
         Destinations : 5        Routes : 5 
 
Destination: ::1/128                                     Protocol  : Dir\
ect 
NextHop    : ::1                                         Preference: 0 
Interface  : InLoop0                                     Cost      : 0
    All HP manuals Comments (0)

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