I've been trying to make some sense of this thread and have failed. I
do want to clarify a couple of things, however.
1) The message in netmon.trace:
/usr/OV/bin/nmcheckconf: ERROR: LAN interface "Name" not UP and RUNNING.
**** Warnings from /usr/OV/bin/nmcheckconf configuration check script
is the result of an AIX problem and can generally be ignored. It happens
in AIX 4.3. There is a report that at bos.net.tcp.client 4.3.3.20 this
can cause netmon to fail to start, but I have not seen that to be the
case, and neither have you, apparently, if it goes on to load the
seedfile.
2) Adding nodes to the seedfile and issuing 'netmon -y' not causing
immediate discovery:
Well sometimes it does, and sometimes it doesn't get around to it for
a few minutes. And sometimes it discovers them, but not completely
enough to promote a router to the top map, because snmp queries fail.
So watch the events display to see the Node added event, or use locate
to search for it at a lower level. I usually stop/start netmon if
I am in a hurry.
3) If the node is discovered but is only a generic node at the segment
level, and you have configured the correct community string in the
alternates file, then you may have this libary problem that Les Dickert
refers to. You could tell for sure if you try a demandpoll on the
node but the snmp section of the poll fails. HOWEVER, my 6.01 system
(at AIX 4.3.3 ML 4) has no such library on it, so I'm not sure what
the efix actually is, and I see no open APARs referring to such a
problem.
I hope this helps.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
alexis.henry@bnpparibas.com@tkg.com on 10/18/2000 03:27:25 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: Réf. : Re: [NV-L] Netmon.trace errors
I have exactly the same problem. I'm running netview 5.1.2 on an AIX 4.3.3
box.
My ovsnmp.conf file has numerical IP addresses in it.
Is there a fix for Netview 5.1.2 ?
Thanks
Aleixs Henry
Groupe BNP-Paribas
Internet
lesdickert@hotmail.com on 17/10/2000 16:15
Veuillez répondre à nv-l@tkg.com
Pour : nv-l
cc :
ccc : Alexis Henry
Objet : Re: [NV-L] Netmon.trace errors
_____________________________________________________________________________________________________________________________________
Ce message et toutes les pièces jointes (ci-après le "message") sont
établis à l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur.
Toute utilisation de ce message non conforme à sa destination, toute
diffusion ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse.
L'internet ne permettant pas d'assurer l'intégrité de ce message, BNP
PARIBAS (et ses filiales) décline(nt) toute responsabilité au titre de ce
message, dans l'hypothèse où il aurait été modifié.
----------------------------------------------------------------------------------
This message and any attachments (the "message") are intended solely for
the addressees and are confidential. If you receive this message in error,
please delete it and immediately notify the sender.
Any use not in accord with its purpose, any dissemination or disclosure,
either whole or partial, is prohibited except formal approval.
The internet can not guarantee the integrity of this message. BNP PARIBAS
(and its subsidiaries) shall (will) not therefore be liable for the message
if modified.
_____________________________________________________________________________________________________________________________________
You may be having the same problem I had. If
your ovsnmp.conf file has numerical IP addresses
in it, there is a bug in 6.0 (and 6.0.1) that
prevents netmon from doing a successful SNMP
query of SNMP accessible nodes, which fouls up
discovery big time since netmon can't get it's
hands on ARP tables and routing tables. Check your
/usr/OV/lib/nvsnmplib.a file, if it has a size of
329771, then you have a bad file. The good one should
have a size of 1248131. Contact Tivoli support to
get the new file and install it. It corrected a world
of discovery problems for me.
BTW, apparently the problem was that netmon wouldn't
pick up the communitiy string from the ovsnmp database
if the IP addresses were entered as numbers.
Good luck!
Les
>From: Scott.Bursik@fritolay.com
>Reply-To: IBM NetView Discussion <nv-l@tkg.com>
>To: nv-l@tkg.com
>Subject: [NV-L] Netmon.trace errors
>Date: Tue, 17 Oct 2000 08:42:34 -0500
>
>
>I am running NetView 6.0 for Unix on a AIX 4.3.2 box and I am having
issues
>with
>discovery of new nodes added to the seed file. I view the netmon.trace
file
>and
>I find the error listed below. When I add files to the seed file, I go to
>the
>command line and enter the netmon -y command and NetView still does not
>discover
>the new nodes.
>
>/usr/OV/bin/nmcheckconf: ERROR: LAN interface "Name" not UP and RUNNING.
>**** Warnings from /usr/OV/bin/nmcheckconf configuration check script
>netmon: Reloading seed file '/usr/OV/conf/netmon.seed'
>netmon: Reloaded seed file '/usr/OV/conf/netmon.seed' successfully
>
>
>_________________________________________________________________________
>NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|