CISCO-IF-LINK-CONFIG-MIB

All MIBs › CISCO-IF-LINK-CONFIG-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2001-10-05

Category: Cisco Devices, Network Interfaces

Description: Configures physical interface link parameters such as speed, duplex mode, and auto-negotiation settings.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is CISCO-IF-LINK-CONFIG-MIB?

CISCO-IF-LINK-CONFIG-MIB is a Cisco-proprietary MIB for configuring bulk distribution, a feature that demultiplexes traffic from a single higher-bandwidth source interface down onto one or more lower-bandwidth target-module interfaces. It exposes a configuration table (cilConfTable) mapping each source interface to a target module/interface and framing type, together with row-creation and status controls. Although primarily a configuration MIB rather than a hardware-health MIB, it supports monitoring software/configuration state by exposing the operational row status of each bulk-distribution mapping, letting an operator confirm whether a given interface-to-module linkage is active, not-in-service, or failed to establish. It relies on the standard IF-MIB ifTable for the interface indices it references. It is typically deployed on Cisco modular chassis platforms, such as channelized or aggregation line cards, where a high-speed interface's traffic must be split out to lower-speed target interfaces. Engineers can download the CISCO-IF-LINK-CONFIG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-IF-LINK-CONFIG-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

Cisco modular chassis line cards/aggregation modules

Monitoring Examples

cilConfTable/cilConfEntry maps each cilSourceInterface to a cilTargetModuleInterface with a configured cilTargetModuleFramingType and a cilRowStatus. An operator would poll cilRowStatus for each entry to verify a bulk-distribution mapping is active(1) rather than notInService or notReady, which would indicate the target module linkage failed to establish; checking cilTargetModuleFramingType confirms the expected framing, such as channelized, is applied on the linked interface.

What Can Be Monitored

bulk-distribution mapping row status
source-to-target interface linkage
target module framing type configuration

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

CiscoLocationSpecifier

From IF-MIB

InterfaceIndex

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoIfLinkConfigMIB	1.3.6.1.4.1.9.9.175			The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interfaces). Terminology : bulk-distribution : The bulk distribution is the feature by which a line/interface on one module can replace the line for the other. bulk-distribution module : The module which links its interfaces to the target module. target module : A module that gets incoming traffic from a bulk distribution module rather than from a back card. The Module which supports bulk distribution, converts traffic from its lines (may be T3, OC-N) to lines on the target module (may be T3, T1 etc). The bulk distribution is achieved by having a point-to-point connection (bulk-distribution bus) between the bulk-distribution module and the target module. The benefit of bulk distribution is that the target module need not have the back cards. The lines/interfaces from bulk-distribution module will be used as lines for the target module. An example is given here on linking interfaces. \|------------------------------------------------\| \| \| \| \|------------------------------\| \| \| \| \| \| \| \| \| \| \|-------------\| \| \| Ta\|rget Module \| \| \| \| \| ------- ------- ------- --------------- \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| T1 \| \| T1 \| \|T1 \| \| Bulk \| \|card \| \|card \| \|card \| \| Distribution \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| Module \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| (T3 card) \| \| \| \| \| \| \| \| \| ------- ------- ------- ---------------
cilConfigMIBObjects	1.3.6.1.4.1.9.9.175.1
cilConfig	1.3.6.1.4.1.9.9.175.1.1
cilConfTable	1.3.6.1.4.1.9.9.175.1.1.1		not-accessible	The interface link configuration table.
cilConfEntry	1.3.6.1.4.1.9.9.175.1.1.1.1		not-accessible	An entry in the cilConfTable. This entry is used for linking an interface identified by cilSourceInterface to an interface identified by cilTaregetModuleInterface. The entries are created and deleted using the cilRowStatus object. An interface on the bulk-distribution module cannot be linked to multiple interfaces in the target module.
NUM cilSourceInterface	1.3.6.1.4.1.9.9.175.1.1.1.1.1	InterfaceIndex	not-accessible	An interface of the bulk-distribution module (Source) which will be linked with the interface of the target module. It represents an entry in the ifTable.
CIS cilTargetModuleInterface	1.3.6.1.4.1.9.9.175.1.1.1.1.2	CiscoLocationSpecifier	read-create	Location of the managed entity on the target module. Following is the supported format for this object and all the values must be present. shelf=, slot=, subSlot= port =. The zero length value for this object is not supported.
ROW cilRowStatus	1.3.6.1.4.1.9.9.175.1.1.1.1.3	RowStatus	read-create	This object is used to create a new row or modify or delete an existing row in the table. The cilTargetModuleFramingType need not be specified to create a row. If cilTargetModuleFramingType is not specified, a default value will be assumed as described in the description of cilTargetModuleFramingType.
INT cilTargetModuleFramingType	1.3.6.1.4.1.9.9.175.1.1.1.1.4	INTEGER	read-create	This object identifies the framing type of the target interface. notApplicable(1) can not be set. dsx1ESF Extended SuperFrame DS1 (T1.107) dsx1D4 AT&T D4 format DS1 (T1.107) Default value is dsx1ESF(3) if cilTargetModuleInterface is a T1 interface and sonet/sdh byte-synchronous mapping is used on the cilSourceInterface. Otherwise, the default value is notApplicable(1).
cilConfigMIBConformance	1.3.6.1.4.1.9.9.175.3
cilConfigMIBCompliances	1.3.6.1.4.1.9.9.175.3.1
cilConfigMIBCompliance	1.3.6.1.4.1.9.9.175.3.1.1			The Compliance statement for interface link configuration group. This has been replaced by the cilConfigMIBComplianceRev1 statement.
cilConfigMIBComplianceRev1	1.3.6.1.4.1.9.9.175.3.1.2			The Compliance statement for interface link configuration group. This statement replaces cilConfigMIBCompliance statement.
cilConfigMIBGroups	1.3.6.1.4.1.9.9.175.3.2
cilConfMIBGroup	1.3.6.1.4.1.9.9.175.3.2.1			These are objects related to interface link configuration group. This group has been replaced by cilConfMIBGroupRev1.
cilConfMIBGroupRev1	1.3.6.1.4.1.9.9.175.3.2.2			These are objects related to interface link configuration group. This group replaces the cilConfMIBGroup.

RFC description

Manages physical interface link parameters including speed, duplex mode, and auto-negotiation settings.

Start monitoring Cisco modular chassis line cards/aggregation modules 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 CISCO-IF-LINK-CONFIG-MIB

What Is CISCO-IF-LINK-CONFIG-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description