<?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: Debugging Algo boost / Warp mode in Switching</title>
    <link>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386335#M414780</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have looked through all command references, it appears that the amount of 'debug' commands has been severely limited on the 3548. Which makes sense, since debugging uses a lot of CPU cycles and slows everything down. Especially since they market this model as being capable of 190 nanosecond packet switching speed due to the algo boost feature...&lt;/P&gt;</description>
    <pubDate>Mon, 21 May 2018 10:42:56 GMT</pubDate>
    <dc:creator>Georg Pauwen</dc:creator>
    <dc:date>2018-05-21T10:42:56Z</dc:date>
    <item>
      <title>Debugging Algo boost / Warp mode</title>
      <link>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386119#M414754</link>
      <description>&lt;P&gt;I have a Nexus 3000 switch that is capable of Algo Boost / Warp mode that I want to debug that is kinda like debug ip packet detail or debug ip cef. What's the command to do this? Also, how do I send that debug output results on console or terminal monitor to syslog?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 23:04:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386119#M414754</guid>
      <dc:creator>homelabnoob</dc:creator>
      <dc:date>2019-03-08T23:04:33Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging Algo boost / Warp mode</title>
      <link>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386335#M414780</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have looked through all command references, it appears that the amount of 'debug' commands has been severely limited on the 3548. Which makes sense, since debugging uses a lot of CPU cycles and slows everything down. Especially since they market this model as being capable of 190 nanosecond packet switching speed due to the algo boost feature...&lt;/P&gt;</description>
      <pubDate>Mon, 21 May 2018 10:42:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386335#M414780</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2018-05-21T10:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: Debugging Algo boost / Warp mode</title>
      <link>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386441#M414804</link>
      <description>Yea, I didn't see one either. Do you think Cisco TAC would know?</description>
      <pubDate>Mon, 21 May 2018 14:16:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/debugging-algo-boost-warp-mode/m-p/3386441#M414804</guid>
      <dc:creator>homelabnoob</dc:creator>
      <dc:date>2018-05-21T14:16:23Z</dc:date>
    </item>
  </channel>
</rss>

