This error message is seen in my controller logs: [ERROR] dhcp_support.c 357: dhcp_bind(): servPort dhcpstate failed. Why?
A. These error messages are mostly seen when the service port of the controller has DHCP enabled, but does not receive an IP address from a DHCP server. By default, the physical service port interface has a DHCP client installed and looks for an address via DHCP. The WLC attempts to request a DHCP address for the service port. If no DHCP server is available, then a DHCP request for the service port fails. Therefore, this generates the error messages. The workaround is to configure a static IP address to the service port (even if the service port is disconnected) or have a DHCP server available to assign an IP address to the service port. Then, reload the controller, if needed. The service port is actually reserved for out-of-band management of the controller and system recovery, and maintenance in the event of a network failure. It is also the only port that is active when the controller is in boot mode. The service port cannot carry 802.1Q tags. Therefore, it must be connected to an a
Related Questions
- When Heartbeat starts up I get this error message in my logs: "WARN: process_clustermsg: node [
] failed authentication". What does this mean? - The Cisco Clean Access Agent receives the "Network Error" error message while it logs on. Why is this?
- Why do the StoredProcessServer logs contain an error message: ARM Application data not available?
