CLI Access to SG200 Switches?

[Jason Van Patten]

Hey folks -

I saw another year old thread on this same topic, but it didn't really seem to be answered.  I just picked up a pair of 18-port SG200s, and I'm trying to figure out of there's some secret trick to getting CLI access to them?  I've upgraded to the latest version of firmware (1.2.7.76) hoping that may help, but no luck.

I can tell the guts to support a CLI are there, because writing the config out to a TFTP server shows identical an identical config style to the SG500 I have here.

Is there some way to enable it?  Thanks!

jas

[Tom Watts · Accepted solution]

Hi Jason, the SG200 does not support any CLI. The SG200E model does.

-Tom
Please mark answered for helpful posts

[Jason Van Patten]

Tom -

Tom Watts wrote:
Hi Jason, the SG200 does not support any CLI. The SG200E model does.

Thanks for the quick answer.  Do you know the reason why Cisco decided to disable it on the SG200s?  It's clear as day that the config is stored in such a way that it could be accessed that way...

jas

[Tom Watts]

Because there is SG200E model which has enchanced management features such as cli

-Tom
Please mark answered for helpful posts

[Jason Van Patten]

Tom Watts wrote:
Because there is SG200E model which has enchanced management features such as cli

Unfortunate, but thanks for the info.

jas

[IRSlashie]

Tom Watts wrote:
Hi Jason, the SG200 does not support any CLI. The SG200E model does.
-Tom 
Please mark answered for helpful posts

I know this is an old post, but I had the same question about the SG200 supporting Cli & Tom’s answer guided me in the correct direction.

However after a lot of research, it seems that you do not get a SG200E, but only the SF200E which is the 10/100Mbit version.
Shame though, would have liked to have the SG range to have Cli functionality too...

[rotogluon]

I got the cisco SG 200 8P smart switch with power over ethernet and I really don't understand how comes there is no CLI support out of the box...

I mean, the latest firmware (1.7.x) still doesn't allow me to stop services that use the ports 2222 and the other one around 4500 (I don't remember the specific number and I'm not at home atm).which are opened by default... how comes I can't choose whether I want those ports to be opened or not ?

I mean, the cost would be nothing for cisco to allow the people who buy this kind of expensive hardware to access CLI, since they obviously spent much time building this "rich HTML" web based interface...

So, no, that's an unacceptable answer.

I'd better have a CLI only management with enable mode rather than this incomplete web interface... not that user friendly, to be said.

[Joe@Franke]

Old post but maybe someone out there still needs it.  I pulled the startup down through the GUI and edited it directly.  Uploaded it back to running-config and BAM my stuff worked!