Page tree

Contents

You can configure the appliance as an SNMP-managed device so that an SNMP management station can send queries to the appliance and retrieve information from its MIBs. Note that you can download all Infoblox MIBs from Multi-Grid Manager, including MIBs that are specific to DNS and DHCP operations. Perform the following tasks to access the Infoblox MIBs:

  1. Configure the appliance to accept queries, as described in Configuring SNMPv3 Users.
  2. Load the MIB files onto the management system. To obtain the latest Infoblox MIB files:
    1. From the Master Grid tab, select the Members tab -> master_grid_member check box, and then select Download -> SNMP MIBs from the Toolbar.
    2. In the Save As dialog box, navigate to a directory to which you want to save the MIBs.
    3. Click Save.
  3. Use a MIB browser or SNMP management application to query the objects in each MIB.

The 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:

  1. IB-SMI-MIB.txt
  2. IB-TRAP-MIB.txt
  3. IB-PLATFORMONE-MIB.txt
  4. IB-DNSONE-MIB.txt
  5. IB-DHCPONE-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

Infoblox 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 probably, you must download the following NET-SNMP MIBs directly from http://net-snmp.sourceforge.net/docs/mibs/:

  • NET-SNMP-MIB
  • UCD-SNMP-MIB

Note: Ensure that you save the MIBs as text files in the directory to which you save all the other MIB files.


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 RFC4273 Definitions of Managed Objects for BGP-4. You must enable and configure the SNMP trap receiver on the Multi-Grid member for the member to send SNMP traps. For information, see SNMP MIB Hierarchy.
The BGP protocol service is configured to send SNMP queries about BGP runtime data. The information is returned using the following OIDs and definitions:

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

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

OIDDefinition
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.2State: 0=down, 1=up
1.3.6.1.2.1.15.900.1.9.a.b.c.d.3ASN
1.3.6.1.2.1.15.900.1.9.a.b.c.d.4Prefixes
1.3.6.1.2.1.15.900.1.9.a.b.c.d.5Up/Down time

ibTrap MIB

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


Note: OIDs shown in the illustrations and tables in this section do not include the prefix .1.3.6.1.4.1.7779.


The ibTrap MIB comprises two trees, ibTrapOneModule and ibNotificationVarBind. The ibTraponeModule tree contains objects for the types of traps that the 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.

Figure 11.3 ibTrapOne MIB Structure

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 the 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. For information, see ibTrapDesc (OID 3.1.1.1.2.11.0) .
You can interpret the sample trap as follows:
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: "10.35.1.156" SNMPv2-SMI::enterprises." tells you the IP address of the appliance on which the trap occurred.
  • 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 appliance can send. There are five types of SNMP traps.
Table 11.2 describe the types of traps and their objects in the ibTrapOneModule tree.

Table 11.2 ibTrapOneModule


OID

Trap Type

MIB Object

Description

3.1.1.1.1.1.0

Equipment Failure

ibEquipmentFailureTrap

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

  • ibNodeName
  • ibTrapSevertiy
  • ibObjectName (equipment name)
  • ibProbableCause
  • ibTrapDesc
    For a list of trap descriptions, see Equipment Failure Traps.

3.1.1.1.1.2.0

Processing and Software Failure

ibProcessingFailureTrap

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

3.1.1.1.1.3.0

Threshold Crossing

ibThresholdCrossingEvent

The appliance generates this trap when any of the following events occur:

  • System memory or disk usage exceeds 90%.
  • A problem occurs when the Grid Master replicates its database to its Grid members.
  • DHCP address usage crosses a watermark threshold. For more information about tracking IP address usage, see Chapter 7, Network Management.
  • 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
  • ibObjectName (threshold name)
  • ibCurThresholdvalue
  • ibThresholdHigh
  • ibThresholdLow
  • ibTrapDesc
    For a list of trap descriptions, see Threshold Crossing Traps.

3.1.1.1.1.4.0

Object State Change

ibStateChangeEvent

The 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
  • ibObjectName
  • ibPreviousState
  • ibCurrentState
  • ibTrapDesc
    For a list of possible trap descriptions, see Object State Change Traps.

3.1.1.1.1.5.0

Process Started and Stopped

ibProcStartStopTrap

The 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
    For a list of possible trap descriptions, see Process Started and Stopped Traps.

Trap Binding Variables (OID 3.1.1.1.2)

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. Table 11.3 describes the objects in the ibNotificationVarBind module.

Table 11.3 ibNotificationVarBind (OID 3.1.1.1.2)


Note: The OIDs shown in the following table do not include the prefix ".1.3.6.1.4.1.7779.".


OID

MIB Object (Type)

Description

3.1.1.1.2.1.0

ibNodeName (DisplayString)

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

ibTrapSeverity (Integer)

The severity of the trap. There are five levels of severity. See Trap Severity (OID 3.1.1.1.2.2.0) for details.

3.1.1.1.2.3.0

ibObjectName (DisplayString)

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

ibProbableCause (Integer)

3.1.1.1.2.5.0

ibSubsystemName (DisplayString)

The subsystem for which the trap was generated, such as NTP or SNMP. This object is used in the Processing and Software Failure traps and the Process Start and Stop traps. See ibSubsystemName Values (OID 3.1.1.1.2.9.0) for definitions.

3.1.1.1.2.6.0

ibCurThresholdValue (Integer)

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

3.1.1.1.2.7.0

ibThresholdHigh (Integer)

The value for 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. This object is used in Threshold Crossing traps.

3.1.1.1.2.8.0

ibThresholdLow (Integer)

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. This object is used in Threshold Crossing traps. For additional information, see BGP4 MIB.

3.1.1.1.2.9.0

ibPreviousState (Integer)

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

3.1.1.1.2.10.0

ibCurrentState (Integer)

The current state of the appliance. This object is used in the Object State Change traps. See ibPreviousState (OID 3.1.1.1.2.9.0) and ibCurrentState (OID 3.1.1.1.2.10.0) for the definition of each value.

3.1.1.1.2.11.0

ibTrapDesc (DisplayString)

The description of the trap. This object is used in all types of traps. See ibTrapDesc (OID 3.1.1.1.2.11.0) 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

Undetermined

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)

Table 11.5 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 software failures, that trigger traps.

Table 11.4 ibProbableCause Values

