Unsolved
This post is more than 5 years old
10 Posts
0
5066
VNX5300 upgrade stuck on CS1 upgrade....
I attemped to upgrade my VNX5300 (7.1.71-1/5.32.0.206-->7.1.72-1/5.32.0.207) by using USM. Things looked OK until started CS1 upgrade. Now the upgrade is stuck on CS1 upgrade. Does anyone have any idea? Thanks in advance.
Here is the details:
Now when i log in, i will got following warning.
Warning!!upgrade is in progress from 7.1.71-1 to 7.1.72-1
Warning!!Please log off IMMEDIATELY if you are not performing the operation on the Celerra
Looks i have blades upgraded, i ignored the warning and upgraded the SPs without issue. But i still see above message when i log in.
From upgrade log, i got following. (confirmed i have enough space on CS1 !)
...... unpack package on CS1...
.......
22:15 Checking CS1 Upgrade status
2013-12-09 22:15:21 -
CS1 Upgrade in-progress...
2013-12-09 22:15:27 -
22:15:18 [ 47/52 ] build administrator profile 1 second
2013-12-09 22:15:42 -
22:15 Checking CS1 Upgrade status
22:15 CS1 Upgrade IM status: Error establishing connection: Connection refused
2013-12-09 22:16:12 -
22:16 CS1 Upgrade IM status: Error establishing connection: Connection refused
2013-12-09 22:16:48 -
CS1 Upgrade starting...this takes a few minutes.
2013-12-09 22:18:03 -
22:18 Checking CS1 Upgrade status
2013-12-09 22:18:09 -
CS1 Upgrade starting...this takes a few minutes.
.....
Vipin VK
812 Posts
0
December 11th, 2013 19:00
Consider moving this discussion to VNX Support Forum ( Select Move from Actions).
Have you tried closing the window and resuming the upgrade ?
felixzhou
10 Posts
1
December 12th, 2013 06:00
Yes, since the current upgrade is still in process. The resume is being blocked.
thanks
felixzhou
10 Posts
0
December 12th, 2013 12:00
After rebooted CS1, now i am able to resume the upgrade and complete both file and block upgrade. when i loged in this time, i didn't see the message "upgrade is in process" any more.
For some reason, the Unishpere is still showing old file version but not from #nas_version. Any idea?
Ybfx
24 Posts
0
December 13th, 2013 01:00
please try to restart the management server of both SPs...and if still the same issue check emc299249...
felixzhou
10 Posts
0
December 13th, 2013 06:00
Thanks for reply.
Unfortunately, it didn’t fix the issue by either restarting SP management server or reboot CS.
felixzhou
10 Posts
0
December 13th, 2013 09:00
I did get correct numbers for block from both SPs and files from nas_version.
The only issue is the Unishpere didn’t get right version for file.
Ybfx
24 Posts
1
December 13th, 2013 09:00
$ nas_storage -info id=1 | grep -i microcode
microcode_version = 05.31.000.5.509 <<< SP A is showing the wrong OE version. The getagent command will confirm code level is correct on the SP.
microcode_version = 05.31.000.5.720
$ nas_storage -sync -all
$ nas_storage -check -all
$ nas_storage -failback id=1
$ nas_storage -info id=1 | grep -i microcode
microcode_version = 05.31.000.5.720
microcode_version = 05.31.000.5.720
christopher_ime
2K Posts
0
December 14th, 2013 11:00
While I'll assume in the meantime you also have an SR open with support to review, do you mind providing a screenshot(s) of what you see in Unisphere and also could you provide the output of the following:
(I'll assume CS0 is currently the primary Control Station)
1) CS0
nas_version
2) CS1
/nasmcd/bin/nas_version
- Would of course also work on the primary CS
3) CS0 (version of data movers)
server_version ALL
Also, I'll assume you are pointing your browser to the primary Control Station, could you instead point your browser to the IP of one of the SP's and log into Unisphere? Do you also see the same version of VNX OE for File of the Control Station(s) being reported in the GUI?
felixzhou
10 Posts
0
December 14th, 2013 20:00
$ nas_version
7.1.72-1
$
$ /nasmcd/bin/nas_version
7.1.72-1
$
$ server_version ALL
server_2 : Product: EMC File Server Version: T7.1.72.1
server_3 : Product: EMC File Server Version: T7.1.72.1
$
If I pointed Unishpere to SP’s, I got same old version information.
felixzhou
10 Posts
0
December 14th, 2013 21:00
christopher_ime
2K Posts
0
December 14th, 2013 21:00
Screenshot?
christopher_ime
2K Posts
0
December 17th, 2013 13:00
The screenshot didn't get posted.
christopher_ime
2K Posts
0
December 17th, 2013 14:00
So maybe to minimize the back-and-forth, the reasoning behind my request for a screenshot was to see if the panel had an "Invalidate cache and refresh" option. It is represented by a small wrench icon in the upper right corner of the *sub*-panel. From everything you responded with (thank you btw), it suggests this is a display issue.
For example, if you are seeing incorrect text in the "Version" column of the Inventory (File) view, in the upper-right on the panel you can select "Invalidate cache and refresh" (via the wrench icon). Not all views have it, just those where the developers acknowledge can cache and need a small kick. Just as one example where I'm wondering you may be seeing this (and has the option to manually invalidate cache) is via the following breadcrumb trail within Unisphere:
System > Hardware > Hardware for File > Inventory