configureAlerts

PDU-MIB · .1.3.6.1.4.1.13742.4.1.1.46
Commands MIB view Table view

Object

scalar r/w SNMPv2-TCDisplayString 
This is an operation. It has write-only semantics. 
GET operation will return the empty string.
For SET operations, it configures alerts 
The format is a comma separated list of the following parameters.
     sensorClass, eventType, eventDirection, policyName
        For sensorclass: use the SensorClass eumeration 
        For eventType: use the EventType enumeration
        For eventDirection: use the EventDirection enumeration
        For Policy Name: use the name of the policy; the Policy Name is case sensitive
Note: setting this variable will overwrite the existing policy 
               
          
 Example: if the External Temperature  upper non-critical threshold is either asserted and deasserted,
            then  execute the policy named multiple destinations
        the string would be 
         0,1,2,multiple destinations

Context

MIB
PDU-MIB
OID
.1.3.6.1.4.1.13742.4.1.1.46
Type
scalar
Access
readwrite
Status
current
Parent
info
Groups
1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'PDU-MIB' -M '/opt/observium/mibs/raritan:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'PDU-MIB::configureAlerts.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'PDU-MIB' -M '/opt/observium/mibs/raritan:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'PDU-MIB::configureAlerts'

Syntax

SNMPv2-TCDisplayString
Source
SNMPv2-TCDisplayString
Base type
OctetString
Display format
255a
Type Description
Represents textual information taken from the NVT ASCII
          
character set, as defined in pages 4, 10-11 of RFC 854.
          
To summarize RFC 854, the NVT ASCII repertoire specifies:
          
  - the use of character codes 0-127 (decimal)
          
  - the graphics characters (32-126) are interpreted as
    US ASCII
          
  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
    meanings specified in RFC 854
          
  - the other 25 codes have no standard interpretation
          
  - the sequence 'CR LF' means newline
          
  - the sequence 'CR NUL' means carriage-return
          
  - an 'LF' not preceded by a 'CR' means moving to the
    same column on the next line.
          
  - the sequence 'CR x' for any x other than LF or NUL is
    illegal.  (Note that this also means that a string may
    end with either 'CR LF' or 'CR NUL', but not with CR.)
          
Any object defined using this syntax may not exceed 255
characters in length.

Values & Constraints

Type Constraints
range: 0..255

Conformance

Member of
infoGroupRev2