1872 AnswerMessageHitResultOrErrorTable

Recommended Action

It is recommended that you do the following to resolve this alarm:

1. Search the debug log for a warning entry indicating that an answer message hit a result or dsc_error table.
2. Note the following information after the warning log entry: 
   • • DSC instance
     • DSC Node name
     • Request Incoming ADN Name
     • Answer Incoming ADN Name
     • Initial Routing Table Name
     • Outgoing Answer Routing Table
     • message content in HEX.
   Note

   The message content must be cleaned up as copied from the debug log. 

3. Using the DSC Search Utility of the DSC instance reporting the alarm and log, upload the message and fill in the required information based on the information collected from the debug log.
4. Perform a search and inspect the DSC Table Records the message goes through before hitting the result or error table.
5. Change the configuration so that the answer message is properly routed and does not hit a result or error table. 
6. If the results of the Search do not output any DSC Table Records, use the Outgoing Answer Routing Table as the Initial Routing Table Name of the DSC Search Utility and perform a search again. 

7. If you still do not get any DSC Table Records, use the Outgoing Answer Routing Table as your starting point and trace the message flow through the routing tables until you find a record that puts the answer message through a result or dsc_error table. 

   Note

   Some answer messages may be generated by the DSC (errors for example) and might not have an Answer Incoming ADN Name value. For this particular case, the Outgoing Answer Routing Table of the Request Incoming ADN Name is routing the answer message through a result or error routing table.