How is it faulty ?
What is on the screen

It is booting and booting again

And if you STA-HISTA:SEARCH; what do you get

I will visit the site tomorrow and update you.

<sta-hista;
STA-HISTA;
H500: AMO HISTA STARTED
+---------+-----+-----------+--------+-------------------------+
I ALARM I ABS I ALARM I ALARM I ALARM NAME I
I GROUP I I NUMBER I PRIO I I
+---------+-----+-----------+--------+-------------------------+
I CENTRAL I A1 I 028 I MAJOR I SYSTEM_TIME_FAILURE I
+---------+-----+-----------+--------+-------------------------+
I CENTRAL I BPA I 005 I MINOR I CC_RESTARTS I
+---------+-----+-----------+--------+-------------------------+
I CENTRAL I BPA I 006 I MINOR I CC_STBY_FAILURE I
+---------+-----+-----------+--------+-------------------------+
I CENTRAL I BPA I 005 I MAJOR I CC_RESTARTS I
+---------+-----+-----------+--------+-------------------------+

AMO-HISTA-111 READ HTS HISTORY FILE
START COMPLETED;

Today I visited the site. see above the result for HISTA command.

What is the date time ? (DIS-DATE;)

Can you go into the PORTAL and see what is happening there.

sbcsu asked for sta-hista:search; which gives you the last 2 hours of messages, but you did sta-hista; which only lists the alarms table. Alarms table shows a CC is restarting but you'd already said that.

Cannot tell from your message whether the CCB VM is restarting, or the whole platform for node 2 is restarting. If you login to the linux, "uptime" will tell you. If the uptime is a long time but you know it restarted a few hours ago, then it looks like you have an RMX problem which is maybe a little less serious than a HW problem on the processor.

But in either case, remedial action is the same. If corosync, atlans connections are all OK and processor A can reach processor B on both networks, then node 2 should be reinstalled.