From: Russ_Fish@idx.com
Date: Thu Jul 25 2002 - 21:01:41 EDT
Thanks to:
Warren Sturm
Bluejay Adametz
Joe Carrico
Suggestion we used:
swxcrmgr will work on V5, but you need to create the device special files
it's looking for.
Look in your /dev/rdisk directory and locate the major and minor device
numbers for the first drive on your SWXCR controller. Then use mknod to
create /dev/rre0c with those numbers.
We did the following:
# ls -l /dev/rdisk/dsk0c (1st disk, 1st controller)
crw------- 1 root system 19, 7 May 7 10:57 /dev/rdisk/dsk0c
# ls -l /dev/rdisk/dsk6c (1st disk, 2nd controller)
crw------- 1 root system 19,120 May 7 10:57 /dev/rdisk/dsk6c
then
# /usr/sbin/mknod /dev/rre0c c 19 7
# /usr/sbin/mknod /dev/rre8c c 19 120
(note swxcrmgr wants to see dsk6 as rre8)
giving
# ls -l /dev/rre*
crw-r--r-- 1 root system 19, 7 Jul 25 12:43 /dev/rre0c
crw-r--r-- 1 root system 19,120 Jul 25 12:53 /dev/rre8c
at which point swxcrmgr was happy.
Bluejay also pointed out a nice utility, /usr/lbin/ra200info5, which gives
a swxcr summary. This can be invoked with
# /usr/lbin/ra200info5 xcrX -f
(X <- controller number) to get a full report.
Other suggestions:
1. Run the RA200 agent on the server, then use SWCC. Recent kzpac or kzpsc
firmware (2.70) and SWCC 2.2 or 2.3 is recommended.
2. Use ra200rcu, or arccf.
Original messgage:
Hi all--
Anyone have a quick start guide on accessing SWXCRs in 5.1A? The old
swxcrmgr utility doesn't find the controllers, and I don't see where/now
Compaq's replacement for Mylexes (arccf.exe) can be made to work.
Any suggestions greatly appreciated.
--Russ
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:47 EDT