Wired Intelligent Edge

Hi,

Have an original HPE 2920 J9726A switch that I am trying to update to the latest version.

Have managed to get to WB.16.05.0013 but any other attempts to go above the 16.05 branch results in the tftp transfer failing. Usually this happens if the branch jump is too great.

Any ideas if there is an upper limit an older HPE version of the 2920 can go to?

Or any other suggestions?

I've tried pretty much every branch and sub version of the current branches above 16.05. All do the same.

thanks.

Hello, 

There is no upper limit for the version to which the older version of the 2920 can go. If there was such a limitation it would have been documented in the release notes. I couldnt find any.

You have updated the switch already to WB.16.05.0013. Does it mean that you already booted the switch from this version or you have simply loaded the version to one of the flash images (primary or secondary)? If the switch was not booted yet, please try to boot it from this version. This will probably update the BootROM which may be necessary for the installation of later releases. If the switch was already booted from WB.16.05.00013 please provide the output of show version and show flash. 

When the tftp transfer is failing what error message is displayed? The copy tftp command allows you to upload a firmware to both primary or secondary image. Are you getting the same error with both primary and secondary?

This switch supports firmware upgrade also via the webUI. Did you already try an update via HTTP/s? Maybe it is just a but with TFTP in 16.05.0013 which prevents the upload?

Thanks for both your inputs.

Switch had been updated and rebooted. All commands suggested looked ok, nothing obvious. TFTP was failing with timeout errors, to both pri & sec locations.

Tried a gui upgrade as suggested and it worked fine.

TFTP still fails in all versions up to and including 16.10, but the gui upgrade works ok. So atleast I have an up to date switch now. Just wonder if it's the TFTP server software i was using, but never had an issue with it before over the years.

Thanks.

Hello Tim_Salt.

Thanks for the feedback!

I tested the TFTP transfer in the lab. The switch was running version WB.16.07.0002 and I was able to transfer firmware version WB.16.10.0007 to the primary image using a free TFTP tool (tftpd64). After that I was also able to boot the switch from primary and essentialy update the switch to WB.16.10.0007.

Hi! as suggested by @Emil_G you should first post the status of your actual flash areas by using show version and show flash commands.

Also a verify signature flash primary (and/or secondary) would be of help to undestand the status of flashed firmware on primary (and/or secondary) flash area.

Genearlly a straight procedure would be (never had an issue downloading a SWI file from a well connected and reacheable TFTP Server):

switch# show version

Image stamp:    /ws/swbuildm/rel_ajanta_qaoff/code/build/lakes(swbuildm_rel_ajanta_qaoff_rel_ajanta)
                Jan 17 2020 05:48:13
                YA.16.10.0003
                391
Boot Image:     Secondary

Boot ROM Version:    YA.15.20

switch# show flash
Image             Size (bytes) Date     Version
----------------- ------------ -------- --------------
Primary Image    :    15069009 01/17/20 YA.16.10.0003
Secondary Image  :    15069009 01/17/20 YA.16.10.0003

Boot ROM Version
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Secondary

switch# verify signature flash primary
Signature is valid

switch# verify signature flash secondary
Signature is valid

switch# copy tftp flash <TFTP-Server-IP-Address> YA_16_10_0007.swi primary
The primary image will be deleted.

Continue (y/n)? y
015M

Validating and Writing System Software to the Filesystem ...

switch# show flash
Image             Size (bytes) Date     Version
----------------- ------------ -------- --------------
Primary Image    :    15100980 04/17/20 YA.16.10.0007
Secondary Image  :    15069009 01/17/20 YA.16.10.0003

Boot ROM Version
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Secondary

switch# verify signature flash primary
Signature is valid

switch# boot system flash primary

The switch will reboot

switch# show version

Image stamp:    /ws/swbuildm/ajanta_qt_qaoff/code/build/lakes(swbuildm_ajanta_qt_qaoff_ajanta_qt)
                Apr 17 2020 04:27:04
                YA.16.10.0007
                240
Boot Image:     Primary

Boot ROM Version:    YA.15.20

switch# show flash
Image             Size (bytes) Date     Version 
----------------- ------------ -------- --------------
Primary Image    :    15100980 04/17/20 YA.16.10.0007        
Secondary Image  :    15069009 01/17/20 YA.16.10.0003       

Boot ROM Version 
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Primary

switch# copy flash flash secondary 

switch# show flash
Image             Size (bytes) Date     Version 
----------------- ------------ -------- --------------
Primary Image    :    15100980 04/17/20 YA.16.10.0007        
Secondary Image  :    15100980 04/17/20 YA.16.10.0007       

Boot ROM Version 
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Primary

 In the example above an Aruba 2530 with a recent YA.16.10.0003 (booted on Primary) is updated to YA.16.10.0007 (latest, released just few days ago).

I upload from TFTP Server the firmware YA_16_10_0007.swi on the Secondary flash area. Then I set the next boot to start from Secondary instead of (default) Primary. That's it. Apart from verifying the flashed firmwares (current and the updated ones) in the end, if no issue will arise, I tend to copy the updated flashed area on the other (non updated) in order to have both areas equally updated.

Just wanna ask
1. how come after you upgrade firmware of primary and secondary flash to YA.16.10.0003
the Boot ROM Version still version YA.15.20
Is that possible to upgrade that too
2. I have HPE Procurve 2530 24 ports FE but my friend has Aruba 2530 24 has GB ports
Is the OS same for both Aruba and HPE 2530

tq

1. 
   1. how come after you upgrade firmware of primary and secondary flash to YA.16.10.0003
   the Boot ROM Version still version YA.15.20
   Is that possible to upgrade that too

