Search

Page tree

Contents

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. Figure 39.2 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 Figure 39.2, 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 Infoblox MIBs.

Figure 39.2 MIB Hierarchy

MIB Objects

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

OBJECT-TYPE

sysObjectID

SYNTAX

Object Identifier

MAX-ACCESS

read-only

STATUS

current

DESCRIPTION

"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'."


Table 39.3 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

1001

ibRsp2

vNIOS appliances on Riverbed Services Platforms

1002

ibCisco

Cisco servers

1003

ibvm

vNIOS appliances on VMware ESX or ESXi servers

1004

ibvnios

Virtual NIOS

1401

ib810

Trinzic 810 appliances

1402

ib820

Trinzic 820 appliances

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

1413

ib2220

Trinzic 2220 appliances

1414

pt2200

Advanced 2200 appliances

1421

ib4010

Infoblox-4010 appliances

1422

ib4030

Infoblox-4030 appliances

1423

ib4000

Infoblox-4000 appliances

1424

pt4000

Advanced 4000 appliances

1431

ib100

Trinzic 100 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

1501ib815Trinzic 815 appliances
1502ib825Trinzic 825 appliances
1503ib1415Trinzic 1415 appliances
1504ib1425Trinzic 1425 appliances
1505ib1405Trinzic 1405 appliances
1506ib805Trinzic 805 appliances
1507pt1405Advanced 1405 appliances
1511ib2205Trinzic 2205 appliances
1512ib2215Trinzic 2215 appliances
1513ib2225Trinzic 2225 appliances
1514pt2205Advanced 2205 appliances
1521ib4015Trinzic 4015 appliances
1522ib4035Trinzic 4035 appliances
1523ib4005Trinzic 4005 appliances
1524pt4005Advanced 4005 appliances
1525ib4025Trinzic 4025 appliances
1541nd805Network Insight 805 appliances
1542nd1405Network Insight 1405 appliances
1543nd2205Network Insight 2205 appliances
1544nd4005Network Insight 4005 appliances


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:

  1. Configure a NIOS 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 Data Management tab, select the Grid tab -> Grid Manager tab, 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 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:

  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
  6. IB-DNSSERV-MIB.txt
  7. IB-DHCPSERV-MIB.txt
  8. 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

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 Grid member for the member to send SNMP traps. For information, see SNMPMIB 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.1IP 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

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. Figure 39.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 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.

Figure 39.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 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. 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 NIOS appliance can send. There are five types of SNMP traps.

Table 39.4 describe the types of traps and their objects in the ibTrapOneModule tree.


Note: Some SNMP traps for ibThresholdCrossingEvent, ibStateChangeEvent, ibProcStartStopTrap, and ibRevokedLicenseTrap do not have an associated ibProbableCause. The following table lists traps that provide ibProbableCause and those that do not have an ibProbableCause value.



Table 39.4 ibTrapOneModule

Trap Binding Variables (OID 3.1.1.1.2)

OID

Trap Type

MIB Object

Description

3.1.1.1.1.1

Equipment Failure

ibEquipmentFailureTrap

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

ibProcessingFailureTrap

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

For a list of trap descriptions, see Processing and Software Failure Traps.

3.1.1.1.1.3

Threshold Crossing

ibThresholdCrossingEvent

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. For more information about tracking IP address usage, see Threshold Crossing Traps.
  • 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

For a list of trap descriptions, see Threshold Crossing Traps.

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

For a list of possible trap descriptions, see Object State Change Traps

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

For a list of possible trap descriptions, see Process Started and Stopped Traps.

3.1.1.1.1.6


ibRevokedLicenseTrap

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

Table 39.5 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)

The probable cause of the trap. See ibProbableCause Values for the definitions of each value.

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.5.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)

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. For more information, see Threshold Crossing Traps.

3.1.1.1.2.8.0

ibThresholdLow (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. For more information, see Threshold Crossing Traps.

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

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)

Table 39.6 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 for process failures, that trigger SNMP traps.

Table 39.6 ibProbableCause Values


Value

OID 3.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.

15

ibSSHDSoftwareFailure

An SSH daemon failure has occurred.

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.

36ibAuthDHCPNamedSoftwareFailureAn auth named server failure has occurred.
37ibFan1FailureFan 1 failure has occurred.
38ibFan2FailureFan 2 failure has occurred.
39ibFan3FailureFan 3 failure has occurred.
40ibFan1OKFan 1 is OK.
41ibFan2OKFan 2 is OK.
42ibFan3OKFan 3 is OK.
44ibFTPDSoftwareFailureAn FTPD daemon failure has occurred.
45ibBloxtoolsSoftwareFailureA Bloxtools service failure has occurred.
46ibPowerSupplyOKThe power supply is OK.
47ibWebUISoftwareFailureA WebUI software failure has occurred.
48ibUNUSED48Unused.
49ibADAgentSyncFailure

An AD agent client synchronizing domain data failure has occurred.

50ibIFMAPSoftwareFailureAn IF-MAP server failure has occurred.
51ibCaptivePortalSoftwareFailureA Captive Portal service failure has occurred.
52ibDuplicateIPAddressFailureA Duplicate IP Address has been detected.
53ibBGPSoftwareFailureAn BGP routing daemon failure has occurred.
54ibRevokedLicenseA license has been revoked.
58ibGUILoginFailureAn admin failed to log in to the GUI.
59ibSerialConsoleLoginFailureAn admin failed to log in to the serial console.
60ibSystemRebootA system reboot was initiated.
61ibSystemRestartA system restart was initiated.
62ibZoneTransferFailureA zone transfer failure occurred.
63ibDHCPLeaseConflictDHCP address conflicts with an existing lease.
64ibDHCPAddressConflictDHCP address conflicts with an existing fixed address.
65ibDHCPRangeConflictDHCP address conflicts with an existing range.
66ibDHCPHostConflictDHCP address conflicts with an existing host.
67ibSyslogFailureA syslog daemon failure occurred.
68ibPowerSupply1FailurePower supply 1 failure has occurred.
69ibPowerSupply2FailurePower supply 2 failure has occurred.
70ibPowerSupply1OKPower supply 1 is OK.
71ibPowerSupply2OKPower supply 2 is OK.
72ibReportingTaskSwFailureA reporting task monitoring failure has occurred.
73ibReportingDbBackupFailure

