December 21, 2007
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Initial Public Release
M9200 - DS-X9032-SSM
DS-X9032-SSM modules require three partitions on the flash memory instead of two. Having two partitions on the flash memory does not directly affect runtime functionality. However, some debugging capability is lost and there can be a problem while upgrading to a software release later than SAN-0S 3.2.1, if the DS-X9032-SSM is running in L3 mode.
Newer SAN-OS releases (after 3.2(1)) assume the card has three partitions. During upgrade from a release after 3.2(1), the upgrade process will reformat the flash and create three partitions if there were only twopartitions previously. As a result, if the DS-X9032-SSM is running in L3 mode, the add-on image (SSI Image) will be erased and will need to be manually downloaded to the module flash.
The third partition is used to store useful debug information when running intelligent applications on a DS-X9032-SSM in L3 mode. If it is missing and a problem occurs, useful debugging information is lost.
Newer releases (after 3.2(1)) assume the card has three partitions. During upgrade from a release after 3.2(1), the upgrade process will reformat the flash and create three partitions if there were only two partitions previously. In this case, the DS-X9032-SSM add-on image (SSI Image) will be erased and will need to be manually downloaded to the module flash.
If customers want to continue in L2 mode then no action is necessary as the next upgrade from 3.2.x will automatically create three partitions and the upgrade will be non-disruptive since the DS-X9032-SSM module is running in L2 mode.
The creation of third partition is only required if the DS-X9032-SSM is running in L2 mode and the customer is planning to upgrade to L3 mode or they are already running in L3 mode. In this situation, customers will first need to check the partitions on the DS-X9032-SSM flash memory by using the procedure provided in the How to Identify Affected Units section to identify if their DS-X9032-SSM flash has two or three partitions. If they find only two partitions on their DS-X9032-SSM module flash memory, they can then use one of the scenarios that best fits their situation to create a third partition in their DS-X9032-SSM module.
Note: All scenarios are disruptive, since they require a reload of the DS-X9032-SSM module.
Scenario 1: Want to stay with current release, but fix the partitions
In releases 3.1(3) or later, a reload module x force-dnld will create three partitions.
i. If you are running in L2 mode, no action is required after reload module x force-dnld
ii. If you are running in L3 mode you have two choices to consider after a reload module x force-dnld .
(a) The first is if the boot variable points to the Modflash: on the DS-X9032-SSM module, it will come up in L2 mode after the reload. You would need to run Install ssi to load SSI image.
(b) The second option is to change the ssi boot variable to point to bootflash:. This will allow you to skip rerunning the install ssi image again.
In both cases, all SSM application configs will be preserved.
Scenario 2: About to upgrade from releases 3.2(1) or later to any other release:
i. If the DS-X9032-SSM module is in L2 mode, the upgrade process will create three partitions. No other action is required.
ii. If the DS-X9032-SSM module is in L3 mode, before running upgrade, either copy all the files to the bootflash or slot0:, or externally out of the system to a tftp server or ftp. The upgrade process will create three partitions and delete old modflash: files. The DS-X9032-SSM module comes up in L2 mode.
Run Install ssi to bring the DS-X9032-SSM module in L3 mode. All application configs are preserved. Copy saved files back into modflash:.
Scenario 3: Running SANOS lower than 3.1.3
If you are at a SAN-OS lower than 3.1(3) then you will need to upgrade to a release that is 3.1(3) or higher to create the three partitions. This should be done only after you determine which release is certified by your OSM and follow the correct scenario as mentioned in scenarios 1 and 2.
Customers can use the following procedure to identify if their DS-X9032-SSM flash has two or three partitions:
Step1: Attach to DS-X9032-SSM module by using the command attach module x
Step2: Run the command show system internal watchdog-timeout .
If you see either of the following errors below then the module has two partitions:
module-2# show system internal watchdog-timeout Unable to read /dev/hdc3, error 61
module-1# show system internal watchdog-timeout Unable to seek /dev/hdc3, error 22
If you see no output or some kernel stack trace, then the module already has three partitions on the Flash. No further action is required.
Example of DS-X9032-SSM flash with three partitions:
module-1# show system internal watchdog-timeout module-1#
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
MDS SSM show system internal watchdog-timeout command errors out.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.