DHCP - S7700 V200R019C10 Log Reference

S7700 V200R019C10 Log Reference

This document provides the explanations, causes, and recommended actions of logs on the product.

Rate and give feedback:

Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).

DHCP

DHCP/4/DHCP_ALLOC_ADDRESS

Message

DHCP/4/DHCP_ALLOC_ADDRESS: Result of IP address allocation from the DHCP server to wireless users.[WLAN_STA_INFO_IP_CONNECTION]ACMAC:[STRING];ACNAME:[STRING];APMAC:[STRING];APNAME:[STRING];USER:[STRING];MAC:[STRING];TIME:[STRING];ZONE:[STRING];DAYLIGHT:[STRING];ERRCODE:[STRING];RESULT:[STRING]

Description

The log indicates the result of IP address allocation by a device functioning as a DHCP server to wireless users.

If a large number of such logs are displayed, other logs may be difficult to view. You can run the info-center filter-id bymodule-alias DHCP DHCP_ALLOC_ADDRESS command in the system view to shield such logs.

Parameters

Parameter Name	Parameter Meaning
ACMAC	MAC address of an AC.
ACNAME	System name of an AC.
APMAC	MAC address of an AP.
APNAME	System name of an AP.
USER	Name of a wireless user.
MAC	MAC address of a wireless user.
TIME	Time when a log is recorded, in seconds. (The seconds are calculated starting from 00:00:00 on January 1, 1970.)
ZONE:UTC	Time zone.
DAYLIGHT	Whether the daylight saving time (DST) is used. true: The DST is used. false: The DST is not used.
ERRCODE RESULT	Error code. IP address allocation result.

Possible Causes

When an AC, Fat AP, or cloud AP functions as a DHCP server, the AP through which a wireless user goes online, SSID of the user, and other user information can be obtained and recorded in this log. The following table lists the mapping relationships between error codes (ERRCODE) and address allocation results (RESULT) in logs.

Table 37-1 Mapping between ERRCODE and RESULT

ERRCODE	RESULT	Description	Possible Causes
0	Success	An IP address is successfully allocated.	–
102	DHCP IP POOL IS OUTFLOW(Pool name:name, the idle address num:num)	There is no idle IP address in the address pool. Parameters in the brackets indicate the address pool name and number of idle IP addresses.	No IP address is available for allocation in the address pool. You can run the display ip pool command to check the number of idle IP addresses. Here, the command output indicates that the number of idle IP addresses is 0.
103	DHCP IP POOL LOCKED(Pool name:name)	The address pool is locked. The parameter in the brackets indicates the address pool name.	The address pool is locked using the lock command in the address pool view.
104	NOT FIND IP POOL (Receive from interface:if, interface ip:ip. Relay ip:ip. Expect ip:ip)	The address pool corresponding to the client-expected IP address is not found. Parameters in the brackets indicate the Layer 3 interface that receives the DHCP Request packet, IP address of the interface, IP address of the DHCP relay agent, and client-expected IP address.	Possible cause 1: When a client is associated with an SSID, the client applies for an IP address in two-message exchange mode. That is, the client sends a DHCP Request packet carrying the expected IP address in Option50. The expected IP address is the address that the client has used before. If the client-expected IP address is on a different network segment from the client gateway address or the address pool corresponding to the client-expected IP address cannot be found, the DHCP server will fail to allocate this IP address. In this case, the DHCP server generates this log and returns a DHCP NAK packet to notify the client to apply for an IP address in four-message exchange mode, that is, the client sends a DHCP Discover packet to request for a new address. The network segment is changed when the client switches to another service VLAN. Possible cause 2: The DHCP server receives a DHCP Discover packet from the client. However, only the dhcp select global command is run on the server and no corresponding address pool is created. As a result, the DHCP server generates this log and does not return any packet. This case rarely occurs.
105	INCORRECT REQUEST IP OR MAC (Ip:ip MAC:mac)	The DHCP server cannot allocate the client-expected IP address. Parameters in the brackets indicate the client-expected IP address and client's MAC address.	Possible cause 1: The DHCP server receives a DHCP Discover packet from the client. In the packet, the client-expected IP address is carried in Option50. When the client-expected IP address is not on the network segment of the address pool, the DHCP server generates this log and allocates a new IP address to the client. Possible cause 2: When a client is associated with an SSID, the client applies for an IP address in two-message exchange mode. That is, the client sends a DHCP Request packet carrying the expected IP address in Option50. The expected IP address is the address that the client has used before. If the client-expected IP address is within the address pool range but the address pool has no record about allocating any IP address to the client, the address pool does not respond to the request. The client waits till its request expires and begins to apply for a new IP address in four-message exchange mode. This log may be generated if the DHCP server restarts, IP address allocation records are manually cleared using the reset ip pool command, or a client exception occurs (for example, the client still uses an IP address after the address expires).
106	IP CONFLICTED(The conflict ip:ip)	An IP address conflict occurs. The parameter in the brackets indicates the conflicted IP address.	An IP address conflict is detected when the DHCP server allocates an IP address to a client. The address pool then sets the IP address status to conflicting and allocates a new IP address to the client.

If the client-expected IP address is displayed as 255.255.255.255, the client does not expect any specific IP address.

Procedure

If there is no idle IP address in the address pool, you are advised to expand the address pool or shorten the address lease time.
If no corresponding address pool is configured, configure the address pool.
If the address pool is locked, determine the reason why it is locked. If the client is a PC, the PC typically applies for a new IP address in four-message exchange mode.
If the PC cannot obtain an IP address or cannot continue to use the original IP address, run the ipconfig /release and ipconfig /renew commands on the PC to enable it to apply for an IP address again. If the client is a mobile phone, delete the SSID recorded on the mobile phone and associate the SSID to the client again.

DHCP/5/DHCP_ALLOC_ADDRESS

Message

DHCP/5/DHCP_ALLOC_ADDRESS: Result of IP address allocation from the DHCP server to wireless users. [STRING]

Only wireless users support this log.

Description

The DHCP server successfully allocates an IP address.

Parameters

Parameter Name	Parameter Meaning
[STRING]	Information about the IP address that has been successfully allocated to a wireless user.

Possible Causes

When a wireless user applies for an IP address, the DHCP server records information about the IP address that has been successfully allocated to the user.

Procedure

This log message is informational only, and no action is required.

DHCP/0/DHCP_SERVER_DETECT

Message

DHCP/0/DHCP_SERVER_DETECT:A NEW SERVER IS FOUND. (SERVER INFO : IP Address = [IPADDR], MAC Address = [STRING1], Interface = [STRING2])

Description

A new DHCP server was discovered.

Parameters

Parameter Name	Parameter Meaning
IP Address	IP address of the server.
MAC Address	MAC address of the server.
Interface	Name of the interface receiving packets from the new server.

Possible Causes

The device receives packets from the new DHCP server.

Procedure

This log is informational only, and no action is required.

DHCP/0/DHCPRATET_LIMIT

Message

DHCP/0/DHCPRATET_LIMIT: The rate of DHCP packets exceeds the speed limit. [INTEGER] packets have been discarded.

Description

DHCPv4 messages exceed the rate and the number of discarded DHCPv4 messages reaches the threshold.

Parameters

Parameter Name	Parameter Meaning
[INTEGER]	Number of discarded packets.

Possible Causes

DHCPv4 messages exceed the rate and the number of discarded DHCPv4 messages reaches the threshold.

Procedure

The device received a large number of DHCPv4 packets, indicating that an attack occurred on the network. Disconnect the device from the network or configure a corresponding attack defense policy.

DHCP/4/DHCPSNP_ONLINE_FAIL

Message

DHCP/4/DHCPSNP_ONLINE_FAIL: The user failed to request an IP address. (Client MAC Address=[STRING], VLAN=[ULONG], APID=[ULONG], APMAC=[STRING], APName=[STRING], RadioId=[ULONG], SSID=[STRING], Failure Reason=[STRING]).

Description

The user fails to apply for an IP address.

Parameters

Parameter Name	Parameter Meaning
Client MAC Address	MAC address of a user.
VLAN	VLAN to which a user belongs.
APID	Index of the AP.
APMAC	MAC address of the AP.
APName	Name of the AP.
RadioId	Radio ID.
SSID	Wireless SSID.
Failure Reason	Failure cause.

Possible Causes

When the AP functions as the DHCP snooping device, the user fails to obtain the IP address and the AP sends this log to the AC. The failure causes displayed in Failure Reason are as follows:

The DHCP server did not respond within the specified period: The time period for waiting for a response from the DHCPv4 server expires.
The DHCP server failed to allocate an IP address: The DHCPv4 server sends a NAK message.
DHCP snooping discarded the packet or DHCPv6 snooping discarded the packet: Packet loss occurs on the DHCP snooping device.
No DHCP offer was received from the DHCP server: The DHCP snooping device does not receive a DHCP Offer message sent by the DHCPv4 server.
No DHCP request in selecting state was received from the DHCP client: The DHCP snooping device does not receive a Request message sent by the DHCPv4 client.
No DHCP ACK was received from the DHCP server in response to the DHCP request in selecting state: During the four-step process, the DHCP snooping device does not receive an ACK message sent by the DHCPv4 server after receiving the Request message sent by the DHCPv4 client.
No DHCP ACK was received from the DHCP server in response to the DHCP request in init-reboot state: During the two-step process, the DHCP snooping device does not receive an ACK message sent by the DHCPv4 server after receiving the Request message sent by the DHCPv4 client.
No DHCP ACK was received from the DHCP server in response to the DHCP request in renewing state: During the lease renewal process, the DHCP snooping device does not receive an ACK message sent by the DHCPv4 server after receiving the unicast Request message sent by the DHCPv4 client.
No DHCP ACK was received from the DHCP server in response to the DHCP request in rebinding state: During the lease renewal process, the DHCP snooping device does not receive an ACK message sent by the DHCPv4 server after receiving the broadcast Request message sent by the DHCPv4 client.
No DHCPv6 advertise was received from the DHCPv6 server: The DHCP snooping device does not receive an Advertise message sent by the DHCPv6 server.
No DHCPv6 request was received from the DHCPv6 client: The DHCP snooping device does not receive a Request message sent by the DHCPv6 client.
No DHCPv6 reply was received from the DHCPv6 server in response to the DHCPv6 request: The DHCP snooping device does not receive a Reply message sent by the DHCPv6 server after receiving the Request message sent by the DHCPv6 client.
No DHCPv6 reply was received from the DHCPv6 server in response to the DHCPv6 renew: The DHCP snooping device does not receive a Reply message sent by the DHCPv6 server after receiving the Renew message sent by the DHCPv6 client.
No DHCPv6 reply was received from the DHCPv6 server in response to the DHCPv6 rebind: The DHCP snooping device does not receive a Reply message sent by the DHCPv6 server after receiving the Rebind message sent by the DHCPv6 client.

Procedure

Locate and rectify the fault according to Failure Reason.

DHCP/4/DHCP_RELAY_WRONG_GIADDR

Message

DHCP/4/DHCP_RELAY_WRONG_GIADDR: DHCP relay receive a dhcp packet with wrong giaddr address. (InterfaceName=[STRING])

Description

The DHCP relay agent received a DHCP packet with an incorrect GIADDR field value.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Indicates the interface name.

Possible Causes

The DHCP packet was processed by another DHCP relay agent on the network, so that information of the GIADDR field was inconsistent with that of the interface where the DHCP relay function is configured.

Procedure

Search for other DHCP relay agents on the network according to the interface name and GIADDR field information in the log. Check the network and determine whether the DHCP relay agent configuration is correct.

DHCP/4/DHCP_RELAY_WRONG_MAC

Message

DHCP/4/DHCP_RELAY_WRONG_MAC: DHCP relay receive a dhcp packet with wrong 'chaddr'. (CHADDR=[STRING1], MAC type=[STRING2], InterfaceName=[STRING3]).

Description

The DHCP relay receives a DHCP packet with the incorrect client MAC address.

Parameters

Parameter Name	Parameter Meaning
CHADDR	MAC address of the DHCP client.
MAC type	MAC address type of the DHCP client. broadcast multicast
InterfaceName	Name of the interface configured with the DHCP relay function.

Possible Causes

The DHCP relay receives a DHCP packet in which the client MAC address field is set to a broadcast or unicast address. To prevent attacks, the device considers this packet as an invalid packet.

Procedure

Check whether there are DHCP attacks based on the client MAC address and the name of the interface that receives the packet.
- Y=>2.
- N=>3.
Configure DHCP snooping to check validity of DHCP packets.
End.

DHCP/4/DHCP_BINDTBL_ADDR_CONFLICT

Message

DHCP/4/DHCP_BINDTBL_ADDR_CONFLICT: Delete dhcp bind-table because IP address conflict. (Bind-table info: InterfaceName=[STRING], Pvlan=[ULONG], Cvlan=[ULONG], IP Address=[IPADDR], MAC Address=[STRING])

Description

A user binding table was deleted because of an IP address conflict.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Indicates the interface connected to a user in the binding table.
Pvlan	Indicates information about the outer VLAN of the user in the binding table.
Cvlan	Indicates information about the inner VLAN of the user in the binding table.
IP Address	Indicates the IP address of the user in the binding table.
MAC Address	Indicates the MAC address of the user in the binding table.

Possible Causes

The IP address of a user in the binding table conflicted with the IP address of another user.

Procedure

This log message is informational only, and no action is required.

DHCP/4/DHCP_INFO_LOG_DHCP_ADD_ACL_FAILED

Message

DHCP/4/DHCP_INFO_LOG_DHCP_ADD_ACL_FAILED: Add ACL failed because of no enough ACL resources. (Slot=[STRING])

Description

ACL rules failed to be delivered because ACL resources were insufficient.

Parameters

Parameter Name	Parameter Meaning
Slot	Slot ID.

Possible Causes

If the ACL resources are insufficient, the configured DHCP commands do not take effect.

Procedure

Adjust the usage of ACL resources using either of the following methods:
1. Run the display acl resource command to view information about ACL resources and check services that occupy many ACL resources.
2. Run the display current-configuration command to view configuration information. Delete unused configurations to release ACl resources.
Delete DHCP-related commands and reconfigure commands related to the DHCP service to redeliver the DHCP service. After performing the preceding operations, check whether the log is still generated.
- If the log is not generated, go to step 4.
- If the log is still generated, go to step 3.
Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.
End.

DHCP/4/DHCP_INFO_LOG_DHCP_REMOTEBACKUP_FAILED

Message

DHCP/4/DHCP_INFO_LOG_DHCP_REMOTEBACKUP_FAILED: Saving the dynamic binding table to a remote server failed. Ensure that the remote server address is reachable and the user name and password and the file path are correct.

Description

DHCP snooping binding entries fail to be backed up on the remote server. Ensure that the device can connect to the server, the entered user name and password are correct, and the path for storing the binding table file is correct.

Parameters

Parameter Name	Parameter Meaning
None	None

Possible Causes

The device cannot connect to the remote server.
The input user name or password is incorrect.
The path for storing the binding table file is incorrect.

Procedure

Check whether the IP address of the remote server is correct. Ensure that the device can correctly connect to the server.
Ensure that the input user name or password is correct.
Ensure that the path for storing the binding table file is correct.

DHCP/4/IPV6CON_LINK

Message

DHCP/4/IPV6CON_LINK: The IPv6 address assigned by a DHCPv6 server conflicts with another host on the link. (InterfaceName=[STRING], Ipv6Address=[STRING], ServerDuid=[STRING])

Description

The IPv6 address assigned to a DHCPv6 client by the DHCPv6 server conflicts with the IPv6 address of another device on the network.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Name of an interface on the DHCPv6 client.
IPv6Address	Conflicting IPv6 address.
ServerDuid	DUID of the DHCPv6 server.

Possible Causes

The DHCPv6 client detects that the IPv6 address assigned to it by the DHCPv6 server conflicts with the IPv6 address of another device on the network.

Procedure

Run the display dhcpv6 client [ interface interface-type interface-number ] command to check whether the DHCPv6 client can request an IPv6 address. If the DHCPv6 client has requested an IPv6 address, no action is required. If the DHCPv6 client fails to request an IPv6 address, contact technical support personnel.

DHCP/0/ND_SERVER_DETECT

Message

DHCP/0/ND_SERVER_DETECT: AN UNTRUSTED ND SERVER IS FOUND. (SERVER INFO : IP Address=[STRING], MAC Address=[STRING], Interface Name=[STRING], Prefix=[STRING], Prefix len=[ULONG], VLAN=[ULONG])

Description

The ND server information is recorded.

Parameters

Parameter Name	Parameter Meaning
IP Address	IP address of the server.
MAC Address	MAC address of the server.
Interface Name	Interface name.
Prefix	Prefix name.
Prefix len	Prefix length.
VLAN	VLAN ID.

Possible Causes

The non-trusted interface receives RA messages from a new server on a network where ND snooping is enabled.

Procedure

Check the network and search for the unauthorized server according to the server IP address.
Deal with the unauthorized server based on requirements. For example, disconnect it from the network or configure a corresponding attack defense policy.

DHCP/4/DHCP_INFO_LOG_DHCP_SLAVE_LOW_SPACE

Message

DHCP/4/DHCP_INFO_LOG_DHCP_SLAVE_LOW_SPACE: There is no space for DHCP on the slave board.

Description

The slave board does not have sufficient space for the DHCP service.

Parameters

None

Possible Causes

When the service is being stored, the storage space of the slave board is insufficient.

Procedure

Run the dir command to view information about all files.
Run the delete /unreserved command to permanently delete expired and unused files to release the occupied storage space.

DHCP/4/DHCP_RELAY_WRONG_TYPE

Message

DHCP/4/DHCP_RELAY_WRONG_TYPE: DHCP relay receive a dhcp packet with wrong packet type. (InterfaceName=[STRING]).

Description

The DHCP relay agent received a DHCP packet of an incorrect packet type.

Parameters

Parameter Name	Parameter Meaning
[STRING]	Indicates the interface name.

Possible Causes

The DHCP relay agent received a DHCP packet of an incorrect packet type.

Procedure

Check whether the DHCP configurations are correct after the DHCP relay agent receives an incorrect type of DHCP packet.

DHCP/0/DHCPV6_SERVER_DETECT

Message

DHCP/0/DHCPV6_SERVER_DETECT: A NEW SERVER IS FOUND. (SERVER INFO: IP Address=[STRING], MAC Address=[STRING], Interface=[STRING])

Description

The DHCPv6 server information is recorded.

Parameters

Parameter Name	Parameter Meaning
IP Address	IP address of the server.
MAC Address	IP address of the server.
Interface	Name of the interface that receives the MAC address of the server.

Possible Causes

Messages from the new DHCPv6 server are received.

Procedure

If a small number of log messages are displayed, this log message is informational only and no action is required.
If a large number of log messages are displayed, you need to search for the unauthorized server according to the interface name, MAC address, and IP address in the logs. Deal with the unauthorized server based on requirements. For example, disconnect it from the network or configure a corresponding attack defense policy.

DHCP/0/DHCPV6RATET_DETECT

Message

DHCP/0/DHCPV6RATET_DETECT: The rate of DHCPV6 packets exceeds the speed limit. [INTEGER] packets have been discarded.

Description

DHCPv6 messages exceed the rate and the number of discarded DHCPv6 messages reaches the threshold.

Parameters

Parameter Name	Parameter Meaning
[INTEGER]	Number of discarded packets.

Possible Causes

DHCPv6 messages exceed the rate and the number of discarded DHCPv6 messages reaches the threshold.

Procedure

