I have been hitting a bug with the version of code we are running on our Cisco SSLM which is holding up a project rollout, as a result TAC have provided a version that it is fix on. I decided to give it a whirl in the test lab however spent a rather long time trying to work out how you upgrade the images on these modules with very little luck. It turns out it is straight forward (arnt all things when you know how to do it).

The procedure that I followed was;

  1. Back-up configuration on both the 6500 and SSLM, I also tend to take a copy of the current running image in case reversion is required.

  2. Put the SSLM into maintenance mode. This is achieved with the following commend from the 6500;

    SLB-Switch#hw-module module 7 reset cf:1 Device BOOT variable for reset = cf:1 Warning: Device list is not verified.

    Proceed with reload of module?[confirm] % reset issued for module 7

You will then notice if you you do a ‘show module’ the status will initially move to ‘other’ before displaying (MP).

SLB-Switch#sh mod 7
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
7    1  SSL Module                             WS-SVC-SSL-1       XXXXXXX
 
Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
7  xxxx.xxxx to xxxx.xxxx   3.2   7.2(1)       2.1(4)       Other
Mod  Online Diag Status
---- -------------------
7  Unknown

 

SLB-Switch# sh mod  7
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
7    1  SSL Module (MP) WS-SVC-SSL-1       XXXXXXX
 
Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
 
7  0014.a90c.c53a to 0014.a90c.c541   3.2   7.2(1)       2.1(2)m      Ok
Mod  Online Diag Status
---- -------------------
7  Pass

The logs will also show something similar to this.

Jul 28 15:33:10.003: SP: OS_BOOT_STATUS(7) MP OS Boot Status: finished booting
Jul 28 15:33:37.079: %DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics...
Jul 28 15:33:43.111: %SNMP-5-MODULETRAP: Module 7 [Up] Trap
Jul 28 15:33:43.115: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.
Jul 28 15:33:42.855: %DIAG-SP-6-DIAG_OK: Module 7: Passed Online Diagnostics
Jul 28 15:33:43.143: %OIR-SP-6-INSCARD: Card inserted in slot 7, interfaces are now online

 

Jul 28 15:26:16.507: %SNMP-5-MODULETRAP: Module 7 [Down] Trap
Jul 28 15:26:16.507: SP: The PC in slot 7 is shutting down. Please wait ...
Jul 28 15:26:40.331: SP: PC shutdown completed for module 7
Jul 28 15:26:40.343: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (Reset)
Jul 28 15:27:30.882: SP: OS_BOOT_STATUS(7) AP OS Boot Status: finished booting
Jul 28 15:28:35.337: %DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics...
Jul 28 15:28:36.085: %DIAG-SP-6-DIAG_OK: Module 7: Passed Online Diagnostics
Jul 28 15:28:36.343: %SNMP-5-MODULETRAP: Module 7 [Up] Trap
Jul 28 15:28:36.347: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.
Jul 28 15:28:36.373: %OIR-SP-6-INSCARD: Card inserted in slot 7, interfaces are now online
Jul 28 15:30:32.691: %SNMP-5-MODULETRAP: Module 7 [Down] Trap
Jul 28 15:30:32.691: SP: The PC in slot 7 is shutting down. Please wait ...
Jul 28 15:30:53.555: SP: PC shutdown completed for module 7
Jul 28 15:30:53.563: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (Reset)

  1. We then install the image by retrieving it from a TFTP server. The pclc#7 bit you just simpily replace 7 for te module you are updating.

    SLB-Switch#copy tftp: pclc#7-fs: Address or name of remote host []? 192.168.1.1

    Source filename []? c6svc-ssl-k9y9.2-1-12-6.bin Destination filename [c6svc-ssl-k9y9.2-1-12-6.bin]? Accessing tftp://192.168.1.1/c6svc-ssl-k9y9.2-1-12-6.bin… Loading c6svc-ssl-k9y9.2-1-12-6.bin from 128.253.20.23 (via GigabitEthernet4/2): !!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!! etc..

    [OK - 18507249 bytes]

    18507249 bytes copied in 158.988 secs (116407 bytes/sec) SLB-Switch#

The logs will look something like this, note that it takes around 5 minutes to upgrade the image. It doesn’t really tell you that, although if you try and restart the module you will get an error message back. I just kept checking the logs to see the desired confirmation.

Jul 28 15:38:03.483: %SVCLC-SP-5-STRRECVD: mod 7: <Application upgrade has started>
Jul 28 15:38:03.483: %SVCLC-SP-5-STRRECVD: mod 7: <Do not reset the module till upgrade completes!!>
Jul 28 15:43:32.035: %SVCLC-SP-5-STRRECVD: mod 7: <Application upgrade has succeeded>
Jul 28 15:43:32.035: %SVCLC-SP-5-STRRECVD: mod 7: <You can now reset the module>

  1. Once see the message that the upgrade has been succsesful you can reload the module for it to take effect.

    SLB-Switch#hw-module module 7 reset Device BOOT variable for reset = Warning: Device list is not verified.

    Proceed with reload of module?[confirm] % reset issued for module 7

The logs will show somthing like this (similar to previously)

Jul 28 15:44:14.079: %SNMP-5-MODULETRAP: Module 7 [Down] Trap
Jul 28 15:44:14.075: SP: The PC in slot 7 is shutting down. Please wait ...
Jul 28 15:44:36.619: SP: PC shutdown completed for module 7
Jul 28 15:44:36.631: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (Reset)
Jul 28 15:45:27.095: SP: OS_BOOT_STATUS(7) AP OS Boot Status: finished booting

  1. You can then do a ‘show module’  and confirm that you new shiny version of code is running.

    SLB-Switch# sh mod 7 Mod Ports Card Type Model Serial No.

    7 1 SSL Module WS-SVC-SSL-1 xxxxxx Mod MAC addresses Hw Fw Sw Status

    7 xxxx.xxxxx to xxxx.xxxxx 3.2 7.2(1) 2.1(12) Ok Mod Online Diag Status

    7 Pass

Don’t panic if the process takes a while, it surprised me how long it took in the lab especially as we had pretty much no configuration.