So,
It looks like you have the mesh point (I assume), named "AP277-MeshPoint" configured to fail over to a second controller, and that is what it is doing for some connectivity reason (Missed Heartbeats). The question is, are controllers .12 and .13 in a master/local topology, because it seems when the the mesh commands are run on the "current" controller, it does not know about that AP. My general advice, if this data is correct, would be to remove the failover mechanism first ( remove the backup lms-ip) and troubleshoot the mesh on a single controller first.
show ap debug system-status ap-name "AP277-MeshPoint"
Reboot Information
------------------
(none found)
------------
Rebootstrap Information
-----------------------
Date Time Reason (Latest 10)
--------------------------------------
2016-07-25 14:24:42 Switching to LMS 10.8.10.12: Missed heartbeats: Last Sequence Generated=12979 Sent=0 Rcvd=12899. Last Ctrl message: KEEPALIVE len=45 dest=10.8.10.12 tries=1 seq=12
2016-07-25 14:25:24 Mesh point up on 10.8.10.12 (call 5360)
2016-07-25 14:33:25 Mesh point up on 10.8.10.13 (call 5360)
2016-07-25 14:46:35 Mesh point up on 10.8.10.12 (call 5360)
2016-07-25 15:07:20 Switching to LMS 10.8.10.12: Missed heartbeats: Last Sequence Generated=15505 Sent=0 Rcvd=15425. Last Ctrl message: KEEPALIVE len=45 dest=10.8.10.12 tries=1 seq=12
2016-07-25 15:07:34 Mesh point up on 10.8.10.12 (call 5360)
2016-07-25 15:16:02 Mesh point up on 10.8.10.13 (call 5360)
2016-07-25 15:29:40 Mesh point up on 10.8.10.12 (call 5360)
2016-07-25 15:58:40 Mesh point up on 10.8.10.13 (call 5360)
2016-07-25 16:11:31 Mesh point up on 10.8.10.12 (call 5360)
show ap mesh topology
Total APs :0
(R): Recovery AP. (N): 11N Enabled. (AC): 11AC Enabled. For Portals 'Uplink Age' equals uptime.
show ap mesh neighbors ap-name "AP277-MeshPoint"
No AP found with ap_name AP277-MeshPoint
show ap mesh debug current-cluster ap-name "AP277-MeshPoint"
No AP found with ap_name AP277-MeshPoint
show ap mesh debug provisioned-clusters ap-name "AP277-MeshPoint"
No AP found with ap_name AP277-MeshPoint
show ap mesh debug counters ap-name "AP277-MeshPoint"
No AP found with ap_name AP277-MeshPoint
show ap mesh debug forwarding-table ap-name "AP277-MeshPoint"
AP ap-name "AP277-MeshPoint" not found. Please make sure it is valid by issuing 'show ap bss-table'
show ap mesh debug meshd-log ap-name "AP277-MeshPoint"
No AP found with ap_name AP277-MeshPoint
show ap mesh debug hostapd-log ap-name "AP277-MeshPoint"
No AP found with ap_name AP277-MeshPoint
show ap debug crypto history ap-name "AP277-MeshPoint"