How to map an eHealth MIB object to its OID or vice-versa.

Document ID : KB000023262
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

How to map an eHealth MIB object to its OID or vice-versa.

 

Answer:

The CA eHealth enterprise MIB definition is found in the following files.

 

   $NH_HOME/extensions/mibs/sys/concord-diagmon.mib.pcm  maps the numeric OIDs to the MIB object name.
   $NH_HOME/extensions/mibs/sys/concord-diagmon.mib defines the hierarchy of the MIB, and gives object descriptions.

 

For troubleshooting purposes, I may want to find out the contents of the MIB.  For example, if I wanted to reference the contents of a trap sent from Live Exceptions in order to troubleshoot an issue, I could search concord-diagmon.mib.pcm for the OID in of interest.  To find the MIB object for OID 1.3.6.1.4.1.149.2.3.7:

 

   grep 1.3.6.1.4.1.149.2.3.7 $NH_HOME/extensions/mibs/sys/concord-diagmon.mib.pcm
   _qualified DiagnosticsMonitor nhSeverity 1.3.6.1.4.1.149.2.3.7

 

nhSeverity is the corresponding object.  Now, I can use the object name to find information about this object from concord-diagmon.mib.

 

To find the OID for MIB object nhElementName:

 

   grep  nhElementName $NH_HOME/extensions/mibs/sys/concord-diagmon.mib.pcm
   _qualified DiagnosticsMonitor nhElementName 1.3.6.1.4.1.149.2.3.2 

 

 1.3.6.1.4.1.149.2.3.2 is the corresponding OID.