I worked around it.... I installed a loopback interface on the client with
the same address as the external address. Then when I told NetView that
this was a SNMP client. It worked.... (This is probably not the most
elegant way to do it, but it looks like it does the work.)
Ray Westphal wrote:
> I use NetView for UNIX (on AIX). Have you checked the SNMP Configuration for
> the IP address 123.123.123.123? You can setup a proxy for the target in the
> SNMP configuration screen.
>
> Hope this helps or applies to NetView on NT.
>
> Ray Westphal
> Enterprise Rent-A-Car
>
> -----Original Message-----
> From: Frode Jemtland [mailto:frode AT roal DOT no]
> Sent: Wednesday, April 03, 2002 8:55 AM
> To: nv-l AT lists.tivoli DOT com
> Subject: [nv-l] NAT problems
>
>
>
> Hello.
>
> I have a problem with a NV installation for a ISP customer.
>
> There is a firewall protecting the ISP from all of the customers, and each
> customer has their own firewalls.
>
> The problem is that the firewalls are using NAT. There no
> problem
> with the trap forwarding. But it is a problem with the status polling.
>
> NetView is suppose to talk to a MLM at the customer site with the
> public address 123.123.123.123 (bound to this host in the firewall NAT
> tables). When NetView does a discovery for this node, it finds out
> that the
> real address is 192.168.1.10. Nobody is answering at this address (of
> course), the node is marked down, even though the address (and
> host name) of 123.123.123.123 can be SNMP browsed, and pinged. Can also do
> the NetView test procedure for the object, both ping and demand poll
> works.
>
> Tech info:
> Server: Win 2000 server, NetView 7.1
> Node/MLM: Win 2000 pro, MLM for NT or win 2000 v. 7.1.0
>
>
> Question:
>
> Is there any feature in NV 7.1 that can be set, so NV knows that this
> host (123.123.123.123) is a NATed host ?
>
> Can I manipulate the route table on the server so every time it asks for
> 192.168.1.10 it is translated to 123.123.123.123 ?
>
> Can I manipulate the firewall at the ISP site so it reNAT's the address
> from 192.168.1.10 to 123.123.123.123 ? (probably not a good solution, but
> a desperate one ;) )
>
> I have heard about something called Tivoli CNAT, what is this, and can
> it solve my problem ?!
>
>
> Please ask me if any thing is unclear.
>
>
>
> ASCII drawing (if it helps?!)
>
> -----------------------------------------------
> 10.100.1.10 nat> <nat 192.168.1.10
>
> |----| |---| |---| |----|
> | NV |-------|fw1|---------|fw2|-------|MLM1|
> |----| |---| |---| |----|
> | |
> |<-------------------------------<|
> | trap forwarding - OK
> |
> |>-X
> | status poll to 192.168.1.10 - unknown address
>
> ----------------------------------------------
>
>
>
> ------------------
> Frode Jemtland
> ITS - IBM Norway
> ------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
> For additional commands, e-mail: nv-l-help AT lists.tivoli DOT 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)
>
>
>
------------------
Frode Jemtland
+47 98 23 28 45
------------------
RandomSelectedSignaturFollows:
«"Amatør" og "inkompetent gjøk" er ikke helt det samme.»
- Erik Naggum, no.it.programmering.c, 2001-12-13 00:41:02 UTC
|
