<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: FXOS and traceroute in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3800637#M982085</link>
    <description>&lt;P&gt;Hi Marvin,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Yes, it is cut&amp;amp;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.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ping with the same params (with or without "count 2") works ok:&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;PJFPR(local-mgmt)# ping 8.8.8.8 count 2&lt;BR /&gt;PING 8.8.8.8 (8.8.8.8) from 10.74.65.43 eth0: 56(84) bytes of data.&lt;BR /&gt;64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=2.61 ms&lt;BR /&gt;64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=2.51 ms&lt;BR /&gt;&lt;BR /&gt;--- 8.8.8.8 ping statistics ---&lt;BR /&gt;2 packets transmitted, 2 received, 0% packet loss, time 1001ms&lt;BR /&gt;rtt min/avg/max/mdev = 2.519/2.567/2.616/0.070 ms&lt;BR /&gt;PJFPR(local-mgmt)# traceroute 8.8.8.8&lt;BR /&gt;Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-&lt;BR /&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/PRE&gt;&lt;DIV&gt;I have two FPRs and both show the same behaviour. ping works, but traceroute (and also traceroute6) don't.&lt;/DIV&gt;&lt;DIV&gt;Machines are in IPv4 only network and ping6 and traceroute6 have different results:&lt;/DIV&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# traceroute6 2a01::1&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# ping 2a01::1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;connect: Network is unreachable&lt;BR /&gt;&lt;SPAN&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;Only ping output is correct.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After few more tries, I added also the source address and it works:&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;traceroute 8.8.8.8 source 1.2.3.4&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;where 1.2.3.4 is my IP I can see in&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# show mgmt-port&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;eth0&amp;nbsp; &amp;nbsp; &amp;nbsp; Link encap:Ethernet&amp;nbsp; HWaddr 70:6d:15:xx:xx:xx &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet addr:1.2.3.4 &amp;nbsp;Bcast:1.2.3.255&amp;nbsp; Mask:255.255.255.0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;...&lt;BR /&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;The output is edited for privacy.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So it definitely looks like a documentation (source is needed) or software bug. Can anyone reproduce?&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR# show version&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Version: 2.4(1.222)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Startup-Vers: 2.4(1.222)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PJFPR#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 13 Feb 2019 06:48:35 GMT</pubDate>
    <dc:creator>paveljanik</dc:creator>
    <dc:date>2019-02-13T06:48:35Z</dc:date>
    <item>
      <title>FXOS and traceroute</title>
      <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3799812#M982070</link>
      <description>&lt;P&gt;Hi friends,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;on a freshly installed FPR 4110 (&lt;SPAN&gt;2.4(1.222)&lt;/SPAN&gt;), traceroute (as a command) doesn't work:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR# connect local-mgmt&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# traceroute 8.8.8.8&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;Any ideas?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 14:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3799812#M982070</guid>
      <dc:creator>paveljanik</dc:creator>
      <dc:date>2019-03-12T14:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: FXOS and traceroute</title>
      <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3800559#M982076</link>
      <description>&lt;P&gt;That's odd - it's definitely a supported command:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/fxos/CLI_Reference_Guide/b_FXOS_CLI_reference/b_CLI_reference_chapter_0101.html#wp2659671621" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/fxos/CLI_Reference_Guide/b_FXOS_CLI_reference/b_CLI_reference_chapter_0101.html#wp2659671621&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What terminal emulator are you using?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 03:08:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3800559#M982076</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-02-13T03:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: FXOS and traceroute</title>
      <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3800637#M982085</link>
      <description>&lt;P&gt;Hi Marvin,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Yes, it is cut&amp;amp;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.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Ping with the same params (with or without "count 2") works ok:&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;PJFPR(local-mgmt)# ping 8.8.8.8 count 2&lt;BR /&gt;PING 8.8.8.8 (8.8.8.8) from 10.74.65.43 eth0: 56(84) bytes of data.&lt;BR /&gt;64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=2.61 ms&lt;BR /&gt;64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=2.51 ms&lt;BR /&gt;&lt;BR /&gt;--- 8.8.8.8 ping statistics ---&lt;BR /&gt;2 packets transmitted, 2 received, 0% packet loss, time 1001ms&lt;BR /&gt;rtt min/avg/max/mdev = 2.519/2.567/2.616/0.070 ms&lt;BR /&gt;PJFPR(local-mgmt)# traceroute 8.8.8.8&lt;BR /&gt;Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-&lt;BR /&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/PRE&gt;&lt;DIV&gt;I have two FPRs and both show the same behaviour. ping works, but traceroute (and also traceroute6) don't.&lt;/DIV&gt;&lt;DIV&gt;Machines are in IPv4 only network and ping6 and traceroute6 have different results:&lt;/DIV&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# traceroute6 2a01::1&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Invalid parameter in , allowed characters are: a-zA-Z0-9. /:@_[]~-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# ping 2a01::1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;connect: Network is unreachable&lt;BR /&gt;&lt;SPAN&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;Only ping output is correct.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After few more tries, I added also the source address and it works:&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;traceroute 8.8.8.8 source 1.2.3.4&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;where 1.2.3.4 is my IP I can see in&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR(local-mgmt)# show mgmt-port&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;eth0&amp;nbsp; &amp;nbsp; &amp;nbsp; Link encap:Ethernet&amp;nbsp; HWaddr 70:6d:15:xx:xx:xx &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; inet addr:1.2.3.4 &amp;nbsp;Bcast:1.2.3.255&amp;nbsp; Mask:255.255.255.0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;...&lt;BR /&gt;PJFPR(local-mgmt)#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;The output is edited for privacy.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So it definitely looks like a documentation (source is needed) or software bug. Can anyone reproduce?&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;PJFPR# show version&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Version: 2.4(1.222)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Startup-Vers: 2.4(1.222)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PJFPR#&amp;nbsp;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 13 Feb 2019 06:48:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3800637#M982085</guid>
      <dc:creator>paveljanik</dc:creator>
      <dc:date>2019-02-13T06:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: FXOS and traceroute</title>
      <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3801417#M982089</link>
      <description>&lt;P&gt;I don't have a 4100 series to test on right now but it definitely looks like a documentation (or possibly software) bug.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've found Cisco to be responsive to feedback via that venue. I've had a couple of docs updated by using it.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 01:59:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3801417#M982089</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-02-14T01:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: FXOS and traceroute</title>
      <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3801637#M982091</link>
      <description>&lt;P&gt;Yes, done.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 09:19:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3801637#M982091</guid>
      <dc:creator>paveljanik</dc:creator>
      <dc:date>2019-02-14T09:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: FXOS and traceroute</title>
      <link>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3819758#M982092</link>
      <description>&lt;P&gt;This was a bug (CSCvo40020 which was a duplicate of CSCvn85159). The issue was fixed in the most recent FXOS release.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2019 18:14:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fxos-and-traceroute/m-p/3819758#M982092</guid>
      <dc:creator>jomarlat</dc:creator>
      <dc:date>2019-03-14T18:14:14Z</dc:date>
    </item>
  </channel>
</rss>

