Cisco Cisco Prime Cable Provisioning 5.1 Release Notes

AddFile

Adding an invalid MIB file, 
<arris_cm.mib>.

Failed to add MIB file <arris_cm.mib>. Not a 
valid MIB file: <arris_cm.mib>.

Adding a MIB file <arris_cm.mib> 
without adding the parent MIB 
<ARRIS-MIB>.

Failed to add MIB file <arris_cm.mib>. Cannot 
find the dependent MIB file <ARRIS-MIB> in 
database.

Adding a new MIB file with a name 
that already exists in the database, 
<SNMPv2-SMI>.

Failed to add MIB file <SNMPv2-SMI>. File 
already exist in the database.

Adding a MIB file which is already 
available in database 
<URI-TC-MIB>. Adding the same 
MIB file with a different name 
<Renamed_URI-TC-MIB>.

Failed to add MIB file 
<Renamed_URI-TC-MIB.MIB> module 
<URI-TC-MIB> already exist in database with 
file name <uri-tc-mib>.

DeleteFile

Delete a MIB file <ARRIS-MIB> 
which is a parent for some other 
MIBs.

Failed to delete MIB file <arris-mib>. MIB file(s) 
<arris_cm.mib, arris_mta_pp.mib> are dependent 
on MIB file <arris-mib>.

Delete a MIB file which is loaded. 
(configured in System Defaults MIB 
LIST).

Failed to delete MIB file <arris-mib>. The MIB 
file is currently in use. Requires System Default 
configuration to be updated under administrator's 
guidance.

ReplaceFile Replace a MIB file <ARRIS-MIB> 

with invalid content (raw text file).

Replace operation failed for MIB file 
<arris-mib>. Not a valid MIB file: 
<ARRIS-MIB>. 

Replace a MIB file <ARRIS-MIB> 
with another valid MIB file 
<arris_cm.mib>.

Replace operation failed for MIB file 
<arris-mib.MIB>. MIB module 
<ARRIS-CM-DEVICE-MIB> conflicts with 
existing MIB module <ARRIS-MIB>.

Replace a MIB file 
<arris_mta_pp.mib> without adding 
the new parent MIB 
<ARRIS-ROUTER-DEVICE-MIB>.

Unable to replace the MIB <arris_mta_pp.mib>. 
Cannot find the dependent MIB module 
<ARRIS-ROUTER-DEVICE-MIB> in database. 

Replace a MIB file <ARRIS-MIB> 
by removing few OIDs which are 
being used by its children.

Replace operation failed for MIB file 
<arris-mib.MIB>. MIB file <arris-mib.MIB> is 
not compatible with child MIB(s).

The validations that are added in the API for the MIB management are explained in the following 
table:

The runCfgUtil script will continue to use the MIBs from the file system (BPR_HOME/rdu/mibs) and 
not from the RDU Database.