SVRMGT-MIB :: svrThrLocalHandlerArguments1

MIB Reference — IPNetwork Monitor

All MIBsSVRMGT-MIBsvrThrLocalHandlerArguments1

svrThrLocalHandlerArguments1

Module: SVRMGT-MIB

OID (symbolic): SVRMGT-MIB::svrThrLocalHandlerArguments1

OID (numeric): 1.3.6.1.4.1.36.2.18.22.2.2.3.1.21

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-write

Description:

This is the first part of the argument line if the svrThrInvokeLocalHandler is used. This argument line is passed directly to the application pointed to by the svrThrLocalHandlerPath. A parameter(s) could be substituted anywhere in the argument line with an oid's value if there is a %oid% found within the string. The %oid% will be replaced with the value of the oid at the time the event occurred. For example if the svrSystemDesc value from the Digital Server System mib is required, then the argument list would have a replacement statement like this: %.1.3.6.1.4.1.36.2.18.22.1.2.3.0%.

If a value from a threshold record is requested, use %oid% where the oid is .1.3.6.1.4.1.36.2.18.22.2.2.3.1.offset.instance. The offset is the oid offset (from 1 to 30) of the threshold entry variable. For svrThrIndex, the offset is 1. The instance can be dropped if the current threshold record (that which caused the event) is to be used. Otherwise, the instance of the requested threshold entry must be part of the %oid% statement.

All the replaced values are inserted into the argument strings as ascii/text strings. For an integer (counter, gauge, etc) value, if the value is negative, there will be a minus sign in front of the value. For a positive number, there is no sign in front of the value. The integer value will be in ascii format - it is the responsibility of the application to convert the text into a decimal number. All octet strings, excluding display strings, will be inserted into the argument string as a text string in the format of 0xoctet value. For example if an octet string (hex based) of 8,23,6a,4e was retrieved using the %oid% format, then the replaced value would be a text string looking like this - 0x8,0x23,0x6a,0x4e where the number are in ascii (displayable) format separated by a comma. The 0x represents the hexadecimal base while the number following that is the ascii representation of the hexadecimal number. For display strings, there will be a pair of quotes around the string.

Use of the Handler Arguments must be done in ascending order. No skipping of argument variables is allowed.

NOTE - All oids must be preceded with a period(.) for proper system group recognition. Also all argument lists (concatenated starting with argument #1) are separated by a space. Default value on row creation is null.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.36.2.18.22.2.2.3.1.21
snmpwalk -v2c -c public <target> SVRMGT-MIB::svrThrLocalHandlerArguments1

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.36.2.18.22.2.2.3.1.21.1
snmpget -v2c -c public <target> SVRMGT-MIB::svrThrLocalHandlerArguments1.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.36.2.18.22.2.2.3.1.21.1 s <value>

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.36decDECATM-MIB
1.3.6.1.4.1.36.2emaDECATM-MIB
1.3.6.1.4.1.36.2.18decMIBextensionDECATM-MIB
1.3.6.1.4.1.36.2.18.22svrSystemSVRMGT-MIB
1.3.6.1.4.1.36.2.18.22.2svrMgtSVRMGT-MIB
1.3.6.1.4.1.36.2.18.22.2.2svrAlarmsSVRMGT-MIB
1.3.6.1.4.1.36.2.18.22.2.2.3svrThresholdTableSVRMGT-MIB
1.3.6.1.4.1.36.2.18.22.2.2.3.1svrThresholdEntrySVRMGT-MIB
1.3.6.1.4.1.36.2.18.22.2.2.3.1.21svrThrLocalHandlerArguments1SVRMGT-MIB