SV9100 Software Upgrade 1

[DoubleDizzle]

I have a NEC SV9100 system out there that is running on software version 1.08.08. (I know, that's crazy old).

I've been tasked with upgrading the system to at least 12.00.5 or higher.

I've never upgraded one that old and not sure if it can handle a big version hop or if it should be done in incremental steps.

Has anyone out there attempted a huge version jump like this before?

Thank you for your input.

DoubleDizzle

 

[DoubleDriveLine]

The release notes don't indicate there would be a problem.

Use the normal precautions (backup etc).

Hope you don't brick it but you are probably not anymore likely to do that in a large jump like this than you would a small one.



There are 10 kinds of people in the World.

Those that understand Binary and those that don't.

 

[DoubleDizzle]

Thank you DoubleDriveLine.

I'm a little apprehensive because this system has 111 MLTs, 28 SLTs,a boat load of VEs and special programming.

If I brick it, there will be hours of "hand-packing" the programming back in.

 

[meyer1y2k]

Back the system up via PC Pro, just in case. You can then save the database file.

 

[CoralTech]

Why the upgrade? Is there an issue?

 

[DoubleDizzle]

Thank you meyer1y2k.

Hello CoralTech,

The phone system has been spontaneously rebooting intermittently for several months and the customer just now got around to reporting it.

Of course, NTAC won't talk to you / troubleshoot unless you are on the latest version.

 

[CoralTech]

Pull up your error logs. If it's plugged into an old UPS I would look at that.

 

[DoubleDizzle]

Hello CoralTech,

I have pulled the logs and can see the system reboots sporatically.

Sometimes everyday, sometimes twice a day, with periods were it goes weeks without rebooting.

I agree with your suggestion on checking the UPS. I saw a SL1100 do this and swapping out the UPS corrected the problem.

The customer purchased software assurance so I am commited to the upgrade. But I will be looking closely at the UPS for issues.

Thank you for your suggestions!

 

[OzzieGeorge]

Ok so first things first, you need to consider all the possibilities, I believe that between upgrades, there are changes to how SIP trunks are handled (I had a similar issue and was advised of this by TAC Aus) so you may need to make changes as you go when upgrading, check the release notes betwen where you are comimg from and where you are going to! But if you don't have sip trunks this may not be necessary. The issue here is you take your chances if you just go for it but there may be a lot of research needed to move forward!

 

[belevedere]

There were so many changes made that I'd suggest a rekey. Use excel to copy and paste to a new dbase. You can completely rekey then upload after verifying by comparison and upgrading the software. You will need the latest version of PCPro. And, it has shortcuts to help you along. EX: SIP trunks has a short cut so you can get to the newer MB's that pertain to only SIP trunks.

 

[CoralTech]

Biggest upgrade I have done was from a version 1.08 to 10. But I had to and it took a LONG time.

 

[DoubleDizzle]

Hello Belevedere,

Thank you for your suggestion, that certainly makes sense to rekey and upload to avoid "bricking" the system.

 

[DoubleDizzle]

Hey CoralTech,

What you've stated is congruant with other technicians I have spoken with. When doing a big hop like that, it takes long time. Sounds like you're crossing your fingers for awhile until you know you didn't tank the system.

 

[DoubleDizzle]

Here's what I learned from another trusted source:

There are 3 ways this usually shakes out:

1. The upgrade takes a long time, but completes without incident. (The least likely scenario)

2. The v12.0.5 upgrade needs to be applied multiple times before the "bugs" clear out. (This is a known issue by NTAC engineers from their lab)

3. Upgrade the system in no more than 3 version hops until you reach v12.0.5 (This is procedure which sounds like it produces the best results with the least amount of time or issues)

We'll see.....

 

[DoubleDizzle]

Follow up.....

The upgrade was successful with no issues.

Upgrading the SV9100 system 3 version hops at a time from v1.08 to v12.00.5 took approximately 2hrs.

This included testing and making a back up of the configuration after each hop.