The host is housed in a small facility that does not have kvm or crash kart. IMM.SSL_SERVER_DIRECTOR_CERT=Private Key and Cert/CSR not available.Īt this point, the only sensible thing before calling in support sounds like reset to factory default. IMM.SSL_LDAP_CLIENT_CSR=Private Key and Cert/CSR not available. IMM.SSL_LDAP_CLIENT_CERT=Private Key and Cert/CSR not available. IMM.SSL_HTTPS_SERVER_CSR=Private Key and Cert/CSR not available. IMM.SSL_HTTPS_SERVER_CERT=Private Key and Cert/CSR not available. Unable to locate a script required to set up LAN-over-USB device, tried location cdc_interface.shĭiscovered IMM at IP address 169.254.95.118Ĭonnected to IMM at IP address 169.254.95.118 IBM Advanced Settings Utility version 9.21.78C The autoneg and duplexing too matches the switch port. We even ran a cable between the IMM port and a laptop.Īs the host is classic ESX 4.1, we used the asu utility from the host to check the configuration.
The MGMT NIC had green light, was blinking and our network guy saw they were exchanging packets. Our network guy validated the switch configuration.
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. We have one server where we cannot reach the IMM remotely. A part of our pre-upgrade checklist is to ensure we have IMM access. It is going to be a two step process, the first of which will be upgrade to 5.1 using the ISO. We are going to upgrade a handful of ESX 4.1 hosts to 5.5 or 6, if the hardware supports.
0 kommentar(er)
