ACC Error Guide

ZCOM Driver Log Messages
ZCOM Driver Messages
Chapter 5 109
zcom 00225: Card <#> Port <#> RXDT15 bad reply (status = <#>),
data dropped!
Explanation: This message can occur when the DAM issues a
request to read inbound data and the Mux firmware
cannot find any inbound data to send or if the length of
the inbound data requested by the DAM is different
then the length maintained by the Mux firmware.
Action: Contact your HP Support Representative.
zcom 00226: Card <#> Port <#> Error on $RXDT15 read
(length mismatch).
Explanation: Processing of inbound data and status is a two step
process. First the DAM receives an unsolicited
interrupt packet indicating the type of inbound data
and its length. The DAM then issues a transaction to
the Mux card to read the inbound data or status
packet. Within this packet is the length of the data. If
this length does not match the length indicated in the
unsolicited interrupt packet, then the DAM logs this
message.
Action: If abnormal behavior is observed or the problem
persists, contact your HP Support Representative.
zcom 00228: Write completion length mis-match on ZLU <#>. FIRQ
length was <#> bytes but message length was <#> bytes.
Explanation: After an outbound write request is completed by the
Mux firmware, it passes a write completion
acknowledgment unsolicited status to the DAM.
Within this status is the length of the original write
request. This message is logged when the length in the
unsolicited status does not match the length of the
actual write request.
Action: If abnormal behavior is observed or the problem
persists, contact your HP Support Representative.