VSS Upgrade using EFSU

[Farooq Razzaque]

Hi All,

Using EFSU, I want to upgrade the Cat.6513 switches running in VSS with currently installed IOS -ipservicesk9_wan-mz.122-33.SXI3.bin.

Want to upgrade to lastest available version in SXI which is SXI13

Eager to understand from members here how successful ISSU is on 65xx platform and does it really mean zero downtime impact?

Any practical experience from those who performed upgrade in VSS scenerio using EFSU

When standby chassis get reloaded in ISSU loadversion step then only all the modules (Service modules & line cards) on standby chassis get reloaded or the modules on Active chassis will also get reloaded.

When Active chassis get reloaded during switchover in ISSU runversion then only the modules (Service modules & line cards) on Active chassis get reloaded or the modules on standby chassis will also get reloaded.

I have service modules installed in both the chassis. Does EFSU have any dependency on these service modules.

Mod Ports Card Type                              Model              
--- ----- -------------------------------------- ------------------ 
  3    1  Application Control Engine Module      ACE20-MOD-K9       
  4    6  Firewall Module                        WS-SVC-FWM-1       
  5    8  Intrusion Detection System             WS-SVC-IDSM-2      
  6    8  Network Analysis Module                WS-SVC-NAM-2-250S  
  7    5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        
  9    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      
 10    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      
 11   48  CEF720 48 port 1000mb SFP              WS-X6748-SFP       
 12   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     
 13   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     

[Leo Laohoo]

There are three methods to upgrade a VSS chassis.  They are:  

1.  eFSU/ISSU; 

2.  Using config-registry 0x2101; or

3.  Using config-registry 0x2102

Go here.  The link will give you how to upgrade your VSS with Options 2 and 3.  If eFSU works, then you'll have minimal downtime.  If it doesn't, you'll have downtime.  Period.

[alf]

Hello,

first you should check the eFSU compatibility matrix. Usually eFSU is only supported if source and target IOS images are within one year of publication. Otherwise this means multiple steps.

I also think that the described IOS Upgrade processes (whatever) for VSS systems are not reflecting impact on service modules, that means you need to make an individual migration plan, which service module to switchover manually during the upgrade process. Otherwise service modules will be rebooted as other line cards. Remember that service modules are "single attached" devices with their own OS, operational state and configuration, even if they are installed within the VSS Chassis.

Although I did not have service-modules in my installation, I decided to go with FSU because of the many interim steps for eFSU. In any case and even with eFSU, I would never commit zero-downtime for a software upgrade of a cluster core device, because there always might happen individual issues.

You can also check the parallel discussion:

https://supportforums.cisco.com/discussion/12093401/vss-ios-upgrade-efsu-vs-fsu

Hope that helps

Alfred

[Farooq Razzaque]

Dear All

During SSO supervisor switchover from active to standby SUP, do the linecards and service modules still have to reset? Is that reset occur only on Standby SUP or both on Active & Standby SUP 

For Modules support eFSU, will these line cards still reset ?

According to below document only following modules supports eFSU and outage time is 300 sec for  Module WS-X6708-10GE ( CEF720 8 port 10GE with DFC ) and outage time is 360 for modules (WS-X6748-SFP & WS-X6748-GE-TX)

The following modules support eFSU preload:

– WS-X67xx modules
– SIP-400 and SIP-600

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/issu_efsu.html#wp1130376

Preloading new module software into memory on supported modules to avoid a hard reset.

If the new software release contains new module software, eFSU preloads the new module software onto any modules in the switch that support eFSU preload. When the switchover occurs between the active and standby supervisor engines, the modules are restarted with the new software image.

The following modules support eFSU preload:
– WS-X67xx modules
– SIP-400 and SIP-600
All other modules undergo a hard reset at switchover, and the software image loads after the module restarts.

Outage Time and Support Considerations

During an eFSU upgrade, modules are restarted or reset after the switchover that occurs between the supervisor engines. Because the modules are restarted or reset, any links attached to the modules go up and down and traffic processing is disrupted until protocols and software features are brought back online. The length of time that module processing is disrupted (outage time) depends on whether the eFSU process was able to preload a new software image onto the module.
• For modules that support eFSU preload, the outage time for an eFSU module warm reload is faster than an RPR mode module reload.
• For modules that do not support eFSU preload, the outage time for module reload is similar to an RPR mode module reload.
Once the new software is loaded (issu loadversion), you can use the show issu outage slot all command to display the maximum outage time for installed modules. See the “Displaying the Maximum Outage
 

Displaying the Maximum Outage Time for Installed Modules (Optional)

Once the new software is downloaded, you can enter the show issu outage slot all command on the switch processor to display the maximum outage time for the installed modules:

Router# show issu outage slot all

Slot # Card Type     MDR Mode Max Outage Time

------ ------------------------------------------- ----------- ---------------

1 CEF720 8 port 10GE with DFC WARM_RELOAD 300 secs

2 96-port 10/100 Mbps RJ45 RELOAD 360 secs

4 CEF720 48 port 1000mb SFP RELOAD 360 secs

[Farooq Razzaque]

Hi All,

Anyone else will share his experience please.

[Maria Yurkina]

Hi, farooqrazzaque.

Some expirience.

Last year we apgraded our VSS from SXI5 to SXJ4. It is pruned in Compatibility Matrix. But there was no problem. 

It was only 1 ping loss to our server segment, when we entered issu runversion. All service modules (IDSM, FWSM) reloaded while eFSU and it is normal.

You shuold carefully read the instruction (http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/issu_efsu.html) and it will be ok.

..but it's better if you can test an upgrade procedure somewhere :)

[Farooq Razzaque]

Dear Maria

What line card and service modules did you have in the chassis during the upgrade.

I just want to know after initiating the command the issu runversion, the current standby chassis takes over the role as the new active chassis and formerly active chassis will reload with all the line cards and service modules installed in that chassis so i want to know during the reload of formerly active chassis, will the line cards and service modules (IDSM,FWSM,ACE etc) reset/reload installed in formerly standby chassis (new active chassis) or not