General 200 Series Error Messages
| Component | Message | Cause |
|---|---|---|
| 200 Series | Invalid USP unit = x, slot = x, port = x | A port was not able to be translated correctly during the receive. |
| 200 Series | 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. |
| 200 Series | 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. |
| 200 Series | 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. |
| 200 Series | 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. |
| 200 Series | ACL (Access Control List) x not found in internal table | Attempting to delete a non-existent ACL. |
| 200 Series | ACL internal table overflow | Attempting to add an ACL to a full table. |
| 200 Series | In hapiBroadQosCosQueueConfig, Failed to configure minimum bandwidth. Available bandwidth x | Attempting to configure the bandwidth beyond it‘s capabilities. |
| 200 Series | 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. |
| 200 Series | USL: failed to sync ipmc table on unit = x | Either the transport failed or the message was dropped. |
| 200 Series | usl_task_ipmc_msg_send(): failed to send with x | Either the transport failed or the message was dropped. |
| 200 Series | USL: No available entries in the STG table | The Spanning Tree Group table is full in USL. |
| 200 Series | 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. |
| 200 Series | USL: A Trunk doesn't exist in USL | Attempting to modify a Trunk that doesn‘t exist. |
| 200 Series | USL: A Trunk being created by bcmx already existed in USL | Possible synchronization issue between the application, hardware, and sync layer. |
| 200 Series | USL: A Trunk being destroyed doesn't exist in USL | Possible synchronization issue between the application, hardware, and sync layer. |
| 200 Series | USL: A Trunk being set doesn't exist in USL | Possible synchronization issue between the application, hardware, and sync layer. |
| 200 Series | USL: failed to sync trunk 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. |
| 200 Series | USL: Mcast entry not found on a join | Possible synchronization issue between the application, hardware, and sync layer. |
| 200 Series | USL: Mcast entry not found on a leave | Possible synchronization issue between the application, hardware, and sync layer. |
| 200 Series | USL: failed to sync dVLAN data 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. |
| 200 Series | USL: failed to sync policy 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. |
| 200 Series | USL: failed to sync VLAN 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. |
| 200 Series | Invalid LAG (Link Aggregation Group) id x | Possible synchronization issue between the BCM driver and HAPI. |
| 200 Series | Invalid uport calculated from the BCM uport bcmx_l2_addr->lport = x | Uport not valid from BCM driver. |
| 200 Series | Invalid USP calculated from the BCM uport\nbcmx_l2_addr->lport = x | USP not able to be calculated from the learn event for BCM driver. |
| 200 Series | Unable to insert route R/P | Route R with prefix P could not be inserted in the hardware route table. A retry will be issued. |
| 200 Series | Unable to Insert host H | Host H could not be inserted in hardware host table. A retry will be issued. |
| 200 Series | USL: failed to sync L3 Intf 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. |
| 200 Series | USL: failed to sync L3 Host 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. |
| 200 Series | USL: failed to sync L3 Route 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. |
| 200 Series | USL: failed to sync initiator 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. |
| 200 Series | USL: failed to sync terminator 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. |
| 200 Series | USL: failed to sync ip-multicast 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. |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB