tim_abney

I actually have the same problem on an 81C we have run all the diags and had Nortel involved. No one can see a "real problem" so we are going to force a swap tomorrow morning and see if it clears the problem. I have forced swaps before with no problem but, it's alays an un-easy situation.

Did you test the stand-by cpu?

John_In_Dakota

could be corrupted data.
could be a bad CPU.

erhatch

Please let me know how the forced swap goes. and I will test the offline cpu.

thanks

HCJes

We would be able to help you best if you posted your stat information from LD 137.

LD 137
. STAT

Your system will show you the status of your cores. One should be active and the other should be on standby. Next check to make sure there are no errors for each CMDU and the RDUN is enabled.

If your RDUN is disabled you can try the below:
CORE DIAGNOSTICS
Type: LD 137
System will prompt: .
Test the SCSI Controllers
Type: TEST SCSI
System should state OK
Record all errors if not OK
System will prompt: .
Test Core Redundancy
Type: TEST RDUN
System will print and realize all RDUN sync errors.
System will prompt: .
Attempt to Re-Sync the CORES
Type: SYNC
System will display warning:
CMDU # IS ACTIVE; HDK WILL BE COPIED
DISK RDUN WILL BE ENABLED;
ENTER Y TO CONFIRM, N TO ABORT

Type: Y
System will state OK if CORES and RDUN have been corrected
System will prompt: OK
Type: STAT RDUN
System will stat Enabled if everything is now OK.
System will prompt: .
Attempt to SWAP CORES
Type: SWAP
System should print OK
System will prompt: .
Type: SWAP
System should print OK
System will prompt: .
Type: ****
System will prompt: >

I would do a manual backup to your floppies if all comes up ok:

START BACKUP OF ACTIVE CORE
Type: LD 43
System will prompt: .
Type: EDD
Do not interrupt this process
System will prompt: .
Type: ****

CHANGE CORES
Type: LD 137
System will prompt: .
Type: SWAP
Do not interrupt this process
System will prompt: OK
System will prompt: .
Type: ****

START BACKUP OF ACTIVE CORE
Type: LD 43
System will prompt: .
Type: EDD
Do not interrupt this process
System will prompt: .
Type: ****

CHANGE BACK TO ORIGINAL CORE
Type: LD 137
System will prompt: .
Type: SWAP
Do not interrupt this process
System will prompt: OK
System will prompt: .
Type: ****

gei_spot

disreguard below response, didn't see what RLS you were running


If you have CP PII cards then your cores won't switch.

If you stat your CPU in LD 135 and it looks like this then you have CP PII cores



.stat cpu

cp 0 16 PASS -- ENBL

TRUE REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 42
VERSION = Nov 17 2000, 16:59:42
Side = 0, DRAM SIZE = 127 MBytes


cp 1 16 PASS -- STDBY

TRUE REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 42
VERSION = Nov 17 2000, 16:59:42
Side = 1, DRAM SIZE = 127 MBytes

slagburn

Along with the testing that others have mentioned is LD135 in the midnight routines? I think it has to be in order for the CPUs to switch at midnight like they are 'supposed' to.

Here is one of the most common errors you get when things aren't healthy and the system is setup to switch CPUs.

CCED219 Cannot SCPU: A stdby net resource(s) has a fault

This will come up if you parallel and forget to SYNC when you're done and the system tries to swap. It's been my experience that even if you fix all the things that are wrong you may still have to force swap to get it to work right.

tim_abney

FYI

This morning I was able to force the swap on my problem system without incident. I tested both sides swapped back and forth a couple of times, put the system into the cpu that would not swap and ran mids. It performed the swap with no problem.