ValueOID 3.1.1.2.4.0
ibProbableCause
0ibClear
1ibUnknown
2ibPrimaryDiskFailure
3ibFanFailure-old
4ibPowerSupplyFailure
5ibDBFailure
6ibApacheSoftwareFailure
7ibSerialConsoleFailure
11ibControldSoftwareFailure
12ibUpgradeFailure
13ibSNMPDFailure
15ibSSHDSoftwareFailure
16ibNTPDSoftwareFailure
17ibClusterdSoftwareFailure
18ibLCDSoftwareFailure
19ibDHCPdSoftwareFailure
20ibNamedSoftwareFailure
21ibAuthServerGroupDown
22ibAuthServerGroupUp
24ibNTLMSoftwareFailure
25ibNetBIOSDaemonFailure
26ibWindowBindDaemonFailure
27ibTFTPDSoftwareFailure
29ibBackupSoftwareFailure
30

ibBackupDatabaseSoftwareFailure

31ibBackupModuleSoftwareFailure
32ibBackupSizeSoftwareFailure
33ibBackupLockSoftwareFailure
34ibHTTPFileDistSoftwareFailure
35ibOSPFSoftwareFailure
36ibAuthDHCPNamedSoftwareFailure
37ibFan1Failure
38ibFan2Failure
39ibFan3Failure
40

ibFan1OK

41ibFan2OK
42ibFan3OK
44ibFTPDSoftwareFailure
46ibPowerSupplyOK
47ibWebUISoftwareFailure
49ibADAgentSyncFailure
50ibIFMAPSoftwareFailure
51ibCaptivePortalSoftwareFailure
52ibDuplicateIPAddressFailure
53ibBGPSoftwareFailure
54ibRevokedLicense
2029ibHSMGroupFailure
2030ibHSMGroupOK
3001ibRAIDIsOptimal
3002ibRAIDIsDegraded
3003ibRAIDIsRebuilding
3004ibRAIDStatusUnknown
3005ibRAIDBatteryIsOK
3006ibRAIDBatteryFailed

ibSubsystemName Values (OID 3.1.1.1.2.9.0)

Table 11.5 lists the values that are associated with the object ibSubsystemName (OID 3.1.1.1.2.9.0). These values provide information about the subsystems that trigger the traps.

Table 11.5 ibSubsystemName Values

Value

OID 3.1.1.1.2.9.0

ibSubsystemName

0Uses the original ibObjectName and ibSubsystemName when the trap is cleared.
1N/A
2N/A
3N/A
4N/A
5Db_jnld
6httpd
7serial_console
11controld
12N/A
13Snmpd
15Sshd
16Ntpd
17Clusterd
18Lcd
19

Dhcpd

20Named
24NTLM
25

Netbiosd

26Winbindd
27

Tftpd

29N/A
30N/A
31N/A
32N/A
33N/A
34HTTPd
35OSPF

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. Table 11.6 shows the message and description for each state.

Table 11.6 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 appliance is connected to the Master Grid.

5

grid-disconnected

The appliance is not connected to the Master Grid.

6

enet-link-up

The ethernet port link is active.

7

enet-link-down

The ethernet port link is inactive.

8

replication-online

The replication is online.

9

replication-offline

The replication is offline.

10

replication-snapshotting

The replication is snapshotting.

11

service-up

The service is up.

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 sync.

17

ms-server-up

The Microsoft server is online.

18

ms-server-down

The Microsoft server is offline.

19

ms-service-up

The Microsoft service connection is up.

20

ms-service-down

The Microsoft service connection is down.

21

nac-server-group-down

The NAC authentication server group is down.

22

nac-server-group-up

The NAC authentication server group is up.

23

mgm-service-up

The connection between the Master Grid and managed Grids is up.

24

mgm-service-down

The connection between the Master Grid and managed Grids is down.

2029

hsm-group-failure

The HSM operation failed.

2030

hsm-group-up

The HSM operation is functioning properly.

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.


Note: Contact Infoblox Technical Support for assistance when the recommended actions do not resolve the problems.


Equipment Failure Traps


ibTrapDesc
OID 3.1.1.1.2.11.0

ibTrapServerity 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 failed. The fan number <n> can be 1, 2, or 3.

Inspect the specified fan for mechanical or electrical problems.

Fan <n> is OK.

Informational

The specified fan is functioning properly. The fan number <n> can be 1, 2, or 3.

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.

RAID monitoring, at 1 minute interval

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.

No action is required.

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.

Major

The RAID system is degrading.

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

The system's RAID array is rebuilding.

Minor

The RAID system is rebuilding.

No action is required.

Processing and Software Failure Traps

ibTrapDesc
OID 3.1.1.1.2.11.0

ibTrapServerity OID 3.1.1.1.2.2

Description/Cause

Recommended Actions

Named Daemon Failure

A named daemon monitoring failure has occurred.

Critical

The named process failed.

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

DHCP Daemon Failure

A DHCP daemon monitoring failure has occurred.

Critical

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 cluster daemon failure has occurred.

Critical

The clusterd process failed.

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

LCD Daemon Failure

An LCD daemon failure has occurred.

Major

The LCD process failed. The alert light is yellow.

  1. Inspect the LCD panel for the possible cause of this problem.
  2. Review the syslog file to identify the possible cause of this problem.

Apache Software httpd failure, monitored every 2 minutes

An Apache software failure has occurred.

Critical

The request to monitor the Apache server failed.

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

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.

Critical

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.

Critical

The tftpd process failed.

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

An FTPD daemon failure has occurred.

Critical

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.

Critical

The HTTP file distribution process failed.

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

auth_named Process Failure

An auth named server failure has occurred.

Critical

The auth_named server 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.

Critical

Either the zebra process or the ospfd process failed.

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

Backup Failure

Backup failed.

Not implemented

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.

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

Database Backup Failure

Database backup failed.

Not implemented

The db_dump process failed.

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

Backup Module Failure

Module backup failed.

Not implemented

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 implemented

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 implemented

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:
<registered client name> failed on
<server IP address>

Critical

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

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

Microsoft Server

Microsoft server
hostname has failed.

Major

The Microsoft server could not be reached.

Check that the Microsoft server is connected to the network and configured properly.

Microsoft server
hostname is OK.

Informational

The Microsoft server can be reached and is functioning properly.

No action is required.

Microsoft DNS/DHCP Service

Service connection to Microsoft DNS server hostname has failed.

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 hostname has failed.

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 hostname is OK.

Informational

The Microsoft DNS service is responding.

No action is required.

Service connection to Microsoft DHCP server hostname is OK.

Informational

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.

Informational

The NAC authentication server group is responding.

No action is required.

Threshold Crossing Traps

ibTrapDesc
OID 3.1.1.1.2.11.0

ibObjectName OID 3.1.1.1.2.3.0

Description/Cause

Recommended Actions

System Memory Usage

