Interesting conflict with DHCP and v4.2.99 and 4.2.130

Unanswered Question

I was running 4.2.130 on my inside controllers, and hadn't yet upgraded my Guest/DMZ Anchor controller to 130 yet, it was running 4.2.99.

I upgraded the ER to .112 as recommended and then the controller to 4.2.130 and DHCP responses were then getting DROPPED by the inside controllers.

The debug output showed this

(look at the last line)

Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb Reassociation received from mobile o n AP 00:1e:13:c7:84:20 Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb STA - rates (8): 18 150 24 36 48 72

96 108 0 0 0 0 0 0 0 0

Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb STA - rates (9): 18 150 24 36 48 72

96 108 12 0 0 0 0 0 0 0

Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb 0.0.0.0 START (0) Deleted mobile LWA PP rule on AP [00:1e:13:84:66:80] Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb Updated location for station old AP 00:00:00:00:00:00-0, new AP 00:1e:13:c7:84:20-0 Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb 0.0.0.0 START (0) Initializing polic y Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb 0.0.0.0 START (0) Change state to AU THCHECK (2) last state AUTHCHECK (2) Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb 0.0.0.0 AUTHCHECK (2) Change state t o L2AUTHCOMPLETE (4) last state L2AUTHCOMPLETE (4) Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb 0.0.0.0 L2AUTHCOMPLETE (4) Plumbed m obile LWAPP rule on AP 00:1e:13:c7:84:20 Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb 0.0.0.0 L2AUTHCOMPLETE (4) Change st ate to DHCP_REQD (7) last state DHCP_REQD (7) Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb apfPemAddUser2 (apf_policy.c:209) Ch anging state for mobile 00:1a:73:9d:96:cb on AP 00:1e:13:c7:84:20 from Probe to Associated Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb Scheduling deletion of Mobile Statio

n: (callerId: 49) in 1800 seconds

Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb Sending Assoc Response to station on BSSID 00:1e:13:c7:84:20 (status 0) Wed Jul 9 10:09:56 2008: 00:1a:73:9d:96:cb apfProcessAssocReq (apf_80211.c:3853

) Changing state for mobile 00:1a:73:9d:96:cb on AP 00:1e:13:c7:84:20 from Assoc iated to Associated Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb 0.0.0.0 DHCP_REQD (7) State Update f rom Mobility-Incomplete to Mobility-Complete, mobility role=ExpForeign Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb 0.0.0.0 DHCP_REQD (7) Change state t o RUN (20) last state RUN (20) Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb 0.0.0.0 RUN (20) Reached PLUMBFASTPA

TH: from line 4013

Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb 0.0.0.0 RUN (20) Adding Fast Path ru le

type = Airespace AP Client

on AP 00:1e:13:c7:84:20, slot 0, interface = 1, QOS = 0

ACL Id = 255, Jumbo Frames = NO, 802.1P = 0, DSCP = 0, TokenID = 5006 Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb 0.0.0.0 RUN (20) Successfully plumbe d mobile rule (ACL ID 255) Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb Set bi-dir guest tunnel for 00:1a:73 :9d:96:cb as in Export Foreign role Wed Jul 9 10:09:58 2008: 00:1a:73:9d:96:cb 0.0.0.0 Added NPU entry of type 1 Wed Jul 9 10:09:59 2008: 00:1a:73:9d:96:cb DHCP received op BOOTREPLY (2) (len 308, port 1, encap 0xec00) Wed Jul 9 10:09:59 2008: 00:1a:73:9d:96:cb DHCP dropping REPLY from Export-Fore ign STA Wed Jul 9 10:10:03 2008: 00:1a:73:9d:96:cb DHCP received op BOOTREPLY (2) (len 308, port 1, encap 0xec00) Wed Jul 9 10:10:03 2008: 00:1a:73:9d:96:cb DHCP dropping REPLY from Export-Fore ign STA Wed Jul 9 10:10:10 2008: 00:1a:73:9d:96:cb DHCP received op BOOTREPLY (2) (len 308, port 1, encap 0xec00) Wed Jul 9 10:10:10 2008: 00:1a:73:9d:96:cb DHCP dropping REPLY from Export-Fore ign STA Wed Jul 9 10:10:26 2008: 00:1a:73:9d:96:cb DHCP received op BOOTREPLY (2) (len 308, port 1, encap 0xec00) Wed Jul 9 10:10:26 2008: 00:1a:73:9d:96:cb DHCP dropping REPLY from Export-Fore ign STA


In order to get things working again, I had to put my anchor back on 4.2.99.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dennischolmes Wed, 07/09/2008 - 13:28
User Badges:
  • Gold, 750 points or more

Did you try diasbling dhcp by proxy?


config dhcp proxy disable

dennischolmes Wed, 07/09/2008 - 13:56
User Badges:
  • Gold, 750 points or more

You have to do that from the cli only.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode