Update to v 6.0.0.34 and now "Device failed to apply configurations. (ErrorCode: switch_100)" errors
After upgrading my OC300 controller to 6.0.0.34 I get "Device failed to apply configurations. (ErrorCode: switch_100)" errors in the Configuration Result Failed logs. Basically 22 lines of failures (before expanding some lines) for every possible configuration detail.
However, the strange thing is that the switches appear to get configured.
I have (besides a ER7412-M2 router), 2x SG3428XPP-M2 v1.20, 1x SG2008 v4.20, 1x SG3218XP-M2 v1.0 and 1x SG2008P v3.20.
The long list of errors appeared after I updated two of the switches to the new firmware which was also released.
I suspected the new firmware was the problem. However, when I Force Provision a switch which is not updated yet, it also gives the same long list of errors. Switches which I did not upgrade or did not Force Provision do not show these errors.
When I make small changes (I add or remove a VLAN or change the name of a switch), the changes *ARE* present on the switches when I check it with "Show Running Config" and these changes are not showning any error. Only Force Provision or Apply Again give me this list of errors.
I removed one of the switches from the controller, did a factory reset of that switch and adopted it again. Same result. I downgraded the firmware, same result.
So it appears that the OC300 with 6.0.0.34 is doing something strange. It appears to configure the switches, but does not like the result of this configuration.
Anyone else seen the same problem?
Marcel
@Vincent-TP Hello Vincent,
These errors occur indeed every time with a force provisioning and/or re-adopt and/or apply-again. The complete list of failures are then shown again (with the current time).
A small change like changing the name of a VLAN, adding or removing a single VLAN, setting the allowed VLANs on a port are *not* causing failures in that log. I checked the "show running config" to see if those small changes are present in the running config and they are. So it appears to be only happening when *all changes* are made at once or something like that.
I also did a factory reset of one of the switches and went through the adopting process. Still exactly the same failures but in the end, it appears to be a fully functioning configuration, at least according to "show running config" and based on the fact that the switch appears to be doing what it is supposed to do.
As it appears to be every provisioning command that has failed, it almost looks like it does not process the (positive) result correctly as the changes appear to have been made.
I do not have Omada Access Points. I have the devices as listed in the attached image.
The problem is currently only with the "Switch AV system". "Switch Tuinhuis" and "Switch Werkkamer".
- Switch Tuinhuis was firmware upgraded to 1.0.16 after the controller upgrade and then showed the errors.
- Switch Werkkamer was firmware upgraded to 3.20.14 after the controller upgrade, then showed the errors. I then downgraded it to 3.20.9, still errors. Then factory reset it, new adoption, still errors, upgrade to 3.20.14 again, still errors.
- Switch AV system was *NOT* upgraded to the recent version, but I did a Force Provision to test the result and that showed the errors also.
- The Switch 1 MER and Switch 2 MER have not been upgraded, I did no Force Provision or Apply Changes and they do *not* show the errors. I bet you that they will show the errors when I would upgrade or force provision them.
Hope this helps.