Kontron AT8404 CLI - Manual (Page 346)

AT8404 FASTPATH log messages
Page B - 13 AT8404 CLI Reference Manual
B.6 Technologies
Table 34: DiffServ Log Messages
Component Message Cause
DiffServ diffserv.c 165: diffServRestore Failed to reset
DiffServ. Recommend resetting device
While attempting to clear the running
configuration an error was encountered in
removing the current settings. This may lead
to an inconsistent state in the system and
resetting is advised.
DiffServ Policy invalid for service intf: "policy name,
intIfNum x, direction y
The DiffServ policy definition is not compatible
with the capabilities of the interface specified.
Check the platform release notes for
information on configuration limitations.
Table 35: Broadcom Error Messages
Component Message Cause
Broadcom Invalid USP unit = x, slot = x, port =x A port was not able to be translated correctly
during the receive.
Broadcom In hapiBroadSystemMacAddress call to
'bcm_l2_addr_add' - FAILED : x
Failed to add an L2 address to the MAC table.
This should only happen when a hash collision
occurs or the table is full.
Broadcom Failed installing mirror action - rest of the
policy applied successfully
A previously configured probe port is not being
used in the policy. The release notes state
that only a single probe port can be configured
Broadcom Policy x does not contain rule x The rule was not added to the policy due to a
discrepancy in the rule count for this specific
policy . Additionally, the message can be
displayed when an old rule is being modified,
but the old rule is not in the policy
Broadcom ERROR: policy x, tmpPolicy x, size x, data x x
x x x x x x
An issue installing the policy due to a possible
duplicate hash
Broadcom ACL x not found in internal table Attempting to delete a non-existent ACL
Broadcom ACL internal table overflow Attempting to add an ACL to a full table
Broadcom In hapiBroadQosCosQueueConfig, Failed to
configure minimum bandwidth. Available
bandwidth x
Attempting to configure the bandwidth beyond
it’s capabilities
Broadcom USL: failed to put sync response on queue A response to a sync request was not
enqueued. This could indicate that a previous
sync request was received after it was timed
out
Broadcom USL: failed to sync ipmc table on unit=x Either the transport failed or the message was
dropped
Broadcom usl_task_ipmc_msg_send(): failed to send
with x
Either the transport failed or the message was
dropped
Broadcom USL: No available entries in the STG table The Spanning Tree Group table is full in USL
Broadcom USL: failed to sync stg table on unit=x Could not synchronize unit x due to a transport
failure or API issue on remote unit. A
synchronization retry will be issued
Broadcom USL: A Trunk doesn't exist in USL Attempting to modify a Trunk that doesn’t exist
Broadcom USL: A Trunk being created by bcmx already
existed in USL
Possible synchronization issue between the
application, hardware, and sync layer