Why does the sx300 series only displays ping and traceroute results in 20ms intervals (see below)? The example in the CLI manual shows "regular" results. These 20ms intervals are not helpful for troubleshooting.  This is version 1.1.0.73 on an sf300-24. Pinging www.google.com. (74.125.224.147) with 18 bytes of data: 18 bytes from 74.125.224.147: icmp_seq=1. time=20 ms 18 bytes from 74.125.224.147: icmp_seq=2. time=20 ms 18 bytes from 74.125.224.147: icmp_seq=3. time=20 ms 18 bytes from 74.125.224.147: icmp_seq=4. time=20 ms #traceroute ip www.google.com Tracing the route to www.google.com. (74.125.224.147) from , 30 hops max, 18 byte packets Type Esc to abort. 1  66.201.xx.xx (66.201.xx.xx)  <80 ms  <20 ms  <20 ms 2  google.com.any2ix.coresite.com. (206.223.143.41)  <20 ms  <20 ms  <20 ms 3  64.233.174.31 (64.233.174.31)  <20 ms  <20 ms  <40 ms 4  64.233.174.192 (64.233.174.192)  <20 ms  <20 ms  <20 ms 5  64.233.174.205 (64.233.174.205)  <20 ms  <20 ms  <40 ms 6  209.85.250.61 (209.85.250.61)  <20 ms  <100 ms  <20 ms 7  64.233.174.119 (64.233.174.119)  <20 ms  <20 ms  <240 ms 8  nuq04s09-in-f19.1e100.net. (74.125.224.147)  <20 ms  <20 ms  <20 ms From the manual: Example Router> traceroute ip umaxp1.physics.lsa.umich.edu Type Esc to abort. Tracing the route to umaxp1.physics.lsa.umich.edu (141.211.101.64) 1 i2-gateway.stanford.edu (192.68.191.83) 0 msec 0 msec 0 msec 2 STAN.POS.calren2.NET (171.64.1.213) 0 msec 0 msec 0 msec 3 SUNV--STAN.POS.calren2.net (198.32.249.73) 1 msec 1 msec 1 msec 4 Abilene--QSV.POS.calren2.net (198.32.249.162) 1 msec 1 msec 1 msec 5 kscyng-snvang.abilene.ucaid.edu (198.32.8.103) 33 msec 35 msec 35 msec 6 iplsng-kscyng.abilene.ucaid.edu (198.32.8.80) 47 msec 45 msec 45 msec 7 so-0-2-0x1.aa1.mich.net (192.122.183.9) 56 msec 53 msec 54 msec 8 atm1-0x24.michnet8.mich.net (198.108.23.82) 56 msec 56 msec 57 msec 9 * * * 10 A-ARB3-LSA-NG.c-SEB.umnet.umich.edu(141.211.5.22)58 msec 58msec 58 msec 11 umaxp1.physics.lsa.umich.edu (141.211.101.64) 62 msec 63 msec 63 msec Trace completed ... View more

We have 3 sf-300 series switches in Layer3 mode deployed in different offices. We have found that approximately every 2-3 months at all 3 locations users experience a serious reduction in bandwidth. Only after rebooting the cisco does the problem go away and we're okay for another few months. Has anyone else experienced this? Does anyone have any ideas on some setting/feature that may be contributing to this? We are only using several ports and 1 static route on each switch. We are not using any of the bells and whistles on the switch. 2 of the switches are using the original firmware, whereas the other is using the newest firmware.  Maybe this is just what we should expect from a Small Business switch? Thanks. ... View more

Hi all, I'm wondering if we are going to be seeing some better IPv6 support on these switches? Maybe even some static IPv6 routing? Thanks. ... View more

Any hopes of being able to do Pings and Traceroutes from the GUI? It's a little frustrating having to telnet/ssh to do those basic things. It would also be nice to be able to switch to Layer3 mode through the web GUI. ... View more

Is it possible to change modes on the 300 Series from L2 to L3 without using the console cable? I can't seem to find a way. ... View more