Unable to ping WLC if I add a dynamic interface that has a different subnet

[Scott Fella]

I have a WLC2006 that the management and ap-manager is in a 10.5.x.x /24. I also created a guest wireless interface in a different subnet but also a /24. I then created another interface for internal users on an existing subnet with a /20. I can then get to the WLC via https but will not be able to ping the WLC. If I cange the mask to a /24, I am able to https and ping the WLC also the users have no problems when associated to that interface on a perticular ssid. Just wondering if anyone has seen this. WLC is running on the latest code 4.0...

[ebreniz]

The Management interface and the AP manger interface should be in the same subnet

[Scott Fella]

They are in the same subnet. But if I create any dynamic interface that is not 255.255.255.0, I will not be able to pind the management interface. For example.... Management and ap-manager is in the same subnet with a /24 mask. I have a dynamic interface on another subnet with a /24 mask also. I created a dynamic interface that is in a subnet with a /20 mask.. unable to ping. When I change the mask to a /24 which is not the same as the subnet it is one, I'm able to ping and users are able to access the network.

Just wondering if anyone has seen this before and what they did.