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:
To configure SNMPv3 on the appliance, do the following:
To enable SNMPv3, you must first configure SNMPv3 users on the appliance. For information about SNMPv3, see
About User-Based Security Model in SNMPv3. To configure an SNMPv3 user:
Disable: Select this check box to retain an inactive profile for this SNMP user in the configuration. You can clear this check box to activate the profile.
Note
If an SNMPv3 user is configured to send SNMP queries, you cannot delete the user.
3. Click Next to define extensible attributes. For information, see Using Extensible Attributes.
4. Save the configuration.
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:
In the Delete confirmation dialog box, click Yes.
Note
You cannot schedule the deletion of an SNMPv3 user.
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 Configuring SNMPv3 Users.
To configure an appliance to accept SNMP queries:
4. Save the configuration.
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:
4. Click the Add icon and select one of the following from the drop-down menu to add an SNMP trap receiver:
In the Trap Receiver table, Grid Manager displays the following information about the trap receivers:
5. Save the configuration.
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:
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:
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:
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 Configuring Thresholds for RPZ Hit Rate.
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.
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 | |
Trinzic Appliances | TE-4025 | 64 GB |
TE-4015 | 64 GB | |
TE-4010 | 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 |
You can specify the event types that trigger trap and email notifications. To set SNMP trap and email notifications:
4. Save the configuration and click Restart if it appears at the top of the screen.
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 check boxes 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 | Sends notifications each time traffic capture is enabled or disabled or a support bundle is downloaded. For more information, see Enabling Automated Traffic Capture. | 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 ibProbableCause Values (OID 3.1.1.1.2.4.0) | 2012-11-22 04:49:06 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibRevokedLicense(53) |
Backup | Sends notifications about the status of backup operation. For more information, see Processing and Software Failure Traps. | 2011-09-22 09:14:17 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) |
BloxTools | Sends notifications about the status of bloxTools. For more information, see Object State Change Traps. | 2011-09-13 20:38:46 10.34.42.4 [UDP: [10.34.42.4]:38187->[10.34.42.2]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (742156) 2:03:41.56 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.42.4" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: bloxTools IB-TRAP-MIB::ibPreviousState.0 = INTEGER: bloxtools-service-failed(41) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: bloxtools-service-working(39) IB-TRAP-MIB::ibTrapDesc.0 = STRING: BloxTools Service is working. |
CPU | Sends notifications about the status of CPU usage. For more information, see Threshold Crossing Traps. | 2012-04-12 01:54:59 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 3 IB-TRAP-MIB::ibTrapDesc.0 = STRING: CPU usage above threshold value. |
CaptivePortal | Sends notifications about the Captive Portal service. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0) | 2016-01-08 02:58:23 10.35.107.4 [UDP: [10.35.107.4]:45111->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (22280) 0:03:42.80 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.107.4" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: captive_portal IB-TRAP-MIB::ibPreviousState.0 = INTEGER: captive-portal-service-inactive(51) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: capative-portal-service-working(49) 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 Object State Change Traps. | 2016-01-07 22:26:19 10.40.240.111 [UDP: [10.40.240.111]:47355->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (16384) 0:02:43.84 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.111" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: cisco_ise_server IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 124 IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 123 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 check box, 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 check box, the CLEAR trap is not sent when any of the mentioned software fails. For more information, see Processing and Software Failure Traps. | 2015-11-12 22:46:21 10.35.124.1 [UDP: [10.35.124.1]:48446->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (12793) 0:02:07.93 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.124.1" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibSubsystemName.0 = STRING: Login IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibClear(0) 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 Cloud Network Automation. | 2014-11-13 00:52:37 10.35.114.10 [UDP: [10.35.114.10]:57772->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (480221) 1:20:02.21 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.114.10" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: cloud_api IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 105 IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 103 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 Processing and Software Failure Traps. | 2011-12-10 09:43:23 infoblox.localdomain [UDP: [10.35.2.70]:44193->[10.35.2.70]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (47140) 0:07:51.40 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "0" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibSubsystemName.0 = STRING: Clusterd_Monitor IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFDSoftwareFailure(32) 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 Processing and Software Failure Traps. | 2012-08-17 05:29:30 <UNKNOWN> [UDP: [10.32.2.80]:43475->[10.32.2.80]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (24722) 0:04:07.22 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "192.168.1.2" IB-TRAP MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibSubsystemName.0 = STRING: controld IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibControldSoftwareFailure(11) IB-TRAP-MIB::ibTrapDesc.0 = STRING: A controld failure has occurred. |
DHCP | Sends notifications about the status of DHCP service. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2016-04-18 02:42:36 10.35.139.15 [UDP: [10.35.139.15]:35531->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (8809) 0:01:28.09 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: dhcpd IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dhcp-service-inactive(48) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dhcp-service-working(45) IB-TRAP-MIB::ibTrapDesc.0 = STRING: DHCP Service is working. |
DNS | Sends notifications about the status of DNS service. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2016-01-08 01:10:53 10.35.3.154 [UDP: [10.35.3.154]:59876->[10.120.20.12]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (324160) 0:54:01.60 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.154" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING:DNS IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dns-service-working(32) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dns-service-inactive(34) 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2016-01-07 23:55:56 10.35.3.201 [UDP: [10.35.3.201]:33199->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (25100) 0:04:11.00 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.201" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibObjectName.0 = STRING: DNSAttack IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dns-attack-active(115) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: dns-attack-inactive(116) IB-TRAP-MIB::ibTrapDesc.0 = STRING: DNS attack conditions have ended. |
DNS Forwarding | Sends notifications about whether DNS | 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 = |
DNS Integrity Check | Sends notifications about whether DNS integrity check is functioning or not. For information about DNS integrity check, see About DNS Integrity Check for Authoritative Zones. | 2014-06-03 05:35:45 10.34.82.121 [UDP: [10.34.82.121]:42577->[10.120.20.232]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (427200) 1:11:12.00 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.154.3" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibSubsystemName.0 = STRING: DNS Integrity Check IB-TRAP-MIB::ibProbableCause.0 =INTEGER: ibDNSIntegrityCheckNameserversFailed(102) 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 Check Connection | Sends notifications about whether DNS integrity check connection is functioning or not. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 016-01-12 05:10:27 10.35.129.15 [UDP: [10.35.129.15]:35201->[10.120.20.12]]: IB-TRAP-MIB::ibTrapSeverity.0= INTEGER: info(2) IB-TRAP-MIB: :ibPreviousState.0 = INTEGER: dns-integrity-check-severity-indetermined(97) |
Database | Sends notifications about the database status. For more information, see Processing and Software Failure Traps. | 2013-04-05 02:27:01 10.35.116.2 [UDP: [10.35.116.2]:45332->[10.120.20.160]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (120021) 0:20:00.21 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibThresholdCrossingEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.116.2" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibObjectName.0 = STRING: db_usage IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 1 IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 85 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 0 IB-TRAP-MIB::ibTrapDesc.0 = STRING: Database capacity used is OK. |
Disconnected Grid | Sends notifications about whether a Grid has been disconnected from the Master Grid. For more information, see Object State Change Traps. | 2011-12-27 23:38:44 IB-TRAP-MIB::ibObjectName.0 = STRING: ID_Grid 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 Infoblox Network Insight. | 2013-10-22 01:35:53 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: discovery_collector |
Discovery Conflict | Sends notifications about conflicts between the DHCP address and the existing IP address. For more information, see Processing and Software Failure Traps. | 2014-06-20 00:48:06 10.34.125.2 [UDP: [10.34.125.2]:36159->[10.120.20.232]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (2241) 0:00:22.41 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.125.2" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibSubsystemName.0 = STRING: DHCP IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibDHCPHostConflict(66) IB-TRAP-MIB::ibTrapDesc.0 = STRING: DHCP address conflicts with an existing host address. |
Discovery 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 Defining Seed Routers for Probe Members. | 2015-02-09 22:53:57 10.35.103.18 [UDP: [10.35.103.18]:45156->[10.120.20.46]]: DISMAN-EVENT-MIB::sysUpTimeInstance =Timeticks: (46090) 0:07:40.90 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibOperationTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.103.18" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibSubsystemName.0 = STRING: Discovery IB-TRAP-MIB::ibProbableCause.0 =INTEGER: 4012 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 Threshold Crossing Traps. | 2012-11-22 03:34:32 IB-TRAP-MIB::ibObjectName.0 =STRING: disk_usage IB-TRAP-MIB::ibThresholdHigh.0 =INTEGER: 10 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 5 IB-TRAP-MIB::ibTrapDesc.0 = STRING: System primary hard disk usage is over |
DuplicateIP | Sends notifications when there are duplicate IP addresses. For more information, see ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2016-04-18 22:47:38 10.35.139.15 [UDP: [10.35.139.15]:35531->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (7239201) 20:06:32.01 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibSubsystemName.0 = STRING: Equipment IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibDuplicateIPAddressFailure(52) 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2012-08-27 03:05:25 10.36.3.132 [UDP: [10.36.3.132]:47962->[10.120.20.232]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (16624) 0:02:46.24 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.132" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibObjectName.0 = STRING: LAN IB-TRAP-MIB::ibPreviousState.0 = INTEGER: enet-link-up(6) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: enet-link-down(7) IB-TRAP-MIB::ibTrapDesc.0 = STRING: LAN1 port link is down. Please check the connection. |
File Distribution Usage | Sends notifications about the HTTP file distribution process. For more information, see Processing and Software Failure Traps. | 2016-01-08 01:48:57 10.40.240.113 [UDP: [10.40.240.113]:41443->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (183757) 0:30:37.57 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.113" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibSubsystemName.0 = STRING: fd_usage IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFDSoftwareFailure(42) 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 Processing and Software Failure Traps. | 2016-01-07 23:27:22 10.40.240.113 [UDP: [10.40.240.113]:36063->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (380473) 1:03:24.73 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.113" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibSubsystemName.0 = STRING: ftp IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFTPDSoftwareFailure(44) 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 lEquipment Failure Traps. | 2012-02-23 23:34:50 10.32.1.222 [UDP: [10.32.1.222]:42742->[10.35.109.24]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (89508) 0:14:55.08 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibEquipmentFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.32.1.222" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibObjectName.0 = STRING: fan IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibFan1Failure(37) 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2014-05-23 00:49:32 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: HA_Replication |
HSM | Sends notifications about the status of the HSM operation. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2016-01-12 20:52:12 10.39.13.77 [UDP: [10.39.13.77]:44962->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (131909) 0:21:59.09 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.39.13.77" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: DNS IB-TRAP-MIB::ibPreviousState.0 = INTEGER: dns-service-working(32) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 55 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2016-01-07 23:16:40 10.40.240.113 [UDP: [10.40.240.113]:36063->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (316247) 0:52:42.47 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.40.240.113" IB-TRAP-MIB::ibTrapSeverity.0= INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: http_file_dist IB-TRAP-MIB::ibPreviousState.0 = INTEGER: http-file-dist-service-inactive(40) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: http-file-dist-service-working(38) 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 ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2016-04-20 23:40:00 10.34.41.60 [UDP: [10.34.41.60]:33231->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (45256) 0:07:32.56 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.41.60" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibSubsystemName.0 = STRING: ifmapd IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibIFMAPSoftwareFailure(50) 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 ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2015-03-24 04:10:21 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) 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 Threshold Crossing Traps. | 2014-07-06 19:33:01 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: Threshold IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 3 IB-TRAP-MIB::ibTrapDesc.0 = STRING: Network IPAM Utilization capacity usage is OK. Network: 20.0.0.0/29/netview |
Load Balancer Device | Sends notifications about whether the LB device is in sync or not. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2013-07-08 02:36:39 10.35.113.2 [UDP: [10.35.113.2]:45568->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (996274) 2:46:02.74 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.113.2" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: device IB-TRAP-MIB::ibPreviousState.0 = INTEGER: lb-device-down(74) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: lb-device-up(73) 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 Processing and Software Failure Traps. | 2011-12-01 06:31:28 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibLCDSoftwareFailure(18) |
LDAP Servers | Sends notifications about whether LDAP servers are available or not. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2012-12-17 03:33:58 10.35.106.6 [UDP: [10.35.106.6]:35751->[10.120.20.249]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4043) 0:00:40.43 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.106.6" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: ldap_servers IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ldap-service-inactive(79) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ldap-servers-ok(76) IB-TRAP-MIB::ibTrapDesc.0 = STRING: All LDAP servers are available. |
License | Sends notifications when the license has been revoked. For more information, see Revoked License Trap. | 2014-05-23 00:49:32 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 Processing and Software Failure Traps. | 2013-04-30 02:56:49 10.34.132.2 [UDP: [10.34.132.2]:35453->[10.120.20.160]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (27604) 0:04:36.04 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.152.2" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibSubsystemName.0 = STRING: Login IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibGUILoginFailure(58) 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2013-04-03 23:48:34 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 23 IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 24 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2013-07-10 03:29:42 10.35.113.2 [UDP: [10.35.113.2]:51679->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1066392) 2:57:43.92 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.113.2" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: ms_service IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ms-service-down(20) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ms-service-up(19) 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 Threshold Crossing Traps. | 2012-04-17 03:09:46 10.35.119.4 [UDP: [10.35.119.4]:37664->[10.120.20.160]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (359835) 0:59:58.35 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibTrapOneModule.3 IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.119.4" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibObjectName.0 = STRING: memory IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 46 IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 50 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 30 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0) | 2013-04-02 23:58:19 10.35.116.6 [UDP: [10.35.116.6]:37505->[10.120.20.160]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (17804) 0:02:58.04 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.1.187" IB-TRAP-MIB::ibObjectName.0 = STRING: ntp_sync IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ntp-sync-down(16) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ntp-sync-up(15) 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 Threshold Crossing Traps. | 2013-01-06 23:52:01 10.35.3.62 [UDP: [10.35.3.62]:49255->[10.120.20.160]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (80879) 0:13:28.79 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibTrapOneModule.3 IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.62" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibObjectName.0 = STRING: MGM IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 8 IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 3 IB-TRAP-MIB::ibTrapDesc.0 = STRING: Network capacity used is over the threshold value. |
OCSP Responders | Sends notifications about the status of OCSP responders. For more information, see ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0). | 2016-01-14 03:21:14 10.34.9.91 [UDP: [10.34.9.91]:34663->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4599) 0:00:45.99 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.9.91" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: ocsp_responders IB-TRAP-MIB::ibPreviousState.0 = INTEGER: ocsp-responders-ok(65) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: ocsp-service-inactive(68) IB-TRAP-MIB::ibTrapDesc.0 = STRING: OCSP service inactive. |
OSPF | Sends notifications about the ospfd process. For more information, see Processing and Software Failure Traps. | 2012-11-22 04:49:56 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibOSPFSoftwareFailure(35) |
OSPF6 | Sends notifications about the ospf process for IPv6. For more information, see ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2016-01-13 02:03:07 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibClear(0) 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 lEquipment Failure Traps. | 2012-01-20 22:45:01 nextgen.com [UDP: [10.32.111.110]:45323->[10.32.111.110]]: IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSystemRestart(61) |
RAID | Sends notifications about the RAID array status. For more information, see lEquipment Failure Traps. | 2016-01-15 14:30:20 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) |
Recursive Clients | Sends notifications about whether the DNS recursive server is under flood attacks. For more information, see Threshold Crossing Traps. | 2015-01-13 02:05:55 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 800 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 300 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 ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2016-01-11 02:05:17 10.34.11.100 [UDP: [10.34.11.100]:52957->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (43623) 0:07:16.23 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.11.100" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibSubsystemName.0 = STRING: RIR SWIP IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibRIRSWIPRegistrationFailure(89) 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 Threshold Crossing Traps. | 2012-01-06 08:59:55 10.35.101.27 [UDP: [10.35.101.27]:59714->[10.35.117.24]]:DISMA N-EVENT-MIB::sysUpTimeInstance = Timeticks: (289200) 0:48:12.00 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibThresholdCrossingEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.46.6" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibObjectName.0 = STRING: reporting_volume IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 85 IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 80 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 71 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 Threshold Crossing Traps. | 2016-04-18 02:52:29 10.35.139.15 [UDP: [10.35.139.15]:35531->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (68173) 0:11:21.73 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibThresholdCrossingEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibObjectName.0 = STRING: RPZHitRate IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 100 IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 1 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 0 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 Threshold Crossing Traps. | 2011-11-29 06:36:24 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 100 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 90 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 Processing and Software Failure Traps. | 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 Processing and Software Failure Traps. | 2011-09-21 21:33:17 10.34.42.6 [UDP: [10.34.42.6]:49776->[10.34.42.2]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6508) 0:01:05.08 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.42.6" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibSubsystemName.0 = STRING: ssh IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibClear(0) 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 Processing and Software Failure Traps. | 2014-12-15 02:47:59 UDP/IPv6: 2620:10a:6000:2400::8104]:55038 [UDP/IPv6: [2620:10a:6000:2400::8104]:55038]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (501585) 1:23:35.85 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "2620:10a:6000:2400::8104" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibSubsystemName.0 = STRING: Login IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSerialConsoleLoginFailure(59) 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 Defining Thresholds for Traps. | 2013-11-25 05:35:56 10.35.129.1 [UDP: [10.35.129.1]:49489->[10.120.20.21]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (24009) 0:04:00.09 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibThresholdCrossingEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.129.1" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibObjectName.0 = STRING: swap_usage IB-TRAP-MIB::ibCurThresholdValue.0 = INTEGER: 100 IB-TRAP-MIB::ibThresholdHigh.0 = INTEGER: 5 IB-TRAP-MIB::ibThresholdLow.0 = INTEGER: 2 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 Processing and Software Failure Traps. | 2016-01-14 01:29:42 10.34.142.105 [UDP: [10.34.142.105]:37566->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (296285) 0:49:22.85 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibProcessingFailureTrap IB-TRAP-MIB::ibNodeName.0 = STRING: "10.34.142.105" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibSubsystemName.0 = STRING: check_syslog_conf IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSyslogFailure(67) 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 Process Started and Stopped Traps. | 2014-03-14 05:54:42 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: minor(3) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibSystemRestart(61) |
TAXII | Sends notifications when you start and stop the TAXII service. For more information, see Object State Change Traps. | 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 Processing and Software Failure Traps. | 2011-09-16 06:54:08 IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: critical(5) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: ibTFTPDSoftwareFailure(27) |
Threat Analytics | Sends notifications about the status of the Threat Analytics service. For more information, see ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2016-01-08 00:19:34 10.35.3.154 [UDP: [10.35.3.154]:59876->[10.120.20.12]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (16184) 0:02:41.84 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.3.154" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: Threat Analytics IB-TRAP-MIB::ibPreviousState.0 = INTEGER: 127 IB-TRAP-MIB::ibCurrentState.0 = INTEGER: 126 IB-TRAP-MIB::ibTrapDesc.0 = STRING: Threat Analytics Service is working. |
Threat Analytics DNS Tunneling | Sends notifications about the DNS tunneling detection. For more information, see ibProbableCause Values (OID 3.1.1.1.2.4.0). | 2016-01-08 00:22:07 10.35.3.154 [UDP: [10.35.3.154]:59876->[10.120.20.12]]: IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: major(4) IB-TRAP-MIB::ibProbableCause.0 = INTEGER: 4013 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 ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0) | 2016-04-18 22:48:08 10.35.139.15 [UDP: [10.35.139.15]:54407->[10.120.21.204]]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3926) 0:00:39.26 SNMPv2-MIB::snmpTrapOID.0 = OID: IB-TRAP-MIB::ibStateChangeEvent IB-TRAP-MIB::ibNodeName.0 = STRING: "10.35.139.15" IB-TRAP-MIB::ibTrapSeverity.0 = INTEGER: info(2) IB-TRAP-MIB::ibObjectName.0 = STRING: threat_protection IB-TRAP-MIB::ibPreviousState.0 = INTEGER: threat-protection-service-inactive(93) IB-TRAP-MIB::ibCurrentState.0 = INTEGER: threat-protection-service-inactive(93) IB-TRAP-MIB::ibTrapDesc.0 = STRING: Threat Protection Service is inactive. |
After you configure SNMP on the appliance, you can do the following to test your SNMP configuration:
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'
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:
This page has no comments.