Technologies; Table 49: Arp Log Message; Table 50: Rip Log Message; Table 51: Driver Error Messages - D-Link DWS-4000 Series Cli Command Reference

D-Link Unified Switch CLI Command Reference
Component Message
ARP ARP received mapping for IP address xxx to MAC
address yyy. This IP address may be configured on
two stations.
Component Message
RIP RIP : discard response from xxx via unexpected
interface
T
ECHNOLOGIES
Component Message
Driver Invalid USP unit = x, slot = x, port = x
Driver In hapiBroadSystemMacAddress call to
'bcm_l2_addr_add' - FAILED : x
Driver Failed installing mirror action - rest of the policy
applied successfully
Driver Policy x does not contain rule x
Driver ERROR: policy x, tmpPolicy x, size x, data x x x x
x x x x
Driver ACL x not found in internal table
Driver ACL internal table overflow
Driver In hapiBroadQosCosQueueConfig, Failed to
configure minimum bandwidth. Available
bandwidth x
Driver USL: failed to put sync response on queue
Driver USL: failed to sync ipmc table on unit = x
Driver usl_task_ipmc_msg_send(): failed to send with x Either the transport failed or the message was
© 2009 D-Link Corporation. All Rights Reserved
534

Table 49: ARP Log Message

Table 50: RIP Log Message

Table 51: Driver Error Messages

Cause
When we receive an ARP response with different
MAC address from another station with the same
IP address as ours. This might be a case of
misconfiguration.
Cause
When RIP response is received with a source
address not matching the incoming interface's
subnet.
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 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.
dropped.