HELP - Major Issues with 61C 5

[M1north]

Now I`m in trouble.....Runnig 61C with 25.40

Had an issue with a bad CMDU 1 a month ago. Had to re-seat everything and it seemed to be fine. Made some changes today and noticed they wouldnt keep (deleted some CLID tables). After further investigation I tried adding a new entry. It took the change. I then tried to delete the entry and the switch re-loaded.

Now whenever I enter LD15 or LD17 this happens:

>LD 15
CDB000
INI000 00002000 22 46 47 00000000 00000000 00000000 00000000 0 ? 00000000
DSET000 DOWN LOAD 0 0 0 0 0 0 0 13083
ACDR ACTIVATED

AUD000

ESDA002 4 22:47:00 23/05/2008

CSA003 4 22:47:00 23/05/2008

DCH1014 19 004CC212 00000106

DCH1014 13 004CC589 00000106

DCH1014 19 004CC212 00000106

DCH1014 13 004CC589 00000106

DCH: 13 EST CONFIRM TIME: 22:47:28 23/05/2008

DCH: 19 EST CONFIRM TIME: 22:47:28 23/05/2008

DCH1014 18 004CC2E6 00000106

DCH 13 ACTV
DCH1014 18 004CC2E6 00000106

SRPT731 OS 0: Warm Start
Release: x112425
Created: Mon Jun 28 21:29:12 PDT 1999
Last Cold Start: 9/4/08 21:27:19 (from '/flash/flashos')
L

DCH: 18 EST CONFIRM TIME: 22:47:28 23/05/2008

SRPT751 INI 0: starting INI on side 0 due to System Restart
Previous INI: side 0 at 23/ 5/08 22:40:52
INIs since switch-over (23/ 5/08 22:31:55): 2, 0

>ld 137
CIOD000
.stat
IOP 0 ENABLED (ACTIVE) IODUC
IOP 1 ENABLED (STANDBY: S/W STATUS) IOP-CMDU
CMDU 0 ENABLED (ACTIVE)
CMDU 1 DISABLED (No Access to HDK)
RDUN DISABLED
ELNK ENABLED
SDEV 0 OK (KC VALID)

.stat cpu
cp 0 15 PASS NORMAL ENBL

cp simm/bank stat
0 0/0 ENBL
0 1/0 ENBL


cp 1 15 PASS NORMAL STDBY

cp simm/bank stat
1 0/0 ENBL
1 1/0 ENBL

Test CPU comes back good. Any ideas?

 

[notapropergeordie]

What if you make the same changes with CMDU 1 disabled?

 

[hhallett]

The CPUs aren't going to be your problem in my opinion.

Since you did all that you did with CMDU 1 a month ago and you say that all was well afterward I'll presume that the ENL/DIS toggle on the face of CMDU 1 is in the ENL position.

the "CMDU 1 DISABLED (No Access to HDK)" is of concern for the moment. A complete system restart might be needed. But before doing that may I suggest another route.

1st, back up your database to CMDU 0. Then enter LD 135 and try the following:

- ENL CMDU 1 (This enables the CMDU. You may or may not get a message about enabling redundancy. tell it "Y" to proceed.)

Once the CMDU is enabled you'll likely see a different HDK message when you STAT the CMDU. Next run a data test on the CMDU:

- DATA CMDU 1 HDK (This will run read tests on the hard drive. This will prove whether the hard drive is functioning or not.)

If the CMDU passes this test you'll likely see a different HDK message saying that the hard drives aren't in synchronization. Next you'll want to sync the drives:

- SYNC

Dependant upon the system usage at the time you execute this it may or may not have an affect upon call processing during synchronization. You might want to wait until an off-peak time to do this.

Presuming all goes well both of your CMDUs will be in sync and redundancy will be restored.

Try swapping the CMDUs two or three times to see if any problem develops when they switch (ld-135 - Swap) But not too much as this can also cause an INI.

Then you just need to be sure that your CPU/IOP/CMDUs match (ex: CPU 0/IOP 0/CMDU 0).

I hope that this is helpful.

Regards,
Harry
"The legitimate powers of government extend to such acts only as are injurious to others. But it does me no injury for my neighbour to say there are twenty gods, or no god. It neither picks my pocket nor breaks my leg." --Thomas Jefferson

 

[Eddie79it]

Could you please post the pdt>rdall so we can see what happens before the ini occurs?

 

[tnphoneman]

What is the release of the IODUC? If it is 4 or 6 replace it before they both go out.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[M1north]

So, I went in yesterday and did a parallel reload. This brought the switch back up and operating normal again. I then dis, re-seated CMDU 1, enl, Sync, and it came back ok.

I think the CMDU 1 has an issue, and I also think CMDU 0 may be problematic here too.

This switch seems to be nothing but problems. The last time this happened, the IOP wouldnt enable and I had to re-seat both CMDU.

EDDIE: I dont know how to run the pdt>rdall, however I do have pdt password and I have used other commands

TNPHONEMAN: I will look for the release numbers...thx

 

[M1north]

CMDU 0 = NT5D61AB 03
CMDU 1 = NT5D61AB 06

I guess I should replace CMDU 1 to start. Was version 03 ok?

 

[M1north]

Reseller is telling me that I need to have both CMDU the same release....Is this true? Also, does it have to be pre-loaded with the same release I have? I thought I could just copy the software and CDB from the active CMDU?

Thx

 

[GHTROUT]

Well, there are a lot of insiders that say you should have both CMDUs on the same release, but no it is not required. I have a number of systems running fine where they are different.

Personally - I would want mine to be the same release.

When you replace one CMDU, yes - you can copy from the "known good" side. You do not need to have the CD or load the OS. Copying does that -.

But you do need the install diskette to get to the install routine - thats how you get to the menu that gives you the option to copy from OS from the other CMDU. Steps following that let you copy the CDB/database too.

You'll want the latest patches on diskette too, since I don't think you can copy those, but I am not positive. I take the position that the patches you have today have prolly been superseded by new ones anyways...so get the new ones.

GHTROUT.com | FAQs | Recent Replies

 

[GHTROUT]

PS You can get CMDUs for under $1000 I think. Ever a 50% markup + 3 hours labor (more than enough) for the vendor is a small price to pay for having it done by them.

GHTROUT.com | FAQs | Recent Replies

 

[johnpoole]

we never worry about same rls, unless it's upgrade time or they start acting up.. another thing i usually check is my software.. how many phones are built and not plugged in? how "dirty" is your software?

is your ram maxed out for your rls? a lot of trash in a switch can burn your ram.. that causes a lot more ini's then we catch..

john poole
bellsouth business
columbia,sc

 

[M1north]

Ok, so I think I`m going to purchase 2x factory refurbs with rls 22 or 23. I`m assuming these were good versions.

This PBX has caused too many issues to leave alone. I will attemp to upgrade them myself so I can learn the process. If it doesnt work, than I will call a vendor.

 

[M1north]

Last Question:

The book recommends copying the software from the active core. I`m wondering if I shouuld load it from the CD considering both CMDU`s have caused me grief?

Any last recommondations?

Thx

 

[tnphoneman]

I always install new drives from the CD as it is the only time you have the option to update the IOP rom. Be sure to burn this when you install software.

Yes the rls 6 card needs to be replaced first.

Make sure core 0 is active and split the cores. Load the software and replace the drives on core 1 then restore redundancy and you are good to go. No need to replace both of the drives.

The release 6 units tended to cause problems. One most notable is that they would just go to sleep and not recover on their own.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.