ECC 5.2 SP5 to ECC 6.1 Upgrade

I am also doing this, has anyone replied yet? could you please share the documents and the procedures.

Hi,

Just a few things come quickly to mind

1) Apply Patch 4013 before upgrading from 5.2.x to 6.1. This should up any inconsistencies in the database

2) Required DLLs missing or conflicting with another application
The ControlCenter Repository upgrade requires the use of two Secure Sockets Layer (SSL) related DLLs libeay32.dll and ssleay32.dll. These DLLs are shipped with the ControlCenter 6.1 upgrade software. However, other applications can also use these DLLs, and this can conflict with the ControlCenter upgrade. Other applications that use these DLLs can put their Application PATHS in the system %PATH% environment variable. If the other application's path is before the ControlCenter entry for the RAMB_Scripts folder (where the libeay32.dll and ssleay32.dll DLLs are shipped to), then the ControlCenter upgrade EXE will choose the other application's DLLs instead. The versions of the DLLs used by the other application are usually different from the ones shipped with ControlCenter, so it halts the ControlCenter upgrade .

Fix: Verify the current system %PATH% variable and add the Path to Ramb_scripts if required. See emc197536 for details on this issue and the complete documented workaround

Apart from that, just follow the Planning & Installation Guide and the Upgrade Guide.

Best of luck!

Regards,
Séamus Coffey
EMC Global Services

As I said, I have patched till 4433 and the installation was completed sucessfully, although I still see the old patch ?
I did restart of the ECC srevice as mentioned in the 4433 read me file and even restarted the ECC server itself.. After restart all the services are running fine only, but still with the old patch level.
any idea?

Seamus Coffey, thanks for the reply. I checked on the 4013 patch that you recommending applying. It states it's for a 5.2 to 6.0 upgrade. I'm doing a 5.2 to 6.1. Please advise if this patch is still needed. Also, I did a 5.2 to 6.1 trial run in my test lab. Everything went fine, except, when I delete a zone from ECC 6.1, and activate the zone set, the zone in Connectrix manager (9.1), is deactivated, but it's not removed from the zone set, any thoughts on this?

Thanks.

Patch 4013 can be applied prior to a 6.1 upgrade also - there's no harm in running it. It's a little DB script which will check for DB inconsistencies.

I haven't come across the issue you mention in Connectrix Manager - it might be something you want to get checked out by Support (via a SR) before you pull the trigger on the 6.1 production upgrade.


Regards,
Séamus