There's a command line interface that provides a certain amount of information
about the raid towers.
In either /usr/Navisphere/bin or /opt/Navisphere/bin there should be at least
these files.
-rw-r--r-- 1 root sys 2622 Mar 3 1999 agent.config
config file that tells the agent what to talk to, and who can talk
to what.
-r-xr-xr-x 1 root sys 3804580 Mar 27 1998 naviagent*
agent running on the box to allow query to the attached devices, is
started and stopped via /etc/init.d/agent
-r-xr-xr-x 1 root sys 1367 Jan 5 1998 naviagent.postinstall*
-r-xr-xr-x 1 root sys 3884396 Mar 27 1998 navicli*
command line interface which queries the attached device
---
Use 'format' to find out what scsi id the raid is attached as:
ROOT:nsm1.phx1.gctr.net [109]$ format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@b,2000/fibre-channel@2/sd@0,0
1. c1t14d0
/sbus@3,0/SUNW,fas@3,8800000/sd@e,0
2. c1t15d0
/sbus@3,0/SUNW,fas@3,8800000/sd@f,0
In this case, the raid device is c0t0d0.
To get information about that device, use:
./navicli -d c0t0d0s2
If you run navicli by itself, it will give you a (not very helpful) list of
commands. The most useful to me, thus far, has been 'getdisk'.
This produces output likes this (truncated):
Enclosure 1 Disk 1
Vendor Id: SEAGATE
Product Id: ST19171F CLAR09
Product Revision: 3511
Lun: 16
State: Hot Spare Ready
Hot Spare: YES
Prct Rebuilt: 100
Prct Bound: 100
Serial Number: LAW88956
Capacity: 8429
Private: 184320
Bind Signature: 3e92, 1, 1
Hard Read Errors: 0
Hard Write Errors 0
Soft Read Errors 0
Soft Write Errors 0
Read Retries 0
Write Retries 0
Remapped Sectors 0
Number of Reads 0
Number of Writes 0
----
If you get a 'cannot connect to device' error, there's likely a problem in
the config file. The agent.config file should have device entries like:
device c0t0d0s2 NAVISPHERE-1 "NAVISPHERE-1"
where the device name is the same as the one that you discovered through
format.