Home/Catalog/ARUBAWIRED-MSTP-MIB

ARUBAWIRED-MSTP-MIB

AI MIB Summary

The ARUBAWIRED-MSTP-MIB enables monitoring and management of Multiple Spanning Tree Protocol (MSTP) instances, port states, and VLAN-to-instance mappings on Aruba wired network switches. It provides visibility into MSTP configuration consistency, region synchronization status, and topology convergence metrics to ensure loop-free Layer 2 redundancy.

This MIB module for Multiple Spanning Tree Protocol(MSTP).
Main OID:
arubaWiredMstpMIB.1.3.6.1.4.1.47196.4.1.1.3.13
36
Objects
Active
Status
4
Dependencies

Imported Objects

Objects

36 total
Object Name
arubaWiredMstpMIBThis MIB module for Multiple Spanning Tree Protocol(MSTP).
MODULE-IDENTITY
.1.3.6.1.4.1.47196.4.1.1.3.13
arubaWiredMstpNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.47196.4.1.1.3.13.0
arubaWiredMstpErrantBpduReceivedThis Trap is generated when an unexpected (errant) BPDU has been received on a port.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.1
arubaWiredMstpInstanceTopologyChangeTrap is generated when a Topology Change is detected in the specified INSTANCE.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.2
arubaWiredMstpCISTTopologyChangeTrap is generated when a Topology Change is detected in CIST.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.3
arubaWiredMstpInstanceNewRootTrap generated when sending agent has become the new root of spanning Tree for the specified INSTANCE; the notification is sent by a bridge soon after its election as the new root.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.4
arubaWiredMstpCISTNewRootTrap generated when sending agent has become the new root of spanning Tree for the specified CIST; the notification is sent by a bridge soon after its election as the new root.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.5
arubaWiredMstpInstanceLoopGuardInconsistencyTrap generated when a Loop Guard feature enabled port receives superior BPDUs on its interface for a given instance.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.6
arubaWiredMstpCISTLoopGuardInconsistencyTrap generated when a Loop Guard feature enabled port receives superior BPDUs on its interface for CIST.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.7
arubaWiredMstpInstanceRootGuardInconsistencyTrap generated when a Root Guard feature enabled port receives superior BPDUs on its interface for a given instance.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.8
arubaWiredMstpCISTRootGuardInconsistencyTrap generated when a Root Guard feature enabled port receives superior BPDUs on its interface for CIST.
NOTIFICATION-TYPE
.1.3.6.1.4.1.47196.4.1.1.3.13.0.9
arubaWiredMstpObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.47196.4.1.1.3.13.1
arubaWiredMstpNotificationTableInformation describing the Mstp configuration and statistics of the Instances and CIST.
SEQUENCE OF ArubaWiredMstpNotificationEntry
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1
arubaWiredMstpNotificationEntryInformation describing the Mstp events for trap generation.
ArubaWiredMstpNotificationEntry
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1
arubaWiredMstpPortNameThe port Namero
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.1
arubaWiredMstpInstanceIDUnique identifier of the STP Instance.ro
Integer32
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.2
arubaWiredMstpPortErrantBpduRxCountThe number of errant bpdu rx on the port for the particular instancero
Integer32
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.3
arubaWiredMstpErrantBpduSrcMacSource MAC address of the port sending this Errant trap.ro
MacAddress (SNMPv2-TC)
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.4
arubaWiredMstpSuperiorBpduSrcPortPort belonging to the Bridge, which transmitted the superior BPDU.ro
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.5
arubaWiredMstpSuperiorBpduSrcMacThe source MAC address of the port sending superior BPDU.ro
MacAddress (SNMPv2-TC)
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.6
arubaWiredMstpPortInstanceStateState of the port for the particular Instancero
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.7
arubaWiredMstpErrantBpduDetectorThe identifier of the feature generating Errant BPDU trap.ro
Enumeration
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.8
arubaWiredMstpPortDesignatedBridgeThe designated bridge name for this STP instance.ro
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.9
arubaWiredMstpOldPortRoleThe previous role of the port before the Topology change. Forwarding/Blocking/Err-DisabledStatero
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.10
arubaWiredMstpNewPortRoleThe new role of the port after the Topology change. Forwarding/Blocking/Err-DisabledStatero
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.11
arubaWiredMstpTopoChangeTimeTime at which the Topology Change happened.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.12
arubaWiredMstpPreviousRootBridgeIDBridge ID of the Previous root, before the Topology change.ro
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.13
arubaWiredMstpNewRootBridgeIDBridge ID of the New root, after the Topology change.ro
DisplayString
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.14
arubaWiredMstpRootBridgeChangeTimeStampTime when the new root is elected.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.15
arubaWiredMstpIdInstance ID
Integer32
.1.3.6.1.4.1.47196.4.1.1.3.13.1.1.1.16
arubaWiredMstpConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.47196.4.1.1.3.13.2
arubaWiredMstpGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.47196.4.1.1.3.13.2.1
arubaWiredMstpNotificationObjectGroupGroup of objects required for notifications.
Unknown
.1.3.6.1.4.1.47196.4.1.1.3.13.2.1.1
arubaWiredMstpNotificationGroupGroup of notifications.
Unknown
.1.3.6.1.4.1.47196.4.1.1.3.13.2.1.2
arubaWiredMstpCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.47196.4.1.1.3.13.2.2
arubaWiredMstpNotificationComplianceThe compliance statement for Mstp extension notifications.
Unknown
.1.3.6.1.4.1.47196.4.1.1.3.13.2.2.1

