-
Cisco MDS 9000 Family Command Reference, Release 3.x
-
New and Changed Information
-
Preface
-
CLI Overview
-
A Commands
-
Advanced Services Modules Commands
-
B Commands
-
C Commands
-
Caching Services Module Commands
-
D Commands
-
Debug Commands
-
E Commands
-
F Commands
-
G Commands
-
H Commands
-
I Commands
-
J Commands
-
K Commands
-
L Commands
-
M Commands
-
N Commands
-
O Commands
-
P Commands
-
Q Commands
-
R Commands
-
S Commands
-
Show Commands
-
T Commands
-
U Commands
-
V Commands
-
W Commands
-
Z Commands
-
Feedback
Table Of Contents
interface sme (Cisco SME cluster node configuration submode)
ip address (FCIP profile configuration submode)
ip address (interface configuration)
iscsi interface vsan-membership
ivr copy active-service-group user-configured-service-group
ivr copy active-topology user-configured-topology
ivr copy active-zoneset full-zoneset
ivr copy auto-topology user-configured-topology
ivr fcdomain database autonomous-fabric-num
I Commands
The commands in this chapter apply to the Cisco MDS 9000 Family of multilayer directors and fabric switches. All commands are shown here in alphabetical order regardless of command mode. See "About the CLI Command Modes" section on page 1-3 to determine the appropriate mode for each command. For more information, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
identity
To configure the identity for the IKE protocol, use the identity command in IKE configuration submode. To delete the identity, use the no form of the command.
identity {address | hostname}
no identity {address | hostname}
Syntax Description
address
Sets the IKE identity to be the IPv4 address of the switch.
hostname
Sets the IKE identity to be the host name of the switch.
Defaults
None.
Command Modes
IKE configuration submode.
Command History
Usage Guidelines
To use this command, the IKE protocol must be enabled using the crypto ike enable command.
Before configuring a certificate for the switch, configure the host name and domain name, and set the identity to be the host name. This allows the certificate to be used for authentication.
Note
The host name is the fully qualified domain name (FQDN) of the switch. To use the switch FQDN for the IKE identity, you must first configure both the switch name and the domain name. The FQDN is required for using RSA signatures for authentication.
Examples
The following example shows how to set the IKE identity to the IP address of the switch:
switch# config terminalswitch(config)# crypto ike domain ipsecswitch(config-ike-ipsec)# identity address 10.10.100.231The following example shows how to delete the IKE identity.
switch(config-ike-ipsec)# no identity 10.10.100.231The following example shows how to set the IKE identity to the host name.
switch(config-ike-ipsec)# identity hostname node1The following example shows how to delete the IKE identity.
switch(config-ike-ipsec)# no identity hostname node1Related Commands
crypto ike domain ipsec
Enters IKE configuration mode.
crypto ike enable
Enables the IKE protocol.
show crypto ike domain ipsec
Displays IKE information for the IPsec domain.
in-order-guarantee
To enable in-order delivery, use the in-order-guarantee command in configuration mode. To disable in-order delivery, use the no form of the command.
in-order-guarantee [vsan vsan-id]
no in-order-guarantee [vsan vsan-id]
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
In-order delivery of data frames guarantees frame delivery to a destination in the same order that they were sent by the originator.
Examples
The following example shows how to enable in-order delivery for the entire switch:
switch# config terminalswitch(config) # in-order-guaranteeThe following example shows how to disable in-order delivery for the entire switch.
switch(config)# no in-order-guaranteeThe following example shows how to enable in-order delivery for a specific VSAN.
switch(config)# in-order-guarantee vsan 3452The following example shows how to disable in-order delivery for a specific VSAN.
switch(config)# no in-order-guarantee vsan 101Related Commands
initiator
To configure the initiator version and address, use the initiator command IKE configuration submode. To revert to the default, use the no form of the command.
initiator version version address ip-address
no initiator version version address ip-address
Syntax Description
version
Specifies the protocol version number. The only valid value is 1.
address ip-address
Specifies the IP address for the IKE peer. The format is A.B.C.D.
Defaults
IKE version 2.
Command Modes
IKE configuration submode.
Command History
Usage Guidelines
To use this command, the IKE protocol must be enabled using the crypto ike enable command.
Examples
The following example shows how initiator information for the IKE protocol:
switch# config terminalswitch(config)# crypto ike domain ipsecswitch(config-ike-ipsec)# initiator version 1 address 10.1.1.1Related Commands
crypto ike domain ipsec
Enters IKE configuration mode.
crypto ike enable
Enables the IKE protocol.
show crypto ike domain ipsec
Displays IKE information for the IPsec domain.
install all
To upgrade all modules in any Cisco MDS 9000 family switch, use the install all command. This upgrade can happen nondisruptively or disruptively depending on the current configuration of your switch.
install all [{asm-sfn | kickstart | ssi | system} URL]
Syntax Description
asm-sfn filename
Upgrades the ASM image.
system
Upgrades the system image.
ssi
Upgrades the SSI image.
kickstart
Upgrades the kickstart image.
URL
The location URL of the source file to be installed.
The following table lists the aliases for URL.
Defaults
None.
Command Modes
EXEC mode.
Command History
1.0(3)
This command was introduced.
1.2(2)
Added the asm-sfn keyword and made all keywords optional.
2.0(1b)
Added the ssi keyword.
Usage Guidelines
The install all command upgrades all modules in any Cisco MDS 9000 Family switch.
Tip
To copy a remote file, specify the entire remote path exactly as it is.
Caution
See the Cisco MDS 9000 Family CLI Configuration Guide for detailed procedures.
Examples
The following example displays the result of the install all command if the system and kickstart files are specified locally.
switch# install all sys bootflash:isan-1.3.1 kickstart bootflash:boot-1.3.1Verifying image bootflash:/boot-1.3.1[####################] 100% -- SUCCESSVerifying image bootflash:/isan-1.3.1[####################] 100% -- SUCCESSExtracting "slc" version from image bootflash:/isan-1.3.1.[####################] 100% -- SUCCESSExtracting "ips" version from image bootflash:/isan-1.3.1.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/isan-1.3.1.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/boot-1.3.1.[####################] 100% -- SUCCESSExtracting "loader" version from image bootflash:/boot-1.3.1.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes disruptive rolling Hitless upgrade is not supported4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive resetImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- -------------------- -------------------- ------------1 slc 1.3(2a) 1.3(1) yes1 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no2 ips 1.3(2a) 1.3(1) yes2 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no3 ips 1.3(2a) 1.3(1) yes3 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no4 slc 1.3(2a) 1.3(1) yes4 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no5 system 1.3(2a) 1.3(1) yes5 kickstart 1.3(2a) 1.3(1) yes5 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no5 loader 1.2(2) 1.2(2) no6 system 1.3(2a) 1.3(1) yes6 kickstart 1.3(2a) 1.3(1) yes6 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no6 loader 1.2(2) 1.2(2) noDo you want to continue with the installation (y/n)? [n] yInstall is in progress, please wait.Syncing image bootflash:/boot-1.3.1 to standby.[####################] 100% -- SUCCESSSyncing image bootflash:/isan-1.3.1 to standby.[####################] 100% -- SUCCESSJan 18 23:40:03 Hacienda %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console fromPerforming configuration copy.[####################] 100% -- SUCCESSModule 6: Waiting for module online.|Auto booting bootflash:/boot-1.3.1 bootflash:/isan-1.3.1...Booting kickstart image: bootflash:/boot-1.3.1.........................................Image verification OKStarting kernel...INIT: version 2.78 bootingChecking all filesystems..r.r.. done.Loading system softwareUncompressing system image: bootflash:/isan-1.3.1CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCINIT: Entering runlevel: 3The following example displays the file output continuation of the install all command on the console of the standby supervisor module.Hacienda(standby)#Auto booting bootflash:/boot-1.3.1 bootflash:/isan-1.3.1...Booting kickstart image: bootflash:/boot-1.3.1.........................................Image verification OKStarting kernel...INIT: version 2.78 bootingChecking all filesystems..r.r.. done.Loading system softwareUncompressing system image: bootflash:/isan-1.3.1CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCINIT: Entering runlevel: 3Continue on installation process, please wait.The login will be disabled until the installation is completed.Module 6: Waiting for module online.Jan 18 23:43:02 Hacienda %PORT-5-IF_UP: Interface mgmt0 is upJan 18 23:43:19 Hacienda %LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature FM_SERVER_PKG. Application(s) shutdown in 53 days.Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature ENTERPRISE_PKG. Application(s) shutdown in 50 days.Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature SAN_EXTN_OVER_IP. Application(s) shutdown in 50 days.Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LICAPP_NO_LIC: Application port-security running without ENTERPRISE_PKG license, shutdown in 50 daysJan 18 23:43:19 Hacienda %LICMGR-4-LOG_LICAPP_EXPIRY_WARNING: Application Roles evaluation license ENTERPRISE_PKG expiry in 50 daysJan 18 23:44:54 Hacienda %BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by neighbor, starting...Module 1: Non-disruptive upgrading.[# ] 0%Jan 18 23:44:56 Hacienda %MODULE-5-STANDBY_SUP_OK: Supervisor 5 is standbyJan 18 23:44:55 Hacienda %IMAGE_DNLD-SLOT1-2-IMG_DNLD_STARTED: Module image download process. Please wait until completion...Jan 18 23:45:12 Hacienda %IMAGE_DNLD-SLOT1-2-IMG_DNLD_COMPLETE: Module image download process. Download successful.Jan 18 23:45:48 Hacienda %MODULE-5-MOD_OK: Module 1 is online[####################] 100% -- SUCCESSModule 4: Non-disruptive upgrading.[# ] 0%Jan 18 23:46:12 Hacienda %IMAGE_DNLD-SLOT4-2-IMG_DNLD_STARTED: Module image download process. Please wait until completion...Jan 18 23:46:26 Hacienda %IMAGE_DNLD-SLOT4-2-IMG_DNLD_COMPLETE: Module image download process. Download successful.Jan 18 23:47:02 Hacienda %MODULE-5-MOD_OK: Module 4 is online[####################] 100% -- SUCCESSModule 2: Disruptive upgrading....-- SUCCESSModule 3: Disruptive upgrading....-- SUCCESSInstall has been successful.MDS SwitchHacienda login:The following example displays the result of the install all command if the system and kickstart files are specified remotely.
switch# install all system scp://user@171.69.16.26/tftpboot/HKrel/qa/vegas/final/m9500-sf1ek9-mz.1.3.2a.bin kickstart scp://user@171.69.16.26/tftpboot/HKrel/qa/vegas/final/m9500-sf1ek9-kickstart-mz.1.3.2a.b inFor scp://user@171.69.16.26, please enter password:For scp://user@171.69.16.26, please enter password:Copying image from scp://user@171.69.16.26/tftpboot/HKrel/qa/vegas/final/m9500-sf1ek9-kickstart-mz.1.3.2a.bin to bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin.[####################] 100% -- SUCCESSCopying image from scp://user@171.69.16.26/tftpboot/HKrel/qa/vegas/final/m9500-sf1ek9-mz.1.3.2a.bin to bootflash:///m9500-sf1ek9-mz.1.3.2a.bin.[####################] 100% -- SUCCESSVerifying image bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin[####################] 100% -- SUCCESSVerifying image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin[####################] 100% -- SUCCESSExtracting "slc" version from image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin.[####################] 100% -- SUCCESSExtracting "ips" version from image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin.[####################] 100% -- SUCCESSExtracting "loader" version from image bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------1 yes non-disruptive rolling2 yes disruptive rolling Hitless upgrade is not supported3 yes non-disruptive rolling4 yes non-disruptive rolling5 yes non-disruptive reset6 yes non-disruptive reset7 yes non-disruptive rolling8 yes non-disruptive rolling9 yes disruptive rolling Hitless upgrade is not supportedImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- -------------------- -------------------- ------------1 slc 1.3(1) 1.3(2a) yes1 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no2 ips 1.3(1) 1.3(2a) yes2 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no3 slc 1.3(1) 1.3(2a) yes3 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no4 slc 1.3(1) 1.3(2a) yes4 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no5 system 1.3(1) 1.3(2a) yes5 kickstart 1.3(1) 1.3(2a) yes5 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no5 loader 1.2(2) 1.2(2) no6 system 1.3(1) 1.3(2a) yes6 kickstart 1.3(1) 1.3(2a) yes6 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no6 loader 1.2(2) 1.2(2) no7 slc 1.3(1) 1.3(2a) yes7 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no8 slc 1.3(1) 1.3(2a) yes8 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no9 ips 1.3(1) 1.3(2a) yes9 bios v1.1.0(10/24/03) v1.0.8(08/07/03) noDo you want to continue with the installation (y/n)? [n]Related Commands
install clock-module
To upgrade the EPLD images of the clock module on a Cisco MDS 9513 Switch Director, use the install clock-module command.
install clock-module [epld {bootflash: | slot0: | volatile:}]
Syntax Description
epld
Installs the clock module EPLD from the EPLD Image.
bootflash:
Local URI containing EPLD Image.
slot0:
Local URI containing EPLD Image.
volatile:
Local URI containing EPLD Image.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
Use this command on the active supervisor to install the standby clock module EPLD from the specified EPLD image. After upgrading the clock module, power cycle the entire chassis for the change to take effect. It is not sufficient to reboot the chassis; you must turn the power off and on.
Note
Examples
The following example upgrades the EPLD images for the clock module:
switch# install clock-module epld bootflash:m9000-epld-3.0.0.278.imgLen 3031343, CS 0x58, string MDS series EPLD image, built on Fri Nov 11 01:11:09 2005EPLD Curr Ver New Ver-------------------------------------------------------Clock Controller 0x03 0x04There are some newer versions of EPLDs in the image!Do you want to continue (y/n) ? yProceeding to program Clock Module B.Do you want to switchover Clock Modules after programming Clock Module B.System Will Reset! y/n) ?n|
Clock Module B EPLD upgrade is successful.Related Commands
show version clock-module epld
Displays the current EPLD versions on the clock module.
install license
To program the supervisor or switching module BIOS, use the install license command.
install license [bootflash: | slot0: | volatile:] file-name
Syntax Description
bootflash:
Source location for the license file.
slot0:
Source location for the license file.
volatile:
Source location for the license file.
file-name
The name of the license file.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
If a target file name is provided after the source URL, the license file is installed with that name. Otherwise, the filename in the source URL is used. This command also verifies the license file before installing it.
Examples
The following example installs a file named license-file which resides in the bootflash: directory..
switch# install license bootflash:license-fileRelated Commands
install module bios
To program the supervisor or switching module BIOS, use the install module bios command.
install module module-number bios {system [bootflash: | slot0: | volatile: | system-image]}
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
If the BIOS is upgraded, you need to reboot to make the new BIOS effective. You can schedule the reboot at a convenient time so traffic will not be impacted.
The console baud rate automatically reverts to the default rate (9600) after any BIOS upgrade.
The URL is always the system image URL in the supervisor module, and points to the bootflash: or slot0: directories.
Examples
The following example shows how to perform a nondisruptive upgrade for the system:
switch# install module 1 biosStarted bios programming .... please wait###BIOS upgrade succeeded for module 1In this example, the switching module in slot 1 was updated.
install module epld
To upgrade the electrically programmable logical devices (EPLDs) module, use the install module epld command. This command is only for supervisor modules, not switching modules.
install module module-number epld [bootflash: | ftp: | scp: | sftp: | tftp: | volatile:]
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
Issue this command from the active supervisor module to update any other module.
If you forcefully upgrade a module that is not online, all EPLDs are forcefully upgraded. If the module is not present in the switch, an error is returned. If the module is present, the command process continues.
Do not insert or extract any modules while an EPLD upgrade or downgrade is in progress.
Examples
The following example upgrades the EPLDs for the module in slot 2.
switch# install module 2 epld scp://user@10.6.16.22/users/dino/epld.imgThe authenticity of host '10.6.16.22' can't be established.RSA1 key fingerprint is 55:2e:1f:0b:18:76:24:02:c2:3b:62:dc:9b:6b:7f:b7.Are you sure you want to continue connecting (yes/no)? yesWarning: Permanently added '10.6.16.22' (RSA1) to the list of known hosts.user@10.6.16.22's password:epld.img 100% |*****************************| 1269 KB 00:00Module Number 2EPLD Curr Ver New Ver----------------------------------------------------Power Manager 0x06XBUS IO 0x07 0x08UD chip Fix 0x05Sahara 0x05 0x05Module 2 will be powered down now!!Do you want to continue (y/n) ? y\ <------------------------------------------------------------progress twirlModule 2 EPLD upgrade is successfulThe following example forcefully upgrades the EPLDs for the module in slot 2.
switch# install module 2 epld scp://user@10.6.16.22/epld-img-file-pathModule 2 is not online, Do you want to continue (y/n) ? ycchetty@171.69.16.22's password:epld.img 100% |*****************************| 1269 KB 00:00\ <------------------------------------------------------------progress twirlModule 2 EPLD upgrade is successfulRelated Commands
show version module number epld
Displays the current EPLD versions.
show version epld
Displays the available EPLD versions.
install module loader
To upgrade the bootloader on either the active or standby supervisor module, use the install module loader command. This command is only for supervisor modules, not switching modules.
install module module-number loader kickstart [bootflash: | slot0: | volatile: | kickstart-image]
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
Before issuing the install module loader command, be sure to read the release notes to verify compatibility issues between the boot loader and the kickstart or system images.
If you install a loader version that is the same as the currently-installed version, the loader will not be upgraded. When both the current version and the installed version are the same, use the init system command to force a loader upgrade.
Examples
The following example shows how to perform a non disruptive upgrade for the system:
switch# install module 6 loader bootflash:kickstart_imageThis example displays the command being issued on the standby supervisor module in slot 6.
Related Commands
install ssi
To perform a nondisruptive upgrade of the SSI image on an SSM, use the install ssi command.
install ssi {bootflash: | slot0: | modflash:} file-name module slot
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
You can use the install ssi command to upgrade or downgrade the SSI boot image if the SSM is only configured for Fibre Channel switching. If your SSM is configured for VSFN or Intelligent Storage Services, you must use the boot command to reconfigure the SSI boot variable and reload the module.
The install ssi command implicitly sets the SSI boot variable.
Note
Note
Examples
The following example installs the SSI boot image on the module in slot 2.
switch# install ssi bootflash:lm9000-ek9-ssi-mz.2.1.2.bin module 2Related Commands
show boot
Displays the current contents of boot variables.
show module
Verifies the status of a module.
boot
Configures the boot variables.
interface
To configure an interface on the Cisco MDS 9000 Family of switches, use the interface command in configuration mode.
interface {cpp | fc | fc-tunnel | fcip | gigabitethernet | iscsi | mgmt | port-channel | svc | vsan}
Note
interface {bay port | ext port}Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interface fc1/1 - 5 , fc2/5 - 7
The spaces are required before and after the dash ( - ) and before and after the comma ( , ).
Examples
The following example selects the mgmt 0 interface and enters interface configuration submode.
switch# config terminalswitch(config)# interface mgmt 0Related Commands
interface bay | ext
To configure a Fibre Channel interface on a Cisco Fabric Switch for HP c-Class BladeSystem and on a Cisco Fabric Switch for IBM BladeCenter, use the interface bay or interface ext command in configuration mode.
interface {bay port | ext port}
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example configures Fibre Channel interface bay2 and enters interface configuration submode.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# int bay 2switch(config-if)#Related Commands
interface fc
To configure a Fibre Channel interface on the Cisco MDS 9000 Family of switches, use the interface fc command in EXEC mode. To revert to defaults, use the no form of the command.
interface fc slot/port
channel-group {group-id [force] | auto}
fcdomain rcf-reject vsan vsan-id
fspf {cost link-cost vsan vsan-id | ficon portnumber portnumber | dead-interval seconds vsan vsan-id | hello-interval seconds vsan vsan-id | passive vsan vsan-id | retransmit-interval seconds vsan vsan-id}interface fc slot/port
no channel-group {group-id [force] | auto}
no fcdomain rcf-reject vsan vsan-id
no fspf {cost link_cost vsan vsan-id | ficon portnumber portnumber | dead-interval seconds vsan vsan-id | hello-interval seconds vsan vsan-id | passive vsan vsan-id | retransmit-interval seconds vsan vsan-id}Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
1.0(2)
This command was introduced.
2.0(x)
Added the auto option to the channel-group keyword.
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interfacespacefc1/1space-space5space,spacefc2/5space-space7
Refer to the Cisco MDS 9000 Family CLI Configuration Guide for information on port number allocation.
Use the no shutdown command to enable the interface.
The channel-group auto command enables autocreation of port channels. If autocreation of port channels is enabled for an interface, you must first disable this configuration before downgrading to earlier software versions or before configuring the interface in a manually configured channel group.
Examples
The following example configures ports 1 to 4 in Fibre Channel interface 9.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# int fc9/1 - 4The following example enables the Fibre Channel interface.
switch# config terminalswitch(config)# interface fc1/1switch(config-if)# no shutdownThe following example assigns the FICON port number to the selected Fibre Channel interface.
switch# config terminalswitch(config)# interface fc1/1switch(config-if)# ficon portnumber 15Related Commands
show interface
Displays an interface configuration for a specified interface.
shutdown
Disables and enables an interface.
interface fc-tunnel
To configure a Fibre Channel tunnel and facilitate RSPAN traffic, use the interface fc-tunnel command. To remove a configured tunnel or revert to factory defaults, use the no form of the command.
interface fc-tunnel number
destination ip-address
explicit-path path-name
source ip-address]no interface fc-tunnel number
no destination ip-address |
no explicit-path path-name
no source ip-addressno interface fc-tunnel number
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example initiates the FC tunnel (100) in the source switch (switch S).
switch(config)# config terminalswitch(config)# interface fc-tunnel 100switch(config-if)#The following example maps the IP address of the source switch (switch S) to the FC tunnel (100).
switchS(config-if)# source 10.10.10.1The following example maps the IP address of the destination switch (switch D) to the FC tunnel (100).
switch(config-if)# destination 10.10.10.2The following example enables traffic flow through this interface.
switch(config-if)# no shutdownThe following example references the configured path in the source switch (switch S).
switch# config tswitch(config)# interface fc-tunnel 100switch(config)# explicit-path Path1Related Commands
show interface fc-tunnel
Displays an FC tunnel interface configuration for a specified interface.
fc-tunnel explicit-path
Configures a new or existing next-hop path.
interface fcip
To configure a Fibre Channel over IP Protocol (FCIP) interface, use the interface fcip command. To disable a FCIP interface, use the no form of the command.
interface fcip interface_number
bport
bport-keepalives
channel-group number [force]
fcdomain rcf-reject vsan vsan-id
ficon portnumber portnumber |
fspf {cost link-cost | dead-interval seconds | hello-interval seconds | passive | retransmit-interval seconds} vsan vsan-id
passive-mode
peer-info ipaddr ip-address [port number]
qos control control-value data data-value
special-frame peer-wwn pwwn-id
tcp-connections number
time-stamp [acceptable-diff number]
use-profile profile-idinterface fcip interface_number
no bport
no bport-keepalives
no channel-group number [force]
no fcdomain rcf-reject vsan vsan-id
no ficon portnumber portnumber
no fspf {cost link-cost | dead-interval seconds | hello-interval seconds | passive | retransmit-interval seconds} vsan vsan-id
no qos control-value data data-value
no passive-mode
no peer-info ipaddr ip-address [port number]
no special-frame peer-wwn pwwn-id
no tcp-connections number
no time-stamp [acceptable-diff number]
no use-profile profile-idSyntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
1.1(1)
This command was introduced.
1.3(1)
Added the ficon portnumber subcommand.
2.0(x)
Added the qos subcommand.
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interface fcip1space-space5space,spacefcip10space-space12space
Refer to the Cisco MDS 9000 Family CLI Configuration Guide for information on port number allocation.
Examples
The following example selects an FCIP interface and enters interface configuration submode.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# interface fcip 1switch(config-if)#The following example assigns the FICON port number to the selected FCIP interface.
switch# config terminalswitch(config)# interface fcip 51switch(config-if)# ficon portnumber 234Related Commands
show interface fcip
Displays an interface configuration for a specified FCIP interface.
interface gigabitethernet
To configure an Gigabit Ethernet interface, use the interface gigabitethernet command. To revert to the default values, use the no form of the command.
interface gigabitethernet slot/port
cdp enable
channel-group group-id [force]
isns profile-nameinterface gigabitethernet slot/port
no cdp enable
no channel-group
no isns profile-nameSyntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
1.0(3a)
This command was introduced.
1.1(1a)
Added the channel-group subcommand.
1.3(1)
Added the isns subcommand.
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interface gigabitethernet1/1space-space2space,spacegigabitethernet3/1space-space2
Examples
The following example configures the Gigabit Ethernet interface at slot 4 port 1.
switch# config terminalswitch(config)# interface gigabitethernet 4/1switch(config-if)#The following example enters a IP address and subnet mask for the selected Gigabit Ethernet interface.
switch(config-if)# ip address 10.1.1.100 255.255.255.0The following example changes the IP maximum transmission unit (MTU) value for the selected Gigabit Ethernet interface.
switch(config-if)# switchport mtu 3000The following example creates a VR ID for the selected Gigabit Ethernet interface, configures the virtual IP address for the VR ID (VRRP group), and assigns a priority.
switch(config-if)# vrrp 100switch(config-if-vrrp)# address 10.1.1.100switch(config-if-vrrp)# priority 10The following example adds the selected Gigabit Ethernet interface to a channel group. If the channel group does not exist, it is created, and the port is shut down.
switch(config-if)# channel-group 10gigabitethernet 4/1 added to port-channel 10 and disabledplease do the same operation on the switch at the other end of the port-channel, then do "no shutdown" at both ends to bring them upRelated Commands
interface iscsi
To configure an iSCSI interface, use the interface iscsi command. To revert to default values, use the no form of the command.
interface iscsi slot/port
mode {pass-thru | store-and-forward}
tcp qos valueinterface iscsi slot/port
no mode {pass-thru | store-and-forward | cut-thru}
no tcp qos valueno interface iscsi slot/port
Syntax Description
Defaults
Disabled.
The TCP QoS default is 0.
The forwarding mode default is store-and-forward.
Command Modes
Configuration mode.
Command History
1.3(1)
This command was introduced.
2.1(1)
Added the cut-thru option for the mode subcommand.
Usage Guidelines
To configure iSCSI interface, enable iSCSI using the iscsi enable command.
You can specify a range of interfaces by issuing a command with the following example format:
interface iscsi space fc1/1space-space5space,spacefc2/5space-space7Examples
The following example enables the iSCSI feature.
switch# config tswitch(config)# iscsi enableThe following example enables the store-and-forward mode for iSCSI interfaces 9/1 to 9/4.
switch(config)# interface iscsi 9/1 - 4switch(config-if)# mode store-and-forwardThe following example reverts to using the default pass-thru mode for iSCSI interface 9/1.
switch(config)# interface iscsi 9/1switch(config-if)# mode pass-thruRelated Commands
iscsi enable
Enables iSCSI.
show interface
Displays an interface configuration for a specified interface.
interface mgmt
To configure a management interface, use the interface mgmt command in configuration mode.
interface mgmt number
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
When you try to shutdown a management interface(mgmt0), a follow-up message confirms your action before performing the operation. Use the force option to bypass this confirmation, if required.
Examples
The following example configures the management interface, displays the options available for the configured interface, and exits to configuration mode.
switch# config terminalswitch(config)#switch(config)# interface mgmt 0switch(config-if)# exitswitch(config)#The following example shuts down the interface without using the force option:
switch# config terminalswitch(config)# interface mgmt 0switch(config-if)# shutdownShutting down this interface will drop all telnet sessions.Do you wish to continue (y/n)? yThe following example shuts down the interface using the force option:
switch# config terminalswitch(config)# interface mgmt 0switch(config-if)# shutdown forceswitch(config-if)#Related Commands
interface port-channel
To configure a PortChannel interface on the Cisco MDS 9000 Family of switches, use the interface port-channel command.
interface port-channel number
channel mode active
fcdomain rcf-reject vsan vsan-id
fspf [cost link_cost | dead-interval seconds | ficon portnumber portnumber | hello-interval seconds | isns profile-name | passive | retransmit-interval seconds]interface port-channel number
no channel mode active
no fcdomain rcf-reject vsan vsan-id
no fspf [cost link_cost | dead-interval seconds | ficon portnumber portnumber | hello-interval seconds | isns profile-name | passive | retransmit-interval seconds]no interface port-channel number
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
1.0(2)
This command was introduced.
1.3(1)
Added channel mode active subcommand.
Usage Guidelines
Refer to the Cisco MDS 9000 Family CLI Configuration Guide for information on port number allocation.
Examples
The following example enters configuration mode and configures a PortChannel interface.
switch# config terminalswitch(config)# interface port-channel 32switch(config-if)#The following example assigns the FICON port number to the selected PortChannel port.
switch# config terminalswitch(config)# interface Port-channel 1switch(config-if)# ficon portnumber 234Related Commands
interface sme
To configure the Cisco SME interface on a switch, use the interface sme command. To remove the interface, use the no form of the command,
interface sme slot /port
no interface sme slot /port
Syntax Description
slot
Identifies the number of the MPS-18/4 module slot.
port
Identifies the number of the Cisco SME port.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, clustering must be enabled using the cluster enable command and Cisco SME services must be activated using the sme enable command.
Once you have configured the interface, use the no shutdown command to enable the interface.
To delete the Cisco SME interface, you must first remove the switch from the cluster. Use the no sme cluster command to remove the switch from the cluster and then use the no interface command to delete the interface.
The interface commands are available in the (config-if) submode.
Examples
The following example configures and enables the Cisco SME interface on the MPS-18/4 module slot and the default Cisco SME port:
switch# config terminalswitch(config)# interface sme 3/1switch(config-if)# no shutdownRelated Commands
shutdown
Enables or disables an interface.
show interface sme
Displays interface information.
interface sme (Cisco SME cluster node configuration submode)
To add Cisco SME interface from a local or a remote switch to a cluster, use the interface sme command. To delete the interface, use the no form of the command.
interface sme (slot/port) [force]
no interface sme (slot/port) [force]
Syntax Description
slot
Identifies the MPS-18/4 module slot.
port
Identifies the Cisco SME port.
force
Forcibly clears the previous interface context in the interface.
Defaults
Disabled.
Command Modes
Cisco SME cluster node configuration submode.
Command History
Usage Guidelines
You have to first configure a node using the fabric-membership command before this command can be executed.
To use this command, clustering must be enabled using the cluster enable command and Cisco SME services must be activated using the sme enable command.
To delete the Cisco SME interface, first remove the switch from the cluster. Use the no sme cluster command to remove the switch from the cluster and then use the no interface command to delete the interface.
Examples
The following example specifies the fabric to which the node belongs and then adds the Cisco SME interface (4/1) from a local switch using the force option:
switch# config tswitch(config)# sme cluster clustername1switch(config-sme-cl)# node localswitch(config-sme-cl-node)# fabric-membership f1switch(config-sme-cl-node)# interface sme 4/1 fabric sw-xyzThe following example specifies the fabric to which the node belongs and then adds the Cisco SME interface (4/1) from a remote switch using the force option:
switch# config tswitch(config)# sme cluster clustername1switch(config-sme-cl)# node 171.71.23.33switch(config-sme-cl-node)# fabric-membership f1switch(config-sme-cl-node)# interface sme 4/1 fabric sw-xyzRelated Commands
fabric-membership
Adds the node to a fabric.
show interface
Displays Cisco SME interface details
interface vsan
To configure a VSAN interface, use the interface vsan command. To remove a VSAN interface, use the no form of the command.
interface vsan vsan-id
no interface vsan vsan-id
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example selects a VSAN interface and enters interface configuration submode.
switch# config terminalswitch(config)# interface vsan 1switch(config-if)#Related Commands
ip access-group
To apply an access list to an interface, use the ip access-group command in interface mode. Use the no form of this command to negate a previously issued command or revert to factory defaults.
ip access-group access-list-name [in | out]
Syntax Description
Defaults
The access list is applied to both ingress and egress traffic.
Command Modes
Interface mode.
Command History
Usage Guidelines
The ip access-group command controls access to an interface. Each interface can only be associated with one access list. The access group becomes active immediately.
We recommend creating all rules in an access list, before creating the access group that uses that access list.
If you create an access group before an access list, the access list is created and all packets in that interface are dropped, because the access list is empty.
The access-group configuration for the ingress traffic applies to both local and remote traffic. The access-group configuration for the egress traffic applies only to local traffic. You can apply a different access list for each type of traffic.
Examples
The following example creates an access group called aclPermit for both the ingress and egress traffic (default)
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclPermit permit ip any anyswitch(config)# interface Gigabitethernet 3/1switch(config-if)# ip access-group aclPermitThe following example deletes the access group called aclPermit.
switch(config-if)# no ip access-group aclPermitThe following example creates an access group called aclDenyTcp (if it does not already exist) for ingress traffic.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclDenyTcp deny tcp any anyswitch(config)# interface gigabitethernet 3/1switch(config-if)# ip access-group aclDenyTcp inThe following example deletes the access group called aclDenyTcp for ingress traffic.
switch(config-if)# no ip access-group aclDenyTcp inThe following example creates an access list called aclPermitUdp (if it does not already exist) for local egress traffic.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclPermitUdp permit udp 192.168.32.0 0.0.7.255 anyswitch(config)# interface gigabitethernet 3/1switch(config-if)# ip access-group aclPermitUdp outThe following example removes the access list called aclPermitUdp for local egress traffic.
switch(config-if)# no ip access-group aclPermitUdp outRelated Commands
ip access-list
Configures IP access control lists.
show ip access-list
Displays the IP-ACL configuration information.
ip access-list
To configure IP access control lists (ACLs), use the ip access-list command in configuration mode. To negate a previously issued command or revert to factory defaults, use the no form of the command.
ip access-list list-name {deny | permit} ip-protocol
{src-addr src-wildcard}
{dest-addr dest-wildcard | operator port-value}
[operator port port-value]
[established | icmp-type icmp-value]
[tos tos-value]
[log-deny]Syntax Description
Defaults
Denied.
Command Modes
Configuration mode.
Command History
3.4(1)
Added a note information for the usage section.
1.2(1)
This command was introduced.
Usage Guidelines
Using the log-deny option at the end of the individual ACL entries shows the ACL number and whether the packet was permitted or denied, in addition to port-specific information. This option causes an information logging message about the packet that matches the dropped entry (or entries).
Note
Examples
The following example configures the an IP-ACL called aclPermit and permits IP traffic from any source address to any destination address.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclPermit permit ip any anyThe following example removes the IP-ACL called aclPermit.
switch(config-if)# no ip access-group aclPermitThe following example updates aclPermit to deny TCP traffic from any source address to any destination address.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclPermit deny tcp any anyThe following example defines an IP-ACL that permits this network. Subtracting 255.255.248.0 (normal mask) from 255.255.255.255 yields 0.0.7.255.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclPermitUdp permit udp 192.168.32.0 0.0.7.255 anyThe following example permits all IP traffic from and to the specified networks.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ip access-list aclPermitIpToServer permit ip 10.1.1.0 0.0.0.255 172.16.1.0 0.0.0.255The following example denies TCP traffic from 1.2.3.0 through source port 5 to any destination.
switch# config terminalEnter configuration commands, one per line. End with CNTL/switch(config)# ip access-list aclDenyTcpIpPrt5 deny tcp 1.2.3.0 0.0.0.255 eq port 5 anyThe following example removes this entry from the IP-ACL.
switch# config terminalEnter configuration commands, one per line. End with CNTL/switch(config)# no ip access-list aclDenyTcpIpPrt5 deny tcp 1.2.3.0 0.0.0.255 eq port 5 anyRelated Commands
ip address (FCIP profile configuration submode)
To assign the local IP address of a Gigabit Ethernet interface to the FCIP profile, use the ip address command. To remove the IP address, use the no form of the command.
ip address address
no ip address address
Syntax Description
Defaults
Disabled.
Command Modes
FCIP profile configuration submode.
Command History
Usage Guidelines
To create a FCIP profile, you must assign a local IP address of a Gigabit Ethernet interface to the FCIP profile.
Examples
The following example assigns the local IP address of a Gigabit Ethernet interface to the FCIP profile.
switch# config terminalswitch(config)# fcip profile 5switch(config-profile)# ip address 10.5.1.1Related Commands
ip address (interface configuration)
To assign an IP address to a Gigabit Ethernet interface, use the ip address command in interface configuration submode. To remove the IP address, us the no form of the command.
ip address address netmask
no ip address address netmask
Syntax Description
Defaults
None.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example assigns an IP address to a Gigabit Ethernet interface.
switch# config terminalswitch(config)# interface gigabitethernet 1/2switch(config-profile)# ip address 10.5.1.1 255.255.0.0Related Commands
ip-compression
To enable compression on the FCIP link, use the ip-compression command in interface configuration submode. To disable compression, use the no form of the command.
ip-compression [auto | mode1 | mode2 | mode3]
no ip-compression [auto | mode1 | mode2 | mode3]
Syntax Description
Defaults
Disabled.
Command Modes
Interface configuration submode.
Command History
1.3(1)
This command was introduced.
2.0(x)
Changed the keywords from high-throughput and high-comp-ratio to mode1, mode2, and mode3.
Usage Guidelines
When no compression mode is entered in the command, the default is auto.
The FCIP compression feature introduced in Cisco SAN-OS Release 1.3 allows IP packets to be compressed on the FCIP link if this feature is enabled on that link. By default the FCIP compression is disabled. When enabled, the software defaults to using the auto mode (if a mode is not specified).
Cisco SAN-OS Release 2.0(1b) and later, you to configure FCIP compression using one of the following modes:
•
•
•
•
The IP compression feature behavior differs between the IPS module(s) and the MPS-14/2 module—while mode2 and mode3 perform software compression in both modules, mode1 performs hardware-based compression in MPS-14/2 modules, and software compression in IPS-4 and IPS-8 modules.
In Cisco MDS SAN-OS Release 2.1(1a) and later, the auto mode option uses a combination of compression modes to effectively utilize the WAN bandwidth. The compression modes change dynamically to maximize the WAN bandwidth utilization.
Examples
The following example enables faster compression.
switch# config terminalswitch(config) interface fcip 1switch(config-if)# ip-compression mode1The following example enables automatic compression by default.
switch(config-if)# ip-compressionThe following example disables compression.
switch(config-if)# no ip-compressionRelated Commands
show interface fcip
Displays an interface configuration for a specified FCIP interface.
ip default-gateway
To configure the IP address of the default gateway, use the ip default-gateway command. To disable the IP address of the default gateway, use the no form of the command.
ip default-gateway destination-ip-address [interface cpp slot_number/processor-number/vsan-id]
no ip default-gateway destination-ip-address [interface cpp slot/processor-number/vsan-id]
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following examples configures the IP default gateway to 1.1.1.4.
switch# config terminalswitch(config)# ip default-gateway 1.1.1.4Related Commands
ip default-network
To configure the IP address of the default network, use the ip default-network command in configuration mode. To disable the IP address of the default network, use the no form of the command.
ip default-network ip-address
no ip default-network ip-address
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following examples configures the IP address of the default network to 1.1.1.4.
switch# config terminalswitch(config)# ip default-network 1.1.1.4switch(config)# ip default-gateway 1.1.1.4Related Commands
ip domain-list
To configure the IP domain list, use the ip domain-list command in configuration mode. To disable the IP domain list, use the no form of the command.
ip domain-list domain-name
no ip domain-list domain-name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example configures the IP domain list.
switch# config terminalswitch(config)# ip domain MyListRelated Commands
ip domain-lookup
To enable the DNS server lookup feature, use the ip domain-lookup command in configuration mode. Use the no form of this command to disable this feature.
ip domain-lookup
no ip domain-lookup
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Instead of IP addresses, you can configure the switch using meaningful names. The configured name automatically looks up the corresponding IP address.
Examples
The following example configures a DNS server lookup feature.
switch# config terminalswitch(config)# ip domain-lookupRelated Commands
ip domain-name
To configure a domain name, use the ip domain-name command in configuration mode. To delete a domain name, use the no form of the command.
ip domain-name domain-name
no ip domain-name domain-name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example configures a domain name.
switch# config terminalswitch(config)# ip domain-name MyDomainRelated Commands
ip name-server
To configure a name server, use the ip name-server command in configuration mode. To disable this feature, use the no form of the command.
ip name-server ip-address
no ip name-server ip-address
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You can configure a maximum of six servers. By default, no server is configured.
Examples
The following example configure a name server with an IP address of 1.1.1.4.
switch# config terminalswitch(config)# ip name-server 1.1.1.4The following example specifies the first address (15.1.0.1) as the primary server and the second address (15.2.0.0) as the secondary sever.
switch(config)# ip name-server 15.1.0.1 15.2.0.0The following example deletes the configured server(s) and reverts to factory default.
switch(config)# no ip name-serverRelated Commands
ip route
To configure a static route, use the ip route command in configuration mode.
ip route ip-address subnet-mask [nexthop_ip-address] [interface {gigabitethernet slot /port | mgmt 0 | port-channel channel-id | vsan vsan-id} | distance distance-number]
no ip route ip-address subnet-mask [nexthop_ip-address] [interface {gigabitethernet slot /port | mgmt 0 | port-channel channel-id | vsan vsan-id} | distance distance-number]
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following examples shows how to configure a static route.
switch# config terminalswitch(config)# IP route 10.0.0.0 255.0.0.0 20.20.20.10 distance 10 interface vsan 1Related Commands
ip routing
To enable the IP forwarding feature, use the ip routing command in configuration mode. To disable this feature, use the no form of the command.
ip routing
no ip routing
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example enables the IP forwarding feature.
switch# config terminalswitch(config)# ip routingRelated Commands
ips netsim delay-ms
To delay packets that arrive at a specified Gigabit Ethernet interface specifying milliseconds, use the ips netsim delay command in SAN extension tuner configuration submode.
ips netsim delay-ms milliseconds ingress gigabitethernet slot/port
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
This command introduces a delay for all packets entering the Gigabit Ethernet interface. Delay is unidirectional. To introduce delay in the opposite direction, use the slot and port number of the adjacent interface.
Examples
The following example shows how to configure a delay of 50 milliseconds for packets entering Gigabit Ethernet interface 2/3.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim delay-ms 50 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim delay-us
To delay packets that arrive at a specified Gigabit Ethernet interface specifying microseconds, use the ips netsim delay command in SAN extension tuner configuration submode.
ips netsim delay-us microseconds ingress gigabitethernet slot/port
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
This command introduces a delay for all packets entering the Gigabit Ethernet interface. Delay is unidirectional. To introduce delay in the opposite direction, use the slot and port number of the adjacent interface.
Examples
The following example shows how to configure a delay of 50 microseconds for packets entering Gigabit Ethernet interface 2/3.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim delay-us 50 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim drop nth
To drop packets every nth packet at a specified Gigabit Ethernet interface, use the ips netsim drop nth command in SAN extension tuner configuration submode.
ips netsim drop nth packet {burst burst-size ingress gigabitethernet slot/port | ingress gigabitethernet slot/port}
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
You can configure the IP Network Simulator to simulate packet drops (even when the queue is not full) randomly (specified as a percentage) or every Nth packet. Percentage is represented as the number of packets in 10,000. For example, if you want to drop one percent of packets, then specify it as 100 packets in 10,000. To simulate a realistic scenario for IP networks using random drops, the drop percentage should be between zero and one percent of packet drops in the specified traffic direction.
If you use the optional burst parameter, then a specified number of packets are dropped. If you do not specify the burst parameter, then only one packet is dropped. The burst limit for either random or Nth drops is 1 to 100 packets. Take the burst parameter into account when specifying the percentage of packets dropped. For example, if you select a random drop of 100 packets in 10,000 (or one percent) with a burst of 2, 200 packets (or two percent) in every 10,000 packets are dropped. Specifying 2 for burst doubles the packet drop.
Examples
The following example shows how to configure an interface to drop every 100th packet, 2 packets at a time.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim drop nth 100 burst 2 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim drop random
To drop packets randomly at a specified Gigabit Ethernet interface, use the ips netsim drop random command in SAN extension tuner configuration submode.
ips netsim drop random packet-percentage {burst burst-size ingress gigabitethernet slot/port | ingress gigabitethernet slot/port}
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
You can configure the IP Network Simulator to simulate packet drops (even when the queue is not full) randomly (specified as a percentage) or every Nth packet. Percentage is represented as the number of packets in 10,000. For example, if you want to drop one percent of packets, then specify it as 100 packets in 10,000. To simulate a realistic scenario for IP networks using random drops, the drop percentage should be between zero and one percent of packet drops in the specified traffic direction.
If you use the optional burst parameter, then a specified number of packets are dropped. If you do not specify the burst parameter, then only one packet is dropped. The burst limit for either random or Nth drops is 1 to 100 packets. Take the burst parameter into account when specifying the percentage of packets dropped. For example, if you select a random drop of 100 packets in 10,000 (or one percent) with a burst of 2, 200 packets (or two percent) in every 10,000 packets are dropped. Specifying 2 for burst doubles the packet drop.
Examples
The following example shows how to configure an interface to drop one percent of packets.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim drop random 100 burst 1 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim enable
To enable two Gigabit Ethernet interfaces to operate in the network simulation mode, enter the ips netsim enable command in SAN extension tuner configuration submode. To disable this feature, use the no form of the command.
ips netsim enable interface gigabitethernet slot/port gigabitethernet slot/port
Syntax Description
interface
Specifies that interfaces are enabled.
gigabitethernet
slot/portSpecifies the the slot and port number of the Gigabit Ethernet interface.
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
This command enables two Gigabit Ethernet interfaces to simulate network characteristics. The first interface specified is the ingress port and the second interface specified is the egress port. Ports must be adjacent and the ingress interface must be an odd-numbered port.
Interfaces configured with this command can no longer be used for FCIP or iSCSI. When the SAN extension tuner configuration submode is turned off, any interface configured for network simulation reverts back to normal operation.
Examples
The following example enables the IP Network Simulator and configures interfaces 2/3 and 2/4 for network simulation.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim enable interface gigabitethernet 2/3 gigabitethernet 2/4Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim max-bandwidth-kbps
To limit the bandwidth in kilobytes per second of a specified Gigabit Ethernet interface, use the ips netsim max-bandwidth-kbps command in SAN extension tuner configuration submode.
ips netsim max-bandwidth-kbps bandwidth ingress gigabitethernet slot/port
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
Examples
The following example shows how to limit the interface bandwidth to 4500 Kbps.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim max-bandwidth-kbps 4500 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim max-bandwidth-mbps
To limit the bandwidth in megabytes per second of a specified Gigabit Ethernet interface, use the ips netsim max-bandwidth-mbps command in SAN extension tuner configuration submode.
ips netsim max-bandwidth-mbps bandwidth ingress gigabitethernet slot/port
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
Examples
The following example shows how to limit the interface bandwidth to 45 Mbps.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim max-bandwidth-mbps 45 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim qsize
To limit the size of the queue on a specified Gigabit Ethernet interface, use the ips netsim qsize command in SAN extension tuner configuration submode.
ips netsim qsize queue-size ingress gigabitethernet slot/port
Syntax Description
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
This command rate limits the size of the queue on a specified Gigabit Ethernet port. The recommended queue size for network simulation is 50000 to 150000. If the queue becomes full, packets are dropped.
Examples
The following example shows how to limit the queue size to 75 KB.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim qsize 75 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ips netsim reorder
To reorder packets entering a specified Gigabit Ethernet interface, use the ips netsim reorder command in SAN extension tuner configuration submode.
ips netsim reorder {nth packet distance dist-packet ingress gigabitethernet slot/port | nth packet ingress gigabitethernet slot/port} | {random percent distance dist-packet ingress gigabitethernet slot/port | random percent ingress gigabitethernet slot/port}
Syntax Description
|
Defaults
Disabled.
Command Modes
SAN extension tuner configuration submode.
Command History
Usage Guidelines
To use this command, you must enable the IP Network Simulator using the ips netsim enable command.
You can configure network simulator to reorder packets (even when the queue is not full) randomly (specified as a percentage) or every Nth packet. Percentage is represented as the number of packets in 10,000. For example, if you want to reorder one percent of packets, then specify it as 100 packets in 10,000. To simulate a realistic scenario for IP networks using random reordering, the percentage should be between zero and one percent of packet reordered in the specified traffic direction.
If you use the optional burst parameter, then the specified number of packets will be reordered. If you do not specify the burst parameter, then only one packet is reordered.
Examples
The following example shows reordering at 50 percent with a distance limit of 5.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim reorder random 50 distance 5 ingress gigabitethernet 2/3The following example shows reordering of every 50th packet with a distance limit of 5.
switch# config terminalswitch(config)#switch(config)# san-ext-tuner enableswitch(config)# exitswitch#switch# ips netsim reorder nth 50 distance 5 ingress gigabitethernet 2/3Related Commands
show ips netsim
Displays a summary of the interfaces that are currently operating in network simulation mode.
ips netsim enable
Enables the IP Network Simulator.
ipv6 access-list
To configure an IPv6 access control list (ACL) and enter IPv6-ACL configuration submode, use the ipv6 access-list command in configuration mode. To discard an IPv6 ACL, use the no form of the command.
ipv6 access-list list-name
no ipv6 access-list list-name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Before using the ipv6 access-list command to configure an IPv6 ACL on a switch, become familiar with the features of IPv6 and its extended addressing capabilities. In particular, it is important to understand the different types of IPv6 address formats, the IPv6 address prefix format, and the different IPv6 address types. For detailed information about IPv6, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Examples
The following example configures an IPv6 access list called List1 and enters IPv6-ACL configuration submode.
switch # config tEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ipv6 access-list List1switch(config-ipv6-acl)#The following example removes the IPv6 access list called List1 and all of its entries.
switch(config)# no ipv6 access-list List1switch(config)#Related Commands
ipv6 address
To enable IPv6 processing and configure an IPv6 address on the interface, use the ipv6 address command in interface configuration submode. To remove an IPv6 address, use the no form of the command.
ipv6 address ipv6-address-prefix
no ipv6 address ipv6-address-prefix
Syntax Description
Defaults
None.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
You can use the ipv6 address command to enable IPv6 processing and configure the IPv6 address on the interface. An IPv6 address must be configured on an interface for the interface to forward IPv6 traffic.
Assigning a unicast address generates a link local address and implicitly enables IPv6.
Note
Examples
The following example assigns a unicast IPv6 address to the interface and enables IPv6 processing on the interface.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z. switch(config)# interface gigabitethernet 2/2 switch(config-if)# ipv6 address 2001:0DB8:800:200C::417A/64Related Commands
ipv6 address autoconfig
To enable automatic configuration of IPv6 addresses using stateless autoconfiguration on an interface and enable IPv6 processing on the interface, use the ipv6 address autoconfig command in interface configuration submode. To remove the address from the interface, use the no form of the command.
ipv6 address autoconfig
no ipv6 address autoconfig
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
You can use the ipv6 address autoconfig command to enable IPv6 stateless autoconfiguration on the specified interface. For additional information about autoconfiguration, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Examples
The following example assigns enables IPv6 stateless autoconfiguration on the interface.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z. switch(config)# interface gigabitethernet 2/2 switch(config-if)# ipv6 address autoconfigRelated Commands
ipv6 enable
To enable IPv6 processing and configure an IPv6 link-local address on the interface, use the ipv6 enable command in interface configuration submode. To disable IPv6 processing and remove the link-local address, use the no form of the command.
ipv6 enable
no ipv6 enable
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
When you enable IPv6 on an interface, a link local address is automatically assigned. This address is used for communication on the switch.
Examples
The following example enables IPv6 processing on the interface.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z. switch(config)# interface gigabitethernet 2/2 switch(config-if)# ipv6 enableThe following example disables IPv6 processing on the interface.
switch(config-if)# no ipv6 enable
Related Commands
ipv6 nd
To configure IPv6 neighbor discovery commands on the interface, use the ipv6 nd command in interface configuration submode. To remove IPv6 neighbor discovery configuration commands, use the no form of the command.
ipv6 nd {dad attempts number | reachable-time time | retransmission-time time}
no ipv6 nd {dad attempts number | reachable-time time | retransmission-time time}
Syntax Description
Defaults
DAD attempts: 0.
Reachable-time: 30000 milliseconds.
Retransmission-time: 1000 milliseconds.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
A router must be able to determine the link-local address for each of its neighboring routers in order to ensure that the target address (the final destination) in a redirect message identifies the neighbor router by its link-local address. For static routing, the address of the next-hop router should be specified using the link-local address of the router; for dynamic routing, all IPv6 routing protocols must exchange the link-local addresses of neighboring routers.
Note
For complete information about IPv6 neighbor discovery, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Examples
The following example sets the duplicate address detection attempts count to 2.
switch# config terminal
switch(config)# interface gigabitethernet 2/2
switch(config-if)# ipv6 nd dad attempts 2
The following example sets the reachability time to 10000 milliseconds.
switch(config-if)# ipv6 nd reachability-time 10000
The following example sets the retransmission time to 20000 milliseconds.
switch(config-if)# ipv6 nd retransmission-time 20000
Related Commands
ipv6 route
To configure an IPv6 static route, use the ipv6 route command in configuration mode. To remove or disable an IPv6 static route, use the no form of the command.
ipv6 route destination-address-prefix next-hop-address [distance distance-metric | interface {gigabitethernet slot/port | mgmt number | port-channel number | vsan vsan-id}]
[distance distance-metric]no ipv6 route destination-address-prefix next-hop-address [distance distance-metric | interface {gigabitethernet slot/port | mgmt number | port-channel number | vsan vsan-id}]
[distance distance-metric]Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Before using the ipv6 route command to configure IPv6 features on a switch, become familiar with the features of IPv6 and its extended addressing capabilities. In particular, it is important to understand the different types of IPv6 address formats, the IPv6 address prefix format, and the different IPv6 address types. For detailed information about IPv6, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Examples
The following example configures a static default IPv6 route on a Gigabit Ethernet interface.
switch # config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ipv6 route ::/0 gigabitethernet 3/1The following example configures a fully specified static route on a Gigabit Ethernet interface.
switch(config)# ipv6 route 2001:0DB8::/32 gigabitethernet 3/2The following example configures a recursive static route to a specified next hop address.
switch(config)# ipv6 route 2001:0DB8::/32 2001:0DB8:2002::1The following example configures a recursive static route to a specified next hop address, from which the output interface is automatically derived, and to a specified interface.
switch(config)# ipv6 route 2001:0DB8::/32 2001:0DB8:2002::1 gigabitethernet 3/2The following example configures a static IPv6 route with an administrative distance of 20.switch(config)# ipv6 route 2001:0DB8::/32 interface gigabitethernet 2/0 distance 20Related Commands
ipv6 routing
To enable IPv6 unicast routing, use the ipv6 routing command in configuration mode. To disable IPv6 unicast routing, use the no form of the command.
ipv6 routing
no ipv6 routing
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Before using the ipv6 routing command to configure IPv6 features on a switch, become familiar with the features of IPv6 and its extended addressing capabilities. In particular, it is important to understand the different types of IPv6 address formats, the IPv6 address prefix format, and the different IPv6 address types. For detailed information about IPv6, refer to the Cisco MDS 9000 Family CLI Configuration Guide.
Examples
The following example enables IPv6 routing.
switch # config terminalswitch(config)# ipv6 routingThe following example disables IPv6 routing.
switch(config)# no ipv6 routingRelated Commands
ipv6 traffic-filter
To configure IPv6 access control lists (ACLs) to filter traffic for packets on the interface, use the ipv6 traffic-filter command in interface configuration submode. To remove an IPv6-ACL traffic filter on the switch, use the no form of the command.
ipv6 traffic-filter access-list-name {in | out}
no ipv6 traffic-filter access-list-name {in | out}
Syntax Description
access-list-name
Specifies the name of an access control list for packets. The maximum size is 64 characters.
in
Configures inbound packets.
out
Configures outbound packets.
Defaults
None.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
None.
Examples
The following example configures a traffic filter, called testfilter, for inbound packets.
switch# config terminal
switch(config)# interface gigabitethernet 2/2
switch(config-if)# ipv6 traffic-filter testfilter in
Related Commands
iscsi authentication
To configure the default authentication method for iSCSI, use the iscsi authentication command. To revert to the default, use the no form of the command.
iscsi authentication {chap | chap-none | none | username username password [0 | 7] password}
no iscsi authentication {chap | chap-none | none | username}
Syntax Description
Defaults
chap-none.
The default password is a cleartext password.
Command Modes
Configuration mode.
Command History
Usage Guidelines
By default, the Cisco MDS 9000 Family switch accepts an iSCSI initiator with either no authentication or CHAP authentication. If CHAP authentication is always required, use the iscsi authentication chap command. If no authentication is always required, use the iscsi authentication none command.
Use the chap-none option to override the global configuration which might have been configured to allow only one option—either CHAP or none—not both.
Note
Examples
The following example configures CHAP only for ISCSI authentication.
switch# config terminalswitch(config)# iscsi authentication chapRelated Commands
iscsi duplicate-wwn-check
To check the current running configuration for conflicts between iSCSI initiators' static WWN allocation and what the system thinks is available in its WWN pool, use the iscsi duplicate-wwn-check command in configuration mode.
iscsi duplicate-wwn-check
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Prior to Cisco MDS SAN-OS Release 2.1(2), WWNs assigned to static iSCSI initiators by the system can be inadvertently returned to the system when an upgrade fails or the system software is manually downgraded (that is, when you manually boot up an older Cisco MDS SAN-OS release without using the install all command). In these instances, the system can later assign those WWNs to other iSCSI initiators (dynamic or static) and cause conflicts.
As of Cisco MDS SAN-OS Release 2.1(2), you can use the iscsi duplicate-wwn-check command to check for and remove any configured WWNs that belong to the system.
Note
Examples
The following example shows how to check the current running configuration for conflicts between iSCSI initiators' static WWN allocation and what the system thinks is available in its WWN pool.
switch# config terminalEnter configuration command, one per line. End with CNTL/Z.switch(config)# iscsi duplicate-wwn-checkList of Potential WWN Conflicts:-------------------------------Node : iqn.test-local-nwnn:1-local-pwwn:1nWWN : 22:03:00:0d:ec:02:cb:02pWWN : 22:04:00:0d:ec:02:cb:02The following example shows how to remove the conflicting nWWN and pWWN.
switch(config)# iscsi initiator name iqn.test-local-nwwn:1-local-pwwn:1switch(config-iscsi-init)# no static nWWN 22:03:00:0d:ec:02:cb:02switch(config-iscsi-init)# no static pWWN 22:04:00:0d:ec:02:cb:02Related Commands
iscsi dynamic initiator
To configure dynamic initiator modes, use the iscsi dynamic initiator command in configuration mode. To revert to the default mode, use the no form of the command.
iscsi dynamic initiator {deny | islb}
no dynamic initiator {deny | islb}
Syntax Description
deny
Specifies that dynamic initiators are denied from logging on to the MDS switch.
islb
Specifies iSLB dynamic initiator mode.
Defaults
iSCSI.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Three dynamic initiator modes are supported:
•
•
•
iSCSI dynamic initiator is the default mode of operation. This configuration is distributed using CFS.
Note
A dynamic iSCSI initiator can be converted to a static iSCSI initiator and its WWNs can be made persistent.
A dynamic iSLB initiator can be converted to a static iSLB initiator and its WWNs can be made persistent.
Note
Note
Examples
The following command configures the dynamic initiator mode as iSLB.
switch(config)# iscsi dynamic initiator islbThe following command configures the dynamic initiator mode as deny.
switch(config)# iscsi dynamic initiator denyThe following command reverts to the default dynamic initiator mode of iSCSI.
switch(config)# no iscsi dynamic initiator denyRelated Commands
iscsi save-initiator
Permanently saves the automatically-assigned nWWN or pWWN mapping.
show iscsi global
Displays global iSCSI configured information.
iscsi enable
To enable the iSCSI feature in any Cisco MDS switch, issue the iscsi enable command. To disable this feature, use the no form of the command.
iscsi enable
no iscsi enable
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
The configuration and verification commands for the iSCSI feature are only available when iSCSI is enabled on a switch. When you disable this feature, all related configurations are automatically discarded.
Note
Examples
The following command enables the iSCSI feature.
switch(config)# iscsi enableswitch(config)# iscsi enable module 8switch(config)# int iscsi 2/1switch(config-if)#switch(config)# no shutdownThe following command disables the iSCSI feature (default).
switch(config)# no iscsi enableiscsi enable module
To enable iSCSI features for each IPS linecard to create corresponding iSCSI interfaces, use the iscsi enable module command.
iscsi enable module module-num
Syntax Description
module-num
Specifies the desired IPS linecard module number on which iSCSI interfaces need to be enabled.
Defaults
iSCSI interfaces are disabled on IPS linecards by default.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example shows how to enable the iSCSI interface on a desired module number on the switch.
switch# configEnter configuration commands, one per line. End with CNTL/Z.switch(config)# iscsi enable module 1
Note
Related Commands
iscsi import target fc
To allow dynamic mapping of Fibre Channel targets, use the iscsi import target fc command. To disable this feature, use the no form of the command.
iscsi import target fc
no iscsi import target fc
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This command directs iSCSI to dynamically import all Fibre Channel targets into iSCSI.
Note
Examples
The following example allows dynamic mapping of Fibre Channel targets.
switch# config terminalswitch(config)# iscsi import target fcThe following example disables dynamic mapping of Fibre Channel targets.
switch(config)# no iscsi import target fcRelated Commands
iscsi initiator idle-timeout
To configure the iSCSI initiator idle timeout, use the iscsi initiator idle-timeout command. To revert to the default, use the no form of the command.
iscsi initiator idle-timeout seconds
no iscsi initiator idle-timeout seconds
Syntax Description
Defaults
300 seconds.
Command Modes
Configuration mode.
Command History
Usage Guidelines
When the idle timeout value is set to 0, the initiator information is cleared immediately after the last session from the initiator terminates.
Note
Examples
The following example configures the iSCSI initiator idle timeout to 180 seconds.
switch# config terminalswitch(config)# iscsi initiator idle-timeout 180The following example reverts the default value of 300 seconds.
switch# config terminalswitch(config)# no iscsi initiator idle-timeout 240Related Commands
iscsi initiator ip-address
To assign persistent WWNs to an iSCSI initiator or assign an iSCSI initiator into VSANs other than the default VSAN, use the iscsi initiator ip-address command. To revert to the default, use the no form of the command.
iscsi initiator ip-address ipaddress
static {nwwn | pwwn} {wwn-id | system-assign number}
vsan vsan-idiscsi initiator ip-address ipaddress
no static {nwwn | pwwn} {wwn-id | system-assign number}
no vsan vsan-idno iscsi initiator ip-address ipaddress
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Under a circumstance where an iSCSI initiator needs to have a persistent binding to FC WWNs, this command should be used. Also, an iSCSI initiator can be put into multiple VSANs. An iSCSI host can become a member of one or more VSANs.
Note
Examples
The following command configures an iSCSI initiator. using the IP address of the initiator node.
switch(config)# iscsi initiator ip address 10.50.1.1The following command deletes the configured iSCSI initiator.
switch(config)# no iscsi initiator ip address 10.5.0.0The following command uses the switch's WWN pool to allocate the nWWN for this iSCSI initiator and keeps it persistent.
switch(config-(iscsi-init))# static nWWN system-assignThe following command assigns the user provided WWN as nWWN for the iSCSI initiator. You can only specify one nWWN for each iSCSI node.
switch(config-(iscsi-init))# nWWN 20:00:00:05:30:00:59:11The following command uses the switch's WWN pool to allocate two pWWNs for this iSCSI initiator and keeps it persistent.
switch(config-(iscsi-init))# static pWWN system-assign 2The following command assigns the user provided WWN as pWWN for the iSCSI initiator.
switch(config-(iscsi-init))# pWWN 21:00:00:20:37:73:3b:20Related Commands
iscsi initiator name
To configure an iSCSI initiator name and change to iSCSI configuration mode, use the iscsi initiator name command. To revert to factory defaults, use the no form of the command.
iscsi initiator name name
no iscsi initiator name name
Syntax Description
name
Enters the initiator name to be used. The minimum length is 16 characters and maximum is 223 characters.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Under a circumstance where an iSCSI initiator needs to have a persistent binding to FC WWNs, this command should be used. Also, an iSCSI initiator can be put into multiple VSANs. An iSCSI host can become a member of one or more VSANs.
Note
Examples
The following example configures an iSCSI initiator using the iSCSI name of the initiator node.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# iscsi initiator name iqn.1987-02.com.cisco.initiatorRelated Commands
iscsi interface vsan-membership
To configure VSAN membership for iSCSI interfaces, use the iscsi interface vsan-membership command. Use the no form of this command to disable this feature or to revert to factory defaults.
iscsi interface vsan-membership
no iscsi interface vsan-membership
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
If the iscsi interface vsan-membership command is disabled, you will not be able to configure iSCSI VSAN membership.
Caution
For additional information, refer to the "Configuring iSCSI" chapter of the Cisco MDS 9000 Family CLI Configuration Guide.
Note
Examples
The following command enables the iSCSI interface VSAN membership.
switch# config terminalswitch(config)# iscsi interface vsan-membershipThe following command disables the iSCSI interface VSAN membership (default).
switch(config)# no iscsi interface vsan-membershipRelated Commands
iscsi save-initiator
To permanently save the automatically-assigned nWWN/pWWN mapping, use the iscsi save-initiator command.
iscsi save-initiator [ip-address ip-address | name name]
Syntax Description
ip-address ip-address
Specifies the initiator IP address.
name name
Specifies the initiator name to be used from 1 to 255 characters. The minimum length is 16 characters.
Defaults
If initiator name or IP address is not specified, the nWWN/pWWN mapping for all initiators becomes permanent.
Command Modes
Configuration mode.
Command History
Usage Guidelines
After executing the iscsi save-initiator command, issue the copy running-config startup-config to save the nWWN/pWWN mapping across switch reboots.
After a dynamic iSCSI initiator has logged in, you may decide to permanently save the automatically assigned nWWN/pWWN mapping so this initiator uses the same mapping the next time it logs in.
You can convert a dynamic iSCSI initiator to static iSCSI initiator and make its WWNs persistent.
Note
Note
Examples
The following example shows how to save the nWWN/pWWN mapping for all the initiators.
switch(config)# iscsi save-initiatorThe following example shows how to save the nWWN/pWWN mapping for an initiator named iqn.1987-02.com.cisco.initiator.
switch(config)# iscsi save-initiator name iqn.1987-02.com.cisco.initiatorRelated Commands
iscsi initiator
Configures an iSCSI initiator.
show iscsi initiator
Displays information about configured iSCSI initiators.
iscsi virtual-target name
To create a static iSCSI virtual target, use the iscsi virtual-target command. To revert to the default values, use the no form of the command.
iscsi virtual-target name name
advertise interface {gigabitethernet slot/port[.subinterface] | port-channel channel-id[.subinterface]}
all-initiator-permit
initiator {initiator-name | ip-address ipaddress [netmask]} permit
pwwn pwwn-id [fc-lun number iscsi-lun number [secondary-pwwn pwwn-id [sec-lun number]] | secondary-pwwn pwwn-id]
revert-primary-port
trespassiscsi virtual-target name name
no advertise interface {gigabitethernet slot/port[.subinterface] | port-channel channel-id[.subinterface]}
no all-initiator-permit
no initiator {initiator-name | ip-address ipaddress [netmask]} permit
no pwwn pwwn-id [fc-lun number iscsi-lun number [secondary-pwwn pwwn-id [sec-lun number]] | secondary-pwwn pwwn-id]
no revert-primary-port
no trespassno iscsi virtual-target name name
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
1.1(1)
This command was introduced.
1.3(1)
Added revert-to-primary and trespass subcommands.
Usage Guidelines
This command is used to configure a static iSCSI target for access by iSCSI initiators. A virtual target may contain a subset of LUs of an FC target or one whole FC target.
Do not specify the LUN if you wish to map the whole Fibre Channel target to an iSCSI target. All Fibre Channel LUN targets are exposed to iSCSI.
Note
One iSCSI target cannot contain more than one Fibre Channel target.
Note
Examples
The follow example creates a static virtual target and enters ISCSI target configuration submode.
switch# config terminalswitch(config)# iscsi virtual-target name 0123456789ABDEFGHIswitch(config-iscsi-tgt)#The following command advertises the virtual target only on the specified interface. By default, it is advertised on all interfaces in all IPS modules.
switch(config-iscsi-tgt)# advertise interface gigabitethernet 4/1The following command maps a virtual target node to a Fibre Channel target.
switch(config-iscsi-tgt)# pWWN 26:00:01:02:03:04:05:06The following command enters the secondary pWWN for the virtual target node.
switch(config-iscsi-tgt)# pWWN 26:00:01:02:03:04:05:06 secondary-pwwn 66:00:01:02:03:04:05:02Use the LUN option to map different Fibre Channel LUNs to different iSCSI virtual targets. If you have already mapped the whole Fibre Channel target, you will not be able to use this option.
switch(config-iscsi-tgt)# pWWN 26:00:01:02:03:04:05:06 fc-lun 0 iscsi-lun 0The following command allows the specified iSCSI initiator node to access this virtual target. You can issue this command multiple times to allow multiple initiators.
switch(config-iscsi-tgt)# initiator iqn.1987-02.com.cisco.initiator1 permitThe following command prevents the specified initiator node from accessing virtual targets.
switch(config-iscsi-tgt)# no initiator iqn.1987-02.com.cisco.initiator1 permitThe following command allows the specified IP address to access this virtual target:
switch(config-iscsi-tgt)# initiator ip-address 10.50.1.1 permitThe following command prevents the specified IP address from accessing virtual targets:
switch(config-iscsi-tgt)# no initiator ip-address 10.50.1.1 permitThe following command allows all initiators in this subnetwork to access this virtual target:
switch(config-iscsi-tgt)# initiator ip-address 10.50.0.0 255.255.255.0 permitThe following command prevents all initiators in this subnetwork from accessing virtual targets:
switch(config-iscsi-tgt)# no initiator ip-address 10.50.0.0 255.255.255.0 permitThe following command allows all initiator nodes to access this virtual target.
switch(config-iscsi-tgt)# all-initiator-permitThe following command prevents any initiator node from accessing virtual targets.
switch(config-iscsi-tgt)# no all-initiator-permitThe following command configures a primary and secondary port and moves the LUNs from one port to the other using the trespass command.
switch# config terminalswitch(config)# iscsi virtual-target name iqn.1987-02.com.cisco.initiatorswitch(config-iscsi-tgt)# pwwn 50:00:00:a1:94:cc secondary-pwwn 50:00:00:a1:97:acswitch(config-iscsi-tgt)# trespassRelated Commands
islb abort
To discard a pending iSCSI Server Load Balancing (iSLB) configuration, use the islb abort command.
islb abort
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You can use the islb abort command to discard the pending changes to the iSLB configuration and release the fabric lock. This action has no effect on the active configuration on any switch in the fabric.
The islb abort command can be issued only by the user who started the Cisco Fabric Services (CFS) session and only on the switch that started the CFS session.
Examples
The following example discards the pending iSLB configuration distribution.
switch# config tswitch(config)# islb abortRelated Commands
islb commit
To commit a pending iSCSI server load balancing (iSLB) configuration, use the islb commit command.
islb commit
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You can use the islb commit command to commit the pending changes to the iSLB configuration and release the fabric lock. This action changes the active configuration on all Cisco MDS switches in the fabric.
The islb commit command can be issued only by the user who started the Cisco Fabric Services (CFS) session and only on the switch that started the CFS session.
Examples
The following example commits the pending iSLB configuration distribution.
switch# config tswitch(config)# islb commitRelated Commands
islb distribute
To enable Cisco Fabric Services for iSCSI Server Load Balancing (iSLB) configuration, use the islb distribute command. To disable the iSLB configuration distribution, use the no form of the command
islb distribute
no islb distribute
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You can use the islb distribute command to enable the distribution of iSLB configuration information to other Cisco MDS switches in the fabric using the Cisco Fabric Services (CFS) infrastructure. You can synchronize the iSLB configuration across the fabric from the console of a single MDS switch.
Note
If you are using both iSLB and inter-VSAN routing (IVR), ensure that the following conditions are satisfied; otherwise, traffic may be disrupted in the fabric.
•
•
Examples
The following example enables iSLB configuration distribution.
switch# config tswitch(config)# islb distributeThe following example disables iSLB configuration distribution.
switch(config)# no islb distributeRelated Commands
islb initiator
To configure the iSCSI server load balancing (iSLB) initiator and enter iSLB initiator configuration submode, use the islb initiator command. To delete the configured ISLB initiator, use the no form of the command.
islb initiator {ip-address {ip-address | ipv6-address} | name name}
no islb initiator name name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You can use the islb initiator command to enter iSLB initiator configuration submode to configure static mapping for an iSLB initiator.
Examples
The following example enters iSLB initiator configuration submode to configure static mapping (using the IPv4 ip-address option) for an iSLB initiator.
switch# config tswitch(config)# islb initiator ipaddress 10.1.2.3switch(config-islb-init)#The following example deletes the configured iSLB initiator.
switch(config)# no islb initiator ipaddress 10.1.2.3The following example enters iSLB initiator configuration submode to configure static mapping (using the IPv6 option) for an iSLB initiator.
switch# config tswitch(config)# islb initiator ipaddress 1111.2222.3333.4::5switch(config-islb-init)#The following example deletes the configured iSLB initiator.
switch(config)# no islb initiator ipaddress 1111.2222.3333.4::5The following example enters iSLB initiator configuration submode to configure static mapping (using the name option) for an iSLB initiator.
switch# config tswitch(config)# islb initiator name iqn.1987-02.co..cisco.initiatorswitch(config-islb-init)#The following example deletes the configured iSLB initiator:switch(config)# no islb initiator ipaddress name iqn.1987-02.co..cisco.initiatorRelated Commands
islb save-initiator
To permanently save the automatically-assigned nWWN/pWWN mapping for the iSLB initiator, use the islb save-initiator command.
islb save-initiator [ip-address ip-address | name name]
Syntax Description
ip-address ip-address
Specifies the initiator IP address. The format is A.B.C.D or X:X:X::X.
name name
Specifies the initiator name to be used from 1 to 223 characters.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Saving the automatically assigned nWWN/pWWN mapping allows the initiator to use the same mapping the next time it logs in.
You can convert a dynamic iSLB initiator to a static iSLB initiator and make its WWNs persistent.
Note
Note
Note
Examples
The following example saves the nWWNs and pWWNs that have automatically been assigned to the iSLB initiator whose name is specified.
switch# config tswitch(config)# islb save-initiator name iqn.1987-02.com.cisco.initiatorThe following example saves the nWWNs and pWWNs that have automatically been assigned to the iSLB initiator whose IPv4 address is specified.
switch(config)# islb save-initiator ip-address 10.10.100.11The following example saves the nWWNs and pWWNs that have automatically been assigned to all the iSLB initiators.
switch(config)# islb save-initiatorPlease execute "copy run start" to keep the WWNs persistent across switch rebootsRelated Commands
islb virtual-target name
To configure an iSLB virtual target and enter iSLB target configuration submode, use the islb virtual-target name command. To revert to the default values, use the no form of the command.
islb virtual-target name name
{all-initiator-permit |
initiator {initiator-name permit | ip address {A.B.C.D permit | X:X:X::X permit}} |
pWWN permit |
revert-primary-port permit |
trespass permit}islb virtual-target name name
{no all-initiator-permit |
no initiator {initiator-name permit | ip address {A.B.C.D permit | X:X:X::X permit}} |
no pWWN permit |
no revert-primary-port permit |
no trespass permit}no islb virtual-target name name
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This command is used to configure a static target for access by iSLB initiators.
Examples
The following example creates a static virtual target and enters iSLB target configuration submode.
switch# config terminalswitch(config)# islb virtual-target name ABCDEFGHIJ1234567890ips-hac1(config-islb-tgt)#The following example allows all iSLB initiators to access the target.
ips-hac1(config-islb-tgt)# all-initiator-permitThe following command allows the specified IP address to access this virtual target:
switch(config-islb-tgt)# initiator ip-address 10.50.1.1 permitThe following example prevents the specified IP address from accessing virtual targets:
switch(config-islb-tgt)# no initiator ip-address 10.50.1.1 permitThe following example allows all initiators in this subnetwork to access this virtual target:
switch(config-islb-tgt)# initiator ip-address 10.50.0.0 255.255.255.0 permitThe following example prevents all initiators in this subnetwork from accessing virtual targets:
switch(config-islb-tgt)# no initiator ip-address 10.50.0.0 255.255.255.0 permitThe following example maps a pWWN to a Fibre Channel target.
ips-hac1(config-islb-tgt)# pwwn 26:00:01:02:03:04:05:06Related Commands
islb vrrp
To configure iSCSI server load balancing (iSLB) on a Virtual Router Redundancy Protocol (VRRP) group, use the islb vrrp command. To disable the iSLB configuration on the VRRP group, use the no form of the command.
islb vrrp {group-number load-balance | ipv6 group-number load-balance}
no islb vrrp {group-number load-balance | ipv6 group-number load-balance}
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
The host is configured with a VRRP address as the portal address. When the VRRP master port receives the first iSCSI session from an initiator, it assigns a slave port to serve that particular host. The information is synchronized to all switches via Cisco Fabric Services (CFS) if recovery is needed when a master port fails. The initiator gets a temporary redirect iSCSI login response. The host then logs in to the slave port at its physical IP address. If the slave port goes down, the host will revert to the master port. The master port knows through CFS that the slave port has gone down and redirects the host to another slave port.
There are separate VRRP groups for IPv4 and IPv6. Each address family is allowed 256 virtual routers.
Note
Tip
Caution
Caution
For additional information, refer to the "Configuring iSCSI" chapter of the Cisco MDS 9000 Family CLI Configuration Guide.
Examples
The following example enables VRRP load balancing for IPv4 Virtual Router group 20.
switch# config tswitch(config)# islb vrrp 20 load-balanceThe following example disables VRRP load balancing for IPv4 Virtual Router group 20.
switch(config)# no islb vrrp 20 load-balanceThe following example enables VRRP load balancing for IPv6 Virtual Router group 30.
switch(config)# islb vrrp ipv6 30 load-balanceThe following example disables VRRP load balancing for IPv6 Virtual Router group 30.
switch(config)# no islb ipv6 30 load-balanceRelated Commands
islb zoneset activate
To activate iSCSI server load balancing (iSLB) auto zones, use the islb zoneset activate command.
islb zoneset activate
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Auto-zoning of the initiator with the initiator targets is enabled by default.
A zone set must be active for a VSAN for auto-zones to be created in that VSAN. The zoneset activate command creates auto-zones only if at least one other change has been made to the zone set.
Examples
The following example activates an iSLB auto zone.
switch# config tswitch(config)# islb zoneset activateRelated Commands
isns
To tag a Gigabit Ethernet or PortChannel interface to an Internet Storage Name Service (iSNS) profile, use the isns command in interface configuration submode. To untag the interface, use the no form of the command.
isns profile-name
no isns profile-name
Syntax Description
Defaults
Disabled.
Command Modes
Interface configuration submode.
Command History
Usage Guidelines
To use this command, iSNS must be enabled using the isns-server enable command.
Use the isns reregister command in EXEC mode to reregister associated iSNS objects (tagged to an iSNS profile) with the iSNS server.
Examples
The following example shows how to tag a Gigabit Ethernet interface to an iSNS profile.
switch# config terminalswitch(config)# interface gigabitethernet 1/2switch(config-if)# isns Profile1The following example shows how to tag a PortChannel interface to an iSNS profile.
switch# config terminalswitch(config)# interface port-channel 2switch(config-if)# isns Profile2Related Commands
isns distribute
To enable Cisco Fabric Services (CFS) distribution for Internet Storage Name Service (iSNS), use the isns distribute command. To disable this feature, use the no form of the command.
isns distribute
no isns distribute
Syntax Description
This command has no other arguments or keywords.
Defaults
Enabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, iSNS must be enabled using the isns-server enable command.
You can configure the pWWN and nWWN of iSCSI initiators and permit a group of iSCSI initiators to share a given nWWN/pWWN pair by using a proxy initiator. The number of iSCSI initiators that register with the iSNS server is more than the number of iSCSI targets that register with the iSNS server. To synchronize the iSCSI initiator entries across switches, you can distribute the iSCSI initiator configuration to iSNS servers across switches.
Examples
The following example shows how to initiate iSNS information distribution.
switch# config terminalswitch(config)# isns distributeThe following example shows how to cancel iSNS information distribution.
switch# config terminalswitch(config)# no isns distributeRelated Commands
isns-server enable
Enables the iSNS server.
show isns
Displays iSNS information.
isns esi retries
To configure the number of entity status inquiry (ESI) retry attempts, use the isns esi retries command in configuration mode. To revert to the default value, use the no form of the command.
isns esi retries number
no isns esi retries number
Syntax Description
Defaults
3 retries.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, Internet Storage Name Service (iSNS) must be enabled using the isns-server enable command.
The iSNS client queries the ESI port at user-configured intervals. Receipt of a response indicates that the client is still alive. Based on the configured value, the interval specifies the number of failed tries before which the client is deregistered from the server.
Examples
The following example shows how change the ESI retries limit to eight.
switch# config terminalswitch(config)# isns esi retries 8Related Commands
isns-server enable
Enables the iSNS server.
show isns
Displays iSNS information.
isns profile name
To create an Internet Storage Name Service (iSNS) profile and enter iSNS profile configuration submode, use the isns profile name command in configuration mode. To delete the iSNS profile, use the no form of the command.
isns profile name profile-name
no isns profile name profile-name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command, iSNS must be enabled using the isns-server enable command.
Examples
The following example shows how to specify an iSNS profile name and enter iSNS profile configuration submode.
switch# config terminalswitch(config)# isns profile name UserProfileswitch(config-isns-profile)#Related Commands
server
Configures a server IP address in an iSNS profile.
show isns
Displays iSNS information.
isns reregister
To register all Internet Storage Name Service (iSNS) objects for an interface that is already tagged to an iSNS profile, use the isns register command.
isns reregister {gigabitethernet slot/number | port-channel channel-group}
Syntax Description
gigabitethernet slot/port
Specifies tagged Gigabit Ethernet interface slot and port.
port-channel channel-group
Specifies tagged PortChannel group. The range is 1 to 128.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
Use this command to reregister portals and targets with the iSNS server for a tagged interface.
Examples
The following command re-registers portal and targets for a tagged interface:
switch# isns reregister gigabitethernet 1/4Related Commands
isns-server enable
To enable the Internet Storage Name Service (iSNS) server, use the isns-server enable command in configuration mode. To disable iSNS, use the no form of the command.
isns-server enable
no isns-server enable
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Performing the isns-server enable command enables the commands used to configure iSNS.
Examples
The following example shows how to enable iSNS.
switch# config terminalswitch(config)# isns-server enableThe following example shows how to disable iSNS.
switch# config terminalswitch(config)# no isns-server enableRelated Commands
ivr abort
To discard an Inter-VSAN Routing (IVR) CFS distribution session in progress, use the ivr abort command in configuration mode.
ivr abort
Syntax Description
This command has no other arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example shows how to discard an IVR CFS distribution session in progress.
switch# config terminalswitch(config)# ivr abortRelated Commands
ivr distribute
Enables CFS distribution for IVR.
show ivr
Displays IVR CFS distribution status and other details.
ivr commit
To apply the pending configuration pertaining to the Inter-VSAN Routing (IVR) Cisco Fabric Services (CFS) distribution session in progress in the fabric, use the ivr commit command in configuration mode.
ivr commit
Syntax Description
This command has no other arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example shows how to apply an IVR configuration to the switches in the fabric.
switch# config terminalswitch(config)# ivr commitRelated Commands
ivr distribute
Enables CFS distribution for IVR.
show ivr
Displays IVR CFS distribution status and other details.
ivr copy active-service-group user-configured-service-group
To copy the active service group to the user configured service group, use the ivr copy active-service-group user-configured-service-group command in EXEC mode.
ivr copy active-service-group user-configured-service-group
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
None.
Examples
The following example copies the active service group to the user defined service group.
switch# ivr copy active-service-group user-configured-service-groupSuccessfully copied active service group to user-configured service group databaseRelated Commands
clear ivr service-group database
Clears the IVR service group database.
show ivr service-group
Displays IVR service groups.
ivr copy active-topology user-configured-topology
To copy the active inter-VSAN routing (IVR) VSAN topology to the user configured topology, use the ivr copy active-topology user-configured-topology command in EXEC mode.
ivr copy active-topology user-configured-topology
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
The ivr copy active-topology user-configured-topology command is useful if you need to edit the active IVR topology, which is not allowed. Instead you copy the active IVR topology to the user configured topology, and then edit the user configured topology.
Examples
The following example copies the active IVR topology to the user configured topology.
switch# ivr copy active-topology user-configured-topologySuccessfully copied active VSAN-topology to user-configured topology databaseRelated Commands
ivr copy active-zoneset full-zoneset
To copy the active zone set to the full zone set, use the ivr copy active-zoneset full-zoneset command in EXEC mode.
ivr copy active-zoneset full-zoneset
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
Copying the active zone set to the full zone set may overwrite common zone and zone set configurations in the full zoning database.
Examples
The following example copies the active zone set to the full zone set.
switch# ivr copy active-zoneset full-zonesetWARNING: This command may overwrite common zones/zonesetsin the IVR full zoneset databasePlease enter yes to proceed.(y/n) [n]?Related Commands
ivr copy auto-topology user-configured-topology
To copy the automatically discovered inter-VSAN routing (IVR) VSAN topology to the user configured topology, use the ivr copy auto-topology user-configured-topology command in EXEC mode.
ivr copy auto-topology user-configured-topology
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC configuration mode.
Command History
Usage Guidelines
After using the ivr copy auto-topology user-configured-topology command to copy the automatically discovered VSAN topology into the user configured topology you must use the ivr commit command to apply the pending configuration changes to the IVR topology using Cisco Fabric Services (CFS) distribution.
Examples
The following example copies the automatically discovered VSAN topology into the user configured topology.
switch# ivr copy auto-topology user-configured-topologyRelated Commands
ivr distribute
To enable Cisco Fabric Services (CFS) distribution for Inter-VSAN Routing (IVR), use the ivr distribute command. To disable this feature, use the no form of the command.
ivr distribute
no ivr distribute
Syntax Description
This command has no other arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
None.
Examples
The following example shows how to enable IVR fabric distribution.
switch# config terminalswitch(config)# ivr distributeRelated Commands
ivr commit
Commits temporary IVR configuration changes to the active configuration.
show ivr
Displays IVR CFS distribution status and other details.
ivr enable
To enable the Inter-VSAN Routing (IVR) feature, use the ivr enable command in configuration mode. To disable this feature, use the no form of the command.
ivr enable
no ivr enable
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
The IVR feature must be enabled in all edge switches in the fabric that participate in the IVR.
The configuration and display commands for the IVR feature are only available when IVR is enabled on a switch.
When you disable this configuration, all related configurations are automatically discarded.
Note
Examples
The following command enters the configuration mode and enables the IVR feature on this switch.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr enableRelated Commands
ivr fcdomain database autonomous-fabric-num
To create IVR persistent FC IDs, use the ivr fcdomain database autonomous-fabric-num command. To delete the IVR fcdomain entry for a given AFID and VSAN, use the no form of the command.
ivr fcdomain database autonomous-fabric-num afid-num vsan vsan-id
no ivr fcdomain database autonomous-fabric-num afid-num vsan vsan-id
Syntax Description
afid-num
Specifies the current AFID. The range is 1 to 64.
vsan vsan-id
Specifies the current VSAN. The range is 1 to 4093.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This configuration only takes effect when NAT mode is enabled.
Examples
The following example shows how to enter IVR fcdomain database configuration submode for AFID 10 and VSAN 20.
switch# config tswitch(config)# ivr fcdomain database autonomous-fabric-num 10 vsan 20switch(config) fcdomain#The following example shows how to delete all persistent FC ID database entries for AFID 10 and
VSAN 20.switch# config tswitch(config)# no ivr fcdomain database autonomous-fabric-num 10 vsan 20Related Commands
ivr nat
To explicitly enable Network Address Translation (NAT) functionality for Inter-VSAN Routing (IVR), use the ivr nat command in configuration mode. To disable this feature, use the no form of the command.
ivr nat
no ivr nat
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
The ivr nat command allows you to explicitly enable NAT functionality of IVR. Upgrading to SAN-OS Release 2.x from SAN-OS Release 1.3.x does not automatically enable the Fibre Channel NAT functionality. This command also allows you to continue to operate in non-NAT mode even in SAN-OS Release 2.x and later.
Note
Examples
The following example shows how to explicitly enable NAT functionality for IVR.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr natRelated Commands
ivr refresh
To refresh devices being advertised by Inter-VSAN Routing (IVR), use the ivr refresh command in EXEC mode.
ivr refresh
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
None.
Examples
The following example shows refresh devices being advertised by IVR.
switch# ivr refreshRelated Commands
ivr enable
Enables the Inter-VSAN Routing (IVR) feature.
ivr withdraw domain
Withdraws an overlapping virtual domain from a specified VSAN.
ivr service-group activate
To activate an inter-VSAN routing (IVR) service group, use the ivr service-group activate command in configuration mode. To disable this feature, use the no form of the command.
ivr service-group activate [default-sg-deny]
no ivr service-group activate [default-sg-deny]
Syntax Description
Defaults
Deactivated.
Command Modes
Configuration mode.
Command History
Usage Guidelines
You must activate a configured IVR service group for the IVR service group to take effect. Once a configured IVR service group is activated, it replaces the currently activated service group, if there is one.
Activating an IVR service group with the default-sg-deny option sets the default service group policy to deny. To change the default service group policy to allow, issue the ivr service-group activate command again, but without the default-sg-deny option.
Examples
The following example activates the default IVR service group:
switch# config terminalswitch(config)# ivr service-group activateThe following example sets the default IVR service group policy to deny:
switch# config terminalswitch(config)# ivr service-group activate default-sg-denyThe following example disables the default service group:
switch# config terminalswitch(config)# no ivr service-group activateRelated Commands
ivr service-group name
To configure an Inter-VSAN Routing (IVR) service group, use the ivr service-group name command in configuration mode. To disable this feature, use the no form of the command.
ivr service-group name service-group
no ivr service-group name service-group
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
In a complex network topology, you might only have a few IVR-enabled VSANs. To reduce the amount of traffic to non-IVR-enabled VSANs, you can configure a service group that restricts the traffic to the IVR-enabled VSANs. A service group is a combination of AFIDs and VSANs. Up to 16 service groups can be configured. A VSAN or AFID can belong to just one service group. When a new IVR-enabled switch is added to the network, you must update the service group to include the new VSANs.
There can be a maximum of 128 AFID/VSAN combinations in all service group. However, all 128 combinations can be in one service group.
The default service group ID is 0. The default service group is for all VSANs that are not a part of a user-defined service group.
Before configuring an IVR service group, you must enable the following:
•
•
•
Using the autonomous-fabric-id (IVR topology database configuration) command, you can restrict the IVR traffic to the AFIDs and VSANs configured in the service group.
Examples
The following example shows how to configure an IVR service group and change to IVR service group configuration mode.
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr enableswitch(config)# ivr vsan-topology autoswitch(config)# ivr service-group name serviceGroup1switch(config-ivr-sg)#Related Commands
ivr enable
Enables the Inter-VSAN Routing (IVR) feature
ivr vsan-topology auto
Enables automatic discovery of the IVR topology.
show ivr
Displays IVR feature information.
ivr virtual-fcdomain-add
To add the Inter-VSAN Routing (IVR) virtual domains in a specific VSAN(s) to the assigned domains list in that VSAN, use the ivr virtual-fcdomain-add command. To delete the IVR virtual domains, use the no form of the command.
ivr virtual-fcdomain-add vsan-ranges vsan-range
no ivr virtual-fcdomain-add vsan-ranges vsan-range
Syntax Description
vsan-ranges vsan-range
Specifies the IVR VSANs or range of VSANs. The range of values for a VSAN ID is 1 to 4093.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
Use the no ivr virtual-fcdomain-add command to remove the currently active domains from the fcdomain manager list in a specified VSAN.
Examples
The following command adds the IVR virtual domains in VSAN 1.
switch# config terminalswitch(config)# ivr virtual-fcdomain-add vsan-ranges 1The following command reverts to the factory default of not adding IVR virtual domains.
switch# config terminalswitch(config)# ivr virtual-fcdomain-add vsan-ranges 1Related Commands
show ivr virtual-fcdomain-add-status
Displays the configured VSAN topology for a fabric.
ivr withdraw domain
Removes overlapping domains.
ivr virtual-fcdomain-add2
To configure the request domain_ID (RDI) mode in a specific autonomous fabric ID (AFID) and VSAN for all IVR-enabled switches, use the ivr virtual-fcdomain-add2 command. To delete the RDI mode, use the no form of the command.
ivr virtual-fcdomain-add2 autonomous-fabric-id value vsan-ranges value
no ivr virtual-fcdomain-add2 autonomous-fabric-id value vsan-ranges value
Syntax Description
fabric-id value
Specifies the fabric ID on which the RDI mode needs to be configured.
vsan-ranges value
Specifies the VSAN range value on which the RDI mode needs to be configured.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This is a CFS distributable command.
Examples
The following example configures the RDI mode on a specific AFID and VSAN.
switch# configEnter configuration commands, one per line. End with CNTL/Z.switch# ivr virtual-fcdomain-add2 autonomous-fabric-id 1 vsan-ranges 2switch# fabric is now locked for configuration. Please 'commit' configuration when done.switch(config)# ivr commitRelated Commands
show ivr virtual-fcdomain-add-status2
Displays the RDI mode in a specific AFID and VSAN for all IVR-enabled switches.
ivr vsan-topology
To configure manual or automatic discovery of the Inter-VSAN Routing (IVR) topology, use the ivr vsan-topology command in configuration mode.
ivr vsan-topology {activate | auto}
Syntax Description
activate
Configures manual discovery of the IVR topology and disables automatic discovery mode.
auto
Configures automatic discovery of the IVR topology.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command you must first enable IVR using the ivr enable command and configure the IVR database using the ivr vsan-topology database command.
Caution
Examples
The following ivr vsan-topology activate command activates the VSAN topology database:
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr enableswitch(config)# ivr vsan-topology databaseswitch(config-ivr-topology-db)# autonomous-fabric-id 1 switch 20:00:00:00:30:00:3c:5e vsan-ranges 2,2000switch(config)# ivr vsan-topology activateThe following command enables VSAN topology database auto mode, which allows the switch to automatically discover the IVR topology.
switch(config)# ivr vsan-topology autoRelated Commands
ivr vsan-topology database
To configure an Inter-VSAN Routing (IVR) topology database, use the ivr vsan-topology database command in configuration mode. To delete an IVR topology database, use the no form of the command.
ivr vsan-topology database
no ivr vsan-topology database
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
To use this command you must first enable IVR using the ivr enable command.
You can have up to 64 VSANs (or 128 VSANs as of Cisco MDS SAN-OS Release 2.1(1a)) in an IVR topology. Specify the IVR topology using the following information:
•
•
•
Note
Caution
The no ivr vsan-topology database command only clears the configured database, not the active database. You can only delete the user-defined entries in the configured database. Auto mode entries only exist in the active database.
Examples
The following command enters configuration mode, enables the IVR feature, enters the VSAN topology database, and configures the pWWN-VSAN association for VSANs 2 and 2000:
switch# config terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr enableswitch(config)# ivr vsan-topology databaseswitch(config-ivr-topology-db)# autonomous-fabric-id 1 switch 20:00:00:00:30:00:3c:5e vsan-ranges 2,2000Related Commands
ivr withdraw domain
To withdraw overlapping virtual domain from a specified VSAN, use the ivr withdraw domain command in EXEC mode.
ivr withdraw domain domain-id vsan vsan-id
Syntax Description
domain-id
Specifies the domain id. The range is 1 to 239.
vsan vsan-id
Specifies the VSAN ID. The range is 1 to 4093.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
When you enable the ivr virtual-fcdomain-add command, links may fail to come up due to overlapping virtual domain identifiers. If so, temporarily withdraw the overlapping virtual domain from that VSAN using the ivr withdraw domain command in EXEC mode.
Examples
The following command withdraws overlapping domains.
switch# ivr withdraw domain 10 vsan 20Related Commands
show ivr virtual-fcdomain-add-status
Displays the configured VSAN topology for a fabric.
ivr zone name
To configure a zone for Inter-VSAN Routing (IVR), use the ivr zone name command. To disable a zone for IVR, use the no form of the command.
ivr zone name ivzs-name
no ivr zone name ivz-name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This command enters IVR zone configuration submode.
Examples
The following command enters the configuration mode, enables the IVR feature, creates an IVZ, and adds a pWWN-VSAN member.
switch# config terminalswitch(config)# ivr enableswitch(config)# ivr zone name Ivz_vsan2-3switch(config-ivr-zone)# member pwwn 21:00:00:e0:8b:02:ca:4a vsan 3Related Commands
ivr zone rename
To rename an inter-VSAN routing (IVR) zone, use the ivr zone rename command.
ivr zone rename current-name new-name
Syntax Description
current-name
Specifies the current zone name. The maximum size is 64 characters.
new-name
Specifies the new zone name. The maximum size is 64 characters.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
None.
Examples
The following example renames the IVR zone from east to west.
switch# ivr zone rename east westRelated Commands
ivr zone name
Creates and configures an IVR zone.
show ivr
Displays IVR information.
ivr zoneset
To configure a zoneset for Inter-VSAN Routing (IVR), use the ivr zoneset command. To revert to the factory defaults, use the no form of the command.
ivr zoneset {activate name ivzs-name [force] | name ivzs-name}
no ivr zoneset {activate name ivzs-name [force] | name ivzs-name}
Syntax Description
activate
Activates a previously-configured IVZS.
force
Forces a IVZS activation
name ivzs-name
Specifies the IVZS name. Maximum length is 59 characters.
Defaults
None.
Command Modes
Configuration mode.
Command History
Usage Guidelines
This command enters IVR zoneset configuration submode.
Examples
The following command enters the configuration mode, enables the IVR feature, creates an IVZS, adds a IVZ member, and activates the IVZS.
switch# config terminalswitch(config)# ivr enableswitch(config)# ivr zoneset name Ivr_zoneset1switch(config-ivr-zoneset)# member Ivz_vsan2-3switch(config-ivr-zoneset)# exitswitch(config)# ivr zoneset activate name IVR_ZoneSet1Related Commands
ivr zoneset rename
To rename an inter-VSAN routing (IVR) zone set, use the ivr zoneset rename command.
ivr zoneset rename current-name new-name
Syntax Description
current-name
Specifies the current zone set name. The maximum size is 64 characters.
new-name
Specifies the new zone set name. The maximum size is 64 characters.
Defaults
None.
Command Modes
EXEC mode.
Command History
Usage Guidelines
None.
Examples
The following example renames the IVR zone set from north to south.
switch# ivr zoneset rename north southRelated Commands
ivr zoneset name
Creates and configures an IVR zone set.
show ivr
Displays IVR information.
