Cannot find debug reference 7.0.116.0

[ewood2624]

We have clients that are dropping off the wireless network at strange times.  I ran a client debug but cannot find any references to the last line.

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP processing DHCP ACK (5)

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP   xid: 0x80227682 (2149742210), secs: 0, flags: 0

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP   chaddr: 00:1a:6b:a8:a5:35

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP   ciaddr: 0.0.0.0,  yiaddr: 10.10.204.159

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP   siaddr: 0.0.0.0,  giaddr: 10.10.204.2

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.506: 00:1a:6b:a8:a5:35 DHCP   server id: 10.30.20.9  rcvd server id: 10.30.20.9

*DHCP Proxy DTL Recv Task: Sep 26 10:27:33.507: 00:1a:6b:a8:a5:35 DHCP successfully bridged packet to STA

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 10.10.204.159 RUN (20) State Update from Mobility-Complete to Mobility-Incomplete

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 Clearing Address 10.10.204.159 on mobile

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 apfMsRunStateDec

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 10.10.204.159 RUN (20) Change state to DHCP_REQD (7) last state RUN (20)

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 apfMmProcessDeleteMobile (apf_mm.c:548) Expiring Mobile!

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 apfMsExpireMobileStation (apf_ms.c:5009) Changing state for mobile 00:1a:6b:a8:a5:35 on AP 00:21:1b:67:70:60 from Associated to Disassociated

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 apfMsAssoStateDec

*apfReceiveTask: Sep 26 10:28:03.117: 00:1a:6b:a8:a5:35 apfMsExpireMobileStation (apf_ms.c:5132) Changing state for mobile 00:1a:6b:a8:a5:35 on AP 00:21:1b:67:70:60 from Disassociated to Idle

*apfReceiveTask: Sep 26 10:28:03.118: 00:1a:6b:a8:a5:35 0.0.0.0 DHCP_REQD (7) Deleted mobile LWAPP rule on AP [00:21:1b:67:70:60]

*apfReceiveTask: Sep 26 10:28:03.118: 00:1a:6b:a8:a5:35 apfMs1xStateDec

*apfReceiveTask: Sep 26 10:28:03.118: 00:1a:6b:a8:a5:35 Deleting mobile on AP 00:21:1b:67:70:60(0)

*pemReceiveTask: Sep 26 10:28:03.125: 00:1a:6b:a8:a5:35 0.0.0.0 Removed NPU entry.

*apfReceiveTask: Sep 26 10:30:14.708: invalid interface name (vlan 208) in mscb!!!

When I see that message on the debugs, the client will not authenticate for anywhere from 10-60 seconds.  After that, they work correctly and receive DHCP as they are supposed to without any problems.  I've combed through most WLC config guides, user guides, CSC discussions, and the WLC troubleshooting book and cannot find any reference.  Any ideas?

[ewood2624]

Here's another weird debug message I cannot find reference to:

*pemReceiveTask: Sep 26 11:21:40.349: 00:1a:6b:a8:a5:35 10.10.204.159 Removed NPU entry.

*emWeb: Sep 26 11:23:11.166: Created WARP Capabilities IE (length 12) for WLAN WLESS-ACS

When did the WLC get WARP capabilities?

[Stephen Rodriguez]

in the first debug, are you using AAA override with options 64/65/81?  Could be a bad packet trying to set the VLAN/Interface.

as for WARP Capabilities, it happend right after Scotty(or Jordy if you a TNG fan) fixed the plasma couplers, to allow the proper flow into the warp core.

that message is per-usual, I don't remember what it means, but it should be fine.

HTH,
Steve

----------------------------------------------------------------------------------------------------------

Please remember to rate helpful posts or to mark the quesiton as answered so that it can be found later.

[wififofum]

I believe WARP refers to information elements - IEs in the beacon frames. These change whenever you modify WLAN properties (Security/DTIM values, etc.). Probably occurs if you change data rates as well.

Here's your debug reference. Applies to all code versions:

"Copy the output and call the TAC" ; p

Sent from Cisco Technical Support iPad App