System has run out of memory.

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.

    Note: Free memory = free physical RAM + free cache buffers. The high threshold for swap pages is 3,200.

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

System memory usage is over 90%.

memory

The memory usage on the appliance exceeded 90%.
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.

    Note: Free memory = free physical RAM + free cache buffers. The high threshold for swap pages is 3,200.

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

System memory is OK.

memory

The memory usage on the system is back to normal from the previous state.

No action is required.

Primary Hard Drive Usage (monitored every 30 seconds)

System primary hard disk usage is over 90%.

disk usage

The primary hard disk usage exceeded 90%. The alert light is yellow.

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

Primary drive is full.

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.

disk usage

The primary hard disk usage is 85% or lower. The alert light is green.

No action is required.

Replication Statistics Monitoring

Grid queue replication problem.

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.

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

DHCP Range Threshold Crossing

DHCP threshold crossed:
Member:
<DHCP server node VIP>
Network: <network>/
<network view>
Range: <DHCP range>/
<network view>
High Watermark: <high watermark percentage> (95% by default)
Low Watermark: <low watermark percentage> (0% by default)
Current Usage: <current usage percentage>
Active Leases: <number of active leases>
Available Leases:
<number of available leases>
Total Addresses: <total addresses>

Threshold

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

  • The address usage in the DHCP range was greater than the high watermark.
  • The address usage in the DHCP range was less than the low watermark.

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

DHCP DDNS Updates Deferred

DHCP DNS updates deferred:
Retried at least once:
<number of retries>
Maximum number of deferred updates since start of problem episode (or restart): <max number>

Threshold

The DNS updates were deferred because of DDNS update errors.

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

Database Capacity Usage

Over 85% database capacity used.

db_usage

The appliance database usage exceeded 85%.

Increase the database capacity.

Database capacity used is OK.

db_usage

The appliance database usage is less than 85%.

No action is required.

DNS Monitor

DNS Monitor

For invalid ports: "dns_security_port"
For invalid TXIDs: "dns_security_txid"

DNS security alert. There were actual DNS responses to {invalid ports with invalid TXID} in the last minute, comprising percent% of all responses. Primary sources: ip_address sent count, ip_address sent count.
where

  • actual is the total number of DNS responses arrive on invalid ports or have invalid TXIDs.
  • percent% is the percentage of invalid DNS responses over the total number of DNS responses.
  • ip_address is the IP address of the primary source that generated the invalid DNS responses.
  • count is the number of invalid responses generated by the specified IP address.

    Example:
    DNS security alert. There were 1072 DNS responses to invalid ports in the last minute, comprising 92% of all responses. Primary sources: 10.0.0.0 sent 1058, 2.2.2.2 sent 14.
  1. Review the following:
    • DNS alert status
    • syslog file
  2. Limit access or block connections from the primary sources.

Object State Change Traps

ibTrapDesc
OID 3.1.1.1.2.11.0


Description/Cause


Recommended Actions

Service Shutdown

Shutting down services due to database snapshot.

The appliance is shutting down its services while synchronizing the database with the grid master.

No action is required.

Shutting down services due to database snapshot.

The appliance is shutting down its services while synchronizing the database with the grid master.

No action is required.

Network Interfaces Monitoring

LAN port link is down. Please check the connection.

The LAN port is up, but the link is down.

Check the LAN link connection.

HA port link is down. Please check the connection.

The HA port is up, but the link is down.

Check the HA link connection.

MGMT port link is down. Please check the connection.

The MGMT port is enabled, but the link is down.

Check the MGMT link connection.

LAN port link is up.

The LAN port link is up and running.

No action is required.

HA port link is up.

The HA port link is up and running.

No action is required.

MGMT port link is up.

The MGMT port link is up and running.

No action is required.

HA State Change from Initial to Active

The node has become ACTIVE.

A node in an HA pair becomes active. The HA pair starts up.

No action is required.

HA State Change from Passive to Active

The node has become ACTIVE.

The node changed from a passive to an active node.

No action is required.

HA State Change from Initial to Passive

The node has become PASSIVE.

A node in an HA pair becomes passive. The HA pair starts up, and the node is not a grid master candidate.

No action is required.

Node Connected to Grid

The grid member is connected to the grid master.

The grid member joined the grid, and it is not a grid master candidate.

No action is required.

Node Disconnected to Grid

The grid member is not connected to the grid master.

The grid member lost its connection to the grid master.

No action is required.

Replication State Monitoring

ha-replication-online (13)

The HA replication is online.

No action is required.

ha-replication-offline (14)

The HA replication is offline.

No action is required.

NTP is out of sync, monitored every 30 seconds

The NTP server is out of synchronization.

The Infoblox NTP server and the external NTP server are not synchronized.

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

Process Started and Stopped Traps

ibTrapDesc
OID 3.1.1.1.2.11.0


Description/Cause


Recommended Actions

Httpd Start

The process started normally.

The httpd process started.

No action is required.

Httpd Stop

The process stopped normally.

The httpd process stopped.

No action is required.

ibPlatformOne MIB

The ibPlatformOne MIB provides information about the CPU temperature of the appliance, the replication status, the average latency of DNS requests, DNS security alerts, CPU and memory utilization of the appliance, and the Infoblox service status. Figure 11.4 illustrates the structure of the PlatformOne MIB. (Note that the OIDs in the illustration do not include the prefix .1.3.6.1.4.1.7779.)
The ibPlatformOne MIB contains the following objects:

  • ibCPUTemperature (IbString) tracks the CPU temperature of the appliance.
  • ibClusterReplicationStatusTable provides information in tabular format about the replication status of the appliance. For information, see ibClusterReplicationStatusTable.
  • ibNetworkMonitor provides information about the average latency of authoritative and nonauthoritative replies to DNS queries for different time intervals. It also provides information about invalid DNS responses that arrive on invalid ports or have invalid DNS transaction IDs. For information, see ibNetwork Monitor.
  • ibHardwareType (IbString) provides information about the hardware platform. For an Infoblox appliance, it provides the model number of the Infoblox hardware platform. For vNIOS appliances, it identifies whether the hardware platform is Riverbed or VMware.
  • ibHardwareId (IbString) provides the hardware ID of the appliance.
  • ibSerialNumber (IbString) provides the serial number of the Infoblox hardware platform.
  • ibNiosVersion (IbString) provides the version of the software.
  • ibSystemMonitor provides information about the CPU and memory utilization of the appliance. For information, see ibSystemMonitor.

