mibmond configuration

[Mike DiLorenzo]

Hello,

In an HP-UX 11.23i MCOE system, in which the high availablity monitors come standard, is it possible to extend the mibmond dictionary to create new resources from other objects in the HP-UX MIB?

For example, is it possible to create a new resource /system/upTime that displays the value of computerSystemUpTime?

Thanks in advance,
Mike

[Stephen Doud]

The /etc/opt/resmon/dictionary/mibmond.dict defines the monitors available.

Here is the line for filesystem size:

# The filesystem free space, derived from the HP-UNIX MIB
RESOURCE_NAME: /system/filesystem/availMb
MONITOR: /etc/opt/resmon/lbin/fsmond

Note that it relies on a 'fsmond' daemon to collect the information. I'm not an expert in this area, but I'd think it necessary to create an uptime-capturing daemon that could interface properly with the API.

[Mike DiLorenzo]

I was told today that EMS does not use the HP-UX mib. It uses it's own mib which supposedly comes with the EMS Developer's kit, however I did not find it there. So I'm still wondering what else might be available in the EMS mib and if the mibmond dictionary can be extended to define other resources available in the EMS mib. Or perhaps everything that's available in the EMS mib already has a resource created for it? Or perhaps to achieve this functionality I have to create a new EMS monitor...

[Sameer_Nirmal · Accepted solution]

Hi,

Here is my understanding.

I guess the classes, subclasses and resources are pre-defined in the EMS and monitor resources are mentioned in the dictionary files( depends on the EMS product installed)

In those dictionary files, you would see they are referred in a EMS source code. Saying that each resource name should be registered in EMS first before a monitor could monior it.

In case of SNMP based (MIB)EMS mibmond has pre-defined MIB objects i.e. resources as explicitly shown in the mibmond dictionary. The mibmond does make use of SNMP master (snmpdm) and subagents (e.g. hp_unixagt which provides HP-UX MIBs.) but only for those MIBs in the dictionary defined as "resources". So unless a resource is pre-defined in a monitor and registered with EMS, simply adding it the dictionary won't make sense and could be a void entry. Based on the dictionary entries, the registrar would call the concerned monitor because it knows that monitor can monitor the resource.

The computerSystemUpTime is SNMP MIB object and unless it is defined/registered in EMS as resource through a monitor, you can't use it directly.

The SNMP traps defined in the EMS are provided as templates in the Developer kit which could be used for writing monitors for OV applications like OV/ITO , OV NNM.