RE: [nv-l] Cursed Cisco Trap Formats

2002-10-03 16:29:18
Subject: RE: [nv-l] Cursed Cisco Trap Formats
From: "Barr, Scott" <Scott_Barr AT csgsystems DOT com>
To: <nv-l AT lists.tivoli DOT com>
Date: Thu, 3 Oct 2002 15:29:18 -0500
One more thing James -

> Note that when you use this in an  action node, it will be three variables higher than what was  sent in the  original trap, because nvcorrd adds on three more elements from  trapd.conf, when the action node is called, so that you can reference them as environment variables.  In order they are (1) event category ( 0= "Threshold Events", 3= "Status events", etc. see the man page on trapd.conf) (2) event source-id  (A=agent, N=netmon, etc. see the man page on trapd.conf)(3) event severity  (0=cleared, 1=indeterminate, 2=warning, 3=minor, 4=critical, 5==major)

Just to make sure I understand this, in my last script example with the frame relay trap, there are at a minimum 8 environment variables ($NVA, $NVATTR_1, $NVATTR_2, $NVATTR_3 plus the 3 you mention). Is that correct?
To Stephen Hochstter - that is another valid approach and I will pursue it if this does not work out but I think James has the answer I need.