Run the display this include-default | include dhcpv6 packet-rate drop-alarm threshold command in the system view to check the alarm threshold for the number of DHCPv6 messages discarded when the rate of DHCPv6 messages exceeds the rate limit. Determine whether the threshold is proper based on the actual service traffic.
- If the threshold value is proper, the device received a large number of DHCPv6 packets, indicating that an attack occurred on the network. Disconnect the device from the network or configure a corresponding attack defense policy.
- If the threshold value is improper, run the dhcpv6 packet-rate drop-alarm threshold threshold command in the system view to modify the alarm threshold for the number of DHCPv6 messages discarded when the rate of DHCPv6 messages exceeds the rate limit.

DHCP/4/DHCPV6_ALLOC_ADDR_CONFLICT

Message

DHCP/4/DHCPV6_ALLOC_ADDR_CONFLICT: DHCPV6 client alloc address is conflict. (IP6 Address = [STRING], InterfaceName=[ STRING]).

Description

The IPv6 address requested by the DHCPv6 client conflicted.

Parameters

Parameter Name	Parameter Meaning
IP6 Address	This object indicates the conflicting IPv6 address.
InterfaceName	This object indicates the name of the interface that requests an IPv6 address.

Possible Causes

The requested IPv6 address has been configured.
Other users in the network use the requested IPv6 network.

Procedure

Run the display dhcpv6 client [ interface interface-type interface-number ] command to check whether the DHCPv6 client can request an IPv6 address. If the DHCPv6 client has requested an IPv6 address, go to step 3. If the DHCPv6 client fails to request an IPv6 address, go to step 2.
Contact technical support personnel.
End.

DHCP/5/REQIPV6_SUC

Message

DHCP/5/REQIPV6_SUC: The DHCPv6 client acquired IPv6 address successfully. (InterfaceName=[STRING1], Ipv6Address=[STRING2], ServerDuid=[STRING3])

Description

A DHCPv6 client obtained an IPv6 address successfully.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Interface name.
Ipv6Address	IPv6 address obtained by the DHCPv6 client.
ServerDuid	DUID of the DHCPv6 server.

Possible Causes

A DHCPv6 client obtained an IPv6 address successfully.

Procedure

This alarm is informational only, and no action is required.

DHCP/4/PREF_LENCHK

Message

DHCP/4/PREF_LENCHK: The delegated prefix is too small to allocate all of its interfaces. (InterfaceName=[STRING1], PrefixName=[STRING2], Prefix=[STRING3], PrefixLength=[INTEGER1], RequiredPrefixLength=[INTEGER2], ServeDuid=[STRING4])

Description

The length of the IPv6 prefix bound to an interface is shorter than the length of the IPv6 prefix obtained by a DHCPv6 PD client. The interface cannot generate the global unicast IPv6 address based on the bound IPv6 prefix.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Interface name.
PrefixName	Prefix name.
Prefix	Obtained prefix.
PrefixLength	Obtained prefix length.
RequiredPrefixLength	Required prefix length.
ServeDuid	Server DUID.

Possible Causes

The length of the IPv6 prefix bound to the interface is shorter than the length of the IPv6 prefix obtained by the DHCPv6 PD client.

Procedure

Run the prefix-delegation ipv6-prefix/ipv6-prefix-length assign-prefix-length command to change the prefix length bound to the IPv6 address pool.

DHCP/5/GW_RENEW

Message

DHCP/5/GW_RENEW: The gateway assigned by a DHCP server changed. (Client InterfaceName=[STRING1], ServerId=[IPADDR], Old Gateway=[STRING2], New Gateway=[STRING3])

Description

The gateway address assigned by the DHCP server changed.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Name of the interface to which the client is connected.
ServerId	DHCP server ID.
Old Gateway	Original gateway address.
New Gateway	New gateway address.

Possible Causes

The gateway address assigned by the DHCP server changed.

Procedure

This log is informational only, and no action is required.

DHCP/4/PREF_UPDATE

Message

DHCP/4/PREF_UPDATE: The IPv6 prefix assigned by a DHCPv6 server changed. (InterfaceName=[STRING1], OldPrefix=[STRING2], NewPrefix=[STRING3], ServerDuid=[STRING4])

Description

The IPv6 prefix assigned by the DHCPv6 server changed.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Interface name.
OldPrefix	Original IPv6 prefix.
NewPrefix	New IPv6 prefix.
ServerDuid	Server DUID.

Possible Causes

The IPv6 prefix assigned by the DHCPv6 server changed.

Procedure

This log is informational only, and no action is required.

DHCP/5/REQPREF_SUC

Message

DHCP/5/REQPREF_SUC: The DHCPv6 client acquired IPv6 prefix successfully. (InterfaceName=[STRING1], Prefix=[STRING2], PrefixLength=[INTEGER], ServerDuid=[STRING3])

Description

A DHCPv6 client obtained an IPv6 prefix successfully.

Parameters

Parameter Name	Parameter Meaning
InterfaceName	Interface name.
Prefix	IPv6 prefix obtained by the DHCPv6 client.
PrefixLength	IPv6 prefix length.
ServerDuid	DUID of the DHCPv6 server.

Possible Causes

A DHCPv6 client obtained an IPv6 prefix successfully.

Procedure

This log is informational only, and no action is required.

DHCP/4/IPCON_IF

Message

DHCP/4/IPCON_IF: The IP address assigned by a DHCP server conflicted with another interface. (Client InterfaceName=[interface-name], ServerId=[ip-address], Assigned IpAddress=[assigned-ip-address])

Description

The IP address allocated for the interface conflicted with that of another interface on the device.

Parameters

Parameter Name	Parameter Meaning
interface-name	Indicates the interface name of the DHCP client.
ip-address	Indicates the IP address of the DHCP server.
assigned-ip-address	Indicates the IP address obtained by the interface from the DHCP server.

Possible Causes

The IP address allocated for the interface conflicted with that of another interface on the device.

Procedure

Run the display current-configuration command to check the configuration of DHCP.
- Yes => Run the display ip interface brief command to check the settings of interfaces on the device, and then find the interfaces of the same IP address. Then run the ip address command to change the IP address of the interface.
- No => Re-configure DHCP according to the requirement.

DHCP/4/IPCON_LINK

Message

DHCP/4/IPCON_LINK: The IP address assigned by a DHCP server conflicted with another host on the link. (Client InterfaceName=[interface-name], ServerId=[ip-address], Assigned IpAddress=[assigned-ip-address])

Description

The IP address allocated for the interface conflicted with that of another device on the network.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Indicates the interface name of the DHCP client.
ServerId	Indicates the IP address of the DHCP server.
Assigned IpAddress	Indicates the IP address obtained by the interface from the DHCP server.

Possible Causes

The IP address allocated for the interface conflicts with that of another interface on the device.

Procedure

The DHCP client will request an IP address again. This log message is informational only and no action is required.

DHCP/4/NAK

Message

DHCP/4/NAK: The DHCP client received a NAK packet from a DHCP server. (Client InterfaceName=[interface-name], ServerId=[ip-address])

Description

The interface received the NAK packet from the DHCP server.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Indicates the name of the interface for which the IP address is applied for again.
ServerId	Indicates the IP address of the DHCP server.

Possible Causes

The IP address obtained by the interface is inconsistent with the lease IP address saved on the DHCP server.

Procedure

If the interface keeps receiving NAK packets from the DHCP server, check whether the DHCP server configuration is correct.
- If the DHCP server configuration is correct, go to step 2.
- If the DHCP server configuration is incorrect, go to step 3.
No action is required and the DHCP client will request an IP address again.
Modify the DHCP server configuration.

DHCP/5/RENEW

Message

DHCP/5/RENEW: The IP address lease is successfully renewed. (Client InterfaceName=[STRING], ServerId=[IPADDR], Acquired IpAddress=[IPADDR], Mask=[IPADDR], Gateway=[STRING], Static Route=[STRING], Lease Duration=[STRING], DNS Server=[STRING], DNS Domain=[STRING], Cloud management URL=[STRING], Option43=[STRING])

Description

The IP address lease of a device functioning as a DHCP client is successfully renewed.

Parameters that a device does not support or are not configured on the DHCP server are recorded as () in the log.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Name of an interface on the DHCP client.
ServerId	IP address of the DHCP server.
Acquired IpAddress	IP address allocated to the DHCP client.
Mask	Network mask.
Gateway	Gateway address.
Static Route	Static route.
Lease Duration	Lease time.
DNS Server	DNS server.
DNS Domain	DNS domain name.
Cloud management URL	URL of the iMaster NCE-Campus.
Option43	Information about DHCP Option43.

Possible Causes

The IP address lease of a device functioning as a DHCP client is successfully renewed.

Procedure

This log is informational only, and no action is required.

DHCP/5/RELEASE

Message

DHCP/5/RELEASE: The DHCP client released address successfully. (Client InterfaceName=[STRING], Lease IpAddress=[IPADDR], Client MacAddress=[STRING], Online Duration=[INTEGER], Lease Duration=[STRING])

Description

A device functioning as a DHCP client successfully releases the IP address.

Parameters that a device does not support or are not configured on the DHCP server are recorded as () in the log.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Interface name of the DHCP client.
Lease IpAddress	IP address of the DHCP server.
Client MacAddress	MAC address of the DHCP client.
Online Duration	Online duration.
Lease Duration	Lease time.

Possible Causes

A device functioning as a DHCP client successfully releases the IP address.

Procedure

This log is informational only, and no action is required.

DHCP/5/REQIP

Message

DHCP/5/REQIP: The DHCP client acquired IP address successfully. (Client InterfaceName=[STRING], ServerId=[IPADDR], Acquired IpAddress=[IPADDR], Mask=[IPADDR], Gateway=[STRING], Static Route=[STRING], Lease Duration=[STRING], DNS Server=[STRING], DNS Domain=[STRING], Cloud management URL=[STRING], Option43=[STRING])

Description

A device functioning as a DHCP client successfully requests an IP address from the DHCP server.