A reporting db backup/restore operation failure has occurred.

74ibFan4FailureFan 4 failure has occurred.
75ibFan5FailureFan 5 failure has occurred.
76ibFan6FailureFan 6 failure has occurred.
77ibFan7FailureFan 7 failure has occurred.
78ibFan8FailureFan 8 failure has occurred.
79ibFan4OKFan 4 is OK.
80ibFan5OKFan 5 is OK.
81ibFan6OKFan 6 is OK.
82ibFan7OKFan 7 is OK.
83ibFan8OKFan 8 is OK.
84ibOSPF6SoftwareFailureAn OSPF6 routing daemon failure has occurred.
85ibOCSPResponderFailureOCSP responder failed.
86ibReportingAlertTriggeredA reporting alert is triggered.
87ibCapturedQueriesUploadFailureUpload for captured DNS queries failed.
88ibLDAPServerFailureThe LDAP server failed.
89ibRIRWIPRegistrationFailureRIR SWIP registration failed.
90ibPowerSupply1RemovedPower supply 1 has been removed.
91ibPowerSupply2RemovedPower supply 2 has been removed.
92ibIPMISensorErrorDetected

Error detected on the sensor for the IPMI port (used for LOM)

93ibDiscoveryConsolidatorTaskSwFailureDiscovery service on the Consolidator failed.
94ibDiscoveryCollectorTaskSwFailureDiscovery service on probes failed.
95ibDiscoveryBackupSwFailureDiscovery backup service failed.
96ibThreatProtectionAutoDownloadFailureAutomatic download of threat protection rule failed.
97ibThreatProtectionPublishFailureThreat protection rule publish failed.
98ibPassiveHANodeARPConnectivityFailureHA node failed to connect to local router.
99ibPassiveHANodeARPConnectivitySuccessHA node successfully connects to local router.
100ibDNSIntegrityCheckConnectionFailedConnection between Grid member and Grid Master failed.
101ibDNSIntegrityCheckPrimaryServersFailedDNS data (NS RRset) check for Grid primaries failed.
102ibDNSIntegrityCheckNameserversFailedDNS data (NS RRset) check for name servers failed.
103ibCloudAPIFailureCloud API service failed.
104ibRpzRefreshFailureAn RPZ refresh failure has occurred.
105ibUnboundSoftwareFailureUnbound software failure has occurred.
106ibAnalyticsAutoDownloadFailureAutomatic download of analytic module set failed.
107ibDnsHealthCheckFailedThe DNS health check has failed.
108ibDnsHealthCheckSucceedThe DNS health check is successful.
109ibBFDSoftwareFailure

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

110ibOutboundWorkerFailedAn Outbound worker has failed.
3001ibRAIDIsOptimal

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

3002ibRAIDIsDegradedThe system’s RAID array is in a degraded state.
3003ibRAIDIsRebuildingThe system’s RAID array is rebuilding.
3004ibRAIDStatusUnknownUnable to retrieve RAID array state!
3005ibRAIDBatteryIsOKThe system’s RAID battery is OK.
3006ibRAIDBatteryFailedA RAID battery failure has occurred.
3007ibRAIDOptimalMismatch

The system's RAID array is now running in an optimal state (Mismatched disk(s) found).

3008ibRAIDDegradedMismatch

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

3009ibRAIDRebuildingMismatch

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

3010ibRAIDBatteryWeakPlease replace the system's RAID battery soon.
3011ibRAIDIsDegradedDisk1

The system's RAID array is in a degraded state. RAID Disk1 is EMPTY.

3012ibRAIDIsDegradedDisk2The system's RAID array is in a degraded state. RAID Disk2 is EMPTY.
3013ibRAIDIsDegradedDisk3The system's RAID array is in a degraded state. RAID Disk3 is EMPTY.
3014ibRAIDIsDegradedDisk4The system's RAID array is in a degraded state. RAID Disk4 is EMPTY.
3015ibRAIDIsDegradedDisk5The system's RAID array is in a degraded state. RAID Disk5 is EMPTY.
3016ibRAIDIsDegradedDisk6The system's RAID array is in a degraded state. RAID Disk6 is EMPTY.
3017ibRAIDIsDegradedDisk7The system's RAID array is in a degraded state. RAID Disk7 is EMPTY.
3018ibRAIDIsDegradedDisk8The system's RAID array is in a degraded state. RAID Disk8 is EMPTY.
3019ibRAIDIsRebuildingDisk1

The system's RAID array is rebuilding. RAID Disk1 is OFFLINE.

3020ibRAIDIsRebuildingDisk2The system's RAID array is rebuilding. RAID Disk2 is OFFLINE.
3021ibRAIDIsRebuildingDisk3The system's RAID array is rebuilding. RAID Disk3 is OFFLINE.
3022ibRAIDIsRebuildingDisk4The system's RAID array is rebuilding. RAID Disk4 is OFFLINE.
3023ibRAIDIsRebuildingDisk5The system's RAID array is rebuilding. RAID Disk5 is OFFLINE.
3024ibRAIDIsRebuildingDisk6The system's RAID array is rebuilding. RAID Disk6 is OFFLINE.
3025ibRAIDIsRebuildingDisk7The system's RAID array is rebuilding. RAID Disk7 is OFFLINE.
3026ibRAIDIsRebuildingDisk8The system's RAID array is rebuilding. RAID Disk8 is OFFLINE.
3027ibRAIDDegradedMismatchDisk1

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

3028ibRAIDDegradedMismatchDisk2The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk2 is EMPTY.
3029ibRAIDDegradedMismatchDisk3The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk3 is EMPTY.
3030ibRAIDDegradedMismatchDisk4The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk4 is EMPTY.
3031ibRAIDDegradedMismatchDisk5The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk5 is EMPTY.
3032ibRAIDDegradedMismatchDisk6The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk6 is EMPTY.
3033ibRAIDDegradedMismatchDisk7The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk7 is EMPTY.
3034ibRAIDDegradedMismatchDisk8The system's RAID array is in a degraded state (Mismatched disk(s) found). RAID Disk8 is EMPTY.
3035ibRAIDRebuildingMismatchDisk1

The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk1 is OFFLINE.

