3com S7906E インストール手順

 

1-35 

Apply a routing policy to a peer 
or peer group 

peer { group-name | 
ip-address } route-policy 
route-policy-name { export | 
import } 

Optional 

By default, no routing policy is 
applied to a peer or peer group. 

 

For information about BGP routing, refer to BGP Configuration in the IP Routing Volume. 

 

If the MPLS backbone on which the VPN routes rely spans multiple ASs, you need to configure 

inter-provider VPN. 

There are three inter-provider VPN solutions. You can choose them as required. 

Before configuring inter-provider VPN, complete these tasks: 

z 

Configuring IGP for the MPLS backbones in each AS to implement IP connectivity of the 

backbones in the AS 

z 

Configuring basic MPLS capabilities for the MPLS backbones of each AS 

z 

Configuring MPLS LDP for the MPLS backbones so that LDP LSPs can be established 

z 

Configuring basic MPLS L3VPN for each AS 

 

When configuring basic MPLS L3VPN for each AS, specific configurations may be required on PEs or 

ASBR-PEs. This depends on the inter-provider VPN solution selected. 

 

Inter-provider VPN option A applies to scenarios where the number of VPNs and that of VPN routes on 

the PEs are relatively small. It is simple to implement. 

To configure inter-provider VPN option A, you only need to: 

z 

Configure basic MPLS L3VPN on each AS. 

z 

Configure each ASBR, taking the peer ASBR PE as its CE. 

In other words, configure VPN instances for PEs and ASBR PEs respectively.  The VPN instance for PE 

is used to allow CEs to access the network, while that for ASBR-PE is used to access its peer 

ASBR-PE.