OID reference
1.3.6.1.4.1.272.4.39.1.1.9
The BridgeIndex is used for assigning the virtual interface. to a specific bridge; -1 means, not connected to a bridge, but used for routing.
Identification
{1 3 6 1 4 1 272 4 39 1 1 9}
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 BIANCA-VIF-MIB, the row index consists of these components in order:
virtIfBaseSlot (INTEGER): one numeric subidentifier for the non-negative value.virtIfBaseUnit (INTEGER): one numeric subidentifier for the non-negative value.virtIfVirtChannel (INTEGER): one numeric subidentifier for the non-negative value.An instance has the form .1.3.6.1.4.1.272.4.39.1.1.9.<virtIfBaseSlot>.<virtIfBaseUnit>.<virtIfVirtChannel>. Use values present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.272.4.39.1.1.9
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.
virtIfBridgeIndex OBJECT-TYPE
SYNTAX INTEGER
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The BridgeIndex is used for assigning the virtual interface.
to a specific bridge; -1 means, not connected to a bridge,
but used for routing."
DEFVAL { -1 }
::= { virtIfDefinitionEntry 9 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The BridgeIndex is used for assigning the virtual interface. to a specific bridge; -1 means, not connected to a bridge, but used for routing.
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: virtIfBridgeIndex
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"virtIfBridgeIndex",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The BridgeIndex is used for assigning the virtual interface. to a specific bridge; -1 means, not connected to a bridge, but used for routing.\"",
"DEFVAL",
"{",
"-",
"1",
"}",
"::=",
"{",
"virtIfDefinitionEntry",
"9",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The BridgeIndex is used for assigning the virtual interface. to a specific bridge; -1 means, not connected to a bridge, but used for routing."
],
null,
null,
null,
[
"DEFVAL",
-1
]
]
}Vendor MIB copy from the Observium Community archive.
Module: BIANCA-VIF-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'SNMPv2-TC': ['RowStatus', 'PhysAddress'], 'BINTEC-MIB': ['bibo', 'vif'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'Gauge', 'TimeTicks', 'enterprises']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.39.1.1.1 | virtIfBaseSlot | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.2 | virtIfBaseUnit | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.3 | virtIfVirtChannel | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.4 | virtIfPhysAddr | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.5 | virtIfAdminStatus | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.6 | virtIfVlanId | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.7 | virtIfOperMode | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.8 | virtIfOrigPhysAddr | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.10 | virtIfUntaggedFrames | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.11 | virtIfNonMemberFrames | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.12 | virtIfAdminOverride | 0 | 0 | |
| 1.3.6.1.4.1.272.4.39.1.1.13 | virtIfStatus | 0 | 0 |