Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell SmartFabric OS10 User Guide Release 10.5.3

PDF

Upgrade OS10 on VLT nodes with minimal traffic loss

This section describes the steps to upgrade OS10 on VLT peer nodes.

When you upgrade VLT peer nodes, you might see minimal traffic loss.

NOTE: The default X.509v3 certificates used for VLT convergence expire on July 27, 2021. See "Dell SmartFabric OS10 certificate expiration and recommended action" section in Dell SmartFabric OS10 Installation, Upgrade, and Downgrade Guide for additional information before you start the VLT upgrade procedure.
VLT leaf-spine topology

In this example topology:

  • VLT-Peer1 and VLT-Peer2 are leaf nodes that are connected to the spine switch through port channel 10.
  • Host1 is connected to both the VLT peer nodes through port channel 20.
  • Host2 uses switch-independent NIC teaming.
  • Switch1 is connected to the VLT peer nodes through port channel 30.

Summary of Upgrade Steps

  1. Download the new OS10 image.
  2. Install the image on VLT-Peer1 and VLT-Peer2 nodes.
  3. Upgrade the secondary VLT node. The production traffic is not affected during this process because the primary VLT node continues to forward traffic.
  4. After the secondary VLT node upgrade is complete, upgrade the primary VLT node. During the primary VLT node upgrade, the system reloads. During this reload, the secondary VLT node becomes the primary VLT node and prevents maximum traffic loss.

Important notes

  • The ports that are connected to Host2 are not part of a VLT port channel. If you have this type of deployment, configure the delay-restore for orphan ports feature on the VLT nodes to reduce the traffic loss during upgrade or reload.
  • When you upgrade one of the VLT peer nodes (for example, VLT-Peer1), the forwarding plane continues to forward the traffic to the other node (VLT-Peer2).
  • If you are upgrading VLT nodes from 10.5.0.x or previous release to 10.5.1.x or later release, see:
  • You must not make any configuration changes when the VLT peer nodes are running different versions of the software.

Detailed Upgrade Steps

  1. Download the new software image on both the VLT peer nodes from the Dell Technologies Support Site. Extract the bin files from the tar file, and save the file in EXEC mode. Download the extracted bin file to the OS10 switch using the image download command. 
    image download file-url
    For example:
    VLT-Peer1# image download ftp://userid:passwd@hostip:/filepath
    VLT-Peer2# image download ftp://userid:passwd@hostip:/filepath
    NOTE: Some Windows unzip applications insert extra carriage returns (CR) or line feeds (LF) when they extract the contents of a .tar file, which may corrupt the downloaded OS10 binary image. Turn off this option if you use a Windows-based tool to untar an OS10 binary file.
  2. (Optional) View the current software download status in EXEC mode. 
    VLT-Peer1# show image status
Image Upgrade State:     idle
==================================================
File Transfer State:     idle
--------------------------------------------------
State Detail:          Completed: No error
Task Start:            2018-08-16T19:38:37Z
Task End:              2018-08-16T19:38:44Z
Transfer Progress:     100 %
Transfer Bytes:        417828173 bytes
File Size:             417828173 bytes
Transfer Rate:         58152 kbps 
 
Installation State:      idle
--------------------------------------------------
State Detail:          No install information available
Task Start:            0000-00-00T00:00:00Z
Task End:              0000-00-00T00:00:00Z

    VLT-Peer2# show image status
Image Upgrade State:     idle
==================================================
File Transfer State:     idle
--------------------------------------------------
State Detail:          Completed: No error
Task Start:            2018-08-16T19:41:49Z
Task End:              2018-08-16T19:42:09Z
Transfer Progress:     100 %
Transfer Bytes:        417828173 bytes
File Size:             417828173 bytes
Transfer Rate:         21092 kbps 
 
Installation State:      idle
--------------------------------------------------
State Detail:          No install information available
Task Start:            0000-00-00T00:00:00Z
Task End:              0000-00-00T00:00:00Z
  3. Install the image using the image install command on both the VLT peer nodes. 
    VLT-Peer1# image install image://PKGS_OS10-Enterprise10.5.1.0.483stretch-installer-x86_64.bin

Install started.
    VLT-Peer2# image install image://PKGS_OS10-Enterprise10.5.1.0.483stretch-installer-x86_64.bin

Install started.
  4. Use the show image status command to view the installation status. 
    VLT-Peer1# show image status
Image Upgrade State:     idle
==================================================
File Transfer State:     idle
--------------------------------------------------
State Detail:          Completed: No error
Task Start:            2018-08-16T19:38:37Z
Task End:              2018-08-16T19:38:44Z
Transfer Progress:     100 %
Transfer Bytes:        417828173 bytes
File Size:             417828173 bytes
Transfer Rate:         58152 kbps 
 
Installation State:      idle
--------------------------------------------------
State Detail:          Completed: Success
Task Start:            2018-08-16T19:40:57Z
Task End:              2018-08-16T19:45:16Z

    VLT-Peer2# show image status
Image Upgrade State:     idle
==================================================
File Transfer State:     idle
--------------------------------------------------
State Detail:          Completed: No error
Task Start:            2018-08-16T19:41:49Z
Task End:              2018-08-16T19:42:09Z
Transfer Progress:     100 %
Transfer Bytes:        417828173 bytes
File Size:             417828173 bytes
Transfer Rate:         21092 kbps 
 
Installation State:      idle
--------------------------------------------------
State Detail:          Completed: Success
Task Start:            2018-08-16T19:42:59Z
Task End:              2018-08-16T19:47:19Z
  5. Change the boot partition to standby on VLT-Peer1. 
    VLT-Peer1# boot system standby
  6. Save the configuration to startup-configuration. Optionally obtain a backup of the startup configuration in EXEC mode on VLT-Peer1. 
    VLT-Peer1# write memory
VLT-Peer1# copy config://startup.xml config://<backup file name>
  7. Reload VLT-Peer1. 
    VLT-Peer1# reload
  8. Wait for VLT-Peer1 to come up. VLT adjacency will be established. VLT-Peer1 becomes the secondary node. Wait until VLT-Peer1 starts to forward traffic after the delay-restore timer expires. 
    VLT-Peer1# show vlt 100
Domain ID                  : 100
Unit ID                    : 2
Role                       : secondary
Version                    : 2.3
Local System MAC address   : 0c:33:d1:73:cd:00
Role priority              : 32768
VLT MAC address            : 0c:33:d1:e7:5e:00
IP address                 : fda5:74c8:b79e:1::2
Delay-Restore timer        : 90 seconds
Remaining Restore time     : 80 seconds
Peer-Routing               : Disabled
  9. Change the boot partition to standby on VLT-Peer2. 
    VLT-Peer1# boot system standby
  10. Save the configuration to startup-configuration. Optionally obtain a backup of the startup configuration in EXEC mode on VLT-Peer2. 
    VLT-Peer2# write memory
VLT-Peer2# copy config://startup.xml config://<backup file name>
  11. Reload VLT-Peer2. 
    VLT-Peer2# reload
  12. Wait for VLT-Peer2 to come up. VLT adjacency is established. VLT-Peer2 becomes the secondary node. Wait until VLT-Peer2 starts to forward traffic after the delay-restore timer expires. To check the delay-restore timer value, enter the show vlt domain-id command. 
    VLT-Peer2# show vlt 100
Domain ID                  : 100
Unit ID                    : 2
Role                       : secondary
Version                    : 2.3
Local System MAC address   : 0c:33:d1:73:ee:00
Role priority              : 32768
VLT MAC address            : 0c:33:d1:e7:5e:00
IP address                 : fda5:74c8:b79e:1::2
Delay-Restore timer        : 90 seconds
Remaining Restore time     : 80 seconds
Peer-Routing               : Disabled

    When the delay-restore timer expires, the system generates a syslog message similar to the following one: 

    <165>1 2021-02-24T02:29:29.296791+00:00 host1 dn_alm 881 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %VLT_DELAY_RESTORE_COMPLETE: VLT delay restore timer stop

Upgrade on VLT peer nodes is now complete. Both the nodes actively forward traffic. After upgrade, VLT-Peer1 is the primary node and VLT-Peer2 is the secondary node.

