Start a Conversation

Unsolved

This post is more than 5 years old

822

May 28th, 2008 07:00

step by step 5.2SP4 to 6.0 host agent upgrade

Assuming primus emc157387 is explaining the following :
------------------------------------------------- 8< -------------------------------------------------
Backward compatibility means that the 5.2.x agents will continue to function as designed within the 6.0 infrastructure (however, you must update the 5.2.x agents to 6.0 to make use of new 6.0 functionality). ControlCenter 6.0 provides agent backward compatibility to ControlCenter 5.2 SP3, SP4, and SP5 agents except as noted in this section and the previous section listing agents that are no longer supported.

Note: The ControlCenter 6.0 infrastructure is backward-compatible with 5.2 SP3 agents and higher. Older versions of ControlCenter agents are not supported.

The following ControlCenter 5.2 SP3, SP4, or SP5 agents are not backwards compatible with the 6.0 infrastructure:
· Storage Agent for HDS
· FCC Agent
------------------------------------------------- 8< -------------------------------------------------

i have planned my ~750 hosts ECC6 migration by steps :

step 1 : stop 5.2 agents, modify "server host" parameter ctg.ini + mga.ini to refer the new 6.0 ecc server, start 5.2SP4 agents
step 2 : upgrade a little number of servers master + hosts agents to 6.0 to see if everything is ok during 1 week
step 3 : upgrade another set of servers and wait 1 week
...
...

=> my problem is that i ran into tests and it seems that a 5.2SP4 host + master agent is not manageable via ECC6 until agents are upgraded to 6.0 !
with 5.2SP4 agents, host is not discovered, masking isn't available, "relationship with" function is unavailable, install agent require 6.0 upgrade first...

One the one hand EMC is writing that "The ControlCenter 6.0 infrastructure is backward-compatible with 5.2 SP3 agents and higher" and on the other hand facts show us that it's not true.

any idea to avoid a "one shot" massive 5.2SP4 to 6.0 agents upgrade ?

2 Intern

 • 

5.7K Posts

May 29th, 2008 00:00

You mention you are going to change a parameter in some ini files to point to the new ECC6 server. Why not keep the old ECC and the new ECC running together and manage "old" hosts in ECC5 and the hosts with the new agents in the new ECC6 ? This means you'd have 2 ECC's, but it also provides you time to migrate to new agents in your pace.

1 Rookie

 • 

32 Posts

May 29th, 2008 09:00

"my problem is that i ran into tests and it seems that a 5.2SP4 host + master agent is not manageable via ECC6 until agents are upgraded to 6.0 !
with 5.2SP4 agents, host is not discovered, masking isn't available, "relationship with" function is unavailable, install agent require 6.0 upgrade first..."

I would like to know how u r able to upgrade the agents, without the host being discovered???
AFAIK the host agents are upgradable only through ECC.
You should be able to discover the new hosts once you change the "server host" parameter ctg.ini + mga.ini to refer the new 6.0 ecc server and start 5.2SP4 agents.

Thanks
Karan

4 Posts

May 30th, 2008 00:00

I'm afraid i will be constrained to use this kind of workaround if the 5.2SP4 agents are not backward compatible with 6.0 infrastructure. The only drawback is that we have to open 2 consoles simultaneously during the migration schedule. Nevertheless, it's a good idea. :-)

6 Posts

June 3rd, 2008 08:00

For all functions to work as described the agents are backwards compatible (5.2.4 ) considering the repository is migrated 5.2.4/5 to 6.0. preserving the name space and uid.
Agents can be installed at lower packages 5.2.4 etc. A push of the agent isn't required.
No Events found!

Top