FORCES-MIB
The FORCES-MIB provides managed object definitions for monitoring and controlling Forwarding and Control Element Separation (ForCES) protocol interactions between Control Elements and Forwarding Elements. It exposes specific metrics for managing protocol sessions, logical unit states, and resource allocation within disaggregated forwarding architectures.
Imported Objects
Objects
24 total| Object Name |
|---|
forcesMibThis MIB module contains managed object definitions
for the ForCES Protocol.
Copyright (c) 2010 IETF Trust and the persons identified
as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the
IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC 5813;
see the RFC itself for full legal notices. MODULE-IDENTITY .1.3.6.1.4.1.3727.20.20.3.1.187 |
forcesMibNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.187.0 |
forcesAssociationEntryUpThis notification is generated as soon
as an association enters the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations. NOTIFICATION-TYPE .1.3.6.1.4.1.3727.20.20.3.1.187.0.1 |
forcesAssociationEntryDownThis notification is generated as soon
as an association leaves the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations. NOTIFICATION-TYPE .1.3.6.1.4.1.3727.20.20.3.1.187.0.2 |
forcesAssociationEntryUpStatsThis notification is generated as soon
as an association enters the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations. NOTIFICATION-TYPE .1.3.6.1.4.1.3727.20.20.3.1.187.0.3 |
forcesAssociationEntryDownStatsThis notification is generated as soon
as an association leaves the UP state.
Note that these notifications are not
throttled as the CE itself should
throttle the setup of associations. NOTIFICATION-TYPE .1.3.6.1.4.1.3727.20.20.3.1.187.0.4 |
forcesMibObjects OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.187.1 |
forcesLatestProtocolVersionSupportedThe ForCES protocol version supported by the CE.
The current protocol version is 1.
Note that the CE must also allow interaction
with FEs supporting earlier versions.ro ForcesProtocolVersion .1.3.6.1.4.1.3727.20.20.3.1.187.1.1 |
forcesAssociations OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.187.1.2 |
forcesAssociationTableThe (conceptual) table of associations. SEQUENCE OF ForcesAssociationEntry .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1 |
forcesAssociationEntryA (conceptual) entry for one association. ForcesAssociationEntry .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1 |
forcesAssociationCEIDThe ForCES ID of the CE. ForcesID .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.1 |
forcesAssociationFEIDThe ForCES ID of the FE. ForcesID .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.2 |
forcesAssociationRunningProtocolVersionThe current ForCES protocol version used in
this association.
The current protocol version is 1.ro ForcesProtocolVersion .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.3 |
forcesAssociationTimeUpThe value of sysUpTime at the time this
association entered the UP state.
If this association started prior to the last
initialization of the network subsystem, then
this object contains a zero value.
This object allows to uniquely identify
associations with the same CE and FE IDs.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.4 |
forcesAssociationTimeDownThe value of sysUpTime at the time this
association left the UP state.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.5 |
forcesAssociationHBMsgSentA counter of how many Heartbeat messages have
been sent by the CE on this association
since the association entered the UP state.
Discontinuities in the value of this counter
can occur at reinitialization of the management
system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime.ro ZeroBasedCounter32 (RMON2-MIB) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.6 |
forcesAssociationHBMsgReceivedA counter of how many Heartbeat messages
have been received by the CE on this association
since the association entered the UP state.
Discontinuities in the value of this counter
can occur at reinitialization of the management
system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime.ro ZeroBasedCounter32 (RMON2-MIB) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.7 |
forcesAssociationOperMsgSentA counter of how many messages other than
Heartbeat (i.e., Config and Query)
have been sent by the CE on this association
since the association entered the UP state.
Discontinuities in the value of this counter
can occur at reinitialization of the management
system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime.ro ZeroBasedCounter32 (RMON2-MIB) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.8 |
forcesAssociationOperMsgReceivedA counter of how many messages other than
Heartbeat (i.e., Config response, Query response,
event notification, and packet redirect)
have been received by the CE on this association
since the association entered the UP state.
Discontinuities in the value of this counter
can occur at reinitialization of the management
system, and at other times as indicated by the
value of forcesAssociationCounterDiscontinuityTime.ro ZeroBasedCounter32 (RMON2-MIB) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.9 |
forcesAssociationCounterDiscontinuityTimeThe value of sysUpTime on the most recent occasion
at which any one or more of this association's
counters suffered a discontinuity. The relevant
counters are the specific instances associated with
this association of any ZeroBasedCounter32 object
contained in the forcesAssociationTable. If no
such discontinuities have occurred since the last
reinitialization of the local management subsystem,
then this object contains a zero value.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.3727.20.20.3.1.187.1.2.1.1.10 |
forcesMibConformance OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.187.2 |
forcesMibCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.187.2.1 |
forcesMibGroups OBJECT IDENTIFIER .1.3.6.1.4.1.3727.20.20.3.1.187.2.2 |
More MIBs from Pseudowire Edge-to-Edge Emulation (PWE3)
Browse all Pseudowire Edge-to-Edge Emulation (PWE3)MIBs →The SUPERCAPBATTERY-MIB module provides SNMP objects to monitor the voltage, current, temperature, and remaining capacity of supercapacitor-based backup power units and their associated battery management systems on networked infrastructure. It enables administrators to track charge levels and health status of these energy storage components to prevent unexpected device shutdowns during power failures.
The VSL2-LINE-MIB module provides a unified management framework for monitoring VDSL2, ADSL, ADSL2, and ADSL2+ physical line interfaces, exposing standardized counters and status objects defined by ITU-T G.99x series and DSL Forum TR-129 specifications. It facilitates the collection of critical performance metrics such as line attenuation, signal-to-noise ratio, and error counts (FEC/HEC) across these copper-based broadband technologies via the SNMP MIB-2 transmission hierarchy.
SNMP MIB module
SNMP MIB module
The OSPFV3-MIB provides SNMP-based monitoring and management of OSPFv3 routing processes, exposing key metrics such as neighbor adjacency states, interface link-local addresses, LSDB synchronization status, and SPF calculation statistics for IPv6 networks.
SNMP MIB module