---
title: "Configuring SNMP"
canonical: "https://docs.infoblox.com/space/nios85/35385484/Configuring%20SNMP"
format: markdown
---
You can configure the appliance to receive SNMP queries from specific management systems and send SNMP traps to specific trap receivers. SNMP operation supports both IPv4 and IPv6 networks. The appliance supports SNMPv1, SNMPv2, and SNMPv3. You can set up either SNMPv1/SNMPv2 or SNMPv3, or all of them for the Grid. You can also override the Grid settings at a member level.  
  
To configure SNMPv1 and SNMPv2 on the appliance, do the following:

- Enable the NIOS appliance to accept queries, as described in [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Accepting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Queries](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)
- Specify the management systems to which the appliance sends traps, as described in [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Adding](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Trap](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Receivers](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)
- Specify system information using managed objects in MIB-II, the standard MIB defined in *RFC* *1213*. For information, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Setting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[System](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Information](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*.

To configure SNMPv3 on the appliance, do the following:

- Add an SNMPv3 user and set up authentication and privacy protocols. For information, see <span style="color: #0000ff"> </span>*<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[User](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*. After you set up an SNMPv3 user, you can modify and delete it. For information, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Modifying](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Users](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276) and [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Deleting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Users](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*.
- Enable the NIOS appliance to accept queries, as described in [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Accepting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Queries](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)
- Specify the management systems to which the appliance sends traps, as described in see <span style="color: #0000ff"> </span>*<span style="color: #0000ff">[Adding](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Trap](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Receivers](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*.
- Specify system information using managed objects in MIB-II, the standard MIB defined in *RFC* *1213*.

# Configuring SNMPv3 Users

To enable SNMPv3, you must first configure SNMPv3 users on the appliance. For information about SNMPv3, see  
[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[About](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[User-Based](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[Security](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[Model](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[in](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35784493/Understanding+Simple+Network+Management+Protocol#UnderstandingSimpleNetworkManagementProtocol-bookmark2866)</span>*. To configure an SNMPv3 user:

1. From the **Administration** tab, select the **SNMPv3** **Users** tab, and then click the Add icon.
2. In the *Add* *SNMPv3* *User* wizard, complete the following:
  - **Name:** Enter a user name for the SNMPv3 management system.
  - **Authentication** **Protocol:** Select one of the following:
    - **MD5**: Select this to use the HMAC-MD5-96 authentication protocol to authenticate the SNMPv3 user.  
This protocol uses the MD5 (Message-Digest algorithm 5) hash function in HMAC (Hash-based Message Authentication Code) and truncates the output to 96 bits. The output is included as part of the SNMP message sent to the receiver. For detailed information about the protocol, refer to *RFC1321,* *The* *MD5* *Message-Digest* *Algorithm*.
    - **SHA**: Select this to use the HMAC-SHA-96 authentication protocol to authenticate the SNMPv3 user.  
This protocol uses the SHA (Secure Hash Algorithm) hash function and truncates the output to 96 bits. The output is included as part of the SNMP message sent to the receiver.
    - **None**: Select this to decline using any authentication protocol for this SNMPv3 user. When you select this option, you are not required to enter a password.
      - **Password:** Enter a password for the selected authentication protocol.
      - **Confirm** ** Password:** Enter the same password.
  - **Privacy** ** Protocol:** Select one of the following:
    - **DES**: Select this to use DES for data encryption. DES is a block cipher that employs a 56-bit key size and 64-bit block size in the encryption.
    - **AES**: Select this to use AES for data encryption. AES is a symmetric-key encryption standard that comprises AES-128 block cipher. The cipher has a 128-bit block size and a key size of 128 bits.
    - **None**: Select this to decline using any privacy protocol for this SNMPv3 user. When you select this option, you are not required to enter a password.
      - **Password:** Enter a password for the privacy protocol.
      - **Confirm** ** Password:** Enter the same password.
  - **Comment:** Enter useful information about the SNMP user, such as location or department.
  - **Disable:** Select this checkbox to retain an inactive profile for this SNMP user in the configuration. You can clear this checkbox to activate the profile.

3. Click **Next** to define extensible attributes. For information, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[Using](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[Extensible](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[Attributes](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*.

4. Save the configuration.

# Modifying SNMPv3 Users

1. From the **Administration** tab, select the **SNMPv3** **Users** tab -> *snmpv3user*, and then click the Edit icon.
2. The *SNMPv3* *User* editor provides the following tabs from which you can edit data:
  - **General**: Modify the data as described in [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Users](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*.
  - **Extensible** **Attributes**: Add and delete extensible attributes that are associated with the SNMPv3 user account. You can also modify the values of extensible attributes. For information, see <span style="color: #0000ff"> </span>*<span style="color: #0000ff">[Using](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[Extensible](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#Using Extensible Attributes)</span>*<span style="color: #0000ff">[Attributes](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448912/Managing+Extensible+Attributes#bookmark868)</span>*.
3. Save the configuration.

# Deleting SNMPv3 Users

When you delete an SNMPv3 user that is configured to send queries or receive traps, a warning message states that the SNMPv3 is associated with the corresponding function. You can then decide whether you want to delete the user or not.  
To delete an SNMPv3 user:

1. From the **Administration** tab, select the **SNMPv3** **Users** tab -> *snmpv3user*, and then click the Delete icon.
2. In the *Delete* *confirmation* dialog box, click **Yes**.

# Accepting Queries

You can allow specific management systems to send SNMP queries to a NIOS appliance. For SNMPv1 and SNMPv2, you must specify a community string. The appliance accepts queries only from management systems that provide the correct community string. You can also specify SNMPv3 users to send queries. For information about configuring SNMPv3 users, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMPv3](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Users](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*.  
To configure an appliance to accept SNMP queries:

1. Grid: From the **Grid** tab, select the **Grid** **Manager** tab, and then select **Grid** **Properties** -> **Edit** from the Toolbar. Member: From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab -> *member*, and then click the **Edit** icon.
2. In the *Grid* *Properties* or *Grid* *Member* *Properties* editor, select the **SNMP** tab. To override Grid settings, click **Override** in the *Grid* *Member* *Properties* editor.
3. Complete the following in the **SNMP** section.
  - **Enable** **SNMPv1/SNMPv2** **Queries:** Select this to accept SNMPv1 and SNMPv2 queries from management systems.
    - **Community** **String:** Enter a text string that the management system must send together with its queries to the appliance. A community string is similar to a password in that the appliance accepts queries only from management systems that send the correct community string. Note that this community string must match exactly what you enter in the management system.
  - **Engine** **ID**: Displays the engine ID of the appliance that manages the SNMP agent. The management system needs this ID to send traps to the appliance. If the appliance is an HA pair, this field displays the engine IDs for both the active and passive nodes.
  - **Enable** **SNMPv3** **Queries**: Select this to enable queries from SNMPv3 management systems. Click the Add icon to add SNMPv3 users that you have configured on the appliance. In the *SNMPv3* *User* *Selector* dialog box, click the SNMPv3 user you want to add. The appliance displays the selected SNMPv3 users in the table. You can add comments in the table. You can also select an SNMPv3 user and click the Delete icon to remove it from the table. Note that a disabled SNMPv3 user cannot send queries to the appliance.

4. Save the configuration.

# > Macro (anchor)

 > Macro (anchor)

Adding Trap Receivers

You can enable the NIOS appliance to send traps to specific management systems using either SNMPv1/SNMPv2 or SNMPv3, or all versions of SNMP. You can then add management systems that are allowed to receive traps from the appliance. Note that you cannot enable both SNMPv1/SNMPv2 and SNMPv3 on the same trap receiver. The appliance sends traps when certain events occur. You can enable SNMP traps and add trap receivers to the Grid. You can also override the Grid settings at the member level.  
To enable the appliance to send traps and to add trap receivers, do the following:

1. Grid: From the **Grid** tab, select the **Grid** **Manager** tab, and then select **Grid** **Properties** -> **Edit** from the Toolbar. Member: From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab -> *member*, and then click the **Edit** icon.
2. In the *Grid* *Properties* or *Grid* *Member* *Properties* editor, select the **SNMP** tab. To override Grid settings, click **Override** in the *Grid* *Member* *Properties* editor.
3. Complete the following in the **SNMP** tab:
  - **Enable** **SNMPv1/SNMPv2** **Traps:** Select this to enable the appliance to send traps to specified management systems.

> Macro (legacy-content)

4. Click the Add icon and select one of the following from the drop-down menu to add an SNMP trap receiver:

> Macro (legacy-content)

In the Trap Receiver table, Grid Manager displays the following information about the trap receivers:

> Macro (legacy-content)

5. Save the configuration.

# Setting SNMP System Information

You can enter values for certain managed objects in MIB-II, the standard MIB defined in *RFC* *1213*. Management systems that are allowed to send queries to the appliance can query these values. You can enter these values for the Grid and specific members. You can also override the Grid values at a member level.  
To enter system information:

1. Grid: From the **Grid** tab, select the **Grid** **Manager** tab, and then select **Grid** **Properties** -> **Edit** from the Toolbar. Member: From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab -> *member*, and then click the **Edit** icon.
2. In the *Grid* *Properties* or *Grid* *Member* *Properties* editor, select the **SNMP** tab. To override Grid settings, click **Override** in the *Grid* *Member* *Properties* editor.
3. Complete the following in the **SNMP** tab. For an HA member, click **Override** **Node** **2** **settings** to enter information for node 2 of the HA pair.
  - **sysContact:** Enter the name of the contact person for the appliance.
  - **sysLocation:** Enter the physical location of the appliance.
  - **sysName:** Enter the fully qualified domain name of the appliance.
  - **sysDescr:** Enter useful information about the appliance, such as the software version it is running.
4. Save the configuration and click **Restart** if it appears at the top of the screen.

# > Macro (anchor)

 > Macro (anchor)

 > Macro (anchor)

Defining Thresholds for Traps

Threshold events for appliance performance are configurable. For each event, you can set a value that triggers the appliance to send a trap and another value at which the appliance sends a CLEAR trap. The appliance sends a CLEAR trap the first time the event value reaches the reset value after it reached the trigger value.

To define the threshold values:

1. Grid: From the **Grid** tab, select the **Grid** **Manager** tab, and then select **Grid** **Properties** -> **Edit** from the Toolbar. Member: From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab -> *member*, and then click the **Edit** icon.
2. In the *Grid* *Properties* or *Grid* *Member* *Properties* editor, click **Toggle** **Advanced** **Mode,** and then select the **SNMP** **Threshold** tab. To override Grid settings, click **Override** in the *Grid* *Member* *Properties* editor.
3. Complete the following in the **SNMP** **Threshold** tab. Each of the following event types have default Trigger and Reset values. You can change the values for any of them. You can set SNMP thresholds above or below which the appliance sends SNMP traps and email notifications, if configured to do so. When any allocated usage exceeds the Trigger value, the appliance sends an SNMP trap and email notification to the designated destination, and the status icon for that usage turns red. When usage drops to the Reset value, the status color goes back to normal and turns green.
  - **CPU** **Usage**: The percentage of the CPU that is currently in use. The default Trigger value is 81%, and the default Reset value is 70%. Note that these default values are set to disable the CPU usage trap. You can enable this trap and configure the trigger and reset values using the CLI command set thresholdtrap.
  - **Database** **Objects:** The percentage of database capacity that is currently in use. The default Trigger value is 80%, and the default Reset value is 70%.
  - **Disk:** The percentage of the primary hard disk that is currently in use. The default Trigger value is 85%, and the default Reset value is 70%.
  - **File** **Distribution** **Usage**: The percentage of the file distribution storage capacity that is currently in use on the selected member. The default Trigger value is 90%, and the default Reset value is 70%.
  - **IPAM** **Utilization:** For a network, this is the percentage based on the IP addresses in use divided by the total addresses in the network and for a network container that contains subnets, this is the percentage of the total address space defined within the container regardless of whether any of the IP addresses in the subnets are in use. The default Trigger value is 95% and the default Reset value is 85%. The status icon turns red when utilization crosses the configured trigger value. When utilization is below the trigger value, the status color turns blue.
  - **Memory:** The percentage of the system memory that is currently in use. The default Trigger value is 90%, and the default Reset value is 80%.
  - **Network** **Capacity**: When the Grid is part of a Master Grid, this is the percentage of the Master Grid's network capacity that is used by the Grid's networks. The default Trigger value is 85% and default Reset value is 75%.
  - **Recursive** **Clients**: The percentage of the limit of concurrent recursive queries. The default Trigger value is 80%, and the default Reset value is 30%. You must also enable the recursive client limit in order for the appliance to send recursive client traps. For information about how to set this limit, see <span style="color: #0000ff"> </span>*<span style="color: #0000ff">[Restricting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*<span style="color: #0000ff">[Recursive](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*<span style="color: #0000ff">[Client](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*<span style="color: #0000ff">[Queries](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35448674/Enabling+Recursive+Queries#EnablingRecursiveQueries-RestrictingRecursiveClientQueries)</span>*. When you configure the Trigger and Reset values, ensure that you do not set them too low or too close together. If the Trigger and Reset values are too close together, the appliance may send excessive traps and email notifications because both trigger and reset traps are sent based on the calculated value of simultaneous recursive client queries. For example, when you set the recursive client limit at 50, Trigger value at 71%, and Reset value at 70%, the value for simultaneous recursive client queries is calculated at 50 x .71 = 35 (integer math truncation) and 50 x .70 = 35. This could result in the appliance sending trigger and reset traps for the same value of simultaneous recursive client queries.

> Macro (legacy-content)

If you have installed Threat Protection licenses on the appliance and are using the Infoblox feature, Grid Manager displays the following for **Trigger** **events** **per** **second** and **Reset** **events** **per** **second**:

> Macro (legacy-content)

If you have installed an RPZ license on the NIOS appliance, you can configure the thresholds to monitor the RPZ hit rate in the **Response** **Policy** **Zones** **Hit** **Rate** **Configuration** section. For information, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[Configuring](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031) [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[Thresholds](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[for](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[RPZ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[Hit](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*<span style="color: #0000ff">[Rate](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35753031)

4. Save the configuration and click **Restart** if it appears at the top of the screen.

The following table lists available Infoblox appliance models and their available memory. Note that TE appliances are IB appliances in Grid Manager.   
> Macro (anchor)

 *Table* *39.1* *Overview* *of* *Available* *Memory* *for* *Infoblox* *Appliance* *Models*

| **Infoblox**** ****Appliance**** ****Series** | **Appliance**** ****Model** | **Memory** |
| --- | --- | --- |
| Cloud Platform Virtual Appliances | CP-V2200 | 12 GB |
|  | CP-V1400 | 8 GB |
|  | CP-V800 | 2 GB |
| Advanced Appliances | PT-4000-10GE | 24 GB |
|  | PT-4000 | 24 GB |
|  | PT-2205-10GE | 64 GB |
|  | PT-2205 | 64 GB |
|  | PT-2200 | 12 GB |
|  | PT-1405 | 32 GB |
|  | PT-1400 | 8 GB |
| Network Insight Appliances | ND-4000 | 64 GB |
|  | ND-2205 | 64 GB |
|  | ND-2200 | 24 GB |
|  | ND-1405 | 32 GB |
|  | ND-1400 | 16 GB |
|  | ND-805 | 32 GB |
|  | ND-800 | 8 GB |
| <span style="color: #333333">Trinzic Appliances</span> | TE-4025 | 64 GB |
|  | TE-4015 | 64 GB |
|  | <span style="color: #333333">TE-4010</span> | 24 GB |
|  | TE-2225 | 64 GB |
|  | TE-2220 | 12 GB |
|  | TE-2215 | 64 GB |
|  | TE-2210 | 12 GB |
|  | TE-1425 | 32 GB |
|  | TE-1420 | 8 GB |
|  | TE-1415 | 32 GB |
|  | TE-1410 | 8 GB |
|  | TE-825 | 16 GB |
|  | TE-820 | 4 GB |
|  | TE-815 | 16 GB |
|  | TE-810 | 2 GB |
|  | TE-100 | 2 GB |
| DNS Cache Acceleration Appliances | IB-4030-10GE | 10 GB |
|  | IB-4030 | 24 GB |

# Setting SNMP and Email Notifications

You can specify the event types that trigger trap and email notifications. To set SNMP trap and email notifications:

1. Grid: From the **Grid** tab, select the **Grid** **Manager** tab, and then select **Grid** **Properties** -> **Edit** from the Toolbar. Member: From the **Grid** tab, select the **Grid** **Manager** -> **Members** tab -> *member*, and then click the **Edit** icon.
2. In the *Grid* *Properties* or *Grid* *Member* *Properties* editor, click **Toggle** **Advanced** **Mode,** and then select the **Notification** tab. To override Grid settings, click **Override** in the *Grid* *Member* *Properties* editor.
3. Complete the following:
  - **Enable** **All** **SNMP** **Notifications:** Select this checkbox if you want the appliance to send SNMP notifications (traps) for all events to the configured trap receivers. This is selected by default. To send SNMP notifications for specific events to the configured trap receiver, select the checkbox for respective event type.  
For information on configuring trap receivers, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Adding](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Trap](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Receivers](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)
  - **Enable** **All** **Email** **Notifications:** Select this checkbox if you want the appliance to send email notifications (traps) for all events to the configured email recipients. This is deselected by default. To send email notifications for specific events to the configured email recipients, select the checkbox for each respective event type. For more information, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Selecting](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[SNMP](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[and](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Email](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Notification](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*<span style="color: #0000ff">[Types](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276) For information on enabling email notifications and specifying recipients, see [ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)</span>*<span style="color: #0000ff">[Notifying](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)</span>*<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)<span style="color: #0000ff">[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)</span>*<span style="color: #0000ff">[Administrators](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)</span>*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849696)
  - Alternatively, you can select specific event types from the table, and specify whether you want the appliance to send SNMP Notifications and Email notifications for each type of event.

4. Save the configuration and click **Restart** if it appears at the top of the screen.

## Selecting SNMP and Email Notification Types

Instead of enabling and receiving SNMP and email notifications for all hardware and software events, you can select specific alert types when a specific hardware or software encounters issues. To enable SNMP or email notifications for specific event types, select the corresponding checkboxes in the Notification tab of the Grid Properties or Member Properties editor. The following table lists the event types you can select:

*Table 39.2 Event Types*

| **Event Type** | **Description** | **Sample SNMP Trap** |
| --- | --- | --- |
| Automated Traffic Capture | <span style="color: #333333">Sends notifications </span><span style="color: #000000">each time traffic capture is enabled or disabled or a support bundle is downloaded. For more information, see </span><span style="color: #0000ff">[*Enabling Automated Traffic Capture*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35881827)</span><span style="color: #000000">.</span> | 01:09:57.938095 IP (tos 0x0, ttl 60, id 37373, offset 0, flags [DF], proto UDP (17), length 356)  
 10.34.172.4.54004 > 10.120.20.61.162: [udp sum ok]  { SNMPv2c { V2Trap(309) R=1114072091  .1.3.6.1.2.1.1.3.0=5985 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.7779.3.1.1.1.1.7 .1.3.6.1.4.1.7779.3.1.1.1.2.1.0="infoblox.localdomain" .1.3.6.1.4.1.7779.3.1.1.1.2.2.0=2 .1.3.6.1.4.1.7779.3.1.1.1.2.5.0="Automated Traffic Capture" .1.3.6.1.4.1.7779.3.1.1.1.2.4.0=4 .1.3.6.1.4.1.7779.3.1.1.1.2.11.0="Automated traffic capture triggered by hitting Queries per second threshold: threshold=100, current=0" } } |
| BGP | Sends notifications when the BGP software has failed. For more information, see <span style="color: #0000ff">[*ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0) | 2012-11-22 04:49:06  
eng-lab-883.inca.infoblox.com [UDP: [10.35.3.115]:38185->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (45366) 0:07:33.66  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibTrapOneModule.2  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.115"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: bgp<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibRevokedLicense(53)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: An BGP routing daemon failure has occurred. |
| Backup | Sends notifications about the status of backup operation. For more information, see <span style="color: #0000ff">[*Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2011-09-22 09:14:17  
ib-10-34-41-4.infoblox.com [UDP: [10.34.41.4]:41243->[10.34.41.4]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (48621) 0:08:06.21  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibProcessingFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.41.4"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: scheduled_tftp_backups  
IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibBackupSoftwareFailure(29)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: Backup failed. |
| BloxTools | Sends notifications about the status of bloxTools. For more information, see<span style="color: #0000ff">[* Object State Change Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2911)</span>. | 2011-09-13 20:38:46<br>10.34.42.4 [UDP: [10.34.42.4]:38187->[10.34.42.2]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (742156) 2:03:41.56<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.42.4"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: bloxTools<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: bloxtools-service-failed(41)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: bloxtools-service-working(39)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: BloxTools Service is working. |
| CPU | Sends notifications about the status of CPU usage. For more information, see <span style="color: #0000ff">[*Threshold Crossing Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span><span style="color: #0000ff">*.*</span> | 2012-04-12 01:54:59  
eng-lab-631.inca.infoblox.com [UDP: [10.35.2.119]:42546->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (786308) 2:11:03.08  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibTrapOneModule.3  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.2.119"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)  
IB-TRAP-MIB::ibObjectName.0 = STRING: cpu_usage  
IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 51<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 3<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: CPU usage above threshold value. |
| CaptivePortal | Sends notifications about the Captive Portal service. For more information, see <span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2016-01-08 02:58:23<br>10.35.107.4 [UDP: [10.35.107.4]:45111->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (22280) 0:03:42.80<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.107.4"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: captive_portal<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: captive-portal-service-inactive(51)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: capative-portal-service-working(49)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Captive Portal Service is working. |
| Cisco ISE | Sends notifications about the status of the Cisco ISE service. For more information, see<span style="color: #0000ff">[* Object State Change Traps. *](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2911)</span> | 2016-01-07 22:26:19<br>10.40.240.111 [UDP: [10.40.240.111]:47355->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (16384) 0:02:43.84<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.111"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: cisco_ise_server<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 124<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 123<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: CiscoISE server 10.36.141.15 is OK. |
| Clear | Sends notifications when the SNMP trap is cleared. When you select the checkbox, the CLEAR trap is sent for the following software failures: LDAP servers, OCSP responders, LCD, Serial Console, OSPF, OSPF6, BGP, HSM, Controld, SSH, HTTP, Cluster, Login, and Duplicate IP. For file distribution, the trap is sent when the service is restored. If you deselect the checkbox, the CLEAR trap is not sent when any of the mentioned software fails. For more information, see <span style="color: #0000ff">[*Processing and Software Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span> | 2015-11-12 22:46:21<br>10.35.124.1 [UDP: [10.35.124.1]:48446->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (12793) 0:02:07.93<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.124.1"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: Login<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibClear(0)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: SNMP Trap is cleared. GUI Login |
| Cloud API | Sends notifications about whether the Cloud API service is functioning or not. for information about Cloud Network Automation, see Introduction to <span style="color: #0000ff">*[Cloud Network Automation](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110)*</span><span style="color: #0000ff">*[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110)*</span>[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110)[ ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35849110) | 2014-11-13 00:52:37<br>10.35.114.10 [UDP: [10.35.114.10]:57772->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (480221) 1:20:02.21<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.114.10"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: cloud_api<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 105<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 103<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Cloud API service is working. |
| Cluster | Sends notifications about the status of NIOS clusterd process. For more information, see*<span style="color: #0000ff"> </span>*<span style="color: #0000ff">[*Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2011-12-10 09:43:23<br>infoblox.localdomain [UDP: [10.35.2.70]:44193->[10.35.2.70]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (47140) 0:07:51.40<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "0"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: Clusterd_Monitor<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFDSoftwareFailure(32)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: WATCHDOG: A grid daemon failure has occurred on 10.35.2.70 |
| Controld | Sends notifications about the NIOS controld process. For more information, see <span style="color: #0000ff">[*Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2012-08-17 05:29:30<br><UNKNOWN> [UDP: [10.32.2.80]:43475->[10.32.2.80]:162]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (24722) 0:04:07.22<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "192.168.1.2"<br>IB-TRAP MIB::ibTrapSeverity.0 = INTEGER: critical(5)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: controld<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibControldSoftwareFailure(11)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: A controld failure has occurred. |
| DHCP | Sends notifications about the status of DHCP service. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span>. | 2016-04-18 02:42:36<br>10.35.139.15 [UDP: [10.35.139.15]:35531->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (8809) 0:01:28.09<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: dhcpd<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dhcp-service-inactive(48)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dhcp-service-working(45)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DHCP Service is working. |
| DNS | Sends notifications about the status of DNS service. For more information, see <span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span>. | 2016-01-08 01:10:53<br>10.35.3.154 [UDP: [10.35.3.154]:59876->[10.120.20.12]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (324160) 0:54:01.60<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.154"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING:DNS<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dns-service-working(32)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dns-service-inactive(34)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS Service is inactive. |
| DNS Attack | Sends notifications about the status of the DNS attacks. For more information, see <span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span>. | 2016-01-07 23:55:56<br>10.35.3.201 [UDP: [10.35.3.201]:33199->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (25100) 0:04:11.00<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.201"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: DNSAttack<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dns-attack-active(115)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dns-attack-inactive(116)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS attack conditions have ended. |
| DNS Forwarding  
to BloxOne Threat Defense Cloud | Sends notifications about whether DNS  
forwarding to BloxOne Threat Defense Cloud is  
functioning or not. For information about  
DNS forwarding to BloxOne Threat Defense Cloud, see <span style="color: #0000ff">[*Forwarding Recursive Queries to BloxOne Threat Defense Cloud*](https://infoblox-docs.atlassian.net/wiki/display/nios84draft/Using+Forwarders#UsingForwarders-bookmark1576)</span><span style="color: #0000ff">*.*</span> | 2017-11-03 14:06:19 192.168.1.3 [UDP: [192.168.1.3]:33577->[192.168.1.2]:162]: Trap, DISMAN-EVENT-MIB::sysUpTimeInstance =  
Timeticks: (180166) 0:30:01.66, SNMPv2-MIB::snmpTrapOID.0 = OID:  
SNMPv2-SMI::enterprises.7779.3.1.1.1.1.4, SNMPv2-SMI::enterprises.7779.3.1.1.1.2.1.0=STRING: "192.168.1.3",  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.2.0 =INTEGER: 2,  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.3.0 =STRING: "DNS",  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.9.0 =INTEGER: 32,  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.10.0= INTEGER: 133,  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.11.0= STRING: "The appliance is still serving DNS even though forwarding DNS queries to BloxOne Threat Defense Cloud is not functioning properly. |
| DNS Integrity<br>Check | Sends notifications about whether DNS integrity check is functioning or not. For information about DNS integrity check, see<span style="color: #0000ff">[* About DNS Integrity Check for Authoritative Zones*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35481915/Configuring+DNS+Integrity+Check+for+Authoritative+Zones#ConfiguringDNSIntegrityCheckforAuthoritativeZones-bookmark1753)</span>. | 2014-06-03 05:35:45<br>10.34.82.121 [UDP: [10.34.82.121]:42577->[10.120.20.232]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance =<br>Timeticks: (427200) 1:11:12.00<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.154.3"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: DNS Integrity Check<br>IB-TRAP-MIB::ibProbableCause.0 =INTEGER: ibDNSIntegrityCheckNameserversFailed(102)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS Integrity Check is unable to connect to any name servers required to perform the check. There are list of nameservers failure: (['10.35.0.56']) |
| DNS Integrity<br>Check<br>Connection | Sends notifications about whether DNS integrity check connection is functioning or not. For more information, see <span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0).*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 016-01-12 05:10:27<br>10.35.129.15 [UDP: [10.35.129.15]:35201->[10.120.20.12]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (213856) 0:35:38.56  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibStateChangeEvent  
IB-TRAP-MIB::ibNodeN ame.0 = STRING: "10.35.129.15"<br>IB-TRAP-MIB::ibTrapSeverity.0= INTEGER: info(2)  
IB-TRAP-MIB::ibObjectName.0 = STRING: DNS Integrity Check<br>IB-TRAP-MIB: :ibPreviousState.0 = INTEGER: dns-integrity-check-severity-indetermined(97)  
IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dns-integrity-check-severity-informational( 99)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS Integrity Check severity has changed. For DNS zone 'default-com.info', severity has changed from 'NONE' to 'INFORMATIONAL'. Reason: While checking server  
ib-10-35-133-2.infoblox.com.(ipv4=10.35.133.2) INFORMATIONAL discrepancy found because  
our servers have record(s): info.com. I N NS ib-10-35-12 |
| Database | Sends notifications about the database status. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2013-04-05 02:27:01<br>10.35.116.2 [UDP: [10.35.116.2]:45332->[10.120.20.160]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (120021) 0:20:00.21<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibThresholdCrossingEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.116.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: db_usage<br>IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 1<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 85<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 0<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Database capacity used is OK. |
| Disconnected<br>Grid | Sends notifications about whether a Grid has been disconnected from the Master Grid. For more information, see <span style="color: #0000ff">[Object State Change Traps](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2911)</span>. | 2011-12-27 23:38:44  
eng-lab-089.inca.infoblox.com [UDP: [10.35.0.89]:53010->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1049) 0:00:10.49  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibStateChangeEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.0.89"<br>IB-TRAP-MIB::ibObjectName.0 = STRING: ID_Grid  
IB-TRAP-MIB::ibPreviousState.0 = INTEGER: grid-disconnected(5)  
IB-TRAP-MIB::ibCurrentState.0 = INTEGER: grid-connected(4)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: The grid member is connected to the grid master. |
| Discovery | Sends notifications about the discovery status. For information about the Discovery feature, see *<span style="color: #0000ff">I</span>*<span style="color: #0000ff">[*nfoblox Network Insight*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35815704/Infoblox+Network+Insight#InfobloxNetworkInsight-bookmark1381)</span>. | 2013-10-22 01:35:53  
eng-lab-302.inca.infoblox.com [UDP: [10.35.1.46]:57126->[10.120.20.102]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (122717) 0:20:27.17  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibStateChangeEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.46"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: discovery_collector  
IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 89  
IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 86  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: Discovery Collector Service is working. |
| Discovery<br>Conflict | Sends notifications about conflicts between the DHCP address and the existing IP address. For more information, see <span style="color: #0000ff">[*Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>*<span style="color: #0000ff">.</span>* | 2014-06-20 00:48:06<br>10.34.125.2 [UDP: [10.34.125.2]:36159->[10.120.20.232]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2241) 0:00:22.41<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.125.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: DHCP<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibDHCPHostConflict(66)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DHCP address conflicts with an existing host address. |
| Discovery<br>Unmanaged | Sends notifications related to the discovery of unmanaged devices and networks. You can configure the maximum number of unmanaged objects the appliance discovers and how often it notifies about these events. For more information about how to configure these parameters, see<span style="color: #0000ff">[* *](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark142)</span><span style="color: #0000ff">[*Defining Seed Routers for Probe Members*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35752716/Configuring+Discovery+Properties#bookmark142)</span>. | 2015-02-09 22:53:57 10.35.103.18 [UDP: [10.35.103.18]:45156->[10.120.20.46]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance =Timeticks: (46090) 0:07:40.90<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibOperationTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.103.18"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: Discovery<br>IB-TRAP-MIB::ibProbableCause.0 =INTEGER: 4012<br>IB-TRAP-MIB::ibTrapDesc.0 =STRING: New unmanaged devices/networks were found during network discovery process. New unmanaged devices in '10.40.16.0/20' network in 'default' network view. |
| Disk | Sends notifications about the status of the primary disk. For more information, see<span style="color: #0000ff">[* Threshold Crossing Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span>*<span style="color: #0000ff">.</span>* | 2012-11-22 03:34:32  
eng-lab-883.inca.infoblox.com [UDP: [10.35.3.115]:37542->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (87141) 0:14:31.41  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibTrapOneModule.3  
IB-TRAP-MIB::ibNodeName.0 = STRING:"10.35.3.115"  
IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 =STRING: disk_usage  
IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 15<br>IB-TRAP-MIB::ibThresholdHigh.0 =INTEGER: 10<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 5<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: System primary hard disk usage is over  
threshold value. |
| DuplicateIP | Sends notifications when there are duplicate IP addresses. For more information, see <span style="color: #0000ff">[*ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0). | 2016-04-18 22:47:38<br>10.35.139.15 [UDP: [10.35.139.15]:35531->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (7239201) 20:06:32.01<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: Equipment<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibDuplicateIPAddressFailure(52)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: A Duplicate IP Address has been detected. |
| ENAT | Sends notifications about the Ethernet port status. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span>. | 2012-08-27 03:05:25<br>10.36.3.132 [UDP: [10.36.3.132]:47962->[10.120.20.232]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (16624) 0:02:46.24<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.132"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: LAN<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: enet-link-up(6)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: enet-link-down(7)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: LAN1 port link is down. Please check the connection. |
| File Distribution<br>Usage | Sends notifications about the HTTP file distribution process. For more information, see <span style="color: #0000ff">[*Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2016-01-08 01:48:57<br>10.40.240.113 [UDP: [10.40.240.113]:41443->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (183757) 0:30:37.57<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.113"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: fd_usage<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFDSoftwareFailure(42)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: File Distribution services storage usage is OK. |
| FTP | Sends notifications about the status of FTP service. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2016-01-07 23:27:22<br>10.40.240.113 [UDP: [10.40.240.113]:36063->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (380473) 1:03:24.73<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.113"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING:<br>ftp IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFTPDSoftwareFailure(44)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: An FTPD daemon failure has occurred. |
| Fan | Sends notifications about the status of the system fan. For more information, see<span style="color: #0000ff">[* lEquipment Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2906)</span><span style="color: #0000ff">*.*</span> | 2012-02-23 23:34:50<br>10.32.1.222 [UDP: [10.32.1.222]:42742->[10.35.109.24]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (89508) 0:14:55.08<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibEquipmentFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.32.1.222"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: fan<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFan1Failure(37)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Fan 1 failure has occurred. |
| HA | Sends notifications about the status of the HA port link. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span><span style="color: #0000ff">*.*</span> | 2014-05-23 00:49:32  
eng-lab-589.inca.infoblox.com [UDP: [10.35.2.77]:46426->[10.36.0.200]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3912) 0:00:39.12  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibStateChangeEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.20.70"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: HA_Replication  
IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ha-replication-offline(14)  
IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ha-replication-online(13)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: HA replication is online. |
| HSM | Sends notifications about the status of the HSM operation. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). *](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2016-01-12 20:52:12<br>10.39.13.77 [UDP: [10.39.13.77]:44962->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (131909) 0:21:59.09<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.39.13.77"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: DNS<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dns-service-working(32)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 55<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS Service restarted not using HSM |
| HTTP | Sends notifications about the status of the HTTP service. For more information, see*<span style="color: #0000ff">[ ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span>*<span style="color: #0000ff">[. ](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2016-01-07 23:16:40<br>10.40.240.113 [UDP: [10.40.240.113]:36063->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (316247) 0:52:42.47<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.113"<br>IB-TRAP-MIB::ibTrapSeverity.0= INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: http_file_dist<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: http-file-dist-service-inactive(40)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: http-file-dist-service-working(38)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: HTTP File Dist Service is working |
| IFMAP | Sends notifications about the status of the IF-MAP service. For more information, see<span style="color: #0000ff">[* ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0). | 2016-04-20 23:40:00<br>10.34.41.60 [UDP: [10.34.41.60]:33231->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (45256) 0:07:32.56<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.41.60"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: ifmapd<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibIFMAPSoftwareFailure(50)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: An IF-MAP server failure has occurred. |
| IPMI Device | Sends notifications about the status of the IPMI device. For more information, see<span style="color: #0000ff">[* ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0). | 2015-03-24 04:10:21  
eng-lab-598.inca.infoblox.com [UDP: [10.35.2.86]:56092->[10.120.20.21]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (103490) 0:17:14.90  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibOperationTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.2.86"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: IPMI Status Check  
IB-TRAP-MIB::ibProbableCause.0 = INTEGER: 2105<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: IPMI is used by some hardware monitors to test hardware health. The IPMI Device is now available; subsequent hardware monitor failures are likely to be genuine. |
| IPAM Utilization | Sends notifications about the percentage of IPv4 addresses that are used in a network. For a network container that contains subnets, this indicates the percentage of the total address space defined within the container regardless of whether any of the IP addresses are used in the subnetwork. For more information, see<span style="color: #0000ff">[* Threshold Crossing Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span><span style="color: #0000ff">*.*</span> | 2014-07-06 19:33:01  
eng-lab-514.inca.infoblox.com [UDP: [10.35.2.2]:33413->[10.120.20.21]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1038846) 2:53:08.46  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibThresholdCrossingEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.2.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: Threshold  
IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 0<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 3<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Network IPAM Utilization capacity usage is OK. Network: 20.0.0.0/29/netview |
| Load Balancer<br>Device | Sends notifications about whether the LB device is in sync or not. For more information, see <span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0).*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2013-07-08 02:36:39<br>10.35.113.2 [UDP: [10.35.113.2]:45568->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (996274) 2:46:02.74<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.113.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: device<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: lb-device-down(74)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: lb-device-up(73)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Load Balancer device 10.36.128.1 sync is OK. |
| LCD | Sends notifications about the status of the LCD process. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span> | 2011-12-01 06:31:28  
ib-10-35-3-125.infoblox.com [UDP: [10.35.3.125]:56609->[10.35.3.125]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (187334) 0:31:13.34  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibProcessingFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.125"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: lcd<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibLCDSoftwareFailure(18)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: An LCD failure has occurred. |
| LDAP Servers | Sends notifications about whether LDAP servers are available or not. For more information, see* *<span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0).*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2012-12-17 03:33:58<br>10.35.106.6 [UDP: [10.35.106.6]:35751->[10.120.20.249]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4043) 0:00:40.43<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.106.6"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: ldap_servers<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ldap-service-inactive(79)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ldap-servers-ok(76)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: All LDAP servers are available. |
| License | Sends notifications when the license has been revoked. For more information, see<span style="color: #0000ff">[* Revoked License Trap*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2913)</span>. | 2014-05-23 00:49:32  
eng-lab-589.inca.infoblox.com [UDP: [10.35.2.77]:46426->[10.36.0.200]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3912) 0:00:39.12  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibTrapOneModule.6.0  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.196.165"  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: vnios<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Grid license of member IP 10.34.196.165 with hardware ID 564d5cf2115391ab3f6efee9a9d974aa is revoked. 0 Cold Start |
| Login | Sends notifications when the login details are incorrect. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span>. | 2013-04-30 02:56:49<br>10.34.132.2 [UDP: [10.34.132.2]:35453->[10.120.20.160]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (27604) 0:04:36.04<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.152.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: Login<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibGUILoginFailure(58)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: A GUI login failure has occurred. |
| MGM | Sends notifications about the status of the multi-Grid configuration. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0).*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2013-04-03 23:48:34  
eng-lab-482.inca.infoblox.com [UDP: [10.35.1.226]:37893->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (24697) 0:04:06.97  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibTrapOneModule.4  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.116.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)  
IB-TRAP-MIB::ibObjectName.0 = STRING: Grid of Grids<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 23<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 24<br>IB-TRAP-MIB::ibTrapDesc.0 =STRING: Grid connection offline. |
| MSServer | Sends notifications about the status of Microsoft Servers for Microsoft management. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). *](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2013-07-10 03:29:42<br>10.35.113.2 [UDP: [10.35.113.2]:51679->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1066392) 2:57:43.92<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.113.2"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: ms_service<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ms-service-down(20)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ms-service-up(19)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Service connection to Microsoft DNS server 10.102.31.67 is OK. |
| Memory | Sends notifications about the status of the system memory. For more information, see<span style="color: #0000ff">[* Threshold Crossing Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span>. | 2012-04-17 03:09:46<br>10.35.119.4 [UDP: [10.35.119.4]:37664->[10.120.20.160]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (359835) 0:59:58.35<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibTrapOneModule.3<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.119.4"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: memory<br>IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 46<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 50<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 30<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: System memory usage is OK. |
| NTP | Sends notifications about the status of the NTP service. For more information, see<span style="color: #0000ff">[* ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2013-04-02 23:58:19<br>10.35.116.6 [UDP: [10.35.116.6]:37505->[10.120.20.160]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17804) 0:02:58.04<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.187"<br>IB-TRAP-MIB::ibObjectName.0 = STRING: ntp_sync<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ntp-sync-down(16)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ntp-sync-up(15)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: The NTP service resumed synchronization. |
| Network | Sends notifications about the status of the LAN port. For more information, see<span style="color: #0000ff">*[ Threshold Crossing Traps](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)*</span>[.](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910) | 2013-01-06 23:52:01<br>10.35.3.62 [UDP: [10.35.3.62]:49255->[10.120.20.160]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (80879) 0:13:28.79<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibTrapOneModule.3<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.62"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: MGM<br>IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 8<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 3<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Network capacity used is over the threshold value. |
| OCSP<br>Responders | Sends notifications about the status of OCSP responders. For more information, see <span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0).*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2016-01-14 03:21:14<br>10.34.9.91 [UDP: [10.34.9.91]:34663->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4599) 0:00:45.99<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.9.91"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: ocsp_responders<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ocsp-responders-ok(65)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ocsp-service-inactive(68)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: OCSP service inactive. |
| OSPF | Sends notifications about the ospfd process. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span><span style="color: #0000ff">*.*</span> | 2012-11-22 04:49:56  
eng-lab-883.inca.infoblox.com [UDP: [10.35.3.115]:38185->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (50414) 0:08:24.14  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibTrapOneModule.2  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.115"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: ospf<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibOSPFSoftwareFailure(35)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: An OSPF routing daemon failure has occurred. |
| OSPF6 | Sends notifications about the ospf process for IPv6. For more information, see<span style="color: #0000ff">[* ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0). | 2016-01-13 02:03:07  
eng-lab-396.inca.infoblox.com [UDP: [10.35.1.140]:45733->[10.120.20.21]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3970) 0:00:39.70  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibProcessingFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.140"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: ospf6<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibClear(0)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: SNMP Trap is cleared. OSPF6 SW |
| PowerSupply | Sends notifications about the status of the power supply. For more information, see<span style="color: #0000ff">[* lEquipment Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2906)</span> | 2012-01-20 22:45:01 nextgen.com [UDP: [10.32.111.110]:45323->[10.32.111.110]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (21044) 0:03:30.44  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibEquipmentFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.32.111.110"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)  
IB-TRAP-MIB::ibObjectName.0 = STRING: power_supply<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSystemRestart(61)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: Power supply 2 is OK. |
| RAID | Sends notifications about the RAID array status. For more information, see<span style="color: #0000ff">[* lEquipment Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2906)</span> | 2016-01-15 14:30:20  
eng-lab-418.inca.infoblox.com [UDP: [10.35.1.162]:57616->[10.120.21.204]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (8737) 0:01:27.37  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibEquipmentFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.162"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)  
IB-TRAP-MIB::ibObjectName.0 = STRING: raid  
IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibRAIDIsDegraded(3002)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: The system's RAID array is in a degraded state. |
| Recursive Clients | Sends notifications about whether the DNS recursive server is under flood attacks. For more information, see<span style="color: #0000ff">* *</span><span style="color: #0000ff">[*Threshold Crossing Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span><span style="color: #0000ff">*.*</span> | 2015-01-13 02:05:55  
eng-lab-078.inca.infoblox.com [UDP: [10.35.0.78]:55233->[10.120.20.21]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (168817) 0:28:08.17  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibThresholdCrossingEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.0.78"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)  
IB-TRAP-MIB::ibObjectName.0 = STRING: RecursiveClients  
IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 1<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 800<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 300<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Number of simultaneous DNS recursive lookups is OK. |
| RIR SWIP | Sends notifications about the status of the RIR SWIP registration. For more information, see<span style="color: #0000ff">[* ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0). | 2016-01-11 02:05:17<br>10.34.11.100 [UDP: [10.34.11.100]:52957->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (43623) 0:07:16.23<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.11.100"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: RIR SWIP<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibRIRSWIPRegistrationFailure(89)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: An RIR SWIP registration failure has occurred.CREATE RIR registration request for network "187.0.0.0/24" failed. |
| Reporting | Sends notifications about the status of the reporting database. For more information, see <span style="color: #0000ff">[*Threshold Crossing Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span> | 2012-01-06 08:59:55 10.35.101.27 [UDP: [10.35.101.27]:59714->[10.35.117.24]]:DISMA<br>N-EVENT-MIB::sysUpTimeInstance = Timeticks: (289200) 0:48:12.00<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibThresholdCrossingEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.46.6"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: reporting_volume<br>IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 85<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 80<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 71<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Reporting volume usage reached the threshold value. |
| RPZ Hit Rate | Send Notifications about the percentage of RPZ Hit Rate. For more information, see<span style="color: #0000ff">[* Threshold Crossing Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span> | 2016-04-18 02:52:29<br>10.35.139.15 [UDP: [10.35.139.15]:35531->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (68173) 0:11:21.73<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibThresholdCrossingEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: RPZHitRate<br>IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 100<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 1<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 0<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: RPZ hit rate is too high: 100%. |
| RootFS | Sends notifications about the status of the root file system. For more information, see<span style="color: #0000ff">[* Threshold Crossing Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2910)</span> | 2011-11-29 06:36:24  
ib-10-35-1-144.infoblox.com [UDP: [10.35.1.144]:59707->[10.35.1.144]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (197388) 0:32:53.88  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibThresholdCrossingEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.144"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)  
IB-TRAP-MIB::ibObjectName.0 = STRING: rootfs_usage  
IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 28<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 100<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 90<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Root filesystem disk usage is OK. |
| SNMP | Sends notifications about the status of the SNMP server. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span> | 2012-02-17 06:24:11  
eng-lab-630.inca.infoblox.com [UDP: [10.35.2.118]:57802->[10.120.20.174]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (855217) 2:22:32.17  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
SNMPv2-SMI::enterprises.7779.3.1.1.1.1.2  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.1.0 = STRING: "10.35.2.118"  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.2.0 = INTEGER: 4  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.5.0 = STRING: "snmp"  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.4.0 = INTEGER: 13  
SNMPv2-SMI::enterprises.7779.3.1.1.1.2.11.0 = STRING: "SNMP Server failure has occurred." |
| SSH | Sends notifications about the status of the sshd process. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span> | 2011-09-21 21:33:17<br>10.34.42.6 [UDP: [10.34.42.6]:49776->[10.34.42.2]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6508) 0:01:05.08<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.42.6"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: ssh<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibClear(0)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: SNMP Trap is cleared. SSHD SW |
| SerialConsole | Sends notifications when the serial console login has failed or the admin failed to login to the serial console. For more information, see <span style="color: #0000ff">[*Processing and Software Failure Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span><span style="color: #0000ff">*.*</span> | 2014-12-15 02:47:59<br>UDP/IPv6: 2620:10a:6000:2400::8104]:55038 [UDP/IPv6: [2620:10a:6000:2400::8104]:55038]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (501585) 1:23:35.85<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "2620:10a:6000:2400::8104"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: Login<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSerialConsoleLoginFailure(59)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: A Serial Console login failure has occurred. |
| Swap Usage | Sends notifications about whether the swap usage has exceeded the trigger or reset value. For more information, see<span style="color: #0000ff">[* Defining Thresholds for Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85draft/pages/26481276)</span>. | 2013-11-25 05:35:56 10.35.129.1 [UDP: [10.35.129.1]:49489->[10.120.20.21]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (24009) 0:04:00.09<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibThresholdCrossingEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.129.1"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: swap_usage<br>IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 100<br>IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5<br>IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 2<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: System swap space usage exceeds the critical threshold value. |
| Syslog | Sends notifications when the syslog process stops. For more information, see<span style="color: #0000ff">* P*</span><span style="color: #0000ff">[*rocessing and Software Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span> | 2016-01-14 01:29:42<br>10.34.142.105 [UDP: [10.34.142.105]:37566->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (296285) 0:49:22.85<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibProcessingFailureTrap<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.142.105"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)<br>IB-TRAP-MIB::ibSubsystemName.0 = STRING: check_syslog_conf<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSyslogFailure(67)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Syslog daemon is not running. |
| System | Sends notifications about the status of the NIOS system. For more information, see<span style="color: #0000ff">[* Process Started and Stopped Traps*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2912)</span><span style="color: #0000ff">*.*</span> | 2014-03-14 05:54:42  
eng-lab-636.inca.infoblox.com [UDP: [10.35.2.124]:33232->[10.36.0.200]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2654067) 7:22:20.67  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibProcessingFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.120.17"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: ID_Grid<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSystemRestart(61)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: The system is being restarted. |
| TAXII | Sends notifications when you start and stop the TAXII service. For more information, see <span style="color: #0000ff">[*Object State Change Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2911)</span> | 2016-01-06 20:16:13  
eng-lab-242.inca.infoblox.com [UDP: [10.35.0.242]:42213->[10.120.20.21]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17553) 0:02:55.53  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibStateChangeEvent  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.0.242"  
IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)  
IB-TRAP-MIB::ibObjectName.0 = STRING: taxii  
IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 122  
IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 119  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: TAXII Service is working. |
| TFTP | Sends notifications about the status of the TFTP service. For more information, see<span style="color: #0000ff">[* Processing and Software Failure Traps.*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2908)</span> | 2011-09-16 06:54:08  
eng-lab-443.inca.infoblox.com [UDP: [10.35.1.187]:35794->[10.120.20.160]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (50382) 0:08:23.82  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibProcessingFailureTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.187"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: tftp<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibTFTPDSoftwareFailure(27)  
IB-TRAP-MIB::ibTrapDesc.0 = STRING: A TFTPD daemon failure has occurred. |
| Threat Analytics | Sends notifications about the status of the Threat Analytics service. For more information, see <span style="color: #0000ff">[*ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span> (OID 3.1.1.1.2.4.0). | 2016-01-08 00:19:34<br>10.35.3.154 [UDP: [10.35.3.154]:59876->[10.120.20.12]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (16184) 0:02:41.84<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.154"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: Threat Analytics<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 127<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 126<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Threat Analytics Service is working. |
| Threat Analytics<br>DNS Tunneling | Sends notifications about the DNS tunneling detection. For more information, see* *<span style="color: #0000ff">[*ibProbableCause Values*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)</span>[* *](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2899)(OID 3.1.1.1.2.4.0). | 2016-01-08 00:22:07<br>10.35.3.154 [UDP: [10.35.3.154]:59876->[10.120.20.12]]:  
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (31567) 0:05:15.67  
SNMPv2-MIB::snmpTrapOID.0 = OID:  
IB-TRAP-MIB::ibOperationTrap  
IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.154"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4)  
IB-TRAP-MIB::ibSubsystemName.0 = STRING: Software<br>IB-TRAP-MIB::ibProbableCause.0 = INTEGER: 4013<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS Tunneling detected: The record '*.any.knjuqljsfyyc2t.com' is successfully added into BlackList RPZ zone with comment '[2016-08-01 08:22:06 UTC] [member: infoblox.localdomain] DNS Tunneling' and policy 'No Data'. |
| Threat Protection | Sends notifications about whether the threat protection service for Infoblox DNS Protection is functioning properly. For more information, see<span style="color: #0000ff">* *</span><span style="color: #0000ff">[*ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)*](https://infoblox-docs.atlassian.net/wiki/spaces/nios85/pages/35418019/SNMP+MIB+Hierarchy#SNMPMIBHierarchy-bookmark2902)</span> | 2016-04-18 22:48:08<br>10.35.139.15 [UDP: [10.35.139.15]:54407->[10.120.21.204]]:<br>DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3926) 0:00:39.26<br>SNMPv2-MIB::snmpTrapOID.0 = OID:<br>IB-TRAP-MIB::ibStateChangeEvent<br>IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15"<br>IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2)<br>IB-TRAP-MIB::ibObjectName.0 = STRING: threat_protection<br>IB-TRAP-MIB::ibPreviousState.0 = INTEGER: threat-protection-service-inactive(93)<br>IB-TRAP-MIB::ibCurrentState.0 = INTEGER: threat-protection-service-inactive(93)<br>IB-TRAP-MIB::ibTrapDesc.0 = STRING: Threat Protection Service is inactive. |

# Testing the SNMP Configuration

After you configure SNMP on the appliance, you can do the following to test your SNMP configuration:

- From the **Grid** tab, select the **Grid** **Manager** tab -> **Members** tab -> *Grid_member* checkbox, and then select **Test** **SNMP** from the Toolbar.

The appliance sends a “test trap” string to the trap receiver and displays a confirmation message at the top of the screen if your SNMP configuration is properly set up. If your SNMP configuration is not complete or if it is invalid, the appliance displays an error message. You can check your configuration and try again.

The following is a sample test trap that the trap receiver can get:

`2011-04-04 17:37:14 10.32.2.80 [UDP: [10.32.2.80]:49244->[10.32.2.80]]:`

`SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-MIB::snmpTrapOID`

`SNMPv2-MIB::sysName.0 = STRING: 'Test trap'`

# Defining Interface for SNMP Traps

By default, the NIOS appliance sends SNMP traps through the MGMT interface to specific trap receivers, or through the LAN1 interface when the MGMT interface is disabled. However, you can choose an interface, instead of the default interface, to send SNMP traps to the trap receivers. For example, if you select LAN2 interface from the drop-down list, the traps are sent from the LAN2 interface instead of the default MGMT interface.

To choose an interface, other than MGMT or LAN1, for a Grid member and a standalone Grid:

1. **Grid**: From the **Grid **tab, select the **Grid Manager **tab -> **Members **tab -> *Grid_member *checkbox.  
**Standalone**: From the **System **tab, select the **System Manager** tab, expand the Toolbar and click **System Properties** -> **Edit.**
2. In the editor, click **Toggle Advanced Mode**.
3. When the additional tabs appear, click the **Advanced **subtab of the **SNMP **tab.
4. Complete the following:
  - **Interface**: Select an interface from the drop-down list:
    - **ANY**: The default value is **ANY**. SNMP traps are sent through the MGMT interface, if it is enabled, when you select this option. If the interface is disabled, the traps are sent through the LAN1 interface.
    - **LAN1**: Select this option to send SNMP traps through the LAN1 interface.
    - **LAN2**: Select this option to send SNMP traps through the LAN2 interface.
    - **MGMT**: Select this option to send SNMP traps through the MGMT interface.
5. Click **Save & Close** to save the changes or **Cancel **to exit.