Do I need 1 or 2 Smart Switches?
-
It's good advice from people with experience. I've done a few of these now, and I agree with them. There really isn't any benefit to leaving the SG 300 in mode 2. As to why it's painful, you loose basic configuration that has nothing to do with mode 2/3 like certificates, users, logging, channel groups, port identification, etc. These are things you really don't want to loose, and really shouldn't loose, in a mode switch. And no, you can't reload the prior config. You have to hand edit a new config, which requires a good knowledge of what has to be changed between the modes. And if you have certificates in the config? Ouch.
-
If you have someone that is unsure of use of the switch, the differences between layer 3 and layer 2.. I don't agree with putting it in layer 3 mode and only using it as layer 2. You would be better off leaving it layer 2 only if that is what your learning/playing with.
The move to layer 3 if that is what you want to do and the having to put back all your common info like users and certs or ssh keys, etc. Would all be good practice for the new user ;)
I don't see how home/lab use of this device be layer 2 or layer 3 moving back and forth should be that big of a deal. If your using it in a actual production setup with a complex setup you should know how your going to use it out of the gate anyway ;)
-
The problem is all your layer2 config. VLANs, tagged/untagged ports are blown out. You should be able to restore a layer 2 config to a layer 3 switch. Layer 3 to layer 2 probably not so much, but I would expect Cisco to disregard the config it doesn't understand and honor what it does. That's what you pay for.
I set my recently-acquired SG300 to L3 out-of-the-box for just this reason.
-
So what if they are blown out, just put them back.. You can paste in the part of the config that is pertinent.. If your trying to restore from the gui you might have some issues? But you can always copy and paste the good stuff from your config via the cli without issue.
You put it in layer 3 mode out of the box for what reason - your using it as layer 3?? Do you see a need in the future to use it as layer 3?
-
You can't just paste the pertinent stuff back. It ends up being more complicated than that. And by the time you have the experience necessary to hand edit the config, you have learned enough to know that you want preserve your options and put the unit in mode 3 from the beginning. Even if you have no immediate need for layer 3 routing, there is no advantage to leaving it in mode 2.
-
Other than less overhead of something your not using..
I am fairly freaking sure I can past my port configs and what vlans they are in back in.. Not like the syntax of commands change for gosh sake..
I half mind to switch it layer 3 just to prove my point ;)
-
In the for what it's worth category, I installed my first SG350 (replacement for the SG300) yesterday. They have completely done away with the system mode setting. :)
-
You wanna say it's always in L3 mode?
BTW: Can you tell differences between 300 and 350 series? I find them extremely hard to find on Cisco's pages… :(
-
Huh? What are you looking for on cisco?
http://www.cisco.com/c/en/us/products/switches/350-series-managed-switches/index.html
http://www.cisco.com/c/en/us/products/switches/small-business-300-series-managed-switches/index.html -
The differences between SG300 and SG350.
Like compare SG300-10 and SG300-20 features and technical data. I know those tables.Or any other document which describes what's new in 350 series.
Basically I don't want to campare the complete feature sets myself, only the diffs. -
You wanna say it's always in L3 mode?
BTW: Can you tell differences between 300 and 350 series? I find them extremely hard to find on Cisco's pages… :(
I wasn't able to find any meaningful comparison of the two series on Cisco's site either. I'm guessing that is intentional.
Yes, the main unit itself is always L3. The biggest change that I've noticed is that the 350 has true IPv6 support, and actually appears to route IPv6 at "wire speed". Other things of note include double the TCAM entries (includes IPv6), sFlow support, remote SPAN support for interface or vlan mirroring, L2/L3 on a per interface basis, policy based routing, and port flap monitoring. It also purports to be truly stackable.
There is a new UI. Mostly good. The built in help effectively replaces the Admin Guide and is pretty good. Couple of annoying things: it seems to ignore the idle timer settings and logs you out every two minutes (I assume this is a bug); it has a basic/advanced display mode which would be fine except that basic mode hides almost all IPv6 settings. It also has SNA (Smart Network Application) which I do not have a good use for yet.
One thing that I thought was rather nice is that the 10 port version can itself be powered by upstream POE ports with pass power through to downstream ports. It can also be used as a backup power to an AC adapter. Kinda sweet.
The big disappointment (for me) is that gigabit port to port latency has not improved. Still 2450ns for idle, 3200ns under load for the 10 port unit. The 28 port should offer slightly better numbers (200-300ns), but I haven't tested it yet.
-
"It also purports to be truly stackable."
Huh where are you seeing that you can stack it? The SG500 series is stackable.. Maybe your thinking the 350X ?
-
I'm aware that it's not in the data sheet John. It's in the UI help and in the configs. I don't have a second 350 unit to confirm or deny, hence the term "purports."
-
I thought the stackable (max 4) part was the 350X.
-
And does it have a stack port on the back of it? How exactly are you suppose to stack it?
Looking online for images of the sg350 and do not see any place that would allow to connect the stack..
-
Perhaps I wasn't clear enough. I only have the 10 port sg350 at this time. Stacking, if it exists on the 350, would be with the 28 or 48 port models, which I have not yet had my hands on. The admin guide directly implies that the 350 series is stackable, and stack information is kicked out in the saved configs, even for the 10 port. Of course, this may be an unintended consequence of Cisco choosing to use the same firmware in the sg350 and sg350x series. I honestly don't know. If the stackable distinction is important to you, I would recommend reaching out to Cisco. Btw, there is no separate physical stack port. According to the admin guide, the standard uplink ports are used for stacking.
-
Oddly there's no mention on the main page for the sg350 saying it stacks but on the 350x it does :-
http://www.cisco.com/c/en/us/products/collateral/switches/350x-series-stackable-managed-switches/datasheet-c78-735986.html?referring_site=RE&pos=3&page=http://www.cisco.com/c/en/us/products/collateral/switches/small-business-smart-switches/data-sheet-c78-737359.html
Stacking commands here :-
http://www.cisco.com/c/dam/en/us/td/docs/switches/lan/csbms/350xg/cli_guide/CLI_Switch_350.pdf
-
Gentlemen, have a look yourself:
Cisco Small Business Online Device EmulatorsIIRC, you can even get an SG300-10 in a "stacked mode" from CLI. Well…
-
BTW, 300-series switches are not even end-of-sale yet.
-
dude is there a port to stack it with or not?
As to end of sale.. Pretty sure this looks like end of sale for some of them..
http://www.cisco.com/c/en/us/products/collateral/switches/small-business-stackable-managed-switches/eos-eol-notice-c51-733213.pdf
But looks like its just model number of specific sg300's There clearly could of been a misread there.. I thought it funny that I thought mine was end of sw support back in april but one came out in may, and then another just last month.. So that is clearly a good thing.
If you can stack it there has to be a port to stack with.. So can you send picture of yours that has this port..
