BCM200 to 400 migration

[NTEDave]

Hello

I'm swapping out a BCM200 to a 400 to give them extra slots to install a DSM module.

The 200 is fairly complext in it's programmming and I was wondering if there was some way to backup the 200 and migrate the data to the new 400?

Cheers

Dave

 

[jwulf1092]

NTEDave, What are the versions of software on the 200 and the new(cough here) 400?
Also I will tell you, I use a personalized version of the Nortel programing record for the BCM. You may jsut need to take the time to go through the programming line by line, to itemize everything jsut to make sure nothing is lost when migrating to the new (cough here) 400.
JW

 

[NTEDave]

Hi

Thanks for your reply, the customer knows its a second user 400, no dodgy dealings here!

Both systems tell me they are V4.0.2.03 under System / Identification

Cheers

 

[jwulf1092]

Dave,
I was making an inside joke for us to laugh at with my new comment, I was NOT questioning your reputation or morality.

I am not familiar enough with the 4.0 system as it is a different OS (Linux vs Win NT) for the systems I am familiar with, so another user will have to educate you about the options for backup and restore on a 4.0 system.

Best of luck!
JW

 

[biv343]

If both systems are on the same software, same patch levels and keycoded similar then a restore of the 200 programming may work. A voicemail restore should work fine but I don't know about the telephony programming. The only real difference between a MSC1A and MSC1B is the lack of DS30 expansion port and two MBM connectors, no functional code differences. That being said, I've never tried it. Logic says the programming should restore, but this is Nortel so logic doesn't always apply. Since you have a replacement system, no harm in trying.

 

[QueBall780]

Yeah that should restore nicely.

I have had some issues where the application DN for voicemail went to a different value so the forwarding on extensions and the Centralized voicemail we had in a networked configuration with other remote BCM's didn't work but once I noticed that it was an easy fix.


And yeah. BCM200/400 are old units running old software that is end of life so calling it "new" is the joke.

 

[NARSBARS]

Just add an expansion cabinet. Cheap, no data migration.

NARSBARS

 

[ECartman]

Personally I would sell them the R6 upgrade kit. That will convert the 200 to a 450 essentially. All programming would be migrated using DMM (well most of it, if you use the latest version of DMM)

At that stage you could just take out the main tray and slot into the 400 chassis. You will then have the extra MBM slots and they are at the latest and greatest release.

Would save alot of labour time/heartache instead of re-progamming.

Just my 2 cents.

 

[NARSBARS]

I know Avaya lists a 450-2 and a 45-4 upgrade kit. I would be concerned about what built in limitations were in one upgrade vs the other.
I do agree that going with the R6 upgrade is the best idea regardless of the path.

NARSBARS

 

[NTEDave]

Thanks for all of the replies, very cool

When I tried a backup of the 200 and a restore to the 400 it looked like it was going to work then got the following error:

"Core Telephony restore failed due to an invalid image size. Restore incomplete. System integrity is not guaranteed!"

In the end I sort of over ruled the sales person.

They had a GASM8 installed and were using four of the ports, they needed twelve ports for digital phones. So I removed the GASM8 and installed a DSM16 and four ATAs

They wouldn't have gone for the 450 upgrade as money is tight.

Reason I was reluctant to do the swap is they have forty phones across three sites using VLANS etc, heavy VM and AA users.

Would have been a nightmare.

Cheers.