-
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
F Commands
This chapter covers the following commands:
•
fcip
failover eligibility
To enable failover by eligibility for all SCSI routing instances running on the storage router, use the failover eligibility command. To disable failover by eligibility, use the no form of this command.
failover eligibility on
no failover eligibility on
Syntax Description
on
Keyword used to enable failover by eligibility for all SCSI routing instances running on the storage router.
Defaults
Failover by eligibility is enabled.
Command Modes
Administrator mode.
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
Each storage router in a cluster maintains and exchanges information about available resources. Failover by eligibility is enabled by default; HA bases the decision to automatically fail over a SCSI routing instance to another node in a cluster based on the Fibre Channel and other resources available to that SCSI routing instance.
Failover occurs when:
•
•
•
•
For more manual control over where a SCSI routing instance runs, use the no failover eligibility on command to prevent failover by eligibility on a storage router. If a SCSI routing instance is running on (or fails over to) a storage router that is configured with failover by eligibility turned off, it will continue running on that storage router unless there are no mapped targets available or a critical resource is unavailable.
Use the failover eligibility on command to restore normal failover functions.
The failover eligibility setting is not retained across a reboot; restarting the storage router restores the default setting (failover by eligibility is enabled).
Examples
The following example disables failover by eligibility for all SCSI routing instances running on the storage router named SN 5428-2A:
[SN5428-2A] no failover eligibility onRelated Commands
failover scsirouter
To cause the named SCSI routing instance to cease running on this storage router and start running on another storage router in the cluster, use the failover scsirouter command.
Note
failover scsirouter name [pri | sec | to systemname]
failover scsirouter all [to systemname]
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
Use the all keyword to failover all SCSI routing instances currently running on this storage router. Each storage router can run a maximum of 12 SCSI routing instances; there is a maximum of 12 SCSI routing instances per cluster.
Examples
The following example causes the SCSI routing instance named foo to failover to another storage router in the cluster:
[SN5428-2A]# failover scsirouter fooThe following example causes all SCSI routing instances to failover to the storage router named TestLab1:
[SN5428-2A]# failover scsirouter all to TestLab1Related Commands
fcalias
To create an alias entity for use in Fibre Channel zoning, use the fcalias command. An alias is a group of FC ports or devices (such as switches, storage or storage routers) that are grouped together for convenience.
fcalias alias-name
Syntax Description
alias-name
The name of the alias entity created by this command. Enter a maximum of 31 characters. The name must begin with an alpha character.
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 allows you to group FC ports and devices together for zoning purposes. Unlike zones, however, aliases do not impose any communication restrictions on its members. An alias can belong to one or more zones, but a zone cannot be a member of an alias, nor can an alias be a member of another alias.
You must create a named alias entity before you can add members to the alias.
A default alias of iscsi is provided that contains both initiators WWPN1 and WWPN2.
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 creates an alias entity named LabGroupA:
[SN5428-2A]# fcalias LabGroupARelated Commands
fcalias member
To add the specified member to the named alias, use the fcalias member command. An alias is a group of FC ports or devices (such as switches, storage or storage routers) that are grouped together for convenience.
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 allows you to group FC ports and devices together for zoning purposes. Unlike zones, however, aliases do not impose any communication restrictions on its members. An alias can belong to one or more zones, but a zone cannot be a member of an alias, nor can an alias be a member of another alias.
The command verifies the format of the WWPN, but does not verify that the specified device exists. A default alias of iscsi is provided that contains both initiators WWPN1 and WWPN2.
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 creates the alias named LabGroupA, and then adds the devices with the WWPN 2200001026558a0f and 220000201744ab3c to the named alias:
[SN5428-2A]# fcalias LabGroupA[SN5428-2A]# fcalias LabGroupA member wwpn 2200001026558a0f[SN5428-2A]# fcalias LabGroupA member wwpn 220000201744ab3cRelated Commands
fcip
To create an FCIP instance, use the fcip command.
fcip name
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
FCIP provides connectivity between SANs. Technically, it employs Fibre Channel over TCP/IP (FCIP) to provide block oriented FC devices connectivity over an IP network. FCIP allows the interconnection of islands of FC storage area networks (SANs) over IP-based networks to form a unified SAN in a single FC fabric. The FCIP instance becomes a binding point for the association of other configuration parameters.
An FCIP instance runs with a point-to-point connection to an FCIP instance on a peer SN 5428-2 Storage Router or MDS 9000 Series system. Each FCIP instance requires one and only one peer.
There can be a maximum of 2 FCIP instances defined per storage router. Each FCIP instance is associated with:
•
•
•
This command updates the running configuration of the storage router. You must save the FCIP instance configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Issue the save fcip command with the bootconfig keyword to save the FCIP instance to the storage router bootable configuration.
Examples
The following example creates an FCIP instance named fcip1:
[SN5428-2A]# fcip fcip1Related Commands
fcip description
To add user-defined identification information to the named FCIP instance, use the fcip description command.
fcip name description "user text"
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
This command allows you to add a new description or change an existing description. Descriptions are site-specific.
Examples
The following example adds the description "Access to lab SAN island 7" to the FCIP instance fcip1:
[SN5428-2A]# fcip fcip2 description "Access to lab SAN island 7"Related Commands
Create an FCIP instance.
Display configuration and operational information for the named FCIP instance.
fcip destination config
To configure operational parameters for the selected FCIP connection protocol type, use the fcip destination config command.
fcip name destination config {rxtcpwinsize | txtcpwinsize} nn
fcip name destination config tcpport port-number
fcip name destination config batchtcp {yes | no}
fcip name destination config {bcouthiwater | burstouthiwater} nn
fcip name destination config frouthiwater nn
fcip name destination config peerneedsackhiwater nn
fcip name destination config {initialtimeout | maxtimeout | totaltimeout} nn
fcip name destination config ipprotocol nn
fcip name destination config rexmitcount nn
fcip name destination config timeoutincrement nn
fcip name destination config frinhiwater nn
fcip name destination config idlepingdelay nn
fcip name destination config pkttracemask mask
fcip name destination config usebport {yes | no}
fcip name destination config compression {off | on}
Syntax Description
Defaults
The following are the default settings for all FCIP connection configuration options:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The default error recovery algorithm for raw connection protocol uses maxtimeout and rexmitcount values (timeout = maxtimeout / rexmitcount--).
Note
Command Modes
Administrator.
Command History
3.3.1
This command was introduced for the SN 5428-2.
3.4.1
The compression keyword was added and the destination name argument was removed.
Usage Guidelines
Each FCIP instance requires three active elements:
•
•
•
An FCIP instance runs with a point-to-point connection to an FCIP instance on a peer SN 5428-2 Storage Router or MDS 9000 Series system. Each FCIP instance requires one and only one peer. Both FCIP instances must be configured to use the same connection protocol, TCP/IP or raw IP.
TCP/IP connection protocol uses the FCIP standard and TCP flow control and error recovery algorithms. FCIP, using TCP connections, allows you to configure TCP receive and transmit window sizes. Raw IP uses a proprietary protocol, but allows you to configure a wider variety of operational settings, providing more granular control over flow control and error recovery. All changes to raw IP operational parameters are applied immediately. Changes to TCP operational parameters are not applied until the FCIP instance is stopped and restarted, or the storage router is rebooted.
Raw IP connections have unique flow control settings for network transmissions and FC transmissions. The FC transmission counter (the frinhiwater keyword) limits the number of frames given to the FC interface for transmission. The FC frames are only acknowledged once they have been transmitted out of the storage router. The network transmissions are controlled by both a byte counter (the burstouthiwater keyword) and a frame counter (the frouthiwater keyword). FCIP will not transmit data when either counter has reached its high water mark. The data is queued until the counters have receded from their high water mark.
Raw IP uses four error recovery algorithms. These algorithms use five different operational settings, which control which error recovery algorithm is used.
•
•
•
•
•
The following are the available error recovery algorithms:
1.
–
For example, using a maxtimeout value of 48 and rexmitcount value of 4 would result in retransmissions at 12, 16, 24 and 48 ticks. This is the default error recovery algorithm.
2.
–
For example, using a timeoutincrement value of 8 and a rexmitcount value of 4 would result in retransmissions at 8, 16, 24 and 32 ticks.
3.
–
–
For example, using a timeoutincrement value of 2, an initialtimeout value of 8, and a rexmitcount of 4 would result in retransmissions at 8, 16, 32 and 64 ticks.
4.
–
–
For example, using a totaltimeout value of 48 and a rexmitcount value of 4 would result in retransmissions at 4, 9, 14 and 17 ticks.
By default, a raw IP connection uses the first error recovery algorithm. To use another error recovery algorithm, set the desired values for the appropriate operational settings. For example, to use the second error recovery algorithm, set the timeoutincrement and, optionally, the rexmitcount. To use the fourth error recovery algorithm, set the totaltimeout and, optionally, the rexmitcount.
Examples
The following example add the destination at IP address 10.1.40.27 to the FCIP instance named fcip1. The FCIP instance is configured to use TCP/IP connection protocol and will initiate the connection (TCP client). The destinations TCP receive window size is set to 1 MB.
[SN5428-2A]# fcip fcip1 destination tcpclient 10.1.40.27*[SN5428-2A]# fcip fcip1 destination config rxtcpwinsize 1048576Related Commands
fcip destination raw
To add a peer destination to the named FCIP instance, with a connection type of raw IP, use the fcip destination raw command.
fcip name destination raw {A.B.C.D | servername}
Syntax Description
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 and the servername argument was added.
Usage Guidelines
Each FCIP instance requires three active elements:
•
•
•
An FCIP instance runs with a point-to-point connection to an FCIP instance on a peer SN 5428-2 Storage Router or MDS 9000 Series system. Each FCIP instance requires one and only one peer. Use this command to configure a peer destination name and IP address, using raw IP as the protocol type.
The destination IP address is the Gigabit Ethernet IP address of the FCIP instance running in the peer system. Both FCIP instances must be configured to use the same connection protocol.
Raw IP uses a proprietary connection protocol, but provides more operational control over flow control and error recovery than standard TCP/IP.
Note
Examples
The following example configures the FCIP instance named fcip1 with a destination at IP address 10.1.3.47, using raw IP connection protocol:
[SN5428-2A]# fcip fcip1 destination raw 10.1.3.47Related Commands
fcip destination tcpclient
To add a peer destination to the named FCIP instance, with a connection type of TCP/IP, use the fcip destination tcpclient command. The named FCIP instance will initiate the TCP connection.
fcip name destination tcpclient {A.B.C.D | servername}
Syntax Description
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 and the servername argument was added.
Usage Guidelines
Each FCIP instance requires three active elements:
•
•
•
An FCIP instance runs with a point-to-point connection to an FCIP instance on a peer SN 5428-2 Storage Router or MDS 9000 Series system. Each FCIP instance requires one and only one peer.
Use this command to configure a peer destination IP address (or name), using TCP/IP as the protocol type. When configured as a TCP client, the FCIP instance initiates the connection to the peer destination. The peer destination must be configured as a TCP server. The TCP server listens for the initial connection.
Note
The destination IP address is the Gigabit Ethernet IP address of the FCIP instance running in the peer system.
TCP/IP connection protocol uses the FCIP standard and TCP flow control and error recovery algorithms. FCIP, using TCP connections, allows you to configure TCP receive and transmit window sizes.
Note
Examples
The following example configures the FCIP instance named fcip2 with a destination at IP address 10.1.4.32, using TCP/IP connection protocol. The FCIP instance is configured as a TCP client, and will initiate the TCP connection to the destination.
[SN5428-2A]# fcip fcip2 destination tcpclient 10.1.4.32Related Commands
fcip destination tcpserver
To add a peer destination to the named FCIP instance, with a connection type of TCP/IP, use the fcip destination tcpserver command. The named FCIP instance will listen for the TCP connection from the named destination.
fcip name destination tcpserver {A.B.C.D | servername}
Syntax Description
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 and the servername argument was added.
Usage Guidelines
Each FCIP instance requires three active elements:
•
•
•
An FCIP instance runs with a point-to-point connection to an FCIP instance on a peer SN 5428-2 Storage Router or MDS 9000 Series system. Each FCIP instance requires one and only one peer.
Use this command to configure a peer destination IP address, using TCP/IP as the protocol type. When configured as a TCP server, the FCIP instance listens for the connection from the peer destination. The peer destination must be configured as a TCP client. The TCP client initiates the TCP initial TCP connection.
Note
The destination IP address is the Gigabit Ethernet IP address of the FCIP instance running in the peer system.
TCP/IP connection protocol uses the FCIP standard and TCP flow control and error recovery algorithms. FCIP, using TCP connections, allows you to configure TCP receive and transmit window sizes.
Note
Examples
The following example configures the FCIP instance named fcip1 with a destination at IP address 10.1.5.222, using TCP/IP connection protocol. The FCIP instance is configured as a TCP server, and will listen for the TCP connection from the destination.
[SN5428-2A]# fcip fcip1 destination tcpserver 10.1.5.222Related Commands
fcip enable
To start the named FCIP instance, use the fcip enable command. To stop the named FCIP instance, use the no form of this command.
fcip {name | all} enable
no fcip {name | all} enable
Syntax Description
name
The name of the FCIP instance to be started. Valid names are fcip1 and fcip2.
all
Start all FCIP instances on this storage router.
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
FCIP instances are automatically started by the storage router during the creation process and when the storage router is restarted. Use this command to manually control the running state of FCIP instances.
Use the all keyword to start all FCIP instances on the storage router. All instances previously stopped on this storage router will be restarted. This form of the command is always available; the only time the command is available for a named FCIP instance is when that FCIP instance has been previously stopped.
Examples
The following example starts the FCIP instance named fcip2. This instance must have been previously stopped.
[SN5428-2A]# fcip fcip2 enableThe following example stops all FCIP instances running on the storage router:
[SN5428-2A]# no fcip all enableRelated Commands
fcip networkif
To assign a Gigabit Ethernet interface and IP address to the named FCIP instance, use the fcip networkif command. The specified interface provides IP connectivity between the FCIP instance and its peer destination.
fcip name networkif {A.B.C.D/bits | A.B.C.D/1.2.3.4} [secondary]
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
The specified interface IP address is configured as the destination IP address for the FCIP instance running in the peer system.
Each FCIP instance requires three active elements:
•
•
•
An FCIP instance runs with a point-to-point connection to an FCIP instance on a peer SN 5428-2 Storage Router or MDS 9000 Series system. Each FCIP instance requires one and only one peer.
Note
Use this command to configure an IP address for the FCIP instance, to be used by the FCIP peer for IP connectivity. For the FCIP instance named fcip1, the IP address is automatically associated with the Gigabit Ethernet interface, ge1. For the FCIP instance named fcip2, the IP address is automatically associated with the Gigabit Ethernet interface, ge2.
When configuring an FCIP instance, you must configure the network interface before you configure the peer destination and protocol.
If the secondary keyword is used, both Gigabit Ethernet interfaces must be connected to the same network segment. If the primary interface goes down and remains down for two seconds, the IP address will be moved to the secondary interface.
Note
You can configure two FCIP instances on a single storage router to use the same network interface. You must fully configure one FCIP instance, and then configure a second FCIP instance without configuring a network interface. The second FCIP instance will use the same network interface as configured for the first instance. The two FCIP instances should use different connection protocols, or if both are configured as TCP servers, each FCIP instance must use a unique TCP port number.
Examples
The following command adds the IP address 10.1.10.128/24, to the FCIP instance named fcip2. This IP address will automatically be associated with the Gigabit Ethernet interface, ge2.
[SN5428-2A]# fcip fcip2 networkif 10.1.10.128/24The following command adds the IP address 10.1.30.128, with a netmask of 255.255.255.0, to the FCIP instance fcip1. This IP address is automatically associated with the Gigabit Ethernet interface, ge1. If the primary interface is not available, the IP address will be moved to the secondary Gigabit Ethernet interface, ge2. The Gigabit Ethernet interfaces must be connected to the same network.
[SN5428-2A]# fcip fcip1 networkif 10.1.30.128/255.255.255.0 secondaryThe following set of commands configures the FCIP instance named fcip1, adds the network IP address 10.1.40.42/24, and configures the destination with a TCP client connection type. The second FCIP instance, fcip2, is configured with a destination and a TCP server connection type. Both FCIP instances will use the 10.1.40.42/24 network interface.
[SN5428-2A]# fcip fcip1*[SN5428-2A] fcip fcip1 networkif 10.1.40.42/24*[SN5428-2A] fcip fcip1 destination tcpclient 10.1.1.144*[SN5428-2A] fcip fcip2*[SN5428-2A] fcip fcip2 destination tcpserver 10.1.5.73Related Commands
fcswitch beacon enable
To enable all Fibre Channel port Logged-In (LOG) LEDs to flash, use the fcswitch beacon enable command. To disable LOG LED flashing, use the no form of this command.
fcswitch beacon enable
no fcswitch beacon enable
Syntax Description
This command has no arguments or keywords.
Defaults
Beacon flashing is disabled, by default. See the appropriate Cisco Storage Router Hardware Installation Guide for your storage router model for default LOG LED indication descriptions.
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
Use this command to assist in locating a physical unit. This command is primarily used for troubleshooting purposes.
Examples
The following example causes all Fibre Channel port LOG LEDs on the storage router to flash:
[SN5428-2A]# fcswitch beacon enableRelated Commands
Display internal Fibre Channel interface parameters.
Display global configuration information for storage router FC interfaces.
fcswitch devlog
To specify the logging parameters for the storage router's integrated Fibre Channel (FC) switch component development log file, use the fcswitch devlog command.
fcswitch devlog components component1 [component2...]
fcswitch devlog level notification-level
Syntax Description
components component1 [component2...]
At least one of the components described in Table 6-1.
level notification-level
Limit logging to messages of a specified level or lower. See Table 6-2 in the Usage Guidelines section for a list of valid names that can be used for the notification-level argument.
Defaults
No components or notification level are configured. Development logging for the storage router's integrated FC switch component is disabled.
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 fcswitch devlog command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
After logging is enabled, use this command to limit the amount of information recorded in the switch development log by component and by notification level. To stop all logging for all components, set the notification level to none. Use the fcswitch devlog enable command to enable development logging.
Examples
The following example limits the switch development log file to informational messages only from the management application and the class 2 frame handler:
[SN5428-2A]# fcswitch devlog components MgmtApp Fc2[SN5428-2A]# fcswitch devlog level infoThe following example stops all switch devlog logging:
[SN5428-2A]# fcswitch devlog level noneRelated Commands
fcswitch devlog enable
To start development logging for the storage router's integrated Fibre Channel (FC) switch component, use the fcswitch devlog enable command. To stop development logging, use the no form of this command.
fcswitch devlog enable
no fcswitch devlog enable
Syntax Description
This command has no arguments or keywords.
Defaults
Development logging is stopped.
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 fcswitch devlog enable command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Examples
The following example starts development logging for the FC switch component and limits the switch development log file to informational messages only from the management application and the class 2 frame handler:
[SN5428-2A]# fcswitch devlog components MgmtApp Fc2[SN5428-2A]# fcswitch devlog level info[SN5428-2A]# fcswitch devlog enableRelated Commands
fcswitch diag
To set all Fibre Channel (FC) interfaces into diagnostic mode for testing purposes, use the fcswitch diag command.
fcswitch diag
Syntax Description
This command has no arguments or keywords.
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
Use this command to change all FC interfaces to diagnostic mode prior to performing internal or external loopback testing on individual FC interfaces.
•
•
Examples
The following example sets all FC interfaces into a diagnostic state and then performs an internal loopback test on the FC interface named fc6:
[SN5428-2A]# fcswitch diag[SN5428-2A]# interface fc6 loopback internalRelated Commands
fcswitch domainid
To set the storage router's domain ID for switched zoned fabric to a unique value, and to prevent the FC fabric from changing that domain ID, use the fcswitch domainid command. To disable the lock and allow the domain ID to be changed by the switched zoned fabric, use the no form of this command.
fcswitch domainid {domain-id} [force]
fcswitch domainid lock enable
no fcswitch domainid lock enable
Syntax Description
Defaults
The default domain ID for fabric zoning is 1. The domain ID can be changed by the switched zoned fabric, by default.
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
Use this command to set the storage router's domain identification number for switched zoned fabric to a unique value or to prevent changes to that value by the zoned fabric. Domain IDs allow fabrics to be segmented into different areas.
Domain IDs must be unique among all switch elements within a fabric. If there is a domain ID conflict, the expansion ports (ports operating as E_Ports) on the two conflicting elements are disabled, isolating the Interswitch Link (ISL).
If you are planning to connect to a switched zoned fabric via one or more FC interfaces, complete the appropriate zoning configuration for the storage router, as described in the appropriate Cisco Storage Router Software Configuration Guide for your storage router model.
Note
Examples
The following example sets the switched zoned fabric domain ID for the storage router to 42:
[SN5428-2A]# fcswitch domainid 42*** Warning: Changing domain ID in an operational fabric will cause traffic disruptionDo you want to continue? [(yes/no (no)] yesThe following example sets the switched zoned fabric domain ID for the storage router to 5 and enables the lock, which prevents the domain ID from being changed by the zoned fabric.
[SN5428-2A]# fcswitch domainid 5*** Warning: Changing domain ID in an operational fabric will cause traffic disruptionDo you want to continue? [(yes/no (no)] yes[SN5428-2A]# fcswitch domainid lock enableRelated Commands
fcswitch dstov
To specify the amount of time the storage router is to wait for Fibre Channel (FC) Distributed Services, use the fcswitch dstov command.
fcswitch dstov {nn | default}
Syntax Description
nn
The Distributed Services timeout value, in milliseconds.
default
Keyword, indicating the storage router is to wait 5000 milliseconds for Fibre Channel Distributed Services.
Defaults
The default Distributed Services timeout value is 5000 milliseconds.
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
Use this command to specify the length of time the storage router should wait for FC Distributed Services, such as the Management Server or Name Server, before returning an error.
Use the default keyword to return the Distributed Services timeout value to 5000 milliseconds.
Examples
The following example sets the Distributed Services timeout value to 7500 milliseconds:
[SN5428-2A]# fcswitch dstov 7500The following example resets the Distributed Services timeout value to the default of 5000 milliseconds:
[SN5428-2A]# fcswitch dstov defaultRelated Commands
fcswitch edtov
To specify an error detect timeout value for all Fibre Channel (FC) interfaces, use the fcswitch edtov command.
fcswitch edtov {nn | default}
Syntax Description
nn
The amount of time a port is to wait for errors to clear, in milliseconds.
default
Keyword, indicating the port is to wait 2000 milliseconds for errors to clear.
Defaults
The default error detect timeout value is 2000 milliseconds.
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 error detect timeout value is the amount of time the FC port is to wait for all errors to clear. This value applies to all FC interfaces in the storage router.
Error detect timeout values should be the same for all storage routers or switches in the fabric.
Examples
The following example sets the error detect timeout value to 4000 milliseconds:
[SN5428-2A]# fcswitch edtov 4000The following example resets the error detect timeout value to the default of 2000 milliseconds:
[SN5428-2A]# fcswitch edtov defaultRelated Commands
fcswitch enable
To enable all Fibre Channel (FC) interfaces, use the fcswitch enable command. To disable all FC interfaces, use the no form of this command.
fcswitch enable
no fcswitch enable
Syntax Description
This command has no arguments or keywords.
Defaults
All FC interfaces are enabled, by default.
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 FC interface must be enabled to allow access to storage targets or perform online loopback testing. Use this command to enable all FC interfaces at one time.
If you experience problems with FC storage, use the no form of this command to quickly disable all FC interfaces at once.
Examples
The following example enables all FC interfaces and then performs an online loopback test for the FC interface named fc6:
[SN5428-2A]# fcswitch enable[SN5428-2A]# interface fc6 loopback onlineThe following example disables all FC interfaces.
[SN5428-2A]# no fcswitch enableRelated Commands
fcswitch fstov
To specify the fabric services timeout value, use the fcswitch fstov command.
fcswitch fstov {nn | default}
Syntax Description
nn
The amount of time the storage router is to wait for fabric services, in milliseconds.
default
Keyword, indicating the storage router will wait for 1000 milliseconds for fabric services.
Defaults
The default fabric stability timeout value is 1000 milliseconds.
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
Use this command to specify the number of milliseconds the storage router will wait for fabric services.
Examples
The following example sets the fabric services timeout value to 5000 milliseconds:
[SN5428-2A]# fcswitch fstov 5000The following example resets the fabric services timeout value to the default of 1000 milliseconds:
[SN5428-2A]# fcswitch fstov defaultRelated Commands
fcswitch interop-credit
To set the buffer-to-buffer credit value for all Fibre Channel (FC) ports, use the fcswitch interop-credit command.
fcswitch interop-credit credit
Syntax Description
credit
The data buffer credit capacity, also known as the buffer-to-buffer credit value. The credit variable is an integer between 0 and 255 inclusive. The default value is 12.
Defaults
The data buffer credit capacity is 12, by default.
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
Use this command to set the data buffer credit capacity for all the storage router FC ports. The port buffer credit is used to determine how many maximum sized frames can be sent to a recipient before the sending port must wait for an acknowledgement. When the acknowledgement is received, the sending port can continue by sending the next frame. Port buffer credits are required when buffer-to-buffer flow control is in use. Buffer-to-buffer flow control occurs between directly connected FC ports.
The data buffer credit capacity must be the same for all switches across the fabric, and should be set to the lowest system-wide setting.
Examples
The following example sets the data buffer credit capacity to 15:
[SN5428-2A]# fcswitch interop-credit 15Related Commands
fcswitch log interface
To restrict the storage router's integrated Fibre Channel (FC) switch logging to information related to a specific FC interface, use the fcswitch log interface command.
fcswitch log interface {if-name | default}
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
The fcswitch log interface command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Examples
The following example restricts logging for the integrated FC switch to information associated with fc3:
[SN5428-2A]# fcswitch log interface fc3Related Commands
fcswitch ratov
To specify a Fibre Channel (FC) resource allocation timeout value for the storage router, use the fcswitch ratov command.
fcswitch ratov {nn | default}
Syntax Description
Defaults
The default resource allocation timeout value is 10000 milliseconds.
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 resource allocation timeout value is the amount of time the storage router is to wait to allow two FC ports to allocate sufficient resources to establish a link.
Resource allocation timeout values should be the same for all storage routers or switches in the fabric.
Examples
The following example sets the resource allocation timeout value to 9000 milliseconds:
[SN5428-2A]# fcswitch ratov 9000The following example resets the resource allocation timeout value to the default of 10000 milliseconds:
[SN5428-2A]# fcswitch ratov defaultRelated Commands
fcswitch syslog
To specify the logging parameters for the storage router's integrated Fibre Channel (FC) switch component system log file, use the fcswitch syslog command.
fcswitch syslog components component1 [component2...]
fcswitch syslog level notification-level
Syntax Description
components component1 [component2...]
At least one of the components described in Table 6-3.
level notification-level
Limit logging to messages of a specified level or lower. See Table 6-4 in the Usage Guidelines section for a list of valid names that can be used for the notification-level argument.
Defaults
All components log information into the storage router's integrated FC switch component system log, by default. The default notification level is critical.
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
Use this command to limit the amount of information recorded in the switch system log by component and by notification level. To stop all logging for all components, set the notification level to none.
Examples
The following example limits the switch system log file to informational messages only for name server, management server, port and switch management events:
[SN5428-2A]# fcswitch syslog components NameServer MgmtServer Port Switch[SN5428-2A]# fcswitch syslog level infoThe following example stops all switch syslog logging:
[SN5428-2A]# fcswitch syslog level noneRelated Commands
fcswitch syslog enable
To start system logging for the storage router's integrated Fibre Channel (FC) switch component, use the fcswitch syslog enable command. To stop system logging, use the no form of this command.
fcswitch syslog enable
no fcswitch syslog enable
Syntax Description
This command has no arguments or keywords.
Defaults
System logging for the integrated FC switch component is started, by default.
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 fcswitch syslog enable command is designed for debug purposes, and should be used under the guidance of a Cisco Technical Support professional.
Examples
The following example stops system logging for the integrated FC switch component. When system logging is started, logging will continue based on the existing component and notification level settings.
[SN5428-2A]# no fcswitch syslog enableRelated Commands
fcswitch zoning autosave
To enable the storage router to automatically save zoning changes received from switches in the fabric, use the fcswitch zoning autosave command. To prevent the storage router from saving zoning changes, use the no form of this command.
fcswitch zoning autosave enable
no fcswitch zoning autosave enable
Syntax Description
autosave enable
Enables the storage router to save zoning changes received from switches in the fabric to non-volatile memory. This is the default.
Defaults
The storage router saves zoning changes by default.
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
By default, the storage router can merge into existing FC switched fabric zones and participate in the zoning. Use the no form of this command, in conjunction with the fcswitch domainid command with the lock keyword to prevent the storage router from participating in FC switched fabric zones.
Examples
The following example prevents the storage router from participating in FC switched fabric zones. The first command prevents the storage router from saving zoning changes received from switches in the fabric, and the second command locks the domain ID, preventing the FC switched fabric from making changes to that value.
[SN5428-2A]# no fcswitch zoning autosave enable[SN5428-2A]# fcswitch domainid lock enableRelated Commands
fcswitch zoning default
To select the level of communication between the storage router and devices in the fabric when there is no active zone set, use the fcswitch zoning default command.
fcswitch zoning default {all | none}
Syntax Description
Defaults
If there is no active zone set, the storage router can communicate with all switches and other devices in the fabric, by default.
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
By default, the storage router can merge into existing FC switched fabric zones and participate in the zoning. Use this command to isolate the storage router and prevent communication with any switch or other device in the fabric, if there is no active zone set.
Before changing the default behavior, disconnect any ISL links to other fabric entities to prevent unintended disruption of fabric traffic.
Examples
The following example prevents the storage router from communicating with switches and all other devices in the fabric, if there is no active zone set:
[SN5428-2A]# fcswitch zoning default noneRelated Commands
fcswitch zoning merge
To set zoning merge compliance, use the fcswitch zoning merge command.
fcswitch zoning merge sw2
Syntax Description
sw2
Indicates the fabric includes only FC-SW-2 compliant switches. A merge may only occur of active zoning information, ensuring all switches have identical active zone sets. This is the default.
Defaults
The storage router is FC-SW-2 compliant, and is configured to participate in a fabric with only FC-SW-2 compliant switches by default.
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
By default, the storage router can merge into existing FC switched fabric zones and participate in the zoning. All switches in a fabric should be set to the same merge mode to prevent switches from becoming isolated from each other. By default, the storage router supports the FC-SW-2 compliant merge mode.
Examples
The following example sets the merge mode for participation in a fabric with FC-SW-2 compliant switches:
[SN5428-2A]# fcswitch zoning merge sw2Related Commands
