In that case I'd try troubleshooting connectivity and SNMP from the airwave server to the switches first, to rule that out before digging into the airwave application.
If you log into the underyling OS of your airwave server (either via console or ssh) as the root user, you'll have a standard CentOS linux system. First see if you can ping the swtiches. If that works on the ones that airwave can't see, I'd next move on to doing a manual SNMP query with the snmpwalk command. If you haven't used it before, try a query like this:
snmpwalk -v 2c -c <your community string> <switch IP address> sysuptimeinstance
filling in your SNMP community string and the IP of the switch you're testing. If it works, it will give you the uptime of the switch, looking something like this:
[root@amp mercury]# snmpwalk -v 2c -c public switch sysuptimeinstance
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3231907400) 374 days, 1:31:14.00
If either of those fail, you have either a connectivity issue (routing, intermediate firewall, etc) or an SNMP agent issue (does the SNMP agent have it's own indepdent ACL separate from the IP layer ACLs?) that you need to address before airwave will be able to help. If they both work, you're looking at something in the actual airwave application itself, and I'd reccomend opening a TAC case.