|
|
| System Event Reference | |
| Tru64 UNIX Version 5.1B, September 2002 |
© 2002 Hewlett-Packard Company
This manual lists all of the Event Manager events in Version 5.1B of the Tru64 UNIX operating system.
Microsoft© and Windows©, and Windows NT© are trademarks of Microsoft Corporation in the U.S. and/or other countries. Intel©, Pentium©, and Intel Inside© are trademarks of Intel Corporation in the U.S. and/or other countries. UNIX© is a trademark of The Open Group in the U.S. and/or other countries. All other product names mentioned herein may be trademarks of their respective companies.
Confidential computer software. Valid license from Compaq Computer Corporation, a wholly owned subsidiary of Hewlett-Packard Company, required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
None of Compaq, HP, or any of their subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP or Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
Event Index |
sys.unix: sys.unix sys.unix.binlog: sys.unix.binlog sys.unix.binlog.hw.backplane_raid_ctlr sys.unix.binlog.hw.console sys.unix.binlog.hw.correctable_env sys.unix.binlog.hw.correctable_rpt_switch sys.unix.binlog.hw.double_err_halt sys.unix.binlog.hw.emx sys.unix.binlog.hw.generic.adapter_error sys.unix.binlog.hw.generic.bus_error sys.unix.binlog.hw.generic.devcntl_error sys.unix.binlog.hw.i2o_error sys.unix.binlog.hw.machine_check sys.unix.binlog.hw.machine_state sys.unix.binlog.hw.machine_state.config sys.unix.binlog.hw.memory_error sys.unix.binlog.hw.mscp.disk_error sys.unix.binlog.hw.mscp.tape_error sys.unix.binlog.hw.recov_uncor sys.unix.binlog.hw.recov_uncor.processor sys.unix.binlog.hw.recov_uncor.system sys.unix.binlog.hw.scsi sys.unix.binlog.hw.stack_dump sys.unix.binlog.hw.stray_interrupt sys.unix.binlog.hw.swcc sys.unix.binlog.hw.system_console sys.unix.binlog.op.filterlog sys.unix.binlog.op.info.ascii_msg sys.unix.binlog.op.maint.diag sys.unix.binlog.op.maint.repair sys.unix.binlog.op.panic sys.unix.binlog.op.shutdown sys.unix.binlog.op.startup sys.unix.binlog.op.timestamp sys.unix.binlog.sw.advfs_domain_panic sys.unix.binlog.sw.ci_ppd sys.unix.binlog.sw.lsm.cont sys.unix.binlog.sw.lsm.note sys.unix.binlog.sw.lsm.warn sys.unix.binlog.sw.scs sys.unix.binlog.unknown_class sys.unix.binlog_chan: sys.unix.binlog_chan sys.unix.binlog_chan.binlog_size sys.unix.clu: sys.unix.clu.caa.action_script sys.unix.clu.caa.app.error sys.unix.clu.caa.app.modified sys.unix.clu.caa.app.registered sys.unix.clu.caa.app.running sys.unix.clu.caa.app.stopped sys.unix.clu.caa.app.transition sys.unix.clu.caa.app.trigger sys.unix.clu.caa.app.unregistered sys.unix.clu.caa.cli sys.unix.clu.caa.err sys.unix.clu.caa.res.profile.create sys.unix.clu.caa.res.profile.delete sys.unix.clu.caa.res.profile.update sys.unix.clu.cfs.advfs.no_server sys.unix.clu.cfs.advfs.not_served sys.unix.clu.cfs.advfs.served sys.unix.clu.cfs.fs.no_server sys.unix.clu.cfs.fs.not_served sys.unix.clu.cfs.fs.served sys.unix.clu.cfs.memory_warning sys.unix.clu.cfsd.anlys.relocsuggested sys.unix.clu.cfsd.control.active sys.unix.clu.cfsd.control.active_query sys.unix.clu.cfsd.control.inactive sys.unix.clu.cfsd.control.reconfigure sys.unix.clu.clua.config sys.unix.clu.clua.leave sys.unix.clu.clua.netroute sys.unix.clu.clua.no_gated sys.unix.clu.clua.proxy sys.unix.clu.clua.routeport sys.unix.clu.clua.routerstart sys.unix.clu.clua.routerstop sys.unix.clu.cnx.member.join sys.unix.clu.cnx.member.leave sys.unix.clu.cnx.qdisk.loss sys.unix.clu.cnx.qdisk.regain sys.unix.clu.cnx.quorum.gain sys.unix.clu.cnx.quorum.loss sys.unix.clu.drd.new_accessnode sys.unix.clu.drd.no_accessnode sys.unix.clu.drd.server_add sys.unix.clu.drd.server_leave sys.unix.clu.member.add sys.unix.clu.member.delete sys.unix.clu.shutdown.abort sys.unix.clu.shutdown.caa_alert sys.unix.clu.shutdown.clean sys.unix.clu.shutdown.private sys.unix.clu.shutdown.start sys.unix.clu.versw sys.unix.clu.versw.msg.success sys.unix.clu.wall sys.unix.evm: sys.unix.evm sys.unix.evm.chmgr sys.unix.evm.chmgr.cleanup_done sys.unix.evm.chmgr.config_error sys.unix.evm.control.reload.channel sys.unix.evm.control.reload.evmdaemon sys.unix.evm.control.reload.logger sys.unix.evm.control.startinet sys.unix.evm.daemon.config_completed sys.unix.evm.daemon.config_failure sys.unix.evm.daemon.config_failure.startup sys.unix.evm.daemon.event_activity sys.unix.evm.daemon.listening.inet sys.unix.evm.daemon.startup_completed sys.unix.evm.daemon.sync_failure sys.unix.evm.evmstart sys.unix.evm.kevm sys.unix.evm.kevm.initialized sys.unix.evm.kevm.lost_event sys.unix.evm.logger.config_err sys.unix.evm.logger.connection.lost sys.unix.evm.logger.connection.made sys.unix.evm.logger.connection.not_made sys.unix.evm.logger.log_closed sys.unix.evm.logger.log_start_err sys.unix.evm.logger.log_started sys.unix.evm.logger.log_write_err sys.unix.evm.logger.missed_event sys.unix.evm.logger.started sys.unix.evm.mark sys.unix.evm.mark.init sys.unix.evm.msg.admin sys.unix.evm.msg.user sys.unix.fs: sys.unix.fs sys.unix.fs.advfs.advscan.recreate sys.unix.fs.advfs.fdmn.addvol sys.unix.fs.advfs.fdmn.bad.mcell.list sys.unix.fs.advfs.fdmn.bal.error sys.unix.fs.advfs.fdmn.bal.lock sys.unix.fs.advfs.fdmn.bal.unlock sys.unix.fs.advfs.fdmn.ccbt.ignored sys.unix.fs.advfs.fdmn.frag.error sys.unix.fs.advfs.fdmn.frag.lock sys.unix.fs.advfs.fdmn.frag.unlock sys.unix.fs.advfs.fdmn.full sys.unix.fs.advfs.fdmn.mk sys.unix.fs.advfs.fdmn.panic sys.unix.fs.advfs.fdmn.rm sys.unix.fs.advfs.fdmn.rmvol.error sys.unix.fs.advfs.fdmn.rmvol.lock sys.unix.fs.advfs.fdmn.rmvol.unlock sys.unix.fs.advfs.fdmn.vd.extend sys.unix.fs.advfs.fset.backup.error sys.unix.fs.advfs.fset.backup.lock sys.unix.fs.advfs.fset.backup.unlock sys.unix.fs.advfs.fset.bad.frag sys.unix.fs.advfs.fset.clone sys.unix.fs.advfs.fset.inconsistent_dir_entry sys.unix.fs.advfs.fset.mk sys.unix.fs.advfs.fset.mount sys.unix.fs.advfs.fset.options sys.unix.fs.advfs.fset.quota.hblk.limit sys.unix.fs.advfs.fset.quota.hfile.limit sys.unix.fs.advfs.fset.quota.sblk.limit sys.unix.fs.advfs.fset.quota.sfile.limit sys.unix.fs.advfs.fset.rename sys.unix.fs.advfs.fset.rm.error sys.unix.fs.advfs.fset.rm.lock sys.unix.fs.advfs.fset.rm.unlock sys.unix.fs.advfs.fset.umount sys.unix.fs.advfs.quota.off sys.unix.fs.advfs.quota.on sys.unix.fs.advfs.quota.setgrp sys.unix.fs.advfs.quota.setusr sys.unix.fs.advfs.special.maxacc sys.unix.fs.advfs.ss.activated sys.unix.fs.advfs.ss.bal.disabled sys.unix.fs.advfs.ss.bal.enabled sys.unix.fs.advfs.ss.deactivated sys.unix.fs.advfs.ss.defrag.disabled sys.unix.fs.advfs.ss.defrag.enabled sys.unix.fs.advfs.ss.suspended sys.unix.fs.advfs.ss.topiobal.disabled sys.unix.fs.advfs.ss.topiobal.enabled sys.unix.fs.cdfs.mount sys.unix.fs.cdfs.umount sys.unix.fs.disklabel sys.unix.fs.newfs sys.unix.fs.nfs.mount sys.unix.fs.nfs.umount sys.unix.fs.ufs.mount sys.unix.fs.ufs.umount sys.unix.fs.vfs.freeze sys.unix.fs.vfs.thaw sys.unix.fs.vfs.thaw.failure sys.unix.fs.vfs.thaw.shutdown sys.unix.fs.vfs.thaw.timeout sys.unix.hw: sys.unix.hw sys.unix.hw.capacity_changed sys.unix.hw.cluster_attribute_change sys.unix.hw.connections_increased sys.unix.hw.connections_reduced sys.unix.hw.deregistered sys.unix.hw.dev_base_name_changed sys.unix.hw.environmental.fault.current sys.unix.hw.environmental.fault.fan sys.unix.hw.environmental.fault.power sys.unix.hw.environmental.fault.thermal sys.unix.hw.environmental.ok.current sys.unix.hw.environmental.ok.fan sys.unix.hw.environmental.ok.power sys.unix.hw.environmental.ok.thermal sys.unix.hw.environmental.warning.current sys.unix.hw.environmental.warning.fan sys.unix.hw.environmental.warning.power sys.unix.hw.environmental.warning.thermal sys.unix.hw.link_down.network sys.unix.hw.link_up.network sys.unix.hw.media_changed sys.unix.hw.net.netrain.alert sys.unix.hw.net.netrain.down sys.unix.hw.net.netrain.up sys.unix.hw.net.niff.alert sys.unix.hw.net.niff.down sys.unix.hw.net.niff.up sys.unix.hw.no_connections sys.unix.hw.platform.error.bus.pci sys.unix.hw.platform.error.environmental sys.unix.hw.platform.error.memory sys.unix.hw.platform.error.sensor sys.unix.hw.platform.warning.environmental sys.unix.hw.registered sys.unix.hw.scan_completed sys.unix.hw.state_change sys.unix.hw.state_change.assigned sys.unix.hw.state_change.available sys.unix.hw.state_change.broken sys.unix.hw.state_change.cod sys.unix.hw.state_change.indicted.high sys.unix.hw.state_change.indicted.low sys.unix.hw.state_change.indicted.medium sys.unix.hw.state_change.indicted.memory_page sys.unix.hw.state_change.limited sys.unix.hw.state_change.off sys.unix.hw.state_change.offline sys.unix.hw.state_change.offline_nosave sys.unix.hw.state_change.offline_request sys.unix.hw.state_change.online sys.unix.hw.state_change.testing sys.unix.hw.state_change.unassigned sys.unix.hw.state_change.unavailable sys.unix.hw.state_change.unindicted sys.unix.hw.state_change.unknown sys.unix.hw.user_name_changed sys.unix.install: sys.unix.install sys.unix.kernel: sys.unix.kernel.starting_cpu sys.unix.kernel.stopping_cpu sys.unix.lsm: sys.unix.lsm.volnotify.msg.deport sys.unix.lsm.volnotify.msg.dgchg sys.unix.lsm.volnotify.msg.dgdis sys.unix.lsm.volnotify.msg.dskchg sys.unix.lsm.volnotify.msg.dskdet sys.unix.lsm.volnotify.msg.import sys.unix.lsm.volnotify.msg.logdet sys.unix.lsm.volnotify.msg.more sys.unix.lsm.volnotify.msg.pldet sys.unix.lsm.volnotify.msg.sddet sys.unix.lsm.volnotify.msg.sdrel sys.unix.lsm.volnotify.msg.vold_dis sys.unix.lsm.volnotify.msg.vold_ena sys.unix.lsm.volnotify.msg.voldeg sys.unix.lsm.volnotify.msg.voldet sys.unix.misclog: sys.unix.misclog sys.unix.misclog.cronlog sys.unix.misclog.evmchmgr sys.unix.misclog.evmdaemon sys.unix.misclog.evmlogger sys.unix.misclog.smsd sys.unix.misclog.sulog sys.unix.net: sys.unix.net sys.unix.net.route.ip.add sys.unix.net.route.ip.change sys.unix.net.route.ip.delete sys.unix.nis: sys.unix.nis.yppush sys.unix.pc_card: sys.unix.pc_card sys.unix.pc_card.battery.dead sys.unix.pc_card.battery.low sys.unix.pc_card.insert sys.unix.pc_card.ready sys.unix.pc_card.remove sys.unix.pc_card.reset sys.unix.perfman: sys.unix.perfman sys.unix.power: sys.unix.power sys.unix.power.attr_change sys.unix.power.battery_change sys.unix.power.dev_dereg sys.unix.power.dev_reg sys.unix.power.state_change sys.unix.power.thermal_change sys.unix.print: sys.unix.print.lpd sys.unix.print.lpd.daemon.start sys.unix.print.lpd.daemon.stop sys.unix.print.lpd.job.remove.complete sys.unix.print.lpd.job.remove.request sys.unix.print.lpd.job.submit.complete sys.unix.print.lpd.job.submit.request sys.unix.print.pxc sys.unix.proc: sys.unix.proc.process_terminated sys.unix.psm: sys.unix.psm.category.create sys.unix.psm.category.remove sys.unix.psm.instance.create sys.unix.psm.instance.exited sys.unix.psm.instance.remove sys.unix.psm.set.create sys.unix.psm.set.remove sys.unix.runsyscheck: sys.unix.runsyscheck sys.unix.runsyscheck.process.not_found sys.unix.runsyscheck.process.started sys.unix.runsyscheck.process.terminated.error sys.unix.runsyscheck.process.terminated.success sys.unix.security: sys.unix.security.authorization.denied sys.unix.security.authorization.granted sys.unix.security.privilege.denied sys.unix.security.privilege.granted sys.unix.sys_check: sys.unix.sys_check sys.unix.sys_check.warning sys.unix.syslog: sys.unix.syslog sys.unix.syslog.auth sys.unix.syslog.cron sys.unix.syslog.daemon sys.unix.syslog.kern sys.unix.syslog.local0 sys.unix.syslog.local1 sys.unix.syslog.local2 sys.unix.syslog.local3 sys.unix.syslog.local4 sys.unix.syslog.local5 sys.unix.syslog.local6 sys.unix.syslog.local7 sys.unix.syslog.lpr sys.unix.syslog.mail sys.unix.syslog.mark sys.unix.syslog.megasafe sys.unix.syslog.news sys.unix.syslog.syslog sys.unix.syslog.user sys.unix.syslog.uucp sys.unix.sysman: sys.unix.sysman sys.unix.sysman.auto_deallocate.component.disable_fail sys.unix.sysman.auto_deallocate.component.offline_attempt sys.unix.sysman.auto_deallocate.component.offline_fail sys.unix.sysman.auto_deallocate.component.policy_evaluation.failure sys.unix.sysman.auto_deallocate.component.power_off_attempt sys.unix.sysman.auto_deallocate.component.power_off_fail sys.unix.sysman.auto_deallocate.component.user_supplied_script.failure sys.unix.sysman.auto_deallocate.component.user_supplied_script.success sys.unix.sysman.auto_deallocate.internal_error sys.unix.sysman.auto_deallocate.memory_page.mapout_attempt sys.unix.sysman.auto_deallocate.memory_page.policy_evaluation.failure sys.unix.sysman.auto_deallocate.memory_page.user_supplied_script.failure sys.unix.sysman.auto_deallocate.memory_page.user_supplied_script.success sys.unix.sysman.diskconfig.alias sys.unix.sysman.diskconfig.swap sys.unix.sysman.generic.config.fail sys.unix.sysman.generic.config.ok sys.unix.sysman.generic.deconfig.fail sys.unix.sysman.generic.deconfig.ok sys.unix.sysman.generic.file sys.unix.sysman.generic.file.create sys.unix.sysman.generic.file.modify sys.unix.sysman.generic.file.remove sys.unix.sysman.generic.process sys.unix.sysman.generic.process.restart sys.unix.sysman.generic.process.start sys.unix.sysman.generic.process.stop sys.unix.sysman.station sys.unix.sysman.station.client sys.unix.sysman.station.client.clear sys.unix.sysman.station.delete sys.unix.sysman.station.fsa sys.unix.sysman.station.fsa.delete sys.unix.sysman.station.fsa.delete.master sys.unix.sysman.station.fsa.new sys.unix.sysman.station.fsa.new.master sys.unix.sysman.station.fsa.nonoptimal sys.unix.sysman.station.fsa.optimal sys.unix.sysman.station.fsa.relocate sys.unix.sysman.station.mcl.master sys.unix.sysman.station.update sys.unix.sysman.station.update.object sys.unix.sysman.suitlet.context_changed sys.unix.sysman.suitlet.set_context sys.unix.vm: sys.unix.vm.memory_page.mapout.completed sys.unix.vm.memory_page.mapout.duplicate sys.unix.vm.memory_page.mapout.not_possible.outside_vm_managed_pool sys.unix.vm.memory_page.mapout.request Total: 393 events To Index
Event Details |
Events whose names begin with "sys.unix" are posted by a component of the operating system. The third component of the event name usually indicates which subsystem posted the event, and the event's message should indicate the reason.
*** EVENT sys.unix Explanation:
Template Dump:
Formatted Message:
Base system event
Event Data Items:
Event Name : sys.unix
Priority : 200
Format : Base system event
Reference : cat:evmexp.cat:20
Variable Items:
None
To Index
*** EVENT sys.unix.binlog
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. They
can contain complex binary data representing the machine state at
the point when an error was detected.
Template Dump:
Formatted Message:
Binary log event
Event Data Items:
Event Name : sys.unix.binlog
Priority : 200
Format : Binary log event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.backplane_raid_ctlr
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when a fault is detected on a RAID controller
backplane.
Template Dump:
Formatted Message:
SWXCR RAID controller event
Event Data Items:
Event Name : sys.unix.binlog.hw.backplane_raid_ctlr
Priority : 200
Format : SWXCR RAID controller event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.console
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type is not used in this operating system.
Template Dump:
Formatted Message:
Console event
Event Data Items:
Event Name : sys.unix.binlog.hw.console
Priority : 200
Format : Console event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.correctable_env
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when the system has recovered from an error that
has been detected in an environmental component such as a
temperature sensor, a power supply or a fan.
Action: Although the system has been able to recover from the error it may now be running under a reduced level of redundancy, and you should call your service provider to investigate the error.
Template Dump:
Formatted Message:
Correctable or uncorrectable environmental error occurred
Event Data Items:
Event Name : sys.unix.binlog.hw.correctable_env
Priority : 200
Format : Correctable or uncorrectable environmental error
occurred
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.correctable_rpt_switch
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when a high number of correctable errors have been
reported over a short period of time, and the system has
temporarily suppressed or re-enabled reporting. Reporting is
automatically re-enabled five minutes after suppression has
started.
Action: If this event occurs repeatedly contact your service provider.
Template Dump:
Formatted Message:
Correctable error reporting state changed
Event Data Items:
Event Name : sys.unix.binlog.hw.correctable_rpt_switch
Priority : 200
Format : Correctable error reporting state changed
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.double_err_halt
Explanation:
This event type is obsolete. The correct event name for this type
of event is sys.unix.binlog.hw.system_console.
Template Dump:
Formatted Message:
Double error halt
Event Data Items:
Event Name : sys.unix.binlog.hw.double_err_halt
Priority : 200
Format : Double error halt
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.emx
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when an error occurs in a device controlled by the
emx fiber channel host bus adaptor driver.
Template Dump:
Formatted Message:
EMX fiber channel adaptor (KGPSA) event
Event Data Items:
Event Name : sys.unix.binlog.hw.emx
Priority : 200
Format : EMX fiber channel adaptor (KGPSA) event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.generic.adapter_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is used to report errors occurring on certain adapters. It
is not used for SCSI adapters.
Action: Contact your service provider.
Template Dump:
Formatted Message:
Generic adapter error
Event Data Items:
Event Name : sys.unix.binlog.hw.generic.adapter_error
Priority : 200
Format : Generic adapter error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.generic.bus_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type is not used in this operating system. Bus errors will
result in machine check error events.
Template Dump:
Formatted Message:
Generic bus error
Event Data Items:
Event Name : sys.unix.binlog.hw.generic.bus_error
Priority : 200
Format : Generic bus error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.generic.devcntl_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event reports errors in certain types of device controllers,
including memory channel controllers. It is not used to report
SCSI controller errors.
Action: Contact your service provider.
Template Dump:
Formatted Message:
Generic device controller error
Event Data Items:
Event Name : sys.unix.binlog.hw.generic.devcntl_error
Priority : 200
Format : Generic device controller error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.i2o_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when an error occurs in a device connected to an
intelligent I/O ("i2o") bus.
Template Dump:
Formatted Message:
Intelligent I/O bus block storage error
Event Data Items:
Event Name : sys.unix.binlog.hw.i2o_error
Priority : 200
Format : Intelligent I/O bus block storage error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.machine_check
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type reports a serious system error.
Action: Contact your service provider.
Template Dump:
Formatted Message:
CPU machine check/exception - CPU $subid_num
Event Data Items:
Event Name : sys.unix.binlog.hw.machine_check
Priority : 200
Format : CPU machine check/exception - CPU $subid_num
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.machine_state
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type is posted to indicate a change in the system state. It
may be posted either by the power subsystem or by the FRU (field
replaceable unit) subsystem.
Template Dump:
Formatted Message:
Generalized machine state event
Event Data Items:
Event Name : sys.unix.binlog.hw.machine_state
Priority : 200
Format : Generalized machine state event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.machine_state.config
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type contains system configuration information, including a
copy of the Field Replaceable Unit (FRU) table, for use by Compaq
Analyze. The event is posted each time the system starts and
whenever a change is made to the system configuration.
Template Dump:
Formatted Message:
Configuration entry (FRU table)
Event Data Items:
Event Name : sys.unix.binlog.hw.machine_state.config
Priority : 200
Format : Configuration entry (FRU table)
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.memory_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event reports correctable (single bit) memory errors. Memory
errors that cannot be corrected are reported as machine check
errors.
Action: There is generally no action required if this event is witnessed sporadically, due to the fact that the reported memory error was corrected. If this event becomes more persistent, it may be indicative of a failing memory component. If the automatic deallocation policy defined in /etc/olar.config and /etc/olar.config.common is enabled, and Compaq Analyze is installed and running, the failing memory location will attempt to be deallocated automatically. Otherwise, it will be necessary to run Compaq Analyze to identify the failing memory component.
Template Dump:
Formatted Message:
Memory error
Event Data Items:
Event Name : sys.unix.binlog.hw.memory_error
Priority : 200
Format : Memory error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.mscp.disk_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event indicates that an error has occurred on an MSCP disk device.
Template Dump:
Formatted Message:
MSCP disk error
Event Data Items:
Event Name : sys.unix.binlog.hw.mscp.disk_error
Priority : 200
Format : MSCP disk error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.mscp.tape_error
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event indicates that an error has occurred on an MSCP tape device.
Template Dump:
Formatted Message:
MSCP tape error
Event Data Items:
Event Name : sys.unix.binlog.hw.mscp.tape_error
Priority : 200
Format : MSCP tape error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.recov_uncor
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. An
event in this class is posted when the system detects an
uncorrectable error that may be recoverable with assistance from
the firmware or the operating system, or both.
Action: Although the system may have been able to recover from the error, it is a serious error requiring action on the part of your service provider.
Template Dump:
Formatted Message:
Recoverable uncorrectable machine check
Event Data Items:
Event Name : sys.unix.binlog.hw.recov_uncor
Priority : 200
Format : Recoverable uncorrectable machine check
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.recov_uncor.processor
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when the system detects an uncorrectable processor
error that may be recoverable with assistance from the firmware or
the operating system, or both.
One example of such an error might be a double-bit-error in the level-2 cache, which may be recoverable if the cache block is shared and a valid copy of the block is available elsewhere in the system.
Action: Although the system may have been able to recover from the error, it is a serious error requiring action on the part of your service provider.
Template Dump:
Formatted Message:
Recoverable uncorrectable processor error
Event Data Items:
Event Name : sys.unix.binlog.hw.recov_uncor.processor
Priority : 200
Format : Recoverable uncorrectable processor error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.recov_uncor.system
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted when the system detects an uncorrectable system
error that may be recoverable with assistance from the firmware or
the operating system, or both.
One example of such an error might be a double-bit error on the system interconnect that is not consumed by the processor that reported the event. Another CPU in the system may report an uncorrectable system error if it also consumes the bad data.
Action: Although the system may have been able to recover from the error, it is a serious error requiring action on the part of your service provider.
Template Dump:
Formatted Message:
Recoverable uncorrectable system error
Event Data Items:
Event Name : sys.unix.binlog.hw.recov_uncor.system
Priority : 200
Format : Recoverable uncorrectable system error
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.scsi
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is used to report all SCSI device errors, including disk,
tape, HSZ raid events and adapter errors.
Action: Use Compaq Analyze or DECevent to read and analyze the system error log to determine if a SCSI device may need to be replaced.
Template Dump:
Formatted Message:
SCSI event
Event Data Items:
Event Name : sys.unix.binlog.hw.scsi
Priority : 200
Format : SCSI event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.stack_dump
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type is not used in this operating system.
Template Dump:
Formatted Message:
Stack dump
Event Data Items:
Event Name : sys.unix.binlog.hw.stack_dump
Priority : 200
Format : Stack dump
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.stray_interrupt
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event type is not used in this operating system.
Template Dump:
Formatted Message:
Stray interrupt
Event Data Items:
Event Name : sys.unix.binlog.hw.stray_interrupt
Priority : 200
Format : Stray interrupt
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.swcc
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog.
Events of this type are posted by the StorageWorks Command Console
(SWCC).
Template Dump:
Formatted Message:
StorageWorks Command Console (SWCC) event
Event Data Items:
Event Name : sys.unix.binlog.hw.swcc
Priority : 200
Format : StorageWorks Command Console (SWCC) event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.hw.system_console
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event contains information retrieved from the hardware log known as
the system console log. A single event can report one or more of
several different errors, including (but not limited to) a double
error halt, an environmental error, or a platform specific system
fault.
Action: Contact your service provider.
Template Dump:
Formatted Message:
System console event
Event Data Items:
Event Name : sys.unix.binlog.hw.system_console
Priority : 200
Format : System console event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.filterlog
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is used to report event filtering status for the binary error
log.
Template Dump:
Formatted Message:
Binary logger filterlog event
Event Data Items:
Event Name : sys.unix.binlog.op.filterlog
Priority : 200
Format : Binary logger filterlog event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.info.ascii_msg
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event contains a simple character string message. Messages of this
type are generally posted by the system administrator, using
logger(1) with the -b option.
Template Dump:
Formatted Message:
ASCII msg: $message
Event Data Items:
Event Name : sys.unix.binlog.op.info.ascii_msg
Priority : 200
Format : ASCII msg: $message
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.maint.diag
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. Refer
to the detailed event translation for more information about this
event.
Template Dump:
Formatted Message:
Maintenance: diagnostic msg: $message
Event Data Items:
Event Name : sys.unix.binlog.op.maint.diag
Priority : 200
Format : Maintenance: diagnostic msg: $message
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.maint.repair
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. Refer
to the detailed event translation for more information about this
event.
Template Dump:
Formatted Message:
Maintenance: repair message
Event Data Items:
Event Name : sys.unix.binlog.op.maint.repair
Priority : 200
Format : Maintenance: repair message
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.panic
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by kernel components as part of the system panic
process.
Action: Contact your service provider.
Template Dump:
Formatted Message:
System panic: $message
Event Data Items:
Event Name : sys.unix.binlog.op.panic
Priority : 200
Format : System panic: $message
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.shutdown
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the shutdown(8), halt(8) and reboot(8) commands
when the system is being shut down. The message includes details
of the user who initiated the shutdown.
Template Dump:
Formatted Message:
System shutdown msg: $message
Event Data Items:
Event Name : sys.unix.binlog.op.shutdown
Priority : 200
Format : System shutdown msg: $message
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.startup
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the kernel when the system is initialized. The
event includes details of the system configuration.
Template Dump:
Formatted Message:
System startup
Event Data Items:
Event Name : sys.unix.binlog.op.startup
Priority : 200
Format : System startup
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.op.timestamp
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted periodically by the binlogd daemon itself, to
indicate when and to ensure that the log contains up-to-date
information about the state of the system. If two timestamp events
are written consecutively, with no other event types intervening,
the later event overwrites the earlier one in the log, to conserve
space.
Template Dump:
Formatted Message:
System timestamp
Event Data Items:
Event Name : sys.unix.binlog.op.timestamp
Priority : 200
Format : System timestamp
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.sw.advfs_domain_panic
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event indicates that an AdvFS domain panic has occurred due to
either a metadata write error or an internal inconsistency. This
domain is being rendered inaccessible.
Action: Please refer to guidelines in the AdvFS Guide to File System Administration.
Template Dump:
Formatted Message:
AdvFS domain panic
Event Data Items:
Event Name : sys.unix.binlog.sw.advfs_domain_panic
Priority : 200
Format : AdvFS domain panic
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.sw.ci_ppd
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the Computer Interconnect Port-to-Port Driver
(CI PPD).
Template Dump:
Formatted Message:
CI PPD event
Event Data Items:
Event Name : sys.unix.binlog.sw.ci_ppd
Priority : 200
Format : CI PPD event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.sw.lsm.cont
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event contains informational data posted by the Logical Storage
Manager (LSM), indicating that the text from the prior event
extends beyond one line. Subsequent events are reported as
continuation events.
Template Dump:
Formatted Message:
LSM continuation
Event Data Items:
Event Name : sys.unix.binlog.sw.lsm.cont
Priority : 200
Format : LSM continuation
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.sw.lsm.note
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the Logical Storage Manager (LSM) as
notification of a normal but significant condition. The contents
of the event provide more information.
Template Dump:
Formatted Message:
LSM note
Event Data Items:
Event Name : sys.unix.binlog.sw.lsm.note
Priority : 200
Format : LSM note
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.sw.lsm.warn
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the Logical Storage Manager (LSM) as a warning
that some action has been taken in response to a system condition.
The event contains an ASCII string that can be used to determine
what happened.
Template Dump:
Formatted Message:
LSM warning
Event Data Items:
Event Name : sys.unix.binlog.sw.lsm.warn
Priority : 200
Format : LSM warning
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.sw.scs
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the Systems Communication Services (SCS) kernel
component.
Template Dump:
Formatted Message:
SCS event
Event Data Items:
Event Name : sys.unix.binlog.sw.scs
Priority : 200
Format : SCS event
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog.unknown_class
Explanation:
Binary error log events are posted through the binlogd daemon, and
stored in the binary error log file, /var/adm/binary.errlog. This
event is posted by the Event Manager/binary error log (binlog)
interface component when an unrecognized binary error log event is
posted.
Action: The event translation provided through the translation utility may provide more detail of the event.
Template Dump:
Formatted Message:
Unknown binary log event class $subid_class
Event Data Items:
Event Name : sys.unix.binlog.unknown_class
Priority : 200
Format : Unknown binary log event class $subid_class
Reference : cat:evmexp.cat:300
Variable Items:
None
To Index
*** EVENT sys.unix.binlog_chan
Explanation:
Binlog channel events are posted by functions in the "binlog" event
channel. This channel is responsible for retrieving binary error
log events and monitoring the state of the log.
Template Dump:
Formatted Message:
binlog event channel base event
Event Data Items:
Event Name : sys.unix.binlog_chan
Priority : 200
Format : binlog event channel base event
Reference : cat:evmexp.cat:330
Variable Items:
None
To Index
*** EVENT sys.unix.binlog_chan.binlog_size
Explanation:
This event is posted by the binlog event channel's daily cleanup
function, to allow the system administrator to monitor the size of
the log. Note that since the message reports the size to one
decimal place, if the size is less than about 50,000 bytes the
message will show the value rounded down to 0.0 Mbytes. The actual
size of the file in bytes can be seen by requesting a detailed
display of the event.
Action: No action is taken by the event channel other than to post this event, and by default the log is unmanaged. See the binlogd(8) reference page for information about cleaning up the log to reduce its size.
Template Dump:
Formatted Message:
binlog channel: Binary error log size is Mbytes
Event Data Items:
Event Name : sys.unix.binlog_chan.binlog_size
Priority : 200
Format : binlog channel: Binary error log size is $mbytes Mbytes
Reference : cat:evmexp.cat:330
Variable Items:
bytes (UINT32) = 0
mbytes (STRING) = ""
logname (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.action_script
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) action scripts when they take a notable action.
Template Dump:
Formatted Message:
CAA: resource $name action script none (none): none
Event Data Items:
Event Name : sys.unix.clu.caa.action_script._name.none._host.none
Cluster Event : True
Priority : 200
Format : CAA: resource $name action script $script ($action):
$message
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = "none"
_host (STRING) = "none"
script (STRING) = "none"
action (STRING) = "none"
message (STRING) = "none"
To Index
*** EVENT sys.unix.clu.caa.app.error
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when it recognizes that the specified managed
application has experienced an error, and has terminated.
Template Dump:
Formatted Message:
CAA: resource went UNKNOWN on
Event Data Items:
Event Name : sys.unix.clu.caa.app.error
Cluster Event : True
Priority : 500
Format : CAA: resource $_name went UNKNOWN on $_host
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
_host (STRING) = ""
when (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.app.modified
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when a registered application has been modified.
Template Dump:
Formatted Message:
CAA: resource was modified
Event Data Items:
Event Name : sys.unix.clu.caa.app.modified
Cluster Event : True
Priority : 300
Format : CAA: resource $_name was modified
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.app.registered
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when a new application has been registered.
Template Dump:
Formatted Message:
CAA: resource was registered
Event Data Items:
Event Name : sys.unix.clu.caa.app.registered
Cluster Event : True
Priority : 300
Format : CAA: resource $_name was registered
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.app.running
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when it starts an application. The message
identifies the cluster member running the application.
Template Dump:
Formatted Message:
CAA: resource started on
Event Data Items:
Event Name : sys.unix.clu.caa.app.running
Cluster Event : True
Priority : 300
Format : CAA: resource $_name started on $_host
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
_host (STRING) = ""
when (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.app.stopped
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when it stops an application which has been running
under its control.
Template Dump:
Formatted Message:
CAA: resource stopped on
Event Data Items:
Event Name : sys.unix.clu.caa.app.stopped
Cluster Event : True
Priority : 300
Format : CAA: resource $_name stopped on $_host
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
_host (STRING) = ""
when (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.app.transition
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when it transitions a managed application from one
state to another.
Template Dump:
Formatted Message:
CAA: is transitioning from state to state on member
Event Data Items:
Event Name : sys.unix.clu.caa.app.transition
Cluster Event : True
Priority : 300
Format : CAA: $_name is transitioning from state $current to
state $target on member $_host
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
current (STRING) = ""
target (STRING) = ""
_host (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.app.trigger
Explanation:
This event is posted by an application to request an action to be
performed by the Cluster Application Availability subsystem (CAA).
Template Dump:
Formatted Message:
CAA is requested to perform action check on resource none by unknown
Event Data Items:
Event Name : sys.unix.clu.caa.app.trigger._name.none._action.check
Cluster Event : True
Priority : 200
Format : CAA is requested to perform action $_action on
resource $_name by $source
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = "none"
_action (STRING) = "check"
source (STRING) = "unknown"
To Index
*** EVENT sys.unix.clu.caa.app.unregistered
Explanation:
This informational event is posted by the Cluster Application
Availability subsystem (CAA) when a previously-registered
application has been unregistered.
Template Dump:
Formatted Message:
CAA: resource was unregistered
Event Data Items:
Event Name : sys.unix.clu.caa.app.unregistered
Cluster Event : True
Priority : 300
Format : CAA: resource $_name was unregistered
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.cli
Explanation:
This generic event is used by Cluster Application Availability
(CAA) commands to display informational messages.
Template Dump:
Formatted Message:
CAA CLI Console:
Event Data Items:
Event Name : sys.unix.clu.caa.cli
Cluster Event : True
Priority : 200
Format : CAA CLI Console: $CAA_LOGGER
Reference : cat:evmexp_caa.cat
Variable Items:
CAA_LOGGER (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.err
Explanation:
This generic event is used by Cluster Application Availability
(CAA) commands to display error messages.
Template Dump:
Formatted Message:
CAA: Error Log:
Event Data Items:
Event Name : sys.unix.clu.caa.err
Cluster Event : True
Priority : 200
Format : CAA: Error Log: $CAA_LOGGER
Reference : cat:evmexp_caa.cat
Variable Items:
CAA_LOGGER (STRING) = ""
To Index
*** EVENT sys.unix.clu.caa.res.profile.create
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when a resource profile has been created.
Template Dump:
Formatted Message:
CAA resource none profile was created
Event Data Items:
Event Name : sys.unix.clu.caa.res.profile.create._name.none
Cluster Event : True
Priority : 300
Format : CAA resource $_name profile was created
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = "none"
To Index
*** EVENT sys.unix.clu.caa.res.profile.delete
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when a resource profile has been deleted.
Template Dump:
Formatted Message:
CAA resource none profile was deleted
Event Data Items:
Event Name : sys.unix.clu.caa.res.profile.delete._name.none
Cluster Event : True
Priority : 300
Format : CAA resource $_name profile was deleted
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = "none"
To Index
*** EVENT sys.unix.clu.caa.res.profile.update
Explanation:
This event is posted by the Cluster Application Availability
subsystem (CAA) when a resource profile has been updated.
Template Dump:
Formatted Message:
CAA resource none profile was updated
Event Data Items:
Event Name : sys.unix.clu.caa.res.profile.update._name.none
Cluster Event : True
Priority : 300
Format : CAA resource $_name profile was updated
Reference : cat:evmexp_caa.cat
Variable Items:
_name (STRING) = "none"
To Index
*** EVENT sys.unix.clu.cfs.advfs.no_server
Explanation:
This event is posted by the cluster filesystem (CFS) to indicate
that an attempt to failover the server of the named AdvFS domain
has failed. There is currently no server for the domain.
Template Dump:
Formatted Message:
CFS: There is no server for AdvFS domain
Event Data Items:
Event Name : sys.unix.clu.cfs.advfs.no_server
Cluster Event : True
Priority : 300
Format : CFS: There is no server for AdvFS domain $domain_name
Reference : cat:evmexp_clu.cat
Variable Items:
domain_name (STRING) = ""
fs_type (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfs.advfs.not_served
Explanation:
This event is posted by the cluster filesystem (CFS) to indicate
that the specified node is no longer the server for the named AdvFS
domain.
Template Dump:
Formatted Message:
CFS: AdvFS domain is no longer served by node
Event Data Items:
Event Name : sys.unix.clu.cfs.advfs.not_served
Cluster Event : True
Priority : 200
Format : CFS: AdvFS domain $domain_name is no longer served by
node $node_name
Reference : cat:evmexp_clu.cat
Variable Items:
domain_name (STRING) = ""
node_name (STRING) = ""
fs_type (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfs.advfs.served
Explanation:
This event is posted by the cluster filesystem (CFS) to indicate
that a filesystem has been mounted in the cluster, or that an AdvFS
domain for which this node is the server has been relocated or
failed over.
Template Dump:
Formatted Message:
CFS: AdvFS domain is now served by node
Event Data Items:
Event Name : sys.unix.clu.cfs.advfs.served
Cluster Event : True
Priority : 200
Format : CFS: AdvFS domain $domain_name is now served by node
$node_name
Reference : cat:evmexp_clu.cat
Variable Items:
domain_name (STRING) = ""
node_name (STRING) = ""
fs_type (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfs.fs.no_server
Explanation:
This event is posted by the cluster filesystem (CFS) to indicate
that an attempt to failover the server of a non-AdvFS file system
has failed. There is currently no server for the file system.
Template Dump:
Formatted Message:
CFS: There is no server for filesystem
Event Data Items:
Event Name : sys.unix.clu.cfs.fs.no_server
Cluster Event : True
Priority : 300
Format : CFS: There is no server for filesystem $mounted_dir
Reference : cat:evmexp_clu.cat
Variable Items:
mounted_dir (STRING) = ""
fs_type (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfs.fs.not_served
Explanation:
This event is posted by the cluster filesystem (CFS) when the
specified node is no longer the server for the named filesystem.
Template Dump:
Formatted Message:
CFS: Filesystem is no longer served by node
Event Data Items:
Event Name : sys.unix.clu.cfs.fs.not_served
Cluster Event : True
Priority : 200
Format : CFS: Filesystem $mounted_dir is no longer served by
node $node_name
Reference : cat:evmexp_clu.cat
Variable Items:
mounted_dir (STRING) = ""
node_name (STRING) = ""
fs_type (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfs.fs.served
Explanation:
This event is posted by the cluster filesystem (CFS) to indicate
that a filesystem has been mounted in the cluster, or that a
filesystem for which this node is the server has been relocated or
failed over.
Template Dump:
Formatted Message:
CFS: Filesystem is now served by node
Event Data Items:
Event Name : sys.unix.clu.cfs.fs.served
Cluster Event : True
Priority : 200
Format : CFS: Filesystem $mounted_dir is now served by node
$node_name
Reference : cat:evmexp_clu.cat
Variable Items:
mounted_dir (STRING) = ""
node_name (STRING) = ""
fs_type (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfs.memory_warning
Explanation:
This event is posted by the cluster filesystem (CFS) to indicate
that the node is approaching its server token structure limit. Once
this limit is reached, applications that access files served by the
node will begin to receive EMFILE (too many open files) errors. See
the section on adjusting CFS memory usage in the "Managing File
Systems and Devices" chapter of the Cluster Administration guide
for more information about this limit.
Action: To ease CFS memory usage on the node, one or more of the filesystems served by the node can be relocated to other nodes in the cluster using the cfsmgr command. See the cfsmgr(8) reference page for details.
Template Dump:
Formatted Message:
CFS: Node is approaching its server token structure limit - 0 of 0
allocated
Event Data Items:
Event Name : sys.unix.clu.cfs.memory_warning
Cluster Event : True
Priority : 300
Format : CFS: Node $node_name is approaching its server token
structure limit - $nsvrcfstoks of $maxsvrcfstoks
allocated
Reference : cat:evmexp_clu.cat
Variable Items:
node_name (STRING) = ""
nsvrcfstoks (UINT64) = 0
maxsvrcfstoks (UINT64) = 0
To Index
*** EVENT sys.unix.clu.cfsd.anlys.relocsuggested
Explanation:
This event is posted by the cluster filesystem (CFS) load
monitoring daemon (cfsd) after it has completed a filesystem
placement analysis and the analysis includes one or more
recommended relocations. The log file indicated in the event
contains the complete analysis report, including any recommended
relocations.
Action: Review the analysis report to decide if any of the placement recommendations are appropriate for your environment. If so, the cfsmgr command can be used to perform those relocations. See the cfsmgr(8) reference page for details.
Template Dump:
Formatted Message:
cfsd: Filesystem relocation is recommended - see for details
Event Data Items:
Event Name : sys.unix.clu.cfsd.anlys.relocsuggested
Cluster Event : True
Priority : 200
Format : cfsd: Filesystem relocation is recommended - see
$logfile for details
Reference : cat:evmexp_clu.cat:800
Variable Items:
logfile (STRING) = ""
To Index
*** EVENT sys.unix.clu.cfsd.control.active
Explanation:
This informational event is posted by the cluster filesystem (CFS)
load monitoring daemon (cfsd) when it becomes active on a node.
No action is required.
Template Dump:
Formatted Message:
cfsd: CFS daemon is active on node -
Event Data Items:
Event Name : sys.unix.clu.cfsd.control.active
Cluster Event : True
Priority : 0
Format : cfsd: CFS daemon is active on node @MEMBER_ID
Reference : cat:evmexp_clu.cat:800
Variable Items:
None
To Index
*** EVENT sys.unix.clu.cfsd.control.active_query
Explanation:
This event is posted by the cluster filesystem (CFS) load
monitoring daemon (cfsd) to request that the other instances of
cfsd in the cluster identify themselves by posting
sys.unix.clu.cfsd.control.active events.
Template Dump:
Formatted Message:
cfsd: Active query request received from node -
Event Data Items:
Event Name : sys.unix.clu.cfsd.control.active_query
Cluster Event : True
Priority : 0
Format : cfsd: Active query request received from node
@MEMBER_ID
Reference : cat:evmexp_clu.cat:800
Variable Items:
None
To Index
*** EVENT sys.unix.clu.cfsd.control.inactive
Explanation:
This informational event is posted by the cluster filesystem (CFS)
load monitoring daemon (cfsd) when it is no longer active on a
node.
No action is required.
Template Dump:
Formatted Message:
cfsd: CFS daemon is no longer active on node -
Event Data Items:
Event Name : sys.unix.clu.cfsd.control.inactive
Cluster Event : True
Priority : 0
Format : cfsd: CFS daemon is no longer active on node @MEMBER_ID
Reference : cat:evmexp_clu.cat:800
Variable Items:
None
To Index
*** EVENT sys.unix.clu.cfsd.control.reconfigure
Explanation:
This event is posted by the cluster filesystem (CFS) load
monitoring daemon (cfsd) when it receives a SIGHUP signal to tell
all instances of cfsd in the cluster to reread the cfsd
configuration file. Upon receiving this event, cfsd rereads its
configuration file.
Template Dump:
Formatted Message:
cfsd: Reconfigure request received from node -
Event Data Items:
Event Name : sys.unix.clu.cfsd.control.reconfigure
Cluster Event : True
Priority : 0
Format : cfsd: Reconfigure request received from node @MEMBER_ID
Reference : cat:evmexp_clu.cat:800
Variable Items:
None
To Index
*** EVENT sys.unix.clu.clua.config
Explanation:
This event is posted by the cluster alias manager (cluamgr) in
response to a cluamgr -a operation to configure a cluster alias.
Template Dump:
Formatted Message:
CLUA: Cluster Alias has been configured by node with selw 0 selp 0 rpri
0 flags 0x0
Event Data Items:
Event Name : sys.unix.clu.clua.config
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Cluster Alias ${clua_addr} has been configured
by node ${node_name} with selw ${selw} selp ${selp}
rpri ${rpri} flags 0x${flags}
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
selw (INT32) = 0
selp (INT32) = 0
rpri (INT32) = 0
flags (INT32) = 0
To Index
*** EVENT sys.unix.clu.clua.leave
Explanation:
This event is posted by the cluster alias manager (cluamgr) in
response to a cluamgr -a operation to leave a cluster alias.
Template Dump:
Formatted Message:
CLUA: Cluster Alias has been left by node
Event Data Items:
Event Name : sys.unix.clu.clua.leave
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Cluster Alias ${clua_addr} has been left by node
${node_name}
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.clua.netroute
Explanation:
This event is posted by the cluster alias daemon (aliasd) when it
sets up a route for a virtual subnet via gated.
Template Dump:
Formatted Message:
CLUA: Node has defined a network route for Cluster Alias virtual subnet
Event Data Items:
Event Name : sys.unix.clu.clua.netroute
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Node ${node_name} has defined a network route
for Cluster Alias virtual subnet ${clua_addr}
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.clua.no_gated
Explanation:
This event is posted by the cluster alias daemon (aliasd) when it
is has been told to not restart "gated" after writing a new gated
configuration file.
Template Dump:
Formatted Message:
CLUA: Node is running "aliasd" with "gated" disabled. Cluster alias may
not function properly.
Event Data Items:
Event Name : sys.unix.clu.clua.no_gated
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Node ${node_name} is running "aliasd" with
"gated" disabled. Cluster alias may not function
properly.
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.clua.proxy
Explanation:
This event is posted by the cluster alias daemon (aliasd) when
aliasd on the given node wins the right to be the "proxy arp
master" for a common subnet cluster alias IP address.
Template Dump:
Formatted Message:
CLUA: Node is responding to ARP requests for Cluster Alias
Event Data Items:
Event Name : sys.unix.clu.clua.proxy
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Node ${node_name} is responding to ARP requests
for Cluster Alias ${clua_addr}
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.clua.routeport
Explanation:
This event is posted by the cluster alias daemon (aliasd) when it
cannot obtain exclusive ownership of the routing message port, and
it cannot determine that "gated" is running.
Template Dump:
Formatted Message:
CLUA: Node appears to be running a program other than "gated" which has
exclusive ownership of the routing message port
Event Data Items:
Event Name : sys.unix.clu.clua.routeport
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Node ${node_name} appears to be running a
program other than "gated" which has exclusive
ownership of the routing message port
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.clua.routerstart
Explanation:
This event is posted by the cluster alias manager (cluamgr) in
response to a cluamgr -r start operation to start cluster alias
routing operations.
Template Dump:
Formatted Message:
CLUA: Node has configured gated for Cluster Alias
Event Data Items:
Event Name : sys.unix.clu.clua.routerstart
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Node ${node_name} has configured gated for
Cluster Alias ${clua_addr}
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.clua.routerstop
Explanation:
This event is posted by the cluster alias manager (cluamgr) in
response to a cluamgr -r stop operation to stop cluster alias
routing operations.
Template Dump:
Formatted Message:
CLUA: Node has stopped routing for Cluster Alias
Event Data Items:
Event Name : sys.unix.clu.clua.routerstop
Priority : 200
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : CLUA: Node ${node_name} has stopped routing for
Cluster Alias ${clua_addr}
Reference : cat:evmexp_clu.cat
Variable Items:
clua_addr (STRING) = ""
node_name (STRING) = ""
To Index
*** EVENT sys.unix.clu.cnx.member.join
Explanation:
This informational event is posted by the cluster subsystem's
connection manager when it recognizes that a new member has been
added to the cluster. The name of the new member is specified in
the event variable "joining_node".
Template Dump:
Formatted Message:
CNX MGR: Node (no host) incarn 0 id 0 has joined the cluster
Event Data Items:
Event Name : sys.unix.clu.cnx.member.join
Priority : 200
Format : CNX MGR: Node $host incarn $incarn id $memberid has
joined the cluster
Reference : cat:evmexp_clu.cat
Variable Items:
host (STRING) = "(no host)"
incarn (UINT64) = 0
memberid (INT32) = 0
csid (UINT32) = 0
To Index
*** EVENT sys.unix.clu.cnx.member.leave
Explanation:
This informational event is posted by the cluster subsystem's
connection manager when it recognizes that an existing member node
has left the cluster. The name of the former member is specified
in the event variable "removed_node", and the reason is specified
in the string variable "reason".
Template Dump:
Formatted Message:
CNX MGR: Node (no host) incarn 0 id 0 has been removed from the cluster
Event Data Items:
Event Name : sys.unix.clu.cnx.member.leave
Priority : 200
Format : CNX MGR: Node $host incarn $incarn id $memberid has
been removed from the cluster
Reference : cat:evmexp_clu.cat
Variable Items:
host (STRING) = "(no host)"
incarn (UINT64) = 0
memberid (INT32) = 0
csid (UINT32) = 0
reason (STRING) = "Reason not specified"
reason_code (UINT64) = 0
To Index
*** EVENT sys.unix.clu.cnx.qdisk.loss
Explanation:
This error event is posted by the cluster subsystem's connection
manager when it detects that the quorum disk has become unavailable
and its votes can no longer contribute to the cluster's
availability. The loss of availability implies that the cluster
may no longer tolerate the loss of a member node without losing
quorum.
The identity of the quorum disk is given by its device major and minor numbers in the event variables "major" and "minor". The type of failure detected is given by the event variable "etype" and the completion status of the previous I/O operation by "errno".
Template Dump:
Formatted Message:
CNX MGR: Cluster quorum disk 0,0 has become unavailable due to a (unknown)
error (status 0)
Event Data Items:
Event Name : sys.unix.clu.cnx.qdisk.loss
Priority : 500
Format : CNX MGR: Cluster quorum disk $major,$minor has become
unavailable due to a $etype error (status $errno)
Reference : cat:evmexp_clu.cat
Variable Items:
major (UINT32) = 0
minor (UINT32) = 0
errno (UINT32) = 0
etype (STRING) = "(unknown)"
To Index
*** EVENT sys.unix.clu.cnx.qdisk.regain
Explanation:
This informational event is posted by the cluster subsystem's
connection manager when it recognizes that the quorum disk has
again become available for use. The identity of the quorum disk is
given by its device major and minor numbers in the event variables
"major" and "minor".
Template Dump:
Formatted Message:
CNX MGR: Cluster quorum disk 0,0 has become available again
Event Data Items:
Event Name : sys.unix.clu.cnx.qdisk.regain
Priority : 200
Format : CNX MGR: Cluster quorum disk $major,$minor has become
available again
Reference : cat:evmexp_clu.cat
Variable Items:
major (UINT32) = 0
minor (UINT32) = 0
To Index
*** EVENT sys.unix.clu.cnx.quorum.gain
Explanation:
This informational event is posted by the cluster subsystem's
connection manager when it recognizes that the node has gained its
quorum and become available for use. A node has quorum when the
number of votes visible to the node is greater than or equal to the
votes required for quorum.
Template Dump:
Formatted Message:
CNX MGR: Node has (re)gained quorum (current votes 0, quorum votes 0)
Event Data Items:
Event Name : sys.unix.clu.cnx.quorum.gain
Priority : 200
Format : CNX MGR: Node has (re)gained quorum (current votes
$current_vote, quorum votes $quorum_vote)
Reference : cat:evmexp_clu.cat
Variable Items:
current_vote (UINT64) = 0
quorum_vote (UINT64) = 0
To Index
*** EVENT sys.unix.clu.cnx.quorum.loss
Explanation:
This error event is posted by the cluster subsystem's connection
manager when it detects that the node has become unavailable due to
lost quorum. A node loses its quorum when the the number of votes
visible to the node is less than the votes required for quorum.
Refer to the cluster administration manual for a discussion of how the connection manager calculates quorum and how to restore quorum for a cluster.
Template Dump:
Formatted Message:
CNX MGR: Node has become unavailable due to quorum loss (current votes 0,
quorum votes 0)
Event Data Items:
Event Name : sys.unix.clu.cnx.quorum.loss
Priority : 500
Format : CNX MGR: Node has become unavailable due to quorum
loss (current votes $current_vote, quorum votes
$quorum_vote)
Reference : cat:evmexp_clu.cat
Variable Items:
current_vote (UINT64) = 0
quorum_vote (UINT64) = 0
To Index
*** EVENT sys.unix.clu.drd.new_accessnode
Explanation:
This event is posted by a DRD client to indicate that it has
selected a server as a new access node for the specified device.
Template Dump:
Formatted Message:
DRD: Server (no name) selected for device 0
Event Data Items:
Event Name : sys.unix.clu.drd.new_accessnode._hwid.0
Cluster Event : True
Priority : 200
Format : DRD: Server $server_name selected for device $_hwid
Reference : cat:evmexp_clu.cat
Variable Items:
disk_type (STRING) = ""
server_name (STRING) = "(no name)"
_hwid (INT64) = 0
reason_code (INT32) = 0
To Index
*** EVENT sys.unix.clu.drd.no_accessnode
Explanation:
This event is posted by a DRD client to indicate that it could not
find a server for the specified device.
Template Dump:
Formatted Message:
DRD: No server found for device 0
Event Data Items:
Event Name : sys.unix.clu.drd.no_accessnode._hwid.0
Cluster Event : True
Priority : 300
Format : DRD: No server found for device $_hwid
Reference : cat:evmexp_clu.cat
Variable Items:
disk_type (STRING) = ""
_hwid (INT64) = 0
reason_code (INT32) = 0
errno (INT32) = 0
failover_type (INT32) = 0
eei (INT16) = 0
To Index
*** EVENT sys.unix.clu.drd.server_add
Explanation:
This event indicates that a new hardware component has appeared on
the system, and has been recognized by the system hardware
configuration manager. The component is accessible from this node,
and the DRD server has been mapped for this component.
Template Dump:
Formatted Message:
DRD: Added (mapped) DRD server (no name)
Event Data Items:
Event Name : sys.unix.clu.drd.server_add._hwid.0
Cluster Event : True
Priority : 200
Format : DRD: Added (mapped) DRD server $server_name
Reference : cat:evmexp_clu.cat
Variable Items:
disk_type (STRING) = ""
server_name (STRING) = "(no name)"
_hwid (INT64) = 0
reason_code (INT32) = 0
server_state (INT32) = 0
To Index
*** EVENT sys.unix.clu.drd.server_leave
Explanation:
This event indicates that a hardware component has been removed
from the system, or that all paths to the component have failed.
The component con no longer be accessed from this node, and the DRD
server has been unmapped for this component.
Template Dump:
Formatted Message:
DRD: Removed (unmapped) DRD server (no name)
Event Data Items:
Event Name : sys.unix.clu.drd.server_leave._hwid.0
Cluster Event : True
Priority : 200
Format : DRD: Removed (unmapped) DRD server $server_name
Reference : cat:evmexp_clu.cat
Variable Items:
disk_type (STRING) = ""
server_name (STRING) = "(no name)"
_hwid (INT64) = 0
reason_code (INT32) = 0
server_state (INT32) = 0
To Index
*** EVENT sys.unix.clu.member.add
Explanation:
This informational event is posted by the cluster command
"clu_add_member" after all processing necessary to boot a new
member has completed successfully.
Template Dump:
Formatted Message:
clu_add_member: Member '%s' has been added to the cluster configuration.
Event Data Items:
Event Name : sys.unix.clu.member.add
Cluster Event : True
Priority : 200
I18N Msg Id : 1
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : clu_add_member: Member ${memberid} has been added to
the cluster configuration
Reference : cat:evmexp_clu.cat
Variable Items:
memberid (STRING) = ""
To Index
*** EVENT sys.unix.clu.member.delete
Explanation:
This informational event is posted by the cluster command
"clu_delete_member" after it has performed the initial step which
would prevent a node from booting as a cluster member.
Template Dump:
Formatted Message:
clu_delete_member: Member '%s' has been deleted from the cluster
configuration.
Event Data Items:
Event Name : sys.unix.clu.member.delete
Cluster Event : True
Priority : 200
I18N Msg Id : 2
I18N Set Id : 41
I18N Catalog : clu_common.cat
Format : clu_delete_member: Member ${memberid} has been deleted
from the cluster configuration
Reference : cat:evmexp_clu.cat
Variable Items:
memberid (STRING) = ""
To Index
*** EVENT sys.unix.clu.shutdown.abort
Explanation:
This event is posted by the clu_shutdown utility when a shutdown
operation has been aborted.
Template Dump:
Formatted Message:
clu_shutdown: Cluster shutdown aborted
Event Data Items:
Event Name : sys.unix.clu.shutdown.abort
Cluster Event : True
Priority : 200
Format : clu_shutdown: Cluster shutdown aborted
Reference : cat:evmexp_clu.cat
Variable Items:
None
To Index
*** EVENT sys.unix.clu.shutdown.caa_alert
Explanation:
This event is posted by the clu_shutdown utility to alert the CAA
monitoring software that a shutdown is occurring.
Template Dump:
Formatted Message:
clu_shutdown: CAA alert event
Event Data Items:
Event Name : sys.unix.clu.shutdown.caa_alert
Cluster Event : True
Priority : 0
Format : clu_shutdown: CAA alert event
Reference : cat:evmexp_clu.cat
Variable Items:
None
To Index
*** EVENT sys.unix.clu.shutdown.clean
Explanation:
This event is posted by the clu_shutdown utility to indicate that
it is responding to a request to clean up temporary "nologin"
files.
Template Dump:
Formatted Message:
clu_shutdown: Cleaning nologin files
Event Data Items:
Event Name : sys.unix.clu.shutdown.clean
Cluster Event : True
Priority : 200
Format : clu_shutdown: Cleaning nologin files
Reference : cat:evmexp_clu.cat
Variable Items:
None
To Index
*** EVENT sys.unix.clu.shutdown.private
Explanation:
This event is posted by the clu_shutdown utility to indicate that
it has completed a "private message" shutdown request.
Template Dump:
Formatted Message:
clu_shutdown: Private message operation complete
Event Data Items:
Event Name : sys.unix.clu.shutdown.private
Cluster Event : True
Priority : 0
Format : clu_shutdown: Private message operation complete
Reference : cat:evmexp_clu.cat
Variable Items:
None
To Index
*** EVENT sys.unix.clu.shutdown.start
Explanation:
This event is posted by the clu_shutdown utility when it begins a
cluster shutdown operation.
Template Dump:
Formatted Message:
clu_shutdown: Starting cluster shutdown
Event Data Items:
Event Name : sys.unix.clu.shutdown.start
Cluster Event : True
Priority : 200
Format : clu_shutdown: Starting cluster shutdown
Reference : cat:evmexp_clu.cat
Variable Items:
None
To Index
*** EVENT sys.unix.clu.versw
Explanation:
Events in this category are posted by the /usr/share/versw
command. See the versw(8) reference page for more information
about this command.
Template Dump:
Formatted Message:
versw: Base event
Event Data Items:
Event Name : sys.unix.clu.versw
Priority : 200
Format : versw: Base event
Reference : cat:evmexp.cat:1800
Variable Items:
None
To Index
*** EVENT sys.unix.clu.versw.msg.success
Explanation:
This event is posted by the /usr/sbin/versw -switch command when a
successful version switch has been accomplished. See the versw(8)
reference page for more information about this command.
Template Dump:
Formatted Message:
versw: Successful cluster version switch by -. Old version: New version:
Event Data Items:
Event Name : sys.unix.clu.versw.msg.success
Cluster Event : True
Priority : 600
Format : versw: Successful cluster version switch by
@host_name. Old version: $old_vers_str New version:
$new_vers_str
Reference : cat:evmexp.cat:1800
Variable Items:
new_vers_str (STRING) = ""
old_vers_str (STRING) = ""
To Index
*** EVENT sys.unix.clu.wall
Explanation:
This cluster_wide event is posted by the clu_wall utility when a
message is to be distributed to all users of the cluster. The
event contains the message text, and is subscribed to by the
clu_wall daemon running on all nodes. The daemon is responsible
for distributing the message to users.
Template Dump:
Formatted Message:
clu_wall msg:
Event Data Items:
Event Name : sys.unix.clu.wall
Cluster Event : True
Priority : 200
Format : clu_wall msg: $mesg
Reference : cat:evmexp_clu.cat
Variable Items:
mesg (STRING) = ""
To Index
*** EVENT sys.unix.evm
Explanation:
Events whose names begin with "sys.unix.evm" are posted by the
Event Manager (EVM), either for control purposes or to report a
change in status. The event's message should indicate the reason
for the event.
Template Dump:
Formatted Message:
EVM base event
Event Data Items:
Event Name : sys.unix.evm
Priority : 200
Format : EVM base event
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.chmgr
Explanation:
Events whose names begin with "sys.unix.evm.chmgr" are posted by
the Event Manager (EVM) channel manager facility. The channel
manager runs as a child of the EVM daemon, and performs periodic
operations on configured event channels.
Template Dump:
Formatted Message:
EVM Channel Manager base event
Event Data Items:
Event Name : sys.unix.evm.chmgr
Priority : 200
Format : EVM Channel Manager base event
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.chmgr.cleanup_done
Explanation:
This event is posted by the Event Manager (EVM) channel manager
facility when it has completed a channel cleanup operation. The
cleanup operation involves running any cleanup commands specified
in the EVM channel configuration file. Cleanup is performed once
daily, at the time specified in the channel configuration file.
Template Dump:
Formatted Message:
EVM channel mgr: Log cleanup completed
Event Data Items:
Event Name : sys.unix.evm.chmgr.cleanup_done
Priority : 200
Format : EVM channel mgr: Log cleanup completed
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.chmgr.config_error
Explanation:
This event is posted by the Event Manager's channel manager
facility when it is unable to complete configuration, either
because its configuration file is missing or unreadable, or because
it contains an error.
Action: The file /var/evm/adm/logfiles/evmchmgr.log contains error information. Once the error has been rectified, use the evmreload(8) command to reconfigure the channel manager.
Template Dump:
Formatted Message:
EVM channel mgr: Channel config error - no event channels configured
Event Data Items:
Event Name : sys.unix.evm.chmgr.config_error
Priority : 400
Format : EVM channel mgr: Channel config error - no event
channels configured
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.control.reload.channel
Explanation:
This control event is posted by the evmreload(8) command to request
the Event Manager's channel manager facility to reload its
configuration.
Template Dump:
Formatted Message:
EVM: Configuration reload requested for channel manager
Event Data Items:
Event Name : sys.unix.evm.control.reload.channel
Cluster Event : True
Priority : 200
Format : EVM: Configuration reload requested for channel manager
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.control.reload.evmdaemon
Explanation:
This control event is posted by the evmreload(8) command to request
the EVM daemon to reload its configuration.
Template Dump:
Formatted Message:
EVM: Configuration reload requested for daemon
Event Data Items:
Event Name : sys.unix.evm.control.reload.evmdaemon
Cluster Event : True
Priority : 200
Format : EVM: Configuration reload requested for daemon
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.control.reload.logger
Explanation:
This control event is posted by the evmreload(8) command to request
the Event Manager's logger facility to reload its configuration.
Template Dump:
Formatted Message:
EVM: Configuration reload requested for logger
Event Data Items:
Event Name : sys.unix.evm.control.reload.logger
Cluster Event : True
Priority : 200
Format : EVM: Configuration reload requested for logger
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.control.startinet
Explanation:
The Event Manager (EVM) "startinet" control event is used to notify
the EVM daemon that the network is now operational. The daemon
responds by establishing a remote connection socket.
Template Dump:
Formatted Message:
EVM: Network start control event
Event Data Items:
Event Name : sys.unix.evm.control.startinet
Priority : 100
Format : EVM: Network start control event
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.daemon.config_completed
Explanation:
This informational event is posted by the Event Manager (EVM)
daemon to indicate that it has completed configuring itself.
Configuration occurs when EVM is started and when a reload is
explicitly requested through the evmreload(8) command or by sending
a SIGHUP signal to the daemon.
Template Dump:
Formatted Message:
EVM daemon: Configuration completed
Event Data Items:
Event Name : sys.unix.evm.daemon.config_completed
Priority : 200
Format : EVM daemon: Configuration completed
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.daemon.config_failure
Explanation:
This event is posted by the Event Manager daemon when it detects a
failure while reconfiguring itself. Details of the failure are
available from the daemon's log file,
/var/evm/adm/logfiles/evmdaemon.log.
Action: Review the daemon's log file to determine the reason for the failure. Once the problem has been corrected you can reload the configuration by running evmreload(8).
Template Dump:
Formatted Message:
EVM daemon: configuration failure
Event Data Items:
Event Name : sys.unix.evm.daemon.config_failure
Priority : 600
Format : EVM daemon: configuration failure
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.daemon.config_failure.startup
Explanation:
This event is posted by the Event Manager daemon when it fails to
configure itself at startup. Details of the failure are available
from the daemon's log file, /var/evm/adm/logfiles/evmdaemon.log.
Action: Review the daemon's log file to determine the reason for the failure. Once the problem has been corrected you can reload the configuration by running evmreload(8).
Template Dump:
Formatted Message:
EVM daemon: configuration failure on startup
Event Data Items:
Event Name : sys.unix.evm.daemon.config_failure.startup
Priority : 600
Format : EVM daemon: configuration failure on startup
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.daemon.event_activity
Explanation:
This high priority event is posted by the Event Manager (EVM)
daemon when it detects a high number of events occurring over
several minutes.
Action: Use the event viewer or the evmget(1) command to review the event log for the source of the activity. If the log does not show high activity around the time at which this event was posted, it is likely that the events were low priority, and hence were not logged. You can monitor low-priority events by running the evmwatch(1) command with an appropriate filter, or by temporarily reconfiguring the EVM logger to log low-priority events.
Note: You can change the parameters which control the posting of this event by modifying the daemon configuration file, /etc/evmdaemon.conf.
Template Dump:
Formatted Message:
EVM daemon: High event activity - exceeds 0 in 0 minutes
Event Data Items:
Event Name : sys.unix.evm.daemon.event_activity
Priority : 600
Format : EVM daemon: High event activity - exceeds $count in
$period minutes
Reference : cat:evmexp.cat:100
Variable Items:
count (INT32) = 0
period (INT32) = 0
To Index
*** EVENT sys.unix.evm.daemon.listening.inet
Explanation:
This event is posted by the Event Manager daemon during system
startup, to synchronize communication among daemons in a cluster
environment.
Template Dump:
Formatted Message:
EVM daemon: Node - (cluster member -) listening
Event Data Items:
Event Name : sys.unix.evm.daemon.listening.inet
Cluster Event : True
Priority : 100
Format : EVM daemon: Node @HOST_NAME (cluster member
@MEMBER_ID) listening
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.daemon.startup_completed
Explanation:
This informational event is posted by the Event Manager daemon when
it has completed its initialization procedures and is ready to
accept posted events.
Template Dump:
Formatted Message:
EVM daemon: Initialization completed
Event Data Items:
Event Name : sys.unix.evm.daemon.startup_completed
Priority : 200
Format : EVM daemon: Initialization completed
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.daemon.sync_failure
Explanation:
This event is posted by the Event Manager (EVM) daemon at startup
time if a synchronizing client fails to subscribe for events within
a reasonable time.
Synchronizing clients are configured through the daemon's configuration file, /etc/evmdaemon.conf, and are started automatically each time the daemon starts. Pre-configured synchronizing clients include the EVM logger and the EVM channel manager. Once started, a synchronizing client must issue an event subscription request before the daemon will accept posting requests from any other client. The daemon waits for up to 30 seconds for all synchronizing clients to issue their subscription requests.
This event is also posted if a synchronizing client cannot be started.
Action: The event contains details of the failing client. Use ps(1) to check whether the client is running, and look for any factors which may be preventing it from completing its initialization process.
Once the problem has been rectified the action depends on which client was failing, and whether it is still running. If the EVM logger or the channel manager fail, you can simply restart them in the background - since they handle the SIGHUP signal they will continue to run, even if you log off. For any other clients you may need to stop and restart EVM, or reboot the system.
Template Dump:
Formatted Message:
EVM daemon: Synchronizing client none failed to subscribe
Event Data Items:
Event Name : sys.unix.evm.daemon.sync_failure
Priority : 600
Format : EVM daemon: Synchronizing client $name failed to
subscribe
Reference : cat:evmexp.cat:100
Variable Items:
name (STRING) = "none"
command (STRING) = "none"
To Index
*** EVENT sys.unix.evm.evmstart
Explanation:
This event is posted by the evmstart(8) command as a means of
verifying that the Event Manager daemon has completed its
initialization procedures and is ready for events to be posted.
Template Dump:
Formatted Message:
EVM startup event
Event Data Items:
Event Name : sys.unix.evm.evmstart
Priority : 100
Format : EVM startup event
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.kevm
Explanation:
Events whose names begin with "sys.unix.evm.kevm" are posted by the
Event Manager kernel interface pseudo-driver, kevm.
Template Dump:
Formatted Message:
EVM Kernel interface base event
Event Data Items:
Event Name : sys.unix.evm.kevm
Priority : 200
Format : EVM Kernel interface base event
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.kevm.initialized
Explanation:
This event is posted by the Event Manager kernel interface
pseudo-driver, kevm, to indicate that the kernel interface is
available.
Template Dump:
Formatted Message:
EVM kernel interface: Initialization complete
Event Data Items:
Event Name : sys.unix.evm.kevm.initialized
Priority : 200
Format : EVM kernel interface: Initialization complete
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.kevm.lost_event
Explanation:
This event is posted by the Event manager (EVM) kernel interface
pseudo-driver, kevm, to indicate that it was unable to pass one or
more events from kernel-level to the EVM daemon. The reason for
this is most likely to be that the limit of the number of events
that may be queued in kernel space for transfer to user space was
exceeded.
Template Dump:
Formatted Message:
EVM kernel interface: Failed to deliver one or more kernel events
Event Data Items:
Event Name : sys.unix.evm.kevm.lost_event
Priority : 400
Format : EVM kernel interface: Failed to deliver one or more
kernel events
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.logger.config_err
Explanation:
This event is posted by the Event Manager's event logger when it
discovers a syntax error in its configuration file. This event
will only occur when the logger is restarted or has received a
reload request event or a SIGHUP signal.
Action: Check the file /var/evm/adm/logfiles/evmlogger.log for error output, and correct the configuration file. Run the command "evmreload -l" to reload the logger configuration.
Template Dump:
Formatted Message:
EVM logger: Logger configuration error - file
Event Data Items:
Event Name : sys.unix.evm.logger.config_err
Priority : 400
Format : EVM logger: Logger configuration error - file $filename
Reference : cat:evmexp.cat:100
Variable Items:
filename (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.connection.lost
Explanation:
This error event is posted by the event logger when it has lost a
connection to an Event Manager daemon running on a remote system.
The logger will continue to try to re-establish the connection at
the intervals specified for the host in the logger's
configuration. It will not receive any events that occur on the
remote host during the period of disconnection.
See the evmlogger.conf(4) reference page for details of remote host configuration.
Action: Verify the status of the remote system. If the system is active, try running evmwatch with the -h option to determine whether it is possible to make a connection to the system. Once the system is available, you can run evmreload to force the logger to retry the connection immediately.
Template Dump:
Formatted Message:
EVM logger: Lost connection to remote host ""
Event Data Items:
Event Name : sys.unix.evm.logger.connection.lost
Priority : 300
Format : EVM logger: Lost connection to remote host
"$remote_host"
Reference : cat:evmexp.cat:100
Variable Items:
remote_host (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.connection.made
Explanation:
This informational event is posted by the event logger when it has
successfully made a connection to an Event Manager daemon running
on a remote system, so that it can log events posted on that
system.
See the evmlogger.conf(4) reference page for details of remote host configuration.
Template Dump:
Formatted Message:
EVM logger: Established connection to remote host ""
Event Data Items:
Event Name : sys.unix.evm.logger.connection.made
Priority : 200
Format : EVM logger: Established connection to remote host
"$remote_host"
Reference : cat:evmexp.cat:100
Variable Items:
remote_host (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.connection.not_made
Explanation:
This error event is posted by the event logger when it has failed
to make a connection to an Event Manager daemon running on a remote
system. The logger will continue to try to make the connection at
the intervals specified for the host in the logger's
configuration.
See the evmlogger.conf(4) reference page for details of remote host configuration.
Action: Verify the status of the remote system. If the system is active, try running evmwatch with the -h option to determine whether it is possible to make a connection to the system. Once the system is available, you can run evmreload to force the logger to retry the connection immediately.
Template Dump:
Formatted Message:
EVM logger: Unable to establish connection to remote host ""
Event Data Items:
Event Name : sys.unix.evm.logger.connection.not_made
Priority : 300
Format : EVM logger: Unable to establish connection to remote
host "$remote_host"
Reference : cat:evmexp.cat:100
Variable Items:
remote_host (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.log_closed
Explanation:
This informational event is posted by the Event Manager's event
logger whenever an operational event log is closed. The event
contains the name of the log file and its size.
A dated log file is closed and a new one started when the first event is to be logged after the date has changed.
Template Dump:
Formatted Message:
EVM logger: Closed eventlog - size 0 bytes
Event Data Items:
Event Name : sys.unix.evm.logger.log_closed
Priority : 200
Format : EVM logger: Closed eventlog $logname - size $logsize
bytes
Reference : cat:evmexp.cat:100
Variable Items:
logname (STRING) = ""
logsize (INT32) = 0
To Index
*** EVENT sys.unix.evm.logger.log_start_err
Explanation:
This event is posted by the Event Manager's event logger when it
fails to start logging to a log file. If an alternate log file has
been specified, and is not already in use, the logger automatically
switches to the alternate file.
The logger writes failure information to its own log file, /var/evm/adm/logfiles/evmlogger.log.
Action: Check the log device for errors. Once you have rectified the problem use evmreload(8) to reconfigure the logger.
Template Dump:
Formatted Message:
EVM logger: Failed to start eventlog
Event Data Items:
Event Name : sys.unix.evm.logger.log_start_err
Priority : 400
Format : EVM logger: Failed to start eventlog $logname
Reference : cat:evmexp.cat:100
Variable Items:
logname (STRING) = ""
filter (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.log_started
Explanation:
This is an informational event, posted by the Event Manager's event
logger whenever a new event log is started. The event contains the
name of the log file and the filter string used to select events to
be stored in the log.
Template Dump:
Formatted Message:
EVM logger: Started eventlog
Event Data Items:
Event Name : sys.unix.evm.logger.log_started
Priority : 200
Format : EVM logger: Started eventlog $logname
Reference : cat:evmexp.cat:100
Variable Items:
logname (STRING) = ""
filter (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.log_write_err
Explanation:
This event is posted by the Event Manager's event logger when it
fails to write to a log file. If an alternate log file has been
specified, and is not currently in use, the logger automatically
switches to the alternate file.
Possible causes of a write failure include the disk being full, and a hardware failure. If the affected log is a terminal device, the device may be disconnected. The logger writes failure information to its own log file, /var/evm/adm/logfiles/evmlogger.log - but note that it may also have difficulty writing to this log if a failure has occurred on that disk.
Action: Once you have rectified the problem use evmreload(8) to reconfigure the logger. This will cause the logger to revert to its original log files.
Template Dump:
Formatted Message:
EVM logger: Failed to write to eventlog
Event Data Items:
Event Name : sys.unix.evm.logger.log_write_err
Priority : 400
Format : EVM logger: Failed to write to eventlog $logname
Reference : cat:evmexp.cat:100
Variable Items:
logname (STRING) = ""
filter (STRING) = ""
To Index
*** EVENT sys.unix.evm.logger.missed_event
Explanation:
This event is inserted into the event log stream by the event
logger when it is notified that the Event Manager daemon has been
unable to send to it one or more subscribed-for events.
This is most likely to occur during a heavy event load (or "event storm"), when the logger has been unable to handle incoming events as fast as they are being posted, causing overflow of the connection with the daemon. When this happens with any client, the daemon discards events that were intended for the client, but at the next opportunity notifies it of the number of events that have been lost.
Action: Check the event log to establish the reason for the high event activity.
Template Dump:
Formatted Message:
EVM logger: Missed receipt of 0 event(s)
Event Data Items:
Event Name : sys.unix.evm.logger.missed_event
Priority : 300
Format : EVM logger: Missed receipt of $count event(s)
Reference : cat:evmexp.cat:100
Variable Items:
count (INT32) = 0
To Index
*** EVENT sys.unix.evm.logger.started
Explanation:
This informational event is posted by the Event Manager's event
logger when the logger starts.
Template Dump:
Formatted Message:
EVM logger: Logger started
Event Data Items:
Event Name : sys.unix.evm.logger.started
Priority : 200
Format : EVM logger: Logger started
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.mark
Explanation:
Event Manager "mark" events are posted by the "evmlog" event
channel's "fn_monitor" function, to provide evidence in the event
log of times at which the system was operational. The frequency
with which mark events are posted depends upon the "mon_period"
setting for the evmlog channel.
Template Dump:
Formatted Message:
EVM: Mark event
Event Data Items:
Event Name : sys.unix.evm.mark
Priority : 200
Format : EVM: Mark event
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.mark.init
Explanation:
The "mark initialization" event is posted by the "evmlog" event
channel's monitor function when it is first run. This event
indicates the point at which the Event Manager began to post "mark"
events. The monitor function is run periodically thereafter to
post normal "mark" events.
Template Dump:
Formatted Message:
EVM: Mark event - initial
Event Data Items:
Event Name : sys.unix.evm.mark.init
Priority : 200
Format : EVM: Mark event - initial
Reference : cat:evmexp.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.evm.msg.admin
Explanation:
The administrator's "quick message" event is posted by evmpost(1)
when it is run with the "-a" option. The event is intended to be
used to add a message entry in the event log. Authorization to
post this event is restricted through the Event Manager's
authorization database.
The priority of the event can be specified by the administrator when the event is posted.
Template Dump:
Formatted Message:
EVM admin msg:
Event Data Items:
Event Name : sys.unix.evm.msg.admin
Priority : 200
Format : EVM admin msg: $message
Reference : cat:evmexp.cat:100
Variable Items:
message (STRING) = ""
To Index
*** EVENT sys.unix.evm.msg.user
Explanation:
The user's "quick message" event is posted by evmpost(1) when it is
run with the "-u" option. The event is intended to be used to add
a message entry in the event log.
The priority of the event can be specified by the user when the event is posted.
Template Dump:
Formatted Message:
EVM user msg (-):
Event Data Items:
Event Name : sys.unix.evm.msg.user
Priority : 200
Format : EVM user msg (@user_name): $message
Reference : cat:evmexp.cat:100
Variable Items:
message (STRING) = ""
To Index
*** EVENT sys.unix.fs
Explanation:
Events whose names begin with "sys.unix.fs" are posted by the
operating system's file system component, to report changes of
state.
Template Dump:
Formatted Message:
Filesystem event
Event Data Items:
Event Name : sys.unix.fs
Priority : 200
Format : Filesystem event
Reference : cat:evmexp.cat:400
Variable Items:
None
To Index
*** EVENT sys.unix.fs.advfs.advscan.recreate
Explanation:
This event is posted by the AdvFS file system to indicate that a
domain has been recreated by the advscan -r command. This command
uses the name of the devices found to exist within a domain to
build the name of a domain it is recreating.
See the advscan(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: domain recreated
Event Data Items:
Event Name : sys.unix.fs.advfs.advscan.recreate
Cluster Event : True
Priority : 200
Format : AdvFS: domain $domain recreated
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.addvol
Explanation:
This event is posted by the AdvFS file system to indicate that a
volume has been added to the specified AdvFS domain.
Template Dump:
Formatted Message:
AdvFS: Volume added to AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.addvol
Cluster Event : True
Priority : 200
Format : AdvFS: Volume $special added to AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.bad.mcell.list
Explanation:
This event is posted by the AdvFS file system to indicate that an
inconsistency has been detected in a BMT metadata file's mcell free
list. This inconsistency is not critical and AdvFS will attempt to
work around the problem but Compaq recommends that at the earliest
convenient time, all filesets in the domain be unmounted and the
/sbin/advfs/fixfdmn command be run on the domain to correct the
free mcell list. Failure to do so may cause AdvFS to use more
space in the affected volume for its BMT metadata than is
necessary. See the fixfdmn(8) man page for details about running
the fixfdmn command.
Template Dump:
Formatted Message:
AdvFS: Bad mcell list on volume in domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.bad.mcell.list
Cluster Event : True
Priority : 300
Format : AdvFS: Bad mcell list on volume $special in domain
$domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.bal.error
Explanation:
This event is posted by the balance(8) command to indicate that an
error has occurred while balancing the domain.
Action: Please refer to the balance(8) reference page for further information.
Template Dump:
Formatted Message:
AdvFS: Balance error on AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.bal.error
Cluster Event : True
Priority : 400
Format : AdvFS: Balance error on AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.bal.lock
Explanation:
This event is posted by the AdvFS file system to indicate that the
balance operation has been started on the specified AdvFS domain.
This operation balances the percentage of used space among volumes
in an AdvFS domain.
Template Dump:
Formatted Message:
AdvFS: Balance started on AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.bal.lock
Cluster Event : True
Priority : 200
Format : AdvFS: Balance started on AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.bal.unlock
Explanation:
This event is posted by the AdvFS file system to indicate that the
balance operation has completed on the specified AdvFS domain.
This operation balances the percentage of used space among volumes
in an AdvFS domain.
Template Dump:
Formatted Message:
AdvFS: Balance completed on AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.bal.unlock
Cluster Event : True
Priority : 200
Format : AdvFS: Balance completed on AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.ccbt.ignored
Explanation:
This event is posted by the AdvFS file system to indicate that the
root file system has been mounted despite an on-disk flag
indicating a corruption in an SBM metadata file. The domain was
mounted despite the error to provide the user a means of booting
until the problem is corrected.
Action: Refer to the AdvFS Administration Guide section: "Trouble Shooting: Can't Clear Bit Twice Error Message" for general instructions and details. Because the domain has already been mounted, the setting and unsetting of the flag AdvfsFixUpSBM described in the Administration Guide is unnecessary. Compaq suggests booting the system from the installation CD or from another bootable disk, then following the instructions provided in the AdvFS Administration Guide.
Template Dump:
Formatted Message:
AdvFS: Domain was mounted despite AdvFS finding an on-disk flag
indicating corruption of an SBM metadata file
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.ccbt.ignored
Cluster Event : True
Priority : 200
Format : AdvFS: Domain $domain was mounted despite AdvFS
finding an on-disk flag indicating corruption of an
SBM metadata file
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.frag.error
Explanation:
This event is posted by the defragment(8) command to indicate that
an error has occurred while defragmenting the domain.
Action: Please refer to the defragment(8) reference page for further information.
Template Dump:
Formatted Message:
AdvFS: Defragment error on AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.frag.error
Cluster Event : True
Priority : 400
Format : AdvFS: Defragment error on AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.frag.lock
Explanation:
This event is posted by the AdvFS file system to indicate that the
defragment operation has been started on the specified AdvFS
domain. This operation makes the files in an AdvFS domain more
contiguous.
Template Dump:
Formatted Message:
AdvFS: Defragment started on AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.frag.lock
Cluster Event : True
Priority : 200
Format : AdvFS: Defragment started on AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.frag.unlock
Explanation:
This event is posted by the AdvFS file system to indicate that the
defragment operation has completed on the specified AdvFS domain.
This operation makes the files in an AdvFS domain more contiguous.
Template Dump:
Formatted Message:
AdvFS: Defragment completed on AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.frag.unlock
Cluster Event : True
Priority : 200
Format : AdvFS: Defragment completed on AdvFS domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.full
Explanation:
This event is posted by the AdvFS file system to provide
notification that the specified AdvFS domain is full. No more
space is available for writing.
Template Dump:
Formatted Message:
AdvFS: AdvFS domain is full
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.full
Cluster Event : True
Priority : 600
Format : AdvFS: AdvFS domain $domain is full
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.mk
Explanation:
This event is posted by the AdvFS file system when an AdvFS domain
has been created on the specified volume.
Template Dump:
Formatted Message:
AdvFS: Domain created on volume
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.mk
Cluster Event : True
Priority : 200
Format : AdvFS: Domain $domain created on volume $special
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.panic
Explanation:
This event is posted by the AdvFS file system to indicate that an
AdvFS domain panic has occurred on the specified domain. This is
due to either a metadata write error or an internal inconsistency.
The domain is being rendered inaccessible.
Action: Please refer to the guidelines in the AdvFS Guide to File System Administration for the steps to recover this domain.
Template Dump:
Formatted Message:
AdvFS: An AdvFS domain panic has occurred on
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.panic
Cluster Event : True
Priority : 600
Format : AdvFS: An AdvFS domain panic has occurred on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.rm
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS domain has been removed.
Template Dump:
Formatted Message:
AdvFS: Domain removed
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.rm
Cluster Event : True
Priority : 200
Format : AdvFS: Domain $domain removed
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.rmvol.error
Explanation:
This event is posted by the rmvol(8) command to indicate that an
error has occurred while removing a volume from the domain.
Action: Please refer to the rmvol(8) reference page for further information.
Template Dump:
Formatted Message:
AdvFS: Error on removal of volume from AdvFS domain
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.rmvol.error
Cluster Event : True
Priority : 400
Format : AdvFS: Error on removal of volume $special from AdvFS
domain $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.rmvol.lock
Explanation:
This event is posted by the AdvFS file system to indicate that an
rmvol operation has been started on the specified AdvFS domain.
This operation removes the specified volume from the specified
AdvFS domain.
Template Dump:
Formatted Message:
AdvFS: Removal of volume from AdvFS domain started
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.rmvol.lock
Cluster Event : True
Priority : 200
Format : AdvFS: Removal of volume $special from AdvFS domain
$domain started
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.rmvol.unlock
Explanation:
This event is posted by the AdvFS file system to indicate that an
rmvol operation has completed on the specified AdvFS domain. This
operation removes the specified volume from the specified domain.
Template Dump:
Formatted Message:
AdvFS: Removal of volume from AdvFS domain completed
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.rmvol.unlock
Cluster Event : True
Priority : 200
Format : AdvFS: Removal of volume $special from AdvFS domain
$domain completed
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fdmn.vd.extend
Explanation:
This event is posted by the AdvFS file system to indicate that
the size of a volume has been extended in the specified AdvFS
domain.
Template Dump:
Formatted Message:
AdvFS: Volume in AdvFS domain has been extended
Event Data Items:
Event Name : sys.unix.fs.advfs.fdmn.vd.extend
Cluster Event : True
Priority : 200
Format : AdvFS: Volume $special in AdvFS domain $domain has
been extended
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
special (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.backup.error
Explanation:
This event is posted by the AdvFS backup/restore utilities to
indicate that an error has occurred during a backup operation on
the domain.
Action: Please refer to the reference pages for the specific operation (vdump(8), vrestore(8), or verify(8)).
Template Dump:
Formatted Message:
AdvFS: Backup error on AdvFS #
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.backup.error
Cluster Event : True
Priority : 400
Format : AdvFS: Backup error on AdvFS $domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.backup.lock
Explanation:
This event is posted by the AdvFS file system to indicate that a
backup or similar exhaustive operation (vdump, vrestore, or verify)
has started on the specified AdvFS fileset.
Template Dump:
Formatted Message:
AdvFS: Backup operation on AdvFS # started
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.backup.lock
Cluster Event : True
Priority : 200
Format : AdvFS: Backup operation on AdvFS $domain#$fileset
started
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.backup.unlock
Explanation:
This event is posted by the AdvFS file system to indicate that a
backup or similar exhaustive operation (vdump, vrestore, or verify)
has completed on the specified AdvFS fileset.
Template Dump:
Formatted Message:
AdvFS: Backup operation on AdvFS # completed
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.backup.unlock
Cluster Event : True
Priority : 200
Format : AdvFS: Backup operation on AdvFS $domain#$fileset
completed
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.bad.frag
Explanation:
This event is posted by the AdvFS file system to indicate that an
inconsistency has been detected in a frag file free list. The frag
file is a metadata file that AdvFS uses to reduce file system
fragmentation. AdvFS will attempt to work around the problem but
Compaq recommends that at the earliest convenient time, all
filesets in the domain be unmounted and the /sbin/advfs/verify
command be run on the domain to check the integrity of the domain's
metadata.
Template Dump:
Formatted Message:
AdvFS: Bad frag free list detected in #
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.bad.frag
Cluster Event : True
Priority : 200
Format : AdvFS: Bad frag free list detected in $domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.clone
Explanation:
This event is posted by the AdvFS file system to indicate that a
clone of the given AdvFS fileset has been created.
Template Dump:
Formatted Message:
AdvFS: Clone created for AdvFS fileset #
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.clone
Cluster Event : True
Priority : 200
Format : AdvFS: Clone $clonefset created for AdvFS fileset
$domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
clonefset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.inconsistent_dir_entry
Explanation:
This event is posted by the AdvFS filesystem to indicate an
inconsistency in a directory entry. This inconsistency is not
critical and AdvFS can avoid problems but some user file(s) will be
unavailable.
Action: Please unmount all filesets in this domain and run /sbin/advfs/fixfdmn to correct this problem at your convenience. Failure to do so will leavefile(s) inaccessible.
Template Dump:
Formatted Message:
AdvFS: Inconsistent dir entry in #, in dir tag 0 on page 0 at offset 0
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.inconsistent_dir_entry
Cluster Event : True
Priority : 500
Format : AdvFS: Inconsistent dir entry in $domain#$fileset, in
dir tag $dirtag on page $dirPgNm at offset $pgOffset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
dirtag (INT64) = 0
dirPgNm (INT64) = 0
pgOffset (INT64) = 0
To Index
*** EVENT sys.unix.fs.advfs.fset.mk
Explanation:
This event is posted by the AdvFS file system to indicate that a
fileset has been created in the specified AdvFS domain.
Template Dump:
Formatted Message:
AdvFS: AdvFS fileset # created
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.mk
Cluster Event : True
Priority : 200
Format : AdvFS: AdvFS fileset $domain#$fileset created
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.mount
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS fileset has been mounted on the named directory.
Template Dump:
Formatted Message:
AdvFS: AdvFS fileset # mounted on
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.mount
Cluster Event : True
Priority : 200
Format : AdvFS: AdvFS fileset $domain#$fileset mounted on
$directory
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.options
Explanation:
This event is posted by the AdvFS file system to indicate that one
or more options have been set for the specified fileset.
Template Dump:
Formatted Message:
AdvFS: Fileset options for # are now
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.options
Cluster Event : True
Priority : 200
Format : AdvFS: Fileset options for $domain#$fileset are now
$options
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
options (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.quota.hblk.limit
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS domain has changed the block usage hard limit
(quota) in 1K blocks of the fileset.
Template Dump:
Formatted Message:
AdvFS: Block (1k) usage hard limit (quota) for # is now 0
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.quota.hblk.limit
Cluster Event : True
Priority : 200
Format : AdvFS: Block (1k) usage hard limit (quota) for
$domain#$fileset is now $blkHLimit
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
blkHLimit (INT64) = 0
To Index
*** EVENT sys.unix.fs.advfs.fset.quota.hfile.limit
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS domain has changed the file usage hard limit
(quota) of the fileset.
Template Dump:
Formatted Message:
AdvFS: File usage hard limit (quota) for # is now 0
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.quota.hfile.limit
Cluster Event : True
Priority : 200
Format : AdvFS: File usage hard limit (quota) for
$domain#$fileset is now $fileHLimit
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
fileHLimit (INT64) = 0
To Index
*** EVENT sys.unix.fs.advfs.fset.quota.sblk.limit
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS domain has changed the block usage soft limit
(quota) in 1K blocks of the fileset.
Template Dump:
Formatted Message:
AdvFS: Block (1k) usage soft limit (quota) for # is now 0
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.quota.sblk.limit
Cluster Event : True
Priority : 200
Format : AdvFS: Block (1k) usage soft limit (quota) for
$domain#$fileset is now $blkSLimit
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
blkSLimit (INT64) = 0
To Index
*** EVENT sys.unix.fs.advfs.fset.quota.sfile.limit
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS domain has changed the file usage soft limit
(quota) of the fileset.
Template Dump:
Formatted Message:
AdvFS: File usage soft limit (quota) for # is now 0
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.quota.sfile.limit
Cluster Event : True
Priority : 200
Format : AdvFS: File usage soft limit (quota) for
$domain#$fileset is now $fileSLimit
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
fileSLimit (INT64) = 0
To Index
*** EVENT sys.unix.fs.advfs.fset.rename
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS fileset has been renamed.
Template Dump:
Formatted Message:
AdvFS: AdvFS fileset # renamed to #
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.rename
Cluster Event : True
Priority : 200
Format : AdvFS: AdvFS fileset $domain#$fileset renamed to
$domain#$renamefset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
renamefset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.rm.error
Explanation:
This event is posted by the rmfset(8) command to indicate that an
error has occurred while removing a fileset.
Action: Please refer to the rmfset(8) reference page for further information.
Template Dump:
Formatted Message:
AdvFS: Error on removal of AdvFS fileset #
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.rm.error
Cluster Event : True
Priority : 400
Format : AdvFS: Error on removal of AdvFS fileset
$domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.rm.lock
Explanation:
This event is posted by the AdvFS file system to indicate that the
removal of the specified AdvFS fileset has been started.
Template Dump:
Formatted Message:
AdvFS: Removal of AdvFS fileset # started
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.rm.lock
Cluster Event : True
Priority : 200
Format : AdvFS: Removal of AdvFS fileset $domain#$fileset
started
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.rm.unlock
Explanation:
This event is posted by the AdvFS file system to indicate that the
removal of the specified AdvFS fileset has completed.
Template Dump:
Formatted Message:
AdvFS: Removal of AdvFS fileset # completed
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.rm.unlock
Cluster Event : True
Priority : 200
Format : AdvFS: Removal of AdvFS fileset $domain#$fileset
completed
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.fset.umount
Explanation:
This event is posted by the AdvFS file system to indicate that the
specified AdvFS fileset has been unmounted from the named
directory.
Template Dump:
Formatted Message:
AdvFS: AdvFS fileset # unmounted from
Event Data Items:
Event Name : sys.unix.fs.advfs.fset.umount
Cluster Event : True
Priority : 200
Format : AdvFS: AdvFS fileset $domain#$fileset unmounted from
$directory
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.quota.off
Explanation:
This event is posted by the AdvFS file system to indicate that
quotas have been turned off for the specified AdvFS fileset.
Template Dump:
Formatted Message:
AdvFS: Quotas turned off for AdvFS fileset #
Event Data Items:
Event Name : sys.unix.fs.advfs.quota.off
Cluster Event : True
Priority : 200
Format : AdvFS: Quotas turned off for AdvFS fileset
$domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.quota.on
Explanation:
This event is posted by the AdvFS file system to indicate that
quotas have been turned on for the specified AdvFS fileset.
Template Dump:
Formatted Message:
AdvFS: Quotas turned on for AdvFS fileset #
Event Data Items:
Event Name : sys.unix.fs.advfs.quota.on
Cluster Event : True
Priority : 200
Format : AdvFS: Quotas turned on for AdvFS fileset
$domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.quota.setgrp
Explanation:
This event is posted by the AdvFS file system to indicate that
quotas have been set for the specified group on the specified AdvFS
fileset.
Template Dump:
Formatted Message:
AdvFS: Group quotas set for on AdvFS fileset #
Event Data Items:
Event Name : sys.unix.fs.advfs.quota.setgrp
Cluster Event : True
Priority : 200
Format : AdvFS: Group quotas set for $group on AdvFS fileset
$domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
group (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.quota.setusr
Explanation:
This event is posted by the AdvFS file system to indicate that
quotas have been set for the specified user on the specified AdvFS
fileset.
Template Dump:
Formatted Message:
AdvFS: User quotas set for on AdvFS fileset #
Event Data Items:
Event Name : sys.unix.fs.advfs.quota.setusr
Cluster Event : True
Priority : 200
Format : AdvFS: User quotas set for $user on AdvFS fileset
$domain#$fileset
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
fileset (STRING) = ""
user (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.special.maxacc
Explanation:
This event is posted by the AdvFS file system to indicate that
AdvFS cannot allocate any more access structures because the memory
limit for access structures specified by AdvfsAccessMaxPercent has
been reached. Access structures are the in-memory structures that
AdvFS uses to represent open files. When AdvFS cannot allocate
more access structures, it cannot open any more files.
Action: Either close some files or reconfigure the AdvfsAccessMaxPercent kernel parameter to a higher value than it currently has. This may be done without rebooting the system.
Template Dump:
Formatted Message:
AdvFS: Cannot open any more files. AdvfsAccessMaxPercent limit reached.
Event Data Items:
Event Name : sys.unix.fs.advfs.special.maxacc
Cluster Event : True
Priority : 500
Format : AdvFS: Cannot open any more files.
AdvfsAccessMaxPercent limit reached.
Reference : cat:evmexp.cat:450
Variable Items:
None
To Index
*** EVENT sys.unix.fs.advfs.ss.activated
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast has been activated on an AdvFS domain. The vfast maintenance
tool automates certain maintenance tasks such as file
defragmentation and balancing, and migration of user files to
eliminate device I/O bottlenecks. The primary goal of vfast is to
provide administrators with a file system that requires no
maintenance beyond adding and subtracting storage. Activation of
vfast is controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast activated on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.activated
Cluster Event : True
Priority : 200
Format : AdvFS: vfast activated on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.bal.disabled
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast balance is disabled on an AdvFS domain. The vfast tool
performs automatic free space balancing over volumes. This is
important for new file creation, as it allows new files to be
distributed evenly over the drives as they are created, usually
resulting in improved performance. Disabling of vfast balance is
controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast balance disabled on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.bal.disabled
Cluster Event : True
Priority : 200
Format : AdvFS: vfast balance disabled on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.bal.enabled
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast balance is enabled on an AdvFS domain. The vfast tool
performs automatic free space balancing over volumes. This is
important for new file creation, as it allows new files to be
distributed evenly over the drives as they are created, usually
resulting in improved performance. Enabling of vfast balance is
controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast balance enabled on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.bal.enabled
Cluster Event : True
Priority : 200
Format : AdvFS: vfast balance enabled on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.deactivated
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast has been deactivated on an AdvFS domain. The vfast
maintenance tool automates certain maintenance tasks such as file
defragmentation and balancing, and migration of user files to
eliminate device I/O bottlenecks. The primary goal of vfast is to
provide administrators with a file system that requires no
maintenance beyond adding and subtracting storage. Deactivation of
vfast is controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast deactivated on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.deactivated
Cluster Event : True
Priority : 200
Format : AdvFS: vfast deactivated on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.defrag.disabled
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast defragment is disabled on an AdvFS domain. The vfast tool
attempts to reduce the number of file extents in a file domain by
making files more contiguous. Vfast also attempts to make the free
space on a disk more contiguous, resulting in less fragmented file
allocations in the future. If vfast defragment, balance or
topIObalance are enabled, and if vfast is activated, the
/usr/sbin/defragment utility will not be allowed to run. Disabling
of vfast defragment is controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast defragment disabled on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.defrag.disabled
Cluster Event : True
Priority : 200
Format : AdvFS: vfast defragment disabled on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.defrag.enabled
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast defragment is enabled on an AdvFS domain. The vfast tool
attempts to reduce the number of file extents in a file domain by
making files more contiguous. Vfast also attempts to make the free
space on a disk more contiguous, resulting in fewer fragmented file
allocations in the future. If vfast defragment, balance or
topIObalance are enabled, and if vfast is activated, the
/usr/sbin/defragment utility will not be allowed to run. Enabling
of vfast defragment is controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast defragment enabled on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.defrag.enabled
Cluster Event : True
Priority : 200
Format : AdvFS: vfast defragment enabled on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.suspended
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast has been suspended on an AdvFS domain. The vfast maintenance
tool automates certain maintenance tasks such as file
defragmentation and balancing, and migration of user files to
eliminate device I/O bottlenecks. The primary goal of vfast is to
provide administrators with a file system that requires no
maintenance beyond adding and subtracting storage. Suspension of
vfast is controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast suspended on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.suspended
Cluster Event : True
Priority : 200
Format : AdvFS: vfast suspended on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.topiobal.disabled
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast top IO balance is disabled on an AdvFS domain. The vfast
tool automatically distributes disk I/O across the available disks,
helping to prevent a single disk from becoming an I/O bottleneck
and thus increasing performance. Disabling of vfast top IO balance
is controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast top IO balance disabled on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.topiobal.disabled
Cluster Event : True
Priority : 200
Format : AdvFS: vfast top IO balance disabled on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.advfs.ss.topiobal.enabled
Explanation:
This event is posted by the AdvFS file system to indicate that
vfast top IO balance is enabled on an AdvFS domain. The vfast tool
automatically distributes disk I/O across the available disks, to
prevent a single disk from becoming an I/O bottleneck and thus
increases performance. Enabling of vfast top IO balance is
controlled with command line options.
See the vfast(8) reference page for more information.
Template Dump:
Formatted Message:
AdvFS: vfast top IO balance enabled on
Event Data Items:
Event Name : sys.unix.fs.advfs.ss.topiobal.enabled
Cluster Event : True
Priority : 200
Format : AdvFS: vfast top IO balance enabled on $domain
Reference : cat:evmexp.cat:450
Variable Items:
domain (STRING) = ""
To Index
*** EVENT sys.unix.fs.cdfs.mount
Explanation:
This informational event is posted by the file system when a CDFS
file system is mounted.
Template Dump:
Formatted Message:
CDFS: CDFS filesystem mounted on
Event Data Items:
Event Name : sys.unix.fs.cdfs.mount
Cluster Event : True
Priority : 200
Format : CDFS: CDFS filesystem $filesystem mounted on $directory
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.cdfs.umount
Explanation:
This informational event is posted by the file system when a CDFS
file system is unmounted.
Template Dump:
Formatted Message:
CDFS: CDFS filesystem unmounted from
Event Data Items:
Event Name : sys.unix.fs.cdfs.umount
Cluster Event : True
Priority : 200
Format : CDFS: CDFS filesystem $filesystem unmounted from
$directory
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.disklabel
Explanation:
This event is posted by the operating system's file system
component to indicate that a new label has been created for a disk
device.
Template Dump:
Formatted Message:
Device "$device" has been labeled
Event Data Items:
Event Name : sys.unix.fs.disklabel
Priority : 200
Format : Device "$device" has been labeled
Reference : cat:evmexp.cat:400
Variable Items:
None
To Index
*** EVENT sys.unix.fs.newfs
Explanation:
This event is posted by the operating system's file system
component to indicate that a new UFS file system has been
established on the device identified in the event.
Template Dump:
Formatted Message:
A UFS file system has been created on partition "$partition" of device
"$device"
Event Data Items:
Event Name : sys.unix.fs.newfs
Priority : 200
Format : A UFS file system has been created on partition
"$partition" of device "$device"
Reference : cat:evmexp.cat:400
Variable Items:
None
To Index
*** EVENT sys.unix.fs.nfs.mount
Explanation:
This informational event is posted by the file system when an NFS
file system is mounted.
Template Dump:
Formatted Message:
NFS: NFS filesystem mounted on
Event Data Items:
Event Name : sys.unix.fs.nfs.mount
Cluster Event : True
Priority : 100
Format : NFS: NFS filesystem $filesystem mounted on $directory
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.nfs.umount
Explanation:
This informational event is posted by the file system when an NFS
file system is unmounted.
Template Dump:
Formatted Message:
NFS: NFS filesystem unmounted from
Event Data Items:
Event Name : sys.unix.fs.nfs.umount
Cluster Event : True
Priority : 100
Format : NFS: NFS filesystem $filesystem unmounted from
$directory
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.ufs.mount
Explanation:
This informational event is posted by the file system when a UFS
file system is mounted.
Template Dump:
Formatted Message:
UFS: UFS filesystem mounted on
Event Data Items:
Event Name : sys.unix.fs.ufs.mount
Cluster Event : True
Priority : 200
Format : UFS: UFS filesystem $filesystem mounted on $directory
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.ufs.umount
Explanation:
This informational event is posted by the file system when a UFS
file system is unmounted.
Template Dump:
Formatted Message:
UFS: UFS filesystem unmounted from
Event Data Items:
Event Name : sys.unix.fs.ufs.umount
Cluster Event : True
Priority : 200
Format : UFS: UFS filesystem $filesystem unmounted from
$directory
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.vfs.freeze
Explanation:
This informational event is posted when a file system is frozen.
Freezing a file system places it into a metadata stable state. Once
frozen, any operations on the file system that attempt to modify
metadata will block until the file system is thawed. This feature
is primarily used for hardware based snapshots and clones.
Template Dump:
Formatted Message:
VFS: filesystem mounted on was frozen
Event Data Items:
Event Name : sys.unix.fs.vfs.freeze
Cluster Event : True
Priority : 200
Format : VFS: filesystem $filesystem mounted on $directory was
frozen
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.vfs.thaw
Explanation:
This informational event is posted when a file system is thawed.
The file system was previously frozen in order to place it into a
metadata stable state. Thawing a file system resumes normal
activity.
Template Dump:
Formatted Message:
VFS: filesystem mounted on was thawed
Event Data Items:
Event Name : sys.unix.fs.vfs.thaw
Cluster Event : True
Priority : 200
Format : VFS: filesystem $filesystem mounted on $directory was
thawed
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.vfs.thaw.failure
Explanation:
This informational event is posted when a file system is thawed
automatically due to a node failure in a cluster. The file system
was previously frozen, but had to be automatically thawed since
processing a cluster node failure could possibly result in changes
to file system metadata. Thawing a file system resumes normal
activity.
Template Dump:
Formatted Message:
VFS: filesystem mounted on was thawed due to a node failure
Event Data Items:
Event Name : sys.unix.fs.vfs.thaw.failure
Cluster Event : True
Priority : 200
Format : VFS: filesystem $filesystem mounted on $directory was
thawed due to a node failure
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.vfs.thaw.shutdown
Explanation:
This informational event is posted when a file system is thawed
automatically due to the shutdown of a cluster node. The file
system was previously frozen, but had to be automatically thawed
since processing a cluster node shutdown could possibly result in
changes to file system metadata. Thawing a file system resumes
normal activity.
Template Dump:
Formatted Message:
VFS: filesystem mounted on was thawed due to a node shutdown
Event Data Items:
Event Name : sys.unix.fs.vfs.thaw.shutdown
Cluster Event : True
Priority : 200
Format : VFS: filesystem $filesystem mounted on $directory was
thawed due to a node shutdown
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.fs.vfs.thaw.timeout
Explanation:
This informational event is posted when a file system is thawed due
to the timeout limit being exceeded. The file system was
previously frozen, but the timeout period has been exceeded,
causing an automatic thaw. Thawing a file system resumes normal
activity.
Template Dump:
Formatted Message:
VFS: filesystem mounted on was thawed due to timeout
Event Data Items:
Event Name : sys.unix.fs.vfs.thaw.timeout
Cluster Event : True
Priority : 200
Format : VFS: filesystem $filesystem mounted on $directory was
thawed due to timeout
Reference : cat:evmexp.cat
Variable Items:
filesystem (STRING) = ""
directory (STRING) = ""
To Index
*** EVENT sys.unix.hw
Explanation:
Events whose names begin with "sys.unix.hw" are posted by hardware
support components.
Template Dump:
Formatted Message:
Base hardware event
Event Data Items:
Event Name : sys.unix.hw
Cluster Event : True
Priority : 200
Format : Base hardware event
Reference : cat:evmexp.cat:800
Variable Items:
None
To Index
*** EVENT sys.unix.hw.capacity_changed
Explanation:
The capacity_changed event is generated when the disk driver
notices that the capacity of the device has changed. We currently
support only increases in capacity. A decrease in capacity is
treated as an error. This policy may change in the future.
The previous and current values in this event contain information about the capacity change.
Template Dump:
Formatted Message:
Capacity of device has changed (HWID=0 lid=0 )
Event Data Items:
Event Name : sys.unix.hw.capacity_changed._hwid.0
Cluster Event : True
Priority : 200
Format : Capacity of device has changed (HWID=$_hwid lid=$lid )
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
lid (UINT32) = 0
previous (UINT32) = 0
current (UINT32) = 0
To Index
*** EVENT sys.unix.hw.cluster_attribute_change
Explanation:
This informational event is posted by the hardware support
subsystem when it detects that a SCSI device has had a change in
its cluster attributes.
Template Dump:
Formatted Message:
A change has occurred in a cluster attribute for device (HWID=0 lid=0)
Event Data Items:
Event Name : sys.unix.hw.cluster_attribute_change._hwid.0
Cluster Event : True
Priority : 200
Format : A change has occurred in a cluster attribute for
device (HWID=$_hwid lid=$lid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
lid (UINT32) = 0
To Index
*** EVENT sys.unix.hw.connections_increased
Explanation:
This informational event is posted by the hardware support
subsystem to indicate that a new connection path has been added to
the device identified in the event.
Template Dump:
Formatted Message:
Connectivity has increased for device (HWID=0 lid=0 btl=0/0/0)
Event Data Items:
Event Name : sys.unix.hw.connections_increased._hwid.0
Cluster Event : True
Priority : 300
Format : Connectivity has increased for device (HWID=$_hwid
lid=$lid btl=$port_id/$target_id/$lun_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
arch (STRING) = "none"
lid (UINT32) = 0
port_id (UINT32) = 0
target_id (UINT64) = 0
lun_id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.connections_reduced
Explanation:
This informational event is posted by the hardware support
subsystem to indicate that the number of paths available to the
device identified in the event has been reduced by one. Other
paths to the device remain viable.
Template Dump:
Formatted Message:
Connectivity has been reduced (but not lost) to device (HWID=0 lid=0
btl=0/0/0)
Event Data Items:
Event Name : sys.unix.hw.connections_reduced._hwid.0
Cluster Event : True
Priority : 400
Format : Connectivity has been reduced (but not lost) to device
(HWID=$_hwid lid=$lid btl=$port_id/$target_id/$lun_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
arch (STRING) = "none"
lid (UINT32) = 0
port_id (UINT32) = 0
target_id (UINT64) = 0
lun_id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.deregistered
Explanation:
This informational event is posted by the hardware support
subsystem to indicate that a hardware component has been removed
from the system. The component is no longer registered in the
system hardware configuration manager's database, and the component
is no longer available for use.
Template Dump:
Formatted Message:
A hardware component has been de-registered (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.deregistered._hwid.0
Cluster Event : True
Priority : 400
Format : A hardware component has been de-registered
(HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.dev_base_name_changed
Explanation:
This event is posted by the hardware support subsystem to indicate
that the base name of the device has changed.
Template Dump:
Formatted Message:
Device base name changed from "unknown" to "unknown" (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.dev_base_name_changed._hwid.0
Cluster Event : True
Priority : 300
Format : Device base name changed from "$old_name" to
"$new_name" (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
old_name (STRING) = "unknown"
new_name (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.environmental.fault.current
Explanation:
This is a system environmental "alert" event. It is posted when a
current sensor is above a critical threshold. Immediate attention
is necessary.
Template Dump:
Formatted Message:
Environmental Current Fault: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.fault.current._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Current Fault: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.fault.fan
Explanation:
This is a system environmental "alert" event. It is posted when a
fan sensor is above a critical threshold. Immediate attention may
be necessary.
Template Dump:
Formatted Message:
Environmental Fan Fault: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.fault.fan._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Fan Fault: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.fault.power
Explanation:
This is a system environmental "alert" event. It is posted when a
power sensor is above a critical threshold. Immediate attention is
necessary.
Template Dump:
Formatted Message:
Environmental Power Fault: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.fault.power._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Power Fault: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.fault.thermal
Explanation:
This is a system environmental "alert" event. It is posted when a
thermal sensor is above a critical threshold. Immediate attention
is necessary.
Template Dump:
Formatted Message:
Environmental Thermal Fault: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.fault.thermal._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Thermal Fault: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.ok.current
Explanation:
This is a system environmental "notice" event. It is posted when a
current sensor returns to operating within a normal range.
Template Dump:
Formatted Message:
Environmental Current OK: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.ok.current._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Current OK: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.ok.fan
Explanation:
This is a system environmental "notice" event. It is posted when a
fan sensor returns to operating within a normal range
Template Dump:
Formatted Message:
Environmental Fan OK: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.ok.fan._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Fan OK: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.ok.power
Explanation:
This is a system environmental "notice" event. It is posted when a
power sensor returns to operating within a normal range.
Template Dump:
Formatted Message:
Environmental Power OK: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.ok.power._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Power OK: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.ok.thermal
Explanation:
This is a system environmental "notice" event. It is posted when a
thermal sensor returns to operating within a normal range.
Template Dump:
Formatted Message:
Environmental Thermal OK: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.ok.thermal._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Thermal OK: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.warning.current
Explanation:
This is a system environmental "alert" event. It is posted when a
current sensor is above a warning threshold but below a critical
threshold.
Template Dump:
Formatted Message:
Environmental Current Warning: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.warning.current._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Current Warning: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.warning.fan
Explanation:
This is a system environmental "alert" event. It is posted when a
fan sensor is above a warning threshold but below a critical
threshold.
Template Dump:
Formatted Message:
Environmental Fan Warning: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.warning.fan._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Fan Warning: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.warning.power
Explanation:
This is a system environmental "alert" event. It is posted when a
power sensor is above a warning threshold but below a critical
threshold.
Template Dump:
Formatted Message:
Environmental Power Warning: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.warning.power._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Power Warning: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.environmental.warning.thermal
Explanation:
This is a system environmental "alert" event. It is posted when a
thermal sensor is above a warning threshold but below a critical
threshold.
Template Dump:
Formatted Message:
Environmental Thermal Warning: HWID=0
Event Data Items:
Event Name : sys.unix.hw.environmental.warning.thermal._hwid.0
Cluster Event : True
Priority : 600
Format : Environmental Thermal Warning: HWID=$_hwid
Reference : cat:evmexp.cat:840
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.link_down.network
Explanation:
This is a LAN driver "notice" event, posted after a network adapter
has detected that the link signal is missing. Usually it indicates
that the network cable been unplugged.
Note that due to the nature of Ethernet, any network adapter will occasionally toggle link down/up with no actual loss of connectivity.
Template Dump:
Formatted Message:
Network adapter (HWID=0) is disconnected
Event Data Items:
Event Name : sys.unix.hw.link_down.network._hwid.0
Cluster Event : True
Priority : 200
Format : Network adapter $_hwcomponent (HWID=$_hwid) is
disconnected
Reference : cat:evmexp.cat:830
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.link_up.network
Explanation:
This is a LAN driver "notice" event, posted after a network adapter
has detected the link signal. Usually it indicates that the
network cable has just been plugged in.
Template Dump:
Formatted Message:
Network adapter (HWID=0) is connected
Event Data Items:
Event Name : sys.unix.hw.link_up.network._hwid.0
Cluster Event : True
Priority : 200
Format : Network adapter $_hwcomponent (HWID=$_hwid) is
connected
Reference : cat:evmexp.cat:830
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.media_changed
Explanation:
This informational event is posted by the hardware support
subsystem to indicate that a Unit Attention signal has has been
detected on the device identified in the event. This signal
indicates either that the media has been changed or that the device
has been reset.
Template Dump:
Formatted Message:
Media may have been changed or device was reset (HWID=0 lid=0 btl=0/0/0)
Event Data Items:
Event Name : sys.unix.hw.media_changed._hwid.0
Cluster Event : True
Priority : 300
Format : Media may have been changed or device was reset
(HWID=$_hwid lid=$lid btl=$port_id/$target_id/$lun_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
arch (STRING) = "none"
lid (UINT32) = 0
port_id (UINT32) = 0
target_id (UINT64) = 0
lun_id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.net.netrain.alert
Explanation:
This is a NetRAIN internal "notice" event, posted after the Network
Interface Failure Finder (NIFF) has detected a lack of connectivity
to a network interface.
Template Dump:
Formatted Message:
NetRAIN: node - has declared a connectivity alert with network via
interface
Event Data Items:
Event Name : sys.unix.hw.net.netrain.alert
Cluster Event : False
Priority : 0
Format : NetRAIN: node @host_name has declared a connectivity
alert with network $network via interface $interface
Reference : cat:evmexp.cat:820
Variable Items:
network (STRING) = ""
interface (STRING) = ""
ipaddress (STRING) = ""
ipmask (STRING) = ""
alert_type (INT32) = 0
interval (INT32) = 0
To Index
*** EVENT sys.unix.hw.net.netrain.down
Explanation:
This is a NetRAIN internal "alert" event, posted after the Network
Interface Failure Finder (NIFF) has detected that connectivity
through a network interface has gone down.
Template Dump:
Formatted Message:
NetRAIN: node - detected a failed network connection on network via
interface
Event Data Items:
Event Name : sys.unix.hw.net.netrain.down
Cluster Event : False
Priority : 0
Format : NetRAIN: node @host_name detected a failed network
connection on network $network via interface $interface
Reference : cat:evmexp.cat:820
Variable Items:
network (STRING) = ""
interface (STRING) = ""
ipaddress (STRING) = ""
ipmask (STRING) = ""
reason (STRING) = "Reason not specified"
reason_code (INT32) = 0
To Index
*** EVENT sys.unix.hw.net.netrain.up
Explanation:
This is a NetRAIN internal "alert" event, posted after the Network
Interface Failure Finder (NIFF) has detected connectivity through a
network interface.
Template Dump:
Formatted Message:
NetRAIN: node - has detected an available network connection on network
via interface
Event Data Items:
Event Name : sys.unix.hw.net.netrain.up
Cluster Event : False
Priority : 0
Format : NetRAIN: node @host_name has detected an available
network connection on network $network via interface
$interface
Reference : cat:evmexp.cat:820
Variable Items:
network (STRING) = ""
interface (STRING) = ""
ipaddress (STRING) = ""
ipmask (STRING) = ""
reason_code (INT32) = 0
To Index
*** EVENT sys.unix.hw.net.niff.alert
Explanation:
This event is an internal event used to communicate interim network
interface failure status among NIFF components within a cluster.
The "color" of the alert is passed in the variable "$alert_type". The time interval used is passed in "$interval" (in seconds),
The alert types are:
- Yellow Alert: no bytes received by the interface for interval T1
- Orange Alert: no bytes received by the interface for interval T2
- Red Alert: no bytes received by the interface for interval T3
where the interval values T1, T2, T3 are NIFF configuration values.
In a cluster environment, this event is posted to all cluster members.
For more information please see the following reference pages: niffconfig(8), niffd(8) and nifftmt(7).
Template Dump:
Formatted Message:
NIFF: node - has declared a connectivity alert with network via interface
Event Data Items:
Event Name : sys.unix.hw.net.niff.alert
Cluster Event : True
Priority : 200
Format : NIFF: node @host_name has declared a connectivity
alert with network $network via interface $interface
Reference : cat:evmexp.cat:810
Variable Items:
network (STRING) = ""
interface (STRING) = ""
ipaddress (STRING) = ""
ipmask (STRING) = ""
alert_type (INT32) = 0
interval (INT32) = 0
To Index
*** EVENT sys.unix.hw.net.niff.down
Explanation:
This alert event is posted by the Network Interface Failure Finder
(NIFF) Traffic Monitoring Thread (nifftmt) when it has detected
that connectivity through a network interface has been lost. This
determination is made when there has been no change in the
interface's received byte count during the configured delay
interval.
In a cluster environment, this event is posted to all cluster members.
For more information please see the following reference pages: niffconfig(8), niffd(8) and nifftmt(7).
Template Dump:
Formatted Message:
NIFF: node - detected a failed network connection on network via interface
Event Data Items:
Event Name : sys.unix.hw.net.niff.down
Cluster Event : True
Priority : 600
Format : NIFF: node @host_name detected a failed network
connection on network $network via interface $interface
Reference : cat:evmexp.cat:810
Variable Items:
network (STRING) = ""
interface (STRING) = ""
ipaddress (STRING) = ""
ipmask (STRING) = ""
reason (STRING) = "Reason not specified"
reason_code (INT32) = 0
To Index
*** EVENT sys.unix.hw.net.niff.up
Explanation:
This event is posted by the Network Interface Failure Finder (NIFF)
when it has detected that connectivity is available through a
network interface.
In a cluster environment, this event is posted to all cluster members.
For more information please see the following reference pages: niffconfig(8), niffd(8) and nifftmt(7).
Template Dump:
Formatted Message:
NIFF: node - has detected an available network connection on network via
interface
Event Data Items:
Event Name : sys.unix.hw.net.niff.up
Cluster Event : True
Priority : 200
Format : NIFF: node @host_name has detected an available
network connection on network $network via interface
$interface
Reference : cat:evmexp.cat:810
Variable Items:
network (STRING) = ""
interface (STRING) = ""
ipaddress (STRING) = ""
ipmask (STRING) = ""
reason_code (INT32) = 0
To Index
*** EVENT sys.unix.hw.no_connections
Explanation:
This event is posted by the hardware support subsystem to report
that all connection paths to the device identified in the event
have been lost, and no access to the device is possible until a
path is restored.
Template Dump:
Formatted Message:
Connectivity has been lost for device (HWID=0 lid=0 btl=0/0/0)
Event Data Items:
Event Name : sys.unix.hw.no_connections._hwid.0
Cluster Event : True
Priority : 500
Format : Connectivity has been lost for device (HWID=$_hwid
lid=$lid btl=$port_id/$target_id/$lun_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
arch (STRING) = "none"
lid (UINT32) = 0
port_id (UINT32) = 0
target_id (UINT64) = 0
lun_id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.platform.error.bus.pci
Explanation:
No explanation is available for event
"sys.unix.hw.platform.error.bus.pci".
Template Dump:
Formatted Message:
A error detected on PCI bus 0.
Event Data Items:
Event Name : sys.unix.hw.platform.error.bus.pci
Cluster Event : True
Priority : 100
Format : A $error_type error detected on PCI bus $bus_num.
Reference : cat:evmexp.cat:840
Variable Items:
error_type (STRING) = ""
bus_num (UINT64) = 0
To Index
*** EVENT sys.unix.hw.platform.error.environmental
Explanation:
No explanation is available for event
"sys.unix.hw.platform.error.environmental".
Template Dump:
Formatted Message:
component (HWID=0) reached error threshold.
Event Data Items:
Event Name : sys.unix.hw.platform.error.environmental
Cluster Event : True
Priority : 100
Format : $component component (HWID=$id) reached error
threshold.
Reference : cat:evmexp.cat:840
Variable Items:
component (STRING) = ""
id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.platform.error.memory
Explanation:
No explanation is available for event
"sys.unix.hw.platform.error.memory".
Template Dump:
Formatted Message:
Memory error in at address 0. Error_type=0
Event Data Items:
Event Name : sys.unix.hw.platform.error.memory
Cluster Event : True
Priority : 100
Format : Memory error in $memory_type at address $memory_addr.
Error_type=$error_type
Reference : cat:evmexp.cat:840
Variable Items:
memory_type (STRING) = ""
error_type (INT32) = 0
memory_addr (UINT64) = 0
To Index
*** EVENT sys.unix.hw.platform.error.sensor
Explanation:
No explanation is available for event
"sys.unix.hw.platform.error.sensor".
Template Dump:
Formatted Message:
Unable to communicate with sensor (HWID=0).
Event Data Items:
Event Name : sys.unix.hw.platform.error.sensor
Cluster Event : True
Priority : 100
Format : Unable to communicate with $sensor sensor (HWID=$id).
Reference : cat:evmexp.cat:840
Variable Items:
sensor (STRING) = ""
id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.platform.warning.environmental
Explanation:
No explanation is available for event
"sys.unix.hw.platform.warning.environmental".
Template Dump:
Formatted Message:
component (HWID=0) reached warning threshold.
Event Data Items:
Event Name : sys.unix.hw.platform.warning.environmental
Cluster Event : True
Priority : 100
Format : $component component (HWID=$id) reached warning
threshold.
Reference : cat:evmexp.cat:840
Variable Items:
component (STRING) = ""
id (UINT64) = 0
To Index
*** EVENT sys.unix.hw.registered
Explanation:
This informational event is posted by the hardware support
subsystem to indicate that a hardware component has appeared on the
system. The component has been recognized and registered by the
system hardware configuration manager, and is now available for
use.
Template Dump:
Formatted Message:
A hardware component has been registered (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.registered._hwid.0
Cluster Event : True
Priority : 400
Format : A hardware component has been registered (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.hw.scan_completed
Explanation:
This event is posted by the hardware support subsystem to indicate
that either a full or partial scan of the system hardware has
completed. This operation scans the buses looking for new
hardware.
Template Dump:
Formatted Message:
A hardware scan has just completed
Event Data Items:
Event Name : sys.unix.hw.scan_completed
Cluster Event : True
Priority : 200
Format : A hardware scan has just completed
Reference : cat:evmexp.cat:800
Variable Items:
None
To Index
*** EVENT sys.unix.hw.state_change
Explanation:
This event is posted by the hardware support subsystem to indicate
that the state of a component has changed.
Template Dump:
Formatted Message:
Device state changed from unknown to unknown (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change._hwid.0
Cluster Event : True
Priority : 200
Format : Device state changed from $previous_state to
$current_state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.assigned
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been assigned to a hard partition. This means
the component is now owned by one of the hard partitions.
Template Dump:
Formatted Message:
Component State Change: Component "" has been assigned to host "" (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.assigned._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" has
been assigned to host "$_hostname" (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
_hostname (STRING) = ""
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
hsbb (UINT32) = 0
sbb (UINT32) = 0
partition (UINT32) = 0
To Index
*** EVENT sys.unix.hw.state_change.available
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has changed to the available state. The available
state is the default initial state when a component joins the
configuration after a successful self-test.
This event is only applicable to GS series machines. It occurs when a system administrator executes a user-level command to cause a CPU to become available.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the available state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.available._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" is
in the available state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.broken
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component is in the broken state. A component in this state
is not functional and cannot be used by the operating system.
Action: Contact your service provider.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the broken state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.broken._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
in the broken state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.cod
Explanation:
This event is used for internal purposes. The event communicates
the fact that the state of the "Capacity On Demand" attribute
"COD_state" has been changed. The hardware management interfaces,
including SysMan Station, subscribe to this event.
The possible values for the "COD_state" attribute are:
- spare: the CPU is currently an offline COD spare
- purchased: the CPU has been purchased by the customer, and is available to be placed online
- on-loan: (not yet implemented) temporary service from previous spare.
Template Dump:
Formatted Message:
Component State Change: the COD (Capacity On Demand) state of component ""
(HWID=0) has been changed to "unknown".
Event Data Items:
Event Name : sys.unix.hw.state_change.cod._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: the COD (Capacity On Demand)
state of component "$_hwcomponent" (HWID=$_hwid) has
been changed to "$current_cod_state".
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
current_cod_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.indicted.high
Explanation:
This event is posted by the hardware support subsystem on behalf of
an error analysis program to indicate that a component has been
`indicted`.
An indictment is a notification that an error condition has been identified or an error threshold has been exceeded for a component, and is therefore a recommendation that the component may require servicing.
An analysis program may indict more than one component if it cannot pinpoint which component is responsible for the error. In such cases, the most likely suspect will be indicted with a `high` probability. The next likely suspect will be indicted with a `medium` probability. Finally, the least likely suspect will be indicted with a `low` probability. The total_indictments and report_handle event variables are used to tie together multiple indictment notifications.
The following event variables may be particularly useful in evaluating this event:
- The urgency event variable is an integer value between 1 and 10 that identifies the seriousness of the problem. The greater the urgency value, the more serious the problem.
- The probability event variable is an integer value between 1 and 100 that identifies the likelihood that the indicted component is the cause of the error. The greater the probability value, the more likely the indicted component is suspect.
- The total_indictments event variable is an integer value between 1 and 10 that ties together the number of components that are being indicted for the same error. For example, if an analysis program cannot pinpoint which one of two components is responsible for the error, the analysis program will indict both components and set total_indictments to 2 in each of the indictment notifications.
- The report_handle event variable is an ASCII string value that is used as a pointer to additional information about the indictment. This variable is also used to tie together multiple indictment notifications (in other words, total_indictments is greater than 1). Indictment notifications that have the same report_handle value are tied to the same error.
Action: If the automatic deallocation policy defined in /etc/olar.config and /etc/olar.config.common is enabled for a particular component indicted with a high probability, the system will automatically deallocate the component. Whether or not automatic deallocation policy has been enabled, it should be verified through diagnostic testing that this component is indeed faulting, and if so, the component should be replaced.
Template Dump:
Formatted Message:
Component State Change: Component "" has been indicted with a `high`
probability of fault (HWID=0, FRUID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.indicted.high._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" has
been indicted with a `high` probability of fault
(HWID=$_hwid, FRUID=$module_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
component_id (UINT64) = 0
component_type (UINT8) = 0
component_subtype (UINT8) = 0
module_id (UINT64) = 0
module_type (UINT8) = 0
module_subtype (UINT8) = 0
category (STRING) = ""
initiator (STRING) = ""
report_handle (STRING) = ""
urgency (INT32) = 0
probability (INT32) = 0
total_indictments (INT32) = 0
previous_probability (INT32) = 0
description (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.indicted.low
Explanation:
This event is posted by the hardware support subsystem on behalf of
an error analysis program to indicate that a component has been
`indicted`.
An indictment is a notification that an error condition has been identified or an error threshold has been exceeded for a component, and is therefore a recommendation that the component may require servicing.
An analysis program may indict more than one component if it cannot pinpoint which component is responsible for the error. In such cases, the most likely suspect will be indicted with a `high` probability. The next likely suspect will be indicted with a `medium` probability. Finally, the least likely suspect will be indicted with a `low` probability. The total_indictments and report_handle event variables are used to tie together multiple indictment notifications.
The following event variables may be particularly useful in evaluating this event:
- The urgency event variable is an integer value between 1 and 10 that identifies the seriousness of the problem. The greater the urgency value, the more serious the problem.
- The probability event variable is an integer value between 1 and 100 that identifies the likelihood that the indicted component is the cause of the error. The greater the probability value, the more likely the indicted component is suspect.
- The total_indictments event variable is an integer value between 1 and 10 that ties together the number of components that are being indicted for the same error. For example, if an analysis program cannot pinpoint which one of two components is responsible for the error, the analysis program will indict both components and set total_indictments to 2 in each of the indictment notifications.
- The report_handle event variable is an ASCII string that is used as a pointer to additional information about the indictment. This variable is also used to tie together multiple indictment notifications (in other words, total_indictments is greater than 1). Indictment notifications that have the same report_handle value are tied to the same error.
Action: If the automatic deallocation policy defined in /etc/olar.config and /etc/olar.config.common is enabled for a particular component indicted with a low probability, the system will automatically deallocate the component. Whether or not automatic deallocation policy has been enabled, it should be verified through diagnostic testing that this component is indeed faulting, and if so, the component should be replaced.
Template Dump:
Formatted Message:
Component State Change: Component "" has been indicted with a `low`
probability of fault (HWID=0, FRUID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.indicted.low._hwid.0
Cluster Event : True
Priority : 300
Format : Component State Change: Component "$_hwcomponent" has
been indicted with a `low` probability of fault
(HWID=$_hwid, FRUID=$module_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
component_id (UINT64) = 0
component_type (UINT8) = 0
component_subtype (UINT8) = 0
module_id (UINT64) = 0
module_type (UINT8) = 0
module_subtype (UINT8) = 0
category (STRING) = ""
initiator (STRING) = ""
report_handle (STRING) = ""
urgency (INT32) = 0
probability (INT32) = 0
total_indictments (INT32) = 0
previous_probability (INT32) = 0
description (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.indicted.medium
Explanation:
This event is posted by the hardware support subsystem on behalf of
an error analysis program to indicate that a component has been
`indicted`.
An indictment is a notification that an error condition has been identified or an error threshold has been exceeded for a component, and is therefore a recommendation that the component may require servicing.
An analysis program may indict more than one component if it cannot pinpoint which component is responsible for the error. In such cases, the most likely suspect will be indicted with a `high` probability. The next likely suspect will be indicted with a `medium` probability. Finally, the least likely suspect will be indicted with a `low` probability. The total_indictments and report_handle event variables are used to tie together multiple indictment notifications.
The following event variables may be particularly useful in evaluating this event:
- The urgency event variable is an integer value between 1 and 10 that identifies the seriousness of the problem. The greater the urgency value, the more serious the problem.
- The probability event variable is an integer value between 1 and 100 that identifies the likelihood that the indicted component is the cause of the error. The greater the probability value, the more likely the indicted component is suspect.
- The total_indictments event variable is an integer value between 1 and 10 that ties together the number of components that are being indicted for the same error. For example, if an analysis program cannot pinpoint which one of two components is responsible for the error, the analysis program will indict both components and set total_indictments to 2 in each of the indictment notifications.
- The report_handle event variable is an ASCII string value that is used as a pointer to additional information about the indictment. This variable is also used to tie together multiple indictment notifications (in other words, total_indictments is greater than 1). Indictment notifications that have the same report_handle value are tied to the same error.
Action: If the automatic deallocation policy defined in /etc/olar.config and /etc/olar.config.common is enabled for a particular component indicted with a medium probability, the system will automatically deallocate the component. Whether or not automatic deallocation policy has been enabled, it should be verified through diagnostic testing that this component is indeed faulting, and if so, the component should be replaced.
Template Dump:
Formatted Message:
Component State Change: Component "" has been indicted with a `medium`
probability of fault (HWID=0, FRUID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.indicted.medium._hwid.0
Cluster Event : True
Priority : 400
Format : Component State Change: Component "$_hwcomponent" has
been indicted with a `medium` probability of fault
(HWID=$_hwid, FRUID=$module_id)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
component_id (UINT64) = 0
component_type (UINT8) = 0
component_subtype (UINT8) = 0
module_id (UINT64) = 0
module_type (UINT8) = 0
module_subtype (UINT8) = 0
category (STRING) = ""
initiator (STRING) = ""
report_handle (STRING) = ""
urgency (INT32) = 0
probability (INT32) = 0
total_indictments (INT32) = 0
previous_probability (INT32) = 0
description (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.indicted.memory_page
Explanation:
This event is posted by the hardware support subsystem on behalf of
an error analysis program to indicate that a bad memory location
has been detected within the page that the page frame number (PFN)
points to. There are two reasons why an analysis program will
indict a memory page. The most likely scenario is that there is a
single cell failure, in a single location, within a single page (in
other words, a stuck bit). The second scenario is that a memory
part has failed (for example, SRAM, DIMM). In the second case, an
indictment will also occur for the memory part.
The following event variables may be particularly useful in evaluating this event:
- The _physical_address event variable identifies the physical memory address of the failing location within the memory page. The PFN is derived from the (faulting) physical address by logically shifting the physical address right some number of places, based on the page size.
- The urgency event variable is an integer value between 1 and 10 that identifies the seriousness of the problem. The greater the urgency value, the more serious the problem.
- The probability event variable is an integer value between 1 and 100 that identifies the likelihood that the indicted memory page is the cause of the error. The greater the probability value, the more likely the memory page is the culprit.
- The total_indictments event variable is an integer value between 1 and 10 that ties together the number of components that are being indicted for the same error. For example, if an analysis program cannot pinpoint which one of two components is responsible for the error, the analysis program will indict both components and set total_indictments to 2 in each of the indictment notifications.
- The report_handle event variable is an ASCII string that is used as a pointer to additional information about the indictment. This variable is also used to tie together multiple indictment notifications (in other words, total_indictments is greater than 1). Indictment notifications that have the same report_handle value are tied to the same error.
Note: The _hwid event variable is required to be present in this event for backwards compatibility with the pre-existing hw.state_change event. For this event, the _hwid is meaningless and its value will always be set to 0.
Action: If the automatic deallocation policy defined in /etc/olar.config and /etc/olar.config.common is enabled, the system will automatically deallocate the memory page containing the indicted physical address when the page is no longer being referenced. Therefore, no action will be required. Note that if automatic deallocation is disabled, a reinitialization of the system with memory testing enabled may uncover this failing location, and map it out automatically prior to boot. Eventually it may be necessary to replace the memory module containing the failing physical address.
Template Dump:
Formatted Message:
Component State Change: Physical address 0 has been indicted
Event Data Items:
Event Name : sys.unix.hw.state_change.indicted.memory_page._physical
_address.0._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Physical address
$_physical_address has been indicted
Reference : cat:evmexp.cat:800
Variable Items:
_physical_address (UINT64) = 0
initiator (STRING) = ""
report_handle (STRING) = ""
urgency (INT32) = 0
probability (INT32) = 0
total_indictments (INT32) = 0
description (STRING) = ""
_hwid (UINT64) = 0
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.limited
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component is operating in the limited state. A component in
this state is not providing full service.
Template Dump:
Formatted Message:
Component State Change: Component "" is operating in the 'limited' state
(HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.limited._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
operating in the 'limited' state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.off
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been changed to the powered off state. Once a
component has been powered off, it can be physically removed from
the system.
Currently, this event is only applicable to GS series machines. It occurs when a system administrator executes a user-level command to turn the CPU power off.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the powered off state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.off._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
in the powered off state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.offline
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been changed to the offline state. A
component in this state is no longer being used by the operating
system. The offline state is persistent and therefore the
component will not come back online at the next reboot or power
cycle.
This event occurs when a system administrator executes a user-level command to take a CPU offline. This function is currently available on all multi-CPU machines.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the offline state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.offline._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
in the offline state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.offline_nosave
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been changed to the offline_nosave state. A
component in this state is no longer being used by the operating
system. The offline_nosave state is not persistent and therefore
the component will come back online at the next reboot or power
cycle.
This event occurs when a system administrator executes a user-level command to take a CPU offline. This function is currently available on all multi-CPU machines.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the offline-nosave state
(HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.offline_nosave._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
in the offline-nosave state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.offline_request
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component is in the process of being taken offline. A
component in this state remains available to its current users, but
the operating system will not allow any new users.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the offline-request state
(HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.offline_request._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" is
in the offline-request state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.online
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been changed to the online state. A component
in this state is operational and available for use.
This event occurs when a system administrator executes a user-level command to bring a CPU online. This function is available on all multi-CPU systems.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the online state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.online._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" is
in the online state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.testing
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component is in the testing state. A component in this
state is running in a mode where it is being tested.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the testing state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.testing._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" is
in the testing state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.unassigned
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been unassigned from a hard partition. This
means the component is no longer owned by any of the hard
partitions.
Template Dump:
Formatted Message:
Component State Change: Component "" has been unassigned from host ""
(HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.unassigned._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" has
been unassigned from host "$_hostname" (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
_hostname (STRING) = ""
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
hsbb (UINT32) = 0
sbb (UINT32) = 0
partition (UINT32) = 0
To Index
*** EVENT sys.unix.hw.state_change.unavailable
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been changed to the unavailable state. A
component in this state cannot be reached by the operating system,
and it cannot be determined if the inability to reach it is due to
a problem with the component itself or with another component in
the access path.
This event is only applicable to GS series machines. It occurs when a system administrator executes a user-level command to cause the CPU to no longer be available.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the unavailable state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.unavailable._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
in the unavailable state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.unindicted
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component has been unindicted. This means that the indicted
state, for a previously indicted component, has been cleared.
Currently, this event is only applicable to GS series machines. It occurs when a system administrator executes a user-level command to "unindict" a previously-indicted CPU component after the CPU has been replaced.
Template Dump:
Formatted Message:
Component State Change: Component "" has been unindicted (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.unindicted._hwid.0
Cluster Event : True
Priority : 200
Format : Component State Change: Component "$_hwcomponent" has
been unindicted (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.state_change.unknown
Explanation:
This event is posted by the hardware support subsystem to indicate
that a component is in the unknown state. The software that is
controlling the component has selected the unknown state because it
could not determine the actual state of the component.
Template Dump:
Formatted Message:
Component State Change: Component "" is in the unknown state (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.state_change.unknown._hwid.0
Cluster Event : True
Priority : 500
Format : Component State Change: Component "$_hwcomponent" is
in the unknown state (HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
initiator (STRING) = ""
current_state (STRING) = "unknown"
previous_state (STRING) = "unknown"
To Index
*** EVENT sys.unix.hw.user_name_changed
Explanation:
This event is posted by the hardware support subsystem to indicate
that the user-settable device attribute "user_name" changed on the
device specified by _hwid.
Template Dump:
Formatted Message:
Attribute user_name changed to "" (HWID=0)
Event Data Items:
Event Name : sys.unix.hw.user_name_changed._hwid.0
Cluster Event : True
Priority : 200
Format : Attribute user_name changed to "$user_name"
(HWID=$_hwid)
Reference : cat:evmexp.cat:800
Variable Items:
_hwid (UINT64) = 0
user_name (STRING) = ""
To Index
*** EVENT sys.unix.install
Explanation:
Events whose names begin with "sys.unix.install" are posted by the
Software Installation subsystem, to report changes of state.
Template Dump:
Formatted Message:
Installation event
Event Data Items:
Event Name : sys.unix.install
Priority : 200
Format : Installation event
Reference : cat:evmexp.cat:500
Variable Items:
None
To Index
*** EVENT sys.unix.kernel.starting_cpu
Explanation:
This event is posted by the kernel in a multi-processor system to
indicate that a secondary CPU is being started. The event will be
accompanied by a sys.unix.hw.state_change.online event.
This event occurs when a system administrator executes a user-level command to bring a CPU online. This function is currently available on all multi-CPU machines.
Template Dump:
Formatted Message:
Secondary CPU 0 is being started
Event Data Items:
Event Name : sys.unix.kernel.starting_cpu
Priority : 200
Format : Secondary CPU $cpu is being started
Reference : cat:evmexp.cat:1300
Variable Items:
cpu (INT32) = 0
To Index
*** EVENT sys.unix.kernel.stopping_cpu
Explanation:
This event is posted by the kernel in a multi-processor system to
indicate that a secondary CPU is being stopped. The event will be
accompanied by a sys.unix.hw.state_change.offline (or
"offline_nosave") event.
This event occurs when a system administrator executes a user-level command to take a CPU offline. This function is currently available on all multi-CPU machines.
Template Dump:
Formatted Message:
Secondary CPU 0 is being stopped
Event Data Items:
Event Name : sys.unix.kernel.stopping_cpu
Priority : 200
Format : Secondary CPU $cpu is being stopped
Reference : cat:evmexp.cat:1300
Variable Items:
cpu (INT32) = 0
To Index
*** EVENT sys.unix.lsm.volnotify.msg.deport
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named disk group has been deported.
Included in the message is the disk group identifier.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: deport dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.deport
Cluster Event : True
Priority : 200
I18N Msg Id : 8003
I18N Catalog : lsm.cat
Format : LSM volnotify: deport dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.dgchg
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility indicating the configuration for the named disk group has
been changed. Included in the message is the transaction
identifier for the update.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: change dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.dgchg
Cluster Event : True
Priority : 200
I18N Msg Id : 8005
I18N Catalog : lsm.cat
Format : LSM volnotify: change dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.dgdis
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named disk group has been disabled.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: disable dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.dgdis
Cluster Event : True
Priority : 300
I18N Msg Id : 8004
I18N Catalog : lsm.cat
Format : LSM volnotify: disable dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.dskchg
Explanation:
Posted by the Logical Storage Manager (LSM) volnotify utility to
indicate that the named disk's header has changed.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: change disk NULL dm NULL dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.dskchg
Cluster Event : True
Priority : 200
I18N Msg Id : 8009
I18N Catalog : lsm.cat
Format : LSM volnotify: change disk $dsk dm $dm dg $dg dgid
$dgid
Reference : cat:evmexp.cat
Variable Items:
dsk (STRING) = "NULL"
dm (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.dskdet
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named disk has been disconnected from
the named disk group, as a result of an apparent total disk
failure.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: detach disk NULL dm NULL dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.dskdet
Cluster Event : True
Priority : 300
I18N Msg Id : 8008
I18N Catalog : lsm.cat
Format : LSM volnotify: detach disk $dsk dm $dm dg $dg dgid
$dgid
Reference : cat:evmexp.cat
Variable Items:
dsk (STRING) = "NULL"
dm (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.import
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named disk group with the named disk
group ID has been imported.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: import dg NULL dgid=NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.import
Cluster Event : True
Priority : 200
I18N Msg Id : 8002
I18N Catalog : lsm.cat
Format : LSM volnotify: import dg $dg dgid=$dgid
Reference : cat:evmexp.cat
Variable Items:
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.logdet
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that all log copies for the named volume have
become unusable as a result of I/O failures or a detected total
disk failure.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: log-detach $log dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.logdet
Cluster Event : True
Priority : 300
I18N Msg Id : 8013
I18N Catalog : lsm.cat
Format : LSM volnotify: log-detach $vol dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
vol (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.more
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that some events may have been lost, possibly
due to internal buffer overruns.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: more events
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.more
Cluster Event : True
Priority : 200
I18N Msg Id : 8014
I18N Catalog : lsm.cat
Format : LSM volnotify: more events
Reference : cat:evmexp.cat
Variable Items:
None
To Index
*** EVENT sys.unix.lsm.volnotify.msg.pldet
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named plex has been detached from its
volume, due either to an I/O failure during normal volume I/O or to
a detected disk failure.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: detach plex NULL volume NULL dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.pldet
Cluster Event : True
Priority : 300
I18N Msg Id : 8006
I18N Catalog : lsm.cat
Format : LSM volnotify: detach plex $pl volume $vol dg $dg dgid
$dgid
Reference : cat:evmexp.cat
Variable Items:
pl (STRING) = "NULL"
vol (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.sddet
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named subdisk has been detached from
its plex, due either to an I/O failure during normal volume I/O or
as a result of a detected disk failure.
A subdisk failure in a RAID5 volume or a log subdisk in a mirrored volume results in a subdisk detach, while other failures generally result in the associated plex being detached.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: detach subdisk NULL plex NULL volume NULL dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.sddet
Cluster Event : True
Priority : 300
I18N Msg Id : 8010
I18N Catalog : lsm.cat
Format : LSM volnotify: detach subdisk $sd plex $pl volume $vol
dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
sd (STRING) = "NULL"
pl (STRING) = "NULL"
vol (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.sdrel
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility indicating the named subdisk has been relocated as a result
of hot sparing.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: relocate subdisk NULL plex NULL volume NULL dg NULL dgid
NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.sdrel
Cluster Event : True
Priority : 300
I18N Msg Id : 8011
I18N Catalog : lsm.cat
Format : LSM volnotify: relocate subdisk $sd plex $pl volume
$vol dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
sd (STRING) = "NULL"
pl (STRING) = "NULL"
vol (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.vold_dis
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that vold was changed to "disabled" mode.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: NULL disabled
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.vold_dis
Cluster Event : True
Priority : 200
I18N Msg Id : 8000
I18N Catalog : lsm.cat
Format : LSM volnotify: $vold_util disabled
Reference : cat:evmexp.cat
Variable Items:
vold_util (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.vold_ena
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that vold was changed to "enabled" mode.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: NULL enabled
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.vold_ena
Cluster Event : True
Priority : 200
I18N Msg Id : 8001
I18N Catalog : lsm.cat
Format : LSM volnotify: $vold_util enabled
Reference : cat:evmexp.cat
Variable Items:
vold_util (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.voldeg
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named RAID5 volume has been put in
degraded mode due to the loss of a subdisk.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: degraded volume NULL dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.voldeg
Cluster Event : True
Priority : 300
I18N Msg Id : 8012
I18N Catalog : lsm.cat
Format : LSM volnotify: degraded volume $vol dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
vol (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.lsm.volnotify.msg.voldet
Explanation:
This event is posted by the Logical Storage Manager (LSM) volnotify
utility to indicate that the named volume has been detached, either
as a result of an I/O failure during normal volume I/O or as a
result of a total disk failure. Normally, only plexes and subdisks
are detached; however, if a volume would become unusable by
detaching a plex or subdisk, the volume may be detached.
See the volnotify(8) reference page for more information.
Template Dump:
Formatted Message:
LSM volnotify: detach volume NULL dg NULL dgid NULL
Event Data Items:
Event Name : sys.unix.lsm.volnotify.msg.voldet
Cluster Event : True
Priority : 300
I18N Msg Id : 8007
I18N Catalog : lsm.cat
Format : LSM volnotify: detach volume $vol dg $dg dgid $dgid
Reference : cat:evmexp.cat
Variable Items:
vol (STRING) = "NULL"
dg (STRING) = "NULL"
dgid (STRING) = "NULL"
To Index
*** EVENT sys.unix.misclog
Explanation:
Miscellaneous log events are messages retrieved from subsystem log
files through the "misclog" event channel.
Template Dump:
Formatted Message:
Miscellaneous log event
Event Data Items:
Event Name : sys.unix.misclog
Priority : 200
Format : Miscellaneous log event
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.misclog.cronlog
Explanation:
Events in this category are messages written by the system clock
daemon, cron, to its own log file, and retrieved through the
"misclog" event channel. The name of the cron log file is
/var/adm/cron/log.
Template Dump:
Formatted Message:
cronlog: Miscellaneous cronlog message
Event Data Items:
Event Name : sys.unix.misclog.cronlog
Priority : 200
Format : cronlog: Miscellaneous cronlog message
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.misclog.evmchmgr
Explanation:
Events in this category are messages written by the Event Manager
(EVM) channel manager to its own log file, and retrieved through
the "misclog" event channel.
The active log is /var/evm/adm/logfiles/evmchmgr.log. Each time EVM is restarted the old log is renamed to evmchmgr.log.old, and a new log is created.
Template Dump:
Formatted Message:
EVM chmgr: Miscellaneous log message
Event Data Items:
Event Name : sys.unix.misclog.evmchmgr
Priority : 200
Format : EVM chmgr: Miscellaneous log message
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.misclog.evmdaemon
Explanation:
Events in this category are messages written by the Event Manager
(EVM) daemon to its own log file, and retrieved through the
"misclog" event channel.
The active log is /var/evm/adm/logfiles/evmdaemon.log. Each time EVM is restarted the old log is renamed to evmdaemon.log.old, and a new log is created.
Template Dump:
Formatted Message:
EVM daemon: Miscellaneous log message
Event Data Items:
Event Name : sys.unix.misclog.evmdaemon
Priority : 200
Format : EVM daemon: Miscellaneous log message
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.misclog.evmlogger
Explanation:
Events in this category are messages written by the Event Manager
(EVM) logger to its own log file, and retrieved through the
"misclog" event channel.
The active log is /var/evm/adm/logfiles/evmlogger.log. Each time EVM is restarted the old log is renamed to evmlogger.log.old, and a new log is created.
Template Dump:
Formatted Message:
EVM logger: Miscellaneous log message
Event Data Items:
Event Name : sys.unix.misclog.evmlogger
Priority : 200
Format : EVM logger: Miscellaneous log message
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.misclog.smsd
Explanation:
Events in this category are messages written by the Sysman Station
daemon, smsd, to its own log file, and retrieved through the
"misclog" event channel.
Log files are stored in the directory /var/adm/sysman/sysman_station.
Template Dump:
Formatted Message:
smsd: Miscellaneous smsd message
Event Data Items:
Event Name : sys.unix.misclog.smsd
Priority : 200
Format : smsd: Miscellaneous smsd message
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.misclog.sulog
Explanation:
Events in this category are messages written by the SU utility, to
its own log file, and retrieved through the "misclog" event
channel. The name of the log file is /var/adm/sulog.
Template Dump:
Formatted Message:
cronlog: Miscellaneous sulog message
Event Data Items:
Event Name : sys.unix.misclog.sulog
Priority : 200
Format : cronlog: Miscellaneous sulog message
Reference : cat:evmexp.cat:320
Variable Items:
None
To Index
*** EVENT sys.unix.net
Explanation:
Events in this category are posted by the kernel network
subsystem.
Template Dump:
Formatted Message:
Base network event
Event Data Items:
Event Name : sys.unix.net
Cluster Event : True
Priority : 200
Format : Base network event
Reference : cat:evmexp.cat:2100
Variable Items:
None
To Index
*** EVENT sys.unix.net.route.ip.add
Explanation:
This informational event is posted by the kernel network routing
subsystem to indicate that a route has been added to an IP routing
table. Although changes to routing tables are generally made by
the route command, it is possible that a change may have been made
by another utility or application program.
Action: No action is required.
Template Dump:
Formatted Message:
An IPv0 route has been added: destination=None, gateway=None,
interface=None
Event Data Items:
Event Name : sys.unix.net.route.ip.add
Cluster Event : True
Priority : 100
Format : An IPv$ipvers route has been added:
destination=$new_dest, gateway=$new_gateway,
interface=$new_ifname
Reference : cat:evmexp.cat:2100
Variable Items:
new_dest (STRING) = "None"
new_gateway (STRING) = "None"
new_ifname (STRING) = "None"
new_flags (STRING) = "None"
new_netmask (STRING) = "None"
ipvers (INT32) = 0
To Index
*** EVENT sys.unix.net.route.ip.change
Explanation:
This informational event is posted by the kernel network routing
subsystem to indicate that a route has been changed in an IP
routing table. Although changes to routing tables are generally
made by the route command, it is possible that a change may have
been made by another utility or application program.
Action: No action is required.
Template Dump:
Formatted Message:
An IPv0 route has been changed to: destination=None, gateway=None,
interface=None
Event Data Items:
Event Name : sys.unix.net.route.ip.change
Cluster Event : True
Priority : 100
Format : An IPv$ipvers route has been changed to:
destination=$new_dest, gateway=$new_gateway,
interface=$new_ifname
Reference : cat:evmexp.cat:2100
Variable Items:
new_dest (STRING) = "None"
new_gateway (STRING) = "None"
new_ifname (STRING) = "None"
new_flags (STRING) = "None"
new_netmask (STRING) = "None"
old_dest (STRING) = "None"
old_gateway (STRING) = "None"
old_ifname (STRING) = "None"
old_flags (STRING) = "None"
old_netmask (STRING) = "None"
ipvers (INT32) = 0
To Index
*** EVENT sys.unix.net.route.ip.delete
Explanation:
This informational event is posted by the kernel network routing
subsystem to indicate that a route has been deleted from an IP
routing table. Although changes to routing tables are generally
made by the route command, it is possible that a change may have
been made by another utility or application program.
Action: No action is required.
Template Dump:
Formatted Message:
An IPv0 route has been deleted: destination=None, gateway=None,
interface=None
Event Data Items:
Event Name : sys.unix.net.route.ip.delete
Cluster Event : True
Priority : 100
Format : An IPv$ipvers route has been deleted:
destination=$old_dest, gateway=$old_gateway,
interface=$old_ifname
Reference : cat:evmexp.cat:2100
Variable Items:
old_dest (STRING) = "None"
old_gateway (STRING) = "None"
old_ifname (STRING) = "None"
old_flags (STRING) = "None"
old_netmask (STRING) = "None"
ipvers (INT32) = 0
To Index
*** EVENT sys.unix.nis.yppush
Explanation:
This event is posted by the Network Information Services (NIS)
subsystem (formerly known as Yellow Pages). NIS is a distributed
name service that allows hosts to share a common set of system and
network files - for example, passwd and group files. Information
distributed by NIS is stored in database files called "maps".
There are two types of NIS servers - master and slave. The master server stores the master copy of the NIS maps, while slave servers store copies of the master server's maps. Whenever a map is updated on the master server, the master "pushes" the new map to the slave servers.
In a single-system environment a yppush requires an updated map to be copied from the master to the slave. In a cluster system, the yppush command posts this cluster-wide event to instruct the slave ypserv daemons running on the various nodes to reload their maps from the shared file system.
Template Dump:
Formatted Message:
NIS detected a yppush event for map
Event Data Items:
Event Name : sys.unix.nis.yppush
Cluster Event : True
Priority : 100
Format : NIS detected a yppush event for map $mapname
Reference : cat:evmexp.cat:1500
Variable Items:
mapname (STRING) = ""
To Index
*** EVENT sys.unix.pc_card
Explanation:
Events whose names begin with "sys.unix.pc_card" are posted by the
PC Cardbus (PCMCIA) component, to report changes of state of a
PCMCIA device.
Template Dump:
Formatted Message:
Cardbus/PCMCIA event
Event Data Items:
Event Name : sys.unix.pc_card
Priority : 200
Format : Cardbus/PCMCIA event
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.pc_card.battery.dead
Explanation:
This event is posted when the battery of a PC card device is dead.
Action: Replace the battery.
Template Dump:
Formatted Message:
Battery dead on the PC Card in socket $socketnum, PCMCIA bus $busnum
Event Data Items:
Event Name : sys.unix.pc_card.battery.dead
Priority : 700
Format : Battery dead on the PC Card in socket $socketnum,
PCMCIA bus $busnum
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.pc_card.battery.low
Explanation:
This event is posted when the battery of a PC Card device is low.
Action: Replace the battery as soon as possible.
Template Dump:
Formatted Message:
Battery low on the PC Card in socket $socketnum, PCMCIA bus $busnum
Event Data Items:
Event Name : sys.unix.pc_card.battery.low
Priority : 600
Format : Battery low on the PC Card in socket $socketnum,
PCMCIA bus $busnum
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.pc_card.insert
Explanation:
This informational event is posted when a PC Card device is
inserted into the Cardbus slot. The event includes details of the
card.
Template Dump:
Formatted Message:
PC Card inserted in socket $socketnum, PCMCIA bus $busnum -- Card
Manufacturer: $manuf_name, Product Name: $prodname
Event Data Items:
Event Name : sys.unix.pc_card.insert
Priority : 200
Format : PC Card inserted in socket $socketnum, PCMCIA bus
$busnum -- Card Manufacturer: $manuf_name, Product
Name: $prodname
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.pc_card.ready
Explanation:
This informational event is posted when a PC Card device has
completed its initialization process and is ready for use.
Template Dump:
Formatted Message:
The PC Card in socket $socketnum, PCMCIA bus $busnum, is READY.
Event Data Items:
Event Name : sys.unix.pc_card.ready
Priority : 200
Format : The PC Card in socket $socketnum, PCMCIA bus $busnum,
is READY.
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.pc_card.remove
Explanation:
This informational event is posted when a PC Card device is removed
from the Cardbus slot.
Template Dump:
Formatted Message:
PC Card removed from socket $socketnum, PCMCIA bus $busnum
Event Data Items:
Event Name : sys.unix.pc_card.remove
Priority : 300
Format : PC Card removed from socket $socketnum, PCMCIA bus
$busnum
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.pc_card.reset
Explanation:
This informational event is posted when a PC Card device has been
reset.
Template Dump:
Formatted Message:
Function $funcnum, in the PC Card in socket $socketnum, PCMCIA bus
$busnum, has been reset.
Event Data Items:
Event Name : sys.unix.pc_card.reset
Priority : 300
Format : Function $funcnum, in the PC Card in socket
$socketnum, PCMCIA bus $busnum, has been reset.
Reference : cat:evmexp.cat:900
Variable Items:
None
To Index
*** EVENT sys.unix.perfman
Explanation:
Events whose names begin with "sys.unix.perfman" are posted by the
Performance Manager (PM) component.
Template Dump:
Formatted Message:
Performance Manager event
Event Data Items:
Event Name : sys.unix.perfman
Priority : 200
Format : Performance Manager event
Reference : cat:evmexp.cat:1200
Variable Items:
None
To Index
*** EVENT sys.unix.power
Explanation:
Events whose names begin with "sys.unix.power" are posted by the
system power management component, to report changes of state.
Template Dump:
Formatted Message:
Power Management event
Event Data Items:
Event Name : sys.unix.power
Priority : 200
Format : Power Management event
Reference : cat:evmexp.cat:1000
Variable Items:
None
To Index
*** EVENT sys.unix.power.attr_change
Explanation:
This event is posted by the power manager. Power-managed devices
subscribe to these events and take the necessary action depending
on the attribute changed.
Action: No action is required.
Template Dump:
Formatted Message:
PwrMgr: Attribute changed
Event Data Items:
Event Name : sys.unix.power.attr_change
Priority : 200
Format : PwrMgr: Attribute changed
Reference : cat:evmexp.cat:1000
Variable Items:
attribute (UINT32) = 0
To Index
*** EVENT sys.unix.power.battery_change
Explanation:
This event is posted by a battery device for any power change. The
power monitor code will be the main subscriber to this event.
Action: The action required will be determined by the power monitor.
NOTE: This event is not currently used. but it is in place for future support of battery changes.
Template Dump:
Formatted Message:
PwrMgr: Battery change in device 0 - state 0
Event Data Items:
Event Name : sys.unix.power.battery_change
Priority : 600
Format : PwrMgr: Battery change in device $device_id - state
$battery_state
Reference : cat:evmexp.cat:1000
Variable Items:
device_id (UINT64) = 0
battery_state (UINT64) = 0
To Index
*** EVENT sys.unix.power.dev_dereg
Explanation:
This event is posted by the power manager when a power-managed
device is deregistered. The user level program would be interested
in subscribing to this event to make sure it has an up-to-date list
of all power-managed devices.
Action: No action is required.
Template Dump:
Formatted Message:
PwrMgr: Device 0 deregistered
Event Data Items:
Event Name : sys.unix.power.dev_dereg
Priority : 200
Format : PwrMgr: Device $device_id deregistered
Reference : cat:evmexp.cat:1000
Variable Items:
device_id (UINT64) = 0
To Index
*** EVENT sys.unix.power.dev_reg
Explanation:
This event is posted by the power manager when a power-managed
device is registered. The user-level program would be interested
in subscribing to this event to make sure it has an up-to-date list
of all power managed devices.
Action: No action is required.
Template Dump:
Formatted Message:
PwrMgr: Device 0 registered
Event Data Items:
Event Name : sys.unix.power.dev_reg
Priority : 200
Format : PwrMgr: Device $device_id registered
Reference : cat:evmexp.cat:1000
Variable Items:
device_id (UINT64) = 0
To Index
*** EVENT sys.unix.power.state_change
Explanation:
This event is posted by a power-managed device when a power state
change occurs on that device - for example, when a disk goes from
being spun up to spun down.
This event is subscribed to by those who care about these type of events. Right now, the user interface would be the main consumer of this event, but it doesn't necessarily have to subscribe to this event.
Action: No action need be taken unless the administrator wants to prevent a device from being powered down.
Template Dump:
Formatted Message:
PwrMgr: State change in device 0 - state 0
Event Data Items:
Event Name : sys.unix.power.state_change
Priority : 200
Format : PwrMgr: State change in device $device_id - state
$power_state
Reference : cat:evmexp.cat:1000
Variable Items:
device_id (UINT64) = 0
power_state (UINT32) = 0
To Index
*** EVENT sys.unix.power.thermal_change
Explanation:
This event is posted by a thermal device for any temperature
change. The environmental monitor code will be the main subscriber
to this event.
Action: The action required will be determined by the environmental monitor.
NOTE: This event is not currently used, but it is in place for future support of temperature changes.
Template Dump:
Formatted Message:
PwrMgr: Thermal change in device device_id - state 0
Event Data Items:
Event Name : sys.unix.power.thermal_change
Priority : 700
Format : PwrMgr: Thermal change in device device_id - state
$thermal_state
Reference : cat:evmexp.cat:1000
Variable Items:
device_id (UINT64) = 0
thermal_state (UINT64) = 0
To Index
*** EVENT sys.unix.print.lpd
Explanation:
Event class name for all printing events related to the lpd
subsystem.
Template Dump:
Formatted Message:
LPD printing event - Printer $printer
Event Data Items:
Event Name : sys.unix.print.lpd
Priority : 200
Format : LPD printing event - Printer $printer
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.lpd.daemon.start
Explanation:
This informational event is posted when the line printer parent
daemon, lpd, is started.
Template Dump:
Formatted Message:
LPD daemon started - Status: $status PID: -
Event Data Items:
Event Name : sys.unix.print.lpd.daemon.start
Priority : 200
Format : LPD daemon started - Status: $status PID: @PID
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.lpd.daemon.stop
Explanation:
This informational event is posted when the line printer parent
daemon, lpd, is stopped.
Template Dump:
Formatted Message:
LPD daemon stopped - Status: $status PID: -
Event Data Items:
Event Name : sys.unix.print.lpd.daemon.stop
Priority : 200
Format : LPD daemon stopped - Status: $status PID: @PID
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.lpd.job.remove.complete
Explanation:
This informational event is posted by the line printer parent
daemon, lpd, when a local or remote request to remove a job from a
queue is complete.
Template Dump:
Formatted Message:
LPD job remove completed - Status $status Printer $printer Job number
$jobnumber
Event Data Items:
Event Name : sys.unix.print.lpd.job.remove.complete
Priority : 200
Format : LPD job remove completed - Status $status Printer
$printer Job number $jobnumber
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.lpd.job.remove.request
Explanation:
This informational event is posted by the line printer parent
daemon, lpd, when a local or remote request to remove a print job
is issued.
Template Dump:
Formatted Message:
LPD job remove requested - Status $status Printer $printer
Event Data Items:
Event Name : sys.unix.print.lpd.job.remove.request
Priority : 200
Format : LPD job remove requested - Status $status Printer
$printer
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.lpd.job.submit.complete
Explanation:
This informational event is posted by the line printer parent
daemon, lpd, when a local or remote print job is complete.
Template Dump:
Formatted Message:
LPD job submit completed - Status $status Printer $printer Job number
$jobnumber
Event Data Items:
Event Name : sys.unix.print.lpd.job.submit.complete
Priority : 200
Format : LPD job submit completed - Status $status Printer
$printer Job number $jobnumber
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.lpd.job.submit.request
Explanation:
This informational event is posted by the line printer parent
daemon, lpd, when a request to submit a local or remote print job
has been made and the job is queued.
Template Dump:
Formatted Message:
LPD job submit requested - Status $status Printer $printer
Event Data Items:
Event Name : sys.unix.print.lpd.job.submit.request
Priority : 200
Format : LPD job submit requested - Status $status Printer
$printer
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.print.pxc
Explanation:
Event class name for all printing events related to the Advanced
Printing Software subsystem.
Template Dump:
Formatted Message:
PXC printing event
Event Data Items:
Event Name : sys.unix.print.pxc
Priority : 200
Format : PXC printing event
Reference : cat:evmexp.cat:1100
Variable Items:
None
To Index
*** EVENT sys.unix.proc.process_terminated
Explanation:
This event is posted by the kernel when a process which has been
selected for process termination events terminates. Process
termination events are provided to support high availability
product requirements, and are not intended for general use.
Template Dump:
Formatted Message:
Process 0 terminated
Event Data Items:
Event Name : sys.unix.proc.process_terminated
Priority : 200
Format : Process $terminated_pid terminated
Reference : cat:evmexp.cat:1300
Variable Items:
terminated_pid (UINT32) = 0
To Index
*** EVENT sys.unix.psm.category.create
Explanation:
This event is posted by the kernel Process Set Manager when a
category is created in the process set.
Template Dump:
Formatted Message:
PSM category unknown created on node -
Event Data Items:
Event Name : sys.unix.psm.category.create._catname.unknown
Cluster Event : False
Priority : 201
Format : PSM category $_catname created on node @host_name
Reference : cat:evmexp.cat:1900
Variable Items:
_catname (STRING) = "unknown"
To Index
*** EVENT sys.unix.psm.category.remove
Explanation:
This event is posted by the kernel Process Set Manager when a
category is removed from the process set.
Template Dump:
Formatted Message:
PSM category unknown removed from node -
Event Data Items:
Event Name : sys.unix.psm.category.remove._catname.unknown
Cluster Event : False
Priority : 211
Format : PSM category $_catname removed from node @host_name
Reference : cat:evmexp.cat:1900
Variable Items:
_catname (STRING) = "unknown"
To Index
*** EVENT sys.unix.psm.instance.create
Explanation:
This event is posted by the kernel Process Set Manager when a
member is added to a category in the process set.
Template Dump:
Formatted Message:
PSM instance 0 created in category unknown on node -
Event Data Items:
Event Name : sys.unix.psm.instance.create._catname.unknown._pid.0
Cluster Event : True
Priority : 202
Format : PSM instance $_pid created in category $_catname on
node @host_name
Reference : cat:evmexp.cat:1900
Variable Items:
_catname (STRING) = "unknown"
_pid (UINT32) = 0
To Index
*** EVENT sys.unix.psm.instance.exited
Explanation:
This event is posted by the kernel Process Set Manager when a
member of the process set terminates.
Template Dump:
Formatted Message:
PSM instance 0 exited in category unknown on node - with exit code 0
Event Data Items:
Event Name : sys.unix.psm.instance.exited._catname.unknown._pid.0
Cluster Event : True
Priority : 300
Format : PSM instance $_pid exited in category $_catname on
node @host_name with exit code $exitcode
Reference : cat:evmexp.cat:1900
Variable Items:
_catname (STRING) = "unknown"
_pid (UINT32) = 0
exitcode (UINT32) = 0
To Index
*** EVENT sys.unix.psm.instance.remove
Explanation:
This event is posted by the kernel Process Set Manager when a
member is removed from a category in the process set.
Template Dump:
Formatted Message:
PSM instance 0 removed from category unknown on node -
Event Data Items:
Event Name : sys.unix.psm.instance.remove._catname.unknown._pid.0
Cluster Event : True
Priority : 212
Format : PSM instance $_pid removed from category $_catname on
node @host_name
Reference : cat:evmexp.cat:1900
Variable Items:
_catname (STRING) = "unknown"
_pid (UINT32) = 0
To Index
*** EVENT sys.unix.psm.set.create
Explanation:
This event is posted by the kernel Process Set Manager when the
process set is created.
Template Dump:
Formatted Message:
PSM set created on node -
Event Data Items:
Event Name : sys.unix.psm.set.create
Cluster Event : False
Priority : 200
Format : PSM set created on node @host_name
Reference : cat:evmexp.cat:1900
Variable Items:
None
To Index
*** EVENT sys.unix.psm.set.remove
Explanation:
This event is posted by the kernel Process Set Manager when the
process set is removed.
Template Dump:
Formatted Message:
PSM set removed from node -
Event Data Items:
Event Name : sys.unix.psm.set.remove
Cluster Event : False
Priority : 210
Format : PSM set removed from node @host_name
Reference : cat:evmexp.cat:1900
Variable Items:
None
To Index
*** EVENT sys.unix.runsyscheck
Explanation:
Events in this category are posted by the
/usr/share/sysman/bin/runsyscheck script.
Template Dump:
Formatted Message:
runsyscheck base event
Event Data Items:
Event Name : sys.unix.runsyscheck
Priority : 200
Format : runsyscheck base event
Reference : cat:evmexp.cat:1750
Variable Items:
None
To Index
*** EVENT sys.unix.runsyscheck.process.not_found
Explanation:
This event is posted by the /usr/share/sysman/bin/runsyscheck
script to indicate that /usr/sbin/sys_check could not be found.
Template Dump:
Formatted Message:
runsyscheck: Process "" could not be found on localhost
Event Data Items:
Event Name : sys.unix.runsyscheck.process.not_found
Priority : 300
Format : runsyscheck: Process "$_process" could not be found on
$target
Reference : cat:evmexp.cat:1750
Variable Items:
_process (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.runsyscheck.process.started
Explanation:
This event is posted by the /usr/share/sysman/bin/runsyscheck
script to indicate that sys_check has been started. The
runsyscheck script runs sys_check and makes the sys_check output
available to Insight Manager. There is a runsyscheck entry in the
root crontab file that runs sys_check at 3:00 a.m. every Sunday
night. By default this entry is commented out.
See the sys_check(8), insight_manager(5) and crontab(1) reference pages for more information.
Template Dump:
Formatted Message:
runsyscheck: started process "" on localhost
Event Data Items:
Event Name : sys.unix.runsyscheck.process.started
Priority : 200
Format : runsyscheck: started process "$_process" on $target
Reference : cat:evmexp.cat:1750
Variable Items:
_process (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.runsyscheck.process.terminated.error
Explanation:
This event is posted by the /usr/share/sysman/bin/runsyscheck
script to indicate that sys_check has terminated with errors. If
sys_check does not complete successfully, the sys_check output will
not be made available to Insight Manager.
Action: Review the sys_check log file to determine the reason for the failure. The name of the log file is located in the event variable "log_filename".
Template Dump:
Formatted Message:
runsyscheck: Process "" terminated with errors on localhost
Event Data Items:
Event Name : sys.unix.runsyscheck.process.terminated.error
Priority : 300
Format : runsyscheck: Process "$_process" terminated with
errors on $target
Reference : cat:evmexp.cat:1750
Variable Items:
_process (STRING) = ""
target (STRING) = "localhost"
exit_code (INT32) = 0
log_filename (STRING) = ""
To Index
*** EVENT sys.unix.runsyscheck.process.terminated.success
Explanation:
This event is posted by the /usr/share/sysman/bin/runsyscheck
script to indicate that sys_check has completed successfully.
After sys_check terminates successfully, the runsyscheck script
makes the sys_check output available to Insight Manager.
See the sys_check(8) and insight_manager(5) reference pages for more information.
Template Dump:
Formatted Message:
runsyscheck: Process "" terminated successfully on localhost
Event Data Items:
Event Name : sys.unix.runsyscheck.process.terminated.success
Priority : 200
Format : runsyscheck: Process "$_process" terminated
successfully on $target
Reference : cat:evmexp.cat:1750
Variable Items:
_process (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.security.authorization.denied
Explanation:
This event may be posted by various system components to record
when a user has requested authorization to perform an action, and
the request has been denied. The contents of the event define the
action.
Security events should be monitored by the System Administrator.
Template Dump:
Formatted Message:
: Authorization for denied to
Event Data Items:
Event Name : sys.unix.security.authorization.denied
Priority : 200
Format : $component: Authorization for $authname denied to
$username
Reference : cat:evmexp.cat:1400
Variable Items:
component (STRING) = ""
authname (STRING) = ""
username (STRING) = ""
To Index
*** EVENT sys.unix.security.authorization.granted
Explanation:
This event may be posted by various system components to record
when a user has been given authorization to perform specific
action. The contents of the event define the action.
Security events should be monitored by the System Administrator.
Template Dump:
Formatted Message:
: Authorization for granted to
Event Data Items:
Event Name : sys.unix.security.authorization.granted
Priority : 200
Format : $component: Authorization for $authname granted to
$username
Reference : cat:evmexp.cat:1400
Variable Items:
component (STRING) = ""
authname (STRING) = ""
username (STRING) = ""
To Index
*** EVENT sys.unix.security.privilege.denied
Explanation:
This event may be posted by various system components to record
when a user has requested a privilege, and the request has been
denied. The contents of the event define the privilege.
Security events should be monitored by the System Administrator.
Template Dump:
Formatted Message:
: Privilege denied to
Event Data Items:
Event Name : sys.unix.security.privilege.denied
Priority : 200
Format : $component: Privilege $privname denied to $username
Reference : cat:evmexp.cat:1400
Variable Items:
component (STRING) = ""
privname (STRING) = ""
username (STRING) = ""
To Index
*** EVENT sys.unix.security.privilege.granted
Explanation:
This event may be posted by various system components to record
when a privilege has been granted to a user. The contents of the
event define the privilege.
Security events should be monitored by the System Administrator.
Template Dump:
Formatted Message:
: Privilege granted to
Event Data Items:
Event Name : sys.unix.security.privilege.granted
Priority : 200
Format : $component: Privilege $privname granted to $username
Reference : cat:evmexp.cat:1400
Variable Items:
component (STRING) = ""
privname (STRING) = ""
username (STRING) = ""
To Index
*** EVENT sys.unix.sys_check
Explanation:
Events in this category are posted by the problem reporting and
escalation program, sys_check. See the sys_check(8) reference page
for more information.
Template Dump:
Formatted Message:
sys_check base event
Event Data Items:
Event Name : sys.unix.sys_check
Priority : 200
Format : sys_check base event
Reference : cat:evmexp.cat:1600
Variable Items:
None
To Index
*** EVENT sys.unix.sys_check.warning
Explanation:
Events in this category are posted by the problem reporting and
escalation program, sys_check. Events are generated and named
dynamically by sys_check according to the conditions it finds, and
the full name and contents of each event define the condition and
any necessary action.
See the sys_check(8) reference page for more information.
Template Dump:
Formatted Message:
sys_check warning: [shmsg]
Event Data Items:
Event Name : sys.unix.sys_check.warning
Priority : 200
Format : sys_check warning: $shmsg
Reference : cat:evmexp.cat:1600
Variable Items:
shmsg (STRING) = "[shmsg]"
lnmsg (STRING) = "[lnmsg]"
To Index
*** EVENT sys.unix.syslog
Explanation:
Syslog events are posted by system or user components to report a
change of status. The text of the message indicates the reason for
the event.
Template Dump:
Formatted Message:
Syslog base event
Event Data Items:
Event Name : sys.unix.syslog
Priority : 200
Format : Syslog base event
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.auth
Explanation:
Syslog authorization events are posted by Security Integration
Architecture (SIA) components to report actions such as granting of
superuser privileges to a user through the "su" command, or refusal
to grant access.
Authorization events should be monitored by the System Administrator.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.auth":
Event Data Items:
Event Name : sys.unix.syslog.auth
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.cron
Explanation:
Syslog cron events are posted by the clock daemon. The text of the
message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.cron":
Event Data Items:
Event Name : sys.unix.syslog.cron
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.daemon
Explanation:
Syslog daemon events are posted by system daemons to alert the
administrator to an unusual condition. The user name field usually
indicates which daemon posted the event. The text of the message
indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.daemon":
Event Data Items:
Event Name : sys.unix.syslog.daemon
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.kern
Explanation:
Syslog kernel events are posted when any kernel component prints a
message. Messages are routed through syslog to the system console,
and may also be stored in the syslog event log files.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.kern":
Event Data Items:
Event Name : sys.unix.syslog.kern
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local0
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local0":
Event Data Items:
Event Name : sys.unix.syslog.local0
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local1
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local1":
Event Data Items:
Event Name : sys.unix.syslog.local1
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local2
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local2":
Event Data Items:
Event Name : sys.unix.syslog.local2
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local3
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local3":
Event Data Items:
Event Name : sys.unix.syslog.local3
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local4
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local4":
Event Data Items:
Event Name : sys.unix.syslog.local4
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local5
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local5":
Event Data Items:
Event Name : sys.unix.syslog.local5
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local6
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local6":
Event Data Items:
Event Name : sys.unix.syslog.local6
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.local7
Explanation:
Syslog "local" events are defined by local site applications. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.local7":
Event Data Items:
Event Name : sys.unix.syslog.local7
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.lpr
Explanation:
Syslog printer events are posted by the print subsystem to record
certain actions. The text of the message indicates the reason for
the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.lpr":
Event Data Items:
Event Name : sys.unix.syslog.lpr
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.mail
Explanation:
Syslog mail events are posted by the mail subsystem. These events
mostly record message traffic, and are intended for monitoring and
tracking purposes.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.mail":
Event Data Items:
Event Name : sys.unix.syslog.mail
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.mark
Explanation:
Syslog mark events are posted periodically by the syslog daemon to
indicate that the system is operational.
Because the mark events are usually logged in the syslog log file, it is possible get information about any extended periods of system down-time by examining the log. Syslog minimizes the storage used by consecutive mark events by storing a single "Last event repeated 'n' times" message.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.mark":
Event Data Items:
Event Name : sys.unix.syslog.mark
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.megasafe
Explanation:
Syslog megasafe events are posted by the AdvFS file system. The
text of the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.megasafe":
Event Data Items:
Event Name : sys.unix.syslog.megasafe
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.news
Explanation:
Syslog news events are posted by the news facility. The text of
the message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.news":
Event Data Items:
Event Name : sys.unix.syslog.news
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.syslog
Explanation:
Syslog "syslog" events are posted by the syslog daemon to alert the
administrator to certain notable events, such as a restart or log
change. The text of the message indicates the reason for the
event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.syslog":
Event Data Items:
Event Name : sys.unix.syslog.syslog
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.user
Explanation:
Syslog user events may be posted by application programs, or by
individual users using the logger(1) command. The text of the
message indicates the reason for the event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.user":
Event Data Items:
Event Name : sys.unix.syslog.user
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.syslog.uucp
Explanation:
Syslog "uucp" events are posted by the uucp communication
subsystem. The text of the message indicates the reason for the
event.
Template Dump:
Formatted Message:
Unformatted event "sys.unix.syslog.uucp":
Event Data Items:
Event Name : sys.unix.syslog.uucp
Priority : 200
Reference : cat:evmexp.cat:200
Variable Items:
None
To Index
*** EVENT sys.unix.sysman
Explanation:
Events whose names begin with "sys.unix.sysman" are posted by the
System Management subsystem, to report changes of state.
Template Dump:
Formatted Message:
System Management base event
Event Data Items:
Event Name : sys.unix.sysman
Priority : 200
Format : System Management base event
Reference : cat:evmexp.cat:600
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.disable_fail
Explanation:
This informational event is posted by the automatic deallocation
facility which is executed in response to an indictment event.
This event is posted to inform the user that the `disable`
operation on the indicted component failed.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The event contains the following variables:
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the indicted component.
- The reason event variable contains the return status from the disable command.
Action: This event is indicative of an internal software error or failure to set a system attribute, and most likely is not related to the fact that the component was indicted. Contact your service provider.
Template Dump:
Formatted Message:
Auto-deallocate utility: Failed to disable indicted component (HWID=0).
See reason event variable for further details
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.disable_fail.
_hwid.0
Priority : 500
Format : Auto-deallocate utility: Failed to disable indicted
component $_hwcomponent (HWID=$_hwid). See reason
event variable for further details
Reference : cat:evmexp.cat:600
Variable Items:
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
reason (STRING) = ""
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.offline_attempt
Explanation:
This informational event is posted by the automatic deallocation
facility which is executed in response to an indictment event.
This event is posted to inform the user that all policy conditions
were satisfied and that the automatic deallocation facility is
attempting to perform an `offline` operation on the indicted
component.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The event contains the following variables:
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the indicted component.
Action: No action required.
Template Dump:
Formatted Message:
Auto-deallocate utility: Attempting to offline indicted component (HWID=0)
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.offline_attem
pt._hwid.0
Priority : 500
Format : Auto-deallocate utility: Attempting to offline
indicted component $_hwcomponent (HWID=$_hwid)
Reference : cat:evmexp.cat:600
Variable Items:
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.offline_fail
Explanation:
This informational event is posted by the automatic deallocation
facility which is executed in response to an indictment event.
This event is posted to inform the user that the `offline`
operation on the indicted component did not execute successfully.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The automatic deallocation facility could fail to offline an indicted CPU for several reasons.
Some of the reasons are:
1. If there are processes bound to the indicted CPU and policy determines that the indicted CPU not be taken offline, the CPU will not be taken offline. For more information on binding processes to a CPU, refer to runon(1).
2. If there are processes bound to the Resource Affinity Domain (RAD), and the last running CPU in the RAD has been indicted, the automatic deallocation user-defined policy may prohibit the offline attempt of this CPU. For more information on binding processes to a RAD, refer to runon(1).
The event contains the following variables:
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the indicted component.
- The reason event variable specifies the reason for the failure of the `offline` operation on the indicted component.
Action: Refer to the reason event variable for an indication of the failure.
Template Dump:
Formatted Message:
Auto-deallocate utility: Failed to offline indicted component (HWID=0).
See reason event variable for further details
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.offline_fail.
_hwid.0
Priority : 500
Format : Auto-deallocate utility: Failed to offline indicted
component $_hwcomponent (HWID=$_hwid). See reason
event variable for further details
Reference : cat:evmexp.cat:600
Variable Items:
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
reason (STRING) = ""
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.policy_evaluation.failure
Explanation:
This informational event is posted by the automatic deallocation
facility, which is executed in response to an indictment event.
This event is posted to inform users that some of the evaluated
policy conditions were not satisfied at the time the indictment
event was received for the component. As a result, the indicted
component was not removed from future use by the operating system.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The policy values that determine whether or not to remove the indicted component from future use by the operating system are:
1. Current time within allowed time bounds
2. Indictment probability within allowed range
3. Whether the user supplied script (if any) executed successfully.
The event contains the following variables:
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the hardware component.
- The time_within_bounds_test event variable displays one of two values: `PASS` or `FAIL`. If the time of day when automatic deallocation is attempted falls within the allowed range specified in the policy settings, then this variable will have the value 'PASS', otherwise this variable will have the value 'FAIL'.
- The user_supplied_script_test event variable displays one of two values: `PASS` or `FAIL`. If the user supplied script failed for any reason, this variable will have the value 'FAIL'.
For the user-defined script to execute successfully, the following conditions must be satisfied:
1. The script must exist in the directory specified
2. The script must be executable
3. The script must be owned by super-user (root)
4. Upon execution, the script must return 0 to indicate success
- The probability_test event variable displays one of two values: `PASS` or `FAIL`. If the indictment probability of the failed component is within the allowed range specified in the policy settings, this variable will display the value 'PASS'; otherwise this variable will display the value 'FAIL'.
Action: Review the event variables to determine which policy evaluation tests failed. Note that the indicted component has not been automatically taken offline and powered off.
Template Dump:
Formatted Message:
Auto-deallocate utility: Some of the policy conditions for
auto-deallocation of indicted component were not met (HWID=0)
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.policy_evalua
tion.failure._hwid.0
Priority : 400
Format : Auto-deallocate utility: Some of the policy conditions
for auto-deallocation of indicted component
$_hwcomponent were not met (HWID=$_hwid)
Reference : cat:evmexp.cat:600
Variable Items:
_hwcomponent (STRING) = ""
_hwid (UINT64) = 0
category (STRING) = ""
time_within_bounds_test (STRING) = ""
user_supplied_script_test (STRING) = ""
probability_test (STRING) = ""
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.power_off_attempt
Explanation:
This informational event is posted by the automatic deallocation
facility which is executed in response to an indictment event.
This event is posted to inform the user that the automatic
deallocation facility is attempting to perform a `power off`
operation on the indicted component.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The event contains the following variables:
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the indicted component.
Action: No action required.
Template Dump:
Formatted Message:
Auto-deallocate utility: Attempting to power-off indicted component
(HWID=0)
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.power_off_att
empt._hwid.0
Priority : 500
Format : Auto-deallocate utility: Attempting to power-off
indicted component $_hwcomponent (HWID=$_hwid)
Reference : cat:evmexp.cat:600
Variable Items:
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.power_off_fail
Explanation:
This informational event is posted by the automatic deallocation
facility utility which is executed in response to an indictment
event. This event is posted to inform the user that the `power
off` operation on the indicted component failed.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The event contains the following variables:
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the indicted component.
- The reason event variable specifies the reason for the failure of the `power off` operation on the indicted component.
Action: Refer to the reason event variable for an indication of the failure. It may be necessary to contact your service provider.
Template Dump:
Formatted Message:
Auto-deallocate utility: Failed to power off indicted component (HWID=0).
See reason event variable for further details
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.power_off_fai
l._hwid.0
Priority : 500
Format : Auto-deallocate utility: Failed to power off indicted
component $_hwcomponent (HWID=$_hwid). See reason
event variable for further details
Reference : cat:evmexp.cat:600
Variable Items:
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
reason (STRING) = ""
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.user_supplied_script.failure
Explanation:
This event is posted by the automatic deallocation facility, which
is executed in response to an indictment event. This event is
posted to inform users that the user-supplied script specified in
the policy configuration file failed to execute.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The following conditions must be satisfied in order for the user-supplied script to execute successfully:
1. The script must exist in the directory specified
2. The script must be executable
3. The script must be owned by super-user (root)
4. Upon execution, the script must return 0 to indicate success
If the script does not execute successfully, the automatic deallocation facility will not prevent further use of the indicted component by the operating system.
The event contains the following variables:
- The user_script event variable refers to the user-supplied script specified in the policy configuration file. The user_script variable contains the absolute path to the user-supplied script.
- The _hwcomponent event variable refers to the hardware component's name and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the hardware component.
Action: Review the conditions for success listed above. Likely causes are that the user-supplied script does not exist, does not have the right permissions, or returned a non-zero value for a valid reason.
Template Dump:
Formatted Message:
Auto-deallocate utility: User supplied script failed to execute for
indicted component (HWID=0)
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.user_supplied
_script.failure._hwid.0
Priority : 400
Format : Auto-deallocate utility: User supplied script
$user_script failed to execute for indicted component
$_hwcomponent (HWID=$_hwid)
Reference : cat:evmexp.cat:600
Variable Items:
user_script (STRING) = ""
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.auto_deallocate.component.user_supplied_script.success
Explanation:
This informational event is posted by the automatic deallocation
facility, which is executed in response to an indictment event.
This event is posted to indicate that the user supplied script
specified in the policy configuration file executed successfully.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The event contains the following variables:
- The user_script event variable refers to the user-supplied script specified in the policy configuration file. The user_script variable contains the absolute path to the user-supplied script.
- The _hwcomponent event variable refers to the hardware component's name, and serves as an identifier for the hardware component that was indicted.
- The category event variable refers to the hardware category to which the hardware component belongs.
- The _hwid event variable refers to the hardware id of the hardware component.
Action: No action required.
Template Dump:
Formatted Message:
Auto-deallocate utility: User supplied script executed successfully for
indicted component (HWID=0)
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.component.user_supplied
_script.success._hwid.0
Priority : 200
Format : Auto-deallocate utility: User supplied script
$user_script executed successfully for indicted
component $_hwcomponent (HWID=$_hwid)
Reference : cat:evmexp.cat:600
Variable Items:
user_script (STRING) = ""
_hwcomponent (STRING) = ""
category (STRING) = ""
_hwid (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.auto_deallocate.internal_error
Explanation:
This warning event is posted by the automatic deallocation facility
which is executed in response to an indictment event. This event
is posted to inform the user that an internal error has occurred in
the execution of the automatic deallocation facility.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to `offline` and `power-off` the indicted component.
The event contains the following variables:
- The command event variable is used to specify the internal command that failed execution.
- The reason event variable specifies the reason for the failure of the internal command on the indicted component.
Action: This event is indicative of an internal software error, and most likely is not related to the fact that a component was indicted. Review the command and reason event variables and contact your service provider.
Template Dump:
Formatted Message:
Auto-deallocate utility: Failed to execute internal command
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.internal_error
Priority : 200
Format : Auto-deallocate utility: Failed to execute internal
command $command
Reference : cat:evmexp.cat:600
Variable Items:
command (STRING) = ""
reason (STRING) = ""
To Index
*** EVENT sys.unix.sysman.auto_deallocate.memory_page.mapout_attempt
Explanation:
This informational event is posted by the automatic deallocation
facility, which is executed in response to an indictment event.
This event is posted to inform users that all the policy conditions
were satisfied and that the automatic deallocation facility is
attempting to retire the memory page containing the indicted
physical address.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to retire the memory page containing the indicted physical address, thus preventing the operating system from using that memory page in the future.
The event contains the following variables:
- The _physical_address event variable is the physical memory address that is associated with the memory failure.
Action: No action required.
Template Dump:
Formatted Message:
Auto-deallocate utility: Attempting to map-out memory page containing
indicted physical address 0
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.memory_page.mapout_atte
mpt._physical_address.0
Priority : 200
Format : Auto-deallocate utility: Attempting to map-out memory
page
containing indicted physical address $_physical_address
Reference : cat:evmexp.cat:600
Variable Items:
_physical_address (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.auto_deallocate.memory_page.policy_evaluation.failure
Explanation:
This informational event is posted by the automatic deallocation
facility, which is executed in response to an indictment event.
This event is posted to inform users that some of the evaluated
policy conditions were not satisfied at the time the indictment
event was received for the physical address. As a result, the
memory page containing the indicted physical address was not
retired from future use by the operating system.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to retire the memory page containing the indicted physical address, thus preventing the operating system from using that memory page in the future.
The policy values that determine whether or not the automatic deallocation facility will attempt to retire the indicted memory page are:
1. Current time within allowed time bounds
2. Indictment probability within allowed range
3. Whether the user supplied script (if any) executed successfully
The event contains the following variables:
- The _physical_address event variable is the physical memory address that is associated with the memory failure.
- The time_within_bounds_test event variable displays one of two values: `PASS` or `FAIL`. If the time of day when deallocation is attempted falls within the allowed range specified in the policy settings, then this variable will display the value `PASS`, otherwise this variable will display the value `FAIL`.
- The user_supplied_script_test event variable displays one of two values: `PASS` or `FAIL`. If the user supplied script failed for any reason, this variable will display the value 'FAIL'.
For the user-defined script to execute successfully, the following conditions must be satisfied:
1. The script must exist in the directory specified
2. The script must be executable
3. The script must be owned by super-user (root)
4. Upon execution, the script must return 0 to indicate success
- The probability_test event variable displays one of two values: `PASS` or `FAIL`. If the indictment probability of the failed component is within the allowed range specified in the policy settings, this variable will display the value 'PASS', otherwise this variable will display the value 'FAIL'.
Action: Review the event variables to determine which policy evaluation tests failed. Note that the memory page containing the indicted physical address has not been automatically deallocated.
Template Dump:
Formatted Message:
Auto-deallocate utility: Some policy conditions for auto-deallocation of
indicted physical address 0 were not met successfully
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.memory_page.policy_eval
uation.failure._physical_address.0
Priority : 200
Format : Auto-deallocate utility: Some policy conditions for
auto-deallocation of indicted physical address
$_physical_address were not met successfully
Reference : cat:evmexp.cat:600
Variable Items:
_physical_address (UINT64) = 0
time_within_bounds_test (STRING) = ""
user_supplied_script_test (STRING) = ""
probability_test (STRING) = ""
To Index
*** EVENT sys.unix.sysman.auto_deallocate.memory_page.user_supplied_script.failure
Explanation:
This informational event is posted by the automatic deallocation
facility, which is executed in response to an indictment event.
This event is posted to indicate that the user supplied script
specified in the policy configuration file failed to execute.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to retire the memory page containing the indicted physical address, thus preventing the operating system from using that memory page in the future.
For the user-defined script to execute successfully, the following conditions must be satisfied:
1. The script must exist in the directory specified
2. The script must be executable
3. The script must be owned by super-user (root)
4. Upon execution, the script must return 0 to indicate success
If the script does not execute successfully, the automatic deallocation facility will not attempt to retire the memory page containing the indicted physical address.
The event contains the following variables:
- The user_script event variable refers to the user-supplied script specified in the policy configuration file. The user_script variable contains the absolute path to the user-supplied script.
- The _physical_address event variable is the physical memory address that is associated with the memory failure.
Action: Review the conditions for success listed above. Likely causes are that the user-supplied script does not exist, does not have the right permissions, or returned a non-zero value for a valid reason.
Template Dump:
Formatted Message:
Auto-deallocate utility: User supplied script failed to execute for
indicted physical address 0
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.memory_page.user_suppli
ed_script.failure._physical_address.0
Priority : 400
Format : Auto-deallocate utility: User supplied script
$user_script failed to execute for indicted physical
address $_physical_address
Reference : cat:evmexp.cat:600
Variable Items:
user_script (STRING) = ""
_physical_address (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.auto_deallocate.memory_page.user_supplied_script.success
Explanation:
This informational event is posted by the automatic deallocation
facility, which is executed in response to an indictment event.
This event is posted to indicate that the user-supplied script
specified in the policy configuration file executed successfully.
The automatic deallocation facility is launched automatically after consulting user-defined policy as specified in the cluster-shared file /etc/olar.config.common and the member-specific file /etc/olar.config. Based on the values specified in the policy configuration files, the automatic deallocation facility will attempt to retire the memory page containing the indicted physical address, thus preventing the operating system from using that memory page in the future.
The event contains the following variables:
- The user_script event variable refers to the user-supplied script specified in the policy configuration file. The user_script variable contains the absolute path to the user-supplied script.
- The _physical_address event variable is the physical memory address that is associated with the memory failure.
Action: No action required.
Template Dump:
Formatted Message:
Auto-deallocate utility: User supplied script executed successfully for
indicted physical address 0
Event Data Items:
Event Name : sys.unix.sysman.auto_deallocate.memory_page.user_suppli
ed_script.success._physical_address.0
Priority : 200
Format : Auto-deallocate utility: User supplied script
$user_script executed successfully for indicted
physical address $_physical_address
Reference : cat:evmexp.cat:600
Variable Items:
user_script (STRING) = ""
_physical_address (UINT64) = 0
To Index
*** EVENT sys.unix.sysman.diskconfig.alias
Explanation:
This event indicates that the diskconfig application has created an
alias for a disk device.
Template Dump:
Formatted Message:
Alias "$alias" has been made for device "$device"
Event Data Items:
Event Name : sys.unix.sysman.diskconfig.alias
Priority : 200
Format : Alias "$alias" has been made for device "$device"
Reference : cat:evmexp.cat:600
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.diskconfig.swap
Explanation:
This event indicates that the diskconfig application has labeled
this partition to be 'swap'.
Template Dump:
Formatted Message:
Swap space is reserved on partition "$partition" of device "$device"
Event Data Items:
Event Name : sys.unix.sysman.diskconfig.swap
Priority : 200
Format : Swap space is reserved on partition "$partition" of
device "$device"
Reference : cat:evmexp.cat:600
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.generic.config.fail
Explanation:
This event indicates that an application tried to configure a
configurable object and the configuration failed for the specified
reason. Check input parameters and retry.
Template Dump:
Formatted Message:
could not configure "" on localhost because
Event Data Items:
Event Name : sys.unix.sysman.generic.config.fail
Priority : 500
Format : $app could not configure "$name" on $target because
$reason
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
reason (STRING) = ""
To Index
*** EVENT sys.unix.sysman.generic.config.ok
Explanation:
This event indicates that an application tried to configure a
configurable object and the configuration succeeded.
Template Dump:
Formatted Message:
configured "" successfully on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.config.ok
Priority : 200
Format : $app configured "$name" successfully on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.deconfig.fail
Explanation:
This event indicates that an application tried to deconfigure a
configurable object, and that the deconfiguration failed for the
noted reason.
Action: Check the command's input parameters and retry.
Template Dump:
Formatted Message:
could not deconfigure "" on localhost because
Event Data Items:
Event Name : sys.unix.sysman.generic.deconfig.fail
Priority : 500
Format : $app could not deconfigure "$name" on $target because
$reason
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
reason (STRING) = ""
To Index
*** EVENT sys.unix.sysman.generic.deconfig.ok
Explanation:
This event indicates that an application tried to deconfigure a
configurable object, and the deconfiguration succeeded.
Template Dump:
Formatted Message:
deconfigured "" successfully on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.deconfig.ok
Priority : 200
Format : $app deconfigured "$name" successfully on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.file
Explanation:
This event indicates that an application has performed a specific
action on a file.
Template Dump:
Formatted Message:
performed action "" on file "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.file
Priority : 200
Format : $app performed action "$action" on file "$name" on
$target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
action (STRING) = ""
To Index
*** EVENT sys.unix.sysman.generic.file.create
Explanation:
This event indicates that an application has created the specified
file.
Template Dump:
Formatted Message:
created file "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.file.create
Priority : 200
Format : $app created file "$name" on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.file.modify
Explanation:
This event indicates that an application has modified the specified
file.
Template Dump:
Formatted Message:
modified file "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.file.modify
Priority : 200
Format : $app modified file "$name" on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.file.remove
Explanation:
This event indicates that an application has removed the specified
file.
Template Dump:
Formatted Message:
removed file "" from localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.file.remove
Priority : 200
Format : $app removed file "$name" from $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.process
Explanation:
This event indicates that an application is about to perform an
action on a command or process.
Template Dump:
Formatted Message:
performed action "" on process "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.process
Priority : 200
Format : $app performed action "$action" on process "$name" on
$target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
action (STRING) = ""
To Index
*** EVENT sys.unix.sysman.generic.process.restart
Explanation:
This event indicates that an application has restarted a command.
Template Dump:
Formatted Message:
restarted process "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.process.restart
Priority : 200
Format : $app restarted process "$name" on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.process.start
Explanation:
This event indicates that an application has started a command.
Template Dump:
Formatted Message:
started process "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.process.start
Priority : 200
Format : $app started process "$name" on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.generic.process.stop
Explanation:
This event indicates that an application has started a command.
Template Dump:
Formatted Message:
stopped process "" on localhost
Event Data Items:
Event Name : sys.unix.sysman.generic.process.stop
Priority : 200
Format : $app stopped process "$name" on $target
Reference : cat:evmexp.cat:600
Variable Items:
app (STRING) = ""
name (STRING) = ""
target (STRING) = "localhost"
To Index
*** EVENT sys.unix.sysman.station
Explanation:
Events whose names begin with "sys.unix.sysman.station" are posted
by the SysMan Station. Refer to the event details for information
about the event.
Template Dump:
Formatted Message:
SysMan Station event
Event Data Items:
Event Name : sys.unix.sysman.station
Priority : 200
Format : SysMan Station event
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.station.client
Explanation:
This is the base event name for events posted on behalf of SysMan
Station clients.
Template Dump:
Formatted Message:
SysMan Station client event
Event Data Items:
Event Name : sys.unix.sysman.station.client
Cluster Event : True
Priority : 200
Format : SysMan Station client event
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.station.client.clear
Explanation:
This event indicates that the SysMan Station client requested that
the state of the specified object be changed to "normal".
Template Dump:
Formatted Message:
SysMan Station: User, none, cleared status on none in attention group none
Event Data Items:
Event Name : sys.unix.sysman.station.client.clear
Priority : 200
Format : SysMan Station: User, $user_name, cleared status on
$obj_name in attention group $group
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
user_name (STRING) = "none"
obj_name (STRING) = "none"
group (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.delete
Explanation:
This cluster-wide event is posted by the SysMan Station daemon when
it detects that an object has been removed from the system.
Template Dump:
Formatted Message:
SysMan Station: Object $id_str has been deleted from host -
Event Data Items:
Event Name : sys.unix.sysman.station.delete
Cluster Event : True
Priority : 200
Format : SysMan Station: Object $id_str has been deleted from
host @host_name
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.station.fsa
Explanation:
This is the base event name for events posted by the SysMan Station
file system analysis module (FSA).
Template Dump:
Formatted Message:
SysMan Station file system event
Event Data Items:
Event Name : sys.unix.sysman.station.fsa
Priority : 200
Format : SysMan Station file system event
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.station.fsa.delete
Explanation:
This event indicates that the SysMan Station file system analysis
module (FSA) has determined that a file system has been unmounted.
Template Dump:
Formatted Message:
SysMan Station: FSA object, none, has been removed.
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.delete
Cluster Event : True
Priority : 200
Format : SysMan Station: FSA object, $obj_name, has been
removed.
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
obj_name (STRING) = "none"
obj_id (STRING) = "none"
id_str (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.fsa.delete.master
Explanation:
In a cluster environment, a single SysMan Station daemon is
responsible for performing file system analysis (FSA). This daemon
is referred to to as the "FSA master". This cluster-wide event is
posted by the daemon when the current FSA master relinquishes that
role.
Template Dump:
Formatted Message:
SysMan Station: Cluster member none is no longer the FSA master. A SysMan
Station daemon on another cluster member will become the master.
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.delete.master
Cluster Event : True
Priority : 200
Format : SysMan Station: Cluster member $obj_name is no longer
the FSA master. A SysMan Station daemon on another
cluster member will become the master.
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
obj_name (STRING) = "none"
obj_id (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.fsa.new
Explanation:
This event indicates that the SysMan Station file system analysis
module (FSA) has determined that a file system has been mounted.
Template Dump:
Formatted Message:
SysMan Station: FSA object, none, has been created.
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.new
Priority : 200
Format : SysMan Station: FSA object, $obj_name, has been
created.
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
obj_name (STRING) = "none"
obj_id (STRING) = "none"
id_str (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.fsa.new.master
Explanation:
In a cluster environment, a single SysMan Station daemon is
responsible for performing file system analysis (FSA). This daemon
is referred to to as the "FSA master". This cluster-wide event is
posted by a daemon when it assumes the FSA master role.
Template Dump:
Formatted Message:
SysMan Station: Cluster member none is now responsible for file system
analysis (FSA master).
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.new.master
Priority : 200
Format : SysMan Station: Cluster member $obj_name is now
responsible for file system analysis (FSA master).
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
obj_name (STRING) = "none"
obj_id (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.fsa.nonoptimal
Explanation:
This event indicates that the SysMan Station file system analysis
module (FSA) has determined that a cluster file system (CFS) has
become non-optimal.
Template Dump:
Formatted Message:
SysMan Station: File system, none, is not optimal. The CFS server,
fs_server, is not in the list of DRD servers, none
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.nonoptimal
Cluster Event : True
Priority : 400
Format : SysMan Station: File system, $fs_name, is not optimal.
The CFS server, fs_server, is not in the list of DRD
servers, $drd_servers
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
fs_name (STRING) = "none"
fs_server (STRING) = "none"
drd_servers (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.fsa.optimal
Explanation:
This event indicates that the SysMan Station file system analysis
module (FSA) has determined that a non-optimal cluster file system
(CFS) has become optimal.
Template Dump:
Formatted Message:
SysMan Station: File system, none, is now optimal
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.optimal
Cluster Event : True
Priority : 200
Format : SysMan Station: File system, $fs_name, is now optimal
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
fs_name (STRING) = "none"
fs_server (STRING) = "none"
drd_servers (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.fsa.relocate
Explanation:
This event indicates that the SysMan Station file system analysis
module (FSA) has determined that a file system has been relocated
to another cluster node.
Template Dump:
Formatted Message:
SysMan Station: FSA filesystem, none, has been relocated to $fs_server.
Event Data Items:
Event Name : sys.unix.sysman.station.fsa.relocate
Cluster Event : True
Priority : 200
Format : SysMan Station: FSA filesystem, $fs_name, has been
relocated to $fs_server.
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
fs_name (STRING) = "none"
obj_id (STRING) = "none"
id_str (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.mcl.master
Explanation:
In a cluster environment, a single SysMan Station daemon is
responsible for making cluster-wide data available to its peers in
the other cluster nodes, through the MCL interface. This event
indicates that this responsibility has been assumed by another
SysMan Station daemon.
Template Dump:
Formatted Message:
SysMan Station: Cluster member none is now responsible for cluster-wide
MCL data.
Event Data Items:
Event Name : sys.unix.sysman.station.mcl.master
Priority : 200
Format : SysMan Station: Cluster member $obj_name is now
responsible for cluster-wide MCL data.
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
obj_name (STRING) = "none"
obj_id (STRING) = "none"
To Index
*** EVENT sys.unix.sysman.station.update
Explanation:
This cluster-wide event is posted by the SysMan Station daemon.
The event indicates that there has been a change of state in the
set of objects being managed by the daemon, and that its
serialization files have been updated as a result. In a cluster
environment the event signals the SysMan Station daemons running on
the other cluster members to update their views of the cluster.
Template Dump:
Formatted Message:
SysMan Station: daemon on host - has written new serialization files.
These files allow the daemons to communicate state and topology changes.
Event Data Items:
Event Name : sys.unix.sysman.station.update
Cluster Event : True
Priority : 200
Format : SysMan Station: daemon on host @host_name has written
new serialization files. These files allow the daemons
to communicate state and topology changes.
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.station.update.object
Explanation:
This cluster-wide event is posted by the SysMan Station daemon.
The event indicates that there has been a change of state in an
object (for example, a local disk) being managed by the daemon. In
a cluster environment the event signals the SysMan Station daemons
running on the other cluster members to update the state of the
managed object.
Template Dump:
Formatted Message:
SysMan Station: A local $definition on this cluster member has changed to
state $state
Event Data Items:
Event Name : sys.unix.sysman.station.update.object
Cluster Event : True
Priority : 200
Format : SysMan Station: A local $definition on this cluster
member has changed to state $state
Reference : cat:evmexp_sysman_station.cat:100
Variable Items:
None
To Index
*** EVENT sys.unix.sysman.suitlet.context_changed
Explanation:
This event is posted by a system management application to report a
change in its "focus". The focus (or "context") is the item from
among those managed by the application that is currently the focus
of attention. Changes usually happen as the result of a user
selection. The event is used for synchronization purposes across
system management tools.
Template Dump:
Formatted Message:
Suitlet (ID ) changed context to
Event Data Items:
Event Name : sys.unix.sysman.suitlet.context_changed
Priority : 0
Format : Suitlet $suitlet_type (ID $instance_id) changed
context to $context
Reference : cat:evmexp.cat:600
Variable Items:
context (STRING) = ""
instance_id (STRING) = ""
suitlet_type (STRING) = ""
To Index
*** EVENT sys.unix.sysman.suitlet.set_context
Explanation:
This event serves as a request for a system management application
to focus its attention on a particular item from among those it
manages. The receiving application can choose to ignore or abide
by the request. The event is used for synchronization purposes
across system management tools.
Template Dump:
Formatted Message:
Set suitlet (ID ) context to
Event Data Items:
Event Name : sys.unix.sysman.suitlet.set_context
Priority : 0
Format : Set suitlet $suitlet_type (ID $instance_id) context to
$context
Reference : cat:evmexp.cat:600
Variable Items:
context (STRING) = ""
instance_id (STRING) = ""
suitlet_type (STRING) = ""
To Index
*** EVENT sys.unix.vm.memory_page.mapout.completed
Explanation:
This event is posted by the virtual memory subsystem to indicate
that a bad memory page that was requested to be taken out of
circulation has been successfully mapped out and is no longer in
use.
The _physical_address event variable identifies the physical memory address of the failing location within the memory page.
Note: Pages that have been requested to be taken out of circulation will remain out of circulation if a warm reboot occurs. However, if the system is reset (for example, power cycle or cold reboot) and memory is re-initialized, pages with persistent single bit errors will remain out of circulation but pages that now function without errors will be reused.
Action: No action required.
Template Dump:
Formatted Message:
VM: Memory page containing physical address 0 has been mapped out
Event Data Items:
Event Name : sys.unix.vm.memory_page.mapout.completed._physical_addr
ess.0
Cluster Event : False
Priority : 300
Format : VM: Memory page containing physical address
$_physical_address has been mapped out
Reference : cat:evmexp.cat:2000
Variable Items:
_physical_address (UINT64) = 0
To Index
*** EVENT sys.unix.vm.memory_page.mapout.duplicate
Explanation:
This event is posted by the virtual memory subsystem to indicate
that a request has been made to map out a page that has already
been requested for removal.
The _physical_address event variable identifies the physical memory address of the failing location within the memory page.
Note: Duplicate requests are possible because multiple applications (for example, Compaq Analyze and the Memory Troller) may detect that the same memory page is bad.
Action: No action required.
Template Dump:
Formatted Message:
VM: Duplicate map out request for memory page containing physical address 0
Event Data Items:
Event Name : sys.unix.vm.memory_page.mapout.duplicate._physical_addr
ess.0
Cluster Event : False
Priority : 300
Format : VM: Duplicate map out request for memory page
containing physical address $_physical_address
Reference : cat:evmexp.cat:2000
Variable Items:
_physical_address (UINT64) = 0
To Index
*** EVENT sys.unix.vm.memory_page.mapout.not_possible.outside_vm_managed_pool
Explanation:
This event is posted by the virtual memory subsystem to indicate
that a bad memory page that was requested to be taken out of
circulation could not be mapped out because the page is not managed
by the operating system.
The _physical_address event variable identifies the physical memory address of the failing location within the memory page.
Action: Memory diagnostics should be run to identify the failing memory location. Contact your service provider.
Template Dump:
Formatted Message:
VM: Memory page containing physical address 0 cannot be mapped out because
the page is outside the virtual memory managed pool
Event Data Items:
Event Name : sys.unix.vm.memory_page.mapout.not_possible.outside_vm_
managed_pool._physical_address.0
Cluster Event : False
Priority : 300
Format : VM: Memory page containing physical address
$_physical_address cannot be mapped out because the
page is outside the virtual memory managed pool
Reference : cat:evmexp.cat:2000
Variable Items:
_physical_address (UINT64) = 0
To Index
*** EVENT sys.unix.vm.memory_page.mapout.request
Explanation:
This event is posted by the virtual memory subsystem to indicate
that a request has been made to take a bad memory page out of
circulation. A memory page is deemed bad if there is a high
occurrence of single bit errors (SBEs) within the memory page or if
the Memory Troller detects a double bit error (DBE) within the
memory page.
A mapout completed event will be posted at a later time if the page is successfully mapped out. If the page is not in use, then it will be mapped out the next time an attempt is made to allocate the page. If the page is currently in use, the page will be mapped out the next time the page is deallocated.
The _physical_address event variable identifies the physical memory address of the failing location within the memory page.
Note: Pages that have been requested to be taken out of circulation will remain out of circulation if a warm reboot occurs. However, if the system is reset (for example, power cycle or cold reboot) and memory is re-initialized, pages with persistent single bit errors will remain out of circulation but pages that now function without errors will be reused.
Action: No action required.
Template Dump:
Formatted Message:
VM: Map out request for memory page containing physical address 0
Event Data Items:
Event Name : sys.unix.vm.memory_page.mapout.request._physical_addres
s.0
Cluster Event : False
Priority : 300
Format : VM: Map out request for memory page containing
physical address $_physical_address
Reference : cat:evmexp.cat:2000
Variable Items:
_physical_address (UINT64) = 0
To Index