The IP address of the failing interface in the Interface down trap, along
with the timestamp of the failure, the object id of the interface object
and the object id of the owning node are given in the 4th variable of the
Interface down trap. You can look in the NetView Administrator's guide and
see the contents of all NetView-generated traps.
You can control netmon discovery by using a seedfile, which can contain the
primary interface you want discovered. Once a node is discovered by that
address, that is exactly the primary interface used for DNS and SNMP.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Terje Lindholm <teli@eec.ericsson.se> on 12/08/98 07:12:14 AM
Please respond to "teli@eec.ericsson.se" <teli@eec.ericsson.se>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: netview trap variables
Hi
I miss some variables in for example IBM_NVIDWN_EV interface down trap.
This should ofcourse apply to up also.
NetView for example supply the object-id of the node, but not the actual
interface ????
Object-id is useless within netview rules except if you go externaly.
Why not supply object-name instead so that you can use it.
I would like to have interface instance, if-type and object-name. This
would make
rules processing much easier in T/EC and NetView.
I also would like to have the possibility to have netmon to use loopback
interfaces
as the primary source for SNMP and DNS resolving.
We use loopback interfaces in an address space we can control, a lot of the
ethernets/token addresses belong to others so we cant control their names.
/Terje
|