> One thing to be mindful of is that zpool and svcs both hard-code the > msg-IDs and keep track of fault status independently of fmd. zfs is a > bit better in that there is a zfs agent that connects zpool status with > what fmd is reporting and doing (i.e. retire or repair). > > In dladm, you will probably have to use libtopo to convert interface > names to a FMRI and then some fmd project private interfaces to get > fault information on the interfaces in question. > > Ideally, what we want is a single entry point for software like dladm to > query fault and FMRI information via libtopo. So, given an interface > name (just a property for a topo FMRI node), return the fault status. > This should be a very easy extension to libtopo and some additional > properties on topo FMRI nodes for network interfaces. > > If you're interested in pursuing this, let Rob Johnston know.
Understood. I'll file a CR and include this information, thanks! > I believe there are a number of instances in PCI and the hardened PCI > leaf drivers where hard faults are diagnosed for conditions that may not > immediately or subsequently impact the device or operating system. In > some instances, you may never see the condition again. Please read the > details section of the diagnosis article (http://www.sun.com/msg). A > number of PCI articles point out that some of the faults can be caused > by poorly seated controllers and recommend unplugging and plugging it > back in. > > But if you suspect that a device is being diagnosed as faulty > incorrectly or too soon, please notify the driver developer or open a > bug. The last thing we want is a bunch of NTF controllers getting > returned to the respective manufacturers. Agreed. -- meem
