Adding (dynamic) interfaces to WLC 2504 causes loss of network

[3moloz123]

I'm trying to add a new dynamic interface, that I will tie a specific WLAN to so that clients on that WLAN is in the correct vlan. After adding it I loose connectivity both to the main management address (10.99.0.60) and to the ip address of the dynamic interface (10.99.12.4). In fact, the dynamic interface address responds and prompts me to login, but after doing so all I get is a blank page. Here's the two interfaces pulled from the CLI - what am I doing wrong?

And oh, not adding an IP to the dynamic interface makes it impossible to use within a WLAN.

Interface Name................................... management

MAC Address...................................... c0:8c:60:c7:99:00

IP Address....................................... 10.99.0.60

IP Netmask....................................... 255.255.255.0

IP Gateway....................................... 10.99.0.1

External NAT IP State............................ Disabled

External NAT IP Address.......................... 0.0.0.0

VLAN............................................. 31        

Quarantine-vlan.................................. 0

Active Physical Port............................. 1         

Primary Physical Port............................ 1         

Backup Physical Port............................. Unconfigured

DHCP Proxy Mode.................................. Global

Primary DHCP Server.............................. 10.99.0.1

Secondary DHCP Server............................ Unconfigured

DHCP Option 82................................... Disabled

IPv4 ACL......................................... Unconfigured

mDNS Profile Name................................ Unconfigured

AP Manager....................................... Yes

Guest Interface.................................. No

L2 Multicast..................................... Enabled

Interface Name................................... lan

MAC Address...................................... c0:8c:60:c7:99:04

IP Address....................................... 10.99.12.4

IP Netmask....................................... 255.255.252.0

IP Gateway....................................... 10.99.12.1

External NAT IP State............................ Disabled

External NAT IP Address.......................... 0.0.0.0

VLAN............................................. 33        

Quarantine-vlan.................................. 0

NAS-Identifier................................... mob-wlc

Active Physical Port............................. 1         

Primary Physical Port............................ 1         

Backup Physical Port............................. Unconfigured

DHCP Proxy Mode.................................. Global

Primary DHCP Server.............................. Unconfigured

Secondary DHCP Server............................ Unconfigured

DHCP Option 82................................... Disabled

IPv4 ACL......................................... Unconfigured

mDNS Profile Name................................ Unconfigured

AP Manager....................................... No

Guest Interface.................................. No

[aaronniiranen]

Update, I managed to get it working after all. Make sure LAG is enabled and it has basic connectivity and LAG is up with allowed VLAN's that you wan to permit for your WLC. You should also always use 2 gig port setup when using LAG. Having LAG with only 1 port is somewhat pointless after all. 

Also if not using Cisco switches dont allow native VLAN 1 over the LAG since CDP can cause issues.

If this WLC is on DMZ make sure you have proxy ARP enabled.

cheers!

[Saravanan Lakshmanan]

wlc code?

for test,

try using /16 for management and keep the remaining config.

or use multiple /24 for dyn.int along with interface group.

or use different mask than /252 for dyn.int.

[jhoude660]

Was there ever a resolution to this. I seen the same issue on two seperate controllers.