NAME | DESCRIPTION | EXAMPLES | FILES | SEE ALSO
The edd.emc file is an ASCII file that specifies how the system monitors certain events. Each system has only one EMC file.
The EMC file is generated from a template file upon invocation of the ssp_config(1M) command. The template file resides in $SSPVAR/.ssp_private/templates/Ultra-Enterprise-10000, and is named edd.emc.
The EMC file contains a series of lines in the following format:
event_type : load_event_monit
where:
A mnemonic (name string) which corresponds to an event type. See EXAMPLE, below.
A keyword, either enabled, which tells the system to load the event-monitoring script for the event type on the CBE, or disabled, which tells it not to.
The fields are separated by a single colon with or without a single space to its right and left. Words or characters that follow a pound sign (#) are treated as comments and are not parsed. The information in the edd.emc file is organized as follows:
System Board Temperature Events
System Board Voltage Events
Control Board Temperature Events
Control Board Voltage Events
Centerplane Temperature Events
Centerplane Voltage Events
Centerplane Support Board Temperature Events
Centerplane Support Board Voltage Events
Host Recovery Events
Other Events
sys_brd_temp_norm : enabled #over-temp readings that go back to normal sys_brd_temp_warn : enabled #brd temp which crosses warning threshold sys_brd_temp_max : enabled #brd temp which crosses maximum threshold sys_brd_temp_911 : enabled #brd temp which crosses 911 threshold sys_brd_temp_bad : enabled #unable to obtain brd temperatures sys_brd_temp_change : enabled #delta change in brd temperature |
sys_brd_volt_norm : enabled #max/min/bad voltage readings which go normal sys_brd_volt_max : enabled #brd voltage which crosses maximum threshold sys_brd_volt_min : enabled #brd voltage which crosses minimum threshold sys_brd_volt_bad : enabled #unable to obtain brd voltage values sys_brd_volt_change : enabled #delta change in brd voltage |
cb_temp_norm : enabled #see system board temperature descriptions cb_temp_warn : enabled cb_temp_max : enabled cb_temp_911 : enabled cb_temp_bad : enabled cb_temp_change : enabled |
cb_volt_norm : enabled #see system board voltage descriptions cb_volt_max : enabled cb_volt_min : enabled cb_volt_bad : enabled cb_volt_change : enabled |
centerplane_temp_norm : enabled #see system board temperature descriptions centerplane_temp_warn : enabled centerplane_temp_max : enabled centerplane_temp_911 : enabled centerplane_temp_bad : enabled centerplane_temp_change : enabled |
centerplane_volt_norm : enabled #see system board voltage descriptions centerplane_volt_max : enabled centerplane_volt_min : enabled centerplane_volt_bad : enabled centerplane_volt_change : enabled |
supp_brd_temp_norm : enabled #see system board temperature descriptions supp_brd_temp_warn : enabled supp_brd_temp_max : enabled supp_brd_temp_911 : enabled supp_brd_temp_bad : enabled supp_brd_temp_change : enabled |
supp_brd_volt_norm : enabled #see system board voltage descriptions supp_brd_volt_max : enabled supp_brd_volt_min : enabled supp_brd_volt_bad : enabled supp_brd_volt_change : enabled |
Certain event types are common among the different components listed above. The following list is organized by event type.
When the temperature of a board goes from over-temperature back to normal.
This event simply reports that temperature readings were not obtainable.
When the temperature readings of critical components on the board have changed by a predefined delta (see Predefined Values, below).
When the voltage reading of a board goes from a maximum or minimum voltage reading back to normal.
When the voltage reading of the board crosses a predefined maximum threshold value (see Predefined Values, below)
When the voltage reading of the board crosses a predefined minimum threshold value (see Predefined Values, below).
When the voltage readings are not obtainable.
When the voltage readings on the board have changed by a predefined delta (see Predefined Values, below).
Note that the InterDomain Network feature is supported only on the Sun Enterprise 10000.
idn_boot : enabled #cpu signature states indicate idn_boot idn_halt : enabled #cpu signature states indicate idn_halt idn_awol : enabled #cpu signature states indicate idn_awol cluster_arbstop : enabled #idn cluster arbitration stop condition cluster_recordstop : enabled #idn cluster record stop condition |
When a domain supporting IDN has booted and the respective IDN driver is loaded. This event indicates to edd(1M) that automatic IDN linking of the respective domain with other members within the same IDN is necessary, provided those other member domains have also been booted.
When an IDN driver that was previously loaded has been unloaded in the respective domain. This event works in conjunction with the idn_boot event to synchronize automatic IDN linking of domains.
When a domain reports that there are some other domains in the IDN that are nonresponsive or AWOL. This event indicates to edd(1M) to unlink the AWOL domains.
When domains within an IDN experience an arbstop. In the standard arbstop event, only state from the boards within the given domain is saved. However, in a cluster_arbstop, the state of all boards from all domains within the IDN is saved.
When domains within an IDN experience a recordstop. In the standard recordstop event, only state from the boards within the given domain is saved. However, in a cluster_recordstop, the state of all boards from all domains within the IDN is saved.
arbstop : enabled #arbstop condition on a sys brd in a domain recordstop : enabled #recordstop condition on a sys brd in a domain watchdog : enabled #watchdog condition on a sys brd in a domain environment_shutdown : enabled reboot : enabled #cpu signature states indicate reboot condition panic1 : enabled #cpu signature states indicate panic1 condition panic2 : enabled #cpu signature states indicate panic2 condition panic_reboot : enabled #cpu sig states indicate panic reboot condition obp_reset : enabled #cpu sig states indicate OBP reset condition obpbooting : enabled #cpu sig states indicate obp/booting condition heartbeat_failure : enabled #cpu heartbeat bits indicate heartbeat failure |
When a system board that belongs to a particular domain experiences an arbitration stop condition.
When a system board that belongs to a particular domain experiences a record stop condition.
When a processor (or set of processors) that belongs to a particular domain experiences a watch-dog condition.
When a processor (or set of processors) that belongs to a particular domain experiences an environmental shutdown condition.
When a processor (or set of processors) that belongs to a particular domain experiences a reboot condition.
When a processor (or set of processors) that belongs to a particular domain experiences a panic1 condition.
When a processor (or set of processors) that belongs to a particular domain experiences a panic2 condition.
When a processor (or set of processors) that belongs to a particular domain experiences a panic reboot condition.
When a processor (or set of processors) that belongs to a particular domain experiences an OBP reset condition.
When a processor (or set of processors) that belongs to a particular domain goes into OBP booting. This condition occurs when the domain is in the midst of booting.
When all the processors that belong to a particular domain experience a heartbeat failure condition.
signature_change : enabled #cpu signature has changed states system_config_change : enabled #any machine module is inserted/removed sys_brd_power_on : enabled #a system board has been powered on sys_brd_power_off : enabled #a system board has been powered off supp_brd_power_on : enabled #a support board has been powered on supp_brd_power_off : enabled #a support board has been powered off cb_power_on : enabled #a control board has been powered on cb_power_off : enabled #a control board has been powered off bulk_power_norm : enabled #bulk p. supply has gone from Failed/OFF to ON bulk_power_fail : enabled #bulk p. supply has gone from ON to Failed/OFF fan_norm : enabled #fan has gone from Failed to ON or OFF fan_fail : enabled #fan has gone from OFF/ON to Failed |
When a processor's signature block changes state.
This event describes a situation where any system board, centerplane support board, control board, fan tray, and/or bulk power supply is removed or inserted into the system.
When the power to a system board has switched from off to on.
When the power to a system board has switched from on to off.
When the power to a centerplane support board has switched from off to on.
When the power to a centerplane support board has switched from on to off.
When the power to a control board has switched from off to on.
When the power to a control board has switched from on to off.
When a bulk power supply has gone from an off or failed state to on.
When a bulk power supply has gone from an on to off or failed state.
When a fan has gone from a failed state to an on or off state.
When a fan has gone from an on or off state to failed state.
Predefined threshold values for over-temperature readings, delta values for temperature readings, and delta values for voltage readings are stored in the SSP's persistent store area; see ssp_resource(4).
# # Event Monitor Configuration File # centerplane_temp_warn : enabled centerplane_volt_max : enabled |
The above example tells the system to enable the two centerplane event types for monitoring.
NAME | DESCRIPTION | EXAMPLES | FILES | SEE ALSO