Translations of this page:

Hersteller

HP-UX

Infos zum Gerät

SNMPTT Config

EVENT hpEMSNormalEvent .1.3.6.1.4.1.11.2.3.1.7.0.1 "Status Events" OK
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Normal Event occurs when the value of the resource is in
a 'normal' state and the threshold condition is not true.
Monitoring requests configured for initial or return
notification may generate this event.  Also, the initial
notification for a Change event is 'normal'.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSNormalEvent
trap, the notification trigger is normal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC
EVENT hpEMSProblemEvent .1.3.6.1.4.1.11.2.3.1.7.0.2 "Status Events" WARNING
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Problem Event occurs when the threshold condition defined
for the resource is true.
A Change Event occurs when the monitored value changes.
Monitoring requests configured for notification when the
value changes may generate this event.
A Poll Event occurs regularly at the configured polling
interval.
An Error Event occurs when the value of a monitored resource
cannot be obtained from the monitor.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSProblemEvent
trap, the notification trigger is abnormal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC
EVENT hpEMSMonitorReboot .1.3.6.1.4.1.11.2.3.1.7.0.3 "Status Events" WARNING
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Monitor Reboot Event occurs when monitors are restarted
due to a system reboot.
The list of resources affected by the restart can be
retrieved on the source node by running:
/opt/resmon/bin/resdata -M <key>
The data passed with the event:
1)  The restart event type, which can be restart or
reboot.  For an EMSMonitorReboot trap, the restart
type is reboot.
2)  The title of the monitor that is restarted.
3)  The command used to restart the monitor.
4)  The name of the vendor that provided the monitor.
5)  The version of the monitor.
6)  The process ID of the restarted monitor process.
7)  The monitor key, which may be used with the -M option
to the resdata command to return the list of resources
being monitored by the restarted monitor.
The list of resources can be retrieved on the source
node by running:
/opt/resmon/bin/resdata -M <monitor key>
Variables:
  1: hpEMSRestartType
  2: hpEMSMonitorTitle
  3: hpEMSCommand
  4: hpEMSVendor
  5: hpEMSVersion
  6: hpEMSPID
  7: hpEMSMonitorKey
EDESC
EVENT hpEMSMonitorRestart .1.3.6.1.4.1.11.2.3.1.7.0.4 "Status Events" OK
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Monitor Restart Event occurs when EMS detects that a
required monitor is no longer running, and restarts the
monitor.
The list of resources affected by the restart can be
retrieved on the source node by running:
/opt/resmon/bin/resdata -M <key>
The data passed with the event:
1)  The restart event type, which can be restart or
reboot.  For an EMSMonitorRestart trap, the restart
type is restart.
2)  The title of the monitor that is restarted.
3)  The command used to restart the monitor.
4)  The name of the vendor that provided the monitor.
5)  The version of the monitor.
6)  The process ID of the restarted monitor process.
7)  The monitor key, which may be used with the -M option
to the resdata command to return the list of resources
being monitored by the restarted monitor.
The list of resources can be retrieved on the source
node by running:
/opt/resmon/bin/resdata -M <monitor key>
Variables:
  1: hpEMSRestartType
  2: hpEMSMonitorTitle
  3: hpEMSCommand
  4: hpEMSVendor
  5: hpEMSVersion
  6: hpEMSPID
  7: hpEMSMonitorKey
EDESC
EVENT hpEMSMonitorRestart .1.3.6.1.4.1.11.2.3.1.7.0.4 "Status Events" OK
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Monitor Restart Event occurs when EMS detects that a
required monitor is no longer running, and restarts the
monitor.
The list of resources affected by the restart can be
retrieved on the source node by running:
/opt/resmon/bin/resdata -M <key>
The data passed with the event:
1)  The restart event type, which can be restart or
reboot.  For an EMSMonitorRestart trap, the restart
type is restart.
2)  The title of the monitor that is restarted.
3)  The command used to restart the monitor.
4)  The name of the vendor that provided the monitor.
5)  The version of the monitor.
6)  The process ID of the restarted monitor process.
7)  The monitor key, which may be used with the -M option
to the resdata command to return the list of resources
being monitored by the restarted monitor.
The list of resources can be retrieved on the source
node by running:
/opt/resmon/bin/resdata -M <monitor key>
Variables:
  1: hpEMSRestartType
  2: hpEMSMonitorTitle
  3: hpEMSCommand
  4: hpEMSVendor
  5: hpEMSVersion
  6: hpEMSPID
  7: hpEMSMonitorKey
