We've been having fun with an issue (TAC case SR 609658193) we discovered this year that others might find interesting. There's not much feedback from Cisco on this one at this point.
Our setup is with ~600 Aruba APs, cisco 3560 PoE access, 3750 & 6506 cores, 4 CAS (3 inline for wireless, 1 oob for wired) still running 4.1.2.1 (we stalled at this rev.) and BIND 9 for DHCP. We've discovered that any Apple OS X client (10.4, 10.5, iphones, etc.) that roams to a new address space (we allocate a /23 for most of our buildings) and requests a new address will not get the new DHCP ACK and fails to pass through the inline CAS. We have found a workaround that works most of the time, which is to have the resident insert a unique value (their student ID number) in the DHCP Client ID field. The DHCP discover is received properly from the client, DHCP offer is made from the server (with new address from proper pool), the DCHP request is passed back from the client, but the DHCP ACK appears to be dropped by the CAS. I'm curious if others have the same setup as ours and might be seeing similar behavior. We've pretty much resolved to take our wireless traffic off of the CCA product (4.5 requires Cisco wireless controller to do out of band) and have put a new Aruba solution in place. Ben Price Manager, Residential Network Services [EMAIL PROTECTED] (805) 893-4747
