Documentation forIpMonitor
Effective December 31, 2024, IpMonitor will reach its end of life and will no longer be available or supported. If you liked IpMonitor, consider trying another SolarWinds product.

Create the SNMPv3 credentials using the New Device and New Monitor wizards

You can create SNMPv3 credentials for a device or monitor using the new device or new monitor wizards. After you create a credential, you can modify it using the Credential List option in the Configuration tab.

The credentials you provide must have the required permissions to access the monitored resources. For example, if you intend to monitor an administrative share (such as C$), the credential you supply must be a member of the Windows Administrators group.

Create SNMPv3 credentials using the New Device Wizard

  1. Log in to ipMonitor.
  2. Click Devices.
  3. Click All Managed Devices.
  4. Click the Add > Add New Device.

  5. Enter the device details.

    1. Enter an IP address or hostname. The default IP address is 127.0.0.1.

    2. Click the SNMP Version drop-down menu and select SNMP Version 3.

    3. (Optional) Under SNMPv3 Credentials, click Select and select a credential.

  6. Click Next.

    ipMonitor scans and locates a new device.

  7. Click View Existing Results.

  8. Review the device summary. Click Modify Selections to change the device list.

  9. Expand Advanced.

  10. Review the naming convention and separator options and make any changes as needed.

  11. Click Create.

Create SNMPv3 credentials using the New Monitor Wizard

  1. Log in to ipMonitor.
  2. Click Devices.
  3. Click All Managed Devices.
  4. Click the target device.
  5. Click Add > Add New Monitor.
  6. Scroll down and click SNMP.

  7. Complete the Identification settings.

    1. Enter a monitor name using up to 64 characters. This name will display in the monitors list, log pages, and reports.

      You can change this name later without impacting your data.
    2. Select Enabled to allow the monitor to test the specified resource using the test parameters you provide below.
    3. Select the Store Monitor Statistics checkbox to enable ipMonitor to record the results of the monitoring activity in the recent activity and historical reports.  

  8. Complete the Test Parameters fields and selections.

    1. Enter an IP address for fully-qualified domain name of the device, server, or sensor you want to monitor.

      For example:

      • 10.10.30.11
      • www.example.com
    2. Enter the UDP port number where the target server responds. A default value is entered depending on the service you are monitoring. The service and corresponding default ports include the following:
      ServicePort
      DNS53
      KERBEROS88
      LDAP389
      RADIUS1812
      SNMP161

    3. Enter the Object Identifier (OID) that identifies the path to the value ipMonitor retrieves for analysis. ipMonitor sends a standard Get Protocol Data Unit (SNMP Get command), asking the SNMP agent to send back the value for this particular MIB instance or unique OID string.

      If you are using a single SNMP monitor, the OID is hard coded to retrieve the 1.3.6.1.2.1.1.3.0 (sysUpTime) OID. This OID represents the time since the network management portion of the target machine was last re-initialized.

    4. Click the SNMP Version drop-down menu and select SNMP Version 3 for the device or sensor you want to monitor.

      Both ipMonitor and the target device must use the same SNMP version.

  9. Enter the Timing settings or accept the default values. These options allow you to increase or minimize testing during the four monitoring test states: Up, Warn, Down, and Lost.

    1. In the Maximum Test Duration field, enter a value that indicates when to time out a test. If no response is returned in the specified value, the test is considered a failed test.

    2. In the remaining fields, update the number of seconds for each option or accept the default options.

      Up indicates the amount of time between each test while the monitor is in an OK state.

      Warn indicates the amount of time between each test after the monitor enters a Fail state. No alerts are processed during this state.

      Down indicates the amount of time between each test while the monitor is in a Fail state. Alerts are processed during this state.

      Low indicates the amount of time between each test while the monitor is in a Fail state and the maximum number of alerts are processed. No additional failure alerts are processed. If the monitor recovers, a recovery notification is sent to the targeted user.

  10. Enter the Notification Control settings or accept the default values. These settings determine how many test failures must occur before an alert is sent to the targeted user, as well as the maximum number of sent alerts.

    1. Enter the number of test failures that must occur before ipMonitor generates an alert.

      Each time a monitor test fails during a Warning state, a sequential failure count is incremented and verified against this value. A successful test resets the accumulated failure count to zero.

    2. Enter the maximum number of alerts to generate before the monitor enters a Lost state. A successful monitor test while in the Down or Lost state causes the alert sequence to reset.

  11. Enter the Recovery Parameters settings. These settings allow ipMonitor to take corrective action and automatically restore a failed resource using an external process, reboot server, or restart service recovery action.

    These parameters must be defined within the monitor that triggers the action. This provides maximum recovery coverage because a one-to-one relationship exists between each monitor and the resource being tested. They also provide a single recovery action that can service many individual monitors, as these parameters are passed to the recovery action by the monitor.

    1. Enter the IP address or name (NetBIOS or FQDN) of the machine hosting the service that needs to be restarted, or the machine that needs to be rebooted. This field is only required for the Reboot Server and/or Restart Service alerts.

      Click Browse to display and select a machine from a list of machines discovered on the network.

    2. Click Select to select a set of credentials used by a recovery alert. This allows ipMonitor to use a specific credential when executing a recovery alert that requires access to restricted resources. These resources can include Reboot Server, Restart Service, and External Process.

      If you do not assign a credential, ipMonitor uses the Windows account assigned to the ipMonitor Service. In this scenario, the results depend on the level of access the ipMonitor service account has to resources through the network

    3. Click Select and select the services to restart on the machine specified in the FQDN / NetBIOS / IP Address field. This is only required for the Restart Service alert.

      If a service includes dependencies, select all dependent services.

  12. Click OK.