<?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: err-disable in Switching</title>
    <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610612#M162969</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI, we have just had the same problem. Every night the links would go into err disabled state. We contact Cisco and found out that the sfp modules we were using were incompatible. So they replaced them for us with ones that were.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Jan 2011 13:38:07 GMT</pubDate>
    <dc:creator>sslackjcb</dc:creator>
    <dc:date>2011-01-14T13:38:07Z</dc:date>
    <item>
      <title>err-disable</title>
      <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610607#M162964</link>
      <description>&lt;P&gt;hey all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have a stack of 2960 s switches that over night go into err-disable state is there away to check the reason behind the port went into the err-disable state?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;these switch have only just been implemented into the network. two losts of stacking were done with same config but only one stack goes into the err disable state and after being up for a whole day to me it looks like an STP issue. but i would love to be able to see what made the port go into err-disable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 22:58:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/err-disable/m-p/1610607#M162964</guid>
      <dc:creator>Scott_O'Brien</dc:creator>
      <dc:date>2019-03-06T22:58:14Z</dc:date>
    </item>
    <item>
      <title>Re: err-disable</title>
      <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610608#M162965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Scott,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please paste the output of "show log " from the switch, if you havenot rebooted them yet?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other capture that you took while diagnosing this issue? Please paste that as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;-amit singh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jan 2011 10:01:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/err-disable/m-p/1610608#M162965</guid>
      <dc:creator>Amit Singh</dc:creator>
      <dc:date>2011-01-13T10:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: err-disable</title>
      <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610609#M162966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually it will tell you in the log why it put those ports into error disable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jan 2011 12:44:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/err-disable/m-p/1610609#M162966</guid>
      <dc:creator>glen.grant</dc:creator>
      <dc:date>2011-01-13T12:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: err-disable</title>
      <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610610#M162967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also see it by issuing this command:&amp;nbsp; sh errdisable recovery&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/tech/tk389/tk621/technologies_tech_note09186a00806cd87b.shtml"&gt;http://www.cisco.com/en/US/tech/tk389/tk621/technologies_tech_note09186a00806cd87b.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alain.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jan 2011 18:40:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/err-disable/m-p/1610610#M162967</guid>
      <dc:creator>cadet alain</dc:creator>
      <dc:date>2011-01-13T18:40:06Z</dc:date>
    </item>
    <item>
      <title>Re: err-disable</title>
      <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610611#M162968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hey guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your help. as i didnt have eer-recovery on i couldnt use the show -errdisable recovery cmd&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so i used the show log and its showed up as the port was flapping so i have changed the cable and set up err-recovery flap so if it goes down again it will come up after 300 seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the odd thing is that both times it went down it went down around 5- 5:30 the first time was just after&amp;nbsp; there were installed ( finished insall at about 4 and went down at 5. second time was after being up all day come back up at 8:30 and went down again at around 5 or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks all&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jan 2011 04:04:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/err-disable/m-p/1610611#M162968</guid>
      <dc:creator>Scott_O'Brien</dc:creator>
      <dc:date>2011-01-14T04:04:26Z</dc:date>
    </item>
    <item>
      <title>Re: err-disable</title>
      <link>https://community.cisco.com/t5/switching/err-disable/m-p/1610612#M162969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI, we have just had the same problem. Every night the links would go into err disabled state. We contact Cisco and found out that the sfp modules we were using were incompatible. So they replaced them for us with ones that were.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jan 2011 13:38:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/err-disable/m-p/1610612#M162969</guid>
      <dc:creator>sslackjcb</dc:creator>
      <dc:date>2011-01-14T13:38:07Z</dc:date>
    </item>
  </channel>
</rss>

