Master Agent issues in 6.1

Hi,

I recommend opening a SR for this issue. A Support Engineer will probably need to WebEx into your environment in order to determine the root cause of the issue.

Obviously, if the Console states that the Master Agent is 'Active' then there should be a mstragent.exe process running locally. You will not be able to delete the Host object if this process is still running. I'm guessing though that this is something that you've already checked.

We have seen a few agent issues at 6.1 so definitely go ahead and open a SR...

Regards,
Séamus Coffey
EMC Global Services

Hi,

There is an open engineering ticket for this issue. Just to confirm even you have similar issue, can you check under %ECC_INSATLL_ROOT%\exec\MGA610, is there is mstragent_FATAL.LOG is present. If yes, you have to wait till we found an update from Engineering.

Regards
Nimai Sood
EMC Global Services

Message was edited by:
Seamus Coffey

Yes I do have the log file on the ECC server, but not on the host. I will begin the process of opening the SR. When I get an answer I will update the forum. Is there a Alert Rule to monitor the Master Agent on the servers?

Yes, the Administration > ServerAlerts > ServerAlert > Security > System > Agent Inactive alert will fire if a Master Agent goes inactive (if enabled).

Regards,
Séamus Coffey
EMC Global Services

We have had a similar issue a few times now. I've got two servers that the Server Support team decommissioned (the servers are GONE) but I can't get rid of the objects in ECC 6.1 because they still show an active agent.

I've also run into issues where I couldn't perform an action (like deleting an empty fabric) because agents were still showing as running (in this case the FCC agent). These agents were definitely NOT running at the time... I even checked for the processes.

We have been waiting for the first round of patches in hopes that some of these issues would be addressed.

Hi Doug,

The Administration > ServerAlerts > ServerAlert > Security > System > Agent Inactive cannot be fine tuned by selecting/deselecting individual servers. It's basically an 'All or Nothing' alert definition. It's worth submitting an enhancement request in Powerlink if this is something you would like to see in a future ControlCenter version.

Regards,
Séamus Coffey
EMC Global Services

A related follow-up question regarding Agent Status alerts...

Is there any known way to enable this alert for ONLY selected hosts? We'd like to enable this to monitor our Infrastructure and dedicated agent platforms, but it gets lost in the flood of hundreds of other Agent transition messages. The only recourse that come up with was to turn them all off.

Thanks,
--Doug Cook

Even i faced a similiar problem while removing hosts from ECC 6.0, the Master Agent cannot be stopped from ECC, so what i tried was ..i uninstalled master agent from command line , and uninstalled host agent from ECC 6.0 console. Then i could remove that host from ECC.

Here is an update on the original question:

Since then I have disabled SSL in ECC, this seemed to allow me to delete the servers from the console, but caused much larger issues with the Symmetrix Agent. The alert for the inactive agent was working. Since we wanted to see if it was an install issue, I reinstalled ECC 6.1 on a new server. Removed all agents and reinstalled. Amazingly enough, same issues arise. I have opened a case with EMC and am on my 3rd engineer. The discovery of the Windows hosts is setup but running on only a few servers for some reason. (This occurs even when I start the DCP myself).

The error "Communication between the master agent and server could not be establish" - seems to be when the server is rebooted. The master agent hangs in the starting state. Only on a few servers though.

I will let everyone know what occurs when my webex session is finished.