FeedbackTable Of Contents
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 the "Command Modes" section to determine the appropriate mode for each command. For more information, refer to the Cisco MDS 9000 Family Configuration Guide.
in-order-guarantee
To enable in-order delivery in the Cisco MDS 9000 Family of switches, use the in-order-guarantee command in configuration mode. To disable in-order delivery, use the no form of the command.
in-order-guarantee
no in-order-guarantee
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
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.
switch## config tswitch(config)##switch(config)# in-order-guaranteeswitch(config)#switch(config)# no in-order-guaranteeswitch(config)#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 system URL kickstart URL
Syntax Description
install all
Upgrades the system.
system
Upgrades the system 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
This command was introduced in Cisco MDS SAN-OS Release 1.0(3).
Usage Guidelines
The install all command upgrades all modules in any Cisco MDS 9000 Family switch.
To copy a remote file, specify the entire remote path exactly as it is.
See the Cisco MDS 9000 Family 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.
sswitch# install all system bootflash:system_image kickstart bootflash:kickstart_imageVerifying image bootflash:/kickstart-image.bin[####################] 100% -- SUCCESSVerifying image bootflash:/system-image.bin[####################] 100% -- SUCCESSExtracting "slc" version from image bootflash:/system-image.bin.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/system-image.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/kickstart-image.bin.[####################] 100% -- SUCCESSExtracting "loader" version from image bootflash:/kickstart-image.bin.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------2 yes non-disruptive none5 yes non-disruptive none6 yes non-disruptive none9 yes non-disruptive noneImages will be upgraded according to following table:Module Image Running-Version New-Version Upg-Required------ ---------- -------------------- -------------------- ------------2 slc 1.2(1) 1.2(1) no2 bios v1.1.1(03/20/03) v1.1.1(03/20/03) no5 system 1.2(1) 1.2(1) no5 kickstart 1.2(1) 1.2(1) no5 bios v1.1.1(03/20/03) v1.1.1(03/20/03) no5 loader 1.0(3a) 1.0(3a) no6 system 1.2(1) 1.2(1) no6 kickstart 1.2(1) 1.2(1) no6 bios v1.1.1(03/20/03) v1.1.1(03/20/03) no6 loader 1.0(3a) 1.0(3a) no9 slc 1.2(1) 1.2(1) no9 bios v1.1.1(03/20/03) v1.1.1(03/20/03) noDo you want to continue with the installation (y/n)? [n] : yInstall is in progress, please wait.Syncing image bootflash:/kickstart-image.bin to standby.[####################] 100% -- SUCCESSSyncing image bootflash:/system-image.bin to standby.[####################] 100% -- SUCCESSPerforming configuration copy.[####################] 100% -- SUCCESSModule 5: Waiting for module online.-- SUCCESSInstall has been successful.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.71.00.000/home/user/golden-sanity/system-image kickstart scp://user@171.71.00.000/home/user/golden-sanity/kickstart-imageFor scp://user@171.71.00.000, please enter password:For scp://user@171.71.00.000, please enter password:Copying image from scp://user@171.71.00.000/tftpboot/kickstart-image to bootflash:///m9500-sf1ek9-kickstart-mzg.1.3.0.12b.bin.[####################] 100% -- SUCCESSCopying image from scp://user@171.71.00.000/tftpboot/system-image to bootflash:///m9500-sf1ek9-mzg.1.3.0.12b.bin.[####################] 100% -- SUCCESSVerifying image bootflash:///kickstart-image[####################] 100% -- SUCCESSVerifying image bootflash:///system-image[####################] 100% -- SUCCESSExtracting "slc" version from image bootflash:///system-image.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:///system-image.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:///kickstart-image.[####################] 100% -- SUCCESSExtracting "loader" version from image bootflash:///kickstart-image.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------2 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------ ---------- -------------------- -------------------- ------------2 slc 1.2(1) 1.3(1) yes2 bios v1.0.7(03/20/03) v1.0.7(03/20/03) no5 system 1.2(1) 1.3(1) yes5 kickstart 1.2(1) 1.3(1) yes5 bios v1.0.7(03/20/03) v1.0.7(03/20/03) no5 loader 1.0(3a) 1.0(3a) no6 system 1.2(1) 1.3(1) yes6 kickstart 1.2(1) 1.3(1) yes6 bios v1.0.7(03/20/03) v1.0.7(03/20/03) no6 loader 1.0(3a) 1.0(3a) noDo you want to continue with the installation (y/n)? [n] :yInstall is in progress, please wait.Syncing image bootflash:///kickstart-image to standby.[####################] 100% -- SUCCESSSyncing image bootflash:///system-image to standby.[####################] 100% -- SUCCESSPerforming configuration copy.[####################] 100% -- SUCCESSModule 6: Waiting for module online.-- SUCCESSSynchronizing with Firmbase...General Software Firmbase[r] SMM Kernel 1.1.1002 Oct 11 2002 13:36:57Copyright (C) 2002 General Software, Inc.Firmbase initialized.00000589K Low Memory Passed01045376K Ext Memory PassedWait.....(C) 2002 General Software, Inc.Pentium III-1.0-6E69-AA6EGeneral Software Pentium III Embedded BIOS 2000 (tm) Revision 1.0.(7)Copyright (C) 2002 General Software, Inc.MDS9000 BIOS design.+------------------------------------------------------------------------------+| System BIOS Configuration, (C) 2002 General Software, Inc. |+---------------------------------------+--------------------------------------+| System CPU : Pentium III | Low Memory : 630KB || Coprocessor : Enabled | Extended Memory : 1021MB || Embedded BIOS Date : 03/20/03 | ROM Shadowing : Enabled |+---------------------------------------+--------------------------------------+Loader Loading stage1.5.\Loader loading, please wait...Auto booting bootflash:/m9500-sf1ek9-kickstart-mzg.1.3.0.12b.bin bootflash:/m9500-sf1ek9-mzg.1.3.0.12b.bin...Booting kickstart image: bootflash:/m9500-sf1ek9-kickstart-mzg.1.3.0.12b.bin..........................................Image verification OKStarting kernel...INIT: version 2.78 bootingChecking all filesystems..... done.Loading system softwareUncompressing system image: bootflash:/m9500-sf1ek9-mzg.1.3.0.12b.binCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCINIT: Entering runlevel: 3MDS Switchswitch login: adminPassword:switch(standby)#Related Commands
install license
To program the supervisor or switching module BIOS, use the install module bios system command.
install license [ bootflash: | slot0: | volatile: ] file-name]}
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.2(1).
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-fileinstall module bios
To program the supervisor or switching module BIOS, use the install module bios system command.
install module module-number bios {system [bootflash: | slot0: | volatile: | system-image]}
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(3).
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 non disruptive 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
This command was introduced in Cisco MDS SAN-OS Release 1.2(1).
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 image
To program the supervisor or switching module image, use the install module image command.
install module module-number image kickstart [bootflash: | slot0: | volatile: | system-image]
Syntax Description
Defaults
None.
Command Modes
EXEC mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(3).
Usage Guidelines
The install module command only upgrades the system image on any module (other than the standby supervisor module). If error occur for any switching module, the module is reset and the new image is downloaded for that module.
If you are issuing this command on the supervisor module, follow these requirements:
•
Update the environment variables before issuing this command.
•
•
Examples
The following example shows how to perform a non disruptive upgrade for the system.
switch# install module 5 image system bootflash:system.imgBeginning the install check...bootflash:/system.img and kickstart image...is compatible.bootflash:/system.img image...can be upgraded non-disruptively from current.Preliminary install check done.Beginning the install process.Parsing of versioning database successful.Preparing file system plan now...Done.Preparing upgrade group plan now...Done.Executing pre-uninstall scripts...Done.Updating the File System for installation...Done.Executing post-install scripts...Done.System Manager will restart the services according to upgrade plan..Done.Installation completed successfully.Related Commands
show version compatibility
Shows the system software that is currently running on the switch
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
This command was introduced in Cisco MDS SAN-OS Release 1.0(3).
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
interface
To configure an interface on the Cisco MDS 9000 Family of switches, use the interface command in configuration mode. To disable an interface, use the no form of the command.
interface fc | mgmt | port-channel | sup-fc | vsan
no interface fc | mgmt | port-channel | sup-fc | vsan
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
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 displays the options for the interface command.
switch## config tswitch(config)# interface ?cpp Virtualization IPFC interfacefc Fiber Channel interfacefc-tunnel Fc-tunnel interfacefcip Fcip interfacegigabitethernet Ethernet interfaceiscsi ISCSI interfacemgmt Management interfaceport-channel Port Channel interfacesup-fc Inband Interfacevsan IPFC VSAN interfaceRelated Commands
interface fc
To configure a Fibre Channel interface on the Cisco MDS 9000 Family of switches, use the interface fc command. To disable a Fibre Channel interface, use the no form of the command.
interface fc slot_number [channel-group number force] | [ fcdomain rcf-reject vsan vsan-id] | [fspf cost link_cost vsan vsan-id | 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
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interface space fc1/1space-space5space,spacefc2/5space-space7
Examples
The following example configures ports 1 to 4 in Fibre Channel interface 9.
switch# config tEnter configuration commands, one per line. End with CNTL/Z.switch(config)# int fc9/1 - 4Related Commands
interface fc-tunnel
To configure a Fibre Channel interface on the Cisco MDS 9000 Family of switches, use the interface fc command. To disable a Fibre Channel interface, 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 [destination ip-address ] | [explicit-path path-name ] | [ source ip-address ]
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.2(1).
Usage Guidelines
None.
Examples
The following example initiates the FC tunnel (100) in the source switch (switch S).
switchS(config)# interface fc-tunnel 100switchS(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).
switchS(config-if)# destination 10.10.10.2The following example enables traffic flow through this interface. .
switchS(config-if)# no shutdownThe following example references the configured path in the source switch (switch S).
switchS# config tswitchS(config)# interface fc-tunnel 100switchS(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 nex-hop path.
interface fcip
To configure a Fibre Channel over IP Protocol (FCIP) interface on the Cisco MDS 9000 Family of switches, 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] exit | fcdomain rcf-reject vsan vsan-id | [fspf cost link_cost vsan vsan-id | dead-interval seconds vsan vsan-id | hello-interval seconds vsan vsan-id | passive vsan vsan-id | retransmit-interval seconds vsan vsan-id] | no | passive-mode | [peer-info ipaddress address | port number] | | special-frame peer-wwn pwwn-id | tcp-connection number | [time-stamp | acceptable-diff number] | use-profile profile-id
no interface fcip interface_number bport | bport-keepalives | [channel-group number | force] exit | fcdomain rcf-reject vsan vsan-id [fspf cost link_cost vsan vsan-id | dead-interval seconds vsan vsan-id | hello-interval seconds vsan vsan-id | passive vsan vsan-id | retransmit-interval seconds vsan vsan-id] | no | passive-mode | [peer-info ipaddress address | port number] | special-frame peer-wwn pwwn-id | tcp-connections number | [time-stamp | acceptable-diff number] | use-profile profile-id
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interface space fcip space1space-space5space,spacefc2/5space-space7
Examples
switch# config tEnter configuration commands, one per line. End with CNTL/Z.switch(config)# interface fcip 1switch(config-if)#Related Commands
show interface fcip
Displays an interface configuration for a specified FCIP interface.
interface fc-tunnel
To configure a Fibre Channel tunnel and facilitate RSPAN traffic in the Cisco MDS 9000 Family of switches, use the interface fc-tunnel command. To remove a configured tunnel or revert to factory defaults, use the no form of the command.
interface fctunnel tunnel-id {destination destination-ip-address | explicit-path path-name | shutdown | source source-ip-address }
no interface fctunnel tunnel-id {destination destination-ip-address | explicit-path path-name | shutdown | source source-ip-address }
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
None.
Examples
switch(config)# interface fc-tunnel 100switch(config-if)# source 10.10.10.1switch(config-if)# destination 10.10.10.2switch(config-if)# no shutdownRelated Commands
show interface fc-tunnel
Displays an interface configuration for a specified FC tunnel.
interface fc switchport
To configure an interface on the Cisco MDS 9000 Family of switches, use the interface command in configuration mode.
interface fc slot-number {switchport beacon | description text | encap eisl | [fcrxbbcredit credit mode E | Fx] fcrxbbcredit default | switchport [fcrxbufsize size | mode auto (E | F | FL | Fx | SD | TL) | speed (1000 | 2000 | auto) | trunk allowed vsan vsan-id] | add [vsan number | all] | mode [auto | off | on]}
no interface fc slot-number {switchport beacon | description text | encap eisl | [fcrxbbcredit credit mode E | Fx] fcrxbbcredit default | switchport [fcrxbufsize size | mode auto (E | F | FL | Fx | SD | TL) | speed (1000 | 2000 | auto) | trunk allowed vsan vsan-id] | add [vsan number | all] | mode [auto | off | on]}
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
You can specify a range of interfaces by issuing a command with the following example format:
interface space fc1/1space-space5space,spacefc2/5space-space7
Examples
The following example changes to Configuration mode, configures a Fibre Channel interface, and configures switchport mode E for the specified BB credit.
switch## config tswitch(config)# interface fc1/1switch(config-if)# switchport fcrxbbcredit 2 mode ERelated Commands
interface mgmt
To configure a management interface on the Cisco MDS 9000 Family of switches, use the interface mgmt command in configuration mode. Use the no form of this command to negate the command or return it to its factory defaults.
interface mgmt number | ip | shutdown force | switchport description text [ vrrp vrrp_id]
nointerface mgmt number | ip | shutdown force | switchport description text [ vrrp vrrp_id]
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode. Issue interface mgmt commands from the config-interface (config-if) mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
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 tswitch(config)##switch(config)# interface mgmt 0switch(config-if)# ?Interface configuration commands:exit Exit from this submodeip [no] ip addressno Negate a command or set its defaultsshutdown Enable/disable an interfaceswitchport Configure switchport parametersvrrp [no] vrrp vr_id: Configure vrrp on this interfaceswitch(config-if)# exitswitch(config)#The following example shuts down the interface without using the force option:
switch# conf tswitch(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# conf tswitch(config-if)# shutdown forceRelated Commands
interface port-channel
To configure a port channel interface on the Cisco MDS 9000 Family of switches, use the interface port-channel command.
interface port-channel number [fcdomain rcf-reject vsan vsan-id] | fspf [cost link_cost | dead-interval seconds | hello-interval seconds | passive | retransmit-interval seconds] | shutdown | switchport
no interface port-channel number [fcdomain rcf-reject vsan vsan-id] | fspf [cost link_cost | dead-interval seconds | hello-interval seconds | passive | retransmit-interval seconds] | shutdown | switchport
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example enters configuration mode and configures a PortChannel interface.
switch## config tswitch(config)##switch(config)# interface port-channel 32switch(config-if)#Related Commands
interface vsan
To configure a VSAN interface on the Cisco MDS 9000 Family of switches, use the interface vsan command.
interface vsan vsan-id exit [ip | no ip] no | shutdown | [vrrp | no vrrp vr_id]
Syntax Description
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example configures a VSAN interface.
switch(config)# interface vsan 1switch(config-if)#Related Commands
ip access-group
To create an access group to use an access list, 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 group-name [ in | out ]
Syntax Description
Defaults
Groups are created for both ingress and egress traffic.
Command Modes
Interface mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.2(1).
Usage Guidelines
The access-group command controls access to an interface. Each interface can only be associated with one access list. The access group becomes active on creation.
We recommend creating all rules in an access list, before creating the access group that uses this access -list.
If you create an access group before an access-list, 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 create a different access-group for each type of traffic.
Examples
The following example creates an access group called SampleName for both the ingress and egress traffic (default)
switch(config-if)# ip access-group SampleNameThe following example deletes the access group called NotRequired.
switch(config-if)# no ip access-group NotRequiredThe following example creates an access group called SampleName (if it does not already exist) for ingress traffic.
switch(config-if)# ip access-group SampleName1 inThe following example deletes the access group called SampleName for ingress traffic.
switch(config-if)# no ip access-group SampleName1 inThe following example creates an access group called SampleName (if it does not already exist) for local egress traffic.
switch(config-if)# ip access-group SampleName2 outThe following example deletes the access group called SampleName for local egress traffic.
switch(config-if)# no ip access-group SampleName2 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 (ACL), use the ip access-list command in configuration mode. Use the no form of this command to negate a previously issued command or revert to factory defaults.
ip access-list list-number [ deny | permit ] ip-protocol source source-wildcard [ operator port-value ] destination destination-wildcard [ operator port port-value ] [ icmp-type icmp-value ] [established ] [ precedence precedence-value ] [ tos tos-value ] [ log ]
Syntax Description
Defaults
Denied.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.2(1).
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).
Examples
The following example configures the an IP-ACL called List 1 and permits IP traffic from any source address to any destination address
switch# config tswitch(config)# ip access-list List1 permit ip any anyThe following example removes the IP-ACL called List 1.
switch# config tswitch(config)# no ip access-list List1 permit ip any anyThe following example updates List 1 to deny TCP traffic from any source address to any destination address.
switch# config tswitch(config)# ip access-list List1 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 tswitch(config)# ip access-list List1 permit udp 192.168.32.0 0.0.7.255The following example permits all IP traffic from and to the specified networks.
switch# config tswitch(config)# ip access-list List1 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 tswitch(config)# ip access-list List2 deny tcp 1.2.3.0 0.0.0.255 eq port 5 anyThe following example rmoves this entry from the IP-ACL.
switch# config tswitch(config)# no ip access-list List2 deny tcp 1.2.3.0 0.0.0.255 eq port 5 anyThe following example creates an access group called SampleName for both the ingress and egress traffic (default).
switch# config tswitch(config)# interface mgmt0switch(config-if)# ip access-group SampleNameThe following example deletes the access group called NotRequired.
switch# config tswitch(config)# interface mgmt0switch(config-if)# no ip access-group SampleNameThe following example creates an access group called SampleName (if it does not already exist) for ingress traffic.
switch# config tswitch(config)# interface mgmt0switch(config-if)# ip access-group SampleName1 inRelated Commands
ip address
To assign the local IP address of a Gigabit Ethernet interface to the FCIP profile, use the ip address command.
ip address address
no ip address address
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode—fcip profile submode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
To create a FCIP profile, you must assign a local IP address of a Gigabit Ethernet interface to the FCIP profile.
Examples
switch## config tswitch(config)# fcip profile 5switch(config-profile)# ip address 10.5.1.1Related Commands
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
no ip default-gateway destination-ip-address
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following examples configures the IP default gateway to 1.1.1.4.
switch## config tswitch(config)##switch(config)# ip default-gateway 1.1.1.4switch(config)#Related 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
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following examples configures the IP address of the default network to 1.1.1.4.
switch## config tswitch(config)##switch(config)# ip default-network 1.1.1.4switch(config)#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
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example configures the IP domain list.
switch## config tswitch(config)##switch(config)# ip domain domain nameswitch(config)#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
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
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 domain name.
switch## config tswitch(config)##switch(config)# ip domain-lookupswitch(config)#ip domain-name
To configure a domain name, use the ip domain-name command in configuration mode.
ip domain-name domain name
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example configures a domain name.
switch## config tswitch(config)##switch(config)# ip domain-name domain nameswitch(config)#ip name-server
To configure a name server, use the ip name-server command in configuration mode.
ip name-server ip-address
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
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 tswitch(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-serverip route
To configure a static route, use the ip route command in configuration mode.
ip route ip-address subnet-mask [nexthop_ip-address] [ interface (mgmt 0 | vsan number) ] [distance distance-number]
Syntax Description
Defaults
None.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following examples shows how to configure a static route.
switch## config tswitch(config)##switch(config)# IP route 10.0.0.0 255.0.0.0 20.20.20.10 distance 10 interface vsan 1switch(config)#Related Commands
ip routing
To enable the IP forwarding feature, use the ip routing command in configuration mode.
ip routing
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.0(2).
Usage Guidelines
None.
Examples
The following example enables the IP forwarding feature.
switch## config tswitch(config)##switch(config)# ip routingswitch(config)#iscsi authentication
Use the iscsi authentication command to configure the default authentication method for iSCSI.
iscsi authentication chap | none
no iscsi authentication chap | none
Syntax Description
Defaults
CHAP or none.
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
By default, the MDS 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. To change back to the default setting use the no iscsi authentication command.
Examples
switch## config tswitch(config)# iscsi authentication chapswitch(config)# iscsi authentication noneRelated Commands
iscsi import target fc
To allow dynamic mapping of Fibre Channel targets, use the iscsi import target fc command.
iscsi import target fc
no iscsi import target fc
Syntax Description
iscsi
Configures iSCSI parameters.
import
Imports Fibre Channel targets to iSCSI domains.
targets
Configures targets to import to the iSCSI domain.
fc
Specifies Fibre Channel targets.
Defaults
Disabled
Command Modes
Configuration mode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
Usage Guidelines
This command directs iSCSI to dynamically import all Fibre Channel targets into iSCSI.
Examples
switch## config tswitch(config)# iscsi import target fcswitch(config)# no iscsi import target fcRelated 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.
iscsi initiator ip address ipaddress [static (nwwn wwn-id | pwwn wwn-id ) | system-assign number ] | vsan vsan-id ]
no iscsi initiator ip address ipaddress [static (nwwn wwn-id | pwwn wwn-id ) | system-assign number] | vsan vsan-id ]
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode—iSCSI-initiator submode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
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.
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 assign persistent WWNs to an iSCSI initiator or assign an iSCSI initiator into VSANs other than the default VSAN, use the iscsi initiator name command.
iscsi initiator name name [static (nwwn wwn-id | pwwn wwn-id ) | system-assign ] | vsan vsan-id ]
no iscsi initiator name name [static (nwwn wwn-id | pwwn wwn-id ) | system-assign ] | vsan vsan-id ]
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode—iSCSI-initiator submode
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
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.
Examples
The following command configures an iSCSI initiator using the iSCSI name of the initiator node.
switch(config)# iscsi initiator name iqn.1987-02.com.cisco.initiatorThe following command deletes the configured iSCSI initiator.
switch(config)# no iscsi initiator name iqn.1987-02.com.cisco.initiatorThe following command configures an iSCSI initiator. using the IP address of the initiator node.
switch(config)# iscsi initiator ip-address 10.50.0.0The following command deletes the configured iSCSI initiator.
switch(config)# no iscsi initiator ip-address 10.50.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 virtual-target name
To create a static iSCSI virtual target, use the iscsi virtual-target command.
iscsi virtual-target name name [advertise interface gigabitethernet interface-number | initiator name initiator-name | pwwn pwwn-id (secondary-pwwn secondary pwwn-id | fc-lun number iscsi-lun number | name initiator-name) | ip-address ip-address (ip-subnet) permit
no iscsi virtual-target name name [advertise interface gigabitethernet interface-number | initiator name initiator-name | pwwn pwwn-id (secondary-pwwn secondary pwwn-id | fc-lun number iscsi-lun number | name initiator-name) | ip-address ip-address (ip-subnet) permit
Syntax Description
Defaults
Disabled
Command Modes
Configuration mode.
Command History
This command was introduced in Cisco MDS SAN-OS Release 1.1(1).
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.
Don't 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.
One iSCSI target cannot contain more than one Fibre Channel target.
Examples
switch## config tswitch(config)# iscsi virtual-target name abc123switch(config-(iscsi-tgt))# ?ISCSI Virt-tgt Configuration:advertise Advertise virtual target on interfaces specifiedexit Exit from this submodeinitiator Allow iSCSI initiator access to this targetno Negate a command or set its defaultspWWN Enter the pWWN of the fc-targetThe 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-permitRelated Commands