225
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 specific
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.
In the inter-AS option C solution,
you must configure the
peer
{
group-name
|
ip-address
}
next-hop-invariable
command on
the RR for multi-hop eBGP
neighbors and reflector clients to
make sure 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 Outbound Route
Filtering (ORF) capability for a BGP
peer or 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
By default, an RR does not filter the
reflected routes.
With an RR reflection policy, only
iBGP routes whose Extended
Communities attribute matches the
specified one are reflected.
By configuring different RR
reflection policies on different RRs,
you can implement load balancing
among the RRs.
NOTE:
For information about VPLS address family, see
MPLS Command Reference.
Configuring specific routing features for BGP-VPNv4 subaddress family
To configure specific routing features for BGP-VPNv4 subaddress family:
To do…
Use the command…
Remarks
Enter system view
system-view
—