Quantum SNC Firmware 4 and 5 Reference Guide, 6-00676-05, Ver. A, March 2007, Made in USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not
limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this
publication from time to time without notice.
COPYRIGHT STATEMENT
Copyright 2007 by Quantum Corporation. All rights reserved.
Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of
Quantum Corporation is prohibited by law and constitutes a punishable violation of the law.
TRADEMARK STATEMENT
Quantum, DLT, DLTtape, the Quantum logo, and the DLTtape logo are all registered trademarks of Quantum Corporation.
SDLT and Super DLTtape are trademarks of Quantum Corporation.
Other trademarks may be mentioned herein which belong to other companies.
This manual contains information necessary for command line management of SNCs (Storage Networking
Controllers) in the 5000, 6000, and 7000 product lines, as well as for the SNC 4000. The SNC 6404 and
SNC 7404 are sometimes referred to as the FC blade (FCB) or the I/O blade (IOB). With the restrictions,
noted for individual commands or command sequences, command line operation of the SNC 6404 and SNC
7404 are also within the scope of this document. The level of the firmware code (4.xx.xx or 5.xx.xx)
appropriate to a particular SNC is stated in the compatibility matrix portion of the Release Notes for the
current library or product release.
Explanation of Symbols and Notes
The following symbols appear throughout this document to highlight important information.
INDICATES A POTENTIALLY HAZARDOUS SITUATION WHICH, IF NOT
AVOIDED, COULD RESULT IN DEATH OR BODILY INJURY.
Indicates a situation that may cause possible damage to equipment, loss of
data, or interference with other equipment.
Indicates important information that helps you make better use of your system.
Other Documents you Might Need
The following documents are also available for this product. These documents can be found on the product
CD or at www.quantum.com/support
•The User’s Guide for the SNC in your Scalar library
StorageCare™, Quantum's comprehensive service approach, leverages advanced data access and
diagnostics technologies with cross-environment, multi-vendor expertise to resolve backup issues faster
and at lower cost.
Accelerate service issue resolution with these exclusive Quantum StorageCare services:
•Service and Support Website -- Register products, license software, browse Quantum Learning
courses, check backup software and operating system support, and locate manuals, FAQs,
firmware downloads, product updates and more in one convenient location. Benefit today at
www.quantum.com/support
•eSupport -- Submit online service requests, update contact information, add attachments, and
receive status updates via email. Online Service accounts are free from Quantum. That account can
also be used to access Quantum's Knowledgebase, a comprehensive repository of product support
information. Sign up today at www.quantum.com/esupport
•StorageCare Guardian -- Securely links Quantum hardware and the diagnostic data from the
surrounding storage ecosystem to Quantum's Global Services Team for faster, more precise root
cause diagnosis. StorageCare Guardian is simple to set up through the internet and provides
secure, two-way communications with Quantum's Secure Service Center. More StorageCare
Guardian information can be found at www.quantum.com/guardian
For further assistance, or if training is desired, contact Quantum Technical Assistance Center:
.
.
.
North America:+1-800-284-5101
UK, France and Germany:00800 4 QUANTUM
EMEA:+44 1256 848 766
For worldwide support:www.quantum.com/contactsupport
For the most updated information on Quantum Global Services, please visit www.quantum.com/support
.
2About This Guide and Your Product
Description
This chapter describes the functionality of the Storage Networking Controller (SNC) Firmware 4 and 5.
The SNC interface between storage and host provides Fibre Channel to SCSI connectivity or Fibre Channel
to Fibre Channel connectivity.
The SNC firmware enables you to map addresses across and between different interfaces, to configure
private maps for security purposes, to condition the data path, and to preserve the persistency of the
address maps when systems, devices, switches, and the SNC are turned on and off. The SNC supports up
to 2048 unique storage devices across multiple interfaces.
Compatible SNC Hardware
This SNC firmware is the operational firmware for:
•SNC 4000, 5000, 6000, and 7000 series
•Pathlight 5000 and Pathlight VX solutions
•Fibre Channel I/O blades in intelligent libraries ("i" series libraries, such as the Scalar i2000 Library
and Scalar i500 Library)
The version of SNC firmware depends on which SNC blade the library uses:
•SNC Firmware 4 is the operational firmware for SNC 4000, 5000, and 6000 series blades, such as
the SNC 6404 blade in the Scalar i2000.
•SNC Firmware 5 is the operational firmware for SNC 7000 series blades, such as the SNC 7404
blade in the Scalar i2000 and Scalar i500.
SNC Firmware 4 and 5 Reference Guide3
Firmware 4 and 5 Features
Firmware 4 and 5 released functionality builds upon the feature set of previous releases, although not all
features are available across product lines. The Firmware 4 and 5 code includes the following features:
Data Path Conditioning
Data path conditioning technology is a set of utilities in the SNC that protect the integrity of the paths carrying
data. They make data transmission faster and more reliable, and they improve overall system availability.
Health checks and heartbeats are conducted at intervals established by the administrator so that fault
conditions can be discovered prior to moving data through the fabric. Error recovery is performed in the data
path to prevent errors in the Fibre Channel layer from causing data transmission (a backup or a restore) to
fail. The error recovery feature requires no administrator intervention. The Host Registration Service (HRS)
is a small utility that can be loaded onto attached hosts, to provide data path checks from the host
perspective.
Multi-Path Mapping
Multi-path mapping enables an administrator to map a single Fibre Channel-attached storage device
through all Fibre Channels on the SNC to provide redundancy. Both manual and automatic versions of the
multi-path feature are available. The automatic version of this feature is used by specialized, highavailability host software. Both versions require a license.
WWN Change Capability
The world wide name (WWN) change capability enables an administrator to change the WWN on the SNC.
Text is posted during the procedure regarding the requirement to maintain a globally unique name. A
password is required in order to complete the change. The world wide node name or just the world wide port
name can be changed. This feature is being implemented to facilitate SNC replacement.
eVPS
The extended virtual private SAN (eVPS) feature enables an administrator to map any physical device to
any logical unit number (LUN) on any host. This is an additional layer of LUN mapping that is unique for
each initiator attached to the SNC through a Fibre Channel port. eVPS automatically provides backwards
compatibility with virtual private SAN (VPS), a legacy mapping system, so you can upgrade to firmware that
supports this feature transparently. Basic configuration is provided through command line interface (CLI)
configuration functions, but the recommended management tool is the graphical user interface for your
SNC—either the ADIC Management Console or the Library Management Console. eVPS also supports inband management through Application Programming Interface (API) extensions to the existing
maintenance in/out functions supported by VPS.
Fibre Channel Host Port Failover
This feature establishes one Fibre Channel port as the operating port and the other as the alternate port.
The alternate port is on standby for the operating port. If an operating port fails, the alternate port takes over
transparently. The configuration is persistent. This feature requires two Fibre Channel ports to be configured
as targets in point-to-point mode.
Both SNC FC connections or at least two FC blade connections are run to a FC switch. A single connection
to the FC host is then run from the FC switch. No explicit changes to the host driver, host bus adapter
firmware or application software is required.
4Description
Alien Firmware Download Prevention
The SNC firmware now prevents the wrong POST image from being programmed into flash.
Enhanced Data Streaming
Enhanced Data Streaming is a function to allow continuous activity on all Fibre Channel ports. It is primarily
used for environmental testing, but it is also useful for testing at customer sites.
SNC Firmware 4 and 5 Reference Guide5
6Description
Setup and Configuration Routines
CAUTION
The procedures in this section are not intended to be used with Fibre
Channel Blades (FCBs) in intelligent libraries ("i" series libraries,
such as Scalar i2000 and Scalar i500) or Pathlight VX systems. Use
the appropriate graphical user interface.
This section contains detailed procedures for basic configuration:
•Preparing SAN Components
•Configuring a Fibre Channel Host SAN
•Configuring a SCSI Host SAN
•Configuring the Ethernet Network
•Using DHCP
•Setting the Date and Time
•Creating User Accounts
•Configuring Ports
For using special features:
•R
eplacing a SCSI Drive
•Configuring Channel Zoning
•Configuring Host Port Failover
•Configuring eVPS
•Using the WWN Lock Mode
•Configuring Host Port Failover
For maintaining and troubleshooting the SNC:
•R
eplacing a SCSI Drive
•Saving a Configuration File
•Updating Firmware
•Loading a Configuration File
•Changing the WWN
SNC Firmware 4 and 5 Reference Guide7
•Retrieving Information About Events
Preparing SAN Components
Before connecting FC (Fibre Channel) or SCSI cables to the SNC, make sure that the SNC:
•Has desktop or rack mount hardware installed
•Has Ethernet cable from the network hub or switch connected to its 10/100 BaseT RJ-45 Ethernet
port for remote management and optional service access
•Has a null modem RS-232 cable connected from its 9-pin service port to a service terminal (PC or
laptop) and a terminal emulation session (for example, HyperTerminal) running on the service
terminal at 19.2K-8-N-XON/XOFF
Preparing Fibre Channel Hosts
Make sure that the host systems:
•Are running the required versions of host platform software and operating system patches.
Download what you need from the manufacturer’s website
•Have compatible Fibre Channel HBAs (Host Bus Adapters) and the appropriate HBA firmware,
BIOS, and device driver installed
•Have HBA(s) configured for Fibre Channel (FC) Loop if they are attached to the SNC, or Point-ToPoint, if attaching to an FC switch
•Have labeled FC cables attached to them, but not yet attached to the SNC (they may be attached
to an intermediate switch, if there is one)
•Have the optional HRS (Host Registration Service) installed if virtual private map (VPM), Scalar
firewall manager (SFM) or extended virtual private SAN (eVPS) is being used
Preparing Fibre Channel Switch
If an FC switch or FC disk subsystem is being used, make sure that:
•The switch or subsystem has been configured
•Its FC cables are labeled and have been run to the SNC, but are not yet connected
•The FC cables are long enough to ensure adequate strain relief
•The FC cables are secured
•The switch is turned on and operational
Refer to the device manufacturer’s documentation for configuration information.
Preparing SCSI Tape or Disk Devices
If SCSI devices are being used, make sure that:
•SCSI IDs have been configured
•The SCSI cables have been labeled and are connected to the SNC
•The SCSI cables have adequate strain relief
•The SCSI cables are secured with mounting screws
8Setup and Configuration Routines
•The SCSI devices are turned on and operational
CAUTION
Note
Refer to the device manufacturer’s documentation for configuration information.
Preparing SCSI Hosts
Make sure that the host systems:
•Are running the required versions of host platform software and operating system patches
•Have compatible HBAs (host bus adapters) and the appropriate HBA firmware, BIOS and device
driver installed. Download what you need from the manufacturer’s websites.
•Have labeled SCSI cables attached to them and to the SNC
•Have the optional HRS (host registration service) installed to facilitate use of VPM (virtual private
map)
•Are turned on
Preparing FC Tape or Disk Devices
If FC devices are being used, make sure:
•That the FC cables have been labeled and are connected to the SNC
•That the FC cables have adequate strain relief
•That the FC cables are secured
•That the FC devices are turned on and operational
Refer to the device manufacturer’s documentation for configuration information.
Configuring a Fibre Channel Host SAN
After you have prepared system components according to the section Preparing SAN Components on page
8, configure the SAN. Configure features such as HPF before attaching hosts to the SAN.
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
To configure the SAN
1Connect a service terminal to the service port. For the location of this port, see Figure 1
the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
2Turn the power on the SNC. For the location of this switch, refer to the User’s Guide for your SNC.
on page 14, or
Allow sufficient time for the SNC to boot up completely.
3Press the Enter key on the service terminal.
If the prompt is not displayed, go to Service Port MAP
SNC Firmware 4 and 5 Reference Guide9
on page 187.
Within one minute, the RDY LED on most SNCs should start flashing once per second and the done
CAUTION
Note
executing startup script message should be displayed on the service terminal. On the SNC 6101, it may
take a little longer.
For the location of the RDY LED, see Figure 1
on page 14, or the User’s Guide for your SNC.
From the service terminal, issue the initializeBox command to return the SNC to its default
settings. For more information about this command, refer to initializeBox
on page 92. This command
causes the SNC to reboot.
Only use the initializeBox command on a new or a replacement
SNC. This command resets the Fibre and SCSI Channels, clears the
device map and the event log, and disables all enabled features.
4Issue the version command to make sure that the proper version of the operational firmware is
installed. For more information about this command, refer to version
5Configure the Ethernet connection. For instructions, refer to Configuring the Ethernet Network
on page 136.
on page
13.
6Optionally, add a user account for telnet. For instructions, refer to Creating User Accounts
on page 18.
7Issue the targets command from the service terminal. It can take several minutes for the devices to
be available for discovery. For more information about this command, refer to targets
If results are not as expected, follow the procedures in the SCSI Channel MAP
on page 132.
on page 172.
8Issue the hostTypeShow command to view host type settings for the Fibre Channel ports. For more
information about this command, refer to hostTypeShow
on page 86.
If you are using SFM, VPS, or eVPS, go to the next step. SFM, VPS, and eVPS
use an internal setting for the host type.
Table 1Host Type Settings for Fibre Channel Ports
Host TypeAliasUsage
AIXNot ApplicableAIX
AS400as/400, os/400, os400AS400
Autosense/NTNot Applicablefunctions identically to “NT”
NTwindows“NT” is the default setting
Gatewayfcr-2, pv-136t-fc, adic sncGateway
GenericNot ApplicableThe host does not use a supported host type
HPUXhp-uxHPUX
LinuxNot ApplicableLinux
NetwareNot ApplicableNetware
Solarissun, linuxSolaris
UnknownNot ApplicableThe host type is unknown or is based on the value
set by VPS
UnisysNot ApplicableUnisys
10Setup and Configuration Routines
If the hosts to be connected are not the type shown in the output of the command, issue the setHost
CAUTION
Note
command to set the host type for each incorrect Fibre Channel port. For more information about this
command, refer to setHost [port],"OS"
9Turn off the FC host(s).
If this SNC is a replacement, and the WWN of the replacement SNC
must be the same as the WWN of the replaced SNC, refer to Changing
the WWN on page 33.
on page 114.
10 If you are going to configure host port failover (HPF), refer to C
before turning on the FC host(s).
11 Connect the FC cables from the FC HBA(s) to the SNC (or from the intermediate switch to the SNC).
12 Turn on the FC host(s).
•If the appropriate FC connection status LEDs for the attached hosts are not on, check FC cables.
•See Figure 1
series SNC or SNC 6101.
•You may have to change the polarity of the FC cables.
•You may have to change port configuration. For instructions on doing so, refer to C
on page 19.
•If problems persist, go to the Fibre Channel MAP
13 Issue the fcShow command to show the status of the FC interface that is installed and connected. For
more information about this command, refer to fcShow [level]
14 Issue the fcShowDevs command to show SCSI target devices that are connected as seen by the Fibre
Channel interface. For more information about this command, refer to fcShowDevs
•If you are running the 5000 or 6000 series, look for FW State=Ready for each FC interface. If FW State=Ready, but devices are not all displaying, go to the SCSI Channel MAP
•If you are running 7404, or if any state other than Ready is specified, go to the Fibre Channel MAP
on page 178.
on page 14 for the placement of the FC1 and FC2 connection status LEDs on a 5000
on page 178.
onfiguring Host Port Failover on page 27
onfiguring Ports
on page 73.
on page 75.
on page 172.
15 Use appropriate host system utilities for disk and/or tape. If all devices are not available, reboot the host
system(s) and check again.
16 Save the configuration to a location you will be able to access if the SNC fails. Refer to S
Configuration File on page 30.
17 Issue the fcShowNames command and save the output to a location you will be able to access if the
SNC fails. For more information about this command, refer to fcShowNames
18 Attach the hosts (or the switch to which the hosts are attached) to the SNC.
on page 76.
aving a
Configuring a SCSI Host SAN
If you are running the 6101, 6404, or 7404, you cannot configure a SCSI Host
SAN.
After you have prepared system components according to the section Preparing SAN Components on page
8, configure the SAN. Configure features such as AMP before attaching hosts to the SAN.
SNC Firmware 4 and 5 Reference Guide11
To configure the SAN
Note
CAUTION
CAUTION
1Connect a service terminal to the service port of your SNC. For the location of this port, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
2Turn the power on the SNC. For the location of this switch, refer to the User’s Guide for your SNC.
Allow sufficient time for the SNC to boot up completely.
3Press the Enter key on the service terminal.
If the prompt is not displayed, go to Service Port MAP
Within one minute, the RDY LED should start flashing once per second and the done executing startup script message should be displayed on the service terminal.
For the location of the RDY LED, see Figure 1
4From the service terminal, issue the initializeBox command to return the SNC to its default
settings.
For a discussion of this command and its output, refer to initializeBox
Only use the initializeBox command on a new or a replacement
SNC. This command resets the Fibre and SCSI Channels, clears the
device map and the event log, and disables all enabled features.
on page 14, or the User’s Guide for your SNC.
on page 187.
on page 92.
on
5From the service terminal, issue the version command to make sure the proper version of operational
firmware is installed. For more information about this command, refer to version
6Issue the
"Target." For more information about this command, refer to scsiHostChanSet [channel],[mode]
page 109.
7Issue the
on page 125.
8Issue the
v
pmFeatureEnable "licensekeystring" on page 140.
•If you are going to use automatic multi-pathing (AMP), go to R
9To determine what device IDs are available for use, issue the targets command.
For an example of the targets command and its output, refer to targets
target devices to which you have access. The numbers you need are in the "Idx" column. If you are
using AMP, targets will appear twice in the list. Do not map any target more than once.
scsiHostChanSet command, setting the channel where the host will be connected to
snReset command. For more information about this command, refer to snReset [channel]
vpmFeatureEnable command. For more information about this command, refer to
While it is acceptable to enable VPM from the command line by
following the procedure specified above, the preferred interface for
managing VPM is the graphical user interface.
eplacing a SCSI Drive on page 28.
•If you configured AMP, issue the mapRebuildDatabase command. For more information
about this command, refer to mapRebuildDatabase
on page 97.
on page 132. Take note of the
on page 136.
on
10 Configure the Ethernet connection.
For instructions, refer to Configuring the Ethernet Network
12Setup and Configuration Routines
on page 13.
11 Issue the setScsiAssign command. For more informationabout this command, refer to
CAUTION
CAUTION
Note
Note
setScsiAssign [devID], [channel], [id], [lun]
While it is possible to configure VPM assignments from the command
line, the code to be manipulated can be so complex, that users are
encouraged to use the graphical user interface.
12 Issue the showScsiAssign command.
•Verify that all target devices are available to the host system.
•Use appropriate host system utilities for disk and/or tape.
on page 115.
•If results are not as expected, refer to V
13 Save the configuration to a location you will be able to access if the SNC fails. Refer to S
Configuration File on page 30.
14 Attach the hosts to the SAN.
PM MAP on page 187 or Start MAP on page 167.
aving a
Configuring the Ethernet Network
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
If you are configuring an SNC 4000, 51xx, or 6101, you can choose to use
DHCP instead of static IP addresses. Refer to Using DHCP
The SNC can be accessed over an Ethernet connection in addition to access by means of the service port.
To configure an IP address for the SNC
1Connect a service terminal to the service port. For the location of this port, see Figure 1
the User’s Guide for your SNC.
.
on page 14, or
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
SNC Firmware 4 and 5 Reference Guide13
Figure 1SNC connector and LED panel
Note
CAUTION
Note
RDY LED
FC1 and FC2 connection LEDs
service port
Ethernet port
The placement of the LEDs, SCSI ports, and service port on your SNC may not
be the same as in this example. Refer to the Hardware User’s Guide for your
SNC.
In all of subsequent steps of this procedure, use the name and
number values that your network manager and you have agreed to
use.
2Issue the hostNameSet
In the example shown, the host name of the SNC was “SN60023”, and it is now being set to “foster.”
The shell prompt will change to reflect the new name.
SN60023 > hostNameSet "foster"
Target hostname set to foster
value = 0 = 0x0
foster >
Step 2 is optional.
3Configure a static IP address, by issuing the ethAddrSet
The IP address is specified as four decimal numbers, separated by periods.
foster > ethAddrSet "192.168.1.54"
Host Address set to 192.168.1.54 for Ethernet interface
value = 0 = 0x0
If you need to set a netmask, specify it after the network address:
foster > ethAddrSet "10.0.0.2", "255.0.0.0"
If you need a network route and/or default gateway, use gateAddrSet
command to set the SNC name.
command to set the host network address.
to specify it.
foster > gateAddrSet "192.168.1.1"
value = 0 = 0x0
14Setup and Configuration Routines
When more complicated routing is required, use the route command to specify the destination address,
CAUTION
CAUTION
Note
Note
as a full address (single host) or as an abbreviated subnet address.
4If you want to add users, follow the procedure in Creating User Accounts
5Issue the reboot
command to reboot the SNC:
below, before rebooting.
Using DHCP
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
An IP address assigned to a device by a Dynamic Host Configuration Protocol (DHCP) server does not
change unless the device is disconnected from the network for a period that exceeds the lease period
defined by the DHCP server. This time period is typically around 3 days. The SNC stores information from
the DHCP server in its boot parameters and attempts to reuse it on subsequent boots in case the DHCP
Server is unreachable.
1Make sure that a DHCP server is present on the network.
If a DHCP server is unreachable, the SNC Ethernet port will be
unusable.
2Connect a service terminal to the service port. For the location of this port, see Figure 1
the User’s Guide for your SNC.
on page 14, or
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
3If you’re using FW 4 and an SNC 4000 or 510x, issue the dhcpEnable command.
4Reboot the SNC for the change to take effect.
5Connect to the SNC serial port and issue the bootShow command to determine the assigned network
address. Refer to bootShow
You must know the IP address in order to use telnet or the ADIC Management
Console (AMC).
6If you were referred to this section by another procedure, return to that procedure.
on page 55.
SNC Firmware 4 and 5 Reference Guide15
Setting the Date and Time
CAUTION
Note
Note
Note
Note
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
The SNC allows you to set the real time clock, to add a timeserver to the system, and to synchronize the
real time clock to the timeserver.
Setting the Real Time Clock
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
on page 18.
on
2Use the rtcDateSet command to set the real time clock.
The time will revert to the time set on the real time clock on the SNC.
Synchronizing the Real Time Clock with the Timeserver
1Use the setTimeHost command to add a host running timeserver to the SNC system. For more
information about this command, refer to setTimeHost "timeserver"
SNC > setTimeHost "butter"
Time Host butter value = 0 = 0x0
SNC >
2Synchronize the real time clock on the SNC with the timeserver using the rtcSetCurrent command.
For more information about this command, refer to r
SNC > rtcSetCurrent
value = 0 = 0x0
SNC >
tcSetCurrent on page 107.
on page 116.
Creating User Accounts
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
Before you access the SNC using telnet, add a user account.
For inband connections, the default user account name is admin and the
default user account password is password.
To add a user account
1Connect a service terminal to the service port. For the location of this port, see Figure 1
the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
2Issue the userAdd command. For more information about this command, refer to the commands
beginning with user in the Service Port Command Reference
The user name you specify must be three or more characters. The password
CAUTION
Note
Note
you specify must be eight or more characters.
Configuring Ports
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
The settings in Table 3 are the default settings on the SNC:
Table 3Default SNC Channel Settings
Fibre ChannelsPublic, Target, Loop
Host Type: NT
SCSI ChannelsInitiator
Termination Enabled
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Use appropriate firmware commands to accommodate SAN configurations that do not conform to the
default settings. For example, if your system contains few devices that are capable only of arbitrated
loop, the default connection type can be changed to from "loop" to "loop preferred." Refer to Table 4
and Table 5
FC Device AttachmentRequired Channel SettingsService Port Commands
FC Host type
1
NT (default)
AIX
AS400
setHost [port], “OS”
and
reboot
Autosense/NT
Gateway
Generic
HP-UX
Linux
Netware
Solaris
Unknown
Unisys
FC SwitchPoint-to-Point
Target (default)
fcConnTypeSet [port],
[connection]
and
fcRestart
FC disk or FC tape
device
Loop (default)
Initiator
2
fcPortModeSet [port],
[mode]
and
fcRestart
1 If eVPS is being used, the FC Host type does not need to be configured manually.
2 The SNCs that use Firmware 4 support 64 initiators per Fibre Channel port
Table 5SCSI channel configuration quick reference
SCSI Device Attachment
Required Channel
Settings
Service Port Commands
SCSI HostTargetscsiHostChanSet
[channel],[mode]
and
reboot
SCSI disk and tape
SCSI Bus shared (dual paths)
SCSI Bus Reset on Power
Up Disabled
scsiResetDisableSet
[channel],[mode]
and
reboot
SCSI disk and tape
SCSI Y-cable (SNC not at
end of SCSI bus)
Termination DisabledscsiTermSet
[channel],[termination]
and
reboot
20Setup and Configuration Routines
Mapping Multiple Paths to Targets
CAUTION
Note
CAUTION
Note
Note
CAUTION
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
The automatic multi-path mapping (AMP) and manual multi-path mapping (MMP) features allow you to map
alternate paths to the SNC from switch-attached FC devices.
Both automatic and multipath mapping require licensing.
To map multiple Fibre Channel paths to targets
1Be sure that the devices, the switch, the host, and the SNC have been powered on and have finished
booting. The SNC connects at least two of its Fibre Channel connections to the switch, which connects
to the devices.
These instructions do not take into account zoning software that may
be on the switch.
2Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
If you are configuring multiple paths to targets after host connections
have been established, the change in target IDs can damage host
configurations. Optimally, configure multipath mapping as part of
setup.
3Issue the ampFeatureEnable command. For more information about this command, refer to
mpFeatureEnable “license” on page 53.
a
4Disconnect SNC Fibre Channel cables from the switch.
5Clear the map database by issuing the mapWinnowDatabase command. For more information about
this command, refer to mapWinnowDatabase
on page 18.
on page 100.
on
6Set the multi-path mapping configuration by issuing the mapMultipathSet command.
SNC Firmware 4 and 5 Reference Guide21
Use manual mode (mapMultipathSet 1) when using special host software. Manual mode exposes
CAUTION
CAUTION
all paths to devices, including paths that are hidden because one target device’s World Wide Port Name
is identical to another target device’s World Wide Port Name. Manual mode is used in conjunction with
special host software, so that the user does not inadvertantly identify a single device as two devices,
which can lead to data corruption. Host software allows the user to set one path to the device as primary
and the other as secondary.
SNC > mapMultipathSet 1
Multipath mode set to manual mode.
value = 1 = 0x1
SNC >
Use automatic mode (mapMultipathSet 2) when special host software is not available and all
devices are capable of responding to an inquiry with a unique serial number. Each target drive must
also have two ports, both of which are connected to separate switches. Each switch must be connected
to an SNC FC port. If either switch fails or any cables or GBICs fail on one path, failover automatically
occurs to the other path.
SNC > mapMultipathSet 2
Multipath mode set to automatic mode.
value = 2 = 0x2
SNC >
For more information about this multipath settings, refer to mapMultipathSet
7Reconnect SNC Fibre Channel cables to the switch.
8Issue the fcRestart command. For more information about this command, refer to fcRestart [port]
page 73.
9Issue the mapShowDevs command to confirm that devices have been remapped using the multi-path
configuration that was selected.
If devices have already been mapped, and they need to be remapped,
use the mapRemoveDevice command. Then issue the fcRestart
command.
on page 96.
on
Configuring Channel Zoning
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
Access between ports configured for host access and ports configured for storage access can be enabled
or disabled as required. The ability to create restricted access on a full-channel basis is called channel
zoning. The default configuration is for all Fibre Channels to have access to all SCSI channels. Channel
zoning is also possible from an FC target channel to an FC initiator channel.
In certain instances, customers may wish to combine the channel level security of channel zoning with the
advanced LUN level security of Scalar Firewall Manager (SFM) to enable a mix of load balancing and host
specific security. In this instance, channel zoning is used to provide load balancing while SFM delivers
resource security and heterogenous host support.
Channel zoning enables load balancing by configuring certain SCSI channels to only be accessible across
specific SAN connections. This is typically done by defining SCSI channels 1 and 2 to be accessible through
FC port 1of the SNC, and SCSI channels 3 and 4 to be to be accessible through FC port 2. This insures that
data traffic is split across the SNC SAN interfaces.
22Setup and Configuration Routines
SFM is configured as usual, but the administrator must be aware that SFM does not override channel
CAUTION
Note
Note
CAUTION
zoning. A host must have LUN level access to a drive through SFM, and be bound to the correct SNC FC
port. If the host is incorrectly connected to the SNC, the combination of channel zoning and SFM may
prevent the host from seeing resources.
While it is possible to configure channel zoning from the command
line by following the procedure specified below, the preferred
interface for channel zoning is the ADIC Management Console (AMC).
For instructions on installing and using AMC, refer to the ADIC Management Console User Guide.
To configure Channel Zoning
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
on
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
on page 18.
2Issue the setFcChanMask command.
Channel Zoning settings take precedence over settings made by VPS/
SFM, and eVPS.
This command uses bitmasked values to enable or disable access. For a complete discussion of the
formula used to obtain appropriate values, refer to setFcChanMask [channel, bitmask]
Table 6
lists some common values. The examples in Table 6 are all given for Fibre Channel 1, but the
on page 112.
bitmasked values representing SCSI Channel access would not change if Fibre Channel 2 were
specified instead.
Table 6Common Channel Zoning Configuration Codes
Command StringEffect
SNC> setFcChanMask 1,1008Enables access to SCSI channels 1 - 4 for Fibre
Channel 1
SNC> setFcChanMask 1,1022Enables access to SCSI channel 1 for Fibre
Channel 1.
SNC> setFcChanMask 1,1021Enables access to SCSI channel 2 for Fibre
Channel 1.
SNC> setFcChanMask 1,1019Enables access to SCSI channel 3 for Fibre
Channel 1.
SNC> setFcChanMask 1,1015Enables access to SCSI channel 4 for Fibre
Channel 1.
SNC> setFcChanMask 1,1020Enables access to SCSI channels 1-2 for Fibre
SNC> setFcChanMask 1,1011Enables access to SCSI channels 3-4 for Fibre
Channel 1.
3After issuing the setFcChanMask command, reboot for the changes to take effect.
Configuring VPM
The VPM (Virtual Private Map) software configures access to specific LUNs for certain SCSI hosts. A
maximum of 256 LUNs per host can be mapped.
While it is possible to configure VPM from the command line by
following the procedure specified below, the preferred interface for
VPM is the ADIC Management Console (AMC). For instructions on
installing and using AMC, refer to the ADIC Management Console
User Guide.
Optionally, before configuring VPM, install the HRS on the hosts involved. Instructions for doing so are in
the User’s Guide for your SNC. It is available for Windows, AIX, HP-UX, Linux, and Solaris hosts.
You must have a license to use VPM.
To configure VPM
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Issue the vpmFeatureEnable command. For more information about this command, refer to
v
pmFeatureEnable "licensekeystring" on page 140.
3Issue the targets command. For more information about this command, refer to targets
Take note of the target devices to which you have access. The numbers you need are in the "Idx"
column.
4Issue the setScsiAssign command. For more information about this command, refer to
setScsiAssign [devID], [channel], [id], [lun]
on page 18.
on page 132.
on page 115.
on
5Issue the showScsiAssign command.
If results are not as expected, refer to V
6Reboot the host(s) or use host utilities to rescan available targets.
24Setup and Configuration Routines
PM MAP on page 187.
Configuring eVPS
CAUTION
CAUTION
Note
Note
Note
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
The eVPS (extended Virtual Private SAN) software configures access to specific LUNs for certain Fibre
Channel hosts. Access to these LUNs can be ordered in different, host-appropriate ways for each host. A
maximum of 256 LUNs per host can be mapped, up to an overall device total of 2048.
While it is possible to configure eVPS from the command line by
following the procedure specified below, the preferred interface for
eVPS is the ADIC Management Console (AMC). For instructions on
installing and using AMC, refer to the ADIC Management Console
User Guide.
Optionally, before configuring eVPS, install HRS on the hosts involved. Instructions for doing so are in the
ADIC Management Console User’s Guide. HRS is available for Windows, AIX, HP-UX, Linux, and Solaris
hosts.
You must have a license to use eVPS.
To configure eVPS
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Issue the vpsFeatureEnable command. For more information about this command, refer to
vpsFeatureEnable "license key string"
3Issue the vpsShow command. For more information about this command, refer to vpsShow [hostIndex]
on page 148.
Take note of the host index number. The host index number is the number in the ID column.
4Issue the targets command. For more information about this command, refer to targets
on page 143.
on page 18.
on page 132.
on
Take note of the target devices to which you have access. The numbers you need are in the "Idx"
column.
5If you are configuring access to all contiguous LUNs, issue the vpsAccessSet command. For more
information about this command, refer to vpsAccessSet [hostIndex],[Starting lun],[Ending lun],[Access]
on page 141.
SNC Firmware 4 and 5 Reference Guide25
Use the number you noted in Step 3 for the value [hostIndex]. Use the lowest number that was
Note
Note
Note
output by the targets command you issued in Step 4
highest number that was output by the targets command you issued in Step 4[Ending lun]. Use an access value of "1" to enable access to these LUNs.
If LUNS are not contiguous, use the vpsSparseAccessSet command. For more information about
this command, refer to vpsSparseAccessSet[hostindex],"LUN string",[
6Issue the vpsAccessApply command.
7Reboot the host(s) or use host utilities to rescan available targets.
as the value for the [Starting lun]. Use the
as the value for the
access] on page 149.
Using the WWN Lock Mode
The wwnLockModeSet command gives a SAN administrator more direct control over which hosts
(initiators) are able to access the library. SFM/VPS/eVPS must already be enabled for it to be used.
A maximum of 64 initiators can be connected per FC port. If the VPS host table is forced to retain host
entries for initiators that do not have authority to access LUNs available through that SNC, then hosts which
are authorized to access those LUNs may not be able to connect to the SAN. In situations where there are
large numbers of initiators, and SFM/VPS/eVPS has been enabled, the contents of the host table can be
controlled by setting the wwnLockMode to ‘1” (enabled). Then use vpsInitDelete [host ID]
unauthorized hosts and vpsInitAdd
The WWN lock mode default state is disabled.
[hiWWN],[loWWN] to add authorized hosts to the host table.
to remove
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Before you enable WWN lock mode, check to see if if SFM/VPS/eVPS is enabled. If not, enable it first.
For instructions, refer to sfmFeatureEnable "license key string"
All hosts whose names are unknown in the VPS host table are deleted.
on page 18.
on page 118 or vpsFeatureEnable
on
The wwnLockMode persists across reboots.
4Check the state of the WWN lock mode, by issuing the wwnLockModeShow command.
SNC > wwnLockModeShow
WWN Locking Mode: Disabled
26Setup and Configuration Routines
value = 0 = 0x0
Note
CAUTION
Note
Note
Note
SNC >
5Display a list of hosts that have access to the SNC by issuing the sfmShow command or the vpsShow
command:
SNC > sfmShow
The sfmShow command and the vpsShow command display all the hosts in the VPS host table. For
more information, refer to sfmShow [hostIndex]
Only the hosts in the VPS host table have access to the command and control
LUN when WWN lock mode is enabled.
a. Remove any unwanted hosts from the VPS host table by issuing the vpsInitDel command.
For more information, refer to vpsInitDelete [host ID]
b. Add hosts to the VPS table by issuing the vpsInitAdd command. For more information, refer
to vpsInitAdd
[hiWWN],[loWWN] on page 146.
on page 120.
on page 146.
Configuring Host Port Failover
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
The host port failover (HPF) feature uses an active/passive methodology. An active (primary) port is used
for host communications, while the passive (standby) port is kept idle. Port failover occurs when connectivity
between the primary port and the SAN ceases to function correctly. This can be caused by a loss of signal
between the ports or excessive errors on the connection. The Fibre Channel ports are connected to the host
computer by means of a switch.
Use automatic or manual multi-pathing (AMP or MMP) to enhance data path
protection for the part of the data path that connects the SNC to devices. Refer
to R
eplacing a SCSI Drive on page 28.
To configure HPF
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
on page 18.
on
2Issue the fcConnTypeGet command to make sure the FC ports on the SNC are configured for point
to point.
SNC Firmware 4 and 5 Reference Guide27
If necessary, issue the fcConnTypeSet command to change the setting. For more information about
Note
Note
this command, refer to fcConnTypeSet [port],[connection]
3Issue the fcPortModeGet command to make sure the FC ports on the SNC are configured as targets.
If necessary, issue the fcPortModeSet command to change the setting. For more information about
this command, refer to fcPortModeSet [port],[mode]
4Issue the hpfFeatureEnable "licensekey" command. For more information about this command,
refer to hpfFeatureEnable "licensekey"
on page 86.
on page 69.
on page 72.
5Issue the hpfShow command. For more information about this command, refer to hpfShow
The default configuration will not result in host port failover. Both FC ports on an SNC are active after
HPF is enabled. Each FC port is a virtual port with a standby list consisting entirely of itself. In order for
host port failover to occur, at least one port needs to be on standby list for each active port.
6Issue the hpfRemovePort command to remove one of the active ports from its own virtual port list. For
example,
SNC > hpfRemovePort 2,2
removes active port 2 from the standby list for virtual port 2.
For another example of the command and its output, refer to hpfRemovePort [virtual port]
on page 88.
7Issue the hpfAddPort command to add the port that you just removed to the other port’s standby list.
For example,
SNC > hpfAddPort 1,2
adds port 2 to the standby list for virtual port 1.
For another example of the command and its output, refer to h
page 86.
Use hpfShow as needed to monitor the effects of each command.
pfAddPort [virtual port],[phys port] on
on page 89.
,[phys port]
8Issue the hpfSetErrorRecovery command to set the recovery scenario for ports configured by HPF.
One choice is to have a port return to active status after recovery occurs. Other choices are "return to
standby" which means that the recovered port becomes the new standby port, and "require intervention"
which means that the port stays down until the hpfAddPort command is issued.
For an example of the command and its output, refer to hpfSetErrorRecovery [value]
on page 88.
Replacing a SCSI Drive
When a storage device managed by the SNC is replaced, the device map can be manipulated so that the
host does not require reconfiguration. To do this, set the replacement device’s SCSI target ID to match the
target ID of the removed device.
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
28Setup and Configuration Routines
on
Note
If you are using Ethernet, open a telnet program to connect to the SNC. Before
CAUTION
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
on page 18.
2Issue the mapShowDatabase command. Use the listing of the device map that is output to identify the
offline drive.
SN601193 > mapShowDatabase
devId Type Chan tId tLun UID Path
------------------------------------------------------000 SNA 127 127 007f 00000060:451704a9 SINGLE
SN: 601193
001 SCSI 001 006 0000 20100060:451704a9 SINGLE
SN:
002 SCSI 002 002 0000 20200060:451704a9 SINGLE
SN:
003 SCSI 002 001 0000 20300060:451704a9 SINGLE
SN:
value = 0 = 0x0
SN601193 >
If you are not sure which drive is offline, issue the scsiShow command. The scsiShow command lists
all active SCSI drives attached to the SNC. The offline drive is the drive that appears in
A comparison of the output of the mapShowdatabase and scsiShow commands makes it clear that
the two drives on SCSI Channel 2 (in the mapShowDatabase output, check the "Chan" column for
devIDs 2 and 3) are not just offline, they are not currently connected at all.
3Unattach the failed drive from the SNC, if it is not already unattached.
4Follow the required library procedures to remove and replace the failed drive. For most libraries, the
SCSI ID can be confirmed from the library operator panel. For the Scalar 1000 and the Scalar 10K, set
the pinwheel on the drive itself to correctly configure the SCSI ID.
Make sure that the SCSI Target ID on the replacement drive is the
same as that of the failed drive.
SNC Firmware 4 and 5 Reference Guide29
5Attach the replacement drive to the same SNC bus as the failed drive.
CAUTION
CAUTION
Note
Note
Do not attach the drive to the SNC SCSI bus before the SCSI ID is set.
6Reboot the SNC so that the SNC rescans for devices.
7Issue the mapShowDevs command.
SN601193 > mapShowDevs
devId Type Chan iId iLun UID tId tLun Handle Path
------000 SNA 127 127 007f 20000060.451704a9 001 000 091bf700h SINGLE
SN: 601193
001 SCSI 001 006 0000 20100060.451704a9 255 255 09ffbc88h SINGLE
SN: ADIC201101595
002 SCSI 002 002 0000 20200060.451704a9 255 255 091b2488h SINGLE
SN: 6811121075
003 SCSI 002 001 0000 20300060.451704a9 255 255 09ffb388h SINGLE
SN: 6811107750
value = 0 = 0x0
SN601193 >
If the replacement drive appears at a different ID than the original devID, make sure that the drive is
attached to the correct SCSI bus and that the drive’s SCSI Target Id (tID) is correct.
Saving a Configuration File
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
Using HyperTerminal to save the configuration takes much longer than using
the graphical user interface.
It is good practice to save the configuration to a remote system any time it changes.
To save the configuration using a HyperTerminal telnet connection
1Connect a service computer to the network that the SNC is on or to the Ethernet port of the SNC. For
the location of this port, see Figure 1
Before you connect by means of telnet, configure a user account. For
instructions, refer to Creating User Accounts
2Follow the manufacturer’s instructions for installing HyperTerminal on the service computer and
opening a session.
on page 14, or the User’s Guide for your SNC.
on page 18.
3Change the working directory to /nvfs:
cd "/nvfs"
30Setup and Configuration Routines
4Issue the saveConfig <index> command.
CAUTION
CAUTION
5From the HyperTerminal window, select Transfer and Receive File.
6In the Receive dialog box, enter the path to the folder where you want to save the file, or click the
Browse button and navigate to it.
7For the receiving protocol select Zmodem and press the Close button.
From the HyperTerminal window, enter sz "config.cfg" and press Enter.
The filename "config.cfg" is an example of a name. You can specify a different filename, but it must be
in quotes, it must be eight characters or less, and it must end in .cfg.
To save the configuration to a remote computer connected to the serial port
1Connect a service computer to the serial port on the SNC. For the location of this port, see Figure 1
page 14, or the User’s Guide for your SNC.
2Follow the manufacturer’s instructions for installing HyperTerminal on the service computer and
opening a session.
3cd "/nvfs"
4From the HyperTerminal window, at the SNC > command prompt, type sz "<filename>.cfg" and then
press the Enter key.
A ZModem session is automatically initiated. It closes automatically when the file transfer has
completed.
on
Updating Firmware
The recommended interface for updating firmware to all SNCs is the
graphical user interface.
Do not interrupt a fimware FTP. If the process is disturbed, damage to
the SNC can result.
As part of ongoing maintenance, firmware can be updated using an Ethernet connection or a telnet
connection.
To update firmware using ftp
1Connect a service computer to the network that the SNC is on or to the Ethernet port of the SNC. For
the location of ths port, see Figure 1
2FTP to the SNC (using usual telnet user and password).
C:\>ftp 172.16.77.101
Connected to 172.16.77.101.
220 VxWorks (5.4.2) FTP server ready
User (172.16.77.101:(none)): admin
331 Password required
Password:
230 User logged in
3Switch to binary mode.
ftp> binary
SNC Firmware 4 and 5 Reference Guide31
on page 14, or the User’s Guide for your SNC.
200 Type set to I, binary mode
Note
CAUTION
4Upload firmware using "/fwl/fw" as the target.
The character after the "fw" is an "el" (l), not a "one" (1).
ftp> put v042208.bin /fwl/fw
200 Port set okay
150 Opening BINARY mode data connection
226 Transfer complete
ftp: 3542016 bytes sent in 2.74Seconds 1290.82Kbytes/sec.
ftp> quit
C:\>
5Wait for the Firmware Update Complete status message to be displayed on the service computer
indicating successful completion.
6Reboot the SNC for the update to take effect.
To update firmware using the serial port
1Connect a service computer to the serial port on the SNC. For the location of this port, see Figure 1
on
page 14, or the User’s Guide for your SNC.
2Follow the manufacturer’s instructions for installing HyperTerminal on the service computer and
opening a session.
3From the HyperTerminal window, at the SNC > command prompt, type rz and then press the Enter key.
4From the HyperTerminal window select Transfer and Send File.
5From the Send File dialog enter the path and filename where the firmware file is located or click the
Browse button and navigate to it.
6In the Protocol field, select Zmodem and click the Send button.
Make sure the serial cable is secure before you begin. Do not disturb
it during the file transfer. If the process is disturbed, damage to the
SNC can result.
The Zmodem file send dialog will display the current status and it will close automatically when the file
transfer has completed.
7Wait for the Firmware Update Complete status message to be displayed on the service computer
indicating successful completion.
8Reboot the SNC for the update to take effect. For more information about the reboot command, refer
to reboot
on page 103.
If HyperTerminal reports an error, try to send the file again.
9Use the exit command to close the telnet session.
32Setup and Configuration Routines
Loading a Configuration File
CAUTION
Note
Note
CAUTION
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
Using HyperTerminal to upload a configuration file takes much longer than
using the graphical user interface.
A saved configuration can be uploaded as part of recovery from system failure.
To upload a configuration using a HyperTerminal serial connection
1Connect a service computer to the serial port on the SNC. For the location of this port, see Figure 1
page 14, or the User’s Guide for your SNC.
2Follow the manufacturer’s instructions for installing HyperTerminal on the service computer and
opening a session.
3Issue the cd "/fw1/fw" command at the prompt to change the working directory to /fwl/fw.
The character after the "fw" is an "el" (l), not a "one" (1).
4From the HyperTerminal window, at the command prompt, type rz and then press the Enter key.
5From the HyperTerminal window select Transfer and Send File.
6From the Send File dialog enter the path and file name where the configuration file is located or click
the Browse button and navigate to it. In the Protocol field, select Zmodem and click the Send button.
7Wait for the Configuration Update Complete status message to be displayed on the service computer
indicating successful completion.
8Issue the restoreConfig <index> command at the Hyperterminal command line.
9Wait for the Configuration has been cleared. Reboot Required status message to be displayed on the
service computer indicating successful completion.
10 Reboot the SNC for the update to take effect. For more information about the reboot command, refer
to reboot
on page 103.
on
Changing the WWN
Before making any changes to the world wide names of the SNC, read the following discussion in its
entirety.
Do not use this procedure on the SNC 6000 I/O blades in a Pathlight
VX I/O system. The Pathlight VX Storage Processor supplies the
WWN to the SNC 6000 I/O blades.
SNC Firmware 4 and 5 Reference Guide33
All Fibre Channel devices are identified by world wide names (WWNs). These names are used to uniquely
CAUTION
Note
Note
identify a device on a storage area network (SAN) and are used by hosts to correctly connect to the storage
networking controller (SNC) or I/O blade. WWNs are divided into two types: port names, which identify
individual ports, and node names, which identify the entire unit. WWNs are formed of three critical
components:
•Port/Node ID—distinguishes port WWNs from node WWNs
•OUI—identifies the device type, stands for organizational unique identifier
•Device ID—identifies the specific device
Except for the I/O blades in the Pathlight VX, the node ID for Quantum/ADIC devices is always “10:00” and
the port ID is “20:0x” where x is the port number. The OUI is “00:60:45” for the 3000 and 5000 series and
“00:30:8C” for the 6000 and 7000 series. If for any reason you incorrectly enter a WWN, the changes can
be cleared and replaced with the original WWN, which is stored in the SNC.
Only trained and authorized service personnel should use these
procedures. Data corruption or loss may result from the incorrect use
of these procedures. Do not change the WWN of any device on the
SAN before talking to your Quantum-authorized service technician.
Before You Change the WWN on a Replacement SNC
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
on
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Locate the saved copy of the current (pre-replacement) configuration.
3Refer to the output of the fcShowNames command you saved in Step 17
Host SAN or Step 14 of Configuring a SCSI Host SAN. For more information, refer to fcShowNames on
page 76.
4Install and cable the replacement SNC. For more information, refer to Preparing SAN Components
page 8.
5Issue the targets command. For more information about this command, refer to targets
If the output of the targets command is not accurate, go to Start MAP
corrections before proceeding with the WWN change.
on page 18.
of Configuring a Fibre Channel
on
on page 132.
on page 167 and make
Changing the WWN for all FC Ports
Use this procedure when you are replacing one SNC with another, and it is critical that the replacement SNC
use the same WWNs as the replaced SNC.
1Read the section Changing the WW
2Follow the instructions in Before You Change the WWN on a Replacement SN
34Setup and Configuration Routines
N on page 33.
C on page 34.
CAUTION
The WWN override functions are available only from the service port.
CAUTION
CAUTION
CAUTION
These commands cannot be executed if attempted in a telnet session.
3Issue the wwnGlobalSet command to establish a new base WWN.
Using the wwnGlobalSet command will update both the node name and port names. For more
information about this command, refer to wwnGlobalSet
The following messages are displayed:
This command will change the WWN for Fibre Channel Ports.
This should only be done when replacing a failed SNC.You should never
operate 2 FC devices that are set to the same WWN. This may destabilize
your SAN.
The unit will be rebooted after the WWN change.
Do you want to proceed (enter "yes" to continue) :
4Type the word yes and press Enter.
The following message is printed:
Enter the new WWN (or q to quit):
5Enter all eight bytes of the new WWN. Each byte of the entry should be delimited by colons. For
example, enter:
00:00:00:30:8C:02:70:21
on page 150.
The wwnGlobalSet command requires that the first byte be entered
as "00" even if fcShowNames displays "10" in that position.
When entering the WWN, the firmware will confirm that the node ID
and OUI match the existing values. This prevents a user from
accidentally making the SNC appear as another vendor’s device.
The first five bytes of the entry are checked. If the entry is valid, you are prompted for a password.
6Type the password OverrideWWN and press Enter.
This causes the SNC to reboot.
7When the SNC has rebooted, issue the fcShowNames command to verify the change.
Verify that the output in the Node Name column is correct.
8Continue with the replacement procedure as specified by the User’s Guide for your SNC.
Changing a WWN for one FC port
Use this procedure when you are replacing another vendor’s appliance with an SNC and it is critical that
one of the replacement SNC FC ports use the same WWN as the FC port of the replaced appliance.
Because you are changing the SNC WWNs to represent another
vendor’s device, there are no checks to make sure an appropriate
node or port ID or OUI are entered. Use caution. Entering in
inaccurate WWN information could cause communication issues.
1Read the section Changing the WW
SNC Firmware 4 and 5 Reference Guide35
N on page 33.
2Follow the instructions in Before You Change the WWN on a Replacement SNC on page 34.
CAUTION
CAUTION
The WWN override functions are available only from the service port.
These commands cannot be executed if attempted in a telnet session.
3Issue the wwnPortSet command to set the WWPN and WWNN for a single FC port. For more
information about this command, refer to wwnPortSet [port]
The following messages are displayed:
This command will change the WWN for Fibre Channel Port <N>.
You will be asked to provide both the Node WWN and Port WWN for this port.
You should never operate 2 FC devices that are set to the same WWN. This
may destabilize your SAN.
The unit will be rebooted after the WWN change.
Do you want to proceed (enter "yes" to continue) :
4Type the word yes and press Enter.
The following message is displayed:
Enter the new Node WWN (or q to quit) :
5Enter all eight bytes of the new WWNN. The entry should be colon delimited between each byte. For
example, enter:
10:00:00:60:45:02:70:21
on page 152.
The syntax of the entry is checked.
6If the entry is valid, you are prompted to enter the new WWPN:
Enter the new Port WWN (or q to quit) :
7Enter all eight bytes of the new WWPN. The entry should be colon delimited between each byte. For
example, enter:
20:01:00:60:45:02:70:21
The syntax of the entry is checked.
Most vendors require the OUI and device ID to match between the
WWPN and WWNN. Make sure these values match or device
connectivity may not occur. It is possible for the SNC to have a
different WWNN for each port.
If the entry is valid, you are prompted for a password.
8Type the password OverrideWWN and press Enter.
This causes the SNC to reboot.
9When the SNC has rebooted, issue the fcShowNames command to verify the change.
Verify that the output in the Port Name column is correct.
10 Continue with the replacement procedure as specified by the User’s Guide for your SNC.
Clearing Changes to the WWN for all FC ports
Use this procedure when you are removing an SNC that had its WWNs changed to match a pre-existing unit.
1Read the section Changing the WW
36Setup and Configuration Routines
N on page 33.
2Follow the instructions in Before You Change the WWN on a Replacement SNC on page 34.
CAUTION
CAUTION
CAUTION
CAUTION
The WWN override functions are available only from the service port.
These commands cannot be executed if attempted in a telnet session.
The wwnGlobalClear command works only if the wwnGlobalSet
command has been used. To clear port changes made with
wwnPortSet, follow the steps outlined in Clearing Changes to the
WWN for one FC Port on page 37. Then follow this procedure.
3Issue the wwnGlobalClear command. For more information about this command, refer to
w
wnGlobalClear on page 150.
The following messages are displayed:
This command will restore the WWN for Fibre Channel Ports.
This should only be done when there is no SNC set to this WWN.
You should never operate 2 FC devices that are set to the same WWN. This
may destabilize your SAN.
The unit will be rebooted after the WWN change.
Do you want to proceed (enter "yes" to continue) :
4Type the word yes and press Enter.
You are prompted for the password.
5Type the password OverrideWWN and press Enter.
This causes the SNC to reboot.
6After the SNC has rebooted, issue the fcShowNames command to verify the change.
The output in the Node Name column of the of the fcShowNames command should no longer match
the output saved in Step 17
Host SAN.
of Configuring a Fibre Channel Host SAN or Step 14 of Configuring a SCSI
Clearing Changes to the WWN for one FC Port
Use this procedure when you are removing an SNC that had the WWN on one port changed to match the
WWN of a pre-existing unit.
1Read the section Changing the WW
2Follow the instructions in Before You Change the WWN on a Replacement SN
The WWN override functions are available only from the service port.
These commands cannot be executed if attempted in a telnet session.
3Issue the wwnPortClear <port> command. For more information about this command, refer to
wwnPortClear [port]
on page 151.
N on page 33
C on page 34.
The wwnPortClear command does not reset the port WWN to the
factory default if the wwnGlobalSet command has been used. It
resets the port WWN to the value assigned by the wwnPortSet
command.
The following message will display:
SNC Firmware 4 and 5 Reference Guide37
This command will restore the WWN for Fibre Channel Port <x>. This should
Note
Note
only be done when there is no SNC set to this WWN.
You should never operate 2 FC devices that are set to the same WWN. This
may destabilize your SAN.
The unit will be rebooted after the WWN change.
Do you want to proceed (enter "yes" to continue) :
4Type the word yes and press Enter.
You are prompted for the password.
5Type the password OverrideWWN and press Enter.
This causes the SNC to reboot.
6After the SNC has rebooted, issue the fcShowNames command to verify the change.
7The output in the Node Name column of the of the fcShowNames command should no longer match
the output saved in Step 17
Host SAN.
of Configuring a Fibre Channel Host SAN or Step 14 of Configuring a SCSI
Retrieving Information About Events
This section contains information about retrieving event logs and Fibre Channel dump information.
Event Log Dump
The events that have been logged in the event log can be displayed. Both normal events and any abnormal
events that may lead you to the source of an internal or external failure are displayed. You can choose to
view only those events logged since the SNC was last booted (loggerDumpCurrent) or you can view a
longer list of events that have accumulated from previous boots (loggerDump).
To view the event log dump
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Issue one of the following commands:
a. loggerDumpCurrent—to view the events listed since the SNC was last booted
b. loggerDump—to view events that have accumulated from as many previous boots as can be
reported until the limit of 2000 events has been reached
on page 18.
on
Each entry contains a sequence number, day, and time-stamp, the event code, event source (interface
name or system process), an index, and a description of the event.
If the real time clock has been set, the time-stamp will be real time. See also Figure 2
38Setup and Configuration Routines
.
Retrieving the Code 43 Dump File
Note
Note
CAUTION
Event code 43 is recorded in the SNC event log along with the name of a file that was saved to the flash file
system. That file contains information about the state of the Fibre Channel interface prior to the reset.
If an event code 43 was reported to the ADIC Management Console client, it is an indication that the SNC
performed an error recovery operation and had to reset the Fibre Channel interface to clear a lock-up
condition.
To retrieve the code 43 dump file
1Connect a service terminal to the service port. Alternatively, connect a service computer to the network
that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1
page 14, or the User’s Guide for your SNC.
Instructions for connecting a service terminal are included in the User’s Guide
for your SNC.
If you are using Ethernet, open a telnet program to connect to the SNC. Before
you connect by means of telnet, configure a user account. For instructions,
refer to Creating User Accounts
2Navigate to the DUMP directory by entering the cd “/ffs/dump” command.
on page 18.
on
3Issue the ls command to get a file listing for the directory.
There may be more than one file present if the error condition has occurred more than once.
Dump file names end in .dmp. Existing dump files can be overwritten
by newer dump files.
4Refer to the section S
Substitute the name of the dump file and use that procedure to save the file to the service computer.
Repeat this step if there is more than one file.
Save each file to the service computer.
5Send the file to technical support for analysis, attaching the dump files to the message.
aving a Configuration File on page 30.
Working With Command Flow Log Information
Two kinds of events are recorded in the command flow log file: sequence events and single command
events. Sequence events are Read/Write commands. All other events are single command events. Several
commands can be used to produce command flow log information:
•cfLogTimePlayback
•cfLogTimePlaybackAll
•cfLogEventPlayback
•cfLogEventPlaybackAll
Use these commands to get command flow log information limited by a particular LUN, time period, or a
specified number of events.
SNC Firmware 4 and 5 Reference Guide39
The output that results from these commands starts with the internal LUN number of the device for which
information is being provided. The device’s vendor, product ID, and serial number are also listed in this line:
After this line, numbered events pertaining to the cited LUN are printed. Each line begins with an event
number. In the following example, the event number is 506:
The event number is followed by the month, day of the month, start time, initiator channel and initiator index.
In event 506, the word "Write" after the initiator index indicates that the sequence event "Write" is being
logged. The number "021540" after "Write" represents the number of times the SNC carried out the "Write"
command. No errors were recorded in the course of the command being carried out. Compare the time
stamp at the end of this line to the start time to determine how long it took the SNC to complete the sequence
event.
If data was transferred to or from the host, a new line is displayed indicating the direction of the transfer
("DIR=IN" is to the host and "DIR=OUT" is from the host), the number of bytes requested (REQ) and the
number of bytes actually transferred (XFER):
DIR=IN REQ=14 XFER=14
If the event is a single command event, as in event 511 below, the initiator index is followed by an 8
character abbreviation for the operation code, the command descriptor block—which may be 6, 10, 12 or
16 bytes in length—the command completion status, and end time:
The status origin is shown as DEV if the status is from the device and SNC if the SNC returned the status.
The sense data fields for Filemark, EOM, ILI, key, additional sense code, and additional sense code qualifier
are translated and displayed on the next line. Refer to a SCSI command reference guide to understand the
the sense data in these fields.
40Setup and Configuration Routines
Service Port Command Reference
A “shell” interface provides access to the management and configuration commands referenced in this
chapter. Connect a terminal or a computer with terminal emulation software to the service port to access
the shell. Instructions for doing so are contained in the User’s Guide for your SNC.
Managing the SNC
The ADIC Management Console application (AMC) is the preferred method for managing the SNC. When
you use AMC, the operations described in this guide are carried out by means of a graphical user interface.
For installation and use, refer to the ADIC Management Console User’s Guide. Not all the commands listed
in this section are available in AMC.
Commands
This section specifies the commands that are available to control, manage, and service the SNC. Each
command description provides procedural information as well as an example of the screen display. The
actual screen display may vary, depending on your SNC and Library version and configuration.
The commands, organized by function, are provided in Table 7
the table, starting with adicNvLogDump
Command Reference on page 155 and Troubleshooting on page 161.
Some commands are only available for Firmware 4 or for Firmware 5, but not both. The page listings in the
FW4 and FW5 columns of Table 7
Each command outputs a status “value” in decimal and hexadecimal after execution and before a new
prompt is displayed.
value = 0 = 0x0
Usually a value of 0 indicates success, but some successful commands return a different value.
Table 7Service port commands listed alphabetically by functional group
Command or Command
Group
disableCCDisable command and control interface65
enableCCEnable command and control interface6666
SNC Firmware 4 and 5 Reference Guide41
on page 53. The commands are also used in the Diagnostic
indicate which commands are available for FW4, FW5, or both.
Description
and alphabetically immediately following
FW4
desc
FW5
desc
65
Table 7Service port commands listed alphabetically by functional group (Continued)
Command or Command
Group
Description
FW4
desc
FW5
desc
setSnaCCLunChange command and control interface LUN116116
Channel Zoning
setFcChanMaskConfigure fibre channel zoning112
112
Data Mover
sncFeatureEnableEnable the optional Data Mover feature123
Data Path Conditioning
ghostIOSetChange the length of time that commands to FC
Refer also to Host Port Failover and Health
Check
80
123
80
targets remain queued
ampFeatureEnableEnable the optional multi-path mapping feature5353
ghostIOShowDisplay the length of time that commands to FC
8080
targets remain queued
mapMultipathSetChange the setting for mapping new targets9696
mapMultipathShowDisplay the current setting for mapping new targets9797
mapRemoveDeviceRemove a device from the persistent device map9898
tpathShowDisplay the state of targets mapped for failover133133
Diagnostics
bootShowDisplay the boot parameters55
diagBootTransition an SNC from normal operations to
Diagnostic commands are located in Diagnostic
Command Reference on page 155.
55
156NA
diagnostic mode
elTestPerform an Ethernet loop back test156
fcSlotTestPerform a confidence test on a fibre channel slot157
normalBootTransition an SNC from diagnostic mode to normal
158
NA
NA
NA
operations
scsiChannelTestPerform a confidence test on a pair of SCSI
158
NA
channels
showBoxDisplay components of the SNC159
supportDumpOutput the result of a number of service port
125
NA
125
commands in a standard way and in a specific
order.
Environmental Sensors
envMonShowDisplay all environmental states67
envMonRangeShowDisplay the allowable ranges for environmental
6767
67
states
42Service Port Command Reference
Table 7Service port commands listed alphabetically by functional group (Continued)
Command or Command
Group
Description
fanShowDisplay fan blade controller, EEPROM, and
FW4
desc
FW5
desc
6868
temperature sensor information
Ethernet Network
arptabShowDisplay a list of known ARP entries53
53
dhcpClientShowDisplay data received from the DHCP serverNA64
If the license key was factory-installed, you can enter the word “enable” (in quotes) rather than the actual
license key.
SNC > ampFeatureEnable "enable"
AMP Enabled, License is Valid
value = 0 = 0x0
SNC >
If value = 1 = 0x1 message is displayed, it means the license is already installed and multi-path
mapping is already enabled.
If the value = -1 = 0xffffffff message is displayed, it means the license is not already installed
and you do need to enter the license key.
arptabShow
The arptabShow command displays the contents of the ARP table. The ARP table contains the current
Internet-to-Ethernet address mappings. This information can be useful to the LAN administrator.
SNC > arptabShow
LINK LEVEL ARP TABLE
destination gateway flags Refcnt Use Interface
The bootShow command displays information about the bootfile and profile used at the last boot.
SNC4 > bootShow
boot device : ibmEmac
unit number : 0
processor number : 0
host name : host
file name : //ffs/vxWorks.st
inet on ethernet (e) : 172.16.76.253:ffffff00
gateway inet (g) : 172.16.76.1
flags (f) : 0x8
target name (tn) : SNC4K
startup script (s) : //ffs/sna.rc
value = 0 = 0x0
SNC>
cd
You can move to a different directory (usually in the flash file system) using the cd command.
SNC > cd "MGMT"
value = 0 = 0x0
SNC >
cfLogHelp
The cfLogHelp command displays a list of the commands used to configure command flow logging or
display command flow log information.
SNC601112 > cfLogHelp
CFL - Command Flow Logging event facility
cfLogDetailDisable - (default) Disables detailed command flow logging. All
command events will be logged as single command events and sequence
command events.
cfLogDetailEnable - Enables detailed command flow logging. All command
events will be logged as single command events.
cfLogDetailShow - Display the current detail trace mode setting.
cfLogTimePlayback <LUN>,<minutes> - Displays a single LUN's command flow
log events for the specified number of minutes (0-4320). If minutes not
specified orZERO, then ALL log entries displayed.
cfLogEventPlayback <LUN>,<events> - Displays a single LUN's command flow
log entries for the specified number of events (0-4096). If events not
specified or ZERO, then ALL log entries displayed.
cfLogEventPlaybackAll <events> - Displays command flow log events for ALL
LUN’s for the specified number of events (0-4096). If events not
specified or ZERO, then ALL log entries displayed.
cfLogTimePlaybackAll <minutes> - Displays command flow log events for all
LUN’s for the specified number of minutes (0-4320). If minutes not
specified or ZERO, then ALL log entries displayed.
value = 0 = 0x0
SNC601112 >
SNC Firmware 4 and 5 Reference Guide55
cfLogDetailDisable
Note
The cfLogDetailDisable command disables detailed logging if detailed command flow logging had
been previously enabled. The default setting for command flow logging is disabled. Logged commands are
classified as "sequence events" or "single events."
When the command flow log is disabled, Read and Write commands are the only commands that are logged
as sequence command events. Multiple Read or Write commands result in one sequence event log entry.
All other commands are logged as single command events.
The cfLogEventPlayback command displays a specified number of command flow log events for a
specified LUN.
Command flow events for disk devices are not logged.
Enter the number of playback events from 0-4096 to limit the number of events displayed. If the number of
events is not specified or is "0", all events for the LUN will be displayed.
This information can be useful to a customer service representative, although the size of the log can be very
large, depending on how long the system has been running.
cfLogEventPlaybackAll [events]
The cfLogEventPlaybackAll command displays a specified number of command flow log events for
all LUNs (up to 10 devices).
Command flow events for disk devices are not logged.
Enter the number of playback events from 0-4096 to limit the number of events displayed. If the number of
events is not specified or is "0", all events for the LUN will be displayed..
This information can be useful to a customer service representative, although the size of the log can be very
large, depending on how long the system has been running.
cfLogTimePlayback [LUN],[minutes]
The cfLogTimePlayback command displays command flow log events for a specified LUN for a specified
time period.
Command flow events for disk devices are not logged.
Enter the number of playback minutes from 0-4320 to limit the number of events displayed. If the number
of minutes is not specified or is "0", all events for the LUN will be displayed.
This information can be useful to a customer service representative, although the size of the log can be very
large, depending on how long the system has been running.
cfLogTimePlaybackAll [minutes]
The cfLogTimePlaybackAll command displays command flow log events for all LUNs (up to 10
devices) for a specified time period.
Command flow events for disk devices are not logged.
Enter the number of playback minutes from 0-4320 to limit the number of events displayed. If the number
of minutes is not specified or is "0", all events for the LUN will be displayed.
This information can be useful to a customer service representative, although the size of the log can be very
large, depending on how long the system has been running.
cflSnapHelp
This command displays a list of commands used to work with command-flow log (CFL) snapshot
SNC > cflSnapHelp
Commands to capture CFL to iMCB file
cflSnap <LUN>- Capture one CFL for the given LUN and save it
to iMCB file
SNC Firmware 4 and 5 Reference Guide57
cflSnapAll- Capture all CFLs and save them to iMCB files
Commands to get CFL information
cflSnapShow- Display CFL size information
cflSnapSizeGet <LUN>- Return total bytes needed in iMCB to save one
CFL file
cfsSnapAllSizeGet- Return total bytes needed in iMCB to save all
CFL files
cflSnap [LUN]
The cflSnap command captures one command-flow log for the given LUN and saves it to the IOB log
NFS mount.
SNC > cflSnap 2
Save CFL for lun 002...
CFL for lun 002 has been saved.
value = 0 = 0x0
SNC >
cflSnapAll
The cflSnapAll command captures all command-flow logs and saves them to the IOB log NFS mount.
SNC > cflSnapAll
Save all CFLs...
Save CFL for lun 000...
CFL for lun 000 has been saved.
Save CFL for lun 001...
2006-06-19 12:31:45 CFL for lun 000 saved
CFL for lun 001 has been saved.
Save CFL for lun 002...
2006-06-19 12:31:46 CFL for lun 001 saved
2006-06-19 12:31:46 Couldn't get Time from NTP Server, ErrorCode 0x31
CFL for lun 002 has been saved.
3 CFLs saved successfully.
value = 0 = 0x0
SNC >
cflSnapAllSizeGet
The cflSnapAllSizeGet command returns the total number of bytes required to save all CFLs.
The clearReservation command can be used to force-clear a reservation held by a host for the
specified target device. It can be necessary to issue this command if a host that has a reservation for a
shared device was disconnected from the SNC without properly shutting down the application software that
issued the reservation. If this is the case, other hosts that attempt to access the shared device will
repeatedly receive reservation conflict status from the device. Issuing this command can result in resetting
the target device.
ParameterValue
devIdThe index of the device (LUN)
SNC > clearReservation 4
value = 0 = 0x0
SNC >
The above example shows the clearReservation command being used to clear a reservation on a
target device at LUN 4.
copyScsiAssign [source channel], [dest channel]
This command is only available with Firmware 4 on a SCSI attachment blade,
like the SNC 6101. When you are using Firmware 5, or Firmware 4 on a fibre
channel blade, this command is unavailable.
The copyScsiAssign command copies the SCSI assignments from a source channel to a destination
channel.
SNC > copyScsiAssign 1,2
value = 0 = 0x0
SNC >
SNC Firmware 4 and 5 Reference Guide59
csClearLogFile
The csClearLogFile command clears the contents of the event log.
SNC > csClearLogFile
value = 0 = 0x0
SNC >
csDisableDisplay
The csDisableDisplay command disables debug and event display to STDOUT, whether it is the
UART or a telnet session. This command is only available with Firmware 5.
SNC > csDisableDisplay
Value = 0 = 0x0
SNC >
csEnableDisplay
The csEnableDisplay command enables debug and event display to STDOUT, whether it is the UART
or a telnet session. This command is only available with Firmware 5.
SNC > csEnableDisplay
value = 0 = 0x0
SNC >
csEnhancedDisplay [on]
The csEnhancedDisplay command enables (on=1) or disables (on=0) STDOUT display enhancement,
if supported by the STDOUT display. This command is only available with Firmware 5. When enhanced
mode is enabled, the different message levels are displayed with ASCII codes for the following colors: level
0 – black, level 1 – green, level 2 – blue, and level 3 – red.
SNC > csEnhancedDisplay 1
value = 0 = 0x0
SNC >
csLogHelp
The csLogHelp command displays a list of the commands used to configure debug and event logging
and display information. This command is only available with Firmware 5.
SNC > csLogHelp
csClearLogFile- Clears the event log
csDisableDisplay- Disables debug display to STDOUT
csEnableDisplay- Enables debug display to STDOUT
csEnhancedDisplay <on>- Enables (1) or disables(0) STDOUT display
enhancement
csSetDisplayLevel <level>- Sets current debug display level
csSetDisplayLevelDefault- Sets current debug display level to default
value
csSetLogLevel <level>- Sets current debug log level
csSetLogLevelDefault- Sets current debug log level to default value
csShowDisplayLevel- Displays current debug display level
csShowLevels- Displays flag value for each subfunction
csShowLogLevel- Displays current debug log level
See User’s Guide for more information
60Service Port Command Reference
value = 0 = 0x0
SNC >
csSetDisplayLevel [level]
The csSetDisplayLevel command allows the user to set the level which determines the types of
messages that get displayed to STDOUT. This command is only available with Firmware 5. This feature is
intended for field debug. The set level is valid for only one hour; after which time the level will revert to the
default value. The supplied level is a 16-bit mask that specifies the display-only flag, level, and subsystem
as described below:
Bit
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
|||
||> Subsystem (bits 0-12)
|> Level (bits 13-14)
> Not Used
The ‘Subsystem’ portion filters out all messages other than those associated with the specified value. The
following is a list of the subsystem values:
Note that subsystem filtering occurs only for messages with a level of Level_1 or higher. Level_0 messages
are always displayed if STDOUT display is enabled (see csEnableDisplay
The following example filters out all messages except for all Level_0 and SNMP-associated Level_1
messages:
The csSetDisplayLevelDefault command returns the message display filter level to the default value
of Level_0. This command is only available with Firmware 5.
SNC > csSetDisplayLevelDefault
value = 0 = 0x0
SNC Firmware 4 and 5 Reference Guide61
SNC >
csSetLogLevel [level]
The csSetLogLevel command allows the user to set the level which determines the types of messages
that get recorded to the event log. This command is only available with Firmware 5. This feature is intended
for field debug. The set level is valid for only one hour; after which time the level will revert to the default
value. Level_0 messages will always be logged. See csSetDisplayLevel [level]
of the value ‘level’.
SNC > csSetLogLevel 0x2010
value = 0 = 0x0
SNC >
on page 61 for a description
csSetLogLevelDefault
The csSetLogLevelDefault command returns the message and event log filter level to the default
value of Level_0. This command is only available with Firmware 5.
SNC > csSetLogLevelDefault
value = 0 = 0x0
SNC >
csShowDisplayLevel
The csShowDisplayLevel command displays the current message display level. This command is only
available with Firmware 5.
The csShowLevels command displays a list of values for the subfunction portion of the filter level. This
command is only available with Firmware 5. This is the value to use for the subfunction when setting the
display level (see csSetDisplayLevel [level]
The date command displays the system’s date and the time. The date command takes into account the
timezone, but the rtcGet command does not. Therefore the output of rtcGet and date may not show
the same value.
The system can be set to read its local real time clock (refer to the dateSetFromRTC command) or a
remote host. Refer to the rdate “timeserver” and rtcSetCurrent commands.
SNC > date
SNC > THU JAN 25 20:32:49 2001
SNC >
dateSetFromRTC
The dateSetFromRTC command sets the real time clock as the source of the date display. Use the date
command to display the date and time.
SNC > dateSetFromRTC
value = 0 = 0x0
SNC >
deleteScsiAssign [devId],[channel], [id],[lun]
This command is only available with Firmware 4 on a SCSI attachment blade,
like the SNC 6101. When you are using Firmware 5, or Firmware 4 on a fibre
channel blade, this command is unavailable.
The deleteScsiAssign command deletes assignments previously created.
Example 1 uses the output of Example 2 to delete assignments from SCSI channel 2.
Example 1:
SNC > deleteScsiAssign 64,2,0,0
value = 0 = 0x0
SNC > deleteScsiAssign 82,2,0,1
value = 0 = 0x0
SNC > deleteScsiAssign 98,2,0,2
value = 0 = 0x0
SNC > deleteScsiAssign 124,2,0,3
value = 0 = 0x0
Example 2:
SNC > showScsiAssign
SCSI 2
ID Lun DevId
0 0 64
SNC Firmware 4 and 5 Reference Guide63
0 1 82
0 2 98
0 3 124
dhcpClientShow
The dhcpClientShow command displays data received from the Dynamic Host Configuration Protocol
(DHCP) server. This command is only available with Firmware 5.
In response to this command—if DHCP is enabled—information about the configuration displayed, as in the
first example shown below.
172.16.40.24
Domain Name : adic.com
DNS Addr : 172.16.72.51
Client DNS name servers:
172.16.72.51
172.16.9.63
172.16.40.24
value = 0 = 0x0
If DHCP is disabled, the dhcpClientShow command displays the following:
SN601515 > dhcpClientShow
Domain Name : (null)
DNS Addr :
value = 0 = 0x0
SN601515 >
64Service Port Command Reference
diagBoot
CAUTION
Refer to diagBoot on page 156. This command is only available with Firmware 4.
diagHelp
The diagHelp command displays a list of the diagnostic commands. This command is only available with
Firmware 4.
SNC > diagHelp
** Diagnostic commands: Available in Diagnostic Mode Only **
elTest Test Ethernet port w/loop-back cable
fcSlotTest <portnum> Test specified Fibre Channel port w/loop-back cable
normalBoot Shutdown and restart in normal mode
scsiChannelTest <x,y> Test specified SCSI Channels w/loop-back cable
See User’s Guide for more information
value = 0 = 0x0
SNC >
disableCC [option number]
Disable the command and control interface (LUN 0) using the disableCC command. Specify one of two
option parameters as follows.
Option
Number
1Hides the command and control interface and results in Inquiry data
2Completely disables all command and control functions
The SNC is addressable as a SCSI target device for command and control support. On a fibre channel
interface, this device will be seen as logical unit number 0, (LUN 0). The LUN 0 device returns a device type
of 0Ch in an inquiry command, indicating it is a controller device. Controller devices are defined in the SCSI3 Controller Commands specification (SCC).
In some cases, it may be desirable to disable this feature. If LUN 0 is disabled, then a device type of 2Ch
will be returned in an inquiry to LUN 0, indicating that the device is not presently available at this LUN. LUN
0 will remain reserved for the command and control interface and will not be allocated to another target
device.
Other commands are available for re-enabling the command and control interface or reassigning it to a
different LUN rather than hiding or disabling it. Refer to the enableCC command and the setSnaCCLun
command for further information.
Meaning
returning “device not available” for LUN 0.
If you issue the disableCC command without specifying an option
number, it has the same effect as disableCC 1.
SNC > disableCC
value = 0 = 0x0
SNC >
SNC Firmware 4 and 5 Reference Guide65
elTest
Refer to elTest on page 156.
enableCC
To restore the capability to send commands to the command and control interface (LUN 0), use the
enableCC command. The command is typically used to re-enable the interface after it was disabled by the
disableCC command.
SNC > enableCC
value = 0 = 0x0
SNC >
envMonRangeShow
The envMonRangeShow command specifies operational ranges for the environmental channels. It displays
ranges of values associated with the Nominal, Warning, and Alarm states for voltage, temperature, and fan/
blower operation according to the channels defined in the envMonShow command. The information displays
for Firmware 4 and 5 are slightly different from each other. An example Firmware 4 display:
SNC > envMonRangeShow
Air Inlet Temp (C):
Nominal: 5 to 45
Warning: 4 <= N < 5 or 45 < N <= 50
Alarm: N < 4 or N > 50
IO Processor Temp (C):
Nominal: 5 to 80
Warning: 4 <= N < 5 or 80 < N <= 108
Alarm: N < 4 or N > 108
Input Power: +5 Volts (V):
Nominal: 4.83 to 5.20
Warning: 4.75 <= N < 4.83 or 5.20 < N <= 5.25
Alarm: N < 4.75 or N > 5.25
Input Power: +12 Volts (V):
Nominal: 11.00 to 12.93
Warning: 10.75 <= N < 11.00 or 12.93 < N <= 13.18
Alarm: N < 10.75 or N > 13.18
Local Power: +2.5 Volts (V):
Nominal: 2.42 to 2.58
Warning: 2.36 <= N < 2.42 or 2.58 < N <= 2.62
Alarm: N < 2.36 or N > 2.62
Local Power: +3.3 Volts (V):
Nominal: 3.20 to 3.39
Warning: 3.13 <= N < 3.20 or 3.39 < N <= 3.46
Alarm: N < 3.13 or N > 3.46
Local Power: +3.3 Volts Aux (V):
Nominal: 3.20 to 3.39
Warning: 3.13 <= N < 3.20 or 3.39 < N <= 3.46
Alarm: N < 3.13 or N > 3.46
Fan :
66Service Port Command Reference
Nominal: 1; Alarm: 0
value = 1 = 0x1
SNC >
envMonShow
The envMonShow command lists all of the environmental channel states and their current values. Use the
command envMonRangeShow to restrict output to a display of the ranges relevant to each state. The
following channels have been defined:
Channel NameDescription
Air Inlet TempTemperature of the air as it enters the unit
Air Outlet TempTemperature of the air as it exits the unit
IO Processor TemperatureTemperature of the IO Processor
Input Power: ±5 VoltsVoltage level of the ±5 input
Input Power: ±12 VoltsVoltage level of the ±12 input
Local Power: ±2.5 VoltsVoltage level of the local 2.5 supply
Local Power: ±3.3 VoltsVoltage level of the local ±3.3 supply
Local Power: ±3.3 Volts
Aux
FanFan running (for tachometer fans: RPM of fan)
The information displays for Firmware 4 and 5 are slightly different from each other. An example Firmware
4 display:
SNC > envMonShow
Channel State Value
-----------------------------------------------------Air Inlet Temperature Nominal 44 C
Air Outlet Temperature Nominal 51 C
IO Processor Temperature Warning 31 C
Input Power: ±5 Volts Nominal 5.2 V
Input Power: ±12 Volts Nominal 12 V
Local Power ±2.5 Volts Nominal 3.3 V
Local Power ±3.3 Volts Nominal 3.3 V
Local Power ±3.3 Volts Aux Nominal 3.29 V
All Power Nominal
All Temp Nominal
Sample Count 20
value = 1 = 0x1
Voltage level of the local auxiliary ±3.3 supply
ethAddrGet
The ethAddrGet command displays the IP address of the SNC, specified as 4 decimal numbers separated
by periods. If there is a subnet mask, it is appended to the end of the IP address, after a semicolon.
SNC > ethAddrGet
SNC Firmware 4 and 5 Reference Guide67
IP Address set to 172.16.77.106:ffffff00
value = 0 = 0x0
SNC >
ethAddrSet
The ethAddrSet command changes the IP address of the SNC. An IP address is specified as 4 decimal
numbers separated by periods.
SNC > ethAddrSet "192.168.1.54"
Host Address set to 192.168.1.54 for Ethernet interface
value = 0 = 0x0
SNC >
If a netmask is required, specify it after the IP address in “dotted decimal” form.
For example:
SNC > ethAddrSet "10.0.0.2","255.255.0.0"
Inet Mask set to ffff0000 for Ethernet interface
Write complete
Host Address set to 10.0.0.2 for Ethernet interface
value = 0 = 0x0
SNC >
fanShow
The fanShow command displays fan blade controller, EEPROM, and temperature sensor information.
I0500031_MGMP > fanShow 2
Fan Controller:
----------------------------------------------------------------------FAULT: 00
STATUS: e1
DACA: 0a
DACB: 0a
Fan 1: 7b
Fan 2: 73
Fan 3: 7a
Fan 4: 73
GPIO Data: 81
GPIO Setup: f0
Fan Controller EEPROM:
----------------------------------------------------------------------Valid EEPROM
Init Count: 189
Fault count: 0
Library serial number: A0C0145914
Blade serial number: AMQ002753-0042
The fcConnTypeGet command is used to display the current connection type for a fibre channel port.
Refer also to the fcConnTypeSet command.
ParameterValueMeaning
port1 - 6The FC port
connection type0Loop
1Point-to-point
2Loop preferred
3Point-to-point preferred (for Firmware 4 only)
The following example shows how the connection type is displayed when fibre channel port 1 is specified
and its connection type is loop.
SNC > fcConnTypeGet 1
FC Port 1: Point-to-point preferred
SNC >
fcConnTypeSet [port],[connection]
The fcConnTypeSet command is used to set the type of connection for a fibre channel port. Refer also to
the fcConnTypeGet command.
SNC Firmware 4 and 5 Reference Guide69
ParameterValueMeaning
CAUTION
port1 - 6The FC port
connection type0Loop
1Point-to-Point
2Loop preferred
3Point-to-point preferred (for Firmware 4 only)
The following example shows how to set fibre channel port 1 connection type to point-to-point.
SNC > fcConnTypeSet 1,1
SNC >
You must issue the fcRestart command or reboot the SNC for the
new setting to take effect. Refer to fcRestart [port]
further information. Using fcRestart is less disruptive to an
established SAN than a reboot.
on page 73 for
fcFibreSpeedGet [port]
The fcFibreSpeedGet command displays the current configured speed setting for the fibre channel port.
The actual speed can be viewed in the output of the fcShow command. The example below shows that
fibre channel port 1 has a maximum speed of 1 Gb/sec.
SNC > fcFibreSpeedGet 1
FC 1 is set to 4 Gb/sec
SNC >
ParameterValueMeaning
port1 - 6The FC port
value =0Speed is set to Autorange
1Speed is set to 1 Gb/sec
2Speed is set to 2 Gb/sec
4Speed is set to 4 Gb/sec
fcFibreSpeedSet [port],[speed]
The fcFibreSpeedSet command sets the configured speed for a fibre channel. The port can also be set
to autorange, as in the example below.
ParameterValueMeaning
port1 - 6The FC port
speed0Autorange
11 Gb/sec
70Service Port Command Reference
CAUTION
ParameterValueMeaning
22 Gb/sec
44 Gb/sec
SNC > fcFibreSpeedSet 1,0
SNC >
You must issue the fcRestart command or reboot the SNC for the
new setting to take effect. The host and the device must both be
capable of the selected speed. Refer to the fcRestart command for
further information.
fcGbicShow [port]
The fcGbicShow command displays the GBIC information for each installed GBIC. Specifying the port
number is optional.
ParameterValueMeaning
port1-6The SNC connection labeled FC1 through
6 respectively
SNC > fcGbicShow
------------------------------------------------------------------ Ctlr : Module : Module
ID : Code : Information
------------------------------------------------------------------ 1 : 4 : Serial Module Definition Protocol
: Transceiver Type ------------- GBIC
: Connector Type --------------- SC
: Nominal Speed ---------------- 2.1 Gb/sec
: Link length for 9/125 um ----- 0 meters
: Link length for 50/125 um ---- 3000 meters
: Link length for 62.5/125 um -- 1500 meters
: Vendor Name ------------------ StratosLightwave
: Vendor OUI ------------------- 000000
: Vendor Part Number ----------- MGBC-20-8-1-S
: Vendor Revision ------------- : Vendor Serial Number --------- ABAEG316
: Vendor Mfg. Date ------------- 04-25-2002
: RX LOS Implemented ----------- Yes
: TX Fault Implemented --------- Yes
: TX Disable Implemented ------- Yes
2 : 4 : Serial Module Definition Protocol
: Transceiver Type ------------- GBIC
: Connector Type --------------- SC
: Nominal Speed ---------------- 2.1 Gb/sec
: Link length for 9/125 um ----- 0 meters
: Link length for 50/125 um ---- 3000 meters
: Link length for 62.5/125 um -- 1500 meters
SNC Firmware 4 and 5 Reference Guide71
: Vendor Name ------------------ StratosLightwave
: Vendor OUI ------------------- 000000
: Vendor Part Number ----------- MGBC-20-8-1-S
: Vendor Revision ------------- : Vendor Serial Number --------- ABAGO316
: Vendor Mfg. Date ------------- 04-25-2002
: RX LOS Implemented ----------- Yes
: TX Fault Implemented --------- Yes
: TX Disable Implemented ------- Yes
The fcPortModeGet command displays the mode for the specified fibre channel port. The default port
mode is Public Target. Refer also to the fcPortModeSet command. This command returns an exit
status set to the port mode, or to -1 if the command fails.
After the command executes, the number displayed as a value indicates the port mode as follows:
ValuePort Mode
1Private Target
2Private Initiator
3Private Target and Initiator
17Public Target
18Public Initiator
19Public Target and Initiator
The following example shows how the connection type is displayed when fibre channel port 1 is specified
and the port mode is Private Target.
SNC >fcPortModeGet 1
FC Port 1 Mode: Private Target
SNC >
fcPortModeSet [port],[mode]
The fcPortModeSet command sets the mode for the specified fibre channel port. Refer also to the
fcPortModeGet command.
The default port mode for FC ports 1 and 2 is Public Target. Consequently, if attached to a Fabric device
the SNC will register as a Target with the name server. If the port mode is Private Target, the SNC
does not register with the name server and the Fabric device will not recognize the SNC as a Target.
The port must be in Initiator mode if you want the SNC to scan for target devices on the port. When the port
is in Private Initiator mode, the SNC only scans for devices on the local loop. If the port mode is in
Public Initiator mode, the SNC also scans for devices attached to a Fabric.
ParameterValueMeaning
Port1 - 6The FC port
72Service Port Command Reference
CAUTION
CAUTION
ParameterValueMeaning
Mode1Private Target
2Private Initiator
3Private Target and Initiator
17Public Target
18Public Initiator
19Public Target and Initiator
SNC > fcPortModeSet 1,2
SNC >
You must issue the fcRestart command or reboot the SNC for the
new setting to take effect. Refer to the fcRestart command for
further information. Using fcRestart is less disruptive to an
established SAN than a reboot.
fcRestart [port]
The fcRestart command restarts the specified fibre channel port. You typically use this command to
restart the port after changing its configuration settings so that the changes take effect. Issuing this
command is an alternative to rebooting the SNC in order to make the configuration changes take effect. It
is less disruptive than a reboot.
This command interrupts traffic.
ParameterValueMeaning
Port1-6The SNC connection labeled FC1 through
FC6 respectively
The following example shows the display when fibre channel port 1 is specified.
SNC > fcRestart 1
Restart of FC Channel 1 succeeded
In order to get the command prompt (for example, SNC >) to show after you have executed the fcRestart
command, you will need to press the Enter key.
fcShow [level]
The fcShow command displays the channel status for each fibre channel interface.
LevelMeaning
0 or
<blank>
sets the verbosity level to the display in the example below
SNC Firmware 4 and 5 Reference Guide73
LevelMeaning
1displays the information displayed below, and appends a break-out
for each channel that includes node type, node name, port name
and port ID
2displays the information included at levels 0 and 1, and appends
Ctlr IdIndicates the port number for this interface.
PCI AddrThe PCI address of the interface, showing bus, device id, and
function number.
ISP TypeThe type of fibre channel controller.
Firmware State (shown for
FW4 only)
74Service Port Command Reference
The current state of the interface as reported by the fibre
channel controller. Firmware states are listed below.
CAUTION
ParameterMeaning
Configuration WaitFirmware is not initialized.
Waiting for AL_PAFirmware is performing or waiting to perform loop initialization.
Waiting for loginFirmware is attempting port and process logins with all loop
ports.
ReadyIndicates that the interface is connected and operational and
ready to process SCSI commands. Any other value indicates
intermediate states or interface failure.
Sync LostThe firmware has detected a loss-of-sync condition and is re-
synchronizing the serial link receiver. This is the state reported
when the fibre channel link does not detect a connection to a
fibre channel device.
ErrorThe firmware has detected an unrecoverable error condition.
NonparticipatingThe firmware is not participating on the loop since it did not
acquire an AL_PA during initialization.
FailedThe firmware is not responding to commands
Firmware VersionThe version of firmware on the fibre channel controller.
Loop IDThe fibre channel loop ID for this interface. PtoP indicates a
point-to-point connection.
Fabric AttachedIndicates whether the port is attached to a Fabric.
Port ModeIndicates the current port mode: Target, Initiator, or both Target
and Initator.
Link SpeedIndicates the current speed of the connection. If the port is not
currently connected, this field is blank.
If the Firmware State is anything but Ready, the information output by
this command will be unreliable.
fcShowDevs
The fcShowDevs command displays information about the devices that are accessible from each fibre
channel interface. The display shows the LUN that the SNC has assigned to each device, the SCSI Channel
that the device is attached to, the actual SCSI ID and LUN of the device, the vendor, product, revision and
serial number of the device.
In the example, channel zoning was used for access control. Fibre channel 1 has access to all of the
attached SCSI tape and disk devices. For the other fibre channel interface, channel zoning has been set up
to restrict access to certain devices.
SNC> fcShowDevs
Targets Visible to Hosts on FC 1:
LUN Chan Id Lun Vendor Product Rev SN
The fcTransceiverShow command displays the SFP (small form-factor pluggable transceiver)
information for each installed SFP. Specifying the port number is optional.
The fcTxDisable command disables a fibre channel port transmitter.
SNC > fcTxDisable 1
SNC >
fcTxEnable [port]
The fcTxEnable command enables or re-enables a fibre channel port transmitter.
SNC > fcTxEnable 1
SNC >
gateAddrGet
The gateAddrGet command displays the default network gateway address if one has been set. This
address is used when connections are made to a different subnet and there are no explicit routes defined
for that subnet. Consult your network administrator for more information on the default gateway (sometimes
referred to as default router) address.
SNC > gateAddrGet
Gateway Address set to 192.168.1.1
value = 0 = 0x0
SNC >
gateAddrSet
The gateAddrSet command changes the default network gateway address. This address is used when
connections are made to a different subnet and there are no explicit routes defined for that subnet. Consult
your network administrator for more information on the default gateway (sometimes referred to as default
router) address.
The following message is received when trying to set a new gateway address and that address is currently
unreachable. The following message is sent to the terminal.
SNC > gateAddrSet "10.0.0.1"
gateAddrSet: Error setting current gate addr: S_errno_ENETUNREACH
value = -1 = 0xffffffff = payloadChecksum + 0xffd418a3
The new gateway address is written to the bootup parameters to be used at the next boot. If at next boot,
the address is reachable, then it will be written to the system file. If at next boot the gateway address is not
reachable and therefore not written to the system file, the following message is displayed:
Failed gateAddrSet (2):
SNC > gateAddrSet "172.16.76.1"
gateAddrSet: Error deleting old gateway addr: S_errno_ESRCH
Gateway Address set to 172.16.76.1 for Ethernet interface
value = 0 = 0x0
SNC >
SNC Firmware 4 and 5 Reference Guide79
getScsiScanTime
The getScsiScanTime command displays the number of minutes that the SNC rescans the SCSI bus in
order to discover devices that come online slowly. The default is 5 minutes. This command is only available
with Firmware 4.
The ghostIOSet command changes the number of ticks that a command remains queued for
transmissions to the target. Each tick is 1/60th of a second. The number of ticks can be set from 1 to 60. If
ticks are set to 0, command queuing is disabled.
ParameterValueValid RangeMeaning
Ticks1/60th of a second0-60Number of ticks commands remain
in queue
SNC > ghostIOSet 30
Ghost I/O support is enabled.
Stale commands will be deleted after 30 ticks (500 ms).
value = 30 = 0x1e
SNC >
ghostIOShow
The ghostIOShow command displays the current status of command queuing. The value 0 is returned
when command queuing is disabled. Otherwise the number of ticks that commands remain in queue is
displayed.
SNC > ghostIOShow
Ghost I/O is disabled.
value = 0 = 0x0
SNC >
80Service Port Command Reference
help
The help command displays a list of the shell commands. The display varies slightly to indicate which
commands are available in FW4 and which are available in FW5. See Table 7
SNC > help
helpPrint this list
cfLogHelpPrint Command Flow Log Entry info
csLogHelpPrint Debug Logging Help info
diagHelpPrint Diagnostic Help info
hlthChkHelpPrint Health Check Help info
ioHelpPrint I/O Utilities Help info
mapHelpPrint Device Map Help info
netHelpPrint Network Help info
snmpHelpPrint SNMP Help info
userHelpPrint User account info
h [n]Print (or set) shell history
pwdPrint working path
shellLockLock or unlock shell command interface
versionPrint Version info
whoamiPrint user name
clearReservation [devId]Clear reservation on a target (may reset
target)
diagBootShutdown and restart in diagnostic mode
initializeBoxDelete all device maps, restore factory
defaults, reboot
saveConfig <index>Saves configuration. Index may be 1 to 4
restoreConfig <index>Restores configuration. Index may be 1 to 4
ridTag ["value"]Display and set serial number of replaced
base unit
disableCC [option]Disable Command and Control Interface
option 1 - Report as Invalid (AIX mode)
option 2 - Fully disabled
enableCCEnable Command and Control Interface
scsiRescan [chan]Rescan SCSI Channel (all if chan not
specified)
scsiShowDisplay info for SCSI Channels
fcChipInfoShow [device]Display manufacturer information for Fibre
Channel device
fcShowDisplay info for Fibre Channels
fcShowDevsDisplay devices available on each Fibre
Channel
fcShowNamesDisplay Node and Port names for Fibre
Channels
fcShowRegs [device]Display register data for Fibre Channel
device
hostTypeShowDisplay Default Host Type settings
loggerDump [count]Display Logger Dump Records
loggerDumpCurrent [level]Display Logger Dump Records for current
boot
rebootShut down and restart
resetRestart without shut down
setFcScsiChanMask [chan],
[scsi],[allow]Set Channel Access Control
setFcFrameSize [chan],[size]Set FC Frame Size
setFcHardId [chan],[id]Set FC Loop ID
setHost [chan],["OS"]Set default host type for FC Channel
on page 41 to verify.
SNC Firmware 4 and 5 Reference Guide81
setSnaCCLunSet LUN for Controller Device (typically
showBoxDisplay graphic of current hardware
showVersionsDisplay System Version Information for
sysConfigShowDisplay System Config Parameters
sysVpdShowDisplay Vital Product Data
sysVpdShowAllDisplay Vital Product Data for all
sysNodeNameModeSetChange Fibre Channel Node Name mode
sysNodeNameModeShowDisplay current Fibre Channel Node Name
targetsList all known target devices
uptimeDisplay time since last boot
See User's Guide for more infomation
value = 0 = 0x0
SNC >
hlthChkHelp
OS may be "aix", "nt", "solaris", "hpux",
"as400", "autosense/nt", ...
zero)
configuration
BootROM, POST, and Application
subsystems
mode
The hlthChkHelp command displays a list of the health check commands.
SNC > hlthChkHelp
hlthChkIntervalGet - Show Check Interval
hlthChkIntervalSet <interval> - Set Check Interval
hlthChkLevelGet - Show Check Level
hlthChkLevelSet <level> - Set Check Level
hlthChkNow - Run Health Check Now
See User’s Guide for more information
value = 0 = 0x0
SNC >
hlthChkIntervalGet
The current health check interval can be viewed using the hlthChkIntervalGet command. The example
below shows the current interval is 60 minutes.
The health check interval controls how often the health check process runs. The interval can range from 1
to 65,535 minutes (about 45 days).
SNC > hlthChkIntervalSet 60
value = 0 = 0x0
SNC >
82Service Port Command Reference
hlthChkLevelGet
To display the current health check level, use the hlthChkLevelGet command. The example below
shows that the current level is 2.
SNC > hlthChkLevelGet
value = 2 = 0x02
SNC >
hlthChkLevelSet [level]
To set the health check level, use the hlthChkLevelSet command. The example below shows setting
the level to “3”. The default level is “2.”
Health Check LevelMeaning
1Checks the health of the SNC, the environment, PCI errors, and the like
2Checks the interfaces, for example, the FC controllers + Level 1 check.
3Checks the devices by sending a SCSI Inquiry command to each known
device + Level 1 and Level 2 checks.
4Checks the device states. This sends a Test Unit Ready command to each
device + Level 1, 2, and 3 checks.
SNC > hlthChkLevelSet 3
value = 0 = 0x0
SNC >
hlthChkNow
The hlthChkNow function causes the SNC to execute an immediate, level four health check. Results are
displayed that will indicate which devices or subsystems failed the check.
SNC > hlthChkNow
Health Check: Starting level 4 check
Health Check: Step 1 -- Checking System
Health Check: Step 2 -- Checking Interfaces
Health Check: Step 3 -- Checking Devices
Health Check: Step 4 -- Checking Device States
Health Check: Passed
value = 0 = 0x0
SNC >
host "add","hostname","ipAddress"
The host "add" command adds the named host to the host table and host file. If the IP address is already
assigned to a host, then the new name is added as an alias for the host. The host "add" command is
invoked to add known hosts and their IP addresses. Alias names are supported, allowing multiple names to
a single host.
The host utilities maintain a host file, nvfs:/mgnt/hosts, which is used at system startup to initialize the
network hosts table. This table associates network names with IP addresses. Use of the hosts table is
entirely optional, but might facilitate frequently needed connections. Each host entry is a single line of the
format:
[IP-address][official_host_name][nicknames ...]
where
SNC Firmware 4 and 5 Reference Guide83
IP-addressis a text string in standard IP address format (i.e., 10.0.0.2)
Note
official_host_nameis the first name selected for this host.
nicknamesis an optional list of additional aliases for the host (separated by
spaces).
The following is an example of host file contents.
192.168.1.90 bruno
200.0.0.42 socrates
200.0.0.45 plato
200.0.0.47 fred
The host file does not exist until you issue the host "add" command.
SNC > host "add","plato","200.0.0.45"
SNC >
host "delete","hostname"
The host "delete" command deletes the named host from the hosts table and hosts file. If the hostname
is an alias, then only the alias is removed. If hostname is the official host name, the entry and all aliases
are removed.
The host utilities maintain a host file, nvfs:/mgnt/hosts, which is used at system startup to initialize the
network hosts table. This table associates network names with IP addresses. Use of the hosts table is
entirely optional, but might facilitate frequently needed connections. Each host entry is a single line of the
format:
[IP-address][official_host_name][nicknames ...]
where
IP-addressis a text string in standard IP address format (i.e., 10.0.0.2).
official_host_
name
nicknamesis an optional list of additional aliases for the host (separated by spaces).
The following is an example of host file contents.
192.168.1.90 bruno
200.0.0.42 socrates
200.0.0.45 plato
200.0.0.47 fred
SNC > host "delete", "plato"
SNC>
is the first name selected for this host.
84Service Port Command Reference
host "list"
The host "list" command prints the content of the hosts file.
The host utilities maintain a host file, nvfs:/mgnt/hosts, which is used at system startup to initialize the
network hosts table. This table associates network names with IP addresses. Use of the hosts table is
entirely optional, but might facilitate frequently needed connections. Each host entry is a single line of the
format:
[IP-address][official_host_name][nicknames ...]
where
IP-addressis a text string in standard IP address format (i.e., 10.0.0.2).
official_host_nameis the first name selected for this host.
nicknamesis an optional list of additional aliases for the host (separated by
spaces).
The following is an example of host file contents.
SNC > host "list"
192.168.1.90 bruno
200.0.0.42 socrates
200.0.0.45 plato
200.0.0.47 fred
value = 0 = 0x0
SNC >
hostNameGet
The hostNameGet command causes the network name of the SNC to display.
SNC > hostNameGet
SNC
value = 0 = 0x0
SNC >
hostNameSet
This command changes the network name of the SNC. The shell prompt will be set to the new host name.
The name you choose cannot be longer than 19 characters. Spaces are not allowed.
SNC > hostNameSet "foster"
Target hostname set to foster
value = 0 = 0x0
foster >
hostShow
The hostShow command displays the IP address and alias (if any) of the unit processing the hostShow
command, the localhost and the timeserver host.
The hostTypeShow command displays the host type setting for each fibre channel.
SNC > hostTypeShow
FC 1: Type 2 - nt
FC 2: Type 1 - solaris
value = 0 = 0x0
SNC >
When a host type is entered, it can be entered either as a valid host type or as an alias. (To enter a host
type, use the setHost command.) The alias is accepted by the system, but only the valid host type is
displayed as output to this command. The output in the example could be the result of the user’s having
chosen either "Linux" or "Solaris" for the host attached to FC2.
hpfAddPort [virtual port],[phys port]
In order for host port failover to configured, one or more FC port(s) must have a virtual port stand by list that
includes at least one port not identical to itself. The default state for the SNC, even after the host port failover
license has been enabled, is that each of the two FC ports is an active physical port with its own virtual port
(itself) and its own virtual port standby list consisting entirely of itself.
The hpfAddPort command adds a different physical port to a virtual port’s standby port list. This allows
host port failover to occur, should the physical port fail. Before adding a physical port to the standby list for
a virtual port, be sure it has been removed from any other virtual port standby list. Refer also to
hpfRemovePort [virtual port]
Failover on page 27.
,[phys port] on page 88, hpfShow on page 89, and Configuring Host Port
SNC > hpfAddPort (1,2)
This command adds physical port 2 to the standby list for virtual port 1.
hpfDisplayLinkDownDelay
The hpfDisplayLinkDownDelay command sets the amount of time in seconds that a link down status
applies to a port before failover occurs. The default is three seconds.
SNC > hpfDisplayLinkDownDelay
The current link down delay is set to 3.
value = 0 = 0x0
SNC >
hpfFeatureEnable "licensekey"
The hpfFeatureEnable command enables the optional host port failover feature. You enable the feature
by entering the unique license key.
The hpfFeatureDisable command disables host port failover. It erases the appropriate configuration
file, and reboots the SNC. No provision is made to restore the existing configuration. Users should save the
SNC configuration before disabling the feature.
For more information, refer to S
SNC > hpfFeatureDisable
This will delete the HPF Config File. Continue? (y/n)y
You have chosen to delete the HPF Config File.
You must restart the SNC for this to take effect.
HPF Command line functionality will no longer work.
value = 0 = 0x0
SNC>
aving a Configuration File on page 30.
hpfMakeActive [virtual port],[phys port]
An effective host port failover configuration includes at least one virtual port with a standby list of two or more
physical ports. The hpfMakeActive command makes a given physical port the active channel for a given
virtual port.
SNC > hpfMakeActive 1,1
Physical Port 1 is now active on virtual port 1.
value = 0 = 0x0
SNC233 > Restarting FC Channel 2
Restarting FC Channel 1
Restart of FC Channel 2 succeeded
Restart of FC Channel 1 succeeded
You must press the Enter key to force the command prompt to display after a
fibre channel restarts.
In the example, physical port 1 takes on the virtual port 1’s characteristics and any data traffic directed to
virtual port 1 will go through physical port 1.
hpfMakePrimary [virtual port],[phys port]
An effective host port failover configuration includes at least one virtual port with a standby list of two or more
physical ports. The first physical port in the standby port list is the primary port. The primary port is initially
the active port, but if it fails, another port on the standby list can become the active port. Use the
hpfMakePrimary command to make a port that is not listed first in the standby ports list into the primary
port.
In the following example, the hpfShow command is issued first, to show the order of the ports listed in the
standby ports list.
SNC > hpfShow
SNC Firmware 4 and 5 Reference Guide87
----------------------------------------------------------------- Fibre Channel Host Port Failover Display
----------------------------------------------------------------- Virtual Port Number | Active Port Index | Standby Port Index(es)
----------------------------------------------------------------- Link Down Error Recovery Setting: Return to Standby
Error Count Recovery Setting: Requires Intervention
Link Down Delay Timer Setting: 3
-----------------------------------------------------------------Physical Port | failure type | Current Port | Requires | Active
| Virtual
index ||State|Intervention|
| Port
----------------------------------------------------------------- 1 | NONE | OFFLINE | NO | NO | NONE
2 | NONE | OFFLINE | NO | NO | NONE
value = 0 = 0x0
SNC > hpfMakePrimary 1,1
Physical port 1 is now the primary port for virtual port 1.
value = 0 = 0x0
SNC >
hpfPortEnable [phys port]
When a port’s recovery type has been set to require intervention, the port will not be usable upon recovery,
until the port has been enabled by an administrator.The hpfPortEnable function is used to re-enable the
port.
hpfRemovePort [virtual port],[phys port]
The hpfRemovePort command is used to remove a physical port from a virtual port’s standby port list.
SNC > hpfRemovePort 1,2
Found the Physical port on the Virtual Ports list.
Port has been removed.
value = 0 = 0x0
SNC >
In this example, physical port 2 has been removed from the standby list for virtual port 1.
hpfSetErrorRecovery [value]
This function sets the recovery scenario for a all ports, when the failure of the port was due to error count.
The parameter "Value" corresponds to the output of hpfShowErrorRecoveryValues command.
ValueMeaning
0Return to active
1Return to standby
2Require intervention
88Service Port Command Reference
In the following example, the ports have been configured to return to standby when they recover from failure.
CAUTION
SNC > hpfSetErrorRecovery 1
value = 0 = 0x0
SNC >
hpfSetLinkDownDelay
The hpfSetLinkDownDelay command sets the amount of time in seconds before failover occurs when a
port's link goes down.
SNC > hpfSetLinkDownDelay 30
The current link down delay is set to 30.
value = 0 = 0x0
SNC >
Consult an authorized service technician before changing this value.
In this example, failover is configured to occur when a link is not back up after 30 seconds. The default is
three seconds.
hpfSetLinkDownRecovery [value]
This function sets the recovery scenario for a all ports, when the failure of the port was due to the link being
down. The parameter "Value" corresponds to the output of the hpfShowErrorRecoveryValues
command.
ValueMeaning
0Return to active
1Return to standby
2Require intervention
In the following example, the ports have been configured to return to standby when they recover from a
failed link.
The hpfShow command displays the current host port failover state and configuration. The default
configuration for an SNC with two FC ports is shown below.
SNC > hpfShow
-------------------------------------------------------------------------------Fibre Channel Host Port Failover Display
-------------------------------------------------------------------------------Virtual Port Number | Active Port Index | Standby Port Index(es)
Link Down Error Recovery Setting: Return to Standby
CAUTION
Error Count Recovery Setting: Requires Intervention
Link Down Delay Timer Setting: 3
-------------------------------------------------------------------------------Physical Port | failure type | Current Port | Requires | Active | Virtual
index ||State|Intervention| |
Port
-------------------------------------------------------------------------------1 | NONE | OFFLINE | NO | NO | NONE
Host port failover cannot occur in the default SNC configuration, even
when host port failure is enabled.
For configuration instructions, refer to Configuring Host Port Failover on page 27. The output of the
hpfShow command for a system configured to allow host port failover to occur is printed below. Virtual port
1 consists of standby physical ports 1 and 2, with physical port 1 (the primary port) currently active.
SNC233 > hpfShow
------------------------------------------------------------------------ Fibre
Channel Host Port Failover Display
------------------------------------------------------------------------ Virtual
Port Number | Active Port Index | Standby Port Index(es)
----------------------------------------------------------------------- Link Down Error Recovery Setting: Requires Intervention
Error Count Recovery Setting: Return to Standby
Link Down Delay Timer Setting: 3
-------------------------------------------------------------------------------Physical Port | failure type | Current Port | Requires | Active | Virtual
index ||State|Intervention | |
Port
-------------------------------------------------------------------------------1 | NONE | ONLINE | NO | YES | 1
2 | NONE | ONLINE | NO | NO | NONE
The hpfShowErrorRecoveryValues command displays the settings configured for recovery scenarios.
These settings are referenced by the hpfSetErrorRecovery command and the
The icmpstatShow command displays ICMP statistics for the Ethernet network. This command is only
available with Firmware 4. Interpreting these statistics requires detailed knowledge of Internet networking
protocols. This information can be useful to the LAN administrator.
SNC > icmpstatShow
ICMP:
0 call to icmp_error
0 error not generated because old message was icmp
0 message with bad code fields
0 message < minimum length
0 bad checksum
0 message with bad length
Input histogram:
destination unreachable: 1
0 message response generated
value = 30 = 0x1e
SNC >
ifShow
The ifShow command is used to show the Ethernet port parameters and status as shown below. The SNC
will show two devices. ibmEmac is the Ethernet port. lo is the local loopback port. If there is no functional
emac, users are unable to connect using either the serial port or a telnet session over the Ethernet port.
SNC > ifShow
ibmEmac (unit number 0):
Flags: (0x8063) UP BROADCAST MULTICAST ARP RUNNING
Type: ETHERNET_CSMACD
Internet address: 172.16.76.211
Broadcast address: 172.16.255.255
Netmask 0xffff0000 Subnetmask 0xffff0000
Ethernet address is 00:60:45:17:02:f0
Metric is 0
Maximum Transfer Unit size is 1500
114192 packets received; 364 packets sent
114023 multicast packets received
116 multicast packets sent
0 input errors; 0 output errors
0 collisions; 0 dropped
lo (unit number 0):
Flags: (0x8069) UP LOOPBACK MULTICAST ARP RUNNING
Type: SOFTWARE_LOOPBACK
Internet address: 127.0.0.1
Netmask 0xff000000 Subnetmask 0xff000000
Metric is 0
Maximum Transfer Unit size is 32768
0 packets received; 0 packets sent
0 multicast packets received
0 multicast packets sent
0 input errors; 0 output errors
0 collisions; 0 dropped
value = 29 = 0x1d
SNC >
SNC Firmware 4 and 5 Reference Guide91
inetstatShow
CAUTION
CAUTION
The inetstatShow command displays statistics about Internet protocol sockets for the Ethernet network.
Interpreting these statistics requires detailed knowledge of Internet networking protocols. This information
can be useful to the LAN administrator.
SNC > inetstatShow
Active Internet connections (including servers)
PCB Proto Recv-Q Send-Q Local Address Foreign Address (state)
Do not use this procedure if you are using an FCB in an intelligent
library ("i" series library, such as Scalar i2000 and Scalar i500) or
Pathlight VX system. Use the appropriate graphical user interface.
Use this function with care on other SNCs, as data can be lost as a
result of devices moving to different LUNs when the mapping
database is removed. Make sure all I/O has been stopped.
The initializeBox command
•removes configuration files, such as management configuration, SCSI device maps, SNMP
parameters, and health check parameters
•shuts down the log service
•removes the log file from the /log directory
•restores factory defaults
To make sure that information from attached hosts or targets is not “recaptued,” run initializeBox
without anything attached except a Telent session or serial port connection. When the command has
executed, you are prompted to reboot. The Ethernet address and SNC name remain unchanged. Factory
installed license keys remain, but features will have to be re-enabled.
The initializeBox command does not erase a global WWN override. Global WWN overrides are stored
in the VPD and are not touched by initializeBox. The port overrides, however, are stored in the
configuration database, which is cleared by the initializeBox command. As a result, individual port
WWN overrides will be cleared.
92Service Port Command Reference
ipstatShow
The ipstatShow command displays Internet protocol statistics for the Ethernet network. Interpreting these
statistics requires detailed knowledge of Internet networking protocols. This information can be useful to the
LAN administrator.
The licenseShow command displays information about software license keys that are installed and the
corresponding features that are available. The following example shows an SNC that contains a license key
for the SFM and Data Mover features.
SNC > licenseShow
License "wsk96-sd59a": Valid
Features:
SFM,
Data Mover.
value = 1 = 0x1
SNC >
loggerDump [number]
The loggerDump command dumps records from the system event log to the console. A numeric parameter
can be used to indicate the number of events to display. With no parameter specified, all events in the log
file are displayed starting with the most recent events.
SNC > loggerDump
*** Dumping 10 of 10 records ***
SEQUENCE TIME CODE DESCRIPTION
0001 FEB 21 2002 17:58:06 31 NOTICE: LOGGING STARTED
0002 FEB 21 2002 17:58:06 14 CS 1: Rev. 4.11.05 Built Feb 5
2002, 18:03:37
0003 FEB 21 2002 17:58:12 14SFM1: Enabled: State = Active, Hosts = 1
0004 FEB 21 2002 17:58:12 14 FCAL 1: External FIFO depth is
unknown (0x0700)
0005 FEB 21 2002 17:58:12 14 FCAL 2: External FIFO depth is
unknown (0x0700)
0006 FEB 21 2002 17:58:13 14 FCAL 1: LIP Initiated
0007 FEB 21 2002 17:58:13 14 FCAL 2: LIP Initiated
0008 FEB 21 2002 17:58:13 28 USCSI 2: Bus RESET
SNC Firmware 4 and 5 Reference Guide93
0009 FEB 21 2002 17:58:13 28 USCSI 4: Bus RESET
0010 FEB 21 2002 17:58:13 14 System 0: ES 1 CC 0/0 Prd 2 Snp
1 HP 1 fMax 254 RstI 0
SNC >
loggerDumpCurrent [level]
The loggerDumpCurrent command dumps records from the system event log to the console. With
loggerDump Current (as opposed to loggerDump) only records logged since the system was booted
are dumped. Unless the device time was configured, the time stamp is based on the time of the last boot.
The “level” specifies the event log level for the events as follows:
NumberLevelExplanation
0NoticeEvents recorded in the event log but not displayed by
the event viewer
1WarningIncludes events that should always be reported, such
as device removals, and changes to temperature or
power systems
2InformationIncludes events that might result in later problems
SNC > loggerDumpCurrent 2
*** Dumping 5 current records (of 13 total) with level <= 2 ***
SEQUENCE TIME CODE DESCRIPTION
0007 FEB 26 2002 19:01:14 28 USCSI 2: Bus RESET
0008 FEB 26 2002 19:01:14 28 USCSI 4: Bus RESET
0010 FEB 26 2002 19:01:14 29 Mapping 1: Target Device Added:
index 0
, handle 0x08fda380
0012 FEB 26 2002 19:01:26 29 Mapping 1: Target Device Added:
index 1
, handle 0x09ffcf08
0013 FEB 26 2002 19:01:27 70 NOTICE: Reboot Complete
value = 0 = 0x0
SNC >
ls or ll
The SNC contains a file system in its flash memory. Use the ls command to display the files as shown
below.