So, I happen to have a pair of Sun Fire X4600s (configured in a HA Sun Cluster) which I'm trying to add 5 new LUNs to online, hoping to prove that it can be done w/o a reconfig reboot, as we have been able to do on other Sun Fire X64 machines.
Is it possible for cfgadm -c to cause problems with already configured disks? This cluster is a production database system, I'm more than happy to wait until the window where we'd planned to reboot them...but I'd like to give it a shot now if it is safe to do so. I have run the cfgadm -al (output below) in order to see what things look like currently. I'm very curious why I only see 2 FC disks, as this system already has 22 FC disks configured (as far as PowerPath shows). # cfgadm -al Ap_Id Type Receptacle Occupant Condition c3 scsi-bus connected configured unknown c3::dsk/c3t0d0 disk connected configured unknown c3::dsk/c3t2d0 disk connected configured unknown c4 fc-fabric connected configured unknown c4::5006048ad52fd298 disk connected configured unknown c5 fc-fabric connected unconfigured unknown c6 fc-fabric connected configured unknown c6::2103000d7775b000 tape connected configured unknown c7 fc-fabric connected configured unknown c7::5006048ad52fd2a7 disk connected configured unknown Any more thoughts? -- This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
