SS7_Monitor | Entering tick dur=10

  • Document ID:KM00206173
  • Creation Date:15-Oct-2012
  • Modified Date:29-Jan-2014
    • Micro Focus Products:
      ocusp-m
      ocsc sep
      ocsac

Summary

This article describes what to check when messages such "SS7_Monitor | Entering tick dur=10" are seen in the nmsg and how to fix it.

Problem

When running Signaling System No:7 (SS7) Monitor nettl trace file nmsg is filled with following messages (about 10/s):

<ocadmin>:tsep1:/home/ocadmin> nmsg 0|tail -20
Sep 25 EETDST 2012 12:47:44.632142| 9665 | code/commonEnvironment/Timer.m| 302| SS7_Monitor | Entering tick dur=10
Sep 25 EETDST 2012 12:47:44.832122| 9665 | code/commonEnvironment/Timer.m| 302| SS7_Monitor | Entering tick dur=20
Sep 25 EETDST 2012 12:47:44.832136| 9665 | code/commonEnvironment/Timer.m| 302| SS7_Monitor | Entering tick dur=10
Sep 25 EETDST 2012 12:47:45.832110| 9665 | code/commonEnvironment/Timer.m| 326| SS7_Monitor | tick tid=1 displaymgr --
Sep 25 EETDST 2012 12:47:45.832123| 9665 | code/commonEnvironment/Timer.m| 302| SS7_Monitor | Entering tick dur=10
Sep 25 EETDST 2012 12:47:45.832138| 9665 | code/commonEnvironment/Timer.m| 326| SS7_Monitor | tick tid=7 nodemgr --
Sep 25 EETDST 2012 12:47:46.321140| 9665 | code/commonEnvironment/Timer.m| 302| SS7_Monitor | Entering tick dur=20
Sep 25 EETDST 2012 12:47:46.321280| 9665 | code/commonEnvironment/Timer.m| 302| SS7_Monitor | Entering tick dur=10

Solution

Checking the /etc/opt/OC/supportability/debug.conf file, the section for SS7_Monitor has the following configuration:

[SS7_Monitor]
COM_E_LL_ERROR_MASK= 0xFFFF0306

Having trace masks as above causes such messages being logged in the nmsg even though there is no problem with the SS7_Monitor.

The solution is to change the setting as below:

[SS7_Monitor]
COM_E_LL_ERROR_MASK= 0x00000000