If you are planning to migrate from 5.2 SP4 or SP5 to 6.1 - let me warn you:
You will need to
MANUALLY uninstall and reinstall
ALL agents.
In my environment I had ECC5.2SP5 server and installed ECC 6.1 on a new server.
I was told I could modify the ctg.ini and MGA.ini files to point to the new ecc_server and actually this works. The problem is that the 'upgrade agent' *doesn't* work. The new ecc_server sees the 5.2SP5 master agent and can even communicate with it, but during the upgrade agent process, the "checking prerequisites" phase hangs.
Engineering is aware of the issue and this is the current response:
"The problems encountered with 6.1 are specific to the new security settings. We unfortunately need to uninstall the previous version agents and install the 6.1 Master agent on each of the targeted hosts."
Yes, this is correct - If one wants to upgrade to CC 6.1, then the only supported method is to go through the official upgrade process (see the Upgrade Guide on Powerlink for more details).
There are issues if one does a fresh installation of a 6.1 infrastructure and then re-points the old 5.2.x/6.0 agents to the new server - this is a result of the new security features in 6.1.
It sounds like you are installing a new infrastructure (a fresh install) and attempting to have the existing agents communicate with that freshly installed infrastructure as opposed to upgrading your existing 5.2 SP5 infrastructure to 6.1 I don't believe SP5 agents against a freshly install 6.1 infrastructure is supported and I don't think it even worked with previous versions, though I could be wrong.
However, you should be able to go through an upgrade (not freshly install a new 6.1 infrastructure) and the 5.2 SP5 agents will continue to work with the upgraded 6.1 infrastructure.
Actually, you are wrong The SP5 agents are supposed to work with this new version of ControlCenter. They did with 6.0.
So it appears I actually have two choices: 1.) Upgrade old_ecc_server from SP5 to 6.0, then migrate the entire 6.0 to the new server hardware, then migrate to 6.1 2.) Uninstall SP5 master agents on 40 hosts; then reinstall them.
The SP5 agents should ]work with 6.1 just like they work with 6.0. The only restriction is that the infrastructure that those agents were associated with has to have been upgraded and not freshly installed.
I believe you can do option 1 but just upgrade old_ecc_server from SP5 to 6.1 in one step and then migrate to the new server hardware following the approved steps for migration which probably involves maintaining the same FQDN, doing database exports and imports, etc.
One option to consider is to take this opportunity to move to running the infrastructure on a VM. That way you can do things like VMotion the VM to different hardware pretty seamlessly. I have not tried it, but you should be able to migrate the existing server to a VM automatically using a VMware supplied utility.
The SP5 agents should ]work with 6.1 just like they work with 6.0. The only restriction is that the infrastructure that those agents were associated with has to have been upgraded and not freshly installed.
You'll actually find that what Julianne has described is correct, issues have been seen with agents from 5.2 being upgraded to 6.1 after the infrastructure has been upgraded to 6.1
In my environment I had ECC5.2SP5 server and installed ECC 6.1 on a new server. I was told I could modify the ctg.ini and MGA.ini files to point to the new ecc_server and actually this works. The problem is that the 'upgrade agent' *doesn't* work. The new ecc_server sees the 5.2SP5 master agent and can't even communicate with it, but during the upgrade agent process, the "checking prerequisites" phase hangs.
I know what your saying, I saw this in our lab environment about 2 weeks ago and pointed it out to some team members who were as shocked as I was. It turns out it was just coming to light at the time.
Wendy indicated that several customers have experienced this issue and engineering was working it. Unfortunately, the security changes in 6.1 appear to eliminate the ability to point to a new ECC server using ctg.ini and mga.ini files.
One great thing about the 6.1 version is the much improved Clariion monitoring .....
It sounds like this is only a problem if a user is installing ECC 6.1 on a new server.
If we upgrade from ECC 5.2 SP5 to ECC 6.1 we should not encounter any issues because the Master Agents will not need to be pointed at a different server.
seamuscoffey
472 Posts
1401
0
Posted September 2nd, 2008 00:00
Yes, this is correct - If one wants to upgrade to CC 6.1, then the only supported method is to go through the official upgrade process (see the Upgrade Guide on Powerlink for more details).
There are issues if one does a fresh installation of a 6.1 infrastructure and then re-points the old 5.2.x/6.0 agents to the new server - this is a result of the new security features in 6.1.
Regards,
Seamus Coffey
EMC Global Services