The ibPlatformOne MIB also contains the following tables that provide status of the Infoblox services as well as system and hardware services on the appliance you query:

  • ibMemberServiceStatusTable provides status of the Infoblox services, such as the DNS and DHCP services, on a queried appliance. For information, see ibMemberServiceStatusTable.
  • ibMemberNode1ServiceStatusTable provides status of the system and hardware services on a queried appliance. For information, see ibMemberNode1ServiceStatusTable.
  • ibMemberNode2ServiceStatusTable provides status of the system and hardware services on the passive node of an HA pair if the queried appliance is the VIP or the active node of an HA pair. For independent appliances and the passive nodes of HA pairs, this table does not display any status. For information, see ibMemberNode2ServiceStatusTable.

Figure 11.4 ibPlatformOne MIB Structure


ibClusterReplicationStatusTable
ibClusterRepliactionStatusTable (object ID 3.1.1.2.1.2.1) provides information about the Master Grid replication status. For information about Infoblox SNMP traps, see ibTrapDesc (OID 3.1.1.1.2.11.0).
Figure 11.5 shows the sub branches of ibClusterReplicationStatusTable.

Figure 11.5 ibClusterReplicationStatusTable Objects

Table 11.7 ibClusterReplicationStatusTable Objects

Object (Type)Description
ibClusterReplicationStatusEntryA conceptual row that provides information about the Master Grid replication status. The status indicates whether the appliance is sending replication queues, receiving queues, or having problems with the replication.
ibNodeIPAddress (IbIpAddr)IP address of a grid member.
ibNodeReplicationStatus (IbString)Replication status of the grid member. The replication status can be one of the following: online, offline, or snapshotting.
ibNodeQueueFromMaster (Integer)“Sent” queue size from master.
ibNodeLastRepTimeFromMaster (IbString)Last sent time from master.
ibNodeQueueToMaster (Integer)“Receive” queue size from master.
ibNodeLastRepTimeToMaster (IbString)Last receive time from master.

ibNetwork Monitor

As shown in Figure 11.6 , the ibNetwork Monitor has one subtree, ibNetworkMonitorDNS, that branches out into the following:

  • ibNetworkMonitorDNSActive (Integer) reports on whether DNS latency monitoring is enabled. This is the only object in this branch. When you send a query for this object, the appliance responds with either "active" (1) or "nonactive" (0).
  • ibNetworkMonitorDNSNonAA provides information about the average latency of nonauthoritative replies to DNS queries for 1-, 5-, 15-, and 60-minute intervals. For information, see ibNetworkMonitorDNSNonAA Objects.
  • ibNetworkMonitorDNSAA provides information about the average latency of authoritative replies to DNS queries for 1-, 5-, 15-, and 60-minute intervals. For information, see ibNetworkMonitorDNSAA Objects.
  • ibNetworkMonitorDNSSecurity provides information about the invalid DNS responses that arrive on invalid ports or have invalid DNS transaction IDs. ibNetworkMonitorDNSSecurity branches out into the following:
    • ibNetworkMonitorDNSSecurityInvalidPort
    • ibNetworkMonitorDNSSecurityInvalidTxid
    • ibNetworkMonitorDNSSecurityInvalidPortOnly (Counter)
      • ibNetworkMonitorDNSSecurityInvalidPortCount (Counter)
    • ibNetworkMonitorDNSSecurityInvalidTxidOnly (Counter)
      • ibNetworkMonitorDNSSecurityInvalidTxidCount (Counter)
    • ibNetworkMonitorDNSSecurityInvalidTxidAndPort (Counter) For information, see Table 11.10

Figure 11.6 ibNetWorkMonitor Objects

Figure 11.7 ibNetworkMonitorDNSNonAA and ibNetworkMonitorDNSAA Subtrees



Table 11.8 describes the objects in ibNetworkMonitorDNSNonAA. You can send queries to retrieve values for these objects.

Table 11.8 ibNetworkMonitorDNSNonAA Objects

Object (Type)Description
ibNetworkMonitorDNSNonAAT1

File that contains the objects for monitoring the average latency of nonauthoritative replies to queries in the last minute.

ibNetworkMonitorDNSNonAAT1AvgLatency (Integer)Indicates the average latency in microseconds of nonauthoritative replies to queries in the last minute.
ibNetworkMonitorDNSNonAAT1Count (Integer)Indicates the number of queries used to calculate the average latency of nonauthoritative replies in the last minute.
ibNetworkMonitorDNSNonAAT5File that contains the objects for monitoring the average latency of nonauthoritative replies to queries in the last five minutes.
ibNetworkMonitorDNSNonAAT5AvgLatency (Integer)Indicates the average latency in microseconds of nonauthoritative replies to queries in the last five minutes.
ibNetworkMonitorDNSNonAAT5Count (Integer)

Indicates the number of queries used to calculate the average latency of nonauthoritative replies in the last five minutes.

ibNetworkMonitorDNSNonAAT15File that contains the objects for monitoring the average latency of nonauthoritative replies to queries in the last 15 minutes.
ibNetworkMonitorDNSNonAAT15AvgLatency (Integer)Indicates the average latency in microseconds of nonauthoritative replies to queries in the last 15 minutes.
ibNetworkMonitorDNSNonAAT15Count (Integer)Indicates the number of queries used to calculate the average latency of nonauthoritative replies in the last 15 minutes.
ibNetworkMonitorDNSNonAAT60File that contains the objects for monitoring the average latency of nonauthoritative replies to queries in the last 60 minutes.
ibNetworkMonitorDNSNonAAT60AvgLatency (Integer)Indicates the average latency in microseconds of nonauthoritative replies to queries in the last 60 minutes.
ibNetworkMonitorDNSNonAAT60Count (Integer)Indicates the number of queries used to calculate the average latency of nonauthoritative replies in the last 60 minutes.
ibNetworkMonitorDNSNonAAT1440

  File that contains the objects for monitoring the average latency of nonauthoritative replies to queries in the last 24 hours.

ibNetworkMonitorDNSNonAAT1440AvgLatency (Integer)Indicates the average latency in microseconds of nonauthoritative replies to queries in the last 24 hours.
ibNetworkMonitorDNSNonAAT1440Count (Integer)Indicates the number of queries used to calculate the average latency of nonauthoritative replies in the last 24 hours.


Table 11.9 describes the objects in ibNetworkMonitorDNSAA. You can send queries to retrieve values for these objects.

Table 11.9 ibNetworkMonitorDNSAA Objects

Object (Type)Description
ibNetworkMonitorDNSAAT1

File that contains the objects for monitoring the average latency of authoritative replies to queries in the last minute.

ibNetworkMonitorDNSAAT1AvgLatency (Integer)Indicates the average latency in microseconds of authoritative replies to queries in the last minute.
ibNetworkMonitorDNSAAT1Count (Integer)

Indicates the number of queries used to calculate the average latency of authoritative replies in the last minute.

ibNetworkMonitorDNSAAT5

File that contains the objects for monitoring the average latency of authoritative replies to queries in the last five minutes.

ibNetworkMonitorDNSAAT5AvgLatency (Integer)Indicates the average latency in microseconds of authoritative replies to queries in the last five minutes.
ibNetworkMonitorDNSAAT5Count (Integer)Indicates the number of queries used to calculate the average latency of authoritative replies in the last five minutes.
ibNetworkMonitorDNSAAT15

File that contains the objects for monitoring the average latency of authoritative replies to queries in the last 15 minutes.

ibNetworkMonitorDNSAAT15AvgLatency (Integer)Indicates the average latency in microseconds of authoritative replies to queries in the last 15 minutes.
ibNetworkMonitorDNSAAT15Count (Integer)Indicates the number of queries used to calculate the average latency of authoritative replies in the last 15 minutes.
ibNetworkMonitorDNSAAT60

File that contains the objects for monitoring the average latency of authoritative replies to queries in the last 60 minutes.

ibNetworkMonitorDNSAAT60AvgLatency (Integer)Indicates the average latency in microseconds of authoritative replies to queries in the last 60 minutes.
ibNetworkMonitorDNSAAT60Count (Integer)Indicates the number of queries used to calculate the average latency of authoritative replies in the last 60 minutes.
ibNetworkMonitorDNSAAT1440

File that contains the objects for monitoring the average latency of authoritative replies to queries in the last 24 hours.

ibNetworkMonitorDNSAAT1440AvgLatency (Integer)Indicates the average latency in microseconds of authoritative replies to queries in the last 24 hours.
ibNetworkMonitorDNSAAT1440Count (Integer)Indicates the number of queries used to calculate the average latency of authoritative replies in the last 24 hours.


Table 11.10 describes the objects in ibNetworkMonitorDNSSecurity. You receive SNMP traps with these objects when you enable the following:

  • SNMP traps
  • DNS network monitoring
  • DNS alert monitoring

Table 11.10 ibNetworkMonitorDNSSecurity Objects

Object (Type)Description
ibNetworkMonitorDNSSecurityInvalidPortTracks the number of invalid DNS responses that arrive on invalid ports. This object contains a subtree with six objects that track invalid ports within a certain time interval. For information, see Table 11.11.
ibNetworkMonitorDNSSecurityInvalidTxidTracks the number of invalid TXIDs (DNS transaction IDs).
For information about invalid TXIDs, see .
This object contains a subtree with six objects that track invalid TXIDs within a certain time interval. For information, see Table 11.12.

ibNetworkMonitorDNSSecurityInvalidPortOnly (Counter)

Tracks the number of DNS responses with both of the following conditions:
  • Arrive on invalid ports
  • Have valid TXIDs
ibNetworkMonitorDNSSecurityInvalidTxidOnly (Counter)

Tracks the number of DNS responses with both of the following conditions:

  • Arrive on valid ports
  • Have Invalid TXIDs
ibNetworkMonitorDNSSecurityInvalidPortCount (Counter)Tracks the total number of invalid DNS responses that arrive on invalid ports.
ibNetworkMonitorDNSSecurityInvalidTxidCount (Counter)Tracks the total number of DNS responses that have invalid DNS transaction IDs.
ibNetworkMonitorDNSSecurityInvalidTxidAndPort (Counter)Tracks the number of DNS responses with both of the following conditions:
  • Arrive on invalid ports
  • Have invalid TXIDs

 
Table 11.11 describes the objects in ibNetworkMonitorDNSSecurityInvalidPort.

Table 11.11 ibNetworkMonitorDNSSecurityInvalidPort Objects

Object (Type)Description
ibNetworkMonitorDNSSecurityInvalidPort1 (Integer)Tracks the number of invalid DNS responses that arrive on invalid ports in the last one minute.
ibNetworkMonitorDNSSecurityInvalidPort5 (Integer)Tracks the number of invalid DNS responses that arrive on invalid ports in the last five minutes.
ibNetworkMonitorDNSSecurityInvalidPort15 (Integer)Tracks the number of invalid DNS responses that arrive on invalid ports in the last 15minutes.
ibNetworkMonitorDNSSecurityInvalidPort60 (Integer)Tracks the number of invalid DNS responses that arrive on invalid ports in the last 60 minutes.
ibNetworkMonitorDNSSecurityInvalidPort1440 (Integer)Tracks the number of invalid DNS responses that arrive on invalid ports in the last 24 hours.
ibNetworkMonitorDNSSecurityInvalidPortCount (Counter)Tracks the total number of invalid DNS responses that arrive on invalid ports.


Table 11.12 describes the objects in ibNetworkMonitorDNSSecurityInvalidTxid.

Table 11.12 ibNetworkMonitorDNSSecurityInvalidTxid Objects

Object (Type)Description
ibNetworkMonitorDNSSecurityInvalidTxid1 (Integer)Tracks the number of DNS responses that have invalid DNS transaction IDs in the last one minute.
ibNetworkMonitorDNSSecurityInvalidTxid5 (Integer)Tracks the number of DNS responses that have invalid DNS transaction IDs in the last five minutes.
ibNetworkMonitorDNSSecurityInvalidTxid15 (Integer)Tracks the number of DNS responses that have invalid DNS transaction IDs in the last 15 minutes.
ibNetworkMonitorDNSSecurityInvalidTxid60 (Integer)Tracks the number of DNS responses that have invalid DNS transaction IDs in the last 60 minutes.
ibNetworkMonitorDNSSecurityInvalidTxid1440 (Integer)Tracks the number of DNS responses that have invalid DNS transaction IDs in the last 24 hours.
ibNetworkMonitorDNSSecurityInvalidTxidCount (Counter)Tracks the total number of DNS responses that have invalid DNS transaction IDs.

ibSystemMonitor

As shown in Figure 11.4 , ibSystemMonitor (object ID 3.1.1.2.1.2.8) has the following subtrees:

    • ibSystemMonitorCpu: Contains ibSystemMonitorCpuUsage (Integer) that reports the CPU usage of the appliance.
    • ibSystemMonitorMem: Contains ibSystemMonitorMemUsage (Integer) that reports the memory usage of the appliance.

Figure 11.8 ibSystemMonitor Objects



ibMemberServiceStatusTable

