ESL322E ESL712E robotics not communicating after nov 2019 date

[Torsten.]

  @SpecProtect-Guy - any new results?

[LibraryGuru]

Hi Team,

We have 1 site with same issue right now. All the other sites we set back 1 year are working good. 9 sites now. The 1 site we are seeing this issue, we are sending FE to site to verify a full power cycle was performed. We are seeing this issue on latest FW level and much older FW levels. My Quantum contacts have not confirmed yet if this is strickly on the HP version or on the quantum versions too (PX702). As soon as I get a reply I will update this post.

Torsten, do you know if they are planning a perminent fix for this? We have seen date sent back to current date and issue returns, set date to 2018 and issue is gone. Thanks for adding your link and details to this post!

Mark

[Torsten.]

AFAIK version 7.70.01. from 2011 is the latest version and probably the issue is there and in previous versions.

I really doubt they (Quantum) will make a newer fixed version, but who knows ... AFAIK the HP version is using the original firmware and extended the box with the interface manager and interface controllers only.

[SpecProtect-Guy]

HI Torsten,

I changed the date back by 1 month.  Did a full power cycle including removing power cables.  And it made no difference. Still get the “Corrupted Database” on the library at the end of the power up. The whole process take 30 mins for me to do.

I shall put the date back to 5-Dec-2018 on the library.

I did put the date back by 3 months last Friday and on power up is when I originally got the “Corrupted database” message.

THANKS.

[Torsten.]

Once the internal database is corrupted, it needs repair or new initialization.

Did you see your mailbox at this page?

[SpecProtect-Guy]

HI,

How do I go about a repair of the ESLE  library database?

I dare not reset to to factory settings as I do not know how to configure the library back to what it is supposed to be.

Thanks S-G.

[Torsten.]

However, once at factory defaults you need to re-configure the IP, the loadports and finally the host mapping if present.

You should be able to get all these values from the library now.

Logon to the IM (serial is better) using cliadm user.

do

show network dhcp

show network ipaddress

/>show

/show>host

if in doubt type "help"

[PDP-Fan]

#metoo

Superb! Another date related HPE problem. Not enough that the SSD's stop working after 32768 hours, now the ESL...

To be fair, ESL is now 15 years old and nobody expected that it will run so long anyway.

[Barry_Reider]

Click the link again for that advisory above - it was updated on December 18, 2019, with additional information.

-Barry

[SpecProtect-Guy]

HI,

Just to complete this from way back when. The ESL library did have to have a factory reset in the end and took some reconfiguring to get it back running. Luckly we had a similar (same) library and compared the config to get it to work.

Migrated the data off the tapes and it is no longer used. Moved to an MSL library.

Thanks to all who helped back then.

Regards SPG