PI76353: UCD DOES NOT DETECT MESSAGING FAILURE WHEN AGENTS ENCOUNTER CLOCK SKEW

APAR status

• Closed as Permanent restriction.

Error description

• The secure messaging layer in UCD's agent-server communication
  relies on the agent and server to share an accurate measurement
  of time.  On machines without Network Time Protocol (NTP)
  facilities, clock skew will cause the secure messaging layer in
  UCD to fail.
  
  UCD does not detect this failure, and will not bring the agent
  offline.  This can result in failed process steps at deployment
  time.
  

Local fix

• Use NTP or other time-keeping best-practices to ensure that the
  agent and server share the same notion of time.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The secure messaging layer in UCD's agent-server             *
  * communication                                                *
  * relies on the agent and server to share an accurate          *
  * measurement                                                  *
  * of time.  On machines without Network Time Protocol (NTP)    *
  * facilities, clock skew will cause the secure messaging layer *
  * in                                                           *
  * UCD to fail.                                                 *
  *                                                              *
  * UCD does not detect this failure, and will not bring the     *
  * agent                                                        *
  * offline.  This can result in failed process steps at         *
  * deployment                                                   *
  * time.                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• New Agent/Server communication will not have this issue
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels