Hi,
Please could I be take me off this list as we no longer have use of Tivoli
products. Many thanks.
Kind Regards,
Mohammed Amir
Senior Systems Engineer
Oxfordshire County Council
ICT Corporate Core
3rd Floor, Clarendon House
52 Cornmarket Street
Oxford OX1 3EJ
DDI : 01865 328874
Mobile : 07810 656 424
mohammed.amir AT oxfordshire.gov DOT uk
-----Original Message-----
From: nv-l-bounces AT lists.ca.ibm DOT com [mailto:nv-l-bounces AT lists.ca.ibm
DOT com] On Behalf Of Francois Le Hir
Sent: 08 July 2010 12:52
To: Tivoli NetView Discussions
Cc: Tivoli NetView Discussions; nv-l-bounces AT lists.ca.ibm DOT com
Subject: Re: [NV-L] Discovery X subnet
If a good subnet already exists, the new nodes that get discovered will
automatically be connected to it.
If you can not solve the snmp access, and you have at least one device with
snmp access for each subnet, a solution is to get all these devices with
snmp access discovered first so that the subnets will be created with the
correct mask. And then the nodes without snmp access will connect to the
existing subnets. You can also use loadhost to create the first interface
of a subnet with the right mask.
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Technology Services
"Do not go where the path may lead; go instead where there is no path and
leave a trail." - Ralph Waldo Emerson.
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Marcelo Zacchi <mzacchi AT gmail DOT com>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|nv-l-bounces AT lists.ca.ibm DOT com
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|07/08/2010 06:44 AM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [NV-L] Discovery X subnet
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|nv-l-bounces AT lists.ca.ibm DOT com
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Hello Francois,
Thanks for your reply!
You're right! All of these equipments are nor responding to SNMP polls. But
why does it happen only to some SNMP-unresponsive devices? There are quite
a few devices that are monitored using ICMP and are placed automatically on
the correct subnet.
Best regards,
Marcelo
On Wed, Jul 7, 2010 at 2:48 PM, Francois Le Hir <flehir AT ca.ibm DOT com>
wrote:
It all depend of the snmp access to the device that has an ip in the
subnet. If there is no snmp access, then netview will assume the mask of
the subnet based on the class of the subnet. 10.x is a class A so the
mask
will be 255.0.0.0.
If you want to correct that after the fact, the only way it to delete the
subnet and the device and start over.
It's always better to configure the community string in netview before
you
get a device discovered.
Salutations, / Regards,
Francois Le Hir
Network Projects & Consulting Services
IBM Global Technology Services
"Do not go where the path may lead; go instead where there is no path and
leave a trail." - Ralph Waldo Emerson.
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Marcelo Zacchi <mzacchi AT gmail DOT com>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|nv-l AT lists.ca.ibm DOT com
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|07/07/2010 12:10 PM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[NV-L] Discovery X subnet
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|nv-l-bounces AT lists.ca.ibm DOT com
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Hello list!
I have a Netview 7.1.5 fp0004 installed on a Linux box and something's
been
bothering me for quite a while:
Most of the device's IPs are in a 10.0.0.0 network, and sometimes when a
new device is discovered (by means of adding it to the netmon.seed file)
it
is added to a IP network symbol named 10. Is there any way to control
this?
I mean when the IP is 10.2.3.3 shouldn't Netview add it to the 10.2.3
network?
Best regards to all!
Marcelo Zacchi
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
This email, including attachments, may contain confidential information. If you
have received it in error, please notify the sender by reply and delete it
immediately. Views expressed by the sender may not be those of Oxfordshire
County Council. Council emails are subject to the Freedom of Information Act
2000. http://www.oxfordshire.gov.uk/emaildisclaimer
_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|
