lwapp associating with controller but clients not leasing IP addresses

Percy Thutoetsile · ‎02-17-2010

i have upgraded wism controllers to software version 6.0. controller 2 is working fine - i can ping, telnet to it from anywhere on my network. on the other hand controller 1 is booting fine and lwapp are associating with the controller but are failing to lease IP addresses from the dhcp server. i can not ping the controller from the network and the controller is also failing to ping the lwapp.

--ronnie

braggb001 · ‎02-17-2010

A few questions:

Did you set the gateway and subnet mask on the Controller Management Interface?
If so, is it correct?
Can you ping the controllers Management IP from the same subnet?
Do you have a firewall or ACL blocking anything on that subnet?

Percy Thutoetsile · ‎02-18-2010

hi,

[wism on catalyst 6509]

1. the gateway and the management interface are all set correctly. i can ping other subnets on my network from this controller, but i can not ping the dhcp server from the controller. i cannot also ping the default gateway of the subnet where the dhcp server is stting.

2. i can ping the controller from the core switch

3. from the controller i can ping AP that are associated on the second controller, but cannot ping APs associated with this controller

4. no internal firewall, no ACLs blocking traffic to the subnet.

George Stefanick · ‎02-17-2010

Can you post your config ?

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

Percy Thutoetsile · ‎02-17-2010

hi,

here is the config file on the controller

--ronnie