<?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 traceroute in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93558#M21607</link>
    <description>&lt;P&gt;I would be grateful if someone could provide an answer or point me to the answer for the following.&lt;/P&gt;&lt;P&gt;Having recently installed X5420f switches running Exos 32.2.x.x. I have found that traceroutes to certain destinations drop although from a different vendor switch on the same network pass to the final destination. I believe this is due to the Extreme switch seeing one of the hops as being an unrouteable address although this is indeed valid. I have tried using the Vr Vr-default as well as from the local IP both have the same outcome&lt;/P&gt;&lt;P&gt;Is there a way of forcing the switch to see the hop IP as valid?&lt;/P&gt;&lt;P&gt;I have included parts of the trace 1st from the Extreme switch and second from a Brocade switch on the same site using the same network and gateway. The traceroute on both switches is the same up to the point it drops on the Extreme&lt;/P&gt;&lt;P&gt;Extreme trace&lt;/P&gt;&lt;P&gt;13 169.254.100.226 18 ms 17 ms 18 ms&lt;BR /&gt;14 * * *&lt;BR /&gt;15 * * *&lt;BR /&gt;16 * * *&lt;BR /&gt;17 * * *&lt;BR /&gt;18 * * *&lt;BR /&gt;19 * * *&lt;BR /&gt;20 * * *&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brocade Trace&lt;/P&gt;&lt;P&gt;12 169.254.100.226 (169.254.100.226) &amp;lt;20 ms &amp;lt;20 ms &amp;lt;40 ms&lt;BR /&gt;13 100.72.40.27 (100.72.40.27) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;14 100.72.40.27 (100.72.40.27) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;15 * * *&lt;BR /&gt;16 216.239.43.215 (216.239.43.215) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;17 74.125.246.228 (74.125.246.228) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;18 74.125.242.97 (74.125.242.97) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;19 142.251.52.145 (142.251.52.145) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;20 8.8.8.8 (8.8.8.8) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;/P&gt;&lt;P&gt;Many Thanks Ric&lt;/P&gt;</description>
    <pubDate>Fri, 28 Oct 2022 14:47:39 GMT</pubDate>
    <dc:creator>Ric</dc:creator>
    <dc:date>2022-10-28T14:47:39Z</dc:date>
    <item>
      <title>traceroute</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93558#M21607</link>
      <description>&lt;P&gt;I would be grateful if someone could provide an answer or point me to the answer for the following.&lt;/P&gt;&lt;P&gt;Having recently installed X5420f switches running Exos 32.2.x.x. I have found that traceroutes to certain destinations drop although from a different vendor switch on the same network pass to the final destination. I believe this is due to the Extreme switch seeing one of the hops as being an unrouteable address although this is indeed valid. I have tried using the Vr Vr-default as well as from the local IP both have the same outcome&lt;/P&gt;&lt;P&gt;Is there a way of forcing the switch to see the hop IP as valid?&lt;/P&gt;&lt;P&gt;I have included parts of the trace 1st from the Extreme switch and second from a Brocade switch on the same site using the same network and gateway. The traceroute on both switches is the same up to the point it drops on the Extreme&lt;/P&gt;&lt;P&gt;Extreme trace&lt;/P&gt;&lt;P&gt;13 169.254.100.226 18 ms 17 ms 18 ms&lt;BR /&gt;14 * * *&lt;BR /&gt;15 * * *&lt;BR /&gt;16 * * *&lt;BR /&gt;17 * * *&lt;BR /&gt;18 * * *&lt;BR /&gt;19 * * *&lt;BR /&gt;20 * * *&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Brocade Trace&lt;/P&gt;&lt;P&gt;12 169.254.100.226 (169.254.100.226) &amp;lt;20 ms &amp;lt;20 ms &amp;lt;40 ms&lt;BR /&gt;13 100.72.40.27 (100.72.40.27) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;14 100.72.40.27 (100.72.40.27) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;15 * * *&lt;BR /&gt;16 216.239.43.215 (216.239.43.215) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;17 74.125.246.228 (74.125.246.228) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;18 74.125.242.97 (74.125.242.97) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;19 142.251.52.145 (142.251.52.145) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;BR /&gt;20 8.8.8.8 (8.8.8.8) &amp;lt;40 ms &amp;lt;40 ms &amp;lt;40 ms&lt;/P&gt;&lt;P&gt;Many Thanks Ric&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2022 14:47:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93558#M21607</guid>
      <dc:creator>Ric</dc:creator>
      <dc:date>2022-10-28T14:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: traceroute</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93576#M21613</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;I have managed to answer this myself but thought it might be useful for others that may have experienced this issue.&lt;/P&gt;&lt;P&gt;It appears that Extreme Os uses UDP as the default packet type for traceroutes and by specifying ICMP it works. traceroute 8.8.8.8 icmp&lt;/P&gt;&lt;P&gt;Ric&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 09:43:26 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93576#M21613</guid>
      <dc:creator>Ric</dc:creator>
      <dc:date>2022-10-31T09:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: traceroute</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93578#M21614</link>
      <description>&lt;P&gt;I appreciate the information and advice you have shared. I will try to figure it out for more.&lt;BR /&gt;&lt;A href="https://www.dnahrblock.net/" target="_self"&gt;&lt;FONT color="#FFFFFF"&gt;DNAHRBlock.com&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 11:15:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/traceroute/m-p/93578#M21614</guid>
      <dc:creator>Jayden69</dc:creator>
      <dc:date>2022-10-31T11:15:54Z</dc:date>
    </item>
  </channel>
</rss>

