I took a look at your buildings. Both buildings have the same issue below. The AP information is specific to the
KAHALA, KAIMUKI building.
This is what the the firewall sees:
Code: Select all
Device ID Local Intrfce Holdtme Capability Platform Port ID
AP4c4e.35b3.e439 Fas 0 156 T B I AIR-LAP10 Gig 0
APbc16.6537.49de Gig 0 129 T B AP802GN-A Gig 0
AP10f3.119a.259c Fas 0 168 T B I AIR-LAP10 Gig 0
AP10f3.119a.259c Fas 0 121 T B I AIR-LAP10 Gig 0
AP10f3.119a.27f9 Fas 0 168 T B I AIR-LAP10 Gig 0
Notice how
AP10f3.119a.259c shows up twice on port Fas 0 (FE 0). Normally this would indicate a network loop.
On closer examination we can see that
AP10f3.119a.259c is showing up on two different IP addresses:
Code: Select all
Device ID: AP10f3.119a.259c
Entry address(es):
IP address: 192.168.108.35
IPv6 address: FE80::12F3:11FF:FE9A:259C (link-local)
Platform: cisco AIR-LAP1041N-A-K9, Capabilities: Trans-Bridge Source-Route-Bridge IGMP
....
Device ID: AP10f3.119a.259c
Entry address(es):
IP address: 192.168.108.34
IPv6 address: FE80::12F3:11FF:FE9A:254F (link-local)
Platform: cisco AIR-LAP1041N-A-K9, Capabilities: Trans-Bridge Source-Route-Bridge IGMP
...
But when you look at the arp table, You can see that your missing AP is using one of those IP addresses:
Code: Select all
Internet 192.168.108.34 0 10f3.119a.254f ARPA Vlan1
Internet 192.168.108.35 0 10f3.119a.259c ARPA Vlan1
I cannot say whether this is a network, firewall, or an AP issue. What I suggest is that you move that AP and connect it directly to the firewall and see if your AP shows up after it boots up and starts working. You might have to wait for the firewall to "check in" after the AP boots up.
If it starts working and shows up in TM, it is a network issue. If not, it's still up in the air whether it is the firewall (less likely since other APs are working properly) or an issue with the AP.