We are going to do the restarting of the first ACE card.
All the ACE contexts which have redundancy were already switched on the second card.
The customers who don't have this fault tolerance will have an interruption during the restarting.
Update(s):
Date: 2012-01-27 16:48:49 UTC Due to connection difficulties on the ACE-s1, we decided to forward a replacement maintenance of the planned RAM.
At the end of the maintenance, when all the contexts were on ACE-s2, we started to face the same connection problems.
After restarting of ACE-s1 and reswitch of the contexts from s2 to s1, the problem continued.
Finally, we identified that one of the last contexts (clients) installed on the ACE seemed to be at the origin of the problem.
We have currently isolated on ACE-s2, in order to guarantee the service quality for all the other contexts on ACE-s1.
We have to understand now what happened with this client.
Date: 2012-01-27 15:48:05 UTC We are replacing the ACE Ram.