Table Of Contents
S Commands
save aaa
save accesslist
save all
save fcip
save fcswitch
save scsirouter
save system
save vlan
scsirouter
scsirouter authentication
scsirouter cdbretrycount
scsirouter description
scsirouter enable
scsirouter failover
scsirouter lun reset
scsirouter password
scsirouter primary
scsirouter serverif
scsirouter slp enable
scsirouter target accesslist
scsirouter target crc
scsirouter target description
scsirouter target enable
scsirouter target {lunid | serial | wwpn} #?
scsirouter target lun lunid
scsirouter target lun serial
scsirouter target lun wwpn lun
scsirouter target maxcmdqueuedepth
scsirouter target profile
scsirouter target trespass
scsirouter target wwpn
scsirouter username
session-timeout
setup
setup access
setup cluster
setup fcip
setup iscsi-port
setup mgmt
setup netmgmt
setup scsi
setup time
slp findattrs
slp findsrvs
slp findsrvtypes
snmp-server
software http url
software http username
software proxy
software proxy url
software proxy username
software tftp
software version
ssh enable
ssh keygen
static iscsibinding interface autolearn
static iscsibinding interface index
S Commands
This chapter covers the following commands:
•
save aaa
•
save accesslist
•
save all
•
save fcip
•
save fcswitch
•
save scsirouter
•
save system
•
save vlan
•
scsirouter
•
scsirouter authentication
•
scsirouter cdbretrycount
•
scsirouter description
•
scsirouter enable
•
scsirouter failover
•
scsirouter lun reset
•
scsirouter password
•
scsirouter primary
•
scsirouter serverif
•
scsirouter slp enable
•
scsirouter target accesslist
•
scsirouter target crc
•
scsirouter target description
•
scsirouter target enable
•
scsirouter target {lunid | serial | wwpn} #?
•
scsirouter target lun lunid
•
scsirouter target lun serial
•
scsirouter target lun wwpn lun
•
scsirouter target maxcmdqueuedepth
•
scsirouter target profile
•
scsirouter target trespass
•
scsirouter target wwpn
•
scsirouter username
•
session-timeout
•
setup
•
setup access
•
setup cluster
•
setup fcip
•
setup iscsi-port
•
setup mgmt
•
setup netmgmt
•
setup scsi
•
setup time
•
slp findattrs
•
slp findsrvs
•
slp findsrvtypes
•
snmp-server
•
software http url
•
software http username
•
software proxy
•
software proxy url
•
software proxy username
•
software tftp
•
software version
•
ssh enable
•
ssh keygen
•
static iscsibinding interface autolearn
•
static iscsibinding interface index
save aaa
To save the current AAA settings to nonvolatile memory, use the save aaa command.
save aaa {filename | bootconfig}
Syntax Description
filename
|
The name of the file where the AAA configuration information will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the AAA settings to the bootable configuration, which is used when the storage router is restarted. If the storage router belongs to a cluster, the saved AAA settings will automatically be propagated to other members of that cluster.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Use the filename parameter to save the AAA configuration to a file. Configurations saved to a file can be moved between storage routers and can be restored at a later time.
The following information is saved:
•
The AAA authentication lists
•
The username database
•
All RADIUS server configuration information (including server groups)
•
All TACACS+ server configuration information (including server groups)
Note
In a cluster environment, AAA management functions are handled by a single storage router. To determine which storage router is performing AAA management functions, issue the show cluster command. If you issue the save aaa command from a storage router that is not performing AAA management functions, the CLI displays an informational message with the name of the node that is currently handling those functions.Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about operating the storage router in a cluster.
Examples
The following example saves the running AAA settings to the bootable configuration, used when the storage router is restarted:
[SN5428-2A]# save aaa bootconfig
The following example saves the running AAA settings to a file named aaa_SN5428-2A:
[SN5428-2A]# save aaa aaa_SN5428-2A
Related Commands
save accesslist
To save configuration data to nonvolatile memory for the named accesslist or for all access lists, use the save accesslist command.
save accesslist {name | all} {filename | bootconfig}
Syntax Description
name
|
The name of the access list to be saved.
|
all
|
Save all access lists.
|
filename
|
The name of the file where the running access list configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the access list from the running configuration to the bootable configuration, used when the storage router is restarted. If the storage router belongs to a cluster, the saved access list information will automatically be propagated to other members of that cluster.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Configurations saved to a file can be moved between storage routers, and can be restored at a later time.
There is a maximum of 100 access lists per storage router or per storage router cluster. There is a maximum of 200 access list identification entries across all access lists in the storage router or storage router cluster.
Note
In a cluster environment, access list management functions are handled by a single storage router. To determine which storage router is performing access list management functions, issue the show cluster command. If you issue the save accesslist command from a storage router that is not performing access list management functions, the CLI displays an informational message with the name of the node that is currently handling those functions. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about operating the storage router in a cluster.
Examples
The following example saves the current configuration for all access lists to the bootable configuration, used when the storage router is restarted:
[SN5428-2A]# save accesslist all bootconfig
The following example saves the access list fooList to a configuration file named fooList_SN5428-2A:
[SN5428-2A]# save accesslist fooList fooList_SN5428-2A
Related Commands
Command
|
Description
|
accesslist
|
Create an access list entity.
|
accesslist A.B.C.D/bits
|
Add IP addresses to an access list.
|
delete accesslist
|
Delete a specific access list entry or an entire access list.
|
delete savedconfig
|
Remove a saved configuration file from the storage router.
|
restore accesslist
|
Restore the named access list or all access lists from the named configuration file.
|
save aaa
|
Save the current AAA configuration information.
|
save all
|
Save all configuration information.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
save system
|
Save selected system configuration information.
|
save vlan
|
Save configuration information for the named VLAN or all VLANs.
|
scsirouter target accesslist
|
Associate an access list with a specific SCSI routing instance target or all targets.
|
show accesslist
|
Display the contents of the named access list or all access lists.
|
show savedconfig
|
List the contents of the savedconfig directory or the contents of the named configuration file.
|
save all
To save all of the storage router configuration data to nonvolatile memory, use the save all command.
save all {filename | bootconfig}
Syntax Description
filename
|
The name of the file where the configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the current running configuration information to the bootable configuration, used when the storage router is restarted. If the storage router belongs to a cluster, any saved cluster elements will automatically be propagated to other members of that cluster.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Depending on the deployment, the save all command saves AAA configuration, SCSI routing instances, FCIP instances, access lists, VLANs, global Fibre Channel (FC) settings and FC interface configurations, and selected system configuration information. Configurations saved to a file can be moved between storage routers and can be restored at a later time.

