Wired Intelligent Edge

 View Only
last person joined: 16 hours ago 

Bring performance and reliability to your network with the Aruba Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of the ArubaOS-Switch and ArubaOS-CX devices, and find ways to improve security across your network to bring together a mobile first solution.
Expand all | Collapse all

Running config shows older switch version

Jump to Best Answer
This thread has been viewed 3 times
  • 1.  Running config shows older switch version

    Posted Jan 03, 2020 10:00 AM

    We recently upgraded a JL322A 2930M switch to code version WC.16.08.0001 from WC.16.06.0006.  However, in the running-config, it still displays the old code version at the top.  Below are the examples:

     

    Switch# show flash

    Image Size (bytes) Date Version
    ----------------- ------------ -------- --------------
    Primary Image : 29616419 11/21/18 WC.16.08.0001
    Secondary Image : 29616419 11/21/18 WC.16.08.0001

    Boot ROM Version
    ----------------
    Primary Boot ROM Version : WC.17.02.0004
    Secondary Boot ROM Version : WC.17.02.0004

    Default Boot Image : Primary
    Default Boot ROM : Primary

     

     

    Switch# show running-config | include WC.16

    ; hpStack_WC Configuration Editor; Created on release #WC.16.06.0006

     

     

    No known issues are currently exhibited from the switch at the moment or at least clients on the switch have not expressed any concern.  Would there be any issues as a result from this?  How would this be able to be fixed?

     

    Other switches that we have upgraded to the WC.16.08.0001 code version have not experienced this.


    #2930M
    #2930M


  • 2.  RE: Running config shows older switch version

    MVP EXPERT
    Posted Jan 03, 2020 11:12 AM

    I update my 2920 from WB.16.07.0002 to WB.16.10.0002 to check this behavoir for you.

     

    After reboot i see...

    HomeLAB-Edgeswitch# show version
    
    Image stamp:    /ws/swbuildm/rel_ajanta_qaoff/code/build/anm(swbuildm_rel_ajanta_qaoff_rel_ajanta)
                    Nov  1 2019 19:16:15
                    WB.16.10.0002
                    323
    Boot Image:     Primary
    
    Boot ROM Version:    WB.16.03
    Active Boot ROM:     Primary
    
    HomeLAB-Edgeswitch# show running-config
    
    Running configuration:
    
    ; J9729A Configuration Editor; Created on release #WB.16.10.0002

    Strange situation, could you do a  "write mem" and check "show run" again or reboot the switch again? Maybe open a TAC case on this, i didnt see this before.

     



  • 3.  RE: Running config shows older switch version

    Posted Jan 03, 2020 11:48 AM

    It still shows the same thing after a write memory on the device.  I thought about opening a case.  Just wanted to post here first in case this has been ran into.  Thanks.



  • 4.  RE: Running config shows older switch version

    EMPLOYEE
    Posted Jan 03, 2020 01:14 PM

    Greetings!

     

    Just to verify: does show version match the software version listed in show flash, or the version displayed in the running configuration? 



  • 5.  RE: Running config shows older switch version

    Posted Jan 03, 2020 02:14 PM

    It appers that the output of show version does indicate the old version.  

     

    Switch# show version


    Image stamp: /ws/swbuildm/rel_washington_qaoff/code/build/lvm(swbuildm_rel_washington_qaoff_rel_washington)
    Jun 22 2018 12:55:58
    WC.16.06.0006
    607
    Boot Image: Primary

    Boot ROM Version: WC.17.02.0004
    Active Boot ROM: Primary



  • 6.  RE: Running config shows older switch version
    Best Answer

    EMPLOYEE
    Posted Jan 03, 2020 02:38 PM

    It looks like the software images in flash were updated, but the switch has not yet been rebooted into the new software.



  • 7.  RE: Running config shows older switch version
    Best Answer

    Posted Jan 03, 2020 02:39 PM

    After speaking with my team, it appears that the image was loaded onto the primary and secondary partitions.  However the switch had not been reloaded to boot from the new image.  I confirmed by using show boot-history and show system.

     

    At the time of the upgrade, we were told not to disrupt clients on this switch.  I had thought that our normal upgrade procedures were completed but I guess they were not.  Thanks for the input.