Cisco SAN Switch
Firmware Update Procedure
SAN-OS
contains 2 packages
1) Kickstart
– image (linux kernel files)
2) System – image (commands and
program files)
Latest
firmware is 3.1 (3a)
Direct
update to 3.1(3a) is allowed from 2.1 (2b), 2.1(2d), 3.0(1), 3.0(2a), 3.0(3),
3.1(2a), 3.1(3).
Now the
firmware flash requires a compact flash card (CF). This CF card is seen in the Cisco SAN-OS as
bootflash card.
There is
an issue, where if you insert a new firmware CF card, and the CF card checkup
utility script finds a bad CF card.
SAW document id: c00876068
The steps
to perform firmware update are as follows
# copy running startup-config
This will save the running
configuration as the startup configuration
# copy running ftp://
address>/
This will save the running
configuration to a FTP site
# show install all impact
This will show the impact of
“install all” command
# show install all failure-reason
This will show the reason why
“install all” command has failed in past.
# cd bootfalsh:
# dir
This will show the contents of the
bootflash (CF) card, and how much space is used and left in the card.
This step is important because the
kickstart image is ~ 20MB and system image is ~80 MB. Thus approx ~ 100 MB
space in bootflash is required.
# copy ftp://
address>/ m9100-s1ek9-kickstart-mz.3.1.3a.bin bootflash:
m9100-s1ek9-kickstart-mz.3.1.3a.bin
This will copy the file
“m9100-s1ek9-kickstart-mz.3.1.3a.bin” from the ftp site to Bootflash
# copy ftp://
address>/m9100-s1ek9-mz.3.1.3a.bin
bootflash: m9100-s1ek9-mz.3.1.3a.bin
This will copy the file
“m9100-s1ek9-mz.3.1.3a.bin” from the ftp site to the Bootflash
# install all kickstart
bootflash:m9100-s1ek9-kickstart-mz.3.1.3a.bin
# install all system
bootflash:m9100-s1ek9-mz.3.1.3a.bin
This will install the Kickstart and
System image from the bootflash.
-----------------------------------------------------------------------------------------------------------
License Key installation
License
key is a readable text file (.lic), and it has the serial number of the chassis
in readable and encrypted format.
Chassis
serial# is also called as host-id
# show license host-id
This
show unique id for this host (chassis) for licensing
# show license usage
Shows the status and usage of
license.
# show license brief
This shows the list of license
files
# copy
bootflash:/// ftp://
address>/
This will save the license file to
a ftp location
This will copy the license file from
the ftp site to the bootflash
# install license
bootflash:///
This will install the license file
from the bootflash.
Once installed
license, can check the activation of license, by “# show license usage”
# clear license
This will clear the license
Eg:
# show license brief
Enterprise_PKG.lic
FabricManager_lic
# clear license Enterprise_PKG.lic
….
….
….
Do you
want to continue (y/n) : Y
Clearing
license …….done
License
is bound to serial #, in case of switch or motherboard replacement new license
key needs to be generated.
1 comment:
Hi There,
Thank you for sharing a knowledgeable blog with us I hope that you will post many more blog with us :)
We are providing the best IT consulting services in whole USA as like as shutdown unix command, brocade zoning commands, types of zoning in san, cisco zoning commands, vmax3 provisioning steps, snapvx, san zoning, unix flavors, timefinder snapvx, san storage explained, storage provisioning steps, emc snapvx, san zoning, symsg commands, how to backup brocade switch config, snapvx step by step, vmax snapvx, san zoning steps, gatekeeper device, zoning explained, emc vmax3, vsan vs zoning, dell emc vmax3, difference between vmax and vmax3, thin provisioning explained, data sovereignty requirements.
Click here for more information:- cisco zoning commands
Post a Comment