From: dpreed@reed.com
To: "William Katsak" <wkatsak@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Switch Issue
Date: Wed, 20 Feb 2013 11:09:04 -0500 (EST) [thread overview]
Message-ID: <1361376544.23218370@apps.rackspace.com> (raw)
In-Reply-To: <8948C7F6-3F35-46D5-9367-02B79553E409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
Not the 3800's switch, but lots of other ones. Often caused by a human cabling error. E.g. a cable connecting one port on a switch to another, which "amplifies" broadcast/multicast traffic into a storm that is also broadcast to other switches, locking up the switch and others.
Just before the switch failed were any events logged related to port up/down? Not that it needs to be the 3800 switch that is the cause.
-----Original Message-----
From: "William Katsak" <wkatsak@gmail.com>
Sent: Wednesday, February 20, 2013 11:01am
To: "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Switch Issue
Hello,
Just wanted to see if anyone has seen an issue like this:
I have a 3800 running Sugarland at a remote site. It was running nice and reliably, connected to the local network by a VLAN trunked connection (I have interfaces for the default VLAN, and VLANS 100 and 200 passing through). Last night it suddenly stopped working. There seems to be no data flowing through the switch at all, even though I can ssh to the router, reboot, poke at it, etc. from over the Internet.
I see no error messages regarding the switch in the logs or dmesg. Anyone else see a 3800 switch crap out unceremoniously?
Thanks,
Bill Katsak
_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 1899 bytes --]
next prev parent reply other threads:[~2013-02-20 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 16:01 William Katsak
2013-02-20 16:09 ` dpreed [this message]
2013-02-20 16:12 ` Dave Taht
2013-02-20 16:28 ` William Katsak
2013-02-20 19:15 ` William Katsak
2013-02-20 19:17 ` Maciej Soltysiak
2013-02-20 19:29 ` David Lang
2013-02-21 13:53 ` Maciej Soltysiak
2013-02-21 14:30 ` William Katsak
2013-02-21 19:43 ` William Katsak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1361376544.23218370@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=wkatsak@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox