If the origin of your trap is not being shown as a hostname, then that is
because gethostbyaddress did not return a name for the address. You can fix this
by adding this node to DNS or to /etc/hosts, whichever is appropriate.  If you
cannot modify DNS, because you do not own it, then you can create your own
/etc/hosts file for just these problem addresses and also provide an
/etc/netsvc.conf which says "hosts=local,bind" so that it will look at your
/etc/hosts first.


James Shanks
Tivoli (NetView for UNIX) L3 Support



"Sin Wai Yee, Maggie" <mwysin AT KCRC DOT COM> on 09/16/99 11:01:47 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:  Trap interpretation




Sometime Netview can interpret the host from the ip address of the trap, but
sometimes does not. It make me difficult to filter the similar in the
certain time through ruleset.

For example, when one of the interface down ( Serial 0 in this case ).
Sometime, it interpret the trap is come from HOST1.
Sometime, it can't interpret the trap, only quote the interface's address
only.

In my ruleset setting, one of the field that will be checked is the origin.
In this case, the origin is different - that can not be interpret as the
same.

10:18:47 AM 17 Sep HOST1 Serial0 22 EIA signal lost 3

10:19:02 AM 17 Sep 10.10.0.2 Serial0 22 EIA signal lost 3

If there anyone has any idea for that ?

Thanks