These messages look to be coming from your SP, indicating an ereport sourced in the SP could not be transported to Solaris for consumption by FMA. This happens via the ETM module in FMA (fmadm config will show if the module is loaded). It so happens that the syslogging of SP alerts also traverses ETM, so it's very likely the module is loaded and at least partially behaving.
As previously suggested, a support ticket should be opened to determine where the breakdown in communication is. I'd expect at a minimum support folks will want to know the versions of FW and OS involved. As for the DSC and DAC errors, these are correctable memory errors. Small numbers are nothing to worry about - they've been corrected in HW already. For deeper details, you can peruse the FMA event registry (http://hub.opensolaris.org/bin/view/Project+events-registry/WebHome). -scott -- This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list sysadmin-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
