NetView doesn't care about interface type. It reports down as down. If
you care, then you have to build what you can. There is a MIB query
instance in the ruleset options you can select. If you don't see what
you want, then you will have to use an Action node to issue a command you
write yourself. If you think more function should be added to NetView,
then send a note detailing your requirements to netview@tivoli.com for
consideration in a future release.
By the way, I think you have a bit of a misconception here. The object id
in NetView is the number assigned to an object in his database. It is not
the same as an SNMP object id. Many different network devices can have the
same SNMP object id, but there will be just one NetView object id for each
node.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Terje Lindholm <teli@EEC.ERICSSON.SE> on 12/08/98 09:37:08 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: Re: netview trap variables
Yes but how do you create a ruleset within NetView that can distinguish
between
serial, ethernet, ATM, loopback, ISDN .............(without stringmatch or
going external)
You can do an query on the node, I would like to be able to get either
interface MIB-instance
so that I can query the router when an interface goes down or If I get
object-name for the
down interface i can do an DB query to see what type of interface it is.
Many of the functions provided within NetViews rulsets use object-name not
object-id.
Why not supply that ??????
The "Query SNMP.." for example should be rebuilt so that you can supply an
instance, which
should be supplied with the trap. If you then use the loopback interface as
one and only
address for queries it would be great.
Today you get an ip-address that is down/inaccessible with the trap, great
!
I still want the actual ip-addres but its not useful within a rule.
/Terje
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.
|