All NetView traps are documented in at least 2 places -- in trapd.conf, which
you can view by using xnmtrap from the command line or by pulling down the
Options menu and selecting Event Configuration, and in the Appendix to the
NetView Administrator's Guide, which you should have received in hard copy but
you can also consult on -line by typing in "dtext" from the command line or
using Help from the GUI.
This particular trap can have several causes, but basically it is issued because
of link-level address mismatches. This can happen if some nodes are on ethernet
and some on token ring, because these media report addresses differently, or it
could be a more serious routing problem. Basically, I would configure the
"ignore" option ring bit swapping errors for netmon as the documentation
suggests and see if the these traps disappear.
Tivoli (NetView for UNIX and NT) L3 Support
Marcelo Pastre <mpastre AT POWER.UFSCAR DOT BR> on 03/01/2000 07:03:41 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L AT UCSBVM.UCSB DOT EDU>
To: NV-L AT UCSBVM.UCSB DOT EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Understanding the History Event's messages!!!
I would like to find more informtaion about these History Event's
Something which show what mind these messages because i don't
for example, what mind "link address reported diferent by 220.127.116.11