F10-VIRTUAL-LINK-TRUNK-MIB
This MIB module provides information on Dual Brain Virtual Link
Trunk(VLT) feature which is a control plane mechanism to provide
Layer2 multipathing between access network devices (switches or
servers) and the core network.
VLT represents a single logical layer 2 domain from the view of
downstream devices that have LAG bundles terminating on separate
chassis in the virtual link trunk domain.
However, the two VLT chassis are independent L2/L3 switches for
devices in the upstream network.
A sample of VLT scenario:
---------------------------------------------------------------
| _______________ |
| | Edge router | |
| |_______________| |
| / \ |
| / \ |
| VLT / \ |
| ____________/_______________________\____________ . |
| | _______/ Back Up Link \_______ | /|\|
| | | |-------------------------| | | | |
| | | | ------- | | | L3| |
| | | S4810 |________| Inter |________| S4810 | |_____|
| | | |________|Chassis|________| | | L2| |
| | | | | Link | | | | | |
| VLT port \_____\ ------- /____/VLT port\|/|
| |_____\_____\_________________________/____/_____| . |
| \ \ -----------------/ / |
| \ \----/------------ / |
| \ / \ / |
| \ / \ / |
|Lag(active)<--- \ / \ /--->Lag(active) |
| ___\__/___________________\_/______ |
| | _______ Stacking ______ | |
| | | S60 |--------------| S60 | | |
| | |__\____| |____/_| | |
| |_____\______________________/______| |
| \ /-->Nic teaming |
| \__________________/ |
| | Nic1 Nic2 | |
| | Server | |
| |____________________| |
---------------------------------------------------------------
Benefits of VLT are as follows:
> Allows a single device to use LAG across two upstream devices
> Eliminates Spanning Tree Protocol (STP) blocked ports
> Provides a loop-free topology
> Uses all available uplink bandwidth
> Provides fast convergence if either the link or a device fails
> Provides link-level resiliency
> Assures high availability
GLOSSARY AND ABBREVIATIONS
VLT - Virtual Link Trunk
The combined port channel between the VLT peer devices and
the downstream device.
VLT Peer device
One of a pair of devices that are connected with the
special port channel known as the chassis interconnect
trunk.
VLT Chassis Interconnect Trunk
The link used to synchronize states between the VLT peer
devices.
VLT domain
This domain includes both VLT peer devices, the VLT chassis
interconnect trunk, and all of the port channels in the VLT
connected to the downstream devices.
VLT Backup link
The backup link monitors the vitality of a VLT peer device.
The backup trunk sends configurable, periodic heart beat
messages between VLT peer devices.
ICL
Abbreviation for Chassis InterConnect Link.
- Source file
F10-VIRTUAL-LINK-TRUNK-MIB- Last revised
- Identity
f10VirtualLinkTrunkMib- Base OID
1.3.6.1.4.1.6027.3.17
Imported Objects
| FORCE10-SMI | f10Mgmt |
| IF-MIB | InterfaceIndex |
| INET-ADDRESS-MIB | InetAddress InetAddressType |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | MacAddress TEXTUAL-CONVENTION (no object page) TimeInterval |
Net-SNMP examples using the force10 MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'F10-VIRTUAL-LINK-TRUNK-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'F10-VIRTUAL-LINK-TRUNK-MIB::f10VirtualLinkTrunkMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'F10-VIRTUAL-LINK-TRUNK-MIB' -M '/opt/observium/mibs/force10:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'F10-VIRTUAL-LINK-TRUNK-MIB::f10VirtualLinkTrunkMib'
Objects (48)
Showing 48 of 48 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.6027.3.17 |
||
.1.3.6.1.4.1.6027.3.17.1 |
||
.1.3.6.1.4.1.6027.3.17.1.1 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.1 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.10 |
||
|
Integer32
|
.1.3.6.1.4.1.6027.3.17.1.1.1.11 |
|
.1.3.6.1.4.1.6027.3.17.1.1.1.12 |
||
|
Unsigned32
|
.1.3.6.1.4.1.6027.3.17.1.1.1.13 |
|
.1.3.6.1.4.1.6027.3.17.1.1.1.14 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.15 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.16 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.17 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.18 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.19 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.2 |
||
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.1.1.20 |
|
.1.3.6.1.4.1.6027.3.17.1.1.1.21 |
||
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.1.1.22 |
|
|
Integer32
|
.1.3.6.1.4.1.6027.3.17.1.1.1.23 |
|
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.1.1.24 |
|
|
Unsigned32
|
.1.3.6.1.4.1.6027.3.17.1.1.1.3 |
|
.1.3.6.1.4.1.6027.3.17.1.1.1.4 |
||
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.1.1.5 |
|
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.1.1.6 |
|
.1.3.6.1.4.1.6027.3.17.1.1.1.7 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.8 |
||
.1.3.6.1.4.1.6027.3.17.1.1.1.9 |
||
.1.3.6.1.4.1.6027.3.17.1.2 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1.1 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1.2 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1.3 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1.4 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1.5 |
||
.1.3.6.1.4.1.6027.3.17.1.2.1.6 |
||
.1.3.6.1.4.1.6027.3.17.1.3 |
||
.1.3.6.1.4.1.6027.3.17.1.3.1 |
||
|
Unsigned32
|
.1.3.6.1.4.1.6027.3.17.1.3.1.1 |
|
|
Unsigned32
|
.1.3.6.1.4.1.6027.3.17.1.3.1.2 |
|
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.3.1.3 |
|
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.3.1.4 |
|
|
Enumeration
|
.1.3.6.1.4.1.6027.3.17.1.4 |
|
.1.3.6.1.4.1.6027.3.17.2 |
||
.1.3.6.1.4.1.6027.3.17.2.0 |
||
.1.3.6.1.4.1.6027.3.17.3 |
||
.1.3.6.1.4.1.6027.3.17.3.1 |
||
.1.3.6.1.4.1.6027.3.17.3.2 |
Dependencies (8) 6 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- FORCE10-SMIforce10
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- F10-VIRTUAL-LINK-TRUNK-MIBforce10selected
Type Definitions (1)
| Enumeration |
linkNotEstablished(0)linkUp(1)linkDown(2)linkError(3) |
Conformance Groups (4)
Compliance Statements (1)
OID
.1.3.6.1.4.1.6027.3.17.3.1.1The compliance statement for the Dell Networking OS Virtual Link Trunk MIB.
Required groups
| mandatory | f10VirtualLinkTrunkGroup | |
| mandatory | f10VirtualLinkStatisticsGroup | |
| mandatory | f10VirtualLinkNotificationGroup | |
| mandatory | f10VirtualLinkDetailsTableGroup |
Notifications / Traps (6)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.6027.3.17.2.0.1 |
The agent generates this norification to denote the change in
role of the VLT device in the VLT domain. This notification carries the information about the new role. The possible roles are as follows: 1. StandAlone 2. Primary 3. Secondary |
|
.1.3.6.1.4.1.6027.3.17.2.0.2 |
The agent generates this notification to denote the change in
InterConnect Link Status.The notification contains information on the new ICL status. The possible states are as follows: 1. NotEstabished 2. LinkUp 3. LinkDown 4. LinkError |
|
.1.3.6.1.4.1.6027.3.17.2.0.3 |
The agent generates this notification to denote the change in
Status of the Peer in the VLT domain. This notification contains information on the new status of the peer device. The possible states are as follows: 1. NotEstablished 2. PeerUp 3. PeerDown 4. LinkDown |
|
.1.3.6.1.4.1.6027.3.17.2.0.4 |
The agent generates this notification to denote the change in
Backup Link Status. The notification contains information on the new BackupLink Status. The possible states are as follows: 1. NotEstabished 2. LinkUp 3. LinkDown 4. LinkError |
|
.1.3.6.1.4.1.6027.3.17.2.0.5 |
The IFM agent generates this notification to denote the change
in Bandwidth usage of ICL Link, when it crosses the threshold above 80 %. The possible states are as follows: 0. Below threshold 1. Above threshold |
|
.1.3.6.1.4.1.6027.3.17.2.0.6 |
The agent generates this notification to denote there is a
error/conflict in the VLT domain config parameters (either locally or in remote node which prevent the peer up. The mismatch can be domain Id, unitId,version or system MAC. The notification contains information on the error/mismatch type. |