- New and Changed Information
- Preface
- A Commands
- Advanced Services Modules Commands
- B Commands
- C Commands
- Caching Services Module Commands
- CLI Overview
- 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
Cisco MDS 9000 Family Command Reference
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- July 13, 2014
Chapter: V Commands
V 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 to determine the appropriate mode for each command.
virtual-domain (SDV virtual device configuration submode)
To configure a persistent virtual domain, use the virtual-domain command in SDV virtual device configuration submode. To remove a persistent virtual domain, use the no form of the command.
Syntax Description
Specifies the persistent virtual domain. The range is 1 to 239 or 0x1 to 0xef. |
Defaults
Command Modes
SDV virtual device configuration submode.
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to configure a persistent virtual domain:
Related Commands
|
|
|
|---|---|
virtual-fcid (SDV virtual device configuration submode)
To configure a persistent virtual FC ID, use the virtual-fcid command in SDV virtual device configuration submode. To remove a persistent virtual FC ID, use the the no form of the command.
Syntax Description
Specifies the persistent virtual FC ID. The format is 0xhhhhhh, where h is a hexadecimal number. |
Defaults
Command Modes
SDV virtual device configuration submode.
Command History
|
|
|
Usage Guidelines
Examples
The following example shows how to configure a persistent virtual FC ID:
Related Commands
|
|
|
|---|---|
vrrp
To enable VRRP, use the vrrp command in configuration mode. Use the no form of the command to revert to the factory defaults or to negate a command.
vrrp ipv4-vr-group-number {address ip-address [ secondary ] | advertisement-interval seconds | authentication { md5 keyname spi index | text password } | preempt | priority value | shutdown | track interface { mgmt 0 | vsan vsan-id } ipv6 ipv6-vr-group-number {address ipv6-address | advertisement-interval centiseconds | preempt | priority value | shutdown | track interface { mgmt 0 | vsan vsan-id }} }
vrrp ipv4-vr-group-number address ip-address [ secondary ] | advertisement-interval seconds | authentication { md5 keyname spi index | text password } | preempt | priority value | shutdown | track interface { mgmt 0 | vsan vsan-id } ipv6 ipv6-vr-group-number {address ipv6-address | advertisement-interval centiseconds | preempt | priority value | shutdown | track interface { mgmt 0 | vsan vsan-id }} }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You enter the Virtual Router configuration submode to access the options for this command. From the VSAN or mgmt0 (management) interface configuration submode, enter vrrp number to enter the switch(config-if-vrrp)# prompt. By default, a virtual router is always disabled (shutdown). VRRP can be configured only if this state is disabled. Be sure to configure at least one IP address before attempting to enable a virtual router.
The total number of of VRRP groups that can be configured on a Gigabit Ethernet port, including main interfaces and subinterfaces, cannot exceed seven. This limitation applies to both IPv4 and IPv6 groups.
Note
If you configure secondary VRRP IPv6 addresses on an IPFC VSAN interface, you must remove the secondary VRRP IPv6 addresses before downgrading to a release prior to Cisco Release 3.0(1). This is required only when you configure IPv6 addresses.
Examples
The following example enables VRRP configuration:
The following example disables VRRP configuration:
The following example configures an IPv4 address for the selected VRRP:
Related Commands
|
|
|
|---|---|
Clears all the software counters for the specified virtual router. |
|
vsan (iSCSI initiator configuration and iSLB initiator configuration)
To assign an iSCSI or iSLB initiator to a VSAN other than the default VSAN, use the vsan command in iSCSI initiator configuration submode or iSLB initiator configuration submode. To disable this feature, use the no form of the command.
Syntax Description
Defaults
Command Modes
iSCSI initiator configuration submode.
iSLB initiator configuration submode.
Command History
|
|
|
|---|---|
Usage Guidelines
When you configure an iSLB initiator in a VSAN other than VSAN 1 (the default VSAN), the initiator is automatically removed from VSAN 1. For example, if you configure an iSLB initiator in VSAN 2 and you also want it to be present in VSAN 1, you must explicitly configure the initiator in VSAN 1.
Examples
The following example assigns an iSCSI initiator to a VSAN other than the default VSAN:
The following example assigns an iSLB initiator to a VSAN other than the default VSAN:
ips-hac2(config-islb-init)# vsan ?
ips-hac2(config-islb-init)# vsan 10
The following example removes the iSLB initiator:
Related Commands
vsan database
To create multiple fabrics sharing the same physical infrastructure, assign ports to VSANs, turn on or off interop mode, load balance either per originator exchange or by source-destination ID, and in order to be able to define these VSANs and specify the various VSAN attributes, use the vsan database command in the vsan database submode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following examples show how to create multiple fabrics sharing the same physical infrastructure and how to assign ports to VSANs:
Related Commands
|
|
|
|---|---|
Configures a WWN for a suspended VSAN that has interop mode 4 enabled. |
vsan interface
To add the interfaces to a VSAN, use the vsan interface command. Use the no form of this command to delete a configured role.
vsan vsan-id interface { fc slot / port | fcip fcip-id | fv slot / dpp-number / fv-port | iscsi slot / port | port-channel portchannel-number . subinterface-number }
no vsan vsan-id interface { fc slot / port | fcip fcip-id | fv slot / dpp-number / fv-port | iscsi slot / port | port-channel portchannel-number . subinterface-number }
Syntax Description
Defaults
Command Modes
Configuration mode—vsan database submode.
Command History
|
|
|
Usage Guidelines
You can configure a role so that it only allows commands to be performed for a selected set of VSANs. By default, the VSAN policy of a role is permit. In other words, the role can perform commands configured by the rule command in all VSANs. In order to selectively allow VSANs for a role, the VSAN policy needs to be set to deny and then the appropriate VSANs need to be permitted.
Examples
The following example show how to add the interfaces to a VSAN:
vsan interop
To specify the VSAN interoperability mode value, use the vsan interop command. Use the no form of this command to delete a configured role.
vsan vsan-id interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }]
no vsan vsan-id interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }]
Syntax Description
Defaults
Command Modes
Configuration mode—vsan database submode.
Command History
|
|
|
Usage Guidelines
You can configure a role so that it only allows commands to be performed for a selected set of VSANs. By default, the VSAN policy of a role is permit. In other words, the role can perform commands configured by the rule command in all VSANs. In order to selectively allow VSANs for a role, the VSAN policy needs to be set to deny and then the appropriate VSANs need to be permitted.
Examples
The following example shows how to specify the Interoperability mode value for Src-id/dst-id loadbalancing:
vsan loadbalancing
To configure the VSAN loadbalancing scheme, use the vsan loadbalancing command. Use the no form of this command to delete a configured role.
vsan vsan-id loadbalancing { src-dst-id | src-dst-ox-id }
no vsan vsan-id loadbalancing { src-dst-id | src-dst-ox-id }
Syntax Description
Defaults
Command Modes
Configuration mode—vsan database submode.
Command History
|
|
|
Usage Guidelines
You can configure a role so that it only allows commands to be performed for a selected set of VSANs. By default, the VSAN policy of a role is permit. In other words, the role can perform commands configured by the rule command in all VSANs. In order to selectively allow VSANs for a role, the VSAN policy needs to be set to deny and then the appropriate VSANs need to be permitted.
Examples
The following example shows how to configure loadbalancing scheme for a Src-id/dst-id loadbalancing:
vsan name
To assign a name to a VSAN, use the vsan name command. Use the no form of this command to delete a configured role.
vsan vsan-id name name [interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }] | loadbalancing { src-dst-id | src-dst-ox-id } | suspend [interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }]
no vsan vsan-id name name [interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }] | loadbalancing { src-dst-id | src-dst-ox-id } | suspend [interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }]
Syntax Description
Assigns a name to the VSAN. Maximum length is 32 characters. |
|
Defaults
Command Modes
Configuration mode—vsan database submode.
Command History
|
|
|
Usage Guidelines
You can configure a role so that it only allows commands to be performed for a selected set of VSANs. By default, the VSAN policy of a role is permit. In other words, the role can perform commands configured by the rule command in all VSANs. In order to selectively allow VSANs for a role, the VSAN policy needs to be set to deny and then the appropriate VSANs need to be permitted.
Examples
The following example shows how to assign a name to a VSAN:
vsan suspend
To suspend a VSAN, use the vsan suspend command. Use the no form of this command to delete a configured role.
vsan vsan-id suspend [interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }] src-dst-ox-id }]
no vsan vsan-id suspend [interop [ mode ] [ loadbalancing { src-dst-id | src-dst-ox-id }]
Syntax Description
Defaults
Command Modes
Configuration mode—vsan database submode.
Command History
|
|
|
Usage Guidelines
You can configure a role so that it only allows commands to be performed for a selected set of VSANs. By default, the VSAN policy of a role is permit. In other words, the role can perform commands configured by the rule command in all VSANs. In order to selectively allow VSANs for a role, the VSAN policy needs to be set to deny and then the appropriate VSANs need to be permitted.
Warning vsan suspend command done on an active VSAN is a very invasive command that requires a lot of supervisor processing. The supervisor is responsible for logging each device out, deprogramming ACLs, removing FCNS entries, generating RSCNs, etc. Because of this, care should be taken when doing this when there are many devices logged into the switch in the VSAN. After suspending the VSAN a minimum of 5 minutes should elapse prior to doing an no vsan suspend to ensure that all of the prior processing has completed.
Examples
The following example shows how to suspend a VSAN and enable interop mode 4:
vsan policy deny
To configure a VSAN-based role, use the vsan policy deny command in configuration mode. Use the no form of this command to delete a configured role.
vsan policy deny permit vsan vsan-id
no vsan policy deny permit vsan vsan-id
Syntax Description
Defaults
Command Modes
Configuration mode—role name submode.
Command History
|
|
|
Usage Guidelines
You can configure a role so that it only allows commands to be performed for a selected set of VSANs. By default, the VSAN policy of a role is permit. In other words, the role can perform commands configured by the rule command in all VSANs. In order to selectively allow VSANs for a role, the VSAN policy needs to be set to deny and then the appropriate VSANs need to be permitted.
Examples
The following example places you in sangroup role submode:
The following example changes the VSAN policy of this role to deny and places you in a submode where VSANs can be selectively permitted:
The following example deletes the configured VSAN role policy and reverts to the factory default (permit):
The following example permits this role to perform the allowed commands for VSANs 10 through 30:
The following example removes the permission for this role to perform commands for VSAN 15 to 20:
Feedback