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 dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Nortel Communications Server (CS) 1000 Release 5.5

Status
Not open for further replies.

whirls86

IS-IT--Management
Apr 18, 2006
63
US
We recently upgraded from release 25.4 to suceesion 5.5. In doing so we were told we would no longer have to have the PBX switch cores during its midnight routine. We were told in having it do this it puts the PBX's health in jeopardy. Does anyone know if there is any truth to this?
 
did you go to fugi? we went from 3.0 to 5.0 and fugi.. and in that state we do not auto switch.. fugi never was built to need that step..

as long as you stat health, and rdun once a day.. it should not cause a problem.. i run a short script that does that then does a ldis on each shelf that i run each morning..

john poole
bellsouth business
columbia,sc
 
They share resources now across the cores. You could turn it on if you wished to do so, but it is default off for a reason.

Mato' Was'aka
 
Now when the cores do a switch over there is a momentary interruption in the elan and basically you get an INI out of the switch. You don't get the error messages but you do get the interruption in call service. That is why you do not switch.

This has nothing to do with the software release this is more of a hardware issue. This started back with the PII processors came out in release 25.

Signature===========================================

 
Also if you run on Core 1 and it barfs, the system will not switch back to Core 0 automatically.

Run on Core 0 until it dies, then it switches to Core 1 with minimal interruption. You then fix Core 0 and switch back when all is well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top