Sorry netdata,
I misunderstood of what you say in the first place, which means to put the fqdn
for the zenoss server instead of localhost.
Now I getting a little feedback, albeit questionable still.
-------------------------------------
>From the output locally:
tracepath.py 192.168.3.6
Getting path from billion.dyndns.org to 192.168.3.6...
zenoss -> -> 192.168.3.6
What's the mean by the missing link between zenoss & 192.168.3.6 ? Maybe the
missing link can be replaced by some readable error message.
---------------------------------------
>From the output remotely:
tracepath.py korriger.homeip.net
Getting path from billion.dyndns.org to korriger.homeip.net...
Traceback (most recent call last):
File "/usr/local/zenoss/bin/tracepath.py", line 30, in ?
path = source.os.traceRoute(destination, [])
File "/usr/local/zenoss/Products/ZenModel/OperatingSystem.py", line 119, in
traceRoute
raise TraceRouteGap("unable to trace to %s, gap at %s" % (target.id,
Products.ZenModel.Exceptions.TraceRouteGap: unable to trace to
korriger.homeip.net, gap at billion.dyndns.org
Some error message which seem to cannot trace the routes between source and
destination.
-------------------------------------------
Testing between zenoss server and the fqdn of internal server:
tracepath.py viva.mordor.com
Getting path from billion.dyndns.org to viva.mordor.com...
Invalid destination.
tracepath.py 192.168.3.135 (a.k.a viva.mordor.com)
Getting path from billion.dyndns.org to 192.168.3.135...
zenoss -> -> 192.168.3.135
This is all output of what I get from my test. [Wink]
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23030#23030
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
