Hi Peter,
Please find below upgrade procedure using ISSU:
Upgrade VSS using ISSU
Current State before ISSU Process:
Switch 1 - Active
Switch 2 - Hot Standby
Verify this using the command "show redundancy"
STEP 1:
- Make sure IOS image is saved in sup-bootdisk and slavesup-bootdisk (dir sup-bootdisk:, dir slavesup-bootdisk:)
STEP 2:
Run the following commands on to make sure, everything is working fine:
show issu state detail
show redundancy
show module switch all
STEP 3:
Run "issu loadversion" so that Standby Chassis reloads (Supervisor and its modules) and comes up in Hot Standby State with new upgarded image.
Command:
issu loadversion sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXI6.bin
Verification:
Wait until all the modules comes up and then verify the following:
show issu state detail
show redundancy
show module switch all
NOTE: “Current Version” for Standby should point to New Image in “show issu state detail” output.
STEP 4:
Run "issu runversion" to force switchover so that the Standby Chassis (with new image) will take the Active Role and former Active will reload and come up as Hot Standby running old image.
Command:
issu runversion
Verification:
Now Standby will become Current Active and have the control (and the active switch goes into Hot Standby). Verifyh from:
show issu state detail
show redundancy
show module switch all
NOTE: "Primary Version" and "Current Version" should point to new image for Current Active Switch in "show issu state detail" output.
STEP 5:
Run "issu acceptversion" to stop the Rollback Timer. (Because if the timer expires, the upgraded chassis reloads and reverts to the previous software version).
Command:
issu acceptversion
CAP-6500-1#issu acceptversion
% Rollback timer stopped. Please issue the commitversion command.
STEP 6:
Run "issu commitversion" so that the current Standby (Running Old image) will reload its SUP and modules and come up as Hot Standby with new upgraded image.
Command:
issu commitversion
NOTE: Everything point to new image and Boot Variable should display both old and new image in “show issu state detail” output.
STEP 7:
Verify that the upgrade was successful using the following commands:
show issu state detail
show redundancy
show module switch all
Current State after ISSU process:
Switch 2 - Active
Switch 1 - Hot Standby
NOTE: If you want Switch 1 to take over the Active role, perform "redundancy force-switchover".
Abortversion (Optional)
At any time before you enter the issu commitversion command, you can roll back the upgrade by entering the issu abortversion command. The upgrade process also aborts automatically if the software detects a failure. The rollback process depends on the current state. If the eFSU is aborted before you enter the issu runversion command, the VSS standby chassis is reloaded with the old image. If the eFSU is aborted after the issu runversion command, a switchover is executed. The VSS standby chassis, running the old image, becomes the VSS active chassis. The formerly VSS active chassis is then reloaded with the old image, completing the rollback.
Reference Link:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/vss.html#wp1169499
2-
Best practice on configuring the VSS:
http://www.cisco.com/en/US/products/ps9336/products_tech_note09186a0080a7c837.shtml
HTH
REgards
Inayathj
*Plz rate all usefull posts.
