how to troubleshoot EOIP tunnel between the foreign and the DMZ guest controllers

[atifali.zaidi1]

Hello Experts,

if the control path is UP between the controllers and the control traffic is down , then do the below mentioned factors come into place ?

controllers model ?

controllers OS version ?

virtual IP should be the same ---- thats a known fact 

IP protocol 16666/16667 and IP protocol 97 ports should be opened on the firewall ----- thats a known fact 

also what troubleshooting commands could be run on both the controllers to troubleshot the data path down issue ?

debug mobility peer-ip <ip address>

debug mobility packet enable 

am i right ?

[Scott Fella]

Here is a link to help you troubleshoot mobility:
https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/111736-guest-troubleshoot-00.html#topic2

I would think that you don’t have IP97 allowed through the FW.

[Saravanan Lakshmanan]

Depends on what we're debugging and its scope:-

https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/107458-wga-faq.html?referring_site=bodynav

https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-5/command/reference/cr75/cr75_chapter_01001.pdf
debug mobility {ap-list | config |directory |dtls |handoff |keep-alive | multicast | oracle |packet |peer-ip
IP-address | pmk | pmtu-discovery | redha} {enable | disable}

(Generally, start with config/handoff/keep-alive/packet)

show mobility statistics and other relevant show cmds per above link.