P-BRIDGE-MIB
The P-BRIDGE-MIB module enables the monitoring and configuration of IEEE 802.1D-1998 compliant bridge devices to manage traffic priority queuing and multicast filtering tables. It provides direct access to specific metrics including bridge port priority values, multicast group membership states, and filtering database entries for Layer 2 traffic control.
Imported Objects
Objects
62 total| Object Name |
|---|
dot1dTpHCPortTableA table that contains information about every high capacity port that is associated with this transparent bridge. SEQUENCE OF Dot1dTpHCPortEntry .1.3.6.1.2.1.17.4.5 |
dot1dTpHCPortEntryStatistics information for each high capacity port of a transparent bridge. Dot1dTpHCPortEntry .1.3.6.1.2.1.17.4.5.1 |
dot1dTpHCPortInFramesThe number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.ro Counter64 .1.3.6.1.2.1.17.4.5.1.1 |
dot1dTpHCPortOutFramesThe number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.ro Counter64 .1.3.6.1.2.1.17.4.5.1.2 |
dot1dTpHCPortInDiscardsCount of valid frames that have been received by this port from its segment which were discarded (i.e., filtered) by the Forwarding Process.ro Counter64 .1.3.6.1.2.1.17.4.5.1.3 |
dot1dTpPortOverflowTableA table that contains the most-significant bits of statistics counters for ports that are associated with this transparent bridge that are on high capacity interfaces, as defined in the conformance clauses for this table. This table is provided as a way to read 64-bit counters for agents which support only SNMPv1. Note that the reporting of most-significant and least-significant counter bits separately runs the risk of missing an overflow of the lower bits in the interval between sampling. The manager must be aware of this possibility, even within the same varbindlist, when interpreting the results of a request or asynchronous notification. SEQUENCE OF Dot1dTpPortOverflowEntry .1.3.6.1.2.1.17.4.6 |
dot1dTpPortOverflowEntryThe most significant bits of statistics counters for a high capacity interface of a transparent bridge. Each object is associated with a corresponding object in dot1dTpPortTable which indicates the least significant bits of the counter. Dot1dTpPortOverflowEntry .1.3.6.1.2.1.17.4.6.1 |
dot1dTpPortInOverflowFramesThe number of times the associated dot1dTpPortInFrames counter has overflowed.ro Counter32 .1.3.6.1.2.1.17.4.6.1.1 |
dot1dTpPortOutOverflowFramesThe number of times the associated dot1dTpPortOutFrames counter has overflowed.ro Counter32 .1.3.6.1.2.1.17.4.6.1.2 |
dot1dTpPortInOverflowDiscardsThe number of times the associated dot1dTpPortInDiscards counter has overflowed.ro Counter32 .1.3.6.1.2.1.17.4.6.1.3 |
pBridgeMIBThe Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998. MODULE-IDENTITY .1.3.6.1.2.1.17.6 |
pBridgeMIBObjects OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.1 |
dot1dExtBase OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.1.1 |
dot1dDeviceCapabilitiesIndicates the optional parts of IEEE 802.1D and 802.1Q that are implemented by this device and are manageable through this MIB. Capabilities that are allowed on a per-port basis are indicated in dot1dPortCapabilities.ro Bits .1.3.6.1.2.1.17.6.1.1.1 |
dot1dTrafficClassesEnabledThe value true(1) indicates that Traffic Classes are enabled on this bridge. When false(2), the bridge operates with a single priority level for all traffic.rw TruthValue (SNMPv2-TC) .1.3.6.1.2.1.17.6.1.1.2 |
dot1dGmrpStatusThe administrative status requested by management for GMRP. The value enabled(1) indicates that GMRP should be enabled on this device, in all VLANs, on all ports for which it has not been specifically disabled. When disabled(2), GMRP is disabled, in all VLANs, on all ports and all GMRP packets will be forwarded transparently. This object affects both Applicant and Registrar state machines. A transition from disabled(2) to enabled(1) will cause a reset of all GMRP state machines on all ports.rw EnabledStatus .1.3.6.1.2.1.17.6.1.1.3 |
dot1dPortCapabilitiesTableA table that contains capabilities information about every port that is associated with this bridge. SEQUENCE OF Dot1dPortCapabilitiesEntry .1.3.6.1.2.1.17.6.1.1.4 |
dot1dPortCapabilitiesEntryA set of capabilities information about this port indexed by dot1dBasePort. Dot1dPortCapabilitiesEntry .1.3.6.1.2.1.17.6.1.1.4.1 |
dot1dPortCapabilitiesIndicates the parts of IEEE 802.1D and 802.1Q that are optional on a per-port basis that are implemented by this device and are manageable through this MIB.ro Bits .1.3.6.1.2.1.17.6.1.1.4.1.1 |
dot1dPriority OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.1.2 |
dot1dPortPriorityTableA table that contains information about every port that is associated with this transparent bridge. SEQUENCE OF Dot1dPortPriorityEntry .1.3.6.1.2.1.17.6.1.2.1 |
dot1dPortPriorityEntryA list of Default User Priorities for each port of a transparent bridge. This is indexed by dot1dBasePort. Dot1dPortPriorityEntry .1.3.6.1.2.1.17.6.1.2.1.1 |
dot1dPortDefaultUserPriorityThe default ingress User Priority for this port. This only has effect on media, such as Ethernet, that do not support native User Priority.rw INTEGER .1.3.6.1.2.1.17.6.1.2.1.1.1 |
dot1dPortNumTrafficClassesThe number of egress traffic classes supported on this port. This object may optionally be read-only.rw INTEGER .1.3.6.1.2.1.17.6.1.2.1.1.2 |
dot1dUserPriorityRegenTableA list of Regenerated User Priorities for each received User Priority on each port of a bridge. The Regenerated User Priority value may be used to index the Traffic Class Table for each input port. This only has effect on media that support native User Priority. The default values for Regenerated User Priorities are the same as the User Priorities. SEQUENCE OF Dot1dUserPriorityRegenEntry .1.3.6.1.2.1.17.6.1.2.2 |
dot1dUserPriorityRegenEntryA mapping of incoming User Priority to a Regenerated User Priority. Dot1dUserPriorityRegenEntry .1.3.6.1.2.1.17.6.1.2.2.1 |
dot1dUserPriorityThe User Priority for a frame received on this port. INTEGER .1.3.6.1.2.1.17.6.1.2.2.1.1 |
dot1dRegenUserPriorityThe Regenerated User Priority the incoming User Priority is mapped to for this port.rw INTEGER .1.3.6.1.2.1.17.6.1.2.2.1.2 |
dot1dTrafficClassTableA table mapping evaluated User Priority to Traffic Class, for forwarding by the bridge. Traffic class is a number in the range (0..(dot1dPortNumTrafficClasses-1)). SEQUENCE OF Dot1dTrafficClassEntry .1.3.6.1.2.1.17.6.1.2.3 |
dot1dTrafficClassEntryUser Priority to Traffic Class mapping. Dot1dTrafficClassEntry .1.3.6.1.2.1.17.6.1.2.3.1 |
dot1dTrafficClassPriorityThe Priority value determined for the received frame. This value is equivalent to the priority indicated in the tagged frame received, or one of the evaluated priorities, determined according to the media-type. For untagged frames received from Ethernet media, this value is equal to the dot1dPortDefaultUserPriority value for the ingress port. For untagged frames received from non-Ethernet media, this value is equal to the dot1dRegenUserPriority value for the ingress port and media-specific user priority. INTEGER .1.3.6.1.2.1.17.6.1.2.3.1.1 |
dot1dTrafficClassThe Traffic Class the received frame is mapped to.rw INTEGER .1.3.6.1.2.1.17.6.1.2.3.1.2 |
dot1dPortOutboundAccessPriorityTableA table mapping Regenerated User Priority to Outbound Access Priority. This is a fixed mapping for all port types, with two options for 802.5 Token Ring. SEQUENCE OF Dot1dPortOutboundAccessPriorityEntry .1.3.6.1.2.1.17.6.1.2.4 |
dot1dPortOutboundAccessPriorityEntryRegenerated User Priority to Outbound Access Priority mapping. Dot1dPortOutboundAccessPriorityEntry .1.3.6.1.2.1.17.6.1.2.4.1 |
dot1dPortOutboundAccessPriorityThe Outbound Access Priority the received frame is mapped to.ro INTEGER .1.3.6.1.2.1.17.6.1.2.4.1.1 |
dot1dGarp OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.1.3 |
dot1dPortGarpTableA table of GARP control information about every bridge port. This is indexed by dot1dBasePort. SEQUENCE OF Dot1dPortGarpEntry .1.3.6.1.2.1.17.6.1.3.1 |
dot1dPortGarpEntryGARP control information for a bridge port. Dot1dPortGarpEntry .1.3.6.1.2.1.17.6.1.3.1.1 |
dot1dPortGarpJoinTimeThe GARP Join time, in centiseconds.rw TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.17.6.1.3.1.1.1 |
dot1dPortGarpLeaveTimeThe GARP Leave time, in centiseconds.rw TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.17.6.1.3.1.1.2 |
dot1dPortGarpLeaveAllTimeThe GARP LeaveAll time, in centiseconds.rw TimeInterval (SNMPv2-TC) .1.3.6.1.2.1.17.6.1.3.1.1.3 |
dot1dGmrp OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.1.4 |
dot1dPortGmrpTableA table of GMRP control and status information about every bridge port. Augments the dot1dBasePortTable. SEQUENCE OF Dot1dPortGmrpEntry .1.3.6.1.2.1.17.6.1.4.1 |
dot1dPortGmrpEntryGMRP control and status information for a bridge port. Dot1dPortGmrpEntry .1.3.6.1.2.1.17.6.1.4.1.1 |
dot1dPortGmrpStatusThe administrative state of GMRP operation on this port. The value enabled(1) indicates that GMRP is enabled on this port in all VLANs as long as dot1dGmrpStatus is also enabled(1). A value of disabled(2) indicates that GMRP is disabled on this port in all VLANs: any GMRP packets received will be silently discarded and no GMRP registrations will be propagated from other ports. Setting this to a value of enabled(1) will be stored by the agent but will only take effect on the GMRP protocol operation if dot1dGmrpStatus also indicates the value enabled(1). This object affects all GMRP Applicant and Registrar state machines on this port. A transition from disabled(2) to enabled(1) will cause a reset of all GMRP state machines on this port.rw EnabledStatus .1.3.6.1.2.1.17.6.1.4.1.1.1 |
dot1dPortGmrpFailedRegistrationsThe total number of failed GMRP registrations, for any reason, in all VLANs, on this port.ro Counter32 .1.3.6.1.2.1.17.6.1.4.1.1.2 |
dot1dPortGmrpLastPduOriginThe Source MAC Address of the last GMRP message received on this port.ro MacAddress (SNMPv2-TC) .1.3.6.1.2.1.17.6.1.4.1.1.3 |
pBridgeConformance OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.2 |
pBridgeGroups OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.2.1 |
pBridgeExtCapGroupA collection of objects indicating the optional capabilites of the device. Unknown .1.3.6.1.2.1.17.6.2.1.1 |
pBridgeDeviceGmrpGroupA collection of objects providing device-level control for the Multicast Filtering extended bridge services. Unknown .1.3.6.1.2.1.17.6.2.1.2 |
pBridgeDevicePriorityGroupA collection of objects providing device-level control for the Priority services. Unknown .1.3.6.1.2.1.17.6.2.1.3 |
pBridgeDefaultPriorityGroupA collection of objects defining the User Priority applicable to each port for media which do not support native User Priority. Unknown .1.3.6.1.2.1.17.6.2.1.4 |
pBridgeRegenPriorityGroupA collection of objects defining the User Priorities applicable to each port for media which support native User Priority. Unknown .1.3.6.1.2.1.17.6.2.1.5 |
pBridgePriorityGroupA collection of objects defining the traffic classes within a bridge for each evaluated User Priority. Unknown .1.3.6.1.2.1.17.6.2.1.6 |
pBridgeAccessPriorityGroupA collection of objects defining the media dependent outbound access level for each priority. Unknown .1.3.6.1.2.1.17.6.2.1.7 |
pBridgePortGarpGroupA collection of objects providing port level control and status information for GARP operation. Unknown .1.3.6.1.2.1.17.6.2.1.8 |
pBridgePortGmrpGroupA collection of objects providing port level control and status information for GMRP operation. Unknown .1.3.6.1.2.1.17.6.2.1.9 |
pBridgeHCPortGroupA collection of objects providing 64-bit statistics counters for high capacity bridge ports. Unknown .1.3.6.1.2.1.17.6.2.1.10 |
pBridgePortOverflowGroupA collection of objects providing overflow statistics counters for high capacity bridge ports. Unknown .1.3.6.1.2.1.17.6.2.1.11 |
pBridgeCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.17.6.2.2 |
pBridgeComplianceThe compliance statement for device support of Priority and Multicast Filtering extended bridging services. Unknown .1.3.6.1.2.1.17.6.2.2.1 |
More MIBs from Default
Browse all DefaultMIBs →SNMP MIB module
The AVAYA-WLAN-MIB provides SNMP-based management and monitoring capabilities for Avaya wireless LAN infrastructure, enabling the collection of performance metrics such as access point status, client association counts, signal strength, and radio interface statistics. This module facilitates the tracking of WLAN-specific events and configuration parameters to support network availability and troubleshooting within Avaya wireless deployments.
The VMWARE-NSX-MIB enables SNMP-based monitoring and management of VMware NSX-T Data Center virtual network infrastructure, exposing metrics for logical switches, routers, distributed firewalls, and overlay tunnel states. It facilitates the tracking of Layer 2 through Layer 7 service instances, including access control lists, Quality of Service policies, and virtual network topology changes within the software-defined networking environment.
Standard SNMP MIB module defining data structures for 923switch.m.
Standard SNMP MIB module defining data structures for CTATX-MIB.
SNMP MIB module