/usr/lib/fm/fmd/fmd [-V] [-f file] [-o opt=val] [-R dir]
fmd is a daemon that runs in the background on each Solaris system. fmd receives telemetry information relating to problems detected by the system software, diagnoses these problems, and initiates proactive self-healing activities such as disabling faulty components. When appropriate, the fault manager also sends a message to the syslogd(1M) service to notify an administrator that a problem has been detected. The message directs administrators to a knowledge article on Oracle's web site, https://support.oracle.com, which explains more about the problem impact and appropriate responses.
Each problem diagnosed by the fault manager is assigned a Universal Unique Identifier (UUID). The UUID uniquely identifes this particular problem across any set of systems. The fmdump(1M) utility can be used to view the list of problems diagnosed by the fault manager, along with their UUIDs and knowledge article message identifiers. The fmadm(1M) utility can be used to view the resources on the system believed to be faulty. The fmstat(1M) utility can be used to report statistics kept by the fault manager. The fault manager is started automatically when Solaris boots, so it is not necessary to use the fmd command directly. Sun's web site explains more about what capabilities are currently available for the fault manager on Solaris.
The standard notification mechanism for new diagnoses is by means of syslog, using the syslog-msgs fmd module delivered in the same package as fmd itself.
By default, only new problem diagnoses are messaged by means of syslog-msgs, using the syslog facility and severity as listed in the table below. An administrator can use svccfg(1M) to request that other events in the problem resolution lifecycle are messaged through syslog-msgs:
# svccfg setnotify event syslog:{active|inactive}
See svccfg(1M) for additional detail.
Event Disposition Facility Severity --------------- ---------------- --------------- ------------- problem-diagnosed active LOG_DAEMON LOG_ERR problem-updated inactive LOG_DAEMON LOG_NOTICE problem-repaired inactive LOG_DAEMON LOG_NOTICE problem-resolved inactive LOG_DAEMON LOG_NOTICE
Notification by means of email is an option for which an additional package must be installed. The SMF service, svc:/system/fm/smtp-notify:default, is delivered by means of the package system/fault-management/smtp-notify and notification preferences configured by means of svccfg(1M). See smtp-notify(1M) for additional detail. Note that in addition to configuring notification preferences for the problem lifecycle events listed above (problem-diagnosed, and so forth) this mechanism can also be configured through svccfg(1M) to provide notification of SMF instance state transition and other events.
Notification of new events using SNMP traps is an option delivered by the package system/fault-management/snmp-notify. The service svc:/system/fm/snmp-notify:default is responsible for raising SNMP traps for problem lifecycle and other designated events (including SMF instance state transition events, if so configured). See snmp-notify(1M) for additional detail.
The fault manager service svc:/system/fmd:default service is configured in both global and non-global Solaris zones. In non-global zones, various hardware-oriented fault manager modules are not delivered, so it is a cut-down fault manager that runs there. In a non-global zone, the fault manager is focussed on software events.
The following options are supported
Read the specified configuration file prior to searching for any of the default fault manager configuration files.
Set the specified fault manager option to the specified value. Fault manager options are currently a Private interface; see attributes(5) for information about Private interfaces.
Use the specified root directory for all pathnames evaluated by the fault manager, instead of the default root (/).
Print the fault manager's version to stdout and exit.
The following exit values are returned:
Successful completion
An error occurred which prevented the fault manager from initializing, such as failure to open the telemetry transport.
Invalid command-line options were specified.
Fault manager configuration directory
Fault manager library directory
Fault manager log directory
See attributes(5) for descriptions of the following attributes:
|
svcs(1), fmadm(1M), fmdump(1M), fmstat(1M), smtp-notify(1M), snmp-notify(1M), svccfg(1M), syslogd(1M), attributes(5), smf(5)
http://www.support.oracle.com/msg/
The Fault Manager is managed by the service management facility, smf(5), under the service identifier:
svc:/system/fmd:default
The service's status can be queried using the svcs(1) command. Administrators should not disable the Fault Manager service.