We are going to upgrade a handful of ESX 4.1 hosts to 5.5 or 6, if the hardware supports. It is going to be a two step process, the first of which will be upgrade to 5.1 using the ISO. We need console access to do this. These are X series IBM servers. A part of our pre-upgrade checklist is to ensure we have IMM access.
We have one server where we cannot reach the IMM remotely. We have seen this before and managed to solve it by resetting the IMM via LanOverUsb or cold restart of the server- graceful shutdown of ESX(i), followed by unplug, plug both power supplies but not this time.
It is no brainer if you can access the IMM physically or remotely. But when you need someone to do it for you, picture helps.
Reboot the server and press F1 to enter setup. Then follow the pictures.
I am unable to open the web interface of IMM for an X series IBM server. I could ping it. I could ssh to it. So the IMM was clearly not hung. But nmap scan did not return port 80 or 443.
Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2016-08-26 11:10 CDT
Interesting ports on IMM_HOSTNAME (IMM_IP):
Not shown: 1675 closed ports
PORT STATE SERVICE
22/tcp open ssh
23/tcp open telnet
427/tcp open svrloc
3389/tcp open ms-term-serv
3900/tcp open udt_os
nmap scan from a working IMM Continue reading