SNMP MIB Hierarchy. MIB Objects

(1)

SNMP MIB Hierarchy

In addition to implementing its own enterprise MIBs, Infoblox supports the standard MIBs defined in RFC-1213, Management Information Base for Network

Management of TCP/IP-based internets: MIB-II.

The Infoblox MIBs are part of a universal hierarchical structure, usually referred to as the MIB tree. The MIB tree has an unlabeled root with three subtrees. The below figure illustrates the branch of the MIB tree that leads to the Infoblox enterprise MIBs. Each object in the MIB tree has a label that consists of a textual description and an OID (object identifier). An OID is a unique dotted-decimal number that identifies the location of the object in the MIB tree. Note that all OIDs begin with a dot (.) to indicate the root of the MIB tree.

As shown in the below figure, Infoblox is a branch of the Enterprise subtree. IANA (Internet Assigned Numbers Authority) administers the Enterprise subtree, which is designated specifically for vendors who define their own MIBs. The IANA-assigned enterprise number of Infoblox is 7779. Therefore, the OIDs of all Infoblox MIB objects begin with the prefix .1.3.6.1.4.1.7779. In addition, IB-DNSSERV and IB-DHCPSERV are branches of the Enterprise subtree as well.

The Infoblox SNMP subtree branches down through two levels, ibProduct and ibOne, to the Infoblox MIBs: ibTrap, ibPlatformOne, ibDNSone, and ibDHCPOne. The ibTrap MIB defines the traps that NIOS appliances send, and the ibPlatformOne, ibDNSone, and ibDHCPOne MIBs provide information about the appliance. For detailed information about these MIBS, see the Infoblox MIBs section.

MIB Hierarchy

(2)

The Infoblox MIB objects were implemented according to the guidelines in RFCs 1155 and 2578. They specify two types of macros for defining MIB objects: OBJECT-TYPE and NOTIFICATION-TYPE. These macros contain clauses that describe the characteristics of an object, such as its syntax and its status. OBJECT-TYPE macros describe MIB objects, and NOTIFICATION-TYPE macros describe objects used in SNMP traps.

Each object in the ibPlatformOne, ibDNSone, and ibDHCPOne MIBs contains the following clauses from the OBJECT-TYPE macro: OBJECT-TYPE: Provides the administratively-assigned name of the object.

SYNTAX: Identifies the data structure of the object, such as integers, counters, and octet strings.

MAX-ACCESS: Identifies the type of access that a management station has to the object. All Infoblox MIB objects provide read-only access. STATUS: Identifies the status of the object. Values are current, obsolete, and deprecated.

DESCRIPTION: Provides a textual description of the object.

INDEX or AUGMENTS: An object that represents a conceptual row must have either an INDEX or AUGMENTS clause that defines a key for selecting a row in a table.

OID: The dotted decimal object identifier that defines the location of the object in the universal MIB tree.

The ibTrap MIB defines the SNMP traps that a NIOS appliance can send. Each object in the ibTrap MIB contains the following clauses from the NOTIFICATION-TYPE macro:

NOTIFICATION-TYPE: Provides the administratively-assigned name of the object. OBJECTS: Provides an ordered list of MIB objects that are in the trap.

STATUS: Identifies the status of the object. Values are current, obsolete, and deprecated. DESCRIPTION: Provides the notification information.

System Object IDs

Infoblox uses the SNMP system object identifier sysObjectID to identify Infoblox appliances. The following is a definition of sysObjectID from the SNMPv2 MIB, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP):

OB JE CT -TY PE sysObjectID SY NT AX Object Identifier MA X-AC CE SS read-only ST AT US current DE SC RI PTI ON

"The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones,Inc.' was assigned the subtree 1.3.6.1.4.1.424242, it could assign the identifier 1.3.6.1.4.1.424242.1.1 to its `Fred Router'."

The table below lists the enterprise IDs and their corresponding Infoblox hardware platforms that an SNMP query can return when you request the sysObjectID value. Note that the IDs shown in the table do not include 1.3.6.1.4.1.7779.1. (the infobloxProducts prefix).

Table 39.3 sysObjectID for Infoblox Hardware

ID Description Definition

1000 ibDefault Default environments, such as chroot

1002 ibCisco Cisco servers

1003 ibvm vNIOS appliances on VMware ESX or ESXi servers

1004 ibvnios Virtual NIOS

1401 ib810 Trinzic 810 appliances

(3)

1403 ib1410 Trinzic 1410 appliances 1404 ib1420 Trinzic 1420 appliances

1405 ib1400 Trinzic Reporting 1400 appliances 1406 ib800 Trinzic Reporting 800 appliances

1407 pt1400 Advanced 1400 appliances

1411 ib2200 Trinzic Reporting 2200 appliances 1412 ib2210 Trinzic 2210 appliances

1421 ib4010 Infoblox-4010 appliances 1422 ib4030 Infoblox-4030 appliances 1423 ib4000 Infoblox-4000 appliances

1441 nd800 Network Insight 800 appliances 1442 nd1400 Network Insight 1400 appliances 1443 nd2200 Network Insight 2200 appliances 1444 nd4000 Network Insight 4000 appliances

1503 ib1415 Trinzic 1415 appliances 1504 ib1425 Trinzic 1425 appliances 1505 ib1405 Trinzic 1405 appliances

(4)

1. 2. a. b. c. 1. 2. 3. 4. 5. 6. 7. 8.

Infoblox MIBs

You can configure a NIOS appliance as an SNMP-managed device so that an SNMP management station can send queries to the appliance and retrieve information from its MIBs. Perform the following tasks to access the Infoblox MIBs:

Configure a NIOS appliance to accept queries, as described in Configuring SNMPv3 Users. Load the MIB files onto the management system. To obtain the latest Infoblox MIB files:

From the Data Management tab, select the Grid tab -> Grid Manager tab, and then select Download -> SNMP MIBs from the Toolbar. In the Save As dialog box, navigate to a directory to which you want to save the MIBs.

Click Save.

3. Use a MIB browser or SNMP management application to query the objects in each MIB.

The NIOS appliance allows read-only access to the MIBs. This is equivalent to the Get and Get Next operations in SNMP.

Loading the Infoblox MIBs

If you are using an SNMP manager toolkit with strict dependency checking, you must download the following Infoblox MIBs in the order they are listed: IB-SMI-MIB.txt IB-TRAP-MIB.txt IB-PLATFORMONE-MIB.txt IB-DNSONE-MIB.txt IB-DHCPONE-MIB.txt IB-DNSSERV-MIB.txt IB-DHCPSERV-MIB.txt IB-DHCPV6ONE-MIB.txt

In addition, if the SNMP manager toolkit you use requires a different MIB file naming convention, you can rename the MIB files accordingly.

NET-SNMP MIBs

NIOS appliances support NET-SNMP (formerly UCD-SNMP), a collection of applications used to implement the SNMP protocol. The NET-SNMP MIBs provide the top-level infrastructure for the SNMP MIB tree. They define, among other things, the objects in the SNMP traps that the agent sends when the SNMP engine starts and stops. For information about NET-SNMP and the MIB files distributed with NET-SNMP, refer to http://net-snmp.sourceforge.net/. For SNMP traps to function properly, you must download the following NET-SNMP MIBs directly from http://net-snmp.sourceforge.net/docs/mibs.

NET-SNMP-MIB UCD-SNMP-MIB

BGP4 MIB

Infoblox supports BGP4 (Border Gateway Protocol) for DNS anycast addressing. BGP is configured to send SNMP traps to neighboring routers, as defined in RFC4273DefinitionsofManagedObjectsforBGP-4. You must enable and configure the SNMP trap receiver on the Grid member for the member to send SNMP traps.

The BGP protocol service is configured to send SNMP queries about BGP runtime data. The information is returned using the following OIDs and definitions:

OID Definition

1.3.6.1.2.1.15.900.1.1 Number of peers 1.3.6.1.2.1.15.900.1.2 Number of active peers 1.3.6.1.2.1.15.900.1.3 Number of AS path entries 1.3.6.1.2.1.15.900.1.4 Number of BGP community entries 1.3.6.1.2.1.15.900.1.5 Total number of prefixes

Note

(5)

For each configured BGP peer (a, b, c, d), the information is returned using the following OIDs and definitions:

OID Definition

1.3.6.1.2.1.15.900.1.9.a.b.c.d.1 IP address: same as a.b.c.d 1.3.6.1.2.1.15.900.1.9.a.b.c.d.2 State: 0=down, 1=up 1.3.6.1.2.1.15.900.1.9.a.b.c.d.3 ASN

1.3.6.1.2.1.15.900.1.9.a.b.c.d.4 Prefixes 1.3.6.1.2.1.15.900.1.9.a.b.c.d.5 Up/Down time

ibTrap MIB

NIOS appliances send SNMP traps when events, internal process failures, or critical service failures occur. The ibTrap MIB defines the types of traps that a NIOS appliance sends and the value that each MIB object represents. The Infoblox SNMP traps report objects which the ibTrap MIB defines. The below figure illustrates the ibTrap MIB structure. It provides the OID and textual description for each object.

The ibTrap MIB comprises two trees, ibTrapOneModule and ibNotificationVarBind. The ibTraponeModule tree contains objects for the types of traps that a NIOS appliance sends. The ibNotificationVarBind tree contains objects that the Infoblox SNMP traps report. You cannot send queries for the objects in this MIB module. The objects are used only in the SNMP traps.

ibTrapOne MIB Structure Note

(6)

Interpreting Infoblox SNMP Traps

Depending on the SNMP management application your management system uses, the SNMP traps you receive may list the OIDs for all relevant MIB objects from both the ibTrapOneModule and ibNotificationVarBind trees. For OIDs that have string values, the trap lists the text. For OIDs that contain integers, you can use the tables in this section to find out the values. Some SNMP management applications list only the object names and their corresponding values in the SNMP traps. Whether or not your SNMP management application lists OIDs, you can use the tables in this section to find out the corresponding value and definition for each MIB object.

The following is a sample trap a NIOS appliance sends:

418:Jan 31 18:52:26 (none) snmptrapd[6087]: 2008-01-31 18:52:26 10.35.1.156 [UDP: [10.35.1.156]:32772]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (1080)

0:00:10.80 SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::enterprises.7779.3.1.1.1.1.4.0 SNMPv2-SMI::enterprises.7779.3.1.1.1.2.1.0 = STRING: "10.35.1.156"

SNMPv2-SMI::enterprises.

7779.3.1.1.1.2.3.0 = STRING: "ntp_sync" SNMPv2-SMI::enterprises.7779.3.1.1.1.2.9.0 = INTEGER: 15 SNMPv2-SMI::enterprises.7779.3.1.1.1.2.10.0 = INTEGER: 16

SNMPv2-SMI::enterprises.7779.3.1.1.1.2.11.0 = STRING: "The NTP service is out of synchronization."

The sample trap lists the OIDs and their corresponding values that can help you identify the cause of an event or problem. To identify the possible cause and recommended actions for the trap, use the ibTrapDesc tables.

(7)

Using the ibTrapOneModule table, you find out OID 7779.3.1.1.1.1.4.0 represents an Object State Change trap. This trap includes the following objects: ibNodeName, ibOjectName, ibPreviousState, ibCurrentState, and ibtrapDesc. For each object, the trap displays the OID and its corresponding value. The following is how you can interpret the rest of the trap:

ibNodeName (OID 7779.3.1.1.1.2.1.0)

Using the ibNotificationVarBind (OID 3.1.1.1.2)table, you find out OID 7779.3.1.1.1.2.1.0 represents the MIB object ibNodeName, which is the IP address of the appliance on which the trap occurred. Therefore, the statement "7779.3.1.1.1.2.1.0 = STRING:

tells you the IP address of the appliance on which the trap occurred.

"10.35.1.156" SNMPv2-SMI::enterprises."

ibObjectName (OID 7779.3.1.1.1.2.3.0)

The statement "7779.3.1.1.1.2.3.0 = STRING: "ntp_sync" SNMPv2-SMI::enterprises." tells you the MIB object ibOjectName, which is the name of the object for which the trap was generated, has a value of "ntp_sync" that indicates NTP synchronization issues.

ibPreviousState (OID 7779.3.1.1.1.2.9.0)

The statement "7779.3.1.1.1.2.9.0 = INTEGER: 15 SNMPv2-SMI::enterprises." tells you the MIB object ibPreviousState, which indicates the previous state of the appliance, has a value of 15. Using the ibPreviousState and ibCurrentState Values table, you know that 15 represents "ntp-sync-up", which means the NTP server was up and running.

ibCurrentState (OID 7779.3.1.1.1.2.10.0)

The statement "7779.3.1.1.1.2.10.0 = INTEGER: 16 SNMPv2-SMI::enterprises." tells you the MIB object ibCurrentState, which indicates the current state of the appliance, has a value of 16. Using the ibPreviousState and ibCurrentState Values table, you know that 16 represents "ntp-sync-down", which means the NTP server is now out of sync.

ibTrapDesc (OID 7779.3.1.1.1.2.11.0)

The last statement "7779.3.1.1.1.2.11.0 = STRING: "The NTP service is out of synchronization." states the description of the trap. Using the Object State Change Traps table for ibTrapDesc, you can find out the trap description and recommended actions for this problem.

Types of Traps (OID 3.1.1.1.1)

ibTrapOneModule defines the types of traps that the NIOS appliance can send. There are five types of SNMP traps.

ibTrapOneModule

Trap Binding Variables (OID 3.1.1.1.2)

OID Trap Type MIB Object Description

3.1.1.1. 1.1

Equipment Failure ibEquipmentFailure Trap

The NIOS appliance generates this trap when a hardware failure occurs. This trap includes the following objects:

ibNodeName ibTrapSevertiy

ibObjectName (equipment name) ibProbableCause

ibTrapDesc

3.1.1.1. 1.2

Processing and Software Failure

ibProcessingFailure Trap

The NIOS appliance generates this trap when a failure occurs in one of the software processes. This trap includes the following objects:

ibNodeName ibTrapSeverity ibSubsystemName ibProbableCause ibTrapDesc 3.1.1.1. 1.3

Threshold Crossing ibThresholdCrossing Event

The NIOS appliance generates this trap when any of the following events occur: System memory or disk usage exceeds 90%.

CPU usage exceeds the trigger value for 15 seconds.

A problem occurs when the Grid Master replicates its database to its Grid members. DHCP address usage crosses a watermark threshold.

The number or percentage of the DNS security alerts exceeds the thresholds of the DNS security alert triggers.

