Configuring An Ospf Sham Link - HP FlexNetwork 10500 Series Configuration Manual

Step
6. Enter interface view of the
interface connected to an
internal router of the AS.
7. Enable MPLS on the
interface.
8. Enable MPLS LDP on the
interface.
9. Return to system view.
10. Enter interface view of the
interface connected to the
remote ASBR.
11. Enable MPLS on the
interface.
12. Return to system view.
13. Enter BGP instance view.
14. Configure the PE in the same
AS as an IBGP peer.
15. Configure the ASBR in
another AS as an EBGP
peer.
16. Create the BGP IPv4 unicast
address family and enter its
view.
17. Enable exchange of IPv4
unicast routes with the PE in
the same AS and the ASBR
in another AS.
18. Enable exchange of labeled
IPv4 routes with the PE in the
same AS and the ASBR in
another AS.
19. Configure the ASBR to set
itself as the next hop of
routes advertised to the PE
in the local AS.
20. (Optional.) Apply a routing
policy to routes incoming
from or outgoing to a peer or
peer group.

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
interface interface-type
interface-number
mpls enable
mpls ldp enable
quit
interface interface-type
interface-number
mpls enable
quit
bgp as-number [ instance
instance-name ]
peer { group-name | ipv4-address
[ mask-length ] } as-number
as-number
peer { group-name | ipv4-address
[ mask-length ] } as-number
as-number
address-family ipv4 [ unicast ]
peer { group-name | ipv4-address
[ mask-length ] } enable
peer { group-name | ipv4-address
[ mask-length ] }
label-route-capability
peer { group-name | ipv4-address
[ mask-length ] } next-hop-local
peer { group-name | ipv4-address
[ mask-length ] } route-policy
route-policy-name { export |
import }
215
Remarks
N/A
By default, MPLS is disabled on
the interface.
By default, MPLS LDP is disabled
on the interface.
N/A
N/A
By default, MPLS is disabled on
the interface.
N/A
N/A
By default, no BGP peers exist.
By default, no BGP peers exist.
By default, the BGP IPv4 unicast
address family is not created.
By default, BGP does not
exchange IPv4 unicast routes with
any peer.
By default, BGP cannot advertise
labeled routes to any IPv4 peer or
peer group.
By default, BGP does not use its
address as the next hop of routes
advertised to an IBGP peer or
peer group.
By default, no routing policy is
applied.