Thank you everyone who responded. We finally discovered the issue and unfortunately I misunderstood the problem, but still received many great answers. Unfortunately, due to my poor troubleshooting I was barking up the wrong tree. When we double-checked the 3510 we discovered we still needed to assign the lun to a hostid. However that said, I still wanted to summarize all the information so someone else can benefit from all your experiences. 1) Make sure your patches are up to date. You can go to sunsolve and have it scan to let you know if you have all the patches. 2) Several people suggested boot -r, touch /reconfigure and reboot, devfsadm, devlinks followed by disks, and cfgadm. Sometimes I still get a kick out of how many ways Sun has to rebuild its device tree ;-) 3) If you have internal fiber drives you need to turn-off the mpxio on the internal and enable the mpxio for the 3510. You can edit /kernel/drv/qlc.conf to disable the internal and /kernel/drv/scsi_vhci.conf for the 3510. Lastly, here is a good command example that was given to me. Try cfgadm -al and check to make sure that the disk devices listed under your FC HBAs are shown as configured. If not, use: cfgadm -c configure <controller id> e.g. cfgadm -c configure c6 (if that is your FC HBA) You can also configure one drive at a time using: cfgadm -c configure c6::<disk WWN> e.g. cfgadm -c configure c6::22000004cf9b6d17 Thank you again everyone. Have a great day, _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Jul 13 13:29:42 2004
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:35 EST