New DC added but only picks up a few devices after rebalancing.
Article ID: 115095
Updated On:
Products
CA Infrastructure Management
CA Performance Management - Usage and Administration
Issue/Introduction
Upgraded CAPM to 3.5, then added a new DC (there was previously just a single DC).
Rebalancing caused only about 35 devices to move to the new DC.
Manual rebalancing has no effect.
Customer firewall team states that there are no FW-related impediments to the rebalancing.
Similarly, customer network team states that the devices currently on the original DC should all respond to the new DC.
Rebalancing caused only about 35 devices to move to the new DC.
Manual rebalancing has no effect.
Customer firewall team states that there are no FW-related impediments to the rebalancing.
Similarly, customer network team states that the devices currently on the original DC should all respond to the new DC.
Environment
CAPM 3.x
Resolution
The new DC is unable to SNMP to any devices, and only could ping 35.
We tried
snmpget -v 2c -c <string> <target ip> 1.3.6.1.2.1.1.2.0
snmpget -v 2c -c <string> <target ip> 1.3.6.1.2.1.1.3.0
Works from old DC to all tested targets
Fails on new DC to all tested targets
Likely acl issue, may be firewall.
We tried
snmpget -v 2c -c <string> <target ip> 1.3.6.1.2.1.1.2.0
snmpget -v 2c -c <string> <target ip> 1.3.6.1.2.1.1.3.0
Works from old DC to all tested targets
Fails on new DC to all tested targets
Likely acl issue, may be firewall.
Feedback
Yes
No
Powered by