3036ibRAIDRebuildingMismatchDisk2The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk2 is OFFLINE.
3037ibRAIDRebuildingMismatchDisk3The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk3 is OFFLINE.
3038ibRAIDRebuildingMismatchDisk4The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk4 is OFFLINE.
3039ibRAIDRebuildingMismatchDisk5The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk5 is OFFLINE.
3040ibRAIDRebuildingMismatchDisk6The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk6 is OFFLINE.
3041ibRAIDRebuildingMismatchDisk7The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk7 is OFFLINE.
3042ibRAIDRebuildingMismatchDisk8The system's RAID array is rebuilding (Mismatched disk(s) found). RAID Disk8 is OFFLINE.
3043ibRAIDIsInoperableThe system’s RAID array is inoperable.
3044

ibRAIDPredictedDegraded

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

ibRAIDPredictedDegradedDisk2

The system's RAID array is in a predicted degraded state. RAID Disk2 is in such predicted degraded state.
3047ibRAIDPredictedDegradedDisk3The system's RAID array is in a predicted degraded state. RAID Disk3 is in such predicted degraded state.
3048ibRAIDPredictedDegradedDisk4The system's RAID array is in a predicted degraded state. RAID Disk4 is in such predicted degraded state.
3049ibRAIDPredictedDegradedDisk5The system's RAID array is in a predicted degraded state. RAID Disk5 is in such predicted degraded state.
3050ibRAIDPredictedDegradedDisk6The system's RAID array is in a predicted degraded state. RAID Disk6 is in such predicted degraded state.
3051ibRAIDPredictedDegradedDisk7The system's RAID array is in a predicted degraded state. RAID Disk7 is in such predicted degraded state.
3052ibRAIDPredictedDegradedDisk8The system's RAID array is in a predicted degraded state. RAID Disk8 is in such predicted degraded state.
4001ibDisconnectGridAttachFailedA disconnected Grid failed to attach to the Master Grid.
4002ibDisconnectedGridDetachFailedA disconnected Grid failed to detach from the Master Grid.
4003

ibDisconnectedGridDetachFailedSubgrid Offline

An offline Grid failed to detach from the Master Grid.
4004ibDisconnectedGridSnapshotFailedThe snapshot operation failed on a disconnected Grid.
4005ibDnssecAutomaticKSKRolloverApproching

An automatic rollover of the KSK will be performed in seven days.

4006ibDnssecManualKSKRolloverDueApprochingA manual KSK rollover is due within the next seven days.
4007ibDnssecAutomaticKSKRolloverDoneThe KSK has been automatically rolled over.
4008ibDnssecManualKSKRolloverDoneThe KSK has been manually rolled over.
4009ibDnssecKSKRolloverOverdueThe KSK rollover is overdue.
4010ibPortDiscoveryConflictA port detection conflict has been detected.
4011ibDeviceDiscoveryConflictA device detection conflict has been detected.
4012ibDeviceUnmanaged

New unmanaged devices/networks were found during network discovery process.

4013ibAnalyticsDnstUpdateThe DNS tunneling detection has occurred.
4014ibSyslogBackupDoneThe syslog backup process is successful.
4015ibSyslogBackupFailedThe syslog backup process failed.

ibSubsystemName Values (OID 3.1.1.1.2.5.0)

Table 39.7 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.


Table 39.7 ibSubsystemName Values

Value

OID 3.1.1.1.2.5.0 ibSubsystemName

0

Uses the original ibObjectName and ibSubsystemName when the trap is cleared. The process failure trap is appended to the CLEAR trap descriptions.

1N/A
2N/A
3N/A
4N/A
5Db_jnld
6httpd
7serial_console
11controld
12N/A
13Snmpd
15Sshd
16Ntpd
17Clusterd
18Lcd
19Dhcpd
20Named
24NTLM
25Netbiosd
26Winbindd
27Tftpd
29N/A
30db_dump
31N/A
32Scheduled_backups
33N/A
34HTTPd
35OSPF
36AuthDhcpNamed
44ftpd
45bloxtools
47webui
50ifmap
51captive_portal
53BGP
58GUI_Login
72Reporting_task
84OSPF6
95Discovery_backups
105Unbounds
-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. Table 39.8 shows the message and description for 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.

26

ftp-service-working

FTP service is working.

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.

34

dns-service-inactive

DNS service is inactive.

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.

46

dhcp-service-warning

DHCP service is in warning state.

47

dhcp-service-failed

DHCP service failed.

48

dhcp-service-inactive

DHCP service is inactive.

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.

69

subgrid-attached

In a Multi-Grid configuration, sub Grid is attached to the Master Grid.

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.

111

ipmi-device-available

IPMI device is available again.

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

outbound-service-manager-started

OUTBOUND Service Manager is working.

130

outbound-service-manager-failed

OUTBOUND Service Manager is failed.

131

outbound-service-manager-stopped

OUTBOUND Service Manager is inactive.

133imc-servers-okSubscriber Collection Service is working.
134imc-server-failureSubscriber Collection Service failed.
135imc-servers-unavailableAll NAS gateways are unavailable.
136imc-service-inactiveSubscriber Collection Service is inactive.
137imc-symantec-service-unavailableInitial category information data is downloading.
138imc-server-initializingInitial Subscriber Collection service interim interval.


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.



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.

No action is required.

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

No action is required.

Syslog Backup Processes

The syslog backup process is successful.

Informational

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

No action is required.

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


Note: 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 Table 39.7 



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

DNS ONE quagga Processes (zebra & ospfd)

An OSPF routing daemon failure has occurred.

Critical

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

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

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.

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>/<IP address> 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>/<IP address> 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>/<IP address> 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>/<IP address> 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>/<IP address> is OK.

Informational

The Microsoft DNS service is responding.

No action is required.

Service connection to Microsoft DHCP server
<hostname>/<IP address> 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.

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.

Informational

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 Resolving DHCP Lease Conflicts.

DHCP Fixed Address Conflict

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 Resolving Fixed Address 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 DHCP Range 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 Resolving Host 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.

Informational

DNS Health Check query has succeeded.

No action required.

Syslog Daemon Failure

Syslog daemon is not running.

Critical

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.

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

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.

Critical

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

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

Unbound Software Failed

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

No action is required.

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.

No action is required.

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.

No action is required.

SNMP Trap is cleared. OSPF

N/A

The SNMP Trap for OSPF is cleared.

No action is required.

