Ok, we have found out that we can upgrade
this vendors hardware so that we can specify a domain name and port.
My next question would be how many SNMP
senders have people come across that cannot be configured to send to another
port number?
I don’t want to build another
machine just to host the Universal agent but I don’t want to implement
the way I am if in short order I run into this port problem again.
Sean
Lawrence
Systems Automation Technical
Specialist
905-790-5728
From: nv-l-bounces@lists.ca.ibm.com [mailto:nv-l-bounces@lists.ca.ibm.com] On Behalf Of James Shanks
Sent: September 18, 2007 10:37 AM
To: Tivoli
NetView Discussions
Subject: Re: [NV-L] Forwarding
traps to ITM UA snmp adapter on the same machine
I'm not sure any configuration you come up with will
work with the Universal Agent on the same box. Generally speaking, NetView does
not support any other trap receivers on the same machine but himself.
As far as I know, traps are not automatically forwarded to 1661 by trapd.
That's the port he uses when a client trapd from the NetView client (remember
that?) connects to him. The client requests a session and they transfer data
across it. So I doubt that merely listening there will get you anything. But you
can try anything you like, of course.
I think in the end you will have to configure trapd to use the -M (all traps)
or -m (just those configured for forwarding in trapd.conf) options and specify
the hostname or IP address and the port you want. I haven't tried that to
another port on the same machine but it just might work. If not, you'll have to
move the Universal Agent.
James Shanks
Level 3 Support for Tivoli
NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp
"Sean Lawrence" <Sean.Lawrence@cantire.com>
I
am having an issue with a vendors product.
They are not
able to configure the snmp trap port of 162 on there side.
I need to send
their traps to the Tivoli Monitoring Universal agent.
My Netview and
Universal agent are on the same machine.
From reading
the trapd documentation it looks like traps are forwarded to the nvtrapd-client
port of 1661 on the remote machine.
Does anyone
see a problem with the Tivoli Monitoring Universal agent listening on this port
where Netview is running?
Does Netview
use this port locally for anything?
Sean Lawrence
Systems Automation Technical Specialist
905-790-5728_______________________________________________
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)
*** eSafe scanned this email for malicious content ***
*** IMPORTANT: Do not open attachments from unrecognized senders ***