|
|
Table Of Contents
Release Notes for Cisco Series Persistent Storage Device Module Software Release 2.0
Persistent Storage Device Orderable Software Image Matrix
Saving and Restoring Configurations
Standards Compliance Specifications
Obtaining Technical Assistance
Release Notes for Cisco Series Persistent Storage Device Module Software Release 2.0
Current Release: 2.0—July 2005
These release notes describe the guidelines and caveats for the Catalyst 6500 Series Persistent Storage Device Module (PSD), software release 2.0.
Note
For detailed installation and configuration procedures for the PSD, refer to the Catalyst 6500 Series Persistent Storage Device Module Installation and Configuration Note at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/ol_4685.html
This release supports the WS-SVC-PSD-1 module. For additional information about the WS-SVC-PSD-1 module, refer to the Catalyst 6500 Series Persistent Storage Device Module Installation and Configuration Note for software release 2.0.
Contents
This document consists of these sections:
•
•
•
•
•
•
Persistent Storage Device Orderable Software Image Matrix
Table 1 lists the PSD software versions and the applicable ordering information.
System Requirements
These sections describe the system requirements.
Supported Hardware
Table 2 lists the PSD hardware versions supported by the Cisco IOS software.
Table 2 PSD Hardware Compatibility
Supervisor Engine 2 with an MSFC2
Supervisor Engine 720 with an MSFC3
Supported Software
Table 3 lists the PSD software versions supported by the Cisco IOS software
Upgrading the PSD Software
You can upgrade both the application software and the maintenance software. To upgrade the application software, see the "Upgrading the PSD Application Software" section. To upgrade the maintenance software, see the "Upgrading the PSD Maintenance Software" section.
Caution
Note
Upgrading the PSD Maintenance Software
Note
To upgrade the PSD maintenance software, follow these steps:
Step 1
Step 2
Step 3
Router# hardware_module module 9 resetDevice BOOT variable for reset = hdd:1Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 9Router#00:31:11:%SNMP-5-MODULETRAP:Module 9 [Down] Trap00:31:11:SP:The PC in slot 9 is shutting down. Please wait ...00:31:25:SP:PC shutdown completed for module 900:31:25:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)00:31:28:SP:Resetting module 9 ...00:31:28:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on00:33:26:%SNMP-5-MODULETRAP:Module 9 [Up] Trap00:33:26:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed00:33:26:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonlineStep 4
Step 5
root@localhost# upgrade ftp-urlftp-url is the FTP location and name of the PSD software image file.
Note
Step 6
Step 7
Step 8
Router# hardware_module module 9 reset cf:1Device BOOT variable for reset = cf:1Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 9Router#00:16:06:%SNMP-5-MODULETRAP:Module 9 [Down] Trap00:16:06:SP:The PC in slot 9 is shutting down. Please wait ...00:16:21:SP:PC shutdown completed for module 900:16:21:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)00:16:24:SP:Resetting module 9 ...00:16:24:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on00:18:21:%SNMP-5-MODULETRAP:Module 9 [Up] Trap00:18:21:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed00:18:21:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonlineRouter#Step 9
root@localhost# show ipStep 10
a.
b.
c.
d.
e.
f.
g.
h.
Step 11
Router# hardware_module module 9 resetThis example shows how to upgrade the PSD maintenance software:
Router#Router# hardware_module module 9 resetDevice BOOT variable for reset = hdd:1Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 9Router#00:31:11:%SNMP-5-MODULETRAP:Module 9 [Down] Trap00:31:11:SP:The PC in slot 9 is shutting down. Please wait ...00:31:25:SP:PC shutdown completed for module 900:31:25:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)00:31:28:SP:Resetting module 9 ...00:31:28:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on00:33:26:%SNMP-5-MODULETRAP:Module 9 [Up] Trap00:33:26:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed00:33:26:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonlineRouter#Router# session slot 9 proc 1The default escape character is Ctrl-^, then x.You can also type 'exit' at the remote prompt to end the sessionTrying 127.0.0.91 ... OpenPersistent Storage Module (WS-SVC-PSD-1)login:rootPassword:Cisco Persistent Storage Module (WS-SVC-PSD-1) Console, 2.2(0.1)Copyright (c) 1999-2002 by cisco Systems, Inc.WARNING! Default password has not been changed!root@localhost.cisco.com#root@localhost.cisco.com# upgrade ftp://host/pub/rmon/mp.1-1-0-1.bin.gzuser password:Downloading image...ftp://host/pub/rmon/mp.1-1-0-1.bin.gz (11065K)- [########################] 11065K | 837.65K/s11331153 bytes transferred in 13.21 sec (837.64k/sec)Uncompressing the image...Verifying the image...Applying the Maintenance image.This may take several minutes...Upgrade of Maintenance image completed successfully.root@hostname.cisco.com# exitRouter# hardware_module module 9 reset cf:1Device BOOT variable for reset = cf:1Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 9Router#02:27:19:%SNMP-5-MODULETRAP:Module 9 [Down] Trap02:27:19:SP:The PC in slot 9 is shutting down. Please wait ...02:27:36:SP:PC shutdown completed for module 902:27:36:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)02:27:39:SP:Resetting module 9 ...02:27:39:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on02:29:37:%SNMP-5-MODULETRAP:Module 9 [Up] Trap02:29:37:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed02:29:37:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonlineRouter#
Upgrading the PSD Application Software
To upgrade the PSD application software, follow these steps:
Step 1
Step 2
Step 3
Router# hardware_module module 9 reset cf:1Device BOOT variable for reset = cf:1Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 9Router#00:03:31:%SNMP-5-MODULETRAP:Module 9 [Down] Trap00:03:31:SP:The PC in slot 9 is shutting down. Please wait ...00:03:41:%SNMP-5-COLDSTART:SNMP agent on host R1 is undergoing a coldstart00:03:46:SP:PC shutdown completed for module 900:03:46:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)00:03:49:SP:Resetting module 9 ...00:03:49:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on00:05:53:%SNMP-5-MODULETRAP:Module 9 [Up] Trap00:05:53:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed00:05:53:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonlineRouter#Step 4
Router# session slot 9 proc 1The default escape character is Ctrl-^, then x.You can also type 'exit' at the remote prompt to end the sessionTrying 127.0.0.91 ... OpenPersistent Storage Module (WS-SVC-PSD-1)Maintenance Partitionlogin:rootPassword:Persistent Storage Module (WS-SVC-PSD-1) Console, 1.4(1)mCopyright (c) 1999, 2000, 2001 by cisco Systems, Inc.Step 5
root@localhost# upgrade ftp-urlftp-url is the FTP location and name of the PSD software image file.
Note
Step 6
Step 7
Step 8
Router# hardware_module mod 8 resetDevice BOOT variable for reset =Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 8Router#00:26:55:%SNMP-5-MODULETRAP:Module 8 [Down] Trap00:26:55:SP:The PC in slot 8 is shutting down. Please wait ...Step 9
root@localhost# show iproot@localhost# show snmpThis example shows how to upgrade the PSD application software:
Router# hardware_module module 9 reset cf:1Device BOOT variable for reset = cf:1Warning:Device list is not verified.Proceed with reload of module? [confirm]% reset issued for module 9Router#00:16:06:%SNMP-5-MODULETRAP:Module 9 [Down] Trap00:16:06:SP:The PC in slot 9 is shutting down. Please wait ...00:16:21:SP:PC shutdown completed for module 900:16:21:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)00:16:24:SP:Resetting module 9 ...00:16:24:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on00:18:21:%SNMP-5-MODULETRAP:Module 9 [Up] Trap00:18:21:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed00:18:21:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonlineRouter# session slot 9 proc 1The default escape character is Ctrl-^, then x.You can also type 'exit' at the remote prompt to end the sessionTrying 127.0.0.91 ... OpenPersistent Storage Module (WS-SVC-PSD-1)Maintenance imagelogin:rootPassword:Maintenance image version:1.4(1)mroot@localhost.cisco.com# upgrade ftp://psdlab-pc1/pub/rmon/c6psd2.2-2-0-8.bin.gzDownloading the image. This may take several minutes...ftp://psdlab-pc1/pub/rmon/c6psd2.2-2-0-8.bin.gz (59198K)/tmp/upgrade.gz [########################] 59198K | 821.24K/s60619473 bytes transferred in 72.08 sec (821.23k/sec)Upgrade file ftp://psdlab-pc1/pub/rmon/c6psd2.2-2-0-8.bin.gz is downloaded.Upgrading will wipe out the contents on the hard disk.Do you want to proceed installing it [y|N]:yProceeding with upgrade. Please do not interrupt.If the upgrade is interrupted or fails, boot intoMaintenance image again and restart upgrade.Creating PSD application image file...Initializing the application image partition...Applying the image, this may take several minutes...Performing post install, please wait...Upgrade complete. You can boot from the Application image.root@hostname.cisco.com# exit[Connection to 127.0.0.91 closed by foreign host]Router#Router# hardware_module module 9 resetDevice BOOT variable for reset =Warning:Device list is not verified.Proceed with reload of module? [confirm] y% reset issued for module 9Router#00:24:04:%SNMP-5-MODULETRAP:Module 9 [Down] Trap00:24:04:SP:The PC in slot 9 is shutting down. Please wait ...00:24:18:SP:PC shutdown completed for module 900:24:18:%C6KPWR-SP-4-DISABLED:power to module in slot 9 set off (adminrequest)00:24:21:SP:Resetting module 9 ...00:24:21:%C6KPWR-SP-4-ENABLED:power to module in slot 9 set on00:26:19:%SNMP-5-MODULETRAP:Module 9 [Up] Trap00:26:19:%DIAG-SP-6-BYPASS:Module 9:Online Diagnostics is Bypassed00:26:19:%OIR-SP-6-INSCARD:Card inserted in slot 9, interfaces are nowonline
Saving and Restoring Configurations
For general information about saving and restoring configurations, refer to the Catalyst 6000 Family IOS Software Configuration Guide or to the Cisco 7600 Series Internet Router IOS Software Configuration Guide.
Prior to Software Release 2.0, the PSD did not provide a dynamic method to save and restore your configuration. Additionally, if you needed to change PSD modules in the Catalyst chassis, you had to configure the new module.
If you have not upgraded to Cisco PSD Software Release 2.0, perform the following procedure to save and store your PSD configuration details:
Step 1
router# session slot slot_num processor numberStep 2
root@localhost.localdomain# show iproot@localhost.localdomain# show snmp-agentroot@localhost.localdomain# show datastore allStep 3
Refer to "New Configuration Details" section for information on how to save and restore configurations in Cisco PSD Software Release 2.0.
Limitations and Restrictions
This section describes the limitations and restrictions for the Cisco PSD software release2.0:
•
New Features
The following features are new in Cisco PSD Software Release 2.0:
•
•
•
•
•
•
New Configuration Details
Saving Your Configuration
Note
Step 1
router# session slot slot_num processor processorIssue the root@localhost.localdomain# show ip command and archive the IP address information for future reference.
Step 2
Step 3
Note
If you choose not to put an FTP server on your network, you can use the following instructions to save and restore your configuration.
Step 1
router# session slot slot_num processor processor
Step 2
root@localhost.localdomain# show iproot@localhost.localdomain# show snmp-agentroot@localhost.localdomain# show datastore allStep 3
Restoring Your Configuration
Note
If you need to restore a previous configuration, use the following instructions:
Step 1
router# session slot slot_num processor processor
Step 2
Step 3
Note
Note
Transfering and Purging Data Files and Datastores
Cisco PSD Software Release 2.0 allows you transfer and purge whole datastores, as well as individual files that exist in a datastore.
To transfer and purge datastores and datastore files, perform the following procedure:
Step 1
datastore transfer {keep | delete} {data-files | salvage-files | all} data-store-name ftp-urlThe specified URL has the following format: ftp://username:password@hostname/fully-qualified-destination-directory
Step 2
datastore purge transferred {data-files | salvage-files | all} data-store-name
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.
Caveats for Cisco IOS Releases 12.3 can be found on CCO at http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123relnt/xprn123t/123tcavs.htm
The " Open Caveats" section lists open caveats that apply to the current release and might also apply to previous releases.
The " Resolved Caveats" section lists caveats resolved in a particular release, which may have been open in previous releases.
Note
Open Caveats
The following caveats are unresolved in Cisco PSD Software Release 2.0:
•
The memory failure can manifest itself in the inability to delete a datastore, or an inability to receive records, etc.
Each session command uses a small amount of memory, and over the course of several weeks and tens of thousands of sessions, this consumes all of the available memory on the PSD.
Workaround: avoid scenarios which involve repeated session commands from IOS to the PSD. For example, enable telnet access directly to the PSD as direct telnet does not result in memory failure. Also, in automated script situations, session into the PSD once and periodically collect data rather than estanblishing and exiting a session every period for an individual data collection.
•
The PSD will not allow commands such as show datastore to complete.
For example: At the PSD, the show ip command displays a default gateway of 0.0.0.0, and show log will display the following error message:
ERROR [main :APPL.CDRBackup ] Runtime exception in main:com.objectspace.jgl.OrderedSet.add(OrderedSet.java)This problem is caused by not having a default gateway configured, configuring a datastore accessor that requires a default gateway.
Workaround: enter the ip gateway ip command with a gateway other than 0.0.0.0
The PSD application should restart shortly, and you should be able to perform normal PSD activities. If this does not occur, reset the PSD. After the reset, if a show ip displays the default gateway as 0.0.0.0 again, then you are suffering from CSCsd47477 and require tac intervention.
•
The PSD will not allow commands such as show datastore to complete. Resetting the PSD or performing an upgrade with the --install option does not fix the problem.
For example:
At the PSD, the show ip command will show a default gateway of 0.0.0.0 and show log will display this error:
ERROR [main :APPL.CDRBackup ] Runtime exception in main:com.objectspace.jgl.OrderedSet.add(OrderedSet.java)This problem is caused by not having a default gateway configured, configuring a datastore accessor that requires a default gateway, and then resetting and upgrading the PSD.
Workaround: Call TAC; they can fix the problem if they can connect to the switch remotely.
Unresolved Caveats Prior to Cisco PSD Software Release 2.0
The following caveats are unresolved in Cisco PSD Software Release 1.1(4):
•
This is a duplicate of CSCeh90943.
The first SSO switchover does not disrupt communication between the CSG and the PSD, but communication between the CSG and PSD is lost after subsequent SSO switchovers until an echo request/response a minute after the communication loss is detected:
00:11:14: %CSM_SLB-4-WARNING: Module 1 warning: Communication with CSG recordstorage 172.18.50.145:3386 failed00:12:14: %CSM_SLB-6-INFO: Module 1 info: Communication with CSG record storage172.18.50.145:3386 established00:12:16: %CSM_SLB-6-INFO: Module 1 info: CSG record storage 172.18.50.145:3386is active.Workaround: communication is always re-established, but at > 1 minute, this is not a successful SSO switchover.
•
The memory failure can manifest itself in the inability to delete a datastore, or an inability to receive records, etc.
Each session command uses a small amount of memory, and over the course of several weeks and tens of thousands of sessions, this consumes all of the available memory on the PSD.
Workaround: avoid scenarios which involve repeated session commands from IOS to the PSD. For example, enable telnet access directly to the PSD as direct telnet does not result in memory failure. Also, in automated script situations, session into the PSD once and periodically collect data rather than estanblishing and exiting a session every period for an individual data collection.
Open Caveats Prior to Cisco PSD Software Release 1.1(4)
The following caveats are unresolved in Cisco PSD Software Release 1.1(2):
•
Using the log supervisor enable command can cause an infinite message loop; you should not use this command. The loop will occur when log supervisor enable is configured and a critical level error message is generated by the PSD. The following example message will recur:
"scp: SCP PC Blade RESP from 0x10/1"
Workaround: Do not enable supervisor logging on the PSD; it is not enabled by default. If you have enabled this function, issue the log supervisor disable command to disable it. If you encounter this problem, disable supervisor logging and recycle the PSD.
Open Caveats Prior to Cisco PSD Software Release 1.1(2)
The following caveats are unresolved prior to Cisco PSD Software Release 1.1(2):
•
When the show datastore name statistics command is issued, the value for the record count may be inaccurate. This might occur when (under certain conditions) a file becomes corrupt. If this occurs, the number of unread records in the corrupt file are not subtracted from the displayed record count, and the value is inaccurate.
Workaround: You can issue a hw-module module psd-module-number reset from the Supervisor to reboot the PSD and force the value to be recalculated. Cisco recommends that you first verify that the PSD is not in use, because issuing this command will cause an interruption in the services the PSD provides while the PSD is rebooting.
•
The PSD ip hosts ftp-url command may time out and not complete.
Workaround: Add individual IP host entries using the ip hosts add command. You must issue this command once for each host.You can also define a nameserver "ip nameserver" or multiple nameservers, and not depend on the ip hosts definitions for name resolution.
•
When upgrading an MP image from the AP, or an AP image from the MP, you must specify a remote image name. If the remote image is on a Windows FTP server, the upgrade may fail due to "CWD" not allowed on the remote host.
Workaround: Place the remote image on a Unix, Linux, Solaris or other non-Windows FTP server. Then, specify that new location on the upgrade command.
Resolved Caveats
The following caveats are resolved in Cisco PSD Software Release 2.0:
•
Using the log supervisor enable command can cause an infinite message loop; you should not use this command. The loop will occur when log supervisor enable is configured and a critical level error message is generated by the PSD. The following example message will recur:
"scp: SCP PC Blade RESP from 0x10/1"
Workaround: Do not enable supervisor logging on the PSD; it is not enabled by default. If you have enabled this function, issue the log supervisor disable command to disable it. If you encounter this problem, disable supervisor logging and recycle the PSD.
•
This is a duplicate of CSCeh90943.
The first SSO switchover does not disrupt communication between the CSG and the PSD, but communication between the CSG and PSD is lost after subsequent SSO switchovers until an echo request/response a minute after the communication loss is detected:
00:11:14: %CSM_SLB-4-WARNING: Module 1 warning: Communication with CSG recordstorage 172.18.50.145:3386 failed00:12:14: %CSM_SLB-6-INFO: Module 1 info: Communication with CSG record storage172.18.50.145:3386 established00:12:16: %CSM_SLB-6-INFO: Module 1 info: CSG record storage 172.18.50.145:3386is active.Workaround: communication is always re-established, but at > 1 minute, this is not a successful SSO switchover.
Resolved Caveats Prior to Cisco PSD Software Release 2.0
The following caveats are resolved in Cisco PSD Software Release 1.1(4):
•
The datastore create command failed. Error messages in the PSD log show JVM OutOfMemory messages.
After around 60 iterations of datastore create and datastore destroy, a datastore create failed. The logs indicate an OutOfMemory condition.
We determined a file handle to a memory mapped file was not closed, which caused an eventual out of memory condition.
Workaround: avoid excessive datastore create/destroy iterations. If the error condition is encountered, the PSD should be rebooted to clear the issue.
Resolved Caveats Prior to Cisco PSD Software Release 1.1(4)
The following caveats are resolved in Cisco PSD Software Release 1.1(3):
•
CSCed32141 documents a PSD enhancement that performs hard disk spin down during periods of inactivity. This enhancement causes less physical use of the hard disk, and leads to greater reliability and life span of the device. The enhancement has no configuration or monitoring capabilities.
We suggests you upgrade the PSD software to release 1.1(3) to include this enhancement.
•
Using the log supervisor enable command can cause an infinite message loop; you should not use this command. The loop will occur when log supervisor enable is configured and a critical level error message is generated by the PSD. The following example message will recur:
"scp: SCP PC Blade RESP from 0x10/1"
Workaround: Do not enable supervisor logging on the PSD; it is not enabled by default. If you have enabled this function, issue the log supervisor disable command to disable it. If you encounter this problem, disable supervisor logging and recycle the PSD.
•
After an RPR+ switchover occurs, the PSD shutdown and reboot commands do not work when entered on the PSD console.
Workaround: You can shutdown the PSD in configuration mode on the supervisor console by entering the no power enable module psd-module# command.
Additionally, you can reboot the PSD from the supervisor console by issuing the hw-module module psd-module# reset command.
Resolved Caveats Prior to Cisco PSD Software Release 1.1(3)
The following caveats are resolved in Cisco PSD Software Release 1.1(2):
•
The PSD is unable to read or write data from data stores. When the PSD is rebooted, and the CSG attempts to write to a data store with partially read data files, the CDR Backup application stops processing requests to read or write to any of the data stores.
Workaround: Either upgrade to Release 1.1(2), or perform the following task:
–
–
–
–
–
–
•
Under certain conditions, the CSG is informed that the PSD's disk is full, but the CSG is not informed when the PSD again has available disk space. As a result, the CSG will not write billing information to the PSD until a billing agent is again available. This creates the possibility that you might lose billing information if the CSG's buffers overrun or the CSG reloads.
This problem occurs if all the billing agents a CSG communicates with are down, and the following sequence of events occur:
–
–
–
If the above sequence of events occur, the PSD does not have a way to communicate to the CSG that there is disk space available for the CSG to resume sending write requests. Normally this information is communicated using a read response, but the billing agents are not available, and the CSG is not sending read requests. Therefore, the PSD cannot communicate that disk space is again available.
Workaround: Restore one of the configured billing agents. This will cause the CSG to send a read request to the PSD, and cause the PSD to send a read response indicating that there is disk space available.
This workaround requires that you are running CSG Release 3.1(3)C4(9) or later.
•
The PSD stops processing GTP' requests from a CSG. This problem occurs when an Echo or Node Alive request triggers the PSD to detect that it has transitioned from a full to a non-full disk state. A subsequent write request causes the PSD to no longer process GTP' requests from a CSG.
Workaround: to recover, the PSD must be reset from the supervisor, or upgraded to release 1.1(2).
Resolved Caveats Prior to Cisco PSD Software Release 1.1(2)
The following caveats are resolved in Cisco PSD Software Release 1.0(2)
•
Once the PSD disk is filled, all data stores are in a "full" state and are no longer able to process write requests. One or more data stores are in a "full" state if the following message is written to the Supervisor console:
error: GTP received a reject cause code, 199
This cause code is sent to a CSG when there are insufficient resources to write data to the PSD. A data store will only transition to a "non-full" state when one of the following events occurs:
–
–
If the PSD disk does not appear to be full and a data store is not processing write requests, the data store may be in a full state.
This condition occurs only if you are running CSG Release 3.1(3)C4(8).
Workaround: Use the following two options to cause the data store to transition out of a "full" state and back to a "non-full" state:
–
–
Related Documentation
This section lists documentation for the Catalyst 6500 series PSD:
•
•
–
–
–
–
•
•
•
–
–
Standards Compliance Specifications
Refer to Appendix A, "Specifications," in the Catalyst 6000 Family Installation Guide and the Catalyst 6000 Regulatory Compliance and Safety Information publication for the standards compliance specifications.
FCC Class B Compliance
This equipment has complies with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules.
The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco's installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. There is no guarantee that interference will not occur in a particular installation.
Modifying the equipment without Cisco's written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.
Note
Refer to the Catalyst 6000 Family Installation Guide and the Catalyst 6000 Regulatory Compliance and Safety Information publication for additional FCC class compliance information.
Copyright Notices
Third-party software used under license accompanies the Cisco Persistent Storage Module Software. One or more of the following notices may apply in connection with the license and use of such third-party software.
GNU General Public License
The Persistent Storage Device contains software covered under the GNU Public License. If you would like to obtain the source for the modified GPL code in the Persistent Storage Device, please send a request to psd-sw-req@Cisco.com.
GNU General Public License
License Text
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software—to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program," below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you."
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version," you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS.
Berkeley Software Distribution License
Various Modules Copyright (C) 1983-2000, The Regents of the University of California. All rights reserved.
BSD License
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the University of California, nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Apache License
Apache
====================================================================
The Apache Software License, Version 1.1
Copyright (c) 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4.
5.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.
Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
Posted: Mon Oct 22 09:27:16 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
