How to determine which one is emgmt-0 vs emgmt-1

EMC engineering is currently investigating this problem. A permanent fix is still in progress.

The workaround is to failover u4v from mgmt-1 to mgmt-0:

• Log into vapp manager on MGMT-1, and reboot the appliance from the top right corner gear wheel. This should fail over Unisphere to MGMT-0.
• Please wait 3-5 minutes and log into U4V and run a spa backup. This workaround should fix the issue with retention and spa backups failing.
• Note if the restart appliance doesn’t fail it over (it will not failover if the ping from the other guest is within the set timeout), contact the PSE lab to shut down the mgmt guest via symmwin.

Ref#

484620 : Embedded VMAX3 Unisphere for VMAX spam error every hour : Retention Failed https://support.emc.com/kb/484620

Hi Wallace ,USAK*

We've been seing these on our older hybrid VMAX40k since 25th October...i'm sure not precipitated by any code upgrade, we don't have any onboard management on our older 40ks ..(although we do have newer 450AFs but not getting simmilar messages).

5876.288.195

We control our 40ks via symapi hosts...hence not familiar with any vapp manager on MGMT-0 or 1, in fact do these refer to vMAx3 only  onboard mgmt tools). We chose not to set these up on our new 450AFs.

So doesn't  look like workaround  appropriate.

Are these messages benign ? Aggregation/Retention failed to run on xxxx within last 24 hours.

Interested to hear of USAK's experience since August ... John

See the same thing. Can someone please address this issue and a workaround for the older VMAX 40K's?

Thanks!
Jo

check this one: https://emcservice.force.com/CustomersPartners/kA2j0000000RHxgCAG similar error caused by a WIndows 2008 bug.