Skip to end of metadata
Go to start of metadata

Debug Event Log Overview


SBC records the maximum number of Debug Event logs, which can potentially cause memory to become congested resulting in unexpected or undesirable SBC performance.

If using INFO filter level is needed for troubleshooting, the SBC triggers the alarm sonusCpEventLogFileDebugLevelInfoNotification any time the Debug Event Log filter level is set to INFO as a reminder of potential memory congestion due to the accumulation of a large number of Debug Event logs in memory. The alarm includes a warning message to set the filter level to MAJOR. The alarm is enabled or disabled using both CLI and EMA

When the filter level is set to INFO, the following events occur:

  • The SBC generates the alarm sonusCpEventLogFileDebugLevelInfoNotification every five minutes.
  • The SBC generates a warning message Debug Event Log filter level is set to INFO. Set to MAJOR if finished troubleshooting on the last modified Debug Event Log file.

Once the troubleshooting is completed, set the filter level to MAJOR. The alarms are cleared when the filter level is set to MAJOR.

When the filter level is changed, the clear alarm sonusCpEventLogFileDebugLevelInfoClearNotification is triggered and a message Debug Event Log filter level is no longer set to INFO is displayed in the log file.

Troubleshooting the SBC using Debug Event Logs

To troubleshoot the SBC and to avoid running out of hard drive space:

  1. Check if the sonusCpEventLogFileDebugLevelInfoNotification alarm is enabled. By default, this alarm is enabled.

    show table oam traps admin sonusCpEventLogFileDebugLevelInfoNotification state
    
    state enabled;

    If it is disabled, enable the sonusCpEventLogFileDebugLevelInfoNotification alarm by executing the following command:

    % set oam traps admin sonusCpEventLogFileDebugLevelInfoNotification state enabled
    
    % commit
  2. Set the filter level of the .DBG files to INFO.

    % set oam eventLog typeAdmin debug filterLevel info
    
    % commit
  3. To inspect the debug log files, navigate to the /var/log/sonus/evlog directory. Check for the files with the .DBG extension.

  4. Check whether the alarm is triggered (optional):

    1. Open the .DBG file with the latest timestamp. List of MAJOR events followed by the list of INFO events are seen. The last Major event has the following description:
      Debug Event Log filter level is set to INFO. Set to MAJOR if finished troubleshooting.
      A sample of a .DBG file is shown below:

      098 10232017 073429.339677:1.01.00.00336.MAJOR   .CHM: *ChmSetNorthboundIface: confd reload start
      099 10232017 073429.732518:1.01.00.00337.MAJOR   .CHM: *ChmSetNorthboundIface: confd reload finish
      104 10232017 073709.116682:1.01.00.00338.MAJOR   .NRM: *Call Admission Updated: NTP Server is Available
      136 10232017 073713.059768:1.01.00.00339.MAJOR   .PRSNP: *PrsNpCoreStatusProc: NP NTP time initialized secsH 3717747433 secsL 256045703
      132 10232017 144508.294726:1.01.00.00340.MAJOR   .NRS: LIFGROUP: Successfully added lifGroupId 3 and name IPIG1 to the lifGroupList
      143 10252017 050651.346691:1.01.00.00341.MAJOR    .EVLOG: Debug Event Log filter level is set to Info. Set to MAJOR if finished troubleshooting.
      111 10252017 050651.377036:1.01.00.00342.Info    .SM: *SystemManager_i::icmMsgHdlr(): Received message: 0x3c25
      112 10252017 050651.377136:1.01.00.00343.Info    .SM: *In SystemManager_i::procConfdGetNextReqMsg(), 1167850545
      121 10252017 050651.377188:1.01.00.00344.Info    .SM: *In HwModuleComputeElement::fillServerStatus()ActualNaem WFDSBC01b
      091 10252017 050651.377303:1.01.00.00345.Info    .SM: *In System_i::fillPeerServerStatus()
      099 10252017 050651.377351:1.01.00.00346.Info    .SM: *In System_i::fillPeerServerStatus() Unknown
      105 10252017 050651.378502:1.01.00.00347.Info    .CPX: *CpxGetNextReqFromCache: Entry not found in cache
      136 10252017 050656.271754:1.01.00.00348.Info    .SCPA: .SCPA: (10492|139950200698624) Putting idle timer message on timer task's queue
    2. To view the details of the alarm, execute the following command as SBC administrator:

      show table alarms currentStatus
      
      ALARM  CLEAR
      ID     TYPE       TIMESTAMP                  INITIAL TIMESTAMP          COUNT  DESC
      -----------------------------------------------------------------------------------------------------------------------------------------------------------
      32026  AUTOMATIC  2017-10-23T11:34:05-00:00  2017-10-23T11:34:05-00:00  1      Packet port pkt2 on CE WFDSBC01b slot 0 with ifIndex 11 is DOWN
      32027  AUTOMATIC  2017-10-23T11:34:05-00:00  2017-10-23T11:34:05-00:00  1      Packet port pkt3 on CE WFDSBC01b slot 0 with ifIndex 12 is DOWN
      32131  MANUAL     2017-10-25T10:26:03-00:00  2017-10-24T10:26:04-00:00  3      SystemSecurity Intrusion Detection: AIDE cronjob detected file modifications
      32227  AUTOMATIC  2017-10-25T10:28:55-00:00  2017-10-25T09:06:51-00:00  18     Debug Event Log filter level is set to INFO. Set to MAJOR if finished troubleshooting

      Set the debug level to MAJOR by executing the following command:

      % set oam eventLog typeAdmin debug filterLevel major
      
      % commit

      Once the filter level is changed to MAJOR, the following message is displayed in log file:
      Debug Event Log filter level is no longer set to INFO