As shown in Figure 11.9 , ibMemberServiceStatusTable (object ID 3.1.1.2.1.2.9) has one subtree, ibMemberServiceStatusEntry, which contains the following objects:

  • ibServiceName (String) reports the names of the Infoblox services. For a list of Infoblox services, see ibMemberServiceStatusTable.
  • ibServiceStatus (Integer) reports the status of the Infoblox services. For a list of service status, see Service Status.
  • ibServiceDesc (String) describes the details of the status.

Figure 11.9 ibMemberServiceStatusTable Objects




Service Status
When you query the service status on an appliance, the response includes the status of the services. Table 11.13 shows the values and descriptions of the status. Note that for internal Master Grid operations, the NTP service is always in the "working" state even if it has been disabled through the Infoblox GUI.

Table 11.13 ibServiceStates Values


Value

Description

Definition

1

working

The service is functioning properly.

2

warning

The service is having some issues. Check the service or hardware function and the syslog to identify the problem.

3

failed

The service failed. Review the syslog to identify the problem.

4

inactive

The service is disabled or out of service.

5

unknown

The appliance cannot detect the current status of the service.


System and Hardware Service Names
Table 11.14 lists the values and descriptions of the system and hardware services that appear in ibMemberServiceStatusTable, ibMemberNode1ServiceStatusTable, and ibMemberNode2ServiceStatusTable.

Table 11.14 Values of ibServiceNames


Value

Description

Definition

1

dhcp

DHCP service

2

dns

DNS service

3

ntp

NTP service

4

tftp

TFTP file distribution

5

http-file-dist

HTTP file distribution

6

ftp

FTP file distribution

7

bloxtools-move

Moving the bloxTools service

8

bloxtools

The bloxTools service

9

node-status

Node status

10

disk-usage

Disk usage

11

enet-lan

LAN 1 port

12

enet-lan2

LAN 2 port

13

enet-ha

HA port

14

enet-mgmt

MGMT port

15

lcd

LCD

16

memory

Virtual memory

17

replication

Replication process

18

db-object

Database usage

19

raid-summary

Summary of the RAID array

20

raid-disk1

Disk 1 of the RAID array (for Infoblox-2000, -2000-A, and -4010)

21

raid-disk2

Disk 2 of the RAID array (for Infoblox-2000, -2000-A, and -4010)

22

raid-disk3

Disk 3 of the RAID array (for Infoblox-2000, -2000-A, and -4010)

23

raid-disk4

Disk 4 of the RAID array (for Infoblox-2000, -2000-A, and -4010))

24

fan1

FAN 1 status

25

fan2

FAN 2 status

26

fan3

FAN 3 status

27

power-supply

Power supply

28

ntp-sync

NTP service synchronization

29

cpu1-temp

CPU 1 temperature

30

cpu2-temp

CPU 2 temperature

31

sys-temp

System temperature

32

raid-battery

RAID battery

33

cpu-usage

CPU usage

34

ospf

Anycast using OSPF

35

bgp

Anycast using BGP

36

mgm-service

Multi-Grid management service

37

subgrid-conn

Connection between the Master Grid and managed Grid

38

network-capacity

Network capacity

ibMemberNode1ServiceStatusTable

As shown in Figure 11.10 , ibMemberNode1ServiceStatusTable (object ID 3.1.1.2.1.2.10) has one subtree, ibMemberNode1ServiceStatusEntry, which contains the following objects:

  • ibMemberNode1ServiceName (String) reports the names of the system and hardware services. For a list of service names, see System and Hardware Service Names.
  • ibMemberNode1ServiceStatus (Integer) reports the status of the services. For a list of service status, see Service Status.
  • ibMemberNode1ServiceDesc (String) describes the details of the status.

ibMemberNode1ServiceStatusTable displays the current status of the system and hardware services on the appliance that you query. For example, when you query an independent appliance, this table shows the information about the independent appliance. When you query the VIP of an HA pair, this table shows the information about the active node. For the active node of the HA pair, you can also query ibMemberNode2StatusTable to get the status of the passive node. For information, see ibMemberNode2ServiceStatusTable.


Note: For an independent appliance and the passive node of an HA pair, no information is returned when you query ibMemberNode2ServiceStatusTable.


Figure 11.10 ibMemberNode1ServiceStatusTable Objects

ibMemberNode2ServiceStatusTable

As shown in Figure 11.11 , ibMemberNode2ServiceStatusTable (object ID 3.1.1.2.1.2.11) has one subtree, ibMemberNode2ServiceStatusEntry, which contains the following objects:

  • ibMemberNode2ServiceName (String) reports the names of the system and hardware services. For a list of service names, see .
  • ibMemberNode2ServiceStatus (Integer) reports the status of the services. For a list of possible service status, see Service Status.
  • ibMemberNode2ServiceDesc (String) describes details of the status.

ibMemberNode2ServiceStatusTable displays the current status of the system and hardware services on the passive node of an HA pair when you query the VIP of the HA pair. For independent appliances and the passive nodes of HA pairs, this table does not display any status.

Figure 11.11 ibMemberNode2ServiceStatusTable Objects


ibDHCPOne MIB

The ibDHCPOne MIB provides information about address usage within a subnet, DHCP lease statistics, and DHCP packet counts. It includes two modules, ibDHCPModule for IPv4 data and ibDHCPv6Module for IPv6 data.

ibDHCPModule

Figure 11.12 illustrates the structure of the ibDHCPModule. (Note that the OIDs shown in the illustration do not include the prefix .1.3.6.1.4.1.7779.) ibDHCPModule contains the following objects:

  • ibDHCPSubnetTable provides statistical data about the DHCP operations of the appliance. For information, see ibDHCPSubnetTable.
  • ibDHCPStatistics maintains counters for different types of packets. For information, see ibDHCPStatistics.
  • ibDHCPDeferredQueuesize tracks the total number of deferred DDNS updates that are currently in the queue to be retried. When DDNS updates are deferred due to timeout or server issues, the DHCP server puts these updates in this queue.
  • ibDHCPDDNSStats monitors the average latency for the DDNS updates in microseconds and the number of timeouts during different time intervals. For information, see ibDHCPDDNSStats.

Figure 11.12 ibDHCPModule



ibDHCPSubnetTable
ibDHCPSubnetTable provides statistical data about the DHCP operations of the appliance. It contains the following objects:

Table 11.15 ibDHCPSubnetTable

Object (Type)Description
ibDHCPSubnet Entry

File that contains the objects for monitoring DHCP operations on the appliance.

