Reference Guide

Table 62: General 200 Series Error Messages (continued)
Component Message Cause
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 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 Log Messages
ExtremeSwitching 200 Series: Command Reference Guide for version 01 .02.04.0007 684