ROMMON CV value in sup720 / 6500 VSS

[~chris]

Hi all,

our customer did a successfully eFSU on Catalyst 6500 VSS.

After checking the issu state w/ "show issu state detail" he is seeing that output:

sh issu state det
                          Slot = 5
                      RP State = Active
                    ISSU State = Init
                 Boot Variable = disk1:s72033-advipservicesk9-mz.151-2.SY.bin,12;disk1:s72033-advipservicesk9-mz.151-1.SY1.bin,12;
                Operating Mode = sso
               Primary Version = N/A
             Secondary Version = N/A
               Current Version = disk1:s72033-advipservicesk9-mz.151-2.SY.bin
                Variable Store = PrstVbl
                     ROMMON CV = [disk1:/s72033-advipservicesk9_wan-mz.122-33.SXH3a.bin]

                          Slot = 6
                      RP State = Standby
                    ISSU State = Init
                 Boot Variable = disk1:s72033-advipservicesk9-mz.151-2.SY.bin,12;disk1:s72033-advipservicesk9-mz.151-1.SY1.bin,12;
                Operating Mode = sso
               Primary Version = N/A
             Secondary Version = N/A
               Current Version = disk1:s72033-advipservicesk9-mz.151-2.SY.bin

The question is:
What is the meaning of that line: ROMMON CV = [disk1:/s72033-advipservicesk9_wan-mz.122-33.SXH3a.bin]

I see this ROMMO CV only on the active SUP. The version in ROMMON CV points to a very old version which has been deleted from
all storage-devices in the Catalyst.

How can it be changed and does it have any impact? Maybe for the next eFSU?

regards
./chris

[Tinya Cheng · Accepted solution]

You can effectively ignore this. CV stands for "Current Version". Similarly, PV stands for "Previous Version". The CV and PV values were used in early version ISSU upgrades. They were used to help the supervisor keep track of what the current and previous versions were.

eFSU/ISSU now use persistent variables in persistent memory to keep track of this. The CV value you're seeing is likely left over from an old ISSU upgrade, hence, the old, non-existent version.

This should not affect your future upgrades. Perhaps the only impact it would have is when you issue a "reset" from ROMMON. You may experience the supervisor attempting to boot from your old version, failing, and going back to ROMMON. In that case, you can unset the CV= value from ROMMON when this happens.

Sent from Cisco Technical Support Android App

[~chris]

Thanks for your good explanation!

regards

./chris