Symptom
Nexus recalibrates it's RR status only when command 'no route-reflector-client' is executed. If we remove the Route Reflector Client by doing "no neighbor x.x.x.x", then the switch will still believe it is a route reflector and the following will be seen under the BGP process:
switch# sh bgp process vrf default | beg VPNv4
Information for address family VPNv4 Unicast in VRF default
Table Id : 0x7
Table state : UP
Peers Active-peers Routes Paths Networks Aggregates
1 0 0 0 0 0
Redistribution
None
Is a Route-reflector <<<-----------------
Conditions
Neighbor is configured as RR client and is removed with command "no neighbor X.X.X.X" prior removing RR client configuration
Workaround
Configure a dummy neighbor as Route Reflector Client, and then do 'no route-reflector-client' before removing the dummy neighbor from the configuration.
Further Problem Description
There is no impact other then we will keep bigger bgp database than needed
for example we will keep all vpnv4 prefixes even if we do not export them to any local vrf
