6 |
Table 6-10. Exception Log Event Codes - Continued
Log Event
Code
Eventª1bº SRTP server event (Continued)
Possible Cause and Resolution
28ªBadremoteapplicationrequest;discardedrequestº
A PDU arrived with a
29ªBadremoteapplicationrequest;discardedrequestº
An Error Request PDU arrived from a remote SRTP endpoint. Entry 4 contains the SRTP error code. Entry 5 contains the invoke ID of the SRTP PDU causing the Error Request to be sent.
2b ªBadremoteapplicationrequest;discardedrequestº
A valid SRTP PDU arrived, but the SRTP Server does not support handling it. The value of the pdu_typefield is contained in Entry 4. Valid PDU type codes are listed above in the description of Entry 2 = 21H.
2c
Internal error: An attempt to write an SRTP Connect Response was made prematurely.
2d
Internal error: More response data arrived from the Backplane (PLC) Driver when more data was unexpected. Entry 4 contains the SRTP PDU type associated with the response data. Valid PDU type codes are listed in the description of Entry 2 = 21H.
2e
Internal error: A mismatched Backplane (PLC) Driver transfer identifier was detected in the context of reading TCP data. Entry 4 contains the transfer identifier.
2f
Internal error: Failed to allocate a new transaction machine.
30
Internal error: Failed to find a transaction machine on the send queue matching the desired Backplane (PLC) Driver task identifier and transfer identifiers. Entry 4 contains the task identifier, and Entry 5 contains the transferidentifier.
31
Internal error: An attempt was made to activate an idle PDU machine.
32
Internal error: A PDU machine was in an unexpectedstate.
33
An attempt to read more TCP data for a transaction machine failed.
34
Internal error: Failed the setup required to read the data field of an SRTP PDU.
TCP/IP Ethernet Communications User's Manual ± January 1996 |
|
