Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 01-12-2017, 04:18 AM
rbellamkonda rbellamkonda is offline
Hot Shot
.
 
Join Date: Jan 2014
Location: Pune, India
Posts: 20
rbellamkonda has 10 reputation points
Default Avaya AES 6.3.3: Intermittent Avaya AES Traps - avAESLicenseFailure: TSAPI:: Entering

Doc ID: SOLN256890
Version: 20.0
Status: Published
Published date: 26 Sep 2014
Updated: 03 Jan 2017
Categories: Configuration, Troubleshooting, Downloads/Patches, Break/Fix, Avaya Aura Application Enablement Services
Author: Rakshit Sinha

Details: End user has reported that the AES Alarm Viewer found on the Operation, Administration, Maintenance (OAM) pages is reporting that “TSAPI has entered a 30 Day Grace Period”

From the log.date file found in /opt/mvap/logs directory the following errors are reported; [root@logs]# vi log.20161111

00:02:02.001 ERROR:WARNING:TSAPI:TSAPI Users->countingAcquire:acquire() failed: Timeout occured contacting license server:

00:02:02.001 ERROR:WARNING:TSAPI:GenericLicense::SetMode:Licens e mode changed to LICENSE_ERROR; cause: Timeout occured contacting license server:; grace period: 2592000 secs

00:02:02.126 ERROR:FYI:TSAPI:GenericLicense::SetMode:License mode changed to LICENSE_NORMAL; cause: Initialize license as normal

If you take the “grace period” in seconds, this works out to 30 days, which is what is reported in your Alarm Viewer on the AES web pages;

2592000/60 seconds = 43200
43200/60 minutes = 720
720/24 hours = 30 Days

This occurs daily with no service impact;
[root@logs]# grep -c "Timeout occured contacting license server" log.*

log.20161011:24
log.20161012:28
log.20161013:25
log.20161014:24
log.20161015:28
log.20161016:36
log.20161017:29
log.20161018:38
log.20161019:35
log.20161020:18
log.20161021:74
log.20161022:24
log.20161023:22
log.20161024:16
log.20161025:23
log.20161026:26
log.20161027:26
log.20161028:21
log.20161029:21
log.20161030:12
log.20161031:34
log.20161101:25
log.20161102:32
log.20161103:26
log.20161104:22
log.20161105:20
log.20161106:20
log.20161107:27
log.20161108:49
log.20161109:36
log.20161110:26
log.20161111:21

As shown on the OAM pages, the license mode remains "Normal"

Problem Clarification: TSAPI has entered a 30 day grace period.

Cause: There have been several known WebLM timeout issues in the AES 6.3.3 release. A PSN was released describing the issue;

WebLM Timeouts: https://downloads.avaya.com/css/P8/documents/101017862

Solution: Please click here to view the full solution on support.avaya.com.

Alternatively, solution can be accessed from; (https://support.avaya.com/ext/index?...&id=SOLN256890).



- Additional Relevant Phrases

WebLM timeout TSAPI reserved licenses AES connection is up and down License issues
__________________
Raghu Bellamkonda | KCS Advisor, Knowledge Centered Support Team|
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:32 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.