Control Path Down

Answered Question
Oct 23rd, 2009

Hi,

The control path between our Guest Anchor WLC4402 and one of our foreign controllers is down all other control paths are up as are all of the data paths. The Anchor is behind a firewall the configuration of which must be ok due to the other WLCs data and control paths being up. Can anyone tell me how I check that the WLCs are reciving each others mobility packets e.g. via debug.

Many Thanks

Scott

Correct Answer by weterry about 7 years 3 months ago

debug mobility keepalive

you should see a "data path" keepalive every 10 seconds and a "control path" keepalive every 30 seconds.

I believe the Control Path will be a message about port 16666.

Run this from all controllers and verify who is sending the keepalive (I believe it is lowest mac address).

Bottom line is that if you see one controller send it, and the other doesn't recieve it, that sounds like it is getting lost along the way.

I've seen configuration before where if the DMZ Controller is the initiator of the keepalive (high mac address?), then the path may be down. It had to do with the firewall allowing the session from Trust to DMZ (and the return traffic), but not allowing the DMZ to initiate the session.

You could try an mping from both controllers and see if you can get a response....?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Correct Answer
weterry Fri, 10/23/2009 - 19:54

debug mobility keepalive

you should see a "data path" keepalive every 10 seconds and a "control path" keepalive every 30 seconds.

I believe the Control Path will be a message about port 16666.

Run this from all controllers and verify who is sending the keepalive (I believe it is lowest mac address).

Bottom line is that if you see one controller send it, and the other doesn't recieve it, that sounds like it is getting lost along the way.

I've seen configuration before where if the DMZ Controller is the initiator of the keepalive (high mac address?), then the path may be down. It had to do with the firewall allowing the session from Trust to DMZ (and the return traffic), but not allowing the DMZ to initiate the session.

You could try an mping from both controllers and see if you can get a response....?

scottwilliamson Mon, 10/26/2009 - 06:52

Hi Wesley,

Thanks for that you've helped me realise what the problem is: The Anchor was not sending udp port 16666 to the problem controller, it occured to me that the Service Port address of the Anchor was on the same subnet as the Manager interfaces of the controller it could not establish the EoIP tunnel with - I've changed the Service Port address and everything now works.

Thank you,

Scott

Actions

This Discussion

 

 

Trending Topics - Security & Network