topic We've worked with cisco TAC in Wireless

IP addr not registering correctly

theophile — Mon, 05 Jul 2021 08:57:32 GMT

Hello,

SInce we've upgraded our 8500 to firmware 8.0 (previously 7.4), the logs are filled with a lot of this message:

DHCP Socket Task: Nov 18 09:05:02.792: #DHCP-4-IPRGSTR_MSCB_FAIL: dhcp_proxy.c:1938 Registering IP on mscb failed for statione0:94:67:07:b1:da
*DHCP Socket Task: Nov 18 09:05:02.792: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1873 Not registering IP address 10.231.14.31 with netmask 255.255.255.240 for client e0:94:67:07:b1:da
*DHCP Socket Task: Nov 18 09:05:02.792: #DHCP-4-IPRGSTR_MSCB_FAIL: dhcp_proxy.c:1938 Registering IP on mscb failed for statione0:94:67:07:b1:da
*DHCP Socket Task: Nov 18 09:05:02.792: #APF-4-NOT_REGISTERING_IP_ADD_ON_MSCB: apf_foreignap.c:1873 Not registering IP address 10.231.14.31 with netmask 255.255.255.240 for client e0:94:67:07:b1:da

Mainly all of our clients get an IP address for a while then disconnect then try to get another one etc. The connection is not stable at all. When looking at the client part of the wlc, the client is noted as 0.0.0.0 althought when doing an ipconfig of the laptop, the laptop has an IP addr.

We didn't change anything in the wlc's configuration since the upgrade, nor in the netwoirk architecture (dhcp, radius). The wlc is acting as dhcp proxy.

I tried to find an explanation on google but no result. Any help will be really appreciated!

Thanks

Théo

Error Message %DHCP-4

mohanak — Tue, 18 Nov 2014 11:11:36 GMT

Error Message    %DHCP-4-IPRGSTR_MSCB_FAIL: Registering IP on mscb failed for 
station[hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Registering IP on the mscb failed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/message/guide/controller_smg/msgs4.html#wp1000716

Hi Theo,Something Client

Sandeep Choudhary — Wed, 19 Nov 2014 09:17:33 GMT

Hi Theo,

Something Client automatically(Many deuath...) goes to excluded list.

1. So first disable exclusion client from WLAN advanced page.

2. Try to connect the client again.

3. Check if mac filtering is enabled on wlan..and client is not added in mac list.

4. If client is not in excluded list then try to reboot the WLC and try again.

Regards

Dont forget to rate helpful posts

We've worked with cisco TAC

theophile — Thu, 20 Nov 2014 13:58:02 GMT

We've worked with cisco TAC yesterday and we're facing CSCur00288 : 8.0.100.0 client is shown with "ip address unknown" and "dhcp required".

This bug will be resolved in WLC 8.1 which is expected to be released by the end of this year.

Théo

This bug also affects local

Sauchanka — Thu, 20 Nov 2014 22:10:15 GMT

This bug also affects local mode APs.

We've just faced with the same issue with WLC 5508 and APs working in local mode.

Thanks for the update8.0MR1

Rasika Nayanajith — Thu, 20 Nov 2014 22:53:39 GMT

Thanks for the update

8.0MR1 would be a Christmas gift from Cisco to the customer running 8.0.100.0

Rasika