Download
Share
Print this page
Unify Openscape 4000 Service Documentation
  1. Manuals
  2. Brands
  3. Unify Manuals
  4. Server
  5. OpenScape 4000
  6. Service documentation
Unify Openscape 4000 Service Documentation

Unify Openscape 4000 Service Documentation

Troubleshooting, alfe
Hide thumbs Also See for Openscape 4000:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990

Advertisement

Quick Links

Download this manual
OpenScape 4000/HiPath 4000
Troubleshooting (AlFe)
Service Documentation
A31003-H3100-S104-14-7620

Advertisement

loading
Need help?

Need help?

Do you have a question about the Openscape 4000 and is the answer not in the manual?

Questions and answers

Deborah L Arnold
February 5, 2025

can you deny access for internal calling and allow external calling

0

Related Manuals for Unify Openscape 4000

Summary of Contents for Unify Openscape 4000

  • Page 1 OpenScape 4000/HiPath 4000 Troubleshooting (AlFe) Service Documentation A31003-H3100-S104-14-7620...
  • Page 2 Availability and technical specifications are subject to change without notice. Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software and Solutions GmbH & Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of their respective holders.
  • Page 3 OpenScape 4000/HiPath 4000 - Troubleshooting (AlFe) - Content OpenScape 4000/HiPath 4000 - Troubleshooting (AlFe) - Content 1 Error codes ................7 1.1 Fundamentals .
  • Page 4 OpenScape 4000/HiPath 4000 - Troubleshooting (AlFe) - Content 3 Controlling error signalling with AMO SIGNL ..........58 3.1 Current (ASD) / Configured (CSD) output devices .
  • Page 5 OpenScape 4000/HiPath 4000 - Troubleshooting (AlFe) - Content 8.2 F1000 ................142 8.3 F2000 .
  • Page 6 OpenScape 4000/HiPath 4000 - Troubleshooting (AlFe) - Content 8.14.9 Special allocation table for circuit error messages........1737 8.15 Device type / Board table .
  • Page 7 code7s.fm Nur für den internen Gebrauch Error codes Fundamentals 1 Error codes 1.1 Fundamentals While the system is starting up the current status of the board (DP or bus board) is displayed on the 7-segment display. Apart from signaling with a 7-segment display it is also possible to output the error code via a terminal connected to the board.
  • Page 8 code7s.fm Error codes Nur für den internen Gebrauch Fundamentals SUSY CR-F CC-AP zmeupdja zmeupdjs zoninth0 zmflbtj0 zocrypt0 zaahcm00 zaahcm0s zodusfm0 zodfmfm0 zmdfest0 zoddscr0 zodbckup zodpcl00 zodpgl00 zggdeb10 zbaacm00 zaftran0 zmhstbma zmhstbms zmiptcha zmqnfyja zmdamcja zmdsig00 zmkbst00 zmncdbr0 zcgoutp0 zppdiag0 zmdhist0 zppcoa00 zppjtae0 zqfabt00...
  • Page 9 code7s.fm Nur für den internen Gebrauch Error codes Fundamentals SUSY CR-F CC-AP zqqpitz0 zmdamcjs zmdamcgs zmbadpj0 zaaftp0a zaaftp0s zmibrtjs zmikttjs zmibzmj0 zcacalp0 zcgcdbm0 zcgcoll0 zqqrto0s zqvvecos zqsrec0s zmiptchs zqqdiag0 zqfjtaes zqfmainl zdbltg00 zqisomhl zeeprep0 zmbamdb0 zqqdc00l zqqpitll zqqrto0l zqvvecol zqsrecol zqqcos00 zqfjtael Table 1...
  • Page 10 code7s.fm Error codes Nur für den internen Gebrauch Fundamentals • Operating status of the board, • Error code. Example: H'93 -> values H'80 and H'10 and H'02 and H'01 => Segments h, e, b, a 1.1.2.1 Segments A distinction is made between 3 sub-functions: •...
  • Page 11 code7s.fm Nur für den internen Gebrauch Error codes Fundamentals Display Status Hardware test, PID Polling, Restart Message, ready to load Error code will be signalled. Most often signalled when no boot device found. Starting SYSLOAD, Loading Subsystems, Creating Checksums If fails here, most like a new SW image is needed - Console output to be checked. The startup of the ADP is finished, ADP active Table 2 Overview DP status displays of the ADP...
  • Page 12 code7s.fm Error codes Nur für den internen Gebrauch Fundamentals Display Creation Flag Status Hardware test, PID Polling, Restart Message, ready to load Loading SYSLOAD Starting SYSLOAD, Loading Subsystems, Creating Checksums If fails here, most like a new SW image is needed - Console output to be checked. ZONNUCL0, RMX-OS ZONNCAN0, OS Extension ZQPCOM00, ZDBOTTRA, common Callgates, Tracer...
  • Page 13 code7s.fm Nur für den internen Gebrauch Error codes Fundamentals Display Creation Flag Status ZCGOUTP0, ETB Support Task ZPPDIAG0, EEA Support Task ZMDHIST0, ZPPCOA00, Residential HISTA Task, COA Task ZPPJTAE0, End-of-Jota-Task ADP ZAAFTP0A, FTP Server Semaphore ONSMINI, wait for Units of the Security Technics The startup of the ADP is finished, ADP active Table 4 Status Outputs on the DP of the ADP...
  • Page 14 code7s.fm Error codes Nur für den internen Gebrauch Fundamentals Display Creation Flag Status ZOXHSR0S, Signalling Router Standby (waiting for active SWU partner) ZQFMAINS, Error Analysis of CC ZQQDC00S, Device Management in CC ZQQPITZ0, Peripheral Setup CC ZMDAMCJS, Technical Equipment AMC ZMDAMCGS, CC specific AM Routins ZMBADPJ0, CP Interface Task to AM ZAAFTP0S, FTP Server...
  • Page 15 code7s.fm Nur für den internen Gebrauch Error codes Fundamentals Display Creation Flag Status SWU Active Standby active Table 5 DP Status Display in the SWU 1 Only valid for Duplex 2 Only valid for Duplex 1.1.2.7 Status Outputs on the DP of the CC-AP Display Creation Flag Status...
  • Page 16 code7s.fm Error codes Nur für den internen Gebrauch Fundamentals Display Creation Flag Status ZODPCL00, Peripheral Computer Loader ZODPGL00, Program Loader ZGGDEB10, Residential Part of Debug ZBAACM00, ACL Manager ZAFTRAN0, File Transfer ZMHSTBMA, Support Task for BELAU ZMQNFYJA, NOTIFY Task ZMDAMCJA, AMO Control internal/external ZMDSIG00, Signalization Task ZMBKST00, ZMNCDBR0, Support Task ZCGOUTP0, ETB Support Task...
  • Page 17 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes Display Creation Flag Status ZDBLTG00, Data Basis Code for SWU and LTG ZQISOMHL, Somup Handler ZEEPREP0, Pre-Processing of SWU ZMBAMDB0, Technical Equipment Support Task LTG ZQQDC00L, Device Management LTG ZQQPITLL, Peripheral Setup LTG ZQQRTO0L, Routine Test Organisation LTG ZQVVECOL, Connection Control in LTG...
  • Page 18 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes 1.2.1 BOOT error codes in the ADP and the CC Hex code Name Explanation Recommended action 1000 WA_E_NMEM No memory in system Check load tables or increase number memory (either with MIP, M8M or by inserting memory modules in DM4L) 1002...
  • Page 19 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes Hex code Name Explanation Recommended action 1017 WA_E_SLOT Start selector invalid Check APS 1018 WA_E_LINK Descriptor link interrupted Check APS 1019 WA_E_SDDL Too many data areas for SDD Check APS request 1020 WA_E_SDT...
  • Page 20 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes Hex code Name Explanation Recommended action 4300 WA_E_PCI_UNEXP Wrong PCI controller found Check DP/if necessary update LW ECTED_DEVICE 4400 WA_E_FW_NO_MAT FW ID does not correspond to Check DP/LW, if necessary, check board ID 4545 WA_E_MONOPROC...
  • Page 21 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes LAN errors (error code 3100 - 31FFH) indicate a defective LAN connection between the CC and ADP. These errors may be specific to either LAN, TPS (Transport Service) or TCP (Transmission Control Protocol). The most frequent LAN error is 310A: The DP4L does not have a LAN connection.
  • Page 22 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes Hex code Name Explanation Recommended action 3187 WA_E_NODATASEND_BUFFLACK - " - - " - 3188 WA_E_RSTSEND_BUFFLACK - " - - " - 3189 WA_E_RSTSEND_SEND - " - - " - 31A0 WA_E_IMPLAUS_STATE_OPEN Error inside TCP state machine - "...
  • Page 23 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes Hex code Name Explanation Recommended action 3202 WA_Y_IMPLAUS_RECORD FWLP - the read record from Check BOOT LW the MCS86-file contained an wrong record type (MCS86 format) 3203 WA_Y_IMPLAUS_BASE_ADDR FWLP - while incrementing the Check BOOT LW base_address the last base_address was already...
  • Page 24 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes • Check ADS: Check whether the modules in the ADP are inserted in the correct slot; whether the ADS powered up correctly; whether the FW of the relevant modules ’are up to date’ . •...
  • Page 25 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes Hex code Name Explanation Recommended action 1A2C WA_E_IOPS Device not initialized Retry and, if necessary, check load medium 1B2C WA_E_IOPS Ready changed: READY/NOT READY/READY Retry and, if necessary, check load medium 1C2C WA_E_IOPS...
  • Page 26 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes 1.2.4 BOOT error codes during the FWLP Errors during the firmware loading process are also signaled at the SSD. The following errors can occur: Hex code Name Explanation Recommended action 3201 WA_Y_WRONG_HEX_POINTER...
  • Page 27 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes Hex code Name Explanation Recommended action 3231 WA_E_FM_DEVICE_NOT_SUPPORT FWLP - Flash module not supported Check BOOT LW - exchange DP, 3232 WA_E_FM_BLOCK_ERASE_FAIL FWLP - Error while deleting Check BOOT LW, 3233 WA_E_FM_PROGRAM_FAIL FWLP - Error while writing...
  • Page 28 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes 1.2.6 BPL286 error codes (BOOT Program Loader) The error codes of the BOOT Program Loader (used to load the IPL) consist of the command used (e.g. ATTACH_VOLUME), the error which occurs (e.g. incorrect parameter transfer) and a basic error code (8880H). Example: Command: MP$ATTACH 0010H Error extension: E$USER$PARAM 0000H...
  • Page 29 code7s.fm Nur für den internen Gebrauch Error codes BOOT error codes Hex code Name Explanation Recommend action 892x E_COMPUTE_RANGE Error comparing first/last segment address Check BOOT FW and load device 893x E_PMT_INIT not used 894x E_PMT_GET not used 895x E_PMT_PUT not used 896x E_PMT_ADD...
  • Page 30 code7s.fm Error codes Nur für den internen Gebrauch BOOT error codes 1.2.7 NFD286 error codes (Named File Driver) Name Explanation Recommended action code 092B E_MEDIA_CHANGED Drive has been changed Check load device 8840 E_DRIVE Drive not okay; New initialization Check load device 8841 E_FNODE Fnode number is too big...
  • Page 31 code7s.fm Nur für den internen Gebrauch Error codes IPL286, PGL286 and PBO286 error codes Name Explanation Recommended action code 8861 E_DATCAT_FUL Too many catalog entries in DAT Check DAT 8862 E_DATCAT_EMPTY No catalog entries in DAT Check DAT 8863 E_DAT_NOSUPPORT Function not supported for DAT Check DAT 8880...
  • Page 32 code7s.fm Error codes Nur für den internen Gebrauch IPL286, PGL286 and PBO286 error codes Hex code Name Explanation Recommended action 8436 MC_Y_E_DSC_ERR Descriptor overlap Reinstall subsystem(s) 8437 MC_Y_E_CHSU_ERR Checksum error Reinstall subsystem(s) 8438 MC_Y_E_MEM_ERR Insufficient memory Insert more memory; verify load tables 8439 MC_Y_E_NAFID_ERR...
  • Page 33 code7s.fm Nur für den internen Gebrauch Error codes PCL286 error codes 1.4 PCL286 error codes Name Explanation Recommended code action 8800 OP_Y_E_WARNINGS No hardware, warning flags output None 8801 OP_Y_E_PGLIBM Internal PGLIBM error 8802 OP_Y_E_MEM Insufficient memory Retry 8803 OP_Y_E_HARD_WARN Errors can occur with other commands or options 8804 OP_Y_E_COMMAND...
  • Page 34 code7s.fm Error codes Nur für den internen Gebrauch FAM/BIOS error codes Name Explanation Recommended code action 8823 OP_Y_E_BUF_SIZE Record to be processed is too long Reinstall 8824 OP_Y_E_EXPAND Expanded iterated record > 64kB Reinstall 8825 OP_Y_E_STACK_SIZE Too many recursions f. iterated record Reinstall 8826 OP_Y_E_COVER_TAB_SIZE...
  • Page 35 code7s.fm Nur für den internen Gebrauch Error codes FAM/BIOS error codes Name Explanation Recommended action code OD_Y_E_SUPPORT Parameter combination not See below supported OD_Y_E_EMPTY_ENTRY Directory is empty See below OD_Y_E_DIR_END Directory does not contain so many See below entries OD_Y_E_ACCESS Invalid access mode See below OD_Y_E_FILE_TYPE...
  • Page 36 code7s.fm Error codes Nur für den internen Gebrauch FAM/BIOS error codes Name Explanation Recommended action code OD_Y_E_PATHNAME_SYNTAX Path name contains invalid Area logically destroyed, save data characters and reinitialize OD_Y_E_FNODE_LIMIT Maximum number of Fnodes Delete unnecessary files exceeded OD_Y_E_LOGNAME_SYNTAX Invalid path name Check file names entered OD_Y_E_CLOSE Error closing file...
  • Page 37 code7s.fm Nur für den internen Gebrauch Error codes FAM/BIOS error codes Name Explanation Recommended action code 8104 OD_Y_E_VOL1 No VOL1 ID See below 8105 OD_Y_E_VOLID Volume ID does not exist Check tape names entered 8106 OD_Y_E_USERID User ID does not exist Check tape names entered 8107 OD_Y_E_HDR...
  • Page 38 code7s.fm Error codes Nur für den internen Gebrauch FAM/BIOS error codes Name Explanation Recommended action code 8308 OD_Y_E_DD_UNIT_RESERVED Device reserved for another See below controller 8309 OD_Y_E_DD_VOL_OVERFLOW End of tape reached; Rewind? See below 830A OD_Y_E_DD_FILE_MARK File marking found See below 830B OD_Y_E_DD_EOT End of tape reached...
  • Page 39 code7s.fm Nur für den internen Gebrauch Error codes FAM/BIOS error codes IMPORTANT: General procedure for DMS errors (unless an action has been given in the above table): 1. Repeat command. 2. If the same or another error should occur: 3. initiate a soft restart in the ADP and repeat the command. 4.
  • Page 40 code7s.fm Error codes Nur für den internen Gebrauch Operating system error codes 1.6 Operating system error codes Name Explanation Recommended action code 0001 ON_Y_E_TIME Timeout 0002 ON_Y_E_MEMORY Insufficient memory 0004 ON_Y_E_LIMIT Object limit reached 0005 ON_Y_E_CONTEXT System call made at incorrect position 0006 ON_Y_E_EXIST Object address of the token does not exist...
  • Page 41 code7s.fm Nur für den internen Gebrauch Error codes Operating system error codes Name Explanation Recommended action code 4000 ON_Y_E_NO_ACKNOWLEDG The system waits for an response for another processor to no avail. Check whether all central boards have been booted 8000 E_ZERO_DIVIDE No longer used 8001...
  • Page 42 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch AMOs used 2 AM handling of alarms 2.1 AMOs used The AMO’s below are used in conjunction with alarms, error messages or message outputs: • AMO-VADSU / VADSM • AMO-GRA •...
  • Page 43 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Configuring, modifying and deleting SWU logical alarms A directional alarm can also be assigned to a group of trunk circuits configured beforehand with the AMO BUEND. In the same way, personal alarms configured with the AMO VADSU can be assigned to station numbers with the AMOs SBCSU and SCSU.
  • Page 44 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch Deactivating and activating alarms DIS-VADSU: ASS,08&&522; Display output ASSIGNMENT: DIRECTIONAL ALARMS ALARM NO. PENS ASSIGNED 1-2-103-00 1-1-007-05 ASSIGNMENT: PERSONAL ALARMS ALARM NO. STATION NUMBERS ASSIGNED 2500 2501 2503 2507 2511 2533 2534 2535...
  • Page 45 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Deactivating and activating alarms If an alarm is waiting at the time when its corresponding alarm class was deactivated, the alarm is reset immediately after deactivation (signaling of an A9002 / A9003 / A9007 message). The alarm is immediately signaled following reactivation (A9000 / A9001 / A9006), if at this time one of the threshold alarms is violated.
  • Page 46 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch DEVICE ALARM AB-VADSU:PERIPHER,4; H500: AMO VADSU STARTED ALARM CLASS: SWU PERIPHERY ALARM CLASSES THRES1 THRES2 FAIL. FAIL TOTAL TIME1 [TIME2 TIME NAME IN % IN % ABS. IN % ABSOL. [SEC] [SEC] TIE LINE...
  • Page 47 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Changing the message priority to alarm This alarm type is a special application. The DEVICE alarm is generally employed for long-term monitoring of trunks or tie lines. If, for example, a trunk is out of service because of a line fault in the exchange, the DEVICE alarm can be used to signal excessively long down times (up to 255 hours).
  • Page 48 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch Changing the message priority to alarm PRIO 0 : The individual alarm messages for the corresponding alarm class retain the message priority assigned to the alarm number with the AMO-SIGNL. PRIO 1 - 8 : The individual alarm messages for the corresponding alarm class have the priority assigned to this alarm class.
  • Page 49 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Changing the message priority to alarm A9001 M4 N3290 NO ACT NMCALARM MAJOR ALARM ON 96-07-25 07:26:44 ALARM CLASS:SWU-PER:001 ALARM NAME:TIE LINE FORMAT:2D DIS-VADSU:PERIPHER,1; H500: AMO VADSU STARTED ALARM CLASS: SWU-PERIPHERY ALARM CLASS THRES1 THRES2 FAIL.
  • Page 50 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch Variable Hardware contacts in the case of individual alarms PRIO = 0 : ALARM MESSAGES FOR THIS ALARM ARE ASSIGNED MESSAGE PRIORITY, CONFIGURED BY THE AMO SIGNL (SEE A9000 BIS A9007) PRIO = 1 TO 8 : THIS PRIORITY IS USED AS THE MESSAGE PRIORITY FOR THE ALARM MESSAGES CONCERNING THIS ALARM...
  • Page 51 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Configuring the validity period for SLA CHA-VADSU:CENTRAL,20,,,,,,,S1; H500: AMO VADSU STARTED H13: ONLY ALARMS WITH HWCONT = S1 ARE SIGNALED IN THE CASE OF LED P2 (PAL) ON IOP AND NAL ON DP. THE SUMMATION DISPLAY (ALL NON-URGENT ALARMS) IS DEACTIVATED FOR THIS HW CONTACT.
  • Page 52 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch Activating the snapshot function START: 05:00 END: 22:00 AMO-VADSU-79 NMC ALARMS CONFIGURATION, SWITCHING UNIT DISPLAY COMPLETE; 2.9 Activating the snapshot function Units which have been preventively configured and which are not in operation or which are blocked by an AMO are considered “defective”...
  • Page 53 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Regenerating the validation data AMO-VADSU-79 NMC ALARMS CONFIGURATION, SWITCHING UNIT DISPLAY CARRIED OUT; ACT-VADSU:SNAPSHOT; H500: AMO VADSU STARTED AMO-VADSU-79 NMC ALARMS CONFIGURATION, SWITCHING UNIT ACTIVATION COMPLETED; DIS-VADSU:SNAPSHOT; H500: AMO VADSU STARTED SNAPSHOT DISPLAY OUTPUT: STATUS SNAPSHOT - STATUS : ON AMO-VADSU-79...
  • Page 54 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch Controlling alarm output • Only service-relevant messages are sent via AFR (Automatic Fault Report) to Remote Service Platform (RSP). • All error and advisory messages are collected in a history file for diagnostics purposes (the HISTO file is assigned to the symbolic device DPT4).
  • Page 55 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Alarm mirror ADD-HISTA:FSIZE=2500; • Display existing messages; DIS-HISTA; The AMO displays the following message, for example; H500 : AMO HISTA STARTED DATABASE SIZE : 2500KB NUMBER OF ENTRIES : OLDEST ENTRY : 95-09-06 07:58 MOST RECENT ENTRY : 95-09-06 08:05...
  • Page 56 alarm_bh.fm AM handling of alarms Nur für den internen Gebrauch Resetting alarms 1. With AMO GRA You can use AMO GRA to request the following alarm-mirror messages: T1 -T3 V1 -V3 (all processors) (Switching unit) (Administation (Call charge (Text and fax (Voice mail and data server)
  • Page 57 alarm_bh.fm Nur für den internen Gebrauch AM handling of alarms Resetting alarms • In ISS: 13, 22, 23, 29. IMPORTANT: All central alarms (SWU and ADP) can be deleted. Example: You want to delete central alarm 05 (CC RESTARTS). DEL-GRA:BP,5; A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 58 alarm_bh_02.fm Controlling error signalling with AMO SIGNL Nur für den internen Gebrauch Current (ASD) / Configured (CSD) output devices 3 Controlling error signalling with AMO SIGNL 3.1 Current (ASD) / Configured (CSD) output devices AMO-SIGNL supports a function that allows you to transfer the devices specified by the ASD parameter to those specified by the CSD parameter.
  • Page 59 alarmgen.fm Nur für den internen Gebrauch Alarm Generation Generating SWU logical alarm classes 4 Alarm Generation 4.1 Generating SWU logical alarm classes The AMO VADSU supports generation of SWU-logical, individual alarm classes. A distinction is made between the generation of directional alarm classes and personal alarm classes. Alarm-class generation permits user definition of the validation data, i.e.
  • Page 60 alarmgen.fm Alarm Generation Nur für den internen Gebrauch Generating SWU logical alarm classes 4.1.3 Alarm class generation The procedure for generating alarm classes is illustrated in general terms by the example below 1. Generate an alarm class with ADD-VADSU. Use the DIR or PERS parameter to select the subgroup. The AMO itself supplies the alarm number if you do not enter an alarm number.
  • Page 61 alarmgen.fm Nur für den internen Gebrauch Alarm Generation DEVICE ALARM LINE), the change is followed by OFF alarm signaling for the TIE LINE alarm. If the threshold of the new alarm class is set to a value such that the newly added PEN (NPR) causes the threshold to be exceeded, the new ALARM is signaled by ON.
  • Page 62 alarmgen.fm Alarm Generation Nur für den internen Gebrauch F4704 Handling • Display; With ) to check whether the alarm is activated and the time (output column: DIS-VADSU DIS-VADSM DEV-T entered. 4.2.1 General notes for this alarm type This alarm type is normally configured when long-term monitoring is activated for trunk or tie lines. It can show how long lines were out of service.
  • Page 63 alarmgen.fm Nur für den internen Gebrauch Alarm Generation F4704 Handling 1. Read message F4704 to discover the name of the SWU alarm which has been triggered (see the example above). 2. If the string at the start of the alarm name is Dxx: or Pxx:, the alarm is an SWU-logical alarm, so you should follow the instructions in Step 3 below.
  • Page 64 alarmgen.fm Alarm Generation Nur für den internen Gebrauch F4704 Handling 4. SWU periphery alarms. A SYSTEM RESTART is the only way of restoring the consistency of the configuration counter assigned to this alarm, i.e. a hard restart of both the active and the stand-by CC is necessary. A system restart can usually be performed only in a light-traffic period or perhaps only with the approval of the customer, so in the interim it is best to deactivate the alarm with (set the thresholds for...
  • Page 65 alarmkon.fm Nur für den internen Gebrauch Alarm concept Important information 5 Alarm concept 5.1 Important information Intervention at the customer system can sometimes cause malfunctions which will be detected by the system and reported to the Remote Service Platform (RSP). You should therefore shut down the Remote Service Platform (RSP) system before beginning work with the AMO-AFR.
  • Page 66 alarmkon.fm Alarm concept Nur für den internen Gebrauch Threshold value and validation time • AMO VADSM (VAlidation Data Service Module) – Alarm validation in ADS/SM. • AMO VADSU (VAlidation Data Switching Unit) – Alarm validation in the SWU. – Configuring customer-specific personal and directional alarms. –...
  • Page 67 alarmkon.fm Nur für den internen Gebrauch Alarm concept DEVICE ALARM The discrimination and prioritization of the alarms thus depends on the different threshold values. See also: • DEVICE ALARM • Alarm classes • Assigning error messages • Single alarms and alarm mirror •...
  • Page 68 alarmkon.fm Alarm concept Nur für den internen Gebrauch RESET ALARM function as the validation time of the respective alarm. Resetting the counters means that the error count is not entered in the error statistics. This means that low-impact (’tolerable’) errors cannot lead to an alarm under normal circumstances. Only an abnormal, rapid succession of errors within one decrementing interval will lead to an alarm.
  • Page 69 alarmkon.fm Nur für den internen Gebrauch Alarm concept Assigning error messages 5.10 Assigning error messages Every error message is assigned to one or more alarms. Error messages contain the ALARM CLASS in the second line. This line is suppressed in the case of output via NMC and is displayed in the case of output via Remote Service Platform (RSP) or printer.
  • Page 70 alarmkon.fm Alarm concept Nur für den internen Gebrauch Alarm mirror See also: • Alarm types • Alarm classes • Assigning error messages • Alarm mirror • Evaluating the alarm mirror 5.12 Alarm mirror The alarm mirror output is carried out with the aid of alarm messages which contain all the set alarms of an alarm class.
  • Page 71 alarmkon.fm Nur für den internen Gebrauch Alarm concept Alarm mirror A9xxx M4 N0188 NO ACT..BPB ..NMCALARM ALARM MIRROR: xxxxxxx..01-10-29 14:52:41 ..DEVICE ALARM: Alarm group: ..MINOR ALARM: Central CENTRAL GRP ..MAJOR ALARM: 01 00 03 00 00 25 SWU periphery SWU-PER GRP ..FORMAT:2C SWU logical device SWU-LOG GRP...
  • Page 72 alarmkon.fm Alarm concept Nur für den internen Gebrauch Alarm mirror 11 = Byte 1 22 = Byte 2 33 = Byte 3 44 = Byte 4 Bytes 1 - 4 contain the 32 SWU periphery alarms. Alarm mirror of the SWU logical device class A9010 M4 N1001 NO ACT...BPA ..NMCALARM MIRROR: SWU-LOG GRP..01-10-29 13:58:45 DEVICE-ALARM:.
  • Page 73 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class • Assigning error messages • Single alarms and alarm mirror • List of alarms: CENTRAL, SWU-PER, SWU-LOG, SM-PER • Alarm mirror 5.13 Central alarm class This group comprises 64 alarms, which cannot be unambiguously assigned to one of the periphery device class, as well as alarms defined as central alarms due to their functionality.
  • Page 74 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class Alarm number Alarm name Threshold value and validation time Messa MINOR MAJOR MINOR MAJOR DEVICE priorit ALARM ALARM ALARM ALARM ALARM (absolut (absolut (seconds (seconds (hours) e value) e value) CENTRAL:003 PHONEMAIL ALARM deact.
  • Page 75 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class Alarm number Alarm name Threshold value and validation time Messa MINOR MAJOR MINOR MAJOR DEVICE priorit ALARM ALARM ALARM ALARM ALARM (absolut (absolut (seconds (seconds (hours) e value) e value) CENTRAL:037 AP EMERGENCY deact.
  • Page 76 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class A9000 F1000 F2000 F3000 F4000 F5000 F6000 F7000 F8000 CENTRAL:000 LTG RESTARTS IMPORTANT: Not relevant for US release. This alarm indicates that at least 1 LTG has undergone too many restarts within the defined period of time. Although the above alarm is a summation alarm, the number of LTG restarts are logged by separate counters for each LTG.
  • Page 77 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class This alarm indicates failure of an LTU shelf, a SYN-clock or the failure of the ac generator ACGEN/ac ringing voltage generator RG. IMPORTANT: The error which generates this alarm can also generate other SWU periphery alarms, e.g. DIGITAL VOICE DEVICES as a secondary reaction.
  • Page 78 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class This alarm indicates a cabling problem between the STBY-CC and the LTUCX board. This happens when the cables to the board are defective, disconnected or connected in the incorrect sequence. Assignment to error message: F5906 Alarm criteria:...
  • Page 79 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class • A minor alarm only is generated for this alarm: STBY-CC failure • The alarm is reset automatically as soon as the standby CC half is back in operation. This alarm can also be cleared with the AMO GRA.
  • Page 80 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class CENTRAL:010 IS RESTARTS This alarm indicates that the ADS has undergone too many restarts. Restart alarm criteria: • The error counters are controlled via error messages. One of the messages assigned to the restart alarm contains a restart flag.
  • Page 81 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class • List: CENTRAL A9000 F6000 CENTRAL:014 Not used • List: CENTRAL CENTRAL:015 EXTERNAL SERVER This alarm indicates that the external server is not available from the point of view of the SWU, i.e. the SWU periphery modules that have a physical connection (via a LAN for example) to an external server monitor this connection.
  • Page 82 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class This alarm can occur both in the SWU and in the ADP. • This alarm indicates too many errors in the central hardware of a CC half. Critical errors of this type which lead to a processor restart are indicated via the alarm CC RESTARTS. Assignment to error messages: F2200 - F2201, F3000 - F3010,...
  • Page 83 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class The alarm “SWITCHING NETWORK” is therefore mainly signaled when individual hardware units fail. The relevant error messages are F5180 - F5183. Assignment to error messages: F5050 - F5059, F5180 - F5183, F5200 Alarm criteria: •...
  • Page 84 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class • This alarm can be reset either by means of an external NMC / DMS command (see NMC Administrator Manual A31003-G8014-A100-*-35) or AMO-GRA (CHA-GRA). If this is not done, the alarm is deleted after 18 hours. •...
  • Page 85 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class These alarms are central alarms of the ADS and the different servers. They indicate too many errors in the central hardware of the server (MEM/IP/MULTIBUS), as well as the hardware interrupts of the DP. Critical errors of this type which lead to a processor restart are indicated via the alarms ’IS RESTARTS’...
  • Page 86 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class F6300 - F6333, F6600 - F6653, F6700 - F6701 • SYSTEM MESSAGES F2050-F2099, F2450, F2750 - F2752, F4352 - F4399, F4400 - F4419, F4450 - F4457, F4500 - F4509, F6103 - F6198, F6200 - F6298, F6300 - F6333,...
  • Page 87 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class Redundancy lost: F8025 / F8026 (pow fail redund loss/back ac/dc sys) F8029 / F8030 (pow fail redund loss/back dc/dc sys) • Major alarm: Mains power failure: F8010 / F8011 (pow fail start/end) F8023 / F8024 (pow fail start/end AC/DC sys) F8027 / F8028 (pow fail start/end DC/DC sys) •...
  • Page 88 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class • MAJOR alarm: F2114 (hw fatal err) / F2105 (fatal err) / F2109 (appl fatal err) • Alarm escalation to a MINOR alarm or if a MINOR alarm already exists, to a MAJOR alarm: F2104 (unix err escal) / F2108 (appl err escal) / F2113 (hw err escal er) •...
  • Page 89 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class CENTRAL:030 SWITCHING UNIT FAILURE This alarm is signaled by the dependability system in the ADP if loss of connection to the active CC has been identified for a period exceeding the soft restart time of the CC (valid only for the 600 ECX model). In this situation, the CC software can no longer control the hardware contact/LED for the ALUM (or Trunk failure transfer TFT).
  • Page 90 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class F5915, F5750, F5470 - F5472 IMPORTANT: In contrast to the central alarms, the error counter and the threshold values for this alarm are not absolute values but percentage values. The error counter performs its calculations on the basis of the faulty IP connections and the configured IP connections.
  • Page 91 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class CENTRAL:035 HW DEFECT This alarm indicates a fatal hardware error in the environment of the central processor boards. At present, only the fans of the PCI systems are monitored. Assignment to error messages: F7084 Alarm criteria:...
  • Page 92 alarmkon.fm Alarm concept Nur für den internen Gebrauch Central alarm class • The alarm is controlled by the above-mentioned error messages. • A major alarm is set when the Access Point Emergency Shelf has assumed control over at least one access point.
  • Page 93 alarmkon.fm Nur für den internen Gebrauch Alarm concept Central alarm class • The encryption problem status (i.e.: type of active encryption problems) can be displayed with AMO-UCSU, AMO-BCSU and AMO-SDSU for the given CGW/NCUI board or IP trunk. IMPORTANT: Since there is only one alarm for all encryption problems and they might happen simultaneously, the error log has to be checked for all related error messages! Each encryption problem has to be checked and solved before manual reset of the alarm by AMO.
  • Page 94 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU-specific alarm classes 5.14 SWU-specific alarm classes This alarm class indicates failure of the SWU periphery, i.e. terminals and connection lines (CO/TIE), as well as SWU periphery boards. These alarms are administered with the AMO VADSU. The alarm type, DEVICE ALARM, can be activated for all SWU alarm classes.
  • Page 95 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU periphery alarm class of service (i.e. status is UNACH / UNACHA), the alarm count is incremented by the number of terminals which have been put out of service. Conversely, the alarm count is decremented by the number of terminals put back into service.
  • Page 96 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU periphery alarm class 5.15.1 Table of SWU periphery alarm Alarm number Alarm name Threshold value and validation time Messa MINOR MAJOR MINOR MAJOR DEVICE priorit ALARM ALARM ALARM ALARM ALARM (percent) (percent) (seconds) (seconds)
  • Page 97 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU periphery alarm class Assignment to error messages: The assignments of error messages of the SWU periphery BOARD / CIRCUIT / terminal to the alarm classes are also dependent in the DH device type, i.e. in the case of a BOARD error message more than one alarm class may be assigned.
  • Page 98 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU periphery alarm class Device types for the boards required. • List: SWU-PER SWU-PER:001 TIE LINE This alarm is a summation alarm for indicating tie-trunk failures. Associated device types: DB_DH_DEV_TYP _QS_SIM " _QS_WES "...
  • Page 99 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU periphery alarm class " _SB_FKT_EG " _MULT_LINE_8 " _MULT_LINE_30 Device types for the boards required. • List: SWU-PER SWU-PER:003 ANALOG VOICE DEVICES This alarm is a summation alarm for indicating failures in the analog voice service. Associated device types: DB_DH_DEV_TYP _ANATE...
  • Page 100 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU periphery alarm class Device types for the boards required. • List: SWU-PER SWU-PER:006 C-O/EXCHANGE DATA LINE This alarm is a summation alarm for indicating failures of special data lines to a public switched data network. Associated device types: DB_DH_DEV_TYP _X21_NC...
  • Page 101 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU periphery alarm class SWU-PER:009 LOGICAL DEVICES This alarm is a summation alarm for indicating the failure of so-called logical or fictitious devices that do not have a physical module connection, for example as in the WAML2, SLMY. Failure of these modules is thus essentially monitored.
  • Page 102 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU periphery alarm class DB_DH_DEV_TYP _APSE_PSE " _APSE_PSM " _APSE_TE " _APSE_ELA " _APSE_DE " _APSE_ANSE_M " _APSE_ANSE_A _APSE_ANSE_S " _APSE_WKE Device types for the boards required. • List: SWU-PER SWU-PER:013 OTHER DEVICES This alarm is a summation alarm for indicating failures of DH device types, which cannot be assigned to specific alarm classes.
  • Page 103 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU periphery alarm class μ This alarm signals a summary of the failure of special resources (conversion resources) for converting A-Law/ Law and for echo cancellation. The CBMMs (Central Byte Manipulation Modules) are available on LTUCC and NCUI boards.
  • Page 104 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU periphery alarm class DB_DH_DEV_TYP_ Board DIG_M SLMB, (Set400) DIGITE SLMB, SLMB16, SLMD HAS_SCH TMBM HAS_WTK HAUSPOST SLMD TMBD, TMFS, DIUC, DIUC64 TMBD, DIUC, DIUC64 MSN_DEVICE SLMU, SLMQ, SLMS, STMD MULTI_LINE_30 DIUS2/VCM MULTI_LINE_8 SLMU, SLMQ, SLMS, STMD, VCM NW_ANALOG...
  • Page 105 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU logical alarm classes DB_DH_DEV_TYP_ Board TMFS_AMT TMFS, DIUC, DIUC64 TMGSR_GS TMGSR_SR TMLS DIUC, DIUC64, TMBLN, TMEMW, TMACH, TMAG, TMAU, TMAS, TMAS8, TMEDG, TMGSR, TMCOW, TMELS, TMGSR, TMLRW, TMLBL,TMEMW, TMLRS, TMLRW, TMLRP, TMLSF, TMLSL, TMLSR, TMN2S TMX21 TMX21 TMX21PPH...
  • Page 106 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU logical alarm classes supervision of important devices (see AMO VADSU). (see AMO VADSU). The NMC alarms ’INWARD TRUNK/EX-LINE’ and ’OUTWARD TRUNK/EX-LINE’ control the TFT (trunk failure transfer) switch-over. Board alarms 8 - 519 shared with directional alarms The board alarms offer variable PEN-assignment for each peripheral board and for each LTU/Access Point (AP).
  • Page 107 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU logical alarm classes 5.16.1 Table of SWU logical device alarms Alarm number Alarm name Threshold value and validation time Mess MINOR MAJOR MINOR MAJOR DEVICE priori ALARM ALARM ALARM ALARM ALARM (percent) (percent) (seconds)
  • Page 108 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU logical alarm classes • Alarm classes • Evaluating the alarm mirror 5.16.2 Special alarms The alarm type, DEVICE ALARM, can be activated for all SWU alarm classes. Examples: A9010 M4 N1001 NO ACT NMCALARM MIRROR: SWU-LOG GRP 94-04-19 13:58:45 DEVICE-ALARM:...
  • Page 109 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU logical alarm classes See also • Alarm classes • Evaluating the alarm mirror A9000 F1000 F2000 F3000 F4000 F5000 F6000 F7000 F8000 SWU-LOG:000 OTHER DEVICES Any dummy devices or unknown devices configured at the PABX will be assigned the OTHER DEVICES alarm. The OTHER DEVICES alarm is not output.
  • Page 110 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU logical alarm classes This special alarm is the Italian variant of the exchange line alarm. It specifically indicates failure of the DIUC exchange lines. The trunk failure transfer may only take place if this alarm is triggered and all DIUC exchange lines are out of service.
  • Page 111 alarmkon.fm Nur für den internen Gebrauch Alarm concept SWU logical alarm classes 112222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222 22222222223333333333333333 MINOR-ALARM: 112222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222 22222222223333333333333333 MAJOR-ALARM: 112222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222 22222222223333333333333333 0 ---------------------------------------------------------> -----------------------------------------------------------> ------------------------> 583 Fxxxx M4 N1769 xxxx ..xxx ..xxx xxxx xxxx ....01-10-29 14:51:41 ..ALARM-CLASS:SWU-LOG:008/010/203/404/405/519 See also: •...
  • Page 112 alarmkon.fm Alarm concept Nur für den internen Gebrauch SWU logical alarm classes 112222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222 22222222223333333333333333 MINOR-ALARM: 112222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222 22222222223333333333333333 MAJOR-ALARM: 112222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222 22222222223333333333333333 0 ---------------------------------------------------------> -----------------------------------------------------------> ------------------------> 583 Fxxxx M4 N1769 xxxx ..xxx ..xxx xxxx xxxx ....01-10-29 14:51:41 ..ALARM-CLASS:SWU-LOG:520/510/513/583 See also: •...
  • Page 113 alarmkon.fm Nur für den internen Gebrauch Alarm concept SM periphery alarm class Based on this board-alarm assignment the board alarms will be set or reset according to the state transitions of the proper peripheral boards or LTUs/APs. Only the given level (LTU or board) will be considered in the alarm evaluation and the subordinate units (e.g.: trunks) not.
  • Page 114 alarmkon.fm Alarm concept Nur für den internen Gebrauch SM periphery alarm class • List of alarms: SM-PER • Alarm classes • Evaluating the alarm mirror 5.17.1 Table SM periphery alarms Alarm number Alarm name Threshold value and validation time Messa MINOR MAJOR MINOR...
  • Page 115 alarmkon.fm Nur für den internen Gebrauch Alarm concept SM periphery alarm class • Description of SM periphery alarms • List of alarms: SM-PER • Alarm classes • Evaluating the alarm mirror 5.17.2 Description of SM periphery alarms The following alarm criteria apply to the server periphery alarms: •...
  • Page 116 alarmkon.fm Alarm concept Nur für den internen Gebrauch SM periphery alarm class SM-PER:004 SM-PER:005 SM-PER:006 SM-PER:007 SM-PER:008 SM-PER:009 SM-PER:010 SM-PER:011 SM-PER:012 SM-PER:013 SM-PER:014 SM-PER:015 SM-PER:016 SM-PER:017 SM-PER:018 SM-PER:019 SM-PER:020 SM-PER:021 SM-PER:022 SM-PER:023 See also: • Alarm classes • Evaluating the alarm mirror A9000 F1000 F2000...
  • Page 117 alarmkon.fm Nur für den internen Gebrauch Alarm concept SM periphery alarm class • List: SM-PER SM-PER:005 SERVICE XENIX This alarm is a summation alarm for indicating failures of server channels, for which the CMS service XENIX is configured, e.g. ETD or even NMC / DMS. The channels usually link the server to special terminals. •...
  • Page 118 alarmkon.fm Alarm concept Nur für den internen Gebrauch SM periphery alarm class This alarm is not yet in use. • List: SM-PER SM-PER:012 Not used This alarm is not yet in use. • List: SM-PER SM-PER:013 Not used This alarm is not yet in use. •...
  • Page 119 alarmkon.fm Nur für den internen Gebrauch Alarm concept Alarm signaling This alarm indicates failures of the hard disk drive of the ADS. • List: SM-PER SM-PER:019 IS CARTRIDGE This alarm indicates failures of the cartridge drive of the ADS. • List: SM-PER SM-PER:020...
  • Page 120 alarmkon.fm Alarm concept Nur für den internen Gebrauch Alarm signaling E9:The alarm message is assigned the message priority that was configured with AMO SIGNL for the alarm number. However, alarm messages with this message priority are not output to AFR1 (Remote Service Platform (RSP)).
  • Page 121 LogM database PM_DATABASE_THRESHOLD threshold reached in the PM database IMPORTANT: Thresholds can be set via SNMP in dbThreshold group of the OpenScape 4000/HiPath 4000 MIB. OpenScape 4000/HiPath 4000 Manager backup alarms HBR_DATA_BACKUP data backup failed In case of logical backup fails the alarms have the format HBR_LOGICAL_BACKUPUNIT e.g.
  • Page 122 License Management generates alarms based on the state of port counters and theirs thresholds. DISK_SATURATION_THRESHOLD Threshold on one of the monitored partitions is reached. IMPORTANT: Partition thresholds can be set via SNMP in fileSysTable of the OpenScape 4000/HiPath 4000 MIB. A31003-H3100-S104-14-7620, 11/2015...
  • Page 123 SNMPprox.fm Nur für den internen Gebrauch Enhanced Alarms Generated on the Manager A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 124 hista_sicherung.fm HISTA backup measures Nur für den internen Gebrauch 7 HISTA backup measures Structure and organization of the HISTA database The error message database of the HISTA function consists of 20 file pairs and a control file. :AMD:HISTORY/INIT :AMD:HISTORY/TEXT01 :AMD:HISTORY/INFO01 :AMD:HISTORY/TEXT20 :AMD:HISTORY/INFO20 The pairs are overwritten cyclically, i.e.
  • Page 125 hista_sicherung.fm Nur für den internen Gebrauch HISTA backup measures customer decides to initiate the data transfer himself via the DMS file transfer function. The transmission of the database can either be carried out via remote file transfer, or with the START-COPY AMO and even with the HISTA AMO (START-HISTA:SEARCH,...).
  • Page 126 bk_error9000.fm Error messages Nur für den internen Gebrauch A9000 8 Error messages Alarm and Error Messages A9000 F1000 F2000 F3000 F4000 F5000 F6000 F7000 F8000 8.1 A9000 A9000 -- F1000 F2000 F3000 F4000 F5000 F6000 F7000 F8000 A9000 A9001 A9002 A9003 A9006 A9007...
  • Page 127 bk_error9000.fm Nur für den internen Gebrauch Error messages A9000 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 128 a9000.fm Nur für den internen Gebrauch A9000 NMCALARM MINOR ALARM ON Cause: Service-Specific (Format 2C) Short text: Alarm Message Cause: Low-priority alarm is set. Action: Save error message data and contact your Next level of support. The device class affected is output in the ALARM-CLASS line. In addition, the individual alarm affected is output in the line ALARM NAME.
  • Page 129 a9001.fm Nur für den internen Gebrauch A9001 NMCALARM MAJOR ALARM ON Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: High-priority alarm is set. Action: The device class affected is output in the DEV-CLASS line. Action: Save error message data and contact your Next level of support.
  • Page 130 a9002.fm Nur für den internen Gebrauch A9002 NMCALARM MINOR ALARM OFF Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: Low-priority alarm has been reset. Action: Positive acknowledgment of A9000, no action necessary. See also: Chapter 5, “Alarm concept”. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 131 a9003.fm Nur für den internen Gebrauch A9003 NMCALARM MAJOR ALARM OFF Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: High-priority alarm has been reset. Action: Positive acknowledgment of A9001, no action necessary. See also: Chapter 5, “Alarm concept”. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 132 a9006.fm Nur für den internen Gebrauch A9006 NMCALARM DEVICE ALARM ON Type: Service-Specific (Format 2C) Short text: Alarm message Cause: DEVICE ALARM was introduced for monitoring vital system components (e.g. lines). The system reports a failure of the system component(s) being monitored. Action: Save error message data and contact your Next level of...
  • Page 133 a9007.fm Nur für den internen Gebrauch A9007 NMCALARM DEVICE ALARM OFF Type: Service-Specific (Format 2C) Short text: Alarm message Cause: DEVICE ALARM has been reset. Action: Positive acknowledgment of A9006, no action necessary. See also: Chapter 5, “Alarm concept”. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 134 a9008.fm Nur für den internen Gebrauch A9008 NMCALARM MIRROR: CENTRAL GRP Type: Service relevant (Format 30) Short text: Alarm messages Cause: This alarm message is displayed after every module restart or switch. The alarm message contains the alarm mirror for all central SWU or SM (ADP) alarms. Action: Save error message data and notify your Next level of...
  • Page 135 a9009.fm Nur für den internen Gebrauch A9009 NMCALARM MIRROR: SWU-PER GRP Type: Service relevant (Format 30) Short text: Alarm messages Cause: The alarm message is displayed after every module restart or switch. This alarm message contains the alarm mirror for all SWU periphery alarms. Action: Save error message data and notify your Next level of...
  • Page 136 a9010.fm Nur für den internen Gebrauch A9010 NMCALARM MIRROR: SWU-LOG GRP Type: Service-Specific (Format 30) Short text: Alarm Message Cause: This alarm message is output after each functional system unit restart or switchover. Alarm mirror for all the logical alarms of the SWU (SWU-LOG). Action: Save error message data and contact your Next level of...
  • Page 137 a9011.fm Nur für den internen Gebrauch A9011 NMCALARM MIRROR: SM-PER GRP Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: This alarm message is output after each functional system unit restart or switchover. Alarm mirror for all the peripheral alarms of the server/ADP (SM-PER). Action: Save error message data and contact your Next level of...
  • Page 138 a9012.fm Nur für den internen Gebrauch A9012 NMCALARM PER-MIR: CENTRAL GRP Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: Alarm mirror requested via AMO GRA or external NMC/DMS command. Alarm mirror for all the central alarms of the SWU (CENTRAL) or server/ADP. Action: See AMO GRA.
  • Page 139 a9013.fm Nur für den internen Gebrauch A9013 NMCALARM PER-MIR: SWU-PER GRP Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: Alarm mirror requested via AMO GRA or external NMC/DMS command. Alarm Mirror alarm for all the peripheral alarms of the SWU (SWU-PER). Action: See AMO GRA.
  • Page 140 a9014.fm Nur für den internen Gebrauch A9014 NMCALARM PER-MIR: SWU-LOG GRP Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: Alarm mirror requested via AMO GRA or external NMC/DMS command. Alarm mirror for all the logical alarms of the SWU (SWU-PER). Action: See AMO GRA.
  • Page 141 a9015.fm Nur für den internen Gebrauch A9015 NMCALARM PER-MIR: SM-PER GRP Type: Service-Specific (Format 2C) Short text: Alarm Message Cause: Alarm mirror requested via AMO GRA or external NMC/DMS command. Alarm mirror for all the peripheral alarms of the server/ADP (SM-PER). Action: See AMO GRA.
  • Page 142 bk_error1000.fm Nur für den internen Gebrauch F1000 8.2 F1000 A9000 -- F1000 -- F2000 F3000 F4000 F5000 F6000 F7000 F8000 F1010 F1020 F1030 F1040 F1050 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 143 bk_error1000.fm Nur für den internen Gebrauch F1000 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 144 f1010.fm Nur für den internen Gebrauch F1010 SIT: The error number F1010 was output several times with different texts. CMD-OPCODE UNKNOWN Type: Service-relevant (Format 16) Short text: Message from AMO to SIT Cause: This message is output in the case of a message from an AMO to the signaling task. Action: If this error message occurs frequently, save the error message data and contact your Next level of...
  • Page 145 f1010.fm Nur für den internen Gebrauch EVT-STATE NOT DEFINED Type: Service-relevant (Format 16) Short text: Event state unknown Cause: The event state assigned in the ADS database of the error class is unknown to the signaling task. The relevant error message is output as a hexadecimal value. Action: Save error message data and contact your Next level of...
  • Page 146 f1010.fm Nur für den internen Gebrauch NO END INITIALIZATION Type: Service-relevant (Format 00) Short text: No end-of-initialization acknowledgement Cause: The signaling task waits until all jobs in the operating system have registered the end of initialization.Only then is the hypen added in the DP display. Action: Save error message data and contact your Next level of...
  • Page 147 f1010.fm Nur für den internen Gebrauch NO SHELF-DATA FOR CC Type: Service-relevant (Format 00) Short text: Frame description data not loaded Cause: The frame description data for the relevant frame type was not loaded. Effect: No mounting pitch display for central module. The cabinet type and frame type file may be damaged or unavailable. Action: Check data with AMO CONSY (DISP-CONSY and REGEN-CONSY).
  • Page 148 f1010.fm Nur für den internen Gebrauch PABX 80 Type: Service-relevant (Format 00) Short text: Configuration data Cause: The extension level is determined on the basis of the configuration data. Effect: Central module data is wrongly interpreted if the extension level is incorrect or unknown. The error message is generated with an N for note after every restart.
  • Page 149 f1010.fm Nur für den internen Gebrauch PABX 3000 Type: Service-relevant (Format 00) Short text: Configuration data Cause: The extension level is determined on the basis of the configuration data. Effect if the extension level is incorrect or unknown: the central module data is incorrectly interpreted. The error message is generated with an N for note after every restart.
  • Page 150 f1010.fm Nur für den internen Gebrauch SOURCE TASK UNKNOWN Type: Service-relevant (Format 16) Short text: Task sender unknown Cause: The signaling task receives a message whose sender is unknown. The relevant message is output as hex data. Action: Save error message data and contact your Next level of support.
  • Page 151 f1010.fm Nur für den internen Gebrauch LOAD MEDIA NOT RMX HD Type: Service-relevant Short text: Load device is not a RMX hard disk Cause: Load device cannot be detected as RMX hard disk. Action: Search for further relevant error messages and check load device! DEFINE WITH AMO CONSY Type: Service-relevant...
  • Page 152 f1010.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 153 f1020.fm Nur für den internen Gebrauch F1020 SIT: MESSAGE CLASS NOT DEFINED Type: Diagnosis-specific (Format 25) Short text: Subevent not assigned to event Cause: The signaling task received a message whose subevent could not be assigned to the appropriate event. The relevant message is output in the HEX data. Action: Save HISTO file and contact your Next level of...
  • Page 154 f1030.fm Nur für den internen Gebrauch F1030 SIT: MESSAGE IMPLAUSIBLE Type: Diagnosis-specific (Format 25) Short text: Error message class not in permitted range Cause: The signaling task has received a message whose error class is not within the range of the DB_M_RS_EVT_SET.
  • Page 155 f1040.fm Nur für den internen Gebrauch F1040 SIT: EVENT NOT DEFINED Type: Diagnosis-specific (Format 16) Short text: Error message class not initialized Cause: The signaling task has received a message whose error class has not yet been initialized. The relevant message is output in the HEX data. Action: Save HISTO file and contact your Next level of...
  • Page 156 f1050.fm Nur für den internen Gebrauch F1050 SIT: SUB-EVENT NOT DEFINED Type: Diagnosis-specific (Format 00) Short text: Subevent not defined Cause: The signaling task has received a message whose subevent is not defined. The relevant message is output in the HEX data. Action: Save HISTO file and contact your Next level of...
  • Page 157 bk_error2000.fm Nur für den internen Gebrauch F2000 8.3 F2000 A9000 F1000 -- F2000 -- F3000 F4000 F5000 F6000 F7000 F8000 F2000 F2001 F2002 F2003 F2004 F2005 F2006 F2007 F2008 F2009 F2010 F2012 F2013 F2014 F2016 F2018 F2019 F2022 F2023 F2024 F2025 F2026 F2027...
  • Page 158 f2000.fm Nur für den internen Gebrauch F2000 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: Save error message data and log file. Contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 159 f2001.fm Nur für den internen Gebrauch F2001 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Wrong event code Cause: Event code valid but not allowed. Action: Save error message data and log file. contact your Next level of support.
  • Page 160 f2002.fm Nur für den internen Gebrauch F2002 IMPLAUSIBLE STATE Type: Diagnosis-specific (several formats apply) Short text: Implausible state Cause: Implausible state. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 161 f2003.fm Nur für den internen Gebrauch F2003 UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Data not expected in current state. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 162 f2004.fm Nur für den internen Gebrauch F2004 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 163 f2005.fm Nur für den internen Gebrauch F2005 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible return value received from a procedure. Action: Save error message data and log file. contact your Next level of support.
  • Page 164 f2006.fm Nur für den internen Gebrauch F2006 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in procedure call. Action: Save error message data and log file. contact your Next level of support.
  • Page 165 f2007.fm Nur für den internen Gebrauch F2007 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Error in the database. Implausible data for database access. Reaction is a soft restart. Action: Check that the PABX completes its restart. Save error message data and log file. contact your Next level of support.
  • Page 166 f2008.fm Nur für den internen Gebrauch F2008 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (static data) in memory. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 167 f2009.fm Nur für den internen Gebrauch F2009 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 168 f2010.fm Nur für den internen Gebrauch F2010 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Negative exception code in operating system call. There may be insufficient memory for executing the AMO during peak load periods, the executed AMO may contain an error or it may be damaged. This error message is also displayed when the operating system is damaged.
  • Page 169 f2012.fm Nur für den internen Gebrauch F2012 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 170 f2013.fm Nur für den internen Gebrauch F2013 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible message header. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 171 f2014.fm Nur für den internen Gebrauch F2014 DMS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative acknowledgments by the data management system Cause: Negative acknowledgments by the data management system (e.g. I/O error). Action: Save error message data and log file. contact your Next level of support.
  • Page 172 f2016.fm Nur für den internen Gebrauch F2016 ADVISORY Type: Diagnosis-specific (several formats apply) Short text: Advisory message Cause: Advisory message Action: If this error occurs repeatedly, save the error message data and contact your Next level support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 173 f2018.fm Nur für den internen Gebrauch F2018 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 174 f2019.fm Nur für den internen Gebrauch F2019 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The OS has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 175 f2022.fm Nur für den internen Gebrauch F2022 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 176 f2023.fm Nur für den internen Gebrauch F2023 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 177 f2024.fm Nur für den internen Gebrauch F2024 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 178 f2025.fm Nur für den internen Gebrauch F2025 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 179 f2026.fm Nur für den internen Gebrauch F2026 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 180 f2027.fm Nur für den internen Gebrauch F2027 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. 1.
  • Page 181 f2028.fm Nur für den internen Gebrauch F2028 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F2027.
  • Page 182 f2029.fm Nur für den internen Gebrauch F2029 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 183 f2029.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 184 f2031.fm Nur für den internen Gebrauch F2031 OBJM INCONSISTENT Type: Diagnosis-specific (Format 01) Short text: Objects in OS System Catalog inconsistent Cause: Due to preceeding faults it may happen that a data processor (ADP, BPA or BPB) may get a request from the OS of a partner processor to update a specific entry in the Name- or Index- Systemcatalog which already holds an other, different object token.
  • Page 185 f2032.fm Nur für den internen Gebrauch F2032 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 186 f2033.fm Nur für den internen Gebrauch F2033 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 187 f2034.fm Nur für den internen Gebrauch F2034 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the OS Task Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. For example, stack messages with the same message ID may exist (F2016).
  • Page 188 f2035.fm Nur für den internen Gebrauch F2035 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. The hard disk may be faulty or the system program is not available or it is faulty. Action: Check that the PABX has restarted.
  • Page 189 f2036.fm Nur für den internen Gebrauch F2036 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 190 f2037.fm Nur für den internen Gebrauch F2037 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 191 f2038.fm Nur für den internen Gebrauch F2038 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 192 f2039.fm Nur für den internen Gebrauch F2039 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 193 f2040.fm Nur für den internen Gebrauch F2040 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 194 f2041.fm Nur für den internen Gebrauch F2041 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 195 f2042.fm Nur für den internen Gebrauch F2042 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 196 f2045.fm Nur für den internen Gebrauch F2045 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 197 f2048.fm Nur für den internen Gebrauch F2048 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 198 f2050.fm Nur für den internen Gebrauch F2050 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 199 f2051.fm Nur für den internen Gebrauch F2051 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Wrong event code Cause: Event code valid but not allowed. Action: Save error message data and log file. contact your Next level of support.
  • Page 200 f2052.fm Nur für den internen Gebrauch F2052 IMPLAUSIBLE STATE Type: Diagnosis-specific (several formats apply) Short text: Implausible state Cause: Implausible state. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 201 f2053.fm Nur für den internen Gebrauch F2053 UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Data not expected in current state. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 202 f2054.fm Nur für den internen Gebrauch F2054 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 203 f2055.fm Nur für den internen Gebrauch F2055 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible return value received from a procedure. Action: Save error message data and log file. contact your Next level of support.
  • Page 204 f2056.fm Nur für den internen Gebrauch F2056 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in procedure call. Action: Save error message data and log file. contact your Next level of support.
  • Page 205 f2057.fm Nur für den internen Gebrauch F2057 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data for database access. Reaction is a soft restart. Action: Check that the PABX completes its restart. Save error message data and log file. contact your Next level of support.
  • Page 206 f2058.fm Nur für den internen Gebrauch F2058 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (static data) in memory. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 207 f2059.fm Nur für den internen Gebrauch F2059 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 208 f2060.fm Nur für den internen Gebrauch F2060 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Negative exception code in operating system call. There may be insufficient memory for executing the AMO during peak load periods, the executed AMO may contain an error or it may be damaged. This error message is also displayed when the operating system is damaged.
  • Page 209 f2062.fm Nur für den internen Gebrauch F2062 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 210 f2063.fm Nur für den internen Gebrauch F2063 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible message header. Action: Save error message data and log file. contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 211 f2064.fm Nur für den internen Gebrauch F2064 DMS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative acknowledgments by the data management system Cause: Negative acknowledgments by the data management system (e.g. I/O error). Action: Save error message data and log file. contact your Next level of support.
  • Page 212 f2066.fm Nur für den internen Gebrauch F2066 ADVISORY Type: Diagnosis-specific (several formats apply) Short text: Advisory message Ursache: Advisory message from administration and maintenance. In the case of the error message text PFS CHECK TASK: FEATURE COUNT ERROR it was established that the number of station / trunks set up does not correspond to the station / trunks ascertained by this task (possibly due to a modified database).
  • Page 213 f2068.fm Nur für den internen Gebrauch F2068 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 214 f2069.fm Nur für den internen Gebrauch F2069 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The AM has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 215 f2072.fm Nur für den internen Gebrauch F2072 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 216 f2073.fm Nur für den internen Gebrauch F2073 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 217 f2074.fm Nur für den internen Gebrauch F2074 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 218 f2075.fm Nur für den internen Gebrauch F2075 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 219 f2076.fm Nur für den internen Gebrauch F2076 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 220 f2077.fm Nur für den internen Gebrauch F2077 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. a.
  • Page 221 f2078.fm Nur für den internen Gebrauch F2078 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F2027.
  • Page 222 f2079.fm Nur für den internen Gebrauch F2079 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 223 f2080.fm Nur für den internen Gebrauch F2080 TIME / DATE NOT VALID Type: Diagnosis-specific (Format 01) Short text: Check reference clock Cause: Error when processing the reference clock. Error only occurs in the ADS. Action: The exception code is output in the HEX data and may have the following meaning: H20 = TIME_NOT_VALID (Clock defective) H21 = MAC_NOT_READY (MAC board defective) H22 = BAT_OFF (Check date/time or support battery in the MAC/IOPA)
  • Page 224 f2082.fm Nur für den internen Gebrauch F2082 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 225 f2083.fm Nur für den internen Gebrauch F2083 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 226 f2084.fm Nur für den internen Gebrauch F2084 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the root job Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. Save error message data and contact your Next level of support.
  • Page 227 f2085.fm Nur für den internen Gebrauch F2085 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. The hard disk may be faulty or the system program is not available or it is faulty. Action: Check that the PABX has restarted.
  • Page 228 f2086.fm Nur für den internen Gebrauch F2086 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 229 f2087.fm Nur für den internen Gebrauch F2087 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 230 f2088.fm Nur für den internen Gebrauch F2088 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 231 f2089.fm Nur für den internen Gebrauch F2089 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 232 f2090.fm Nur für den internen Gebrauch F2090 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 233 f2091.fm Nur für den internen Gebrauch F2091 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 234 f2092.fm Nur für den internen Gebrauch F2092 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 235 f2095.fm Nur für den internen Gebrauch F2095 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 236 f2098.fm Nur für den internen Gebrauch F2098 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 237 f2100.fm Nur für den internen Gebrauch F2100 MESSAGE Type: Service-specific (Format 17) Short text: XENIX error Cause: The following tables contain possible error messages which are divided into: Panic messages Messages with formats such as >panic: Out of swap< denote serious errors which lead to a restart of the XENIX Other messages During XENIX operation, error messages which denote input errors or errors in the application programs may also be output.
  • Page 238 f2101.fm Nur für den internen Gebrauch F2101 ERROR Type: Service-specific (Format 17) Short text: Total Failure of XENIX Cause: Total failure of XENIX OS in the server. XENIX carries out a "REBOOT", i.e. the OS is reloaded from the hard disk. Action: Save error message data and contact your Next level of...
  • Page 239 f2102.fm Nur für den internen Gebrauch F2102 UNIX MESSAGE Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX advisory message Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 240 f2103.fm Nur für den internen Gebrauch F2103 UNIX ERROR Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX error message Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 241 f2104.fm Nur für den internen Gebrauch F2104 UNIX ERROR ESCAL Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX error message (with NMC minor alarm) Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 242 f2105.fm Nur für den internen Gebrauch F2105 UNIX FATAL ERROR Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX error message (with NMC major alarm) Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 243 f2106.fm Nur für den internen Gebrauch F2106 UNIX APPL MESSAGE Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX application advisory message Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 244 f2107.fm Nur für den internen Gebrauch F2107 UNIX APPL ERROR Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX application error message Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 245 f2108.fm Nur für den internen Gebrauch F2108 UNIX APPL ERROR ESCAL Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX application error message (with NMC minor alarm) Action: Save error message data and contact your Next level of support.
  • Page 246 f2109.fm Nur für den internen Gebrauch F2109 UNIX APPL FATAL ERROR Type: Service-specific (Format 17) Short text: Error in UNIX application Cause: UNIX application error message (with NMC major alarm) Action: Save error message data and contact your Next level of support.
  • Page 247 f2110.fm Nur für den internen Gebrauch F2110 SW RESET ALARM Type: Service-specific (Format 3A) Short text: NMC / DMS alarm level reset Cause: The NMC alarm level for the UNIX SW will be reset in this UNIX server. This message is sent by the UNIX loader or by the uninterruptible power supply.
  • Page 248 f2111.fm Nur für den internen Gebrauch F2111 HW MESSAGE Type: Service-specific (Format 3A) Short text: Hardware error Cause: HW warning issued by the UNIX server. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 249 f2112.fm Nur für den internen Gebrauch F2112 HW ERROR Type: Service-specific (Format 3A) Short text: Hardware error Cause: The UNIX server detected a minor HW error. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 250 f2113.fm Nur für den internen Gebrauch F2113 HW ERROR ESCAL Type: Service-specific (Format 3A) Short text: Hardware error Cause: A minor error in the UNIX server has escalated to a major HW error. This measure is taken by the uninterruptible power supply. Action: Save error message data and contact your Next level of...
  • Page 251 f2114.fm Nur für den internen Gebrauch F2114 HW FATAL ERROR Type: Service-specific (Format 3A) Short text: Hardware error Cause: The UNIX server detected a major HW error. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 252 f2115.fm Nur für den internen Gebrauch F2115 HW RESET ALARM Type: Service-specific (Format 3A) Short text: NMC / DMS alarm level reset Cause: The NMC alarm level for the UNIX HW will be reset in this UNIX server. This message is sent by the UNIX loader or by the uninterruptable power supply. Action: Save error message data and contact your Next level of...
  • Page 253 f2115.fm Nur für den internen Gebrauch panic: Segment Not Present Segment not present. panic: Stack fault Stack overflow. panic: Timeout table overflow Internal table overflow. Can be caused by bad applications. panic: Trap in system Processor interrupt. panic: unknown interrupt Error in the XENIX OS (interrupt handling).
  • Page 254 f2115.fm Nur für den internen Gebrauch ctopen: hsndmp reserve ct failed The cartridge could not be opened. Error in communication between RMX and XENIX. ctopen: support task mailbox not found Cartridge could not be opened. Error in communication between RMX and XE- NIX.
  • Page 255 f2200.fm Nur für den internen Gebrauch F2200 PROC INT REGISTER Type: Diagnosis-specific (Format 2B) Short text: Interrupt message Cause: Interrupt message with output of registers and stack links. Action: See SW Systems Service. Save error message data and contact your Next level of support.
  • Page 256 f2201.fm Nur für den internen Gebrauch F2201 PROC INT STACK Type: Diagnosis-specific (Format 14) Short text: Interrupt message Cause: Output of stack at time of interrupt. This message is output before the actual message (F2200). Action: See SW Systems Service. Save error message data and contact your Next level of support.
  • Page 257 f2202.fm Nur für den internen Gebrauch F2202 PROC INT ESCALATION Type: Diagnosis-specific (Format 2C) Short text: Escalation error following multiple INT13 in Call Processing Cause: This message only applies to US Rel.6.4. If a predefined number of protection errors is exceeded by Call Processing, Sysload requests a soft restart instead of the usual TOP stack clean-up.
  • Page 258 f2203.fm Nur für den internen Gebrauch F2203 PROC INT TASK ADDRESS Type: Diagnosis-specific (Format 14) Short text: Output of Running Task Address Cause: Interrupt caused by task. The user address and stack pointer are indicated in the main part of the message. The auxiliary data contains the start address of the running task at the time of the interrupt. Action: No action necessary.
  • Page 259 f2204.fm Nur für den internen Gebrauch F2204 PROC INT INFO TEMPORARY SUSY Type: Diagnosis-specific (Format 17) Short text: Error in temporary subsystem Cause: Interrupt caused by temporary subsystem. The auxiliary data indicates the selector and limit of the data and code segments of the subsystem concerned. Action: Save error message data and contact your Next level of...
  • Page 260 f2205.fm Nur für den internen Gebrauch F2205 PROC INT DIVIDE ERROR Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Divide Error (INT 0) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 261 f2206.fm Nur für den internen Gebrauch F2206 PROC INT DEBUG ERROR Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Debugger call (INT 1) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 262 f2207.fm Nur für den internen Gebrauch F2207 PROC INT Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: NMI (INT 2) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 263 f2208.fm Nur für den internen Gebrauch F2208 PROC INT BREAKPOINT Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Breakpoint (INT 3) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 264 f2209.fm Nur für den internen Gebrauch F2209 PROC INT OVERFLOW Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: INTO-Detected Overflow (INT 4) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 265 f2210.fm Nur für den internen Gebrauch F2210 PROC INT BOUND ERROR Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Bound Range Exceeded (INT 5) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 266 f2211.fm Nur für den internen Gebrauch F2211 PROC INT INVALID OPCODE Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Invalid Opcode (INT 6) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 267 f2212.fm Nur für den internen Gebrauch F2212 PROC INT COPROC NOT AVAILABLE Type: Diagnosis-specific (Format 2C Short text: Processor interrupt: Coprocessor Not Available (INT 7) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200.
  • Page 268 f2213.fm Nur für den internen Gebrauch F2213 PROC INT DOUBLE FAULT Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Double Fault (INT 8) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 269 f2214.fm Nur für den internen Gebrauch F2214 PROC INT COPROC SEG OVERRUN Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Coprocessor Segment Overrun (INT 9) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200.
  • Page 270 f2215.fm Nur für den internen Gebrauch F2215 PROC INT INVALID TSS Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Invalid Task State Segment (INT 10) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200.
  • Page 271 f2216.fm Nur für den internen Gebrauch F2216 PROC INT SEGMENT NOT PRESENT Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Segment Not Present (INT 11) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200.
  • Page 272 f2217.fm Nur für den internen Gebrauch F2217 PROC INT STACK EXCEPTION Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: Stack Exception (INT 12) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 273 f2218.fm Nur für den internen Gebrauch F2218 PROC INT GENERAL PROTECTION Type: Diagnosis-specific (Format 2C) Short text: Processor interrupt: General Protection (INT 13) Cause: Interrupt message with output of registers and stack links. Except for the subevent, this message is identical with F2200. It is assigned the interrupt name. Action: Save error message data and contact your Next level of...
  • Page 274 f2219.fm Nur für den internen Gebrauch F2219 PROC INT MULTIBUS TIMEOUT Type: Service-relevant (Format 27) Short text: Multibus timeout, bus cycle canceled due to time overflow. Cause: Sporadic defective components at the multibus or SW addressing error. System reaction: Soft restart Action: Save error message data and contact your Next level of support...
  • Page 275 f2224.fm Nur für den internen Gebrauch F2224 MAINTENANCE Type: Service-relevant (several formats relevant) Short text: Maintenance note, triggered by the alarm CENTRAL:029 MAINTENANCE NOTE. Cause: This message contains a transparent text in the rule that is either self-explanatory or refers to another chapter in the service manual. Action: In general, the above-mentioned alarm must be deleted with an AMO after fault removal:...
  • Page 276 f2244.fm Nur für den internen Gebrauch F2244 MAINTENANCE Type: Service-specific Short text: Service advisory message, initiated by the alarm CENTRAL:029 MAINTENANCE NOTE. Cause: This message usually consists of plain text, which is either self-explanatory or refers to a specific section of the Service Manual. Action: The MAINTENANCE NOTE alarm must always be reset (deleted) via AMO.
  • Page 277 f2250.fm Nur für den internen Gebrauch F2250 PROC INT COMMON MEMORY ALARM Type: Service-relevant (Format 27) Short text: Common memory alarm. Cause: Sporadic defective memory components or SW addressing error. System reaction: Reload. Action: If this error occurs repeatedly, replace the processor board. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 278 f2251.fm Nur für den internen Gebrauch F2251 PROC INT NMI PCI ERROR Type: Service-relevant (Format 47) Short text: Non Maskable Interrupt at the peripheral computer interface bus (PCI BUS) Cause: The CPU and the connected units, such as memory or hard disk, LAN controller, etc. are connected via the peripheral computer interface bus (PCI BUS).
  • Page 279 f2252.fm Nur für den internen Gebrauch F2252 PROC INT LOCAL MEMORY ERROR Type: Service-relevant (Format 47) Short text: Local memory error. Cause: Sporadic defective memory components or SW addressing error. System reaction: Reload. Action: If this error occurs repeatedly, replace the processor board. Interpretation of auxiliary data: see error message F3176.
  • Page 280 f2450.fm Nur für den internen Gebrauch F2450 SD Q OFL ******** (no subevent exists) Type: Diagnosis-specific (no format) Short text: Loss of error messages. Cause: The SIT of the ADP is unable to accept further error messages from SYSDEP (SIT mailbox overflow).
  • Page 281 f2750.fm Nur für den internen Gebrauch F2750 CP-MSG MC TRACE Type: Service-specific (Format 02) Short text: Call number traced Cause: This message outputs the tracing station (in message field f1) and the traced station or number (in message field f2). Action: Save error message data.
  • Page 282 f2751.fm Nur für den internen Gebrauch F2751 CP-MSG CO TRACE Type: (Format 2E) Short text: Trace job Cause: For INCOMING connections: A trace job printout is started by an internal user. The source exchange is prohibited from carrying out a forward release.
  • Page 283 f2752.fm Nur für den internen Gebrauch F2752 CP-MSG RELEASE DESPITE TRACE REQUEST Type: Service-specific (Format 2E) Short text: Release from trace hold status Cause: A line which is being held during tracing can be released by means of an AMO or by the destination exchange.
  • Page 284 f2753.fm Nur für den internen Gebrauch F2753 CP-MSG TRANSIT-/SATELLITE-COUNTER Type: Service-specific (Format 2E) Short text: Connection setup interrupted Cause: In order to avoid network loops or limit the number of paths in connections which are routed via satellite PABXs, the ISDN service maintains transit counters, which are incremented with each transit line seizure or satellite PABX path.
  • Page 285 f2754.fm Nur für den internen Gebrauch F2754 CP-MSG PIN TRACE Type: Service-specific (Format 34) Short text: Unauthorized PIN use detected Cause: This message allows unauthorized PIN users to be traced. This message is output if an invalid manual PIN is entered repeatedly at the same station. The maximum number of wrong PIN entry attempts has been exceeded (see AMO PERSI).
  • Page 286 f2755.fm Nur für den internen Gebrauch F2755 CP-MSG MSG WAIT CLR BY AMO Type: Service-specific (Format 31) Short text: ”Message Waiting” data deleted Cause: The administrator deleted the message waiting data via AMO SUBFT (message waiting is a R6.3 restart feature). A message is sent to Dependability via the call trace mechanism.
  • Page 287 f2756.fm Nur für den internen Gebrauch F2756 CPMSG TRACE Type: Diagnosis-relevant (Format 31) Short text: MCID or malicious call tracing of a PIN hacker. Cause: Malicious call tracing is a feature that can be activated with classes of service. It is used to log a malicious caller.
  • Page 288 bk_error3000.fm Nur für den internen Gebrauch F3000 8.4 F3000 A9000 F1000 F2000 -- F3000 -- F4000 F5000 F6000 F7000 F8000 F3000 F3002 F3004 F3008 F3010 F3011 F3050 F3059 F3100 F3101 F3102 F3103 F3104 F3106 F3108 F3109 F3110 F3150 F3151 F3153 F3155 F3157 F3158...
  • Page 289 bk_error3000.fm Nur für den internen Gebrauch F3000 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 290 f3000.fm Nur für den internen Gebrauch F3000 SWU-DP PARTNER NOT READY Type: Service-specific (Format 00) Short text: Standby partner failure Cause: Standby partner failure. Action: Replace partner data processor (DP). A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 291 f3002.fm Nur für den internen Gebrauch F3002 SWU-DP WD0 INT DEF Type: Service-specific (Format 18) Short text: Watchdog 0 INT test negative Cause: Watchdog 0 INT test negative Action: Replace DP. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 292 f3004.fm Nur für den internen Gebrauch F3004 SWU-DP WD1 INT DEF Type: (Format 18) Short text: Watchdog 1 INT test negative Cause: Watchdog 1 INT test negative Action: Replace DP. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 293 f3008.fm Nur für den internen Gebrauch F3008 SWU-DP MBTO INT DEF Type: Service-specific (Format 18) Short text: Multibus timeout Cause: Multibus timeout. Interrupt test negative. Action: Replace data processor (DP). A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 294 f3010.fm Nur für den internen Gebrauch F3010 SWU-DP NMI DEFECT Type: Service-specific (Format 18) Short text: Interrupt logic defective Cause: Interrupt logic defective Action: Replace DP. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 295 f3011.fm Nur für den internen Gebrauch F3011 SWU-DP CHKSUM ERROR Type: Service-specific (Format 22) Short text: Checksum error Cause: RTO detected a checksum error during system startup. A hard restart with a reload and a new checksum test are initiated. Action: Check that the PABX completes the restart.
  • Page 296 f3050.fm Nur für den internen Gebrauch F3050 SWU-MEM 1 BIT ERROR Type: Service-specific (Format 1D) Short text: 1-bit error Cause: 1-bit error, corrected in memory. Event signal came from routine test organization RTO (AMO FUNSU / MEM1AREQ). Action: Replace M2M board if necessary. The RTO can be temporarily deactivated with the FUNSU AMO (notify your Next level of support).
  • Page 297 f3059.fm Nur für den internen Gebrauch F3059 SWU-MEM PARITY ERROR Type: Service-specific (Format 1D) Short text: Parity error Cause: Parity error in board test by RTO (test only if RTO is activated via AMO FUNSU / MEMACEA or if a test is called up with AMO DIAG-TSU: CC, ... ). Word (2 bytes) 1 and 2 specify the corrupt memory cell as a basis / offset address (in accordance with the error address output of AMO TSU).
  • Page 298 f3100.fm Nur für den internen Gebrauch F3100 SWU-IP PROM ERROR Type: Service-specific (Format 1E/22) Short text: IP board defective Cause: Format 1E: PROM error. IP has found an internal error, but has booted and has reported this error. Replace IP board if error is repeated.
  • Page 299 f3101.fm Nur für den internen Gebrauch F3101 SWU-IP RAM ERROR Type: Service-specific (Format 1E/22) Short text: IP board defective Cause: Format 1E: RAM error. IP has found an internal error, but has booted and has reported this error. Event signal came from interface processor (IP). Format 22: Event signal came from routine test organization.
  • Page 300 f3102.fm Nur für den internen Gebrauch F3102 SWU-IP TIMER ERROR Type: Service-specific (Format 1E/22) Short text: IP board defective Cause: Format 1E: Timeout. IP has found an internal error, but has booted and has reported this error. Event signal came from interface processor (IP). Format 22: Event signal came from routine test organization.
  • Page 301 f3103.fm Nur für den internen Gebrauch F3103 SWU-IP FW ERROR Type: Service-specific (several formats apply) Short text: IP board defective Cause: Firmware error in interface processor (IP). Formats 1E and 22 are relevant to this message. In format 22, byte 1 contains HEX value ’EE for differentiation. The following is valid for format 1E: IP has found an internal error, but has booted and has reported this error.
  • Page 302 f3104.fm Nur für den internen Gebrauch F3104 SWU-IP Type: Service-specific (Format 22/29) Short text: IP board defective Cause: Bytes 0 and 1 contain information on the error (read in reverse order). Format 29: IP board is defective. Format 22: Event signal came from routine test organization. IP did not react to a status query. Action: Replace IP board if error is repeated.
  • Page 303 f3106.fm Nur für den internen Gebrauch F3106 SWU-IP IEC BUS DOWN Type: Service-specific (Format 22) Short text: IEC bus defective Cause: Error on IEC bus. Message after a soft restart. The error is evaluated by error analysis. Action: If the error persists after the restart, check the IEC bus cable and the IP boards. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 304 f3108.fm Nur für den internen Gebrauch F3108 SWU-IP HW ERROR Type: Service-specific (Format 1E/22) Short text: IP board defective. Format 1E: Hardware error. IP has found an internal error, but has booted and has reported this error. Event signal came from interface processor (IP). Format 22: Event signal came from routine test organization.
  • Page 305 f3109.fm Nur für den internen Gebrauch F3109 SWU-IP BACK ON-LINE Type: Service-specific (Format 29) Short text: IP board defective Cause: Slave interface processor (IP) has reported to master processor again. Event signal came from interface processor (IP). Action: If error occurs repeatedly, save the error message data and contact your Next level of support.
  • Page 306 f3110.fm Nur für den internen Gebrauch F3110 SWU-IP SLAVE IP DOWN Type: Service-specific (Format 22) Short text: IP board defective Cause: Slave interface processor is down. The error is evaluated by error analysis. Action: Check the connections between the IP boards. Replace IP board if error is repeated. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 307 f3150.fm Nur für den internen Gebrauch F3150 SWU-INT WATCHDOG 0 Type: Diagnosis-specific (several formats apply) Short text: Watchdog 0 timeout Cause: Repetitive error loop in high-priority task (between 0 and 34), OS deadlock, or WD0 task no longer being polled. Action: Save diagnosis data (stack messages and task information messages) and contact your Next level of...
  • Page 308 f3150.fm Nur für den internen Gebrauch Please also refer to the section entitled "SW/Interrupt/Stack message interpretation" A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 309 f3151.fm Nur für den internen Gebrauch F3151 SWU-INT WATCHDOG 1 Type: Diagnosis-specific (several formats apply) Short text: Watchdog 1 timeout Cause: Repetitive error loop in high-priority task (between 35 and 192). Action: Save diagnosis data (stack messages and task information messages) and contact your Next level of support.
  • Page 310 f3151.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 311 f3153.fm Nur für den internen Gebrauch F3153 SWU-INT MULTIBUS TIMEOUT Type: Diagnosis-specific (several formats apply) Short text: Timeout on multibus Cause: Format 28. Multibus user not responding or does not exist. Action: Save diagnosis data (stack messages and task information messages) and contact your Next level of support.
  • Page 312 f3155.fm Nur für den internen Gebrauch F3155 SWU-INT PARTNER INACTIVE Type: Diagnosis-specific (Format 00) Short text: Error in active controller Cause: Central error in the active controller. Non-active controller realizes that the active partner controller has reset the active line. Action: Save error message data and contact your Next level of...
  • Page 313 f3157.fm Nur für den internen Gebrauch F3157 SWU-INT 2BIT Type: Service-specific (several formats apply) Short text: 2-bit error Cause: 2-bit error Action: Switch off power and replace M2M board. Contact your Next level of support if this does not work. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 314 f3158.fm Nur für den internen Gebrauch F3158 SWU-INT DATA BLOCKED Type: Service-specific (Format 18) Short text: Non-maskable interrupt blocked (NMI) Cause: A non-maskable interrupt cannot be acknowledged.. Action: Switch off power and replace data processor. Contact your Next level of support if this does not work.
  • Page 315 f3159.fm Nur für den internen Gebrauch F3159 SWU-INT NO DATA Type: Service-specific (Format 18) Short text: No readable data (non-maskable interrupt has occurred) Cause: The data processor (DP) board may be defective. Action: Check DP board. Switch off power and replace if necessary. Contact your Next level of support if this does not work.
  • Page 316 f3171.fm Nur für den internen Gebrauch F3171 SWU-INT WD CLOCK Type: Service-specific (Format 18) Short text: Clock failure Cause: Failure of watchdog clock. Action: Switch off power and replace data processor (DP). Contact your Next level of support this does not work. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 317 f3172.fm Nur für den internen Gebrauch F3172 SWU-INT DP PARITY ERROR Type: Service-relevant (Format 47) Short text: Parity error, see F3176. Cause: The cause can be limited to the RAM chip. See F3176. System reaction: RELOAD only when DUPLEX system is on standby. No ACTION in the case of simplex systems Action: F3176...
  • Page 318 f3173.fm Nur für den internen Gebrauch F3173 SWU-INT MEM PARITY ERROR Type: Service-specific (Format 28) Short text: Parity error in memory board Cause: Parity error in read/write operation (not in connection with RTO). System responds with a hard restart. Action: The contents of the memory cell can only be restored by a reload.
  • Page 319 f3174.fm Nur für den internen Gebrauch F3174 SWU-INT DISALLOWED ADDRESS Type: Service-specific (several formats apply) Short text: Error in RAM of DP386 Cause: Only for DP386. Processor attempted to access an invalid address outside the 24 megabytes of the on-board RAM. Action: Save error message data and contact your Next level of...
  • Page 320 f3175.fm Nur für den internen Gebrauch F3175 SWU-INT POWER FAIL Type: Service-specific (several formats apply) Short text: Power failure Cause: A power failure has been detected. This message is output, if an interrupt has occurred due to a short-term power failure. No consequences for user. Action: Check the power supply units.
  • Page 321 f3176.fm Nur für den internen Gebrauch F3176 SWU-INT DP NMI PCI Type: Service-relevant (Format 47) Short text: Non Maskable Interrupt at the peripheral computer interface bus (PCI BUS) Cause: The CPU and the connected units, such as memory or hard disk, LAN controller, etc. are connected via the peripheral computer interface bus (PCI BUS).
  • Page 322 f3177.fm Nur für den internen Gebrauch F3177 SWU-INT RTM RESET Type: Diagnosis-relevant (Format 0) Short text: RTM failure interrupt was triggered. Cause: The RTM failure interrupt was triggered because: 1. the RTM loadware executed a self-reset after a hard restart or Reload in order to reset all settings 2.
  • Page 323 bk_error4000.fm Nur für den internen Gebrauch F4000 8.5 F4000 A9000 F1000 F2000 F3000 -- F4000 -- F5000 F6000 F7000 F8000 F4005 F4006 F4008 F4016 F4018 F4019 F4022 F4023 F4024 F4025 F4026 F4027 F4028 F4029 F4030 F4032 F4033 F4034 F4035 F4036 F4037 F4038 F4039...
  • Page 324 bk_error4000.fm Nur für den internen Gebrauch F4000 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 325 f4005.fm Nur für den internen Gebrauch F4005 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible return value Cause: Implausible return value received from procedure. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 326 f4006.fm Nur für den internen Gebrauch F4006 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values for procedure call. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 327 f4008.fm Nur für den internen Gebrauch F4008 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible static data in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 328 f4016.fm Nur für den internen Gebrauch F4016 ADVISORY Type: Diagnosis-specific (several formats apply) Short text: Advisory message Cause: Advisory message Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 329 f4018.fm Nur für den internen Gebrauch F4018 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 330 f4019.fm Nur für den internen Gebrauch F4019 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The OS has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 331 f4022.fm Nur für den internen Gebrauch F4022 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 332 f4023.fm Nur für den internen Gebrauch F4023 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 333 f4024.fm Nur für den internen Gebrauch F4024 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 334 f4025.fm Nur für den internen Gebrauch F4025 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 335 f4026.fm Nur für den internen Gebrauch F4026 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 336 f4027.fm Nur für den internen Gebrauch F4027 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. 1.
  • Page 337 f4028.fm Nur für den internen Gebrauch F4028 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F4027.
  • Page 338 f4029.fm Nur für den internen Gebrauch F4029 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 339 f4030.fm Nur für den internen Gebrauch F4030 TIME / DATE NOT VALID Type: Diagnosis-specific (Format 01) Short text: Check reference clock Cause: Error when processing the reference clock. Error only occurs in the ADS. Action: The exception code is output in the HEX data and may have the following meaning: H20 = TIME_NOT_VALID (Clock defective) H21 = MAC_NOT_READY (MAC board defective) H22 = BAT_OFF (Check date/time or support battery in the MAC/IOPA)
  • Page 340 f4032.fm Nur für den internen Gebrauch F4032 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 341 f4033.fm Nur für den internen Gebrauch F4033 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 342 f4034.fm Nur für den internen Gebrauch F4034 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the root job Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. Save error message data and contact your Next level of support A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 343 f4035.fm Nur für den internen Gebrauch F4035 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. The hard disk may be faulty or the system program may not exist or may be faulty. Action: Check that the PABX has restarted.
  • Page 344 f4036.fm Nur für den internen Gebrauch F4036 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 345 f4037.fm Nur für den internen Gebrauch F4037 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 346 f4038.fm Nur für den internen Gebrauch F4038 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 347 f4039.fm Nur für den internen Gebrauch F4039 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 348 f4040.fm Nur für den internen Gebrauch F4040 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 349 f4041.fm Nur für den internen Gebrauch F4041 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 350 f4042.fm Nur für den internen Gebrauch F4042 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 351 f4045.fm Nur für den internen Gebrauch F4045 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 352 f4048.fm Nur für den internen Gebrauch F4048 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 353 f4050.fm Nur für den internen Gebrauch F4050 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 354 f4051.fm Nur für den internen Gebrauch F4051 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Event code disallowed Cause: Event code valid but not allowed. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 355 f4052.fm Nur für den internen Gebrauch F4052 IMPLAUSIBLE STATE Type: Diagnosis-specific (several formats apply) Short text: Implausible state Cause: Implausible state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 356 f4053.fm Nur für den internen Gebrauch F4053 UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Unexpected message Cause: Message not expected in the current state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 357 f4054.fm Nur für den internen Gebrauch F4054 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 358 f4055.fm Nur für den internen Gebrauch F4055 IMPLAUSIBLE PROC RET Type: (several formats apply) Short text: Implausible return value Cause: Implausible return value received from a procedure. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 359 f4056.fm Nur für den internen Gebrauch F4056 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in procedure call. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 360 f4057.fm Nur für den internen Gebrauch F4057 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data for database access. Reaction is a soft restart. Action: Save error message data and contact your Next level of support. For initial diagnosis, display the patch list with DIS-PATCH:SYS;.
  • Page 361 f4058.fm Nur für den internen Gebrauch F4058 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (static data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 362 f4059.fm Nur für den internen Gebrauch F4059 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 363 f4060.fm Nur für den internen Gebrauch F4060 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative exception code Cause: Negative exception code for OS calls. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 364 f4061.fm Nur für den internen Gebrauch F4061 MTS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Software error in MTS handler call. Switching network set with implausible data. Action: Save error message data and contact your Next level of support.
  • Page 365 f4062.fm Nur für den internen Gebrauch F4062 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 366 f4063.fm Nur für den internen Gebrauch F4063 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible message header Cause: Implausible message header. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 367 f4066.fm Nur für den internen Gebrauch F4066 ADVISORY Type: Diagnosis-relevant (several formats relevant) Short text: Advisory message. Cause: The printout of these messages is set at the operating terminal by means of a switch. The switches are to be set with the diagnosis switch patch. A switch can be assigned to several advisory messages.
  • Page 368 f4066.fm Nur für den internen Gebrauch Byte 0F-18 Path data new (long path, A_EXIT_TSL, TSL_CSN_A, TSL_CSN_B, CSN_MTS_NR, B_EXIT_TSL) 02 Same switch The diagnosis message was output on the arrival of the FAC PR REQ in networking record C because both stations A and C are in the same node. Byte 04-05 Loden terminal A Byte 06-07...
  • Page 369 f4066.fm Nur für den internen Gebrauch Byte 03-18 Initiator station number Byte 19-1A Loden initiator 04 = Least cost routing "LCR data" Switch: no switch; always output on account of configuration error in the AMOs LODR, LDPLN, LDAT Byte 00 (= 04) Diagnosis format 04 Byte 01 Length of data...
  • Page 370 f4066.fm Nur für den internen Gebrauch 06 = Emergency disconnect Switch: S05 for DIAGS CP Byte 00 (= 06) Diagnosis format 06 Byte 01 Length of data Byte 02-03 Loden of the clearing-down device Byte 04-19 Station number of the clearing-down device Byte 1A-21 Filler Byte 22-23...
  • Page 371 f4066.fm Nur für den internen Gebrauch Byte 05 Number of Loden Byte 06 Attempts to find free Loden Byte 07 Attempts to seize path Byte 08 Path type Byte 09 Byte 0A-0B TSL_CSN_A Byte 0C-0D A_EXIT_TSL Byte 0E LTG_A Byte 0F-10 TSL_CSN_B Byte 11-12 B_EXIT_TSL...
  • Page 372 f4066.fm Nur für den internen Gebrauch 08 = Synchronous Announcement "No announcement buffer available" Switch: S06 for DIAGS CP Wrong dimensioning / synchronous announcement works with restrictions Byte 00 (= 08) Diagnosis format 08 Byte 01 Length of data Byte 02-03 Loden of the clearing-down device Byte 04 Device type...
  • Page 373 f4066.fm Nur für den internen Gebrauch Byte 0A-0B TSL_CSN_A Byte 0C-0D A_EXIT_TSL Byte 0E LTG_A Byte 0F-10 TSL_CSN_B Byte 11-12 B_EXIT_TSL Byte 13-14 Loden B Byte 15 LTG_B Byte 16 Announcement type Byte 17 Repetition factor Byte 18 Return tone Byte 19 Reason for announcement Byte 1A...
  • Page 374 f4066.fm Nur für den internen Gebrauch Byte 18 Attribute Byte 19 Cycle information Byte 1A Check information 0B = Synchronous Announcement "Switch from start/stop to continuous mode" Switch: S11 for DIAGS CP Pure diagnosis to optimize dimensioning of announcement devices Byte 00 (= 0B) Diagnosis format 0B Byte 01...
  • Page 375 f4066.fm Nur für den internen Gebrauch 0D = Multiple code calling "invalid CPB" Switch: S08 for DIAGS CP Byte 00 (= 0D) Diagnosis format 0D Byte 01 Length of data Byte 02-03 TMOM Loden Byte 04 TMOM status Byte 05-06 CPB-IDX paging memory Byte 07-1C Station number in paging memory...
  • Page 376 f4066.fm Nur für den internen Gebrauch 07 = DB_GS_C_PAR_VARIANT7 08 = DB_GS_C_PAR_VARIANT8 0F = Error on feature stack operation Switch: - Byte 00 (= 0F) Diagnosis format 0F Byte 01 Length of data Byte 02 Stack pointer Byte 03-04 Feature stack 1 Byte 03 Feature state Byte 04...
  • Page 377 f4066.fm Nur für den internen Gebrauch 1A = DB_FEA_CO_LCR 1B = DB_FEA_CO_SR_SAVE_CALL 1C = DB_FEA_CO_CALL_TO_ATND: 1D = DB_FEA_CO_THREE_PARTY 1E = DB_FEA_CO_TSC_SERVER_MWI 1F = DB_FEA_CO_REMOTE_CFU 20 = DB_FEA_CO_TRANSFER 21 = DB_FEA_CO_GF 22 = DB_FEA_CO_TSC 23 = DB_FEA_CO_CSN7 24 = DB_FEA_CO_RR_NETW_INTW 25 = DB_FEA_CO_CALL_TO_ACD 26 = DB_FEA_CO_CALL_TO_ACD_RSL 27 = DB_FEA_CO_HOLD_BEFORE_ACT 28 = DB_FEA_CO_GPUN_OUT...
  • Page 378 f4066.fm Nur für den internen Gebrauch Byte 04 Device type of the requesting device Byte 05 Number of Loden for announcement type = 0 Byte 06 Path type Byte 07 Byte 08-09 TSL_CSN_A Byte 0A-0B A_EXIT_TSL Byte 0C LTG_A Byte 0D-0E TSL_CSN_B Byte 0F-10 B_EXIT_TSL...
  • Page 379 f4066.fm Nur für den internen Gebrauch Byte 00 (= 13) Diagnosis format 13 Byte 01 Length of data Byte 02 Reason for diagnostic output: 00 = Shortage of local resources 01 = Signaling from remote link rejected: Byte 03-04 Local group number Byte 05-1E Data remote link: Byte 05...
  • Page 380 f4066.fm Nur für den internen Gebrauch 3. At a digital circuit which is operated with CorNetNQ and received the flagtrace activation for a connection. This can take place both forwards in an incoming seizure and backwards in an outgoing connection. 4.
  • Page 381 f4066.fm Nur für den internen Gebrauch Byte 57-58 Loden of the B station (if not available 0) Byte 59-60 Line of the B station (if not available 0) Display of flagtrace activation via an external connection Byte 00 Diagnosis format 14 (always 14H -> CP-ADVISORY flagtrace) Byte 01 Always C7H <=>...
  • Page 382 f4066.fm Nur für den internen Gebrauch Byte 34 Station number of the B station (if not available 0) Byte 35-56 Station number of the B station (initialized with 0F) Byte 57-58 Loden of the B station (if not available 0) Byte 59-60 Line of the B station (if not available 0) 15h = Service function not complete...
  • Page 383 f4066.fm Nur für den internen Gebrauch Byte 01 Length of data Byte 02 AC group (value 0-15 from DB_M_ATTENDANT_GROUP_RNG mode) Byte 03 Digit analysis result missing (from DB_M_WABE_KZP_SET mode) 18h = TTS timer expiry Switch: none Byte 00 (= 18) Diagnosis format 18 Byte 01 Length of data = 12 Byte 02-05...
  • Page 384 f4066.fm Nur für den internen Gebrauch Byte 05-06 Called party’s LODEN Byte 07 Called party’s DEVICE TYPE Byte 08 Called party’s SOURCE GROUP Byte 09 LENGTH of station number called Byte 10-31 Station number called Byte 32 Reason for alternative routing Byte 33 Reason for rejection Byte 34-56...
  • Page 385 f4066.fm Nur für den internen Gebrauch 1Ch = ONS diagnosis Switch: CP_DIAG_FM_ONS_DIAG Byte 00 (= 1C) Diagnosis format 1C Byte 01 Length of data Byte 02-03 ONS group number (from AMO AUN) Byte 04 ONS-Membertype (DB_M_CP_ONS_ROLE_SET) Byte 05-06 ONS Master’s LODEN Byte 07 ONS calltype (CP_M_ONS_CTYPE_SET) Byte 08...
  • Page 386 f4068.fm Nur für den internen Gebrauch F4068 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 387 f4069.fm Nur für den internen Gebrauch F4069 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The AM has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 388 f4072.fm Nur für den internen Gebrauch F4072 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 389 f4073.fm Nur für den internen Gebrauch F4073 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 390 f4074.fm Nur für den internen Gebrauch F4074 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 391 f4075.fm Nur für den internen Gebrauch F4075 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 392 f4076.fm Nur für den internen Gebrauch F4076 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 393 f4077.fm Nur für den internen Gebrauch F4077 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. 1.
  • Page 394 f4078.fm Nur für den internen Gebrauch F4078 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F4077.
  • Page 395 f4079.fm Nur für den internen Gebrauch F4079 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 396 f4080.fm Nur für den internen Gebrauch F4080 TIME / DATE NOT VALID Type: Diagnosis-specific (Format 01) Short text: Check reference clock Cause: Error when processing the reference clock. Error only occurs in the ADS. Action: The exception code is output in the HEX data and may have the following meaning: H20 = TIME_NOT_VALID (Clock defective) H21 = MAC_NOT_READY (MAC board defective) H22 = BAT_OFF (Check date/time or support battery in the MAC/IOPA)
  • Page 397 f4082.fm Nur für den internen Gebrauch F4082 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 398 f4083.fm Nur für den internen Gebrauch F4083 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 399 f4084.fm Nur für den internen Gebrauch F4084 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the root job Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. Save error message data and contact your Next level of support.
  • Page 400 f4085.fm Nur für den internen Gebrauch F4085 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. Action: Check that the PABX has restarted. contact your Next level of support if the system fails to restart.
  • Page 401 f4086.fm Nur für den internen Gebrauch F4086 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 402 f4087.fm Nur für den internen Gebrauch F4087 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 403 f4088.fm Nur für den internen Gebrauch F4088 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 404 f4089.fm Nur für den internen Gebrauch F4089 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 405 f4090.fm Nur für den internen Gebrauch F4090 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 406 f4091.fm Nur für den internen Gebrauch F4091 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 407 f4092.fm Nur für den internen Gebrauch F4092 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 408 f4095.fm Nur für den internen Gebrauch F4095 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 409 f4098.fm Nur für den internen Gebrauch F4098 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 410 f4100.fm Nur für den internen Gebrauch F4100 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 411 f4101.fm Nur für den internen Gebrauch F4101 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Event code disallowed Cause: Event code valid but not allowed. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 412 f4102.fm Nur für den internen Gebrauch F4102 IMPLAUSIBLE STATE Type: Diagnosis-specific (several formats apply) Short text: Implausible state Cause: Implausible state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 413 f4103.fm Nur für den internen Gebrauch F4103 UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Unexpected message Cause: Message not expected in the current state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 414 f4104.fm Nur für den internen Gebrauch F4104 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 415 f4105.fm Nur für den internen Gebrauch F4105 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible return value Cause: Implausible return value received from a procedure. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 416 f4106.fm Nur für den internen Gebrauch F4106 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in procedure call. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 417 f4107.fm Nur für den internen Gebrauch F4107 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data for database access. Reaction is a soft restart. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 418 f4108.fm Nur für den internen Gebrauch F4108 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (static data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 419 f4109.fm Nur für den internen Gebrauch F4109 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 420 f4110.fm Nur für den internen Gebrauch F4110 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative exception code Cause: Negative exception code for OS calls. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 421 f4111.fm Nur für den internen Gebrauch F4111 MTS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Software error in MTS handler call. Switching network set with implausible data. Action: Save error message data and contact your Next level of support.
  • Page 422 f4112.fm Nur für den internen Gebrauch F4112 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 423 f4113.fm Nur für den internen Gebrauch F4113 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible message header Cause: Implausible message header. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 424 f4116.fm Nur für den internen Gebrauch F4116 ADVISORY Type: Diagnosis-specific (several formats apply) Short text: Advisory message Cause: Advisory message. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 425 f4118.fm Nur für den internen Gebrauch F4118 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 426 f4119.fm Nur für den internen Gebrauch F4119 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The OS has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 427 f4122.fm Nur für den internen Gebrauch F4122 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 428 f4123.fm Nur für den internen Gebrauch F4123 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 429 f4124.fm Nur für den internen Gebrauch F4124 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 430 f4125.fm Nur für den internen Gebrauch F4125 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 431 f4126.fm Nur für den internen Gebrauch F4126 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 432 f4127.fm Nur für den internen Gebrauch F4127 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. 1.
  • Page 433 f4128.fm Nur für den internen Gebrauch F4128 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F4127.
  • Page 434 f4129.fm Nur für den internen Gebrauch F4129 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 435 f4130.fm Nur für den internen Gebrauch F4130 TIME / DATE NOT VALID Type: Diagnosis-specific (Format 01) Short text: Check reference clock Cause: Error when processing the reference clock. Error only occurs in the ADS. Action: The exception code is output in the HEX data and may have the following meaning: H20 = TIME_NOT_VALID (Clock defective) H21 = MAC_NOT_READY (MAC board defective) H22 = BAT_OFF (Check date/time or support battery in the MAC/IOPA)
  • Page 436 f4132.fm Nur für den internen Gebrauch F4132 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 437 f4133.fm Nur für den internen Gebrauch F4133 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 438 f4134.fm Nur für den internen Gebrauch F4134 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the root job Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. Save error message data and contact your Next level of support.
  • Page 439 f4135.fm Nur für den internen Gebrauch F4135 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. The hard disk may be faulty or the system program may not exist or may be faulty. Action: Check that the PABX has restarted.
  • Page 440 f4136.fm Nur für den internen Gebrauch F4136 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 441 f4137.fm Nur für den internen Gebrauch F4137 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 442 f4138.fm Nur für den internen Gebrauch F4138 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 443 f4139.fm Nur für den internen Gebrauch F4139 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 444 f4140.fm Nur für den internen Gebrauch F4140 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 445 f4141.fm Nur für den internen Gebrauch F4141 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 446 f4142.fm Nur für den internen Gebrauch F4142 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 447 f4145.fm Nur für den internen Gebrauch F4145 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 448 f4148.fm Nur für den internen Gebrauch F4148 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 449 f4150.fm Nur für den internen Gebrauch F4150 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 450 f4151.fm Nur für den internen Gebrauch F4151 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Event code disallowed Cause: Event code valid but not allowed. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 451 f4152.fm Nur für den internen Gebrauch F4152 IMPLAUSIBLE STATE Type: Diagnosis-specific (several formats apply) Short text: Implausible state Cause: Implausible state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 452 f4153.fm Nur für den internen Gebrauch F4153 Type: UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Unexpected message Cause: Message not expected in the current state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 453 f4154.fm Nur für den internen Gebrauch F4154 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 454 f4155.fm Nur für den internen Gebrauch F4155 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible return value Cause: Implausible return value received from a procedure. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 455 f4156.fm Nur für den internen Gebrauch F4156 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in procedure call. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 456 f4157.fm Nur für den internen Gebrauch F4157 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data for database access. Reaction is a soft restart. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 457 f4158.fm Nur für den internen Gebrauch F4158 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (static data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 458 f4159.fm Nur für den internen Gebrauch F4159 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 459 f4160.fm Nur für den internen Gebrauch F4160 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative exception code Cause: Negative exception code for OS calls. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 460 f4161.fm Nur für den internen Gebrauch F4161 MTS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Software error in MTS handler call. Switching network set with implausible data. Action: Save error message data and contact your Next level of support.
  • Page 461 f4162.fm Nur für den internen Gebrauch F4162 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 462 f4163.fm Nur für den internen Gebrauch F4163 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible message header Cause: Implausible message header. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 463 f4166.fm Nur für den internen Gebrauch F4166 ADVISORY Type: Diagnosis-specific (several formats apply) Short text: Advisory message Cause: Advisory message. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 464 f4168.fm Nur für den internen Gebrauch F4168 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 465 f4169.fm Nur für den internen Gebrauch F4169 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The AM has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 466 f4172.fm Nur für den internen Gebrauch F4172 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 467 f4173.fm Nur für den internen Gebrauch F4173 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 468 f4174.fm Nur für den internen Gebrauch F4174 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 469 f4175.fm Nur für den internen Gebrauch F4175 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 470 f4176.fm Nur für den internen Gebrauch F4176 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 471 f4177.fm Nur für den internen Gebrauch F4177 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. 1.
  • Page 472 f4178.fm Nur für den internen Gebrauch F4178 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F4177.
  • Page 473 f4179.fm Nur für den internen Gebrauch F4179 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 474 f4180.fm Nur für den internen Gebrauch F4180 TIME / DATE NOT VALID Type: Diagnosis-specific (Format 01) Short text: Check reference clock Cause: Error when processing the reference clock. Error only occurs in the ADS. Action: The exception code is output in the HEX data and may have the following meaning: H20 = TIME_NOT_VALID (Clock defective) H21 = MAC_NOT_READY (MAC board defective) H22 = BAT_OFF (Check date/time or support battery in the MAC/IOPA)
  • Page 475 f4182.fm Nur für den internen Gebrauch F4182 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 476 f4183.fm Nur für den internen Gebrauch F4183 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 477 f4184.fm Nur für den internen Gebrauch F4184 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the root job Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. Save error message data and contact your Next level of support.
  • Page 478 f4185.fm Nur für den internen Gebrauch F4185 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. Action: Check that the PABX has restarted. Contact your Next level of support if the system fails to restart.
  • Page 479 f4186.fm Nur für den internen Gebrauch F4186 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 480 f4187.fm Nur für den internen Gebrauch F4187 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 481 f4188.fm Nur für den internen Gebrauch F4188 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 482 f4189.fm Nur für den internen Gebrauch F4189 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 483 f4190.fm Nur für den internen Gebrauch F4190 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 484 f4191.fm Nur für den internen Gebrauch F4191 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 485 f4192.fm Nur für den internen Gebrauch F4192 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 486 f4195.fm Nur für den internen Gebrauch F4195 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 487 f4198.fm Nur für den internen Gebrauch F4198 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 488 f4200.fm Nur für den internen Gebrauch F4200 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 489 f4201.fm Nur für den internen Gebrauch F4201 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Event code disallowed Cause: Event code valid but not allowed. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 490 f4203.fm Nur für den internen Gebrauch F4203 UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Unexpected message Cause: Message not expected in the current state. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 491 f4204.fm Nur für den internen Gebrauch F4204 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 492 f4205.fm Nur für den internen Gebrauch F4205 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible return value Cause: Implausible return value received from a procedure. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 493 f4206.fm Nur für den internen Gebrauch F4206 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in a procedure call. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 494 f4207.fm Nur für den internen Gebrauch F4207 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data for database access. Reaction is a soft restart. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 495 f4208.fm Nur für den internen Gebrauch F4208 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (static data) in memory. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 496 f4209.fm Nur für den internen Gebrauch F4209 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 497 f4210.fm Nur für den internen Gebrauch F4210 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative exception code Cause: Negative exception code for OS calls. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 498 f4212.fm Nur für den internen Gebrauch F4212 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 499 f4213.fm Nur für den internen Gebrauch F4213 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible message header Cause: Implausible message header. Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 500 f4214.fm Nur für den internen Gebrauch F4214 DMS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative acknowledgments by the data management system Cause: Negative acknowledgments by the data management system (e.g. I/O error). Action: If this error occurs repeatedly, save the error message data and contact your Next level support.
  • Page 501 f4216.fm Nur für den internen Gebrauch F4216 SM-CR ADVISORY Type: Diagnosis-specific (several formats apply) Short text: Advisory message of the call data recording system Cause: This advisory message always refers to an error in call data recording. Possible causes: Tariff tables with AMO TTBL incorrectly configured, Type of call data recording per carrier with AMO GEFE incorrectly configured, Tariff table with AMO TTBL incorrectly configured (group 0 for display), Tariffs with AMO TTBL incorrectly configured.
  • Page 502 f4216.fm Nur für den internen Gebrauch Byte 27 = CONN_SERVICE_IND Communication service of connection 0 Voice 1 Teletext 2 Videotex 3 Fax 4 Data 5 Telex via TTC (interworking) Byte 28 = CONN_NETWORK Specifies the network in which the call was set up 0 Analog network 1 IDN 2 ISDN...
  • Page 503 f4216.fm Nur für den internen Gebrauch BIT 0 Local connection BIT 1 Toll connection BIT 2 Chargee = ATND BIT 3 Chargee = MTLC BIT 4 Chargee = Night Station BIT 5 User with CDRS authorization BIT 6 User with CDRS authorization BIT 7 Poss.
  • Page 504 f4216.fm Nur für den internen Gebrauch 11 HUNTING_GROUP 12 MAIL_BOX 13 PAGING 14 DICTATION 15 CREDIT_CARD_CHRG 16 REVERSE_CHARGING 17 CALL_DEFECTION 18 DOOR_OPENING_SYS Byte 81-92 = IDENT_CARD Personal identification number Byte 93 = IDENT_CARD_COPIN Class of PIN, values 0-8 Byte 94 = CAUSE Reason for connection cleardown, values 0-149 Byte 95 = B_CHNL_CNT Number of 64-Kbit-channels of a connection, values 0-30...
  • Page 505 f4216.fm Nur für den internen Gebrauch Byte 131 : Month (1-12) Byte 132 : Day (1-31) Byte 133 : Hour Byte 134 : Minute Byte 135 : Second Byte 136 : 1/10 second Byte 137-140 = CONN_TIME_EXC Connection duration Byte 137 : Hours Byte 138 : Minutes Byte 139 : Seconds Byte 140 : 1/10 second...
  • Page 506 f4216.fm Nur für den internen Gebrauch Advisory Message with Exception Address UA:0000:3D74:8F97 The error message was caused by calling the charge calculation without a valid connection block. Save the error message data and contact your Next level of support. The last block of the error message has the following structure: Byte 0 = CC-State Byte 1-9 = CALL_ID Byte 10-13 = TRUNK_NR Number of exchange trunk seized...
  • Page 507 f4216.fm Nur für den internen Gebrauch Advisory Message with Exception Address UA:0000:4878:89A1: The preceding F4216 message contains the CP error message. The error occurs when two seizure messages are sent by the SWU. Save error message data and contact your Next level of support.
  • Page 508 f4216.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 509 f4218.fm Nur für den internen Gebrauch F4218 BOARD NOT READY Type: Diagnosis-specific (Format 01) Short text: Board not in operation Cause: The operating system (OS) has detected that the MDL_READY field of a dual-port RAM (DPR) no longer contains the value READY, which means that a board (IP, DCL, CCH, MBU, IOCG) is currently not operative.
  • Page 510 f4219.fm Nur für den internen Gebrauch F4219 DPR NOT VALID Type: Diagnosis-specific (Format 01) Short text: Dual Port Ram Cause: The OS has detected that the DPR_VALID field of a dual-port RAM (DPR) no longer contains the value VALID because, for instance, a container chaining error has been found by board. No hexadecimal data is output with this message.
  • Page 511 f4222.fm Nur für den internen Gebrauch F4222 BUSHANDLER TIMEOUT Type: Diagnosis-specific (Format 01) Short text: Bus handler (BH) reports timeout Cause: Bus handler (BH) reports timeout error, i.e. transmission was not complete. The BH enables all the containers in the associated command queue and disables this queue with its block byte. Containers are only chained to the command queue again after the SP (in its own processor) has reset the block byte of the corresponding queue with ON_W_RESET_QBLOCK.
  • Page 512 f4223.fm Nur für den internen Gebrauch F4223 BUSHANDLER NO PARTNER Type: Diagnosis-specific (Format 01) Short text: Board failure of remote processor Cause: BH identifies that a message could not be transmitted because, for instance, the destination processor’s board had failed. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 513 f4224.fm Nur für den internen Gebrauch F4224 BUSHANDLER CONTEXT Type: Diagnosis-specific (Format 01) Short text: Implausible data for the BH Cause: This means the container has been fed the wrong data for the BH by the operating system. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 514 f4225.fm Nur für den internen Gebrauch F4225 DESTINATION CATALOG Type: Diagnosis-specific (Format 01) Short text: Name not contained in index catalog Cause: During processor communication, a container with an index/name that was not in the receiver’s index catalog was received from a firmware processor or boot. The error is signaled at the receiving end.
  • Page 515 f4226.fm Nur für den internen Gebrauch F4226 DESTINATION MAILBOX Type: Diagnosis-specific (Format 01) Short text: Destination mailbox no longer exists Cause: During processor communication, it was found at the receiving end that the destination mailbox named in the container no longer exists or is wrong. The error is signaled at the receiving end. Action: Not more than the first 64 bytes of the container that has not been transmitted are output in the HEX data.
  • Page 516 f4227.fm Nur für den internen Gebrauch F4227 DESTINATION RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: Resources short for receiving messages over processor borders. Whether the message was intended for an operating system mailbox or for a user’s mailbox, is of no concern as regards this error. 1.
  • Page 517 f4228.fm Nur für den internen Gebrauch F4228 OS RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough OS resources Cause: The operating system did not have a free element in its internal buffer pool or a segment available, nor, despite a wait, a short or long container. Shortage of operating system resources when receiving messages over processor borders is, however, reported with error message F4227.
  • Page 518 f4229.fm Nur für den internen Gebrauch F4229 MAILBOX TIMER Type: Diagnosis-specific (Format 01) Short text: Mailbox no longer exists Cause: When a timer runs down, the destination mailbox is found to be no longer existing. Action: In the HEX data, the message is output by the timer in a length of 20 bytes. Save error message data and contact your Next level of support.
  • Page 519 f4230.fm Nur für den internen Gebrauch F4230 TIME / DATE NOT VALID Type: Diagnosis-specific (Format 01) Short text: Check reference clock Cause: Error when processing the reference clock. Error only occurs in the ADS. Action: The exception code is output in the HEX data and may have the following meaning: H20 = TIME_NOT_VALID (Clock defective) H21 = MAC_NOT_READY (MAC board defective) H22 = BAT_OFF (Check date/time or support battery in the MAC/IOPA)
  • Page 520 f4232.fm Nur für den internen Gebrauch F4232 JOTA Type: Diagnosis-specific (Format 01) Short text: Implausible data in job table Cause: ROOT finds implausible data in the job table (JOTA). Depending on the state of the boot, the error is reported to SYSLOAD or to error analysis. It is assumed that the JOTA checksum is no longer correct. Action: If byte 0 of the HEX data contains the value 01, the other bytes output the layer number.
  • Page 521 f4233.fm Nur für den internen Gebrauch F4233 PLAUS MAX LIMIT Type: Diagnosis-specific (Format 01) Short text: Error statistics overflow Cause: Too many plausibility errors within a certain time. The error statistics overflow. Action: Save error message data and contact your Next level of support.
  • Page 522 f4234.fm Nur für den internen Gebrauch F4234 SYSTEM EXCEPTN HANDLER Type: Diagnosis-specific (Format 01) Short text: Error when processing the root job Cause: The system exception handler was activated by an error. Action: Find the cause with further error reports. Save error message data and contact your Next level of support.
  • Page 523 f4235.fm Nur für den internen Gebrauch F4235 INIT ERROR Type: Diagnosis-specific (Format 01) Short text: Error in OS initialization Cause: This error is reported to SYSLOAD, not to error analysis. The reaction is a hard restart. Action: Check that the PABX has restarted. contact your Next level of support if the system fails to restart.
  • Page 524 f4236.fm Nur für den internen Gebrauch F4236 BUSHANDLER QBLOCK S Type: Diagnosis-specific (Format 01) Short text: No free short container available Cause: Bus handler (BH) reports that for a certain time the destination processor’s dual-port RAM (DPR) did not have a short free container available to hold a message that was to be transmitted. The BH enables all the containers in the associated command queue and disables this queue with its block byte.
  • Page 525 f4237.fm Nur für den internen Gebrauch F4237 BUSHANDLER QBLOCK L Type: Diagnosis-specific (Format 01) Short text: No free long container available Cause: BH reports that for a certain time the destination processor’s DPR did not have along free container available to hold a message that was to be transmitted. The BH enables all the containers of the associated command queue and disables this queue with its block byte.
  • Page 526 f4238.fm Nur für den internen Gebrauch F4238 BROADCAST ON, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_ON order (order to all) from the active base processor (BP) to the message buffers (MBU) was not acknowledged punctually by at least one MBU.
  • Page 527 f4239.fm Nur für den internen Gebrauch F4239 BROADCAST OFF, NO ACK Type: Diagnosis-specific (Format 01) Short text: Broadcast not acknowledged by at least one MBU Cause: The BROADCAST_OFF order from the active BP to the MBUs was not acknowledged punctually by at least one MBU. The error is reported in the active BP. Action: Check the MBU boards and replace defective boards.
  • Page 528 f4240.fm Nur für den internen Gebrauch F4240 BROADCAST LONG Type: Diagnosis-specific (Format 01) Short text: Message not retrieved by MBU Cause: When long message was to be acknowledged by the base processor (BP) acting on behalf of the group processors (GP), it was found that this message had not yet been collected by at least one message buffer (MBU).
  • Page 529 f4241.fm Nur für den internen Gebrauch F4241 GP IN BROADCAST MODE Type: Diagnosis-specific (Format 01) Short text: Processor communication error Cause: During processor communication it was found at the receiving end (active BP) that the destination processor specified in the container was a GP currently affected by the load broadcast rather than the GP designated in the load broadcast.
  • Page 530 f4242.fm Nur für den internen Gebrauch F4242 DESTINATION PROCESSOR Type: Diagnosis-specific (Format 01) Short text: Destination processor not available Cause: During processor communication it was found at the receiving end (active BP) that the destination processor named in the container according to the directory table (DIR_TBL) was not available. The sender of the message was either a firmware processor or a data processor whose DIR_TBL was not consistent with the destination DIR_TBL.
  • Page 531 f4245.fm Nur für den internen Gebrauch F4245 MAILBX TIMER RESOURCES Type: Diagnosis-specific (Format 01) Short text: Not enough resources Cause: After the timer had run down, the system was able to determine that the destination mailbox exists but that the message could not be transmitted due to lack of free memory. Action: The timer message is output in the HEX data up to a length of 20 Bytes.
  • Page 532 f4248.fm Nur für den internen Gebrauch F4248 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: SYSLOAD has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 533 f4250.fm Nur für den internen Gebrauch F4250 IMPLAUSIBLE EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Implausible event code Cause: Implausible event code. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 534 f4251.fm Nur für den internen Gebrauch F4251 DISALL EVT CODE Type: Diagnosis-specific (several formats apply) Short text: Event code disallowed Cause: Event code valid but not allowed. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 535 f4252.fm Nur für den internen Gebrauch F4252 IMPLAUSIBLE STATE Type: Diagnosis-specific (several formats apply) Short text: Implausible state Cause: Implausible state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 536 f4253.fm Nur für den internen Gebrauch F4253 UNEXP MESSAGE Type: Diagnosis-specific (several formats apply) Short text: Unexpected message Cause: Message not expected in the current state. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 537 f4254.fm Nur für den internen Gebrauch F4254 IMPLAUSIBLE MESSAGE DATA Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data in the message. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 538 f4255.fm Nur für den internen Gebrauch F4255 IMPLAUSIBLE PROC RET Type: Diagnosis-specific (several formats apply) Short text: Implausible return value Cause: Implausible return value received from a procedure. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 539 f4256.fm Nur für den internen Gebrauch F4256 IMPLAUSIBLE PROC PARAM Type: Diagnosis-specific (several formats apply) Short text: Implausible parameter values Cause: Implausible parameter values in a procedure call. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 540 f4257.fm Nur für den internen Gebrauch F4257 DBAR Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data for database access. Action: Reaction is a soft restart. Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 541 f4258.fm Nur für den internen Gebrauch F4258 STATIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Database inconsistent Cause: Database inconsistencies detected during soft restart (ACTION=HREXSRRE). Action: Reaction is a hard restart. Save error message data and contact your Next level of support.
  • Page 542 f4259.fm Nur für den internen Gebrauch F4259 DYNAMIC DATA FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Implausible data (dynamic data) in memory. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 543 f4260.fm Nur für den internen Gebrauch F4260 OS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Negative exception code Cause: Negative exception code for OS calls. In this error message the user address is the only place to find the relevant user as long as the call and exception codes refer directly to the OS call. The HEX data then reflects the last error analysis input message.
  • Page 544 f4261.fm Nur für den internen Gebrauch F4261 MTS CALL FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible data Cause: Software error in MTS handler call. Switching network set with implausible data. Action: Save error message data and contact your Next level of support.
  • Page 545 f4262.fm Nur für den internen Gebrauch F4262 TIMEOUT FAULT Type: Diagnosis-specific (several formats apply) Short text: Timer run down Cause: Timeout for expected response. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 546 f4263.fm Nur für den internen Gebrauch F4263 MSG HEADER FAULT Type: Diagnosis-specific (several formats apply) Short text: Implausible message header Cause: Implausible message header. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 547 f4265.fm Nur für den internen Gebrauch F4265 DEP SWU USER Type: Diagnosis-specific (several formats apply) Short text: Software error in SWU dependability. Cause: The contents of the stack can be output in the HEX data with this message. In conjunction with a processor interrupt (F4298), the system outputs 5 messages whose stack data can be interpreted.
  • Page 548 f4266.fm Nur für den internen Gebrauch F4266 ADVISORY Type: Diagnosis-relevant (several formats relevant) Short text: Advisory message from the SW complex dependability system Cause: The dependability system outputs advisory messages for different reasons. The messages are partially text-driven. Messages containing the following texts are RTO messages: The message text identifies the three different message types: •...
  • Page 549 f4266.fm Nur für den internen Gebrauch LAN SEGMENT LINK DOWN PARTNER CC HAS LINK UP SWITCHOVER INITIATED Switchover is rejected because LAN link of partner CC is down: LAN SEGMENT LINK DOWN SWITCHOVER REJECTED: STANDBY LAN LINK IS DOWN Switchover is rejected because partner CC is not standby: LAN SEGMENT LINK DOWN SWITCHOVER REJECTED: PARTNER IS NOT STANDBY...
  • Page 550 f4293.fm Nur für den internen Gebrauch F4293 POSTLOAD ACTION Type: Diagnosis-specific (Format 23) Short text: Postloading active Cause: If defective boards are detected during loading, a second attempt is made to start the boards with a postloading run. Action: Check that error message F4294 is output (indicates that postloading has been completed).
  • Page 551 f4294.fm Nur für den internen Gebrauch F4294 POSTLOAD END Type: Diagnosis-specific (Format 00) Short text: Postloading completed Cause: Postloading is completed. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 552 f4298.fm Nur für den internen Gebrauch F4298 PROCESSOR INTERRUPT Type: Diagnosis-specific (Format 01) Short text: Interrupt Cause: Sysload or interrupt handler has processed or output an interrupt. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 553 f4352.fm Nur für den internen Gebrauch F4352 COMMON ERROR Type: Diagnosis relevant (Format 24) Short text: Recovery error occurred when saving connection data. Cause: Save, unsave, save process, recovery. General recovery error occurred when saving connection data. Error message indicates a number of diverse "less serious" recovery errors. The interpretation of the hexadecimal data for this message provides more detailed information about these diverse errors.
  • Page 554 f4352.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 555 f4353.fm Nur für den internen Gebrauch F4353 INCONSISTENT Type: Diagnosis-specific (Format 24) Short text: Inconsistency in save list Cause: This error message occurs when an inconsistency is detected in the save list (entry of established connections). This list is checked while saving, deleting and re-establishing connection data. The inconsistency is usually that only one data record (instead of a pair) exists in the save file, or that partner references are either incomplete or missing.
  • Page 556 f4355.fm Nur für den internen Gebrauch F4355 NO DCL RESPONSE Type: Diagnosis-specific (Format 24) Short text: DCL board defective Cause: After a soft restart the DCL (data communication link) is prompted to poll the peripherals again. If it fails to respond, this error message will activate a hard start (DCL may be defective). Action: Replace DCL if defective.
  • Page 557 f4376.fm Nur für den internen Gebrauch F4376 NO CPB AVAILABLE Type: Diagnosis-specific (Format 24) Short text: No call processing buffer available Cause: No call processing buffer available. Action: Save error message data and contact your Next level of support. Interpretation of auxiliary data: Structure of the auxiliary data same as for F4352.
  • Page 558 f4377.fm Nur für den internen Gebrauch F4377 NO CP RESPONSE Type: Diagnosis-specific (Format 24) Short text: No acknowledgment from call processing Cause: No acknowledgment from call processing (only for 3000 systems). Action: Save error message data and contact your Next level of support.
  • Page 559 f4378.fm Nur für den internen Gebrauch F4378 NO MBU RESPONSE Type: Diagnosis-specific (Format 24) Short text: No acknowledgment received from message buffer unit Cause: No acknowledgment received from message buffer unit(s) (MBUs). Action: Check the connections (bus cable) and replace the MBU board(s) if defective. If this does not work, save error message data and contact your Next level of support.
  • Page 560 f4379.fm Nur für den internen Gebrauch F4379 NO PP RESPONSE Type: Diagnosis-specific (Format 24) Short text: No acknowledgment from peripheral processing Cause: No acknowledgment from peripheral processing. Action: Save error message data and contact your Next level of support. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 561 f4380.fm Nur für den internen Gebrauch F4380 NO LTG RESPONSE Type: Diagnosis-specific (Format 42) Short text: No response from LTG Cause: No response from (one) LTG. Action: Check connecting cables to see whether LTG has really failed. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 562 f4382.fm Nur für den internen Gebrauch F4382 NO LTG RESPONDING Type: Diagnosis-specific (Format 42) Short text: No serviceable line trunk group Cause: No serviceable line trunk group (LTG) found, soft restart of common control (SR CC). Action: Check reason why no functioning LTG can be found. Often, this is due to the CC undergoing a soft restart after a voltage drop.
  • Page 563 f4383.fm Nur für den internen Gebrauch F4383 LTG DEF Type: Diagnosis-specific (Format 42 Short text: LTG does not start Cause: LTG does not start. Possible power supply problems (incompatible partial voltages). Action: Check the LTG hardware (boards, bus cable). Old hardware versions: check that the Faston connectors on the backplane are locked in correctly.
  • Page 564 f4384.fm Nur für den internen Gebrauch F4384 ADMIN TAB IMPLAUSIBLE Type: Diagnosis-specific (Format 24) Short text: Implausibility in line trunk group Cause: Implausible data found in recovery status management during soft restart in line trunk group (SR LTG). Action: Initiate a soft restart, hard restart or reload of the LTG. If this does not work, save the error message data and contact your Next level of support.
  • Page 565 f4385.fm Nur für den internen Gebrauch F4385 END CC SOFT RESTART Type: Diagnosis-specific (Format 24) Short text: End of soft restart (advisory) Cause: End of common control soft restart (SR CC). Action: If you cannot find the cause of the CC soft restart, save the error message data and contact your Next level of support.
  • Page 566 f4386.fm Nur für den internen Gebrauch F4386 END LTG SOFT RESTART Type: Diagnosis-specific (Format 42) Short text: End of soft restart (advisory) Cause: End of line/trunk group soft restart (SR LTG). Action: If you cannot find the cause of the LTG soft restart, save the error message data and contact your Next level of support.
  • Page 567 f4387.fm Nur für den internen Gebrauch F4387 END CC SR CLEAN-UP Type: Diagnosis-specific (Format 24) Short text: Connection release end message (advisory) Cause: End message of connection release during soft restart of common control (SR CC). Full CP operation ensured as of now. Action: If you cannot find the cause of the CC soft restart, save the error message data and contact your...
  • Page 568 f4388.fm Nur für den internen Gebrauch F4388 END LTG SR CLEAN-UP Type: Diagnosis-specific (Format 42) Short text: End of connection release (advisory) Cause: End of connection release during SR of LTG. Full CP operation in LTG ensured as of now. Action: If you cannot find the cause of the LTG soft restart, save the error message data and contact your...
  • Page 569 f4389.fm Nur für den internen Gebrauch F4389 LTG SOFT RESTART ABORT Type: Diagnosis-specific (Format 42) Short text: SR of LTG aborted Cause: SR of LTG was aborted (advisory). Action: Initiate a soft restart, hard restart or reload of the LTG, if this does not work, save the error message data and contact your Next level of support.
  • Page 570 f4390.fm Nur für den internen Gebrauch F4390 END SBR LTG Type: Diagnosis-specific (Format 42) Short text: End message from standby restoration (advisory) Cause: End message from standby restoration of LTG. Action: If you cannot find the cause of the standby restoration, save the error message data and contact your Next level of support.
  • Page 571 f4391.fm Nur für den internen Gebrauch F4391 END SBR CC Type: Diagnosis-specific (Format 24) Short text: End message from standby restoration (advisory) Cause: End message from standby restoration of common control (CC). Action: If you cannot find the cause of the standby restoration, save the error message data and contact your Next level of support.
  • Page 572 f4392.fm Nur für den internen Gebrauch F4392 END SBR CSN Type: Diagnosis-specific (Format 42) Short text: End message from standby restoration (advisory) Cause: End message from standby restoration of central switching network (CSN). Message only for H3000 systems. Action: If you cannot find the cause of the standby restoration, save the error message data and contact your Next level of support.
  • Page 573 f4397.fm Nur für den internen Gebrauch F4397 PD INVALID Type: Diagnosis relevant (Format 24) Short text: The protocol discriminator (PD) cannot be converted. Cause: Error is detected during a soft restart or when saving. A default PD value is entered. The error may be caused by using the AMO PRODE.
  • Page 574 f4398.fm Nur für den internen Gebrauch F4398 NO NW DYN DEV TABLE DH Type: Diagnosis-specific (Format 24) Short text: No device memory Cause: No device memory DH pool element available for an NW circuit. Error is detected during a current soft restart or SAVE procedure and leads to a hard restart in the relevant LTG. Action: Save error message data and contact your Next level of...
  • Page 575 f4399.fm Nur für den internen Gebrauch F4399 NO GSP Type: Diagnosis-specific (Format 24) Short text: No device memory Cause: This error occurs if the dynamic device memories cannot be accessed while saving, deleting and restoring the established connection data. This error leads to a soft restart. Action: Save error message data and contact your Next level of...
  • Page 576 f4400.fm Nur für den internen Gebrauch F4400 VECO DEV CP, BAD SEIZURE Type: Diagnosis relevant (Format 24) Short text: Blocked device in the device memory. Cause: Blocked device in the call processing (CP) device memory. The CPH bit is set but the device is in the "idle"...
  • Page 577 f4400.fm Nur für den internen Gebrauch Byte 22 CP LineType Byte 23 CP MultLineType Byte 24 CP BusType Byte 25-26 LODEN Byte 27-28 Dynamic LODEN Byte 29 CP Device Type Byte 30 CP State Byte 31 FEATURE_CODE Byte 32 FEATURE_STATE Byte 33-43 FEATURE_STACK Byte 44-46...
  • Page 578 f4401.fm Nur für den internen Gebrauch F4401 VECO DEV DH, BAD SEIZURE Type: Diagnosis-specific (Format 26) Short text: Blocked device in device memory Cause: Blocked device found in device handler device memory (DH), i.e. the device handler bit is set but the same device is in idle state in the call processing device memory (CPH). Action: Save error message data and contact your Next level of...
  • Page 579 f4402.fm Nur für den internen Gebrauch F4402 VECO BAD LINE PATH SEIZURE Type: Diagnosis-specific (Format 24) Short text: Blocked short path Cause: Blocked short path found, i.e., path seized but no associated device can be identified. Auxiliary data may point to cause (DH Device Type). The appropriate bit for the blocked short path is reset in the device memory.
  • Page 580 f4403.fm Nur für den internen Gebrauch F4403 VECO B-CHAN, BAD SEIZURE Type: Diagnosis-specific (Format 24) Short text: Blocked B-channel Cause: Blocked B-channel found without associated device. The appropriate bit for the blocked B-channel is reset in the device memory. Action: Save error message data and contact your Next level of support.
  • Page 581 f4404.fm Nur für den internen Gebrauch F4404 VECO CODE RCVR, BAD SEIZURE Type: Diagnosis-specific (Format 24) Short text: Blocked code receiver Cause: Blocked code receiver found without associated device. The appropriate bit for the blocked code receiver is reset in the device memory. Action: Save error message data and contact your Next level of...
  • Page 582 f4405.fm Nur für den internen Gebrauch F4405 VECO DIALTONE RCVR,BAD SEIZ Type: Diagnosis-specific (Format 24) Short text: Dial tone receiver Cause: Blocked dial tone receiver found without associated device. The appropriate bit for the blocked dial tone receiver is reset in the device memory. Action: Save error message data and contact your Next level of...
  • Page 583 f4406.fm Nur für den internen Gebrauch F4406 VECO CONF, BAD SEIZURE Type: Diagnosis-specific (Format 24) Short text: Blocked conference status byte Cause: Blocked conference user found without associated devices. The appropriate bit for the blocked conference user is reset in the device memory and the circuit is released. Action: Save error message data and contact your Next level of...
  • Page 584 f4407.fm Nur für den internen Gebrauch F4407 VECO NO DH ANSWER Type: Diagnosis relevant (Format 24) Short text: No response to test job Cause: No response to test performed by device handler (DH). Timeout (5 min.) elapsed. The error can be caused by board loadware (LW) which does not provide confirmation. Action: Save error message data and contact your Next level of...
  • Page 585 f4408.fm Nur für den internen Gebrauch F4408 VECO LTG RESET ERROR Type: Diagnosis-specific (Format 42) Short text: LTG reset task not completed Cause: One of the reset tasks in the LTG has not completed, e.g. due to timeout. In 3000 systems, the LTG carries out a soft restart. Action: Save error message data and contact your Next level of...
  • Page 586 f4410.fm Nur für den internen Gebrauch F4410 VECO CP INCONSISTENT Type: Diagnosis-specific (Format 24) Short text: Inconsistent CP Statuses Cause: Status of sub-unit (SU) and main device inconsistent. This error message only concerns attendant consoles. A release message is sent to the call processing device memory in these cases. Action: Save error message data and contact your Next level of...
  • Page 587 f4411.fm Nur für den internen Gebrauch F4411 VECO CODE SENDER, BAD SEIZ Type: Diagnosis-specific (Format 24) Short text: Blocked code transmitter Cause: Blocked code transmitter found in the device handler. The appropriate bit for the blocked code transmitter is reset in the device memory. Action: Save error message data and contact your Next level of...
  • Page 588 f4412.fm Nur für den internen Gebrauch F4412 VECO CONS TEST ERROR Type: Diagnosis-specific (Format 24) Short text: Inconsistencies in memories Cause: Inconsistencies detected when comparing the device search memory with the device memory. The appropriate bit is reset in the device search memory. Action: Save error message data and contact your Next level of...
  • Page 589 f4413.fm Nur für den internen Gebrauch F4413 VECO MFC SEND/RCVR,BAD SEIZ Type: Diagnosis-specific (Format 24) Short text: Blocked MFC transmitter/receiver Cause: Blocked MFC transmitter or MFC receiver found in the device handler. The appropriate bit for the blocked MFC transmitter/receiver is reset in the device memory. Action: Save error message data and contact your Next level of...
  • Page 590 f4414.fm Nur für den internen Gebrauch F4414 VECO CC RESET ERROR Type: Diagnosis-specific (Format 24) Short text: CC reset task not completed Cause: A common control (CC) reset task has not completed. Action: Save error message data and contact your Next level of support.
  • Page 591 f4415.fm Nur für den internen Gebrauch F4415 VECO NW CR, BAD SZ Type: Diagnosis-specific (Format 24) Short text: LODEN/DTI entry missing Cause: A call reference is allocated in a digital NW circuit, but no corresponding LODEN/ DTI entry exists. The VECO resets the appropriate bit for the call reference. Action: Save error message data and contact your Next level of...
  • Page 592 f4416.fm Nur für den internen Gebrauch F4416 VECO NW CR CP, BAD SZ Type: Diagnosis-specific (Format 24) Short text: No valid LODEN Cause: No logical device number is found for an allocated call reference in the CP device memory. The VECO resets the appropriate bit for the call reference. Action: Save error message data and contact your Next level of...
  • Page 593 f4417.fm Nur für den internen Gebrauch F4417 VECO NW CR DH, BAD SZ Type: Diagnosis-specific (Format 24) Short text: No valid DTI Cause: No valid DTI is found for an allocated call reference in the DH device memory. The VECO resets the appropriate bit for the call reference. Action: Save error message data and contact your Next level of...
  • Page 594 f4418.fm Nur für den internen Gebrauch F4418 VECO SB CRI CP BADSZ Type: Diagnosis-specific (Format 24) Short text: No valid LODEN Cause: No valid LODEN can be found for a functional terminal with the allocated call reference in the CP device memory. The VECO resets the appropriate bit for the call reference. Action: Save error message data and contact your Next level of...
  • Page 595 f4419.fm Nur für den internen Gebrauch F4419 VECO SB CRI DH BADSZ Type: Diagnosis-specific (Format 24) Short text: No valid DTI Cause: No valid DTI is found for a functional terminal with the allocated call reference in the DH device memory. The VECO resets the appropriate bit for the call reference. Action: Save error message data and contact your Next level of...
  • Page 596 f4420.fm Nur für den internen Gebrauch F4420 VECO BAD LINK PATH SEIZURE Type: Diagnosis-specific (Format 24) Short text: Blocked long path Cause: Blocked long path found, i.e., path seized but no associated device can be identified. Auxiliary data may point to cause (CP Device Type). The appropriate bit for the blocked long path is reset in the device memory.
  • Page 597 f4421.fm Nur für den internen Gebrauch F4421 VECO STATISTIC CC Type: Diagnosis relevant (Format 24) Short text: Statistics threshold value exceeded Cause: Once the statistics threshold value of a VECO error class has been reached, all error counters are listed according to their CP device type. CC error counters, that are only registered together in CC, are at the beginning of the statistics data.
  • Page 598 f4422.fm Nur für den internen Gebrauch F4422 VECO STATISTIC LTG Type: Diagnosis relevant (Format 24) Short text: Statistic threshold value exceeded Cause: Once the statistics threshold value of a VECO error class has been reached, all error counters are listed according to their DH device types. The DH error counters, that are only registered together in the LTG, are at the beginning of the statistic data.
  • Page 599 f4424.fm Nur für den internen Gebrauch F4424 VECO CPB, BAD SEIZURE Type: Diagnosis relevant (Format 24) Short text: Blocked call processing buffer found Cause: The call processing buffer was not enabled when a connection was cleared down by the switch. System reaction: Call processing buffer is enabled by VECO.
  • Page 600 f4425.fm Nur für den internen Gebrauch F4425 VECO CBM RESOURCE PER BADSZ Type: Diagnosis relevant (Format 24) Short text: Bad CBM seizure in periphery. Cause: There is no corresponding CBM seizure in CC to an existing CBM seizure in periphery. System reaction: VECO releases the resource.
  • Page 601 f4426.fm Nur für den internen Gebrauch F4426 VECO CBM RESOURCE CC BADSZ Type: Diagnosis relevant (Format 24) Short text: Bad CBM seizure in CC. Cause: There is no corresponding CBM seizure in periphery to an existing CBM seizure in CC. System reaction: VECO releases the resource.
  • Page 602 f4427.fm Nur für den internen Gebrauch F4427 VECO CBM RESOURCE TSL BADSZ Type: Diagnosis relevant (Format 24) Short text: Defective CBM seizure of HWY/TSL. Cause: CBM is seized for a path but the device table for the corresponding LODEN is not seized anymore or the LODEN is invalid.
  • Page 603 f4428.fm Nur für den internen Gebrauch F4428 VECO CBM NO PERI ANSWER Type: Diagnosis relevant (Format 24) Short text: No answer from LW to VECO request. Cause: The loadware of the affected board (e.g. LTUCC, NCUI) does not respond on a request of VECO.
  • Page 604 f4429.fm Nur für den internen Gebrauch F4429 VECO EXT PERI BADSZ Type: Diagnosis relevant (Format 24) Short text: Bad seizure for external connections on peripheral board. Cause: VECO detected that there are bad seizures in periphery (NCUI, STMI) for connections to the external network.
  • Page 605 f4430.fm Nur für den internen Gebrauch F4430 VECO INT PERI BADSZ Type: Diagnosis relevant (Format 24) Short text: Bad seizure for internal connections on peripheral board. Cause: VECO detected that there are bad seizures in periphery (NCUI) for internal connections. System reaction: VECO releases the bad connections.
  • Page 606 f4431.fm Nur für den internen Gebrauch F4431 VECO EXT CC BADSZ Type: Diagnosis relevant (Format 24) Short text: Bad seizure for external connections in CC. Cause: VECO detected that there are bad seizures in CC for connections to the external network.
  • Page 607 f4432.fm Nur für den internen Gebrauch F4432 VECO INT CC BADSZ Type: Diagnosis relevant (Format 24) Short text: Bad seizure for internal connections in CC. Cause: VECO detected that there are bad seizures in CC for internal connections. System reaction: VECO releases the bad connections.
  • Page 608 f4433.fm Nur für den internen Gebrauch F4433 VECO HHS MTS TIMER EXPIRED Type: Diagnosis-specific (Format 24) Short text: No answer from PP to VECO request. Cause: The component PreProcessing does not respond on a request of VECO. With this request the MTS data should be read from RTM board. System reaction: Only signalling.
  • Page 609 f4434.fm Nur für den internen Gebrauch F4434 VECO CYCLE END Type: Diagnosis-specific (Format 24) Short text: All resources have been checked. Cause: All resources have been checked (advisory message). The output of this message is set at the operating terminal via AMO DIAGS (VECO switch S06). System reaction: Only signalling.
  • Page 610 f4435.fm Nur für den internen Gebrauch F4435 VECO IPDA CYCLE END Type: Diagnosis-specific (Format 24) Short text: All IPDA resources have been checked. Cause: All IPDA resources have been checked (advisory message). The output of this message is set at the operating terminal via AMO DIAGS (VECO switch S06). System reaction: Only signalling.
  • Page 611 f4436.fm Nur für den internen Gebrauch F4436 VECO DIAGNOSIS ADVISORY Type: Diagnosis-specific (Format 24) Short text: Advisory message. Cause: Advisory message. When Resource Manager is configured sometimes connections will be blocked if no resources are free. In such a case an F4436 advisory message is signalled. Usually the reason for the error message is a correct one and defined by configuration i.e.
  • Page 612 f4436.fm Nur für den internen Gebrauch Not enough bandwidth for a HFA-HFA connection. Error Address: DBDB (Word) MessageID (Word) LTG_LINE->PEN of Ext.A (Word) Sector Attribute (Powerset:DB_M_RESM_SSPA_SCT_ATT_SET) (Word) Sector where lack of resources was recognized (Word) Configured Bandwith (Byte) LTGLINE A (word) LTGLINE B (word) Filler DB_M_RESM_SSPA_SCT_ATT_SET = SET (...
  • Page 613 f4436.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 614 f4450.fm Nur für den internen Gebrauch F4450 OVERLOAD Type: Diagnosis-specific (Format 00) Short text: Call processing buffer shortage Cause: Call processing (CP) reports a call processing buffer (CPB) shortage. CPBs are used for storing the connection data for established connections. A resource shortage of this type either means that the system traffic capacity is exhausted (too many connections), or indicates a program error.
  • Page 615 f4451.fm Nur für den internen Gebrauch F4451 END OF OVERLOAD Type: Diagnosis-specific (Format 00) Short text: End of call processing buffer shortage Cause: Call processing (CP) reports end of call processing buffer (CPB) shortage, i.e., connections have been terminated and the associated call processing buffers have been released. System reaction: system permits new seizures.
  • Page 616 f4452.fm Nur für den internen Gebrauch F4452 OVERLOAD SUPV. TIMEOUT Type: Diagnosis-specific (Format 00) Short text: No end of CPB shortage Cause: End of CPB shortage is not reported within a specific interval. System reaction: system reacts with a restart. Action: See F4450.
  • Page 617 f4453.fm Nur für den internen Gebrauch F4453 CP MBX OVERLOAD Type: Diagnosis-specific (Format 00) Short text: CP mailbox overload Cause: The number of allocated CP event buffers in the PP/DH pool exceeds a specified threshold (overload strategy). System reaction: system activates overload safeguard routine. Action: Check which acknowledgment message is output, F4454...
  • Page 618 f4454.fm Nur für den internen Gebrauch F4454 CP MBX OVERLOAD END Type: Diagnosis-specific (Format 00) Short text: End of CP mailbox overload Cause: The number of allocated CP event buffers in the PP/DH pool has dropped back below the specified threshold (overload strategy). Positive acknowledgment of F4453. System reaction: system deactivates overload safeguard routine.
  • Page 619 f4455.fm Nur für den internen Gebrauch F4455 CP MBX SUPV. TIMEOUT Type: Diagnosis-specific (Format 00) Short text: No end of CP mailbox overload Cause: End of CP mailbox overload is not reported within a specific interval (F4454). System reaction: system reacts with a restart. Action: If this error message occurs frequently, save the error message data and contact your Next level of...
  • Page 620 f4456.fm Nur für den internen Gebrauch F4456 DYNAMIC OVERLOAD Type: Diagnosis-specific (Format 00) Short text: Start of dynamic overload Cause: Start of dynamic overload (processor overload). System reaction: all further initial seizure attempts are rejected. Action: Check that positive acknowledgment is output (F4457). Save error message data and contact your Next level of support.
  • Page 621 f4457.fm Nur für den internen Gebrauch F4457 END OF DYNAM. OVERLOAD Type: Diagnosis-specific (Format 00) Short text: End of dynamic overload Cause: End of dynamic overload (processor overload). System reaction: system permits new seizures. Action: Positive acknowledgment of F4456. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 622 f4458.fm Nur für den internen Gebrauch F4458 DH MBX OVERLOAD Type: Diagnosis-specific (Format 00) Short text: DH mailbox overload Cause: The number of buffer elements used in the PP/DH receive pool exceeds a specified threshold (overload strategy). System reaction: system activates overload safeguard routine. Action: Check which acknowledgment message is output, F4459...
  • Page 623 f4459.fm Nur für den internen Gebrauch F4459 DH MBX OVERLOAD END Type: Diagnosis-specific (Format 00) Short text: End of DH mailbox overload Cause: The number of buffer elements used in the PP/DH receive pool has dropped back below the specified threshold (overload strategy). Positive acknowledgment of F4458. System reaction: system deactivates overload safeguard routine.
  • Page 624 f4460.fm Nur für den internen Gebrauch F4460 DH MBX SUPV. TIMEOUT Type: Diagnosis-specific (Format 00) Short text: No end of DH mailbox overload Cause: The lower threshold for (F4459) is not reached within a specific interval. A program error may have occured. System reaction: system reacts with a restart.
  • Page 625 f4461.fm Nur für den internen Gebrauch F4461 TRANSIT CTR OVERFLOW Type: Service-specific (Format 22) Short text: Overflow of TRANSIT counter Cause: Connection setup canceled through TRANSIT counter overflow. The TRANSIT counter counts the number of transit nodes involved in a connection setup in a meshed network. The connection setup is canceled if this counter reaches a specific threshold value, in order to prevent "endless"...
  • Page 626 f4462.fm Nur für den internen Gebrauch F4462 SATELLITE CTR OVERFLOW Type: Service-specific (Format 22) Short text: Overflow of SATELLITE counter Cause: Connection setup canceled through SATELLITE counter overflow. The SATELLITE counter counts the number of satellite route seizures attempted during a connection setup in a meshed network.
  • Page 627 f4463.fm Nur für den internen Gebrauch F4463 CAS DIVERT OVERFLOW Type: Service-specific (Format 22) Short text: Overflow of CAS call diversion counter Cause: Overflow of CAS call diversion counter in a meshed network. A network loop has occurred: attendant calls are being forwarded to an attendant console in the CAS group by the night station, despite the fact that the night service option has been activated (looped, multiple call forwarding).
  • Page 628 f4464.fm Nur für den internen Gebrauch F4464 LOAD MEASUREMENT DATA Type: Diagnosis-relevant (Format 17, 48, 49) Short text: Processor load with average value or ZAUSL differences. Cause: Output of processor load with average value or the ZAUSL differences. The output of this diagnosis information was started with the AMO DIAGS.
  • Page 629 f4464.fm Nur für den internen Gebrauch Scenario 2: ZAUSL differences: ZAUSL DIFFERENCES 1/2: 000000 000006 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000...
  • Page 630 f4464.fm Nur für den internen Gebrauch DB_TM_EREIGN_DMDR_INSF_BUF, /* DBDR buffer could not be obtained, therefore no data call record generated */ DB_TM_EREIGN_RNGI_BEN , /* Individual speed dialing - use */ DB_TM_EREIGN_ZIELT_BEN , /* Destination keys - use */ DB_TM_EREIGN_NAMENST_BEN, /* Name/repertory keys - use */ DB_TM_EREIGN_DIREKTRUF_BEN, /* Automatic DSS keys - use */ DB_TM_EREIGN_AUL_EINSCH , /* Call forwarding - activate */ DB_TM_EREIGN_AK_AS_DURCHF , /* Call forwarding/override - carry OUT */...
  • Page 631 f4464.fm Nur für den internen Gebrauch DB_TM_EREIGN_INT_DYN_OVL, /* Number of 1.5s intervals in dynamic overload */ DB_TM_EREIGN_DYN_OVL_BEG, /* Number of times the switch goes from non-overload to a dynamic overload condition */ DB_TM_EREIGN_CALL_ATT_OVL, /* Number of calls of the procedure DB_T_DH_S_UEBERLAST if the overload bit is set */ DB_TM_EREIGN_ADAPT_ALL, /* ALL EVENTS FOR AM ADAPT */ DB_TM_EREIGN_ADAPT_NEG_TIM, /* EVENTS FOR AM ADAPT, THAT HAVE BEEN NEGATIVELY...
  • Page 632 f4465.fm Nur für den internen Gebrauch F4465 CP CBM RESOURCES CC Type: Service relevant (Format 43) Short text: Information about the CBM resources in CC. Cause: This message shows if CBM resources which are counted in CC are low or run out. The message is reported by call processing (CP).
  • Page 633 f4466.fm Nur für den internen Gebrauch F4466 VECO CBM RESOURCES CC Type: Service relevant (Format 43) Short text: Information about the CBM resources in CC. Cause: This message shows if CBM resources which are counted in CC are low or run out. The message is reported by VECO.
  • Page 634 f4500.fm Nur für den internen Gebrauch F4500 RESTART Type: Service-specific (Format 18) Short text: Restart initiated by AMO Cause: Error analysis (FA) is to make a restart in a certain control unit at the request of an AMO. Action: Restart will be carried out by the system. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 635 f4501.fm Nur für den internen Gebrauch F4501 RELOAD Type: Service-specific (Format 18) Short text: Reload initiated by AMO Cause: Error analysis (FA) is to make a reload in a certain control unit at the request of an AMO. Action: Reload will be carried out by the system A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 636 f4502.fm Nur für den internen Gebrauch F4502 SYS RESTART Type: Service-specific (Format 18) Short text: Restart initiated by AMO Cause: Error analysis (FA) is to make a system restart at the request of an AMO. Action: Restart will be carried out by the system. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 637 f4503.fm Nur für den internen Gebrauch F4503 PS NODE Type: Service-specific - US-specific (Format 29) Short text: Periodical switching of SWU via time task Cause: A periodical switching of the SWU was executed. An SR CC was initiated via specific AMO events.
  • Page 638 f4505.fm Nur für den internen Gebrauch F4505 PS CANCEL Type: Service-specific - US-specific (Format 29) Short text: The timer for periodical SWU switching was cancelled Cause: The time task for periodical SWU switching was cancelled; the timer for the next period was activated.
  • Page 639 f4506.fm Nur für den internen Gebrauch F4506 SOFT RESTART Type: Service-specific (Format 29) Short text: Soft restart initiated by AMO Cause: Soft restart initialized by REST AMO. Action: Soft restart will be carried out by the system. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 640 f4507.fm Nur für den internen Gebrauch F4507 LTUR HARD RESTART Type: Service-specific (Format 18) Short text: Hard restart initiated by AMO Cause: LTUR hard restart requested via AMO. This confirms that the task was accepted. Action: Hard restart will be carried out by the system. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 641 f4508.fm Nur für den internen Gebrauch F4508 LTUR SOFT RESTART Type: Service-specific (Format 18) Short text: Soft restart initiated by AMO Cause: LTUR soft restart requested via AMO. This confirms that the task was accepted. Action: Soft restart will be carried out by the system. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 642 f4509.fm Nur für den internen Gebrauch F4509 LTUR RELOAD Type: Service-specific (Format 18) Short text: Reload initiated by AMO Cause: LTUR reload requested via AMO. This confirms that the task was accepted. Action: Reload will be carried out by the system. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 643 f4604.fm Nur für den internen Gebrauch F4604 MAINTENANCE Type: Service-specific Short text: Trace job via TRACS AMO Cause: The trace job was started with the trace conditions defined in the TRACS AMO. The trace situation created with the AMO has occurred. This message usually consists of plain text, which is either self-explanatory or explained in the auxiliary data or refers to a specific section of the Service Manual.
  • Page 644 f4624.fm Nur für den internen Gebrauch F4624 MAINTENANCE Type: Service-specific Short text: Service advisory message, initiated by the alarm CENTRAL:029 MAINTENANCE NOTE. Cause: This message usually consists of plain text, which is either self-explanatory or refers to a specific section of the Service Manual. Action: The MAINTENANCE NOTE alarm must always be reset (deleted) via AMO.
  • Page 645 f4644.fm Nur für den internen Gebrauch F4644 MAINTENANCE Type: Service-specific Short text: Service advisory message, initiated by the alarm CENTRAL:029 MAINTENANCE NOTE. Cause: This message usually consists of plain text, which is either self-explanatory or refers to a specific section of the Service Manual. Action: The MAINTENANCE NOTE alarm must always be reset (deleted) via AMO.
  • Page 646 f4664.fm Nur für den internen Gebrauch F4664 MAINTENANCE Type: Service-specific Short text: Service advisory message, initiated by the alarm CENTRAL:029 MAINTENANCE NOTE. Cause: This message usually consists of plain text, which is either self-explanatory or refers to a specific section of the Service Manual. Action: The MAINTENANCE NOTE alarm must always be reset (deleted) via AMO.
  • Page 647 f4684.fm Nur für den internen Gebrauch F4684 MAINTENANCE Type: Service-specific Short text: Service advisory message, initiated by the alarm CENTRAL:029 MAINTENANCE NOTE. Cause: This message usually consists of plain text, which is either self-explanatory or refers to a specific section of the Service Manual. Example (if data records cannot be written): "CDB-POOL 60% FULL"...
  • Page 648 f4703.fm Nur für den internen Gebrauch F4703 STATISTIC OVERFLOW Type: Diagnosis-relevant (Format 0) Short text: Statistics overflow. Cause: Too many errors have occurred within a brief time interval: • Soft restarts • SW errors Action: If the error occurs frequently, save the error messages and contact a product specialist.
  • Page 649 f4704.fm Nur für den internen Gebrauch F4704 MAINTENANCE Type: Service-relevant (Format 34) Short text: Maintenance note, triggered by the MAINTENANCE NOTE alarm. Cause: This message contains a transparent text in the rule that is either self-explanatory, refers to another service manual chapter or is described below. Action: In general, the above-mentioned alarm should be deleted with an AMO after fault removal:...
  • Page 650 f4704.fm Nur für den internen Gebrauch RTO TEST ERROR Cause: Connection loss between WAML and ADP. The result of the RTO test of the WAML connection via the internal LAN to the ADP was negative (LOOP DATA ERR) as confirmed by the FA. See also self-explanatory message text in the error message! Action: Use AMO TSU to check if the connection to the ADP is still defective: PR-TSU:...
  • Page 651 f4704.fm Nur für den internen Gebrauch Interpretation of auxiliary data: see F5959. LAN CONTROLLER DEFECT NO ACCESS TO EXTERNAL LAN Cause: Hardware error. The LAN controller is set in the direction ’external’ LAN is not possible. This LAN interface was put out of service by the LW. Destinations at this interface cannot be accessed any longer. Action: Take the board out of service and put it back in service manually;...
  • Page 652 f4704.fm Nur für den internen Gebrauch TRADEBOARD E DOWN - SEE SYSTEM MANAGER REPORT Cause: A Tradeboard E failed, it cannot be accessed by the SLMY. Action: See system manager for additional information and notes. Clarify whether Tradeboard E can still be reached via LAN and establish its status. If still accessible via LAN: Check the cables to the MUXY, Terminal replacement If multiple terminals on the same MUXY fail: Check the MUXY, its power supply and cabling.
  • Page 653 f4704.fm Nur für den internen Gebrauch FRONT REFERENCE NOT CONFIGURED WITH AMO REFTA Cause: A front reference was connected to or removed from the clock generator, although the front reference was not configured with the AMO REFTA. Action: Configuring the front reference with an AMO: ADD-REFTA:FRONT; CONFIGURATION OF SIGNALING ADDRESS MISSING Cause: An AP has been configured with AMO UCSU but the parameter APIPADR has not yet...
  • Page 654 f4704.fm Nur für den internen Gebrauch ROUTE FOR TAP CONNECTION COULD NOT BE CHANGED Cause: An error occurred when the route entry for the TAP connection to an AP has been changed from primary path to survivability path or vice versa for feature signaling survivability. Action: Checking and correcting the IP addresses with AMO UCSU.
  • Page 655 f4704.fm Nur für den internen Gebrauch CONFIGURATION OF SURVIVABILITY PATH MISSING Cause: With AMO STMIB the signaling path switch mode SIGPTHSW has been configured with the value EXTEND or SURVONLY but signaling survivability has not yet been configured for the AP. Action: Action: Either changing with AMO STMIB the signaling path switch mode SIGPTHSW back to default value STD or configuring the missing survivability configuration with AMO APRT.
  • Page 656 f4704.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 657 f4706.fm Nur für den internen Gebrauch F4706 RESTART LEVEL Type: Service-specific (Format 41) Short text: Type of restart carried out Cause: This SWU error message replaces F4266 (advisory message with HEX data). This message is always output by dependability following a restart, and describes the type of restart in plain text as well as a possible restart escalation.
  • Page 658 f4750.fm Nur für den internen Gebrauch F4750 NO RESP FROM LTUR Type: Service-specific (Format ) Short text: No response from LTUR Cause: Dynamic overload or faulty LTUR. Error message is output by defective LTUR. Action: Replace board. If this does not work, save the error message data and contact your Next level of support.
  • Page 659 f4751.fm Nur für den internen Gebrauch F4751 NO RESP FROM SCAN Type: Service-specific (Format ) Short text: No response from LTUR Cause: Dynamic overload or faulty LTUR. Error message is output by defective LTUR. Action: Replace board. If this does not work, save the error message data and contact your Next level of support.
  • Page 660 f4752.fm Nur für den internen Gebrauch F4752 NO RESPONSE SR LTUR Type: Service-specific (Format 24) Short text: No response from LTG subsystem Cause: Error in transport layer between CC and LTG. Error message indicates LTG concerned. Action: Analyze environment. If this does not work, save the error message data and contact your Next level of support.
  • Page 661 f4753.fm Nur für den internen Gebrauch F4753 NO LTU REPLY Type: Service-specific (Format ) Short text: No response from LTUR Cause: None of the LTUs associated with an LTG is responding. Possible reason: dynamic overload. Error message is output by affected LTG. Action: Analyze environment.
  • Page 662 f4754.fm Nur für den internen Gebrauch F4754 (UN)SAVE UNDETERMINED Type: Diagnosis-specific (Format 24) Short text: Invalid save list Cause: The device memories assigned to a stored connection are marked as "saved" in the CC standby half of the SWU, but entered in the save list under the wrong SAVE TYPE. Action: The standby CC half executes a hard restart.
  • Page 663 f4755.fm Nur für den internen Gebrauch F4755 SAVELIST INCONSISTENT Type: Diagnosis-specific (Format 24) Short text: No partner for saved device Cause: A saved device connection without a corresponding connection partner has been detected in the save list during the call processing database recovery. This error only occurs in soft restarts of simplex CCs.
  • Page 664 f4756.fm Nur für den internen Gebrauch F4756 2PTY CONNECTION EXISTS Type: Diagnosis-specific (Format 24) Short text: Saved connection deleted Cause: One of the communication partners of a connection to be saved is already marked as saved. Action: The old save connection will be deleted by the PABX, and the new connection saved instead.
  • Page 665 f4757.fm Nur für den internen Gebrauch F4757 DEVICE BUSY Type: Diagnosis-specific (Format 24) Short text: Device busy Cause: Device is already busy. This error message usually appears in conjunction with F4756. The message is sent from the standby LTG. Action: Analyze frequency of occurrence and environment.
  • Page 666 f4758.fm Nur für den internen Gebrauch F4758 DEVICE IDLE Type: Diagnosis-specific (Format 24) Short text: Device is already released Cause: Device is already released. This message is sent from the standby LTG half. Action: Save error message data and contact your Next level of support.
  • Page 667 f4759.fm Nur für den internen Gebrauch F4759 NO CPB USED Type: Diagnosis-specific (Format 24) Short text: CPB not released Cause: No CPB can be released, or CPB is already released. Action: Save error message data and contact your Next level of support.
  • Page 668 f4760.fm Nur für den internen Gebrauch F4760 NO S0 DYN DEVICE TABLE Type: Diagnosis-specific (Format 24) Short text: No dynamic device memory Cause: No dynamic device memory available for saving device data. Action: The standby half of the SWU-CC executes a hard restart. Save error message data and contact your Next level of support.
  • Page 669 f4761.fm Nur für den internen Gebrauch F4761 NO IGNORED Type: Diagnosis-specific (Format 24) Short text: Connection not saved Cause: One of the devices of a connection which is to be saved cannot be saved. Action: The connection data will not be saved. Analyze frequency of occurrence and environment.
  • Page 670 f4762.fm Nur für den internen Gebrauch F4762 SAVELIST OVERFLOW Type: Diagnosis-specific (Format 24) Short text: Connection not saved Cause: Insufficient memory for saving a connection. The connection data will not be saved. Action: Use AMO DIMSU to enlarge the save list. EINR-DIMSU:TYPE=CC2,SILI=<value>...
  • Page 671 f4763.fm Nur für den internen Gebrauch F4763 PATH ALREADY IDLE Type: Diagnosis-specific (Format 24) Short text: Path already released Cause: The system has attempted to release the connection path of a saved connection which was either already released or not seized in the first place. This message occurs in normal operation. Action: Analyze frequency of occurrence and environment.
  • Page 672 f4764.fm Nur für den internen Gebrauch F4764 PATH ALREADY BUSY Type: Diagnosis-specific (Format 24) Short text: Path busy Cause: The system attempts to seize the path of a saved connection and finds that it already busy. This error message may occur in normal operation and also during a simplex CC soft restart. Action: Analyze frequency of occurrence and environment.
  • Page 673 f4765.fm Nur für den internen Gebrauch F4765 B-CHAN ALREADY IDLE Type: Diagnosis-specific (Format 24) Short text: B-channel already released Cause: The system has attempted to release the B-channel of a saved connection which was either already released or not seized in the first place. This error message occurs in normal operation. Action: Analyze frequency of occurrence and environment.
  • Page 674 f4766.fm Nur für den internen Gebrauch F4766 B-CHAN ALREADY BUSY Type: Diagnosis-specific (Format 24) Short text: B-channel busy Cause: The system attempts to seize the B-channel of a saved connection, only to find it already busy. This error message may occur in normal operation and also during a simplex CC soft restart. Action: Analyze frequency of occurrence and environment.
  • Page 675 f4767.fm Nur für den internen Gebrauch F4767 LODEN MISMATCH IN CP Type: Diagnosis-specific (Format 24) Short text: LODENs do not match Cause: The system discovers that the LODENs of the saved devices do not match on erasing the connection data. Action: Analyze frequency of occurrence and environment.
  • Page 676 f4768.fm Nur für den internen Gebrauch F4768 CPB IDX MISMATCH IN CP Type: Diagnosis-specific (Format 24) Short text: Invalid CPB-indices Cause: Connection to be saved has invalid CPB indices in the device memories. Action: The connection will not be saved. Analyze frequency of occurrence and environment. If this does not work, save the error message data and contact your Next level of support.
  • Page 677 f4769.fm Nur für den internen Gebrauch F4769 NO RESPONSE DD UPDATE Type: Diagnosis-specific (Format 24) Short text: LTG update not acknowledged Cause: LTG dynamic data update during Standby Restoration is not acknowledged. Action: Save error message data and contact your Next level of support A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 678 f4770.fm Nur für den internen Gebrauch F4770 INVALID SAVETYPE Type: Diagnosis-specific (Format 24) Short text: Invalid save list Cause: Invalid SAVE TYPE entry in the save list for a saved device. Action: The save element will be deleted. Analyze frequency of occurrence and environment. If this does not work, save the error message data and contact your Next level of support.
  • Page 679 f4771.fm Nur für den internen Gebrauch F4771 LODEN 0 OR IDENT IN CP Type: Diagnosis-specific (Format 24) Short text: Invalid LODEN Cause: Connection to be saved or deleted has invalid LODEN entries: (LODEN = 0 or LODEN A = LODEN B). Action: The connection will not be saved (i.e.
  • Page 680 f4772.fm Nur für den internen Gebrauch F4772 CONNECTION MISMATCH Type: Diagnosis-specific (Format 24) Short text: Invalid partner LODEN Cause: Connection to be deleted has an invalid partner LODEN. Action: The device with the valid LODEN will be deleted. Analyze frequency of occurrence and environment.
  • Page 681 f4773.fm Nur für den internen Gebrauch F4773 PARTNER NOT IN SAVELST Type: Diagnosis-specific (Format 24) Short text: Device is not saved Cause: The system attempts to delete a saved connection of which one of the devices is no longer saved (no entry found). Action: Analyze frequency of occurrence and environment.
  • Page 682 f4776.fm Nur für den internen Gebrauch F4776 SAVED 1PTY EXIST Type: Diagnosis-specific (Format 24) Short text: Already saved as single device Cause: One of the call parties is already in the save list, as a single device. Action: This save list entry is deleted, and the two-party call to be saved is saved. Analyze frequency of occurrence and environment.
  • Page 683 f4777.fm Nur für den internen Gebrauch F4777 INVALID DEVICE Type: Diagnosis-specific (Format 24) Short text: Save type not carried out Cause: The required save type cannot be carried out for this device. Action: The old connection is deleted and the new one saved. Analyze frequency of occurrence and environment.
  • Page 684 f4778.fm Nur für den internen Gebrauch F4778 INVALID TSL Type: Diagnosis-specific (Format 24) Short text: Invalid route data Cause: The connection to be saved has invalid route data. Action: The connection will not be saved. Analyze frequency of occurrence and environment. If this does not work, save the error message data and contact your Next level of support.
  • Page 685 f4779.fm Nur für den internen Gebrauch F4779 SEQUENCE ERROR Type: Diagnosis-specific (Format 24) Short text: Unexpected sequence Cause: Different save types have been carried out in an unexpected sequence. Action: The saved data is deleted, and the new data to be saved is saved. Analyze frequency of occurrence and environment.
  • Page 686 f4780.fm Nur für den internen Gebrauch F4780 NO RESOURCES Type: Diagnosis-relevant (Format 24) Short text: Error in the standby processor, no CP or DH data buffer Cause: When saving a connection for Nx64, no CP or DH data buffer is available. System reaction: The CC standby (SWU) causes a hard restart.
  • Page 687 f4781.fm Nur für den internen Gebrauch F4781 NO NW DYN DEVICE TABLE Type: Diagnosis-relevant (Format 24) Short text: No dynamic NW device memory Cause: When saving a D-channel connection, no dynamic pool device buffer can be seized in the CP for networking. System reaction: The CC standby (SWU) causes a hard restart.
  • Page 688 f4782.fm Nur für den internen Gebrauch F4782 PARTIAL RESOURCES Type: Diagnosis-relevant (Format 24) Short text: Not all resources for a connection available. Cause: When saving a connection, all resources cannot be seized. The backup was still performed. System reaction: Soft restart only after corresponding statistics overflow Action: Analyze the frequency and scope of the error message.
  • Page 689 f4783.fm Nur für den internen Gebrauch F4783 UPD COSTI MISMATCH Type: Diagnosis relevant (Format 24) Short text: Mismatch of costi buffer index for a saved connection. Cause: The costi buffer index to update does not match the index in the save list. System reaction: Only signalling.
  • Page 690 bk_error5000.fm Nur für den internen Gebrauch F5000 8.6 F5000 A9000 F1000 F2000 F3000 F4000 -- F5000 -- F6000 F7000 F8000 F5000 F5001 F5002 F5003 F5004 F5019 F5020 F5021 F5030 F5031 F5032 F5033 F5034 F5035 F5036 F5037 F5038 F5039 F5041 F5042 F5043 F5044 F5045...
  • Page 691 bk_error5000.fm Nur für den internen Gebrauch F5000 F5748 F5749 F5750 F5751 F5752 F5753 F5754 F5755 F5756 F5757 F5758 F5759 F5760 F5761 F5762 F5763 F5764 F5765 F5766 F5767 F5768 F5769 F5770 F5771 F5772 F5773 F5774 F5775 F5776 F5777 F5778 F5780 F5781 F5800 F5801 F5802...
  • Page 692 f5000.fm Nur für den internen Gebrauch F5000 XCNL PROM ERROR Type: Service-specific (Format 1E/22) Short text: PROM error Cause: Format 1E: PROM error. Cross channel has detected an internal error, but has booted and has reported this error / if error is repeated, replace board CCH. Format 22: Error was reported by the routine test organization.
  • Page 693 f5001.fm Nur für den internen Gebrauch F5001 XCNL RAM ERROR Type: Service-specific (Format 1E/22) Short text: RAM error Cause: Format 1E: RAM error in cross channel (CCH). CCH has detected an internal error, but has booted and has reported this error / if error is repeated, replace board CCH. Format 22: Error was reported by the routine test organization.
  • Page 694 f5002.fm Nur für den internen Gebrauch F5002 XCNL TIMER ERROR Type: Service-specific (Format 1E/22) Short text: Timer error Cause: Format 1E: Timeout in cross channel (CCH). Cross channel has detected an internal error, but has booted and has reported this error / if error is repeated, replace board CCH. Format 22: Error was reported by the routine test organization.
  • Page 695 f5003.fm Nur für den internen Gebrauch F5003 XCNL FW ERROR Type: Service-specific (several formats apply) Short text: Firmware error Cause: Firmware error in cross channel (CCH). Formats 1E and 22 are relevant for this message. For the sake of differentiation, byte 1 contains HEX value ’EE in format 22. Format 1E: cross channel has detected an internal error, but has booted and has reported this error.
  • Page 696 f5004.fm Nur für den internen Gebrauch F5004 XCNL Type: Service-specific (Format 18/22) Short text: Cross channel defective Cause: Format 18: Cross channel (CCH) defective / replace board CCH. Format 22: Error was reported by the routine test organization. CCH has not answered the status query. Action: Replace CCH board.
  • Page 697 f5019.fm Nur für den internen Gebrauch F5019 XCNL BACK ON-LINE Type: Diagnosis-specific (Format 00) Short text: Cross channel reports back Cause: Cross channel board reports back again. Action: If error occurs repeatedly, save the error message data and contact your Next level of support.
  • Page 698 f5020.fm Nur für den internen Gebrauch F5020 XCNL XCNL OR IEC DOWN Type: Diagnosis-specific (Format 22) Short text: No response from CCH board Cause: No response from remote (partner) cross channel board. Cross channel board or IEC bus defective. Action: Replace CCH board.
  • Page 699 f5021.fm Nur für den internen Gebrauch F5021 XCNL EC DOWN Type: Diagnosis-specific (Format 18/22) Short text: IEC bus defective Cause: Connection setup possible, but traffic not correct, IEC bus possibly defective. Action: Check the hardware (e.g. cables and shelves). If this does not work, save the error message data and contact your Next level of support.
  • Page 700 f5030.fm Nur für den internen Gebrauch F5030 PROM ERROR Type: Service-specific (several formats apply) Short text: PROM error Cause: PROM error. DCL detects an internal error and reports it either in its own error message or in a status acknowledgment to error analysis. Format 1E and format 22 may be relevant for this message. If the first two HEX items contain ’01EE, this message is a status acknowledgment.
  • Page 701 f5031.fm Nur für den internen Gebrauch F5031 RAM ERROR Type: Service-specific (several formats apply) Short text: RAM error Cause: RAM error. DCL detects an internal error and reports it either in its own error message or in a status acknowledgment to error analysis. If the error is repeated, replace the DCL board. •...
  • Page 702 f5032.fm Nur für den internen Gebrauch F5032 TIMER ERROR Type: Service-specific (several formats apply) Short text: Timer error Cause: Timeout. DCL detects an internal error and reports it either in its own error message or in a status acknowledgment to error analysis. If the error is repeated, replace the DCL. •...
  • Page 703 f5033.fm Nur für den internen Gebrauch F5033 FW ERROR Type: Service-specific (several formats apply) Short text: Firmware error Cause: DCL detects an internal error and reports it either in its own error message or in a status acknowledgment to error analysis. If the error is repeated, replace DCL. •...
  • Page 704 f5034.fm Nur für den internen Gebrauch F5034 NO POLLING Type: Service-specific (Format 18) Short text: DCL is not polling Cause: DCL does not poll the peripherals. This may be because there are not enough free containers (<5) for transporting messages. This message is output after a soft DCL restart. Action: If the error is repeated, start test with TSU AMO.
  • Page 705 f5035.fm Nur für den internen Gebrauch F5035 POLLING AGAIN Type: Service-specific (Format 18) Short text: DCL is polling again Cause: DCL is polling the peripherals again. Action: Positive acknowledgment without action. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 706 f5036.fm Nur für den internen Gebrauch F5036 MSG NOT PLAUS Type: Diagnosis-specific (Format 18) Short text: Implausible message (SW error) Cause: The DCL has received a message it cannot interpret from the peripherals or group processor. This message is packed in an array of 50 bytes and forwarded transparently to DEP-S. Action: The sender and, hence, the cause can be ascertained from the implausible message.
  • Page 707 f5037.fm Nur für den internen Gebrauch F5037 DATA OVERFLOW Type: Diagnosis-specific (Format 18) Short text: Data overflow in DCL Cause: Data overflow in the DCL, i.e. the DCL does not acknowledge the initialization message. Message after a soft DCL restart. Action: Save error message data and contact your Next level of...
  • Page 708 f5038.fm Nur für den internen Gebrauch F5038 DMA ERROR Type: Diagnosis-specific (Format 18) Short text: DMA controller of DCL defective Cause: DCL’s DMA (Direct Memory Access) controller is defective. Message after a soft DCL restart. If the error is repeated, look for the cause in the DCL. Replace DCL board if necessary. Action: If the error is repeated, start test with TSU AMO.
  • Page 709 f5039.fm Nur für den internen Gebrauch F5039 Type: Service-specific (Format 18/22) Short text: DCL board defective Cause: • Format 18: DCL defective. Message after a soft DCL restart. If the error is repeated, look for the cause in the DCL. Replace DCL board if necessary. This error message can also be output together with F5100 and possibly F5042, and then indicates a clock...
  • Page 710 f5041.fm Nur für den internen Gebrauch F5041 PBC DEF Type: Service-specific (Format 1F) Short text: DCL soft restart Cause: Message indicating defective PBCs of the DCL. Action: If the error is repeated, start test with TSU AMO. If test completes with negative results, replace DCL.
  • Page 711 f5042.fm Nur für den internen Gebrauch F5042 HDLC DEFECT Type: Service-specific (Format 22) Short text: HDLC link defective Cause: This LTUC/DCL error is reported by the error analysis system if a number of boards on the same shelf report out-of-service within a short period of time. This error is also reported (together with F5100 and F5039) if the clock generator fails or if, as a result of an...
  • Page 712 f5043.fm Nur für den internen Gebrauch F5043 DCL RELOAD REQUEST Type: Service-specific (Format 18) Short text: Error in DCL loadware Cause: DCL reloaded due to an error in the DCL loadware. Action: The DCL triggered an interrupt that resulted in a hard restart with a reload of the DCL loadware via the interrupt handler (INTH), fault analysis (FA) and SYSLOAD.
  • Page 713 f5044.fm Nur für den internen Gebrauch F5044 HDLC LAYER1 NPR Type: Service-specific (Format 22) Short text: HDLC link interrupt Cause: After a restart CC it was determined that at least one HDLC path to a configured LTU has been interrupted. This results in a ’HW Partially Defective’ in FA (active CC changeover to standby CC, or restart in the standby half).
  • Page 714 f5045.fm Nur für den internen Gebrauch F5045 HDLC LAYER1 LEFT Type: Service-specific (Format 22) Short text: HDLC link lost Cause: The DCL in the standby CC signals a lost HDLC connection to an LTU (cable interruption). Action: See also F5042, F5044, and F5046. Check hardware (shelf, LTUC and DCL boards). A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 715 f5046.fm Nur für den internen Gebrauch F5046 NEW HDLC LAYER1 Type: Service-specific (Format 22) Short text: HDLC link restored Cause: The DCL in the standby CC signals a restored HDLC connection to an LTU. Action: See also F5042, F5044, and F5045. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 716 f5047.fm Nur für den internen Gebrauch F5047 SPOR ERROR Type: Service-specific (Format 22) Short text: Sporadic error in QDCL Cause: A status check of the QDCL showed a sporadic error (QDCL background test). Action: The type of error is shown in the status byte. Save error message data and contact your Next level of support.
  • Page 717 f5050.fm Nur für den internen Gebrauch F5050 PROM ERROR Type: Service-specific (Format 22) Short text: PROM error Cause: Error reported by the RTO, or error message is output in conjunction with F5053 additional information. Action: If error F5050 is not output in conjunction with error F5053 (within 2 seconds), the message indicates that the RTO has detected a defective MBU.
  • Page 718 f5051.fm Nur für den internen Gebrauch F5051 RAM ERROR Type: Service-specific (Format 22) Short text: RAM error Cause: Error reported by the RTO or MBU firmware. Action: Replace MBU. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 719 f5052.fm Nur für den internen Gebrauch F5052 TIMER ERROR Type: Service-specific (Format 22) Short text: Timer error Cause: Error reported by the RTO or MBU firmware. Action: If error F5052 does not occur in conjunction with F5053 (# 2 seconds), the message indicates that the RTO has detected a defective MBU.
  • Page 720 f5053.fm Nur für den internen Gebrauch F5053 FW ERROR Type: Service-specific (Format 1E/22) Short text: Firmware error in MBU Cause: See also F5050 and F5052. MBU has detected an internal error, but was able to complete booting and then report the error. Action: If error is repeated, check firmware status against firmware list and upgrade FW if necessary.
  • Page 721 f5054.fm Nur für den internen Gebrauch F5054 HW ERROR Type: Service-specific (Format 22) Short text: MBU hardware error Cause: Error reported by the RTO or MBU firmware. Action: Check firmware status against firmware list and upgrade FW if necessary. If this does not work, replace MBU board.
  • Page 722 f5055.fm Nur für den internen Gebrauch F5055 MBU OR HDLC DOWN Type: Service-specific (Format 22) Short text: MBU or HDLC link defective Cause: Message buffer unit (MBU) or HDLC links defective. Message can also occur in conjunction with an LTG block. Action: Check MBU, message distributor (MD) or cabling, replace if necessary.
  • Page 723 f5056.fm Nur für den internen Gebrauch F5056 IOCC DOWN Type: Service-specific (Format 22) Short text: IOCC not responding Cause: IOCC no longer responding to a request. Either the central switching network (CSN) is defective or deactivated, or the HDLC highway to the CSN is defective. Action: Check CSN and cabling, replace if necessary.
  • Page 724 f5057.fm Nur für den internen Gebrauch F5057 IOCG DOWN Type: Service-specific (Format 22) Short text: IOCG not responding Cause: IOCG no longer responding to a request. Either the LTG is deactivated, or the HDLC highway to the IOCG is defective, or the IOCG itself is defective. Action: Check LTG/IOCG and cabling, replace if necessary.
  • Page 725 f5058.fm Nur für den internen Gebrauch F5058 IOCC BACK ON-LINE Type: Service-specific (Format 22) Short text: IOCC respüonding again Cause: IOCC answers again. Positive acknowledgment of error message F5056. Action: Positive acknowledgment without action. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 726 f5059.fm Nur für den internen Gebrauch F5059 IOCG BACK ON-LINE Type: Service-specific (Format 22) Short text: IOCG responding again Cause: IOCG answers again. Positive acknowledgment of error message F5057. Action: Positive acknowledgment without action. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 727 f5060.fm Nur für den internen Gebrauch F5060 IOCC MTS OR CR DEF Type: Service-specific (Format 18) Short text: Failure of all MTS boards or CR on IOCC Cause: Failure of all MTS boards or clock repeater (CR) on the IOCC board Action: Check appropriate board, replace if necessary.
  • Page 728 f5061.fm Nur für den internen Gebrauch F5061 IOCC MTS DEF Type: Service-specific (Format 18) Short text: Timeslot or MTS defective Cause: Timeslot or MTS board has failed Action: Check MTS board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 729 f5062.fm Nur für den internen Gebrauch F5062 IOCC WATCHDOG TIMEOUT Type: Diagnosis-specific (Format 29) Short text: Watchdog timeout Cause: Watchdog timeout on the IOCC board. Action: Error analysis (FA) keeps statistics to this effect. Save error message data and contact your Next level of support.
  • Page 730 f5063.fm Nur für den internen Gebrauch F5063 IOCC SUM POWER FAIL Type: Service-specific (Format 29) Short text: Feed power failure Cause: Summation counter (for voltage fluctuations) signals failure of a feed voltage in the system (inverter or charging rectifier output). Action: Check power supply and appropriate voltages.
  • Page 731 f5064.fm Nur für den internen Gebrauch F5064 IOCC RESOURCES Type: Service-specific (Format 29) Short text: IOCC resource shortage Cause: IOCC short of resources. Action: Save error message data and contact your Next level of support. Note related error messages. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 732 f5065.fm Nur für den internen Gebrauch F5065 IOCC NEW ACTIVE Type: Service-specific (Format 29) Short text: IOCC active Cause: IOCC has assumed the activity. Action: If error occurs repeatedly, save the error message data and contact your Next level of support.
  • Page 733 f5066.fm Nur für den internen Gebrauch F5066 IOCC BOTH CSN ACT Type: Service-specific (Format 19) Short text: IOCC partner active Cause: An IOCC signals that both partners are active. Action: If error occurs repeatedly, save the error message data and contact your Next level of support A31003-H3100-S104-14-7620, 11/2015...
  • Page 734 f5067.fm Nur für den internen Gebrauch F5067 IOCC HDLC CC SBY DEF Type: Service-specific (Format 29) Short text: HDLC link to standby CC interrupted Cause: HDLC connection to standby common control (standby CC) is interrupted. Action: Check HDLC connection. Also check rest of hardware (shelf and cables). A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 735 f5068.fm Nur für den internen Gebrauch F5068 IOCC Type: Service-specific (several formats apply) Short text: CCG reference clock failed Cause: • Format 18: failure of clock reference signal from CCG. • Format 22: Error in status word query. The error is reported by the routine test organization. For the sake of differentiation, the HEX data contains H’EE in byte 1, then a series of items describing the disabled and defective CSN elements, and the CSN status.
  • Page 736 f5068.fm Nur für den internen Gebrauch Byte 14 Status of MTS64 board 5 (SLOT 90) Byte 15 Status of MTS64 board 6 (SLOT 83) Byte 16 Status of MTS64 board 7 (SLOT 76) A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 737 f5069.fm Nur für den internen Gebrauch F5069 IOCC IOCG DEF Type: Service-specific (Format 18) Short text: IOCG defective Cause: IOCG board is defective or cannot supply a clock. Action: Replace IOCG board. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 738 f5070.fm Nur für den internen Gebrauch F5070 IOCC CCG DEF Type: Service-specific (several formats apply) Short text: CCG defective Cause: • Format 18: clock repeater (CR) of the central clock generator (CCG) is defective. • Format 22: byte 1 contains H’EE for differentiation. Status of IOCC is bad. Action: Action depends on the evaluation of the HEX data.
  • Page 739 f5071.fm Nur für den internen Gebrauch F5071 IOCC CCG FAIL Type: Service-specific Short text: Error on CCG Cause: Central clock generator (CCG) has identified an error in the reference input. Action: Check CCG board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 740 f5072.fm Nur für den internen Gebrauch F5072 IOCC CCG NO CLOCK Type: Service-specific (Format 18) Short text: No clock signal from CCG Cause: Central clock generator (CCG) can no longer send clock signal. Action: Check CCG board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 741 f5073.fm Nur für den internen Gebrauch F5073 IOCC CCG ON-LINE Type: Service-specific (Format 29) Short text: CCG okay again Cause: Defective central clock generator (CCG) is okay again. Action: Positive acknowledgment without action. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 742 f5074.fm Nur für den internen Gebrauch F5074 IOCC CCG REF LOSS Type: Service-specific (Format 29) Short text: Loss of external reference clock Cause: Central clock generator (CCG) has lost external clock reference signal. Action: Check external clock source. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 743 f5075.fm Nur für den internen Gebrauch F5075 IOCC CCG REF OK Type: Service-specific (Format 29) Short text: Synchronized to external reference clock Cause: Central clock generator (CCG) has been synchronized with an external clock reference signal. Action: If error occurs repeatedly, save the error message data and contact your Next level of support.
  • Page 744 f5076.fm Nur für den internen Gebrauch F5076 IOCC IMPLAUSIBLE MSG Type: Service-specific (Format 22) Short text: Implausible message to IOCC Cause: IOCC has received an implausible message. The container with the implausible message is reflected in the HEX data (F1-F2-F3). Action: Save error message data and contact your Next level of...
  • Page 745 f5100.fm Nur für den internen Gebrauch F5100 CLOCK NOT READY Type: Service-specific (Format 1A) Short text: PCG not in order Cause: Error in internal communication with clock generator. System reaction: system automatically carries out a hard restart. Action: Replace clock generator board if error is signaled again after restart. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 746 f5101.fm Nur für den internen Gebrauch F5101 CLOCK DEFECT Type: Service-specific (Format 1A/22) Short text: Clock signal detection error Cause: Format 1A: This message is output on duplex systems., if • active clock generator has detected a clock frequency, but the standby clock generator has not (false clock) •...
  • Page 747 f5103.fm Nur für den internen Gebrauch F5103 CLOCK PROM ERROR Type: Service-specific (Format 1A) Short text: Clock generator PROM error Cause: Clock generator has detected a PROM error. System reaction: This is treated as a system hardware error. Duplex systems: system carries out a hard restart, if standby CC half has better HW status.
  • Page 748 f5104.fm Nur für den internen Gebrauch F5104 CLOCK RAM ERROR Type: Service-specific (Format 1A) Short text: Clock generator RAM error Cause: Clock generator has detected a RAM error. System reaction: this is treated as a system hardware error. Duplex systems: system carries out a hard restart, if standby CC half has better HW status.
  • Page 749 f5105.fm Nur für den internen Gebrauch F5105 CLOCK PROC ERROR Type: Service-specific (Format 1A) Short text: Clock generator processor error Cause: Clock generator has detected a processor error. System reaction: this is treated as a system hardware error. Duplex systems: system carries out a hard restart, if standby CC half has better HW status.
  • Page 750 f5106.fm Nur für den internen Gebrauch F5106 CLOCK MASTER/SLAVE ERROR Type: Service-specific (Format 1A) Short text: Master/slave error Cause: Clock generator has detected a master/slave switchover error. System reaction: no automatic response. Action: Initiate system restart to test whether error can be eliminated. If the error is signaled again after the restart, replace the clock generator A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 751 f5107.fm Nur für den internen Gebrauch F5107 CLOCK CKA ERROR Type: Service-specific (Format 1A) Short text: System clock error Cause: Clock generator has detected a system clock failure. System reaction: system automatically carries out a hard restart. Action: Replace clock generator board if error is signaled again after restart. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 752 f5112.fm Nur für den internen Gebrauch F5112 CLOCK CLOCK NOT RECOGNIZED Type: Service-specific (Format 22) Short text: Reference clock missing Cause: Clock generator cannot identify external reference clock despite valid source. System reaction: error counter of clock source is incremented, and search for new circuit is carried out. Action: If the error occurs frequently on a particular circuit, check the clock source.
  • Page 753 f5130.fm Nur für den internen Gebrauch F5130 SM/UNIT ON-LINE Type: Service-specific (Format 29) Short text: Server restart end Cause: End-of-restart of a service module. Either the TCS or the VMS (not the ADS) has executed an independent restart. Action: If error occurs repeatedly, save the error message data and contact your Next level of support.
  • Page 754 f5133.fm Nur für den internen Gebrauch F5133 SM/UNIT CDC DISABLE Type: Service-specific (Format 29) Short text: Server disabled via AMO. Cause: Server disabled via AMO. Action: Determine why server was disabled and enable server again via AMO. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 755 f5134.fm Nur für den internen Gebrauch F5134 SM/UNIT RESTART BEG Type: Service-specific (Format 29) Short text: Server restart Cause: Beginning of independent restart of either the TCS or the VMS (not the ADS). Action: Save error message data and contact your Next level of support.
  • Page 756 f5135.fm Nur für den internen Gebrauch F5135 SM/UNIT RESTART DUE TO SERVER Type: Diagnosis-specific (Format 22) Short text: SWU restart Cause: SWU has carried out a restart at the request of a server. Action: Save error message data and contact your Next level of support.
  • Page 757 f5136.fm Nur für den internen Gebrauch F5136 SM/UNIT STATISTIC Type: Diagnosis-specific (Format 22) Short text: Counter overflow Cause: Counter overflow for server restarts. Action: Determine the cause of the frequent restarts. Save error message data and contact your Next level of support.
  • Page 758 f5140.fm Nur für den internen Gebrauch F5140 POW SUPL POWER SUPPLY DEF Type: Service-specific (Format 00) Short text: Inverter failure Cause: Inverter failure on the LTU shelf, CC shelf or in the server. An LTU failure, CC partner failure or server failure occurs simultaneously. Action: Check power supply.
  • Page 759 f5141.fm Nur für den internen Gebrauch F5141 POW SUPL POWER SUPPLY OK Type: Service-specific (Format 00) Short text: Inverter okay Cause: Inverter in order again. Action: Positive acknowledgment of F5140. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 760 f5160.fm Nur für den internen Gebrauch F5160 IOCG PROM ERROR Type: Service-specific (Format 1E/22) Short text: PROM error. Cause: Error reported by the RTO or board FW. This message is output after booting and contains the errors that led to the IOCG restart. The error code and the error address of the operating system on the IOCG boards are output in the HEX data.
  • Page 761 f5161.fm Nur für den internen Gebrauch F5161 IOCG RAM ERROR Type: Service-specific (Format 1E/22) Short text: RAM error Cause: Error reported by the RTO or board FW. This message is output after booting and contains the errors that led to the IOCG restart. The error code and the error address of the operating system on the IOCG boards are output in the HEX data.
  • Page 762 f5162.fm Nur für den internen Gebrauch F5162 IOCG TIMER ERROR Type: Service-specific (Format 1E/22) Short text: Timer error Cause: Error reported by the RTO or board FW. This message is output after booting and contains the errors that led to the IOCG restart. The error code and the error address of the operating system on the IOCG boards are output in the HEX data.
  • Page 763 f5163.fm Nur für den internen Gebrauch F5163 IOCG SW ERROR Type: Service-specific (Format 1E/22) Short text: Software error Cause: Error reported by the RTO or board FW. This message is output after booting and indicates the error that led to the IOCG restart. Action: If error is repeated, check firmware status against firmware list and upgrade FW if necessary.
  • Page 764 f5164.fm Nur für den internen Gebrauch F5164 IOCG HW ERROR Type: Service-specific (Format 1E/22) Short text: Hardware error Cause: Error reported by the RTO or board FW (clock problems). This message is output after booting and contains the error that has led to the IOCG restart. The error code and the error address of the operating system on the IOCG boards are output in the HEX data.
  • Page 765 f5165.fm Nur für den internen Gebrauch F5165 IOCG MBU OR HDLC DOWN Type: Service-specific (Format 22) Short text: MBU or HDLC defective Cause: Message buffer unit (MBU) or HDLC path defective. This message can also indicate that the SWU is undergoing a restart or is deactivated. Action: If all IOCG and IOCC boards report this error at the same time, check the MBU board and replace if necessary.
  • Page 766 f5166.fm Nur für den internen Gebrauch F5166 IOCG Type: Service-specific (Format 22) Short text: Status query not acknowledged Cause: IOCG can no longer be initialized. Error reported by the routine test organization. The IOCG has not acknowledged the status query. Action: Check the IOCG board and replace if necessary.
  • Page 767 f5167.fm Nur für den internen Gebrauch F5167 IOCG MBU ON-LINE Type: Service-specific (Format 22) Short text: IOCG on-line again Cause: IOCG has contact again with the common control (CC). Action: Positive acknowledgment without action. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 768 f5168.fm Nur für den internen Gebrauch F5168 IOCG CLOCK REPEATER DEF Type: Service-specific (Format 18) Short text: Clock repeater defective Cause: IOCG’s clock repeater (CR) defective. Action: Check IOCG board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 769 f5169.fm Nur für den internen Gebrauch F5169 IOCG PARTNER DOWN Type: Service-specific (Format 18) Short text: IOCG defective Cause: IOCG power failure or defect detected in the partner half of the LTG. Action: Check power supply and replace IOCG if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 770 f5170.fm Nur für den internen Gebrauch F5170 IOCG LOGIC ACTIVE Type: Service-specific (Format 22) Short text: IOCG output active Cause: Status of active logic changed. The remote partner of the reporting IOCG has driven its output inactive, LTG half of reporting IOCG is active. Action: Check reason for status change in partner half.
  • Page 771 f5171.fm Nur für den internen Gebrauch F5171 IOCG LOGIC NOT ACTIVE Type: Service-specific (Format 22) Short text: IOCG output inactive Cause: Status of active logic changed. The remote partner of the reporting IOCG has driven its output active. Action: No action necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 772 f5173.fm Nur für den internen Gebrauch F5173 IOCG END OF FAIL Type: Service-specific (Format 22) Short text: IOCG clock repeater okay again Cause: Errors reported by the clock repeater no longer exist. Action: Byte 0 of the HEX data indicates the IOCG state. Interpretation of auxiliary data: The IOCG state is indicated by whichever bit is set (1) Byte 0...
  • Page 773 f5180.fm Nur für den internen Gebrauch F5180 Type: Diagnosis-specific (Format 21/22) Short text: Highway failure Cause: The RTO reports a highway failure, after several tests (RTO test only if activated via AMO FUNSU / LTUAHWYA, CSNHWYA). Format 21 is output with action = OUT_SERV. This is followed by format 22 with the RTO trace message. The RTO trace message is not further explained here.
  • Page 774 f5180.fm Nur für den internen Gebrauch If action is OUT_SERV (Format 21): Byte 0 LTG (0-31) Byte 1 LTU (1-xx) Byte 2 HWY (1-xx) Byte 3 TSL (0-xx) A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 775 f5181.fm Nur für den internen Gebrauch F5181 TSL DEF Type: Diagnosis-specific (Format 21/22) Short text: Timeslot failure Cause: The RTO reports a timeslot failure (RTO test only if activated via AMO FUNSU / LTUAHWYA, CSNHWYA). Format 21 is output with action = OUT_SERV. This is followed by format 22 with the RTO trace message. 1.
  • Page 776 f5182.fm Nur für den internen Gebrauch F5182 TSL SPORAD Type: Diagnosis-specific (Format 21/22) Short text: Sporadic timeslot failure Cause: The RTO reports a sporadic timeslot failure (RTO test only if activated via AMO FUNSU / LTUAHWYA, CSNHWYA). Format 21 is output with action = OUT_SERV. This is followed by format 22 with the RTO trace message. Action: See F5180.
  • Page 777 f5183.fm Nur für den internen Gebrauch F5183 TESTTR TIMEOUT Type: Diagnosis-specific (Format 21) Short text: Timeout on highway test Cause: The RTO reports a highway test timeout (RTO test only if activated via AMO FUNSU / LTUAHWYA, CSNHWYA). Action: If hard restart is unsuccessful, replace SIU board. If this does not work, replace connecting cable between MTS and LTUC or replace LTUC board.
  • Page 778 f5200.fm Nur für den internen Gebrauch F5200 BOARD DEFECTIVE Type: Service-specific (Format 21) Short text: MTS board defective Cause: MTS defective. Event signal came from the MTS handler. Action: Replace MTS board. Interpretation of auxiliary data: Byte 0 LTG (0-31) Byte 1 LTU (00-07) Byte 2...
  • Page 779 f5201.fm Nur für den internen Gebrauch F5201 HWYS DEFECT Type: Service-relevant (Format 22) Short text: LTU highways defective Cause: Defective highways were detected by RTO test in one or more LTUs on an MTS/SICOE module. State set to DEF. Total defects of relevant LTUC unavailable. Action: Replace highway cable on relevant LTUC.
  • Page 780 f5220.fm Nur für den internen Gebrauch F5220 Type: Service-relevant (Format 20/22/43) Short text: SIU defect Cause: Format 20: SIU boards defective. All terminals are powered (but no dial tone). Format 22: SIU micro processor error reported by the RTO. Format 43: SIU part on NCUI board defective. System reaction: Format 43: The AP is locked.
  • Page 781 f5222.fm Nur für den internen Gebrauch F5222 SPORAD Type: Service-specific (Format 20/22) Short text: Sporadic error Cause: Format 20: Sporadic error. Only for statistics. Format 22: Sporadic SIU microprocessor error reported by the routine test organization. Action: Format 22: Check board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 782 f5225.fm Nur für den internen Gebrauch F5225 PER DEF Type: Service-specific (Format 20) Short text: SIU peripherals defective Cause: SIU peripherals defective. Action: Replace board. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 783 f5227.fm Nur für den internen Gebrauch F5227 INIT ERROR Type: Service-specific (Format 20) Short text: Initialization error Cause: SIU board initialization error. Action: Evaluate auxiliary data. Interpretation of auxiliary data: Byte 2 Initialization error (DB_M_QC_ERROR_SET) Board in service (can occur if byte 3 = H´0B) Wrong board or board incorrectly configured (see F5242) Board not present Board defective...
  • Page 784 f5227.fm Nur für den internen Gebrauch FTP LOGON PROBLEM A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 785 f5228.fm Nur für den internen Gebrauch F5228 CON RESP Type: Service-specific (Format 20) Short text: Transmission error Cause: Transmission error on the HDLC link. Action: Check the appropriate hardware, depending on the system type (shelf and HDLC link). A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 786 f5229.fm Nur für den internen Gebrauch F5229 TEST DEF Type: Service-specific (Format 20/22) Short text: Test transmitter/receiver defective Cause: • Format 20: Test transmitter/receiver defective. • Format 22: Reported by the RTO. Action: Format 20: replace board A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 787 f5230.fm Nur für den internen Gebrauch F5230 BAD DIALTONE Type: Service-specific (Format 20/22) Short text: Bad external dial tone Cause: • Format 20: Bad external dial tone. • Format 22: Reported by the RTO. Action: Format 20: replace board A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 788 f5232.fm Nur für den internen Gebrauch F5232 BAD PULSED TONE Type: Service-specific (Format 20/22) Short text: Bad cadenced tone (internal dial tone) Cause: • Format 20: Bad cadenced tone (internal dial tone) • Format 22: Reported by the RTO. Action: Format 20: replace board A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 789 f5233.fm Nur für den internen Gebrauch F5233 DTR DEF Type: Service-specific (Format 20/22) Short text: Dial tone receiver defective Cause: • Format 20: Dial tone receiver of SIU defective. No exchange dial tone. • Format 22: Reported by the RTO. Action: Format 20: replace board A31003-H3100-S104-14-7620, 11/2015...
  • Page 790 f5234.fm Nur für den internen Gebrauch F5234 OUT (ATTENDANCE LIST) Type: Service-specific (Format 20) Short text: Board not plugged Cause: Board pulled out, i.e. the board is no longer on the DCL’s attendance list. Action: Replug board. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 791 f5235.fm Nur für den internen Gebrauch F5235 IN (ATTENDANCE LIST) Type: Service-specific (Format 20) Short text: Board replugged Cause: Board back on DCL attendance list. Action: Positive acknowledgment without action. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 792 f5236.fm Nur für den internen Gebrauch F5236 PER EVT ERROR Type: Service-specific (Format 20) Short text: Implausible message from SIU Cause: Peripheral processing has received an implausible message from the SIU firmware. Action: Check SIU board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 793 f5237.fm Nur für den internen Gebrauch F5237 MP EVT ERROR Type: Service-specific (Format 20) Short text: SIU cannot interpret message Cause: SIU firmware cannot interpret an incoming message. Action: Check SIU board and replace if necessary. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 794 f5238.fm Nur für den internen Gebrauch F5238 FUNCT DEF (FUNCT. DEF.) Type: Service-specific (Format 20/22) Short text: SIU defective Cause: • Format 20: SIU function bad. • Format 22: Reported by the routine test organization. Action: Format 20: replace board. Interpretation of auxiliary data: Additional HEX data is signaled with the following interpretation for the 80CMX-DSC: Byte 0-4...
  • Page 795 f5240.fm Nur für den internen Gebrauch F5240 CS DEF Type: Service-specific (Format 22) Short text: Code transmitter defective Cause: Code transmitter of SIU board defective. No dialing possible for DTMF telephones. Action: Replace SIU board. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 796 f5241.fm Nur für den internen Gebrauch F5241 CR DEF Type: Service-specific (Format 22) Short text: Code receiver defective Cause: Code transmitter of SIU board defective. No dialing possible for DTMF telephones. Action: Replace SIU board. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 797 f5242.fm Nur für den internen Gebrauch F5242 CONFIG ERROR Type: Service-relevant (Format 20) Short text: SIU incorrectly configured Cause: The central SIU board was incorrectly configured or an incorrect board type was connected. The boot operation was not completed. Action: A hard restart is performed if the error is not rectified within a specific period of time (20 min.).
  • Page 798 f5242.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 799 f5243.fm Nur für den internen Gebrauch F5243 CONFIG OK Type: Service-specific (Format 20) Short text: Board configuration corrected Cause: The configuration error on the central SIU board was corrected. Startup was completed. Action: Positive acknowledgment without action. Interpretation of auxiliary data: Byte 2 Initialization error (DB_M_QC_ERROR_SET) Wrong board or board incorrectly configured (F5242)
  • Page 800 f5250.fm Nur für den internen Gebrauch F5250 COP READY Type: Diagnosis-specific (Format H’42) Short text: DSC80: message Co-processor (CoP) ready Cause: Information on the last restart of the DSC80 co-processor is displayed if a co-processor error (see F5251, F5252, F5255, F5257) is followed by a restart. This message is always output in conjunction with the message relating to the cause of the error and is only required for interpretation by loadware developers.
  • Page 801 f5251.fm Nur für den internen Gebrauch F5251 COP HARD ERROR Type: Diagnosis-specific (Format H’42) Short text: DSC80: critical error in co-processor (CoP) Cause: A critical error has occurred on the co-processor (P68340) of the DSC80. This error always results in a hard restart, since the co-processor cannot run. If the same error recurs during the subsequent restart, the restart is delayed for one hour.
  • Page 802 f5252.fm Nur für den internen Gebrauch F5252 COP EXCEPTION Type: Diagnosis-specific (Format H’42) Short text: DSC80: Co-processor (CoP) program conflict Cause: A program conflict (exception situation) has occurred on the co-processor (P68340) of the DSC80. This error is treated statistically. In the event of a statistics overflow, a soft restart is initiated. Other possible messages are available in the HW-DPR contents or a COP ready message (F5250) for interpretation by the loadware developers.
  • Page 803 f5253.fm Nur für den internen Gebrauch F5253 MP ERROR Type: Diagnosis-specific (Format H’42) Short text: DSC80: error in process of the micro-processor (MP) Cause: The MP has come across an internal error, e.g. DPR invalid, OS Call Fault or an earlier QDLC-CMP exception.
  • Page 804 f5254.fm Nur für den internen Gebrauch F5254 MP PGL ERROR Type: Diagnosis-specific (Format H’42) Short text: DSC80: micro-processor program loader error (PGL) Cause: The micro-processor (MP) has come across a program loader error. Up to two (logically associated) messages may be sent. The error causes a hard restart.
  • Page 805 f5255.fm Nur für den internen Gebrauch F5255 MP COP FATAL ERROR Type: Diagnosis-specific (Format 42) Short text: DSC80: micro-processor (MP) detects a fatal co-processor error (CoP). Cause: The MP has come across a time overflow error in the co-processor of the DSC80. This error indicates that the co-processor has previously responded to the MP.
  • Page 806 f5256.fm Nur für den internen Gebrauch F5256 MP COP UNEXP RESULT Type: Diagnosis-specific (Format H’42) Short text: DSC80: micro-processor (MP) receives an unexpected result code from the co- processor (CoP). Cause: An unexpected result code was returned by the co-processor (LP). Up to two (logically associated) messages may be sent.
  • Page 807 f5257.fm Nur für den internen Gebrauch F5257 MP COP STARTUP ERROR Type: Diagnosis-specific (Format H’42) Short text: DSC80: co-processor (CoP) time overflow during startup. Cause: The micro-processor (MP) returns a co-processor error (time overflow) before the co- processor reaches normal operational status. Up to two (logically associated) messages may be sent. System reaction: The error causes a hard restart and the co-processor loadware may be reloaded under certain conditions.
  • Page 808 f5258.fm Nur für den internen Gebrauch F5258 HSR ADVISORY Type: Service-relevant (format 42) Short text: Advisory message from the HiPath Signaling Router (HSR) SW complex Cause: The HiPath Signaling Router (HSR) outputs an advisory message when a problem with the IP signaling connection to an AP is detected. System reaction: The HSR requests one of two possible reactions: •...
  • Page 809 f5258.fm Nur für den internen Gebrauch just occurring sporadically, but globally. This is determined by statistical analysis in the HSR. 9 errors only are reported during a specific unit of time, the 10th error then leads to a repair attempt via a hard restart, with the aim of repairing the cryptlib again.
  • Page 810 f5259.fm Nur für den internen Gebrauch F5259 AP CONNECTION NEW Type: Diagnosis-relevant (Format 40) Short text: Connection to Access Point restored. Cause: After the loss of connection or a restart/reload, an attempt was made to set up a connection to the access point again. System reaction: None.
  • Page 811 f5260.fm Nur für den internen Gebrauch F5260 CONF CONTR RESP ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5260 = F5340 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 812 f5262.fm Nur für den internen Gebrauch F5262 CONF DATA OVERFLOW Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5262 = F5342 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 813 f5263.fm Nur für den internen Gebrauch F5263 CONF HDLC ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5263 = F5343 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 814 f5264.fm Nur für den internen Gebrauch F5264 CONF HW ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5264 = F5344 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 815 f5265.fm Nur für den internen Gebrauch F5265 CONF INIT ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5265 = F5345 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 816 f5266.fm Nur für den internen Gebrauch F5266 CONF LOOP DATA ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5266 = F5346 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 817 f5267.fm Nur für den internen Gebrauch F5267 CONF MP EC ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5267 = F5347 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 818 f5268.fm Nur für den internen Gebrauch F5268 CONF MP LW ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5268 = F5348 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 819 f5269.fm Nur für den internen Gebrauch F5269 CONF MSG NOT TRANSMITTABLE Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5269 = F5349 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 820 f5270.fm Nur für den internen Gebrauch F5270 CONF SECONDARY IN ATTEND L Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5270 = F5350 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 821 f5271.fm Nur für den internen Gebrauch F5271 CONF PER ADDR ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5271 = F5351 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 822 f5272.fm Nur für den internen Gebrauch F5272 CONF PER EVT ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5272 = F5352 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 823 f5273.fm Nur für den internen Gebrauch F5273 CONF REGISTER ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5273 = F5353 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 824 f5274.fm Nur für den internen Gebrauch F5274 CONF SECONDARY OUT ATTEND L Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5274 = F5354 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 825 f5275.fm Nur für den internen Gebrauch F5275 CONF SPOR ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5275 = F5355 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 826 f5276.fm Nur für den internen Gebrauch F5276 CONF STATUS WORD ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5276 = F5356 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 827 f5278.fm Nur für den internen Gebrauch F5278 CONF TIME ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5278 = F5358 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 828 f5279.fm Nur für den internen Gebrauch F5279 CONF PIT ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5279 = F5359 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 829 f5291.fm Nur für den internen Gebrauch F5291 CONF STAT OVERFLOW Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5291 = F5371 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 830 f5293.fm Nur für den internen Gebrauch F5293 CONF STOP NEW SEIZURES Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5293 = F5373 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 831 f5294.fm Nur für den internen Gebrauch F5294 CONF START NEW SEIZURES Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5294 = F5374 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 832 f5296.fm Nur für den internen Gebrauch F5296 CONF DFE ERROR Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5296 = F5376 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 833 f5297.fm Nur für den internen Gebrauch F5297 CONF RMS LEFT Note: The description of this error message corresponds to the description of the following error message from the BOARD area: F5297 = F5377 A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 834 f5297.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 835 f5304.fm Nur für den internen Gebrauch F5304 LTUC CONTR RESP Type: Service-specific (Format 22) Short text: Control response error. Cause: Control response error from LTUC board. PP performs a routine PBC control response check. PP received an errored control response byte from the PBC of the LTUC. The PBC may be defective since the FW and the MP are not affected.
  • Page 836 f5305.fm Nur für den internen Gebrauch F5305 LTUC HW ERROR Type: Service relevant (Format 22, Format 43) Short text: Error in the LTUC hardware. Cause: The trigger is recognized by the LTUC firmware. A defective LTU power supply may be the cause of this error.
  • Page 837 f5305.fm Nur für den internen Gebrauch Reason: 10H WRONG CBM PARAMETER Type: Service relevant Short text: Error in the configuration of CBM parameters. Cause: The configuration of CBM parameters does not match the number or type of the available CBM modules on the board (LTUCC, NCUI). After startup of the board, the LW is able to recognize wrong configured CBM parameters.
  • Page 838 f5305.fm Nur für den internen Gebrauch auxiliary data: Diagnosis data filled in by board LW for product specialist. Reason: 13H NO CBM RESOURCES Reason: 14H WRONG CBM CONNECTION DATA Type: Service relevant Short text: No CBM resources available on the board. Cause: A CP switching order arrives at LTUC after the defect of a CBM module has been recognized by LW, but the resources have not been corrected in the SWU database yet.
  • Page 839 f5305.fm Nur für den internen Gebrauch Reason: 15H 19 INCH EXPANSION BOX EXISTS Type: Service relevant. Short text: The expansion box for 19inch NBCS AP does not exist. Cause: This message should never be signaled because it describes the normal working operation.
  • Page 840 f5305.fm Nur für den internen Gebrauch Reason: 17H POWER SUPPLY ERROR Reason: 18H POWER SUPPLY OK Type: Service relevant. Short text: Power supply error/ok Cause: 17H: A power supply module in a peripheral shelf is defective. This error message indicates a problem with the power supply module for a standard LTU shelf (DC or AC signal from a power supply unit) as well as for a 19inch LTU (power supply signal of the base box or the expansion box).fault messages weist ASC on Problem WITH dem Power supply module für one STANDARD LTUboardtype (DC oder AC-Signal einer Stromversorgungseinheit)
  • Page 841 f5305.fm Nur für den internen Gebrauch 19 INCH BASE BOX FAN 2 19 INCH EXPANSION BOX FAN 1 19 INCH EXPANSION BOX FAN 2 Reason: 1BH RESET REASON Type: Service relevant. Short text: LTU control board reset reason (NCUI) Cause: There exist some resets of the LTUC control board which are initiated by the control board itself.
  • Page 842 f5305.fm Nur für den internen Gebrauch auxiliary data: Diagnosis data filled in by board LW for product specialist. Reason: 1DH NO CP PATH RESOURCES IN PERIPHERY Type: Service relevant Short text: No CP path resources in periphery Cause: The loadware of the LTU control board has detect that there were not enough CP resources on the board to establish a requested call.
  • Page 843 f5305.fm Nur für den internen Gebrauch Reason: 1FH RG/WG ACTIVE Reason: 20H RG/WG INACTIVE Type: Service relevant Short text: RG/WG active/inactive Cause: 1FH: The LTU control board loadware has detected the signal of a RG/WG board or modul (In a 19inch shelf only a RG module is possible).
  • Page 844 f5305.fm Nur für den internen Gebrauch Interpretation of auxiliary data: RG/WG device: RG STANDARD BOARD WG STANDARD BOARD Reason: 22H AP SIU ERROR (LW) Reason: 23H AP CG EROR (LW) Reason: 24H AP DCL ERROR (LW) Type: Service relevant Short text: 22H: AP SIU error (detected during normal operation by LW) 23H: AP CG error (detected during normal operation by LW) 24H: AP DCL error (detected during normal operation by LW)
  • Page 845 f5305.fm Nur für den internen Gebrauch 27H: AP V24 interface error (detected during startup by board selftest)Eigentest erkannt) 28H: AP Ethernet interface error (detected during startup by board selftest) The board is added to the ’in service task’. Cause: The loadware or the selftest of the LTU control board (NCUI) in a NBCS AP shelf has detected an error on the V24/Ethernet interface on the board.
  • Page 846 f5306.fm Nur für den internen Gebrauch F5306 LTUC IN (ATTENDANCE LIST) Type: Service-specific (Format 22) Short text: LTUC is back on the attendance list Cause: LTUC is in service once more and is back on the attendance list. Event signal came from DCL firmware.
  • Page 847 f5307.fm Nur für den internen Gebrauch F5307 LTUC INIT ERROR Type: Service relevant (Format 23) Short text: Initialization error Cause: LTUC board initialization error. LTUs that are not put into service are signaled with this message during the LTG boot operation. System reaction: LTUC already set as defective by DC.
  • Page 848 f5308.fm Nur für den internen Gebrauch F5308 LTUC OUT OF ATTENDANCE LIST Type: Service-specific (Format 22) Short text: LTUC is no longer on attendance list Cause: LTUC board has been pulled out, i.e. it is no longer on the attendance list. Alternatively, the LTUC board may be defective or the LTU power supply has failed.
  • Page 849 f5309.fm Nur für den internen Gebrauch F5309 LTUC LOOP DATA ERROR Type: Service-specific (Format 18/22) Short text: RTO: Test loop insertion error Cause: Format 18: Test loop insertion error. Format 22: The RTO error message is entered in the HEX data. Action: Format 18: Replace board.
  • Page 850 f5309.fm Nur für den internen Gebrauch Byte 7-8 LTG-LINE Byte 19 Byte 20 Byte 21 Byte 22 Byte 23 B-Channel Byte 24 Loop Back Byte 25 Highway Byte 26 Timeslot Byte 27 First RTO Event Byte 30 Curr RTO Event Byte 31 User Byte 32...
  • Page 851 f5310.fm Nur für den internen Gebrauch F5310 LTUC MP EC ERROR Type: Diagnosis-specific (Format 22) Short text: Implausible event code received by LTUC Cause: The LTUC firmware has received a message from peripheral processing (PP) with an invalid event code (EC). The event signal came from the LTUC firmware. System reaction: signaling only.
  • Page 852 f5311.fm Nur für den internen Gebrauch F5311 LTUC PER EC ERROR Type: Diagnosis-specific (Format 22) Short text: Implausible event code from LTUC Cause: Peripheral processing (PP) received a message from the peripheral firmware with an implausible event code EC. The event signal came from peripheral processing in the LTUC. System reaction: signaling only.
  • Page 853 f5312.fm Nur für den internen Gebrauch F5312 LTUC REGISTER ERROR Type: Service-specific (Format 18/22) Short text: RTO: peripheral board controller (PBC) error Cause: Format 18: Error in the code check register of the peripheral board controller (PBC). Replace appropriate board. Format 22: The entire error message sent by the RTO is entered in the HEX data.
  • Page 854 f5313.fm Nur für den internen Gebrauch F5313 LTUC SPOR ERROR Type: Service-specific (Format 22) Short text: RTO: Sporadic error Cause: ACTION=NO ACT; sporadic error (advisory). ACTION=OUT SERV; sporadic error in conjunction with disable message generated due to peripheral error counter overflow. The RTO message is entered in the HEX data.
  • Page 855 f5314.fm Nur für den internen Gebrauch F5314 LTUC STATUS WORD ERROR Type: Service-specific (Format 22) Short text: RTO: RAM/PROM error. Cause: The LTUC and, as a result, the shelf are locked away. The entire message sent by the RTO is entered in the HEX data. Action: Replace appropriate board.
  • Page 856 f5315.fm Nur für den internen Gebrauch F5315 LTUC TEST OK Type: Service-specific (Format 22) Short text: RTO: LTUC okay again. Cause: LTUC startup was interrupted by soft restart, startup repeated by CDC. Action: If error occurs repeatedly, save the error message data and contact your Next level of support.
  • Page 857 f5316.fm Nur für den internen Gebrauch F5316 LTUC TIME ERROR Type: Service-specific (Format 18/22) Short text: RTO: Timeout error Cause: Format 18: Timeout error. No response to routine test. System places the shelf out of service. Can sometimes be caused by LTU power failure. Alternatively, an LTUC or SLMB failure may have been caused by adjacent TMBD or TMOM boards.
  • Page 858 f5325.fm Nur für den internen Gebrauch F5325 LTUC RGEN/ACGEN INSERTED Type: Service-specific (Format 18) Short text: Ringing generator or AC generator board plugged Cause: Peripheral ringing/ac power generator board has been plugged in. Event signal came from LTUC firmware. System reaction: the RGEN or WGEN is released.
  • Page 859 f5326.fm Nur für den internen Gebrauch F5326 LTUC RGEN/ACGEN REMOVED Type: Service-specific (Format 18) Short text: RGEN or WGEN (ACGEN) have been unplugged Cause: Peripheral ringing/ac power generator board has been pulled out. Event signal came from LTUC firmware. System reaction: blocks the RGEN or WGEN.
  • Page 860 f5327.fm Nur für den internen Gebrauch F5327 LTUC RGEN SYN OFF) Type: Service-specific (Format 18) Short text: SYN1 clock of RGEN missing Cause: No LTUC SYN1 clock (ringing current synchronization clock) from RGEN. Event signal came from LTUC firmware. Positive acknowledgment with F5334. System reaction: blocks the RGEN Action:...
  • Page 861 f5328.fm Nur für den internen Gebrauch F5328 LTUC ACGEN SYN OFF Type: Service-specific (Format 18) Short text: SYN2 clock of ACGEN missing Cause: No LTUC SYN2 clock (AC synchronization clock) from ACGEN. Event signal came from LTUC firmware. Positive acknowledgment with F5335. System reaction: locks the WGEN.
  • Page 862 f5329.fm Nur für den internen Gebrauch F5329 LTUC RGEN OVERLOAD Type: Service-specific (Format 23) Short text: Ringing current generator overloaded Cause: The ringing current generator is temporarily overloaded. If the overload does not end within 30 seconds, this will be interpreted as a board failure. System reaction: only signals overload.
  • Page 863 f5330.fm Nur für den internen Gebrauch F5330 LTUC AC GEN OVERLOAD Type: Service-specific (Format 23) Short text: Alternating current generator overloaded Cause: The alternating current generator is temporarily overloaded. If the overload does not end within 30 seconds, this will be interpreted as a board failure. System reaction: only signals overloads.
  • Page 864 f5331.fm Nur für den internen Gebrauch F5331 LTUC Type: Service-specific (Format 18) Short text: LTUC board defective. Cause: Analysis of overall clock supervision reveals that the LTUC board is defective. (Input clock, output clock, MUX or shelf distribution) System reaction: locks the LTUC and attempts to start up.
  • Page 865 f5332.fm Nur für den internen Gebrauch F5332 LTUC STBY CLOCK DEF Type: Service-specific (Format 18) Short text: Standby clock supply defective for all LTUCs Cause: Analysis of overall clock supervision reveals that the standby clock supply for all LTUCs is defective. System reaction: signals only.
  • Page 866 f5333.fm Nur für den internen Gebrauch F5333 LTUC STBY DEF Type: Service-specific (Format 18) Short text: Standby part of the LTUC board defective. Cause: Analysis of overall clock supervision concludes that the standby input level of the LTUC board is defective, but also that this error did not adversely affect system operation until after switchover. System reaction: locks the LTUC after switchover.
  • Page 867 f5334.fm Nur für den internen Gebrauch F5334 LTUC RGEN SYN ON Type: Service-specific (Format 18) Short text: SYN1 clock from RGEN okay again. Cause: LTUC SYN1 clock (ringing current generator synchronization clock) is available again. Event signal came from LTUC firmware. System reaction: starts up the RGEN Action:...
  • Page 868 f5335.fm Nur für den internen Gebrauch F5335 LTUC ACGEN SYN ON Type: Service-specific (Format 18) Short text: SYN2 clock from ACGEN okay again. Cause: LTUC SYN2 clock (AC generator synchronization clock) is available again. Event signal came from LTUC firmware. Action: Positive acknowledgment of F5328.
  • Page 869 f5336.fm Nur für den internen Gebrauch F5336 LTUC Type: Service-specific (several formats apply) Short text: RMS2 remote switch error Cause: Remote switch error (RMS2), reported by DIUR. Format 18: (entire RMS) ACTION=IN SERV means that the entire RMS is back in service. ACTION=OUT SERV means that the entire RMS is out-of-service.
  • Page 870 f5336.fm Nur für den internen Gebrauch Byte 1 Byte 2 Byte 3 [01] PCM Highway [02] Layer 2 error [01] No partner [02] Partner restored [03] Message cannot be sent [02]RMS Shelf [03] Message from RG [01] Clock error [03] Main system [02] Clock restored [04] Message from PCG [01] Bad reference clock...
  • Page 871 f5336.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 872 f5337.fm Nur für den internen Gebrauch F5337 LTUC MUSAC DEFECT Type: Service-relevant (Format 22) Short text: MUSAC chip defective Cause: A MUSAC chip in the LTUCE / LTUCX is defective. Traffic restriction in proportion to the number of failed speech highways. The trigger is recognized by the firmware / loadware of the LTUCE / LTUCX or the SCC and reported by the loadware to the system.
  • Page 873 f5337.fm Nur für den internen Gebrauch In the case of an LTUCX, the failure of the third or fourth MUSAC chip (0D, 0E) is reported even if the highways assigned are currently not in use. This is the case if there is no 'overlay' LTU configured for the relevant basic LTU. The reported MUSAC is also defective in this case and has to be replaced in order to avoid problems with later configurations of the 'overlay' LTU.
  • Page 874 f5338.fm Nur für den internen Gebrauch F5338 LTUC MTSC DEFECT Type: Service-specific (Format 22) Short text: MTSC component defective Cause: An MTSC component on the LTUC is defective. The highways on one LTU half have failed. Event signal came from the LTUC firmware. System reaction: locks the relevant highways.
  • Page 875 f5339.fm Nur für den internen Gebrauch F5339 LTUC PLL REDUNDANCE LOSS Type: Service-specific (Format 22) Short text: PLL component of LTUCE defective Cause: A redundant PLL component is defective. Event signal came from the LTUCE firmware. System reaction: board has been changed over to the other PLL circuit. Action: Replace board at next opportunity.
  • Page 876 f5340.fm Nur für den internen Gebrauch F5340 BOARD CONTR RESP ERROR Type: Service-specific (Format 22) Short text: Control response error. Cause: Control response error from a peripheral board. PP has received an errored control response byte from the PBC of the board during a routine PBC control response check. This indicates a defective PBC, since the FW and the MP are not affected.
  • Page 877 f5340.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 878 f5343.fm Nur für den internen Gebrauch F5343 BOARD HDLC ERROR Type: Service-specific (Format 22) Short text: HDLC link error. Cause: Message is output if the HDLC link of a peripheral board is defective. Errors on the HDLC shelf highway are detected by the data communication link (DCL) and reported to the error analysis system (FA).
  • Page 879 f5344.fm Nur für den internen Gebrauch F5344 BOARD HW ERROR Type: Service relevant (Format 22 and 43) Short text: Hardware fault on a peripheral board Cause: A hardware fault on a board was detected by the board self-test. This message can also appear as a result of an overflow of the SLMB16 board central queue.
  • Page 880 f5344.fm Nur für den internen Gebrauch RAM Error TDM Buffer Overflow FW Error Format 43: In format 43 fault scenarios are described by a meaningful REASON text. Depending on the REASON there are additional description fields: Reason: 00H WRONG CBM PARAMETER Type: Service relevant Short text:...
  • Page 881 f5344.fm Nur für den internen Gebrauch Interpretation of auxiliary data: CBM module: 00H-07H Number of affected CBM module on the board HWY/TSL table: All HWY/TSLs of the defective CBM module (32 x 3Bytes: 1Byte TSL and 2Bytes HWY); This table is only valid for LTUCC, not for STMI. text string: Error description text filled in by board LW.
  • Page 882 f5344.fm Nur für den internen Gebrauch Reason: 04 H AP ETHERNET ERROR (SELFTEST), Reason: 05 H AP ETHERNET ERROR (LW) Type: Service relevant Short text: 04H: Ethernet interface error (detected during startup by board selftest) 05H: Ethernet interface error (detected during normal operation by LW) Cause: The loadware or the selftest of the board (STMI) has detected an error on the Ethernet interface on the board.
  • Page 883 f5345.fm Nur für den internen Gebrauch F5345 BOARD INIT ERROR Type: Service-specific (Format 23) Short text: Peripheral board initialization error Cause: A peripheral board cannot be loaded. The causes may be traced to the board, but it may also be found to be the transmission of the LW from the hard disk to the board. The board is not necessarily a special board if the HW ID H’999 (HW-ID of the special board) is signaled.
  • Page 884 f5345.fm Nur für den internen Gebrauch Hex value Output text Interpretation Loadware not found on the HD Loadware on HD faulty or corrupt Board not available (NPR) BOARD DATA NOT LOADED Board data not loaded COPY ENDED Copy operation terminated by RAM in the Flash RECORD LOADED Loadware container loaded LW NOT FOUND...
  • Page 885 f5346.fm Nur für den internen Gebrauch F5346 BOARD LOOP DATA ERROR Type: Service-specific (Format 18/22) Short text: RTO: Test loop insertion error Cause: Format 18: Test loop insertion error. The board is automatically disabled. Format 22: The message from the RTO to FA is output in the HEX data. Action: Replace board specified in slot information (LTG:).
  • Page 886 f5347.fm Nur für den internen Gebrauch F5347 BOARD MP EC ERROR Type: Diagnosis-specific (Format 22) Short text: Implausible event code received by peripheral board. Cause: The firmware of the peripheral board concerned has received a message from peripheral processing (PP) with an invalid event code (EC). The event signal came from the board firmware. System reaction: statistics, signaling.
  • Page 887 f5348.fm Nur für den internen Gebrauch F5348 BOARD MP LW ERROR Type: Diagnosis-specific (Format 22) Short text: Error in microprocessor loadware. Cause: A loadware or hardware error has been detected in an analog or digital peripheral board. This error message can also be caused by a line error. Event signal came from the firmware of the board concerned.
  • Page 888 f5348.fm Nur für den internen Gebrauch Byte 0 Length of relevant bytes to follow Byte 1 Error type (DB_M_EE_LW_ERR_CODE_SET) Invalid function Invalid event code (F5631) Invalid OF branch Timeout List overflow (F5731) Scan overflow (F5401) PBC error following test No procedure Watchdog timeout (F5732) Invalid parameter (also: line error)(F5409) Checksum error (F5733)
  • Page 889 f5348.fm Nur für den internen Gebrauch NOTE: Can only be interpreted by your system specialist. A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 890 f5348.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 891 f5349.fm Nur für den internen Gebrauch F5349 BOARD MSG NOT TRANSMITTABLE Type: Service-specific (Format 22) Short text: Message cannot be transmitted to peripheral board. Cause: The data communication link (DCL) has made repeated, unsuccessful attempts to dispatch a message to a peripheral board (includes LTUC, SIU, CONF, PSIO). This error can also occur if the board is out of service, i.e., if it has only just been removed from the attendance list.
  • Page 892 f5350.fm Nur für den internen Gebrauch F5350 BOARD SECONDARY IN ATTEND L Type: Service-specific (Format 22) Short text: Board is back on attendance list Cause: The peripheral board concerned is back on the attendance list of the DCL. This message is output when a board is plugged into the correct slot or when the LTU power is turned back on. The event signal came from the firmware of the data communication link (DCL).
  • Page 893 f5351.fm Nur für den internen Gebrauch F5351 BOARD PER ADDR ERROR Type: Diagnosis-specific (Format 22) Short text: Message corrupted Cause: 1. Peripheral processing (PP) has received a message with an invalid source address (wrong PBC address). This is noticed by the TOP (task organization program) if no board is found or the wrong board type is detected at the address, or if the address is out of range.
  • Page 894 f5352.fm Nur für den internen Gebrauch F5352 BOARD PER EVT ERROR Type: Diagnosis-specific (Format 22) Short text: Implausible message from peripheral board to PP Cause: Implausible message received by peripheral processing (PP) from the microprocessor of a peripheral board. Event signal came from PP. System reaction: statistics.
  • Page 895 f5353.fm Nur für den internen Gebrauch F5353 BOARD REGISTER ERROR Type: Service-specific (Format 18/22) Short text: RTO: Error in code check register Cause: Format 18: Error in the code check register of the peripheral board controller (PBC). The board is automatically disabled. Format 22: The message from the RTO to FA is output in the HEX data.
  • Page 896 f5354.fm Nur für den internen Gebrauch F5354 BOARD SECONDARY OUT ATTEND L Type: Service-specific (Format 22) Short text: Board not plugged Cause: Board has been unplugged or has been placed out of service due to a board error, and is therefore no longer on the attendance list of the DCL. Positive acknowledgment with F5350. Error message F5308 LTUC OUT OF ATTENDANCE LIST is reported, in all cases (i.e., no individual message...
  • Page 897 f5355.fm Nur für den internen Gebrauch F5355 BOARD SPOR ERROR Type: Service-specific (Format 22) Short text: RTO: Sporadic error Cause: ACTION=NO ACT: sporadic error (advisory). ACTION=OUT OF SERV: sporadic error in conjunction with disable message generated due to peripheral error counter overflow. Board is entered in the IBP (startup procedure task) list and RTO message is output in the HEX data.
  • Page 898 f5356.fm Nur für den internen Gebrauch F5356 BOARD STATUS WORD ERROR Type: Service-specific (Format 22) Short text: RTO: RAM/PROM error. Cause: The board is automatically disabled due to a RAM/PROM error. The RTO message is entered in the HEX data. Action: Replace board.
  • Page 899 f5358.fm Nur für den internen Gebrauch F5358 BOARD TIME ERROR Type: Service-specific (Format 18/22) Short text: RTO: Timeout Cause: Format 18: Timeout, no response to routine test order. ACTION=RESET indicates the board was automatically reset. The functional earth of the shelf may not correspond to the required values. Format 22: Board is entered in the IBP (startup procedure task) list and RTO message is output in the HEX data.
  • Page 900 f5359.fm Nur für den internen Gebrauch F5359 BOARD PIT ERROR Type: Service-specific (Format 23) Short text: PIT load error Cause: Load error of the peripheral initialization task. Connection between PIT and DCL or peripheral processing lost while loading the peripherals. System reaction: message output about the fatal error on level 2 of the FA with the relevant response.
  • Page 901 f5371.fm Nur für den internen Gebrauch F5371 BOARD STAT OVERFLOW Type: Service-specific (Format 22) Short text: Statistics counter overflow (threshold value overstepped) Cause: Statistics counters monitor the alarms on this board. The board has been placed out of service due to too many alarms. Counter sequence: each alarm increments the error counter by 1.
  • Page 902 f5372.fm Nur für den internen Gebrauch F5372 BOARD BACK IN SERVICE Type: Service-relevant (Format 18/43) Short text: Board back in service Cause: Following a defect, the board was put back into service after multiple attempts and a preset block timeout. The board is then monitored in case any further failures occur. If a new defect occurs during this monitoring time, it is put back into service on a trial basis after a longer block time.
  • Page 903 f5373.fm Nur für den internen Gebrauch F5373 BOARD STOP NEW SEIZURES Type: Service-specific (Format 18) Short text: No outgoing calls possible on peripheral board Cause: Overload situation on the board. Outgoing calls are no longer possible; existing connections are preserved. At the end of the overload the system outputs message F5374 if no data is lost;...
  • Page 904 f5374.fm Nur für den internen Gebrauch F5374 BOARD START NEW SEIZURES Type: Service-specific (Format 18) Short text: Overload end Cause: End of board overload since no new lines have been seized. System reaction: outgoing calls are possible once more. Action: Positive acknowledgment of F5373, no action necessary.
  • Page 905 f5376.fm Nur für den internen Gebrauch F5376 BOARD DFE ERROR Type: Service-specific (Format 22) Short text: DFE error (Data Front End) Cause: The SLMR (Rolm board) has a DFE error. System reaction: statistics Action: No specific action. If the error persists contact your Next level of support..
  • Page 906 f5377.fm Nur für den internen Gebrauch F5377 BOARD RMS LEFT Type: Service-specific (Format 22) Short text: Board removed from the attendance list Cause: - Board of RMS shelf is not plugged or not correctly plugged. - Board error on a remote RMS shelf caused board to be removed from attendance list. System reaction: blocks the board in NPR status.
  • Page 907 f5388.fm Nur für den internen Gebrauch F5388 CIRCUIT EARTH BEGIN Type: Service-specific (Format 18) Short text: Start of ground leakage on main station line. Cause: Ground leakage on a-wire or b-wire of a main PABX loop circuit (main station line). Event signal came from the DH.
  • Page 908 f5389.fm Nur für den internen Gebrauch F5389 CIRCUIT EARTH END Type: Service-specific (Format 18) Short text: End of ground leakage on main station line Cause: End of ground leakage on main PABX loop circuit (main station line). Event signal came from the DH.
  • Page 909 f5390.fm Nur für den internen Gebrauch F5390 CIRCUIT END SHORT CIRCUIT Type: Service-specific (Format 18) Short text: End of short-circuit on station line Cause: Board has detected end of ground short on user circuit, and has switched feed signal back to active low. Positive acknowledgment of F5403 with automatic startup.
  • Page 910 f5391.fm Nur für den internen Gebrauch F5391 CIRCUIT EXT DIALTONE ERROR Type: Service-specific (Format 18) Short text: No external dial tone Cause: No external dial tone (i.e. no outward dialing to exchange). Exchange or tie line may have a breakage or is otherwise interrupted. Event signal came from device handler. System reaction: signals only.
  • Page 911 f5395.fm Nur für den internen Gebrauch F5395 CIRCUIT START UP ERROR Type: Service-specific (Format 22) Short text: Attendant console self-test error. Cause: Error found by attendant console self-test while booting. Event signal came from the ATND device handler. System reaction: locks the attendant console and delays startup.
  • Page 912 f5396.fm Nur für den internen Gebrauch F5396 CIRCUIT IDLE LOOP ERROR Type: Service-specific (Format 22) Short text: Attendant console self-test error. Cause: Error found by attendant console self-test. Event signal came from the ATND device handler. System reaction: locks the attendant console and delays startup. Action: Check the attendant console.
  • Page 913 f5397.fm Nur für den internen Gebrauch F5397 CIRCUIT INIT ERROR Type: Service-specific (Format 22) Short text: Initialization error Cause: Initialization error of a board circuit. Action: Action depends on the evaluation of the HEX data. System reaction: circuit already locked by DC. Interpretation of auxiliary data: In byte 1 of the hexadecimal output, the error is displayed according to the structure DB_M_LC_LOAD_RESULT_SET.
  • Page 914 f5398.fm Nur für den internen Gebrauch F5398 CIRCUIT LINE DISCONNECTED Type: Service-specific (Format 22) Short text: U* line switched off Cause: Line switched off by SLMD firmware. If the SLMD board is unable to receive messages from the CTE, e.g. because the terminal has been switched off or disconnected, the CTE will release any terminal connections and deactivate the U* interface on the system side.
  • Page 915 f5399.fm Nur für den internen Gebrauch F5399 CIRCUIT LINE ALARM BEG Type: Service-relevant (Format 43) Short text: Start of line alarm. Cause: Start of line alarm for a trunk or tie circuit. The trunk/tie line may have been interrupted. The error message F5400 is issued if the port is back in service.
  • Page 916 f5399.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 917 f5401.fm Nur für den internen Gebrauch F5401 CIRCUIT MP SCAN OVERFLOW Type: Service-specific (Format 22) Short text: Too many scan events Cause: Too many scan events for a circuit within a certain time unit. In the case of SLMA and SLMA1 boards, the second, associated circuit is also disabled (DUAL-SLIC). The second circuit on the board is calculated on the basis of the circuit number output in the HEX data, as follows: circuit number plus 8, or circuit number minus 8.
  • Page 918 f5401.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 919 f5403.fm Nur für den internen Gebrauch F5403 CIRCUIT SHORT CIRCUIT Type: Service-specific (Format 18) Short text: Short-circuit on user port Cause: Board has detected overcurrent on user port and has switched feed to active high. Positive acknowledgment with F5390. System reaction: lock for the circuit.
  • Page 920 f5404.fm Nur für den internen Gebrauch F5404 CIRCUIT LINE ACTIVATED Type: Service-specific (Format 18) Short text: U* line active again Cause: SLMD line active again, i.e. terminal has been plugged back in. The U* interface is re- activated either by the CTE or by the call processing system (CP). System reaction: end of the line alarm.
  • Page 921 f5405.fm Nur für den internen Gebrauch F5405 CIRCUIT LINE TIMEOUT Type: Service-specific (Format 18) Short text: No response from service module / U* line Cause: SLMD receives no answer from the service module or from the U* line. Positive acknowledgment with F5404. System reaction: locks the circuit and delays startup.
  • Page 922 f5406.fm Nur für den internen Gebrauch F5406 CIRCUIT SPOR ERROR Type: Service-specific (Format 43) Short text: RTO: Sporadic error during routine test operation Cause: ACTION=NO ACT: sporadic error (advisory). ACTION=OUT OF SERV: sporadic error in conjunction with disable message generated due to peripheral error counter overflow.
  • Page 923 f5407.fm Nur für den internen Gebrauch F5407 CIRCUIT TEST ERROR Type: Service-specific (Format 18/43) Short text: RTO: routine test error Cause: Format 18: Error detected during routine test. Format 43: invalid or implausible firmware parameters on an analog board. The RTO message is output in HEX data Device names, test carried out and test results are output in plain text (Format 43).
  • Page 924 f5409.fm Nur für den internen Gebrauch F5409 CIRCUIT MP INVALID PARA Type: Service-specific (Format 22) Short text: Invalid microprocessor parameters Cause: Invalid or bad parameters detected by microprocessor of an analog board. LW or system software error. System reaction: resets the circuit. Action: Save error message data and contact your Next level of...
  • Page 925 f5410.fm Nur für den internen Gebrauch F5410 CIRCUIT SYNC FAIL Type: Service-specific (Format 18) Short text: Loss of synchronization on U* line Cause: SLMD detects loss of synchronization or line alarm on the U* line, e.g. because terminal has been switched off or disconnected. Slot information (LTG:) is included. Positive acknowledgment with F5404. System reaction: locks the circuit.
  • Page 926 f5411.fm Nur für den internen Gebrauch F5411 CIRCUIT L1 SPOR ERROR Type: Service-specific (Format 22) Short text: Sporadic layer 1 error Cause: Short line alarm. Sporadic layer 1 error in digital networking circuit or for ATM circuits of all operating modes. It can refer to one circuit or all circuits of a board (see circuit information). Action: Check line or localize error with protocol tester.
  • Page 927 f5411.fm Nur für den internen Gebrauch ATM (for explanation of error types, see F5412) ATM cell lost Bit stuffing error Transmit FIFO overflow Receive FIFO overflow Fault at the UTOPIA interface Signal label mismatched Byte 1,2 Number of errors reported Byte 3 Length of data to follow Byte 4-90...
  • Page 928 f5412.fm Nur für den internen Gebrauch F5412 CIRCUIT L1 ERROR Type: Service-relevant (Format 22/36) Short text: Layer 1 error(s) (line alarm) Cause: There is a fault on layer 1 of the line. • Networking circuit only (Format 36). • This message is also used for ATM circuits in all operating modes. It can refer to a circuit or all circuits on the board (see circuit information).
  • Page 929 f5412.fm Nur für den internen Gebrauch REASON: 05H AIS Cause: Alarm indication signal from partner (AIS ALARM) REASON: 06H REMOTE ALARM Cause: Remote alarm from partner (DISTANT ALARM) REASON: 07H NO DATA LOADED Cause: Record data not loaded (no line alarm) REASON: 0BH REMOTE ALARM CRC4 Cause: Remote alarm CRC4 from partner (DISTANT ALARM)
  • Page 930 f5412.fm Nur für den internen Gebrauch REASON: 10H LOSS OF SIGNAL Cause: Loss of signal detected for greater than the specified interval. REASON: 11H MAX ERROR SECS Cause: The maximum number of errored seconds has been detected for the specified interval. REASON: 12H RED ALARM LFA Cause: The board is in a red alarm condition (detected locally) due to loss of single frame...
  • Page 931 f5412.fm Nur für den internen Gebrauch Only for ATM: REASON: 19H PORTSWITCHING: BOARD IN ATM-HUB MISSING Type: Service-relevant Cause: Board in the system’s ATM hub not connected, occurs in ports witching operating mode in the case of STMA. Action: Check the system’s ATM hub, verify that all necessary subscriber line boards are connected/cabled/check for hardware errors.
  • Page 932 f5412.fm Nur für den internen Gebrauch REASON: 1EH RECEIVE FIFO OVERFLOW Cause: FIFO overflow on receipt (LOCAL ALARM) Action: Check parameter "CELL Delay Variation time"; if necessary increase if the error occurs frequently (result: Increased delay in voice connections, possible echo problems) If parameter OK: Replace board REASON: 1FH UTOPIA INTERFACE FAULT Cause:...
  • Page 933 f5412.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 934 f5413.fm Nur für den internen Gebrauch F5413 CIRCUIT L2 SPOR ERROR Type: Service-specific (Format 22) Short text: Sporadic layer 2 error Cause: Sporadic layer 2 error in digital networking circuit. System reaction: statistics Action: Action depends on the evaluation of the HEX data. Save error message data and contact your Next level of support.
  • Page 935 f5413.fm Nur für den internen Gebrauch Error Type Error Code Error Condition Affected Network User States (Note 1) Management Action Management Action Receipt of unsolicited Supervisory (F=1) Error log Implementation response dependent DM (F=1) 7, 8 Error log Implementation dependent UA (F=1) 4, 7, 8 TEI removal procedure...
  • Page 936 f5413.fm Nur für den internen Gebrauch Reason: Wrong Wiring: - Send-Send and Receive-Receive instead of Send-Receive, Receive-Send. Special case: 00-03 Byte PNE: (Private Network Emulator) The following information indicates a PNE error message Byte 04-90 PNE error message in ASCII format See also Section 8.14, “Device names”.
  • Page 937 f5414.fm Nur für den internen Gebrauch F5414 CIRCUIT L2 ERROR Type: Service-specific (Format 22/36) Short text: Layer 2 error Cause: Layer 2 error (protocol), may also have been caused by remote partner. Format 36: Layer 2 error in digital networking circuit only (protocol). Positive acknowledgment with F5418. System reaction: statistics, locks layer 2-3 Action:...
  • Page 938 f5415.fm Nur für den internen Gebrauch F5415 CIRCUIT L2 STOP NEW SEIZURES Type: Service-specific (Format 18) Short text: Overload prevention is active Cause: STOP for re-seizures. Overload prevention for digital networking circuits System reaction: locks layer 2-3 Action: Look for any associated, additional error messages. If this error occurs frequently, save the error message data and contact your Next level of support.
  • Page 939 f5416.fm Nur für den internen Gebrauch F5416 CIRCUIT L2 START NEW SEIZURES Type: Service-specific (Format 18) Short text: Overload end Cause: Re-seizures possible again. Overload queue has been worked off or board has reset itself. System reaction: ends of lock on layer 2-3 Action: Look for any associated, additional error messages.
  • Page 940 f5417.fm Nur für den internen Gebrauch F5417 CIRCUIT L3 ERROR Type: Service-relevant (Format 22) Short text: Layer 3 error Cause: Layer 3 error in digital networking record (switching technology). An L3 ERROR can occur in connection with AMO TWABE. The S2 interface requires a response from the remote system within 1.5 seconds.
  • Page 941 f5417.fm Nur für den internen Gebrauch A31003-H3100-S104-14-7620, 11/2015 Troubleshooting (AlFe), Service Documentation...
  • Page 942 f5417.fm Nur für den internen Gebrauch To find the message type convert the HEX to binary and look up below. Excerpt ETS 300 102-1: December 1990 4.4 Message type Table 4.2: Message types Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 Escape to nationally specific message type;...
  • Page 943 f5417.fm Nur für den internen Gebrauch Other formats from reported scenarios: F5417 E8 N0532 NO ACT CIRCUIT L3 ERROR 11-04-19 11:39:49 ALARM CLASS:SWU-LOG:201 P301:LTG1 :LTU4 :025: 01 : 0 Q2196-X DIU-N2/1 BST:01 PLS:-07 FORMAT:22 DEVICE NAME: S2VERB 2600010A08007D080280D1140100FFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF...
  • Page 944 f5417.fm Nur für den internen Gebrauch DB_QF_CIR_L3_CHAN_REST_LOC for US Release 6.0 (no supplementary data) DB_QF_CIR_L3_SPAN_REST_LOC for US Release 6.0 (no supplementary data) DB_QF_CIR_L3_CHAN_REST_REM for US Release 6.0 (no supplementary data) DB_QF_CIR_L3_SPAN_REST_REM for US Release 6.0 (no supplementary data) DB_QF_CIR_L3_REST_NO_ACK for US Release 6.0 (no supplementary data) DB_QF_CIR_L3_CHAN_MB_REM for US Release 6.0 (no supplementary data) DB_QF_CIR_L3_CHAN_OOS_REM...
  • Page 945 f5417.fm Nur für den internen Gebrauch DB_QF_CIR_L3_Y_OVERFLOW ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_TAG ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_LENGTH ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_RANGE ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_ENUMERATED ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_SIZE ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_SELECT ASN1 encoder error (DH_M_NW_L3_ERR_COMP_STR) DB_QF_CIR_L3_Y_ANY_DEF_BY ASN1 encoder error...
  • Page 946 f5418.fm Nur für den internen Gebrauch F5418 CIRCUIT LX ACTIVE Type: Service-specific (Format 36) Short text: Layer 1, or layer 2/3 okay again Cause: The errored protocol layer (L1, L2 or L3) of the networking circuit is intact again. Positive response for F5412 and F5414.
  • Page 947 f5420.fm Nur für den internen Gebrauch F5420 TERM ASYNC Type: Service-specific (Format 18) Short text: Terminal asynchronous Cause: Terminal asynchronous (DIGITE, DIG M86). Board attempts to synchronize. If error repeats and DH is already asynchronous, the terminal will remain asynchronous. The FA error analysis system deactivates the terminal after each error, although the error message is only signaled once.
  • Page 948 f5421.fm Nur für den internen Gebrauch F5421 TERM NO BLOCKED ID Type: Service-specific (Format 18) Short text: Defective ID card reader (IDCR). Cause: Board checks for end-of-block character. If this is missing, PP sends a TERM_AWL_DEF message to the FA. System reaction: - SLMB, SLMB16: terminal is reset automatically.
  • Page 949 f5422.fm Nur für den internen Gebrauch F5422 TERM DEACTIVATED Type: Service-specific (Format 22) Short text: Terminal deactivated Cause: Terminal connected to SLMD (direct or via adapter CTE) has deactivated itself due to an error. Terminal sends message to SLMD. System reaction: terminal is blocked by FA and restored to service after a delay.
  • Page 950 f5423.fm Nur für den internen Gebrauch F5423 TERM LL STAT Type: Service-specific (Format 22) Short text: Terminal last look error Cause: - Sporadic transmission error, detected more than three times during terminal last look verification (DIGITE / ATND). - DH receives ‘data transfer error’ or ‘unknown command’ message from DIGITE or attendant console. - DCI cannot be reloaded.
  • Page 951 f5424.fm Nur für den internen Gebrauch F5424 TERM NOT READY Type: Service-specific (Format 18) Short text: X.21 terminal not ready Cause: Terminal is not ready, i.e. cannot accept call, power failure at TTX terminal, or terminal adapter of CTE loose/not plugged. Terminals with S* interface: terminal is not configured. Positive acknowledgment with F5425.
  • Page 952 f5425.fm Nur für den internen Gebrauch F5425 TERM READY Type: Service-specific (Format 18) Short text: X.21 terminal ready again / plugged in Cause: X.21/T3510/S3510/CTE a/b or DCI terminal startup (restart) completed. For terminals with an S* interface this message means terminal is installed. System reaction: end of line alarm for the terminal Action:...
  • Page 953 f5426.fm Nur für den internen Gebrauch F5426 TERM REFRESH Type: Service-specific (Format 18) Short text: Refresh requested by terminal in ‘asynchronous’ status Cause: Terminal has lost call processing data and sent a refresh request to the DH. End of synchronization indicated by F5688 and terminal is automatically restored to service by FA.
  • Page 954 f5427.fm Nur für den internen Gebrauch F5427 TERM DEV HARDWARE ERROR Type: Service-specific (Format 22) Short text: Hardware error of a terminal (HWER) Cause: Terminal has detected a hardware error and has reported it to the SOMUP handler by means of a transfer message sent via PP. System reaction: terminal is blocked (deactivated) Action:...
  • Page 955 f5428.fm Nur für den internen Gebrauch F5428 TERM DEV MSG ERROR Type: Service-specific (Format 22) Short text: Message error of a terminal (MSER) Cause: Terminal has received a bad message and has reported it to the SOMUP handler by means of a transfer message sent via PP. System reaction: signals only Action:...
  • Page 956 f5429.fm Nur für den internen Gebrauch F5429 TERM TERMINAL SWITCHED OFF Type: Service-specific (Format 18) Short text: Terminal switch-off indication (TSOI) detected Cause: Message from SOMUP handler to FA: a) An adapted server has switched itself off. b) The DCI has been unplugged or the line is asynchronous. c) T3510 / S3510 monitor has been switched off.
  • Page 957 f5431.fm Nur für den internen Gebrauch F5431 TERM TERMINAL RESET Type: Service-specific (Format 18) Short text: Terminal adapter reset indication (TARI) detected Cause: a) Message TERM_SOM_TARI - Terminal adapter reset on CTE or T3510 / S3510 b) Message TERM_DCI_DH_TARI - Partner DCI does not respond to cleardown attempt - DCI power-on (USA) - DCI plugged in (USA).
  • Page 958 f5432.fm Nur für den internen Gebrauch F5432 TERM TIMEOUT Type: Service-specific (Format 18) Short text: Timeout error Cause: Terminal does not react to a request or signaling criterion from call processing (CP). Positive acknowledgment with F5425. System reaction: terminal line alarm Action: Check terminal, connector and line circuit board.
  • Page 959 f5433.fm Nur für den internen Gebrauch F5433 TERM DCI WRONG VERS Type: Service-specific (Format 18) Short text: Wrong DCI version Cause: The DCI cannot be loaded but replies with a parameter error, e.g. due to wrong PROM version. System reaction: the DCI is deactivated.
  • Page 960 f5434.fm Nur für den internen Gebrauch F5434 TERM DCI NO ANSW Type: Service-specific (Format 22) Short text: DCI not responding properly Cause: DCI is not responding properly and cannot be loaded. Positive acknowledgment with F5425. System reaction: locks the DCI Action: Action depends on the evaluation of the HEX data.
  • Page 961 f5439.fm Nur für den internen Gebrauch F5439 TERM COR-T/SET4 AK D BIT Type: Service-specific (Format 18) Short text: Set 400 downloading aborted Cause: The DIGITE M86 downloading process has been aborted. Data inconsistency in downloaded data. System reaction: terminal disabled Action: Check terminal.
  • Page 962 f5440.fm Nur für den internen Gebrauch F5440 TERM COR-T/SET4 AK W BIT Type: Service-specific (Format 18) Short text: Set 400 watchdog timeout Cause: Watchdog timeout in DIGITE M86. System reaction: the terminal is disabled by the system and subsequently restored to service again after a delay.
  • Page 963 f5444.fm Nur für den internen Gebrauch F5444 TERM TERMINAL NPR Type: Service-specific (Format 18) Short text: Terminal (adapter) not present Cause: Terminal adapters, adapted servers or non-voice terminals connected to CTE are absent (not present) or are not responding during startup. Positive acknowledgment with F5425. System reaction: line alarm.
  • Page 964 f5445.fm Nur für den internen Gebrauch F5445 TERM STAT OVERFLOW Type: Service-specific (Format 22) Short text: Statistics counter overflow (threshold value exceeded) Cause: Statistics counters monitor the alarms on this terminal. The terminal has been placed out of service due to too many alarms. Counter sequence: each alarm increments the error counter by 1.
  • Page 965 f5446.fm Nur für den internen Gebrauch F5446 TERM BACK IN SERVICE Type: Service-relevant (Format 18) Short text: Terminal back in service Cause: Following a defect, the terminal was put back into service after multiple attempts and a preset block timeout. The terminal is monitored to see if another failure occurs. If a new defect occurs during this monitoring time, it is put back into service on a trial basis after a longer block time.
  • Page 966 f5447.fm Nur für den internen Gebrauch F5447 TERM OVERLOAD BEG Type: Service-specific (Format 22) Short text: Overload of digital terminal Cause: Station user "playing" on the Digite (e.g. indiscriminately pressing keys or "drumming" on the hook switch). The message came from call processing. The terminal is deactivated and enabled again after about one minute.
  • Page 967 f5448.fm Nur für den internen Gebrauch F5448 TERM OVERLOAD END Type: Service-specific (Format 22) Short text: Terminal back in service Cause: Station user stopped "playing" on the Digite System reaction: the Digite is placed in service again. Action: Positive acknowledgment of F5447, no action. Interpretation of auxiliary data: Byte 0 = Length of following, relevant bytes Byte 1-7 = HEX value, convert using ASCII table.
  • Page 968 f5449.fm Nur für den internen Gebrauch F5449 TERM CORNET-T ERROR Type: Service-specific (Format 22) Short text: Error in CorNet-T terminal startup Cause: Error in CorNet-T terminal during downloading, or line alarm on CorNet-T line. System reaction: depends on the error types, see Interpretation of auxiliary data. Action: If error recurs frequently, replace terminal.
  • Page 969 f5450.fm Nur für den internen Gebrauch F5450 TERM CORNET-T MSG ERROR Type: Service-specific (Format 22) Short text: CorNet-T terminal message corrupted Cause: Corruption of CorNet-T messages to line peripheral (device handler). Software error! Action: Action depends on the evaluation of the HEX data. Save error message data and contact your Next level of support.
  • Page 970 f5451.fm Nur für den internen Gebrauch F5451 TERM CORNET-T TIME ERROR Type: Service-specific (Format 22) Short text: Timeout while waiting for CorNet T messages Cause: Timer exceeded (timeout) during CorNet T message exchange; detected by system software. Board possibly unplugged during operation, causing loss of message traffic. System reaction: statistics Action:...
  • Page 971 f5452.fm Nur für den internen Gebrauch F5452 TERM FUNCT L3 ERROR Type: Diagnosis-specific (Format 22) Short text: Layer 3 error of functional terminal Cause: Layer 3 error of functional terminal. Software error! Error type indicated in byte 1 of hexadecimal output. System reaction: signals only Action:...
  • Page 972 f5453.fm Nur für den internen Gebrauch F5453 TERM L2 ERROR Type: Service-specific (Format 22) Short text: Layer 2 terminal error Cause: Layer 2 error of terminals in S bus or similar configurations. This is only an error, if it is not due to unplugging or manually deactivating a terminal.
  • Page 973 f5453.fm Nur für den internen Gebrauch 0F Device is not connected or not responding must not be indicated for reasons of serviceability. These cases are indicated by TRS instead of NPR in the status memory. See also Section 8.14, “Device names”.
  • Page 974 f5454.fm Nur für den internen Gebrauch F5454 TERM L2 SPOR ERROR Type: Service-specific (Format 22) Short text: Sporadic layer 2 error Cause: Sporadic Layer 2 error of S bus terminals or similar configuration.. System reaction: statistics. It is only locked when the statistics overflow Action: No action currently necessary.
  • Page 975 f5455.fm Nur für den internen Gebrauch F5455 TERM LX ACTIVE Type: Service-specific (Format 22) Short text: Terminal layer 2 active again Cause: Terminal or user circuit of S bus is okay again. System reaction: layer 2 protocol successfully established. Action: Positive acknowledgment of F5453, without action.
  • Page 976 f5457.fm Nur für den internen Gebrauch F5457 TERM A ANS T OUT Type: Service-specific (Format 18) Short text: RolmPhone timeout (USA) Cause: RolmPhone timeout in automatic answer mode (auto answer timeout). System reaction: locks and delayed restart Action: Check device and ensure that the auto answer function is working properly. See also Section 8.14, “Device names”.
  • Page 977 f5458.fm Nur für den internen Gebrauch F5458 TERM WRONG R DEV Type: Service-specific (Format 22) Short text: Wrong Rolm device Cause: Wrong RolmPhone connected. System reaction: signals only Action: Connect the correct RolmPhone model or reconfigure the line. Interpretation of auxiliary data: Byte 0 = Length of data to follow (3) Byte 1 = CONFIGURED: (RolmPhone ID of configured device) Byte 2 = EXISTING: (RolmPhone ID of connected device)
  • Page 978 f5459.fm Nur für den internen Gebrauch F5459 TERM BAD TRUNK K Type: Service-specific (Format 18) Short text: Central office trunk connection defective (USA) Cause: RolmPhone user reports defective or bad central office trunk connection by pressing "Bad Trunk" key. System reaction: signals only Action: Check central office trunk.
  • Page 979 f5460.fm Nur für den internen Gebrauch F5460 CIRCUIT LW EXCEPTION IMPORTANT: This message replaces the error messages F5970 to F5983. Message texts: REASON: H00 CALLED FUNCTION DOES NOT EXIST Type: Diagnosis-specific (Format 43) Short text: Procedure cannot be called (identical to F5970) Cause: A specific procedure cannot be called.
  • Page 980 f5460.fm Nur für den internen Gebrauch REASON: H01 MESSAGE SENT TO NOT EXISTING PROCESS Type: Diagnosis-specific (Format 43) Short text: Message sent to non-existent process (identical to F5971) Cause: A message or an event was sent to a non-existent process. Error in the loadware of a COSMOS module or in the system software.
  • Page 981 f5460.fm Nur für den internen Gebrauch REASON: H04 MAILBOX OR BUFFER OVERFLOW Type: Diagnosis-specific (Format 43) Short text: Buffer overflow in the mailbox (identical to F5974) Cause: Error in the loadware of a COSMOS module, or too many messages are arriving at the circuit.
  • Page 982 f5460.fm Nur für den internen Gebrauch REASON: H07 COSMOS EXCEPTION Type: Diagnosis-specific (Format 43) Short text: COSMOS exception (identical to F5977) Cause: An exception (error) was output by the COSMOS operating system. There is an invalid COSMOS call or an incorrect parameter. Error in the loadware of a COSMOS module. Action: A solution is determined by the interpretation of the auxiliary data.
  • Page 983 f5460.fm Nur für den internen Gebrauch REASON: H0A PARAMETER NOT VALID Type: Diagnosis-specific (Format 43) Short text: Parameter invalid (identical to F5980) Cause: The parameters provided are invalid in the current CASE. Error in the loadware of a COSMOS module or in the system software. Action: The circuit is reset by the system and restarted immediately.
  • Page 984 f5460.fm Nur für den internen Gebrauch REASON: H0D STMA DYNAMIC TRUNKING: SVC TRACEPOINT Type: Diagnosis-specific (Format 43) Short text: One of the "SVC connection" trace points was reached in STMA operating mode Networking2.0. Cause: One or more STMA, Networking 2.0 specific trace points were enabled by means of the PETRA AMO in order to display information on the setting up and clearing down of switched virtual connections in the ATM network.
  • Page 985 f5460.fm Nur für den internen Gebrauch REASON: H14 LW EXCEPTION DUMMY Type: Diagnosis-specific (Format 43) Short text: Error with DUMMY event (identical to F5983) Cause: An error occurred with a DUMMY event Action: For diagnosis purposes, this message is temporarily incorporated into the loadware code of some boards by the loadware development department.
  • Page 986 f5461.fm Nur für den internen Gebrauch F5461 CIRCUIT LW DETECT ERROR Cause: See REASON. See also Section 8.14, “Device names”. REASON: 04H CONFIG ERR: EXTENDED SUBSCR LOOP AND PULSE METERING BY TONES Type: Service-specific Short text: Incorrect configuration, extended subscriber loop and pulse metering by tones cannot be performed simultaneously.
  • Page 987 f5462.fm Nur für den internen Gebrauch F5462 CIRCUIT NCT REJECTION (US-specific) Type: Service-specific (Format 22) Short text: MCI-NCT (MCI Communications Corporation - Network Call Transfer) rejected. Cause: The CP sends a message to indicate that it was not possible to call up a network-wide call transfer with MCI.
  • Page 988 f5463.fm Nur für den internen Gebrauch F5463 CIRCUIT NOT IN SERVICE Type: Service-relevant (Format 18) Short text: Circuit did not go into service. Cause: Despite several attempts to put the unit into service (max. 8, for more information, see AMO PSTAT), the element could not be put into service correctly due to a new error. This problem may also be caused by the line or the remote station.
  • Page 989 f5470.fm Nur für den internen Gebrauch F5470 L1 PORT ERROR Type: Service relevant (Format 43) Short text: A loss of layer 1 of the physical cable is detected. Cause: This message is directly related to the physical cable which is mounted on the board. The layer 1 has detected an error.
  • Page 990 f5471.fm Nur für den internen Gebrauch F5471 L1 PORT ACTIVE Type: Service relevant (Format 43) Short text: The layer 1 of the physical cable is back again. Cause: This message is directly related to the physical cable which is mounted on the board. The layer 1 has been detected again.
  • Page 991 f5472.fm Nur für den internen Gebrauch F5472 L1 SPOR PORT ERROR Type: Diagnosis relevant (Format 43) Short text: A sporadical error of layer 1 of the physical cable is detected. Cause: A sporadical error of layer 1 of the physical cable is detected. System reaction: Standard : The error counter for reference clock handling is incremented.
  • Page 992 f5473.fm Nur für den internen Gebrauch F5473 LOSS OF SIGNAL Type: Service relevant (Format 22) Short text: Loss of signal. Cause: T1 specific. Sporadic T1 layer 1 error. Loss of signal. Line interrupted for less than 1500 ms. System reaction: Set the lock bit for reference clock.
  • Page 993 f5474.fm Nur für den internen Gebrauch F5474 MAX ERROR SECS Type: Service relevant (Format 22) Short text: Max error secs. Cause: T1 specific. Sporadic T1 layer 1 error. Max error per seconds (Bit slips). number of errors is above threshold. System reaction: Set the lock bit for reference clock.
  • Page 994 f5475.fm Nur für den internen Gebrauch F5475 ACQUISITION OF SIGNAL Type: Service relevant (Format 22) Short text: Acquisition of signal. Cause: T1 specific. End of sporadic T1 layer 1 error. Acquisition of signal. Line connected again. System reaction: Reset of lock bit for reference clock. Action: No action necessary because ’good’...
  • Page 995 f5476.fm Nur für den internen Gebrauch F5476 MIN ERROR SECS Type: Service relevant (Format 22) Short text: Min error secs. Cause: T1 specific. End of sporadic T1 layer 1 error. Min error per seconds (Bit slips). Number of errors is below threshold. System reaction: Reset of lock bit for reference clock.
  • Page 996 f5477.fm Nur für den internen Gebrauch F5477 CIRCUIT ENCRYPTION ERROR Type: Service-relevant (Format 43) Short text: Problem for TLS connection to the partner. Cause: Certificate or configuration missing. System reaction: Connection is set up unencrypted. Action: Find the cause of the encryption problem and correct the setting. Interpretation of auxiliary data: Start and end of encryption problems are indicated in plain text: 00h - NO TLS CONNECTION ESTABLISHED...
  • Page 997 f5500.fm Nur für den internen Gebrauch F5500 L2 BS LOAD ERROR Type: Service-specific (Format 22) Short text: Load error in the base station Cause: Base station was not installed by the cordless module or is no longer installed. The end of the error is signaled with F5455 TERM LX AKTIV.
  • Page 998 f5501.fm Nur für den internen Gebrauch F5501 TERM L2 BS NO RESPONSE Type: Service-specific (Format 22) Short text: Base station not responding Cause: The cordless module can no longer contact the base station. The end of the error is signaled with F5455 TERM LX AKTIV.
  • Page 999 f5502.fm Nur für den internen Gebrauch F5502 TERM RESTORED Type: Service-specific (Format 18) Short text: Terminal was blocked and has been restored Cause: Following a restore process, an ISDN terminal remained in the NPR state. This was detected by the DC. System reaction: reset command for the terminal.
  • Page 1000 f5503.fm Nur für den internen Gebrauch F5503 TERM LW DETECT ERROR Cause: See REASON. See also Section 8.14, “Device names”. REASON: 00H PROLONGING CONNECTION: SIGNALLING DISCONNECTED Type: Service-specific (Format 43) Short text: Prolonging connection interrupted. (Emergency mode). Cause: Prolonging connection (TSC) to the remote Optiset port was interrupted. Calls that have been set up by the remote subscriber are then executed via the remote node (emergency mode).

This manual is also suitable for:

Hipath 4000
Save PDF