This topic describes how to configure SNMP.

SNMP is a standard protocol for managing devices on IP networks. The Delphix Engine can be configured to provide basic system level status via SNMP, and send alerts to an external SNMP manager.

Prerequisites

There are no prerequisites for enabling SNMP to provide system status. The following are prerequisites for sending alerts to an external SNMP manager.

  • At least one SNMP manager must be available, and must be configured to accept SNMPv2 InformRequest notifications.
  • Delphix's MIB (Management Information Base) files must be installed on the SNMP manager or managers. These MIB files describe the information that the Delphix Engine will send out. They are attached to this topic.

Procedure

  1. On the Delphix Engine login screen, select Server Setup.
  2. In the Delphix Setup login screen, enter the sysadmin username and password.
  3. Click Log In.
  4. Select Engine Setup.
  5. On the Delphix Engine Setup screen, select Delphix Engine Preferences.
  6. Select SNMP Configuration.
  7. Select Use SNMP.
  8. OPTIONAL: change the following settings:
    1. Community String – The string that SNMP clients must provide in order to be authorized to retrieve SNMP information from the Delphix Engine
    2. Authorized Network – The set of client IP addresses (in CIDR notation) authorized to retrieve SNMP information from the Delphix Engine. To allow all clients, set this to 0.0.0.0/0 (the default). To prevent all clients from connecting, set this to the loopback address, 127.0.0.1/32.
    3. System Location – A free-form text description of the Delphix Engine's physical location. This is provided as the value for MIB-II OID 

      .1.3.6.1.2.1.1.6.0 (sysLocation).

  9. If you do not want to send alerts to SNMP managers, then skip to step 14 to save the configuration.
  10. If you wish to send alerts using SNMP in addition, set the severity level of the messages you want to be sent to the SNMP manager(s).
  11. Click the + icon.
  12. Enter an SNMP Manager hostname / IP address.  
    Provide a community string and adjust the port number if necessary.
  13. Click Save.
    The newly-entered manager will appear in the list.
  14. The Delphix Engine will attempt to connect with the SNMP manager by transmitting an informational level message. If the Delphix Engine receives a response from the manager within 20 seconds, a check mark will appear along with the manager entry. If not, a red X will appear – check your settings and try again.
  15. Click Save to commit the SNMP configuration.

Supported MIBs

The Delphix software can be configured to send SNMP traps when Delphix alerts are generated as described in the procedure above. In order to process these traps in your SNMP manager software, you will need the base Delphix MIB, and the Delphix Alert MIB.

In addition to generating traps, the Delphix Engine supports read-only access to the following MIBs for basic system monitoring purposes.

  • The following MIB-II object hierarchies defined in RFC 1213:
    • system (OID .1.3.6.1.2.1.1): Provides basic system identity information
    • interfaces (OID .1.3.6.1.2.1.2): Provides network interface information including I/O statistics
    • ip (OID .1.3.6.1.2.1.4): IP protocol information including IP addresses configured, routes, and IP statistics
  • The following UCD objects defined in http://www.net-snmp.org/docs/mibs/ucdavis.html
    • memory usage (OID .1.3.6.1.4.1.2021.4)
    • CPU usage (OID .1.3.6.1.4.1.2021.11)
    • Disk I/O statistics (OID .1.3.6.1.4.1.2021.13.15)

Examples

The following examples assume that you have enabled SNMP on a Delphix Engine named example.company.com, and have set the community string to "public".

  1. Walking the MIB-II objects using the net-snmp snmpwalk tool:

    $ snmpwalk -v 2c -c public example.company.com
    SNMPv2-MIB::sysDescr.0 = STRING: Delphix Engine 5.1.6.0 DelphixOS 5.1.2017.03.24
    SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.41028
    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (476432) 1:19:24.32
    SNMPv2-MIB::sysContact.0 = STRING: administrator@company.com
    SNMPv2-MIB::sysName.0 = STRING: example.company.com
    SNMPv2-MIB::sysLocation.0 = STRING: VM Host 
    ...
  2. Walking Disk read and write I/O statistics:

    $ snmpwalk  -v 2c -c public example.company.com .1.3.6.1.4.1.2021.13.15.1.1.12
    UCD-DISKIO-MIB::diskIONReadX.1 = Counter64: 11310593921
    UCD-DISKIO-MIB::diskIONReadX.2 = Counter64: 334
    UCD-DISKIO-MIB::diskIONReadX.3 = Counter64: 334
    UCD-DISKIO-MIB::diskIONReadX.4 = Counter64: 865912605
    UCD-DISKIO-MIB::diskIONReadX.5 = Counter64: 867599133
    UCD-DISKIO-MIB::diskIONReadX.6 = Counter64: 865339677
    UCD-DISKIO-MIB::diskIONReadX.7 = Counter64: 11309258752
    UCD-DISKIO-MIB::diskIONReadX.8 = Counter64: 0
    UCD-DISKIO-MIB::diskIONReadX.9 = Counter64: 1822880256
    seb-laptop:~$ snmpwalk  -v 2c -c public example.company.com .1.3.6.1.4.1.2021.13.15.1.1.13
    UCD-DISKIO-MIB::diskIONWrittenX.1 = Counter64: 22337830400
    UCD-DISKIO-MIB::diskIONWrittenX.2 = Counter64: 0
    UCD-DISKIO-MIB::diskIONWrittenX.3 = Counter64: 0
    UCD-DISKIO-MIB::diskIONWrittenX.4 = Counter64: 45118203392
    UCD-DISKIO-MIB::diskIONWrittenX.5 = Counter64: 45137660928
    UCD-DISKIO-MIB::diskIONWrittenX.6 = Counter64: 45139064320
    UCD-DISKIO-MIB::diskIONWrittenX.7 = Counter64: 22337830400
    UCD-DISKIO-MIB::diskIONWrittenX.8 = Counter64: 0
    UCD-DISKIO-MIB::diskIONWrittenX.9 = Counter64: 33023515648
  3. Retrieving the system uptime:

    $ snmpget -v 2c -c public example.company.com .1.3.6.1.2.1.1.3.0
    DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1453172) 4:02:11.72