ibDHCPSubnetNetworkAddress (IbIpAddr)The subnetworks, in IP address format, that have IP addresses for lease. A subnetwork may have many address ranges for lease.
ibDHCPSubnetNetworkMask (IbIpAddr)The subnet mask in dotted decimal format.
ibDHCPSubnetPercentUsed (Integer)The percentage of dynamic DHCP addresses leased out at this time for each subnet. Fixed addresses are always counted as leased for this calculation, if the fixed addresses are within a leased address range.


Following is an example of the table as viewed through a MIB browser:

Figure 11.13 MIB Browser View 1


ibDHCPStatistics

ibDHCPStatistics maintains counters for different types of packets. The counters always start with zero when the DHCP service is restarted. Therefore, the numbers reflect the total number of packets received since the DHCP service was last restarted on the appliance. The ibDHCPStatistics module contains the following objects:

Table 11.16 ibDHCPStatistics

Object (Type)Description
ibDhcpTotalNoOfDiscovers (Counter)The number of DHCPDISCOVER messages that the appliance received. Clients broadcast DHCPDISCOVER messages when they need an IP address and network configuration information.
ibDhcpTotalNoOfRequests (Counter)The number of DHCPREQUEST messages that the appliance received. A client sends a DHCPREQUEST message requesting configuration information, after it receives the DHCPOFFER message.
ibDhcpTotalNoOfReleases (Counter)The number of DHCPRELEASE messages that the appliance received from its clients. A client sends a DHCP release when it terminates its lease on an IP address.
ibDhcpTotalNoOfOffers (Counter)The number of DHCPOFFER messages that the appliance has sent to clients. The appliance sends a DHCPOFFER message to a client. It contains an IP address and configuration information.
ibDhcpTotalNoOfAcks (Counter)The number of DHCPACK messages that the appliance sent to clients. It sends a DHCPACK message to a client to confirm that the IP address offered is still available.
ibDhcpTotalNoOfNacks (Counter)The number of DHCPNACK messages that the appliance sent to clients. It sends a DHCPNACK message to withdraw its offer of an IP address.
ibDhcpTotalNoOfDeclines (Counter)The number of DHCPDECLINE messages that the appliance received. A client sends a DHCPDECLINE message if it determines that an offered IP address is already in use.
ibDhcpTotalNoOfInforms (Counter)The number of DHCPINFORM messages that the appliance received. A client sends a DHCPINFORM message when it has an IP address but needs information about the network.
ibDhcpTotalNoOfOthers (Counter)The total number of DHCP messages other than those used in negotiation, such as DHCPFORCERENEW, DHCPKNOWN, and DHCPLEASEQUERY.

ibDHCPDDNSStats

ibDHCPDDNSStats monitors the average latency for the DHCP DDNS updates in microseconds and the number of timeouts during different time intervals. The ibDHCPDDNSStats module contains the following objects:

Table 11.17 ibDHCPStatistics

Object (Type)Desciption
ibDHCPDDNSAvgLatency5 (Integer)Indicates the average latency in microseconds of the DHCP DDNS updates in the last five minutes.
ibDHCPDDNSAvgLatency15 (Integer)Indicates the average latency in microseconds of the DHCP DDNS updates in the last 15 minutes.
ibDHCPDDNSAvgLatency60 (Integer)Indicates the average latency in microseconds of the DHCP DDNS updates in the last 60 minutes.
ibDHCPDDNSAvgLatency1440 (Integer)Indicates the average latency in microseconds of the DHCP DDNS updates in the last 24 hours.
ibDHCPDDNSTimeoutCount5 (Integer)The number of timeouts for the DHCP DDNS updates in the last five minutes.
ibDHCPDDNSTimeoutCount15 (Integer)The number of timeouts for the DHCP DDNS updates in the last 15 minutes.
ibDHCPDDNSTimeoutCount60 (Integer)The number of timeouts for the DHCP DDNS updates in the last 60 minutes.
ibDHCPDDNSTimeoutCount1440 (Integer)The number of timeouts for the DHCP DDNS updates in the last 24 hours.

ibDHCPv6Module

Figure 11.14 illustrates the structure of the ibDHCPv6Module, which contains the following objects:

  • ibDHCPv6SubnetTable provides statistical data about the DHCPv6 operations of the appliance. For information, see ibDHCPv6SubnetTable.
  • ibDHCPv6Statistics maintains counters for different types of packets. For information, see ibDHCPv6Statistics.
  • ibDHCPv6DeferredQueuesize tracks the total number of deferred DDNS updates that are currently in the queue to be retried. When DDNS updates are deferred due to timeout or server issues, the DHCP server puts these updates in this queue.
  • ibDHCPv6DDNSStats monitors the average latency for the DDNS updates in microseconds and the number of timeouts during different time intervals. For information, see ibDHCPv6DDNSStats.

Figure 11.14 ibDHCPv6Module




ibDHCPv6SubnetTable
ibDHCPSubnetTable provides statistical data about the DHCPv6 operations of the appliance. It contains the following objects:

Table 11.18 ibDHCPSubnetTable

Object (Type)Description
ibDHCPv6Subnet

Entry File that contains the objects for monitoring DHCPv6 operations on the appliance.

ibDHCPv6SubnetNetworkAddress (IbIpAddr)The subnetworks, in IPv6 address format, that have IPv6 addresses for lease. A subnetwork may have many address ranges for lease.
ibDHCPv6SubnetNetworkMask (IbIpAddr)

The subnet mask in CIDR notation format.

ibDHCPv6Statistics

ibDHCPv6Statistics maintains counters for different types of packets. The counters always start with zero when the DHCP service is restarted. Therefore, the numbers reflect the total number of packets received since the DHCP service was last restarted on the appliance. The ibDHCPv6Statistics module contains the following objects:

Table 11.19 ibDHCPv6Statistics

Object (Type)Description
ibDhcpv6TotalNoOfSolicits (Counter)The number of Solicit messages that the Grid member received, including Solicit messages embedded in Relay-Forward messages. A DHCP client sends a Solicit message to locate DHCP servers.
ibDhcpv6TotalNoOfRequests (Counter)The number of Request messages that the Grid member received. A DHCP client sends a Request message to request one or more IP addresses and configuration parameters from a DHCP server.
ibDhcpv6TotalNoOfReleases (Counter)The number of Release messages that the Grid member received. A DHCP client sends a Release message when it terminates its lease and releases its IP address.
ibDhcpv6TotalNoOfAdvertises (Counter)The number of Advertise messages that the Grid member sent. When a DHCP server receives a Solicit message, it can respond with an Advertise message to indicate that the server is available for DHCP service.
ibDhcpv6TotalNoOfReplies (Counter)

