Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Unique error codes in VOM SNMP traps

Created: 31 Mar 2011 • Updated: 20 Jun 2011 | 2 comments
bsobek's picture
4 Agree
0 Disagree
+4 4 Votes
Login to vote
Status: In Review

Hi,

we send snmp traps from VOM to nagios. The nagios system receives the following trap:

\'Unknown Trap: enterprises.1302.3.14.10.1.1 ():150:15:19:21.44 enterprises.1302.3.14.10.1.2 ():all_vxvm+vxfs enterprises.1302.3.14.10.1.3 ():event.alert.vom.vm.volume.stopped enterprises.1302.3.14.10.1.4 ():1 enterprises.1302.3.14.10.1.5 ():<hostname>.corp.int enterprises.1302.3.14.10.1.6 ():Volume <volumename> is in stopped state enterprises.1302.3.14.10.1.7 ():Volume <volumename> is in stopped state enterprises.1302.3.14.10.1.8 ():none enterprises.1302.3.14.10.1.9 ():vm\'

I miss a unique errorcode in all traps which I know from the system/cluster logs (e.g.  ERROR V-123-4-5 <message>). With a unique error/warning/... code we can search in your and our own knowledge base to a solution to our problem.

Comments 2 CommentsJump to latest comment

Michael Auria's picture

What OS is the VOM Central Server running ?  What version is installed ?  What patch level has been applied ?  If this is a Unix server, what are the versions of the packgages or rpm's (VRTSsfmcs and VRTSsfmh) ?

 

Have you copied the MIB trap definition file frm the VOM Central Server to the SNMP server configuration ?  In Unix, that file is located at:

 

/opt/VRTSsfmcs/config/snmp/VRTSsfm.mib
 

0
Login to vote
Kimberley's picture
 
I just wanted to see if you've had a chance to provide the details that the product team was looking for on this? Thanks for any additional materials.
Best,
Kimberley

Thanks for participating in the community!

0
Login to vote