VCX Data locks up the CPU

[Ed Holt]

Ok Folks here is the toughest problem I have ever seen.

About every 24 to 48 hours my primary region server on version 7.1.14c stops passing calls. When I check it the CPU is spiked and I have to restart VCX data to get the system to start passing calls again. This is a very large setup I have 25 branches. When the lockup occurs I lose calls branch to region, region to branch, and branch to branch because those calls all depend on region primary to route the calls. Support has looked at oracle my database my config's and can not give me an answer. I just want to know is there anyone out there with the same problem or one very close to it. It has been escilated to development but no good idea from them as of yet.

This message was edited by vcxguru68 on 2-2-09 @ 1:00 PM

[Luckycharms]

7.1.12c is an old version. 3Com is up to something like 7.1.21c now. Not knowing more details I can't say for sure if your problem is identical or not to one i had a few year ago. In my case Call P was not the problem just the victim of something else. Its so long ago i cant remember the specifics.

What i can tell you is that my problem and another one i had went away once I upgraded to 7.1.16c at the time.



I would suggest upgrading to the latest 7.1.21c from your 7.1.12c. But make sure you have problem call opened with 3Com Technical Support in case there is a core dump or soemthing they can look at for you.

[Ed Holt]

Thanks Lucky,

Yess Callp is the victim VCX data is the offender because a restart of the VCX data service frees the system up. As for tech support I have given them about 10 core files I have had their team even go through oracle. As for upgrading OMG what a nightmare that is. I have 25 branches and when we went from 7.0 to 7.1 (14c was only a week old at that point) it took a full weekend starting on Friday at 5pm until Monday at 6 am almost straight through to upgrade everything.

This message was edited by vcxguru68 on 2-2-09 @ 1:00 PM

[Luckycharms]

Going from 7.0 to 7.1.anything is a huge change. All i can say is that going between 7.1.x versions is a lot smoother. Not to say strange and unnatural things wont happen. So you will still need to set aside a weekend regardless with the number of locations you have.



Its well worth the cost and a safer bet to pay 3Com to do it with/for you. Specially with the number of locations you have or if you don't feel comfortable doing it yourself. With the size of you environment. The last thing you need is for there to be a hiccup and then calling in for support under contract.



If you are doing it yourself. An ounce or preparation prevents gallons of perspiration. Don't skimp on the prep work. Make sure its all done and understood up-front i.e.

Have good backup, understand the order in which locations are being upgraded, verify replication is totally in sync with no errors on every VCX, NTP is working, did i mention good backups, stop the tomcat service on all VCX the night before to prevent users/admin from making changes, lastly make a backup (in case i didn't mention it 20 times already).

[Ed Holt]

Thanks for the advice. Fortunatly I have done this before and I know all 3 persons who have admin access one of which is my self. as for replication that has to be dropped before upgrade time anyway. As for paying 3com fortunately we have a 24x7 contract and GSO is already well aware of the issues going on and I am intimatly familiar with the upgrade process this system is my baby I built her from pretty much the ground up going on 3 years ago. Hell I have had to reload V6000's in this setup from scratch after the customer cooked one.

3Com Certified IP Telephony VCX/NBX Expert

[Booda88]

Going from 7.1.14c to 7.1.21c you do not have to drop replication prior to the upgrade.

Craig Cuillard

Senior Field System Engineer

North America Services, GSO

3Com Corporation



In Thoroughness is Satisfaction