Policy Server and Web Agent will log key roll over and cache update messages.

Document ID : KB000051326
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

As no messages were logged when key roll over happened, it was difficult to troubleshoot scenarios where some agents roll their keys and others do not.
With 6.0 SP6/R12 Sp2 CR 1 release, new messages will be logged in both Policy Server and Web Agent logs.

Solution:

Logging would be as follows in Policy Server and Web Agent under differerent scenarios: Policy server:
Key rollover logging:
Policy Server shall log three different kinds of messages to smps.log file, depending on the situation:

  1. A message that it has begun an administrator initiated key rollover request.
    [7024/3444][Fri Jan 22 2010 14:03:32][SmObjKeyManagement.cpp:395][INFO] Key Rollover Request has been initiated manually
  2. A message that it has begun an automatic key rollover event.
    [10072/10376][Fri Jan 22 2010 17:12:11][SmObjKeyManagement.cpp:399][INFO] Key Rollover Request has been initiated automatically by Policy Server
  3. A message that it has begun a key distribution request, which would be the result of one of the two events above.
     [10072/5588][Fri Jan 22 2010 17:12:11][SmObjStore.cpp:309][INFO] Key distribution has been initiated by Policy Server 

    Cache Update logging:
    Policy Server shall log two different kinds of messages to smps.log file, depending on the situation:

  4. A message that Cache update has been enabled.
    [7208/8596][Fri Jan 22 2010 12:58:59][SmObjStore.cpp:492][INFO] Server 'enablecacheupdates' command received.
  5. A message that Cache update has been disabled.
    [7208/8596][Fri Jan 22 2010 12:58:59][SmObjStore.cpp:664][INFO] Server 'disablecacheupdates' command received.

Web Agent
Key rollover logging:
WA shall log three different kinds of messages to smagent.log file, depending on the situation. Either one or multiple messages will be received in smagent log. The messages reintroduced and reused to keep the consistency for the existing messages

  1. A message that it got a key rollover command from a policy server.
    [1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:733][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_LAST'.[1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:756][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_CURRENT'.[1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:707][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_NEXT'.[1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:781][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_PERSISTENT'.
  2. A message that it rolled over its keys successfully
    [1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:749][INFO] ADMIN: Successfully processed key update attribute 'LAST'.[1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:774][INFO] ADMIN: Successfully processed key update attribute 'CURRENT'.[1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:724][INFO] ADMIN: Successfully processed key update attribute 'NEXT'.[1032/688][Mon Jan 25 2010 15:42:39][CSmAdminManager.cpp:799][INFO] ADMIN: Successfully processed key update attribute 'PERSISTENT'.
  3. A message that it key rollover was unsuccessful.
    ADMIN: Unable to process key update attribute 'LAST'ADMIN: Unable to process key update attribute 'CURRENT'ADMIN: Unable to process key update attribute 'NEXT'ADMIN: Unable to process key update attribute 'PERSISTENT' 

Please note that these new log messages will appear only in smps.log and webagent log files and not in trace files.