CS1K 6.0 system state = split and RDUN is disabled 1

[TDMtek]

While I was doing some systems checks (LD 135) I found that our CS1000M MG 6.0 system state is “SPLIT” and the Disk State is “SPLIT” and in LD 137 RDUN is disabled.

LD 135
CCED000
.stat cpu

cp 0 16 PASS -- ENBL

SYSTEM STATE = SPLIT
DISK STATE = SPLIT
HEALTH = 36
VERSION = Jun 2 2009, 17:46:52
Side = 0, DRAM SIZE = 512 MBytes

cp 1 16 PASS -- STDBY

SYSTEM STATE = SPLIT
DISK STATE = SPLIT
HEALTH = 26
VERSION = Jun 2 2009, 17:46:52
Side = 1, DRAM SIZE = 512 MBytes

>ld 137
CIOD000

STAT RDUN DISABLED

I have ran test in ld 135,137,37.39 and 60, that I can think of, or found in the NTP’s to run, and most of the test pass.
What did not pass was the CNI test in core 1 and the “TEST RDUN” both state in the NTP’s that redundancy must be enabled before the test will run.
I believe that the system health difference must be the redundancy issue.
All I have found is to correct both issues is to use the join command and the system will perform the following:

JOIN Performs the following actions:
• Restores redundancy to a system put in single mode by the SPLIT
command.
• Synchronizes the processor’s memory and drives.
Note 1: This command CANNOT be used unless the system is already in
single mode (SPLIT).
Note 2: This command MUST be entered by the I/O port on the active
processor.
MIDN Run

Am I correct in what I have found? Any other ideas on what I may need to do or look at?

 

[bhassell2000]

join should join the two sides together if no issues are present, I would wait till after hours to join them just incase

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/pub/buddy-hassell/7/5a5/b8b

 

[TDMtek]

After coming in after hours 00:30 AM and issuing the join command, the join command seems to be stuck. Every time I stat CPU I get this same response.

SYSTEM STATE = SYNCING
And
DISK STATE = NOT REDUNDANT

I hooked up a laptop to core 1, the inactive side and I get this over and over
HIRM: Inactive Redundant Mode Performing Background Test….
This may be normal for the inactive core.

 

[guycable2]

When ours did this we had to ini the inactive side and that caused the cores to join and go redundant.

 

[curtismo]

Have had the same issue with CPPM processors on 6.0 where the system state stays in Syncinc. There is a patch MPLR29146 that supposedly fixes this but we are still having this issue show up on our 6.0 system.

What we were seeing during boot of the inactive processor (when splitting cores or swapping cores) had the following problem:

0x228225c0 (tRptd): EXC 0: Exception 14 in Task "tDiskRed" (0x21f6bf30)
SR=0x10246, PC=0x25bd63bd, Addr(CR2)=0xc16d8750, ErrCode=0x2,ValidFlags=0xb
0x228225c0 (tRptd): RST 0: Task tDiskRed being restarted


To resolve (temporarily) peform a manual INI on the standby processor.

That message is normal for the