Solved!
Go to SolutionOpenManage internal error after connecting
I installed Openmanage version 9.5, from the included DVD, on a Windows 10 system. The T340 is running ESXi 7.01, new install. I downloaded the vib for ESXi and installed. software vib list shows:
dcism 3.6.0.2249-DEL.700.0.0.15843807 DEL VMwareAccepted 2021-03-06
openmanage 9.5.0.4145-DEL.700.0.0.15843807 DEL VMwareAccepted 2021-03-06
When I go to the openmanage (port 1311) and log in, it appears to log in and then gets Failed internal error. The lifecycle log shows:
| 2021-03-06 13:14:20 | USR0030 | Successfully logged in using root, from 10.0.2.210 and WS-MAN. | |
|
Log Sequence Number:
219
Detailed Description:
Successful login for the username, IP address, and interface identified in the message.
Recommended Action:
No response action is required.
|
| Operating System | VMware ESXi |
| Operating System Version | 7.0.1 Update 1 Patch 25 (build-17325551) Kernel 7.0.1 (x86_64) |
| Service Tag | XXXXXX |
| BIOS Version | 2.4.1 |
| iDRAC Firmware Version | 4.40.00.00 |
| IP Address(es) |
I see nothing in the /var/log at that time. I am wondering if there is some setting I am missing?
Thanks for any advice.
Lou
2884
0
Posted March 7th, 2021 22:00
https://dell.to/3kTwrzf Hi, please refer to this and make sure OMSA installation is done ok. Have a great one and let us know if you have any further questions!
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!2875
0
Posted March 8th, 2021 05:00
Thanks. OMSA remote enablement test says:
Dell, Inc. Exception: Input string was not in a correct format.
Top2868
0
Posted March 8th, 2021 07:00
Hello @louyo,
I cannot see Windows 10 as a supported os for OMSA 9.5: https://dell.to/3ceDApQPlease, check the manual: https://dell.to/3cguby0
Regards.
2864
0
Posted March 8th, 2021 09:00
Good afternoon Louyo,
Would you be able to test connection to the OMSA service on the host from another system, not a guest on the same host? I ask because I've found this to be the easiest way to quickly rule out communication issues.
Second, has the ESXi host been restarted? Apologies if this seems like a bit of a silly question. It's a mandatory step for ESXi installation, but not for Windows. That difference can catch people sometimes.
2865
0
Posted March 8th, 2021 09:00
Thank you. Does the same thing from Windows Server 2016
Lou
2857
0
Posted March 8th, 2021 14:00
Thank you. I have tried from several systems, both installation of OpenManage and connection via browser. Following the suggestion above, the trouble shooting program fails as well. Yes, ESXi was running.
2854
0
Posted March 8th, 2021 15:00
What browser are you using when attempting to connect? OpenManage issues like this tend to be more related to the client attempting to access, but if you can, I'd use the ps command to make sure the OpenManage process is running.
On the guest, do you see any change in behavior if you launch your browser and manually navigate to the IP of the host, followed by ':1311?'
2837
0
Posted March 9th, 2021 04:00
Thank you. You name the browser, I have tried it. One of the power supplies let out a puff of smoke and left this earth. I have decided to redo the Datastores and add a pair of drives. Will go back to square one, re-installng ESXi and the VM layouts. Will try again in a couple of days, prior to going into production.
Thanks again.
Lou
louyo
1 Rookie
•
32 Posts
2740
0
Posted March 11th, 2021 17:00
After adding 2 new drives, replacing a defective power supply and re-installing ESXi 7 and the virtual machines, I am able to access iDRAC via OpenManage. I am thinking that the problem was self inflicted, although the trouble shooter still fails. Thanks to all who responded.
Lou