Loading...
Loading...
The recommended method to backup and restore a switch configuration is to use thestartup.yamlfile located in the Cumulus/etc/nvue.d/directory. Before replacing any hardware or re-installing a switch NOS, generate acl-support of the switch using nv action generate system tech-support,and transfer the resulting file from/var/support to a secure location from the switch along with/etc/nvue.d/startup.yaml.However, saving a local copy of thestartup.yaml configuration file requires root privileges. As a result, if you are logged in as the user "cumulus," you will not have the proper OS permissions to copy the file directly from the/etc/nvue.ddirectory.Saving the Switch Configuration:The following procedure can be used to save thestartup.yamlfile:Issue thenv config applycommands and then thenv config savecommands. These two steps may be combined into one command by issuingnv set system config auto-save stateenabled and thennv config apply. Applying a configuration in the future will automatically save it to/etc/nvue.d/startup.yaml.Copy the configuration file to the/home/cumulusdirectory on the switch using the command,sudo cp /etc/nvue.d/startup.yaml /home/cumulusModify the permissions of the copied configuration file using the command,sudo chmod 777 /home/cumulus/startup.yaml. Then change the name of the startup file to reflect which switch it was copied from. For example,mv startup.yaml startup-switch1.yamlComplete an SCP/SFTP session to switch as the "cumulus" user and copy the/home/cumulus/startup.yamlfile to a safe location from the switch. The file can now be used to restore a switch in the future.Restoring the Switch Configuration:The following procedure can be used to restore the configuration to a new switch or an existing switch that has been rebuilt/factory reset:If the switch is unconfigured, then it is necessary to assign the IPaddress/subnet/gateway/DNSinformation so that an SFTP/SCP session can be made.SFTP or SCP the startup.yaml file that was saved from the switch previously back to the/home/cumulusdirectory.Issue the command,nv config patch /home/cumulus/startup.yaml,and thennv config applyReboot the switch using the command,nv action reboot systemEnsure that the switch is accessible.Linux-based procedure to remove old cl-support files:SSH to the switch using the "cumulus" user.Issue thecd /var/supportcommandIssue thels'command to show all generated switch cl-support files.Issue the sudo rm (file name.txz)command to remove the file from the switch.If using Cumulus 5.10.0 (or later), you may also use the following procedure:Issue the command,nv show system tech-support filesIssue the command,nv action delete system tech-support files (file name),to remove the file.It is recommended to periodically backup thestartup.yamlfile from all switches to generate support files after making configuration changes and delete the oldcl-supportfiles.
HPE M-Series Cumulus switches in an MLAG configuration are affected by this issue:HPE SN2010M 25GbE 18SFP28 4QSFP28 Power to Connector Airflow Half Width Switch SN2010M with NVIDIA Cumulus - S2T75AHPE SN2100M 100GbE 16QSFP28 Power to Connector Airflow Half Width Switch SN2100M with NVIDIA Cumulus - S2T76AHPE SN3420M 25GbE 48SFP28 12QSFP28 Power to Connector Airflow Switch SN3420M with NVIDIA Cumulus - S2T77AHPE SN3700cM 100GbE 32QSFP28 Power to Connector Airflow Switch SN3700cM with NVIDIA Cumulus - S2T78AHPE SN4600cM 100GbE 64QSFP28 Power to Connector Airflow Switch SN4600cM with NVIDIA Cumulus - S2T80AHPE SN3700M 200GbE 32QSFP56 Power to Connector Airflow Switch SN3700M with NVIDIA Cumulus - S2T79AHPE SN4700M 400GbE 32QSFPDD Power to Connector Airflow Switch SN4700M with NVIDIA Cumulus S2T81A
Go toHPE Services - Technical support phone numbersto create a Sales Force Developer Community (SFDC) case. Provide a note and ask for an escalation to the Engineering Resolution Team (ERT) as soon as possible.Contact the HPE Services L2 team athpepointnextl2networks@hpe.comif you need assistance with creating an HPE Services support case. When opening a case to the HPE ERT team, include thecl-supportandstartup.yamlfiles.If further assistance is needed, contactHPE Customer Support.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.