This trap includes the following objects: ibNodeName

ibTrapSeverity

ibObjectName (threshold name) ibCurThresholdvalue ibThresholdHigh ibThresholdLow ibTrapDesc Note

(8)

3.1.1.1. 1.4

Object State Change ibStateChangeEvent The NIOS appliance generates this trap when there is a change in its state, such as: The link to one of the configured ports goes down, and then goes back up again. A failover occurs in an HA (high availability) pair configuration.

A member connects to the Grid Master.

An appliance in a Grid goes offline. This trap includes the following objects: ibNodeName ibTrapSeverity ibObjectName ibPreviousState ibCurrentState ibTrapDesc 3.1.1.1. 1.5

Process Started and Stopped

ibProcStartStopTrap The NIOS appliance generates this type of trap when any of the following events occur: When you enable HTTP redirection.

When you change the HTTP access setting. When you change the HTTP session time out setting. When a failover occurs in an HA pair configuration. This trap includes the following objects:

ibNodeName ibSubsystemName ibTrapDesc 3.1.1.1. 1.6 ibRevokedLicenseTr ap

The NIOS appliance generates this trap when a license is revoked. This trap includes the following objects:

ibNodeName ibTrapSeverity ibSubsystemName ibTrapDesc 3.1.1.1. 1.7

ibOperationTrap The NIOS appliance generates this trap when a software operation is noteworthy. This trap includes the following objects:

ibNodeName ibTrapSeverity ibSubsystemName ibProbableCause ibTrapDesc

Each SNMP trap contains information about the event or the problem. The Infoblox SNMP traps include MIB objects and their corresponding values from the ibNotificationVarBind module. The following table describes the objects in the ibNotificationVarBind module:

ibNotificationVarBind (OID 3.1.1.1.2) OID MIB Object (Type) Description 3.1.1. 1.2.1.0 ibNodeNa me (DisplayStri ng)

The IP address of the appliance on which the trap occurs. This may or may not be the same as the appliance that sends the trap. This object is used in all types of traps.

3.1.1. 1.2.2.0

ibTrapSeve rity (Integer)

The severity of the trap. There are five levels of severity.

3.1.1. 1.2.3.0 ibObjectNa me (DisplayStri ng)

The name of the object for which the trap was generated. This is used in the Equipment Failure traps, Threshold Crossing Event traps, and the Object State Change traps. The following shows what this object represents depending on the type of traps:

Equipment Failure traps: The equipment name.

Threshold Crossing Event traps: The object name of the trap. State Change traps: The object that changes state.

3.1.1. 1.2.4.0

ibProbable Cause (Integer)

The probable cause of the trap.

3.1.1. 1.2.5.0 ibSubsyste mName (DisplayStri ng)

(9)

3.1.1. 1.2.6.0

ibCurThres holdValue (Integer)

The current value of the threshold counter. This object is used in the Threshold Crossing traps.

3.1.1. 1.2.7.0

ibThreshold High (Integer)

This object is used in Threshold Crossing traps. For CPU usage, this is the trigger value of the SNMP trap. For DHCP address usage, this is the value of the high watermark. This only applies when the appliance sends a trap to indicate that DHCP address usage is above the configured high watermark value for a DHCP address range.

3.1.1. 1.2.8.0

ibThreshold Low (Integer)

This object is used in Threshold Crossing traps. For CPU usage, this is the reset value of the SNMP trap. For DHCP address usage, this is the value for the low watermark. This only applies when the appliance sends a trap to indicate that DHCP address usage went below the configured low watermark value for a DHCP address range.

3.1.1. 1.2.9.0

ibPrevious State (Integer)

The previous state of the appliance. This object is used in the Object State Change traps. See the ibPreviousState (OID section for definitions of each value.

3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)

3.1.1. 1.2.1 0.0 ibCurrentSt ate (Integer)

The current state of the appliance. This object is used in the Object State Change traps. See the ibPreviousState (OID section for definitions of each value.

3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)

3.1.1. 1.2.1 1.0 ibTrapDesc (DisplayStri ng)

The description of the trap. This object is used in all types of traps. See the ibTrapDesc (OID 3.1.1.1.2.11.0) section for the description, possible cause, and recommended actions for each Infoblox SNMP trap.

Trap Severity (OID 3.1.1.1.2.2.0)

The object ibTrapSeverity defines the severity level for each Infoblox SNMP trap. There are five levels of severity:

Value Description

1 Indetermined [sic]

2 Informational: Event that requires no further action. 3 Minor: Event that does not require user intervention.

4 Major: Event that requires user intervention and assistance from Infoblox Technical Support.

5 Critical: Problem that affects services and system operations, and requires assistance from Infoblox Technical Support.

ibProbableCause Values (OID 3.1.1.1.2.4.0)

The following table lists the values that are associated with the object ibProbableCause (OID 3.1.1.1.2.4.0). These values provide information about the events such as hardware, software or process failures, that trigger SNMP traps.

Table 39.6 ibProbableCause Values

Value

OID 3.1.1.1.2.4.0

ibProbableCause Equipment, Software, or Process Failure Traps

0 ibClear SNMP Trap is cleared.

1 ibUnknown An unknown failure has occurred.

2 ibPrimaryDiskFailure A primary drive failure has occurred.

3 ibFanFailure-old Unused.

4 ibPowerSupplyFailure A power supply failure has occurred.

5 ibDBFailure A database daemon monitoring failure has occurred.

6 ibApacheSoftwareFailure An apache software failure has occurred.

7 ibSerialConsoleFailure An Infoblox serial console software failure has occurred.

11 ibControldSoftwareFailure A controld failure has occurred.

12 ibUpgradeFailure A system upgrade failure has occurred.

13 ibSNMPDFailure SNMP Server failure has occurred.

(10)

16 ibNTPDSoftwareFailure An NTP daemon failure has occurred.

17 ibClusterdSoftwareFailure A cluster daemon failure has occurred.

18 ibLCDSoftwareFailure An LCD daemon failure has occurred.

19 ibDHCPdSoftwareFailure A DHCP daemon monitoring failure has occurred.

20 ibNamedSoftwareFailure A named daemon monitoring failure has occurred.

21 ibAuthServerGroupDown NAC Authentication server group is down.

22 ibAuthServerGroupUp NAC Authentication server group is up.

24 ibNTLMSoftwareFailure An NTLM monitoring failure has occurred.

25 ibNetBIOSDaemonFailure A NetBIOS daemon monitoring failure has occurred.

26 ibWindowBindDaemonFailure An NT domain service monitoring failure has occurred.

27 ibTFTPDSoftwareFailure A TFTPD daemon failure has occurred.

28 ibUNUSED28 Unused.

29 ibBackupSoftwareFailure Backup failed.

30 ibBackupDatabaseSoftwareFailure Database backup failed.

31 ibBackupModuleSoftwareFailure Module backup failed.

32 ibBackupSizeSoftwareFailure File size exceeded the quota. Backup failed.

33 ibBackupLockSoftwareFailure Another backup is in progress. Backup will not be performed. 34 ibHTTPFileDistSoftwareFailure An HTTP file distribution daemon failure has occurred.

35 ibOSPFSoftwareFailure An OSPF routing daemon failure has occurred.

36 ibAuthDHCPNamedSoftwareFailure An auth named server failure has occurred.

37 ibFan1Failure Fan 1 failure has occurred.

40 ibFan1OK Fan 1 is OK.

44 ibFTPDSoftwareFailure An FTPD daemon failure has occurred.

45 ibBloxtoolsSoftwareFailure A Bloxtools service failure has occurred.

46 ibPowerSupplyOK The power supply is OK.

47 ibWebUISoftwareFailure A WebUI software failure has occurred.

48 ibUNUSED48 Unused.

49 ibADAgentSyncFailure An AD agent client synchronizing domain data failure has occurred.

50 ibIFMAPSoftwareFailure An IF-MAP server failure has occurred.

51 ibCaptivePortalSoftwareFailure A Captive Portal service failure has occurred. 52 ibDuplicateIPAddressFailure A Duplicate IP Address has been detected.

53 ibBGPSoftwareFailure An BGP routing daemon failure has occurred.

54 ibRevokedLicense A license has been revoked.

58 ibGUILoginFailure An admin failed to log in to the GUI.

59 ibSerialConsoleLoginFailure An admin failed to log in to the serial console.

60 ibSystemReboot A system reboot was initiated.

(11)

62 ibZoneTransferFailure A zone transfer failure occurred.

63 ibDHCPLeaseConflict DHCP address conflicts with an existing lease.

64 ibDHCPAddressConflict DHCP address conflicts with an existing fixed address.

65 ibDHCPRangeConflict DHCP address conflicts with an existing range.

66 ibDHCPHostConflict DHCP address conflicts with an existing host.

67 ibSyslogFailure A syslog daemon failure occurred.

68 ibPowerSupply1Failure Power supply 1 failure has occurred.

69 ibPowerSupply2Failure Power supply 2 failure has occurred.

70 ibPowerSupply1OK Power supply 1 is OK.

71 ibPowerSupply2OK Power supply 2 is OK.

72 ibReportingTaskSwFailure A reporting task monitoring failure has occurred.

73 ibReportingDbBackupFailure A reporting db backup/restore operation failure has occurred.

84 ibOSPF6SoftwareFailure An OSPF6 routing daemon failure has occurred.

85 ibOCSPResponderFailure OCSP responder failed.

86 ibReportingAlertTriggered A reporting alert is triggered.

87 ibCapturedQueriesUploadFailure Upload for captured DNS queries failed.

88 ibLDAPServerFailure The LDAP server failed.

89 ibRIRWIPRegistrationFailure RIR SWIP registration failed.

90 ibPowerSupply1Removed Power supply 1 has been removed.

91 ibPowerSupply2Removed Power supply 2 has been removed.

92 ibIPMISensorErrorDetected Error detected on the sensor for the IPMI port (used for LOM) 93 ibDiscoveryConsolidatorTaskSwFailure Discovery service on the Consolidator failed.

94 ibDiscoveryCollectorTaskSwFailure Discovery service on probes failed.

95 ibDiscoveryBackupSwFailure Discovery backup service failed.

96 ibThreatProtectionAutoDownloadFailure Automatic download of threat protection rule failed. 97 ibThreatProtectionPublishFailure Threat protection rule publish failed.

98 ibPassiveHANodeARPConnectivityFailure HA node failed to connect to local router. 99 ibPassiveHANodeARPConnectivitySuccess HA node successfully connects to local router.

(12)

103 ibCloudAPIFailure Cloud API service failed.

104 ibRpzRefreshFailure An RPZ refresh failure has occurred.

105 ibUnboundSoftwareFailure Unbound software failure has occurred.

106 ibAnalyticsAutoDownloadFailure Automatic download of analytic module set failed.

107 ibDnsHealthCheckFailed The DNS health check has failed.

108 ibDnsHealthCheckSucceed The DNS health check is successful.

109 ibBFDSoftwareFailure BFD has failed to detect failure in the bidirectional path between two interfaces.

110 ibOutboundWorkerFailed An Outbound worker has failed.

3001 ibRAIDIsOptimal The system’s RAID array is now running in an optimal state.

3002 ibRAIDIsDegraded The system’s RAID array is in a degraded state.

3003 ibRAIDIsRebuilding The system’s RAID array is rebuilding.

3004 ibRAIDStatusUnknown Unable to retrieve RAID array state!

3005 ibRAIDBatteryIsOK The system’s RAID battery is OK.

3006 ibRAIDBatteryFailed A RAID battery failure has occurred.

3007 ibRAIDOptimalMismatch The system's RAID array is now running in an optimal state (Mismatched disk(s) found). 3008 ibRAIDDegradedMismatch The system's RAID array is in a degraded state (Mismatched disk(s) found).

3009 ibRAIDRebuildingMismatch The system's RAID array is rebuilding (Mismatched disk(s) found).

3010 ibRAIDBatteryWeak Please replace the system's RAID battery soon.

3011 ibRAIDIsDegradedDisk1 The system's RAID array is in a degraded state. RAID Disk1 is EMPTY. 3012 ibRAIDIsDegradedDisk2 The system's RAID array is in a degraded state. RAID Disk2 is EMPTY. 3013 ibRAIDIsDegradedDisk3 The system's RAID array is in a degraded state. RAID Disk3 is EMPTY. 3014 ibRAIDIsDegradedDisk4 The system's RAID array is in a degraded state. RAID Disk4 is EMPTY. 3015 ibRAIDIsDegradedDisk5 The system's RAID array is in a degraded state. RAID Disk5 is EMPTY. 3016 ibRAIDIsDegradedDisk6 The system's RAID array is in a degraded state. RAID Disk6 is EMPTY. 3017 ibRAIDIsDegradedDisk7 The system's RAID array is in a degraded state. RAID Disk7 is EMPTY. 3018 ibRAIDIsDegradedDisk8 The system's RAID array is in a degraded state. RAID Disk8 is EMPTY. 3019 ibRAIDIsRebuildingDisk1 The system's RAID array is rebuilding. RAID Disk1 is OFFLINE. 3020 ibRAIDIsRebuildingDisk2 The system's RAID array is rebuilding. RAID Disk2 is OFFLINE. 3021 ibRAIDIsRebuildingDisk3 The system's RAID array is rebuilding. RAID Disk3 is OFFLINE. 3022 ibRAIDIsRebuildingDisk4 The system's RAID array is rebuilding. RAID Disk4 is OFFLINE. 3023 ibRAIDIsRebuildingDisk5 The system's RAID array is rebuilding. RAID Disk5 is OFFLINE. 3024 ibRAIDIsRebuildingDisk6 The system's RAID array is rebuilding. RAID Disk6 is OFFLINE. 3025 ibRAIDIsRebuildingDisk7 The system's RAID array is rebuilding. RAID Disk7 is OFFLINE. 3026 ibRAIDIsRebuildingDisk8 The system's RAID array is rebuilding. RAID Disk8 is OFFLINE.

3027 ibRAIDDegradedMismatchDisk1 The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk1 is EMPTY.

(13)

EMPTY.

3035 ibRAIDRebuildingMismatchDisk1 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk1 is OFFLINE. 3036 ibRAIDRebuildingMismatchDisk2 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk2 is OFFLINE. 3037 ibRAIDRebuildingMismatchDisk3 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk3 is OFFLINE. 3038 ibRAIDRebuildingMismatchDisk4 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk4 is OFFLINE. 3039 ibRAIDRebuildingMismatchDisk5 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk5 is OFFLINE. 3040 ibRAIDRebuildingMismatchDisk6 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk6 is OFFLINE. 3041 ibRAIDRebuildingMismatchDisk7 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk7 is OFFLINE. 3042 ibRAIDRebuildingMismatchDisk8 The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk8 is OFFLINE.

3043 ibRAIDIsInoperable The system’s RAID array is inoperable.

3044 ibRAIDPredictedDegraded The system's RAID array is in a predicted degraded state.

3045 ibRAIDPredictedDegradedDisk1 The system's RAID array is in a predicted degraded state. RAID Disk1 is in such predicted degraded state.

4001 ibDisconnectGridAttachFailed A disconnected Grid failed to attach to the Master Grid. 4002 ibDisconnectedGridDetachFailed A disconnected Grid failed to detach from the Master Grid. 4003 ibDisconnectedGridDetachFailedSubgrid

Offline

An offline Grid failed to detach from the Master Grid.

4004 ibDisconnectedGridSnapshotFailed The snapshot operation failed on a disconnected Grid.

4005 ibDnssecAutomaticKSKRolloverApproching An automatic rollover of the KSK will be performed in seven days. 4006 ibDnssecManualKSKRolloverDueApprochi

ng

A manual KSK rollover is due within the next seven days.

4007 ibDnssecAutomaticKSKRolloverDone The KSK has been automatically rolled over. 4008 ibDnssecManualKSKRolloverDone The KSK has been manually rolled over.

4009 ibDnssecKSKRolloverOverdue The KSK rollover is overdue.

4010 ibPortDiscoveryConflict A port detection conflict has been detected. 4011 ibDeviceDiscoveryConflict A device detection conflict has been detected.

(14)

4013 ibAnalyticsDnstUpdate The DNS tunneling detection has occurred.

4014 ibSyslogBackupDone The syslog backup process is successful.

4015 ibSyslogBackupFailed The syslog backup process failed.

ibSubsystemName Values (OID 3.1.1.1.2.5.0)

The below table lists the values that are associated with the object ibSubsystemName (OID 3.1.1.1.2.5.0). These values provide information about the subsystems that trigger the traps.

ibSubsystemName Values

Value OID 3.1.1.1.2.5.0 ibSubsystemName

(15)

50 ifmap 51 captive_portal 53 BGP 58 GUI_Login 72 Reporting_task 84 OSPF6 95 Discovery_backups 105 Unbounds - HA_Replication - HSM Group Status - Cluster - Cluster_Send_Queue - Cluster_Recv_Queue - RPZHitRate

- Authentication Server Group

ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0)

The ibPreviousState object indicates the state of the appliance before the event triggered the trap. The ibCurrentState object indicates the current state of the appliance. The following table shows the message and description of each state:

Table 39.8 ibPreviousState and ibCurrentState Values

Value Description Definition

1 ha-active The HA pair is in ACTIVE state.

2 ha-passive The HA pair is in PASSIVE state.

3 ha-initial The HA pair is in INITIAL state.

4 Grid-connected The Grid member is connected to the Grid Master.

5 Grid-disconnected The Grid member is not connected to the Grid Master.

12 service-down The service is down.

13 ha-replication-online The HA pair replication is online.

14 ha-replication-offline The HA pair replication is offline.

15 ntp-syn-up The NTP server is synchronizing.

16 ntp-syn-down The NTP server is out of synchronization.

17 ms-server-up Microsoft server is up.

18 ms-server-down Microsoft server is down.

19 ms-service-up Microsoft service connection is active.

20 ms-service-down Microsoft service connection is inactive.

21 nac-server-group-down NAC Authentication server group is down.

22 nac-server-group-up NAC Authentication server group is up.

23 mgm-service-up MGM service is active.

24 mgm-service-down MGM service is inactive.

25 ha-active-active HA Pair is in Dual Active state.

(16)

27 ftp-service-failed FTP service failed.

28 ftp-service-inactive FTP service is inactive.

29 tftp-service-working TFTP service is working.

30 tftp-service-failed TFTP service failed.

31 tftp-service-inactive TFTP service is inactive.

32 dns-service-working DNS service is working.

33 dns-service-failed DNS service failed. Review the syslog file.

34 dns-service-inactive DNS service is inactive. Check if an administrator disabled the service.

35 ntp-service-working NTP service is working.

36 ntp-service-failed NTP service failed.

37 ntp-service-inactive NTP service is inactive.

38 http-file-dist-service-working HTTP File Dist service is working.

39 http-file-dist-service-failed HTTP File Dist service failed.

40 http-file-dist-service-inactive HTTP File Dist service is inactive.

41 bloxtools-service-working bloxTools service is working.

42 bloxtools-service-warning bloxTools service is in warning state.

43 bloxtools-service-failed bloxTools service failed.

44 bloxtools-service-inactive bloxTools service is inactive.

45 dhcp-service-working DHCP service is working. No action required.

46 dhcp-service-warning DHCP service is in warning state. Review the syslog file.

47 dhcp-service-failed DHCP service failed. Review the syslog file.

48 dhcp-service-inactive DHCP service is inactive. Check if an administrator disabled the service.

49 captive-portal-service-working Captive portal service is working.

50 captive-portal-service-failed Captive portal service failed.

51 captive-portal-service-inactive Captive portal service inactive.

52 ifmap-service-working IF-MAP service is working.

53 ifmap-service-failed IF-MAP service failed.

54 ifmap-service-inactive IF-MAP service inactive.

56 hsm-group-down HSM operation failed.

57 hsm-group-up HSM operation succeeded.

59 reporting-service-working Reporting service is working.

60 reporting-service-failed Reporting service failed.

61 reporting-service-inactive Reporting service inactive.

62 dns-cache-acceleration-working DNS cache acceleration is working.

63 dns-cache-acceleration-failed DNS cache acceleration failed.

64 dns-cache-acceleration-inactive DNS cache acceleration is inactive.

65 ocsp-responders-ok All OCSP responders are available.

66 ocsp-responder-failed At least one OCSP responder has become unavailable.

67 ocsp-responders-unavailable All OCSP responders are out of service.

68 cas-inactive Certificate authentication service is inactive.

(17)

70 subgrid-detached In a Multi-Grid configuration, sub Grid is detached from the Master Grid. 71 snapshot-disabled In a Multi-Grid configuration, the snapshot of the Grid's current state is disabled. 72 snapshot-enabled In a Multi-Grid configuration, the snapshot of the Grid's current state is enabled.

73 lb-device-up Load balancer device is working.

74 lb-device-down Load balancer device is down.

76 ldap-servers-ok All LDAP servers are available.

77 ldap-server-failure At least one LDAP server is unavailable.

78 ldap-servers-unavailable All LDAP servers are unavailable.

79 ldap-service-inactive LDAP service is inactive.

80 sgm-state-online SGM is online.

81 sgm-state-offline SGM is offline.

82 discovery-consolidator-service-working Service on discovery the consolidator for Network Insight is working. 83 discovery-consolidator-service-warning Service on discovery the consolidator for Network Insight is in warning state. 84 discovery-consolidator-service-failed Service on discovery the consolidator for Network Insight failed.

85 discovery-consolidator-service-inactive Service on discovery the consolidator for Network Insight is inactive. 86 discovery-collector-service-working Service on discovery probes for Network Insight is working. 87 discovery-collector-service-warning Service on discovery probes for Network Insight is in warning state. 88 discovery-collector-service-failed Service on discovery probes for Network Insight failed.

89 discovery-collector-service-inactive Service on discovery probes for Network Insight is inactive. 90 threat-protection-service-working Threat protection service for Infoblox DNS Protection is working. 91 threat-protection-service-warning Threat protection service for Infoblox DNS Protection is in warning state. 92 threat-protection-service-failed Threat protection service for Infoblox DNS Protection failed.

93 threat-protection-service inactive Threat protection service for Infoblox DNS Protection is inactive.

94 mgm-external-storage-disabled MGM external storage is disabled.

95 dns-integrity-check-failed DNS Integrity check for authoritative zones failed. 96 dns-integrity-check-working DNS Integrity check for authoritative zones is working. 97 dns-integrity-check-severity-indetermined DNS Integrity check severity is None.

98 dns-integrity-check-severity-normal DNS Integrity check severity is NORMAL. 99 dns-integrity-check-severity-informational DNS Integrity check severity is INFORMATIONAL. 100 dns-integrity-check-severity-warning DNS Integrity check severity is WARNING. 101 dns-integrity-check-severity-severe DNS Integrity check severity is SEVERE. 102 dns-integrity-check-severity-critical DNS Integrity check severity is CRITICAL.

103 cloud-api-service-working Cloud API service is working.

104 cloud-api-service-failed Cloud API service failed.

105 cloud-api-service-inactive Could API service is inactive.

106 dns-service-dtc-failed DNS sub-feature DNS Traffic Control failed.

107 raid-status-is-unavailable RAID hardware status is unavailable.

108 raid-status-is-available RAID hardware status is available again.

109 ipmi-device-warning IPMI device is not available.

110 ipmi-device-unavailable IPMI device repeatedly is not available.

(18)

112 rpz-refresh-working RPZ refresh is working.

113 rpz-refresh-failed RPZ refresh failed.

114 rpz-refresh-unknown RPZ refresh unknown.

115 dns-attack-active DNS attack is active.

116 dns-attack-inactive DNS attack is inactive.

117 high-rpz-hit-rate RPZ hit rate exceeds the normal value.

118 normal-rpz-hit-rate RPZ hit rate has returned to normal value.

119 taxii-working TAXII server is working.

120 taxii-warning TAXII server is warning.

121 taxii-failed TAXII server is failed.

122 taxii-inactive TAXII server is inactive.

123 cisco-ise-server-up Cisco ISE server is connected.

124 cisco-ise-server-down Cisco ISE server is not connected.

125 threat-analytics-service-inactive Threat Analytics service is inactive. 126 threat-analytics-service-working Threat Analytics service is working. 127 threat-analytics-service-warning Threat Analytics service is in warning state. 128 threat-analytics-service-failed Threat Analytics Service is failed.

129 reporting-service-warning Reporting Service is warning.

130 outbound-service-manager-started OUTBOUND Service Manager started.

131 outbound-service-manager-stopped OUTBOUND Service Manager is inactive.

132 outbound-service-manager-failed OUTBOUND Service Manager is failed.

133 imc-servers-ok Subscriber Collection Service is working.

134 imc-server-failure Subscriber Collection Service failed.

135 imc-servers-unavailable All NAS gateways are unavailable.

136 imc-service-inactive Subscriber Collection Service is inactive.

137 imc-zvelo-service-unavailable Initial category information data is downloading. 138 imc-server-initializing Initial Subscriber Collection service interim interval. 139 dns-service-working-atc-fwd-down DNS Service is working but ATC forwarding is down.

140 dfp-service-working DFP service is working.

141 dfp-service-failed DFP service is failed.

142 dfp-service-inactive DFP service is disabled.

143 dfp-service-stopped DFP service stopped by user.

The Grid member running Subscriber Collection Service has a default state of 136 (imc-service-inactive). When Subscriber Collection Service is enabled, it goes to the 138 (imc-server-initializing) state. That is, the service will be enabled, but not fully populated until the interim interval expires. Once the interim interval expires, it transitions to the 133 (imc-servers-ok) state unless parental control is enabled. If parental control is enabled, the state changes to 137 (im

) until the category data is downloaded. Then, it goes to state 133 (

c-zvelo-service-unavailable imc-servers-ok). If the collector service is not running, it

transitions to state 134 (imc-server-failure).

Trap 136 implies that subscriber collection is not active. Trap 134 implies that the collector is not running. If the monitor is disabled, then trap 136 (imc-service-inactive) is triggered.

Note

(19)

ibTrapDesc (OID 3.1.1.1.2.11.0)

The ibTrapDesc object lists the trap messages of all Infoblox SNMP traps. This section lists all the SNMP traps by their trap types. Each trap table describes the trap message, severity, cause, and recommended actions.

lEquipment Failure Traps

ibTrapDesc OID 3.1.1.1.2.11.0

ibTrapSeverity

OID 3.1.1.1.2.2 Description/Cause Recommended Actions

Primary Drive Full

Primary drive is full. Major The primary disk drive reached 100% of usage. Review the syslog file to identify the possible cause of this problem. Fan Monitoring

Fan <n> failure has occurred. Minor The specified fan <n> failed, where <n> indicates the fan number.

Inspect the specified fan for mechanical or electrical problems.

Fan <n> is OK. Informational The specified fan <n> is functioning properly, where <n> indicates the fan number.

No action is required.

Power Supply Failure: monitored at 1 minute

A power supply failure has occurred. Major The power supply failed. Inspect the power supply for the possible cause of the failure. Power supply <n> failure has occurred. Major The specified power supply <n> failed, where <n> indicates the

power supply number.

Inspect the specified power supply for the possible cause of the failure. The power supply is OK. Informational The power supply is functioning properly. No action is required.

Power supply <n> is OK. Informational The specified power supply <n> is functioning properly, where <n> indicates the power supply number.

RAID monitoring, at 1 minute intervals

A RAID battery failure has occurred. Major The system RAID battery failed. The alert light is red. Inspect the battery for the possible cause of the failure.

The system's RAID battery is OK. Informational The system RAID battery is charging and functioning properly. The alert light changed from red to green.

Unable to retrieve RAID array state! Undetermined The appliance failed to retrieve the RAID array state. The alert light is red.

Review the syslog file to identify the possible cause of this problem. The system's RAID array is now running

in an optimal state.

Informational The RAID system is functioning at an optimal state. No action is required.

The system's RAID array is in a degraded state. RAID Disk <n> is EMPTY.

Major The RAID system is degrading. The specified RAID Disk <n> is empty, where <n> indicates the RAID disk number.

Review the syslog file to identify the possible cause of this problem.

The system's RAID array is rebuilding. RAID Disk <n> is OFFLINE.

Minor The RAID system is rebuilding. The specified RAID Disk <n> is offline, where <n> indicates the RAID disk number.

Syslog Backup Processes The syslog backup process is successful.

Informational Rotated syslog files are uploaded successfully to the external backup server.

The syslog backup process failed. Major Failed to forward the rotated syslog files to the external backup server.

Review the syslog messages to identify the possible cause of this problem.

Processing and Software Failure Traps

The ibSubsystemName object is associated with certain traps of the Processing and Software Failure traps. Therefore, you cannot map all the traps of the Processing and Software Failure traps with the ibSubsystemName. If there is no value in the ibSubsystemName, then it belongs to the N/A category. For more information on the values for the ibSubsystemName, see the ibSubsystemName Values table..

Named Daemon Failure

A named daemon monitoring failure has occurred. The named process failed. Note

(20)

1. 2. Critic

al

DHCP Daemon Failure

A DHCP daemon monitoring failure has occurred. Critic al

The dhcpd process failed. Review the syslog file to identify the possible cause of this problem.

SSH Daemon Failure

An SSH daemon failure has occurred. Major The sshd process failed. Review the syslog file to identify the possible cause of this problem.

NTP Daemon Failure, monitored every 10 minutes

An NTP daemon failure has occurred. Major The ntpd process failed. Review the syslog file to identify the possible cause of this problem.

Cluster Daemon Failure

A grid daemon failure has occurred. Critic al

The clusterd process failed. Review the syslog file to identify the possible cause of this problem.

LCD Daemon Failure

An LCD failure has occurred. Major The LCD process failed. The alert light is

yellow. Inspect the LCD panel for the possible cause of this problem.

Apache Software httpd failure, monitored every 2 minutes An Apache software failure has occurred. Critic

al

The request to monitor the Apache server failed.

Serial Console Failure

An Infoblox serial console software failure has occurred.

Major The Infoblox serial console failed. Review the syslog file to identify the possible cause of this problem.

Controld Software Failure

A controld failure has occurred. Critic al

The controld process failed. Review the syslog file to identify the possible cause of this problem.

SNMP Sub-agent Failure

An SNMP server failure has occurred. Major The one-subagent process failed. Review the syslog file to identify the possible cause of this problem.

TFTPD and FTPD Failure

A TFTPD daemon failure has occurred. Critic al

The tftpd process failed. Review the syslog file to identify the possible cause of this problem.

An FTPD daemon failure has occurred. Critic al

The ftpd process failed. Review the syslog file to identify the possible cause of this problem.

HTTP File Distribution, monitored at 10 second intervals An HTTP file distribution daemon failure has occurred. Critic

al

The HTTP file distribution process failed. Review the syslog file to identify the possible cause of this problem.

DNS ONE quagga Processes (zebra & ospfd)

An OSPF routing daemon failure has occurred. Critic al

Either the zebra process or the ospfd process failed. Both the zebra and ospfd process belongs to ospf subsystem.

Backup Failure

Backup failed. Minor The backup failed.

One of the following could be the cause of the failure:

The appliance could not access a backup directory.

The backup was interrupted by one of the following signals: SIGINT, SIGHUP, or SIGTERM.

Incorrect login or connection failure in an FTP backup.

The backup failed to create temporary files.

Database Backup Failure

Database backup failed. Not

impl

(21)

eme nted Backup Module Failure

Module backup failed. Not

impl eme nted

The backup of product- specific files failed. Review the syslog file to identify the possible cause of this problem.

Backup File Size Exceeded

File size exceeded the quota. Backup failed. Not impl eme nted

The backup failed because the file size exceeded the limit of 5GB.

Limit the size of the backup file to less than 5GB.

Another backup is in progress. Backup will not be performed.

Not impl eme nted

The backup failed because of an attempt to back up or merge files while another backup or restore was in progress.

Wait until the backup or restore is complete before starting another backup.

Watchdog Process Monitoring WATCHDOG:

failed on <registered client name> <server IP address>.

Critic al

The watchdog process detected a registered client failure on a specific server.

The <registered client name> could be one of the following: Clusterd _timeout DB_Sentinel Process_Manager Clusterd_monitor Disk_monitor

Microsoft Server Microsoft server

has failed. <hostname>/<IP address>

Major The Microsoft server could not be reached. Check that the Microsoft server is connected to the network and configured properly.

Microsoft server is OK. <hostname>/<IP address> Infor mati onal

The Microsoft server can be reached and is functioning properly.

Microsoft DNS/DHCP Service

Service connection to Microsoft DNS server has failed. <hostname>/<IP address>

Major The Microsoft DNS service is not responding. Check that the DNS service is configured and running on the Microsoft server.

Service connection to Microsoft DHCP server has failed. <hostname>/<IP address>

Major The Microsoft DHCP service is not responding.

Check that the DHCP service is configured and running on the Microsoft server.

Service connection to Microsoft DNS server is OK. <hostname>/<IP address>

Infor mati onal

The Microsoft DNS service is responding. No action is required.

Service connection to Microsoft DHCP server is OK.

<hostname>/<IP address>

Infor mati onal

The Microsoft DHCP service is responding. No action is required.

NAC Authentication Server Group

NAC Authentication server group is down. Major None of the servers in the NAC

authentication server group can be reached.

Review the syslog.

NAC Authentication server group is up. Infor mati onal

The NAC authentication server group is responding.

GUI Login

A GUI login failure has occurred. Major An admin failed to log in to the GUI. Check the credentials of the admin. Serial Console Login

A Serial Console login failure has occurred. Major An admin failed to log in through the serial console.

Check the credentials and permissions, and check that the serial console is enabled.

Reboot

The system is rebooting. Infor

mati onal

A system reboot command was sent. No action is required.

DHCP Lease Conflict

DHCP address conflicts with an existing lease. Major The discovery process found a DHCP lease conflict.

In the IP Map or List panel, select a conflicting address, and then click Resolve Conflict. For more information, see ResolvingDHCPLease Conflicts.

(22)

DHCP address conflicts with an existing fixed address. Major The discovery process found a fixed address conflict.

In the IP Map or List panel, select a conflicting address, and then click Resolve Conflict. For more information, see ResolvingFixedAddress Conflicts.

DHCP Range Conflict

DHCP address conflicts with an existing range. Major The discovery process found a conflict with an existing range.

In the IP Map or List panel, select a conflicting address, and then click Resolve Conflict. For more information, see Resolving DHCPRange Conflicts.

DHCP Host Conflict

DHCP address conflicts with an existing host address. Major The discovery process found a conflict with an existing host address.

In the IP Map or List panel, select a conflicting address, and then click Resolve Conflict. For more information, see ResolvingHost Conflicts.

DNS Health Check Monitor

DNS Health Check query failed. Major DNS Health Check query has failed. Review the syslog file to identify the possible cause of this problem.

DNS Health Check query has succeeded Infor mati onal

DNS Health Check query has succeeded. No action required.

Syslog Daemon Failure

Syslog daemon is not running. Critic al

Syslog process stopped. Review the syslog file to identify the possible cause of this problem.

BFD Daemon Failure

An BFD daemon failure has occurred. Major BFD has failed to detect failure in the bidirectional path between two interfaces.

Process Stop/Start

The system stopped and started a process. Major The system restarted a process. Review the syslog file to identify the possible cause of this problem.

Zone Transfer Failed

A zone transfer failure has occurred. Major A zone transfer failed. Review the syslog file to identify the possible cause of this problem.

RPZ Refresh Failed

RPZ refresh failure has occurred. Critic al

An RPZ refresh has failed. The appliance sends this trap only when RPZ refresh from all the configured primary servers fail.

Unbound Software Failed

An unbound daemon monitoring failure has occurred. Major Unbound software failure has occurred. Review the syslog file to identify the possible cause of this problem.

Threat Analytics Service Failed

