Configuring Hovpn - HP MSR2000 Configuration Manual

Msr series mpls
Hide thumbs Also See for MSR2000:
Table of Contents

Advertisement

Step
10.
(Optional.) Configure the SoO
attribute for the BGP peer or
peer group.

Configuring HoVPN

In a HoVPN networking scenario, perform basic MPLS L3VPN settings on UPE and SPE. In addition,
configure the following settings on the SPE:
Specify the BGP peer or peer group as a UPE.
Advertise the default route of the specified VPN instance or routes matching a routing policy to the
UPE.
Create a BGP-VPN instance so the learned VPNv4 routes can be added into the BGP routing table
of the corresponding VPN instance by RTs.
Associating an interface with a VPN instance is not required on the SPE because no interface on
the SPE is directly connected to the customer network.
Follow these restrictions and guidelines when you configure HoVPN:
Do not configure the peer default-route-advertise vpn-instance and peer upe route-policy
commands at the same time.
Do not connect an SPE to a CE directly. If an SPE must be directly connected to a CE, the VPN
instance on the SPE and that on the UPE must be configured with different RDs.
To configure SPE for HoVPN:
Step
Enter system view.
1.
2.
Enter BGP view.
3.
Specify a BGP peer or peer
group.
4.
Enter BGP-VPN VPNv4 address
family view.
5.
Enable BGP VPNv4 route
exchange with the peer or peer
group.
6.
Specify the BGP peer or peer
group as a UPE.
Command
peer { group-name | ip-address }
soo site-of-origin
Command
system-view
bgp as-number
peer { group-name |
peer-address } as-number
as-number
address-family vpnv4
peer { group-name | ip-address }
enable
peer { group-name | ip-address }
upe
204
Remarks
By default, the SoO attribute is not
configured.
Remarks
N/A
N/A
By default, no BGP peer is
specified.
N/A
By default, BGP does not exchange
VPNv4 routes with any peer.
By default, no peer is a UPE.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents