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

6-33
To do… Use the command… Remarks
Configure the PE as the peer
peer { group-name | ip-address }
as-number as-number
Required
Configure the route advertisement
behavior
import-route protocol
[ process-id ] [ med med-value |
route-policy route-policy-name ] *
Optional
A CE needs to advertise its routes
to the connected PE so that the PE
can advertise them to the peer CE.
z
Exchange of BGP routes for a VPN instance is the same as that of ordinary BGP routes.
z
The configuration task in BGP instance view is the same as that in BGP view. For detailed
information, see BGP Configuration in the Layer 3 - IP Routing Configuration Guide.
z
For information about BGP peer and peer group configuration, see BGP Configuration in the
Layer 3 - IP Routing Configuration Guide . This chapter does not differentiate between peer and
peer group.
Configuring Route Advertisement Between PEs
Follow these steps to configure route advertisement between PEs:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number Required
Configure the remote PE as the
peer
peer { group-name | ip-address }
as-number as-number
Required
Specify the source interface for
route updates
peer { group-name | ip-address }
connect-interface interface-type
interface-number
Required
By default, BGP uses the source
interface of the optimal route
update packet.
Enter BGP-VPNv4 subaddress
family view
ipv4-family vpnv4 [ unicast ] Required
Enable the exchange of
BGP-VPNv4 routing information
with the specified peer
peer { group-name | ip-address }
enable
Required
By default, BGP peers exchange
IPv4 routing information only.