BCM50 upgrade 1.0 to 6.0 4

[YankeeNation]

I realize you can't go directly from 1.0 to 6.0, but what are the possible ramifications we can expect to encounter? We will go from 1.0 to 3.0 then 3.0 to 6.0 i believe. Barring any major problems during upgrade, what will be lost, besides just VM messages. Is there anything else to worry about, I assume the keycodes should be fine? Any input would be greatly appreciated. Thanks in advance.

Money may not buy you happiness, but in MLB it buys you CHAMPIONSHIPS. (27 and counting). MLB,stands for Major League Baseball for you slower Boston Fans!

 

[biv343]

You shouldn't lose anything during the upgrade process. That being said, I would have a backup of the system before going to 3.0, then grab a backup after the upgrade to 3.0 and application of the 3.0 factory image patch is completed. The keycodes will be fine. Just make sure you generate your 1 to 3 keycode, upgrade to 3, then generate the 3 to 6 keycode.

 

[snd1234]

Can you not just apply an R6 image to the unit and put in the keycode with the R6 upgrade on it?

 

[biv343]

I suppose you could if you don't mind reconfiguring the entire system. I've never tried that as I haven't yet had a customer who was willing to start from scratch.

 

[atascoman]

I don't think the upgrade kit for 1.0 to 3.0 is available anymore. The keycode for it is, but not the actual software. I recently had to do this on several systems and we had to get new R6 units and then regenerate the keycodes for each set of R1 keycodes. Then of course was the rebuild which was not fun at all.

 

[snd1234]

I've got the R1 to R3 CDs and I bet supportdude does as well. I think I also have the R1 to R2 also.

I'm having my own problems going from R2 to R6. Keeps saying invalid keycode when I try to apply to upgrade patch. System is 300 miles away so guess I'll have to do an L2 reset.

If I backup, L2 reset, and just put an R6 image on the HD, can I apply the R2 backup to the R6 system?

 

[gberger]

No, it won't accept it.

 

[ECartman]

@snd1234

I know there is a patch for the invalid keycode issue when upgrading from R3 to R6

BCM050.R300.CFS-236

Not too sure if there's one for R2 though.

 

[snd1234]

Yes, I got that last night upgrading an R3 to R6. Wouldn't take the R6 update until that was applied. After which it worked fine.

My R2 system is still stuck, however. It has the latest (2009) SU and Desktop patches. Every angle I've attacked it has failed.

R2 to R3 (invalid) [w/ R3 license]
R2 to R6 (invalid) [w/ R6 license]
R2 to R5 (invalid) [w/ R6 license]
R2 to R3 (invalid) [w/ R6 license]

The software history basically has three updates. The SU, DU, and the R3 pre-upgrade patch.

I'm going to try to reimage to R2, apply my backup, and try without the SU and DU. If that doesn't work, I'm going to image a fresh R6 onto it and recreate everything from scratch. Hate to do that as it's fairly tricked out with VOIP trunking and such.

 

[Firebird Scrambler]

I think I've seen this problem when I played with a BCM 400 system that I had acquired from an unkown source.

The BCM 50 needs to be reimaged back to version 2 and the thing to do is to try and follow the method below.

Tips on rebuilding or reloading a different database on a BCM system


This might come in handy as I had discovered a number of traps if it’s done in the wrong order. I recently re imaged 8 BCM 400 disks and I needed to test out one of them to be sure they were OK. I don’t think it’s documented very well in the books and I also think it will apply to the BCM 50 / 450 model range.

Put in your replacement BCM disk and power it up. Wait until you can log in. After having to change the default account nnadmin password (Usually back to default of PxxCxxMx!!), you must load back in the original keycode for that BCM site ID that you are connected on at that release. Failure to do so at this stage will mean that you will probably have to start again from the beginning.

The second most important thing is to install the BCM system patches first, usually requiring it to be done in two parts and it’s a reboot each time!.
Also install the desktop patch afterwards. The latest System patch is now at 029 and desktop at 018 for the 400 range.

The third thing to do is to use the restore facility with a backed up database.

The mistakes I made were on my test BCM and I just carried out a restore from a different site ID. It worked fine, but I couldn’t re enter in the original keycode!. Also I found that I couldn’t patch the system as I kept getting “Shadow” or “Bin” errors. The reason is that the restore database can’t be done on a system that has no patches or out of date patches. It’s OK if the system has the same release or later patches installed.



All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[snd1234]

OK, here's the update:

On the way to the site I realized the stakes were much higher considering the unit was hosting 10 IP phones at various unmanned sites around the state so if I reimaged and rebuilt I would basically be driving over 500 miles reprogramming IP phones.

So I got on site and did a backup. Then I did an L2 reset. Then I restore with backup WITHOUT restoring the keycodes and restarted. Then I applied the keycodes and restarted. Then I skipped updating the R2 at all and loaded the R2 to R6 upgrade pack. This time it showed AVAILABLE and I applied it.

Everything went better than expected; all registered IP phones came back up and acquired new firmware.