Sorry, this is a long one.
Here is what I want to do
-------------------------
Tonight we are adding a TL896 to an existing 2 node cluster (8400's - DUNIX
V4.0D + patch 3) - I'll refer to them as nodes P & Z. The silo will
ultimately belong to a tape service - but that's not until after a long
night! Each 8400 has 6 * KZPSA's to be added with appropriate Y cables etc
to connect the whole thing up. Each KZPSA to go to its own tape drive on
the silo.
The controllers will be added to both nodes 'at the end' of the existing
controllers to avoid device name changes etc.
What I need to understand is tape special file names, how to create them in
a consistent manner and how to test the silo. What I want to do tonight is
to show that the tapes are visible and work on both sides and are consistent
on both sides. The service creation will be done tomorrow during the day.
Please, if you have any comments, please pass them back.
best regards - Tony
Quotation: "Is the glass half full or half empty?? ...
Well, drink it anyhow, that's what I say".
Pete Goss.
+-----------------------------------------------------------------+
| TONY MILLER - Systems Projects - VODAFONE LTD, Derby House, |
| Newbury Business Park, Newbury, Berkshire. |
+-------------+---------------------------------------------------+
| Phone | 01635-507687(local) |
| Work email | ANTHONY.MILLER_at_VF.VODAFONE.CO.UK |
| FAX | 01635-233517 |
+-------------+---------------------------------------------------+
Disclaimer: Opinions expressed in this mail are my own and do not
reflect the company view unless explicitly stated. The information
is provided on an 'as is' basis and no responsibility is accepted for
any system damage howsoever caused.
Here is the relevant config on both nodes
-----------------------------------------
Node P already has 2 locally attached tape drives:
p>ls -l /dev/rmt*h
crw-rw-rw- 1 root system 9,199682 Sep 15 1998 /dev/rmt0h
crw-rw-rw- 1 root system 9,201730 Jan 28 13:50 /dev/rmt1h
p>file /dev/rmt*h
/dev/rmt0h: character special (9/199682) SCSI #12 TZ88 tape #327 (SCSI
ID #3
) (SCSI LUN #0) offline
/dev/rmt1h: character special (9/201730) SCSI #12 TZ887 tape #328 (SCSI
ID #
5) (SCSI LUN #0) loader 81630_bpi
p>scu show edt | grep -i sequential
Device: TZ88 Bus: 12, Target: 3, Lun: 0, Type: Sequential Access
Device: TZ887 Bus: 12, Target: 5, Lun: 0, Type: Sequential Access
Node Z already has 6 locally attached tape drives:
z>ls -l /dev/rmt*h
crw-rw-rw- 1 root system 9, 35842 Sep 14 1998 /dev/rmt0h
crw-rw-rw- 1 root system 9, 37890 Sep 14 1998 /dev/rmt1h
crw-rw-rw- 1 root system 9,199682 Feb 27 14:14 /dev/rmt2h
crw-rw-rw- 1 root system 9,201730 Sep 14 1998 /dev/rmt3h
crw-rw-rw- 1 root system 9,265218 Sep 14 1998 /dev/rmt4h
crw-rw-rw- 1 root system 9,267266 Feb 27 14:08 /dev/rmt5h
z>file /dev/rmt*h
/dev/rmt0h: character special (9/35842) SCSI #2 TZ88 tape #6 (SCSI ID
#3) (S
CSI LUN #0) offline
/dev/rmt1h: character special (9/37890) SCSI #2 TZ887 tape #7 (SCSI ID
#5) (
SCSI LUN #0) loader 81630_bpi
/dev/rmt2h: character special (9/199682) SCSI #12 TZ88 tape #330 (SCSI
ID #3
) (SCSI LUN #0) offline
/dev/rmt3h: character special (9/201730) SCSI #12 TZ887 tape #331 (SCSI
ID #
5) (SCSI LUN #0) loader 81630_bpi
/dev/rmt4h: character special (9/265218) SCSI #16 TZ88 tape #453 (SCSI
ID #3
) (SCSI LUN #0) offline
/dev/rmt5h: character special (9/267266) SCSI #16 TZ887 tape #454 (SCSI
ID #
5) (SCSI LUN #0) loader 81630_bpi
z>scu show edt | grep -i sequential
Device: TZ88 Bus: 2, Target: 3, Lun: 0, Type: Sequential Access
Device: TZ887 Bus: 2, Target: 5, Lun: 0, Type: Sequential Access
Device: TZ88 Bus: 12, Target: 3, Lun: 0, Type: Sequential Access
Device: TZ887 Bus: 12, Target: 5, Lun: 0, Type: Sequential Access
Device: TZ88 Bus: 16, Target: 3, Lun: 0, Type: Sequential Access
Device: TZ887 Bus: 16, Target: 5, Lun: 0, Type: Sequential Access
For service reasons, node P will be left online whilst node Z is taken down
and has its controllers installed, the silo connected and tested etc. When
we are happy, node P will also be taken down and connected to the silo and
the tape drives tested again. Then both nodes will be brought online.
Node Z will be booted single user from genvmunix after the installation of
the controllers, and a new kernel will be built then reboot from the new
kernel. I guess UNIX will automatically create me 6 new device special
files (rmt6* thru rmt11*).
Now, when we do node P and reboot after the kernel rebuild, I'll have 6 new
device special files created but they will be rmt2* thru rmt7* - i.e.., not
the same as node Z. This will stop me creating the tape service as the
device special files will NOT be the same on both nodes. To be consistent on
both sides, here is what I plan to do:
Node Z
------
1. Remove the new device special files (nrmt6*/rmt6* thru nrmt11*/rmt11*)
which were automatically created.
2. do a 'scu show edt | grep -i sequential' and note the bus, target and
LUN of each new tape drive.
3. The major number (I assume) is 9. Calculate the minor number for each
drive as follows:
Minor=(16384*bus)+(1024*target)+(64*lun).
4. Create the device special files:
mknod /dev/rmt6l c 9 minor_number
mknod /dev/nrmt6l c 9 minor_number+1
mknod /dev/rmt6h c 9 minor_number+2
mknod /dev/nrmt6h c 9 minor_number+3
mknod /dev/rmt6n c 9 minor_number+4
mknod /dev/nrmt6n c 9 minor_number+5
mknod /dev/rmt6a c 9 minor_number+6
mknod /dev/nrmt6a c 9 minor_number+7
5. Do a 'file /dev/rmt*h' to verify the drives are visible etc.
6. Load MRU (media robot utility) to permit me to manipulate the robot to
load tapes into each drive.
7. Test each drive works via a simple 'tar' command.
Node P
------
1. Remove the new device special files (nrmt2*/rmt2* thru nrmt7*/rmt7*)
which were automatically created.
2. do a 'scu show edt | grep -i sequential' and note the bus, target and
LUN of each new tape drive (should be the same as for node Z).
3. The major number (I assume) is 9. Calculate the minor number for each
drive as above.
4. Create the device special files as above.
5. Do a 'file /dev/rmt*h' to verify the drives are visible etc.
6. Load MRU (media robot utility) to permit me to manipulate the robot to
load tapes into each drive.
7. Test each drive works via a simple 'tar' command.
Received on Tue Jun 08 1999 - 11:53:38 NZST