SG300 Configuration Files and Compatibility

[fmarshall]

We have a number of SG300 switches.  For now, I'm happy to just limit the discussion to the -20.

I have a -20v02 switch in production with firmware 1.3.0.62 and need to upgrade to 1.4.9.4.

I also have a couple more v02 switches with 1.4.9.4.

I have backed up the configuration file from the 1.3.0.62 and have had no luck in loading it into one with 1.4.9.4.  Maybe that one switch is bad but I can't try another right now.  

Anyway, this situation results in questions:

1) Can a configuration .txt file from a 1.3.0.62 be loaded into a 1.4.9.4 normally?

2) Can a configured v02 be upgraded fro 1.3.0.62 to 1.4.9.4 and keep its configuration?

3) Can a configuration from a 1.4.9.4 v02 be loaded into another `1.4.9.4 v02 successfully?

4) Or, are the configuration files for 1.4.9.4 v02 machine-specific? (I hope NOT).

5) Since the configuration files are .txt, can they be edited and, if so, why might one want or need to do that?

[riteshsh]

Hi,

My name is Ritesh Sharma from Cisco TAC. 

Please find the below answeres for your queries :

1. Yes, you can upload the config file from SG300 1.3.0.62 firmware to Sg300 1.4.9.4.

2. Yes, uploading the firmware will not delete the switch configuration.

3. Yes, uploading a config file from same device with same firmware is also possible.

4. No, its not machine specific.

5. No, config file cannot be edited.

Please mark this as helpful if it resolved your issue.

Thanks and Regards

Ritesh Sharma

[fmarshall]

I am having no success in loading configurations into SG300-20 v02 1.4.9.4

Not via http and not via tftp.

In the http cases, there is not a data value showing at all.

In the tftp cases, the number is something like 1260 or 2580 where it should be around 18000.

Also, most often the port lights go out during the transfer .. ???

[fmarshall · Accepted solution]

The default choice for the upload is the RUNNING file. 

Because of port configuration differences, VLANS, etc., the new ports don't match the original ports.

So, it appears it's important to select the STARTUP configuration file as the Destination.

Then, reboot of course.

It seems rather simple but puts in question the default setting in Download/Backup Configuration/Log.

So obvious and fundamental EXCEPT one doesn't know how the interaction between the "Running File" and the download is actually going to go.  As the download proceeds do parts of the running file change?  It seems so.  Very strange design.  It suggests that the setting Running configuration file is an unusual choice - well unless one wants to change the configuration by upload without going off line.  And, it explains why some configurations could be loaded and others NOT!