Ô¶¶ËÉ豸ÀàÐÍ 0x00:ÎÞÉ豸 0x01: Old-NB110B 0x02: New-NB110B 0x03:NB110E 0x04:NB110F 0x05:FT160 0x06:NB110G 0x10:Router 0x11:EPAS
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.5651.3.499.1.1.1.1.2
Ô¶¶ËÉ豸ÀàÐÍ 0x00:ÎÞÉ豸 0x01: Old-NB110B 0x02: New-NB110B 0x03:NB110E 0x04:NB110F 0x05:FT160 0x06:NB110G 0x10:Router 0x11:EPAS
Identification
{1 3 6 1 4 1 5651 3 499 1 1 1 1 2}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In MPVETH, the row index VethRemoteTypeIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.5651.3.499.1.1.1.1.2.<VethRemoteTypeIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.5651.3.499.1.1.1.1.2
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.
VethDeviceType OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Ô¶¶ËÉ豸ÀàÐÍ 0x00:ÎÞÉ豸 0x01: Old-NB110B 0x02: New-NB110B 0x03:NB110E 0x04:NB110F 0x05:FT160 0x06:NB110G 0x10:Router 0x11:EPAS"
::= {VethRemoteTypeEntry 2}
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Ô¶¶ËÉ豸ÀàÐÍ 0x00:ÎÞÉ豸 0x01: Old-NB110B 0x02: New-NB110B 0x03:NB110E 0x04:NB110F 0x05:FT160 0x06:NB110G 0x10:Router 0x11:EPAS
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: mandatory.
Names: VethDeviceType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"VethDeviceType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Ô¶¶ËÉ豸ÀàÐÍ 0x00:ÎÞÉ豸 0x01: Old-NB110B 0x02: New-NB110B 0x03:NB110E 0x04:NB110F 0x05:FT160 0x06:NB110G 0x10:Router 0x11:EPAS\"",
"::=",
"{",
"VethRemoteTypeEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Ô¶¶ËÉ豸ÀàÐÍ 0x00:ÎÞÉ豸 0x01: Old-NB110B 0x02: New-NB110B 0x03:NB110E 0x04:NB110F 0x05:FT160 0x06:NB110G 0x10:Router 0x11:EPAS"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: MPVETH
See published definition above
{'MAIPU-SMI': ['mpMgmt'], 'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32']}Source data warning: The published value identifier starts with an uppercase letter, outside SMI identifier syntax. Its exact spelling and numeric OID are retained.
· Download MPVETHRelated source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.5651.3.499.1.1.1.1.1 | VethRemoteTypeIndex | 0 | 0 | |
| 1.3.6.1.4.1.5651.3.499.1.1.1.1.3 | VethDeviceState | 0 | 0 |