D-Link DXS-5000-54S Emulator - Page 1254

5000 Series Layer 2/3 Managed Data Center Switch CLI Reference Guide Component DVMRP DVMRP Message DVMRP Prune Control message Send Failed; rtrlfNum - xxx. DVMRP Probe Control message Send Failed on rtrlfNum - xxx. Cause Neighbor - %s, SrcAddr - %s, GrpAddr %s DVMRP Prune control message send failed. This could mostly be because of a Failure return status of the socket call sendto(). As a result of this, the unwanted multicast traffic is still received and forwarded. DVMRP Probe control message send failed. This could mostly be because of a Failure return status of the socket call sendto(). As a result of this, the DVMRP neighbor could be lost in the neighboring DVMRP routers. Technologies Table 59: Error Messages Message Cause invalid USP unit = x, slot = x, port = x in hapiBroadSystemMacAddress call to 'l2_addr_add' - FAILED : x Failed installing mirror action - rest of the policy applied successfully Policy x does not contain rule x ERROR: policy x, tmpPolicy x, size x, data x x x x x x x x ACL x not found in internal table ACL internal table overflow In hapiBroadQosCosQueueConfig, Failed to configure minimum bandwidth. Available bandwidth x USL: failed to put sync response on queue USL: failed to sync ipmc table on unit = x usl_task_ipmc_msg_send(): failed to send with x USL: No available entries in the 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 dupliate 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. 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. 1248