R3721-F3210-F3171-HP High-End Firewalls Network Management Command Reference-6PW101

415
Typcially, a cluster has only one route reflector. The router ID of the route reflector is the ID of the cluster.
You can configure multiple route reflectors to improve network stability. Using this command can
configure the identical cluster ID for all the route reflectors to avoid routing loops.
Related commands: reflect between-clients and peer reflect-client.
Examples
# Set the cluster ID to 80.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] reflector cluster-id 80
# In BGP-VPN instance view, set the cluster ID to 80. (vpn1 must have been created.)
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp] ipv4-family vpn-instance vpn1
[Sysname-bgp-vpn1] reflector cluster-id 80
refresh bgp
Syntax
refresh bgp { ip-address | all | group group-name | external | internal } { export | import }
View
User view
Default level
1: Monitor level
Parameters
ip-address: Soft-resets the BGP connection to a peer.
all: Soft-resets all BGP connections.
group-name: Soft-resets connections to a peer group, name of which is a sting of 1 to 47 characters.
external: eBGP connection.
internal: iBGP connection.
export: Outbound soft reset.
import: Inbound soft reset.
Description
Use refresh bgp to perform soft reset on specified BGP connections. Using this function can refresh the
BGP routing table without tearing down BGP connections and apply a newly configured routing policy.
To perform BGP soft reset, all routers in the network must support route-refresh. If a router not supporting
route-refresh exists in the network, you need to configure the peer keep-all-routes command to save all
routing updates before performing soft reset.
Examples
# Perform inbound BGP soft reset.
<Sysname> refresh bgp all import