lwapp associating with controller but clients not leasing IP addresses

Unanswered Question
Feb 17th, 2010
User Badges:

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
braggb001 Wed, 02/17/2010 - 09:51
User Badges:

A few questions:

  1. Did you set the gateway and subnet mask on the Controller Management Interface?
  2. If so, is it correct?
  3. Can you ping the controllers Management IP from the same subnet?
  4. Do you have a firewall or ACL blocking anything on that subnet?
Percy Thutoetsile Thu, 02/18/2010 - 00:04
User Badges:

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 Wed, 02/17/2010 - 21:10
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, October 2015

Can you post your config ?

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode