Configuring An Ospf Sham Link - HP HPE FlexNetwork MSR Router Series Configuration Manual

•
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 comparing 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.
As a best practice, do not configure the peer default-route-advertise vpn-instance and peer upe
route-policy commands at the same time.
To configure SPE for HoVPN:
Step
1. Enter system view.
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.
7. Advertise routes to the UPE.
8. Return to BGP view.
9. Create a BGP-VPN instance,
and enter BGP-VPN
instance view.

Configuring an OSPF sham link

When a backdoor link exists between the two sites of a VPN, you can create a sham link between
PEs to forward VPN traffic through the sham link on the backbone rather than the backdoor link. A
sham link is considered an OSPF intra-area route.
The source and destination addresses of the sham link must be loopback interface addresses with
32-bit masks. The loopback interfaces must be bound to VPN instances, and their addresses are
advertised through BGP.
Command
system-view
bgp as-number
peer { group-name | peer-address
[ mask-length ] } as-number
as-number
address-family vpnv4
peer { group-name | ip-address
[ mask-length ] } enable
peer { group-name | ip-address
[ mask-length ] } upe
•
Advertise a default VPN
route to the UPE:
peer { group-name |
ip-address [ mask-length ] }
default-route-advertise
vpn-instance
vpn-instance-name
•
Advertise routes permitted
by a routing policy to the
UPE:
peer { group-name |
ip-address [ mask-length ] }
upe route-policy
route-policy-name export
quit
ip vpn-instance
vpn-instance-name
227
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.
By default, no route is advertised
to the UPE.
Do not configure both commands.
The peer
default-route-advertise
vpn-instance command
advertises a default route using
the local address as the next hop
to the UPE, regardless of whether
the default route exists in the local
routing table. However, if the
specified peer is not a UPE, the
command does not advertise a
default route.
N/A
By default, no BGP-VPN instance
is created.