CIRCUIT-IF-MIB.mib object view, vendor RFC

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file CIRCUIT-IF-MIB and use it to monitor vendor specific OID's.

CIRCUIT-IF-MIB file content

Object view of CIRCUIT-IF-MIB:

Scalar Object
ciCircuitEntry	.1.3.6.1.2.1.94.1.1.1
An entry in the Circuit Interface Circuit Table.
ciIfMapEntry	.1.3.6.1.2.1.94.1.2.1
An entry in the Circuit Interface Map Table.
ciIfLastChange	.1.3.6.1.2.1.94.1.3
The value of sysUpTime at the most recent change to ciCircuitStatus for any row in ciCircuitTable.
ciIfNumActive	.1.3.6.1.2.1.94.1.4
The number of active rows in ciCircuitTable.
Tabular Object
ciCircuitObject	.1.3.6.1.2.1.94.1.1.1.1
This value contains the RowPointer that uniquely describes the circuit that is to be added to this table. Any RowPointer that will force the size of OBJECT IDENTIFIER of the row to grow beyond the legal limit MUST be rejected. The purpose of this object is to point a network manager to the table in which the circuit was created as well as define the circuit on which the interface is defined. Valid tables for this object include the frCircuitTable from the Frame Relay DTE MIB(FRAME-RELAY-DTE-MIB), the frPVCEndptTable from the Frame Relay Service MIB (FRNETSERV-MIB), and the aal5VccTable from the ATM MIB (ATM MIB). However, including circuits from other MIB tables IS NOT prohibited.
ciCircuitFlow	.1.3.6.1.2.1.94.1.1.1.2
The direction of data flow through the circuit for which the virtual interface is defined. The following define the information that the virtual interface will report. transmit(1) - Only transmitted frames receive(2) - Only received frames both(3) - Both transmitted and received frames. It is recommended that the ifDescr of the circuit interfaces that are not both(3) SHOULD have text warning the operators that the particular interface represents only half the traffic on the circuit.
ciCircuitStatus	.1.3.6.1.2.1.94.1.1.1.3
The status of the current row. This object is used to add, delete, and disable rows in this table. When the status changes to active(1), a row will also be added to the interface map table below and a row will be added to the ifTable. These rows SHOULD not be removed until the status is changed from active(1). The value of ifIndex for the row that is added to the ifTable is determined by the agent and MUST follow the rules of the ifTable. The value of ifType for that interface will be frDlciEndPt(193) for a frame relay circuit, atmVciEndPt(194) for an ATM circuit, or another ifType defining the circuit type for any other circuit. When this object is set to destroy(6), the associated row in the interface map table will be removed and the ifIndex will be removed from the ifTable. Removing the ifIndex MAY initiate a chain of events that causes changes to other tables as well. The rows added to this table MUST have a valid object identifier for ciCircuitObject. This means that the referenced object must exist and it must be in a table that supports circuits. The object referenced by ciCircuitObject MUST exist prior to transitioning a row to active(1). If at any point the object referenced by ciCircuitObject does not exist or the row containing it is not in the active(1) state, the status SHOULD either age out the row or report notReady(3). The effects transitioning from active(1) to notReady(3) are the same as those caused by setting the status to destroy(6). Each row in this table relies on information from other MIB modules. The rules persistence of data SHOULD follow the same rules as those of the underlying MIB module. For example, if the circuit defined by ciCircuitObject would normally be stored in non-volatile memory, then the row SHOULD also be non-volatile.
ciCircuitIfIndex	.1.3.6.1.2.1.94.1.1.1.4
The ifIndex that the agent assigns to this row.
ciCircuitCreateTime	.1.3.6.1.2.1.94.1.1.1.5
This object returns the value of sysUpTime at the time the value of ciCircuitStatus last transitioned to active(1). If ciCircuitStatus has never been active(1), this object SHOULD return 0.
ciCircuitStorageType	.1.3.6.1.2.1.94.1.1.1.6
The storage type used for this row.
ciIfMapObject	.1.3.6.1.2.1.94.1.2.1.1
This value contains the value of RowPointer that corresponds to the current ifIndex.
ciIfMapFlow	.1.3.6.1.2.1.94.1.2.1.2
The value contains the value of ciCircuitFlow that corresponds to the current ifIndex.
Table
ciCircuitTable	.1.3.6.1.2.1.94.1.1
The Circuit Interface Circuit Table.
ciIfMapTable	.1.3.6.1.2.1.94.1.2
The Circuit Interface Map Table.
Object Identifier
circuitIfMIB	.1.3.6.1.2.1.94
The MIB module to allow insertion of selected circuit into the ifTable.
ciObjects	.1.3.6.1.2.1.94.1
ciCapabilities	.1.3.6.1.2.1.94.2
ciConformance	.1.3.6.1.2.1.94.3
ciMIBGroups	.1.3.6.1.2.1.94.3.1
ciMIBCompliances	.1.3.6.1.2.1.94.3.2
Group
ciCircuitGroup	.1.3.6.1.2.1.94.3.1.1
A collection of required objects providing information from the circuit table.
ciIfMapGroup	.1.3.6.1.2.1.94.3.1.2
A collection of required objects providing information from the interface map table.
ciStatsGroup	.1.3.6.1.2.1.94.3.1.3
A collection of statistical metrics used to help manage the ciCircuitTable.