Unsolved
This post is more than 5 years old
12 Posts
0
1321
February 19th, 2014 11:00
Error when upgrading: "Configuration type 2.08.10.00 does not match 2.."
I'm trying to upgrade our ESRS IP client from 2.08 to 2.26. However, I get this error message and it fails. Why does it say it doesn't match "2"?
Wed Feb 19 14:09:42 2014 INFO ****************************************************
Wed Feb 19 14:09:42 2014 INFO * START OF ESRS-IP UPGRADE *
Wed Feb 19 14:09:42 2014 INFO ****************************************************
Wed Feb 19 14:09:45 2014 INFO User entered 'y'.
Wed Feb 19 14:09:45 2014 INFO User elected to proceed with upgrade.
Wed Feb 19 14:09:45 2014 INFO
Wed Feb 19 14:09:45 2014 INFO ::::::::::::::::::::::::::::::::::::::::::::::::::::
Wed Feb 19 14:09:45 2014 INFO :: READING VALUES FROM THE REGISTRY ::
Wed Feb 19 14:09:45 2014 INFO ::::::::::::::::::::::::::::::::::::::::::::::::::::
Wed Feb 19 14:09:45 2014 INFO Client service name: EMC SRS CLARiiON Management Station Device Client
Wed Feb 19 14:09:45 2014 INFO Watchdog service name: EMC SRS Watchdog
Wed Feb 19 14:09:45 2014 INFO HTTPS Listener service name: ESRSHTTPS
Wed Feb 19 14:09:45 2014 INFO Registry value does not existL ProxyServiceName
Wed Feb 19 14:09:45 2014 ERROR Privoxy service name is null or empty.
Wed Feb 19 14:09:45 2014 INFO Current ESRS-IP Version: 2.08.10.00
Wed Feb 19 14:09:45 2014 INFO Base Path: C:\Program Files\EMC\ESRS IP Client
Wed Feb 19 14:09:45 2014 INFO Configuration Type: CLARiiON-MGMT-DC
Wed Feb 19 14:09:45 2014 INFO Gateway Serial Number: CLARMGMTDC_
Wed Feb 19 14:09:45 2014 INFO Gateway Config Path: C:\Program Files\EMC\ESRS IP Client\Gateway
Wed Feb 19 14:09:45 2014 INFO
Wed Feb 19 14:09:45 2014 INFO ::::::::::::::::::::::::::::::::::::::::::::::::::::
Wed Feb 19 14:09:45 2014 INFO :: CHECK AVAILABLE DISK SPACE ::
Wed Feb 19 14:09:45 2014 INFO ::::::::::::::::::::::::::::::::::::::::::::::::::::
Wed Feb 19 14:09:45 2014 INFO Total free disk space <347527 MB>
Wed Feb 19 14:09:45 2014 INFO Available space check passed.
Wed Feb 19 14:09:45 2014 INFO
Wed Feb 19 14:09:45 2014 INFO ::::::::::::::::::::::::::::::::::::::::::::::::::::
Wed Feb 19 14:09:45 2014 INFO :: CHECK CURRENT CONFIGURATION TYPE ::
Wed Feb 19 14:09:45 2014 INFO ::::::::::::::::::::::::::::::::::::::::::::::::::::
Wed Feb 19 14:09:45 2014 ERROR ESRS-IP configuration type check failed.
Wed Feb 19 14:09:45 2014 ERROR Configuration type 2.08.10.00 does not match 2..
Wed Feb 19 14:09:45 2014 ERROR
Wed Feb 19 14:09:45 2014 ERROR Error code 5.
Wed Feb 19 14:09:45 2014 ERROR Exiting setup.
ryanbrancel1
53 Posts
0
February 19th, 2014 20:00
The ESRS patches are not supported for ESRS IP Client. It is supplied for the full version ESRS as the patch [mostly] provides support for additional products. IP Client provides support for Clariion and VNX arrays, and those are fully supported in the 2.08 version. Also you do benefit from 2.26 updates as the backend EMC servers are updated. Basically there is not a benefit to patching IP Client. Or please advise if there was a feature/fix you desired. Thanks, Ryan.
MaxStr
12 Posts
0
February 20th, 2014 06:00
Ah, I see. I'm trying to understand why we have an ESRS IP client anyway. Doesn't the VNX have this built-in now?
ryanbrancel1
53 Posts
0
February 20th, 2014 08:00
VNX Unified arrays (File & Block) do have ESRS built in to the control station now. This was added with File 7.1 code (and also VNX2 8.1). Since VNX Block does not have a management workstation, it requires a separate physical or virtual workstation to host IP Client. Basically on each control station you have to enable 443 & 8443 outbound only, and also make sure DNS is configured. And then ESRS is enabled in Unisphere.
Otherwise IP Client may be preferred with VNX Unified, especially if there are multiple storage arrays, or the preference is just to open up ports on a single workstation, compared to opening ports on each VNX CS.