4500 VSS IOS UPGRADE

Поделиться
HTML-код
  • Опубликовано: 17 янв 2025

Комментарии • 19

  • @chupamel4
    @chupamel4 4 года назад +2

    Your explanation was perfect, no errors...
    I recently made an upgrade to my 4500 VSS following this guide and its worked flawlessly. Thanks a lot my friend!

  • @dewaldvos8901
    @dewaldvos8901 4 года назад +2

    Thanks Network Base. Used the steps outline last night for a large Hospital network. The only thing that I left out was Step: boot system flash slavebootflash:'
    When doing "Sh Bootvar" command it looked a bit wonky if you add that in. You only have to do bootflash:bootflash:' It will then have the correct image in bootvar for both Primary and slave. Upgrade took 10 Minutes. Also did upgrade on to 3850 which was a whole different story. Thanks for the clear concise steps made it so much easier then rummaging through all the confusing Cisco guidelines.

  • @chk_gupta_vlogs3305
    @chk_gupta_vlogs3305 Год назад +1

    Thanks for the help 😊

  • @teamhhh1
    @teamhhh1 Год назад

    Best video point to point🎉

  • @satyapramod8762
    @satyapramod8762 2 года назад

    Great work ... Really the informative one ... It was very easy process. no confusions.Thanks for your time.

    • @networkbase8731
      @networkbase8731  2 года назад

      Thanks such reviews encourage me to make more content.

  • @sohailkhan3594
    @sohailkhan3594 2 года назад +1

    I am curious about the redundancy reload shelf command at the end. Would it not be wise to force switchover to standby supervisor and then console on to the primary and reload that and confirm upgrade is successful. Then on the standby do a force switchover to the original primary and then repeat the process on the standby via console, test it works by the force switch over and then do another force switchover to back to the primary. It sounds long winded but would it not mean no downtime and if something went wrong in the upgrade you will not have any downtime since you are always running a working supervisor. Just curious is all as rebooting both primary and standby at the same time means if it goes wrong then it goes wrong for both which in a way defeats the advantages of having a primary and standby in the first place.

  • @sayedrohid1695
    @sayedrohid1695 4 года назад +1

    Thank you for sharing this video i found it very help full

  • @manileo3308
    @manileo3308 Месяц назад

    Hi, thank you for this informational video.
    After doing all the steps, my reg shows as x2302. How can we bring it down to x2102?

  • @sohailkhan3594
    @sohailkhan3594 2 года назад

    Brilliant Instructions! i will be trying this out on several 4507R+E switch next week and feel more confidant after watching this video, so thanks! Hopefully it will go all well. I never new about the redundancy reload shelf command, if you just typed reload i wonder what would happen even if the new IOS is on both primary and standby supervisors and both the boot system paths are correct?

  • @nareshkuchipudi3920
    @nareshkuchipudi3920 Год назад

    what the process for 6500 ?

  • @aksel9392
    @aksel9392 3 года назад

    what should we do to uplinks and vsl links,should they be down?

    • @networkbase8731
      @networkbase8731  3 года назад

      If you have maintenance window then don't down any port

  • @johnmelvingironella8632
    @johnmelvingironella8632 4 года назад

    Will this work on 6880-x switch? And is rebooting takes time? If so how long? Tia

    • @networkbase8731
      @networkbase8731  4 года назад

      Yes the procedure is same for vss switch mode.
      I have performed on 4500 so no idea of rebooting time of 6880.may be it takes upto 20min to reboot.
      Copy the IOS to the primary bootflash:
      Copy the IOS to the secondary bootflash:
      Remove the boot variable string pointing to the old IOS
      Add the new boot variable string pointing to the new IOS
      Insert the boot variable string pointing to the old IOS
      Make sure the config-registry is 0x2102
      Save the config
      Reboot
      "redundancy reload shelf" should have worked.