IEEE8021-MIRP-MIB
Standard SNMP MIB module defining data structures for IEEE8021-MIRP-MIB.
Imported Objects
Objects
12 total| Object Name |
|---|
ieee8021PbbMirpEnableStatusThe administrative status requested by management for
MIRP. The value true(1) indicates that MIRP should be enabled
on this component, on all ports for which it has not been
specifically disabled. When false(2), MIRP is disabled on all
ports. This object affects all MIRP Applicant and Registrar
state machines. A transition from false(2) to true(1) will
cause a reset of all MIRP state machines on all ports.
The value of this object MUST be retained across
reinitializations of the management system.rw TruthValue (SNMPv2-TC) .1.3.111.2.802.1.1.9.1.1.1.7 |
ieee8021PbbMirpBvidThe B-VID to which received MIRPDUs are to be assigned, or 0,
if they are to be sent on the CBP PVID.rw VlanIdOrNone (Q-BRIDGE-MIB) .1.3.111.2.802.1.1.9.1.1.1.8 |
ieee8021PbbMirpDestSelectorAn enumerated value specifying what destination_address and
vlan_identifier are to be used when the MIRP Participant
transmits an MIRPDU towards the MAC relay entity:
cbpMirpGroup (1) Use the Nearest Customer Bridge group
address from Table 8-1 with the MIRP BVID.
cbpMirpVlan (2) Use the Nearest Customer Bridge group
address from Table 8-1 with the Backbone
VLAN Identifier field from the Backbone
Service Instance table.
cbpMirpTable (3) Use the Default Backbone Destination and
Backbone VLAN Identifier fields from the
Backbone Service Instance table.
The value of this object MUST be retained across
reinitializations of the management system.rw Enumeration .1.3.111.2.802.1.1.9.1.1.1.9 |
ieee8021PbbMirpPnpEnableA Boolean value specifying the administrative status requested
by management for attaching a MIRP Participant to a PNP if
and only if this system is a Backbone Edge Bridge (BEB):
true(1) The BEB is to attach a MIRP Participant to exactly one
Port, either a management Port with no LAN connection
external to the BEB, or a PNP.
false(2) No MIRP Participant is to be present on any PNP (or
on the MAC Relay-facing side of a CBP).
The value of this object MUST be retained across
reinitializations of the management system.rw TruthValue (SNMPv2-TC) .1.3.111.2.802.1.1.9.1.1.1.10 |
ieee8021PbbMirpPnpPortNumberThe Bridge Port Number of the Provider Network Port (PNP) that
has an associated MIRP Participant, or 0, if no Bridge Port has
an associated MIRP Participant. This object indexes an entry in
the Bridge Port Table. The system SHALL ensure that either
ieee8021PbbMirpPnpPortNumber contains 0, or that the indexed
ieee8021BridgeBasePortType object contains the value
providerNetworkPort(3).ro IEEE8021BridgePortNumberOrZero (IEEE8021-TC-MIB) .1.3.111.2.802.1.1.9.1.1.1.11 |
ieee8021MirpV2MIBObjects OBJECT IDENTIFIER .ieee8021MirpMib.1 |
ieee8021MirpV2PortTableA table that contains controls for the Multiple I-SID
Registration Protocol (MIRP) state machines for all of the Ports
of a Bridge. SEQUENCE OF Ieee8021MirpV2PortEntry .ieee8021MirpMib.1.1 |
ieee8021MirpV2PortEntryEach entry contains the MIRP Participant controls for one Port. Ieee8021MirpV2PortEntry .ieee8021MirpMib.1.1.1 |
ieee8021MirpV2PortEnabledStatusThe state of MIRP operation on this port. The value
true(1) indicates that MIRP is enabled on this port,
as long as ieee8021PbbMirpEnableStatus is also enabled
for this component. When false(2) but
ieee8021PbbMirpEnableStatus is still
enabled for the device, MIRP is disabled on this port.
If MIRP is enabled on a VIP, then the MIRP Participant is
enabled on that VIP's PIP. If MIRP is enabled on none of the
VIPs on a PIP, then the MIRP Participant on the PIP is
diabled; any MIRP packets received will be silently discarded,
and no MIRP registrations will be propagated from the PIP. A
transition from all VIPs on a PIP false(2) to at least one VIP
on the PIP true(1) will cause a reset of all MIRP state
machines on this PIP.
If MIRP is enabled on any port not a VIP, then the MIRP
Participant is enabled on that port. If MIRP is
disabled on a non-VIP port, then MIRP packets received will be
silently discarded, and no MIRP registrations will be
propagated from the port. A transition from false(2) to
true(1) will cause a reset of all MIRP state machines on a
non-VIP port.
The value of this object MUST be retained across
reinitializations of the management system.rw TruthValue (SNMPv2-TC) .ieee8021MirpMib.1.1.1.1 |
ieee8021MirpV2Conformance OBJECT IDENTIFIER .ieee8021MirpMib.2 |
ieee8021MirpV2Compliances OBJECT IDENTIFIER .ieee8021MirpMib.2.1 |
ieee8021MirpV2Groups OBJECT IDENTIFIER .ieee8021MirpMib.2.2 |
More MIBs from Versa
Browse all VersaMIBs →The LLDP-EXT-DOT1-V2-MIB module extends the LLDP-V2 framework to expose IEEE 802.1Q and 802.1Qaz organizationally defined TLVs, enabling the monitoring of VLAN tagging configurations, Priority Flow Control (PFC) states, and Enhanced Transmission Selection (ETS) parameters on Layer 2 network switches. This allows administrators to verify and manage data center network flow control policies and VLAN membership attributes via SNMP.
The IEEE8021-Q-BRIDGE-MIB enables monitoring and configuration of IEEE 802.1Q VLAN-tagged bridging domains, specifically tracking VLAN membership, port filtering tables, and bridge protocol data unit (BPDU) states on Layer 2 network switches.
SNMP MIB module
The LLDP-V2-MIB module manages IEEE 802.1AB-2009 compliant Link Layer Discovery Protocol agents to monitor local system identity, remote neighbor topology, and per-port transmission statistics, specifically supporting multi-agent architectures where distinct MAC addresses are associated with a single physical port.
The IEEE8021-EVB-MIB provides SNMP management capabilities for Ethernet Virtual Bridging (EVB) devices, specifically monitoring and configuring virtual station interfaces (VSIs), virtual bridge ports, and associated bridge domain parameters as defined in IEEE 802.1Q-2014. It enables the retrieval of operational states, configuration parameters, and performance counters for virtualization features such as MAC-in-MAC encapsulation and port isolation within IEEE 802.1Q-compliant network infrastructure.
The IEEE8021-MSTP-MIB enables the monitoring and configuration of IEEE 802.1Q Multiple Spanning Tree (MSTP) instances, specifically tracking MST region definitions, instance-to-VLAN mappings, and port state transitions across bridged network devices. It provides granular visibility into MSTP topology convergence, including root bridge election status, path costs, and port roles (designated, root, blocked) to ensure loop-free Layer 2 redundancy.