cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
421
Views
0
Helpful
10
Replies
Highlighted

Cisco 9500-48Y4C - Upgrade from FUJI 16.9.4 to GIBRALTAR 16.12.03a

We have 2*9500-48Y4C in Stackwise Virtual configuration on the FUJI 16.9.4, running well for the last few months. Cisco Support has stated that SVL, even through works on the FUJI 16.9.4 is not supported, thus we need to migrate to at least Gibraltar 16.12.2, so we want to migrate to Gibraltar 16.12.03a.

 

Please if you can tell me if the below steps will be safe.

 

1. install add file tftp://192.168.1.100/ cat9k_iosxe.16.12.03a.SPA.bin

      I have already run this and the image is now extracted in the flash of the 9500. But i can't see            the cat9k_iosxe.16.12.03a.SPA.bin. Should the command remove the .bin after the packages are extracted. Also how many packages should be in the flash. 

 

2. install activate auto-abort-timer 60 [please correct me if i am wrong in here, in case Gibraltar is not stable upon testing, the 9500 stack will reboot after 60 mins, since we did not enter the install commit command]

 

3. install commit [In case we see that Gibraltar is fine, then we can commit]

 

Also suppose the switch did not come up after reload from Step 1, can we just do the following step and recover the switch and still ensure that the switches boot up in the install mode.

 

 

Output - Step 1

Finished downloading file tftp://192.168.1.100/cat9k_iosxe.16.12.03a.SPA.bin to bootflash:cat9k_iosxe.16.12.03a.SPA.bin
install_add: Adding PACKAGE

--- Starting initial file syncing ---
[1]: Copying bootflash:cat9k_iosxe.16.12.03a.SPA.bin from chassis 1 to chassis 2
[2]: Finished copying to chassis 2
Info: Finished copying bootflash:cat9k_iosxe.16.12.03a.SPA.bin to the selected c hassis
Finished initial file syncing

--- Starting Add ---
Performing Add on all members
[1] Add package(s) on chassis 1
[1] Finished Add on chassis 1
[2] Add package(s) on chassis 2
[2] Finished Add on chassis 2
Checking status of Add on [1 2]
Add: Passed on [1 2]
Finished Add

 

show flash:

77 89113604 May 27 2020 15:17:05.0000000000 +00:00 cat9k-espbase.16.12.03a.SPA.pkg
78 14291976 May 27 2020 15:17:05.0000000000 +00:00 cat9k-cc_srdriver.16.12.03a.SPA.pkg
79 1680392 May 27 2020 15:17:05.0000000000 +00:00 cat9k-guestshell.16.12.03a.SPA.pkg
80 530838532 May 27 2020 15:17:06.0000000000 +00:00 cat9k-rpbase.16.12.03a.SPA.pkg
81 41796428 May 27 2020 15:17:25.0000000000 +00:00 cat9k-rpboot.16.12.03a.SPA.pkg
82 31458308 May 27 2020 15:17:06.0000000000 +00:00 cat9k-sipbase.16.12.03a.SPA.pkg
83 60355588 May 27 2020 15:17:06.0000000000 +00:00 cat9k-sipspa.16.12.03a.SPA.pkg
84 22950916 May 27 2020 15:17:06.0000000000 +00:00 cat9k-srdriver.16.12.03a.SPA.pkg
85 12891136 May 27 2020 15:17:06.0000000000 +00:00 cat9k-webui.16.12.03a.SPA.pkg
86 9216 May 27 2020 15:17:06.0000000000 +00:00 cat9k-wlc.16.12.03a.SPA.pkg
87 7613 May 27 2020 15:17:25.0000000000 +00:00 cat9k_iosxe.16.12.03a.SPA.conf

4 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted
VIP Mentor

Hello
I upgraded a 9300 distribution stack today via USB, 95Ks should be similar if not the same procedure (check release notes)

When you actually perform the install the .bin file,  .PKGs files gets extracted to the flash, Then you shouldn't(well i didn't) see the .bin file after this extraction

dir flash:*.pkg's < should see two sets of PKGs old and new beginning with  xxxx.cc_srdiverc.xxxxx

dir flash:*.conf < should see update packages.conf file and new software backup conf file 

 

