02-11-2019 11:11 PM - edited 03-12-2019 07:17 AM
Hi friends,
on a freshly installed FPR 4110 (2.4(1.222)), traceroute (as a command) doesn't work:
PJFPR# connect local-mgmt
PJFPR(local-mgmt)# traceroute 8.8.8.8
Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-
PJFPR(local-mgmt)#
Any ideas?
02-12-2019 07:08 PM
That's odd - it's definitely a supported command:
What terminal emulator are you using?
02-12-2019 10:48 PM
Hi Marvin,
Yes, it is cut&pasted directly from the documentation. I have used macOS Terminal and ssh. I have now tested the freshly installed SLES and its console now with the same result. I can’t test serial console now unfortunately.
Ping with the same params (with or without "count 2") works ok:
PJFPR(local-mgmt)# ping 8.8.8.8 count 2
PING 8.8.8.8 (8.8.8.8) from 10.74.65.43 eth0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=2.61 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=2.51 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.519/2.567/2.616/0.070 ms
PJFPR(local-mgmt)# traceroute 8.8.8.8
Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-
PJFPR(local-mgmt)#
PJFPR(local-mgmt)# traceroute6 2a01::1
Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-
PJFPR(local-mgmt)# ping 2a01::1
connect: Network is unreachable
PJFPR(local-mgmt)#
Only ping output is correct.
After few more tries, I added also the source address and it works:
traceroute 8.8.8.8 source 1.2.3.4
where 1.2.3.4 is my IP I can see in
PJFPR(local-mgmt)# show mgmt-port
eth0 Link encap:Ethernet HWaddr 70:6d:15:xx:xx:xx
inet addr:1.2.3.4 Bcast:1.2.3.255 Mask:255.255.255.0
...
PJFPR(local-mgmt)#
The output is edited for privacy.
So it definitely looks like a documentation (source is needed) or software bug. Can anyone reproduce?
PJFPR# show version
Version: 2.4(1.222)
Startup-Vers: 2.4(1.222)
PJFPR#
02-13-2019 05:59 PM
I don't have a 4100 series to test on right now but it definitely looks like a documentation (or possibly software) bug.
I'd recommend submitting a documentation feedback report by clicking the link on the page I mentioned earlier documenting the command. It definitely indicates the "source" keyword is optional.
I've found Cisco to be responsive to feedback via that venue. I've had a couple of docs updated by using it.
02-14-2019 01:19 AM
Yes, done.
03-14-2019 11:14 AM
This was a bug (CSCvo40020 which was a duplicate of CSCvn85159). The issue was fixed in the most recent FXOS release.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: