IBS FAULT

[selectt_DUP]

After recently replaceing a faulty HD on a 4400 and loading the customer database everything is working except the IBS. The IBS are currently showing a solid red light and showing out of service.
The system is programed to IBS, the base stations are programed on the relevant UA32 board in ACT - boards. I have tried to reset the dect service , dectrestart to no avail, warm reseted system fault remains. Ive also swapped the base station onto another working UA32 but still showing out of service. There are 3 base station with the same fault, any ideas ?

[knightr1der]

have you tried to delete the IBS from the UA boards, de-assign the PARI from the shelf, delete the PARI from the system, then reprogram all again?

I had this before on a 6.1 system and only by dleteing everything (like I said above) and reprogramming, it just starting working fine again.

[tot3nkopf]

Use "downstat" command in shelf and see what it returns to you.
Maybe is a firmware problem.
This way you will rule that out.

Regards.

[selectt_DUP]

Tried that still showing out of service when entering the command dectview ibs

0/04/22 neqt 143 RPN : 0 OUTSERV (6 channels) DECT V 2G 0.00 even IDENT NOI
SY
0/04/28 neqt 149 RPN : 1 OUTSERV (6 channels) DECT V 2G 0.00 even IDENT NOI
SY
0/04/30 neqt 151 RPN : 2 OUTSERV (6 channels) DECT V 2G 0.00 even IDENT NOt

Attempted to place IBS base station back into service using inserv p 0 4 0 all ....ect but no joy.

Tried to restart the application using dectrestart, command not available any other pointers ?

[Eliott_DUP]

Which type of CPU?
CPU6 or CPU7 should be managed to DTM Synchro = Yes (ACT=0) under RBS System.
Maybe you can restart the ibs_download process: dhs3_init -R IBS_DOWNLOAD
Then you can check your synchronization with dectinfo 3 and infocs.

[selectt_DUP]

Just realised that my colleague had to use a spare CPU3 to get the system working due to the replacement CPU6 not booting up. This is on a release 5.0ux system.

The system ops states a cpu6 but the system is currently running a CPU 3. Im expecting another replacement next week, so i guess this will resolve the issue.

In the mean time i wonder if i deleted the cpu in management and modified to cpu3 it would work ? Maybe not i guess as it would not allow me to do this !

Thanks in advance

[Eliott_DUP]

The CPU6 has a DTM - the CPU3 not. You have to keep this in mind.
You can delete the CPU6 in mgr and create a CPU3 followed by a
reboot. Why not? But if you use a CPU6 it has to be managed as
CPU6 - identified as CPU6* and the DTM in RBS System must be set
to the ACT with the CPU6 - normally 0. You can check the clock
source of your DECT system then with infocs and dectinfo 3. You
can also enter dectview syncibs and check this after some days.
The command put all IBS in a own group and after each handover
from one IBS to another IBS the groups will be merged. So after
some days you should have one group only.

Example for 4 IBS:

Start tool:
Group 1
IBS 1
Group 2
IBS 2
Group 3
IBS 3
Group 4
IBS 4

After handover IBS 3 to IBS 4:

Group 1
IBS 1
Group 2
IBS 2
Group 3
IBS 3, IBS 4

After handover IBS 1 to IBS 2

Group 1
IBS 1, IBS 2
Group 3
IBS 3, IBS 4

After handover (IBS 1 to IBS 3 or IBS 4) or (IBS 2 to IBS 3 or IBS 4)

Group 1
IBS 1, IBS 2, IBS 3, IBS 4

=> All IBS are well synchronized.

*) After mtcl login which type of CPU is shown in the line with the SW identification? c6s2?