Retrieve Config file from locked out SG200

[chris.elledge]

Hello,

I have a few SG200s, mostly one at each building.  There is one that I suddenly can't log into - "invalid user name or password"*.  With no COM port, it sounds like I don't have many options other than factory reset.   Right?  The basic re-config of this switch shouldn't be too bad, but I dread reconfiguring the 48 ports (full) and various VLANs.  

If I brought another SG200 onsite, would I be able to see any config info of one unit from the other?  These switches don't truly "stack" so I'm doubtful.  Again, mostly need port > VLAN membership.  Even retrieving port "description" field would be a big help.

*In regards to the issue - I just web-accessed that switch about two weeks ago, and I swear I didn't change the PW.  I have no recollection of it at all.  I couldn't get my creds to work one day.  The next day I could - but I was at an inconvenient workstation, figured "must have been a fluke yesterday", closed out, tried to log in from my laptop, and then no luck from that point on.  Can't get on from any computer / VLAN.  Otherwise the device is operational.  I plan on power cycling the device sometime but now I'm afraid that it won't come back up at all.  Anyone else hear of this symptom?  Or am I just in denial?

[Michal Bruncko · Accepted solution]

Hi Chris

> I dread reconfiguring the 48 ports (full) and various VLANs.

no worries. SG200 switches uses plain-text form of configuration files (with same syntax like SG300 units have). if you are doubt with "click-hell" due to number of ports and VLAN assignments, then I propose to:

• download configuration file from switch from another building
• make changes to meet your needs on affected switch with directly editing/modifying all config options in that config file regards to VLANs and ports requirements
• and upload that file to affected switch after factory reset

SG200 switches uses a bit modified firmware of SG300 units (looks like only CLI is disabled), but syntax and options are almost same.

And of course make an copy of configurations from all switches for future cases :-)

[chris.elledge]

Good idea on the SNMP, but I believe that switch still has the factory defaults for SNMP (Service is enabled but not configured).  

I had looked at the downloaded config files for another switch and hoped to be able to do as you suggest (text edit and upload to problem switch).  I figured there would be no real loss if it didn't work.

Thanks for your suggestions!

[Michal Bruncko]

hi Chris

you're right - if you haven't configured SNMP communities by yourself, then they are not set by default even if SNMP service is enabled. Thus you will not be able to use it unfortunately. Some NW devices has at least default community strings set from factory ("private" for RW access, "public" for RO access) which is not this case. On the other side this behavior on Cisco SMB devices increases security as SNMP is really powerful tool.

[Michal Bruncko]

by the way what about SNMP on switches? are you use it? If so (and if it will work, there will be possibility to change admin password via SNMP write community or at least retrieving configuration options from SNMP MIB).