On Wed, May 31, 2006 at 12:31:17PM -0700, Octave Orgeron wrote: > I agree that some consolidation and reorganization is required for the /dev > tree. However, I do believe it's important to maintain compatibility. Many > sysadmin's depend on knowing which device is on which pci bus, pci slot, or > IB cage , etc. It would be nice if that trace-ability is not lost. Having > generic names is nice, but having specific names cXtWWNdXsX is kinda handy > when swapping a disk or moving a LUN. To illustrate this issue.. lets say.. > > - 6900 with multiple domains > - Box is physically in another location > - Multiple NIC's and HBA's for multipathing > > If I want to know which NIC will be ce0 for jumpstarting, this requires some > foot work at the OBP. > > So ce0 could be /[EMAIL PROTECTED],0/[EMAIL PROTECTED],600000/[EMAIL > PROTECTED]/[EMAIL PROTECTED] in the OBP, which translates to PCI slot 7 on > IB6. This information will be reflected in /devices. > > Same situation with HBA's: > > c12 could be /[EMAIL PROTECTED],0/[EMAIL PROTECTED],600000/SUNW,[EMAIL > PROTECTED] in OBP, which translates to PCI slot 6 on IB6. > > Now multiply this by the number of NIC's and HBA's and you have a lot to > troubleshoot when something goes wrong. The good part is that the information > is very specific, so I track down a component if I have my sunsolve system > handbook ready. This is both a blessing and a curse. It takes time to track > down this kind of information. It would be nice to have a command to present > this information clearly and correctly. Manually tracking it down can be a > pain. >
yeah, we could do better in this space. do prtdiag and/or cfgadm help you in these situations? ed _______________________________________________ opensolaris-discuss mailing list [email protected]