1) install remove active <  cleans up old inactive install files
2) copy usbflash1:xxxxxxxx.bin flash: < you only need to do this on the stack master
3) dir flash *.pkg's, dir flash:*.conf
4) show boot system < check for packages.conf is the boot variable
5) install add file flash:xxxxxxxx.bin activate commit < installs the new software to stack and activates it
6) stack reloads

7) install remove active <  once your happy with the new software



kind regards
Paul

Please rate and mark posts accordingly if you have found any of the information provided useful.
It will hopefully assist others with similar issues in the future

View solution in original post

Highlighted

Thanks Leo

 

I have already copied the IOS in to the 9500 stack.

 

The current status with the dir flash:*.pkg is as follows (Active currently is FUJI 16.9.4):

 

308276 -rw- 27231232 Dec 9 2019 19:03:51 +12:00 cat9k-cc_srdriver.16.09.04.SPA.pkg
308277 -rw- 81241084 Dec 9 2019 19:03:51 +12:00 cat9k-espbase.16.09.04.SPA.pkg
308278 -rw- 1647612 Dec 9 2019 19:03:51 +12:00 cat9k-guestshell.16.09.04.SPA.pkg
308279 -rw- 425411576 Dec 9 2019 19:03:51 +12:00 cat9k-rpbase.16.09.04.SPA.pkg
308285 -rw- 34612458 Dec 9 2019 19:04:07 +12:00 cat9k-rpboot.16.09.04.SPA.pkg
308280 -rw- 28931068 Dec 9 2019 19:03:51 +12:00 cat9k-sipbase.16.09.04.SPA.pkg
308281 -rw- 55047160 Dec 9 2019 19:03:51 +12:00 cat9k-sipspa.16.09.04.SPA.pkg
308282 -rw- 35243004 Dec 9 2019 19:03:51 +12:00 cat9k-srdriver.16.09.04.SPA.pkg
308283 -rw- 15856632 Dec 9 2019 19:03:51 +12:00 cat9k-webui.16.09.04.SPA.pkg
308284 -rw- 9208 Dec 9 2019 19:03:51 +12:00 cat9k-wlc.16.09.04.SPA.pkg
397492 -rw- 89113604 May 27 2020 15:17:05 +12:00 cat9k-espbase.16.12.03a.SPA.pkg
397491 -rw- 14291976 May 27 2020 15:17:05 +12:00 cat9k-cc_srdriver.16.12.03a.SPA.pkg
397493 -rw- 1680392 May 27 2020 15:17:05 +12:00 cat9k-guestshell.16.12.03a.SPA.pkg
397494 -rw- 530838532 May 27 2020 15:17:06 +12:00 cat9k-rpbase.16.12.03a.SPA.pkg
397500 -rw- 41796428 May 27 2020 15:17:25 +12:00 cat9k-rpboot.16.12.03a.SPA.pkg
397495 -rw- 31458308 May 27 2020 15:17:06 +12:00 cat9k-sipbase.16.12.03a.SPA.pkg
397496 -rw- 60355588 May 27 2020 15:17:06 +12:00 cat9k-sipspa.16.12.03a.SPA.pkg
397497 -rw- 22950916 May 27 2020 15:17:06 +12:00 cat9k-srdriver.16.12.03a.SPA.pkg
397498 -rw- 12891136 May 27 2020 15:17:06 +12:00 cat9k-webui.16.12.03a.SPA.pkg
397499 -rw- 9216 May 27 2020 15:17:06 +12:00 cat9k-wlc.16.12.03a.SPA.pkg

 

dir flash:*.conf

308275 -rw- 7554 Dec 9 2019 19:04:07 +12:00 packages.conf
397490 -rw- 7613 May 27 2020 15:17:25 +12:00 cat9k_iosxe.16.12.03a.SPA.conf

 

Please if you can guide with the above files whether we will be ok to do a install activate auto-abort-timer 60 and once the switches is fully online and tested ok, then we can do a install commit.

 

 

View solution in original post

Highlighted

Hello

The command i used added/installed and committed the software all in one, but you can do each step individually however it looks like you’ve already added and installed the new software,


