snmpGeneralCommunity
LUM-SNMP-MIB ·
.1.3.6.1.4.1.8708.2.17.2.2.4
Object
The community string for the SNMP agent. SNMP
v1/v2c must have a matching community string
for the SNMP agent and Manager.
To disable SNMP v1/v2c access the community
string should be empty.
SNMP v1 and v2c access are GET (read-only) for
security reasons. To be able to change settings
a SNMPv3 user must be defined. The node only
supports one community string.
All printable ASCII characters except '&' are
allowed in the community string. Note that the
community string is case sensitive.
Context
- MIB
- LUM-SNMP-MIB
- OID
.1.3.6.1.4.1.8708.2.17.2.2.4- Type
- scalar
- Access
- readwrite
- Status
- current
- Default
"public"- Parent
- snmpGeneral
- Groups
- 5
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 'LUM-SNMP-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LUM-SNMP-MIB::snmpGeneralCommunity.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'LUM-SNMP-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LUM-SNMP-MIB::snmpGeneralCommunity'
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
Object Constraints
range: 0-33
Type Constraints
range: 0..255