Cisco Cisco Prime Cable Provisioning 5.1

In the Prime Cable Provisioning 5.1.1 migration, all the custom MIB files will be migrated to the 
database along with the default MIB files. If the user has configured the MIB file names in 
rdu.properties, the MIB files will be migrated to the database during the migration. If not, the migration 
script will get the MIB file names from the System Default configuration and migrate those files to the 
database.

The Prime Cable Provisioning database migration procedure requires that you migrate the components 
in the sequence recommended in below-mentioned sections. 

For steps 1-4, see 

.

Backup the RDU database.

Recover the backed up RDU database.

Verify the database integrity.

Backup the property files.

Migrate the RDU database along with the customer specific MIB files. Follow the steps provided in 

 along with -mibdir option explained below:

If you have added any custom MIB files in your current installation(4.2.x, 5.x), you will need 
to first back them up from $BPR_HOME/rdu/mibs/ and then copy them manually to the Prime 
Cable Provisioning 5.1.1 server. 

The backed up MIB files should be copied to a location in Prime Cable Provisioning 5.1.1 server 
other than default $BPR_HOME/rdu/mibs, to avoid overwriting default 5.1.1 MIB files. 

Run the migrateDb.sh tool on the backed up database and backed up custom MIB directory if 
present. The migrateDb.sh script resides in the $BPR_HOME/migration directory. The 
migrateDb.sh script supports a new MIB migrating option as shown below:

-mibdir 

 An optional parameter with custom MIB directory

 path. -mibdir option should be followed with a

 directory path which exists in file system and 

 contains custom MIB files to be loaded.

For example:

# $BPR_HOME/migration/migrateDb.sh -dbdir /var/backup/rdu-backup-20120829-031028 

-mibdir /tmp/mibs

-dbdir 

 Specifies the location of the database backup that 

 is to be migrated; in this case, /var/backup.

-mibdir 

 Specifies the location of the custom mibs backup that 

 is to be migrated; in this case, /tmp/mibs.

The MIB migration happens along with the database migration and it cannot be performed separately.