397492 -rw- 89113604 May 27 2020 15:17:05 +12:00 cat9k-espbase.16.12.03a.SPA.pkg
397491 -rw- 14291976 May 27 2020 15:17:05 +12:00 cat9k-cc_srdriver.16.12.03a.SPA.pkg
397493 -rw- 1680392 May 27 2020 15:17:05 +12:00 cat9k-guestshell.16.12.03a.SPA.pkg
397494 -rw- 530838532 May 27 2020 15:17:06 +12:00 cat9k-rpbase.16.12.03a.SPA.pkg
397500 -rw- 41796428 May 27 2020 15:17:25 +12:00 cat9k-rpboot.16.12.03a.SPA.pkg
397495 -rw- 31458308 May 27 2020 15:17:06 +12:00 cat9k-sipbase.16.12.03a.SPA.pkg
397496 -rw- 60355588 May 27 2020 15:17:06 +12:00 cat9k-sipspa.16.12.03a.SPA.pkg
397497 -rw- 22950916 May 27 2020 15:17:06 +12:00 cat9k-srdriver.16.12.03a.SPA.pkg
397498 -rw- 12891136 May 27 2020 15:17:06 +12:00 cat9k-webui.16.12.03a.SPA.pkg
397499 -rw- 9216 May 27 2020 15:17:06 +12:00 cat9k-wlc.16.12.03a.SPA.pkg

So you may just need to commit it, but first make sure the switch(s) are actually using the new software if they arent then you may need to reload.

sh boot system
sh version



kind regards
Paul

Please rate and mark posts accordingly if you have found any of the information provided useful.
It will hopefully assist others with similar issues in the future

View solution in original post

Highlighted
Hall of Fame Community Legend

Whao.   Wait.  That's not right.  That output does not look correct at all.  

Can you provide the output to the command 

more flash:packages.conf

I want to see the output from the 2nd page (I am not interested in the first page).

View solution in original post

10 REPLIES 10
Highlighted
Hall of Fame Community Legend

The correct process should be the following: 

1.  Copy the file into the flash:

copy tftp://<TFTP_IP_ADDRESS>/cat9k_iosxe.16.12.03a.SPA.bin bootflash:cat9k_iosxe.16.12.03a.SPA.bin

WARNING:  After Step 2, the switch will automatically reboot at the end of the unpacking process. 

2.  Unpack the file

install add file bootflash:cat9k_iosxe.16.12.03a.SPA.bin activate commit
Highlighted

Thanks Leo

 

I have already copied the IOS in to the 9500 stack.

 

The current status with the dir flash:*.pkg is as follows (Active currently is FUJI 16.9.4):

 

308276 -rw- 27231232 Dec 9 2019 19:03:51 +12:00 cat9k-cc_srdriver.16.09.04.SPA.pkg
308277 -rw- 81241084 Dec 9 2019 19:03:51 +12:00 cat9k-espbase.16.09.04.SPA.pkg
308278 -rw- 1647612 Dec 9 2019 19:03:51 +12:00 cat9k-guestshell.16.09.04.SPA.pkg
308279 -rw- 425411576 Dec 9 2019 19:03:51 +12:00 cat9k-rpbase.16.09.04.SPA.pkg
308285 -rw- 34612458 Dec 9 2019 19:04:07 +12:00 cat9k-rpboot.16.09.04.SPA.pkg
308280 -rw- 28931068 Dec 9 2019 19:03:51 +12:00 cat9k-sipbase.16.09.04.SPA.pkg
308281 -rw- 55047160 Dec 9 2019 19:03:51 +12:00 cat9k-sipspa.16.09.04.SPA.pkg
308282 -rw- 35243004 Dec 9 2019 19:03:51 +12:00 cat9k-srdriver.16.09.04.SPA.pkg
308283 -rw- 15856632 Dec 9 2019 19:03:51 +12:00 cat9k-webui.16.09.04.SPA.pkg
308284 -rw- 9208 Dec 9 2019 19:03:51 +12:00 cat9k-wlc.16.09.04.SPA.pkg
397492 -rw- 89113604 May 27 2020 15:17:05 +12:00 cat9k-espbase.16.12.03a.SPA.pkg
397491 -rw- 14291976 May 27 2020 15:17:05 +12:00 cat9k-cc_srdriver.16.12.03a.SPA.pkg
397493 -rw- 1680392 May 27 2020 15:17:05 +12:00 cat9k-guestshell.16.12.03a.SPA.pkg
397494 -rw- 530838532 May 27 2020 15:17:06 +12:00 cat9k-rpbase.16.12.03a.SPA.pkg
397500 -rw- 41796428 May 27 2020 15:17:25 +12:00 cat9k-rpboot.16.12.03a.SPA.pkg
397495 -rw- 31458308 May 27 2020 15:17:06 +12:00 cat9k-sipbase.16.12.03a.SPA.pkg
397496 -rw- 60355588 May 27 2020 15:17:06 +12:00 cat9k-sipspa.16.12.03a.SPA.pkg
397497 -rw- 22950916 May 27 2020 15:17:06 +12:00 cat9k-srdriver.16.12.03a.SPA.pkg
397498 -rw- 12891136 May 27 2020 15:17:06 +12:00 cat9k-webui.16.12.03a.SPA.pkg
397499 -rw- 9216 May 27 2020 15:17:06 +12:00 cat9k-wlc.16.12.03a.SPA.pkg

 

