MAS Error

[phonetechgal]

We are getting a error in the maintenance log that shows VS PERF 1. I looked it up in the manual and it shows the error is unrepairable. Callers get a recording when trying to login to their mailboxes saying "please wait we are having a problem" This is intermittent. Only happened this morning. My other questions is how do we monitor system traffice on the MAS-MSS?

Description of error in manual:
This alarm indicates that too many callers are experiencing delays while interacting with the system. An internal monitor checks the system every 15 minutes, and if three of these checks within an hour indicate that more than 1% of calls have experienced delays, the system generates this warning.

Repair Procedure:
There is no repair procedure for this warning. This alarm could be generated simply as a result of heavier than normal system traffic. Once the system indicates that fewer than 1% of calls are experiencing delays again, then the problem is considered resolved and the system automatically generates a resolved-alarm event

 

[84Mike]

There should be a "Port Monitor" application on the MAS. This will show all the ports that connect to phone system, the state they are in, and how long they have been in that state. (Idle/Recording/Playing/etc)

 

[phonetechgal]

So monitor with the port monitor application? I also noticed as the documentation stated that the alrm should clear on its own. Do I understand correctly that a certain percentage of the ports will need to be in use before the alarm will display in the log?

 

[phonetechgal]

Also, what type of delays are the caller experiencing that the documentation refers to?

 

[84Mike]

I'm not sure, as I have never seen that error on my system.

 

[KenMeans]

You can run reports on the system from the VMSC under reports for the port traffic. What type of PBX and integration do you have?
And are you sure that theprivate network is at the top of the LAN list? The error means that the mas is trying to pull the MB info from the MSS and is having trouble doing so. It may be that the traffic on the private LAN is at a point where it is overloaded.

Also do you ever see a heart beat error. and is it rel 2 or 3


Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[phonetechgal]

How can you tell what NIC is at the top of the network list? Reports look ok with no all ports busy. Integration is SMDI, and version is 2.0 with all updates. No heartbeat errors in the event logs.

 

[KenMeans]

In network connections go to the advanced tab and make sure the priv network NIC is at the top of the list so it will use that link first

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[phonetechgal]

Private LAN is selected first in order. Anything else to check?

 

[KenMeans]

not that i know of.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[phonetechgal]

Ok thanks for your assistance. By the way, where are you located?

 

[ChuckRCT]

I'd check to see if PCN #581U applies to your system on the Avaya support site with regards to the "please wait" (assuming you are on Release 2). You may also want to see what MM Service Pack you are running to see if you are current (I think MM service pack 5 came out recently).

 

[phonetechgal]

Tracing is not active. This issue is the first time that this has ever happened. The system has been installed for quite a while. Unit is at Service Pack 3

 

[KenMeans]

I live in Dallas but we cover world wide

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)