I see this a lot, mostly with the Cabletron hubs. While defining the
management
interface as an intentional duplicate (%) helps, you will still see it
moved from
device to device every time you start netmon. In addition, that second
interface
usually causes the device to be promoted from a hub to a router, which
clutters
up the IP Internet level of the map.
What I have taken to doing is defining them in oid_to_type with flag 'I',
for
ignore, which treats them as non-snmp. This means that they will not
be polled for addresses after the initial discovery. Then I put them in
oid_to_sym so they get the right picture (normally they would get the
default hub picture by virtue of the 'H' flag in oid_to_type). There are
some negative aspects to this use of the 'I' flag, but that's what it is
there for, I think.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Oliver
Bruchhaeuser/Germany/Contr To: IBM NetView
Discussion <nv-l@tkg.com>
/IBM@IBMDE cc:
Sent by: Subject: Re: [NV-L]
Netview 6 and duplicated
owner-nv-l@tkg.com addresses discovery
01/07/02 07:33 AM
Please respond to IBM
NetView Discussion
Luc,
try to put the following entry in your seedfile:
%10.0.0.1
and restart netmon.
Although %-entries are meant to identify HSRP interfaces
it should also work for your "duplicate" IP addresses.
Kind regards
Oliver Bruchhaeuser
Tivoli NetView EMEA L2 Support
IBM Deutschland GmbH - ITS Tivoli - Dept. 7977 - Hechtsheimer Str. 2 -
55131 Mainz - Germany
Phone: +49-6131-84-5108 - Fax: +49-6131-84-6585 - email:
bruchhae@de.ibm.com
Need help with Tivoli Software Products?
Ask Tivoli!
http://www.tivoli.com/asktivoli (login with your customer account)
Luc BARNOUIN
<luc.barnouin@thal To: IBM NetView Discussion
<nv-l@tkg.com>
esatm.com> cc:
Sent by: Subject: [NV-L] Netview 6
and duplicated addresses discovery
owner-nv-l@tkg.com
07.01.2002 12:38
Please respond to
IBM NetView
Discussion
Hi forumers,
Platform :
Netview 6.02
Tru64 UNIX 4.0F
Since we migrated to Netview 6 (we were formerly using 5.1.3), we are
having some problems for
discovering some of the network equipment's (Digital/Cabletron Hubs,
repeaters, concentrators and
VnSwitches).
Although declared in the seed.file, the hubs and some of the repeaters and
concentrators are not
discovered by netmon. When forcing discovery (loadhost command), they
temporarly appear in topology
database (ovtopodump) but are removed from it when ipmap tries to create
associated symbols. After
analysis, it seems to be linked with configuration of the OBM (Out Band
Management) port on those
equipment, which have all been declared with the same IP@ (10.0.0.1). This
port is used to connect a
laptop running the ClearVISN configuration tool, and it seems easier for
hardware installation
people to have a the same @ on this port for all the equipment they want to
connect to their laptop.
Those equipment are configured with other interfaces (on Ethernet and FDDI
networks) so as to
directly access them from the NNM. They are discovered through those
interfaces, but then the OBM
interface is also discovered (I have not seen any way to prevent it).
I have seen that discovery algorithm had changed between releases 5 and 6,
and that duplicated @ was
causing some problem for the discovery, but is there any configuration
mean, any netmon parameter
that would allow Netview 6 to cope with that?
Thanks for your help
Luc BARNOUIN
#### luc.barnouin.vcf has been removed from this note on January 07 2002 by
Oliver Bruchhaeuser
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|