what tool do you use for this trace?
If the UnDP (Universal Device poller), you might want to use of of the formatter that will help decoding IP addresses (Show advanced options – Format). You should not need a transform, a formatting should be enough to display IP addresses.
Your tech Oliver recieved the same response as I - I spent 10 hours - on this and pollling mibs is a lot of what i do in my work
It is of course the obvious answer that you should share - but you might try testing it first! :-)
I hope you dont mind my joke! :-O
I tried to create a UnDP on this IP SLA OID, and format it as an "IP Address", and got this.
Is it what you are trying to achieve?
Capture.PNG 8.3 KB
Hi Fcaron... I'm dragging this up from the past..
I am still unable to display the returned IP gibberish from 220.127.116.11.18.104.22.168.22.214.171.124.1.2 rttMonEchoAdminTargetAddress to display as IP addresses correctly.
I just get unreadable characters.
Can you elaborate on how you got this to work?
In 'Show Advanced Options'.
Many thanks in advance.
yes we worked on this and I have now the same result as shown in the screenshot.
We will work on this offline and hopefully have it resolved.
Did this ever get resolved? I'm having the same problem reading IP addresses from and F5 BigIP in NPM 10.3. Trying to read OID 126.96.36.199.4.1.33188.8.131.52.184.108.40.206 (
220.127.116.11.4.1.3318.104.22.168.22.214.171.124) and getting garbage out...