how to change community name for trap triggered by EMS ?

[Giaumé]

I've declared a monitor request using next command:
emscli -a /storage/status/disks/default/10_0_15_0.6.0 -n 1 -r eq -o ini -p 300 -u sec -t snmp -s cri -c "Created by CLI"

When the alarm condition is meet, an snmp trap is generated with community name = hp_trapGroup.

Is there a way to change the community name of traps generated by ems ?

Pascal Giaumé

[Adisuria Wangsadinata_1]

Hi Pascal,

In an EMS HA Monitor environment, perform the following steps to change the SNMP community name:

1. Edit snmpd.conf in order to change the community name.
2. Kill snmpdm.
3. Execute "snmpd" to start the snmp master agent and subagents.
4. Edit the following two files to add the "-c " string in each line starting MONITOR:

/etc/opt/resmon/dictionary/mibmond.dict
/etc/opt/resmon/dictionary/rdbmsmond.dict
Note: Make sure not to save a backup copy of the original dictionary files in the /etc/opt/resmon/dictionary directory or in any subdirectory of it.
5. Kill the HA Monitors (mibmond, fsmond, pkgmond, etc.. ). These processes will be restarted automatically if needed.
6. Test with "resls -s /system/jobQueue15Min".

Hope this information can help you.

Cheers,
AW

[Giaumé]

Thanks for your help.

Unfortunately it does not solve my problem: all trap community name is still set to "hp_trapGroup".
Here is list of deamons, monitors and snmp processes running:
root 14861 1 0 17:56:16 pts/tf 0:00 ./fsmond
root 14864 1 0 17:56:16 pts/tf 0:00 ./mibmond
root 14869 1 0 17:56:16 pts/tf 0:00 ./clustermond
root 14873 1 0 17:56:16 pts/tf 0:00 ./krmond
root 14876 1 0 17:56:16 pts/tf 0:00 ./p_client
root 14674 1 0 17:56:12 ? 0:00 /etc/opt/resmon/lbin/p_client
root 14881 1 0 17:56:16 ? 0:00 ./emsagent


root 23900 1 0 18:17:12 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/disk_em -c public
root 23447 1 0 18:16:20 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/fpl_em -c public
root 23459 1 0 18:16:20 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/psmmon -c public
root 23942 1 0 18:17:13 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em -c public
root 23888 1 0 18:17:12 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_stape -c public
root 23933 1 0 18:17:13 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em -c public
root 23912 1 0 18:17:13 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_memory -c public
root 23476 1 0 18:16:21 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/ia64_corehw -c public
root 23924 1 0 18:17:13 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw -c public

root 22007 1 0 18:10:08 ? 0:00 /usr/sbin/mib2agt
root 22005 1 0 18:10:08 ? 0:00 /usr/sbin/snmpdm
root 22009 1 0 18:10:08 ? 0:00 /usr/sbin/hp_unixagt
root 22011 1 0 18:10:08 ? 0:00 /usr/sbin/trapdestagt



I've added next entries into snmpd.conf
get-community-name: public
set-community-name: public

On my HP server, there is no /etc/opt/resmon/dictionary/rdbmsmond.dict. I added "-c public" to each monitors dictonary.
I also started /usr/sbin/snmpdm -c public with no success.
Finally I deleted the ems request and created it again with no more success.
Any clue ?