This event is generated when the DSA fails to update a shadow naming
 context. This event can be generated by both the supplier and the
 consumer of the naming context. The event provides the following
 information:

 -    The reason for the failure, which is one of the following:

      -  Supplier DSA Unavailable
      -  Cannot Save Updates
      -  Update Incompatible
      -  Failed to Apply Updates
      -  Invalid Arguments
      -  Cannot Read Supplier Address
      -  Invalid Protocol
      -  Unexpected Failure
      -  Consumer Not Authenticated
      -  Communications Failure
      -  DISP error received
      -  DISP error sent
      -  Schema incompatible
      -  DIT incompatible

 -    The name of each naming context that failed to be updated.

 -    Whether the DSA generating the event was the supplier
      DSA or the consumer DSA.

 -    The access point of the DSA with which the update was processed.

 -    If the reason was DISP error received or DISP error sent, then
      the agreement identifier is displayed, and one of the following
      problems:

       -  Invalid Agreement ID
       -  Inactive Agreement
       -  Invalid Information Received
       -  Unsupported Strategy
       -  Missed Previous
       -  Full Update Required
       -  Unwilling To Perform
       -  Unsuitable Timing
       -  Update Already Received
       -  Invalid Sequencing

 Most of the DISP problems are self correcting. In some cases, a
 DISP problem causes a total (or full) update to occur. This makes
 sure that the consumer DSA has a complete, up-to-date copy of the
 relevant naming context.

 Some of the DISP problems can only be generated if an HP DSA
 is interworking with another vendor's DSA.

 If any of these problems happen frequently, refer to HP Enterprise
 Directory  - Problem Solving.