This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

NPM 12.0 and VMware 6.5

havox over 7 years ago

We just upgraded our vCenter to 6.5 and now our Orion instance can't connect to it. Everything worked fine prior to the upgrade (5.5 before). In the Manage Nodes screen the credential validation under the VMware Polling Settings fails with the error, "Test Failed. Cannot login with selected vCenter or ESX credential."

- removed vCenter node and added back

- verified IP address was the same as before

- tried with full administrator account and it failed

- ICMP and Poll for VMware are only boxes checked

Any ideas here?

Thanks,

Jon

Top Replies

0 havox over 7 years ago

The new VMware appliance is Linux-based, so does that change the way NPM behaves?
Cancel
Vote Up 0 Vote Down

Cancel
0 damien.solodow over 7 years ago

Is this on the vCenter Server node or on the ESXi nodes?
Cancel
Vote Up 0 Vote Down

Cancel
0 havox over 7 years ago in reply to damien.solodow

This was for the vCenter appliance. I did get this fixed by upgrading VMAN to 7.0 and NPM to 12.0.1.
Thanks,
Jon
Cancel
Vote Up 0 Vote Down

Cancel
0 sjohnson1 over 7 years ago in reply to havox

I'm running into the same problem with the vCenter 6.5 appliance. I've upgraded to NPM 12.0.1, we don't use VMAN, and I'm still getting the same error both in vSphere and the ESX hosts. I've tried the domain login and the local administrator@domain.local accounts with the same result.
Cancel
Vote Up +1 Vote Down

Cancel
0 havox over 7 years ago in reply to sjohnson1

I just checked mine again and it is not working. I guess the VM details are coming from my VMAN installation.
Cancel
Vote Up 0 Vote Down

Cancel
0 damien.solodow over 7 years ago

I have a case open with Solarwinds on this; looks like they need to fix IVM (the NPM builtin VMware integration).
Case number is 1088199 if you want to reference it when you submit your own..
Cancel
Vote Up 0 Vote Down

Cancel
0 havox over 7 years ago in reply to damien.solodow

I have opened a case as well referencing yours. Case ID #1091601.
Thanks,
Jon
Cancel
Vote Up 0 Vote Down

Cancel
0 orioncrack over 7 years ago in reply to havox

Any news on this?
This is tragic. We just upgraded to 6.5 and now I have zero V monitoring.
Cancel
Vote Up 0 Vote Down

Cancel
0 havox over 7 years ago in reply to orioncrack

We have it working. We upgraded to NPM 12.0.1 and VMAN 7.0. I think we ended up restarting all Orion services and got it working again. Good luck.
Cancel
Vote Up 0 Vote Down

Cancel
0 damien.solodow over 7 years ago in reply to orioncrack

Support had us upgrade VIM to 7.0 (was a separate download that I don't see in the Portal), and that resolved the error.
We don't have VMAN, so VIM was the piece we needed to upgrade.
Cancel
Vote Up 0 Vote Down

Cancel