Users Guide
Table Of Contents
- Dell EMC SmartFabric OS10 Installation, Upgrade, and Downgrade Guide
- About this guide
- Installing SmartFabric OS10
- Preparing for an upgrade
- Supported upgrade paths—Full Switch mode deployments
- Supported upgrade paths—SFS mode in Dell EMC VxRail deployments
- Supported upgrade paths—SFS mode in Dell EMC PowerEdge MX deployments
- Upgrading other related hardware and software components
- Prerequisites for SmartFabric OS10 deployments
- Prerequisites for solution deployments
- Upgrading OS10 software
- Downgrading OS10 software
- Frequently asked questions
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.1 or later releases
NOTE: This procedure is applicable only when upgrading to 10.5.1.x or future releases from 10.5.0.5 or earlier OS10 releases.
The VLT upgrade procedure is not applicable when upgrading to 10.5.2.0 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.0 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.6, 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.6, 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.2.0 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.2.0 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 if
network statements are used to advertise BGP prefixes
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 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, you
avoid this additional step.
● If the prefix advertised using a network statement is present only on one of the VLT peers, you avoid this additional
step for those prefixes alone.
This section covers the additional steps needed to achieve a VLT upgrade to 10.5.2.0 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 in the following example 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.
OS10# configure terminal
OS10(config)# route-map set_origin
OS10(config-route-map)# set origin igp
OS10(config-route-map)# exit
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
26
Upgrading OS10 software