Is this a brand new installation? Then I would check your name
resolution, especially if your seed file has names in it. They must
resolve correctly, both forward (hostname to IP address) and back (IP
address to hostname). I would also check, using snmpconf (you can invoke
that from the command line), that either the SNMP community string that you
have for the global default is the same as the one as the NetView machine
itself, or that you have a separate entry for the NetView machine and for
127.0.0.1 which specify the correct community name to use. netmon gets
very confused when it cannot talk to SNMP on its own machine.
If that's no help, then you can try looking more closely at the netmon
trace. You did not indicate whether you just examined the file or set some
options to get more information. You can turn on the full netmon trace
from the command line with "netmon -M -1" and watch what happens as he
runs. You can turn it off again with "netmon -M 0". If you can't get any
clues from the netmon trace, then I would open a problem to IBM Support,
since the netmon trace is not really designed as a user-friendly interface.
It's most useful to a netmon specialist, particularly one who has access to
the code.
Hope this helps,
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
"Robson Souza"
<robsoneng@gmail.
com> To
Sent by: NV-L@lists.ca.ibm.com
nv-l-bounces@list cc
s.ca.ibm.com
Subject
[NV-L] Netview not discovering
08/24/2006 08:44
AM
Please respond to
Tivoli NetView
Discussions
<nv-l@lists.ca.ib
m.com>
Hi all,
We have got the following problem:
We have just installed Netview 7.1.4 with FP04 in a Windows 2000 Server.
After the instalation, we expected that the discovery process started to
find out our network but it does not occurs.
The seed file is OK and it has a lot of routers included in it.
I have enabled the netmon trace in order to see if the netmon is trying to
discover the network through the ping mechanism. The netmon.trace file
denounces that its trying to ping each of router IP.
To be certain about that, I enabled a sniffer to capture the ICMP packets
related above. For my surprise, there was not any ICMP packet trying to get
out through the network interface.
I have tested the Netview ping utility to ping the routers: it is working.
And I have tested the ping through Windows CLI, it is OK too.
Does anybody have an idea to solve this problem?
Robson
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to
internal IBM'ers only)
|