How to monitor the growth of the queue size for the SE and EP to ensure that the queue does not exceed the maximum size limit

[TCC_2]

Core Issue

When the current size of the queue exceeds the maximum size limit set for the queue, the element can no longer process traffic. When the queue exceeds the maximum size, the queue starts to drop elements either from the front or back, on the basis of the discard policy of the queue.

Resolution

Use Simple Network Management Protocol (SNMP) traps to notify the SNMP console about certain events. Enable the "sipTrapUAQueueMaxSizeExceeded" trap to send a notification when the current size of the queue exceeds the maximum size limit set for the queue.

Perform these steps to configure SNMP traps:

1. Verify whether the "sipTrapUAQueueMaxSizeExceeded" trap exists under the Command Line Interface (CLI) context SNMP. This is the command:
   
   snmp> view trap
    
2. If this trap does not exist, enable the trap:
   
   snmp> trap -o 1.1 -n sipTrapUAQueueMaxSizeExceeded
   
   Note: The log file in which the traps are generated resides in the /log directory for Service Engine (SE) and Edge Proxy (EP).
    
3. Set up rotation on the log file for every day, week or never. Configure rotation under the CLI context log-mgmt:
   
   log-mgmt> log-rotation -l -frequency never/week/day
   
   Note: Configuration of log-rotation to never implies that the log file is not rotated and that the name of the log file is not appended with a timestamp.
    
4. Issue the log snmp-alarm command to enable logging for this trap under the CLI context log-mgmt:
   
   log-mgmt> log -e snmp-alarm -l -s "%t %o %n %d"