The number of Reply messages that the Grid member sent. A DHCP server sends a Reply message that includes IP addresses and configuration parameters when it responds to Solicit, Request, Renew or Rebind message. It sends a Reply message with configuration parameters only when it responds to an Information-Request message.

ibDhcpv6TotalNoOfRenews (Counter)The number of Renew messages that the Grid member received. A DHCP client sends a Renew message to a DHCP server to extend the lifetimes on the leases granted by the DHCP server and to update other properties.
ibDhcpv6TotalNoOfRebinds (Counter)The number of Rebind messages that the Grid member received. A DHCP client sends a Rebind message to extend the lifetime of its lease and to update configuration parameters.
ibDhcpv6TotalNoOfDeclines (Counter)

The number of Decline messages that the Grid member received. A DHCP client sends a Decline message to a DHCP server when it discovers that the IP address offered by a DHCP server is already in use.

ibDhcpv6TotalNoOfInformationRequests (Counter)

The number of Information-Request messages that the Grid member received. A client sends an Information-Request message to retrieve configuration parameters, such as the IP addresses of DNS servers in the network.
ibDhcpv6TotalNoOfOthers (Counter)The total number of DHCP messages other than those used in negotiation.

ibDHCPv6DDNSStats

ibDHCPv6DDNSStats monitors the average latency for the DHCPv6 DDNS updates in microseconds and the number of timeouts during different time intervals. The ibDHCPv6DDNSStats module contains the following objects:

Table 11.20 ibDHCPStatistics

Object (Type)Description
ibDHCPv6DDNSAvgLatency5 (Integer)Indicates the average latency in microseconds of the DHCPv6 DDNS updates in the last five minutes.

ibDHCPv6DDNSAvgLatency15 (Integer)

Indicates the average latency in microseconds of the DHCPv6 DDNS updates in the last 15 minutes.
ibDHCPv6DDNSAvgLatency60 (Integer)Indicates the average latency in microseconds of the DHCPv6 DDNS updates in the last 60 minutes.
ibDHCPv6DDNSAvgLatency1440 (Integer)Indicates the average latency in microseconds of the DHCPv6 DDNS updates in the last 24 hours.
ibDHCPv6DDNSTimeoutCount5 (Integer)The number of timeouts for the DHCPv6 DDNS updates in the last five minutes.

ibDHCPv6DDNSTimeoutCount15 (Integer)

The number of timeouts for the DHCPv6 DDNS updates in the last 15 minutes.
ibDHCPv6DDNSTimeoutCount60 (Integer)The number of timeouts for the DHCPv6 DDNS updates in the last 60 minutes.
ibDHCPv6DDNSTimeoutCount1440 (Integer)The number of timeouts for the DHCPv6 DDNS updates in the last 24 hours.

ibDNSOne MIB

The ibDNSOne MIB provides statistical information about the DNS processes and about the views and zones in the database. Figure 11.15 illustrates the structure of the ibDNSOne MIB. (Note that the OIDs shown in the illustration do not include the prefix 1.3.6.1.4.1.7779.) The ibDNSOne MIB contains four subtrees, ibZoneStatisticsTable, ibZonePlusViewStatisticsTable, ibDDNSUpdateStatistics, and ibBindZoneTransferCount (Counter64).

Figure 11.15 ibDNSOne MIB



ibZoneStatisticsTable
ibZoneStatisticsTable provides statistical data about the DNS operations on the appliance. The syntax of these objects uses a Counter64 format. In some cases, the counter format may not be compatible with SNMP toolkits that use a 32-bit counter. Ensure that you reconfigure or update these tools to use the Counter64 format.
ibZoneStatisticsTable contains the following objects:

Table 11.21 ibZoneStatisticsTable

Object (Type)Description
ibBindZoneName (IbString)DNS Zone name.
ibBindZoneSuccess (Counter64)The number of successful responses since the DNS process started.
ibBindZoneReferral (Counter64)The number of DNS referrals since the DNS process started.
ibBindZoneNxRRset (Counter64)The number of DNS queries received for non-existent records.
ibBindZoneNxDomain (Counter64)The number of DNS queries received for non-existent domains.
ibBindZoneRecursion (Counter64)The number of queries received using recursion since the DNS process started.
ibBindZoneFailure (Counter64)The number of failed queries since the DNS process started.

ibZonePlusViewStatisticsTable

ibZonePlusViewStatisticsTable provides statistical data about DNS views and their zones. It contains the following objects:

Table 11.22 ibZonePlusViewStatisticsTable

Object (Type)Description
ibBindZonePlusViewName (IbString)The zone name. The first one in the default view is the global summary statistics. Index name for global statistics is "summary."
ibBindZonePlusViewSuccess (Counter64)Number of successful responses since the DNS process started.
ibBindZonePlusViewReferral (Counter64)Number of DNS referrals
ibBindZonePlusViewNxRRset (Counter64)

Number of DNS queries received for non-existent records.

ibBindZonePlusViewNxDomain (Counter64)Number of DNS queries received for non-existent domains.
ibBindZonePlusViewRecursion (Counter64)Number of DNS recursive queries received
ibBindZonePlusViewFailure (Counter64)Number of failed queries
ibBindViewName (IbString)View name. This is blank for default view


Following is an example of the table as viewed through a MIB browser:

Figure 11.16 MIB Browser View


ibDDNSUpdateStatistics

ibDDNSUpdateStatistics provides statistical data about DDNS updates. The counters always start with zero when the DNS service is restarted. They report the total numbers since the DNS service was last restarted.
ibDDNSUpdateStatistics contains the following objects:

Table 11.23 ibDDNSUpdateStatistics

Object (Type)

Description
ibDDNSUpdateSuccess (Counter64)The number of successful dynamic DNS updates.
ibDDNSUpdateFailure (Counter64)The number of all failed dynamic DNS updates, excluding those reported by the ibDDNSUpdateReject object.
ibDDNSUpdateReject (Counter64)The number of dynamic DNS updates that failed because they were denied by the DNS server.
ibDDNSUpdatePrerequisiteReject (Counter64)The number of dynamic DNS updates that failed because the prerequisites were not satisfied. This is also included in the total number of failures reported by the ibDDNSUpdateFailure object.

ibBindZoneTransferCount

ibBindZoneTransferCount (Counter64) provides the total number of successful zone transfers from an Infoblox primary or secondary DNS server to a DNS client, since the DNS service was last restarted. Note th at this counter tracks the number of successful full zone transfers (AXFRs) and incremental zone transfers (IXFRs).

  • No labels

This page has no comments.