Active IQ Unified Manager Discussions
Active IQ Unified Manager Discussions
Hi all,
I have one VM that balance had discovered on an ESX server. Before selecting it to be monitored, I destroyed the VM and reinstalled it in vCenter, same name, IP address etc.
No Balance finds the VM, but wont monitor it, I've used valid root and passowrd credentials (SSH likes them ok), but Balance complains that the server is unreachable.
I've rebooted balance, refreshed and rediscovered the ESX server, but still have the same problem.
Any ideas?
Thanks
Solved! See The Solution
Hi, unfortunately, there is not much detail to go on. My first guess is that the server is already monitored under a different name or by FQDN etc etc.
I would need to know a lot of things like; Is the ESX part of vcenter or is it stand alone? What version of Balance e.g. 4.1.0.220 ? What OS and version is the Server e.g. RedHat 6.1?
Balance identifies the VM's based off the UUID. It is the unique identifier similar to a mac address that prevents balance from mistakenly merging statistics of different servers. Is this server from a template? if so, was the SID regen?
Please see some suggestions that may help you;
1) Make sure the server is not already being monitored. balanced will prevent you from adding the same VM twice.
Rediscover your vcenter in Balance
2) Log into Balance web GUI as support | netapp
navigate to the Admin--> advanced --. diagnostics menu
select network tools.
Select the Ping option and enter the IP address for the server that is failing.
this will send a ping request from the Balance "linux" appliance.
3) Check the other network settings -- see the "nslookup" option under the diagnostic tools
Make sure you can Nslookup the IP->Fqdn-> and host name (all 3) and that they "ALL" resolve to the proper server.
4) Verify server in the same network- Domain - vlan etc.
5) is the Domain specified under the admin--> Configuration --> network --> Domain search address? e.g netapp.com mylab.org (select apply/update)
** multiple domains can be specified separated by a space.
6) Are there any Firewalls or ACL's?
Best regards,
Don Bourque
OnCommand Balance SE
Hi, unfortunately, there is not much detail to go on. My first guess is that the server is already monitored under a different name or by FQDN etc etc.
I would need to know a lot of things like; Is the ESX part of vcenter or is it stand alone? What version of Balance e.g. 4.1.0.220 ? What OS and version is the Server e.g. RedHat 6.1?
Balance identifies the VM's based off the UUID. It is the unique identifier similar to a mac address that prevents balance from mistakenly merging statistics of different servers. Is this server from a template? if so, was the SID regen?
Please see some suggestions that may help you;
1) Make sure the server is not already being monitored. balanced will prevent you from adding the same VM twice.
Rediscover your vcenter in Balance
2) Log into Balance web GUI as support | netapp
navigate to the Admin--> advanced --. diagnostics menu
select network tools.
Select the Ping option and enter the IP address for the server that is failing.
this will send a ping request from the Balance "linux" appliance.
3) Check the other network settings -- see the "nslookup" option under the diagnostic tools
Make sure you can Nslookup the IP->Fqdn-> and host name (all 3) and that they "ALL" resolve to the proper server.
4) Verify server in the same network- Domain - vlan etc.
5) is the Domain specified under the admin--> Configuration --> network --> Domain search address? e.g netapp.com mylab.org (select apply/update)
** multiple domains can be specified separated by a space.
6) Are there any Firewalls or ACL's?
Best regards,
Don Bourque
OnCommand Balance SE
Please see last response to your question. if the issue was resolved, Could you please mark as answered?
Thank you
best regards,
Don Bourque
Sorry, got lost in the post. Thanks for the answer/