nv-l
[Top] [All Lists]

Re: [nv-l] More on netmon.seed ranges

To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] More on netmon.seed ranges
From: john.j.mackney@accenture.com
Date: Wed, 25 Sep 2002 09:45:14 +0100
Forgot to copy to the list

----- Forwarded by John J. Mackney/External/Accenture on 25/09/2002 09:45
-----
                                                                                
                                                 
              John J. Mackney                                                   
                                                 
                                               To:      James Shanks 
<jshanks@us.ibm.com>                                        
              24/09/2002 18:54                 cc:                              
                                                 
                                               Subject: Re: [nv-l] More on 
netmon.seed ranges                                    
                                                                                
                                                 



Thanks James (and all),

Actually  after reviewing the replies here, and studying the UNIX
configuration guide I think what I have in my seed file is actually what I
want.
i.e. I have specified all the routers and excluded all the DHCP ranges. I
didn't quite appreciate how ranges limited discovery, but as I do not want
to discover any nodes outside the ranges I have specified, what I have is
in fact what I need.

What is confusing me though is why netmon doesn't discover some (what I
would consider as ) perfectly discoverable nodes i.e they can be pinged,
they have DNS entries and I can snmpget information using the correct
community name strings. I suppose they are only not discovered because
there is no ARP entry or routing table entry somewhere (though I find this
hard to accept).

I intend to add these missing nodes by tacking them onto the end of the
netmon.seed file - then when everything has been discovered, clearing them
out and just leaving the routers and HSRP addresses.

Thanks again all
John


                                                                                
                                                 
              James Shanks                                                      
                                                 
              <jshanks@us.ibm.com>             To:      nv-l@lists.tivoli.com   
                                                 
                                               cc:                              
                                                 
              24/09/2002 17:16                 Subject: Re: [nv-l] More on 
netmon.seed ranges                                    
                                                                                
                                                 
                                                                                
                                                 



You might want to review the functions of the seed file in the
Installation Manual or the help.

Ranges do not force discovery, they only permit discovery.
Only individual entries will force discovery, as you found out
netmon explicitly seeks those interfaces/nodes at start up.
For the others he reads the arp cache of what he has already discovered.
That's why routers are good candidates for the seed file.

By adding a range you have limited discovery to just what is in that
range.
If netmon finds anything else, it will throw it away.
So you can prevent discovery of anything outside the individual entries in
the seed file by adding an invalid range such as 3.3.3.* at the end of
your file.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group




john.j.mackney@accenture.com
09/24/2002 11:38 AM


        To:     nv-l@lists.tivoli.com
        cc:
        Subject:        [nv-l] More on netmon.seed ranges



Is my logic correct?

a netmon.seed entry of:
10.250.0.1-254

Should discover all the nodes in range (if it works).

It doesn't work for me!!

However, If I enter nodes exactly it discovers them i.e.
10.250.0.25
10.250.0.37

This looks like a bug... Is anyone else using Solaris 8 and NetView 7.1.2?


This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete the
original.  Any other use of the email by you is prohibited.


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)





---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)







This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete the
original.  Any other use of the email by you is prohibited.


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web