System Event Reference
	Tru64 UNIX Version 5.1B, September 2002

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.

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 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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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 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:

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:

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:

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 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 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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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 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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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 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:

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:

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:

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:

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:

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:

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:

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:

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 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 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:

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 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:

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:

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 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:

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:

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:

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:

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 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 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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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 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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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