Recovering and Resetting Cumulus Linux on a PowerPC Switch

Follow

Issue

Somehow my Cumulus Linux OS got corrupted I want to reset it by performing a fresh installation of Cumulus Linux.

For example, you can simulate a corruption by moving the entire system from / to /root/, which corrupts almost every command. At this point, not even a reboot is possible so you reboot the switch by pulling the power cord.

Environment

  • Cumulus Linux 2.x
  • Cumulus Linux 1.5.x
  • PowerPC processor

Note: You can determine your switch's processor type by running uname -p:

cumulus@switch$ uname -p
powerpc
cumulus@switch$

Resolution

  1. Back up anything that your system will let you. Read this article for more information.
  2. Boot the switch, press a key to interrupt the U-Boot countdown and access the U-Boot prompt. At the U-Boot prompt, enter the following:
    => printenv cl.active
    1
  3. This indicates into which slot the switch was last booted. In this case, the switch was booted into slot 1, the corrupted one. To begin fixing the image in slot 1, change to the other slot and boot the switch:
    => setenv cl.active 2
    => saveenv
    => run bootcmd
  4. Reset the other slot (the corrupted slot 1 in this case) by running cl-img-clear-overlay:
    cumulus@switch:~$ sudo cl-img-clear-overlay 1
    You can read more about this command in the Cumulus Linux user guide.
  5. Boot into the now reset slot 1 (the previously corrupt slot) by running cl-img-select:
    cumulus@switch:~$ sudo cl-img-select 1
    Success: Primary image slot set to 1.
    active => slot 1 (primary): 1.5.3-5d31a31-201401211606-final
    slot 2 (alt ): 1.5.3-5d31a31-201401211606-final
    Reboot required to take effect.
    cumulus@switch:~$
  6. Reboot the box and let it boot into slot 1.
  7. Check to see that you are running the switch from the correct image slot:
    cumulus@switch:~$ sudo cl-img-select
    active => slot 1 (primary): 1.5.3-5d31a31-201401211606-final
    slot 2 (alt ): 1.5.3-5d31a31-201401211606-final
    cumulus@switch:~$
Have more questions? Submit a request

Comments

Powered by Zendesk