Table Of Contents
Cisco MDS 9000 Family Release Notes
for Cisco MDS SAN-OS Release 1.3(3)
Release Date: January 16, 2004
Text Part Number: OL-4959-03 Rev. P0
This document describes the caveats and limitations for switches in the Cisco MDS 9000 Family. Use this document in conjunction with documents listed in the "Related Documentation" section.
Note Releases notes are sometimes updated with new information on restrictions and caveats. Refer to the following website for the most recent version of the Cisco MDS 9000 Family Release Note: http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_release_notes_list.html
Table 1 shows the on-line change history for this document.
Table 1 On-Line Change History
Revision Date Description
Added DDTS CSCed44067.
Added a limitation about Upgrading to Release 1.3(3).
Added DDTS CSCed64425.
Added DDTS CSCee01143.
Added DDTS CSCin81760
Added DDTS CSCeg61535
Added DDTS CSCeg56197.
Modified DDTS CSCee06496
Added workaround information for all resolved caveats.
Added DDTS CSCei25319
Removed DDTS CSCed16845.
Added DDTS CSCsh27840.
This document includes the following section:
The Cisco MDS 9000 Family of multilayer directors and fabric switches offer intelligent fabric-switching services that realize maximum performance while ensuring high reliability levels. They combine robust and flexible hardware architecture with multiple layers of network and storage management intelligence. This powerful combination enables highly available, scalable storage networks that provide advanced security and unified management features.
The Cisco MDS 9000 Family provides intelligent networking features such as multiprotocol and multitransport integration, virtual SANs (VSANs), advanced security, sophisticated debug analysis tools, and unified SAN management.
This section describes the system requirements for Cisco MDS SAN-OS Release 1.3(3) and includes the following topics:
Table 2 Cisco MDS 9000 Family Supported Hardware Modules and Minimum Software Requirements
Component Part Number Description Applicable Products
MDS 9500 Series supervisor/fabric-I, enterprise software
MDS 9500 Series only
MDS 9216 enterprise software
MDS 9216 only
MDS 9100 Series enterprise software
MDS 9100 Series only
MDS 9509 director, base configuration (9-slot modular chassis includes 7 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately)
MDS 9509 only
MDS 9506 director (6-slot modular chassis includes 4 slots for switching modules and 2 slots for supervisor modules—SFPs sold separately.
MDS 9506 only
MDS 9216 16-port semi-modular fabric switch (includes sixteen 1 / 2-Gbps Fibre Channel ports, power supply, and expansion slot—SFPs sold separately)
MDS 9216 only
MDS 9120 fixed configuration, non-modular, fabric switch (includes 4 full rate ports and 16 host-optimized ports)
MDS 9120 only
MDS 9140 fixed configuration (non-modular) fabric switch (includes 8 full rate ports and 32 host-optimized ports)
MDS 9140 only
MDS 9500 supervisor/fabric-I, module
MDS 9500 Series only
MDS 9000 16-port 2/1-Gbps Fibre Channel module (SFPs sold separately)
MDS 9500 Series and 9216
MDS 9000 32-port 2/1-Gbps Fibre Channel module (SFPs sold separately)
8-port Gigabit Ethernet IP storage services module.
32-port Fibre Channel Advanced Services Module (ASM).
Caching Services Module (CSM)
LC-type fiber-optic SFP1
2/1-Gbps Fibre Channel — short wave SFP
MDS 9000 Family
2/1-Gbps Fibre Channel — long wave SFP
1-Gbps Ethernet and 2/1-Gbps Fibre Channel—short wave SFP
1-Gbps Ethernet and 2/1-Gbps Fibre Channel — long wave SFP
Gigabit Ethernet and 2/1-Gbps Fibre Channel SFP LC interface xxxx nm, where xxxx = 1470, 1490, 1510, 1530, 1550, 1570, 1590, or 1610 nm
MDS 9000 Family
Add/drop multiplexer for four CWDM wavelengths
Add/drop multiplexer for eight CWDM wavelengths
Two slot chassis for CWDM add/drop multiplexer(s)
300W AC power supply
MDS 9100 Series only
845W3 AC power supply
MDS 9216 only
2500W AC power supply
MDS 9509 only
2500W DC power supply
4000W AC power supply for US (cable attached)
4000W AC power supply international (cable attached)
1900W AC power supply
MDS 9506 only
1900W DC power supply
MDS 9500 supervisor CompactFlash disk, 512MB
MDS 9500 Series only
Port analyzer adapter
A standalone Fibre Channel-to-Ethernet adapter that allows for simple, transparent analysis of Fibre Channel traffic in a switched fabric.
MDS 9000 Family
1 SFP = small form factor pluggable
2 CWDM = coarse wave division multiplexing
3 W = Watt
Determining the Software Version
Note We strongly recommend that you use the latest available software release for all Cisco MDS 9000 Family products.
To determine the version of the Cisco SAN-OS software currently running on a Cisco MDS 9000 Family switch, log in to the switch and enter the show version EXEC command.
The Cisco MDS SAN-OS software is designed for mission-critical high availability environments. To realize the benefits of nondisruptive upgrades on the Cisco MDS 9500 Directors, we highly recommend that you install dual supervisor modules.
You can nondisruptively upgrade to (or downgrade from) Release 1.3(3) using any Cisco MDS SAN-OS software release other than Release 1.0(2a).
New Features in Release 1.3(3)
SAN-OS Release 1.3(3) is a maintenance release for switches in the Cisco MDS 9000 Family. See the "Caveats" section for details on closed and outstanding caveats and limitations.
Note The Release Notes are specific to this maintenance release. For the rest of the 1.3 documentation, refer to the Release 1.3 document set (see the "Related Documentation" section).
Caution Releases 1.3(2a) and 1.3(3) have been deferred. Please use SAN-OS Release 1.3(3c) or later.
The following new features are introduced in Release 1.3(3):
iSCSI SACK Default
Effective Release 1.3(3), the TCP SACK parameter is enabled by default for iSCSI configurations.
Refer to Cisco MDS 9000 Family Configuration Guide for further information.
Essential Upgrade Prerequisites
Before performing any software upgrade, contact your respective customer service representative to review your software upgrade requirements and to provide recommendations based on your current operating environment.
Note If you purchased Cisco support through a Cisco reseller, contact the reseller directly. If you purchased support directly from Cisco, contact Cisco Technical Support at this URL: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtm
Limitations and Restrictions
The following limitations and restrictions apply to all switches in the Cisco MDS 9000 Family:
Upgrading to Release 1.3(3)
When upgrading to SAN-OS Release 1.3(3) from any earlier SAN-OS release, the upgrade may fail based on the type of Call Home options configured. Refer to CSCed44067 for further information.
Remove all email address configurations for all destination profiles before performing the upgrade. Apply the Call Home configuration after the upgrade. Use the following command to remove the email address configurations.switch(config-callhome)# no destination-profile profile-name email-addr email-address
CompactFlash Device Usage
The SAN-OS software only supports Cisco-certified CompactFlash devices that are formatted using Cisco MDS switches. Using uncertified CompactFlash devices may result in unpredictable consequences; formatting CompactFlash devices using other platforms may result in errors.
Refer to Table 2 for a lists of Cisco-certified CompactFlash devices.
Aborting the install all Command
Avoid aborting the switch progress after issuing the install all command. If the install all command is aborted, be sure to verify the state of the switch at every stage and reissue the command after 10 seconds. If you reissue the install all command within the 10-second span, the command is rejected with an error message indicating that an installation is currently in progress.
Refer to Cisco MDS 9000 Family Configuration Guide for further information.
This section lists the caveats and corrected caveats for this release. Use Table 3 to determine the status of a particular caveat. In the table, "R" indicates a resolved caveat, and "O" indicates an open caveat.
Symptom: Upon receiving a Type Length Value (TLV) parameter type that is outside of the valid range (0x1 - 0x18), the Cisco Discovery Protocol (CDP) daemon may cause the MDS switch to reload.
Workaround: If you observe this problem in Release 1.3(2a) and earlier, disable CDP.
Symptom: Non-MDS switches do not handle IVR frames graciously, resulting in resources (for example, exchange/memory) not being freed.
Symptom: When an IVR zoneset is displayed using the CLI, duplicate members are displayed in the zones. This does not occur if displayed using the GUI.
Workaround: Use the GUI to display an IVR zone set.
Symptom: Moving a host from one switch to another does not get reflected in the Fabric Manager map.
Sympton: An error message in the log file occurs because the platform manager component passes the wrong parameter while responding to a SNMP query. In some cases, this results in the query not being responded to.
Workaround: Perform a refresh on Device Manager to clear the problem.
Symptom: While using an FCIP link for remote SPAN, it is possible that the FCIP link may flap.
Workaround: Do not use FCIP links for Remote SPAN.
Symptom: When the Fabric Manager or Device Manager communicates with the Cisco MDS switch through Virtual Private Network (VPN) or any Network Address Translation (NAT) scheme, a generic error message occurs while adding duplicate zone members from a VPN connection.
Workaround: None. If an error occurs while running through VPN/NAT, all errors will show up as generic errors without a detailed message describing the error.
Symptom: When IVR is enabled, the Fabric-Device Management Interface information is not transferred across VSANs for IVR devices.
Symptom: When the FCIP write acceleration feature is enabled, IPFC frames and related Fibre Channel exchanges may not be handled correctly—the IPFC traffic generated using a ping function did not follow the specified exchange management assumptions and norms.
Workaround: None. Upgrade to Cisco MDS SAN-OS Release 1.3(3).
Symptom: If the switchname of the MDS switch is only assigned numeric characters, the licensing functionality may encounter problems.
Workaround: Modify the switchname to also contain one or more alpha characters.
Symptom: An IBM iSERIES server with a Fibre Channel disk HBA (Model 2766) requires the F-port mode to be configured in the MDS switch in order to bring up the attached MDS switch port.
Workaround: For IBM iSERIES sever with Fibre Channel disk HBA (Model 2766), set the MDS switch port mode to F-port instead of using the default auto-mode.
Symptom: IP address-based access control for an iSCSI virtual target was not enforced as designed.
Symptom: When altering an Fx-port state using SNMP, the following error is reported:snmpset: Agent reported error with variable #1..iso.org.dod.internet.mgmt.mib-22.214.171.124.126.96.36.199.0: SNMP: A generalfailure occurred on the agent.
Symptom: When adding zone aliases 2048 to a zone, an Snmp Wrong length error is displayed.
Symptom: The add zoneset command removes zones with the same name from existing zone sets. Even after adding a new zone, other zone sets don't have the new zone as part of their zone sets. This is only caused by third party applications.
Workaround: Use the G3 AZD command with third party applications to add zone sets.
Symptom: When upgrading to SAN-OS Release 1.3(3) from any earlier SAN-OS release, the upgrade may fail based on the type of Call Home options configured.
Workaround: Remove all email address configurations for all destination profiles before performing the upgrade. Apply the Call Home configuration after the upgrade. Use the following command to remove the email address configurations.switch(config-callhome)# no destination-profile profile-name email-addr email-address
Symptom: The name server loses route entries (well-known address routes) when a new module is inserted or if an existing module is reset in a Cisco MDS 9000Family switch that has been nondisruptively upgraded to SAN-OS 1.3(2a) or 1.3(3) from a SAN OS release 1.0(x), or 1.1(x), or 1.2(x). This results in the host is unable to communicate with that module.
a. This bug is fixed in Release 1.3(3c) and all subsequent releases.
b. If you received the Cisco MDS Switch with a factory-installed SAN-OS Release1.3(x), you will not be affected by this bug.
c. If you are currently running SAN-OS Releases 1.0(x), 1.1(x), or 1.2(x) and planning to upgrade to Releases 1.3(2a) or 1.3(3), be sure to schedule a switch reload after the SAN-OS upgrade.
Symptom: A license installation failure occurs on the Cisco MDS 9216A switch running Cisco SAN-OS software releases 1.3(2a), 1.3(4a) and 1.3(5).
Workaround: Upgrade to Cisco SAN-OS software releases 1.3(6), 2.0(1b) or later for successful license installation. If desired, the Cisco MDS 9216A switch can then be downgraded to releases 1.3(2a), 1.3(4a), or 1.3(5).
Symptom: When configuring the nWWN for an iSCSI initiator using the Device Manager, you may encounter a NullPointerException error.
Symptom: When a McData switch with firmware 4.01.xx/5.01.xx/5.02.xx in open-fabric mode is attached to a Cisco MDS switch and the hosts attached to the MDS register a symbolic port or node name with the FCNS, the name server on the McData switch may send abort sequences to devices that are locally attached to the McData switch. According to the FC-SW2 spec, (Section 9.3.3 Name Server Objects), Port Symbolic Name and Node Symbolic Name are not mandatory fields in the small name server object. The result is that an end device that successfully registers a symbolic Port/Node name with an MDS switch may cause the McData switch name server to malfunction and send abort sequences to end devices that log into the McData name server.
Workaround: Plug all devices that register symbolic node/port world wide names into the McData. This issue exists as of Cisco MDS firmware up to and including 1.3(3c).
Symptom: In some rare instances in Cisco MDS SAN-OS Release 1.3, 2.0, and 2.1(1), when the IP Storage Services (IPS) module restarted after a failure, VSAN membership information about iSCSI interfaces was lost. However, a configuration saved with the copy running-config startup command was not lost.
Symptom: A vulnerability in the Transmission Control Protocol (TCP) specification (RFC 793) was discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the attacked protocol, a successful attack may have additional consequences beyond terminated connection. This attack vector is only applicable to those sessions terminating in a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality. All Cisco products which contain TCP stack are susceptible to this vulnerability.
This advisory is available at the following website, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software. http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml.
Workaround: Depending on the application, the connection may get automatically reestablished. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session).
Symptom: If a spare supervisor module has the local boot variables pointing to Release 1.0(1) or 1.0(2) images, inserting that spare supervisor module into a functioning switch will cause the active supervisor module to fail. This issue exists in all releases up to and including Release 1.3(3c).
Workaround: If the active supervisor runs any of the affected releases, check the version of the spare supervisor module before inserting it, or issue the reload module slot-number force-dnld command immediately after the insertion. The slot-number is the number of the slot in which the spare module is inserted.
Symptom: A malformed ELS frame destined to the RSCN process results in the packet not being discarded. This prevents RSCN process from receiving any further frames.
Symptom: You may not be able to login to Fabric Manager or Device Manager using SNMPv3. You may get the following error message:SNMP NotInTimeWindow
Workaround: Set the clock on the switch to a different value and then set it to your correct time. For Example.MDS# clock set 04:23:01 26 March 2000MDS# clock set 04:23:01 11 November 2004
After setting the clock, launch FM and verify the connection.
Symptom: If you are running Cisco MDS SAN-OS releases 1.1(3), 1.2(1a), 1.2(1b), 1.2(2a), 1.3(1), 1.3(2a), 1.3(3), or 1.3(3c), the following sequence of operations might lead to the failure of one or both supervisor modules simultaneously:
a. Removing an IPS-8 module from the switch.
b. Inserting a different type of module in the same slot.
c. Configuring the new module.
d. Issuing the copy running-config startup-config command.
Removing the IPS-8 module at any time and replacing with another IPS-8 module does not cause this problem.
Workaround: Before replacing an IPS-8 module with a different type of module in the same slot, upgrade to Cisco MDS SAN-OS Release 1.3(4a).
Symptom: After doing a VSAN delete operation, if a switchover or code upgrade is performed then FSPF will loose all the routes on all the higher numbered (than the VSAN that has been deleted) VSANs. As an example, if you have VSANs 1, 2 and 3 and now you delete VSAN 2, then you will see the FSPF routes missing in VSAN 3, after switchover/upgrade.
Workaround: Deleting and readding the affected VSANs or disabling and enabling FSPF on the VSANs will bring back the routes.
Symptom: If a malfunctioning device does not swap the source and destination FCIDs, a PLOGI frame sent by this device can cause high CPU utilization. These PLOGI frame errors are reported by the zone server.
Symptom: The system does not recognize a CLI password containing the "$" character.
Workaround: Change your password to a different string that does not include the "$" character. For an admin user-account, you might have to perform the password-recovery procedure to reset the password.
Symptom: When an iSCSI initiator logs in to a Gigabit Ethernet port number 1 on an IPS module in slot 1, the switch sends a login response with the value of the Target Session Identifying Handle (TSIH) field set to zero (0), which is an iSCSI protocol violation. This situation can also occur when an iSCSI initiator logs in to Ethernet PortChannel number 1. The Qlogic iSCSI initiator may verify the TSIH value and reject it.
Symptom: The Device Manager shows a port in the down state (red square) when the operational status of the port is up. This rare occurrence is due to the failure cause of the port not being empty (for example, the failure case reflects the initializing state).
Symptom: When a switch is upgraded while the Device Manager for that switch is open, a Java error of class cast exception occurs. When this error occurs, some Device Manager menu items are unusable while other menu items remain in this error state.
Workaround: Close the Device Manager and reopen it.
Symptom: When a previously-connected port is disconnected and reconnected to a different port, the old port connection displays a red cross. The tool tip continues to shows the presence of the new port and the old port as members of the loop. When this happen the WWN of the new device is both in the tool tip of the nonexistent loop and in the disconnected device. It may take a poll cycle for the PortChannel to appear on the fabric map.
Workaround: Refresh or purge the fabric map to remove the nonexistent (dead) link.
Symptom: If a switch does not have sufficient PortChannels available for an SVC Interface, it will remain in a failure state. This situation can occur if you allocate all 128 PortChannels available in the system. You can verify this failure if you see the node down status in the output of the show interface svc slot/node command. To confirm that this failure is a result of insufficient PortChannels, issue the show port-channel usage command.
Workaround: Identify at least three PortChannels that can be released so they appear in the unused section of the show port-channel usage command output. Use the no interface port-channel number command to delete unneeded PortChannels. Finally, reset the SVC Interface.
Symptom: During a switch upgrade, a SVC node may not save its entire state under rare circumstances. This results in that node not being part of the cluster after the switch upgrade. Verify this symptom by issuing the show nodes local command at the svc-config prompt—the command output displays the following information:
–The cluster state of the affected SVC node will be unconfigured.
–The node state of the affected SVC node will be free.
Workaround: Manually remove the SVC node from the cluster and then add the node back into the cluster. Refer to Cisco MDS 9000 Family SAN Volume Controller Configuration Guide for procedural details.
Symptom: On rare occasions, the install license command may fail due to the saved state of the switch configuration. This may occur after saving a remote configuration to the switch using the copy remote-url start-up command.
Workaround: Issue the copy ru st command. The install license command should work properly after that.
Symptom: Due to an internal error, the fcFxPortID returns a wrong FCID value from the FIBRE-CHANNEL-FE-MIB.
Symptom: The Fabric Manager map layout is not preserved when the FC domain is restarted.
Symptom: Using a script to send Common Information Model (CIM) queries via the CIM Pegasus CLI client may result in a memory leak.
Workaround: None. The CIM server automatically reinitializes on detecting a memory leak.
Symptom: Configuring the iSCSI TCP minimum bandwidth sets the maximum bandwidth; configuring the maximum bandwidth sets the minimum bandwidth.
Symptom: The Fabric Manager (FM) cannot correlate an iSCSI host with two NIC cards when the iSCSI initiator is identified by the IP address (either from a matching static iscsi initiator ip-address command or from an iSCSI interface switchport initiator id ip-address command for dynamic initiators). This is a result of the switch putting IP address in the symbolic-node-name field in the FCNS entry for that initiator. This was done to allow zoning based on IP address in ISAN software Release 1.1(x) and 1.2(x) where zone membership for iSCSI initiator can only be based on symbolic-node-name value.
Workaround: To allow FM to show the above-mentioned host properly, the switch will instead fill the FCNS entry's symbolic-node-name field with the actual iSCSI initiator node name (i.e. its IQN name).
This impacts for users who configure zoning based on iSCSI initiator's IP address via the symbolic node name field, e.g.zone name a vsan 1 member symbolic-nodename 10.2.2.112
Change the above configuration to the following for this configuration to continue working after upgrading to Release 1.3(4a).zone name a vsan 1 member ip-address 10.2.2.112
Symptom: If Write Acceleration was enabled in some cases, the first few Fibre Channel data frames of an IO were not sent to the target for a FCIP write IO operation. This caused the IO operation to abort with a check-condition and also reset the connection to the initiator. This problem was caused by the FCIP Write Acceleration functionality which uses internal timers to free up resources. The software erroneously freed up buffered frames of pending write IO operations.
Symptom: You can TFTP to a Cisco MDS switch through the management interface from any TFTP client. In SAN-OS Releases 1.3(4a), 1.3(4b) and 1.3(5), a default IP access control list (ACL) rule is added to block frames for ports like TFTP, SUNRP and BOOTP.
Workaround: For Cisco MDS SAN-OS Releases 1.2(1a), 1.2(1b), 1.2(2a), 1.3(1), 1.3(2a), 1.3(3), and 1.3(3c), manually create the drop rule by issuing the following commands in succession:switch(config)# ip access-list abc deny udp any any eq port 69switch(config)# ip access-list abc permit ip any anyswitch(config)# interface mgmt 0switch(config-if)# ip access-group abc
Symptom: The SAN-OS software rejects FDISC frames for the following cases:
a. AIX Version 5.1 sends FDISC frame with all zeros. This is not allowed by the FC-FS standards.
b. AIX Version 5.2 (without patch IBM APAR IY54881) has same issue as Case a (above), and sends the FDISC frame to FFFFFC instead of FFFFFE which is not allowed by the standards.
c. The SAN-OS software did not handle the FDISC ELS command which displays N port ID, port WWN, and node WWN values obtained from a prior FLOGI session, but fills in zeros for the common service parameters.
a. Irrespective of AIX fixes, the SAN-OS workaround is required to handle Case c (above).
b. Even if Case a (above) is an AIX 5.1 issue, the SAN-OS patch allows Cisco MDS switches to work with existing AIX 5.1 installations.
c. AIX Version 5.2 with patch IBM APAR IY54881 along with this SAN-OS patch addresses Case b (above).
d. AIX Version 5.2 without the SAN-OS patch will not work as it sends FDISC to FFFFFC, for which no patch is intended in SAN-OS software.
Symptom: Effective Release 1.3.x, despite assigning an IP address to a Gigabit Ethernet interface on a IPS module and enabling that interface (using the no shutdown command), a ping command to the interface's IP address is not answered.
Workaround: You must explicitly enable either FCIP or iSCSI using the enable fcip or enable iscsi commands.
Symptom: If the Cisco MDS SAN-OS fcanalyzer local display-filter command is issued in configuration mode with prepended lengthy and intricate filtering strings, it may cause the actual analyzer process to terminate. There is no impact on the stability of the Cisco MDS switch. Configurations without lengthy display-filters work fine.
Symptom: Under rare circumstances, it is possible to lose the cluster IP address when the config node fails. This problem is fixed in Cisco MDS SAN-OS Release 1.3(5).
Workaround: For releases prior to Cisco MDS SAN-OS 1.3(5):
a. Connect to the switch using the switch's management IP address
b. Use the svc-config and show nodes local commands to verify that the config node of the required cluster in present in that switch.
c. Use the svc-config, cluster config cluster-name, and ip new-ip-address commands to change the cluster IP address for the cluster to another random address.
d. Change the cluster IP address back to the original IP address using the same steps defined in Step C.
Symptom: This caveat applies to Release 1.1(1) up to, and including, Release 1.3(4b). The Fibre Channel port link reinitialization sequence triggered by a link down event does not succeed if the switching module is up for more than 248 days and the last shutdown command on that port was issued 248 days prior to the link failure. After the link-down event, the port remains in the link failure or not connected state as shown in the following command output:switch# show interface fc2/1fc2/1 is down (Link failure or not-connected)
Workaround: Issue the shutdown command, followed by the no shutdown command, on the affected port to bring the port back to link-up state as shown in the following command output:switch# config tswitch(config)# interface fc2/1switch(config)# shutdownswitch(config)# no shutdown
Issue the following commands to verify the module uptime.switch# attach module 2Attaching to module 2 ...
To exit type exit, to abort type $.module-2# show versionSoftwareBIOS: version 1.0.8system: version 2.0(1) [build 2.0(0.139)]BIOS compile time: 08/07/03system compile Time: 10/25/2020 12:00:00HardwareRAM 186668 kBbootflash: 125184 blocks (block size 512b)lc02 uptime is 11 days 18 hours 18 minute(s) 9 second(s)
–Any nondisruptive upgrade or downgrade resets the 248-day window.
–Once the shutdown and no shutdown commands are issued, it is good for another 248 days.
–If the switch has been up for a long time and the customer wants to connect new devices to the switch ports, then you may start with the shutdown and no shutdown commands on those ports.
Symptom: Configuring the CIM server certificate as listed below might cause your switch to crash.
a. Create a self-certified key (xxxxxx.pem file) on an external server (we use a utility under Hi-Command).
b. Enter conf t to enter configuration mode.
c. Enter cimserver certificate xxxxxx.pem to install a certificate specified in the file named with a .pem extension.
d. Enter cimserver enablehttps to enable HTTPS (secure protocol).
e. Enter cimserver enable to enable the CIM server.
f. Enter Ctrl-z to quit
Symptom: The Telnet server may not be disabled even if you disable it through setup. A telnet session will still work in the switch.
Workaround: Issue the no telnet server enable command in configuration mode to disable telnet after you login to the switch.
Symptom: Password recovery might fail if you use the copy <config-url> startup command to save the switch configuration, or if you boot a system image that is older than the image you used to store the configuration and did not use the install all command. The following message might display in syslog or on the console during the process of password recovery.
Workaround: Issue the write erase command from the switchboot prompt.
Note Using the write erase command will erase the configuration. You must reapply the configuration, if externally stored, after the switch login.
Symptom: If the NetApp file server appliance is configured as an initiator performing a Network Data Management Protocol (NDMP) backup, then the fabric login (FLOGI) process on the MDS switch might terminate because of excessive LSTS requests.
This might happen if your N port or NL port uses extended link services to manage and control a public remote loop. The NetApp file server appliance configuration uses these services, namely LSTS and LINIT, which are documented in the Fibre Channel standards compliance (FC-FLA standard) specification.
Workaround: Upgrade to Cisco MDS SAN-OS Release 2.0(4).
Symptom: If iSCSI virtual targets are configured with more than 50 LUN maps, then erroneous overlapping LUN map system messages appear when the iSCSI initiator is not allowed to log in to these iSCSI virtual targets.
Workaround: Limit the number of configured LUN maps for an iSCSI virtual target to fewer than 50 LUNs.
Symptom: A Linux host with an iSCSI driver can see only the first eight Logical Units (LUs) of a configured iSCSI virtual target with more than eight LUN maps configured.
Symptom: In some rare cases, license features are disabled when the IP address on a management port is changed.
Workaround: None. Enable the license features again.
Symptom: If you try to configure SSH key for any of the non-local user- accounts, in some rare cases you might see a core dump on standby.
Workaround: First delete the non-local user-account and create it again so that it becomes a local user-account. Then perform any type of configuration for that user-account. User should not perform configuration operations on non- local user-accounts. Non-local user-accounts can be created due to users getting authenticated using RADIUS/TACACS+ server.
The documentation set for the Cisco MDS 9000 Family includes the following documents:
•Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family
•Cisco MDS 9000 Family Release Notes for Cisco MDS SAN-OS Release 1.3(2a)
•Cisco MDS 9100 Series Quick Start Guide
•Cisco MDS 9500 Series and Cisco MDS 9216 Switch Quick Start Guide
•Cisco MDS 9100 Series Hardware Installation Guide
•Cisco MDS 9216 Switch Hardware Installation Guide
•Cisco MDS 9500 Series Hardware Installation Guide
•Cisco MDS 9000 Family Configuration Guide
•Cisco MDS 9000 Family SAN Volume Controller Configuration Guide
•Cisco MDS 9000 Family Command Reference
•Cisco MDS 9000 Family Fabric and Device Manager User Guide
•Cisco MDS 9000 Family Troubleshooting Guide
•Cisco MDS 9000 Family System Messages Guide
•Cisco MDS 9000 Family MIB Reference Guide
•Cisco MDS 9000 Family CIM Programming Reference Guide
For information on VERITAS Storage Foundation™ for Networks 1.0, Cisco, refer to the following VERITAS documents available at http://support.veritas.com/
•VERITAS Storage Foundation for Networks Overview
•VERITAS Storage Foundation for Networks Installation and Configuration Guide
•VERITAS Storage Foundation for Networks Obtaining and Installing Licenses
•VERITAS Storage Foundation for Networks GUI Administrator's Guide
•VERITAS Storage Foundation for Networks CLI Administrator's Guide
•VERITAS Storage Foundation for Networks README
For information on IBM TotalStorage SAN Volume Controller Storage Software for Cisco MDS 9000, refer to the following IBM documents available on the IBM TotalStorage Support web site: http://www.ibm.com/storage/support/2062-2300/
•Getting Started—IBM TotalStorage SAN Volume Controller Storage Software for Cisco MDS 9000
•Configuration Guide—IBM TotalStorage SAN Volume Controller Storage Software for Cisco MDS 9000
•Supported Hardware List—IBM TotalStorage SAN Volume Controller Storage Software for Cisco MDS 9000
•Supported Software Levels—IBM TotalStorage SAN Volume Controller Storage Software for Cisco MDS 9000
•Command Line Interface User's Guide—IBM TotalStorage SAN Volume Controller Storage Software for Cisco MDS 9000
•Host Attachment Guide—IBM TotalStorage SAN Volume Controller Storage Software
•User Guide—Subsystem Device Driver User's Guide
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
You can find instructions for ordering documentation at this URL:
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).
You can send comments about technical documentation to email@example.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you can perform these tasks:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — firstname.lastname@example.org
•Nonemergencies — email@example.com
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•World-class networking training is available from Cisco. You can view current offerings at this URL:
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.