Disallow or allow SNMPv3 accounts that do not comply with NIST compliance mode when NIST compliance has been enabled.
Sources for this description
IBM MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.2.3.51.3.3.4.2.4.7.2
Disallow or allow SNMPv3 accounts that do not comply with NIST compliance mode when NIST compliance has been enabled.
Identification
{1 3 6 1 4 1 2 3 51 3 3 4 2 4 7 2}
| Value | Name |
|---|---|
| 0 | disallow |
| 1 | allow |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.2.3.51.3.3.4.2.4.7.2.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
cryptoSnmpv3 OBJECT-TYPE
SYNTAX INTEGER {
disallow(0),
allow(1)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Disallow or allow SNMPv3 accounts that do not comply with
NIST compliance mode when NIST compliance has been enabled."
::= { cryptoSettings 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Disallow or allow SNMPv3 accounts that do not comply with NIST compliance mode when NIST compliance has been enabled.
IBM MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: cryptoSnmpv3
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"cryptoSnmpv3",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"disallow",
"(",
"0",
")",
",",
"allow",
"(",
"1",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Disallow or allow SNMPv3 accounts that do not comply with NIST compliance mode when NIST compliance has been enabled.\"",
"::=",
"{",
"cryptoSettings",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"disallow",
0
],
[
"allow",
1
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Disallow or allow SNMPv3 accounts that do not comply with NIST compliance mode when NIST compliance has been enabled."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive. IBM support.
Module: IMM-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress', 'Gauge'], 'RFC1213-MIB': ['DisplayString']}Related source files and packages:
Vendor MIB copy from the Observium Community archive. IBM support.
Module: IMM-MIB
{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RFC1155-SMI': ['enterprises', 'IpAddress', 'Gauge'], 'RFC1213-MIB': ['DisplayString']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.3.51.3.3.4.2.4.7.1 | cryptoMode | 0 | 0 | |
| 1.3.6.1.4.1.2.3.51.3.3.4.2.4.7.3 | cryptoInsufCompliance | 1 | 4 |