Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*NetView\s+trapd\.log\s+and\s+events\s+display\s+report\s+wrong\s+source\s+IP\s+address\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*NetView\s+trapd\.log\s+and\s+events\s+display\s+report\s+wrong\s+source\s+IP\s+address\s*$/: 2 ]

Total 2 documents matching your query.

1. NetView trapd.log and events display report wrong source IP address (score: 1): Author: Goran Saradzic <gorans AT US.IBM DOT COM>; Date: Wed, 3 Nov 1999 09:03:42 -0700; Good day everyone, has anyone encountered this problem? The traps coming in from Xylan switches are reporting a non-existant source IP address which prevent us from identifying which switch has a pro; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-11/msg00032.html (10,846 bytes)
2. Re: NetView trapd.log and events display report wrong source IP address (score: 1): Author: James Shanks <James_Shanks AT TIVOLI DOT COM>; Date: Wed, 3 Nov 1999 12:17:46 -0500; I find it a bit difficult to understand exactly what you are saying. Do you mean that the sender of the trap ( $A ) is mis-identified? That is usually a DNS reverse-lookup problem. Trapd does a getho; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-11/msg00039.html (12,432 bytes)

Current List: 1 - 2
Page: [1]