I saw that there is a FanOutOfRangeOrMalfunctioning in the Management Event Configuration, then I would like to know whether I can create this event to the SNMP Trap Configuration as well.
Thanks & Best Regards,
what you want to achieve?
Management incidents of node componnets like fans are created as a result of :
1. discovery of fan on managed node (see NNMi support matrix for vendors/devices models where fans can be discovwred)
2. NNMi active polling and analysis of the results.
SNMP trap is event what managed node is sending to NNMi. Different vendors /devices are sending their specific SNMP traps about the fan statuses. First of all you have to found what types of the devices are in your network and then look into relevant MIBs.
For example on NNMI out of the box you already have: CiscoEnvMonFanStatusChangeNotif .220.127.116.11.18.104.22.168.22.214.171.124, RcChasFanDown .126.96.36.199.4.1.22188.8.131.52 (RAPID CITY MIB)
Other vendors like Alteon switch trap is altSwFanFailure .184.108.40.206.4.1.18220.127.116.11.0.24 , F5 bigipChassisFanBad .18.104.22.168.4.1.3322.214.171.124.8. So relevant MIBs must be loaded and SNMP traps incidents configured in NNMI.
my 2 cents
Thanks for your information. Acutally I have tried to test the nnmsnmpnotify.ovpl -a Cisco3850ip nnmip .126.96.36.199.188.8.131.52.184.108.40.206 and it's working, therefore I replaced the oid .220.127.116.11.18.104.22.168.22.214.171.124.15 with the same command, but showed nothing on the incident browsing, and I'm very confused why I couldn't find the oid .126.96.36.199.188.8.131.52.184.108.40.206.15 from snmpwalk tool.
Thanks & Best Regards,
the .220.127.116.11.18.104.22.168.22.214.171.124.15 is a NNMi internal incident (Management Event) and you cannot use ot with snmptrap. You have to create your own SNMP trap incident configuration if you want to use a script to sent events to NNMi or devices will sent you SNMP traps which are documented in their MIB definitions.
HTH and kind regards
As Allessandro stated, the Internal NNMi management incidents can't be "mimiced" using traps. However it is possible to raise some of them using the jmx-console which can then inject them into the internal event stream for test purposes. Unfortunately the incident referenced in this thread has not been implemented, I did check ! The jmx-console is a support tool and therefore there are limitations and only a certain set of the management incidents have been implemented. to date.
All the best