Reminder: The Next HA Rollover is Coming May 14th – We Need You to Perform a Connectivity Test!

Twice each year, CU*Answers tests our ability to redirect CU*BASE core-processing from our production data center in Kentwood, MI to our high-availability (HA) data center in Yankton, SD.  The next HA rollover is scheduled for Sunday, May 14^th.

The rollover is scheduled to begin at 2:00 AM ET on Sunday, May 14^th with the rollback planned for 2:00 AM ET on Sunday, May 21^st.  There will be brief service interruptions during both the rollover and rollback processes.  Additional details will be included in future announcements as we get closer to the date.

*Please note: CU*BASE Training Edition (CTE) services are not available during the rollover period while operating from the HA data center.

As a reminder, we strongly encourage that someone at each branch tests connectivity to the HA data center from a GOLD workstation prior to the rollover event.  Additionally, if your credit union has any employees who are working remotely, we recommend asking them to perform the connectivity test as well.  Use the links below to complete one or both of the connectivity tests.

• Test connectivity using the TELNET command by following the instructions in this AnswerBook item: https://kb.cuanswers.com/cuanswers/ext/kbdetail.aspx?kbid=3606
• Test connectivity using the PING command by following the instructions in this AnswerBook item: https://kb.cuanswers.com/cuanswers/consumer/kbdetail.asp?kbid=1930

Please contact the CU*Answers Network Services Help Desk at helpdesk@cuanswers.com if the tests above are unsuccessful.  Failure to complete the tests may result in CU*BASE/GOLD connectivity issues on the morning following the May 14^th rollover event.

There’s still time to register for our “Unpacking the HA Rollover” webinar, scheduled for May 18^th at 3:30 PM ET.  If you are interested in a deeper dive into the rollover process, you can sign up for this 30-minute webinar via our Education Calendar or by contacting a member of the Business Continuity Team.