Skip to main content

2 - Dell Open Networking Switch OS10

Managed Object Procedure (MOP) for Upgrading Dell Open Networking Switch OS10 to Latest Firmware on an Air-Gapped System

Purpose: This MOP outlines the steps to upgrade the firmware on a Dell Open Networking (OS10) switch to the latest version on an air-gapped system (no internet connection). The upgrade will be performed by transferring the firmware image using Secure Copy (SCP) from a laptop directly connected to the switch's dedicated management interface.

Service Impact Summary:

  • The switch's management interface will be unavailable during the upgrade process, which can range from a few minutes to half an hour depending on the switch model and firmware size.
  • Depending on the firmware version being upgraded from, there might be brief service interruptions on data plane ports while the switch reboots after the upgrade.

Backup Procedure:

  1. Configuration Backup:

    • Connect to the switch using the command-line interface (CLI).
    • Enter the following command to capture the running configuration:
    Bash
    copy running-config startup-config
    • This will save the current switch configuration to the startup-config file, which is used to automatically load the configuration when the switch reboots.

  2. Software Image Backup (Optional):

    • Download the currently running firmware image from the switch using SCP (refer to "Transferring the Firmware Image" section for SCP details). This step is optional but recommended in case of any rollback scenario.

Upgrade Procedure:

  1. Preparation:

    • Download the latest firmware image compatible with your switch model from Dell's support website (https://www.dell.com/support/home/en-us). Ensure the downloaded image is suitable for air-gap deployment.
    • Connect your laptop directly to the switch's dedicated management port using a standard Ethernet cable.
    • Verify network connectivity between the laptop and the switch's management interface. You can use ping or SSH to test connectivity.

  2. Transferring the Firmware Image:

    • On your laptop, initiate an SCP session to transfer the downloaded firmware image to the switch. You will need the switch's IP address, username, and password for the management interface.
    Bash
    scp <firmware_image_filename> <switch_ip_address>:/path/to/store/on/switch
    • Replace <firmware_image_filename> with the actual filename of the downloaded firmware image.
    • Replace <switch_ip_address> with the management IP address of the switch.
    • Replace /path/to/store/on/switch with the desired location on the switch to store the firmware image. The default location might be /flash/.

  3. Upgrading the Firmware:

    • Login to the switch's CLI using SSH or the console port.
    • Enter the following command to install the transferred firmware image:
    Bash
    install software image-path /path/to/firmware/image.bin force

    • Replace /path/to/firmware/image.bin with the actual path where you uploaded the firmware image in the previous step.

    • The force option is used to overwrite any existing firmware with the same version.

    • The switch will prompt you to confirm the upgrade process. Enter y to proceed.

    • The switch will download and install the new firmware. The switch might reboot one or more times during the installation process.

  4. Verification:

    • After the upgrade is complete, the switch will automatically reboot.
    • Once the switch is back online, log in to the switch's CLI and verify the firmware version using the following command:
    Bash
    show version
    • The output should display the newly installed firmware version.

Rollback Procedure:

  1. If you encounter any issues after the upgrade, you can perform a rollback to the previous firmware version.
  2. Ensure you have a backup of the previously running firmware image (refer to the "Backup Procedure" section).
  3. Follow steps 2 and 3 from the "Upgrade Procedure" section to transfer the backup firmware image to the switch and install it using the install software command.

Important Notes:

  • This MOP is a general guideline and might need adjustments based on your specific switch model and firmware version.
  • Always refer to the Dell documentation for your specific switch model for detailed upgrade instructions and supported firmware versions.
  • Carefully review the release notes of the new firmware version to understand any potential risks or limitations before proceeding with the upgrade.
  • Perform the upgrade during a maintenance window to minimize service disruption.

By following this MOP, you can securely upgrade the firmware on your Dell Open Networking switch in an air-gapped environment. Remember to document the entire process, including the firmware version used before and

Comments

Post a Comment

Popular posts from this blog

Swagger

Subject: Next Steps for Troubleshooting Your Filter Issue - Test Scenario with Swagger Subject: Next Steps for Troubleshooting Your Filter Issue - Test Scenario with Swagger Hi [Customer Name], Thank you for your patience as we continue to troubleshoot the filter deletion issue you're experiencing. To further investigate the cause, we'd like your help running a quick test scenario using the Swagger software. Here's what we need you to do: Access Swagger: Open Swagger for our application. You can usually access it through [link to Swagger documentation/interface - replace with specific instructions]. Target Selection: Locate the endpoint related to retrieving filters. This might be named something like "GET /filters". "Try it Out": Click the "Try it out" button associated with the endpoint. Filter Criteria: In the request body section, locate the field for filtering results. Set the criteria to retrieve only filters with an "active...
Post a Comment
Read more

Closure

Closure Criteria: Issue Resolved : The underlying problem has been successfully resolved. Workaround Provided : A temporary solution has been provided, and the user has been informed of the permanent resolution timeline. Issue is Deferred : The customer has agreed to defer resolution to a future release or update. Additional Considerations: Knowledge Base Update : If applicable, the resolution should be documented in the knowledge base for future reference. Follow-up : If necessary, schedule a follow-up ticket to ensure the resolution is holding. Escalation : If the issue cannot be resolved, escalate to BES team.
Post a Comment
Read more