Technologies - Ubiquiti EDGESWITCH ES-24-250W Command Reference Manual

EdgeSwitch CLI Command Reference

Technologies

Component Message
Invalid USP unit = x, slot = x, port
Broadcom
= x
In hapiBroadSystemMacAddress call to
Broadcom
'bcm_l2_addr_add' - FAILED : x
Failed installing mirror action - rest
Broadcom
of the policy applied successfully
Policy x does not contain rule x
Broadcom
ERROR: policy x, tmpPolicy x, size x,
Broadcom
data x x x x x x x x
ACL x not found in internal table
Broadcom
ACL internal table overflow
Broadcom
In hapiBroadQosCosQueueConfig, Failed
Broadcom
to configure minimum bandwidth.
Available bandwidth x
USL: failed to put sync response on
Broadcom
queue
USL: failed to sync ipmc table on
Broadcom
unit = x
usl_task_ipmc_msg_send(): failed to
Broadcom
send with x
USL: No available entries in the STG
Broadcom
table
USL: failed to sync stg table on
Broadcom
unit = x
USL: A Trunk doesn't exist in USL
Broadcom
USL: A Trunk being created by bcmx
Broadcom
already existed in USL
USL: A Trunk being destroyed doesn't
Broadcom
exist in USL
USL: A Trunk being set doesn't exist in
Broadcom
USL
USL: failed to sync trunk table on
Broadcom
unit = x
USL: Mcast entry not found on a join
Broadcom
USL: Mcast entry not found on a leave
Broadcom
USL: failed to sync dVLAN data on
Broadcom
unit = x
USL: failed to sync policy table on
Broadcom
unit = x
Ubiquiti Networks, Inc.
Table 53. Error Messages
Cause
A port was not able to be translated correctly during
the receive.
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 its
capabilities.
A response to a sync request was not 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.
The Spanning Tree Group table is full in 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.
Possible synchronization issue between the
application, hardware, and sync layer.
Could not synchronize unit x due to a transport failure
or API issue on remote unit. A synchronization retry
will be issued.
Possible synchronization issue between the
application, hardware, and sync layer.
Possible synchronization issue between the
application, hardware, and sync layer.
Could not synchronize unit x due to a transport failure
or API issue on remote unit. A synchronization retry
will be issued.
Could not synchronize unit x due to a transport failure
or API issue on remote unit. A synchronization retry
will be issued.
Log Messages
432