SNMP Trap is cleared. OSPF6

N/A

The SNMP Trap for OSPF6 is cleared.

No action is required.

SNMP Trap is cleared. BGP

N/A

The SNMP Trap for BGP is cleared.

No action is required.

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.

Informational

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.

No action is required.


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.

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

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

Minor

memory

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

No action is required.

Primary Hard Drive Usage (monitored every 30 seconds)

System primary hard disk usage is over threshold value.

Minor

disk_usage

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.

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

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.

No action is required.

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.

No action is required.

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 Thresholds for 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.

No action is required.

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.

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

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
percentage> (80% by default)
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.

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

DHCP high threshold reset:
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
percentage> (80% by default)
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:
<network>/
<network view>

N/A

Threshold

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

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

Network Container IPAM Utilization capacity usage is over the threshold value. Network container:
<network>/
<network view>

N/A

Threshold

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

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

Network IPAM Utilization capacity usage is OK. Network:
<network>/
<network view>

N/A

Threshold

The appliance sends this trap when the IPAM utilization for a network is below the configured Reset value.

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

Network Container IPAM Utilization capacity usage is OK. Network container:
<network>/
<network view>

N/A

Threshold

The appliance sends this trap when the IPAM utilization for a network container is below the configured Reset value.

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>

N/A

Threshold

The DNS updates were deferred because of DDNS update errors.

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

RPZ Hit Rate

RPZ hit rate exceed normal value.

N/A

Threshold

The appliance sends this trap when the RPZ hit rate exceeds the configured Trigger value.

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

RPZ hit rate has returned to normal value.

N/A

Threshold

The appliance sends this trap when the RPZ hit rate equals the configured Reset value.

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

Threat Protection Total Traffic

Threat Protection Service total traffic is above threshold.

N/A

Threshold

The appliance sends this trap when the Treat Protection total traffic exceeds the configured Trigger value.

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

Threat Protection Service total traffic is OK.

N/A

Threshold

The appliance sends this trap when the Threat Protection total traffic is less than the configured Reset value.

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

Threat Protection Dropped Traffic

Threat Protection Service dropped traffic is above threshold.

N/A

Threshold

The appliance sends this trap when the Treat Protection dropped traffic exceeds the configured Trigger value.

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

Threat Protection Service dropped traffic is OK.

N/A

Threshold

The appliance sends this trap when the Threat Protection dropped traffic is less than the configured Reset value.

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

Database Capacity Usage

Database capacity used is over the threshold value.

Minor

db_usage

The appliance database usage exceeded the configured threshold value.

Increase the database capacity.

Database capacity used is OK.

Minor

db_usage

The appliance database usage is less than the configured threshold value.

No action is required.

DNS Monitor

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

Major

dns_security_ port

DNS security alert. There were actual DNS responses to invalid ports 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.
  • 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. For information, see Configuring Rate Limiting Rules.

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

N/A

dns_security_t xid

DNS security alert. There were actual DNS responses 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 that 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 with invalid TXID 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. For information, see Configuring Rate Limiting Rules.

RootFS Partition Monitor

Root file system is full.

Major

Root filesystem

The Root filesystem usage exceeded the maximum.

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

Root file system disk usage is over threshold value.

Minor

Root filesystem

The appliance sends this trap when the Root filesystem usage first exceeds the configured Trigger value.

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

Root file system disk usage is OK.

Minor

Root filesystem

The appliance sends this trap when the Root filesystem disk usage first moves at or below the configured Reset value after it exceeded the Trigger value. For information on setting the Trigger and Reset values, see Defining Thresholds for Traps.

No action.

Reporting

Reporting drive is full.

Major

Reporting

Reporting drive reached the maximum capacity.

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

Reporting drive usage is over threshold value.

Minor

Reporting

The appliance sends this trap when the Reporting volume first exceeds the configured Trigger value. The default Trigger value is 80.

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

Reporting drive usage is OK.

Minor

Reporting

The appliance sends this trap when the Reporting volume first moves at or below the configured Reset value after it exceeded the Trigger value. The default Reset value is 71.

For information on setting the Trigger and Reset values, see Defining Thresholds for Traps.

No action.

File Distribution

File Distribution services storage usage reached the threshold value.

N/A

File Distribution

File distribution service storage reached the configured threshold value.

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


Object State Change Traps

ibTrapDesc
OID 3.1.1.1.2.11.0

ibTrapSeverity

Description/Cause

Recommended Actions

Service Shutdown

Shutting down services due to database snapshot.

Major

The appliance is shutting down its services while synchronizing the database with the Grid Master.

No action is required.

Network Interfaces Monitoring

LAN1 port link is down. Please check the connection.

Major

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

Check the LAN1 link connection.

LAN2 port link is down. Please check the connection.

Major

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

Check the LAN2 link connection.

HA port link is down. Please check the connection.

Major

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

Check the HA link connection.

MGMT port link is down. Please check the connection.

Major

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

Check the MGMT link connection.

LAN1 port link is up.

Major

The LAN1 port link is up and running.

No action is required.

LAN2 port link is up.

Major

The LAN2 port link is up and running.

No action is required.

HA port link is up.

Major

The HA port link is up and running.

No action is required.

MGMT port link is up.

Major

The MGMT port link is up and running.

No action is required.

HA State Change from Initial to Active

The node has become ACTIVE.

Informational

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.

Informational

The node changed from a passive to an active node.

No action is required.

HA State Change to Active-Active

The node is in an ACTIVE-ACTIVE state.

Informational

The node is in the active state.

No action is required.

HA State Change from Initial to Passive

The node has become PASSIVE.

Informational

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.

Informational

The Grid member joined the Grid, and it is not a Grid Master candidate.

No action is required.

Node Disconnected from Grid

The Grid member is not connected to the Grid master.

Informational

The Grid member lost its connection to the Grid Master.

No action is required.

Replication State Monitoring

HA replication is online.

Informational

The HA replication is online.

No action is required.

HA replication is offline.

Informational

The HA replication is offline.

No action is required.

NTP is out of sync, monitored every 30 seconds

The NTP service is out of synchronization.

Major

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

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

NTP Service is working.

Informational

The NTP service started working again.

No action is required.

NTP service is synchronizing to local clock

The NTP service is synchronizing to local clock.

Major

The Infoblox NTP server synchronizes its clients with its local clock.

