Wired Networks Thread, Cisco SG300 series, any reason why not? in Technical; I'm replacing the aging ethernet switches at our school. My plan is to use a 28 port as the core, ...
25th April 2013, 07:39 PM #1
- Rep Power
Cisco SG300 series, any reason why not?
I'm replacing the aging ethernet switches at our school. My plan is to use a 28 port as the core, a 28 port to aggregate non-wifi traffic and 2 x 10 port PoE to host and aggregate traffic from the wireless access points.
Does anybody have any show-stopping reasons why not? They seem competitively priced to me.
29th April 2013, 01:53 AM #2
They are a decent SMB managed switch. That being said you are limited to configuration via the web interface as these do not run the full Cisco IOS. If you don't require some advanced layer 2 features, these would be fine for general access closet switches.
Thanks to Destinova from:
catch21 (29th April 2013)
30th April 2013, 12:37 PM #3
You can also config the switch via SSH, Telnet and serial connection. If you want to enable Layer3 you will need to use Telnet to enable it.
Originally Posted by Destinova
30th April 2013, 03:13 PM #4
You could also call it Docker wtf.
Thanks to Miscbrah from:
catch21 (30th April 2013)
30th April 2013, 04:05 PM #5
- Rep Power
I flippin' hope they're all right I've had five arrive on site today
1st May 2013, 10:29 AM #6
- Rep Power
Ah, the joys of CLI and quick-start guides written by people who know how to do things.
e.g. "use the CLI to set your IP address"
I used maximop and george 3 in the mid 70's which were less opaque than CLI and must be the longest persisting joke in history.
Anyway the challenge is to get a web browser session going on it. (Them, everything is x 5)
I can't see the default IP address as its not my network id and putting the switch on the network gives it a dynamic IP address from a large pool. What am I supposed to do, guess?
OK so I can get onto the 2008 server and see what's happening but what if you can't? As the quick start guide says, use the console interface, but then doesn't proceed to tell you how.
What I ended up doing was nmapping the n/w once it had received a dynamic IP address and looked for the base MAC address. For one of the switches that didn't work for some reason and I had to use my RPi to talk to it initially on its default address.
Anyway we're getting there, thank goodness for a small amount of networking knowledge and equipment and the web-based configuration. Personally I think that CLI is something left well behind.
1st May 2013, 01:45 PM #7
Were your switches second hand? Ours came with a manual clearly stating that the switch was factory configured with the IP address 192.168.1.254 so all I had to do was connect the switch to a PC on that range and login and change it.
Cisco Small Business 300 Series Managed Switches Command References - Cisco Systems
1st May 2013, 05:37 PM #8
- Rep Power
Yes, they were new and thanks for the thoughts. I used my RPi in the end to do exactly as you say because its, and you're not supposed to use the "T" word in schools, slightly less thick than a PC which is more likely to give up without trying for an address than succeeding.
My rant was more directed towards the (IMHO) deeply esoteric CLI or more specifically towards the quick start guide designer who didn't think or couldn't be bothered to include the five or so lines of commands needed to set a static IP address, save and exit.
By Mr_M_Cox in forum MIS Systems
Last Post: 25th August 2008, 03:06 PM
By sidewinder in forum General Chat
Last Post: 10th June 2008, 05:46 PM
By TronXP in forum Wireless Networks
Last Post: 7th May 2008, 02:26 PM
By rpycroft in forum Hardware
Last Post: 29th January 2008, 04:55 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)