Restore fails after upgrade to 6.1 1

[jcurtiss]

We upgraded from MICS 5.0 to XC 6.1. we did a full backup prior. when we try to restore afterwards, we get an incompatibility error and the restore fails. is there a way around this? alter the fnvram.new file or something?

 

[GrumSFC]

When you back up with NRU it corresponds the file saved with the the System ID number. Unfortunately the Sys ID changes when you upgrade software release sometimes, which would mean it doesnt know what file to restore with because it doesn't recognise the switch.
Thats my theory, i may be wrong but it sounds likely.

Graham
graham.b@ashtelecom.co.uk
Ash Telecommunications Ltd
Tel:+447832 11 33 64

 

[jcurtiss]

my vendor's tech support tells me this cannot be done; that i had to use nortel's MICS Upgrade Tool. I think you might be right about the system ID. i was hoping there was someway to trick the backup file with the new system ID.

 

[GrumSFC]

I have heard of this happening before and the guy said he had to downgrade the software back to its original state which gave it back its Sys ID. He then restored the programming and printed off work sheets in excel (naics2) when he upgraded he could manually copy the info back in.

There is another quite obvious answer which would be that you backed up with NRU9 when you should use NRU10 with Rel 6.1?

Graham
graham.b@ashtelecom.co.uk
Ash Telecommunications Ltd
Tel:+447832 11 33 64

 

[jcurtiss]

i backed up with nru 10. there is an "upgrade tool" pc card that i was supposed to use but wasn't informed of. oh well.

 

[bkrike]

You cannot put a backed up 5.0 into 6.1 because many things change between releases, including line numbering, etc..

 

[Sphoneman]

I'm confused. Why didn't your Vendor use the Tool?

Steve
tele-dataservices.com

 

[jdavid99]

just put the 5.0 pcmcia card back in and restore your backup. then use the upgrade tool. you should get the patched version of 6.1 because the original 6.1 is full of bugs. especially with T1. after upgradeing your lines will auto answer with DISA. you have to disable the T1 card and build each channel as E&M and access each lines programming option for answer with DISA yes or no. even though it says no you still have to click no anyway. then rebuild your DTI as PRI and it will start working. that is just 1 of the problems with 6.1. Also if you have any M7310 with BLF attached, you must make sure the 7310 is firmware rel.16 or higher or the BLF will just flash.

 

[rhowlett]

Also make sure the Upgrade tool is for XC software and not just NA. You are going from 5.0 NA to 6.1 XC which is a tough jump to make. The upgrade tool should work, but I would get a paper copy on the programming record paperwork just in case.

Target line numbers changed from 5.0 to 6.1 to watch out for that. It started at 145 on 5.0 I forget what the first line is on 6.1.

 

[DueE]

Is there a "new" upgrade tool for releases above MICS 5.0?
Have used one for getting to 4.0 but haven't heard about a newer version, when is it supposed to be used?
Thanks

DueE

 

[jcurtiss]

thanks, but we already rebuilt the system from scratch. only took a few hours. when i said vendor, i meant distributor. we are the "vendor," that is, reseller and installer, for the end customer. either whoever bought the software from our distributor failed to mention that we were using it for an upgrade, or, if they DID mention it, our distributor failed to mention the host of issues we would have attempting to upgrade. But that's neither here nor there at this point. system's back up and running on 6.1 XC now.

i'm told we have another one of these upcoming, though. next time we'll know about the upgrade tool.

 

[telemarv]

Upgrade tool is designed to upgrade MICS 3.0 and lower to 4.0 and higher. Its purpose is to load the current database from VRAM cartidges that do not have a pcmcia card slot onto one that has the slot. Prior to 4.0 the software came loaded in the VRAM cartridge. Theoretically, all that is required to upgrade systems with 4.0 and higher is change the pcmcia software card in the VRAM carteidge.

jcurtiss went from 5.0 to 6.1 no upgrade tool was required. He could have just plugged in the new software without losing the old database. Changes in line numbering would require a little reprogramming though.

Backed data from 5.0 is not compatible with 6.x software

 

[alexburke]

Telemarv, the USA-MICS-XC Upgrade Tool *IS* required to move from non-XC to XC software without causing a coldstart.

 

[DueE]

alexburke, I would agree if the upgrade was pre4.0 going to XC6.1, use the XC4.0 upgrade tool, but the first post said MICS 5.0 TO XC 6.1. Using "the tool" would be a downgrade and resulting zip-defaulted database.

DueE

 

[DonRight]

One does not need an upgrade tool whence going from MICS 5.0 to Mics 6.1. Any data backups done at the MICS 5.0 level become academic after such an upgrade has taken place. One must then perform a new data backup using NRU 9.1. A cautionary point here - ensure that the associated map files have been introduced to your NRU 9.1 in order for your backed-up data to be viable.

Further, be advised that PRI Enabler key codes DO NOT get backed-up. Should one have a system loaded with the enabler backed-up, it is of paramount importance that the key code be recorded amongst the customer's files for future reference should an undue KSU catastrophy be realized. The marketing info on restores via NRU is incorrect. My advice here stems from actual experience and from my taking ITAS to task where this matter is concerned. Failing to have the original keycode in such an episode, one will need to produce the original PO for the Enabler as purchased from the dealer. From this ITAS will capitulate another Enabler.

The lesson here is that Norstar Remote Utilities will not offer the type of damage control as typically expected. One must be prepared!

 

[DueE]

Yeah Dude!! Command the English language! YOU GOTTA STAR FOR IT!!!! ITAS needs to capitulate more often on alot more issues! DANG!!

DueE