Diamond Storage Array Installation, Operations, Maintenance Manual
Table Of Contents
- Preface
- 1.0 Diamond Storage Array Product Overview
- 2.0 Diamond Storage Array Technical Overview
- 3.0 Installation Instructions
- 3.2 Physical Set Up
- 4.0 Determining Drive and Sled Designations
- 5.0 Accessing the Array
- Command Line Interface
- ATTO ExpressNAV
- In-band SCSI over Fibre Channel
- RS-232 port
- Ethernet port
- SNMP
- I/O details
- Browser compatibility
- Opening an ExpressNAV session
- Navigating ExpressNAV
- Exhibit 5.4-1 Atypical page in the ATTO ExpressNAV configuration tool.
- Status
- Ethernet
- SNMP
- Serial Port
- Fibre Channel
- Storage Management
- RAID
- Clear Data
- Logical Units
- Rebuild
- Configuration
- Advanced
- Restart
- Help
- FirmwareRestart
- Help
- RestoreConfiguration
- SaveConfiguration
- SystemSN
- VerboseMode
- EthernetSpeed
- FTPPassword
- IPAddress
- IPDHCP
- IPGateway
- IPSubnetMask
- SNMPTrapAddress
- SNMPTraps
- SNMPUpdates
- TelnetPassword
- TelnetTimeout
- TelnetUsername
- FcConnMode
- FcDataRate
- FcFairArb
- FcFrameLength
- FcFullDuplex
- FcHard
- FcHardAddress
- FcNodeName
- FcPortInfo
- FcPortList
- FcPortName
- FcWWName
- SerialPortBaudRate
- SerialPortEcho
- SerialPortHandshake
- SerialPortStopBits
- AudibleAlarm
- DiamondModel
- DiamondName
- DriveCopyStatus
- DriveInfo
- FcNodeName
- FcPortList
- FcPortName
- Help
- IdentifyDiamond
- Info
- LUNInfo
- SerialNumber
- SledFaultLED
- SMARTData
- Temperature
- VirtualDriveInfo
- FcScsiBusyStatus
- FirmwareRestart
- MaxEnclTempAlrm
- MinEnclTempAlrm
- Temperature
- Zmodem
- ATADiskState
- AutoRebuild
- ClearDiskReservedAreaData
- DriveCopy
- DriveCopyHalt
- DriveCopyResume
- DriveCopyStatus
- DriveInfo
- DriveSledPower
- DriveWipe
- IdeTransferRate
- LUNInfo
- LUNState
- QuickRAID0
- QuickRAID1
- QuickRAID5
- QuickRAID10
- RAID5ClearData
- RAID5ClearDataStatus
- RAIDInterleave
- RAIDHaltRebuild
- RAIDManualRebuild
- RAIDRebuildState
- RAIDRebuildStatus
- RAIDResumeRebuild
- RebuildPriority
- ResolveLUNConflicts
- RestoreModePages
- SledFaultLED
- VirtualDriveInfo
- 6.0 Configuring Drives
- JBOD (Just a Bunch of Disks)
- RAID Level 0
- RAID Level 1
- RAID Level 10
- RAID Level 5
- Interleave
- Hot Spare sleds
- Enhancing performance
- Sled-based versus disk-based
- Exhibit 6.2-1 Sled-based QuickRAID0 stripe groups with LUN designations in a fully populated Array set up as QuickRAID0 6 sled. If sled 6 were to be withdrawn from the array, LUN 3 (grayed boxes) would be unavailable.
- Exhibit 6.2-2 Drive-based QuickRAID0 stripe groups with LUN designations in a fully populated Array set up as QuickRAID0 6 Drive. If sled 6 were to be withdrawn from the array, LUNs 2 and 5 would be unavailable.
- Exhibit 6.2-3 Configurations of a fully populated Diamond Storage Array in RAID Level 0.
- Exhibit 6.3-1 Drive sleds, LUNs and mirror partners in a RAID Level 1 configuration.
- Hot Spare sleds
- Configuring a fully-populated array
- Configuring a partially-populated array
- Removing RAID groups
- Hot Spare sleds
- 7.0 Hardware Maintenance
- 8.0 Copying Drives
- 9.0 Updating Firmware
- 10.0 System Monitoring and Reporting
- RS-232 monitoring port and CLI
- Ethernet monitoring port and CLI
- Power On Self Test (POST)
- Ready LED
- Audible alarm
- Thermal monitoring
- Power supply monitoring
- System fault LED and error codes
- Disk drive activity and disk fault LEDs
- Windows 2000 special instructions
- Error messages
- Specific situations and suggestions
- Default
- Factory Default
- Appendix A ATA Disk Technology
- Appendix B Information Commands Results
- Appendix C Product Safety
- Appendix D Specifications
- Appendix E Warranty

19
ATTO Technology Inc. Diamond Storage Array Installation and Operation Manual
5.1 In-band CLI Over the Fibre Channel
In-band Command Line Interface (CLI) configures and manages the Diamond Storage Array using
SCSI-based CLI commands over a Fibre Channel port connection.
In-band CLI allows a programmer to configure
the Diamond Storage Array while it is moving
data. Using a programmer’s interface, CLI
commands as described previously in this manual
may be implemented.
In-band CLI is implemented as part of LUN 0. It
uses a different LUN than the array, and reports as
a Storage Enclosure Services (SES) device
(device type 0x0D).
LUN 0 is visible on all Fibre ports but is actually
a single unit. The default value for LUN 0 is 0x00.
LUN 0 must be reserved for each Write
Buffer/Read Buffer pair, using the SCSI Reserve
command to insure integrity of the in-band CLI
session.
1 An initiator (host) sends a SCSI Reserve
command to LUN 0.
• If LUN 0 is not reserved by another initiator,
LUN 0 is now reserved and ready to begin a
new CLI session.
• If the array configuration is reserved by a
different CLI session (i.e. serial or Telnet),
the in-band session will not be allowed to
modify the array configuration. If you try, the
results buffer of LUN 0 will return
Process X has the configuration
reserved.
ID of this session = Y
Ready.
2 The initiator issues a SCSI Write Buffer
command to LUN 0. A
Write Buffer
command
must be accompanied by an ASCII buffer
representing the CLI command string such as
set DiamondName Omega1
3 LUN 0 will execute the command line and
create feedback in the form of ASCII characters
into a buffer. This buffer is 8 KB and circular.
Retrieve the results by issuing a Read Buffer
command before issuing another Write Buffer
command.
4 A subsequent Write Buffer command will
execute the new command line and overwrite
the previous results in the buffer with new
results.
5 LUN 0 can be released by issuing a SCSI
Release command to the LUN after each
Write/Read Buffer
pair, or multiple
Write/Read
Buffer pairs.
I/O details
The buffer sent to the Services LUN during the
data out phase of a Write Buffer command must
be
• ASCII data
• maximum 80 bytes length
• terminated with either a carriage return
character (0x0D), line feed character (0x0A) or
NULL character (0x00)
• Characters following the first carriage return
character, line feed character or NULL character
are ignored.
The buffer retrieved from the Services LUN
during the data-in phase of a Read Buffer
command will be
• ASCII data
• 8 KBytes (8192 bytes) in length
• terminated with a NULL character (0x00)
• Characters following the NULL character are
meaningless.
Initiator (Host) Diamond Array
Reserve LUN 0 return: “ok”
Write Buffer
LUN 0
bid ‘AA’
“get Temperature”
executes the CLI command,
stores output in buffer
Read Buffer
LUN 0
bid ‘AA’
return:
”Temperature=28C\r\n\Ready
.\r\n\0”
Release LUN 0 return: “ok”










