Dell SmartFabric OS10 Installation, Upgrade, and Downgrade Guide

Important notes

• Single rack SFS upgrade from Release 10.5.0.7P3 to 10.5.2.6 or later with breakout configuration on uplink connections For single rack deployment with two leaf switches, if there is breakout configuration on the uplink connections, do not use the OMNI user interface for upgrade. Use the OS10 CLI and follow the steps that are listed below to upgrade the switches:
  1. Upgrade the SFS standby node from the CLI. After the SFS standby node is upgraded and joins the cluster, perform a switchover through the Linux shell to make this node the SFS primary node (Master). To do this, you must enter the following commands:

     system sudo -i
     python /opt/dell/os10/bin/rest-service/tool/dnv_cli.py
     dnv$ switchover
     dnv$ exit
     

  2. Upgrade the second node after the switchover.
• Single rack SFS upgrade from Release 10.5.0.7P3 to 10.5.2.6 or later without breakout configuration on uplink connections: For single rack deployment with two leaf switches, if there is no breakout configuration on the uplink connections, follow the normal upgrade procedure using the OMNI user interface.
• Dell Networking SFS deployment with S4100 switches: If you have deployed S4100-ON switches, see the Dell PowerSwitch S4100-ON Series ONIE Firmware Updater Release Notes for the latest recommended ONIE and ONIE firmware versions. We recommend that you upgrade ONIE and ONIE firmware to the latest recommended versions before you upgrade OS10.
• See the Networking Solutions Support Matrix for more information.
• SFS upgrade from Release 10.5.3.1 or earlier to Release 10.5.3.2 or later: The following procedure is not applicable if the OS10 switch is already running Release 10.5.3.2 or later software. Before you upgrade the fabric, you must run the following curl command on each of the leaf nodes in the deployment. Run this command on the leaf nodes one after another continuously. You can run this command in any one of the following ways:
  • Run this command from a remote server using the leaf node's management IP address if the node is reachable:

    login-chn-02:/swt_scripts_repo/feature/SFS> curl -i -k -H "Accept: application/json" -H "Content-Type: application/json" -u REST_USER:admin -d '{"nvo-evpn:evpn":{"disable-rt-asn":true}}' -X PATCH https://10.10.72.184/restconf/data/nvo-evpn:evpn
    HTTP/1.1 204 No Content
    Server: nginx
    Date: Thu, 04 Aug 2022 06:44:47 GMT
    Connection: keep-alive
    Cache-Control: no-cache
    Pragma: no-cache
    X-Frame-Options: SAMEORIGIN
    Strict-Transport-Security: max-age=31536000; includeSubDomains
    X-XSS-Protection: 1; mode=block
    
    login-chn-02:/swt_scripts_repo/feature/SFS>
    
    

    where 10.10.72.184 is the management IP address of the leaf node.
  • If you have not configured a management IP address or if the node is not reachable, log in to the leaf node through the console and enter the following command using the loopback address:

    LEAF1# system "sudo -i"
    
    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:
    
        #1) Respect the privacy of others.    #2) Think before you type.    #3) With great power comes great responsibility.
    
    [sudo] password for admin:
    root@POD3-LEAF1:~#
    root@POD3-LEAF1:~# curl -i -k -H "Accept: application/json" -H "Content-Type: application/json" -u REST_USER:admin -d '{"nvo-evpn:evpn":{"disable-rt-asn":true}}' -X PATCH https://127.0.0.1/restconf/data/nvo-evpn:evpn
    
    HTTP/1.1 204 No Content
    Server: nginx
    Date: Thu, 04 Aug 2022 06:40:15 GMT
    Connection: keep-alive
    Cache-Control: no-cache
    Pragma: no-cache
    X-Frame-Options: SAMEORIGIN
    Strict-Transport-Security: max-age=31536000; includeSubDomains
    X-XSS-Protection: 1; mode=block
    
    LEAF1:~#

  • You can also use any API tool such as Postman on the leaf nodes.
  • Secure (HTTPS) mode support in SFS: Starting from Release 10.5.5.5, SFS supports secure (HTTPS) mode of access by default. With this enhancement, all nodes in a cluster automatically transition from the previous nonsecure (HTTP) mode to the secure (HTTPS) mode once they are upgraded to the latest OS10 version. However, note that the transition to the secure mode does not occur if any switch available in the cluster is running an earlier version of the software that does not support the HTTPS protocol. In such cases, the cluster continues to operate in the nonsecure mode until all switches are updated to an OS10 version that supports HTTPS. Once the cluster has fully transitioned to the secure mode, any new node attempting to join the cluster must run an OS10 version that supports HTTPS; otherwise, the cluster joining process will not be successful.
  NOTE:Without running the curl command on the leaf nodes, if you upgrade from Release 10.5.3.1 or earlier to Release 10.5.3.2 or later, traffic loss for about 5 to 7 minutes is observed.