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.
|
Imported Objects
| f10Mgmt | FORCE10-SMI |
| InterfaceIndex | IF-MIB |
| InetAddressType, InetAddress | INET-ADDRESS-MIB |
| MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
| MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Unsigned32 | SNMPv2-SMI |
| TEXTUAL-CONVENTION, MacAddress, TimeInterval | SNMPv2-TC |
Type Definitions (1)
| Name | Base Type | Values/Constraints |
|---|---|---|
 F10VLTMemberLinkStatus | linkNotEstablished(0), linkUp(1), linkDown(2), linkError(3) |
Objects
  f10VirtualLinkTrunkMib  | .1.3.6.1.4.1.6027.3.17 | |
| f10VirtualLinkTrunkObjects | .1.3.6.1.4.1.6027.3.17.1 | |
 f10VirtualLinkTrunkTable | .1.3.6.1.4.1.6027.3.17.1.1 | |
 f10VirtualLinkTrunkTableEntry | .1.3.6.1.4.1.6027.3.17.1.1.1 | |
 f10VLTDomainId | .1.3.6.1.4.1.6027.3.17.1.1.1.1 | |
| f10VLTBkUpIpAddr | .1.3.6.1.4.1.6027.3.17.1.1.1.10 | |
| f10VLTBkUpInterval | .1.3.6.1.4.1.6027.3.17.1.1.1.11 | |
| f10VLTRemoteMacAddr | .1.3.6.1.4.1.6027.3.17.1.1.1.12 | |
| f10VLTRemoteRolePriority | .1.3.6.1.4.1.6027.3.17.1.1.1.13 | |
| f10VLTUnitId | .1.3.6.1.4.1.6027.3.17.1.1.1.14 | |
| f10VLTVersionMajor | .1.3.6.1.4.1.6027.3.17.1.1.1.15 | |
| f10VLTVersionMinor | .1.3.6.1.4.1.6027.3.17.1.1.1.16 | |
| f10VLTRemoteUnitId | .1.3.6.1.4.1.6027.3.17.1.1.1.17 | |
| f10VLTRemoteVersionMajor | .1.3.6.1.4.1.6027.3.17.1.1.1.18 | |
| f10VLTRemoteVersionMinor | .1.3.6.1.4.1.6027.3.17.1.1.1.19 | |
| f10VLTMacAddr | .1.3.6.1.4.1.6027.3.17.1.1.1.2 | |
| f10VLTIclBwStatus | .1.3.6.1.4.1.6027.3.17.1.1.1.20 | |
| f10VLTCfgSysMacAddr | .1.3.6.1.4.1.6027.3.17.1.1.1.21 | |
| f10VLTPeerRouting | .1.3.6.1.4.1.6027.3.17.1.1.1.22 | |
| f10VLTPeerRoutingTimeout | .1.3.6.1.4.1.6027.3.17.1.1.1.23 | |
| f10VLTRemotePeerRouting | .1.3.6.1.4.1.6027.3.17.1.1.1.24 | |
| f10VLTPriority | .1.3.6.1.4.1.6027.3.17.1.1.1.3 | |
| f10VLTIclIfIndex | .1.3.6.1.4.1.6027.3.17.1.1.1.4 | |
| f10VLTRole | .1.3.6.1.4.1.6027.3.17.1.1.1.5 | |
| f10VLTPeerStatus | .1.3.6.1.4.1.6027.3.17.1.1.1.6 | |
| f10VLTIclStatus | .1.3.6.1.4.1.6027.3.17.1.1.1.7 | |
| f10VLTHBeatStatus | .1.3.6.1.4.1.6027.3.17.1.1.1.8 | |
| f10VLTBkUpIpAddrType | .1.3.6.1.4.1.6027.3.17.1.1.1.9 | |
| f10VirtualLinkStatsTable | .1.3.6.1.4.1.6027.3.17.1.2 | |
| f10VirtualLinkStatsTableEntry | .1.3.6.1.4.1.6027.3.17.1.2.1 | |
| f10VLTStatNumHelloSent | .1.3.6.1.4.1.6027.3.17.1.2.1.1 | |
| f10VLTStatNumHelloRcvd | .1.3.6.1.4.1.6027.3.17.1.2.1.2 | |
| f10VLTStatNumHbeatSent | .1.3.6.1.4.1.6027.3.17.1.2.1.3 | |
| f10VLTStatNumHbeatRcvd | .1.3.6.1.4.1.6027.3.17.1.2.1.4 | |
| f10VLTStatNumDomainErrors | .1.3.6.1.4.1.6027.3.17.1.2.1.5 | |
| f10VLTStatNumVersionErrors | .1.3.6.1.4.1.6027.3.17.1.2.1.6 | |
| f10VirtualLinkDetailsTable | .1.3.6.1.4.1.6027.3.17.1.3 | |
| f10VirtualLinkDetailsTableEntry | .1.3.6.1.4.1.6027.3.17.1.3.1 | |
| f10VLTDetailLocalLagID | .1.3.6.1.4.1.6027.3.17.1.3.1.1 | |
| f10VLTDetailPeerLagID | .1.3.6.1.4.1.6027.3.17.1.3.1.2 | |
| f10VLTDetailLocalStatus | .1.3.6.1.4.1.6027.3.17.1.3.1.3 | |
| f10VLTDetailPeerStatus | .1.3.6.1.4.1.6027.3.17.1.3.1.4 | |
 f10VLTErrorReason | .1.3.6.1.4.1.6027.3.17.1.4 | |
| f10VirtualLinkTrunkNotifObjects | .1.3.6.1.4.1.6027.3.17.2 | |
| f10VirtualLinkTrunkNotifications | .1.3.6.1.4.1.6027.3.17.2.0 | |
| f10VirtualLinkTrunkConformance | .1.3.6.1.4.1.6027.3.17.3 | |
| f10VirtualLinkTrunkCompliances | .1.3.6.1.4.1.6027.3.17.3.1 | |
| f10VirtualLinkTrunkGroups | .1.3.6.1.4.1.6027.3.17.3.2 |
Notifications/Traps
| Name | OID | Description |
|---|---|---|
 f10VLTRoleChange | .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 |
| f10VLTIclStatusChange | .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 |
| f10VLTPeerStatusChange | .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 |
| f10VLTHBeatStatusChange | .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 |
| f10VLTIclBwUsageExceed | .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 |
| f10VLTDomainConfigError | .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. |