Hi Jane,
We don't have firewall inasmuch as I can ping the gateways included in the
seed file manually, both through netview utility and CLI.
The tracert works fine and we don't have routing problems.
We are almost formatting the HD and reinstalling everything in order to
solve this problem...
Robson
-----Mensagem original-----
De: nv-l-bounces AT lists.ca.ibm DOT com [mailto:nv-l-bounces AT lists.ca.ibm
DOT com] Em
nome de Jane Curry
Enviada em: quinta-feira, 31 de agosto de 2006 20:01
Para: Tivoli NetView Discussions
Assunto: Re: [NV-L] Netview not discovering
Do you have firewalls in the way?? Have you tried using tracert to see
what happens to packets? Do you have routing problems?
Cheers,
Jane
Robson Souza wrote:
> Hi James,
>
> Thx for your fast replying.
>
> Yes, that's a new instalation, but we don't use names for the routers
> in our network. There are only routers ip addresses in the seed file.
> In any way, we just use name resolution for our servers and it's OK.
>
> As you advised, we checked the machine and the Netview SNMP
> communities. There was really a difference between one and another
> one. After that, we have configured the both with the same community.
> But there have not been some effects.
>
> The netmon trace was enabled with -1 option already. As I said, I can
> see in that file a lot of ping attempts to all of routers I have put
> in the seed file. But those pings does not happen effectively through
> a sniffer installed in the same machine.
>
> Robson
>
> On 8/24/06, *James Shanks* <jshanks AT us.ibm DOT com
> <mailto:jshanks AT us.ibm DOT com>> wrote:
>
> 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 <http://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 AT lists.ca.ibm DOT com
> <mailto:NV-L AT lists.ca.ibm DOT com>
> nv-l-bounces@list
cc
> s.ca.ibm.com <http://s.ca.ibm.com>
>
Subject
>
> [NV-L] Netview not discovering
> 08/24/2006 08:44
> AM
>
>
> Please respond to
> Tivoli NetView
> Discussions
> <nv-l AT lists.ca DOT ib <mailto:nv-l AT lists.ca DOT ib>
> m.com <http://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 AT lists.ca.ibm DOT com <mailto:NV-L AT lists.ca.ibm DOT com>
> Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
> <mailto: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 <mailto:NV-L AT lists.ca.ibm DOT com>
> Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
> <mailto: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)
>
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2006 Jane Curry <jane.curry AT skills-1st.co DOT uk>. All rights
reserved.
_______________________________________________
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)
|