More MIBs from HPE/Aruba Networking Division

Browse all HPE/Aruba Networking DivisionMIBs →
ARUBAWIRED-NETWORKING-OID

The ARUBAWIRED-NETWORKING-OID MIB module provides proprietary extensions for monitoring HPE Aruba Networking hardware, enabling the retrieval of device-specific operational metrics, interface statistics, and system health indicators not covered by standard SNMP MIBs.

144 objects→
ARUBAWIRED-MGMD-SNOOPING-MIB

The ARUBAWIRED-MGMD-SNOOPING-MIB enables monitoring and management of Multicast Group Management Daemon (MGMD) snooping configurations and state metrics on HPE Aruba wired network switches. This module provides visibility into multicast group memberships, snooping table entries, and interface-specific filtering states to optimize Layer 2 multicast traffic forwarding.

124 objects→
ARUBAWIRED-PM-MIB

The ARUBAWIRED-PM-MIB enables SNMP-based monitoring and management of pluggable optical transceivers and SFP modules on Aruba wired network infrastructure, exposing critical telemetry such as optical power levels, laser bias currents, temperature, and voltage status for hardware health verification.

93 objects→
ARUBAWIRED-RPVST-MIB

The ARUBAWIRED-RPVST-MIB module enables monitoring and management of Rapid Per-VLAN Spanning Tree (RPVST) protocol states, port roles, and topology changes on Aruba wired network switches. It provides visibility into VLAN-specific spanning tree instances, including root bridge election, port blocking/forwarding status, and BPDU transmission metrics for each configured VLAN.

78 objects→
ARUBAWIRED-LLDP-MIB

The ARUBAWIRED-LLDP-MIB enables monitoring of Link Layer Discovery Protocol (LLDP) objects specifically for Power Source Equipment (PSE) capabilities on HPE Aruba wired network devices. This module facilitates the retrieval of power negotiation parameters, such as Power via MDI (802.3af/at) status and allocated power levels, to manage PoE distribution and device connectivity.

64 objects→
ARUBAWIRED-VSX-MIB

The ARUBAWIRED-VSX-MIB provides SNMP access to monitor and manage High Availability and Virtual Switching Extension (VSX) cluster states, synchronization status, and inter-chassis link health on HPE Aruba CX switches. It exposes specific metrics for VSX peer relationships, including active/standby roles, keepalive status, and configuration synchronization counters to ensure cluster integrity.

60 objects→