Hello , @Exalog I read your Question and my conclusion on it is in detailed ,
The blunder message "Mistake opening nvram:/startup-config (No such document or registry)" shows that the gadget can't find or access the startup setup record in the non-unstable Smash (NVRAM) when the "compose memory" order is executed. This mistake can happen in specific situations, and the presence of failover arrangement may be connected with the issue. Here are a few potential reasons and answers for this mistake:
File System Corruption: The NVRAM file system may have become corrupted, causing the device to be unable to locate the startup configuration file. In this case, you can try to perform a file system repair or format the NVRAM. However, before proceeding with this step, make sure to back up your configuration settings to avoid data loss.
File Permissions: The user attempting to save the running configuration may not have the necessary permissions to access or modify the startup-config file. Ensure that the user has the appropriate privileges to write to the NVRAM.
Failover Configuration: Since you mentioned that the customer has failover configured, it's possible that the startup-config file is being saved on the secondary (failover) device. In a failover setup, the primary and secondary devices share a common configuration, but only the active device (primary) writes to the NVRAM. If the failover has occurred, the secondary device might not have a startup-config file.
Check if the failover has been triggered, and the secondary device is currently active. If so, try executing the "write memory" command on the primary device, which should save the configuration to NVRAM.
File System Location: Depending on the device model and software version, the startup-config file might be stored in a different location. Double-check the correct path for the startup-config file on your specific device.
Hardware or Firmware Issue: In rare cases, the error could be caused by a hardware or firmware issue. If none of the above solutions work, consider contacting the device vendor's support or consulting with a qualified network administrator to investigate further.
Please note that any changes to the device's configuration should be approached with caution, as misconfigurations could lead to network disruptions or security vulnerabilities. If you are not familiar with the device's configuration or troubleshooting procedures, consider seeking assistance from a qualified network professional or the device vendor's support team.
I hope you are like my answer always i try my best thank you ,
Best Regards ,
