190
7. Advertise routes to the UPE.
•
route to the UPE:
peer { group-name |
ip-address [ mask-length ] }
default-route-advertise
vpn-instance
vpn-instance-name
• Ad
vertise routes permitted
by a routing policy to the
UPE:
peer { group-name |
ip-address [ mask-length ] }
upe route-policy
route-policy-name export
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 is present in the
local routing table. However, if the
specified peer is not a UPE, the
command does not advertise a
default route.
8. Return to BGP view.
quit
N/A
9. Create a BGP-VPN instance,
and enter BGP-VPN
instance view.
ip vpn-instance
vpn-instance-name
By default, no BGP-VPN instance
is created.
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.
Before you configure an OSPF sham link, complete the following tasks:
• Configure basic MPLS L3VPN (OSPF is used between PE and CE).
• Configure OSPF in the LAN where customer CEs reside.
Configuring a loopback interface
1. Enter system view.
N/A
2. Create a loopback interface
and enter loopback interface
view.
interface-number
By default, no loopback interface
is created.
3. Associate
interface with
instance.
ip binding vpn-instance
vpn-instance-name
By default, the interface is
associated with no VPN instance.
4. Configure the address of the
loopback interface.
ip address
ip-address
{ mask |
mask-length }
N/A
To Next Page
Loading...
Need help?
General