Slow speed for image redirection in LOM

[Just_Crj]

Hi!
I am trying to perform a fresh install for a remote gateways 9200 (LOM version 7.12.1) and for qls250 (LOM version 6.22) via upload cd images (different images for 9200 and for qls 250)from my computer in LOM console session.

Problem:
The speed is only 1 KB per couple of minutes.

Sometimes after waiting 15-20 minutes, 4-5 KB is uploaded and after that the session in the console is interrupted,the file upload progress is reset and everything starts over.

Tests:

The image is uploaded from computers on the internal network. I tried 4 different browsers (incognito mode too), tried uploading from different computers, rebooted the LOM via the cli command "set lom reboot-card", installed the latest firmware version for the LOM of each gateway - the problem still persists. 
The firmware for LOM (60 MB) is uploaded in a couple of seconds. I also checked the upload of the same iso file for the same gateway to cpuse (Mgmt and LOM interface in the same network) via the "Import package" (it doesn't make sense, but it provides visual information about the upload speed) - it takes a couple of minutes to upload the iso file (4 GB).

Therefore, I concluded that there are no network problems, the problem is in the LOM settings.

Current status:
I left upload process for 2 days of holidays - the session is currently active, but only 800 KB has been uploaded.

I do not have physical access to this gateways. Therefore, i will not be able to perform a fresh install via USB .
Please help me figure out the problem, thank you!

[PhoneBoy]

Unless you used the exact same cable/port/switch for the LOM as you used for the appliance when uploading via CPUSE, you haven't ruled out the network.
Packet captures of the LOM connection might provide some clues as to what is really going on. 
Getting that might be tricky, obviously.

[Lesley]

Worth to try a cold reboot.

- shutdown appliance

- remove power

- wait few minutes and connect power

- boot fw

You can also try:

ipmitool mc reset cold

Ping the LOM IP to make sure this command really works (it depends)

Extra tip i found in old sk:

Please keep in mind that installing using this method depends on the connection from the host on which the ISO is stored and also on the LOM card. If the connection experiences latency, or the link is slow and the ISO takes a long time to upload, the installation can fail. This will leave the appliance needing local access to reinstall. Please try to avoid this by using a local host, which can be remotely controlled, to connect to the LOM gui and upload the ISO. This should improve the time that it takes to complete the installation process.

Sometimes, the LOM console (JViewer) will only show a static message and no progress (only showing 'Ready' status). You can monitor the ISO file upload process during installation by going to - Device -> Redirect CDROM or Redirect ISO. This will show the amount of data that has been transferred. After the file transfer finishes, it should take a few more minutes until the installation finishes.

[the_rock]

Those steps make sense to me.

[Just_Crj]

Hi!
In my case, the command did not work (I tried clish and expert)


The last paragraph refers to Java based LOM cards, as I understand it, but I have HTML5 based cards.

[JozkoMrkvicka]

Both gateways have HTML5 or Java based LOM cards ?

Try to check LOM network settings. Sometimes I noticed the speed was recognized automatically just as 100M and duplex was set to half, instead of full.

To 100% rule out network issue, you have to connect physically into LOM port and start upload of ISO from directly connected notebook.

[Bob_Zimmerman]

I've seen attempts to hard-code gigabit lead to an autonegotiating system arriving at 100M half.

Note that for gigabit, autonegotiation is not optional. Officially, gigabit speed or faster over copper can only be negotiated, so hard-coding it is violating the specification, and likely to cause problems.

[Just_Crj]

Hi Jozko,
It looks like the autonegotiation settings are correct

[Just_Crj · Accepted solution]

The problem was resolved after some more reboots of LOM cards via clish. Now after the Start Media and during the gateway reboot the reinstall process has begun.