All MIBs › Vct-Loopdetect-59-MIB
Category: VLAN and Layer 2 Switching
Description: Covers a loop detection protocol on Ethernet switches used to prevent broadcast storms on access ports.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is Vct-Loopdetect-59-MIB?
Vct-Loopdetect-59-MIB is a vendor MIB implementing Ethernet loop-detection on switches, using per-port cable/loop parameters (the vctTable) to prevent broadcast storms caused by accidental Layer 2 loops on access ports. Its data falls into the fault-detection and configuration categories, per-port loop-detection settings and cable-related parameters used by the switch to identify a looped port. This is a hardware/interface-status monitoring feature: it lets an administrator identify which switch port has triggered loop detection (and typically been shut down or blocked) and confirm cable-related detection parameters are correctly configured, protecting the network from storm-induced outages. No specific standards dependency is evident beyond the switch's own base bridge/interface MIBs it would be indexed against. It's deployed on access-layer Ethernet switches, especially in environments with unmanaged end-user wiring where accidental loops are common, and a Vct-Loopdetect-59-MIB download provides the definitions needed to load it into a MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in Vct-Loopdetect-59-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- access-layer Ethernet switch
Monitoring Examples
An administrator would poll vctTable for the cable-related parameters on each port and check which port entries indicate an active loop condition, since the module description states the table "contains the parameter of cable" used for loop detection. A port shown in a loop-detected/blocked state would explain a sudden broadcast storm or MAC address flapping reported elsewhere on the switch. Beyond vctTable, no further object names were available in the source data to cite.
What Can Be Monitored
- per-port loop detection state
- cable parameter per port
- loop-triggered port shutdown/block status
Imported Objects
From RFC1155-SMI
| Counter | |
| Gauge | |
| IpAddress | |
| NetworkAddress | |
| mgmt |
From RFC1213-MIB
| ifIndex |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 | |
| enterprises | |
| experimental |
From SNMPv2-TC
| MacAddress | |
| RowStatus |
OIDs
RFC description
Manages loop detection protocol on Ethernet switches to prevent broadcast storms on access ports.
Start monitoring access-layer Ethernet switch (per-port loop-detection/cable-parameter status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.