Recover of EML 71e? SOAP-FAULT, conection refused.

[Baggens]

After restoring system defaults the OCP screen freezes at the boot, showing a HP logo for hours(and days if you have the time to wait). It's possible to make a connection and logon with RS232 to the serial port of the IM. But when logged on it's not possible to view, set, restore or do anything else than walking up and down in the structure of the menus. All other commands give a error code 20, SOAP FAULT. For example when trying to reboot the IM:
"/reboot>mgmt

Caution: Rebooting the interface manager could take up to 2
minutes, and you will have to log on again to use the CLI.
Do you really want to reboot the interface manager?
Enter 'y' to continue or 'n' to skip [default='n']: y

Error processing command
src/EMFIMInfoReaderWriter.cpp (102): A Soap ETLAUtils::Exception ocurred while communicating with the IM. The error code is 20 error comment: SOAP FAULT:SOAP-ENV:Client
Connection refused
Detail:TCP connect failed in tcp_connect()
"

Power cycling the library doesn't help. Is there a way to recover the interface manager completely?

[Marino Meloni_1]

this indicate that the IM is not responding, and have the FW probably corrupted.
Try to pin reset theIM, and see if you can telnet it

If you cannot access from telnet to IM then probably you need a new smartcard

Open a call with HP will help to solve this situation

[Baggens]

Thanks for your answer.
A pin reset didn't solve the problem, but I was able to see the IM booting correctly though serial cable.
I'm not completely sure about this, but a technician logged in with a service account and changed a setting from ESL to EML mode. This little feature/bug made the IM believe that it was an ESL robot after a factoy reset and as a result the internal network did not work.
After changing the setting everything worked correctly.

[s_bert]

What account was used to reset to EML mode? I'm in the exact same mode after reset.

Thanks

[Baggens]

Hi!
I don't know the service account name and password since the technician from HP logged in and made the changes.
So I think you have to log a support case to get it solved, I'm afraid.
And we can hope that the "feature" will get fixed in a coming update.

[s_bert]

Trying to resolve it now, will let you know how it turns out.