Configuring a routing policy on an asbr-pe, Configuring nested vpn – H3C Technologies H3C S12500-X Series Switches User Manual

Page 142

Advertising
background image

131

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter BGP view.

bgp as-number N/A

3.

Configure the PE in the same
AS as an IBGP peer.

peer { group-name | ip-address }
as-number as-number

By default, no BGP peer is created.

4.

Configure the peer ASBR-PE
as an EBGP peer.

peer { group-name | ip-address }
as-number as-number

By default, no BGP peer is created.

5.

Enter BGP IPv4 unicast

address family view.

address-family ipv4 [ unicast ]

N/A

6.

Enable exchange of IPv4
unicast routes with the peer or

peer group.

peer { group-name | ip-address }
enable

By default, BGP does not exchange
IPv4 unicast routes with any peer.

7.

Enable exchange of labeled
IPv4 routes with the PE in the

local AS and the peer

ASBR-PE.

peer { group-name | ip-address }
label-route-capability

By default, BGP does not advertise
labeled routes to any IPv4 peer or

peer group.

8.

Configure the ASBR-PE to set
itself as the next hop of routes

advertised to the PE in the

local AS.

peer { group-name | ip-address }
next-hop-local

By default, BGP does not use its
address as the next hop of routes
advertised to an IBGP peer or peer

group.

Configuring a routing policy on an ASBR-PE

A routing policy on an ASBR-PE does the following:

Assigns MPLS labels to routes received from the PEs in the local AS before advertising them to the
peer ASBR-PE.

Assigns new MPLS labels to labeled IPv4 routes advertised to PEs in the local AS.

Which IPv4 routes are assigned with MPLS labels depends on the routing policy. Only routes that meet

the criteria are assigned with labels. All other routes are still common IPv4 routes.
To configure a routing policy for inter-AS option C on an ASBR-PE:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Create a routing policy and
enter routing policy view.

route-policy route-policy-name
{ deny | permit } node

node-number

By default, no routing policy is
created.

3.

Match IPv4 routes carrying
labels.

if-match mpls-label

By default, no match criterion is
configured.

4.

Set labels for IPv4 routes.

apply mpls-label

By default, no apply clause is
configured.

Configuring nested VPN

For a network with many VPNs, nested VPN is a good solution to implement layered management of

VPNs and to conceal the deployment of internal VPNs.

Advertising