Yes, you can add all of this info. The AP is the only element that has an SNMP engine and it polls the SUs for the SU RSSI and associated values. If you perform an SNMP walk on the AP, you'll see the SU table. For SU specific info, I created some functions to get all of the pertinent info for the SU when you hover over the SU in the MAP. To do this, I use the three custom fields in the SU settings.
Field 1: Customer name
Field 2: AP IP address
Field 3: SU number
My functions then use field 2 and 3 to get the SU X data from AP Y
On the AP-SU links in the map, we add the following OIDs to the link Appearance and set the Device IP to the APs IP. Currently, there isn't a way to use the attached SU custom field 3 as you can only point to one device IP and that must be the AP. I requested an enhancement to allow more options in using other device IPs/fields but I'm still waiting for the enhancement. Thus, you must manually add the SU ID to the OID. In the example below, the RSSI info will be polled for SU 8. This will add more network traffic as its polled every 10 seconds. If you want to poll less frequently, then you don't want to add it to a link (I requested a configurable parameter for link polling also...still waiting):
AP RSSI: [oid("iso.org.dod.internet.private.enterprises.trango.tbw.m5830sap.su.suInfoTable.suInfoEntry.suRSSIFromSU.8")]
SU RSSI: [oid("iso.org.dod.internet.private.enterprises.trango.tbw.m5830sap.su.suInfoTable.suInfoEntry.suRSSIFromAP.8")]
For temp, you can plot the AP temp but the Atlas Foxes don't have temp sensors. You can plot AP ingress/egress traffic for the wireless or ether interfaces, or for each SU. We plot SU throughput for SUs that we use for backhauls to satellite towers. I asked Trango for the max SNMP requests per second/min but they didn't have this info
So we don't poll everything as we are not sure what the limit is for CPU util and SNMP.
Hope that helps. If you need more info, let me know. You have my email address