Threat Analytics Auto Download has failed. Major Auto download for Threat Analytics has failed. Review the syslog file to identify the possible cause of this problem.

Outbound Service Failed

The Outbound worker failed. Major The Outbound service failure has occurred. Review the syslog file to identify the possible cause of this problem.

Clear

SNMP Trap is cleared. LCD failure. N/A The SNMP Trap for LCD failure is cleared. No action is required. SNMP Trap is cleared. Serial Console. N/A The SNMP Trap for Serial Console is cleared. No action is required. SNMP Trap is cleared. ControlD failure. N/A The SNMP Trap for ControlD failure is

cleared.

SNMP Trap is cleared. GUI Login. N/A The SNMP Trap for GUI Login is cleared. No action is required. SNMP Trap is cleared. Serial Console Login. N/A The SNMP Trap for Serial Console Login is

cleared.

SNMP Trap is cleared. SSHD failure. N/A The SNMP Trap for SSHD failure is cleared. No action is required. SNMP Trap is cleared. LDAP servers. N/A The SNMP Trap for LDAP server is cleared. No action is required. SNMP Trap is cleared. OCSP Responders. N/A The SNMP Trap for OCSP Responders is

cleared.

(23)

SNMP Trap is cleared. HSM N/A The SNMP Trap for HSM is cleared. No action is required. SNMP Trap is cleared. HTTP N/A The SNMP Trap for HTTP is cleared. No action is required. SNMP Trap is cleared. Cluster N/A The SNMP Trap for Cluster is cleared. No action is required. SNMP Trap is cleared. DuplicateIP N/A The SNMP Trap for Duplicate IP is cleared. No action is required. Restart

The system is being restarted. Infor mati onal

A system restart command was sent. No action is required.

DNS Integrity Check

Cannot perform DNS Integrity Check because the appliance is unable to connect to the external DNS server. There are list of nameservers failure: <IP addresses>

N/A The DNS integrity check cannot be performed because the appliance is unable to connect to the external DNS server.

Threshold Crossing Traps

ibTrapDesc

OID 3.1.1.1.2.11.0 ibTrapSeverity

ibObjectName OID 3.1.1.1.2.3.0

Description/Cause Recommended Actions

System Memory Usage

System has run out of memory. Major memory The appliance ran out of memory.

The appliance encountered this problem when one of the following occurred:

The total free memory on the appliance was less than or equal to 0%.

The total physical memory was less than the total free memory. The percentage of free memory compared to the total physical memory was less than 5%, and the free swap percentage was less than 80%.

The percentage of free memory compared to the total physical memory was less than 5%, plus the numbers of both swap INs and swap OUTs were greater than or equal to 3,200. The percentage of free memory compared to the total physical memory was between 5% and 10%, the free swap percentage was greater than or equal to 80%, plus the numbers of both swap INs and swap OUTs were greater than or equal to 3,200. The percentage of free memory compared to the total physical memory was greater than 10%, the free swap percentage was less than 80%, plus the numbers of both swap INs and swap OUTs were greater than or equal to 3,200.

: Free memory = free physical RAM + free cache buffers.

Note

The high threshold for swap pages is 3,200.

System memory usage exceeds the critical threshold value.

Minor memory The memory usage on the appliance exceeded the configured Trigger value. For more information, see Defining Thresholds for Traps

.

The appliance encountered this problem when one of the following occurred:

The percentage of free memory compared to the total physical memory was less than 5%, and the free swap percentage was less than 90%.

The percentage of free memory compared to the total physical memory was less than 5%, plus the number of swap INs was less than 3,200 and the number of swap OUTs was greater than or equal to 3,200.

The percentage of free memory compared to the total physical memory was between 5% and 10%, and the free swap percentage was less than 80%.

The percentage of free memory compared to the total physical memory was greater than 5%, plus the number of swap INs was less than 3,200 and the number of swap OUTs was greater than or equal to 3,200.

: Free memory = free physical RAM + free cache buffers.

Note

The high threshold for swap pages is 3,200.

System memory usage is OK. Minor memory The memory usage on the system is at or below the Reset value after it went above the Trigger value.

Primary Hard Drive Usage (monitored every 30 seconds)

System primary hard disk usage is over threshold value.

(24)

The appliance sends this trap when primary hard disk usage first exceeds the configured Trigger value. The default value is 85. The alert light is yellow.

For more information, see Defining Thresholds for Traps.

Primary drive is full. Major disk_usage The primary hard disk usage exceeded 95%. The alert light is red. Review the syslog file to identify the possible cause of this problem.

Primary drive usage is OK. Minor disk_usage The appliance sends this trap when the primary hard disk usage first moves at or below the configured Reset value after it exceeded the Trigger value. The default is 70. The alert light is green.

CPU Usage

CPU usage above threshold value. Major cpu_usage CPU usage exceeded the Trigger value for 15 seconds. For more information, see Defining Thresholds for Traps.

Monitor CPU usage. CPU usage OK. Minor cpu_usage CPU usage dipped below the reset value after the "CPU usage above

threshold value" trap was sent.

Note: Use the CLI command set thresholdtrap to enable the CPU usage trap and configure the trigger and reset values. For information, refer to the Infoblox CLI Guide.

Swap Usage

System swap space usage exceeds the critical threshold value.

Major swap_usage System swap space usage exceeded the Trigger value. For more information, see Defining Thresholdsfor Traps.

Monitor System swap usage. System swap space usage is OK. Minor swap_usage System swap space usage dipped below the reset value after it

exceeded the Trigger value.

Replication Statistics Monitoring

Grid queue replication problem. N/A For send trap: Cluster_Send_ Queue For receive trap: Cluster_Recv_ Queue

The system encountered this problem when all of the following conditions occurred:

The node was online.

The number of the replication queue being sent from the master column was greater than 0, or the number of the queue received was greater than 0.

It was more than 10 minutes since the last replication queue was sent and monitored.

DHCP Range Threshold Crossing

DHCP high threshold crossed: Member:

<DHCP server node VIP>

Network:

<network>/ <network view>

Range: <DHCP range>/ <network view>

High Trigger Mark:

<high percentage>

(95% by default) High Reset Mark:

<reset

(80% by default)

percentage>

Current Usage:

<current usage percentage>

Active Leases:

<number of active leases>

Available Leases:

<number of available leases>

Total Addresses:

<total addresses>

N/A Threshold The system encountered this problem when the address usage in the DHCP range is greater than the configured High Trigger value.

DHCP high threshold reset: Member:

<DHCP server node VIP>

Network:

Range: <DHCP range>/<network view>

High Trigger Mark:

<high percentage>

(95% by default) High Reset Mark:

<reset

(80% by default)

percentage>

Current Usage:

<current usage percentage>

Active Leases:

<number of active leases>

Available Leases:

<number of available leases>

Total Addresses:

<total addresses>

N/A Threshold The system encountered this problem when the address usage in the DHCP range goes below the Reset value after it hit the Trigger value.

IPAM Utilization Threshold Crossing

Network IPAM Utilization capacity usage is over the threshold value. Network:

N/A Threshold The appliance sends this trap when the IPAM utilization for a network is above the configured Trigger value.

Network Container IPAM Utilization capacity usage is over the threshold value. Network container:

N/A Threshold The appliance sends this trap when the IPAM utilization for a network container is above the configured Trigger value.

Network IPAM Utilization capacity usage is OK. Network: