I have it working fine for three different customers. I cannot vouch for
the 1600, though.
You might check the interface table for the device and see if it shows up
there. You
should be getting an interface card as well as a network for it, if the mib
lists it.
Another possibility: There are certain things you can mess up using the
location.conf file,
where the interfaces don't get drawn but still contribute to status. It is
not yet clear whether
this is a bug or a user problem, but I have done it. Symptoms: an interface
is listed in
Tools...Display Object Info but does not appear under the router. If it
goes down (eg not
a loopback), the router turns yellow but when you look under it, there are
no red cards.
There are also messages in the nettl.LOGxx from ipmap complaining about
OVwError=181: Connection symbol endpoint not found
and OVwError=184: Connection symbol endoints in different Submaps
If you do a Locate by IP Address on the interface, it will show up in the
list as being in a
Location Submap which failed to get drawn. If you manually add that
Location icon to
the correct level of the map (says object with that name already exists, do
you want to
create another symbol - say yes), then the missing networks and interfaces
appear.
I lost a lot of loopbacks that way when I figured out that loopback
addresses are the
same as their networks, and so make a handy way to associate a router with
a
location and put them in the location.conf file - along with a lot of other
stuff. I lost a lot
of non-loopback interfaces, too, and only really noticed it when I checked
my
ProblemNodes collection and found a bunch of routers with status of
Marginal, but
which were all green, no red or ack'd cards under them. The cards were out
there, but
not in any submap which was being expressed in the map.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
Kuffer Andreas <Andreas.Kuffer@kuoni.ch>@tkg.com on 07/07/2000 03:48:14 AM
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>
cc:
Subject: RE: [NV-L] What happened to netmon Flag?
I checked the netmask of the loopback interface, it was indeed set to
255.255.255.252. I asked the network guys why and the answer was that in
earlier times you were not allowed (unable) to set a mask of
255.255.255.255. So the "loopback-netmask"-design of our network is
255.255.255.252 due to historical reasons.
Anyway we reconfigured the Cisco 1600 to 255.255.255.255, did a demand poll
and also a new discovery but received the same results as I posted before.
I will call support today but I'm still interested if there is anybody out
there with NetView 6.0 discovering loopback interfaces.
With kind regards / mit freundlichen Gruessen
Andreas Kuffer (System Manager UNIX and Enterprise Management)
-----Original Message-----
From: lclark@us.ibm.com [mailto:lclark@us.ibm.com]
Sent: Donnerstag, Juli 06, 2000 16:30
To: IBM NetView Discussion
Subject: Re: [NV-L] What happened to netmon Flag?
The -L flag was dropped in V6 (made a no-op) because it was no longer
needed. This is because, according to the internal update I attended,
32-bit masks are now fully supported; 32-bit masks are generally used for
software loopback interfaces. The connection is not exactly clear to me,
but I have seen loopbacks discovered successfully in V6, whether the
loopback was the address specified in the seedfile or not. So by my
voodoo-problem-determination methodology, I would suggest checking
the mask on the loopback that is missing. If it is not 255.255.255.255,
make
it so. If it is already so, look for some other, more mundane discovery
problem, or call Support with a trace of the discovery handy.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Kuffer Andreas <Andreas.Kuffer@kuoni.ch>@tkg.com on 07/06/2000 04:59:40 AM
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>
cc:
Subject: [NV-L] What happened to netmon Flag?
AIX 4.3.2, NV 5.1.2 and NV 6.0
in version 6.0 of netview it seems that one flag of netmon (-L, discover
loopback interfaces with other address than 127.0.0.0) was withdrawn.
I have a Cisco 1600 with loopback interface 10.10.224.85 and three other
interfaces
Demand poll with NV 5.1.2 (netmon runs with -L):
Interface 10.10.232.86 (currently up) responded to ping
Interface 10.10.21.1 (currently up) responded to ping
Interface 10.10.224.85 (currently up) responded to ping
Interface 10.10.240.86 (down since 07/03/00) ping timed out
Demand poll with NV 6.0 shows:
Interface 10.10.232.86 (currently up) responded to ping
Interface 10.10.21.1 (currently up) responded to ping
Interface 10.10.240.86 (down since 07/03/00) ping timed out
So it looks like netmon V6.0 doesn't discover the loopback interface I'd
like to see. Does that work as designed? Did I miss anything? Can I use an
undocumented "-L feature"?
Any help is very welcome...Andreas
With kind regards / mit freundlichen Gruessen
Andreas Kuffer (System Manager UNIX and Enterprise Management)
Kuoni Travel Ltd.
Dep. TOU
Neue Hard 7
CH-8010 Zuerich
Switzerland
Telefon : + 41 1 277 52 41
Fax : + 41 1 272 52 55
<<< the smile that you send out returns to you >>>
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|