Cisco Bug: CSCvj15424 - Replication IP not getting freedup up once the node goes down
Jun 29, 2018
- Cisco HyperFlex HX-Series
Known Affected Releases
2.5(1d) 2.6(1d) 3.0(1a)
Symptom: If we have replication configured on your cluster, and one node goes down due to some hardware/software issue and we install a new controller VM and try to add the node back it gives us an error that there are not enough replication ips. This is because the eth2 ip for the node which went down is not cleared. Conditions: 1. Replication network is configured on the cluster with just enough IPs in the IP pool as required. In other words, there are no more free replication IP's left in the pool. 2. A node in the cluster is temporarily down, and is replaced without doing an explicit node removal (stcli node remove). 3. The node is now repaired and is going to be put back into the cluster using node add ... -f 4. Since there are no more replication IP's left in the pool, node add fails with 'no more replication ip' message.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases