Unsolved
This post is more than 5 years old
18 Posts
0
805
Upgrade from 2.0.7120 mis-match SDC 2.0.7058
Why is there a version miss match? Note the drv_cfg is 7120 and the sdc is 7058. This is the latest I pulled from the web a couple of days ago.
I completed an upgrade but a few sdc are complaining of not being upgraded.....Everything looks solid except this.
Everything is running 7120 except my SDC are at 7058.
ScaleIO-10-99-6-100:~ # scli --mdm_ip 10.99.6.100,10.99.6.101 --query_upgrade
Upgrade State: No Upgrade
List of Slave MDMs not yet upgraded:
0 Slave MDMs need to be upgraded in total
List of Tie-Breakers not yet upgraded:
0 Tie-Breakers need to be upgraded in total
List of SDSs not yet upgraded:
Protection Domain 69a91a9100000000 Name: pd1
0 SDSs need to be upgraded in this Protection Domain
0 SDSs need to be upgraded in total
List of SDCs not yet upgraded:
SDC ID: 96ad47e200000003 Name: ESX-10.99.6.1 IP: 10.99.6.1 State: Connected GUID: 7BCB2FDA-69E3-4AB9-B2B1-7F096374F6B1 Version: 2.0.7058
Read bandwidth: 0 IOPS 0 Bytes per-second
Write bandwidth: 7 IOPS 7.0 KB (7168 Bytes) per-second
SDC ID: 96ad47e100000002 Name: ESX-10.99.6.3 IP: 10.99.6.3 State: Connected GUID: DC2E0266-58EC-4222-B3C7-62B83DD58F1C Version: 2.0.7058
Read bandwidth: 0 IOPS 0 Bytes per-second
Write bandwidth: 7 IOPS 7.0 KB (7168 Bytes) per-second
SDC ID: 96ad47e000000001 Name: ESX-10.99.6.7 IP: 10.99.6.7 State: Connected GUID: 23703C29-C944-4CEF-9499-0BC68A4F14E6 Version: 2.0.7058
Read bandwidth: 0 IOPS 0 Bytes per-second
Write bandwidth: 7 IOPS 7.0 KB (7168 Bytes) per-second
SDC ID: 96ad47df00000000 Name: ESX-10.99.6.5 IP: 10.99.6.5 State: Connected GUID: 92F14357-4A39-4341-A4BE-7021E9E6B2F5 Version: 2.0.7058
Read bandwidth: 1 IOPS 1.0 KB (1024 Bytes) per-second
Write bandwidth: 7 IOPS 7.0 KB (7168 Bytes) per-second
4 SDCs need to be upgraded in total
ScaleIO-10-99-6-100:~ #
c0redump
68 Posts
0
September 30th, 2016 05:00
Hello Roger00,
are you performing the upgrade from the Installation Manager or installing the SDC package manually on every node?
I had some problem upgrading the SDC component from the Installation Manager, for the SDC component I placed hosts in turn in maintenance mode and installed new SDC package version manually (from SSH console) to get it upgraded. I didn't find solution to upgrade SDC component from Installation Manager (gateway).
Davide
pawelw1
306 Posts
0
October 6th, 2016 01:00
Hi Davide, Roger,
In ESXi environment you upgrade SDC through the WebPlugin rather than via Installation Manager - just install the new plugin and deploy new OVA, then right click on the SDC and select "Upgrade" - when it's done, click Finish and reboot the ESX host (one at a time).
@Roger - I could see a similar behavior in the lab, we will discuss it internally and let you know whether it's a bug and if anything else that 'query_upgrade' output is actually affected.
Many thanks,
Pawel
c0redump
68 Posts
1
October 6th, 2016 06:00
Hello Pawel,
thanks for the info, I didn't tried to upgrade the SDC component using web plugin, the next upgrade I will try this way. With last upgrade I solved this issue working with VIB packages from ESXi console.
Thanks again for the info!
Davide
pawelw1
306 Posts
0
October 6th, 2016 23:00
Hi Roger,
I think it's the same issue as the one described in below KB article:
https://support.emc.com/kb/481184
even if it wasn't an upgrade from 1.32 to 2.0, it seems that 2.0.0.x versions still have the same flaw, so we might update the KB.
Anyway, as the KB states, it's only a cosmetic issue and it isn't affecting anything, so you can just ignore it.
Cheers,
Pawel