[SunHELP] Veritas VM help connecting to an ESS?

[sunhelp at sunhelp.org]

Tim does your sd.conf have entries for lun>0 ? ie.
name="sd" parent="lpfc" target=17 lun=0;
name="sd" parent="lpfc" target=17 lun=1;
name="sd" parent="lpfc" target=17 lun=2;
name="sd" parent="lpfc" target=17 lun=3;

I had a similar issue with the discovery part until I squared away the
sd.conf file.

-----Original Message-----
From: Tim Bingham [mailto:binghamt at upstate.edu]
Sent: Friday, July 25, 2003 9:56 AM
To: The SunHELP List
Subject: [SunHELP] Veritas VM help connecting to an ESS?


Hello,

I have Veritas Volume Manager 3.5 on a 420R running Solaris 7. I'm 
trying to connect two disks defined on an IBM ESS Shark through an 
Emulex LP8000 HBA.

I can see the disks correctly and configure them in VM without a problem.

At boot time though, the polling of the disks takes quite a while and 
Veritas VM starts before the second LUN is discovered. VM declares 
the second disk is missing and starts the process of moving data 
around to recreate the mirrors on the lost device. Once the system is 
booted to where I can login, I can issue a "vxdctl enable" and that 
rediscovers the disk and I can add it back into the disk group but 
it's too late.

Is there a way to discover the disks earlier in the boot process, or 
a way to delay the start of VM? The volumes on the disks in question 
are not part of rootdg. I tried forceloading the lpfc driver for the 
HBA in /etc/system but that didn't speed up polling of the disks.

Any help would be appreciated! I've been wrestling with this one for a
while.

Thanks,
Tim

-- 
ooooooooooooooooooooooooooooooooooo

Tim Bingham
SUNY Upstate Medical University
Syracuse, NY
binghamt at upstate.edu
_______________________________________________
SunHELP maillist  -  SunHELP at sunhelp.org
http://www.sunhelp.org/mailman/listinfo/sunhelp