EDESC
EVENT hpEMSNormalSevEvent .1.3.6.1.4.1.11.2.3.1.7.0.5 "Status Events" OK
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Problem Event occurs when the threshold condition defined
for the resource is true.
A Change Event occurs when the monitored value changes.
Monitoring requests configured for notification when the
value changes may generate this event.
A Poll Event occurs regularly at the configured polling
interval.
An Error Event occurs when the value of a monitored resource
cannot be obtained from the monitor.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSProblemEvent
trap, the notification trigger is abnormal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC
EVENT hpEMSWarningEvent .1.3.6.1.4.1.11.2.3.1.7.0.6 "Status Events" WARNING
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Problem Event occurs when the threshold condition defined
for the resource is true.
A Change Event occurs when the monitored value changes.
Monitoring requests configured for notification when the
value changes may generate this event.
A Poll Event occurs regularly at the configured polling
interval.
An Error Event occurs when the value of a monitored resource
cannot be obtained from the monitor.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSProblemEvent
trap, the notification trigger is abnormal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC
EVENT hpEMSMinorEvent .1.3.6.1.4.1.11.2.3.1.7.0.7 "Status Events" CRITICAL
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Problem Event occurs when the threshold condition defined
for the resource is true.
A Change Event occurs when the monitored value changes.
Monitoring requests configured for notification when the
value changes may generate this event.
A Poll Event occurs regularly at the configured polling
interval.
An Error Event occurs when the value of a monitored resource
cannot be obtained from the monitor.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSProblemEvent
trap, the notification trigger is abnormal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC
EVENT hpEMSMajorEvent .1.3.6.1.4.1.11.2.3.1.7.0.8 "Status Events" CRITICAL
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Problem Event occurs when the threshold condition defined
for the resource is true.
A Change Event occurs when the monitored value changes.
Monitoring requests configured for notification when the
value changes may generate this event.
A Poll Event occurs regularly at the configured polling
interval.
An Error Event occurs when the value of a monitored resource
cannot be obtained from the monitor.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSProblemEvent
trap, the notification trigger is abnormal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC
EVENT hpEMSCriticalEvent .1.3.6.1.4.1.11.2.3.1.7.0.9 "Status Events" CRITICAL
FORMAT The Event Monitoring Service (EMS) has generated an event  $*
SDESC
The Event Monitoring Service (EMS) has generated an event
for a monitored resource.
A Problem Event occurs when the threshold condition defined
for the resource is true.
A Change Event occurs when the monitored value changes.
Monitoring requests configured for notification when the
value changes may generate this event.
A Poll Event occurs regularly at the configured polling
interval.
An Error Event occurs when the value of a monitored resource
cannot be obtained from the monitor.
The data passed with the event:
1)  The name of the resource being monitored.
2)  The request id, a unique identifier for the
monitoring request.  This value should be used when
using resdata to retrieve additional information
about the event.
3)  The operator used by EMS to determine when event
notifications should be sent.  Possible values
include:  poll, change, >, >=, <, <=, = and !=.
4)  The resource type, which defines the type of value
being monitored.  Possible values include:  string,
enumerated, integer, and float.
5)  The resource value, which is the current value of the
resource being monitored.  It is converted based on
the resource type.
6)  The threshold type (usually the same as the resource
type) defines the type of value configured for the
threshold.  Possible values include: string,
integer, and float.
7)  The threshold value configured for the resource being
monitored.
8)  The user data flag, which indicates whether or not
user data are available.  User data are comments
provided by the user when the request was configured.
User data can be retrieved on the source node by
running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> -u
9)  The monitor data flag, which indicates whether or not
the monitor has additional data regarding the event.
Additional data provided by the resource monitor
can be retrieved on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
10)  The notification trigger indicates if the resource
condition is normal or not.  For an EMSProblemEvent
trap, the notification trigger is abnormal.
11)  The event type indicates the type of notification
being sent.  The different types are:
Poll    - for notification at every interval
Change  - for notification when the value changes
Normal  - for notification when the threshold
condition for the resource is not true
Problem - for notification when the threshold
condition for the resource is true
Error   - for notification when the monitor
encountered an error determining
the resource value
12)  The notify id, a unique identifier for a specific
notification event.  This value should be used when
using resdata to retrieve additional information
about the event.  Monitor data can be retrieved
on the source node by running:
/opt/resmon/bin/resdata -r <resource name> \
-R <request id> [-n <notify id>] -m
Variables:
  1: hpEMSResourceName
  2: hpEMSRequestID
  3: hpEMSOperator
  4: hpEMSResourceType
  5: hpEMSResourceValue
  6: hpEMSThresholdType
  7: hpEMSThresholdValue
  8: hpEMSUserDataFlag
  9: hpEMSMonitorDataFlag
  10: hpEMSNotificationTrigger
  11: hpEMSEventType
  12: hpEMSNotifyID
EDESC

Bemerkung

snmptt/hp-ems.txt · Zuletzt geändert: 2005/11/23 08:37 von crocodile
CC Attribution-Noncommercial-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0