From: Dave Taht <dave.taht@gmail.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:12:51 -0500 [thread overview]
Message-ID: <CAA93jw5gYJ6kjcG+oCyZjvjjUc+2Zi+ysN5TgB7sLkrUTOc2NQ@mail.gmail.com> (raw)
In-Reply-To: <8948C7F6-3F35-46D5-9367-02B79553E409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
I only recently tried to get vlans to work. I ran into major issues trying
to get babel to work across them, am not sure if I was running into bugs in
quagga or not and gave up (the symptom was that it didn't like having the
same fe80 address on the same LAN despite being vlan'd. )
This obviously isn't your problem. I have not tried of late to jam jumbo
packets through it, I have generally been concerned that bad things would
happen if anyone tried. Aside from that, no clue. There are various means
of monitoring the switch behavior including snmp stuff buried inside the
switch (?) command.
On Wed, Feb 20, 2013 at 11:01 AM, William Katsak <wkatsak@gmail.com> wrote:
> 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
>
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 2195 bytes --]
next prev parent reply other threads:[~2013-02-20 16:12 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
2013-02-20 16:12 ` Dave Taht [this message]
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=CAA93jw5gYJ6kjcG+oCyZjvjjUc+2Zi+ysN5TgB7sLkrUTOc2NQ@mail.gmail.com \
--to=dave.taht@gmail.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