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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Majix Upgrade ???
- Thread starter phonesrus
- Start date
Considering it is a .BIN file, if you have the means to burn it to a flash card then it should do the upgrade just fine.
If you have the flash card burning capability, why not go for the R4.0 V7.1 Software.
If you have the flash card burning capability, why not go for the R4.0 V7.1 Software.
- Thread starter
- #3
MM,
The reason I was asking was we had a 2.2 system that the voicemail malfunctioned and would not answer. One of our techs checked the system and discovered an alarm "dual port ram failure" on the vm slot under the demand test, he rebooted the system and it came back up, but the last vm port (6th) was flashing green and still would not answer. We did not have a 2.2 spare processor, only a 2.0 and 2.1 in stock, and of course, it would not accept a 2.2 restore from the backup flashcard.
Hence my question.
I have found previously that the download Avaya "bin" files, specifically the Legend R7V14 is not a forced upgrade, only a maintenance one within the same release ie: R7V10 to V14. I wasn't sure if a Magix 2.2 maintenance release would upgrade a 2.0 load, it is something that I will have to try, unless someone knows for sure.
I do have the capability to write the "bin" file to a flashcard, and have done so with the R7 load.
I did a download of the 2.2 and converted it to 3.0 and when I uploaded to a 3.0 processor in a duplicated system with the customers voicemail, the same issue presented, flashing on the last vm port and no response. I played with the customers system for a while after reinstalling their VM and finally decided it had to be a software corruption.
I performed a restore on the 2.2 from Autobackup2, prior to the system malfunction which occurred on 28 Nov, caused by whatever happened. The system returned to normal.
I did a laptop backup again on the BAK2 load and did a convert to 3.0 at our shop on the duplicated system and it also returned that system to service using a different vm, same version.
The reason I was asking was we had a 2.2 system that the voicemail malfunctioned and would not answer. One of our techs checked the system and discovered an alarm "dual port ram failure" on the vm slot under the demand test, he rebooted the system and it came back up, but the last vm port (6th) was flashing green and still would not answer. We did not have a 2.2 spare processor, only a 2.0 and 2.1 in stock, and of course, it would not accept a 2.2 restore from the backup flashcard.
Hence my question.
I have found previously that the download Avaya "bin" files, specifically the Legend R7V14 is not a forced upgrade, only a maintenance one within the same release ie: R7V10 to V14. I wasn't sure if a Magix 2.2 maintenance release would upgrade a 2.0 load, it is something that I will have to try, unless someone knows for sure.
I do have the capability to write the "bin" file to a flashcard, and have done so with the R7 load.
I did a download of the 2.2 and converted it to 3.0 and when I uploaded to a 3.0 processor in a duplicated system with the customers voicemail, the same issue presented, flashing on the last vm port and no response. I played with the customers system for a while after reinstalling their VM and finally decided it had to be a software corruption.
I performed a restore on the 2.2 from Autobackup2, prior to the system malfunction which occurred on 28 Nov, caused by whatever happened. The system returned to normal.
I did a laptop backup again on the BAK2 load and did a convert to 3.0 at our shop on the duplicated system and it also returned that system to service using a different vm, same version.
dagwoodsystems
Programmer
I would not replace the processor unless the logs repeated show 780D or 780E errors. Even then, you want to clear the logs and power cycle the system at least twice before concluding that the processor itself has suffered a failure.
It sounds like you got a 0016 error which is supposedly unrelated to programming. However, I've seen very weird behavior and alarms generated by corrupt translations. The testing you did clearly shows that this was the case with this Magix as well.
I have only seen this issue with system translations, and never the software image itself. You can upgrade the processor software if you want, but I really don't think that was the issue here.
Tim Alberstein
It sounds like you got a 0016 error which is supposedly unrelated to programming. However, I've seen very weird behavior and alarms generated by corrupt translations. The testing you did clearly shows that this was the case with this Magix as well.
I have only seen this issue with system translations, and never the software image itself. You can upgrade the processor software if you want, but I really don't think that was the issue here.
Tim Alberstein
- Thread starter
- #5
I have seen cases where the systems experienced "brownouts" and bounced, powering down and backup in almost the same instant and suffering from a corruption of the load. This system has a UPS, but I do not know if it is stable (good batteries), and have suggested that it be tested/replaced.
The error log (last 99) that I printed showed 7801 errors (slot 4-VM) "not in normal op mode" at ~ 1:55 am. on 11/28, 29, 30th. This was the print log I did on 12/04 when I arrived on site. There were no permanent errors recorded.
The "Boss" was the one who wanted to replace the processor, but we did not have a 2.2 in stock, hence my original question as to whether anyone had tried a 2.2 Maintenance release and whether that would upgrade a 2.0 or 2.1 processor to 2.2.
The Avaya site has maintenance releases for 2.0, 2.1, and 2.2 for download, so I am suspecting that they will only upgrade individual 2.x releases to their final load. I know that the Legend R-7 Maint. release will not take a 6.x processor to R-7 v14, that requires the "forced upgrade" first, but it will take an R-7 Vx to V-14.
I will have to load a flashcard with the 2.2 release and see if it will take a 2.x to 2.2 since they are both in the major release of 2.x
The error log (last 99) that I printed showed 7801 errors (slot 4-VM) "not in normal op mode" at ~ 1:55 am. on 11/28, 29, 30th. This was the print log I did on 12/04 when I arrived on site. There were no permanent errors recorded.
The "Boss" was the one who wanted to replace the processor, but we did not have a 2.2 in stock, hence my original question as to whether anyone had tried a 2.2 Maintenance release and whether that would upgrade a 2.0 or 2.1 processor to 2.2.
The Avaya site has maintenance releases for 2.0, 2.1, and 2.2 for download, so I am suspecting that they will only upgrade individual 2.x releases to their final load. I know that the Legend R-7 Maint. release will not take a 6.x processor to R-7 v14, that requires the "forced upgrade" first, but it will take an R-7 Vx to V-14.
I will have to load a flashcard with the 2.2 release and see if it will take a 2.x to 2.2 since they are both in the major release of 2.x
I am assuming something here, and that assumption is that you have more than 1 carrier. If I am wrong, then please correct me.
-BROWN OUTS-
A lot of the times, when power goes out, you have a problem of an improper "BOOT UP" due to a mish-mash of Power Units.
Here's the deal, some Power Units come up faster than others.
Remember, the proper way to power a system up is to power up the RIGHT MOST SLOT first, and then the NEXT LEFT and the NEXT LEFT after that. (If you have 3 carriers)
Thus, if you have a "FAST" POWER UNIT in slot 1, and a "SLOW" one in slot 2, slot two will come up AFTER slot 1, therefore you have the problem.
The problem being, slot 1 won't see slot 2, 'cause it came up "LATE".
I really can't remember which ones are SLOW or FAST, but it can easily be proven by turning off the "SOURCE", and then when it is turned back on, observing which POWER UNIT comes up first.
But, as I said, if you only have one carrier, I am all wet here.
-BROWN OUTS-
A lot of the times, when power goes out, you have a problem of an improper "BOOT UP" due to a mish-mash of Power Units.
Here's the deal, some Power Units come up faster than others.
Remember, the proper way to power a system up is to power up the RIGHT MOST SLOT first, and then the NEXT LEFT and the NEXT LEFT after that. (If you have 3 carriers)
Thus, if you have a "FAST" POWER UNIT in slot 1, and a "SLOW" one in slot 2, slot two will come up AFTER slot 1, therefore you have the problem.
The problem being, slot 1 won't see slot 2, 'cause it came up "LATE".
I really can't remember which ones are SLOW or FAST, but it can easily be proven by turning off the "SOURCE", and then when it is turned back on, observing which POWER UNIT comes up first.
But, as I said, if you only have one carrier, I am all wet here.
- Thread starter
- #7
MM,
Want a towel, Single Carrier 3 4x12's and VM, and to add insult to injury, in a lawyers office. I have no idea what really caused the issue, just a guess. I was not the first responder, one of our other techs was. I got sent out to "fix"it because one of the lawyers was having a "hissy fit".
I took a duplicated system with the 3.0 with me to test with for the processor replacement/upgrade, which when converted and loaded presented the same symptoms, and yes, I did a board renumber on each system, more than once.
When I took the now working BAK2 load back to the office, converted and loaded it to the duplicated system, it fixed the same issue that presented on the 3.0 also, so I at least have a spare, just "In Case".
Want a towel, Single Carrier 3 4x12's and VM, and to add insult to injury, in a lawyers office. I have no idea what really caused the issue, just a guess. I was not the first responder, one of our other techs was. I got sent out to "fix"it because one of the lawyers was having a "hissy fit".
I took a duplicated system with the 3.0 with me to test with for the processor replacement/upgrade, which when converted and loaded presented the same symptoms, and yes, I did a board renumber on each system, more than once.
When I took the now working BAK2 load back to the office, converted and loaded it to the duplicated system, it fixed the same issue that presented on the 3.0 also, so I at least have a spare, just "In Case".
- Thread starter
- #9
ttech,
If that were the case, then the other five ports would be answering calls, which was not the case.
Whatever happened initially caused the VM to be unresponsive. The Boss had the other tech remove the VM from the system and bring it to the shop along with the customers flashcard for testing, thinking it had failed. He installed it in the duplicated system that I have been referring to, with a defaulted Magix 2.0 load, and the VM was working normally, answering calls and no flashing 6th port.
He then tried to reload from the customers flashcard which didn't work and leads us back to my original question.
At that point the problem and subsequent resolution was dumped on me.
I have no other explanation other than something caused a corruption in the software load, and was resolved by restoring to the AutoBack2 which was 2 weeks old.
My next project will be to see if the 2.2 maintenance download will upgrade a 2.0 processor, or not!
If that were the case, then the other five ports would be answering calls, which was not the case.
Whatever happened initially caused the VM to be unresponsive. The Boss had the other tech remove the VM from the system and bring it to the shop along with the customers flashcard for testing, thinking it had failed. He installed it in the duplicated system that I have been referring to, with a defaulted Magix 2.0 load, and the VM was working normally, answering calls and no flashing 6th port.
He then tried to reload from the customers flashcard which didn't work and leads us back to my original question.
At that point the problem and subsequent resolution was dumped on me.
I have no other explanation other than something caused a corruption in the software load, and was resolved by restoring to the AutoBack2 which was 2 weeks old.
My next project will be to see if the 2.2 maintenance download will upgrade a 2.0 processor, or not!
- Thread starter
- #11
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question