dir flash:*.conf

308275 -rw- 7554 Dec 9 2019 19:04:07 +12:00 packages.conf
397490 -rw- 7613 May 27 2020 15:17:25 +12:00 cat9k_iosxe.16.12.03a.SPA.conf

 

Please if you can guide with the above files whether we will be ok to do a install activate auto-abort-timer 60 and once the switches is fully online and tested ok, then we can do a install commit.

 

 

View solution in original post

Highlighted
Hall of Fame Community Legend

Post the complete output to the following commands: 

sh boot
more flash:packages.conf | b CAT9k
Highlighted

Thanks Leo

 

The output is as follows:

 

VSS#show boot
BOOT variable = bootflash:packages.conf;
Configuration Register is 0x102
MANUAL_BOOT variable = no
BAUD variable = 9600
ENABLE_BREAK variable does not exist
BOOTMODE variable does not exist
IPXE_TIMEOUT variable does not exist
CONFIG_FILE variable =

 

Standby BOOT variable = bootflash:packages.conf;
Standby Configuration Register is 0x102
Standby MANUAL_BOOT variable = no
Standby BAUD variable = 9600
Standby ENABLE_BREAK variable does not exist
Standby BOOTMODE variable does not exist
Standby IPXE_TIMEOUT variable does not exist
Standby CONFIG_FILE variable =


VSS#more flash:packages.conf | b CAT9K
# pkginfo: Platform: CAT9K
# pkginfo: User: mcpre
# pkginfo: PackageName: universalk9
# pkginfo: Build: 16.09.04
# pkginfo: .SupportedBoards: cat9k
# pkginfo: .InstallModel:
# pkginfo: .PackageRole: rp_super
# pkginfo: .RestartRole: rp_super
# pkginfo: .UnifiedPlatformList: passport,nyquist,starfleet
# pkginfo: CardTypes:
# pkginfo: .CardTypes:
# pkginfo: .BuildPath: /scratch/mcpre/release/BLD-V16_09_04_FC2/binos/linkfarm/s tage-cat9k/hard/rp_super_universalk9.x86_64
# pkginfo: .Version: 16.9.4.0.3431.1566523032..Fuji
# pkginfo: .InstallVersion: 1.0.0
# pkginfo: .InstallCapCommitSupport: yes
#
# -end- superpackage .pkginfo
#

Highlighted
Hall of Fame Community Legend

Whao.   Wait.  That's not right.  That output does not look correct at all.  

Can you provide the output to the command 

more flash:packages.conf

I want to see the output from the 2nd page (I am not interested in the first page).

View solution in original post

Highlighted

Thanks Leo

 

Please find it below. I have not run the command install activate auto-abort-timer 60 and the install commit as yet.

 

Will only do it once we are ok that the switch will come up on Gibraltar 16.12.03a.

 

Currently, the switch is running FUJI 16.09.04 in the stack.

 

For the Gibraltar 16.12.03a, have just ran the command 

  1. install add file tftp://192.168.1.100/ cat9k_iosxe.16.12.03a.SPA.bin

So I am assuming that the packages.conf would not be updated from just the install add file.... I believe the install add file only copies the .bin and extracts the packages into the flash...

 

Please correct me if I am wrong.

 

VSS#more flash:packages.conf
#! /usr/binos/bin/packages_conf.sh

sha1sum: ccc8fba2f434a5eaaeef10346bfc4fa5827a1e61

# sha1sum above - used to verify that this file is not corrupted.

#
# package.conf: provisioned software file for build 2019-08-22_18.17
#

