05-02-2014 08:54 AM
We have BNA (IBM re-branded) v12.0.2 pointed to our vCenter 5.1.0 instance. There are ~160 ESXi hosts that have been discovered.
Our VMware team has asked us to stop this monitoring as the connections from BNA to vCenter are quite aggressive and crash the vCenter services fairly regularly.
A Wireshark capture on our BNA box shows upwards of 40-50Mbps of traffic outbound to our vCenter server which seems almost absurdly high. Something must be wrong!
We're deleting the vCenter instance from our VM Manager list to hopefully stop the issue, but are wondering if we've misconfigured something or if this is expected behavior.
05-02-2014 09:51 AM
Quick follow-up on this.
Tried to delete our vCenter object from the VM Managers list. This operation timed out after a few minutes and retries elicited the same.
Ended up adding a null route to our vCenter host on the BNA host's routing table. This stopped all traffic to vCenter after which I was able to successfully delete the vCenter object from the VM Managers list.
Have a support ticket open so hopefully will figure out what was going on here.
02-04-2016 11:45 AM
We have BNA 12.4.1 and vCenter 5.5. We had a similar expirience when we tried to add our main vCenter to BNA. BNA logged into vCenter 150 times and broght vCenter to it's knees until we disabled the user in vCenter. Our main vCenter has 137 hosts and over 1300 VMs. Is there a way to limit the discover by BNA?