No action is required.

DHCP service state change

DHCP Service is working.

Informational

The DHCP service started working again.

No action is required.

DHCP Service is in a warning state.

Informational

The DHCP service is in a warning state.

Review the syslog file

DHCP Service is inactive.

Informational

The DHCP service became inactive.

Check if an admin disabled the service.

DNS service state change

DNS Service is working.

Informational

The DNS service started working again.

No action is required.

DNS Service is in a warning state.

Informational

The DNS service is in a warning state.

Review the syslog file.

DNS Service is inactive.

Informational

The DNS service became inactive.

Check if an admin disabled the service.

NTP service state change

The NTP service resumed synchronization.

Informational

The NTP service started working again.

No action is required.

NTP Service is inactive.

Informational

The NTP service became inactive.

Check if an admin disabled the service.

TFTP service state change

TFTP Service is working.

Informational

The TFTP service started working again.

No action is required.

TFTP Service is inactive.

Informational

The TFTP service became inactive.

Check if an admin disabled the service.

FTP service state change

FTP Service is working.

Informational

The FTP service started working again.

No action is required.

FTP Service is inactive.

Informational

The FTP service became inactive.

Check if an admin disabled the service.

HTTP service state change

HTTP File Dist Service is working.

Informational

The HTTP file distribution service started working again.

No action is required.

HTTP File Dist Service is inactive.

Informational

The HTTP file distribution service became inactive.

Check if an admin disabled the service.

bloxTools service state change

BloxTools Service is working.

Informational

The bloxTools service started working again.

No action is required.

BloxTools Service is in warning state.

Informational

The bloxTools service is in a warning state.

Review the syslog file.

BloxTools Service is inactive.

Informational

The bloxTools service became inactive.

Check if an admin disabled the service.

BloxTools Service failed.

Critical

The bloxTools daemon failed.

Review the syslog file.

Captive Portal service state change

Captive Portal Service is working.

Informational

The captive portal service started working again.

No action is required.

Captive Portal Service is inactive.

Informational

The captive portal service became inactive.

Check if an admin disabled the service.

Discovery Collector service state change

Discovery Collector Service is working.

Informational

The discovery collector service started working again.

No action is required.

Discovery Collector Service is inactive.

Informational

The discovery collector service became inactive.

Check if an admin disabled the service.

Discovery Collector Service is in warning state.

Informational

The discovery collector service is in a warning state.

Review the syslog file.

Discovery Collector Service has failed.

Informational

The discovery collector service has failed.

Review the syslog file.

Discovery Collector service state change

Discovery Consolidator Service is working.

Informational

The discovery consolidator service started working again.

No action is required.

Discovery Consolidator Service is inactive.

Informational

The discovery consolidator service became inactive.

Check if an admin disabled the service.

Discovery Consolidator Service is in warning state.

Informational

The discovery consolidator service is in a warning state.

Review the syslog file.

Discovery Consolidator Service has failed.

Critical

The discovery consolidator service has failed.

Review the syslog file.

IF-MAP service state change

IFMAP Service is inactive.

Informational

The IF-MAP service became inactive.

Check if an admin disabled the service.

IFMAP Service is working.

Informational

The IF-MAP service started working again.

No action is required.

LDAP service state change

LDAP service is inactive.

Informational

The LDAP service became inactive.

Check if an admin disabled the LDAP service.

All LDAP servers are available.

Informational

All LDAP servers are available.

No action is required.

At least one LDAP server is unavailable.

Major 

At least one LDAP server is out of service.

  • Check if an admin disabled the LDAP server.
  • Review the syslog file.

All LDAP servers are unavailable.

Informational

All LDAP servers are not available.

  • Check if an admin disabled the LDAP server.
  • Review the syslog file.

Certificate Authentication Service state change

CAS service is working.

Informational

The certificate authentication service started working again.

No action is required.

CAS service is inactive.

Informational

The certificate authentication service became inactive.

Check if an admin disabled the service.

OCSP responders state change

All OCSP responders available.

Informational

The OCSP responders are available.

No action is required.

All OCSP responders are out of service.

Informational

The OCSP responders are out of service.

  • Check if an admin disabled the service.
  • Review the syslog file.

OCSP service inactive.

Informational

The OCSP responders service became inactive.

  • Check if an admin disabled the service.
  • Review the syslog file.

Reporting service state change

Reporting Service is working.

Informational

The Reporting service started working again.

No action is required.

Reporting Service is inactive.

Informational

The Reporting service became inactive.

Check if an admin disabled the service.

Reporting Service is in warning state.

Informational

The Reporting service is in warning state.

Review the audit log file.

Threat Analytics state change

Threat Analytics Service is working.

Informational

The Threat Analytics service started working again.

No action is required.

Threat Analytics Service is inactive.

Informational

The Threat Analytics service became inactive.

Check if an admin disabled the service.

Threat Analytics Service is failed.

Informational

The Threat Analytics service has failed.

Review the audit log file.

Threat Analytics Service is in warning state.

Informational

The Threat Analytics service is in warning state.

Review the audit log file.

RPZ refresh state change

RPZ refresh is OK.

Informational

An RPZ refresh succeeded. The appliance sends this trap every time an RPZ zone transfer is successful.

No action is required.

Cisco ISE service state change

Cisco ISE server is OK.

Informational

The Cisco ISE service started working again.

No action is required.

Connection Error has occurred In Cisco ISE server.

Informational

There is a loss of connection between the NIOS appliance and Cisco ISE server.

  • Check if an admin disabled the service.
  • Review the audit log file.

Cloud API service state change

Cloud API service is working.

Informational

The Cloud API service started working again.

No action is required.

Cloud API service is inactive.

Informational

The Cloud API service became inactive.

  • Check if an admin disabled the Cloud API service.
  • Review the audit log file.

Cloud API service has failed.

Critical

The Cloud API service has failed.

  • Check if an admin disabled the Cloud API service.
  • Review the audit log file.

DNS Integrity Check state change

DNS Integrity Check is working.

Informational

The DNS Integrity Check started working again.

No action is required.

DNS Integrity Check failed.

Informational

The DNS Integrity Check has failed.

  • Check if an admin disabled the service.
  • Review the audit log file.

DNS Integrity Check severity has changed.

Informational

The DNS Integrity Check has changed.

