H3C Technologies H3C S7500E Series Switches - Manual (Page 262)

6-37
To do… Use the command… Remarks
Apply a route filtering policy based
on IP prefix list to a peer or peer
group
peer { group-name | ip-address }
ip-prefix prefix-name { export |
import }
Optional
By default, no route filtering policy
based on IP prefix list is applied to
a peer or peer group.
Specify not to change the next hop
of a route when advertising it to an
EBGP peer
peer { group-name | ip-address }
next-hop-invariable
Optional
By default, a device uses its
address as the next hop when
advertising a route to its EBGP
peer.
Specify the preferred value for the
routes received from the peer/peer
group
peer { group-name | ip-address }
preferred-value value
Optional
0 by default
Make BGP updates to be sent
carry no private AS numbers
peer { group-name | ip-address }
public-as-only
Optional
By default, a BGP update carries
private AS numbers.
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, see BGP Configuration in the Layer 3 - IP Routing Configuration
Guide .
Configuring Inter-Provider VPN
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.
Configuration Prerequisites
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