I have been working on sending vCOps SNMP traps to Smarts, however the content of the vCOps SNMP trap isn't sufficient to quickly determine the alert type Eg, it simply refers to Resource kind as 'Resource' , the event is too generic.I am also having problems getting the vCenter events (Faults) sent via SNMP from vCOps.
Has anyone any experience with getting vCOps alerts presented to any alert monitoring tool? Or indeed in an environment with vCOps how are you alerted to issues?
This is probably a silly question but did you add an alert handler instance and did you select the alerts to send because those are the steps you need to go through to configure vCenter Operations Manager to send alerts to Smarts.
It is pretty well documented in the EMC Smarts Integration Guide.
Thanks for the replies. I'm not using the vcops-smarts adapter as its not yet certified with vCOps v5 and Smarts v9 - hence I'm trying to use standard SNMP. I have alerts coming through ok, its just the issues outlined in my initial Q.
I am thinking i will have to wait until certification of vcop-smarts adapter, ......
Not necessarily. The details are usually in the trap's variable bindings. Did you try to reconfigure the Smarts Trap Adapter to display the variable bindings in the user defined fields of the Smarts notification? When I have trouble transforming traps into Smarts notifications, I start adding entries to the trap_mgr.conf file, like this:
BEGIN_TRAP <your OID>
EventName: TestEvent_<your OID>
I then know what information is available in the trap so that I can start mapping fields accordingly.
I hope this helps.
Thanks for your advice, (I'm kindof a newbie in the smarts field, which prob doesn't help matters).
I think thats part of the problem - the trap varbinds coming from vCOps is simply referred to as 'Resource' ??
Timestamp: 'June 20, 2012 9:30:31 AM EDT'
Enterprise OID: '.126.96.36.199.4.1.19004'
Generic Type: '6'
Specific Type: '101'
'.188.8.131.52.4.1.19004.2.1' --> 'localhost'
'.184.108.40.206.4.1.19004.2.2' --> 'GIS-Lab-Portal'
'.220.127.116.11.4.1.19004.2.3' --> 'Resource'
'.18.104.22.168.4.1.19004.2.4' --> '1340199198881'
'.22.214.171.124.4.1.19004.2.5' --> '4'
'.126.96.36.199.4.1.19004.2.6' --> 'New alert by id 6751 is generated at Wed Jun 20 09:33:18 EDT 2012; Root Cause : (71 OUT OF 160 SYMPTOMS)
60% - DT ABOVE - SUMMARY | NUMBER OF VMOTIONS
100% - DT ABOVE - DISK:NAA.6006016041102D007CCAF89DF030E111 | PHYSICAL DEVICE COMMAND LATENCY (MS)
20% - DT ABOVE - DISK | WORKLOAD (%)
20% - DT ABOVE - DISK:NAA.6006016041102D0043F43CFC772BE111 | READ RATE (KBPS)
20% - DT ABOVE - DISK:AGGREGATE OF ALL INSTANCES | KERNEL DISK COMMAND LATENCY (MS)
20% - DT ABOVE - DISK:NAA.6006016041102D0043F43CFC772BE111 | READS PER SECOND
Realizing that you've posted this question 2 months ago, are you still looking for some help? if so, please let me know how I can be of assistance.
I didn't proceed any further with testing via standard SNMP, instead I waited for the latest version of the smarts-vcops adapter (which supports Smarts 9.x and vCops 5.x) which is a far superior solution. However not so good at passing the Faults from vCOps to smarts however that is another matter entirely!