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

6-39
To do… Use the command… Remarks
Enter BGP-VPNv4 subaddress
family view
ipv4-family vpnv4 —
Disable VPN target filtering for
VPNv4 routes
undo policy vpn-target
Required
By default, PE performs VPN
target filtering of the received
VPNv4 routes.
The routes surviving the filtering
will be added to the routing table,
and the others are discarded.
In the inter-provider VPN option B solution, the ASBR PEs need to maintain all VPNv4 routing
information and advertise the information to peer ASBR PEs. In this case, the ASBR PEs must receive
all VPNv4 routing information without performing VPN target filtering.
In the inter-provider VPN option B solution, for the same VPN, the VPN targets for the VPN instances
of the PEs must match those for the VPN instances of the ASBR-PEs in the same AS. This is true for
PEs in different ASs.
For inter-provider VPN option B, two configuration methods are available:
z
Do not change the next hop on an ASBR. With this method, you still need to configure MPLS LDP
between ASBRs.
z
Change the next hop on an ASBR. With this method, MPLS LDP is not required between ASBRs.
Currently, only the second method is supported. Therefore, MP-EBGP routes will get their next hops
changed by default before being redistributed to MP-IBGP. On conventional BGP, however, EBGP
routes to be advertised to IBGP do not have their next hops changed by default. If the next hops need
to be changed to the local addresses, you can configure the peer { ip-address | group-name }
next-hop-local command. For information about the command, see BGP Configuration in the Layer 3
- IP Routing Configuration Guide .
Configuring Inter-Provider VPN Option C
Configuring the PEs
You need to establish ordinary IBGP peer relationship between PEs and ASBR PEs in an AS and
MP-EBGP peer relationship between PEs of different ASs.