Maybe you uploaded this version to both primary and secondary flash but didn’t reboot the switch yet. Before the switch is rebooted from a flash partition containing the new firmware the update is not completed. The command to boot the switch from a particular partition is “boot system flash primary” or “boot system flash secondary”

You can use the command “show version” to verify which firmware version is running the switch at the moment. It is possible that the switch is still running an old version although you have the new in both flash images.

1. 
   2. I have HPE Procurve 2530 24 ports FE but my friend has Aruba 2530 24 has GB ports
   Is the OS same for both Aruba and HPE 2530.

Aruba 2530 and HPE 2530 are the same switches. Before the Aruba acquisition this were known as HPE 2530 series.

There is a difference of OS between models with different port options.

All the Gigabit switches of the 2530 series are running the YA branch. The FestEthernet switches with 48 ports are also running YA. The rest of the FastEthernet switches (8 and 24 ports) are running YB branch.

You can use the MyNetworking lookup tool to get access to the download link for every specific model

https://h10145.www1.hpe.com/support/SupportLookUp.aspx

Just enter the product number (starting with J for example J9782A) or product description. In the results set the checkbox in front of your mode. The tool will display links with resources for this model, one of them is Software Downloads for the particular model.

The same search can be done in Aruba Support Portal (asp)

https://asp.arubanetworks.com/downloads;products=Aruba%20Switches

Hello, 

Sorry, I have to correct my answer to your first question. I was assuming that the update to YA.16.10.0003 is supposed to update the bootROM to a higher version. However in the release notes it is stated

https://support.hpe.com/hpesc/public/docDisplay?docId=a00095259en_us

Before/After reboot to Primary. Primary Boot ROM Version = YB.15.10
HP-2530-24# sh flash
Image Size (bytes) Date Version
----------------- ------------ -------- --------------
Primary Image : 13581456 08/21/20 YB.16.10.0010
Secondary Image : 7918805 02/28/13 YB.15.12.0006
Boot ROM Version
----------------
Primary Boot ROM Version : YB.15.10
Default Boot Image : Primary

Thanks for the outputs!

Yes, this should be the expected BootROM version with firmware version YB.16.10.0010. See my previous post.

Release notes 16.10.0010, page 79

https://support.hpe.com/hpesc/public/docDisplay?docId=a00104961en_us

Hi! as suggested by @Emil_G you should first post the status of your actual flash areas by using show version and show flash commands.

Also a verify signature flash primary (and/or secondary) would be of help to undestand the status of flashed firmware on primary (and/or secondary) flash area.

Genearlly a straight procedure would be (never had an issue downloading a SWI file from a well connected and reacheable TFTP Server):

switch# show version

Image stamp:    /ws/swbuildm/rel_ajanta_qaoff/code/build/lakes(swbuildm_rel_ajanta_qaoff_rel_ajanta)
                Jan 17 2020 05:48:13
                YA.16.10.0003
                391
Boot Image:     Secondary

Boot ROM Version:    YA.15.20

switch# show flash
Image             Size (bytes) Date     Version
----------------- ------------ -------- --------------
Primary Image    :    15069009 01/17/20 YA.16.10.0003
Secondary Image  :    15069009 01/17/20 YA.16.10.0003

Boot ROM Version
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Secondary

switch# verify signature flash primary
Signature is valid

switch# verify signature flash secondary
Signature is valid

switch# copy tftp flash <TFTP-Server-IP-Address> YA_16_10_0007.swi primary
The primary image will be deleted.

Continue (y/n)? y
015M

Validating and Writing System Software to the Filesystem ...

switch# show flash
Image             Size (bytes) Date     Version
----------------- ------------ -------- --------------
Primary Image    :    15100980 04/17/20 YA.16.10.0007
Secondary Image  :    15069009 01/17/20 YA.16.10.0003

Boot ROM Version
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Secondary

switch# verify signature flash primary
Signature is valid

switch# boot system flash primary

The switch will reboot

switch# show version

Image stamp:    /ws/swbuildm/ajanta_qt_qaoff/code/build/lakes(swbuildm_ajanta_qt_qaoff_ajanta_qt)
                Apr 17 2020 04:27:04
                YA.16.10.0007
                240
Boot Image:     Primary

Boot ROM Version:    YA.15.20

switch# show flash
Image             Size (bytes) Date     Version 
----------------- ------------ -------- --------------
Primary Image    :    15100980 04/17/20 YA.16.10.0007        
Secondary Image  :    15069009 01/17/20 YA.16.10.0003       

Boot ROM Version 
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Primary

switch# copy flash flash secondary 

switch# show flash
Image             Size (bytes) Date     Version 
----------------- ------------ -------- --------------
Primary Image    :    15100980 04/17/20 YA.16.10.0007        
Secondary Image  :    15100980 04/17/20 YA.16.10.0007       

Boot ROM Version 
----------------
Primary Boot ROM Version   : YA.15.20

Default Boot Image   : Primary

 In the example above an Aruba 2530 with a recent YA.16.10.0003 (booted on Primary) is updated to YA.16.10.0007 (latest, released just few days ago).

I upload from TFTP Server the firmware YA_16_10_0007.swi on the Secondary flash area. Then I set the next boot to start from Secondary instead of (default) Primary. That's it. Apart from verifying the flashed firmwares (current and the updated ones) in the end, if no issue will arise, I tend to copy the updated flashed area on the other (non updated) in order to have both areas equally updated.

The update procedure of an Aruba (HP) 2920, if made with the help of a TFTP Server, is identical.