Joe,
In NetView 6.0,  new code to use the Cisco CDP information was implemented to
improve the discovery of unnumbered serial interfaces.
As a part of this, the netmon parameter to discover unnumbered interfaces was
made a default. I suspect, your discovery problem is
related to the discovery of nodes linked by these unnumbered serial interfaces.
I suggest turning off the discovery of nodes linked by
unnumbered interfaces to observe its effect on your problem.  Go to Serversetup
->Daemons ->Netmon ->Discovery and uncheck
"IP Nodes beyond Unnumbered Interfaces".

Regards,
Walt Ostack     Tivoli NetView Product Integrity


Pagliuca Joseph <Joseph.Pagliuca AT irs DOT gov> on 09/01/2000 12:44:58 PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

To:   "'nv-l AT tkg DOT com'" <nv-l AT tkg DOT com>
cc:    (bcc: Walt Ostack/Tivoli Systems)
Subject:  [NV-L] NetView Discovery Problem in 6.0.1




I recently upgraded my system to NV 6.0.1 for NT to solve the SNMP data
collection graphing problem (APAR# IY10046) which worked. However it has
created a new problem.  I have been using seed file discovery/seed nodes
only to control the scope of my network management areas. When I upgraded to
NV 6.0.1 my entire network now gets discovered. I cannot stop or control the
discovery process.  After close examination of the netmontrace log netmon is
using CDP (CISCO router environment) and discovering the next hop routers
then going out and discovering the next hop routers off the pervious
discovered set.  Within minutes I have a mess and routers added I do not
want.  I opened a PMR. This seems like a new bug. Comments/suggestions. I
cannot use the product in this state!
Joe

I recently upgraded my system to NV 6.0.1 for NT to solve the SNMP data collection graphing problem (APAR# IY10046) which worked. However it has created a new problem.  I have been using seed file discovery/seed nodes only to control the scope of my network management areas. When I upgraded to NV 6.0.1 my entire network now gets discovered. I cannot stop or control the discovery process.  After close examination of the netmontrace log netmon is using CDP (CISCO router environment) and discovering the next hop routers then going out and discovering the next hop routers off the pervious discovered set.  Within minutes I have a mess and routers added I do not want.  I opened a PMR. This seems like a new bug. Comments/suggestions. I cannot use the product in this state! 

Joe