OK, this is causing a headache. After 10-15 minutes of CPU/CMDU 1 being active, we get this sequence:
HWI529 CMB: Primary CP can't access secondary CP
Check both the CMB cable and the standby CP
CIOD126 CMDU 0 DISABLED: due to SPLIT mode
HWI529 CMB: Primary CP can't access secondary CP
Check both the CMB cable and the standby CP
HWI534 CMB: Synchronization of memories begun: CP 1 master
HWI533 CMB: Synchronization of memories completed
A stat (LD 137) shows:
.stat
IOP 0 ENABLED (STANDBY: S/W STATUS) IODUC
IOP 1 ENABLED (ACTIVE) IODUC
CMDU 0 DISABLED (Out of Split Mode)
CMDU 1 ENABLED (ACTIVE)
RDUN DISABLED
ELNK ENABLED
SDEV 1 OK (KC VALID)
After a sync, the new stat has CMDU 0 enabled (standby), and RDUN enabled. scpu is successful in either direction, with all stats being fine unless it is left on CPU 1, at which time this happens. To keep all data the same we do a sync, scpu back to 0, let it run until the midnights. Then we do it again in the morning.
About a month ago CPU 0 went down. When we replaced it last week, we found different databases, indicating a possible connection between the switch failing & the current problem. All faceplate switches are correct, cables have been checked. We did find a bad floppy in one side, but that has been resolved.
Any ideas?
See the next post for more info on the PBX.
HWI529 CMB: Primary CP can't access secondary CP
Check both the CMB cable and the standby CP
CIOD126 CMDU 0 DISABLED: due to SPLIT mode
HWI529 CMB: Primary CP can't access secondary CP
Check both the CMB cable and the standby CP
HWI534 CMB: Synchronization of memories begun: CP 1 master
HWI533 CMB: Synchronization of memories completed
A stat (LD 137) shows:
.stat
IOP 0 ENABLED (STANDBY: S/W STATUS) IODUC
IOP 1 ENABLED (ACTIVE) IODUC
CMDU 0 DISABLED (Out of Split Mode)
CMDU 1 ENABLED (ACTIVE)
RDUN DISABLED
ELNK ENABLED
SDEV 1 OK (KC VALID)
After a sync, the new stat has CMDU 0 enabled (standby), and RDUN enabled. scpu is successful in either direction, with all stats being fine unless it is left on CPU 1, at which time this happens. To keep all data the same we do a sync, scpu back to 0, let it run until the midnights. Then we do it again in the morning.
About a month ago CPU 0 went down. When we replaced it last week, we found different databases, indicating a possible connection between the switch failing & the current problem. All faceplate switches are correct, cables have been checked. We did find a bad floppy in one side, but that has been resolved.
Any ideas?
See the next post for more info on the PBX.