Parameters that a device does not support or are not configured on the DHCP server are recorded as () in the log.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Name of an interface on the DHCP client.
ServerId	IP address of the DHCP server.
Acquired IpAddress	IP address allocated to the DHCP client.
Mask	Network mask.
Gateway	Gateway address.
Static Route	Static route.
Lease Duration	Lease time.
DNS Server	DNS server.
DNS Domain	DNS domain name.
Cloud management URL	URL of the iMaster NCE-Campus.
Option43	Information about DHCP Option43.

Possible Causes

A device functioning as a DHCP client successfully requests an IP address from the DHCP server.

Procedure

This log is informational only, and no action is required.

DHCP/5/RT_RENEW

Message

DHCP/5/RT_RENEW: The static route assigned by a DHCP server changed. (Client InterfaceName=[interface-name], ServerId=[ip-address], Old StaticRoute=[old-static-route], New StaticRoute=[new-static-route])

Description

The static route obtained by the interface from the DHCP server was changed.

Parameters

Parameter Name	Parameter Meaning
interface-name	Indicates the interface name.
ip-address	Indicates the IP address of the DHCP server.
old-static-route	Indicates the static route before the change.
new-static-route	Indicates the static route after the change.

Possible Causes

Option 33 or option 121 configured on the DHCP server was changed.

Procedure

This log message indicates a normal situation, and no action is required.

DHCP/4/DHCP_DELIVCONFIG_LPU_FAILED

Message

DHCP/4/DHCP_DELIVCONFIG_LPU_FAILED: Failed to deliver the LPU configuration. (Configuration view=[STRING], configuration=[STRING], Slot=[STRING])

Description

Related configurations of the function of checking abnormal packets failed to be delivered on the LPU.

Parameters

Parameter Name	Parameter Meaning
Configuration view	Configuration view.
configuration	Configuration content.
Slot	Slot ID.

Possible Causes

The configuration of the dhcp anti-attack check magic-cookie or dhcp anti-attack check udp-checksum command fails to be delivered on the LPU.

Procedure

After the undo dhcp anti-attack check magic-cookie or undo dhcp anti-attack check udp-checksum command is run, run the dhcp anti-attack check magic-cookie or dhcp anti-attack check udp-checksum command again to redeliver the configuration.

DHCP/4/ENQUEUE_FAILED

Message

DHCP/4/ENQUEUE_FAILED: The number of the DHCP discarded packets that Write queue fail. (DiscardedNumber=[STRING], Type=[INTEGER], UTC=[INTEGER])

Description

Statistics on DHCPv4 or DHCPv6 messages discarded because they fail to be written into the queue are collected.

Parameters

Parameter Name	Parameter Meaning
DiscardedNumber	Number of discarded messages.
Type	Packet type. The value can be: DHCPv4: Statistics on discarded DHCPv4 messages. DHCPv6: Statistics on discarded DHCPv6 messages.
UTC	Timestamp.

Parameter Name

Parameter Meaning

DiscardedNumber

Number of discarded messages.

Type

Packet type. The value can be:

DHCPv4: Statistics on discarded DHCPv4 messages.
DHCPv6: Statistics on discarded DHCPv6 messages.

UTC

Timestamp.

Possible Causes

The queue for DHCPv4 or DHCPv6 messages is full.

Procedure

When a user login suspends, the message queue is automatically cleared. After the queue is cleared, the user can go online again.

DHCP/6/SNP_RCV_MSG

Message

DHCP/6/SNP_RCV_MSG: DHCP snooping received a message. (Msgtype=[STRING], UserMac=[STRING], Vlan=[INTEGER], TransId=[STRING], ClientIp=[STRING], RequestIp=[STRING], ServerIp=[STRING], YourIp=[STRING], RelayIp=[STRING], SrcMac=[STRING], DstMac=[STRING], SrcIp=[STRING], DstIp=[STRING], BFlag=[INTEGER], UTC=[INTEGER])

Description

A DHCP snooping-enabled device receives a DHCP message.

Parameters

Parameter Name	Parameter Meaning
Msgtype	Indicates the type of the received DHCP message.
UserMac	Indicates the user's MAC address.
Vlan	Indicates the VLAN to which the user belongs.
TransId	Indicates the transaction ID of the received message.
ClientIp	Indicates the IP address of the DHCP client.
RequestIp	Indicates the IP address requested by the DHCP client.
ServerIp	Indicates the IP address of the DHCP server.
YourIp	Indicates the IP address assigned by the DHCP server to the DHCP client.
RelayIp	Indicates the IP address of the DHCP relay agent.
SrcMac	Indicates the source MAC address of the DHCP message.
DstMac	Indicates the destination MAC address of the DHCP message.
SrcIp	Indicates the source IP address of the DHCP message.
DstIp	Indicates the destination IP address of the DHCP message.
BFlag	Indicates the BOOTP flap in the DHCP message.
UTC	Indicates the time stamp.

Possible Causes

This log is recorded if a DHCP snooping-enabled device receives a DHCP message including a DHCP Discover, DHCP Offer, DHCP Request, DHCP ACK, DHCP NAK, DHCP Decline, DHCP Release, and DHCP Inform message.

Procedure

This log is informational only, and no action is required.

DHCP/6/DHCP_SNP_USERBIND_RECOVER

Message

DHCP/6/DHCP_SNP_USERBIND_RECOVER: DHCP snooping user-bind table is recovered from remote server. ([STRING])

Description

The DHCP snooping binding table is restored from the remote server.

Parameters

Parameter Name	Parameter Meaning
[STRING]	Information about restored DHCP snooping binding entries: Total number: indicates the number of DHCP snooping binding entries backed up from the remote server. success: indicates the number of successfully restored DHCP snooping binding entries. fail: indicates the number of DHCP snooping binding entries that failed to be restored. Details of failure: indicates the details of restoration failure causes. Binding Collision: indicates that DHCP snooping binding entries failed to be restored due to a collision between local entries and remote entries. Exceeds max limit: indicates that DHCP snooping binding entries failed to be restored because the number of local DHCP snooping binding entries reached the upper limit. Invalid interface: indicates that DHCP snooping binding entries failed to be restored because the local interface was invalid, for example, the local interface was Down. Invalid VLAN: indicates that DHCP snooping binding entries failed to be restored because the VLAN of the local device was invalid, for example, the VLAN does not exist. Invalid snooping configuration: indicates that DHCP snooping binding entries failed to be restored because the DHCP snooping function was not enabled. Expired lease: indicates that DHCP snooping binding entries failed to be restored because the lease of the DHCP snooping binding table expired. Parse failure: indicates that DHCP snooping binding entries failed to be restored because the device failed to parse the DHCP snooping binding table file.

Parameter Name

Parameter Meaning

[STRING]

Information about restored DHCP snooping binding entries:

Total number: indicates the number of DHCP snooping binding entries backed up from the remote server.
success: indicates the number of successfully restored DHCP snooping binding entries.
fail: indicates the number of DHCP snooping binding entries that failed to be restored.
Details of failure: indicates the details of restoration failure causes.
Binding Collision: indicates that DHCP snooping binding entries failed to be restored due to a collision between local entries and remote entries.
Exceeds max limit: indicates that DHCP snooping binding entries failed to be restored because the number of local DHCP snooping binding entries reached the upper limit.
Invalid interface: indicates that DHCP snooping binding entries failed to be restored because the local interface was invalid, for example, the local interface was Down.
Invalid VLAN: indicates that DHCP snooping binding entries failed to be restored because the VLAN of the local device was invalid, for example, the VLAN does not exist.
Invalid snooping configuration: indicates that DHCP snooping binding entries failed to be restored because the DHCP snooping function was not enabled.
Expired lease: indicates that DHCP snooping binding entries failed to be restored because the lease of the DHCP snooping binding table expired.
Parse failure: indicates that DHCP snooping binding entries failed to be restored because the device failed to parse the DHCP snooping binding table file.

Possible Causes

Backed up DHCP snooping binding entries are restored from the remote server.

Procedure

If DHCP snooping binding entries are restored successfully, this log message is informational only, and no action is required.
If DHCP snooping binding entries failed to be restored, rectify the fault according to failure causes:
- Cause: Binding Collision
  
  There are DHCP snooping binding entries on the local device, so no action is required.
- Cause: Exceeds max limit
  
  Run the reset dhcp snooping user-bind command to delete unnecessary DHCP snooping binding entries.
- Cause: Invalid interface
  
  Ensure that the interface is working properly.
- Cause: Invalid VLAN
  
  Ensure that the VLAN has been created.
- Cause: Invalid snooping configuration
  
  Run the dhcp snooping enable command in the system view to enable DHCP snooping globally.
- Cause: Expired lease
  
  The lease of the DHCP snooping binding table expires, so no action is required.
- Cause: Parse failure
  
  Ensure that the file format is correct or contact technical support personnel.

DHCP/5/WAITOFFER_TIMEOUT

Message

DHCP/5/WAITOFFER_TIMEOUT: The DHCP server did not respond within the specified period. (Client InterfaceName=[STRING], Current state=[IPADDR], MAC address=[STRING], Expected address=[STRING])

Description

A device functioning as a DHCP client does not receive any response packet from the DHCP server within a specified period of time.

Parameters that a device does not support or are not configured on the DHCP server are recorded as () in the log.

Parameters

Parameter Name	Parameter Meaning
Client InterfaceName	Name of an interface on the DHCP client.
Current state	Status of the DHCP client.
MAC address	MAC address of the DHCP client.
Expected address	Original IP address of the DHCP client.

Possible Causes

A device functioning as a DHCP client does not receive any response packet from the DHCP server within a specified period of time.

Procedure

This log is informational only, and no action is required.

Translation

简体中文

Download

Updated: 2022-01-25

Document ID: EDOC1100126883

Downloads: 18

Average rating:

This Document Applies to these Products

Related Version

Digital Signature File

Digital Signature Authentication Mode