Well, here I go again, replying to myself. Turns out everything is working correctly. It was a matter of getting the correct controller on my end (c11/c12/c13/c14) and matching that up with the correct WWN on the other end. When I re-read the install guide, I decided to just do a cfgadm -c configure on every WWN listed in the cfgadm -al output. Four of them matched, and I got my luns partitioned and newfs'd. -Adam ---------- Forwarded message ---------- Date: Wed, 21 Apr 2004 14:06:22 -0400 (EDT) From: Adam Levin <levins@westnet.com> To: Sun Managers Mailing List <sunmanagers@sunmanagers.org> Subject: new to SAN -- need some direction So we've got an Enterprise E3500 running Solaris 8 04/01 with the latest recommended patch cluster (as of last week). I've got a brandy-nifty new NetApp FAS960c with SAN functionality. It's connected to two Brocade SilkWorm 8 port switches. I've got two Sun SBus dual-port HBAs in my E3500 (both are the QLOGIC cards). They are likewise connected to the Brocade switches. I've installed the SFS 4.4 software packages and patches, and I rebooted the machine. I'm trying to follow the SFS install and config guides, but I'm getting a bit lost. I've never dealt with a SAN before. I run cfgadm -al and get this (I removed everything but the FC stuff): c11 fc-fabric connected unconfigured unknown c11::210100e08b299781 unknown connected unconfigured unknown c11::500a098183511e35 disk connected unconfigured unknown c11::500a098183f11ddf disk connected unconfigured unknown c11::500a098a83511e35 disk connected unconfigured unknown c11::500a098a83f11ddf disk connected unconfigured unknown c12 fc-fabric connected unconfigured unknown c12::210000e08b099781 unknown connected unconfigured unknown c12::500a098183511e35 disk connected unconfigured unknown c12::500a098183f11ddf disk connected unconfigured unknown c12::500a098a83511e35 disk connected unconfigured unknown c12::500a098a83f11ddf disk connected unconfigured unknown c13 fc-fabric connected unconfigured unknown c13::210100e08b27ecbb unknown connected unconfigured unknown c13::500a098383511e35 disk connected unconfigured unknown c13::500a098383f11ddf disk connected unconfigured unknown c13::500a098c83511e35 disk connected unconfigured unknown c13::500a098c83f11ddf disk connected unconfigured unknown c14 fc-fabric connected unconfigured unknown c14::210000e08b07ecbb unknown connected unconfigured unknown c14::500a098383511e35 disk connected unconfigured unknown c14::500a098383f11ddf disk connected unconfigured unknown c14::500a098c83511e35 disk connected unconfigured unknown c14::500a098c83f11ddf disk connected unconfigured unknown Now, the 500xxx stuff is confirmed to be the WWNs on the NetApp. I'm not sure what the 210xxx stuff is -- are those the WWNs of my HBAs? Why are they unknown? More importantly, if they *aren't* the WWNs of my HBAs, then how do I get the WWNs so that I can configure the NetApp LUNs correctly? Secondly, I've tried to configure the LUNs using cfgadm -c configure, but I get this: [14:05:18]root@oracle1.stage:/root$ cfgadm -c configure c11::500a098183511e35 cfgadm: Library error: failed to create device node: 500a098183511e35: Invalid argument Could this be because the LUNs don't have the correct WWNs associated with them, or is there perhaps another issue? Any help with this would be greatly appreciated -- it's all new to me. Thanks very much, -Adam _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed Apr 21 14:54:15 2004
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:31 EST