Note
In a cluster environment, all AAA, access list, password, and VLAN management functions are handled by a single storage router. To determine which storage router is performing these management functions, issue the show cluster command. If you issue the save all command from a storage router that is not performing these management functions, the CLI displays an informational message with the name of the node that is currently handling the functions. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about operating the storage router in a cluster.
Examples
The following example saves the current running configuration to the bootable configuration:
[SN5428-2A]# save all bootconfig
The following example saves the current running configuration to the file named SN5428-2A_03Nov2001. You may want to do this as a means of archiving the current running configuration of the storage router on a regular basis.
[SN5428-2A]# save all SN5428-2A_03Nov2001
Related Commands
Command
|
Description
|
delete savedconfig
|
Remove a saved configuration file from the storage router.
|
restore all
|
Restore the contents of the named configuration file into memory.
|
save aaa
|
Save current AAA configuration information.
|
save accesslist
|
Save configuration data for the named access list or for all access lists.
|
save fcip
|
Save configuration information for the named FCIP instance.
|
save fcswitch
|
Save all Fibre Channel configuration, including global configuration settings and zoning information.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
save system
|
Save selected system configuration information.
|
save vlan
|
Save configuration information for the named VLAN or all VLANs.
|
show savedconfig
|
List the contents of the savedconfig directory or the contents of the named configuration file.
|
save fcip
To save all configuration data associated with the named FCIP instance to nonvolatile memory, use the save fcip command.
save fcip {name | all} {filename | bootconfig}
Syntax Description
name
|
The name of the FCIP instance. Valid names are fcip1 and fcip2.
|
all
|
Save configuration data for all FCIP instances.
|
filename
|
The name of the file where the configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the FCIP instance from the running configuration to the bootable configuration, used when the storage router is restarted.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Maintenance
|
3.3.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Configurations saved to a file can be moved between storage routers and can be restored at a later time.
Examples
The following example saves all FCIP instances currently running on this storage router to the bootable configuration, used when the storage router is restarted:
[SN5428-2A]# save fcip all bootconfig
The following example saves the FCIP instance named fcip1 to the file named fcip_SN5428-2A:
[SN5428-2A]# save fcip fcip1 fcip_SN5428-2A
Related Commands
Command
|
Description
|
fcip
|
Create an FCIP instance.
|
fcip enable
|
Stop or start the named FCIP instance.
|
restore fcip
|
Restore the named SCSI routing instance from the named configuration file.
|
show fcip
|
Display configuration and operational information for the named FCIP instance.
|
save fcswitch
To save all of the configuration data for the storage router Fibre Channel (FC) interfaces to nonvolatile memory, use the save fcswitch command.
save fcswitch {filename | bootconfig}
Syntax Description
filename
|
The name of the file where the configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the FC configuration from the running configuration to the bootable configuration, used when the storage router is restarted.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.5.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Configurations saved to a file can be moved between storage routers and can be restored at a later time.
Examples
The following example saves all the FC configuration information to the bootable configuration, used when the storage router is restarted:
[SN5428-2A]# save fcswitch bootconfig
The following example saves all the FC configuration information to the file named fc_SN5428-2A:
[SN5428-2A]# save fcswitch fc_SN5428-2A
Related Commands
Command
|
Description
|
delete fcalias
|
Delete the named alias or the specified alias member.
|
delete zone
|
Delete the specified Fibre Channel zone or the specified member of the zone from the zoning database.
|
delete zoneset
|
Delete the specified zone from the zone set or to delete the entire named zone set from the zoning database.
|
fcalias
|
Create an alias entity for use in Fibre Channel zoning.
|
fcswitch domainid
|
Set the domain ID for the storage router, to be used for FC switched fabric zoning.
|
fcswitch dstov
|
Specify the amount of time the storage router is to wait for Fibre Channel Distributed Services.
|
fcswitch edtov
|
Specify an error detect timeout value for all Fibre Channel interfaces.
|
fcswitch fstov
|
Specify the fabric stability timeout value.
|
fcswitch interop-credit
|
Set the data buffer credit capacity for all FC ports.
|
fcswitch ratov
|
Specify a Fibre Channel resource allocation timeout value for the storage router.
|
fcswitch zoning autosave
|
Enable the storage router to save zoning changes received from switches in the fabric.
|
fcswitch zoning default
|
Select the level of communication between the storage router and devices in the fabric where there is no active zone set.
|
fcswitch zoning merge
|
Set zoning merge compliance.
|
interface fc? al-fairness
|
Enable the fairness algorithm on the named FC interface.
|
interface fc? fan-enable
|
Enable Fabric Address Notification (FAN) on the named FC interface.
|
interface fc? linkspeed
|
Set the transfer rate for the named FC interface.
|
interface fc? mfs-bundle
|
Enable Multi-Frame Sequence bundling for the named FC interface.
|
interface fc? type
|
Set the port type for the named FC interface.
|
restore fcswitch
|
Restore Fibre Channel configuration information from the named configuration file.
|
show fcalias
|
Display information about aliases and their members.
|
show fcswitch
|
Display global configuration information for storage router FC interfaces.
|
show fcswitch eport
|
Display FSPF protocol information.
|
show interface
|
Display operational and configuration information for the specified interface or all interfaces.
|
show zone
|
Display configuration and operational information for Fibre Channel fabric zones from the local zoning database.
|
show zoneset
|
Display configuration and operational information for Fibre Channel fabric zone sets.
|
zone
|
Create a Fibre Channel fabric zone.
|
zoneset
|
Create a Fibre Channel fabric zone set.
|
save scsirouter
To save all configuration data associated with the named SCSI routing instance to nonvolatile memory, use the save scsirouter command.
save scsirouter {name | all} {filename | bootconfig}
Syntax Description
name
|
The name of the SCSI routing instance.
|
all
|
Save configuration data for all SCSI routing instances.
|
filename
|
The name of the file where the configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the SCSI routing instance from the running configuration to the bootable configuration, used when the storage router is restarted.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Maintenance
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Configurations saved to a file can be moved between storage routers and can be restored at a later time.
In a cluster environment, the SCSI routing instance can only be saved on the node that is currently running that instance.
Examples
The following example saves all SCSI routing instances currently running on this storage router to the bootable configuration, used when the storage router is restarted:
[SN5428-2A]# save scsirouter all bootconfig
The following example saves the SCSI routing instance named foo to the file named foo_SN5428-2A:
[SN5428-2A]# save scsirouter foo foo_SN5428-2A
Related Commands
Commands
|
Description
|
delete savedconfig
|
Remove a saved configuration file from the storage router.
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save aaa
|
Save the current AAA configuration information.
|
save accesslist
|
Save configuration data for the named access list or all access lists.
|
save all
|
Save all configuration information.
|
save system
|
Save selected system configuration information.
|
save vlan
|
Save configuration information for the named VLAN or all VLANs.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
scsirouter target maxcmdqueuedepth
|
Specify the maximum number of commands allowed at any given time from each iSCSI session to the specified target.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show savedconfig
|
List the contents of the savedconfig directory or the contents of the named configuration file.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
save system
To save selected system configuration information to nonvolatile memory, use the save system command.
save system {filename | bootconfig}
Syntax Description
filename
|
The name of the file where the system configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the current running system configuration to the bootable configuration, used when the storage router is restarted.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Configurations saved to a file can be moved between storage routers and can be restored at a later time.
The following system configuration data is saved:
•
Monitor and Administrator passwords
•
Administrative contact information
•
Network Time Protocol (NTP) server name
•
Primary and optional secondary Domain Name Server (DNS)
•
Default location for downloading storage router software
•
System and cluster name
•
Management and high availability (HA) interface addresses
•
Static routes
•
RIP settings
•
SNMP settings
•
CDP settings
•
Restrict settings
•
IP address of remote syslog host for logging
•
Logging table
•
Configuration information for the Gigabit Ethernet interfaces
•
Management session timeout value
•
Secure Shell (SSH) settings
Examples
The following example saves the current system configuration to the bootable configuration, used when the storage router is restarted:
[SN5428-2A]# save system bootconfig
The following example copies the current system configuration to the file named sys_SN5428-2A:
[SN5428-2A]# save system sys_SN5428-2A
Related Commands
Commands
|
Description
|
delete savedconfig
|
Remove a saved configuration file from the storage router.
|
hostname
|
Specify the storage router system name.
|
restore system
|
Restore selected system information from the named configuration file.
|
save aaa
|
Save the current AAA configuration information.
|
save accesslist
|
Save configuration data for the named access list or all access lists.
|
save all
|
Save all configuration information.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
save vlan
|
Save configuration information for the named VLAN or all VLANs.
|
show savedconfig
|
List the contents of the savedconfig directory or the contents of the named configuration file.
|
show system
|
Display selected system information, including system name.
|
save vlan
To save VLAN and VTP configuration information for the specified VLAN or for all VLANs to nonvolatile memory, use the save vlan command.
save vlan {vid | all} {filename | bootconfig}
Syntax Description
vid
|
The VLAN identification number of the VLAN configuration to be saved.
|
all
|
Save all VLANs associated with this storage router.
|
filename
|
The name of the file where the current VLAN configuration data will be written. This file is stored in the savedconfig directory.
|
bootconfig
|
Save the current VLAN configuration to the system's bootable configuration, to be used when the storage router is restarted. If the storage router belongs to a cluster, the saved VLAN information will automatically be propagated to other members of that cluster.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
You must save configuration data from the running configuration to the bootable configuration for it to be retained in the storage router when it is restarted. Configurations saved to a file can be moved between storage routers and can be restored at a later time.
VTP mode and domain information is saved, along with the specified VLAN configuration information.
Note
In a cluster environment, VLAN management functions are handled by a single storage router. To determine which storage router is performing VLAN management functions, issue the show cluster command. If you issue the save vlan command from a storage router that is not performing VLAN management functions, the CLI displays an informational message with the name of the node that is currently handling those functions. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about operating the storage router in a cluster.
Examples
The following example saves the current configuration for all VLANs to the system's bootable configuration, to be used when the storage router is restarted:
[SN5428-2A]# save vlan all bootconfig
The following example saves VLAN 12 to the file named vlanbackup:
[SN5428-2A]# save vlan 12 vlanbackup
Related Commands
Command
|
Description
|
restore vlan
|
Restore VLAN configuration information from the named configuration file.
|
save aaa
|
Save current AAA configuration information.
|
save accesslist
|
Save configuration data for the named access list or all access lists.
|
save all
|
Save all configuration information.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
save system
|
Save selected system configuration information.
|
show savedconfig
|
List the contents of the savedconfig directory or the contents of the named configuration file.
|
show vlan
|
Display configuration and operational information for the specified VLAN or all VLANs.
|
slp findattrs
|
Display configuration and operational information for VTP.
|
vlan
|
Configure a non-VTP VLAN on the storage router.
|
vtp domain
|
Assign a VTP domain name to the storage router.
|
vtp mode
|
Configure the storage router to operate in client or transparent VTP mode.
|
scsirouter
To create a SCSI routing instance, use the scsirouter command.
scsirouter name
Syntax Description
name
|
The name of the SCSI routing instance created by this command. Enter a maximum of 31 characters.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
SCSI routing is the routing of SCSI requests and responses between IP hosts in an IP network and storage devices in a Fibre Channel storage network. The SCSI routing instance becomes a binding point for the association of other configuration parameters. A SCSI routing instance provides IP hosts access to Fibre Channel storage.
There can be a maximum of 12 SCSI routing instances defined per storage router; if the storage router is a member of a cluster, no more than 12 instances can be defined across the cluster.
Note
If the storage router is deployed for transparent SCSI routing, there can be only one SCSI routing instance. The SCSI routing instance is named transparent and is automatically created during initial system configuration.
Examples
The following command creates a SCSI routing entity named myCompanyWebserver2.
[SN5428-2A]# scsirouter myCompanyWebserver2
Related Commands
Command
|
Description
|
accesslist
|
Create an access list entity.
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
failover scsirouter
|
Cause the named SCSI routing instance to cease running on the storage router.
|
restore accesslist
|
Restore the named access list or all access lists from the named configuration file.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save accesslist
|
Save configuration data for the named access list or all access lists.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter authentication
|
Enable iSCSI authentication for the named SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter authentication
To enable iSCSI authentication using the specified AAA authentication services for the named SCSI routing instance, use the scsirouter authentication command.
scsirouter name authentication {listname | default | none}
Syntax Description
name
|
The name of this SCSI routing instance.
|
listname
|
Enable AAA authentication using the specified iSCSI authentication list.
|
default
|
Enable AAA authentication using the default iSCSI authentication list.
|
none
|
Disable AAA authentication for this SCSI routing instance.
|
Defaults
AAA authentication is disabled.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.5.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
Use the scsirouter authentication command to enable iSCSI authentication for IP hosts requesting access to storage using the named SCSI routing instance. AAA performs authentication using the services configured on the specified iSCSI authentication list. Use the aaa authentication iscsi command to configure the iSCSI authentication list.
Note
If authentication is enabled for a SCSI routing instance using the default iSCSI authentication list, but no AAA authentication list is available, AAA attempts to use the "local" authentication method. If a list other than default is specified and not available, AAA authentication will fail for the SCSI routing instance.
Examples
The following example enables iSCSI authentication for the SCSI routing instance named foo, using the default iSCSI authentication list:
[SN5428-2A]# scsirouter foo authentication default
The following example enables iSCSI authentication of the SCSI routing instance named foo2, using the iSCSI authentication list named testlab:
[SN5428-2A]# scsirouter foo2 authentication testlab
Related Commands
scsirouter cdbretrycount
To specify the number of times a failed command should be retried before returning an error on the CDB, use the scsirouter cdbretrycount command.
scsirouter name cdbretrycount nn
Syntax Description
name
|
The name of this SCSI routing instance.
|
nn
|
The number of CDB retries. nn is an integer from 0 to 512. The default value is 6. There is one second between retries.
|
Defaults
The number of CDB retries is 6, by default.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.3.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2. For the SN 5428, the default value was changed to 6 seconds.
|
Usage Guidelines
Use this command to change the number of times a failed CDB will be retried by the storage router before returning an error on the CDB. Retries occur every second. For example, with the default retry count value of 6, it would take 6 seconds before a failed command would be returned with an error.
If an intelligent storage array includes multiple paths between hosts and storage, lowering the CDB retry count value could change the triggering of failover situations.
Note
In a high availability cluster, the storage router may fail over a SCSI routing instance when some or all devices accessed through that instance cannot be reached, before the maximum number of CDB retries occurs.
Examples
The following example sets the CDB retry count value to 10:
[SN5428-2A]# scsirouter transparent cdbretrycount 10
Related Commands
Command
|
Description
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter description
To add user-defined identification information to the named SCSI routing instance, use the scsirouter description command.
scsirouter name description "user text"
Syntax Description
name
|
The name of this SCSI routing instance.
|
"user text"
|
User-defined identification information associated with this SCSI routing instance. If the string contains spaces, enclose it in quotes. Enter a maximum of 64 characters.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The scsirouter description command allows you to add a new description or change an existing description. Descriptions are site-specific.
Examples
The following example adds the description "Access to WebServer4 WebServer5" to the SCSI routing instance foo1:
[SN5428-2A]# scsirouter foo1 description "Access to WebServer4 WebServer5"
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter enable
To start the named SCSI routing instance on this storage router, use the scsirouter enable command. To stop the named SCSI routing instance, use the no form of this command.
scsirouter {name | all} enable
no scsirouter {name | all} enable
Syntax Description
name
|
The name of the SCSI routing instance to be started.
|
all
|
Start all SCSI routing instances on this storage router.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
SCSI routing instances are automatically started by the storage router during the creation process, when the storage router is restarted, and when they are failed over to another storage router in a cluster. Use this command to manually control the running state of SCSI routing instances; for example, when a SCSI routing instance is restored from a saved configuration file.
SCSI routing instances that are in a stopped state are not running anywhere in the cluster. To restart a stopped SCSI routing instance, use the scsirouter enable command. Use the all keyword to start all instances on the storage router. All instances previously stopped on this storage router or available instances not running elsewhere in the cluster will start on this node.
The SCSI routing instance can only be started from the storage router on which it was stopped. A stopped SCSI routing instance is no longer known to any other storage router in the cluster.
Use the scsirouter enable command to bring a restored SCSI routing instance into the running configuration. A restored instance must be started before you can make any additional configuration changes to that instance.
Examples
The following example starts the SCSI routing instance named foo2. This instance must have been previously stopped.
[SN5428-2A]# scsirouter foo2 enable
The following example stops all SCSI routing instances running on the storage router:
[SN5428-2A]# no scsirouter all enable
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
failover scsirouter
|
Cause the named SCSI routing instance to cease running on the storage router.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter primary
|
Identify a storage router as the preferred storage router to run the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter failover
To build a list of storage routers to be used for failover purposes, use the scsirouter failover command.
scsirouter name failover {primary | secondary} sysname
Syntax Description
name
|
The name of the SCSI routing instance.
|
primary sysname
|
The name of the storage router in the cluster. In case of failure, the specified SCSI routing instance will be failed over to this storage router.
|
secondary sysname
|
(Optional) The name of the storage router in the cluster. If the primary storage router in the list cannot run the SCSI routing instance, it will be failed over to this storage router.
Note Because a high availability cluster consists of two storage routers, this parameter is not used.
|
Defaults
None. By default, the HA failover list is not populated.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
Use the scsirouter failover command to build a list of storage routers that will be used during the failover process. If the specified SCSI routing instance fails over, the cluster attempts to start running the instance on the storage router designated as the primary in the HA failover list. If that storage router cannot run the SCSI routing instance, the cluster will attempt to start the instance on the storage router designated as the secondary in the HA failover list.
If there is no primary or secondary storage router on the HA failover list when the SCSI routing instance fails over, the cluster uses normal failover algorithms to determine where the SCSI routing instance should run.
The storage routers specified as primary and secondary should be active in the cluster when the command is issued. If the specified storage router is not currently active in the cluster, the setting will not take effect until the node is added to the cluster and the SCSI routing instance is restarted.
Use the clear scsirouter failover command to remove the current primary or secondary storage router from the HA failover list.
Note
This command causes the SCSI routing instance configuration information to be saved and all nodes in the cluster to be updated.
Examples
The following example builds the HA failover list for the SCSI routing instance named foo. The primary storage router in the HA failover list is SN5428-2A.
[SN5428-2A]# scsirouter foo failover primary SN5428-2A
Related Commands
Command
|
Description
|
clear scsirouter failover
|
Remove the designated primary or secondary storage router from the HA failover list for the specified SCSI routing instance.
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
failover scsirouter
|
Cause the named SCSI routing instance to cease running on the storage router.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter primary
|
Identify a storage router as the preferred storage router to run the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter lun reset
To specify that "LUN reset" rather than "clear task" commands will be sent to the storage resources opened by the specified SCSI routing instance, use the scsirouter lun reset command.
scsirouter name lun reset {yes | no}
Syntax Description
name
|
The name of the SCSI routing instance. The specified SCSI routing instance must be running.
|
yes
|
Send "lun reset" to storage resources when they are opened.
|
no
|
Send "clear task" to storage resources when they are opened.
|
Defaults
The default is to send "clear task" commands to storage resources.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
It is preferable to send "LUN reset" commands if the device supports them. The specified SCSI routing instance must be running.
Examples
The following example enables "LUN resets" to all storage resources opened by the SCSI routing instance foo2:
[SN5428-2A]# scsirouter foo2 lun reset yes
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter primary
|
Identify a storage router as the preferred storage router to run the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter password
To assign a password to a SCSI routing instance for iSCSI authentication purposes, use the scsirouter password command.
scsirouter name password {password-string | none}
Syntax Description
name
|
The name of the SCSI routing instance.
|
password-string
|
The password associated with the named SCSI routing instance. If the password is encrypted (starts with "9"), enter a maximum of 170 characters. If the password is unencrypted (starts with "0"), enter a maximum of 66 characters. If the password is entered as an unencrypted text string, enter a maximum of 64 characters.
|
none
|
Keyword, removing any existing iSCSI password assigned to the named SCSI routing instance.
|
Defaults
None.
Command Modes
Administrator
Command History
Release
|
Modification
|
3.2.1
|
This command was introduced.
|
Usage Guidelines
Use this command to assign a password to the SCSI routing instance for two-way iSCSI authentication. Two-way iSCSI authentication allows authentication of the IP host and also allows the IP host, acting as an iSCSI initiator, to require authentication of the SCSI routing instance, acting as an iSCSI target. The user name and password assigned to the SCSI routing instance are used by the IP host for iSCSI authentication purposes.
iSCSI authentication must be enabled for the named SCSI routing instance. If iSCSI authentication is not enabled, the user name and password assigned to the SCSI routing instance will not be used.
The following rules apply to passwords:
•
Passwords are entered in clear text. However, they are changed to "XXXXX" in the CLI command history cache, and are stored in the local username database in an encrypted format.
•
If the password contains embedded spaces, enclose it with single or double quotes.
•
After initial entry, passwords display in their encrypted format. Use the show scsirouter command to display the SCSI routing instance authentication information. The following is an example display:
SCSI Router Authentication Information
Router Authentication Username Password
---------- --------------- -------------- --------
zeus web1 zeus_lab1 9 ea9bb0c57ca4806d3555f3f78a4204177a
The initial "9" in the example display indicates that the password is encrypted.
•
You can re-enter an encrypted password using the normal scsirouter password command. Enter the encrypted password in single or double quotes, starting with 9 and a single space. For example, copying and pasting password "9 ea9bb0c57ca4806d3555f3f78a4204177a" from the example above into the scsirouter mars password command would assign the SCSI routing instance mars the same iSCSI password as the SCSI routing instance zeus. This functionality allows passwords to be restored from saved configuration files.
•
When entering a password, a zero followed by a single space indicates that the following string is not encrypted; 9 followed by a single space indicates that the following string is encrypted. To enter a password that starts with 9 or zero, followed by one or more spaces, enter a zero and a space and then enter the password string. For example, to enter the password "0 123" for the SCSI routing instance zeus, enter this command:
scsirouter zeus password "0 0 123"
To enter the password "9 73Zjm 5" for SCSI routing instance lab3, use this command:
scsirouter lab3 password `0 9 73Zjm 5'
Examples
The following example enables iSCSI authentication, using the default authentication list, for the SCSI routing instance named lab3 and assigns a user name of lab3-admin and a password of testing to the instance for two-way authentication:
[SN5428-2A]# scsirouter lab3 authentication default
*[SN5428-2A]# scsirouter lab3 username lab3-admin
*[SN5428-2A]# scsirouter lab3 password testing
Related Commands
Command
|
Description
|
scsirouter authentication
|
Enable iSCSI authentication for the named SCSI routing instance.
|
scsirouter username
|
Assign a user name to a SCSI routing instance for iSCSI authentication purposes.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter primary
To assign the specified system as the preferred storage router for the named SCSI routing instance, use the scsirouter primary command.
scsirouter name primary sysname
Syntax Description
name
|
The name of this SCSI routing instance.
|
primary sysname
|
The system name of the preferred storage router.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2. For the SN 5428, the none keyword was removed.
|
Usage Guidelines
At any given time, a SCSI routing instance can run on only one node in a cluster. If a SCSI routing instance has the primary attribute set, the specified storage router will take over running that instance upon system restart or whenever target and critical resources are available.
If the primary attribute is not set, the SCSI routing instance continues running on the node where it was started until it is explicitly stopped (via a no scsirouter enable command), it automatically fails over to another node in the cluster because targets or critical resources are unavailable, or an explicit failover scsirouter command is issued. This is the default behavior.
Use the scsirouter primary command if you always want the specified SCSI routing instance to run on a specific storage router in a cluster whenever that node is available (assuming target and critical resources are available). Use the clear scsirouter primary command to remove the currently configured primary value for the named SCSI routing instance.
Note
Setting the primary attribute saves the SCSI routing instance configuration and circulates those changes to the high availability cluster. If the specified storage router is available to the cluster and has all target and critical resources available, the SCSI routing instance will be immediately failed over. If the specified storage router is not available to the cluster, failover will occur as soon as that storage router becomes available to the cluster (assuming target and critical resources are available).
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about HA, cluster configuration, and managing SCSI routing instances in a cluster environment.
Examples
The following command designates the SN 5428-2 LabRouter1 as the storage router on which the SCSI routing instance named foo will always, under normal conditions, run.
[SN5428-2A]# scsirouter foo primary LabRouter1
Related Commands
Command
|
Description
|
clear scsirouter primary
|
Remove the storage router configured as the primary for the named SCSI routing instance.
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter failover
|
Add the storage router to the HA failover list for the specified SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter serverif
To assign a Gigabit Ethernet interface and IP address to the named SCSI routing instance, use the scsirouter serverif command. The specified interface allows IP hosts access to Fibre Channel storage.
scsirouter name serverif ge? {A.B.C.D/bits | A.B.C.D/1.2.3.4} [secondary ge?]
scsirouter name serverif ge? vlan vid {A.B.C.D/bits | A.B.C.D/1.2.3.4} [secondary ge?]
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the Gigabit Ethernet interface.
|
serverif ge?
|
The name of the interface. When you type the scsirouter serverif command, followed by ?, the CLI lists the interfaces available. You cannot specify a nonexistent interface.
|
A.B.C.D/bits
|
The IP address of the named interface. If the keyword vlan is used, the IP address is part of the specified VLAN. A.B.C.D is the dotted quad notation of the IP address. The /bits specifies the subnet mask in CIDR style.
Note The IP address must be on a unique subnet; you cannot configure an IP address that is on the same subnet as another storage router network interface.
|
A.B.C.D/1.2.3.4
|
The IP address of the named interface. If the keyword vlan is used, the IP address is part of the specified VLAN. A.B.C.D is the dotted quad notation of the IP address. 1.2.3.4 is the dotted quad notation of the subnet mask.
Note The IP address must be on a unique subnet; you cannot configure an IP address that is on the same subnet as another storage router network interface.
|
secondary ge?
|
(Optional) The name of the Gigabit Ethernet interface to be used as a secondary interface for the specified IP address. If the primary interface goes down and remains down for two seconds, the specified IP address will be moved to the secondary interface.
|
vlan vid
|
The keyword and the VLAN identifier.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The secondary keyword was added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The specified interface IP address is configured on IP hosts requiring access to storage resources through the storage router.
Each SCSI routing instance requires two active elements:
•
The serverif element assigns an interface and IP address for use by IP hosts requiring access to storage resources. The instance becomes active when this interface is added. A SCSI routing instance can have multiple serverif elements; one IP address per logical interface can be configured for a SCSI routing instance.
•
The target element is a complex item that specifies the mapping between LUNs on the storage devices and the host systems.
The scsirouter serverif vlan command is used to associate a VLAN with a SCSI routing instance. All traffic using the specified Gigabit Ethernet interface will be considered as part of the VLAN; all IP hosts accessing storage through the storage router using the specified Gigabit Ethernet interface IP address must connect as part of the specified VLAN.
When the SCSI routing instance is started, a logical interface (for example, ge2VLAN100) is created, which incorporates the physical interface and the VID. This logical interface can be displayed via the show interface command.
If the secondary keyword is used, both Gigabit Ethernet interfaces must be connected to the same network segment. If the primary interface goes down and remains down for two seconds, the IP address will be moved to the secondary interface.
Note
If you configure a Gigabit Ethernet IP address with a secondary interface, all Gigabit Ethernet IP addresses on the same subnet must also be configured with the same secondary interface.
Examples
The following command adds the Gigabit Ethernet interface ge1, with the IP address 10.1.10.128/24, to the SCSI routing instance named foo2.
[SN5428-2A]# scsirouter foo2 serverif ge1 10.1.10.128/24
The following command adds the Gigabit Ethernet interface ge2 and VLAN ID 45, with IP address 10.1.30.128/24, to the SCSI routing instance fooA. If the primary interface is not available, the IP address will be moved to the secondary Gigabit Ethernet interface, ge1. The Gigabit Ethernet interfaces must be connected to the same network.
[SN5428-2A]# scsirouter fooA serverif ge2 vlan 45 10.1.30.128/24 secondary ge1
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter slp enable
To enable the advertisement of the targets of the named SCSI routing instance with the Service Location Protocol (SLP) service, use the scsirouter slp enable command. To disable target advertisement, use the no form of this command.
scsirouter name slp enable
no scsirouter name slp enable
Syntax Description
name
|
Name of the SCSI routing instance. All targets associated with this SCSI routing instance are advertised with the SLP service.
|
Defaults
Advertising with the SLP Service is enabled for all targets.
Command Modes
Administrator.
Command History
Release
|
Modification
|
3.2.1
|
This command was introduced.
|
Usage Guidelines
SLP is an IP protocol designed to make it easy for network clients to discover available services on a network and to learn about the configuration of those services. By default, SLP advertisement is enabled when:
•
A SCSI routing instance is started by the storage router during the creation process.
•
The storage router is restarted.
•
A SCSI routing instance is failed over to another storage router in a cluster.
Use this command to manually disable and re-enable the advertisement of targets with the SLP service. When target advertisement is disabled, all existing targets for the specified SCSI routing instance are de-registered, and any new targets that are added will not be advertised.
Examples
The following example disables target advertisement for the SCSI routing instance named foo and deregisters all of its previously registered targets from the SLP service:
[SN5428-2A]# no scsirouter foo slp enable
The following example re-enables target advertisement for the SCSI routing instance named foo:
[SN5428-2A]# scsirouter foo slp enable
Related Commands
Command
|
Description
|
show slp
|
Display the status of the SLP service and the interface address where the SLP service is listening for incoming SLP service requests.
|
slp findattrs
|
Discover the attributes of a specific SLP registered service.
|
slp findsrvs
|
Locate a SLP registered service of a specific type on the local subnet.
|
slp findsrvtypes
|
Discover all SLP registered service types on the local subnet.
|
scsirouter target accesslist
To associate the named access list with the specified target, use the scsirouter target accesslist command.
scsirouter name target {name | all} accesslist {name | any | none} [ro | rw]
Syntax Description
name
|
The name of the SCSI routing instance to which this target belongs.
|
target name
|
The name of the storage target to associate with this access list. The target must already exist.
|
target all
|
Associate all targets with the named access list.
|
accesslist name
|
The name of the access list to associate with this storage target.
|
accesslist any
|
Allow connections and logins for the specified target from any IP host. This is effectively "open access."
|
accesslist none
|
Prevent any new connections or logins to this target from any IP hosts. This is effectively "no access."
|
ro
|
(Optional) Allow the IP hosts identified by the specified access list read-only device access.
|
rw
|
(Optional) Allow the IP hosts identified by the specified access list read/write device access. This is the default.
|
Defaults
If access type (read-only or read/write) is not specified, the default is read/write.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2. For the SN 5428, the ro and rw keywords were added.
|
Usage Guidelines
An access list identifies the IP hosts allowed to access the associated storage target through the storage router. IP hosts can be identified by IP address, CHAP user name, or iSCSI Name. Access lists are associated with specific storage targets. Each target can be associated with one access list that provides IP hosts read/write device access and one access list that provides read-only device access.
When an IP host attempts to access a storage resource, the storage router first looks for a matching entry using the access list configured to allow read/write device access. If the IP host does not have a matching entry in the read/write access list, the access list configured for read-only device access (if any) is used. If the IP host does not have a matching entry on either access list, the IP host is denied access to the storage resource.
Note
Some host operating systems impose restrictions on the use of read-only access lists. For details, see the readme files and Release Notes for Cisco iSCSI Driver for your IP host operating system.
•
Use the target all form of this command to create an association between the specified access list and all targets.
•
Use the reserved access list name none to remove any access list associations for the specified target. This effectively prevents access to this storage target from any IP host.
•
Use the reserved access list name any to allow access to this storage target from any IP host.This is effectively "open access."
•
Existing connections and logins are not affected by an access list change. However, if there are existing connections, the storage router issues a warning message with that information in response to this command.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Examples
The following example creates an association between the storage target webserver4 (accessed via SCSI routing instance foo) and the access list webserver2. By default, the IP hosts identified by the webserver2 access list will be allowed read/write device access to the target.
[SN5428-2A]# scsirouter foo target webserver4 accesslist webserver2
The following example provides the IP hosts identified in the access list named media read-only access to all targets accessed via SCSI routing instance LabA:
[SN5428-2A]# scsirouter LabA target all accesslist media ro
Note
Some host operating systems impose restrictions on the use of read-only access lists. For details, see the readme files and Release Notes for Cisco iSCSI Driver for your IP host operating system.
The following example provides the IP hosts identified by the access list webcheck read-only device access, and provides the IP hosts identified by access list webserver2 read/write device access, to the target webserver3:
[SN5428-2A]# scsirouter foo target webserver3 accesslist webcheck ro
Setting read-only accesslist to 'webcheck' for scsirouter 'foo' target 'webserver3
*[SN5428-2A]# scsirouter foo target webserver3 accesslist webserver2 rw
Setting read-write accesslist to 'webserver2' for scsirouter 'foo' target 'webserver3
Related Commands
Command
|
Description
|
accesslist
|
Create an access list entity.
|
accesslist A.B.C.D/bits
|
Add IP addresses to an access list.
|
accesslist chap-username
|
Add CHAP user name entries to an access list.
|
accesslist iscsi-name
|
Add iSCSI Name entries to an access list.
|
delete accesslist
|
Delete a specific access list entry or an entire access list.
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore accesslist
|
Restore the named access list or all access lists from the named configuration file.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save accesslist
|
Save configuration data for the named access list or all access lists.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
scsirouter primary
|
Identify a storage router as the preferred storage router to run the named SCSI routing instance.
|
scsirouter serverif
|
Assign a Gigabit Ethernet interface, IP address, and optionally a VLAN to the named SCSI routing instance.
|
scsirouter target crc
|
Control the usage of iSCSI cyclical redundancy check (CRC) on the specified target or all targets.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
show accesslist
|
Display the contents of the named access list or all access lists.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter target crc
To control the usage of iSCSI cyclical redundancy check (CRC) on the specified target or all targets, use the scsirouter target crc command.
scsirouter name target {name | all} crc {always | any | never | prefer-off | prefer-on}
Syntax Description
name
|
The name of the SCSI routing instance to which this target belongs.
|
target name
|
The name of the storage target.
|
target all
|
Apply the specified iSCSI CRC usage to all targets associated with this SCSI routing instance.
|
always
|
Always force iSCSI CRC on the target.
|
any
|
The target supports both CRC and non-CRC modes. The use of CRC is negotiated to the initiator preference.
|
never
|
The use of iSCSI CRC is disabled on this target.
|
prefer-off
|
The use of iSCSI CRC is not the preferred mode of operation for this target, but the target will negotiate the mode if CRC mode is the only mode supported by the initiator. This is the default setting.
|
prefer-on
|
The use of iSCSI CRC is the preferred mode of operation for this target, but the target will function in non-CRC mode if it is the only mode supported by the initiator.
|
Defaults
iSCSI CRC is not the preferred mode of operation for the target.
Command Modes
Administrator.
Command History
Release
|
Modification
|
3.2.1
|
This command was introduced.
|
Usage Guidelines
CRC codes are shortened cyclic codes used for error detection. A target configured for iSCSI CRC as the preferred mode of operation (prefer-on) opts for data integrity over performance. A target configured for non-CRC mode as the preferred mode of operation (prefer-off) opts for performance over data integrity.
Depending on the initiator and target configurations, the usage of iSCSI CRC is negotiated. Table 14-1 lists the CRC negotiation outcomes for each possible pair of CRC configurations.
Table 14-1 iSCSI CRC Negotiation Outcomes
Initiator CRC Mode
|
Target CRC Mode
|
CRC Negotiation Outcome
|
always
|
always
|
CRC is enabled.
|
| |
never
|
Negotiation is rejected. No session is established to the target.
|
| |
prefer-on
|
CRC is enabled.
|
| |
prefer-off
|
CRC is enabled.
|
| |
any
|
CRC is enabled.
|
never
|
always
|
Negotiation is rejected. No session is established to the target.
|
| |
never
|
CRC is disabled.
|
| |
prefer-on
|
CRC is disabled.
|
| |
prefer-off
|
CRC is disabled.
|
| |
any
|
CRC is disabled.
|
prefer-on
|
always
|
CRC is enabled.
|
| |
never
|
CRC is disabled.
|
| |
prefer-on
|
CRC is enabled.
|
| |
prefer-off
|
CRC is disabled.
|
| |
any
|
CRC is enabled.
|
prefer-off
|
always
|
CRC is enabled.
|
| |
never
|
CRC is disabled.
|
| |
prefer-on
|
CRC is enabled.
|
| |
prefer-off
|
CRC is disabled.
|
| |
any
|
CRC is disabled.
|
Examples
The following example configures the storage target webserver4, accessed through SCSI routing instanced foo, to always use iSCSI CRC:
[SN 5428-2A}# scsirouter foo target webserver4 crc always
The following example configures all storage targets accessed through SCSI routing instances lab2, to prefer the use of iSCSI CRC:
[SN 5428-2A}# scsirouter lab2 target all crc prefer-on
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter target accesslist
|
Associate an access list with a specific SCSI routing instance target or all targets.
|
scsirouter target enable
|
Allow or disallow connections and logins for the named target.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter target description
To add a description to the named target, use the scsirouter target description command.
scsirouter name target name description "user text"
Syntax Description
name
|
The name of the SCSI routing instance to which this target belongs.
|
target name
|
The name of the storage target.
|
"user text"
|
User-defined identification information associated with this storage target. If the description contains spaces, enclose the string in quotes. Enter a maximum of 64 characters.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
Target description information is an optional attribute of a SCSI routing instance. Use the show scsirouter command to display target description information.
Examples
The following example adds a description to the storage target webserver4, accessed through the SCSI routing instance foo:
[SN5428-2A]# scsirouter foo target webserver4 description "Web databases"
Related Commands
scsirouter target enable
To allow connections and logins for the named target, use the scsirouter target enable command. To disallow connections and logins for the named target, use the no form of this command.
scsirouter name target {name | all} enable
no scsirouter name target {name | all} enable [force]
Syntax Description
name
|
The name of the SCSI routing instance to which this target belongs.
|
target name
|
The name of the storage target.
|
target all
|
Allow connections for all targets of this SCSI routing instance to be enabled or disabled.
|
force
|
(Optional) Disable the target and forcibly remove any active iSCSI sessions.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
3.4.1
|
The force keyword was added.
|
Usage Guidelines
When you add a target to a SCSI routing instance, it is by default enabled. However, no access list is associated with the target, thus effectively preventing any access to the storage target from any IP hosts. When you associate an access list with a target, the specified connections and logins are allowed.
Use this command to control access without changing the target access list association.
Existing connections and logins are not affected by the no form of this command, but future connections and logins are not allowed. If existing IP hosts are connected, the storage router issues a warning message with that information in response to this command. Use the force keyword if you want to disable the target and forcibly remove any existing iSCSI sessions.
Use the reserved target name all to enable or disable connections for all targets of this SCSI routing instance.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Examples
The following example enables connections for all targets of the SCSI routing instance foo.
[SN5428-2A]# scsirouter foo target all enable
The following examples disables connections for the target webservices2 of the SCSI routing instance named lab2:
[SN5428-2A]# no scsirouter lab2 target webservices2 enable
Related Commands
scsirouter target {lunid | serial | wwpn} #?
To use an index method of mapping a logical target or a logical target and LUN combination to storage, use the scsirouter target {serial | lunid | wwpn} #? command. This command creates an indexed list of storage resources, assigning a unique index number to each LUN available. Specify the storage resources to map by using the appropriate index numbers.
scsirouter name target name wwpn #?
scsirouter name target name [lun nn] wwpn #?
scsirouter name target name lun nn {serial | lunid} #?
scsirouter name target name wwpn #nn [wwpn #nn]
scsirouter name target name lun nn wwpn #nn [wwpn #nn] [force]
scsirouter name target name lun nn {serial | lunid} #nn [force]
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the storage target.
|
target name
|
A user-specified name of the logical target. Enter a maximum of 31 characters or a valid iSCSI Name. There is a maximum of 100 targets per storage router or per high availability cluster.
|
lun nn
|
The LUN number associated with the logical target. The LUN number is optional if mapping to a World Wide Port Name (WWPN) address type. The LUN number is required if mapping to a serial number or LUN identifier.
|
#?
|
Request an indexed list of storage resources available on the Fibre Channel (FC) network.
|
serial
|
Use the serial number for the named storage resource. The storage resource must support unique serial numbers for each LUN.
|
wwpn
|
Use the World Wide Port Name (WWPN) address type for the named storage resource. You can specify a primary and optional secondary WWPN.
|
lunid
|
Use the unique LUN identifier, assigned when the LUN is discovered by the FC interface.
|
#nn
|
The index number from the displayed list. The storage resource listed after the number specified is the physical storage address to which the logical target or logical target and LUN combination is to be mapped.
|
force
|
(Optional) Keyword used to allow LUN-mapping of the same storage array control LUNs in multiple targets.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The lunwwn keyword was replaced by the lunid keyword and the force keyword was added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
This command can be used for target-only or target-and-LUN mapping.
When you map a target using WWPN and the target needs to be accessed in a high availability cluster, you must specify both the primary WWPN (the WWPN of the storage resource as known to the first storage router in the cluster) and the secondary WWPN (the WWPN of the storage resource as known to the second storage router in the cluster).
To display the indexed list of storage resources, use the number sign (#) character followed by a question mark (?). That action will cause a list of devices discovered on the FC network to display as a numbered (indexed) table. The original command is re-displayed at the prompt below the list to the point of the # keyword. Complete the command by entering the appropriate index number.
When a target is added, it is by default enabled. However, it is not associated with any access list ("accesslist none"), effectively disabling access to the target from any IP hosts. Use the scsirouter target accesslist command to enable access to this storage target for selected IP hosts. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about configuring SCSI routing instances on the storage router.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Use the force keyword to allow target-and-LUN mapping of the same storage array control LUN in multiple targets. Do not use the force keyword to LUN-map the same data LUN in multiple targets. LUN-mapping of the same LUN in multiple targets is advised for a control LUN on a storage controller only.
Examples
The following example displays an indexed list of storage resources available to SCSI routing instance lab2 and maps the logical target webserver8 to the WWPN storage address represented by index number 2.
[SN5428-2A]# scsirouter lab2 target webserver8 wwpn #?
Id I/F WWPN Lun Type Vendor Product
--- ----- --- ---------------- ----- ------ -------- ----------------
1 fc1 2200001026448a0d 0 Disk SEAGATE ST217340FC
2 fc1 22000003be3203bc 0 Disk SEAGATE ST217341FC
*[SN5428-2A]# scsirouter lab2 target webserver8 wwpn #2
Related Commands
scsirouter target lun lunid
To map a logical target and LUN combination to a unique LUN identifier, use the scsirouter target lun lunid command. The scsirouter target lun lunid command is a target-and-LUN mapping method of mapping a logical target to storage.
scsirouter name target name lun nn lunid lun-identifier [force]
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the storage target.
|
target name
|
A user-specified name of the logical target. Enter a maximum of 31 characters or a valid iSCSI Name. There is a maximum of 100 targets per storage router or per high availability cluster.
|
lun nn
|
The LUN number associated with the logical target. LUNs are integers between 0 and 255.
|
lunid lun-identifier
|
Use the unique LUN identifier, assigned when the LUN is discovered by the Fibre Channel interface. Enter either 16 or 32 hex digits.
|
force
|
(Optional) Keyword used to allow LUN-mapping of the same storage array control LUNs in multiple targets.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The force keyword was added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The scsirouter target lun lunid command specifies a logical target name and LUN number combination to be mapped to a physical LUN by its unique LUN identifier. The LUN identifier is represented by 16 or 32 hex digits. The digits may be separated by colons.
When a target is added, it is by default enabled. However, it is not associated with any access list ("accesslist none"), effectively disabling access to the target from any IP hosts. Use the scsirouter target accesslist command to enable access to this storage target for selected IP hosts.
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about configuring SCSI routing instances on the storage router.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Use the force keyword to allow mapping of the same storage array control LUN in multiple targets. Do not use the force keyword to LUN-map the same data LUN in multiple targets. LUN-mapping of the same LUN in multiple targets is advised for a control LUN on a storage controller only.
Examples
The following example maps a logical target and LUN combination for SCSI router instance foo. The logical target and LUN combination, webserver5 LUN 5, is mapped to the physical LUN represented by the LUN identifier 200000203719129d.
[SN5428-2A]# scsirouter foo target webserver5 lun 5 lunid 220000203719129d
Related Commands
scsirouter target lun serial
To map a logical target and LUN combination to the serial number of the physical LUN, use the scsirouter target lun serial command. The scsirouter target lun serial command is a target-and-LUN mapping method of mapping a logical target and LUN combination to a physical storage resource by the LUN serial number.
scsirouter name target name lun nn serial serial_number [force]
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the storage target.
|
target name
|
A user-specified name of the logical target. Enter a maximum of 31 characters or a valid iSCSI Name. There is a maximum of 100 targets per storage router or per high availability cluster.
|
lun nn
|
The LUN number associated with the target (the iSCSI LUN). iSCSI LUNs are integers between 0 and 255.
|
serial serial_number
|
The serial number of the physical LUN. The storage resource must support unique serial numbers for each LUN.
|
force
|
(Optional) Keyword used to allow LUN-mapping of the same storage array control LUNs in multiple targets.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The force keyword was added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The scsirouter target lun serial command requires both a logical target and LUN combination and the serial number of the physical LUN.
When a target is added, it is by default enabled. However, it is not associated with any access list ("accesslist none"), effectively disabling access to the target from any IP hosts. Use the scsirouter target accesslist command to enable access to this storage target for selected IP hosts.
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about configuring SCSI routing instances on the storage router.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Use the force keyword to allow mapping of the same storage array control LUN in multiple targets. Do not use the force keyword to LUN-map the same data LUN in multiple targets. LUN-mapping of the same LUN in multiple targets is advised for a control LUN on a storage controller only.
Examples
The following example maps the logical target and LUN combination for SCSI routing instance lab2. The logical target and LUN combination, webserver9 LUN 1, is mapped to the physical LUN with a serial number of ST318451FC3CC05T3N00007116DLWQ.
[SN5428-2A]# scsirouter lab2 target webserver9 lun 1 serial ST318451FC3CC05T3N00007116DLWQ
Related Commands
scsirouter target lun wwpn lun
To map a logical target and LUN combination to a primary (and optional secondary) storage address where each storage address is specified by World Wide Port Name (WWPN) and LUN, use the scsirouter target lun wwpn lun command. The scsirouter target lun wwpn lun command is a target-and-LUN mapping method of mapping a logical target to storage.
scsirouter name target name lun nn wwpn xxxxxxxxxxxxxxxx lun nn
[wwpn xxxxxxxxxxxxxxxx lun nn] [force]
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the storage target.
|
target name
|
A user-specified name of the logical target. Enter a maximum of 31 characters or a valid iSCSI Name. There is a maximum of 100 targets per storage router or per high-availability cluster.
|
lun nn
|
The first instance is the LUN number associated with the target (the iSCSI LUN). iSCSI LUNs are integers between 0 and 255. The second instance is the LUN number associated with the primary WWPN (physical device LUN). Physical LUNs may be any physical device number, for example 0x51d1 or 123.
|
wwpn xxxxxxxxxxxxxxxx
|
Specify a WWPN for the primary storage address. In a high availability cluster, this is the WWPN for the storage resource as known to the first storage router in the cluster.
|
wwpn xxxxxxxxxxxxxxxx
|
(Optional) Specify a WWPN for the secondary storage address, used as an alternate for mapping if the primary is not available. In a high availability cluster, this is the WWPN for the storage resource as known to the second storage router in the cluster.
|
lun nn
|
(Optional) Specify the LUN associated with the optional secondary WWPN. Physical LUNs may be any physical device number, for example 0x51d1 or 123.
|
force
|
(Optional) Keyword used to allow LUN-mapping of the same storage array control LUNs in multiple targets.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The force keyword was added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The scsirouter target lun wwpn lun command specifies a logical target name and LUN number combination to be mapped to a physical WWPN and LUN combination in storage.
Tips
WWPN address notation is represented by 16 hex digits. The digits may be separated by colons. When entering WWPN addresses, colons can be omitted or placed anywhere in the address notation as long as they do not leave one character without a partner character. The entry should be zero-filled from the most significant (the left-most) character position.
The following examples are correct:
•
0000:0000:1234:5678
•
0A0F2860:02111750
•
0A0F286002111750
The following examples are incorrect:
•
1:234:567:8:91:23:FF:6
•
12:34:56
The secondary WWPN and LUN combination is optional. The secondary combination is mapped to the logical target name and LUN combination as an alternate, if the primary WWPN and LUN combination is not available.
When you map a target using WWPN and the target needs to be accessed in a high availability cluster, you must specify both the primary WWPN (the WWPN of the storage resource as known to the first storage router in the cluster) and the secondary WWPN (the WWPN of the storage resource as known to the second storage router in the cluster). The secondary WWPN value may need to be retrieved by issuing the appropriate commands (such as the show devices command) from the second node in the cluster, or by temporarily attaching the secondary port of the storage device to the first storage router.
When a target is added, it is by default enabled. However, it is not associated with any access list ("accesslist none"), effectively disabling access to the target from any IP hosts. Use the scsirouter target accesslist command to enable access to this storage target for selected IP hosts.
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about configuring SCSI routing instances on the storage router.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Use the force keyword to allow mapping of the same storage array control LUN in multiple targets. Do not use the force keyword to LUN-map the same data LUN in multiple targets. LUN-mapping of the same LUN in multiple targets is advised for a control LUN on a storage controller only.
Examples
The following example maps a logical target and LUN combination for SCSI router instance lab3. The logical target and LUN combination, webserver7 LUN 7, is mapped to the primary WWPN and LUN combination, 2200002037191505 LUN 0.
[SN5428-2A]# scsirouter lab3 target webserver7 lun 7 wwpn 2200002037191505 lun 0
The following example maps a logical target and LUN combination to a primary and secondary WWPN. You may need to obtain the secondary WWPN from the storage router to which the secondary port of the device is attached, or temporarily attach the storage device's secondary port to the storage router being configured.
[SN5428-2A]# scsirouter lab4 target webserver8 lun 0 wwpn 2200002037c6756d lun 0 wwpn
2100002037c6747f lun 0
Related Commands
scsirouter target maxcmdqueuedepth
To specify the maximum number of commands allowed at any given time from each iSCSI session to the specified target, use the scsirouter target maxcmdqueuedepth command.
scsirouter name target {all | name} maxcmdqueuedepth nn
Syntax Description
name
|
Name of the SCSI routing instance.
|
target all
|
Specify the maximum number of command for all targets.
|
target name
|
The name of the storage target.
|
nn
|
The maximum number of commands allowed from each iSCSI session. If the value is set to zero, the feature is disabled.
|
Defaults
This feature is disabled; maxcmdqueuedepth is set to zero.
Command Modes
Administrator.
Command History
Release
|
Modification
|
3.3.1
|
This command was introduced.
|
Usage Guidelines
When this value is configured, all current and future iSCSI sessions to the specified target will enforce the maximum command queue depth. To disable this feature, and allow an unlimited number of commands to the target from each iSCSI session, set the maxcmdqueuedepth to zero. This is the default setting.
Use the show scsirouter command with the bootconfig or runningconfig keyword to display the current maximum command queue depth value.
Note
Normal limitations, based on the available command buffer space, are always enforced. Setting the maximum command queue depth does not override these normal limitations.
Examples
The following example sets the maximum command queue depth to 20, for all targets associated with the SCSI routing instance named foo.
[SN5428-2A]# scsirouter foo target all maxcmdqueuedepth 20
The following example disables the maximum command queue depth, allowing an unlimited number of commands to the target named webservices2, associated with the SCSI routing instance named foo.
[SN5428-2A]# scsirouter foo target webservices2 maxcmdqueuedepth 0
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter target enable
|
Allow or disallow connections and logins for the named target.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter target profile
To disable the use of an initial iSCSI Ready-to-Transfer (R2T) on connections coming to this target, use the scsirouter target profile command.
scsirouter name target name profile {high | low}
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the target profile.
|
target name
|
The name of the storage target.
|
high
|
Disable the use of R2T for the specified target. This allows a host that opens a connection to the specified target to start sending data of a certain length as if it had received an initial R2T.
|
low
|
Enable the use of R2T for the specified target. This prevents a host that opens a connection to the specified target from sending any data packets to the target until the target has sent the host an R2T message. This adds latency to data transfer activities to this target.
|
Defaults
All targets are configured as high profile targets.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.5.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The storage router supports up to 16 concurrent connections that do not use an initial R2T. If there are 16 existing connections to targets configured as high profile, the 17th connection will be handled as though the target were defined as low profile, causing the connection performance to be a bit slower.
By default, all targets are defined as high profile targets to provide the best performance. Use the scsirouter target profile command to configure targets that do not require the additional performance as low profile targets.
Examples
The following example configures the target labserver8 for SCSI routing instance lab4 as a low profile target. Any host opening a connection to the labserver8 target cannot send any data to the target until the target sends the host an R2T.
[SN5428-2A]# scsirouter lab4 target labserver8 profile low
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter target enable
|
Allow or disallow connections and logins for the named target.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter target trespass
To enable the active/passive controller trespass feature for the specified storage target, use the scsirouter target trespass command. To disable the trespass feature, use the no form of this command.
scsirouter name target {all | name} trespass
no scsirouter name target {all | name} trespass
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the trespass feature.
|
target all
|
Enable the trespass feature for all targets.
|
target name
|
The name of the storage target.
|
Defaults
The trespass feature is disabled for all targets.
Command Modes
Administrator.
Command History
Release
|
Modification
|
3.4.1
|
This command was introduced.
|
Usage Guidelines
The trespass feature provides LUN failover capability for selected storage arrays that operate on the active/passive port model. When enabled, the trespass feature provides a redundant path from the storage router to the storage array by allowing the storage router to detect a path failure to a storage array port and perform the necessary operations to fail LUNs over to the other port on the storage array without using any multi-path software.
The trespass feature requires the SCSI routing instance target to be LUN mapped, using primary and secondary WWPNs, or LUN mapped using LUN ID. The proper mapping, along with the activation of the trespass feature, ensures that the storage router will detect a path failure and fail the LUNs over to the other port on the storage array.
This feature also provides redundant paths from the storage router to the storage array, and can be used in a high availability cluster.
Note
After enabling the trespass feature, restart the SCSI routing instance to activate the feature.
Examples
The following example enables the trespass feature for the target labserver7, associated with SCSI routing instance lab3. The SCSI routing instance is then disabled and reenabled to active the trespass feature.
[SN5428-2A]# scsirouter lab3 target labserver7 trespass
*[SN5428-2A]# no scsirouter lab3 enable
*[SN5428-2A]# scsirouter lab3 enable
Related Commands
Command
|
Description
|
delete scsirouter
|
Delete the named SCSI routing instance or the specified element of the SCSI routing instance.
|
restore scsirouter
|
Restore the named SCSI routing instance from the named configuration file.
|
save scsirouter
|
Save configuration information for the named SCSI routing instance.
|
scsirouter
|
Create a SCSI routing instance.
|
scsirouter enable
|
Stop or start the named SCSI routing instance.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
scsirouter target wwpn
To map a logical target to a primary (and, optionally, a secondary) storage address specified by World Wide Port Names (WWPNs), use the scsirouter target wwpn command. The scsirouter target wwpn command is a target-only method of mapping a logical target specified by WWPNs.
scsirouter name target name wwpn xxxxxxxxxxxxxxxx [wwpn xxxxxxxxxxxxxxxx]
Syntax Description
name
|
Name of the SCSI routing instance to which you are adding the storage target.
|
target name
|
A user-specified name of the logical target. Enter a maximum of 31 characters or a valid iSCSI Name. There is a maximum of 100 targets per storage router or per high availability cluster.
|
wwpn xxxxxxxxxxxxxxxx
|
Specify a WWPN for the primary storage address. In a high availability cluster, this is the WWPN for the storage resource as known to the first storage router in the cluster.
|
wwpn xxxxxxxxxxxxxxxx
|
(Optional) Specify a WWPN for the secondary storage address, used as an alternate for mapping if the primary is not available. In a high availability cluster, this is the WWPN for the storage resource as known to the second storage router in the cluster.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The scsirouter target wwpn command requires only a logical target name to be mapped to a physical target address—no LUNS are specified. However, all LUNs that are part of the physical target address are discovered and made apparent as LUNs belonging to the logical target.
Tips
WWPN address notation is represented by 16 hex digits. The digits may be separated by colons. When entering WWPN addresses, colons can be omitted or placed anywhere in the address notation as long as they do not leave one character without a partner character. The entry should be zero-filled from the most significant (the left-most) character position.
The following examples are correct:
•
0000:0000:1234:5678
•
0A0F2860:02111750
•
0A0F286002111750
The following examples are incorrect:
•
1:234:567:8:91:23:FF:6
•
12:34:56
When you map a target using WWPN and the target needs to be accessed in a high availability cluster, you must specify both the primary WWPN (the WWPN of the storage resource as known to the first storage router in the cluster) and the secondary WWPN (the WWPN of the storage resource as known to the second storage router in the cluster). The secondary WWPN value may need to be retrieved by issuing the appropriate commands (such as the show devices command) from the second node in the cluster, or by temporarily attaching the secondary port of the storage device to the first storage router.
When a target is added, it is by default enabled. However, it is not associated with any access list ("accesslist none"), effectively disabling access to the target from any IP hosts. Use the scsirouter target accesslist command to enable access to this storage target for selected IP hosts.
Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about configuring SCSI routing instances on the storage router.
Note
When making changes to SCSI routing instances (such as adding or deleting targets or changing access) be sure to make the complimentary changes to the iSCSI configuration of IP hosts using these services to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.
Examples
The following example maps a logical target for SCSI router instance lab4. The logical target webserver1 is mapped to the primary WWPN, 22:00:00:20:37:19:15:05.
[SN5428-2A]# scsirouter lab4 target webserver1 wwpn 22:00:00:20:37:19:15:05
The following example maps a logical target to a primary and secondary WWPN. You may need to obtain the secondary WWPN from the storage router to which the secondary port of the device is attached, or temporarily attach the storage device's secondary port to the storage router being configured.
[SN5428-2A]# scsirouter lab5 target webserver9 wwpn 2200002037c6756d wwpn 2100002037c6747f
Related Commands
scsirouter username
To assign a user name to a SCSI routing instance for iSCSI authentication purposes, use the scsirouter username command.
scsirouter name username {user-name | none}
Syntax Description
name
|
The name of the SCSI routing instance.
|
user-name
|
A valid user name. Enter a maximum of 63 characters
|
none
|
Keyword, removing any existing iSCSI user name assigned to the named SCSI routing instance.
|
Defaults
None.
Command Modes
Administrator.
Command History
Release
|
Modification
|
3.2.1
|
This command was introduced.
|
Usage Guidelines
Use this command to assign a user name to the SCSI routing instance for two-way iSCSI authentication. Two way iSCSI authentication allows authentication of the IP host and also allows the IP host, acting as an iSCSI initiator, to require authentication of the SCSI routing instance, acting as an iSCSI target. The user name and password assigned to the SCSI routing instance are used by the IP host for iSCSI authentication purposes.
iSCSI authentication must be enabled for the named SCSI routing instance. If iSCSI authentication is not enabled, the user name and password assigned to the SCSI routing instance will not be used.
Examples
The following example enables iSCSI authentication, using the default authentication list, for the SCSI routing instance named lab3 and assigns a user name of lab3-admin and a password of testing to the instance for two-way authentication:
[SN5428-2A]# scsirouter lab3 authentication default
*[SN5428-2A]# scsirouter lab3 username lab3-admin
*[SN5428-2A]# scsirouter lab3 password testing
Related Commands
Command
|
Description
|
scsirouter authentication
|
Enable iSCSI authentication for the named SCSI routing instance.
|
scsirouter password
|
Assign a password to a SCSI routing instance for iSCSI authentication purposes.
|
show scsirouter
|
Display configuration and operational information for the named SCSI routing instance.
|
session-timeout
To set the number of minutes a Telnet or SSH management session (or an Administrator mode session via the EIA/TIA-232 console connection) to the storage router can be inactive before the session times out, use the session timeout command. To prevent management sessions from timing out, use the no form of this command.
session-timeout nn
no session-timeout
Syntax Description
nn
|
The number of minutes the management session can be inactive before it is terminated. By default, management sessions do not timeout.
|
Defaults
There is no timeout for management sessions. This has the same effect as the following command:
session-timeout 0
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.5.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
Use this command to configure the number of minutes a Telnet or SSH management session (or an Administrator mode session via the console) can be inactive before it is terminated. By default, management sessions do not time out.
When an Administrator mode session via the console times out, the console returns automatically to Monitor mode. If passwords are enabled on the console, the password prompt displays.
A change in the session timeout value is effective at the next time-check interval, and will affect all currently logged in management sessions as well as future sessions, until the storage router is restarted.
Use the show system command to display the current time out value for management sessions.
Examples
The following example allows management sessions to be inactive for 15 minutes before being terminated.
[SN5428-2A]# session-timeout 15
The following example disables automatic termination of inactive management sessions:
[SN5428-2A]# no session-timeout
Related Commands
Command
|
Description
|
show sessions
|
Display information about active console, Telnet, SSH or GUI sessions to the storage router.
|
show system
|
Display selected system information.
|
setup
To configure the storage router using the setup configuration wizard, use the setup command. The Setup configuration wizard runs the Management Interface, Date and Time, Network Management, Management Access, and SCSI routing (if applicable) individual wizards in sequence.
setup
Syntax Description
This command has no arguments or keywords.
Defaults
For multiple choice questions, the system presents the choices enclosed in brackets, [ ]. Each multiple choice question has a default answer that is selected when you press Enter or Return. The default is shown in parentheses, ( ). For example:
Enable High Availability? [yes/no (no)]
For configuration variables, the current value saved in the system is presented in brackets. For example:
Network mask ? [255.255.255.0]
If the configuration variable does not have a value, the system will present a set of "empty" brackets, [(empty)], or a template that provides the required format of the value. For example:
SN5428-2 system name? [(empty)]
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
Initial system configuration and subsequent reconfiguration can be performed via interactive configuration wizards through the console interface (or via Telnet or SSH once the management interface has been configured). The configuration wizards prompt you for the necessary information to accomplish the specific configuration task and may invoke multiple commands to complete their functions.
The CLI provides the following configuration wizards:
•
Setup—runs the Management Interface, Date and Time, Network Management, Management Access, and SCSI routing (if applicable) individual wizards in sequence.
•
Management Interface—configures the management interface with a system name, IP address, and optional DNS server information.
•
Date and Time—configures the time zone, use (or non-use) of daylight savings time, and the NTP server address (if one is present) or the current date and time.
•
Network Management—configures the use of Telnet, web-based GUI, and SNMP for managing the storage router over the network.
•
Management Access—configures passwords for monitoring and configuring the storage router.
•
SCSI Routing—configures a SCSI routing instance. The wizard is only available when the storage router is deployed for SCSI routing; it is not available if the storage router is deployed for transparent SCSI routing.
•
FCIP—configures FCIP instances. The wizard is only available when the storage router is deployed for FCIP; it is not available if the storage router is deployed for SCSI routing or transparent SCSI routing.
If the storage router is deployed for SCSI routing, the CLI also provides a Cluster wizard, which configures the storage router to participate in a high availability cluster. Because the initial configuration script configures the high availability environment, the Setup configuration wizard does not include the Cluster wizard. However, the Cluster wizard, using the setup cluster command, can be run after initial system configuration to change the configuration mode from standalone to clustered, to change membership from one cluster to another, or to resign from a cluster and run as a standalone storage router. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about initial system configuration.
During configuration with the Setup configuration wizard, operational changes take place and are applied to the currently running system. For example, after the Network Management wizard completes, SNMP network management will be configured for the storage router. However, these changes are not saved to the system's bootable configuration until the end of the entire Setup configuration wizard. To quit the setup configuration wizard without saving changes, press Ctrl-C at any time before the end of the wizard, and then reboot the storage router to restore previous values.
Note
Some changes may be retained after a reboot. Be sure to review the values provided in the prompts that display if you rerun the setup configuration wizard or run each individual wizard.
After entering the Setup configuration wizard, several informational messages display, including the following prompt:
User level for setup? [novice/expert (expert)]
•
Enter novice to continue with the configuration process. Explanatory text displays before each prompt in the wizard.
•
Enter expert to continue with the configuration process, suppressing all explanatory text. If you are an experienced user familiar with the setup configuration wizard, you may prefer this option.
At the end of the Setup configuration wizard, the following prompt displays:
Note
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Examples
The following shows the initial explanatory text for the setup command:
You are about to set up the SN5428-2. Running this wizard will modify
the configuration of this system.
During setup, operational changes will take place. However, these changes
are not saved until the end of the script. To quit the setup wizard without
saving changes, ** hit CTRL-C at any time **. Reboot to restore previous values.
For multiple choice questions, the system will present the choices enclosed
in brackets []. Each multiple choice question has a default answer that is
selected when you press return.
Choices are yes and no. No is the default answer.
For configuration variables, the current value saved in the system is
presented in brackets [varname]. If the configuration variable does not have a
value, the system will present a set of brackets [(empty)] or a template that
provides the expected format of the value.
Example: [mySN5428-2] configuration variable has a value
Example: [(empty)] configuration variable does not have a value, no template
Example: [A.B.C.D] template for an IP address.
User level for setup? [novice/expert (expert)]
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup access
To configure passwords for monitoring and administering the storage router, use the setup access configuration wizard. The wizard prompts you to enter and confirm new passwords.
setup access [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
The factory default password for both Administrator mode and Monitor mode is cisco.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The wizard prompts you to enter (and confirm by re-entering) the new Monitor password, which allows view-only access to the storage router. It also prompts you to enter (and confirm by re-entering) the new Administrator password, which allows changes to be made to the storage router configuration. Passwords are cluster configuration elements. In a high availability (HA) cluster, the setup access wizard can only be run from the storage router that is currently performing password management functions.
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup access wizard from a command script. All parameters required by the wizard must be included. The setup access wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup access wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup access command when using the parameter arguments.
Examples
The following example sets the Monitor mode and Administrator mode passwords for the storage router, but does not apply them to the console interface. Administrator contact information is also configured. Passwords display as asterisks when entered.
[SN5428-2_PR]# setup access
###############################
## Management Access Setup ##
###############################
The SN5428-2 CLI and GUI are protected by two passwords. The initial password
entered when logging in allows the user to monitor the SN5428-2, but does not
allow changes. The "admin" password allows the user to make configuration
Enter the current "monitor" password:******
A password can contain any combination of numbers and letters, but should
not be something familiar to you and easy to guess.
Enter the new "monitor" password: *****
Enter the new "monitor" password again: *****
Enter the current "admin" password: ******
Enter the new "admin" password: *****
Enter the new "admin" password again: *****
The new passwords will apply to all telnet and web-based GUI sessions.
They will also be applied to the console. If the SN5428-2 console is in
a physically secure location, console passwords are not recommended
since they can be lost or forgotten. If the SN5428-2 is deployed in a
less secure environment, the passwords should be applied. If passwords
are subsequently lost, visit http://www.cisco.com/public/Support_root.shtml
for information on recovery.
Apply passwords to console ? [yes/no (no)] no
The administrative contact is the person or group responsible for
configuration and management of the SN5428-2. The system will store a name,
e-mail address, phone number, and pager number for the system administrator.
Management applications can retrieve this information and provide it to a
support person or directly use it to e-mail or page the administrator.
Input Administrator Info? [yes/no (yes)] yes
Administrator name? [(empty) ] Pat Hurley
Phone? [(empty) ] 123.456.7890
Pager number? [(empty)] 12.456.3444 pin 2234
Email? [(empty)] hurley@abc123z.com
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup cluster
To configure the high availability (HA) environment for the storage router, to add the storage router to a cluster, or to remove it from an existing cluster, use the setup cluster configuration wizard. The wizard prompts you to select the appropriate HA configuration mode, enter a cluster name and (if necessary) an HA interface IP address and subnet mask.
setup cluster [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
Defaults or current values are shown in parentheses within the allowable response brackets. In the following example, the allowable responses are retain and delete, and the default is delete.
Retain or delete applications ? [retain/delete (delete)]
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The HA features of the storage router are designed around a cluster of systems that back each other up in case of failure. A cluster consists of two identically configured SN 5428-2s (or one SN 5428 and one SN 5428-2) that continually exchange HA information over their HA and management interfaces.
Clusters are defined by name. The setup cluster command prompts you for the appropriate HA configuration mode and the cluster name.
•
Use the standalone keyword to identify the storage router as not participating in a cluster. A standalone storage router does not require the management or HA interfaces to be available in order to complete the system configuration. The MGMT and HA ports do not need to be cabled.
•
Use the clustered keyword to identify the storage router as participating in a cluster. To participate in a cluster, the storage router management and HA interfaces must be available in order to complete the system configuration. The MGMT and HA ports must be correctly cabled.
The command also prompts you to either retain the SCSI routing instance configurations for this storage router, merging them with others in the cluster, or to delete the existing SCSI routing instance configuration data and replace it with cluster data. Retained SCSi routing instance configuration data is replicated to other storage routers in the cluster. When joining an existing cluster, access list information and other cluster configuration elements, including VLAN, AAA and password settings, are always deleted and replaced by the cluster's access lists and other cluster configuration elements.
Caution 
Retaining SCSI routing instance configuration data could provide unexpected results.
Changing the cluster name, thereby joining another cluster, has the following effects on its existing configurations and operations:
•
All SCSI routing instances are failed over to another member in the original cluster.
•
All applications are stopped.
•
The cluster name is changed.
•
If you choose to retain data, any unsaved cluster configuration information is saved.
•
The system reboots. Configuration information is exchanged and the storage router learns AAA, access list, password, SCSI routing instance and VLAN configuration information from the cluster. All of the original SCSI routing instances appears in the new cluster, unless you chose to delete rather than retain data.
•
Access lists that existed on the storage router prior to joining the new cluster are always deleted. To preserve an existing access list and make it available to the new cluster, you must save the access list to a configuration file before issuing the setup cluster command. Make the saved configuration file available to the storage router currently performing access list maintenance functions for the cluster (via the copy command), and then restore the saved access list to the new cluster from that configuration file. Refer to the appropriate Cisco Storage Router Software Configuration Guide for your storage router model for more information about configuring the storage router to participate in a cluster.
•
For cases where the names of SCSI routing instances are duplicated within the new cluster (meaning instances of the same name are already running in the new cluster), configuration data from the old cluster is deleted in favor of what is currently running in the new cluster.
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup cluster wizard from a command script. All parameters required by the wizard must be included. The setup cluster wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup cluster wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup cluster command when using the parameter arguments.
Examples
The following shows example output and input for the setup cluster command:
[SN5428-2_PR]# setup cluster
The system has the ability to run in a standalone or clustered state.
By default, the system will run in a clustered state and communicate
with other SN5428-2s in the same cluster. If a single SN5428-2 is deployed
and you don't intend to add a second SN5428-2 to provide high availability
features in a clustered configuration, you should configure the SN5428-2 in
standalone mode. Enter CTRL-C at any prompt to cancel changes and return
HA configuration? [standalone/clustered (standalone)] clustered
If you select HA configuration mode clustered, the wizard prompts you to enter an HA IP address:
To determine the health of other SN5428-2s in a cluster, the SN5428-2 must send
occasional heartbeat packets on at least two interfaces (in case one interface
has problems). By default, the interfaces used are the 10/100 management
interface (already set up) and the 10/100 HA interface. Please select an IP
address and network mask for the HA interface.
HA Interface IP address? [10.1.40.230/24]
After selecting the HA configuration mode, and optionally setting the HA IP address, the wizard prompts you to enter a cluster name:
When you change the cluster that the SN5428-2 belongs to, you need to
decide if you want the scsirouter instances running on the SN5428-2 to be
deleted or if you want them to be retained and merged with the new cluster.
Change cluster to ? [Cluster1]
For a change from standalone to clustered:
If you retain the configuration, there may be conflicts when the
scsirouter instances are replicated between this SN5428-2 and others in the
For a change from clustered to standalone:
You can retain the configuration without causing any scsirouter instance
conflicts for this SN5428-2 since it will be the only member of the
Retain or delete scsirouter instances ? [retain/delete (delete)] retain
If you choose to retain the existing SCSI routing instance configurations, an additional warning displays:
#########################################################
Please confirm that you want to retain the configuration.
#########################################################
All configuration settings will be saved.
The system will REBOOT if you answer "yes"
** Enter CTRL-C to cancel. **
Are you sure you want to retain the configuration ? [must type "yes"] yes
If you choose to delete your existing configuration, this warning displays:
Retain or delete applications ? [retain/delete (delete)] delete
#########################################################
Please confirm that you want to delete the configuration.
#########################################################
Cluster configuration settings will be saved.
The system will REBOOT if you answer "yes"
** Enter CTRL-C to cancel and abort the cluster change. **
Are you sure you want to delete the configuration ? [must type "yes"] yes
After confirming your selection, the storage router automatically reboots.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup fcip
To configure an FCIP instance, use the setup fcip configuration wizard. The wizard prompts you to choose the name of the FCIP instance and specify the Gigabit Ethernet IP address and network mask. Then the wizard prompts you to enter the peer IP address and the connection protocol type. More extensive configuration of FCIP instances can be performed via the CLI or the web-based GUI.
setup fcip [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
Defaults or current values are shown in parentheses within the allowable response brackets. In the following example, the current default FCIP instance name is fcip1.
Create which FCIP instance ? [fcip1/fcip2 (fcip1)]
Command Modes
Administrator.
Command History
Release
|
Modification
|
3.3.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The setup fcip command can only be run when at least one FCIP instance is not currently configured on the storage router; if both FCIP instances are configured, you cannot run the setup fcip wizard. Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup fcip wizard from a command script. All parameters required by the wizard must be included. The setup fcip wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup fcip wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup fcip command when using the parameter arguments.
Examples
The following shows example output and input for the setup scsi command:
In order to correctly configure this FCIP instance, be sure you know
the configuration of the remote FCIP instance. You will need to know
the IP address and the communication protocol of the remote FCIP instance.
In addition, you will need to ensure that the Fibre Channel domain ID you
assign is different than the Fibre Channel domain ID assigned to the remote
The system enables you to create two FCIP instances. Each instance
uses a different Fibre Channel interface and gigabit Ethernet interface.
Create which FCIP instance ? [fcip1/fcip2 (fcip1)] fcip2
Please specify an IP address and netmask for the gigabit
IP address? [A.B.C.D/nn] 10.1.0.16/24
If both gigabit Ethernet interfaces are cabled to the same network, you
can configure the FCIP instance to failover to the secondary interface
in case of a failure on the primary interface.
Configure secondary interface for the FCIP instance? [yes/no (no)] no
Please enter the IP address of the remote FCIP instance to
which you wish to connect.
IP address of remote FCIP instance? [A.B.C.D] 10.1.0.47
Choose how you want the FCIP instance to communicate with the
remote FCIP instance. If the remote FCIP instance is configured to use raw IP,
select raw as the protocol. If the remote FCIP instance is configured as a TCP
server, select client. If the remote FCIP instance is configured as a TCP client,
Use which protocol? [raw/client/server] raw
If this is the first FCIP instance to be configured on the storage router, you will be prompted to specify a Fibre Channel domain ID:
Please specify a domain ID for use by this FCIP instance. This
domain ID must be unique. It can not be assigned to any switch in the Fibre
Channel fabric that this switch is connected to or assigned to any switch
in the remote Fibre Channel network.
Domain ID for the Fibre Channel switch? [1 - 127] 80
set Domain ID on Fibre Channel interfaces to 80
Mar 14 15:08:48: %FC-5-FCIP09: fcip2 has been started
Mar 14 15:08:48: %UI-5-FAFD2: Added FCIP device fci2
Mar 14 15:08:48: %UI-5-NMAOOI: Address 10.1.0.16/24 is now operational on interface ge1
Mar 14 15:08:48: %UI-5-FAFNI: Added FCIP network interface ge2, 10.1.0.16/255.255.255.0
FCIP-2: addPeer raw 10.1.0.47
Mar 14 15:08:48: %UI-5-FAFD: Added FCIP destination dest2 (raw, 10.1.50.50)
FCIP instance fcip2 is now configured.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup iscsi-port
To change the default listening port used for iSCSI traffic, use the setup iscsi-port wizard.
setup iscsi-port [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
The default listening port used for iSCSI traffic is 3260. This is the port number assigned by IANA.
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
If you change the listening port used for iSCSI traffic on the storage router, you must make corresponding changes to the IP hosts sending iSCSI traffic to the storage router. For example, on a UNIX system, you must update the /etc/services file. After selecting a new port for iSCSI traffic, the storage router automatically reboots.
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup iscsi-port wizard from a command script. All parameters required by the wizard must be included. The setup iscsi-port wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup iscsi-port wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup iscsi-port command when using the parameter arguments.
Examples
The following shows example output and input for the show iscsi-port command:
[SN5428-2A]# setup iscsi-port
###############################
## iSCSI port Setup Wizard ##
###############################
If you change the iSCSI port number, the system will reboot itself
for the change to take effect. This will cause all scsirouters to
** Enter CTRL-C to cancel. **
Do you want to change the iSCSI port number? [yes/no (no)] yes
##########################
## Changing iSCSI port ##
##########################
Now, you will need to enter a new iSCSI port number. The new port
will be used as the iSCSI server listen port. Make sure the new
port is not used by other applications in your network environment.
New port number ? [nn] 5003
#########################################################
## Please confirm that you want to change iSCSI port ##
#########################################################
iSCSI port configuration settings will be saved.
The system will REBOOT if you answer "yes".
** Enter CTRL-C to cancel. **
Proceed to change the iSCSI port? [yes/no (no)] yes
After confirming your intentions, the storage router automatically reboots.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup mgmt
To configure the storage router management interface, use the setup mgmt configuration wizard. The wizard prompts you to enter the system name, management interface IP address and subnet mask, optional default gateway and DNS information.
setup mgmt [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
Defaults or current values are shown in parentheses within the allowable response brackets. In the following example, the current system name is SN5428-2_Lab1.
SN5428-2 system name? [SN5428-2_Lab1]
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The management interface must be configured before the Telnet interface or web-based GUI can be used for configuration or monitoring tasks. When the wizard is completed, the system displays notification that the management interface is operational.
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup mgmt wizard from a command script. All parameters required by the wizard must be included. The setup mgmt wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup mgmt wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup mgmt command when using the parameter arguments.
Examples
The following shows example output for the setup mgmt command:
################################
## Management Interface Setup ##
################################
Please choose a name for the SN5428-2. This name is associated with the
SN5428-2 Management Interface IP address. If you wish to enable network
management on the SN5428-2, you should add the system name you provide
at this prompt and its IP address to a domain name server (nis, nis+, WINS).
SN5428-2 system name? [SN5428-2A]
The SN5428-2 may be managed using telnet, or a web-based GUI, or SNMP via the
10/100 Ethernet interface labeled "mgmt" on the front panel of the system. This
interface must be assigned an IP address.
Management Interface IP address? [10.1.12.122/24]
If the SN5428-2 is to be managed from a subnet other than the one to which it
is physically attached, a static route is required. The static route format
is "destination/netmask gateway".
Static route for Management Interface? [0.0.0.0/0 10.1.12.1]
If IP addresses are to be entered as host names via any of the SN5428-2
management interfaces, a Domain Name Server must be specified. A secondary
DNS may be specified for use if the primary DNS is not available.
Primary DNS Server? [A.B.C.D]
Secondary DNS Server? [A.B.C.D]
Setting up the management interface ... Done
The management port is now operational. It may be tested using ping
or telnet from a host on the network.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup netmgmt
To enable network management via any or all of the available interfaces (Telnet, web-based GUI, or SNMP), use the setup netmgmt configuration wizard. The wizard prompts you to selectively enable the various interfaces and, if SNMP is enabled, will prompt you to enter the read and write community information, IP addresses for SNMP traps, and additional SNMP configuration information.
setup netmgmt [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
Defaults or current values are shown in parentheses within the allowable response brackets. In the following example, the default name for the read community is public:
Read Community ? [public]
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
All network management interfaces are enabled by default, with SNMP "gets" via the public read community. Run this wizard to disable any of these interfaces, or to change the SNMP read community, configure the SNMP write community for SNMP "sets," or add addresses for SNMP traps.
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup netmgmt wizard from a command script. All parameters required by the wizard must be included. The setup netmgmt wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup netmgmt wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup netmgmt command when using the parameter arguments.
Examples
The following shows example output and input for the setup netmgmt command:
[SN5428-2A]# setup netmgmt
#####################################
## Network Management Access Setup ##
#####################################
This wizard will enable you to configure access to telnet, the web-based
GUI, and configure SNMP. By default, telnet and the web-based GUI are
enabled. SNMP gets via the "public" community are also enabled via the
10/100 management interface. If you want to change these values or configure
other SNMP features, please set up the network management.
Set up Network Management ? [yes/no (yes)] yes
Enable telnet on all interfaces? [yes/no (yes)] yes
Configure SNMP ? [yes/no (yes)] yes
If you select to configure SNMP, the wizard prompts you for the following information:
Read Community ? [public]
Write Community ? [private] mynetmanagers
First IP address for SNMP traps ? [A.B.C.D] 10.1.30.17
Trap version for first IP address? [1/2 (1)]
Second IP address for SNMP traps ? [A.B.C.D] 10.1.30.18
Trap version for second IP address? [1/2 (1)]
Send auth trap when requester specifies
incorrect community? [yes/no (no)] yes
Modify link up/down traps for one or more interfaces? [yes/no (yes)] yes
Send link up/down traps for MGMT interface? [yes/no (yes)] yes
Send link up/down traps for HA interface? [yes/no (yes)] yes
Send link up/down traps for GE interface? [yes/no (yes)] no
Send link up/down traps for fibre
channel interface? [yes/no (yes)] yes
The wizard ends by displaying the following information:
Network Management setup is complete.
By default, these methods of network management will work from any network
which is not separated from the SN5428-2 by a firewall or other traffic-limiting
device. To further specify security requirements, please use the normal
configuration functions of the CLI or GUI after completing this wizard.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup scsi
To configure a SCSI routing instance, use the setup scsi configuration wizard. The wizard prompts you to enter the name of the SCSI routing instance (maximum 32 characters) and to specify the IP address and Gigabit Ethernet interface for the SCSI routing instance. Then the wizard discovers all Fibre Channel devices connected to the storage router. More extensive configuration of SCSI routing instances can be performed via the CLI or the web-based GUI.
setup scsi [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
Defaults or current values are shown in parentheses within the allowable response brackets. In the following example, the current default Gigabit Ethernet interface is ge1.
Scsirouter instance GE interface ? [ge1|ge2 (ge1)]
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
After the wizard finishes the discovery process, it displays a list of accessible storage resources. Targets can be explicitly added by using the web-based GUI or CLI commands.
The setup scsi command can only be run when no SCSI routing instance is currently configured on the storage router. Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup scsi wizard from a command script. All parameters required by the wizard must be included. The setup scsi wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup scsi wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup scsi command when using the parameter arguments.
Examples
The following shows example output and input for the setup scsi command:
This wizard will enable you to set up a scsirouter instance, but will not enable you to
specify a VLAN for the IP interface. If a VLAN is required for the scsirouter instance,
please use CLI commands to configure the scsirouter.
Do you want to configure a scsirouter instance ? [yes/no (no)] yes
scsirouter instance name ? [(empty)] foo
The scsirouter instance communicates with IP hosts via the Gigabit Ethernet interface. To
enable communication, you need to assign an IP address and network mask to the scsirouter
instance for it to use on the Ethernet interface.
IP Address ? [A.B.C.D/nn] 10.1.0.45/24
Enter the name of the GE interface that you want the scsirouter instance to use.
Scsirouter instance GE interface ? [ge1|ge2 (ge1)] ge2
Now discovering all FC devices connected to the SN 5428-2-K9...
A scsirouter has been created. A list of accessible FC devices
is shown in the table below. Use the "scsirouter" command or the
configuration screen via the GUI to define one or more scsirouter targets.
Access to scsirouter targets will be disabled until access is explicitly
configured using the "scsirouter" command or the configuration
Fabric Attached Devices detected
Interface WWPN PortId Device Type Lun Lunid Type Lunid
--------- ---------------- -------- ----------- ----- -------------- -----
fc1 2200001026448a0d 0x101e1 Disk 0 IEEE Extended 2000001026448a0d
fc1 22000003be3203bc 0x101e2 Disk 0 IEEE Extended 20000003be3203bc
Interface WWPN Lun Capacity Vendor Product Serial
--------- ---------------- ----- -------- ------------ ------------ ------
fc1 2200001026448a0d 0 17GB SEAGATE ST217340EB 2BB01L3J0000600256BW
fc1 22000003be3203bc 0 17GB SEAGATE ST217341EB 2DU0537A00006105FGJ6
scsirouter setup is complete.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup time
|
Run the wizard to configure the system date and time.
|
setup time
To set current date and time information and other time-related configuration settings, use the setup time configuration wizard. The storage router uses date and time information for log files and the user interface.
setup time [parameter1 parameter2...]
Syntax Description
parameter1 parameter2 ...
|
(Optional) Enter each parameter that the wizard prompts for. All parameters must be passed. If a parameter includes an embedded space, enclose the parameter in quotation marks.
|
Defaults
Defaults or current values are shown in parentheses within the allowable response brackets. In the following example, the current date is 02/05/2002.
Date (mm/dd/yyyy)? [02/05/2002]
Command Modes
Administrator.
Command History
Release
|
Modification
|
2.2.1
|
This command was introduced for the SN 5428.
|
2.5.1
|
The parameter arguments were added.
|
3.2.1
|
This command was introduced for the SN 5428-2.
|
Usage Guidelines
The wizard prompts you to enter the appropriate time zone (as an offset from Universal/GMT). You can also enter an optional IP address of an NTP server, to be used by the storage router for date and time synchronization. If no NTP server address is provided, the wizard prompts you for the current date and time.
Only one setup wizard can be active at any given time. Multiple users cannot run multiple setup wizards concurrently.
Use the optional parameter arguments to run the setup time wizard from a command script. All parameters required by the wizard must be included. The setup time wizard will not complete unless all parameters are passed.
Note
If too many parameters are passed, the setup time wizard will ignore the extra parameters and may complete. If a parameter is not in the correct format or is otherwise invalid, the next parameter is used to attempt to fulfill the prompt. In either case, unexpected results could occur. Always check the output from a setup time command when using the parameter arguments.
After a time change, a system reboot is required to synchronize the system timestamp with the timestamps on the integrated FC switch log files, syslog and devlog.
Examples
The following shows example output and input for the setup time command:
#########################
## Date and Time Setup ##
#########################
To provide correct information in log files and user interfaces, the SN5428-2
must have a reasonably accurate date and time.
To use Daylight Savings Time or specify time zone by geographic region
use the "clock timezone" command.
The time zone must be entered as an offset from GMT.
0=[0000 GMT] 1=[-0100 WAT] 2=[-0200 AT]
3=[-0300 Brazil] 4=[-0400 AST] 5=[-0500 EST]
6=[-0600 CST] 7=[-0700 MST] 8=[-0800 PST]
9=[-0900 YST] 10=[-1000 AHST] 11=[-1100 NT]
12=[+1200 IDLW] 13=[+1100 WST] 14=[+1000 GST]
15=[+0900 JST] 16=[+0800 CCT] 17=[+0700 WAST]
18=[+0600 ZP6] 19=[+0500 ZP5] 20=[+0400 ZP4]
21=[+0300 BT] 22=[+0200 EET] 23=[+0100 CET]
If a Network Time Protocol (NTP) server is in use on a network reachable
via the SN5428-2 management interface, it may be used to keep the SN5428-2 date
and time in sync with the rest of the network.
NTP Server IP Address? [A.B.C.D] 10.1.60.86
If you enter the NTP server IP address, the date and time is synchronized with the network and the wizard completes. If you do not enter an NTP server IP address, the wizard prompts you for the current date and time information.
NTP Server IP Address? [A.B.C.D]
Date (mm/dd/yyyy)? [02/05/2002]
Time (hh:mm:ss)? [16:42:38] 10:42:12
Date and time are now configured.
Related Commands
Command
|
Description
|
clear conf
|
Return most configuration settings to factory defaults.
|
setup
|
Run the setup configuration wizard.
|
setup access
|
Run the wizard to configure Monitor mode and Administrator mode passwords.
|
setup cluster
|
Change the configuration of the high availability environment.
|
setup fcip
|
Run the wizard to manually configure FCIP instances.
|
setup iscsi-port
|
Run the wizard to manually configure the port used for iSCSI traffic.
|
setup mgmt
|
Run the wizard to configure the management interface.
|
setup netmgmt
|
Run the wizard to configure network management.
|
setup scsi
|
Run the wizard to configure a SCSI routing instance.
|
slp findattrs
To discover the attributes of a specific Service Location Protocol (SLP) registered service, use the slp findattrs command.
slp findattrs service [attribute]
Syntax Description
service
|
The SLP service. Use the slp findsrvs command to locate the specific service.
|
attribute
|
Display the value of the specified service attribute.
|
Defaults
None.
Command Modes
Administrator or Monitor.
Command History
Release
|
Modification
|
3.2.1
|
This command was introduced.
|
Usage Guidelines
Use this command to verify that the attributes of advertised targets associated with a SCSI routing instance are correct.
Use the slp findsrvs command to display the service information used as arguments in the command.
Examples
The following example discovers the attributes of all iscsi:target services:
[SN5428-2A]# slp findattrs iscsi:target
(iscsi-name=iqn.1987-05.com.cisco:00.dd6b75bc42ef.chimaera_apps),(alias=chimaera_apps),
(portal-group=1),(auth-addr=any),(auth-name=an)
(iscsi-name=iqn.1987-05.com.cisco.00.d621b8e50a31.chimaera_web),(alias=chimaera_web),
(portal-group=1),(auth-a)
The following example discovers the value of the alias attribute for all iscsi:target services:
[SN5428-2A]# slp findattrs iscsi:target alias
Related Commands
Command
|
Description
|
scsirouter slp enable
|
Enable the advertisement of the targets of the named SCSI routing instance with the SLP service.
|
show slp
|
Display the status of the SLP service and the interface address where the SLP service is listening for incoming SLP service requests.
|
slp findsrvs
|
Locate a SLP registered service of a specific type on the local subnet.
|
slp findsrvtypes
|
Discover all SLP registered service types on the local subnet.
|
slp findsrvs
To locate a Service Location Protocol (SLP) registered service of a specific type on the local subnet where the storage router is located, use the slp findsrvs command.
slp findsrvs service [(attribute=value)]
Syntax Description
service
|
The SLP service type. For example, the SLP service type for iSCSI targets is iscsi:target.
|
attribute=value
|
Display the specified service attribute value pair. The attribute value pair must be displayed in parenthesis.
|
Defaults
None.
Command Modes