Hey Guys, I just solved, just for record, thats is the config that works for me:
DMZ: Guest LAN NAME: 90_99 (Ingress NONE, Egress 99) Anchor self. WLC1: Guest LAN NAME: 90_99 (Ingress 90, Egress Management) Anchor DMZ. So, the trick for me is to setup the None as ingress in the DMZ Controller. The GUI don't allow me. I need to setup it in the CLI, using this command: config guest-lan ingress-interface 1 none Thats work fine! I can authenticate and get access to the SW2 Web interface. Best Regards, Yuri From: [email protected] To: [email protected] Subject: Guest LAN + Anchor Date: Wed, 27 Apr 2011 00:22:24 -0300 Hi guys, Work today in the Guest Lan + Anchor. I think I'm doing some mistake. I'm using the two 4402 from the Proctorlabs, where the first one is called DMZ, the seccond one is called WLC1. I create a Guest Lan in the WLC1 with ingress vlan90 and egress management and anchor it to DMZ. In the DMZ I create another Guest Lan, same name, with ingress 90 and egress 99. So when I setup the "auto-anchor" the ssid comes disable and I saw this message in the console: Request failed - Ingress interface should be cleared from guest LAN for mobility anchor wlc. Did I some mistake? Anyone work in that? Best Regards, Yuri
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
