cisco-entity-provisioning-mib.mib object
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 2025 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 2025 can import MIB file cisco-entity-provisioning-mib and use it to monitor vendor specific OID's.
cisco-entity-provisioning-mib file content
Object view of cisco-entity-provisioning-mib:
| Scalar Object |
| ceProvContainerEntry |
.1.3.6.1.4.1.9.9.139.1.1.1 |
|
The attributes that support the provisioning of a physical
entity of the 'container' class (i.e., a physical entity
having an entPhysicalClass of 'container').
|
| Tabular Object |
| ceProvContainerStatus |
.1.3.6.1.4.1.9.9.139.1.1.1.1 |
|
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.
|
| ceProvContainerEquipped |
.1.3.6.1.4.1.9.9.139.1.1.1.2 |
|
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.
|
| ceProvContainerDetected |
.1.3.6.1.4.1.9.9.139.1.1.1.3 |
|
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.
|
| Table |
| ceProvContainerTable |
.1.3.6.1.4.1.9.9.139.1.1 |
|
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.
|
| Object Identifier |
| 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 |
| 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 |
| ceProvMIBGroups |
.1.3.6.1.4.1.9.9.139.3.2 |
| Group |
| 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.
|
