This article consists of:
- SNMP Setup
- MIB Configuration
- KEMP 360 Vision
- SNMP Setup
SNMP (Simple Network Management Protocol) can be used to monitor the LoadMaster unit, for example, CPU load and statistics. To enable SNMP, follow the steps below in the LoadMaster Web User Interface (WUI):
- In the main menu, select System Configuration > Logging Options > SNMP Options.
- Select Enable SNMP.
- Enter the IP address or hostname of the SNMP server in the SNMP Clients text box.
- Add the Community String. This can be set to public if open to all, or to a private string name.
- In the Contact text box, enter the username of the contact person who has the management information, for example, KEMP Support.
- Enter the device Location, for example, Ireland.
- Choose whether to Enable SNMP Traps or not. When enabled, this displays two additional text boxes: SNMP Trap Sink1 and SNMP Trap Sink2. SNMP Trap Sink1 is related to SNMP v1 and SNMP Trap Sink2 is related to SNMPv2. These options allow you to specify a list of hosts to which an SNMPv1 or SNMPv2 trap is sent when a trap is created.
2. MIB Configuration
To monitor your LoadMaster, you can configure the Simple Network Management Protocol (SNMP) parameters.
Ensure that SNMP is enabled on the LoadMaster.
Navigate to: System Configuration > Logging Options > SNMP Options and ensure that Enable SNMP is selected.
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.
The LoadMaster has custom Management Information Bases (MIBs) which are available for download here.
You can import these to your preferred monitoring tool. Each major revision of firmware has specific Object Identifiers (OIDs), so be sure you are using the correct MIB bundle for the firmware you are running.
After importing the MIBs, there are a few groups of OIDs. The grouping of OIDs under the ipvs folder provides information concerning Layer 4 Virtual Services.
Alternateively, if you have configured Layer 7 Virtual Services, you should look through the b100 grouped OIDs.
If you want to monitor the general properties and settings of the LoadMaster, you can view the OIDs within the b100-0 grouping.
Almost any piece of information can be pulled from the LoadMaster using SNMP. The key is to determine which OID(s) you want to track.
Four extra fields are present when you enable SNMPv3: Username, Password, Authentication Protocol, and Privacy Protocol. You can determine the most appropriate protocols from the SNMP manager settings.
You can decide what SNMP clients are able to access your LoadMaster and what Community String is used.
Your Contact field should be populated with the email address of your LoadMaster administrator. If you have multiple administrators, you should use a distribution group.
You can configure the Location string with a friendly location name to inform you 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
You can populate SNMP Trap Sink 1 with the IP address of a manager that runs either SNMPv1 or SNMPv2, while you should only populate SNMPv2 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.
3. KEMP 360 Vision
When using KEMP 360 Vision, you cannot use SNMPv3. This is to reduce overhead when monitoring your LoadMaster with KEMP 360 Vision. There are no current plans to integrate SNMPv3 with KEMP 360 Vision.