The LoadMaster has the ability to use Simple Network Management Protocol (SNMP) on its management interface to monitor certain Management Information Bases (MIBs). These MIBs can be found here. To download the MIBs, navigate here.
The only prerequisite for allowing SNMP monitoring on your LoadMaster is that UDP port 162 is open between your SNMP monitoring tool and the LoadMaster.
First, enable SNMP by navigating to System Configuration > Logging Options > SNMP Options > Enable SNMP.
Decide whether or not to use SNMPv3. You will notice that four extra fields are present when enabling SNMPv3: Username, Password, Authentication Protocol, and Privacy Protocol. The most appropriate protocols can be discovered from the SNMP manager settings.
Next, decide what SNMP clients will be able to access your LoadMaster and what Community String will be used.
Your contact field should be populated with the email address of your LoadMaster administrator. If you have multiple administrators, a distribution group should be used.
You can configure the Location string with a friendly location name to inform you of which LoadMaster should be observed. For example, you may want to populate the IP address of the LoadMaster in question.
SNMP Traps can be enabled for SNMP monitoring. Options to configure SNMP Traps include:
- Whether or not Traps are sent from the HA Shared IP (if HA is configured)
- SNMP Trap Sink 1
- SNMP Trap Sink 2
SNMP Trap Sink 1 can be populated with the IP of a manager that runs either SNMPv1 or SNMPv2, while SNMPv2 should only be populated with devices that are SNMPv2 managers. The reason for this is that SNMPv2 is backwards compatible, while SNMPv1 is not able to decipher SNMPv2 messages.
When using 360 Vision, you cannot use SNMPv3. This is to reduce overhead when monitoring your LoadMaster with 360 Vision. There are no current plans to integrate SNMPv3 with 360 Vision.