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

Issues with Upgrade to R11.0.4 9

Status
Not open for further replies.

pyoung85

Technical User
Feb 13, 2016
25
CA
We recently upgraded an IP Office from R.9.1.7 to 11.0.4. We passed from 9.1 to 10.0 and finally 11.
Following the first upgrade to R10 I noticed the IP Office wasn't responding well. I started a continuous ping on the IP Office. I would get delayed responses of 20 ms to 5000 ms and 1/3 of the ping's would timeout.

This IP Office has approx 50 digital phones and another 50 IP phones at various locations. They would slowly come back on one after another. The PBX seemed stabilized after everyone has been connected (more or less 20 minutes).

Two days later we had to reboot the PBX to change a combo card that has been defect for the past 2 weeks. Following this reboot, the PBX would go through the same process I mentioned but would NEVER stabilize. We tried formatting and recreating the SD Card. We tried to power on the IP Office and plug in one card at a time. Once all cards and the DS expansion module all proved to be working fine, we tried plugging in one phone at a time. After all proved to be fine, we tried plugging in the PRI. Next we plugged in the WAN which contains only SIP lines. So far everything is up and running fine. We have a laptop in LAN 1 monitoring the system. We waited a bit with calls going in and out and everything is fine.

We plugged in LAN 1 to the local network, which also has the Voicemail Pro server, XIMA Chronicall + Multimedia server and +-50 IP Phones in various locations. All hell broke loose. At this point we do understand the IP Office is loaded with requests but nothing has been added recently and it never acted this way. The only new factor is the XIMA multimedia server but at this point I had all XIMA services turned off to limit the requests.

So we installed a new IP Office 500 V2 cabinet. Right away the IP Office responds with reasonable delays (1ms to 4 or 5ms) but the IP Phones took approximately 20 minutes to come back online one after another. At this point we're certain the IP Office network card was faulty and the issue is resolved.

Come in the next day and surprise we have some new issues. Voicemail isn't always answering, and if it does the sound cuts off halfway. No DTMF is supported once in the Voicemail. So we restarted the Voicemail Pro service. Issue resolved. A few hours later, the client mentions digital phones can no longer dial out. When they press on digits, nothing appears on the screen. If they press very slowly, the digits will go through.

So we now proceed to downgrade from R11.0.4 to 11.0.2. We read about different numerous issues online concerning 11.0.4. After this downgrade we come back to point A. The IP Office responds only 2/3 of the time with major delays. It takes approximately 30 minutes or so for everything to come back online. Yet after 30 minutes it all seems stable. For now...

The only errors we can see in the Sys monitor are the following :
ERR: Vil Cafeteria Terminal PGO Response !OK:(0x1)
TFTP Write:: Too many retries (from 0.0.0.0, 49597, to 4207) file=deltaconfig/svmail1/CHqoAZFPD9irGpRmDx8u6JbzCCinHJADCyeqGZK4020

Any ideas ?
 
Hi Intrigrant

Did any of the systems you have upgraded have expansion modules on?
 
We have worked on this issue for the past two months.
Everything has been changed.
The SD card has been formatted and recreated.
We monitored the network during a reboot and all we can see we're legitimate gatekeeper requests from the IP Phones.
We then turned to Avaya and opened up a service request.

Even Avaya can't explain clearly this behaviour but we did manage to resolve it with a simple solution a few days ago. I have rebooted a few times since and I can say the issue is definitely resolved : Remove all ADI nodal licences that are obsolete !

I'm guessing everyone else experiencing this issue has upgraded from an older release using ADI nodal licence to R11 using PLDS licences. These ADI nodal licences appear as obsolete so we believed they were dormant or invalid yet the system seems to still try and register using these licences.

This is Avaya's vague explanation :
If old ADI licenses are in the system, then it can cause a memory leak in resources, this manifests itself when X amount of sets attempt simultaneous registrations which can then lead to resources being exhausted and multiple other issues
 

Great! Solved that issue at two of our customers after upgraded to 10.1 - I’ll try next week at our customer where we wanted to upgrade vom 9.1.8 to 11.0.2 ...

Thanks for sharing!
 
Removing obsolete licenses should always been done as it has caused issues in the past.
Funny to see that this is still the case as it should not.

BAZINGA!

I'm not insane, my mother had me tested!
 
I got told after raising an SR that it was a corrupted database and to default and start again.

This cured the issue but (probably because it cleared the licenses) but now I have 260 extensions to setup again!

Least its fixed though!
 
With removing ADI obsolete license the issue has been resolved.
I have upgraded the IP Office from 9.1.12 to 11.0.02 and the IP Office is stable and working fine with R11.0.02
Thank You pyoung85 your advice was very helpfull for resolving this problem
 
The more you know. I've always left obsolete licenses around.

Depending on the URI configuration the ICR can be completely ignored.

If your URI is configured to use internal data then the IP Office will look into the user's SIP tab and if you have *'s it will look into ICR.

A madman with a taste for speed.
 
After upgrading IP Office form R9 to R11, and then upgrade One-X Portal to R11,
Avaya One-X mobile client would not able SIP register to IP office.
Also when I try to login same user on One-X portal, the login has been refused after shortly displaying user dashboard, and show this One-X portal message :

"You have been logged out because the phone system became unavailable"

Is there any idea how to resolve this ?
 
Did you upgrade the one-x (app server?) to 9.1 or 10 before 11?

Whilst the IPO can go directly from 9.0 to 11, the app server can't (or shouldn't)

| ACSS SME |
 
Sorry, exactly One-X Portal was on 9.1.12 and then upgraded to 11.0.02.
 
Thank you very much for this solution! One of my customers is asking for something official from Avaya (we have had two failed windows). Do you happen to have the solution ID for your ticket?

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top