Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RESOLVED\:\s+\[NV\-L\]\s+trapd\s+forwarding\s+to\s+tec\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*RESOLVED\:\s+\[NV\-L\]\s+trapd\s+forwarding\s+to\s+tec\s*$/: 2 ]

Total 2 documents matching your query.

1. RESOLVED: [NV-L] trapd forwarding to tec (score: 1): Author: "Senthil Kumar Mani" <Senthil.Mani AT ust-global DOT com>; Date: Wed, 25 Feb 2009 11:24:14 +0530; Leslie Great day for me to start! Yes it really resolved my issue by adding a 0 at the end of actual enterprise ID. Now I started seeing the event being flown towards TEC. Even I had a look into MIB; /usr/local/webapp/mharc-adsm.org/html/nv-l/2009-02/msg00052.html (25,822 bytes)
2. Re: RESOLVED: [NV-L] trapd forwarding to tec (score: 1): Author: James Shanks <jshanks AT us.ibm DOT com>; Date: Wed, 25 Feb 2009 09:17:33 -0500; Glad you resolved your problem. But if the trap that was sent did not match what mib2trap extracted that is an error on the vendor's part. The MIB does not match what his agent is sending. James Shan; /usr/local/webapp/mharc-adsm.org/html/nv-l/2009-02/msg00054.html (25,462 bytes)

Current List: 1 - 2
Page: [1]