Nancy, Unless I missed something in a later feature release, Wireless requires IN-band.
Also, I would not run the VLAN for the LWAPP access points through the CAS. You want your AP's to be on an unmanaged network. Think of it this way. Your doubling the traffic through your CAS because all the traffic has to traverse the CAS to get to the Wireless controller, and then sent back to the CAS to have authentication/posture. ( Client -> AP -> CAS -> WirelessController -> CAS -> Internet ) Another side affect is that you would have to create exclusions (Filters) for all the Access Points in the CAM/CAS so the AP's could communicate with the Wireless Controller. I would trunk a VLAN into the Wireless controller, and run that VLAN thru CAS. Then you have your SSID dump all your traffic on this VLAN. This is how I've setup CCA before. You can even get fancy and apply different VLAN's to different User accounts, using the same SSID. I'm sure Lee will chime in with a similar answer. Mike On Tue, Oct 7, 2008 at 4:57 PM, Nancy Watson <[EMAIL PROTECTED]> wrote: > We are deploying the Cisco NAC, inband, real-ip gateway to replace our > Bluesocket solution for authentication. The plan is to use the HA-CAS as > the dhcp servers and configuring upwards in the 100's of vlans on the box > for our LWAPP access points. > Does anyone know of any issues using the NAC servers as the dhcp server > versus an external dhcp server? Is there issues with handling large numbers > of vlans? > > We have 2 WiSM centrally located and will be moving to OOB and posture > assessment in the future. > > Thanks, > Nancy > > -- > <><><><><><><><><><><><><><><><><><><><><><><><><><> > Nancy Watson CNS Network Services > Sr. Network Engineer 352-273-1057 > https://net-services.ufl.edu 352-392-5579 x167 > <><><><><><><><><><><><><><><><><><><><><><><><><><> >
