No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Plenty of Alarms Occur Because of the Change of the slot-warning-threshold

Publication Date:  2012-07-27 Views:  73 Downloads:  0
Issue Description

In an office, an ME60 is cut over and is used. The logs of the ME60, however, frequently indicate the message “AAA/4/SLOTUSER_TOTHRESHOLD:OID Reach the slot max user number (Slot=1,SlotMaxUserThreshold=1)”. This affects the customer’s query of the running logs of the ME60.  

Alarm Information
AAA/4/SLOTUSER_TOTHRESHOLD:OID Reach the slot max user number (Slot=1,SlotMaxUserThreshold=1) 
Handling Process
1. Run a command to check the number of users in slot 1. There are only 2000 users in slot 1, which fall within the system specifications.
2. Check the threshold-value. The customer has changed the threshold-value to 1. The alarm threshold for the number of users on a board can be set with the slot-warning-threshold threshold-value command. In this case, the slot-warning-threshold is set to 1. Each board of the ME60, however, supports a maximum of 16,000 users. Therefore, the alarm is reported when the number of users exceeds 160.
3. Change the threshold-value to 90. The alarm disappears. 
Root Cause
1. The number of users exceeds the maximum number of users allowed by the system.
2. The system alarm threshold is changed to a smaller value. 
By default, the threshold-value is 100 in the slot-warning-threshold threshold-value command. In general, you should not change the default threshold-value.