Two things I can think of that have killed netmon recently on my system:
1. Demand poll a Microsoft NT server. This kills netmon on both my
production and backup systems. Does not seem to be happening with config or
status polls etc. I haven't ever gotten around this but have been beating on
the microsoft agent to find the problem. (PMR64800 - problem still appears
to be Microsoft SNMP agent)
2. Discovery of a device with an inappropriate address. We have a "sentinel"
device that serves as a dial in access point for our telephone switches.
When NETMON would discover this device (which has an ethernet interface to
talk to the switch) we would discover and address of 0.0.0.1 with a
255.255.255.0 mask. NETMON would die every time he found one of these
devices. This is supposed to be corrected in next release (or maybe already
is, not sure of PMR number).
I guess what I am saying is that if netmon dies frequently, it may be
discovery killing it and not a seed file problem. You might try turning off
discovery
-----Original Message-----
From: owner-nv-l@tkg.com [mailto:owner-nv-l@tkg.com]On Behalf Of Kevin
Gow
Sent: Thursday, July 12, 2001 11:24 AM
To: nv-l
Subject: RE: [NV-L] Netmon died
Leslie,
Thanks for saying what I MEANT to say...
I missed the part of the unresolvable names which will print to the screen.
Those are the ones which need to be removed / commented out in the seedfile,
and obviously the unreachable names will need to be investigated.
While we are on this subject, how can I redirect those unresolvable names
to a file as well? If the list is long, a "cut & paste" approach will be a
bit tedious.
Regards,
Kevin.
-----Original Message-----
From: lclark@us.ibm.com [mailto:lclark@us.ibm.com]
Sent: Thursday, July 12, 2001 3:51 PM
To: nv-l@tkg.com
Subject: RE: [NV-L] Netmon died
A clarification on Kevin's observation:
Unreachable things in the seedfile are not a problem. But
unresolvable names in the seedfile ARE. If you do
ovstatus netmon
it will tell you if that is the problem and direct you to
/usr/OV/log/netmon.trace. That file will list all of the unresolvable
names so you can fix them. If netmon was down, it will fail to start.
If it was up and you did a 'netmon -y', it will refuse to reload the
seedfile.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Kevin Gow <kevin.gow@csfs.com>@tkg.com on 07/12/2001 07:08:42 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l <nv-l@tkg.com>
cc: parduengo <parduengo@telecable.es>
Subject: RE: [NV-L] Netmon died
Something similar was happening to me. This is what I did...
Check your seedfile. Use the fping command and route the output to a file,
e.g.: fping -f objects.seed > objects.seed.output
You will get a list of objects wich are reachable and wich are not.
Comment out the unreachable objects in your seedfile.
I don't know if this will help in your case... perhaps it is worth a try.
Regards,
Kevin Gow.
-----Original Message-----
From: parduengo@telecable.es [mailto:parduengo@telecable.es]
Sent: Thursday, July 12, 2001 11:44 AM
To: nv-l@tkg.com
Subject: [NV-L] Netmon died
I have netview 6.0.1 on Solaris. If I start netmon about 2 minutes it is
died.
I active de netmon trace and once of trace show netmon died by PMD, but in
my
Control desk in events show "netmon probably died: ungracefully
disconnected
from trapd".
I running ovmapcount, ovtopofix, ... ovstop, ovstart, reset_ci, all
commands I
know for repair one problem, I view the file system, memory, and processor
and
it is good state.
What can i do?
Thanks to all.
---------------------------------------------
Este mensaje fue enviado
utilizando el servicio de correo-web de:
http://www.telecable.es
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
|