OID reference
1.3.6.1.4.1.8962.2.1.2.1.1.17
This object contains the portion of the seed value to be used for generating UIDs' for alerts and logs. In case there is a mismatch, the ISM would set the right value, which would used by the sensor for new alerts and logs.
Identification
{1 3 6 1 4 1 8962 2 1 2 1 1 17}
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.8962.2.1.2.1.1.17.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.
ivSysUIDSeed OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object contains the portion of the seed value to be used for generating
UIDs' for alerts and logs. In case there is a mismatch, the ISM would set the
right value, which would used by the sensor for new alerts and logs."
::= { systemGrp 17 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This object contains the portion of the seed value to be used for generating UIDs' for alerts and logs. In case there is a mismatch, the ISM would set the right value, which would used by the sensor for new alerts and logs.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: ivSysUIDSeed
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ivSysUIDSeed",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"65535",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object contains the portion of the seed value to be used for generating UIDs' for alerts and logs. In case there is a mismatch, the ISM would set the right value, which would used by the sensor for new alerts and logs.\"",
"::=",
"{",
"systemGrp",
"17",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
65535
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object contains the portion of the seed value to be used for generating UIDs' for alerts and logs. In case there is a mismatch, the ISM would set the right value, which would used by the sensor for new alerts and logs."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: TRELLIX-SENSOR-CONF-MIB
See published definition above
{'IPV6-TC': ['Ipv6Address'], 'SNMPv2-TC': ['TimeInterval', 'TruthValue', 'RowStatus', 'MacAddress', 'DateAndTime', 'DisplayString'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'Integer32', 'IpAddress', 'TimeTicks', 'Unsigned32'], 'TRELLIX-SENSOR-SMI': ['ivSensorConfiguration', 'respPortIndex', 'intfPortIndex', 'slotIndex', 'intfPhysicalPortIndex', 'ntpServerIndex', 'sslProbeIpv4Index', 'sslProbeIpv6Index', 'processorNumIndex', 'intfVirtualPortIndex', 'intfVirtualSlotIndex'], 'TRELLIX-INTRUVERT-TC': ['TrellixFEType', 'TrellixIDSOperatingMode', 'TrellixIDSPortType', 'TrellixIDSResponseMode', 'TrellixIDSActionResult', 'TrellixIDSActionStatus', 'TrellixIDSAction', 'TrellixIDSCardType', 'TrellixTFTPFileType', 'TrellixTFTPFailedResult', 'TrellixTFTPInProgressResult', 'TrellixTFTPStatus', 'TrellixTFTPAction', 'TrellixGEType', 'TrellixCUGEType', 'TrellixPortSpeed', 'TrellixPluggableModuleType', 'TrellixPortLinearIndex']}Related source files and packages:
Registration