NEC America, Inc. reserves t he right to change th e specifications, functions, or
features, at any time, without notice.
NEC America, Inc. has prepared this document for use by its employees and
customers. The information contained herein is the property of NEC America,
Inc. and shall not be reproduced without prior written approval from NEC
America, Inc.
This manual describes routine system maintenance and fault repair procedures. This chapter explains how to
follow the manual and p rovides precaut ions pertaining t o maintenance jo bs as a whole. Be s ure to read thi s chapยญter thoroughly before starting the req uired maintenance job.
2. HOW TO FOLLOW THE MANUAL
If technicians engage in a fault repair with a sufficient amount of knowledge of the system (system
configurations, controlling systems, functions, etc.), the time spent repairing the system is minimized. This
manual provides explanations about the system, while placing emphasis on system configurations, controlling
systems, and functions. If fau lts of all conceivable cas es are to be assumed for the expl anations, the explanat ions
may lack reality and be more difficult to understand. Therefore, this manual provides the explanations on the
basis of the following points:
(1) It is very important to judge whether the fault has occurred in the system or at any of the peripheral
equipment.
(2) In case the system is faulty, explanations will be given about the actions to be taken until you identify the
faulty circu it card/cards.
(3) Explanations will be omitted pertaining to the following faults:
โขFault of peripheral equipment (MAT, telephone sets, etc.)
โขFault due to an error in office data assignment
โขFault due to an error in ins tall atio n proced ure (an er ror i n circ uit ca rd swit ch s etting, c ross- conn ecti on,
etc.)
(4) How to Read This Manual
โขWhen a fau lt is to be repaired fo r the first time
See Section 3, Howto Read Precautions,Diagnostic,
See Section 3, How to Read Prec autions, Diagnostic,
Go to Chapter 5.
Go to Chapter 5.
See Section 4, Reporting Fault to NEC,
and Fault Repair Information, Chapter 2.
and F a ult Repair Information, Chapter 2.
in Chapter 2.
NDA-24307CHAPTER 1
Page 1
Issue 1
Page 30
INTRODUCTION
โขWhen only the contents of a system message needs to be known, or when a fault is to be diagnosed
from a system message
โขWhen the range of faulty conditions has been specified and a faulty circuit card can be assumed
โขWhen investigating the system for the purpose of a fault repair
Chapter 5
Chapter 5
See Section 4, Reporting Fau lt to NEC, in Chapter 2.
See Section 4, Reporting Fault to NEC, in Chapter 2.
Chapter 5
โขWhen replacing a unit/circuit card with a spare
Chapter 4
โขWhen performing routine maintenance
Chapter 7
CHAPTER 1NDA-24307
Page 2
Issue 1
Page 31
CHAPTER 2SYSTEM MAINTENANCE OUTLINE
1. GENERAL
1.1 Purpose
This chapter explains the outline of fault diagnosis and duties necessary to maintain the PBX.
1.2 Administrative Management Procedures
Figure 2-1 shows the work flow of the administrative management procedures.
Administrative
Management Works
Administrative Works
Expansion and Change of
Station Users
See Chapter 6
Traffic Management
Actions on Claims from
Station Users and/or Operators
Management Works
Station Message Detail
Recording System (SMDR)
Routine Diagnosis
Diagnosis result, system message displays abnormality
Routine Maintenance
System Status Monitor
Alarm Indications
Collection of System Messages
Indication of Lockout Stations
See Chapter 6
(B)
Office Data Management and Office
Data Protection
(A)
See Chapter 6
See Chapter 6
See Chapter 7
See Chapter 6
(A)
See Chapter 6
Fault Analysis/
Test Operation/
Changeover/
Make-Busy/Circuit
Card Change/
Initialization
(B)
Line fault
Circuit card fault
Terminal
(Tel., etc.) fault
Fault cause not
able to be localized
Refer to
Chapter 5
(Abnormal
Congestion)
Line Load Control
See Chapter 6
Figure 2-1 Flow of Administrative Management Procedures
NDA-24307CHAPTER 2
Page 3
Issue 1
Page 32
SYSTEM MAINTENANCE OUTLINE
1.3 How to Follow This Manual
Table 2-1 provides a brief d es cription of the contents for each chapter in this manu a l.
Table 2-1 How to Follow This Manual Guide
CHAPTERDESCRIPTION
2See Section 2, Basic Knowledge.
Explains basic knowledge of fault detection and indication, functions and fault range of the system,
etc.
See Section 3, How to Read Precautions, Diagnost ic, and Fault Repair Information.
Explains the methods of procedure performance and various symbols used in the description.
See Section 4, Reporting Fault to NEC.
Explains the method of forwarding faulty circuit cards, the method of creating a history record for
future fault repair, and the method of reporting faults to NEC.
3Explains how to read and analyze system messages.
4Explains the method of replacing a unit/circuit card due to a fault.
5Explains repair procedures corresponding to the faults of processors or equipment.
6Explains how to control the system in service management functions and precautions required in the
system control process.
7Explains routine maintenance.
8Explains the commands used in the system administrative management procedure.
2. BASIC KNOWLEDGE
This section identifi es the information nec essary for the system operations and maintenance procedures.
2.1 System Configuration
2.2 Line Equipment Numbers (LENS)
2.3 Loca l Partition (LP) Numb er
2.4 Assignment of Network Control Node (NCN)
2.5 System Messages
2.6 Fault Detecting Function
2.7 Range of Faults Specification
2.8 Explanation of Terms
CHAPTER 2NDA-24307
Page 4
Issue 1
Page 33
SYSTEM MAINTENANCE OUTLINE
2.1 System Configuration
Figure 2-2 shows the system configuration of the fully expanded NEAX2400 IPX IPX-U.
LN0
ISW
......
......
LN1
LN3LN2
ISW: Inter-node Switch
LN:Local Node
FRONT VIEW
Figure 2-2 NEAX2400 IPX IPX-U
NDA-24307CHAPTER 2
Page 5
Issue 1
Page 34
SYSTEM MAINTENANCE OUTLINE
2.1.1Configuration of the System
The NEAX2400 IPX IPX-U system (referred to in the remainder of this manual as โthe systemโ) is
configured by a single Inter-node Switch (ISW) and a maximum of 4 Local Nodes (LNs). Refer to
figures in this sec tion. The ISW and LNs are connec ted via the Fusion link, wit h Ethernet and physi cal
PCM cables connected to ea ch other. Figure 2-3 pro vides a n overall image of system configura tion. A
two-module ISW and maximum four Local nodes compose a single network system via the Fusion
link.
Ether
ISW
PCM Cable
LN0LN1
IMG0IMG1IMG2IMG3
TOPUTOPUTOPUTOPU
PIM3PIM3PIM3PIM3
LN0/1/2/3
LN2LN3
LN0
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
ISW
LN1
......
......
......
......
......
......
......
......
......
......
LN3LN2
......
......
......
......
......
......
......
......
PIM2PIM2PIM2PIM2
ISW
TOPU
ISWM
LPM
BASEU
ISW: Inter-node Switch
LN: Local Node
TOPU: Top Unit
LPM: Local Processor Module
TSWM: Time Division Switch Module
ISWM:
FANUFANUFANUFANU
PIM1PIM1PIM1PIM1
PIM0PIM0PIM0PIM0
LPMTSWM0TSWM1DUMMY
BASEUBASEUBASEUBASEU
Inter-node Switch Module
Figure 2-3 System Configuration
CHAPTER 2NDA-24307
Page 6
Issue 1
FRONT VIEWFRONT VIEW
PIM:
FANU:
Port Interface Module
Fan Unit
BASEU: Base Unit
Page 35
[ Details on PC M Cable Connections between ISW and LN ]
For actual cable runnings, refer tothe Installation Manual.
LN: L o ca l N o d e IS W: Inte r-n o d e S w itch
Figure 2-4 Details on Inter-node PCM Cable Connections
NDA-24307CHAPTER 2
To LN3
To LN2
To LN1
Page 7
Issue 1
Page 36
SYSTEM MAINTENANCE OUTLINE
[Details on Ether Cable Connections]
ISW and each LN can achieve a Fusion link by physically connecting themselves via the 10 BASE-T cables. This figure
shows an example where the CPR-accommodated LANI cards (internal LANI: PCI slot 00) are mutually connected via
HUB0/HUB1 (PA-M96) cards in PIM0 of LN0, IMG0 (HUB0 for CPU0 of all nodes, HUB1 for CPU1 of all nodes.)
Note 1
IMG0 (LN0)
Note
HUB0HUB1
From LN3
From LN2
From LN1
From ISW
HUB card can be mounted in any universal slot of PIM.
The connections , shown in this figure, are only an example. Actual cabl e running s may vary, depending o n your
system configuration. (Refer to the โIns tallation Manualโ for more details)
Note 2:
The mutual 10 BASE-T (Ethernet) connections must be within 328 feet (100m) in their distance. If the distance is
longer [e.g. , Fusion Link is provided also with other distant IPX node(s)], use FCH (P A-FCHA) card as a protocol
converter for the Fusion-link data. For more de tails, refer to the โFusion Network System Manual.
LN3
CPU1
L1
Note 2
L1
CPU1
LN1
: 10 BASE-T connector
Figure 2-5 Details on Ethernet Cab le Connections (Establishment of Fusion Link) (1/2)
CHAPTER 2NDA-24307
Page 8
Issue 1
Page 37
SYSTEM MAINTENANCE OUTLINE
[ Details on Ether Cable Connections: When Dual LANIs are used for each CPU ]
When dual LANIs are used for each CPU, the whole second LANIs (external LANI: PCI slot 03) must also be
connected in addition to the first LANIs explained on the previous page. This figure shows an example where the
second LANIs are connected to the additional HUB2/HUB3 (PA-M96) cards in PIM0 of LN2, IMG0 (HUB2 for
CPU0 of all nodes, HUB3 for CPU1 of all nodes).
The above connections ar e only an e xample. Actual cable runnings may va ry , depending on your system
10 BASE-T Cables (Straight)
LI LI
CPU0
LN3
: 10 BASE-T connector
configuration (Refer to the โInstallation Manualโ for more details.)
Note 2:
The mutual 10 BASE-T (Ethernet) connections must be within 328 ft (100m) in their distance. If disยญtance is longer (e.g., Fus ion link is provided with other distant IPX node(s), use FCH (PA-FCHA) card
as a pr otoco l converter for the Fusion link data. For more detai ls, refer to the โFusion Network System
Manual.โ
Figure 2-5 Details on Ethernet Cable Connections (Establishment of Fusion Link) (2/2)
NDA-24307CHAPTER 2
Page 9
Issue 1
Page 38
SYSTEM MAINTENANCE OUTLINE
[ Details on Ether Cable Connections: When using MAT via Ethernet ]
The IPX-U system can use both IOC (PH-IO24) card or each CPR-accommodated LANI (PZ-PC19) card as
an interface for the connection to a MAT. This figure shows an example where a MAT is connected via the
LANI card in PCI slot 01 of each LN/ISW.
Fusion Link
Ether for MAT
This figure is an example where a MAT is connected to LN1 via the 10 BASE-T ca bles
(Ethernet). As seen from this, the MAT, a single terminal connected to the Ether, can control
the whole system status , thus capable of a single-point entry to each LN and ISW.
ISW
LN0LN1LN2LN3
MAT
IMG0 (LN 1)
HUB
Note 1
HUB
Note 1
PIM0
LN1
IMG0 IMG1 IMG2 IMG3
Note 2
Note 1:
Note 2:
To LANI0 of LN3
To LANI0 of LN2
To LANI0 of LN0
To LANI0 of ISW
10 BASE-T Cable
(Straight)
MAT
When connecting the MAT by this way, be s ure to use dedicated HUB (PA-M96) car d( s).
Because ISW has no universal slot for external HUB cards, connect the 10 BASE -T caยญbles (from the ISW) to a MAT-dedicated HUB in any of the LNs (LN0 - LN3). In this ex-
10 BASE-T Cable
(Cross)
CPU1
00
CPU0
010100
LANI
ample, the cables are ISW) to a MAT-dedicated HUB in any of the LNs (LN0 - LN3). In
this example, the cables are connected to HUB in LN1.
Note:
CHAPTER 2NDA-24307
Page 10
Issue 1
The LANI card for MAT connection is mounted in PCI slot No. 01 of each CPR.
Figure 2-6 Details on Ethernet Cable Connections (Using MAT via Ethernet)
LPM
To LANI1 of LN3
To LANI1 of LN2
To LANI1 of LN0
To LANI1 of ISW
10 BASE-T Cable
(Straight)
Note 2
ISW
: Inter-node Switch
LN
: Local Node
LANI
: LANI (PZ-PC19)
HUB
: PA-M96
: 10 BASE-T connector
Page 39
TOPU
SYSTEM MAINTENANCE OUTLINE
ISW
Note:
13 14
IOGT1 (PH-GT10)
PLO1
(PH-CK16-A/17-A)
ISWM
LPM
BASEU
00 01 02 03 04 05 06 07 0810 1116 17 18 1915
PWR0 (PH-PW14)
HSW00 (PU-SW01)
PWR1 (PH-PW14)
TSW00 (PU-SW00)
HSW01 (PU-SW01)
TSW01 (PU-SW00)
TSW02 (PU-SW00)
0912
TSW03 (PU-SW00)
IOGT0 (PH-GT10)
PLO0
(PH-CK16-A/17-A)
(RES)
03 04
01 02
00
MMC (PH-M22)
IOC (PH-IO24)
EMA (PH-PC40)
Note
FDD/HDDPWRDSP
The 2nd IOC card (optional) may be mounted in this slot.
The Line Equipment Numbers (LENS) are used to specify the location of a circuit (trunk/port) in any of
the PIM universal slots. Refer to the figures in this section, and confirm the LENS format used in the
system.
As shown in Figure 2-12, the LENs consists of six digits: two digits for MG, one digit for U, two digits
for G, and one digit for Lv.
LENS = XX X XX X
Lv (Level) : 0 - 7
Note:
In addition to Group No. 00-23, 24-31 can be used as the extended group numbers.
2.2.1Module Group
Figure 2-13 explains the Module Group (MG). In a fully expanded system, the MG number ranges
from 00 to 07 in each local node.
IMG0
TOPU
PIM3
MG01
PIM2
G (Group) : 00 - 23
U (Unit) : 0 - 3
MG (Module Group) : 00 - 07
Figure 2-12 LENS Format
LN0/1/2/3
IMG1
TOPU
MG03
MG05
IMG2
TOPU
Note
IMG3
TOPU
MG07
FANU
PIM1
MG00
PIM0
LPM
BASEU
FANU
MG02
TSWM0
BASEU
FRONT VIEW
Figure 2-13 Module Group Allocations (LN0/1/2/3)
CHAPTER 2NDA-24307
Page 16
Issue 1
FANU
MG04
TSWM1
BASEU
FANU
MG06
DUMMY
BASEU
Page 45
SYSTEM MAINTENANCE OUTLINE
2.2.2Unit
Details on Unit (U) numbe rs are shown in Figure 2-14. The numbers range from 0 to 3, and each uni t
represents the PIM universal slots, No. 04-12 (U 0/2) or No. 15-23 (U 1/3).
On each Module Group (MG: #00 - 07), a total of four Units (U0 - U3) can be assigned.
The Group (G) numbers are all ocated as shown in Figure 2-15. A tot al o f t wo Groups are assigned on
each universal slots within the PIM. Slot numbers 10, 11, 12, 21, 22, 23 can contain a total of four
Groups as an exception.
A total of two or four Groups (G) can be assig ned on eac h PIM uni ve rsal s lot.
In addition to Group No. 00 - 23, the system can use No. 24 - 31 as theoretically valid numbers.
Refer to the Fusion Network System Manual for information on Extended Group No. 26 - 31.
Figure 2-15 Group Number Allocations (LN0/1/2/3)
CHAPTER 2NDA-24307
Page 18
Issue 1
Page 47
2.2.4Level
Figure 2-16 explains the Level (Lv) numbers. There are a total of eight Levels (Lv0 - Lv7) on every
Group number, which ranges from 00 to 31.
A total of eight Levels (Lv0 - Lv7) c an be ass i gned on each Group.
LN0/1/2/3
IMG0
TOPU
PIM3
PIM2
PIM1
PIM0
U2
MG01
U0
U2
MG00
U0
BASEU
FANU
LPM
Group
(G = Odd No., < 11)
Group
(G = Even No., < 10)
U3
U1
U3
U1
Group No.
Level (Lv)
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IMG1
TOPU
U2
U0
U2
U0
MG03
FANU
MG02
TSWM0
BASEU
U3
U1
U3
U1
FRONT VIEW
00 02 04 05 06 07 08 09 10 11 12 13 14
0100030205040706090811
(24) (25)
2726292831
IMG2
TOPU
U2
MG05
U0
FANU
U2
MG04
U0
DUMMY
BASEU
U = 0 / 2
10
30
IMG3
TOPU
U3
U1
U3
U1
15
19
23
14
18
22
13
17
21
12
16
20
16-port Slot
U2
U0
U2
U0
U = 1 / 3
15 16 17 18 19 20 21 22 23
0100030205040706090811
2726292831
MG07
FANU
MG06
DUMMY
BASEU
15
14
13
10
12
30
U3
U1
U3
U1
19
18
17
16
32-port Slot
SYSTEM MAINTENANCE OUTLINE
23
22
PIM
21
20
Level (Lv)
7
6
5
4
3
Group
(G = 15/19/23)
2
1
0
7
6
5
4
3
Group
(G = 14/18/22)
2
1
0
7
6
5
4
3
Group
(G = 13/17/21)
2
1
0
7
6
5
4
3
Group
(G = 12/16/20)
2
1
0
Figure 2-16 Level Number Alloc ations (LN0/1/2/3)
NDA-24307CHAPTER 2
Page 19
Issue 1
Page 48
SYSTEM MAINTENANCE OUTLINE
2.3 Local Partition (LP) Number
The Local Partition (LP) number refers to a logical local processor number, theoretically assigned for each
IMG that consists of four (or less) Port Interface Modules (PIM). Though the local processor does not
actually e xist in any of the IM Gs, ex cept for IMG0, the system can apply the tw o-digit LP number to each
IMG (see Figure 2-17) on i ts data memory program. The LP numbers are used primaril y i n the followi ng
cases:
โขDisplay of system messages
โขAssignment of line load control data (ALLC command)
โขBackup for Call Forwarding/Speed Calling data (MEM_HDD command), etc.
The Local Partition No. (two digits, even number) is assigned on each IMG.
IMG0
TOPU
PIM3
IMG1
TOPU
PIM3
LN0/1/2/3
IMG2
TOPU
PIM3
IMG3
TOPU
PIM3
PIM2
FANU
PIM1
PIM0
LPM
BASEU
LP No. = 00LP No. = 02LP No. = 04LP No. = 06
PIM2
FANU
PIM1
PIM0
TSWM0
BASEU
FRONT VIEW
PIM2
FANU
PIM1
PIM0
TSWM1
BASEU
PIM2
FANU
PIM1
PIM0
DUMMY
BASEU
Figure 2-17 LP Number Allocations (LN0/1/2/3)
CHAPTER 2NDA-24307
Page 20
Issue 1
Page 49
SYSTEM MAINTENANCE OUTLINE
2.4 Assignment of Network Control Node (NCN)
The IPX-U system can be in service by dialing a T elephone Number assigned for each station at a Network
Control Node (NCN). Because these network-level data (NDM data) can be assigned via the MAT
dedicated to the NCN only, designate any of the following nodes as this network data manager (NCN):
โขOne of the Local Nodes (LN), excepting for the ISW, within the IPX-U system
โขOne of the belonging Fusion nodes outsi de the IPX-U system
For more det ails, refer to Figure 2-18.
Note 1:
W ithin the IPX-U sys tem, the NCN can be designat ed only fr om the Loca l Nodes (LN0-LN3). The ISW
cannot be assigned as the NCN.
Note 2:
On a Fusion network, assign only one NCN. Multiple nodes cannot be assigned as the NCN.
Because the Fusion link can be es tablished e ither independe ntly within the syste m (IPX-U) or jo intly with
other outside IPX series, the assignment of NCN can differ, depending on the network configuration.
NDA-24307CHAPTER 2
Page 21
Issue 1
Page 50
SYSTEM MAINTENANCE OUTLINE
Pattern 1 When the system has a Fusion link independently of other systems
If the system has a Fusion li nk only within the system (i.e. no Fusi on link is esta blished with ot her IPX
series), an NCN must be assigned from any of the existing Local Nodes, excepting the ISW. In this
example, LN0 is assigned as the NCN.
Ne twor k Data Me mor y
-Sy s te m Data
AS Y DN, AFMU, ALRTN ....
-Number Planning Data
ANPDN, ASPAN....
-Station Num b ering
ALGN N , ALG SN....
......
Station A
TELN: 41000
No te 1
DM
LDM
NDM
Assignment of NDM Data
via Cen tr a lized MA T
Station C
TELN: 43002
NDM
(FP C =1 6)
......
......
......
......
......
......
......
......
(FP C =1 8)
LN2
......
......
......
......
LN0
......
......
......
......
......
......
......
......
......
......
N
D
M
D
a
Network Control Node
t
a
C
o
p
y
(FPC = 1 7)
LN1
......
......
......
......
......
......
......
......
Station B
TELN: 420 05
No te 2
(FPC=15)
IS W
......
......
......
......
NDM
(FPC = 1 9)
LN3
......
......
......
......
......
......
NDM
NDM
......
......
Station D
TELN: 450 07
IS W : In te r-n o d e S w itc h
LN : L o c a l Node
NCN: Network Control Node
Note 1:
The network-lev el data (NDM data) can be assig ned only at th e NCN. Howeve r, other node-level
D M : D ata Memo ry
LDM: Local Data M e mory
NDM: Network Data Memory
data (LDM data) must also be assigned at each node (including ISW), depending on the
requirements. For more details, refer to the โInstallation Manual (IPX-U Type)โ or the โFusion
Network System Manual.โ
Note 2:
When the system is oper ated, th e funct ion to be performed by t he ISW is only t o provide the PCM
time slot switching between the Local Nodes. However, an FPC (Fusion Point Code) must be asยญsigned also for the ISW together with other Local nodes, by using the ASYDL command.
Figure 2-18 Example of NCN Assignment (1/3)
CHAPTER 2NDA-24307
Page 22
Issue 1
< IPX-U >
FPC : F u s io n Po int C od e
TELN: Telephone Number
MAT : Maintenance Ad mini strati on T erm i n al
Page 51
SYSTEM MAINTENANCE OUTLINE
Pattern 2 When the system has a Fusion link with other IPX series and an NCN exists within the system
If the system has a Fusion link also with other IPX series (i.e. the Fusion nodes exist also outside the
system), an NCN can be assigned from either Local Nodes outside the system or the Local Nodes
inside the system. In this e xample, LN0 of the IPX-U system is designated as the NCN.
Network Data Memory
-System Data
ASYDN, AFMU, ALR TN ....
-Number Planning Data
ANPDN, ASPAN....
-Station Numbering
ALGNN, ALGSN....
......
Station A
TELN: 41000
NDM
Assignment of ND M Data
via C en tra lized M A T
Station C
TELN: 43002
Fusion Link
(FPC = 1 6 )
LN0
......
......
......
......
......
......
......
......
......
......
......
......
Note 1
DM
LDM
N
(FPC=18)
LN2
................................................
NDM
IPX-U
System
Sta tio n E
TELN: 47001
Network Contro l Node
......
......
......
......
D
M
D
a
t
a
C
o
p
y
Note 2
(FPC = 1 5 )
ISW
......
......
Sta tio n G
TELN: 49012
(FPC = 1 )
LN-A
................................................
NDM
NDM
(FPC=3)
LN-C
NDM
(FPC = 1 7 )
LN1
......
......
......
......
......
......
......
......
(FPC=19)
LN3
......
......
......
......
........................
(FPC = 2 )
............
......
......
LN-B
Station B
TELN: 42005
NDM
......
......
Station D
TELN: 45007
NDM
Station F
TELN: 48003
NDM
Note 1:
Note 2:
IS W : I n t e r -no de Switc h
LN : Local No de
NCN : Network Control Node
D M : D ata M e mory
LDM: L oc al Da ta Me mory
NDM: Network Data Memory
FPC : Fusion Point Code
TELN: Tel ephone Number
MAT : Maintenance Administration T erminal
The network-level data (NDM data) can be assigned only at the NCN. However, other nodeยญlevel data (LDM data) must also be assigned at each node (including ISW), depending on the
requirements. For more details, refer to the โInstallation Manual (IPX-U Type)โ or the
โFusion Network System Manual.โ
When the system is operated, the function to be performed by the ISW is only to provide PCM
time slo t switching b etween the Local Nodes. However, an FPC (Fusion Point Code) mus t be
assigned also for the ISW together with other Local nodes, by using the ASYDL command.
Figure 2-18 Example of NCN Assignment (2/3)
NDA-24307CHAPTER 2
Page 23
Issue 1
Page 52
SYSTEM MAINTENANCE OUTLINE
Pattern 3 When the system has a Fusion link with other IPX series and an NCN exists outside the system
If the system has a Fusion link also with other IPX series (i.e. the Fusion nodes exist also outside the
system), an NCN can be assigned from either Local Nodes outside the system or the Local Nodes
inside the system. In this example, LN-A (NEAX2400IPX series, 4-IMG type) outside the system is
designated as the NCN.
(FPC = 1)
LN-A
......
......
......
Network Data Memory
-System Data
ASYDN, AFMU, ALRTN....
-Number Planning Data
ANPDN, ASPAN....
-Station Numbering
ALGNN, ALGSN....
......
Station E
TELN: 47001
Note 1
DM
LDM
NDM
Assignment of NDM D ata
via Centralized MAT
......
......
......
......
......
......
......
......
......
......
......
......
......
Network Control N ode
NDM Data Copy
(FP C=2 )
LN-B
Statio n F
................................................
TELN: 48003
............
Note 1:
(FPC= 3)
LN-C
......
......
......
Station G
TELN: 49012
LN1
................................................
LN3
................................................
......
NDM
Station B
TELN: 42005
NDM
Station D
NDM
TELN: 45007
Fusion Link
ISW : Inter-node Switch
LN : Lo ca l N o de
NCN: Network Control Node
(FPC=16)
Station A
TELN: 41000
TELN: 43002
Station C
LN0
NDM
(FPC=18)
LN2
......
......
......
......
NDM
DM : D ata M e mory
LDM: Local Data Me m ory
NDM: Network Data Memory
IPX- U
System
................................................
......
......
......
......
NDM
(FPC=17)
No te 2
(FPC=15)
ISW
............
(FPC=19)
NDM
FPC : Fusion Point C ode
TELN: Telephone Number
MAT : M aintenance Administration Terminal
The network-level data (NDM data) can be assigned only at the NCN. However, other node-level
data (LDM data) must also be assigned at each node (including ISW), depending on the
requirements. For more details, refer to the โInstallation Manual (IPX-U Type)โ or the โFusion
Network System Manual.โ
Note 2:
When the system is operated, the function to be performed by the ISW is on ly to pro vi de the PCM
time slot switching between the Local Nodes. However, a FPC (Fusion Point Code) must be
assigned also for the ISW together with other Local nod e s , by u s i ng the ASYDL command.
Figure 2-18 Example of NCN Assignment (3/3)
CHAPTER 2NDA-24307
Page 24
Issue 1
Page 53
SYSTEM MAINTENANCE OUTLINE
2.5 System Messages
System messages display during routine diagnosis, system operation status controlling, and fault
occurrence. Figure 2- 19 shows an example of a system message.
Refer to Chapter 3 for details on each message.
(1) SYSTEM MESSAGE 3-E SUP LOCK UP FAILURE (TEMPORARY)
(2)NEC TOKYO
(1) : SYSTEM MESSAGE 3-E SUP LOCK-UP FAILURE (TEMPORARY)
Meaning of the message
System Message Level
(Indicated by Alarm Lamp)
System Message Number
(2) : Office Name, Date and Time
(3) : LP00-0-ACT
ACT/STBY indication for dual systems
Note 2
No.0/No.1 system indication for dual systems
Faulty processor/Related processor
(4) : Message detail data (notation by hexadecimal numbers)
Note 1:
The data here indicates the Office Name, uniquely assigned to each node and ISW. This
can be set by using the ASYD (SYS1, Index 96-115) or AOFC command.
Note 2:
There are four kinds of al a rm informati on to be indica ted by alarm lamps: MN, MJ, SUP,
and NON indications.
Figure 2-19 System Message Example
NDA-24307CHAPTER 2
Page 25
Issue 1
Page 54
SYSTEM MAINTENANCE OUTLINE
2.6 Fault Detecting Function
The system fin ds a f ault b y its f aul t dete cting c ircui t and th e f aul t detec ting progr am. Once a fa ult occ urs,
the system initiates a remedial action such as system changeover, make-busy setting, or restart processing
by the automatic di agnosis func tion. This ac tion reduces the influe nce of the f ault so t hat system ser vicing
may be minimized. The result of the process ta ken and the fault situat ion are indica ted for equipmen t conยญcerned.
Among the faults, those related to speech path (noise , one-way speech, sp eech inability, etc.) are not
detectable. Since t hese f ault r eports a re to be obtaine d from a s tation o r operator, periodic trunk tests mus t
be performed without failure to detect the faults related to speech path.
Figure 2-20 and Figure 2-21 shows an outline of fault detection, and Figure 2-23 shows a block diagram
of fault detect ion.
CHAPTER 2NDA-24307
Page 26
Issue 1
Page 55
SYSTEM MAINTENANCE OUTLINE
LN0
LN1
ISW
Indication
of Audible
and Visual Alarm
Indicating Panel
Indication of Fault OccurrenceInformation Collection
MMC
......
Indication of
Alarm Lamps
on TOPU
MMC
Indication of
Alarm Lamps
on TOPU
NEC
MJ
OFF
ON
BELL
MMC
......
......
......
and Diagnosis
CPU
EMA
CPU
EMA
CPU
Example of Faults
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Indication of
Alarm Lamps
on TOPU
......
......
EMA
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
LN2
MMC
Indication of
Alarm Lamps
on TOPU
CPU
......
......
EMA
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
LN3
MMC
CPU
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
Indication of
Alarm Lamps
on TOPU
......
EMA
power supply failure,
fuse blowing, etc., within
......
the equipment frame
Note: Alarm Indicating Panel indicates the fault information on both ISW and other Local Nodes (fault notification on a system
basis). Meanwhile, alarm lamps on the TOPU for ISW and Local Nodes (indicated in dotted lines above) provide the fault
indication only related to the belonging node. For more details, refer to CHAPTER 6.
Figure 2-20 Fault Detection General Diagram (via Alarm Lamps on TOPU)
NDA-24307CHAPTER 2
Page 27
Issue 1
Page 56
SYSTEM MAINTENANCE OUTLINE
LN0
LN1
Display of
System Messages
ISW
Indication of Fault OccurrenceInformation Collection
...-:;..+..*
...-:;..+..*
...-:;..+..*
...-:;..+..*
Display of
System Messages
LANI
and Diagnosis
IOC
CPU
MMC
EMA
...-:;..+..*
...-:;..+..*
...-:;..+..*
...-:;..+..*
Display of
System Messages
LANI
...-:;..+..*
...-:;..+..*
...-:;..+..*
...-:;..+..*
MMC
IOC
CPU
EMA
...-:;..+..*
...-:;..+..*
...-:;..+..*
...-:;..+..*
IOC
CPU
LANI
Display of
System Messages
Example of Faults
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
Fault of line/trunk card
TSW write failure,
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
LN2
Ether
LANI
MMC
MMC
...-:;..+..*
...-:;..+..*
Display of
System Messages
EMA
...-:;..+..*
...-:;..+..*
IOC
CPU
EMA
the equipment frame
...-:;..+..*
...-:;..+..*
...-:;..+..*
Display of
System Messages
...-:;..+..*
IOC
Fault of line/trunk card
LN3
TSW write failure,
LANI
MMC
CPU
EMA
Fault of clocks, etc.
Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame
Note: In addition to the connection to a port of IOC (PH-IO24) circuit card, a MAT can be connected also to the
Ethernet via LAN Interfaces (PZ-PC19: PCI Slot 01 of each CPR).
Figure 2-21 Fault Detection Block Diagram (via Display of System Messages)
CHAPTER 2NDA-24307
Page 28
Issue 1
Page 57
SYSTEM MAINTENANCE OUTLINE
< LN >
Firmware
Fault
RDY
Clock
etc.
To M AT,
Printer, etc.
LANI
- Symbols -
: Circuit Card
: Main faults to be detected
: Speech path
: Flow of fault information
CPU
:Central Processing Unit
EMA
:Emergency Alarm Controller
MMC
:Man Machine Controller
TSW
:Time Division Switch
INT
:Speech Path Control Interface
MUX
:Multiplexer
HSW
:Highway Switch
DLKC
:Data Link Controller
PWR
:Power Supply
LANI
:Local Area Network Interface
IOC
:I/O Controller
GT
:Gate
IOGT
:Input/Output Gate
LC/TRK
:Line/Trunk
MAT
:Maintenance Administration Terminal
LN
:Local Node
TSWM
:Time Division Switch Module
ISW
:Inter-node Switch
ISWM
:Inter-node Switch Module
RDY
Clock
Write
etc.
IOC
MMC
MUX
RDY
Clock
Write
etc.
C-level
monitor
LC/TRK
TSW/
INT
RDY
Clock
Write
etc.
CPU
Fault
Information
Note
To TSW
of ISWM
TSW/
INT
DLKC
TSWM0
C-level
monitor
From
other existing
Local Nodes
Howler
Ringing
Circuit
EMA
Alarm Lamps on the TOPU
Thermal Reed Relay
LC/TRK
MUX
RDY
TSW/
Clock
INT
Write
etc.
RDY
Clock
Write
etc.
GTGT
PWR
PWR Supply
Failure,
Fuse Blown
To TSW
of ISWM
TSW/
INT
TSWM1
MMC
To MAT
on the Ethernet
To M AT,
Printer, etc.
< LN >
To M AT,
Printer, etc.
LANI
From
other
nodes
LANI
Firmware
Fault
RDY
Clock
etc.
IOC
RDY
Clock
Write
etc.
RDY
Clock
Write
etc.
GT
C-level
monitor
IOC
MMC
CPU
Fault
Information
Note
LC/TRK
MUX
TSW/
INT
RDY
Clock
Write
etc.
CPU
Fault
Information
Note
Note:
C-level
monitor
Alarm Lamps on the TOPU
Thermal Reed Relay
LC/TRK
DLKC
TSWM0
C-level
monitor
To TSW
of ISWM
TSW/
INT
Howler
Ringing
Circuit
EMA
RDY
Clock
Write
etc.
GT
PWR Supply
Failure,
Fuse Blown
PWR
MUX
RDY
Clock
Write
etc.
TSW/
INT
To TSW
of ISWM
TSWM1
MJ, MN fault
Power, Fuse blown fault
Temperature, CPU fault
Speech Path System fault (SPE)
RGU, Howler fault
PFT fault
CPU Clock fault
Alarm Lamps on the TOPU
Thermal Reed Relay
To/From TSW
of each LN
RDY
TSW/
Clock
INT
Write
Howler
Ringing
Circuit
EMA
etc.
IOGT
PWR
PWR Supply
Failure,
Fuse Blown
RDY
Clock
Write
etc.
HSW
ISWM
< ISW >
TSW/
INT
Figure 2-22 Fault Detection Block Diagram
NDA-24307CHAPTER 2
Page 29
Issue 1
Page 58
SYSTEM MAINTENANCE OUTLINE
(a) Main Faults
Faults that may o ccur in the syst em can be general ly categor ized into Processo r System F ault, Speech
Path System Fault, Line/Trunk Fault, etc.
โขProces sor System Fault
The CPU alarm detecting circuit contin uously monitors whether the CPU is working normally. If
a fault is detected, the CPU calls up the diagnostic program, which identifies the cause of the fault
and determines whether the fault is temporary or permanent. When the fault affects system
operations, Active/Standby status of the CPU is changed over (provided that the system has dual
configuration).
โขBus System Fault
The CPU transfers line/trunk card control information to the associated peripheral circuits via IO
Bus. When a parity error is detected in the transfer data or when the required information cannot
be transferred from a circuit card, the CPU identifies the cause of the fault, changes over the CPU
so that system operation is not affected, and executes restart processing.
โขSpeech Path Fault
The CPU monitors the operating status of the TSW card, the occurrence of errors in writing data
to the switch memory, and the basic clocks s upplied t o the spee ch path. Upon detecti ng a fau lt, the
CPU identifies the cause of the fault, determines whether the fault is temporary or permanent, and
executes required processing such as changeover of the TSW card.
โขOthers
The alarm detecting circui t on the EMA card con tinuousl y monitors the occ urrence of fa ults in the
PWR supply cards, such as abnormal temperatures within the equipment frame, and lights the
alarm lamp on the TOPU when a fault is detected.
(b) Lamp Indications on the TOPU
When a fault occurs, the corr esponding lamp on the T OPU indicate s the locati on of the f ault. F or the
meaning of each lamp indication, refer to Chapter 6.
CHAPTER 2NDA-24307
Page 30
Issue 1
Page 59
SYSTEM MAINTENANCE OUTLINE
2.7 Range of Faults Specification
(1) Upon receiving a fault report from a station user or an operator, the technician can assume a faulty card
exists if the range to be affected by the fault can be determined. For the de tailed procedure, re fer to
Chapter 5. Use the following actions to check the MDF:
(a) Check the LENS of the reporter (Station or ATTCON/DESKCON).
(b) Check other circuits of the circuit card in which the reporter (station line or ATTCON/DESKCON)
is located.
(c) Check the other groups (ot her ci rcuit car ds mounte d in t he sa me modul e) i n the module i n wh ich th e
reporter is located.
(d) Check lines in each of the other modules on the basis of plural lines.
(2) If the fault cannot be detecte d by the system (a f ault related to the speech path such a s noise during speec h,
one-way speech, speech inability), the range of (a) through (d) (itemized above) should be limited.
(3) When a major faul t is det e cted i n the du al sys te ms , the C PU or TS W sy st em auto m ati c al ly ch ang es over
if the fault ra nge is (c) an d (d). In th is case, the w hole modul e involved is placed into m ake-busy sta tus
even if the fault is partial, and the station lines currently operating normally become faulty status.
Diagnose the fault from the content of the system message displayed and repair the fault as required.
(4) When limiting the range of faults, consider the system circuitry that consists of the control (see Figure 2 -
24 and Figure 2-25, where CPU 0 is active) and speech path systems (see Figure 2-26).
(5) As seen from the block diagrams in Figure 2-24 through Figure 2-27, if a fault occurs within the common
portions to be controlled, all other associated portions are affected by that fault occurrence. If the range
of faults is outside PIM fault, CPU/TSW system changeover is executed (only when the fault is detectable
by the system).
NDA-24307CHAPTER 2
Page 31
Issue 1
Page 60
SYSTEM MAINTENANCE OUTLINE
:
:
Note 1
HSW00, 01 for No. 0 System /
HSW10, 11 for No. 1 System
The two HSW cards here provide the space division switching for a maximum of 16 PCM
highways fr om/to the TSW (PU-SW00) car ds in ISWM. For more deta ils, refer to NEAX240 0 IPX
IPX-U โCir cuit Card Manualโ.
Note 2:
Note 3:
See details in Figure 2-26, Speech Path Block Diagram.
Multiple connection is pr o vided on t he back boar d side bet ween the PLOs h er e. For more details,
refer to the โCircuit Card Manualโ.
Figure 2-24 CPU Controlling Block Diagram (ISW)
CHAPTER 2NDA-24307
Page 34
Issue 1
Page 63
SYSTEM MAINTENANCE OUTLINE
This figure shows a block diagram of the CPU controlling block in LN0, where CPU 0 is active.
See details in F igure 2-26 , Speech Path Block Diagram.
Multiple connection is provided on the backboard side between the PLOs here. For more
details, refer to th e โCircuit Card Manual.โ
Figure 2-25 CPU Controlling Block Diagram (LN)
NDA-24307CHAPTER 2
Page 35
Issue 1
Page 64
SYSTEM MAINTENANCE OUTLINE
This figure shows a block diagram of speech path.
IMG0 of LN1
MUXMUX
LC/TRK
PIM3
MUXMUX
LC/TRK
PIM2
- Symbols ยญ: Speech Path
: Cable
: Circuit card (ACT)
: Circuit card (ST-BY)
TSW (in ISWM) : PU-SW00
HSW: PU-SW01
TSW (in TSWM0/1) : PH-SW12
MUX: PH-PC36
A fault within this range
affects the circuit card.
LC/TRK
LC/TRK
A fault within this range
affects the circuit card.
LC/TRK
LC/TRK
32ch
32ch
32ch
MUX
A fault within this range
affects two slots.
MUX
A fault within this range
affects two slots.
MUX
A fault within this range
affects this module.
512ch
A fault within this range
affects this module.
512ch
A fault within this range
affects this module.
512ch
PIM 3
Symbols
A fault within this range
affects the circuit card.
A fault within this range
affects two slots.
LC/TRK
LC/TRK
A fault within this range
affects the circuit card.
TSW
: Circuit Card: Possible fault range to be affected: Speech Path
32ch
MUX
TSW/INT
A fault within this range
affects this module.
512ch
Figure 2-27 Speech Path Range of Fault
CHAPTER 2NDA-24307
Page 38
Issue 1
Page 67
2.8 Explanation of Terms
โขC-Level Infinite Lo op
The program repeatedly e xecutes speci fic routines due to a fault of the main memory , data des truction,
etc. The program is not a ble to b e proces se d normall y. This faulty conditi on is re ferr ed to as Program
Infinite Loop. C-Level infinite loop is a state where a clock-level program, which runs under clock
interrupt disable state, is in an infi nite loop status.
โขB-Level Infinite Lo op
This is a state where a program infinite loop has occurred during a connection processing and the
connection for the ne xt call is not able to be processed.
โขPM (Port Microprocessor)
Each line/trunk card mounted in the PIM is equipped with a processor called Port Microprocessor
(PM), which continuously supervi se s the lines /t runks.
โขReady Error
For acknowledging the connection between the CPU and a circuit card, an interface signal called
Ready Signal is used. When the CPU has accessed a specific circuit card and the normality of the
connection is ac kno wledged, the Ready S ignal is returne d to th e CPU within 6 ยตs. If t he Ready si gnal
is not returne d to the CPU withi n 6 ยตs after access, the situation is referred to as Ready Error.
SYSTEM MAINTENANCE OUTLINE
โขParity Error
For confirming the normality of data transfer be twee n the CPU and the circuit card un der the control
of the CPU, parity check is made. When an error is detected in a parity check, it is referred to as Parity
Error. Parity check means to confirm the normality of data by adding an error detecting parity bit to
a set of data to be transferred.
When a set of data is transferred , a parity bit is added to the data so that the data has an even-number
of โ1โ bits (it is referred to as Even Parity). When there is an odd-number of โ1โ bits in the received
one set of data, it is detected as an error.
โขMonitor Restart
Monitor restart processing suspends current processings in progress without applying any hardware
controlling, allowing the system to restart its operations from the monitor program.
The system abandons only the processings of the calls being handled by the program, and maintains
all the connections that have already been established.
โขCircuit Card Front Initializing Restart
The whole system is forcibly initialized. However, the initialization varies with the setting of the
SENSE switch on the DSP of CPU (see Table 2-2).
NDA-24307CHAPTER 2
Page 39
Issue 1
Page 68
SYSTEM MAINTENANCE OUTLINE
Table 2-2 Kinds of Circuit Card Front Restart
SENSE (0~F)KIND OF RESTARTREMARKS
1DM Clear Restart
2DM Load RestartWhen the system is in operation
5OAI Memory Clear Restart
COFF-line Restart
โขPM (Line/Trunk Card) Make-Busy Restart
In this processing, the fault y PM (Line/Trunk Card) is isolated from the system and, at the same time,
the calls associated with that faulty PM (Line/Trunk Card) are released. No calls related to the faulty
PM (Line/T runk Card) are processed and t he system normal ly runs without the faulty PM (Line/T runk
Card).
โขData Copy Restart
In a system of dual CPU conf iguration, t he RAM memory (including th e data memory) is copi ed from
the ACT side CPU into the STBY side CPU, and ACT/STBY is changed over and monitor restart is
executed.
In the case of this restart processing, only the ACT side CPU and the STBY side CPU are changed
over without any effect on the current connections. However, no call processings are executed while
the restart processing is in progress (from copying until the end of the changeover).
CHAPTER 2NDA-24307
Page 40
Issue 1
Page 69
SYSTEM MAINTENANCE OUTLINE
3. HOW TO READ PRECAUTIONS, DIAGNOSTIC, AND FAULT REPAIR INFORMATION
3.1 Precaution about Diagnostic Procedure/Fault Repair Procedure
When perform ing diagnostic p rocedures/fault repair procedures, be aware of the fo llowing ac t ions:
(1) When replac ing a circuit card with a spare, h andle the circuit card using the Fiel d Service Kit.
(a) T o protect the circuit card from static electricity, wear a wrist strap before handling the ci rcuit card.
(b) Before extracting the circuit card from its mountin g slot, set its MB s w itch to the UP side (ON).
(2) When holding a circuit card by hand, wear glo v es and be car ef ul not to touch mounted part s, gold-
plated terminal, etc., on the circuit card.
๏
The 3M
Model 8012 Portable Field Service Kit, shown in Figure 2-28, is recommended as an effective
countermeasure against static electricity.
Note:
Connect ground wire to the Earth
terminal of the Module Group.
Place the Circuit
Card on a
conductive sheet.
Wrist Strap
3M๏ is a registered trademark of Minnesota Mining and Manufacturing, Inc.
Figure 2-28 3Mยฎ Model 8012 Portable Field Service Kit
NDA-24307CHAPTER 2
Page 41
Issue 1
Page 70
SYSTEM MAINTENANCE OUTLINE
Circuit Card
8
7
6
5
4
4
3
3
2
8
2
1
7
OFF
1
OFF
6
5
4
8
3
7
2
6
8
1
5
4
3
2
1
Plastic Bag
OFF
7
6
5
4
OFF
3
2
1
OFF
Gold Plated Terminal
7
4
2
3
8
4
1
2
6
3
1
5
OFF
OFF
4
2
3
7
8
5
6
1
OFF
4
2
7
3
8
5
6
1
OFF
4
2
7
3
8
5
6
1
OFF
Circuit Card
Note
4
3
2
1
OFF
Card Puller Tab
Note:
Do not touch the Gold Plated Terminal with bare hands.
Figure 2-29 How to Hold a Circuit Card
(3) When a circuit card appears to be faulty, check the following items before replacing it with a spare:
(a) Poor connector contact at the circuit card may be responsible for the fault. Repeat insertion and
extraction of the circuit card a few times. Clean the connector portion, and recheck for proper
operation.
(b) Check the le ad w i re s of vert ic al ly- m oun t ed par ts ( re sis to rs , ca pa ci tor s , e tc .) to ens ure th ey have not
shorted each other or b roken.
(c) Check the back side of the circuit card to see if there is any short-circuited soldered portion, or
modified cross connection wires erroneously left unconnected.
(d) Check the ROMs to ensure proper seating in the IC socket. Figure 2-30 s hows a leg th at is be nt a nd
not set in the socket.
A pin is bent, not
inserted in the socket.
ROM
SOCKET
Figure 2-30 How to Set the ROM in IC Socket
CHAPTER 2NDA-24307
Page 42
Issue 1
Page 71
SYSTEM MAINTENANCE OUTLINE
(4) How to clean the connector portion (gold-plated ter minal):
(a) Dip the gold-plated terminal po rtion in th e cleaning flui d for 3 to 5 seconds (only PA-XX type circuit
card), as sh own i n Figure 2-31.
Cleaning
Fluid
Circuit
Card
Figure 2-31 How to Clean the Connector Portion
Container
Note 1:
Some of the parts are subject to damage if they come in contact with the cleansing liquid. Be careful
to allow only the connector portion (gold-plated terminal) to contact the cleaning liquid.
Note 2:
Be sure to use fresh cleaning fluid (FREON or isopropyl alcohol).
(b) Using a soft cotton cloth, wipe both side s of the conne ctor port ion (gold- plated te rminal) cl ean (only
PA-XX type circuit card), as shown in Figure 2-32.
gauze
Gold-plated terminal
Figure 2-32 How to Clean Gold-Pl at ed Terminal
Note 1:
Note 2:
Use cloth (gauze, etc.) to clean.
After wiping, be careful not to leave lint on the surface of the circuit card.
(5) When a check on the flat cable or LT cable is directed in the tree, check the following items:
(a) Make a visual check to see if the connector is properly connected.
(b) Poor connector contact may be responsible for the f ault . Repeat connect ion and disc onnect ion a fe w
times, and check again to see if the connector is properly connected.
(c) Perform continuity test on the flat cable.
(6) When replacing the circuit card is directed in the tree, replace the circuit card with a spare as per Chapter 4.
(7) When multiple circuit cards appea r t o be f aulty, before replacing them with spares, remount th em (one a t
a time) into their slots , to determine which cards should be replaced.
NDA-24307CHAPTER 2
Page 43
Issue 1
Page 72
SYSTEM MAINTENANCE OUTLINE
The following is an example where the fault was recovered after the replacement of circuit cards:
START
Set the 1st circuit card back into its mounting slot
If the fault recurs: Replace the circuit card.
Set the 2nd circuit card back into its mounting slot
If the fault recurs: Replace the circuit card.
Set the 3rd circuit card back into its mounting slot
If the fault recurs: Replace the circuit card.
If a circuit card is found to be faulty, send the faulty circuit card for repair.
The fault may be a temporary one, or due to poor contact of the circuit card. Observe the
situation fo r a while.
END
(8) When a fault recovery is completed, use the RALM/RALMN command to clea r all the alarm indications
and registered system messages. If required, restore temporary cross connections and transient data for
testing to the original ones.
CHAPTER 2NDA-24307
Page 44
Issue 1
Page 73
SYSTEM MAINTENANCE OUTLINE
3.2 How to Follow Diagnostic Procedure/Fault Repair Procedure
(a) Diagnostic Work
A fault diagnostic proced ure by system messa ge is expl ained in the โTREEโ format o n an individual
system message basis.
โขProceed with judgment as to whether the fault status coincides with the indicated status, following
the sequence beginning from START.
โขHow to proceed with the diagnosis work is explained in Figure 2-33.
STEP 1Determine whether the fault coincides with the fault status (1) in Figure 2-33.
STEP 2If the fault status does coincide, t he fault is indica ted by (2) . Repair the fault by r eferri ng to the
relevant section in Chapter 5. Otherwise, proceed to (3).
STEP 3Perform the work indicated by (3). The result of the work (3) is broken down as indicated by
(4).
STEP 4Determine whether the result of work (3) coincides with the status indicated by (5). If so, the
fault(s) is/are indicated either by (6) or by (7). If not, proceed to the next Step.
STEP 5Perform the work indicated by (8), and if the result of the work is the same as the status
indicated, the fault is indicated by (9). If the fault repair work indicated by (9) affects another
normal line, recheck the work as indicated by (10).
(b) Fault Repair Procedure
A fault repair procedure is explained by means of โTREEโ format in Chapter 5. The following
explains how to follow the โTREEโ format and proceed with designated work. See Figure 2-34.
โขBegin from START and proceed with the necessary repair work following the sequence.
โขWhen a faulty circuit ca rd (or circuit cards) is suspect ed, replace the f aulty circu it card with a spar e
in accorda nc e with the work pr ocedure pertainin g to that specific circuit card.
STEP 1Replace the circuit card indicated by (A) with a spare and check it. Perform the detailed work
as per (B). If the fault status is beyond repair, proceed to the next step.
STEP 2If the range of the fault or the system configuration is as indicated by (C), perform a check as
indicated by (D). If the fault status is beyond repair, proceed to the next step.
STEP 3Replace the circuit card indicated by (E) with a spare and check it. The detailed procedure
indicated by (G) varies with the system configuration indicated by (F).
NDA-24307CHAPTER 2
Page 45
Issue 1
Page 74
SYSTEM MAINTENANCE OUTLINE
Note:
START
END
(4)
When
Perform
When
(1)
(3)
(5)
When
(5)
When
(8)
with
performed
(2)
FAULT
FAULT SUPERVISION
FAULT
FAULT
: It is the fault of
Section No.
(7)
: It is the fault of
Section No.
(9)
:
CHECK OF WORK
Section No.
(Chapter 5)
(11)
(6)
(Chapter 5)
(11)
(10)
(Chapter 5)
(11)
(1):Judgment of fault status
(2),(6),(7),(9): When the fault status coinci des with the indicati on, the cause of the fault is indicated .
(11):When repairing the fault, refer to the relevant section in Chapter 5.
(3):Operating items for diagnosis
(4):Branching of the result of the operation
(5):Judgment of the status of the result of the operation
(8):When operating method is unknown, refer to Chapter 6.
Figure 2-33 Diagnostic Work Items and Symbols Example
CHAPTER 2NDA-24307
Page 46
Issue 1
Page 75
SYSTEM MAINTENANCE OUTLINE
START
Check
When
Check
When
When
(A)
(C)
(E)
(F)
(B)
(D)
Check
(G)
(F)
(G)
END
Figure 2-34 Recovery Procedure Example
NDA-24307CHAPTER 2
Page 47
Issue 1
Page 76
SYSTEM MAINTENANCE OUTLINE
4. REPORTING FAULT TO NEC
When the cause of a fault is uncertain, make note of the situation involved and report it to NEC. When
forwarding faulty circuit cards to NEC, exercise caution to protect from static electricity.
4.1 Fault Reporting Method
The following three items must be included in the report without fail:
(1) Faulty situation (reports should be similar to โdial tone is not heard only on individual lines,โ โincoming
C.O. line calls are not able to be terminated only to a specific ATTCON/DESKCON,โ etc. )
โขFaulty phenomena
On lifting the handset, d ia l tone is not heard but side tone is heard, etc.
โขHistory of fault
When did the fault occu r? What kind of repair procedur e has been executed? Does the fault still exist
or not exist? etc.
โขRange of fault
Range of fault sh ould be report ed: Single li ne?, Specif ic trunk? , Specif ic circuit card?, Speci fic PIM?,
Whole system?, etc.
(2) Circuit Card Version Number, Program Name, and Program Package V ersion Number of the circuit card.
Figure 2-35 shows an example of PA-16LCBE circuit card.
CHAPTER 2NDA-24307
Page 48
Issue 1
Page 77
Circuit Card Name
Program Name
SYSTEM MAINTENANCE OUTLINE
PAยญ16LCBE
Circuit Card Version Number
SPAยญ16LCBE
SP 785
A 6A
Program Package
Version Number
Front
9A 91-03
TR 5448
Right View of Circuit Card
Figure 2-35 Circuit Card Version Number, Program Name, and Program Package Version Number
NDA-24307CHAPTER 2
Page 49
Issue 1
Page 78
SYSTEM MAINTENANCE OUTLINE
4.2 Forwarding Faulty Circuit Card Method
Send the faulty circuit card to the NEC agent to whom a request is made for a replacement card. Adhere
to the following procedure for sending the faulty circuit card:
(1) Insert connector covers onto the circuit card terminals.
(2) Put the circuit card into a static electricity protective bag.
(3) Pack the circuit card with air cap, etc.
(4) Set the circuit card into the cardboard box for that specific circuit card.
(5) If multiple circuit cards are to be sent, set each circuit card in a separate cardboard box and stuff the box
with shock absorbing material.
Note:
When sending a faulty circuit card, put it in a static guard bag. To prevent damage, NEVER place the
circ uit card in a vin yl bag or ship it without a protective bag .
CHAPTER 2NDA-24307
Page 50
Issue 1
Page 79
CHAPTER 3SYSTEM MESSAGES
This chapter explains how to read and ana lyze sy stem message s displayed du ring routine diag n osis, syst em opยญeration status controlling, and occurrence of a fault within the system. Table 3-1 provides a list of system mesยญsages.
1-JHSW Write Failure76
1-KBoth HSW CLK Failure77
1-LHSW CLK Failure79
1-OBoth PLO Failure81
1-PPLO Failure83
1-SModule Group Down Fai l ure85
1-TTSW ACT Change Report86
1-UDLKC Data Transfer Failure (Permanent)88
1-VDLKC Data Transfer Failure (Temporary)89
1-WPLO Restore90
1-XLN ร ISW CLK/FH Failure91
NDA-24307CHAPTER 3
Page 51
Issue 1
Page 80
SYSTEM MESSAGES
Table 3-1 List of System Messages (Continued)
MESSAGE NO. SYSTEM MESSAGEPAGE
1-YLN ร ISW CLK/FH Failure (Both)93
1-ZLN ร IS W CLK/FH Release95
2-TAP-INT Data Transfer Failure (Permanent) Note 1ยญ2-UAP-INT Data Transfer Failure (Temporary) Note 1ยญ2-VIP Data Transfer Failure (Permanent) Note 1-
2-WIP Dat a Transfer Failure (Temporary) Note 1-
3-BC-Level Infinite Loop (Perman e nt)97
3-CC-Level Infinite Loop (Temporary)98
3-DLock-Up Failure (Permanent)99
3-ELock-Up Failure (Temporary)100
3-F-48V Ov e r Current101
3-GGround Failure102
3-HDigital Line Warning103
13-JRestoration From CCS Link Failure194
13-KCCH Reset Interrupt Failure195
13-NDigital Line Warning196
13-ODigital Line Failure197
NDA-24307CHAPTER 3
Page 53
Issue 1
Page 82
SYSTEM MESSAGES
Table 3-1 List of System Messages (Continued)
MESSAGE NO. SYSTEM MESSAGEPAGE
13-PDigital Line Restore198
13-QDAU Battery Operation199
13-RDAU Line Operation200
13-ZPower Failure201
15-AVPS Failure (Temporary)202
15-BVPS Failure (Permanent)203
15-CVPS Restore204
16-AInside Trunk All Busy205
16-BVirtual Tie Line Set Report207
16-CVirtual Tie Line Cancel Report208
16-EVirtual Tie Line Set Time Out209
16-FSender Start Time Out212
16-KI/O Port Line OFF219
16-LI/O Port Line Restore220
Refer to โFusion Network Sys tem Manual . โ
Refer to the manual related to ATM.
Refer to โWireless System Manual.โ
Refer to the manual related to OAI.
Note 2
Note 2
255
-
-
257
258
259
260
261
263
266
267
NDA-24307CHAPTER 3
Page 55
Issue 1
Page 84
SYSTEM MESSAGES
Reset Interrupt
0-C
Default Alarm:
MN
This messag e displays whe n the processor is reset due to a failure in the system.
b0:0/1=-/Monitor Restart
b3:0/1=-/Initialization
b4:0/1=-/Data Copy restart (for Dual-CPU system only)
b5:0/1=-/MB control
b7:0/1=ACT/STBY (active system indication after restart)
b0:0/1=-/Monitor Restart
b3:0/1=-/Initialization
b4:0/1=-/Data Copy restart (for Dual-CPU system only)
b5:0/1=-/MB control
b7:0/1=ACT/STBY (active system indication after restart)
โ
Related Call Information
b7:0/1=Released/Not released
b7
See Chapter 5 for repair procedure.
CHAPTER 3NDA-24307
Page 58
Issue 1
Page 87
SYSTEM MESSAGES
C-Level Infinite Loop
0-E
Default Alarm:
SUP
C-level infinite loop is a state where a clock-level program, running under clock interrupt disable state, is in
an infinite loop. This message displays when the counter value to check the normality of the processing has
become abnormal.
b0:0/1 = -/Monitor Restart
b3:0/1 = -/Initialization
b4:0/1 = -/Data Copy Restart (for Dual-CPU system only)
b5:0/1 = -/MB contro l
b7:0/1 = ACT/STBY (active system indication after restart)
b0:0/1 = -/Monitor Restart
b3:0/1 = -/Initialization
b4:0/1 = -/Data Copy Restart (for Dual-CPU system only)
b5:0/1 = -/MB contro l
b7:0/1 = ACT/STBY (active system indication after restart)
โ
NMI Factor
b6b5b4b3b2b1b0
See Chapter 5 for repair procedure.
b0:0/1 = -/Reset by Power On
b1:0/1 = -/Watchdog Tim er timeou t
b2:0/1 = ISAGT is mounted/ISGAT is not mounted
b3:0/1 = -/OSC clock interrupt on ISGAT
b4:0/1 = -/IO parity Alarm
b5:0/1 = -/IO ready Alarm
b6:0/1 = -/External NMI
NDA-24307CHAPTER 3
Page 59
Issue 1
Page 88
SYSTEM MESSAGES
โ
System Controlling Port B
b7b6b5b4b3b2b1b0
โ
CPU Alarm
b7b6b5b4b3b2b1b0
โ
CPU Changeover Factors
b7b6b5b4b3b2b1b0
b0:0/1 = Ti mer 2 Gate ON/OFF
b1:0/1 = Speaker Gate ON/OFF
b2:0/1 = Parity Check Enable/MASK
b3:0/1 = Channel Check Enable/MASK
b4:0/1 = -/RAM Refresh Pulse Outp ut State
b5:0/1 = -/Timer 2 Output State
b6:0/1 = -/Channel Check Error Detected
b7:0/1 = -/Parity Error Detected
Information on Self-CPU Restart
after detection of a clock fault
b7b5b4b3b0
โ
Mate-CPU Restart Information
b7b5b4b3b0
b0:0/1 = -/Monitor Restart
b3:0/1 = -/Initialization
b4:0/1 = -/Data Copy Restart (for Dual-CPU system only)
b5:0/1 = -/MB control
b7:0/1 = ACT/STBY (active system indication after restart)
b0:0/1 = -/Monitor Restart
b3:0/1 = -/Initialization
b4:0/1 = -/Data Copy Restart (for Dual-CPU system only)
b5:0/1 = -/MB control
b7:0/1 = ACT/STBY (active system indication after restart)
โ
NMI Factor
b6b5b4b3b2b1b0
See Chapter 5 for repair procedure.
b0:0/1 = -/Reset by Power On
b1:0/1 = -/W at chdo g Timer timeout
b2:0/1 = ISGAT is mo unted/ISGAT is not mounted
b3:0/1 = -/OSC clock interrupt on ISGAT
b4:0/1 = -/IO parity Alarm
b5:0/1 = -/IO ready Alarm
b6:0/1 = -/External NMI
b0:0/1 = -/CLK Alarm
b1:0/1 = -/Emergency T i mer O v er fl ow
b2:0/1 = -/SOFT EMA
b3:0/1 = -/SOFT changeover
b4:0/1 = -/Emergency Counter Ov er fl ow
b5:0/1 = STBY/ACT
b6:0/1 = Dual/Single
b7:0/1 = CPU 0/CPU 1
b0:0/1 = -/Main Power Alarm
b1:0/1 = -/Power Alarm
b2:0/1 = -/FUSE Alarm
b3:0/1 = -/TEMP MJ Alarm
b4:0/1 = -/TEMP MN Alarm
b5:0/1 = -/Parity Alarm
b6:0/1 = Card is not mounted/mounted
b7:0/1 = -/EM A CLK Alarm
b7b6b5b4b3b2b1b0
CHAPTER 3NDA-24307
Page 62
Issue 1
Page 91
SYSTEM MESSAGES
B-Level Infinite Loop (Permanent)
0-G
Default Alarm:
MN
This message displays when a B-leve l inf inite loop failure occurs.