# NOTE: Editing this file by hand is not recommended. It is generated
# as part of the build process, and is subject to boot-time
# consistency checks. Automatically-produced package files are
# guaranteed to pass those checks. Manually-maintained ones are
# not. Because "nfs" and "mount" directives are processed first,
# regardless of their position in the file, the recommended
# approach is to keep a separate file containing JUST your
# personal "nfs" and "mount" directives, and to append it to the
# automatically-generated file.
#
# Note further that when SHA-1 checksum verification is enabled,
# you will NOT be able to alter this file without updating the
# SHA-1 sum.

#
# This file can contain three types of entries:
#

#
# NFS directives (optional)
# notes: NFS directives are processed before all others (mount, iso).
# Multiple NFS directives may appear so long as they do not
# conflict -- that is, specify the same source or mountpoint.
# syntax: nfs <IP ADDRESS>:<REMOTE_PATH> <LOCAL_MOUNTPOINT>
# example: nfs 127.0.0.1:/auto/some/nfs/path /auto/some/nfs/path
#

#
# mount directives (optional)
# notes: mount directives are processed after 'nfs' and before 'iso'.
# One mount directive may appear for each F/S/B/P tuple
# syntax: mount FRU SLOT BAY PACKAGE_NAME LINUX_PATH
# example: mount rp 0 0 rp_base /auto/some/nfs/path/abs_soft/rp_base.ppc
#
# The specified LINUX_PATH may be local [sata disk] or
# reference the NFS mounts since they are processed first.
#
# Mount directives cause the package-specific mount link to
# be set to the specified path instead of to the mountpoint
# in sw for the corresponding ISO.
#

#
# iso directives (mandatory)
# notes: iso directives are processed last: any package for which
# a 'mount' directive does not appear will be mounted.
# One iso directive may appear for each F/S/B/P tuple.
# syntax: iso FRU SLOT BAY PACKAGE_NAME PACKAGE_FILE.bin
# example: iso rp 0 0 rp_base rp_base.ppc.bin
#
# PACKAGE_FILE.bin is a path relative to the packages.conf
# file. Although it supports sub-directories for development
# purposes, in deployment the files will always be managed
# as in the same directory as packages.conf so as to
# guarantee that name collisions cannot occur.
#
# Note that the RP 0/1 distinction is a convenience for development
# and testing as it allows us to have a packages.conf describe a
# SW load that varies depending on whether the RP finds itself in
# slot 0 or 1.
#
# The ISSU process *must* update *both* RP slots simultaneously so that
# the RP will behave predictably whichever slot it finds itself on [e.g.,
# if package X is upgraded, and the RP is ejected and put into either
# slot of a new chassis, we expect to see the upgraded X without regard
# to slot].
#

# This is for CAT9k
boot rp 0 0 rp_boot cat9k-rpboot.16.09.04.SPA.pkg
iso rp 0 0 rp_base cat9k-rpbase.16.09.04.SPA.pkg
iso rp 0 0 rp_daemons cat9k-rpbase.16.09.04.SPA.pkg
iso rp 0 0 rp_iosd cat9k-rpbase.16.09.04.SPA.pkg
iso rp 0 0 rp_security cat9k-rpbase.16.09.04.SPA.pkg
iso rp 0 0 rp_wlc cat9k-wlc.16.09.04.SPA.pkg
iso rp 0 0 rp_webui cat9k-webui.16.09.04.SPA.pkg
iso rp 0 0 srdriver cat9k-srdriver.16.09.04.SPA.pkg
iso rp 0 0 guestshell cat9k-guestshell.16.09.04.SPA.pkg

boot rp 1 0 rp_boot cat9k-rpboot.16.09.04.SPA.pkg
iso rp 1 0 rp_base cat9k-rpbase.16.09.04.SPA.pkg
iso rp 1 0 rp_daemons cat9k-rpbase.16.09.04.SPA.pkg
iso rp 1 0 rp_iosd cat9k-rpbase.16.09.04.SPA.pkg
iso rp 1 0 rp_security cat9k-rpbase.16.09.04.SPA.pkg
iso rp 1 0 rp_wlc cat9k-wlc.16.09.04.SPA.pkg
iso rp 1 0 rp_webui cat9k-webui.16.09.04.SPA.pkg
iso rp 1 0 srdriver cat9k-srdriver.16.09.04.SPA.pkg
iso rp 1 0 guestshell cat9k-guestshell.16.09.04.SPA.pkg

