Mate CPU error

[TheRealTed]

One of my two old NEC 2400 IMG's (IPS's that were upgraded to IMG status, or so I was told) has started reporting a MATE CPU error. Since the rest of the error report shows that the same CPU is running day after day and not switching between (from memory)LP0-0 and LP0-1.

I am making the assumption that this error is telling me that the automatic switchover from CPU 0 to CPU1 is NOT happening every night as it should.

1) Am I correct on this?
2) If 1=yes, then I believe this means the redundancy of having two CPU's/Memory/Programing of this system is compromised. If so, what do I need to do to prove this and to correct it?

Thanks

 

[belevedere]

You can try the CMOD command. That will manually switch over CPU's, however if the CPU's are not in synch it will not switch over. Before that I would try to do a mem_hdd back up from the operating CPU. If it fails to back up to the redundant CPU then it indicates a problem.

 

[TheRealTed]

>New Post belevedere (Instructor)
>18 Mar 14 13:38
>You can try the CMOD command. That will manually switch over CPU's, however if the CPU's are not in synch it will not switch over. Before that I would try to do a mem_hdd back up >from the operating CPU. If it fails to back up to the redundant CPU then it indicates a problem.

Thanks, I'll give this a try (CMOD) tomorrow and see what happens.

Ted

 

[EXC300]

You can use cmd DHDF and check the date of the DM and CF files to see if they have the same time stamp in both CPU's. If the cpu's have flash drives it's possible a back up to laptop was done and CFCS wasn't executed to reconnect the flash drive to the CPU. if there are red lights on the CPU you probably have a hardware issue.

 

[TheRealTed]

>belevedere (Instructor)
>18 Mar 14 13:38
>You can try the CMOD command. That will manually switch over CPU's, however if the CPU's are not in synch it will not switch over. Before that I would try to do a mem_hdd back up >from the operating CPU. If it fails to back up to the redundant CPU then it indicates a problem.

I've been busy putting out other fires and finely got back to this one. mem_hdd is a no go on this (these) systems. NEC 2400IMS (Upgraded to IMG's or so I've been told). Backup is either DMBU (Data Memory BackUP ?) or MMBU (Main Memory BackUp ?). I've run both to floppy (on both systems) so I feel a little better.

What are the risks in attempting a CMOD on this system?

1) It works and all is Unicorns and Rainbows from here on?
2) It works and I need to run a CMOD every day/week/month to switch CPU's?
3) It does not work and I'm still right where I started and need to start looking for a new (good/clean) CPU and memory for this system and a tech who knows how to install them.
4) All life as I know it stopping instantaneously and every molecule in my body exploding at the speed of light?
5) The BPX melts and my bosses happily run out and buy a new one?

Thoughts?

 

[belevedere]

If the DMBU ran successfully to both CPU's, then they should be in good shape. A CMOD will attempt to switch over from the active CPU to the standby CPU. If the system detects a problem with the standby CPU it will not switch over. In any case, this should be done after hours just in case.
If it switches over successfully and testing reveals no issues, then you can look at CMD ASYD, sys 1, index's 88,89,90 for the CPU automatic switch over times.
If there is an issue with the standby CPU then there are some things that can be done to bring it back to life.
Obviously a CPU reset,
A CPU default, once it's back up, a back up to HDD should move the database in from the on line CPU.
A CPU reload. This requires they you have all of the disks and config disk available for reload.