HP Operations Manager for Windows

SNMP variables


The variables listed below can be used in most SNMP Interceptor text entry boxes (exceptions are noted). The variables can be used within HP Operations Manager, or passed to external programs. Each variable is shown with the required syntax, but note that it is also often useful to surround the variable with quotation marks, especially if it may return a value that contains spaces.

<$#>
Returns the number of variables in an enterprise-specific SNMP event (generic event 6 Enterprise specific ID). Sample output: 2
<$*>
Returns all variables assigned to the event up to the possible fifteen. Sample output: [1] .1.1 (OctetString): arg1 [2] .1.2 (OctetString): turnip.veg.com
<$@>
Returns the time the event was received as the number of seconds since Jan 1, 1970 using the time_t representation. Sample output: 859479898
<$1>
Returns one or more of the fifteen possible event parameters that are part of an SNMP event. (<$1> returns the first variable, <$2> returns the second variable, and so on.)
<$\>1>
Returns all attributes greater than n as value strings, useful for printing a variable number of arguments. <$\>0> is equivalent to $* without sequence numbers, names, or types. Sample output: bokchoy.veg.com
<$\>+1>
Returns all attributes greater than n as name:value string. Sample output: .1.2: asparagus.veg.com
<$+2>
Returns the nth variable binding as name:value . (Note: not valid in the command box.) Sample output: .1.2: artichoke.veg.com
<$\>-n >
Returns all attributes greater than n as [seq] name (type): value strings. Sample output: [2] .1.2 (OctetString): cauliflower.veg.com
<$-2>
Returns the nth variable binding as [seq] name-type:value . (Note: not valid in Command Box.) Sample output: [2] .1.2 (OctetString): brusselsprouts.veg.com
<$A>
Returns the node which produced the event. Sample output: eggplant.veg.com
<$C>
Returns the community of the event. Sample output: public
<$c>
Returns the event's category. Sample output: SNMP
<$E>
Returns the enterprise ID of the event. Sample output: .1.3.6.1.4.1.11.2.17.1
<$e>
Returns the enterprise object ID. Sample output: .1.3.6.1.4.1.11.2.17.1
<$F>
Returns the textual name of the remote postmaster daemon's computer if the event was forwarded. Sample output: cress.veg.com
<$G>
Returns the generic event ID. Sample output: 6
<$MSG_OBJECT>
Returns the name of the object associated with the event. This is set in the Message Defaults section of the policy editor.
<$N>
Returns the event name (textual alias) of the event format specification used to format the event, as defined in the Event Configurator. Sample output: OV_Node_Down
<$O>
Returns the name (object identifier) of the event. Sample output: .1.3.6.1.4.1.11.2.17.1.0.58916865
<$o>
Returns the numeric object identifier of the event. Sample output: .1.3.6.1.4.1.11.2.17.1.0.58916865
<$R>
Returns the true source of the event. This value is inferred through the transport mechanism which delivered the event. Sample output: carrot.veg.com
<$r>
Returns the implied source of the event. This may not be the true source of the event if the true source is proxying for another source, such as when a monitoring application running locally is reporting information about a remote node. Sample output: rutabaga.veg.com
<$S>
Returns the specific event ID. Sample output: 5891686
<$s>
Returns the event's severity. Sample output: Normal
<$T>
Returns the event time stamp. Sample output: 0
<$V>
Returns the event type, based on the transport from which the event was received. Currently supported types are SNMPv1, SNMPv2, CMIP, GENERIC, and SNMPv2INFORM. Sample output: SNMPv1
<$X>
Returns the time the event was received using the local time representation. Sample output: 17:24:58
<$x>
Returns the date the event was received using the local date representation. Sample output: 03/27/97

Related Topics: