-
Cisco SN 5400 Series Storage Router Command Reference, Release 3.4
-
About This Guide
-
Chapter 1 - CLI Overview
-
Chapter 2 - A Commands
-
Chapter 3 - C Commands
-
Chapter 4 - D Commands
-
Chapter 5 - E Commands
-
Chapter 6 - F Commands
-
Chapter 7 - H Commands
-
Chapter 8 - I Commands
-
Chapter 9 - L Commands
-
Chapter 10 - M Commands
-
Chapter 11 - N Commands
-
Chapter 12 - P Commands
-
Chapter 13 - R Commands
-
Chapter 14 - S Commands
-
Chapter 15 - Show Commands
-
Chapter 16 - T Commands
-
Chapter 17 - U Commands
-
Chapter 18 - V Commands
-
Chapter 19 - Z Commands
-
Table Of Contents
interface fci? devicediscoverytimer
I Commands
This chapter covers the following commands:
•
interface fci? devicediscoverytimer
interface fc? al-fairness
To enable the fairness algorithm (loop priority) on the named Fibre Channel (FC) interface, use the interface fc? al-fairness command. To disable the fairness algorithm on the named FC interface, use the no form of this command.
interface fc? al-fairness enable
no interface fc? al-fairness enable
Syntax Description
Defaults
The fairness algorithm is disabled on all FC interfaces by default, allowing the switch to have priority.
Command Modes
Administrator.
Command History
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
When the fairness algorithm is not enabled for a specific FC interface, the switch receives priority. Use this command to enable the fairness algorithm for the named interface, removing the switch priority for that interface.
Note
Examples
The following example enables the fairness algorithm on the FC interface named fc6:
[SN5428-2A]# interface fc6 al-fairness enableThe following example disables the fairness algorithm on the FC interface named fc3. The switch receives priority for traffic on this interface.
[SN5428-2A]# no interface fc3 al-fairness enableRelated Commands
interface fc? default
To return the named Fibre Channel (FC) interface to its default operational characteristics, use the interface fc? default command.
interface fc? default
Syntax Description
Defaults
The following are the default operational characteristics for the Fibre Channel interface:
•
•
•
•
•
•
•
•
Command Modes
Administrator.
Command History
Usage Guidelines
Use this command to quickly reset the named FC interface to its default operational characteristics. The results of this command are the same as if each of the following commands were issued for the same named FC interface:
•
•
•
•
•
•
•
•
Note
Examples
The following example returns the operational characteristics to their default settings for the FC interface named fc6:
[SN5428-2A]# interface fc6 defaultRelated Commands
interface fc? diag
To set the named Fibre Channel (FC) interface into diagnostic mode for testing purposes, use the interface fc? diag command.
interface fc? diag
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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 this command to change the named FC interface to diagnostic mode prior to performing an internal or external loopback test.
•
•
Examples
The following example sets the FC interface fc6 into a diagnostic state and then performs an internal loopback test:
[SN5428-2A]# interface fc6 diag[SN5428-2A]# interface fc6 loopback internalRelated Commands
interface fc? enable
To enable the named Fibre Channel (FC) interface, use the interface fc? enable command. To disable the named FC interface, use the no form of this command.
interface fc? enable
no interface fc? enable
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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
An FC interface must be enabled to allow access to storage targets or perform online loopback testing. Use this command to enable an individual FC interface.
If you experience a problem with the FC interface or a specific storage resource, use the no form of this command to disable the named FC interface.
Examples
The following example enables the FC interface fc6 and then performs an online loopback test:
[SN5428-2A]# interface fc6 enable[SN5428-2A]# interface fc6 loopback onlineThe following example disables the FC interface fc3:
[SN5428-2A]# no interface fc3 enableRelated Commands
interface fc? ext-credit
To configure the specified interface for credit extension, use the interface fc? ext-credit command.
interface fc? ext-credit nn
Syntax Description
Defaults
No extended credits are available. By default, each FC interface has 12 data buffer credits available.
Command Modes
Administrator.
Command History
Usage Guidelines
By default, each storage router Fibre Channel (FC) interface has a data buffer capacity of 12 maximum sized FC frames or "credits." This enables full bandwidth class 2 service over a distance of 20 kilometers at 1 Gbps, or 10 kilometers at 2 Gbps, for fibre optic cables. Longer distances can be spanned at full bandwidth by extending the credits available to an interface. An interface configured for credit extension draws on a pool of credits donated by designated donor interfaces. Each donor interface contributes 11 credits to the pool from which the recipient interfaces can draw.
In order to receive donated credits, the interface must have a running port type of E_Port, F_Port or G_Port. An interface with a running loop mode port type (FL_Port, GL_Port or translated loop) cannot receive donated credits. In order to donate credits, the interface port type must be donor.
Each interface with a port type of donor donates 11 buffer credits; all 11 buffer credits must go to a single recipient interface.
Use the show interface command to display the maximum data buffer credits available to an interface, and to display the ports receiving donated credits.
To make the interface unavailable for donated data buffer credits, use this command with a maximum number of additional buffer credits of 0 (zero).
Examples
The following example sets the port type for interface fc1 to F_Port, sets the port type for interface fc8 as donor (making 11 extended credits available to the interface fc1), and configures interface fc1 for credit extension:
[SN5428-2A]# interface fc8 type donor*[SN5428-2A]# interface fc1 type f-port*[SN5428-2A]# interface fc1 ext-credit 11The following example makes the interface fc1 unavailable for credit extension:
[SN5428-2A]# interface fc1 ext-credit 0Related Commands
interface fc? fan-enable
To enable Fabric Address Notification (FAN) on the named Fibre Channel (FC) interface, use the interface fc? fan-enable command. To disable FAN on the named FC interface, use the no form of this command.
interface fc? fan-enable enable
no interface fc? fan-enable enable
Syntax Description
Defaults
FAN is enabled on all FC interfaces by default
Command Modes
Administrator.
Command History
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 this command to enable or disable FAN loop login behavior on the named FC interface.
Note
Examples
The following example disables FAN on the FC interface named fc6:
[SN5428-2A]# no interface fc6 fan-enable enableThe following example enables FAN on the FC interface named fc3.
[SN5428-2A]# interface fc3 fan-enable enableRelated Commands
interface fc? linkspeed
To set the transfer rate for the named Fibre Channel (FC) interface, use the interface fc? linkspeed command.
interface fc? linkspeed {auto | 1gb | 2gb}
Syntax Description
Defaults
The transfer rate is automatically negotiated to either 1 Gbps or 2 Gbps, by default.
Command Modes
Administrator.
Command History
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 this command to change the transfer rate for the named FC interface.
Note
Examples
The following example sets the transfer rate for to 2 Gbps for the FC interface named fc6:
[SN5428-2A]# interface fc6 linkspeed 2gbRelated Commands
interface fc? loopback
To initiate a loopback test on the named Fibre Channel (FC) interface, use the interface fc? loopback command.
interface fc? loopback {external | internal | online}
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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
Loopback tests are part of standard diagnostic procedures. To display the results or status of a loopback test, use the show interface fc? command.
Before performing a loopback test, the named FC interface must be in the correct state.
•
•
Examples
The following example sets the FC interface fc6 into a diagnostic state and then performs an internal loopback test:
[SN5428-2A]# interface fc6 diag[SN5428-2A]# interface fc6 loopback internalThe following example enables the FC interface fc3 and then performs an online loopback test:
[SN5428-2A]# interface fc3 enable[SN5428-2A]# interface fc3 loopback onlineRelated Commands
interface fc? mfs-bundle
To enable Multi-Frame Sequence (MFS) bundling for the named Fibre Channel (FC) interface, use the interface fc? mfs-bundle command. To disable MFS bundling for the named FC interface, use the no form of this command.
interface fc? mfs-bundle enable timeout nn
no interface fc? mfs-bundle enable
Syntax Description
Defaults
MFS bundling is enabled on all FC interfaces, by default. The default timeout value is 10 msec.
Command Modes
Administrator.
Command History
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
MFS bundling is used to support systems that require frames to be sequenced in a particular order.
Note
Examples
The following example enables MFS bundling for the FC interface named fc6, and sets the timeout value to 640 msecs:
[SN5428-2A]# interface fc6 mfs-bundle enable timeout 640The following example disables MFS bundling for the FC interface named fc3:
[SN5428-2A]# no interface fc3 mfs-bundle enableRelated Commands
interface fc? ms-enable
To enable GS-3 management server commands for the specified Fibre Channel (FC) interface, use the interface fc? ms-enable command. To disable GS-3 management server commands, use the no form of this command.
interface fc? ms-enable enable
no interface fc? ms-enable enable
Syntax Description
Defaults
GS-3 management server commands are enabled on all FC interfaces.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Enabling GS-3 management server commands for the FC interface allows in-band management of the storage router's integrated FC switch component. GS-3 management server commands must be enabled if you want to use storage management tools to provide in-band management of the integrated FC switch component along with other switches in the fabric.
Use the no form of this command to disable in-band management on the specified FC interface.
Examples
The following example disables GS-3 management server commands for fc8:
[SN5428-2A]# no interface fc8 ms-enable enableRelated Commands
interface fc? reset
To disable and then enable the specified Fibre Channel (FC) interface, use the interface fc? reset command.
interface fc? reset
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
This command is functionally equivalent to issuing a no interface fc? enable command, followed by an interface fc? enable command.
After placing the FC interface into diagnostic mode and performing internal loopback testing, use this command to return the interface to an operational state.
Examples
The following example resets the FC interface named fc3:
[SN5428-2A]# interface fc3 resetRelated Commands
Set the named FC interface into diagnostic mode for testing purposes.
Enable the named FC interface.
Initiate a loopback test on the named FC interface.
interface fc? rscn
To enable the generation of Registered State Control Notification (RSCN) messages on the specified Fibre Channel (FC) interface, use the interface fc? rscn command. To disable RSCN messages, use the no form of this command.
interface fc? rscn enable
no interface fc? rscn enable
Syntax Description
Defaults
RSCN messages are generated on all FC interfaces.
Command Modes
Administrator.
Command History
Usage Guidelines
Each storage router and FC switch contains its own local Name Server, called a distributed Name Server (dNS). By default, all storage routers and FC switches in the fabric distribute RSCN messages whenever a change takes place in their local dNS database. RSCN notification is used to maintain the integrity of the local dNS database.
Examples
The following example disables generation of RSCN messages on interface fc5:
[SN5428-2A]# no interface fc5 rscn enableRelated Commands
Return the named FC interface to its default operational characteristics.
Display the local Fibre Channel nameserver database.
interface fc? type
To set the port type for the named Fibre Channel interface, use the interface fc? type command.
interface fc? type {auto | f-port | fl-port | g-port | gl-port}
interface fc? type tl-port mode {autobridge | autolearn}
interface fc? type donor
Syntax Description
Defaults
The port type is generic loop (GL_Port), by default.
Command Modes
Administrator.
Command History
Usage Guidelines
Select the appropriate port type based on the connected equipment. By default, all of the storage router FC ports are defined as self configuring GL_Ports.
•
•
•
•
•
•
Public devices have full Fibre Channel addressing capability and can communicate with any other public device on the fabric; private devices do not have full FC addressing capability. Private devices have only the Arbitrated Loop Physical Address (ALPA) portion.
The storage router supports a maximum of 7 FC Interswitch Link (ISL) hops.
Note
Examples
The following example sets the port type to fabric for the FC interface named fc6:
[SN5428-2A]# interface fc6 type f-portThe following example set the port type to translated loop for the FC interface named fc3. The mode is autolearn, so targets in private loop are made visible.
[SN5428-2A]# interface fc3 type tl-port mode autolearnThe following example sets the port type for interface fc1 to F_Port, sets the port type for interface fc8 as donor (making 11 buffer credits available to the interface fc1), and configures interface fc1 for credit extension:
[SN5428-2A]# interface fc1 type f-port*[SN5428-2A]# interface fc8 type donor*[SN5428-2A]# interface fc1 ext-credit 11Related Commands
interface fci? devicediscoverytimer
To enable the storage router's internal Fibre Channel (FC) interfaces to perform background device rediscovery for all attached FC targets at specific time intervals, use the interface fci? devicediscoverytimer command.
interface fci? devicediscoverytimer nn
Syntax Description
Defaults
The device discovery timer value is 0, indicating that automatic background device rediscovery is disabled.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to enable automatic device rediscovery on a periodic basis in environments where LUNs can be created on FC targets, but no event occurs to cause devices to be rediscovered. This situation may occur with certain RAID controllers or virtualization type devices.
You do not need to issue the interface fci? devicediscoverytimer command for both internal FC interfaces. When you enable automatic background device rediscovery for one internal FC interface (for example, fci1), the same setting is enabled for the other internal FC interface (for example, fci2).
When automatic background device rediscovery is enabled, use the show interface command with the stats keyword to display the current device rediscovery timer configuration.
Examples
The following example enables automatic device rediscovery every 20 minutes:
[SN5428-2A]# interface fci2 devicediscoverytimer 20device discovery timer changed to 20 minutes on interface fci1device discovery timer changed to 20 minutes on interface fci2The following example disables automatic background device rediscovery by setting the device discovery timer interval to 0. (This is the default setting.)
[SN5428-2A]# interface fci2 devicediscoverytimer 0device discovery timer changed to 0 minutes on interface fci1device discovery timer changed to 0 minutes on interface fci2Use the show interface command with the stats keyword to display the current device rediscovery timer configuration. In the following example, the storage router will perform background device rediscovery every 10 minutes.
[SN5428-2B]# show interface fci1 statsloop: LOOP READYconnection: F PortData Rate: 2 Gb/sport id: 0x20f00ALPA: 0x0firmware: READYdevice rediscovery timer: 10 minutes. . .
Note
Related Commands
Display operational and configuration information for the specified interface or all interfaces.
interface fci? mode
To set the interface mode for the specified internal Fibre Channel (FC) interface, use the interface fci? mode command.
interface fci? mode {fcip | scsirouter}
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
Use the interface fci? mode command to manually deploy the storage router for mixed mode support. When the storage router is deployed for mixed mode, one internal FC interface is configured to support SCSI routing or transparent SCSI routing, and the other internal FC interface is configured to support FCIP.
When the storage router is deployed for SCSI routing or transparent SCSI routing, one internal FC interface can be configured to support FCIP. When the storage router is deployed for FCIP, one internal FC interface can be configured to support SCSI routing.
To change the deployment option for a storage router deployed for SCSI routing without clearing the system configuration, reconfigure both internal FC interfaces for FCIP, and delete all SCSI routing instances. To change the deployment option for a storage router deployed for FCIP without clearing the system configuration, reconfigure both internal FC interfaces for SCSI routing, and delete all FCIP instances.
Use the show system command to see the current system deployment for the storage router.
Note
Examples
The following example enables the fci1 interface for SCSI routing, saves the storage router bootable configuration and reboots the system:
[SN5428-2A]# interface fci1 mode scsirouterNote: You must save your configuration and reboot the system for this change to take effect*[SN5428-2A]# save all bootconfigAug 13 22:23:44: %UI-5-CSCS: System configuration savedAug 13 22:23:44: %UI-5-CSRCS: ScsiRouter configuration savedAug 13 22:23:44: %UI-5-CRCS: FCIP configuration savedAug 13 22:23:44: %UI-5-CCCS: Cluster configuration savedAug 13 22:23:44: %UI-5-CACS: aaa configuration savedAug 13 22:23:45: %UI-5-FCSW: fc configuration saved[SN5428-2A]# rebootRelated Commands
interface ge?
To set various operational parameters associated with the Gigabit Ethernet interface, such as the size of the maximum transfer unit (MTU) or the use of VLANs, use the interface ge? command. To disable the use of VLANs, use the no form of this command. To specify that auto negotiation will never be used on this interface, use the interface ge? no autonegotiation command.
interface ge? {autonegotiation [autodetect] | mtusize {nn | default}
interface ge? no autonegotiation
interface ge? vlan enable
no interface ge? vlan enable
Syntax Description
Defaults
MTU size defaults to 1500 bytes. Auto negotiation defaults to autodetect. For storage routers deployed for SCSI routing, the use of VLANs is enabled by default.
Command Modes
Administrator.
Command History
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
All storage routers in a cluster should be configured with the same MTU size and other interface-specific parameters, allowing failover of applications to provide consistent performance characteristics.
If the storage router is deployed for FCIP, a larger MTU size is desirable. Set the MTU size to 9000 bytes, if possible.
Use the no interface ge? vlan enable command to quickly restrict VLAN functionality on the Gigabit Ethernet interface for troubleshooting purposes.
Examples
The following example enables auto negotiation on the Gigabit Ethernet interface, ge1. The ge1 interface will not come up until auto negotiation is successfully completed.
[SN5428-2A]# interface ge1 autonegotiationThe following example disables VLANs for the Gigabit Ethernet interface, ge2:
[SN5428-2A]# no interface ge2 vlan enableThe following examples changes the MTU size for the Gigabit Ethernet interface, ge1, to 9000 bytes. This is the recommended setting when the storage router is deployed for FCIP.
[SN5428-2A]# no interface ge2 vlan enableRelated Commands
Display operational and configuration information for the specified interface or all interfaces.
interface ge? ip-address
To enable an IP address on a Gigabit Ethernet interface for management of the storage router, use the interface ge? ip-address command. To disable an IP address configured for storage router management, use the no form of this command.
interface ge? [vlan vid] ip-address {A.B.C.D/bits | A.B.C.D/1.2.3.4} [secondary ge?]
no interface ge? [vlan vid] ip-address
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to designate an IP address on a Gigabit Ethernet interface to be used for management of the storage router (in-band management). The Gigabit Ethernet IP address specified for storage router management can perform all the normal management tasks, but unlike the management interface, it cannot perform HA functions in a cluster environment if the HA interface is unavailable.
In-band management is performed via a Telnet or Secure Shell (SSH) session, or via the web-based GUI. Only one IP address per logical interface can be configured for in-band management. Telnet, SSH, HTTP and SSL access is restricted, by default, on all Gigabit Ethernet interfaces. Use the no restrict CLI command to allow access to the storage router using the desired protocol via the specified Gigabit Ethernet interface.
If the secondary keyword is used, both Gigabit Ethernet interfaces must be connected to the same network segment. 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.
If you are using the Gigabit Ethernet interface IP address in configuration of external servers, such as RADIUS, TACACS+ or SNMP, that will access the storage router via this interface, reboot the storage router after configuring the Gigabit Ethernet IP address and saving the change to the system bootable configuration. This assures that the IP address is the first address associated with the specified interface.
Note
Examples
The following example configures the IP address 10.1.0.244/24 on ge1 for management of the storage router, and enables the ge1 interface for Telnet access.
[SN5428-2B]# interface ge1 ip-address 10.1.0.244/24[SN5428-2B]# no restrict ge1 telnetThe following example configures two IP addresses on unique logical interfaces for storage router management. The IP address 10.1.0.160/255.255.255.128 is specified as part of VLAN 100 on ge2; the IP address 10.1.0.168/255.255.255.128 is also on ge2 but is not part of a VLAN. The interface ge2 is enabled for SSH access.
[SN5428-2B]# interface ge2 vlan 100 ip-address 10.1.0.160/255.255.255.128[SN5428-2B]# interface ge2 ip-address 10.1.0.168/255.255.255.128[SN5428-2B]# no restrict ge2 sshThe following example configures the IP address 10.1.0.230/24 on ge2 for storage router management. If the ge2 interface is unavailable, the ge1 interface will be used. Both ge1 and ge2 are enabled for HTTP access.
[SN5428-2B]# interface ge2 ip-address 10.1.0.230/24 secondary ge1[SN5428-2B]# no restrict ge2 http[SN5428-2B]# no restrict ge1 httpThe following example removes the IP address configured for storage router management from ge1, and restricts SSL access to the interface:
[SN5428-2B]# no interface ge1 ip-address[SN5428-2B]# restrict ge1 sslThe following example configures the IP address 10.1.0.212/24 on ge2 for management of the storage router, saves the changes to the bootable configuration, and then performs a fast reboot. This assures that the IP address will be the first address associated with the ge2 interface, and allows the IP address to be used by external servers (such as RADIUS or TACACS+) to communicate with the storage router.
[SN5428-2B]# interface ge2 ip-address 10.1.0.212/24*[SN5428-2B]# save all bootconfig[SN5428-2B]# reboot fastRelated Commands
interface ha
To set various operational parameters associated with the high availability (HA) interface, such as the speed and duplex mode, use the interface ha command.
interface ha autonegotiation
interface ha no autonegotiation [speed {10 | 100}] [duplex {full | half}]
Syntax Description
Defaults
Auto negotiation is enabled.
Command Modes
Administrator.
Command History
Usage Guidelines
Use this command to manually set a specific interface speed and duplex setting, if the partner is unable to auto negotiate these settings.
All storage routers in a cluster should be configured with the same interface-specific parameters, allowing failover to provide consistent performance characteristics. Use the show interface ha command to display current operating characteristics for the HA interface.
Examples
The following example disables auto negotiation, and sets the interface speed to 10 Mbps, duplex full:
[SN5428-2A] interface ha no autonegotiation speed 10 duplex fullRelated Commands
Specify the HA interface IP address and subnet mask.
Display operational and configuration information for the specified interface or all interfaces.
interface ha ip-address
To specify the IP address and subnet mask for this system's high availability interface, use the interface ha ip-address command.
interface ha ip-address {A.B.C.D/bits | A.B.C.D/1.2.3.4}
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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 HA features are used within a cluster of storage routers. Each member of the cluster communicates over the HA and management interfaces, exchanging heartbeats and other configuration information, allowing for failover in case of system problems.
The HA interface and the management interface must be on unique IP subnets. In a cluster, the HA interfaces for all nodes should be on the same IP subnet.
After initial system configuration, use the setup cluster command to change the configuration of the high availability environment.
The HA interface is optional for storage router deployed for transparent SCSI routing, or for standalone storage routers deployed for SCSI routing.
Examples
The following example assigns the IP address of 10.1.20.56/24 to the HA interface:
[SN5428-2B]# interface ha ip-address 10.1.20.56/24Related Commands
interface mgmt
To set various operational parameters associated with the management interface, such as the speed and duplex mode, use the interface mgmt command.
interface mgmt autonegotiation
interface mgmt no autonegotiation [speed {10 | 100}] [duplex {full | half}]
Syntax Description
Defaults
Auto negotiation is enabled.
Command Modes
Administrator.
Command History
Usage Guidelines
Use this command to manually set a specific interface speed and duplex setting, if the partner is unable to auto negotiate these settings.
All storage routers in a cluster should be configured with the same interface-specific parameters, allowing failover to provide consistent performance characteristics. Use the show interface mgmt command to display current operating characteristics for the management interface.
Examples
The following example disables auto negotiation, and sets the interface speed to 10 Mbps, duplex full:
[SN5428-2A] interface mgmt no autonegotiation speed 10 duplex fullRelated Commands
Specify the management interface IP address and subnet mask.
Display operational and configuration information for the specified interface or all interfaces.
interface mgmt ip-address
To specify the IP address and subnet mask of the interface labeled MGMT on the front panel of the storage router, use the interface mgmt ip-address command. This address is used to manage the storage router via Telnet, Secure Shell (SSH), the web-based GUI, or SNMP.
interface mgmt ip-address {A.B.C.D/bits | A.B.C.D/1.2.3.4}
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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 management and HA interfaces must be on unique IP subnets. In a cluster, the management interfaces for all nodes should be on the same IP subnet.
Examples
The following example assigns the IP address of 10.1.10.244/24 to the management interface:
[SN5428-2A]# interface mgmt ip-address 10.1.10.244/24Related Commands
ip default-gateway
To add a gateway to the default route in the storage router routing table, use the ip default-gateway command. To delete the gateway, use the no form of this command.
ip default-gateway E.F.G.H [administrative-distance]
no ip default-gateway [A.B.C.D]
Syntax Description
Defaults
The default administrative distance for a static route is 1.
Command Modes
Administrator.
Command History
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
All IP interfaces in the storage router use the routing table to reach services and networks outside their local network. Other facilities, such as SNMP and connections to an NTP server or DNS servers, may also use the routing table. Use the ip default-gateway command to add a gateway to the default route in this table.
Only one default route is allowed in the routing table.
Note
The administrative distance is used to determine which route to install in the routing table when there are multiple routes to the same destination. The default administrative distance for static routes is 1; the administrative distance for dynamic routes created by RIP is 120. The route with the lower administrative distance is installed in the routing table (as long as the interface used by the route is up).
By default, a static route will always override a dynamic route learned by RIP. To modify this behavior, change the administrative distance of a static route to a value greater than 120.
Examples
The following example adds a default route to gateway 10.3.40.1 in the routing table. The administrative distance is 1, by default.
[SN5428-2A]# ip default-gateway 10.3.40.1The following example adds a default route to gateway 10.3.30.1, with an administrative distance of 130, in the routing table. If RIP is enabled for the storage router, the default route can be overridden by a dynamically learned route.
[SN5428-2A]# ip default-gateway 10.3.30.1 130Related Commands
ip domain-name
To specify the name of the storage router domain, use the ip domain-name command. To remove a domain name, use the no form of this command.
ip domain-name name
no ip domain-name
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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 ip domain-name command in conjunction with the ip name-server command. The storage router requires access to a DNS if any IP addresses are entered as host names via any of the storage router management interfaces, or if the management interface IP address is to be correlated with a DNS host name.
Note
Examples
The following example assigns the domain name abc123z.com to the storage router.
[SN5428-2A]# ip domain-name abc123z.comRelated Commands
ip name-server
To specify the IP address of the primary and optional secondary Domain Name Server (DNS), use the ip name-server command. To remove the settings for current domain name servers, use the no form of this command.
ip name-server A.B.C.D [E.F.G.H]
no ip name-server
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
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 storage router requires access to a DNS if any IP addresses are entered as host names via any of the storage router management interfaces, or if the management interface IP address is to be correlated with a DNS host name. To use the services of a DNS, you must also assign a domain name to the storage router via the ip domain-name command.
If the DNS is outside the storage router management subnet, use the ip route command to add an appropriate gateway IP address to the routing table.
Examples
The following example assigns the domain name abc123z.com to the storage router, and assigns the IP address of the primary DNS to 10.1.40.243 and the secondary DNS to 10.1.50.249:
[SN5428-2A]# ip domain-name abc123z.com[SN5428-2A]# ip name-server 10.1.40.243 10.1.50.249Related Commands
ip radius sourceinterface
To specify a single network interface to be used as the source IP address for all outgoing AAA authentication requests to RADIUS servers, use the ip radius sourceinterface command. To disable this restriction, use the no form of this command.
ip radius sourceinterface if-name
no ip radius sourceinterface
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to restrict all outgoing AAA authentication requests to RADIUS servers to a single interface.
Examples
The following example restricts all outgoing AAA authentication requests to RADIUS servers to the Gigabit Ethernet interface ge1:
[SN5428-2A]# ip radius sourceinterface ge1Related Commands
ip rip enable
To enable the storage router to learn dynamic routing using the routing information protocol (RIP), use the ip rip enable command. To disable dynamic routing via RIP, use the no form of this command.
ip rip enable
no ip rip enable
Syntax Description
This command has no arguments or keywords.
Defaults
RIP is disabled by default.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP) for dynamic routing and uses a distance vector algorithm to determine the best route between nodes in an Autonomous System (AS).
The storage router is a passive, or silent, RIP device; it updates routes based on RIP advertisements but it does not advertise. The storage router listens for advertised routes, learning routing information dynamically as it is exchanged in the network. The storage router supports both RIP version 1 (v1) and RIP version 2 (v2).
The RIP implementation runs RIP v2 in broadcast mode. This allows the storage router to learn from either RIP v1 or RIP v2 hosts that are operating in broadcast mode. The storage router will not learn routes from RIP v2 hosts operating in multicast mode.
If you are using RIP in your network, you can enable RIP support on the storage router. RIP eliminates or reduces the need to configure static routes for the storage router, because the storage router updates the route table based on the RIP advertisements.
The storage router can learn a maximum of 200 routes. Additional routes that are received are silently ignored. In the routing table, a static route will always override a dynamic route by default. To modify this behavior, change the administrative distance of a static route to a value greater than 120.
Examples
The following example enables RIP for the storage router:
[SN5428-2A]# ip rip enable[SN5428-2A] Dec 09 17:54:16: %IP-5-IRMRSAR: RIP Services are runningThe following command disables RIP:
[SN5428-2A]# no ip rip enableRelated Commands
ip rip timers
To configure various RIP timers, use the ip rip timers command.
ip rip timers invalid {nn | default}
Syntax Description
Defaults
The RIP invalid timer defaults to 180 seconds.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP) for dynamic routing and uses a distance vector algorithm to determine the best route between nodes in an Autonomous System (AS).
The storage router is a passive, or silent, RIP device; it updates routes based on RIP advertisements but it does not advertise. The storage router listens for advertised routes, learning routing information dynamically as it is exchanged in the network. The storage router supports both RIP version 1 (v1) and RIP version 2 (v2).
The RIP implementation runs RIP v2 in broadcast mode. This allows the storage router to learn from either RIP v1 or RIP v2 hosts that are operating in broadcast mode. The storage router will not learn routes from RIP v2 hosts operating in multicast mode.
The storage router can learn a maximum of 200 routes. Additional routes that are received are silently ignored. In the routing table, a static route will always override a dynamic route by default. To modify this behavior, change the administrative distance of a static route to a value greater than 120.
Timers are used to configure the timing of RIP activities. The invalid timer configures the maximum amount of time between updates of the internal route table. Use the default keyword to return a RIP timer to its default value.
Examples
The following example sets the RIP invalid timer to a value of 200 seconds and saves all configuration changes. This is the maximum amount of time between updates before a route is marked as expired.
[SN5428-2A]# ip rip timers invalid 200*[SN5428-2A]# save all bootconfigRelated Commands
ip route
To add a static route to the storage router routing table, use the ip route command. The specified IP address is accessed via the gateway specified in the command. To remove a static route from the routing table, use the no form of this command.
ip route {A.B.C.D/bits | A.B.C.D/1.2.3.4} E.F.G.H [administrative-distance]
no ip route {A.B.C.D/bits | A.B.C.D/1.2.3.4} [E.F.G.H]
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
All IP interfaces in the storage router use the routing table to reach services and networks outside their local network. Other facilities, such as SNMP and connections to an NTP server or DNS servers, may also use the routing table. Use the ip route command to specify routes for servers or networks outside the local networks associated with the storage router IP interfaces.
Use the show ip route command to display the routing table. Use the show route command to display all the default routes, included the routes that have been configured but not added to the routing table.
The administrative distance is used to determine which route to install in the routing table when there are multiple routes to the same destination. The default administrative distance for static routes is 1; the administrative distance for dynamic routes created by RIP is 120. The route with the lower administrative distance is installed in the routing table (as long as the interface used by the route is up).
By default, a static route will always override a dynamic route learned by RIP. To modify this behavior, change the administrative distance of a static route to a value greater than 120.
Note
Examples
The following command adds a unique route for IP address 10.1.30.0, specifying the subnet mask in dotted quad notation:
[SN5428-2A]# ip route 10.1.30.0/255.255.255.0 10.1.10.10The following command adds a unique route for IP address 10.1.40.0, using gateway 10.1.10.10, which is not yet on a locally connected network. The message indicates that the route has been configured but has not yet been made operational in the storage router.
[SN5428-2A]# ip route 10.1.40.0/24 10.1.10.10Oct 25 19:25:17: %UI-4-NMREEO1: Gateway 10.1.10.10 used by route 10.1.40.0/24 is currently unreachableThe following command adds a unique route for IP address 10.1.20.0 with an administrative distance of 130, in the routing table. If RIP is enabled for the storage router, the route can be overridden by a dynamically learned route.
[SN5428-2A]# ip route 10.1.20.0/24 10.1.10.10 130Related Commands
ip tacacs sourceinterface
To specify a single network interface to be used as the source IP address for all outgoing AAA authentication requests to TACACS+ servers, use the ip tacacs sourceinterface command. To disable this restriction, use the no form of this command.
ip tacacs sourceinterface if-name
no ip tacacs sourceinterface
Syntax Description
Defaults
None.
Command Modes
Administrator.
Command History
2.5.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use this command to restrict all outgoing AAA authentication requests to TACACS+ servers to a single interface.
Examples
The following example restricts all outgoing AAA authentication requests to TACACS+ servers to the management interface, mgmt:
[SN5428-2A]# ip tacacs sourceinterface mgmtRelated Commands
isns enable
To enable communications and client registrations with an iSNS server, use the isns enable command. To disable iSNS communications and services, use the no form of this command.
isns enable {tcp | udp} server A.B.C.D [port port-number]
no isns enable
Syntax Description
Defaults
The default iSNS listening port is 3205.
Command Modes
Administrator.
Command History
Usage Guidelines
Internet Storage Name Service (iSNS) is an IETF standard that facilitates scalable configuration and management of iSCSI and FC storage devices in an IP network by providing a set of services comparable to that available in FC networks. Using the iSNS, each storage device subordinates its discovery and management responsibilities to the iSNS server.
The storage router functions as an iSNS client. SCSI routing instances are registered as iSNS entities, targets are registered as storage nodes, and SCSI routing instance server interface IP addresses are registered as network portals with the iSNS server. The storage router management interface IP address is registered as an attribute of the SCSI routing instance iSNS entity.
iSNS servers may use TCP or UDP protocol for client registrations and other communications. Use the isns enable command to identify the iSNS server and communications protocol to the storage router.
Examples
The following example enables iSNS communications and client registrations using TCP protocol to the iSNS server at 10.1.70.43, using the default port 3205:
[SN5428-2A]# isns enable tcp server 10.1.70.43The following example enables iSNS communications and client registrations using UDP protocol to the iSNS server at 10.1.20.21, using port 1443:
[SN5428-2A]# isns enable udp server 10.1.20.21 port 1443The following examples disables all iSNS communications and client registrations:
[SN5428-2A]# no isns enableRelated Commands
isns refresh
To force the storage router to reregister all device registrations with the iSNS server, use the isns refresh command.
isns refresh
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Administrator.
Command History
Usage Guidelines
Use the isns refresh command to manually force the storage router to reregister all iSNS entities, storage nodes and network portals. Use the show isns objects commands to view the iSNS client and device registrations.
Examples
The following example refreshes the client and device registrations for the storage router named SN5428-2A:
[SN5428-2A]# isns refreshRelated Commands