iso fp 0 0 fp cat9k-espbase.16.09.04.SPA.pkg
iso fp 1 0 fp cat9k-espbase.16.09.04.SPA.pkg

iso cc 0 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 1 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 2 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 3 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 4 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 5 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 6 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 7 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 8 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 9 0 cc cat9k-sipbase.16.09.04.SPA.pkg
iso cc 10 0 cc cat9k-sipbase.16.09.04.SPA.pkg

iso cc 0 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 1 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 2 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 3 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 4 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 5 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 6 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 7 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 8 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 9 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg
iso cc 10 0 cc_spa cat9k-sipspa.16.09.04.SPA.pkg

iso cc 0 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 1 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 2 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 3 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 4 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 5 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 6 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 7 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 8 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 9 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg
iso cc 10 0 cc_srdriver cat9k-cc_srdriver.16.09.04.SPA.pkg

#
# -start- superpackage .pkginfo
#
# pkginfo: Name: rp_super
# pkginfo: BuildTime: 2019-08-22_18.17
# pkginfo: ReleaseDate: Thu-22-Aug-19-19:22
# pkginfo: .BuildArch: x86_64
# pkginfo: BootArchitecture: i686
# pkginfo: .BootArch: i686
# pkginfo: RouteProcessor: cat9k
# pkginfo: Platform: CAT9K
# pkginfo: User: mcpre
# pkginfo: PackageName: universalk9
# pkginfo: Build: 16.09.04
# pkginfo: .SupportedBoards: cat9k
# pkginfo: .InstallModel:
# pkginfo: .PackageRole: rp_super
# pkginfo: .RestartRole: rp_super
# pkginfo: .UnifiedPlatformList: passport,nyquist,starfleet
# pkginfo: CardTypes:
# pkginfo: .CardTypes:
# pkginfo: .BuildPath: /scratch/mcpre/release/BLD-V16_09_04_FC2/binos/linkfarm/stage-cat9k/hard/rp_super_universalk9.x86_64
# pkginfo: .Version: 16.9.4.0.3431.1566523032..Fuji
# pkginfo: .InstallVersion: 1.0.0
# pkginfo: .InstallCapCommitSupport: yes
#
# -end- superpackage .pkginfo
#

Highlighted
Hall of Fame Community Legend

The command is missing the options to activate and commit:

install add file bootflash:cat9k_iosxe.16.12.03a.SPA.bin activate commit

This command will automatically reboot the appliance after the unpacking is complete.

Highlighted
VIP Mentor

Hello
I upgraded a 9300 distribution stack today via USB, 95Ks should be similar if not the same procedure (check release notes)

When you actually perform the install the .bin file,  .PKGs files gets extracted to the flash, Then you shouldn't(well i didn't) see the .bin file after this extraction

dir flash:*.pkg's < should see two sets of PKGs old and new beginning with  xxxx.cc_srdiverc.xxxxx

dir flash:*.conf < should see update packages.conf file and new software backup conf file 

 

1) install remove active <  cleans up old inactive install files
2) copy usbflash1:xxxxxxxx.bin flash: < you only need to do this on the stack master
3) dir flash *.pkg's, dir flash:*.conf
4) show boot system < check for packages.conf is the boot variable
5) install add file flash:xxxxxxxx.bin activate commit < installs the new software to stack and activates it
6) stack reloads

7) install remove active <  once your happy with the new software



kind regards
Paul

Please rate and mark posts accordingly if you have found any of the information provided useful.
It will hopefully assist others with similar issues in the future

View solution in original post

Highlighted

Thanks Paul.

 

I have already copied the IOS in to the 9500 stack.

 

The current status with the dir flash:*.pkg is as follows (Active currently is FUJI 16.9.4):

 

