Instead of devfsadm, try your luck with 'cfgadm -c configure <controller>'
Verify with 'cfgadm -al' /dale On Nov 26, 2008, at 12:30 PM, Sean Alderman wrote: > Greetings, > > I'm curious if anyone might have a plausible explanation to some > strange behaviors I see between various Solaris 10 systems running > on Sun X64 hardware. > > We have a couple of EMC Symmetrix and Clariion SANs, and 20 or so > Sun Fire X4200 and X4600 servers. They all run Solaris 10, most of > them are also running Sun Cluster 3.2. I believe they all have Sun > branded emulex HBA's as well, and we are using PowerPath (for > reasons I am unaware of). > > In my experience, when adding new LUNs to these machines, the > X4200s (probably a mix of M2's and not) seem to be very capable of > picking up the new LUNs using devfsadm and powermt config. The > X4600s (definitely not M2's) do not seem to be able to discover new > LUNs and require the old reconfig reboot in order to pickup the new > LUNs. Our other Admins have reported that the X4200s also tend to > discover nothing new, but I have not personally witnessed this. I > have not seen any messages in /var/adm/messages that would indicate > failure or error while trying to discover the new devices. Devfsadm > -v shows no output when it doesn't find anything new. > > Can anyone offer ideas as to why this seems to be the case? Our > current theory has us wondering about HBA firmware levels between > the servers. > > Thanks. > -- > This message posted from opensolaris.org > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
