CISCO-ENTITY-PROVISIONING-MIB

All MIBs › CISCO-ENTITY-PROVISIONING-MIB

Organization: Cisco Systems, Inc.

Last Updated: 1999-07-08

Category: Cisco Devices, Device Management, Hardware and Environment

Description: Manages provisioning operations for Cisco hardware entities, tracking module insertion, activation, and configuration deployment.

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-ENTITY-PROVISIONING-MIB?

CISCO-ENTITY-PROVISIONING-MIB is a Cisco vendor MIB that manages provisioning of "container" class physical entities, placeholders that let a network manager pre-configure a slot, chassis, or module before the actual hardware is physically installed. It exposes container status objects indicating whether a container is equipped, detected, and its overall provisioning state, letting operators prepare configuration for hardware that will be installed later (a scenario the MIB's description explicitly frames around carriers pre-configuring service ahead of a technician visit). This is a hardware lifecycle/status monitoring MIB: it tracks whether expected physical hardware has actually been detected in a slot versus merely provisioned, which is valuable for catching a mismatch between planned and actual equipment installation (e.g., a card that was configured but never physically inserted). It builds directly on the standard ENTITY-MIB (RFC 6933/4133), extending its physical-entity model with a provisioning/container concept, and includes its own notifications for provisioning state changes. It is deployed on Cisco chassis-based platforms (routers/switches with modular line cards) where carriers or enterprises pre-provision slots ahead of physical hardware installation. Engineers can download the CISCO-ENTITY-PROVISIONING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ENTITY-PROVISIONING-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 router/switch

Monitoring Examples

A provisioning system would create entries in ceProvContainerTable/ceProvContainerEntry and monitor ceProvContainerStatus to track whether a pre-configured slot is still pending, and check ceProvContainerEquipped versus ceProvContainerDetected to determine whether a physical card is now recognized as installed. A mismatch, a container marked as equipped/provisioned but never showing as detected, would indicate a technician has not yet installed the expected hardware or that the card failed to come up, and ceProvMIBNotifications would fire to alert operators of that state change.

What Can Be Monitored

physical container provisioning status
container equipped state
container detected (physical presence) state
provisioning state-change notifications

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From ENTITY-MIB

entPhysicalIndex

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

AutonomousType

How to Use in IPNetwork Monitor

Example using ceProvContainerStatus OID:

Select a Cisco modular chassis router/switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type ceProvContainerStatus into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The equipment status of the container — unequipped, provisioned, mismatched, invalid, equipped, or failed. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is 'mismatched', 'invalid', or 'failed', since 'unequipped'/'provisioned'/'equipped' are all normal depending on whether a physical entity is present in this container slot. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoEntityProvMIB	1.3.6.1.4.1.9.9.139			This MIB module defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'container' to hold a specified physical entity. This allows a management client to configure the specified physical entity, including all of its subordinates physical entities, before installation. Consider a network manager of a CLEC (Competitive Local Exchange Carrier) planning for the installation of the hardware necessary to support several new subscribers. This network manager wants to pre-configure the ADSL (Asymmetric Digital Subscriber Loop) modems that will support these subscribers, thereby reducing the bring-up time once they arrive. Under normal circumstances this would not be possible. However, provisioning allows the network manager to 'create' the physical entities that represent the new modems. In essence, the device simulates the installation of the new modules into the system. This has the effect of creating all conceptual rows in all the necessary tables that support the physical entity and all its subordinate physical entities (e.g., entPhysicalTable, entAliasMappingTable, and ifTable).
ciscoEntityProvMIBObjects	1.3.6.1.4.1.9.9.139.1
ceProvContainerTable	1.3.6.1.4.1.9.9.139.1.1		not-accessible	This table extends some entries in the entPhysicalTable (see ENTITY-MIB for further details). A entry appears in this table for a physical entity matching the following criteria: 1) Its entPhysicalClass object has a value of 'container'; 2) It can contain one (but not multiple) physical entity; and, 3) It supports provisioning.
ceProvContainerEntry	1.3.6.1.4.1.9.9.139.1.1.1		not-accessible	The attributes that support the provisioning of a physical entity of the 'container' class (i.e., a physical entity having an entPhysicalClass of 'container').
INT ceProvContainerStatusEx	1.3.6.1.4.1.9.9.139.1.1.1.1	INTEGER	read-only	This object represents the equipment status of the container: 'unequipped' The container neither holds a physical entity, nor has it been provisioned to hold a physical entity. 'provisioned' The container does not hold a physical entity However, it has been provisioned to hold a physical entity of a particular type. This physical entity appears in the entPhysicalTable as a child of the container. 'mismatched' The container holds a valid physical entity that does not match the type of physical entity for which the container has been previously provisioned. 'invalid' The container holds a recognized physical entity that the container is not capable of supporting, or the container holds an unrecognized physical entity. 'equipped' The container holds a valid physical entity for which the container has been previously provisioned to hold. 'failed' The container holds a valid physical entity that has become totally inoperable and incapable of providing service.
OID ceProvContainerEquipped	1.3.6.1.4.1.9.9.139.1.1.1.2	AutonomousType	read-write	This object specifies the vendor type of the physical entity for which this container has been provisioned to hold. If the container has no provisioning, then the value of this object is { 0 0 }. For more information concerning 'vendor type', see the definition of the entPhysicalVendorType object in the ENTITY-MIB.
OID ceProvContainerDetected	1.3.6.1.4.1.9.9.139.1.1.1.3	AutonomousType	read-only	This object specifies the vendor type of the physical entity held by the container. If the container does not hold a physical entity, then the value of this object is { 0 0 }. For more information concerning 'vendor type', see the definition of the entPhysicalVendorType object in the ENTITY-MIB.
ceProvMIBNotificationsPrefix	1.3.6.1.4.1.9.9.139.2
ceProvMIBNotifications	1.3.6.1.4.1.9.9.139.2.0
ceProvMIBConformance	1.3.6.1.4.1.9.9.139.3
ceProvMIBCompliances	1.3.6.1.4.1.9.9.139.3.1
ceProvMIBCompliance	1.3.6.1.4.1.9.9.139.3.1.1			The compliance statement for entities that implement the CISCO-ENTITY-PROVISIONING-MIB. Implementation of this MIB is strongly recommended for any platform targeted for a carrier-class environment.
ceProvMIBGroups	1.3.6.1.4.1.9.9.139.3.2
ceProvContainerGroup	1.3.6.1.4.1.9.9.139.3.2.1			A collection of attributes that support provisioning of a physical entity of the 'container' class.

RFC description

Extends ENTITY-MIB to support pre-provisioning of container class physical entities on Cisco devices, enabling network managers to configure modular equipment before installation and reduce bring-up time.

Start monitoring Cisco modular chassis router/switch 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-ENTITY-PROVISIONING-MIB