308276 -rw- 27231232 Dec 9 2019 19:03:51 +12:00 cat9k-cc_srdriver.16.09.04.SPA.pkg
308277 -rw- 81241084 Dec 9 2019 19:03:51 +12:00 cat9k-espbase.16.09.04.SPA.pkg
308278 -rw- 1647612 Dec 9 2019 19:03:51 +12:00 cat9k-guestshell.16.09.04.SPA.pkg
308279 -rw- 425411576 Dec 9 2019 19:03:51 +12:00 cat9k-rpbase.16.09.04.SPA.pkg
308285 -rw- 34612458 Dec 9 2019 19:04:07 +12:00 cat9k-rpboot.16.09.04.SPA.pkg
308280 -rw- 28931068 Dec 9 2019 19:03:51 +12:00 cat9k-sipbase.16.09.04.SPA.pkg
308281 -rw- 55047160 Dec 9 2019 19:03:51 +12:00 cat9k-sipspa.16.09.04.SPA.pkg
308282 -rw- 35243004 Dec 9 2019 19:03:51 +12:00 cat9k-srdriver.16.09.04.SPA.pkg
308283 -rw- 15856632 Dec 9 2019 19:03:51 +12:00 cat9k-webui.16.09.04.SPA.pkg
308284 -rw- 9208 Dec 9 2019 19:03:51 +12:00 cat9k-wlc.16.09.04.SPA.pkg
397492 -rw- 89113604 May 27 2020 15:17:05 +12:00 cat9k-espbase.16.12.03a.SPA.pkg
397491 -rw- 14291976 May 27 2020 15:17:05 +12:00 cat9k-cc_srdriver.16.12.03a.SPA.pkg
397493 -rw- 1680392 May 27 2020 15:17:05 +12:00 cat9k-guestshell.16.12.03a.SPA.pkg
397494 -rw- 530838532 May 27 2020 15:17:06 +12:00 cat9k-rpbase.16.12.03a.SPA.pkg
397500 -rw- 41796428 May 27 2020 15:17:25 +12:00 cat9k-rpboot.16.12.03a.SPA.pkg
397495 -rw- 31458308 May 27 2020 15:17:06 +12:00 cat9k-sipbase.16.12.03a.SPA.pkg
397496 -rw- 60355588 May 27 2020 15:17:06 +12:00 cat9k-sipspa.16.12.03a.SPA.pkg
397497 -rw- 22950916 May 27 2020 15:17:06 +12:00 cat9k-srdriver.16.12.03a.SPA.pkg
397498 -rw- 12891136 May 27 2020 15:17:06 +12:00 cat9k-webui.16.12.03a.SPA.pkg
397499 -rw- 9216 May 27 2020 15:17:06 +12:00 cat9k-wlc.16.12.03a.SPA.pkg

 

dir flash:*.conf

308275 -rw- 7554 Dec 9 2019 19:04:07 +12:00 packages.conf
397490 -rw- 7613 May 27 2020 15:17:25 +12:00 cat9k_iosxe.16.12.03a.SPA.conf

 

Please if you can guide with the above files whether we will be ok to do a install activate auto-abort-timer 60 and once the switches is fully online and tested ok, then we can do a install commit.

 

 

Highlighted

Hello

The command i used added/installed and committed the software all in one, but you can do each step individually however it looks like you’ve already added and installed the new software,


397492 -rw- 89113604 May 27 2020 15:17:05 +12:00 cat9k-espbase.16.12.03a.SPA.pkg
397491 -rw- 14291976 May 27 2020 15:17:05 +12:00 cat9k-cc_srdriver.16.12.03a.SPA.pkg
397493 -rw- 1680392 May 27 2020 15:17:05 +12:00 cat9k-guestshell.16.12.03a.SPA.pkg
397494 -rw- 530838532 May 27 2020 15:17:06 +12:00 cat9k-rpbase.16.12.03a.SPA.pkg
397500 -rw- 41796428 May 27 2020 15:17:25 +12:00 cat9k-rpboot.16.12.03a.SPA.pkg
397495 -rw- 31458308 May 27 2020 15:17:06 +12:00 cat9k-sipbase.16.12.03a.SPA.pkg
397496 -rw- 60355588 May 27 2020 15:17:06 +12:00 cat9k-sipspa.16.12.03a.SPA.pkg
397497 -rw- 22950916 May 27 2020 15:17:06 +12:00 cat9k-srdriver.16.12.03a.SPA.pkg
397498 -rw- 12891136 May 27 2020 15:17:06 +12:00 cat9k-webui.16.12.03a.SPA.pkg
397499 -rw- 9216 May 27 2020 15:17:06 +12:00 cat9k-wlc.16.12.03a.SPA.pkg

So you may just need to commit it, but first make sure the switch(s) are actually using the new software if they arent then you may need to reload.

sh boot system
sh version



kind regards
Paul

Please rate and mark posts accordingly if you have found any of the information provided useful.
It will hopefully assist others with similar issues in the future

View solution in original post

Content for Community-Ad