Comware

 View Only
  • 1.  3Com-branded HP V1910-24G Switch (JE006A) does not boot

    Posted 24 days ago

    the problem with the switch is that the "Power" led keep blinking (like 3 times a second).

    and does not work, i bought an rj45-usb cable to see the Console through program like:

    - moba xterm

    - putty

    - Tera Term 5 (i used this)

    I download the firmware (1910_5.20.R1513P99.zip) that contains the file (V1910-CMW520-R1513P99.bin) from the HPE site.

    i "upload" it into the switch using XMODEM and named it "V1910-CMW520-R1513P99.bin".

    Then i went into the menu > Select Application file to boot > Set application file

    and here i choose the only file present (that is the one i uploaded before).

    BUT when i select it and chose to set it as "Main", the console print out:

    The attribute of V1910-CMW520-R1513P99.bin is changed from main to none!
    Something went wrong with the file.
    Set the file attribute failed!

    i dont know what to do at this point, the switch is stuck with this power light linking and the port does not work



  • 2.  RE: 3Com-branded HP V1910-24G Switch (JE006A) does not boot

    Posted yesterday

    The 3Com branding matters here. JE006A units that started life as 3CRBSG2893 have a documented history of firmware compatibility trouble: R1516 flat out bricked 3Com-branded boxes, and the fix only landed in R1517P01 and R1518, whose release notes call out the 3Com no-boot problem specifically. So before anything else I'd try R1518 rather than R1513P99, since you're loading an older image onto the exact hardware variant these releases were patched for.

    The other suspect is the transfer itself. That set-attribute error usually means the image failed validation, and a 50 MB bin over XMODEM at 38400 takes hours and corrupts easily. Check the file size shown in the boot menu against the actual bin, and if your boot menu has the Ethernet download option, use TFTP instead, it's minutes instead of hours. The good news: if you can reach Ctrl-B, the bootrom's alive and the box is recoverable. It's not bricked, it's just booting up the wrong tree.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------