I have a Merlin Legend 6.1 that I want to upgrade to 7.0. I have access to and downloaded the EFlash software that allows me to flash the backup/restore card but I get lost after this. I have read another article relating to this subject but I'm confused. The other articles said to backup to either the restore card or a PC and in this case I would backup to a PC. Then I run WINSPM Version 7.0 to do a convert on the 6.1 backup to a 7.0 backup. Then I perform a restore from the PC using the converted 6.1 to 7.0 backup file. Where does the EFlash software that flashes the Backup/Restore (Translation) card come into play if I'm using WINSPM to convert my backup files? Please help - Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
LEGEND 6.1 to 7.0 UPGRADE HELP PLEASE!!! 2
- Thread starter BURLYMAN
- Start date
gregarican
IS-IT--Management
A couple of months ago I upgraded from Legend r6.1 to r7.0 and it wasn't too bad. I've never used the EFlash software, instead I had a PCMCIA card with the r7.0 software on it. I just followed those documented steps of backing up, converting, upgrading, and restoring like you mentioned.
To me it sounds like your getting system programming translations and software upgrades mixed up a little. I am assuming that the EFlash allows you to write the r7.0 software upgrade to an available backup translation PCMCIA card. Then that's what you'd use to perform a forced upgrade.
So it'd be like this:
1) You'd backup existing translations to hard disk using WinSPM.
2) You'd convert the system programming contained in those existing translations on hard disk using WinSPM (has to be Release 7 of WinSPM).
3) You'd place the EFlash'ed backup translation PCMCIA card into the system and power on the system from scratch.
4) The system should perform a forced upgrade and after that you can restore the previous translations converted to r7.0 using WinSPM from hard disk.
Anyone else have any insights? Since I never used EFlash I'm assuming it writes out to an available PCMCIA card and makes it a forced upgrade upon a powering up.
To me it sounds like your getting system programming translations and software upgrades mixed up a little. I am assuming that the EFlash allows you to write the r7.0 software upgrade to an available backup translation PCMCIA card. Then that's what you'd use to perform a forced upgrade.
So it'd be like this:
1) You'd backup existing translations to hard disk using WinSPM.
2) You'd convert the system programming contained in those existing translations on hard disk using WinSPM (has to be Release 7 of WinSPM).
3) You'd place the EFlash'ed backup translation PCMCIA card into the system and power on the system from scratch.
4) The system should perform a forced upgrade and after that you can restore the previous translations converted to r7.0 using WinSPM from hard disk.
Anyone else have any insights? Since I never used EFlash I'm assuming it writes out to an available PCMCIA card and makes it a forced upgrade upon a powering up.
- Thread starter
- #3
I guess I still don't understand. I have a Backup/Restore card (aka Translation card?). How do I get the Merlin Legend flashed to version 7.0? I understand how to covert my PC backups to version 7.0 but how does the system firmware get upgraded to 7.0? I get very confused with the terms flash card, backup/restore card, translation card, etc... Are they all the same? How do I force the upgrade to version 7.0 then load my converted 6.1 to 7.0 backup?
THanks for all the help
THanks for all the help
gregarican
IS-IT--Management
I would think there's an EFlashTool (or something like that I recall reading about) that will allow you to write the Legend r7.0 upgrade to your available backup/restore card. That backup/restore/translation/flash card (it's basically the same difference) won't be actively used for backing up or restoring for this 6.1 to 7.0 upgrade. It will be written to and will contain the r7.0 software. The actual system programming is backed up using WinSPM to a local computer and that's where the backup/convert/restore operations will emanate from. Card=r7.0 software. PC=customer programming.
I couldn't even log into the Avaya area where you can get EFlash, so I ordered a PCMCIA card with the r7.0 already on it. So the part where you use the EFlashTool to write out to a spare PCMCIA card is something that I haven't done.
Here's the steps the way I'm seeing it:
1) Use the EFlash system to flash your PCMCIA card with the r7.0 software.
2) Backup system programming translations using WinSPM. Do not backup to Flash. Backup to File.
3) Convert system programming translations using WinSPM. The File will then be converted from r6.1 to r7.0. and be sitting on your computer.
4) Power down the phone system with the PCMCIA card inserted into the processor board. Once you power the system backup the system will automatically start the upgrade process.
5) Restore system programming translations using WinSPM. The File that was converted in Step 3 will be restored to the newly upgraded phone system.
Like I said, step 4 is something that I am assuming. If EFlash writes out to the PCMCIA card and forces the upgrade you won't have to do anything more than power cycle the phone system.
Don't you have any documentation on the EFlash/EFlashTool utility? Since I don't I'm assuming some things here for sure.
I couldn't even log into the Avaya area where you can get EFlash, so I ordered a PCMCIA card with the r7.0 already on it. So the part where you use the EFlashTool to write out to a spare PCMCIA card is something that I haven't done.
Here's the steps the way I'm seeing it:
1) Use the EFlash system to flash your PCMCIA card with the r7.0 software.
2) Backup system programming translations using WinSPM. Do not backup to Flash. Backup to File.
3) Convert system programming translations using WinSPM. The File will then be converted from r6.1 to r7.0. and be sitting on your computer.
4) Power down the phone system with the PCMCIA card inserted into the processor board. Once you power the system backup the system will automatically start the upgrade process.
5) Restore system programming translations using WinSPM. The File that was converted in Step 3 will be restored to the newly upgraded phone system.
Like I said, step 4 is something that I am assuming. If EFlash writes out to the PCMCIA card and forces the upgrade you won't have to do anything more than power cycle the phone system.
Don't you have any documentation on the EFlash/EFlashTool utility? Since I don't I'm assuming some things here for sure.
-
2
- #5
Here is a related question. I have a orange forced upgrade card for Magix 2.2
It says it can support either a board with CKE4 or CKE5.
I tried to upgrade a CKE4 version 7.0 and it states incompatible. Do I have to have Magix 1.1 loaded first?
If so, anybody have a copy?
It says it can support either a board with CKE4 or CKE5.
I tried to upgrade a CKE4 version 7.0 and it states incompatible. Do I have to have Magix 1.1 loaded first?
If so, anybody have a copy?
gregarican
IS-IT--Management
Do you meet the hardware requirements? For example, you can't have any of the old ATL or CO Loop Start cards in the Merlin if you are looking to upgrade to Magix. You also cannot have the 391A3 or 391C1 Power Supplies.
From what I have read you can upgrade directly from Legend to Magix, be it to Magix r1.x or r2.x. As long as the Legend is CKE4 or CKE5 and you have no unsupported boards you should be fine. This is taken directly from the docs I got with a Magix 2.0 system.
From what I have read you can upgrade directly from Legend to Magix, be it to Magix r1.x or r2.x. As long as the Legend is CKE4 or CKE5 and you have no unsupported boards you should be fine. This is taken directly from the docs I got with a Magix 2.0 system.
Scottel
These are avaya's instructions for upgrading any R7x to an R7V1.2 but the part about imcompatible releases works for any upgrade. I only mention that it is for R7x to R714.2 because the instructions don't mention backing up to your computer or converting the saved translation to R7 or restoring from the converted file
PCMCIA Upgrade Instructions for
MERLIN LEGEND R7.0 V14.2 and MERLIN MAGIX R2.0 V10.2
1. Make sure a Current Backup of the customer's translations is available.
2. Insert the PCMCIA Upgrade Card (11ML70-E5 or 11MX20-B1) into the PCMCIA slot
Go through menus: Maintenance (F6) -> System (F1) -> Upgrade (F6)
Screen will show "Validation of Memory Card in Progress" then "Validation of Memory Card Successfully Completed "then choose "exit" (F5)
The next screen will appear with each release name
If screen displays "incompatible releases" continue with step 3
If screen displays compatible releases choose "exit" (F5) and proceed with step 4
3. Press "F10" twice
4. Answer "yes" to the next screen and the system will continue with the upgrade.
5 After the system goes through a 'cold start' restore translations and set the system's date and time.
6. Execute some test calls to insure all modes of calls can be made.
7. Backup customer's translations to PCMCIA Card, floppy (PC) or hard drive (PC)
Don
These are avaya's instructions for upgrading any R7x to an R7V1.2 but the part about imcompatible releases works for any upgrade. I only mention that it is for R7x to R714.2 because the instructions don't mention backing up to your computer or converting the saved translation to R7 or restoring from the converted file
PCMCIA Upgrade Instructions for
MERLIN LEGEND R7.0 V14.2 and MERLIN MAGIX R2.0 V10.2
1. Make sure a Current Backup of the customer's translations is available.
2. Insert the PCMCIA Upgrade Card (11ML70-E5 or 11MX20-B1) into the PCMCIA slot
Go through menus: Maintenance (F6) -> System (F1) -> Upgrade (F6)
Screen will show "Validation of Memory Card in Progress" then "Validation of Memory Card Successfully Completed "then choose "exit" (F5)
The next screen will appear with each release name
If screen displays "incompatible releases" continue with step 3
If screen displays compatible releases choose "exit" (F5) and proceed with step 4
3. Press "F10" twice
4. Answer "yes" to the next screen and the system will continue with the upgrade.
5 After the system goes through a 'cold start' restore translations and set the system's date and time.
6. Execute some test calls to insure all modes of calls can be made.
7. Backup customer's translations to PCMCIA Card, floppy (PC) or hard drive (PC)
Don
- Status
Similar threads
- Locked
- Question
- Locked
- Question