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

6-35
To do… Use the command… Remarks
Configure the system to use the
local address as the next hop of a
route to be advertised to a
specified peer or peer group
peer { group-name | ip-address }
next-hop-local
Optional
By default, the system uses the
local address as the next hop of a
route to be advertised to an EBGP
peer. Note that in the inter-provider
VPN option C solution, you need to
configure the peer { group-name |
ip-address } next-hop-invariable
command on the RR for multi-hop
EBGP neighbors and reflector
clients to ensure that the next hop
of a VPN route will not be
changed.
Configure the system to be the RR
and set a peer or peer group as
the client of the RR
peer { group-name | ip-address }
reflect-client
Optional
By default, no RR or RR client is
configured.
Enable the ORF capability for a
BGP peer/peer group
peer { group-name | ip-address }
capability-advertise orf ip-prefix
{ both | receive | send }
Optional
By default, the ORF capability is
disabled on a BGP peer or peer
group.
Enable VPN target filtering for
received VPNv4 routes
policy vpn-target
Optional
Enabled by default
Enable route reflection between
clients
reflect between-clients
Optional
Enabled by default
Specify the cluster ID of the RR
reflector cluster-id { cluster-id |
ip-address }
Optional
Router ID of an RR in the cluster
by default
Create an RR reflection policy
rr-filter
extended-community-list-number
Optional
For information about BGP-L2VPN address family and VPLS address family, see MPLS L2VPN
Configuration Commands and VPLS Configuration Commands in the MPLS Command Reference.
Configuring specific routing features for BGP-VPNv4 subaddress family
Follow these steps to configure specific routing features for BGP-VPNv4 subaddress family: