Upgrade from SSC to CP-MGS

[twlcolorado]

I have 50 sites that are going to upgrade from Option 11C 3.0 to CS1000E 7.6 with CP-MGS cards. I have done dozens of upgrades to 7.6, but never from 3.0, although I have done upgrades from SSC to earlier versions of CP-PM (5.0, 5.5, 6.0).

Because there are so many sites, we are staging the systems from a test switch. Therefore, I need to patch and deploy locally, instead of from a centralized Security Server. I have archives from the Option 11C systems. When I go to deploy the CS+SS+EM on the new systems, I get to the point of uploading the existing SSC database. Every time I try to do that, I get an Invalid customer database directory error. I am uploading from my laptop, as that is the only option it gives me.

Anyone have any ideas?

 

[KCFLHRC]

I think part of the problem is you are going from small system TN architecture to large system tn architecture. The Option 11 C knows card and unit not loop, shelf, card, and unit. At some point it needs to convert those TN's to large system tn's. I would look in the upgrade guide and see what it says.

 

[KCFLHRC]

Just another thought here, do you have the new dongle installed on the CPMGS?

 

[twlcolorado]

I was following the docs on the upgrade. The new system automatically converts from small system to large system format. I have done this with CP-PM before, and it should work. I discovered that using a back up (BKO in LD 43) instead of an archive also works. Also, a contact at Avaya said that you can do a default database and then just copy a couple of files into the new system. That also worked. I do have the new dongle installed.

 

[KCFLHRC]

That sounds like Avaya. When their printed practices don't work they will have an undocumented back door option. Were your CPPM upgrades also CoRes? I understand it should convert the TN's, just thought that might be your snag. Good luck

 

[scotthdiv]

It's probably looking for the correct folder/directory structure. If you are uploading an Archive, the folder would need to be located in the ARCH_DB folder. As an example, the database would be on your desktop under a folder called ARCH_DB, which would have the "Site1" folder in it, which would contain the actual contents of the archive.

It's a little hokey, but I've done dozens of these without issue using an Archive.