NETGEAR XSM7224S - ProSafe 10 Gigabit Stackable Manual page 522

ProSafe XSM7224S Managed Stackable Switch CLI Manual, Software Version 9.0
Table 8-52: System General Error Messages
Component Message
OS In hapiBroadSystemMacAddress call to
'bcm_l2_addr_add' - FAILED : x
OS Failed installing mirror action - rest of the
policy applied successfully
OS Policy x does not contain rule x
OS ERROR: policy x, tmpPolicy x, size x, data x
x x x x x x x
OS ACL x not found in internal table
OS ACL internal table overflow
OS In hapiBroadQosCosQueueConfig, Failed to
configure minimum bandwidth. Available
bandwidth x
OS USL: failed to put sync response on queue A response to a sync request was not
OS USL: failed to sync ipmc table on unit=x
OS usl_task_ipmc_msg_send(): failed to send
with x
OS USL: No available entries in the STG table The Spanning Tree Group table is full in
OS USL: failed to sync stg table on unit=x
OS USL: A Trunk doesn't exist in USL
OS USL: A Trunk being created by bcmx
already existed in USL
OS USL: A Trunk being destroyed doesn't exist
in USL
Log Messages
Cause
Failed to add an L2 address to the MAC
table. This should only happen when a hash
collision occurs or the table is full.
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
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
An issue installing the policy due to a
possible duplicate hash
Attempting to delete a non-existent ACL
Attempting to add an ACL to a full table
Attempting to configure the bandwidth
beyond it's capabilities
enqueued. This could indicate that a
previous sync request was received after it
was timed out
Either the transport failed or the message
was dropped
Either the transport failed or the message
was dropped
USL
Could not synchronize unit x due to a
transport failure or API issue on remote unit.
A synchronization retry will be issued
Attempting to modify a Trunk that doesn't
exist
Possible synchronization issue between the
application, hardware, and sync layer
Possible synchronization issue between the
application, hardware, and sync layer.
v1.0, November 2010
8-24