alarmText
NSCRTV-EDFA ·
.1.3.6.1.4.1.17409.1.2.4
Object
This trap targets for the needs of information contained in a text field transponder information is achievable. The field contains the text of the object depends on the definition of alarm parameters, it is uncertain, This object can not access provisions.
Context
- MIB
- NSCRTV-EDFA
- OID
.1.3.6.1.4.1.17409.1.2.4- Type
- scalar
- Access
- noaccess
- Status
- optional
- Parent
- alarmsIdent
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'NSCRTV-EDFA' -M '/opt/observium/mibs/vialite:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'NSCRTV-EDFA::alarmText.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'NSCRTV-EDFA' -M '/opt/observium/mibs/vialite:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'NSCRTV-EDFA::alarmText'
Syntax
- 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