FORCES-MIB

All MIBs › FORCES-MIB

Organization: IETF Forwarding and Control Element Separation (ForCES) Working Group

Last Updated: 2010-03-10

Category: IP and Core Protocols

Description: Defines a read-only MIB for monitoring Forwarding and Control Element Separation (ForCES) protocol associations.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring FORCES-MIB with a free 30-day trial of IPNetwork Monitor.

What Is FORCES-MIB?

FORCES-MIB is a vendor-neutral, IETF standards-based MIB for read-only monitoring of the Forwarding and Control Element Separation (ForCES) protocol, which defines the standardized interface between a network element's control plane and forwarding plane in disaggregated router architectures. However, the sample data provided for this MIB contains no object names, so its specific tables and leaf objects cannot be confirmed here. Conceptually, such a MIB would expose associations between Control Elements (CEs) and Forwarding Elements (FEs), letting an operator monitor whether the control-to-forwarding association for a router is currently up, which is a software-level indicator of whether the router's control and data planes are properly synchronized. It is explicitly tied to the IETF ForCES protocol standard and has no vendor dependency. As a FORCES-MIB reference, it would be deployed on disaggregated router platforms implementing a split control-plane/forwarding-plane architecture per the ForCES specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in FORCES-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

vendor-neutral, standards-based IETF ForCES MIB, applicable to disaggregated routers with separate control and forwarding elements

Monitoring Examples

No sample objects were supplied for this MIB, so a concrete polling example naming real object names cannot be given honestly; the module description indicates it defines read-only managed objects for the ForCES protocol, but the actual table and leaf names are not available here. In principle such a MIB would let an operator confirm whether a CE-FE association is established and healthy. Consulting the actual FORCES-MIB source would be required to identify pollable objects for a real monitoring setup.

Imported Objects

From RMON2-MIB

ZeroBasedCounter32

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
mib-2

From SNMPv2-TC

TEXTUAL-CONVENTION
TimeStamp

OIDs

OID symbolic	OID numeric	Type	Access	Description
forcesMib	1.3.6.1.2.1.187			This 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.
forcesMibNotifications	1.3.6.1.2.1.187.0
NTF forcesAssociationEntryUp	1.3.6.1.2.1.187.0.1			This 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.
NTF forcesAssociationEntryDown	1.3.6.1.2.1.187.0.2			This 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.
NTF forcesAssociationEntryUpStats	1.3.6.1.2.1.187.0.3			This 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.
NTF forcesAssociationEntryDownStats	1.3.6.1.2.1.187.0.4			This 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.
forcesMibObjects	1.3.6.1.2.1.187.1
FOR forcesLatestProtocolVersionSupported	1.3.6.1.2.1.187.1.1	ForcesProtocolVersion	read-only	The 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.
forcesAssociations	1.3.6.1.2.1.187.1.2
forcesAssociationTable	1.3.6.1.2.1.187.1.2.1		not-accessible	The (conceptual) table of associations.
forcesAssociationEntry	1.3.6.1.2.1.187.1.2.1.1		not-accessible	A (conceptual) entry for one association.
FOR forcesAssociationCEID	1.3.6.1.2.1.187.1.2.1.1.1	ForcesID	not-accessible	The ForCES ID of the CE.
FOR forcesAssociationFEID	1.3.6.1.2.1.187.1.2.1.1.2	ForcesID	not-accessible	The ForCES ID of the FE.
FOR forcesAssociationRunningProtocolVersion	1.3.6.1.2.1.187.1.2.1.1.3	ForcesProtocolVersion	read-only	The current ForCES protocol version used in this association. The current protocol version is 1.
TIM forcesAssociationTimeUp	1.3.6.1.2.1.187.1.2.1.1.4	TimeStamp	read-only	The 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.
TIM forcesAssociationTimeDown	1.3.6.1.2.1.187.1.2.1.1.5	TimeStamp	accessible-for-notify	The value of sysUpTime at the time this association left the UP state.
NUM forcesAssociationHBMsgSent	1.3.6.1.2.1.187.1.2.1.1.6	ZeroBasedCounter32	read-only	A 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.
NUM forcesAssociationHBMsgReceived	1.3.6.1.2.1.187.1.2.1.1.7	ZeroBasedCounter32	read-only	A 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.
NUM forcesAssociationOperMsgSent	1.3.6.1.2.1.187.1.2.1.1.8	ZeroBasedCounter32	read-only	A 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.
NUM forcesAssociationOperMsgReceived	1.3.6.1.2.1.187.1.2.1.1.9	ZeroBasedCounter32	read-only	A 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.
TIM forcesAssociationCounterDiscontinuityTime	1.3.6.1.2.1.187.1.2.1.1.10	TimeStamp	read-only	The 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.
forcesMibConformance	1.3.6.1.2.1.187.2
forcesMibCompliances	1.3.6.1.2.1.187.2.1
forcesMibCompliance	1.3.6.1.2.1.187.2.1.1			The compliance statement for routers running ForCES and implementing the ForCES MIB.
forcesMibGroups	1.3.6.1.2.1.187.2.2
forcesNotificationGroup	1.3.6.1.2.1.187.2.2.1			A collection of notifications for signaling important ForCES events.
forcesMibGroup	1.3.6.1.2.1.187.2.2.2			A collection of objects to support management of ForCES routers.
forcesNotificationStatsGroup	1.3.6.1.2.1.187.2.2.3			A collection of optional notifications for signaling important ForCES events including statistics.
forcesStatsGroup	1.3.6.1.2.1.187.2.2.4			A collection of optional objects to provide extra information about the associations. There is no protocol reason to keep such information, but these objects can be very useful in debugging connectivity problems.

RFC description

Management information for Forwarding and Control Element Separation (ForCES) Protocol, enabling separation of forwarding and control planes.

Start monitoring Vendor-neutral disaggregated router, any manufacturer (IETF ForCES protocol, RFC 5813) 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.

Download FORCES-MIB

What Is FORCES-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description