Search

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
titleNote

...

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

...

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
titleNote

...

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.

Anchor
bookmark2894
bookmark2894
Figure 39.3 ibTrapOne MIB Structure

...

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

Note
titleNote

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.


Anchor
bookmark2895
bookmark2895
Table 39.4 ibTrapOneModule
Trap Binding Variables (OID 3.1.1.1.2)

...


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

Anchor
bookmark2896
bookmark2896
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.".

...

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
titleNote

...

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



Anchor
bookmark2905
bookmark2905
Anchor
bookmark2906
bookmark2906
lEquipment Failure Traps

...

 
Anchor
bookmark2907
bookmark2907
Anchor
bookmark2908
bookmark2908
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 

...

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
titleNote

...

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


Anchor
bookmark2935
bookmark2935
Figure 39.10 ibMemberNodeServiceStatusTable Objects

...