I expect that you are right. Given a choice between all traps and no
traps, I take no traps every time. On current Cisco equipment you can
indicate exactly which interfaces you would like the up and down
events sent for. Only send them for the ones that are supposed to be
up all of the time. They have given us more rope. What we do with it
is up to us. We can, as you point out, easily hang ourselves. And
we can also make the system much more reflective of real status
without additional polling.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Kevin J Lee" <kevinl@iormyx.com>@tkg.com on 03/20/2001 04:32:17 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "IBM NetView Discussion" <nv-l@tkg.com>, "IBM NetView Discussion"
<nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Netview discovery status
Putting one plus one together... if NetView responds to every trap it
receives and has to re-eveluate the node(s), and since Netview (netmon)
is single threaded, wouldn't this at least double the processing efforts
required on the server during an event storm? Maybe even to a point
where netmon never completes a status polling cycle because it is
interrupted by the re-evaluate request?
Kevin Lee
kevinl@iormyx.com
(703)855-2408
-----Original Message-----
From: Leslie Clark
Sent: Tue 3/20/2001 3:39 PM
To: IBM NetView Discussion
Cc:
Subject: RE: [NV-L] Netview discovery status
Les, you are right for 6.01, but, as I said yesterday, Netview will now,
at 6.02, respond to that trap from the device and re-evaluate the node,
and update the status everywhere. So in Varadhu's scenario, when an
Up trap comes in from the device right after a netmon status poll that
fails,
the node will switch to Up right away instead of waiting for the next
polling
cycle. If you are at 6.01, you will see it down until the next polling
cycle.
This is an awesome new feature. Not only to see things come up more
immediately, but to also see small outages that you were missing
before.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Les Dickert" <lesdickert@HOTMAIL.COM>@tkg.com on 03/20/2001 08:23:28 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: RE: [NV-L] Netview discovery status
When netmon polls for status, it uses either
'ping' or 'SNMPGET' to determine if the
device or interface is up or down. The reply
it gets back from the device is not generally
referred to as a 'trap' or an 'event', but rather
merely a reply to the netmon poll. From this
reply, netmon determines if the device/interface
is up or down, and sets the database status and
GUI symbol color accordingly. It also sends an
internal trap to 'trapd' which displays an
event looking message on the various event
viewers.
In addition to this, various device agents can
send in traps of their own, not in response
to a netmon poll. These are displayed in the
event veiwers, but do not affect the status in
the database or the symbol color.
Unless I'm horribly wrong. If so, someone please
straighten me out.
Thanks,
Les
>From: "S. Varathu, IBM" <Varathu@bom4.siemens.co.in>
>Reply-To: IBM NetView Discussion <nv-l@tkg.com>
>To: "'IBM NetView Discussion'" <nv-l@tkg.com>
>Subject: RE: [NV-L] Netview discovery status
>Date: Sat, 17 Mar 2001 14:51:46 +0530
>
>Thanks Les, But still i have doubt. For an example, if i define netmon
>polling interval is 10mts. when it polls to device and one of the
interface
>is down for the device and display the same down inofrmation in
GUI.(object
>DB also). Immediately after the poll, the interface is UP, so the
device
>send the trap information to netview about the status. In that case
what
>would be the object database? will netview display "UP" information?
>
>Once again thanks for the info..
>
>varadhu
>
>
> > ----------
> > From: Les Dickert[SMTP:lesdickert@hotmail.com]
> > Sent: Friday, March 16, 2001 10:26 PM
> > To: nv-l@tkg.com
> > Subject: Re: [NV-L] Netview discovery status
> >
> > Yes, NetView updates the status of objects in
> > the database, and on the maps, based on polling
> > for status. Events received by NetView have no
> > affect on either, unless you write a special event
> > (trap) handler to do it. James Shanks has previously
> > (many times) posted a method of changing the status
> > of an object, which could be done upon receipt of
> > an event, but remember that NetView (netmon) is still
> > going to poll for status and might change the status
> > right back.
> >
> > Remember that if a device can send an event trap
> > to NetView that means there is IP connectivity to
> > the device and therefore netmon will think it is
> > up and operational.
> >
> > Les Dickert
> > Verisign Consulting
> >
> >
> > >From: "S. Varathu, IBM" <Varathu@bom4.siemens.co.in>
> > >Reply-To: IBM NetView Discussion <nv-l@tkg.com>
> > >To: "'nv-l@tkg.com'" <nv-l@tkg.com>
> > >Subject: [NV-L] Netview discovery status
> > >Date: Fri, 16 Mar 2001 15:41:41 +0530
> > >
> > >hi,
> > >
> > >Does netview update the status of objects in topology database
based
on
> > >polling on each device or can trap event generated by the device
(say
> > >router) which reflect to corresponding change in topology map?
> > >
> > >Regards,
> > >varadhu
> >
> >
________________________________________________________________________
_
> > >NV-L List information and Archives: http://www.tkg.com/nv-l
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
> >
>_______________________________________________________________________
__
> > NV-L List information and Archives: http://www.tkg.com/nv-l
> >
>_______________________________________________________________________
__
>NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
________________________________________________________________________
_
NV-L List information and Archives: http://www.tkg.com/nv-l
________________________________________________________________________
_
NV-L List information and Archives: http://www.tkg.com/nv-l
|