I have been configuring and deploying different Cisco routers and switches, and all of them has the same usability. Checking the location of IOS on routers and switches simply use show flash:
or dir
command, this is not the case on Cisco 7609S.
Cisco 7609S storage filesystem is more complex than other Cisco routers and switches which I have encountered.
Cannot find IOS but the IOS is booted?!
Cisco 7609S RPS720 has two CF flash slots labeled as DISK0 and DISK1.
To show the contents of the CF flash use show disk0:
command.
C7609-1#sh disk0: No files on device 256524288 bytes available (0 bytes used) C7609-1#
It turns out that IOS is not in the external compact flash and no configuration files was saved in CF.
From the “?” I found this command show bootdisk:
, naturally I thought the IOS must have stored in this partition, but I was wrong.
C7609-1#sh bootdisk: No files on device 512090112 bytes available (0 bytes used) C7609-1#
Use the dir ?
I saw multiple partitions.
C7609-1#dir ? /all List all files /recursive List files recursively all-filesystems List files on all filesystems bootdisk: Directory or file name cns: Directory or file name const_nvram: Directory or file name dfc#1-bootflash: Directory or file name dfc#2-bootdisk: Directory or file name dfc#3-bootdisk: Directory or file name dfc#4-bootdisk: Directory or file name disk0: Directory or file name disk1: Directory or file name flexwan-fpd: Directory or file name null: Directory or file name nvram: Directory or file name revrcsf: Directory or file name slavebootdisk: Directory or file name slaveconst_nvram: Directory or file name slavedisk0: Directory or file name slavedisk1: Directory or file name slavenvram: Directory or file name slavercsf: Directory or file name slavesup-bootdisk: Directory or file name slavesystem: Directory or file name sup-bootdisk: Directory or file name sup-microcode: Directory or file name system: Directory or file name tar: Directory or file name tmpsys: Directory or file name <cr> C7609-1#
But I decided not to go in one by one instead I want to study and understand the partitions.
Additionally the boot variable is empty, how does IOS load when there is no pointer to boot the IOS?
C7609-1#sh bootvar BOOT variable = CONFIG_FILE variable = BOOTLDR variable = Configuration register is 0x2102 Standby BOOT variable = Standby CONFIG_FILE variable = Standby BOOTLDR variable = Standby Configuration register is 0x2102 C7609-1#
Exploring the file systems
Use show file systems
command to display the entire filesystems detail.
C7609-1#sh file systems File Systems: Size(b) Free(b) Type Flags Prefixes - - opaque rw system: - - opaque rw tmpsys: - - opaque ro flexwan-fpd: * 256524288 256524288 disk rw disk0: - - disk rw disk1: 512081920 308699136 disk rw sup-bootdisk: 126386878 0 opaque ro sup-microcode: 0 476566804 opaque wo sup-image: 127212 126108 nvram rw const_nvram: - - opaque rw null: - - opaque ro tar: - - network rw tftp: - - opaque wo syslog: 4059328 4050580 nvram rw nvram: 512090112 512090112 disk rw bootdisk:# - - network rw rcp: - - network rw ftp: - - network rw http: - - network rw scp: - - network rw https: - - opaque ro cns: 4059328 4050580 nvram rw slavenvram: 127212 126108 nvram rw slaveconst_nvram: 256524288 256524288 disk rw slavedisk0: - - disk rw slavedisk1: 512081920 347807744 disk rw slavesup-bootdisk: 512090112 512090112 disk rw slavebootdisk: - - nvram rw slavercsf: - - opaque rw slavesystem: 1024573440 1023606784 disk rw dfc#2-bootdisk: 1024573440 1023606784 disk rw dfc#3-bootdisk: 1024573440 1023606784 disk rw dfc#4-bootdisk: 32768000 32768000 flash rw dfc#1-bootflash: - - opaque rw revrcsf: C7609-1#
Now this output is very clear, I look for the partitions which are utilized and went in to explore.
It turns out that the IOS is stored in the sup-bootdisk:
and slavesup-bootdisk:
partitions.
C7609-1#sh sup-bootdisk: -#- --length-- -----date/time------ path 1 130713444 May 25 2012 06:46:54 +00:00 c7600rsp72043-advipservicesk9-mz.122-33.SRD8.bin 2 33554432 Aug 6 2012 02:22:22 +00:00 sea_log.dat 3 39106560 May 25 2012 14:12:04 +00:00 c7600-fpd-pkg.122-33.SRD8.pkg 308699136 bytes available (203382784 bytes used) C7609-1# C7609-1#sh slavesup-bootdisk: -#- --length-- -----date/time------ path 1 130713444 May 25 2012 06:56:14 +00:00 c7600rsp72043-advipservicesk9-mz.122-33.SRD8.bin 2 33554432 Aug 6 2012 02:23:44 +00:00 sea_log.dat 347807744 bytes available (164274176 bytes used) C7609-1#
The startup-config and other persistent configs are stored in nvram: (of course :))
C7609-1#dir nvram: Directory of nvram:/ 3965 -rw- 5599 <no date> startup-config 3966 ---- 25 <no date> private-config 3967 -rw- 5599 <no date> underlying-config 1 ---- 0 <no date> rf_cold_starts 2 ---- 258 <no date> persistent-data 3 -rw- 0 <no date> ifIndex-table 4059328 bytes total (4050580 bytes free) C7609-1#
The running-config is stored in system:
C7609-1#dir system: Directory of system:/ 2 -r-- 0 <no date> default-running-config 3 dr-x 0 <no date> memory 1 -rw- 5599 <no date> running-config 11 dr-x 0 <no date> vfiles No space information available C7609-1#
The vlan.dat file is stored in const_nvram:
C7609-1#dir const_nvram: Directory of const_nvram:/ 1 -rw- 1104 <no date> vlan.dat 127212 bytes total (126108 bytes free) C7609-1#
To filter the type you want to see for example I only want to see disk type.
C7609-1#sh file systems | include disk * 256524288 256524288 disk rw disk0: - - disk rw disk1: 512081920 308699136 disk rw sup-bootdisk: 512090112 512090112 disk rw bootdisk:# 256524288 256524288 disk rw slavedisk0: - - disk rw slavedisk1: 512081920 347807744 disk rw slavesup-bootdisk: 512090112 512090112 disk rw slavebootdisk: 1024573440 1023606784 disk rw dfc#2-bootdisk: 1024573440 1023606784 disk rw dfc#3-bootdisk: 1024573440 1023606784 disk rw dfc#4-bootdisk: C7609-1#
This is because of Supervisor Engines (2 slots, that’s why you get sup-bootdisk: & slavesup-bootdisk, one working as primary and other for redundancy) on Cisco7609. I have up-graded them and also while you up-grade there is different command to do that from the usual Cisco platfoms.
Regards,
Atif Saleem
I have used the 4506 catalyst switch, the SUPV engine did not have partition like 7609S, thanks for the information. I believe 7609 ISSU procedure should not be too different from the IOS way of doing…
How many SUPV Engines are there on 4506? Maybe it is for the 7609 being with dual SUPV Engines with disk partitions on them.
You are right the command is not way different rather the procedure is a bit different than traditional.
Just for reference (for people visiting here) following is the procedure to do up-grade.
If having flash disk installed in Router, upload IOS on it and do the following;
#no boot system flash
#write mem
#boot system flash disk1:xxxxxx.bin (name of IOS being up-graded to and to boot with new IOS after reload)
#boot system flash sup-bootflash:xxxxx(name of existing IOS which would be standby image)
#write mem
#copy tftp: sup-bootflash: (upon prompt give credentials and path to the IOS on tftp server, tftp server can be your system attached to Ethernet on SUPV Engine)
#show bootvar
#sh sup-bootflash: (here you can see current IOS and the IOS being up-graded to)
#reload
Also, if you do
#sh version
Then you may see the following in the output pointing to the IOS.
System image file is “sup-bootflash:xxxxx.bin” (name of current IOS)
After setting boot system to new IOS if you do “Sh running-config”, you should see following.
“boot-start-marker
boot system flash sup-bootflash:c7600s72033-advipservicesk9-mz.122-33.SRC2.bin (new IOS in my case to which 7609 was up-graded to)
boot-end-marker”
(Note: after setting boot system flash, you must write it in order to see it in your output)
Thanks,
Atif Saleem
Hi Atif Saleem thank you very much for sharing this valuable information. Oh regarding the sup engines V of 4506, it is a pair, but that one only supports SSO, 7609 RPS supports sso and nsf which I tested with a timer, 3seconds to recover. You on skype? Perhaps we should keep in touch 🙂
Yes, I am on skype (**obfuscated**), and NSF is a nice feature to have.
Hi, I have added you 🙂