-
Cisco SN 5400 Series Storage Router Command Reference, Release 3.4
-
About This Guide
-
Chapter 1 - CLI Overview
-
Chapter 2 - A Commands
-
Chapter 3 - C Commands
-
Chapter 4 - D Commands
-
Chapter 5 - E Commands
-
Chapter 6 - F Commands
-
Chapter 7 - H Commands
-
Chapter 8 - I Commands
-
Chapter 9 - L Commands
-
Chapter 10 - M Commands
-
Chapter 11 - N Commands
-
Chapter 12 - P Commands
-
Chapter 13 - R Commands
-
Chapter 14 - S Commands
-
Chapter 15 - Show Commands
-
Chapter 16 - T Commands
-
Chapter 17 - U Commands
-
Chapter 18 - V Commands
-
Chapter 19 - Z Commands
-
Table Of Contents
D Commands
This chapter covers the following commands:
debug aaa
To enable debugging for authentication, authorization, and accounting (AAA) services, use the debug aaa command. To disable debugging for AAA authentication services, use the no form of this command.
debug aaa
no debug aaa
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is not enabled.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to debug problems with iSCSI, Enable and Login authentication or general AAA authentication services. Create log route entries for notification level debugging to send the trace and debug messages to the desired destination, using the logging level command.
Examples
The following example enables AAA debugging:
[SN5428-2A]# debug aaaRelated Commands
debug cmd
To run any operating system command with up to five arguments from the CLI, use the debug cmd command.
debug cmd os-command [parameters]
Syntax Description
os-command
Any valid operating system command. Do not invoke interactive functions.
parameters
Up to five command parameters.
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
The debug cmd command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Examples
The following example displays usage information for the debug cmd:
[SN5428-2A]# debug cmd dbgRunOSCmdHelp 0[SN5428-2A]# debug cmd dbgRunOSCmdHelp 0c 1a c4 3cRunning command dbgRunOSCmdHelp(0xc1ac43c) with args 0 0 0 0 0CLI usage: debug cmd symbol arg1 .. arg5symbol -- any named OS functionarg1 .. arg5 -- numbers (interpreted as hex) orstrings if escaped with an initial '$', such as $fc1Anything that doesn't convert to a number is a stringReturn value is 0 = 0x0 (OK)Related Commands
Enable debugging for AAA authentication services.
Enable debugging for the named SCSI routing instance.
debug fcip
To enable trace facilities for debugging FCIP instances, use the debug fcip command. To disable debugging, use the no form of this command.
debug fcip name {mailboxtrace | packettrace mask}
no debug fcip name mailboxtrace
Syntax Description
Defaults
All trace facilities are enabled, by default. The packet trace mask value defaults to 0xFFFF, capturing all traces.
Command Modes
Administrator.
Command History
Usage Guidelines
The debug fcip command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Use this command to trace traffic associated with the named FCIP instance. Use the show debug fcip command to view the trace buffer output. The mask value defaults to 0xFFF, all packets are traced. A mask value of 0x0000 will turn off packet tracing.
Debug settings are not persistent and will return to default value when the storage router is rebooted. To retain a mask value for packet tracing services, use the fcip destination config command with the pkttracemask keyword to change the FCIP instance configuration and then save the changes to the storage router bootable configuration.
Examples
The following example enables the debug mail box tracing services for the FCIP instance named fcip1:
[SN5428-2A]# debug fcip fcip1 mailboxtraceThe following example enables the debug packet tracing services for the FCIP instance named fcip2. All packets will be traced.
[SN5428-2A]# debug fcip fcip2 packettrace 0xffffThe following example disables debug mail box tracing services for the FCIP instance named fcip1:
[SN5428-2A]# no debug fcip fcip1 mailboxtraceThe following example turns off all packet tracing services for the FCIP instance named fcip2:
[SN5428-2A]# debug fcip fcip2 packettrace 0x0000Related Commands
Create an FCIP instance.
Configure operational parameters for the named FCIP instance.
Display debugging information for the named FCIP instance.
debug interface fc?
To configure a variety of operational parameters for the internal FC interface switch ports, use the debug interface fc? command. To disable various parameters, use the no form of this command.
debug interface fc? {al-fairness | fan-enable |ms-enable} enable
debug interface fc? default
debug interface fc? diag
debug interface fc? enable
debug interface fc? ext-credit nn
debug interface fc? linkspeed {auto | 1gb | 2gb}
debug interface fc? loopback {external | internal | online}
debug interface fc? mfs-bundle enable [timeout nn]
debug interface fc? type {auto | donor | f-port | fl-port | g-port | gl-port}
debug interface fc? type tl-port mode {autobridge | autolearn}
no debug interface fc? {al-fairness | fan-enable | ms-enable} enable
no debug interface fc? enable
no debug interface fc? mfs-bundle enable [timeout nn]
Syntax Description
Defaults
The internal FC switch ports have the following default operational characteristics:
•
fairness algorithm is disabled (switch has priority)
•
•
•
•
•
•
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2. For the SN 5428, the ext-credit keyword was added.
Usage Guidelines
The debug interface fc? command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Caution
Examples
The following example places the internal FC switch port fc0 into diagnostic mode for testing purposes:
[SN5428-2A]# debug interface fc0 diagRelated Commands
debug interface fci?
To specify the maximum number of firmware dump files that can exist on the storage router for a specified initiator interface, or to remove all existing firmware dump files, use the debug interface command.
debug interface if-name {forcefcfwdump | lldrestartfcfw}
debug interface if-name fwdumpcount nn
debug interface if-name removefwdumps
Syntax Description
Defaults
The maximum number of times firmware dump files can be overwritten for each FC initiator interface is 1.
Command Modes
Administrator.
Command History
Usage Guidelines
Best practices suggest clearing all existing firmware dump files for the specified interface before requesting a new firmware dump.
Caution
Examples
The following example sets the maximum number of times the firmware dump files for fci1 can be overwritten to 2:
[SN5428-2A]# debug interface fci1 fwdumpcount 2The following example clears all firmware dump files for fci2:
[SN5428-2A]# debug interface fci2 removefwdumpsRelated Commands
debug interface ge?
To enable packet tracing on a Gigabit Ethernet interface, use the debug interface ge? command. To disable packet tracing, use the no form of this command.
debug interface ge? trace [pktcnt nn] [pktsize nn] enable
no debug interface ge? trace enable
Syntax Description
Defaults
IP packet tracing for all Gigabit Ethernet interfaces is disabled by default. The maximum trace size is 128, and all packets use a circular trace buffer.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
The debug interface ge? command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
•
•
•
Note
Examples
The following example enables IP packet tracing on the ge2 interface:
[SN5428-2A]# debug interface ge2 trace enableThe following example enables IP packet tracing on ge1, for a maximum of 100 packets. A maximum of 200 bytes will be traced per packet.
[SN5428-2A]# debug interface ge1 trace pktcnt 100 pktsize 200 enableRelated Commands
Display a variety of debug information or perform specific troubleshooting activities.
Display IP packet trace statistics or the contents of the trace buffer.
debug ip rip
To enable routing information protocol (RIP) debug log message, use the debug ip rip command. To disable RIP debug log message, use the no form of this command.
debug ip rip
no debug ip rip
Syntax Description
This command has no arguments or keywords.
Defaults
RIP debug log messages are disabled.
Command Modes
Administrator.
Command History
Usage Guidelines
The debug ip rip command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Examples
The following example enables RIP, configures logging to send debug message to all virtual terminal sessions, and then enables RIP debug log messages. The show ip rip command is used to verify the running RIP configuration.
[SN5428-2A]# ip rip enableDec 09 16:12:50: %IP-5-IRMRSAR: RIP Services are running*[SN5428-2A]# logging level debug from ip to vty*[SN5428-2A]# debug ip ripDec 31 12:52:14: %IP-7-IRRPRL00: RIP Packet received from 10.1.30.1 length 124Dec 31 12:52:14: %IP-7-IRRPRL01: command 2 version 1Dec 31 12:52:14: %IP-7-IRRPRL02: route af 2, dest 10.1.40.0 mask 0.0.0.0 nextHop 0.0.0.0 metric 2Dec 31 12:52:14: %IP-7-IRRPRL02: route af 2, dest 10.1.51.0 mask 0.0.0.0 nextHop 0.0.0.0 metric 1*[SN5428-2A]# show ip ripRouting Information Protocol (RIP) Information:Invalid Timer: 180Enabled Flag: trueDebug Flag: trueRunning Flag: trueRelated Commands
debug isns
To enable tracing of iSNS Protocol Data Units (PDUs), use the debug isns command. To disable the iSNS trace facility, use the no form of this command.
debug isns trace [pducnt nn] [pdusize nn] enable
no debug isns trace enable
Syntax Description
Defaults
iSNS PDU tracing is disabled. The default PDU size is 1024 bytes, and uses a circular trace buffer.
Command Modes
Administrator.
Command History
Usage Guidelines
The debug isns command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Examples
The following example enables iSNS PDU tracing:
[SN5428-2A]# debug isns trace enableThe following example enables iSNS PDU tracing, for a maximum of 100 PDUs. A maximum of 40 bytes will be traced per PDU.
[SN5428-2A]# debug isns trace pducnt 100 pdusize 40 enableRelated Commands
debug scsirouter
To enable trace facilities for debugging SCSI routing instances, use the debug scsirouter command. To disable debugging, use the no form of this command.
debug scsirouter name scsitrace
no debug scsirouter name scsitrace
Syntax Description
name
The name of the SCSI routing instance to be debugged.
scsitrace
Keyword indicating tracing services will be enabled.
Defaults
All trace facilities are enabled by default.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
When enabled at this level, debug tracing will trace traffic to and from all targets associated with the named SCSI routing instance. Use the show debug scsirouter command to view the trace buffer output.
Examples
The following example enables debug tracing facilities for a SCSI routing instance named foo:
[SN5428-2A]# debug scsirouter foo scsitraceRelated Commands
debug scsirouter iscsitrace
To enable trace facilities for debugging iSCSI connections to and from SCSI routing instances, use the debug scsirouter iscsitrace command. To disable iSCSI trace facilities, use the no form of this command.
debug scsirouter name iscsitrace [fromto {A.B.C.D/bits | A.B.C.D/1.2.3.4}] [pducnt nn] [pdusize nn] enable
no debug scsirouter name iscsitrace enable
Syntax Description
Defaults
The following are the default iSCSI trace options:
•
•
•
•
Command Modes
Administrator.
Command History
Usage Guidelines
The debug scsirouter iscsitrace command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Use the show debug scsirouter command with the iscsitrace keyword to display iSCSI trace information.
Examples
The following example enables iSCSI trace facilities for the SCSI routing instance named zeus, using the default iSCSI trace options:
[SN5428-2A]# debug scsirouter zeus iscsitrace enableRelated Commands
Enable debugging for the named SCSI routing instance.
Enable debugging for a specific SCSI routing instance target and LUN combination.
Display trace buffer output.
debug scsirouter target
To enable trace facilities for debugging a specific SCSI routing instance target and LUN combination, use the debug scsirouter target command. To disable debugging, use the no debug scsirouter target form of this command.
debug scsirouter name target name lun nn scsitrace
no debug scsirouter name target name lun nn scsitrace
Syntax Description
Defaults
All trace facilities are enabled by default.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
When enabled at this level, SCSI tracing will trace traffic to and from the specified target and LUN combination associated with the named SCSI routing instance. Use the show debug scsirouter command to view the trace buffer output.
Examples
The following example enables SCSI tracing facilities for the target and LUN combination myTarget, LUN 0, associated with the SCSI routing instance named foo:
[SN5428-2A]# debug scsirouter foo target myTarget lun 0 scsitraceRelated Commands
delete accesslist
To delete an entire access list, all access lists, or a specified entry from the named access list, use the delete accesslist command. This command does not change the persistent storage router configuration until the relevant configuration information has been saved using the appropriate save command with the bootconfig keyword.
delete accesslist all
delete accesslist name [A.B.C.D/bits | A.B.C.D/1.2.3.4]
delete accesslist name [chap-username username | iscsi-name string]
delete accesslist name all
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
2.3.1
The chap-username and iscsi-name keywords were added.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Because access lists are cluster entities, this operation affects all targets associated with this access list, regardless of where the associated SCSI routing instance is running within the high availability cluster.
•
•
Changes to access lists do not impact currently connected IP hosts; changes are effective for all subsequent connections.
Note
In a cluster environment, access list management functions are handled by a single storage router. To determine which storage router is performing access list management functions, issue the show cluster command. If you issue a delete accesslist command from a storage router that is not performing access list management functions, the CLI displays an informational message with the name of the node that is currently handling those functions.
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information on operating the storage router in a cluster.
Examples
The following example completely deletes the access list named fooList from the currently running configuration:
[SN5428-2A]# delete accesslist fooListThe following example deletes all entries from the access list named fooList1. The access list entity itself is not deleted from the currently running configuration:
[SN5428-2A]# delete accesslist fooList1 allThe following example deletes all access lists from the currently running configuration:
[SN5428-2A]# delete accesslist allThe following example deletes the specified IP address from the named access list, fooList2. This command does not update the bootable configuration of the storage router until a save accesslist bootconfig or save all bootconfig command is issued.
[SN5428-2A]# delete fooList2 192.168.54.12/32The following example deletes the specified CHAP user name from the named accesslist, fooList3. This command does not update the bootable configuration of the storage router until a save accesslist bootconfig or save all bootconfig command is issued.
[SN5428-2A]# delete fooList3 chap-username webserver15The following example deletes the specified iSCSI Name from the named accesslist, fooList4. This command does not update the bootable configuration of the storage router until a save accesslist bootconfig or save all bootconfig command is issued.
[SN5428-2A]# delete fooList4 iscsi-name ign.1987-05.com.cisco.01.8838a325b4017fRelated Commands
delete fcalias
To delete the named alias, or the specified member WWPN from the named alias, use the delete fcalias command.
delete fcalias alias-name [member wwpn xxxxxxxxxxxxxxxx]
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
An alias is a collection of Fibre Channel devices, such as switches, initiators, storage and other storage routers, that can be zoned together. An alias is not a zone and cannot include a zone or another alias as a member.
Use this command to delete an entire alias and all its members from the zoning database, or to delete a specified member WWPN from an alias.
If the alias is a member of the active zone set, the alias will not be removed from the active zone set until the active zone set is deactivated. Use the no zoneset command with the enable keyword to deactivate the active zone set.
Caution
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about FC fabric zoning.
Examples
The following example deletes the alias named AliasFoo and all its members. The alias will be removed from all zone sets in which it is used.
[SN5428-2A]# delete fcalias AliasFooThe following example deletes the member WWPN 21000004ed4105ab from the alias AliasFoo:
[SN5428-2A]# delete fcalias AliasFoo member wwpn 21000004ed4105abRelated Commands
Create an alias entity for use in Fibre Channel zoning.
Add the specified member to the named alias.
Display information about aliases and their members.
delete fcip
To delete the named elements from the FCIP instance, or to delete the named instance or all FCIP instances, use the delete fcip command. This command does not change the persistent storage router configuration until the relevant configuration information has been saved using the appropriate save command with the bootconfig keyword.
delete fcip {name | all}
delete fcip name destination
Syntax Description
name
The name of the FCIP instance.
all
Keyword, used to delete all FCIP instances from the storage router.
Note
Defaults
None.
Command Modes
Administrator.
Command History
3.3.1
This command was introduced for the SN 5428-2.
3.4.1
The destination name argument was removed.
Usage Guidelines
Use this command if you want to reconfigure the FCIP instance. You can delete the peer destination or the entire FCIP instance, or all FCIP instances. You must save the configuration changes to update the storage router bootable configuration.
Examples
The following examples deletes the destination from the FCIP instance, fcip2:
[SN5428-2A]# delete fcip fcip2 destinationThe following example deletes all FCIP instances:
[SN5428-2A]# delete fcip allThe following example deletes the FCIP instance named fcip1:
[SN5428-2A]# delete fcip fcip1Related Commands
Create an FCIP instance.
Display configuration and operational information for the named FCIP instance.
delete logging
To delete a rule from the logging table, use the delete logging command.
delete logging level notification-level from facility-name
delete logging #?
delete logging #nn
Syntax Description
level notification-level
The notification level of the routing rules entry to be deleted. See Table 4-1 in the Usage Guidelines section for a list of valid names that can be used for the notification-level argument.
from facility-name
The name of the facility. A facility is the feature area from which the message is received. See Table 4-2 in the Usage Guidelines section for a list of valid facility names.
#?
Request an indexed list of entries in the logging table.
#nn
The index number from the displayed list of entries. The specified routing rule will be deleted.
Defaults
None.
Command Modes
Administrator.
Command History
2.3.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Event, trace and debug messages can be routed to various destinations, based on the notification level of the message and the application area (facility) that generated the message. When a log message is received by the storage router, the logging table rules are searched by facility name and by message level until a match is found. The log message is sent to all the destinations specified by the matching rule.
Use this command to delete logging rules based on notification level and facility name, or by index number.
To display an indexed lists of entries in the logging table, use the number sign (#) character followed by a question mark (?). That action will cause the routing rules in the logging table to be displayed as a numbered (indexed) set of lines. The command is displayed at the prompt below the list to the point of the # keyword. Complete the command by entering the appropriate index number. The specified routing rule will be deleted.
The level limits logging to messages of the specified level or lower levels, based on level number. Table 4-1 describes the available logging levels.
Note
Each facility can have up to eight notification levels. Each facility and notification level pair can have up to seven destinations. Table 4-2 describes the available facility names.
Use the save system bootconfig or save all bootconfig commands to save the updated logging table.
Examples
The following example displays the logging table and then deletes the routing rule entry for messages at level info from facility all:
[SN5428-2A]# show loggingLogging is enabledIndex Level Priority Facility Route1 info 6 all console logfile2 debug 7 HA logfile rslogSyslog host is enabled, ip-address is 10.1.1.144[SN5428-2A]# delete logging level info from allThe following example displays an indexed list of the routing rules in the logging table and then deletes the third entry:
[SN5428-2A]# delete logging #?Logging is enabledIndex Level Priority Facility Route1 critical 2 all console logfile2 debug 7 SNMP rslog3 notice 5 HA all4 warning 4 CDP rslogSyslog host is enabled, ip-address is 10.1.1.144[SN5428-2A]# delete logging #3Related Commands
delete savedconfig
To remove the named file from the savedconfig directory, use the delete savedconfig command.
delete savedconfig {filename | all}
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use the show savedconfig command to display the contents of the savedconfig directory.
Examples
The following example removes the configuration file named foo_config from the storage router:
[SN5428-2A]# delete savedconfig foo_configRelated Commands
delete script
To remove the named command file from the script directory, use the delete script command.
delete script {filename | all}
Syntax Description
filename
The name of the command file to be deleted. This file must exist in the script directory.
all
Keyword, indicating that all command files in the script directory are to be deleted.
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use the show script command to display the contents of the script directory or the specified command file.
Examples
The following example removes the command file named foo_script from the storage router:
[SN5428-2A]# delete script foo_scriptRelated Commands
delete scsirouter
To delete the named elements from the SCSI routing instance, use the delete scsirouter command. This command does not change the persistent storage router configuration until the relevant configuration information has been saved using the appropriate save command with the bootconfig keyword.
delete scsirouter {name | all} [connection nn | serverif ge? [vlan vid]]
delete scsirouter {name | all} serverif ge? force
delete scsirouter {name | all} target {name | all} [lun nn]
delete scsirouter {name | all} target {name | all} [lun nn] force
delete scsirouter {name | all} force
delete scsirouter name all
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
In a cluster environment, changes to the SCSI routing instance can only be made on the storage router that is the currently running that instance. The SCSI routing instance may be in a stopped state at the time it is deleted.
The force option allows the SCSI routing instance to be deleted from a storage router that is not currently running the instance. The force option should only be used when the storage router, or a specific SCSI routing instance, is in an abnormal state and cannot be recovered without rebooting.
When used with the target or LUN keywords, the force option allows the specified object to be deleted, even if in use by an iSCSI driver. Under normal circumstances, a target or LUN cannot be deleted if an iSCSI driver is logged in.
Use the all keyword to delete all attributes of a named SCSI routing instance. The named SCSI routing instance, however, is not deleted.
Note
Examples
The following example deletes all targets associated with the SCSI routing instance named foo:
[SN5428-2A]# delete scsirouter foo target allThe following example deletes the specified VLAN from the Gigabit Ethernet interface, ge2, used by the SCSI routing instance named foo2:
[SN5428-2A]# delete scsirouter foo2 serverif ge2 vlan 101The following example deletes all attributes of the SCSI routing instance named foo3. The SCSI routing instance named foo3 remains available for configuration on the storage router.
[SN5428-2A]# delete scsirouter foo3 allThe following example deletes the entire SCSI routing instance named foo4:
[SN5428-2A]# delete scsirouter foo4
Note
Related Commands
delete software version
To delete a version of software from the storage router, use the delete software version command.
Note
delete software version {v.x.y | all}
Syntax Description
v.x.y
The version of storage router software to be deleted.
all
Delete all non-bootable and non-current software versions.
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to remove old versions of software from the storage router.
Examples
The following example removes version 2.0.1 from the storage router:
[SN5428-2A]# delete software version 2.0.1Related Commands
delete zone
To delete the specified Fibre Channel (FC) zone or the specified member of the zone from the zoning database, use the delete zone command.
delete zone name [member {fcalias alias-name | fcid port-id | wwpn xxxxxxxxxxxxxxxx}]
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
A zone is a group of FC ports or devices, such as switches, storage or storage routers, grouped together to control the exchange of information.
Use this command to delete the specified zone from the zoning database. If the zone is a member of the active zone set, the zone will not be removed from the active zone set until the active zone set is deactivated. Use the no zoneset command with the enable keyword to disable the active zone set.
Use the member keyword to delete the specified alias, Port ID or WWPN member from the named zone.
Caution
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about FC fabric zoning.
Examples
The following example deletes the zone named testlab from the zoning database:
[SN5428-2A]# delete zone testlabThe following example deletes the alias member myfoo from the zone webservices:
[SN5428-2A]# delete zone webservices member fcalias myfooRelated Commands
delete zoneset
To delete the specified zone from the zone set or to delete the entire named zone set from the zoning database, use the delete zoneset command.
delete zoneset name [zone name]
Syntax Description
name
The name of the zone set.
zone name
(Optional) Deletes the named zone from the specified zone set.
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
A zone set is a group of zones. Zoning enables you to divide the ports and devices of the Fibre Channel fabric into zones for more efficient and secure communication among functionally grouped nodes. Only one zone set can be active at a time. The active zone set defines the zoning for the Fibre Channel fabric.
Use this command to delete an entire zone set from the zoning database or only the named zone from the zone set. If the zone set is active, the command does not take effect until the zone set is deactivated. Use the no zoneset command with the enable keyword to disable the active zone set.
Caution
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about FC fabric zoning.
Examples
The following example deletes the zone set named testgroup:
[SN5428-2A]# delete zoneset testgroupThe following example deletes the zone named zoneA from the zoneset named testgroupA:
[SN5428-2A]# delete zoneset testgroupA zone zoneARelated Commands
download software
To fetch the specified object from the named location or the default download location, use the download software list command.
download software {http | proxy} {list | url full_url | version v.x.y}
download software tftp {hostname host filename file | list | version v.x.y}
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
The list of available software versions is stored in the file named sw-sn5428-2-versions.txt. This text file must contain one line for each version of software that is available from the download location. If you store and download software from a site other than the system default (http://www.cisco.com), create this file and update it whenever a new version of software is available.
Software is either downloaded from the default locations set for the specified protocol or from the location specified as part of the command. Always verify software after it has downloaded to assure no errors were encountered. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for details on verification and making updated software available to the storage router.
A maximum of two versions of software can be stored on the storage router.
Note
Examples
The following example downloads storage router software version 3.3.1-K9 from the default location via standard Hypertext Transfer Protocol (HTTP):
[SN5428-2A]# download software http version 3.3.1-K9The following example downloads a file named sn5428-2v331.tar from the TFTP host named my_tftpHost. The file must exist in the default TFTP directory.
[SN5428-2A]# download software tftp hostname my_tftpHost filename sn5428-2v331.tarThe following file downloads the list of available software from the default location using the proxy configuration:
[SN5428-2A]# download software proxy listRelated Commands
