Tom, Not sure the exact syntax on VMWare or Windows, but this is the equivalent of what you need to do on Solaris:
/usr/sbin/fcinfo hba-port \ | /usr/bin/grep "HBA Port WWN: " \ | /usr/bin/cut -d: -f2- \ | while read dev; do \ /usr/sbin/fcinfo remote-port -p $dev; \ done; \ /usr/sbin/devfsadm -C; \ /usr/sbin/devfsadm Essentially, this causes each local FC Port to scan for remote ports and then configures devices just found. Cheers, Joel. Tom Vaughan wrote:
Hello, I'm new to OpenSolaris, but I must say I am very impressed with my initial experiences with OpenSolaris and COMSTAR. My issues are with a home lab using some older equipment that is keeping my basement warm... OpenSolaris 2009.06 - COMSTAR TARGET HP DL140 G2 Server HP-branded Emulex LP8000 1GB FC HBA, Firmware 3.93a0 Using built in emlxs driver $ uname -a SunOS tom-solaris2 5.11 snv_111b i86pc i386 i86pc Solaris VMWare ESXi 4.0 - INITIATOR HP DL140 G2 Server HP-branded Emulex LP8000 1GB FC HBA, Firmware 2.80a (need to udpate) Windows Server 2003 SP2 32-bit - INITIATOR HP DL380 G2 Server HP-branded Emulex LP8000 1GB FC HBA, Firmware 3.93a0 Brocade Silkworm 2800 16-port 1GB FC Switch - Fabric OS 2.6.1c On my COMSTAR target, I have three file-based LUNs created. I have one target group, two host groups. Two LUNs presented to 2003 Server, using HG and TG One LUN present to VMWare Server, using HG and TG Having dealt with real FC SANs, I always bring up the switch first, then storage environment, then SAN-attached servers. With my lab at home, I have to bring up the switch, then the 2003 Server and VMWare Server, then boot the OpenSolaris COMSTAR server. Most times, the LUNS are automatically seen by the host, but sometimes I have to do a rescan. The Windows host will not boot if the COMSTAR server is up it gets stuck at Applying Computer Settings, the VMWare host just doesn't see the LUNs. In addition to that, creating new LUNs and trying to present them will require a reboot of the COMSTAR box before the servers can see thew new LUN. If this was only happening on the Windows server or the VMWare Server, I would expect a host issue. But I can't see how this could be anything but a COMSTAR target issue. I understand there are newer OpenSolaris builds (currently running snv_111b), so if an upgrade is recommended, I will have to figure out how to do that :) Thanks for any help! Please let me know if any logs or additional config information would be helpful Tom
_______________________________________________ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
