This article explains a scenario where devices managed via Mist may show frequent configuration failures. The issue is typically related to additional CLI configuration that may not be applied correctly, causing repeated commit attempts and instability in configuration deployment.

Frequent “Config failed” messages observed in the Mist UIMultiple commit confirmed operations triggered automaticallyLogs showing repeated commit confirmation messages:

commit confirmed will be rolled back in 7 minutes

Device repeatedly enters configuration mode without successful commit completion

Root Cause

The issue is often caused by incorrect or unsupported configuration present in the Additional CLI section within Mist. This configuration may fail validation or conflict with existing settings, leading to repeated commit attempts.

Recommended Actions

• Review the Additional CLI configuration in Mist
• Validate configuration syntax and compatibility
• Identify and remove or correct unsupported or conflicting statements

Best Practice

• Test the Additional CLI configuration on a lab device before applying it to production
• Confirm that the configuration can be successfully committed without errors