214
Use
undo reflector cluster-id
to remove the configured cluster ID.
By default, each route reflector uses its router ID as the cluster ID.
A route reflector reflects a route from a client to another client. The router ID of the route reflector is the ID
of the cluster. You can configure multiple route reflectors to improve network stability. If a cluster has
multiple route reflectors, you must use the
reflector cluster-id
command to specify the same cluster ID for
these route reflectors, in order to avoid routing loops.
Related commands:
reflect between-clients
and
peer reflect-client
.
Examples
# Specify 80 as the cluster ID for the route reflector, which is one of multiple route reflectors in the cluster.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] ipv4-family multicast
[Sysname-bgp-af-mul] reflector cluster-id 80
refresh bgp ipv4 multicast
Syntax
refresh bgp ipv4 multicast
{
all
|
ip-address
|
group
group-name
|
external
|
internal
} {
export
|
import
}
View
User view
Default level
2: Monitor level
Parameters
all
: Soft-resets all BGP connections.
ip-address
: Specifies an IPv4 MBGP peer by its IP address.
group-name
: Specifies an IPv4 MBGP peer group by its name, a string of 1 to 47 characters.
external
: Soft-resets eBGP connections.
internal
: Soft-resets iBGP connections.
export
: Specifies an outbound soft reset.
import
: Specifies an inbound soft reset.
Description
Use
refresh bgp ipv4 multicast
to perform a soft reset on specified IPv4 MBGP connections. This method
can also refresh the MBGP routing table and apply a new routing policy seamlessly.
To perform a BGP soft reset, be sure that all routers in the network support route refresh. If a router does
not support the route-refresh function, you must configure the
peer keep-all-routes
command to save all
the routing information of the peer before BGP soft reset.
Examples
# Soft-reset all the IPv4 MBGP connections.
<Sysname> refresh bgp ipv4 multicast all import
