nv-l
[Top] [All Lists]

Re: [nv-l] Interface down not receiving!

To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Interface down not receiving!
From: Larry Fagan <larrytechie@yahoo.com>
Date: Wed, 9 Mar 2005 06:37:35 -0800 (PST)
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
Delivery-date: Wed, 09 Mar 2005 14:38:23 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=i2qK4XbwI1N83I2oGaozhNkL2iCnR5fjuNOV1lVxDTyp3rQvdGVcdlrZmkjSQL0VNgdl1IJ+n5KcQawhfHr+j73rLnLT+K0kT3InKZdtToozPuxSH6pTig13lFEFVeUREeidWd4zSDJklDm6oWmjRUvptZCcyMY41ZS2KoekpA8= ;
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <422E208C.20704@skills-1st.co.uk>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Jane,
Global default says 5.0 in timeout, retry 3 and
pooling is 3m. Is this setting fair enough for any
environment?
Yes.. This has only single interface.. 
I knwo some time back had interface down traps from
this switch.. wonder what happened now... anyway
thanks.. i'll try and dig more into it..
Thanks all again..
Larry

--- Jane Curry <jane.curry@skills-1st.co.uk> wrote:

> Hi Larry,
> Just a little clarification on the netmon -a 12 data
> - your 88 seconds 
> says that the next ping poll will take place in 88
> seconds, not every 88 
> seconds.  If your global default is to poll every 5
> minutes, then you 
> shouldn't see any ping-polled machines in a netmon
> -a 12 output, with a 
> first field greater than 300 seconds.  You can watch
> it change with 
> subsequent netmon -a 12 commands.
> 
> Are you really saying that your retry time is in
> minutes rather than 
> seconds?????  Or is your poll time 3 minutes?  As
> Bill says, if your 
> timeout is in minutes then you have all sorts of
> problems.
> 
> As a test, I would do a netmon -a 12 and check when
> my switch was going 
> to be polled.  Then I'd disconnect the switch and do
> another netmon -a 
> 12 to make sure that that first field rolls past 0
> and goes back on the 
> ping list again.  With the switch still down, also
> do a Test -> Ping of 
> the box from the NetView GUI.
> 
> If you do an ovtopodump -lr <your switch name> this
> should show the 
> topology info on the box and it's interface(s) - are
> you sure it only 
> has 1 interface?
> 
> Cheers,
> Jane
> (Signing off for the night - supper done, wine
> drunk!)
> 
> Larry Fagan wrote:
> 
> >Jane,
> >Many thanks here..
> >When i looked into the netmon -12 in netmon.trcae,
> it
> >said that the switch i was looking for , does exist
> >and the poll interval says 88. This means it polls
> >every 88 seconds.
> >Also in global default in SNMP, the setting is set
> to
> >5 timeout in 3 retires with 3m. and there is
> nothing
> >else configured for sure.
> >But even by this i'm not getting any interface down
> >event from this device in trapd.log. Any ideas?
> >Thanks,
> >Larry
> >
> >
> >--- Jane Curry <jane.curry@skills-1st.co.uk> wrote:
> >
> >  
> >
> >>By default, NetView polls everything in his
> database
> >>every 5 minutes. 
> >>The default is to use ping for this polling.  The
> >>type of polling is 
> >>sometime changed to use SNMP - this may happen
> >>automatically (for 
> >>example if a box has unnumbered interfaces) or it
> >>can be configured via 
> >>the netmon seedfile or in
> /usr/OV/conf/oid_to_type. 
> >>
> >>The frequency of the polling is configured using
> the
> >>Options -> SNMP 
> >>Configuration menu.  By default, this has a single
> >>global default that 
> >>polls everything every 5 minutes (the frequency of
> >>the status poll is 
> >>unaffected by the ping/SNMP type).  Check this
> panel
> >>and see if there 
> >>are other entries - you can specify different
> >>polling characteristics 
> >>for individual nodes, networks of nodes or by 
> >>SmartSets. 
> >>
> >>The netmon -a 12 command I suggested earlier dumps
> >>netmon's ping list to 
> >>/usr/OV/log/netmon.trace.  The first field in this
> >>output specifies how 
> >>many seconds before the device is next to be
> pinged
> >>- it's a good 
> >>debugging sanity check.
> >>
> >>Cheers,
> >>Jane
> >>Larry Fagan wrote:
> >>
> >>    
> >>
> >>>Jason, 
> >>>I guess the problem is both.
> >>>First is that, i have SNMP traps(link up/downs)
> to
> >>>      
> >>>
> >>be
> >>    
> >>
> >>>sent to Netview is enabled on the device. But i'm
> >>>      
> >>>
> >>not
> >>    
> >>
> >>>getting any traps.
> >>>Second, 
> >>>As i guess, we have this device in netview and we
> >>>      
> >>>
> >>are
> >>    
> >>
> >>>using ping to check the interface up/down i
> >>>      
> >>>
> >>believe.
> >>    
> >>
> >>>But we are getting any interface down when this
> >>>      
> >>>
> >>device
> >>    
> >>
> >>>is switched off. This is not defined in SNMP
> config
> >>>      
> >>>
> >>or
> >>    
> >>
> >>>in seed file. Does this means netview uses ping
> to
> >>>check up/down's? Pardon my little knowledge in
> >>>      
> >>>
> >>here.
> >>    
> >>
> >>>Many thanks,
> >>>Larry
> >>>
> >>>--- "Allison, Jason (JALLISON)"
> >>>      
> >>>
> >><JALLISON@arinc.com>
> >>    
> >>
> >>>wrote:
> >>> 
> >>>
> >>>      
> >>>
> >>>>I guess there is two parts, and I am not fully
> >>>>        
> >>>>
> >>aware
> >>    
> >>
> >>>>of which one you
> >>>>are having problems with.
> >>>>
> >>>>1.  Cisco devices can be configured to send
> alarms
> >>>>to a management
> >>>>station when certain events occur.
> >>>>
> >>>>2.  NetView can be configuerd so that a device
> is
> >>>>managed and polled
> >>>>using some specific interval.  When NetView
> >>>>determines a device is not
> >>>>responding, it will send a trap to itself of a
> >>>>device being down.
> >>>>
> >>>>Which one are you having problems with?
> >>>>
> >>>>Thanks,
> >>>>
> >>>>Jason Allison
> >>>>Principal Engineer
> >>>>ARINC Incorporated
> >>>>
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web