26 Posts
0
6216
RP4VM 5.1.1.15 upgrade to 5.2
Hi,
We are in the process of upgrading a eng test environment, but the upgrade is failing at 12%
Migration to ip communication is completed, system check, upgrade pre-req passes,
-the change version requirements section, i've downloaded the a-cca.xml file manually..
i have two questions - -
The Modification file, does this require changes from EMC support ? or is it just a check ..
Currently it's not a registered system, does it have to be registered for the upgrade to complete ?
- also can i tail a specific log file during the upgrade to find the issue...
Cheer
esxi & vc = 6.5
Idan
675 Posts
0
August 29th, 2018 05:00
The mod file looks OK, while 5.2P1
Fixes some upgrade-related issues, this can be a browser refresh issue during the upgrade process.
Did you raise a SR with support ? We need to look at the logs.
Regards,
Idan
Idan
675 Posts
0
August 29th, 2018 04:00
Hi there,
Modifications file needs to be checked by support to make sure that there are no non-standard tweaks applied to this cluster.
Also, are you upgrading to 5.2P1 ?
Regards,
Idan
DDave447
26 Posts
0
August 29th, 2018 05:00
Hi,
Yes, going from 5.1.SP1.P5(d.246) to 5.2P1 (rel5.2.P1_a.362_release_emc_md5_1bb251ae2f6a2c5f5efb57a68b718b61_RP4VMs)
and nothing non standard with the deployment
example of mod file....
{
"1": {
"modifiedTweaks": [
{
"tweakName": "t_defaultNetworkSecurityLevel",
"value": "SECURITY_LEVEL_NON_SECURE",
"modifierName": "Cluster Logic(5.1)"
},
{
"tweakName": "t_isIPSplitterDefault",
"value": "false",
"modifierName": "Cluster Logic(5.1)"
},
{
"tweakName": "t_isIPSplitterDefault",
"value": "true",
"modifierName": "Cluster Logic(5.1)"
},
{
"tweakName": "t_shouldEnableIOF",
"value": "false",
"modifierName": "Cluster Logic(5.1)"
}
],
"ranSignedScripts": []
},
"2": {
"modifiedTweaks": [
{
"tweakName": "t_defaultNetworkSecurityLevel",
"value": "SECURITY_LEVEL_NON_SECURE",
"modifierName": "Cluster Logic(5.1)"
},
{
"tweakName": "t_isIPSplitterDefault",
"value": "false",
"modifierName": "Cluster Logic(5.1)"
},
{
"tweakName": "t_isIPSplitterDefault",
"value": "true",
"modifierName": "Cluster Logic(5.1)"
},
{
"tweakName": "t_shouldEnableIOF",
"value": "false",
"modifierName": "Cluster Logic(5.1)"
}
],
"ranSignedScripts": []
}
}
Cheers
Dave
DDave447
26 Posts
0
August 29th, 2018 06:00
Cheers Idan...
Changed browser (IE) and the install has moved it on ..
so i will monitor for now..is there any log i could tail for some more details ?
DDave447
26 Posts
0
August 29th, 2018 08:00
cluster upgrade completed, now for the remote cluster
DDave447
26 Posts
0
September 4th, 2018 03:00
The remote cluster upgrade experienced some similar issues as above,
I got to the point where one node updated and the second node failed, so i mounted the iso via the boxmgmt cli and complete the auto upgrade of the node...
my understanding was that it had completed, and rejoined the cluster as the https://192.168.1.66/WDM/#/welcome page show both nodes upgraded, active and connected to the vc.
the dashboard, components section gave a slightly different status..
The second node looks to be stuck in maintenance mode, on closer inspection the second rpa is removed for upgrade..
using the finish_maintenance_mode fails with not all boxes are in the cluster, and resume_rpa_from_maintanence is unavailable....
vrl2-vrpa-c1> get_versions
Versions:
vrl-vrpa-c1: 5.2.P1(a.362)
vrl2-vrpa-c1: 5.2.P1(a.362)
vrl2-vrpa-c1>
vrl2-vrpa-c1> get_system_settings
Clusters:
vrl2-vrpa-c1:
Software serial ID: 2040548EID706689932000
Site ID: 4090926194959114923
Maintenance Status: MAJOR UPGRADE
Cluster management IPv4: 192.168.1.66
Cluster management IP available: YES
Repository volume:
Type: OTHER
UID: 60,00,c2,97,df,7a,58,cb,52,2b,a2,bc,7b,81,88,53
Vendor: EMC
Product: RP_VStorage
Size: 5.72 GB
Name: RPVS_Lun00001
Array Serial: 0012486212ab7d504b0dd3
RPA To volume paths map: None
vCenter Server settings:
vCenter Servers:
192.168.1.19:
IP address: 192.168.1.19
User name: ehc_sysadmin@vlab.local
Port: 443
Certificate: YES
Enabled storage awareness: NO
Communication Mode: IP
System problems:
WARNING: Cluster vrl2-vrpa-c1 is currently in Maintenance mode. It is recommended to postpone any new configurations until Cluster vrl2-vrpa-c1 maintenance is completed.
WARNING: It is recommended that you change the default password for the admin user: Log in to the CLI as user admin, and run the set_password command.
Clusters problems: None
WANs problems: OK
Groups problems: OK
vrl2-vrpa-c1> get_rpa_states
Enter cluster name, or press 'ENTER' for all clusters: vrl2-vrpa-c1
Cluster:
vrl2-vrpa-c1:
RPA:
RPA 1:
Status: OK
Repository volume status: OK
Remote connections: OK
Network Interfaces:
LAN (eth1):
Status: OK
Speed: Unknown
Local connections (IPv4): OK
Local connections (IPv6):
RPA 1: N/A
RPA 2: N/A
WAN (eth0):
Status: OK
Speed: Unknown
Local connections (IPv4): OK
Local connections (IPv6):
RPA 1: N/A
RPA 2: N/A
FC Speed: N/A
iSCSI Speed: Unknown
Data Link:N/A
Vendor: VMware, Inc.
Hardware Serial ID: 4216c8076fdac97fbf894aae943f67
Volume Connections:
[AutoCGPriority02, vRA-copy, CG_RSET_rp.vra73-02.copy.shadow_0_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_rp.vra73-02.copy.shadow_1_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_rp.vra73-02.copy.shadow_2_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_rp.vra73-02.copy.shadow_3_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_vra73-01.copy_0_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_vra73-01.copy_1_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_vra73-01.copy_2_0_scsi]: ERROR
[AutoCGPriority02, vRA-copy, CG_RSET_vra73-01.copy_3_0_scsi]: ERROR
[TenantCG01, Debian-copy, CG_RSET_Deb1.copy_0_0_scsi]: ERROR
Hardware Platform: VMware, Inc. VMware Virtual Platform vGEN
RPA 2:
Status: REMOVED FOR UPGRADE
Repository volume status: OK
Remote connections: OK
Network Interfaces:
LAN (eth1):
Status: OK
Speed: Unknown
Local connections (IPv4): OK
Local connections (IPv6):
RPA 1: N/A
RPA 2: N/A
WAN (eth0):
Status: OK
Speed: Unknown
Local connections (IPv4): OK
Local connections (IPv6):
RPA 1: N/A
RPA 2: N/A
FC Speed: N/A
iSCSI Speed: Unknown
Data Link:N/A
Vendor: VMware, Inc.
Hardware Serial ID: 4216c6763c92f3afd8fd2178cea2d1
Volume Connections:
[AutoCGPriority01, SQL-copy, CG_RSET_Auto-PSC.copy.1_0_0_scsi]: ERROR
[AutoCGPriority01, SQL-copy, CG_RSET_Auto-PSC.copy.1_10_0_scsi]: ERROR
[AutoCGPriority01, SQL-copy, CG_RSET_Auto-PSC.copy.1_11_0_scsi]: ERROR
[AutoCGPriority01, SQL-copy, CG_RSET_Auto-PSC.copy.1_12_0_scsi]: ERROR
[AutoCGPriority01, SQL-copy, CG_RSET_Auto-PSC.copy.1_1_0_scsi]: ERROR
Hardware Platform: VMware, Inc. VMware Virtual Platform vGEN
vrl2-vrpa-c1>
vrl2-vrpa-c1> finish_maintenance_mode
Enter cluster name, or press 'ENTER' for all clusters
Error: Maintainance mode can't be finished when not all boxes are in cluster. ( Exit maintanance mode with removed boxes )
Found the below command from https://support.emc.com/kb/521279 but it seems it's not available through the admin account, is there another account we should use?
vrl2-vrpa-c1> resume_rpa_from_maintenance
Error: Unknown command: resume_rpa_from_maintenance
Is there another option to resume/complete the maintenance mode ?
Cheers
Idan
675 Posts
0
September 4th, 2018 03:00
Yes Dave but it has to be executed by support, we would need to determine why the upgrade failed on RPA2.
Regards,
Idan