[Top] [All Lists]

RE: PING only to monitor

To: nv-l@lists.tivoli.com
Subject: RE: PING only to monitor
From: "Davis, Donald" <donald.davis@firstcitizens.com>
Date: Tue, 11 Dec 2001 16:06:35 -0500
The simple answer is that you cannot prevent SNMP polling of "their" routers
if they have been discovered by NetView.
You can set the Configuration Polling Interval to 5 years. You can set
Discovery Polling to Off.
However, You cannot prevent netmon from config polling them any time that
netmon is cold started.

Like I said in my previous post, your only solution is not to monitor them
at all if "they" are complaining about SNMP authentication failures in
"their" router logs and refuse to give you read-only access to "their"

Good luck,

Don Davis

-----Original Message-----
From: Davis, Donald [mailto:donald.davis@firstcitizens.com]
Sent: Tuesday, December 11, 2001 3:48 PM
To: 'IBM NetView Discussion'
Subject: RE: [NV-L] PING only to monitor

NetView is an SNMP manager. It uses ping to discover and check status.
It uses SNMP to find out lots of other important information about devices.
It sounds like your problems are POLITICAL, rather than application.
If the university coughed up the big bucks to purchase NetView, they ought
to let it do what they paid for.
If your router folks do not want "your" NetView SNMP polling "their"
routers, you might as well not monitor them at all.
You can't tell much about a router by pinging one interface.
I would put negative entries in the seedfile and not monitor them at all!
You can still use NetView to manage your servers and other resources without
monitoring "their" routers!

Don Davis

-----Original Message-----
From: Thomas Kunz [mailto:t-kunz@admin.ndis.umn.edu]
Sent: Tuesday, December 11, 2001 3:06 PM
To: nv-l@tkg.com; shochste@us.ibm.com
Subject: Re: [NV-L] PING only to monitor

These devices that I am referring to are all cisco routers that have already
been discovered and are in my seedfile and the owners say that every time
netview polls the device and the snmp get fails they get an error message on
their log about wrong community name. 

>>> shochste@us.ibm.com 12/11/01 01:49PM >>>

By default, NetView will do just that.    Of course, NetView will only ping
the 1 interface.   It cannot find out about the other interfaces if they
exist since it cannot read the MIB.    So hopefully this is a server, not a
router.    If that subnet is not discovered yet, use the command loadhost
to add it to NetView.    You will see it get loaded into NetView and remain
a non-SNMP box with a single interface.

Kind regards,
Stephen Hochstetler              shochste@us.ibm.com 
International Technical Support Organization  - Austin
Office - 512-436-8564                      FAX - 512-436-8701

ITSO redbooks at  http://www.redbooks.ibm.com 

NV-L List information and Archives: http://www.tkg.com/nv-l

This e-mail and its attachments have been scanned for viruses.
NDIS/ADCS University of Minnesota 
NV-L List information and Archives: http://www.tkg.com/nv-l

This electronic mail and any files transmitted with it are confidential and
are intended solely for the use of individual or entity to whom they are
addressed. If you are not the intended recipient or the person responsible
for delivering the electronic mail to the intended recipient, be advised
that you have received this electronic mail in error and that any use,
dissemination, forwarding, printing, or copying of this electronic mail is
strictly prohibited. If you have received this electronic mail in error,
please immediately notify the sender by return mail.



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

Archive operated by Skills 1st Ltd

See also: The NetView Web