Netgear M4300-24X24F (XSM4348S) - Stackable Managed Switch with 48x10G including 24x10GBASE-T and 24xSFP+ Layer 3 Guia Do Programa

OS

Invalid USP unit = x, slot = x, port = x

A port was not able to be translated correctly 

during the receive. 

OS

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.

OS

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.

OS

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.

OS

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.

OS

ACL x not found in internal table

Attempting to delete a non-existent ACL.

OS

ACL internal table overflow

Attempting to add an ACL to a full table.

OS

In hapiBroadQosCosQueueConfig, Failed to 
configure minimum bandwidth. Available 
bandwidth x

Attempting to configure the bandwidth beyond it’s 

capabilities.

OS

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.

OS

USL: failed to sync ipmc table on unit = x

Either the transport failed or the message was 
dropped.

OS

usl_task_ipmc_msg_send(): failed to send with x Either the transport failed or the message was 

dropped.

OS

USL: No available entries in the STG table

The Spanning Tree Group table is full in USL.

OS

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.

OS

USL: A Trunk doesn't exist in USL

Attempting to modify a Trunk that doesn’t exist.

OS

USL: A Trunk being created by bcmx already 
existed in USL

Possible synchronization issue between the 
application, hardware, and sync layer.

OS

USL: A Trunk being destroyed doesn't exist in 
USL

Possible synchronization issue between the 
application, hardware, and sync layer.