One other thing.  I think this is still applicable (craig or gilles might
know otherwise) -- that you want the 1st lun on the system to NOT be used by
your mpe box.  I don't exactly recall the reason why (it might have to do
with the label or something).  Anyhow, here's the first few lines of the
script I used when configuring luns on my va array:

armcfg	-L	0	-a	10M	-g	1
armcfg	-L	1	-a	4G	-g	1
armcfg	-L	2	-a	16G	-g	1
armcfg	-L	3	-a	9G	-g	1
armcfg	-L	4	-a	20G	-g	1
armcfg	-L	5	-a	30G	-g	1
armcfg	-L	6	-a	30G	-g	1

-L # -- indicates the lun number.  See how lun0 is quite tiny?  (0 = 1, how
computer) Also note how lun1 is configured.  It will eventually become ldev
1 (1 = 1, how human & tidy :-)  same for lun2, etc.

---
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330


> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of Joe Barnett
> Sent: Friday, April 17, 2009 8:36 AM
> To: [log in to unmask]
> Subject: [HP3000-L] Administrivia: N Class connecting to a VA7410
> 
> We are putting in a N3000-750 connecting via fiber to a VA7410 and are
> having issues.  the server can see the LUN's and can boot to the array
> ok
> When we try to restore our data via Orbit we keep getting
>  Bad SYSTEM LOGICAL Sector number 0x14EF520  on ldev 1
> (io_status=FFD90071)
>  Bad SYSTEM LOGICAL Sector number 0x14EF520  on ldev 1
> (io_status=FFD90071)
> We are connected through a fiber switch since we could not get the
> direct
> connection to work.
> 
> Has anyone run into this before and have any suggestions
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *