In March 2022, it worked. I upgraded three SG350 switches (two non-PoE 24 port and one non-PoE 8 port) by backing up the running config from each SG350 and updating (importing) each into its CBS 350 counterpart (we bought the CBS models based on Cisco's upgrade guide from the SG350 to CBS 350 line).
So that worked and it was easy through the GUI.
But in July 2022 (today and last week), it hasn't worked with 3 new CBS 350 switches that recently arrived after being backordered forever. Today, for example, I tried to update a new CBS 350 24P using the SG350 28P's backed up config file (tried the running config then focused on startup config; tried with "encrypted," "plaintext" and "excluded" backups from the SG350).
I also tried after updating the firmware that just out on July 21st for the SG 350 and CBS 350.
When trying to update the startup config in the CBS 350 24P, errors appeared referring to Line 44: username <ourswitch's username> has a an encrypted password.
When I tried again using a plaintext backup config and even an excluded backup startup config file, an error appeared that in Line 50: yada yada the same thing, ...the user's <ourswitchusername> password is encrypted.
On each brand new switch, I had already created a username and password that matches their SG350 predecessors.
The error is perplexing. Searching the web for errors with "Line 44" and "Line 50" plus "password encrypted" etc. didn't help.
The only thing different between March and July with the SG350 switches is they no longer have VLAN1 as the native and VLAN1 is disabled now (for security and performance). Back in March, VLAN1 was active and native on the SG350 switches (before I knew better).
Any ideas?
We might reconfigure the new CBS 24P manually with CLI referring to a plaintext version of the running config from the SG350.
Ugh.
