OEAP 600

[spkolla]

Hi There

We are working on a solution for deploying OEAP 600 using DMZ WLC 2504. We have a production WLC 5508. The WLC5508 is anchor to WLC2504 for mobile devices.

The DMZ WLC 2504 is configured for OEAP 600 to connect and it is connected properly and able to extend WLAN.

We have WLAN for guests in DMZ WLC2504 with internal DHCP.

This networks working fine when we connect through OEAP600.

We have a corporate network WLAN, which authenticates with Radius server and DHCP also released from the Internal servers. We have established the firewall rules for the DMZ management interface to talk to the Radius server and DHCP Servers.

When we publich the corporate LAN through OEAP 600, we are abel to seel WLAN. But the DHCP is not assigning from the corporate LAN.

the problem here is the DHCP is not assigned to the clients. How to solve this issue.

[Richard Atkin]

Are you anchoring the Corporate WLAN from the OEAP to the internal 5508 or leaving them out in the DMZ?

If you monitor the Policy Manager Status of a Client, or perform a "debug client " on the CLI, what output do you get? We need to establish if the problem lays with tunnelling, authentication, dhcp, or the switching infrastructure.

Sent from Cisco Technical Support iPad App

[Scott Fella]

You need to verify the WLAN anchoring. Its what considered as a reverse anchor. So you need to make sure you have the 2504 WLAN anchor to the 5508 and the SSID on the 5508 anchored to itself. It's the reverse of how your doing the guest WLAN.

You can also test the setup is wrong if you create a dhcp scope on the 2504 for the WLAN for the OEAP600. If devices pull an IP address from the anchor 2504, then the WLAN isn't being tunneled to your internal 5508.

Sent from Cisco Technical Support iPhone App