Review the syslog file.

TAXII service state change

TAXII service is working.

Informational

The TAXII service started working again.

No action is required.

TAXII Service is failed.

Informational

The TAXII service has failed.

  • Check if an admin disabled the service.
  • Review the audit log file.

TAXII service is inactive.

Informational

The TAXII service became inactive.

  • Check if an admin disabled the service.
  • Review the audit log file.

TAXII Service is in warning state.

Informational

The TAXII service is in warning state.

Review the audit log file.

Outbound service state change

The Outbound Service Manager stopped.

Informational

The Outbound service manager has stopped working.

  • Check if an admin disabled the service.
  • Review the audit log file.

The Outbound Service Manager failed.

Major

The Outbound service manager has failed.

  • Check if an admin disabled the service.
  • Review the audit log file.

The Outbound Service Manager started.

Informational

The Outbound service manager has started.

No action is required.

The Outbound worker failed.

Major

The Outbound worker has failed.

Review the audit log file.

IPMI Device state change

IPMI is used by some hardware monitors to test hardware health. The IPMI Device has not responded. Hardware monitors may show spurious failures.

Informational

The IPMI Device has not responded.

  • Check if an admin disabled the IPMI interface.
  • Review the audit log file.

IPMI is used by some hardware monitors to test hardware health. Because the IPMI Device has not responded for a while, hardware monitor failures are likely to be spurious.

Informational

The IPMI Device has not responded.

  • Check if an admin disabled the IPMI interface.
  • Review the audit log file.

IPMI is used by some hardware monitors to test hardware health. The IPMI Device is now available; subsequent hardware monitor failures are likely to be genuine.

Informational

The IPMI Device is now available

No action required.


Process Started and Stopped Traps

ibTrapDesc
OID 3.1.1.1.2.11.0


ibTrapSeverity


Description/Cause


Recommended Actions

Httpd Start

The process started normally.

Informational

The httpd process started.

No action is required.

Httpd Stop

The process stopped normally.

Informational

The httpd process stopped.

No action is required.

Process Stop/Start




The system stopped and started a process.

Major

The system restarted a process.

No action is required.

Zone Transfer Failed

A zone transfer failure has occurred.

Critical

A zone transfer failed.

Review the syslog file.


Revoked License Trap

ibTrapDesc
OID 3.1.1.1.2.11.0

ibTrapSeverity

Description/Cause

Recommended Actions

Revoked License




This trap is generated when a license is revoked.

Critical

A license was revoked.

Obtain and install new license.

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 39.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 non authoritative 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 NIOS appliance.
  • ibSerialNumber (IbString) provides the serial number of the Infoblox hardware platform.
  • ibNiosVersion (IbString) provides the version of the NIOS software.
  • ibSystemMonitor provides information about the CPU and memory utilization of the appliance. For information, see ibSystemMonitor.
  • ibGridStatus provides information about an appliance. It indicates whether the appliance is a Grid Master, member, or an independent appliance.
  • ibHAStatus provides information about the HA status of a member. It indicates if the member is part of an HA configuration, and if it is the active or passive node.
  • ibGridMasterCandStatus indicates if a member is a Grid Master candidate.
  • ibGridMasterVIP provides the Grid Master virtual IP address.
  • ibGridReplicationState provides information about the replication status.

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.
  • ibMemberNodeServiceStatusTable provides status of the system and hardware services on a queried appliance. For information, see ibMemberNodeServiceStatusTable.
  • ibMemberPassiveNodeServiceStatusTable 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 ibMemberPassiveNodeServiceStatusTable.



Figure 39.4 ibPlatformOne MIB Structure

 

ibClusterReplicationStatusTable

ibClusterRepliactionStatusTable (object ID 3.1.1.2.1.2.1) provides information about the Grid replication status. For information about Infoblox SNMP traps, see ibTrapDesc (OID 3.1.1.1.2.11.0).

Figure 39.5 shows the sub branches of ibClusterReplicationStatusTable.

Figure 39.5 ibClusterReplicationStatusTable Objects
 

Table 39.9 provides information about the ibClusterReplicationStatusTable objects.
Table 39.9 ibClusterReplicationStatusTableObjects

Object (Type)

Description
ibClusterReplicationStatusEntry

A conceptual row that provides information about the 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 39.6, the ibNetwork Monitor has one subtree, ibNetworkMonitorDNS, that branches out into the following:

  • ibNetworkMonitorDNSActive (Integer) reports on whether DNS latency monitoring is enabled. You can enable DNS latency monitoring using the CLI command set monitor dns. For more information, see Enabling and Disabling DNS Alert Monitoring. 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 non authoritative 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 39.12.


Figure 39.6 ibNetWorkMonitorObjects

 

Figure 39.7 ibNetworkMonitorDNSNonAAandibNetworkMonitorDNSAASub trees



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

Table 39.10 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.

ibNetworkMonitorDNSNonAAT5

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

ibNetworkMonitorDNSNonAAT15

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

ibNetworkMonitorDNSNonAAT60

File 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 39.11 describes the objects in ibNetworkMonitorDNSAA. You can send queries to retrieve values for these objects.

Table 39.11 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 39.12 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 39.12ibNetworkMonitorDNSSecurityObjects

Object (Type)

Description
ibNetworkMonitorDNSSecurityInvalidPort

Tracks the number of invalid DNS responses that arrive on invalid ports. For information about invalid ports, see Monitoring DNS Transactions. This object contains a subtree with six objects that track invalid ports within a certain time interval. For information, see Table 39.13.

ibNetworkMonitorDNSSecurityInvalidTxid

Tracks the number of invalid TXIDs (DNS transaction IDs). For information about invalid TXIDs, see Monitoring DNS Transactions. This object contains a subtree with six objects that track invalid TXIDs within a certain time interval. For information, see Table 39.14.

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 39.13 describes the objects in ibNetworkMonitorDNSSecurityInvalidPort.

Table 39.13 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 15 minutes.

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 39.14 describes the objects in ibNetworkMonitorDNSSecurityInvalidTxid.

