Card dies after each Restart - Merlin Magix 2

[jonnybb1]

Ok this may seem basic, but I have a Merlin MAgix that I added a new card to, then renumbered the boards, and renumbered the proper extension (ie renumbered 7842 to 592).

Problem is everytime I do a cold shutdow-power-up all the extensions on that card no longer work and I see the blinking red message light.

Can you tell me the step-by-step procedure for what I must have missed?

John B

 

[merlinman]

I think you need to print a SYSTEM SET UP and let us see what you may be dealing with.

You already stated that you did a "BOARD RENUMBER" which should have insured that the processor knows what it's dealing with.

UNLESS, your new card is not seated properly.

Perhaps you have nothing to loose by powering down and reseating eveerthing, especially your new module.

 

[jonnybb1]

----- Site: Allied Chula Vista. Captured: 06/09/06 -----
SYSTEM INFORMATION


Current Date: 06/09/06
Current Time: 08:10:10

System : Mode AutoMaintBusy AutoBusyTie
: Hybrid/PBX Disable Disable

Language: SystemLang SMDR Printer
English English English

CTI Links :
Direct Line Operators : 505 580
Queued Call Operators :
SysProg Port : 505 Password : craftr4

Transfer : Type Audible OneTouch(Complete) ReturnTimer
: Ring MusicOnHold Transfer(Auto) 6 rings

VMS Transfer Return Interval : 5
Paging System Lines : 8207
Music On Hold Line : 8208
Camp On Time : 90 sec
Call Park Return Time : 180 sec
Auto Callback Rings : 3
Extension Status (ESS) : Group Call Supv
ESS Operators :

SMDR: Min.CallTime CallReport Format UDP
: 0 sec In/Out ISDN In/Out

Intercom Dial Tone : Inside
Reminder Service Cancel : :

Behind Switch Code : Drop Transfer Conference
:

Inter-digit Timers (seconds) : 5 24 24 10 10 10 10 5 5
Recall Timer : 450 msec
Second Dial-tone Timer : 0 msec
Rotary Line Cut Through : Delay
Unassigned Extension : 505

Automatic Backup : :Off

T1/PRI/BRI Clock Synchronization:
Primary Secondary Tertiary
3/1 Loop 4/0 Local

Slot # 0: CKE5 CPU
Slot # 1: 412 LS-TDL
Slot # 2: 408 GLM-U
Slot # 3: 100D-U
Slot # 4: 100D-U
Slot # 5: 024 TDL
Slot # 6: 016 TRR Ringing Frequency - 20 Hz
Slot # 7: 016 TRR Ringing Frequency - 20 Hz
Slot # 8: 016 TRR Ringing Frequency - 20 Hz
Slot # 9: 412 LS-TDL
Slot # 10: Not Used
Slot # 11: Not Used
Slot # 12: Not Used
Slot # 13: Not Used
Slot # 14: Not Used
Slot # 15: Not Used
Slot # 16: Not Used
Slot # 17: Not Used 


----------------------------------- ANNOTATION -----------------------------------

 

[merlinman]

OK, I know you said that you renumbered the boards.

But let me say this about that.

It has been our recent experience, and we know not why, that AT TIMES, you have to do a "BOARD RENUMBER" more than once to make it "TAKE".

I would suggest doing that a couple of more times, and then, if you still have "ISSUES", let's do a print of the ERROR LOG, and see if that tells us anything.

 

[jonnybb1]

I have tried several Board Renumbers because I have had the same3 ISSUES you mentioned. The only thing I can think of is to turn on Auto-Backup?

JOhn B

 

[merlinman]

Well, I ALWAYS turn on AUTO BACK UP, but I set it to WEEKLY, so that you'll have something to fall back on.

Setting it daily can cause problems 'cause it may be 3 days before you realize you have a problem, and by that time, both of your Auto Back files are the same corrupted mess.

Now, about your problem.

Have you looked at the errors?

Can you print the error log?

We could suspect that new board.

 

[2BAvoice]

I have had several systems in which I have had problems with slot 9 and the module being recognized properly. What I have always ended up doing is shutting the system down, remove the module from slot 9, power up and do a renumber. Then power down and reinstall the module. I have had at least 3 instances of this and I suspect a relation to Winspm R9's glitches.