We recently updated vCenter and ESXI from v7 to v8. During this time, Eaton IPM wasn’t having any issues with the vCenter Connector.

Now we’re getting an API mismatch after adding a the vCenter or ESXi connectors to a new Eaton IPM appliance running version 2.7.

I saw in the release notes that IPM 2.7 can run on vCenter 8 but cannot be managed by it? I’m guessing this may be why I’m getting an API mismatch error.

Anyone know when IPM will release a version that supports vCenter and ESXi 8?

@Eaton @VMware

6 Spice ups

Hello - Yes, this sounds like it could either be a license issue or a compatibility issue if the vCenter version has changed. If you don’t mind, please send a message to softwareconnectivityts at eaton dot com and they’ll help troubleshoot the issue.

3 Spice ups

@jay-eaton Thanks for pointing me to the right contact email. Glad your in the SpiceWorks community! :slight_smile:

Unfortunately they said there’s no ETA for ESXi 8 compatibility but to check back periodically. Fingers crossed that it’s soon.

1 Spice up

You are welcome! Glad they got back to you quickly with an answer. Hopefully we can get it upgraded soon.

2 Spice ups

Hi everyone,

how can I fix “Error while getting list of documents: Impossible to connect to server”. Trying to login with local user on IPM2.

Didn’t do any change on network or settings for IPM. Error happened after host restart.

Thanks for help.

Best regards

I would try restarting the server and see if that fixes it. If not, send a message to softwareconnectivityts at Eaton dot com

1 Spice up