Table 39.14 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 39.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.
    • ibSnicCore: Contains ibSnicCore (integer) that contains the smart NIC (SNIC) details. The OID 3.1.1.2.1.8.4.3.1.1.4.112.111.111.108 indicates that the member is a pool, 3.1.1.2.1.8.4.3.1.1.5.99.97.99.104.101 indicates that the member is a cache, 3.1.1.2.1.8.4.3.1.1.5.116.99.111.114.101 indicates that the cache is tcore, and 3.1.1.2.1.8.4.3.1.1.5.109.99.111.114.101 indicates that the cache is mcore.


Figure 39.8 ibSystemMonitor Objects


ibMemberServiceStatusTable

As shown in Figure 39.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 Infoblox Services for 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.

ibMemberServiceStatusTable displays the current status of the Infoblox services on the appliance that you query. For an HA pair, this table displays the service status of the active node. If the appliance you query is the passive node of an HA pair, this table reflects the service status of the passive node, which can be "inactive" or "unknown."
You can also query ibMemberNodeServiceStatusTable and ibMemberPassiveNodeServiceStatusTable that display system and hardware status on the queried appliance. For information, see ibMemberNodeServiceStatusTable and ibMemberPassiveNodeServiceStatusTable.


Figure 39.9 ibMemberServiceStatusTable Objects
 

Infoblox Services for ibMemberServiceStatusTable

Table 39.15 lists the values and descriptions of the Infoblox services that appear in ibMemberServiceStatusTable.

Table 39.15 ibServiceName Values for ibMemberServiceStatusTable

Value

Description

Definition

1

dhcp

DHCP service

2

dns

DNS service

3

ntp

NTP service

4

tftp

File distribution using the TFTP service

5

http-file-dist

File distribution using the HTTP service

6

ftp

File distribution using the FTP service

7

bloxtools-move

Moving the bloxTools service

8

bloxtools

The bloxTools environment

9

node-status

Member status

10

disk-usage

Disk usage

11

enet-lan

LAN port

12

enet-lan2

LAN2 port

13

enet-ha

HA port

14

enet-mgmt

MGMT port

15

lcd

LCD

16

memory

Memory

17

replication

Replication service

18

db-object

Database object

19

raid-summary

RAID array

20

raid-disk1

RAID Disk 1 (For appliances with RAID arrays)

21

raid-disk2

RAID Disk 2 (For appliances with RAID arrays)

22

raid-disk3

RAID Disk 3 (For appliances with RAID arrays)

23

raid-disk4

RAID Disk 4 (For appliances with RAID arrays)

24

raid-disk5

RAID Disk 5 (For appliances with RAID arrays)

25

raid-disk6

RAID Disk 6 (For appliances with RAID arrays)

26

raid-disk7

RAID Disk 7 (For appliances with RAID arrays)

27

raid-disk8

RAID Disk 8 (For appliances with RAID arrays)

28

fan1

Fan 1

29

fan2

Fan 2

30

fan3

Fan 3

31

fan4

Fan 4

32

fan5

Fan 5

33

fan6

Fan 6

34

fan7

Fan 7

35

fan8

Fan 8

36

power-supply1

Power supply 1

37

power-supply2

Power supply 2

38

ntp-sync

NTP synchronization

39

cpu1-temp

CPU temperature

40

cpu2-temp

CPU temperature

41

sys-temp

System temperature

42

raid-battery

RAID battery

43

cpu-usage

CPU usage

44

ospf

OSPF

45

bgp

BGP

46

mgm-service

Multi-Grid management

47

subGrid-conn

Grid in Master Grid

48

network-capacity

Network capacity

49

reporting

Reporting service

50

dns-cache-acceleration

DNS Cache Acceleration services

51

ospf6

OSPF6

57

cloud-api

Cloud API service

Service Status

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

Table 39.16 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.

ibMemberNodeServiceStatusTable

As shown in Figure 39.10, ibMemberNodeServiceStatusTable (object ID 3.1.1.2.1.10) has one subtree, ibMemberNodeServiceStatusEntry, which contains the following objects:

  • ibMemberNodeServiceName (String) reports the names of the system and hardware services. For a list of service names, see Infoblox Services for ibMemberServiceStatusTable.
  • ibMemberNodeServiceStatus (Integer) reports the status of the services. For a list of service status, see Service Status.
  • ibMemberNodeServiceDesc (String) describes the details of the status.

ibMemberNodeServiceStatusTable 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 ibMemberPassiveNodeStatusTable to get the status of the passive node. For information, see ibMemberPassiveNodeServiceStatusTable.


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




Figure 39.10 ibMemberNodeServiceStatusTable Objects

ibMemberPassiveNodeServiceStatusTable

As shown in Figure 39.11, ibMemberPassiveNodeServiceStatusTable (object ID 3.1.1.2.1.2.11) has one subtree, ibMemberPassiveNodeServiceStatusEntry, which contains the following objects:

  • ibMemberPassiveNodeServiceName (String) reports the names of the system and hardware services. For a list of service names, see Infoblox Services for ibMemberServiceStatusTable.
  • ibMemberPassiveNodeServiceStatus (Integer) reports the status of the services. For a list of possible service status, see Service Status.
  • ibMemberPassiveNodeServiceDesc (String) describes details of the status.

ibMemberPassiveNodeServiceStatusTable 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 39.11 ibMemberPassiveNodeServiceStatusTable 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 39.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 39.12 ibDHCPModule

 

ibDHCPSubnetTable

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

Table 39.17 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.

The percentage of dynamic DHCP addresses that are leased out are calculated as the [Total number of active leases in the range + Fixed addresses (leased or unused) + DHCP reservation addresses + Host addresses with DHCP enabled inside the specified subnet]/[Total number of IP address available in the range + Number of Fixed address inside the subnet + Number of IPv4 reservation addresses + Host addresses].

For example:
Network: 10.192.16.0/24
Range: 10.192.16.10 – 10.192.16.20 (11 free IP addresses)
Fixed addresses: 10.192.16.3 (outside DHCP range) and 10.192.16.11 (within DHCP range).

There are 10 free IP addresses in the DHCP Range: 10.192.16.10 – 10.192.16.20 and one fixed address within the DHCP range
IPv4 DHCP Utilization in Infoblox GUI: 16.6% (2/12) -> For this case,
(1 fixed address outside range + 1 fixed address within range) / (fixed address outside DHCP range + number of IP addresses in the DHCP range which includes the fixed address within range)] * 100 = (2/12)*100 -> 17%.

SNMP output from the CLI of the server:

Infoblox > show snmp variable .1.3.6.1.4.1.7779.3.1.1.4.1.1.1.3.11.49.48.46.49.57.50.46.49.54.46.48
IB-DHCPONE-MIB::ibDHCPSubnetPercentUsed."10.192.16.0" = INTEGER: 17.


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


Figure 39.13 MIBBrowserView1

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 39.18 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 39.19 ibDHCPStatistics

Object (Type)Description

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 39.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 39.14 ibDHCPv6Module
 



ibDHCPv6SubnetTable

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

Table 39.20 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 39.21 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 39.22 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 DNS statistics about all zones in all views. Figure 39.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 (Counter64), ibZonePlusViewStatisticsTable (Counter64), ibDDNSUpdateStatistics (Counter64), and ibBindZoneTransferCount (Counter64).

Figure 39.15 ibDNSOne MIB
 
 

Using the DNS Zone Statistics Tables

ibZoneStatistcisTable and ibZonePlusViewStatisticsTable provide DNS statistics for all zones in all DNS views, including the default and all user-defined DNS views. You can use the information in these tables to calculate the total number of recursive queries on the DNS server. Depending on whether your DNS server is an authoritative or a caching-only server, you calculate the total number of recursive queries differently. For information, see Calculating Recursive DNS Queries.

ibZoneStatisticsTable

ibZoneStatisticsTable contains DNS statistics of all zones in the default DNS view. DNS statistics of user-defined DNS views are captured in ibZonePlusViewStatisticsTable. For information, see ibZonePlusViewStatisticsTable.

ibZoneStatisticsTable includes a "summary" zone that provides global statistics for the DNS server, including statistics for all zones in the default and user-defined DNS views.

The syntax of the objects in ibZoneStatisticsTable 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 39.23 ibZoneStatisticsTable

Object (Type)Description

ibBindZoneName (IbString)

DNS zone name. The index name for global statistics is “summary.”

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 recursive queries received since the DNS process started.

ibBindZoneFailure (Counter64)

The number of failed queries since the DNS process started.


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

Figure 39.16 MIBBrowserView


ibZonePlusViewStatisticsTable

ibZonePlusViewStatisticsTable provides DNS statistics about all zones in user-defined DNS views. DNS statistics about zones in the default view are captured in ibZoneStatisticsTable. Note that information in ibZonePlusViewStatisticsTable is rolled up to the "summary" zone in ibZoneStatisticsTable. For information, see ibZoneStatisticsTable.

The syntax of the objects in ibZonePlusViewStatisticsTable 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. ibZonePlusViewStatisticsTable contains the following objects:


Table39.24 ibZonePlusViewStatistics Table

Object (Type)Description

ibBindZonePlusViewName (IbString)

The zone name.

ibBindZonePlusViewSuccess (Counter64)

The number of successful responses since the DNS process started.

ibBindZonePlusViewReferral (Counter64)

The number of DNS referrals since the DNS process started.

ibBindZonePlusViewNxRRset (Counter64)

The number of DNS queries received for non-existent records.

ibBindZonePlusViewNxDomain (Counter64)

The number of DNS queries received for non-existent domains.

ibBindZonePlusViewRecursion (Counter64)

The number of queries that caused recursion since the DNS process started.

ibBindZonePlusViewFailure (Counter64)

The number of failed queries since the DNS process started.

ibBindViewName (IbString)

The DNS view name.

Calculating Recursive DNS Queries

You can use the information in ibZoneStatisticsTable and ibZonePlusViewStatisticsTable to calculate the total number of recursive queries.
Following is an example of ibZoneStatisticsTable indexed by zone names in the default view:


index   ibBindZoneNameibBindZoneSuccessibBindZoneReferralibBindZoneNxRRset

ibBindZoneNxDomainibBindZoneRecursionibBindZoneFailure

=====================================================================================================
"abc.com"abc.com000
       0   0   0
"summary"summary500
       0   0   0
"internal.com"internal.com100

       0   0   0

Following is an example of ibZonePlusViewStatisticsTable indexed by zone names in all user-defined views:


index   ibBindZonePlusViewNameibBindZonePlusViewSuccessibBindZonePlusViewReferralibBindZonePlusViewNxRRset

ibBindZonePlusViewNxDomainibBindZonePlusViewRecursionibBindZonePlusViewFailureibBindViewName

=====================================================================================================
"ext1.com"ext1.com100
        0  00  DNS1
"ext2.com"ext2.com200
        0  00  DNS1
"ext3.com"ext3.com000
        0  00  DNS2
Use the ibBindZoneSuccess object in both tables to determine the total number of recursive queries. If your DNS server is a caching-only server, the total number of recursive queries is the number indicated in the ibBindZoneSuccess object of the "summary" zone. In this example, for a caching-only server, the total number of recursive queries is 5.

If your DNS server is an authoritative server, add all the numbers in ibBindZoneSuccess for all zones in both tables, excluding the "summary" zone. In this example, the total is 4. You then subtract this number from the number in ibBindZoneSuccess of the "summary" zone. In this case, the total number of recursive queries is 1 for an authoritative DNS server.

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:


Table39.25 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 that this counter tracks the number of successful full zone transfers (AXFRs) and incremental zone transfers (IXFRs).

IB-DNSSERV-MIB

The IB-DNSSERV-MIB contains one object, ibDnsServConfig, which reports the DNS BIND version implemented by the NIOS software.

IB-DNSHITRATIO-MIB

The IB-DNSHITRATIO-MIB contains one object, ibDnsHitRatio, which provides information about the DNS cache hit ratio. Note that the MIB variable (ibDNSOne) for cache hit rate has an OID of 1.3.6.1.4.1.7779.3.1.1.3.1.5.0, where 1.3.6.1.4.1.7779 is the prefix.

IB-DNSQUERYRATE-MIB

The IB-DNSQUERYRATE-MIB contains one object, ibDnsQueryRate, which provides information about the DNS queries per second. Note that the MIB variable (ibDNSOne) for DNS query rate has an OID of 1.3.6.1.4.1.7779.3.1.1.3.1.6.0, where 1.3.6.1.4.1.7779 is the prefix.

IB-DHCPSERV-MIB

The IB-DHCPSERV-MIB contains one object, ibDhcpv4ServerSystemDescr, which provides the DHCP server name and its DHCP version.

This page has no comments.