Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SPLIT Command Fails

Status
Not open for further replies.

Telephonist

Technical User
Joined
Sep 3, 2003
Messages
95
Location
US
We recently upgraded our CS1000M-MG (Option 81C) to Pentium 4 processors and FNF, and we have found that the Split command in LD 135 doesn't work. We get this:

LD 135
.SPLIT
OK
.
SRPT037 LCS: SPLIT COMMAND NOT VALID IN SYNCING STATE.

The work-around has been to unplug the Ethernet cable that connects the processors when we needed to split.

It's like the switch perpetually thinks it's syncing the cores, even though the sync process has completed after rejoining the cores. Our maintenance vendor is trying to find resolution on this, but is coming up empty.

Has anyone else experienced this? Any ideas?

Thanks.


 
What does it report when you stat?

JohnThePhoneGuy

"If I can't fix it, it's not broke!
 
This.

.stat cpu

cp 0 16 PASS -- ENBL

TRUE REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 36
VERSION = Jul 28 2005, 04:14:02
Side = 0, DRAM SIZE = 512 MBytes


cp 1 16 PASS -- STDBY

TRUE REDUNDANT
DISK STATE = REDUNDANT
HEALTH = 36
VERSION = Jul 28 2005, 04:14:02
Side = 1, DRAM SIZE = 512 MBytes

.
 
i think this is one for Nortel, haven't seen it report both sides with full health and not split.

JohnThePhoneGuy

"If I can't fix it, it's not broke!
 
Please post also a printout from a stat in LD 137
 
Is this what you wanted?

>ld 137
CIOD000
.stat

FMD
VENDOR: STI Flash 7.2.0
/p CAPACITY 318767104 Bytes
FREE SPACE 249860096 Bytes
/d CAPACITY 318767104 Bytes
FREE SPACE 310067200 Bytes
/e CAPACITY 318767104 Bytes
FREE SPACE 298020864 Bytes


RMD
VENDOR: SanDisk SDCFH-256
/cf2 CAPACITY 256622592 Bytes
FREE SPACE 254930944 Bytes

SDEV 1 OK (KC VALID)
.
 
We resolved this issue. It turned out to be a faulty NT4N48BA Utility Card in Core 1. Nortel has apparently seen this with incorrect switch settings on a Utility Card, as well as a faulty card in one of the cores.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top