VLT upgrade with minimal loss for upgrades from 10.5.0.5 or earlier to 10.5.1.9 or later releases

NOTE: The default X.509v3 certificates used for VLT convergence expire on July 27, 2021. See "Dell SmartFabric OS10 certificate expiration and recommended action" section in Dell SmartFabric OS10 Installation, Upgrade, and Downgrade Guide for additional information before you start the VLT upgrade procedure.
NOTE: This procedure is applicable only when upgrading to 10.5.1.9 or future releases from 10.5.0.5 or earlier OS10 releases. This VLT upgrade procedure is not applicable when upgrading to 10.5.2.6 or future releases from 10.5.0.6 or later releases. You can directly upgrade VLT nodes from 10.5.0.6 or later release to 10.5.2.6 or future release using the regular VLT upgrade procedure.
  1. Upgrade one VLT peer (VLT-Peer1) running a 10.5.0.x or 10.4.3.x release image to 10.5.0.9 or later, using the standard image upgrade procedure. Reboot the switch with the newly installed image. Wait for VLT-Peer1 to forward traffic after the delay restore timer stops.
  2. Upgrade the other VLT peer (VLT-Peer2), running a 10.5.0.x or 10.4.3.x release image to 10.5.0.9 or later, using the standard image upgrade procedure. Reboot the switch with the newly installed image. Wait for VLT-Peer2 to forward traffic after the delay restore timer stops.
  3. Upgrade one VLT peer (VLT-Peer1) to 10.5.1.9 or later/10.5.2.6 or later using the standard image upgrade procedure. Reboot the switch with the newly installed image. Wait for VLT-Peer1 to forward traffic after the delay restore timer stops.
  4. Upgrade the other VLT peer (VLT-Peer2) to 10.5.1.9 or later/10.5.2.6 or later using the standard image upgrade procedure. Reboot the switch with the newly installed image.

VLT upgrade with minimal loss in a VLT or VXLAN topology when network statements are used to advertise prefixes that are present in both VLT nodes

NOTE: The following procedure is not applicable when upgrading to 10.5.2.0 or future releases from 10.5.1.x releases. You can directly upgrade VLT nodes from 10.5.1.x release to 10.5.2.0 or future release.
NOTE:
  • This section is applicable only if network statements are used under address-family {ipv4|ipv6} unicast to advertise prefixes that are present in both VLT peers.
  • If you have not used network statements and instead used redistribute connected to advertise prefixes, this additional step could be avoided.
  • If the prefix advertised using a network statement is present only on one of the VLT peers, this additional step could be avoided for those prefixes alone.

This section covers the additional steps needed to achieve a VLT upgrade to 10.5.2.6 or later from a 10.5.0.x or 10.4.3.x release with minimal traffic loss in a VLT or VXLAN topology.

NOTE: The steps that are shown below are for IPv4. Follow the same steps for IPv6 where applicable.
  1. Apply a route map to set the origin as IGP for the prefixes on both VLT peers in a VLT domain one after the other.
    NOTE: OS10# configure terminal OS10(config)# route-map set_origin OS10(config-route-map)# set origin igp OS10(config-route-map)# exitThe following procedure is not applicable when upgrading to 10.5.2.6 or future releases from 10.5.1.x releases. You can directly upgrade VLT nodes from 10.5.1.x to 10.5.2.6 or future release. 
    OS10(config)# router bgp <AS-Number>
OS10(config-router-bgp-<AS-Number>)# address-family ipv4 unicast
OS10(configure-router-bgpv4-af)# network <prefix> route-map set_origin
OS10(configure-router-bgpv4-af)# end
OS10#
  2. Follow the VLT min-loss upgrade procedure outlined above.
  3. Remove the route-map on both VLT peers one after the other. 
    OS10(config)# router bgp <AS-Number>
OS10(config-router-bgp-<AS-Number)# address-family ipv4 unicast
OS10(configure-router-bgpv4-af)# no network <prefix> route-map set_origin
OS10(configure-router-bgpv4-af)# network <prefix>
OS10(configure-router-bgpv4-af)#

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\