NEC Neax 2400 Imx Fusion Network System Manual

							CHAPTER 7 ND-70185 (E)
Page 166
Revision 3.0
TROUBLESHOOTING
23-U FCH Status Information
9.5 FLTINF = 1FH Spanning Tree Generation Start
This message is displayed when Spanning Tree Generation starts.
Figure 7-22   23-U FCCH Status Notification - Spanning Tree Generation
9.6 FLTINF = 85H Checksum Verification Failure
This message is displayed when Checksum verification has resulted in failure between the PBX and the firm-
ware.
Figure 7-23   23-U FCCH Status Notification - Checksum Verification Failure
1. xx 0x  1F xx  00 00   00 00          2.  00 00   00 00   00 00   00 00.........
MG
UG
FCH Mounting Location
FCH CKT No.TRC
RS
00
MG: Module Group 
U: Unit (0-3)
G: Group (0-23)TRC: Trace Confirmation Bit
(0/1 = Status Notification / Primitive Trace)
RS: Receive / Send Primitive Trace (not effective)
FCH CKT No. = Circuit No. of FCH

 1FFLTINF: 1FH = Spanning Tree Generation Start
Spanning Tree Generation Start:  00H = Normal
b7 b0b7 b0b7 b0b7 b0
Spanning Tree Generation  Start
1. xx 0x  85 xx  xx 00   00 00          2.  00 00   00 00   00 00   00 00.........
MG
UG
FCH CKT No.TRC
RS
FCH Mounting Location
00
MG: Module Group 
U: Unit (0-3)
G: Group (0-23)TRC: Trace Confirmation Bit
(0/1 = Status Notification / Primitive Trace)
RS: Receive / Send Primitive Trace (not effective)
FCH CKT No. = Circuit No. of FCH

 85FLTINF: 85 H =  Checksum Verification Failure 
Checksum of PBX 
b7 b0b7 b0b7 b0b7 b0b7 b0
Checksum Verification Failure
Checksum of Firmware 
						

							ND-70185 (E) CHAPTER 7
Page 167
Revision 3.0
TROUBLESHOOTING
23-W FCH Alternate Routing Start Notification
10. 23-W FCH Alternate Routing Start Notification
This message is displayed when the indicated FCH card of self-Node becomes inoperative. This message is also
displayed when the card is placed in make busy status by MNT 3 switch operation. In addition, when the FCH
of the adjacent node becomes inoperative, this message is displayed.
Figure 7-24   23-W FCCH Alternate Routing Start Notification
11. 23-X FCH Alternate Routing End Notification
This message is displayed when an inoperative FCH card of self-Node resumes its operation. Therefore, when
the card is placed in make idle status by MNT 3 switch operation, this message is also displayed.
Figure 7-25   23-X FCCH Alternate Routing End Notification
1. xx0x  0000 0000 0000    2. 0000 0000 0000 0000      3. 0000 .........
MG
U
G
FCH Mounting Location
FCH Mounting Location
MG: Module Group 
U: Unit (0-3)
G: Group (00-23)
FCH CKT No.
Circuit Number of FCH (0 - 7)
b0 b7b0 b7
1. xx0x  0000 0000 0000    2. 0000 0000 0000 0000      3. 0000 .........
MG
U
G
FCH Mounting Location
FCH Mounting Location
MG: Module Group 
U: Unit (0-3)
G: Group (00-23)
FCH CKT No.
Circuit Number of FCH (0 - 7)
b0 b7b0 b7 
						

							CHAPTER 7 ND-70185 (E)
Page 168
Revision 3.0
This page is for your notes. 
						

							ND-70185 (E) CHAPTER 8
Page 169
Revision 3.0
CHAPTER 8 EX- FCCS
1. General
This feature provides the following functions (they are activated when connecting multiple Fusion networks) or
a NEAX2000 IVS
2 system to a Fusion Network using the Enhanced CCIS feature. The network connected by
EX-FCCS function is referred as EX-FCCS Network in this manual. The network connected via Enhanced CCIS
function is referred to as Enhanced CCIS network in the manual.
1. Number PortabilitySee Section 3.1 “Number Portability”.
The Telephone Number data in a Fusion Network can be moved to another different Fusion Network by a
simple command operation from the sole Centralized-MAT in multiple Fusion Networks connected
through EX-FCCS link or Enhanced CCIS link. See “Centralized Maintenance (Centralized-MAT for EX-
FCCS)” for explanation of the Centralized-MAT. 
2. Centralized Maintenance (Centralized-MAT for EX-FCCS) 
See Section 3.2 “Centralized-MAT for EX-FCCS”
All nodes (NEAX2400 IMX system) in the multiple Fusion Networks and NEAX2000 IVS
2 systems con-
nected through Enhanced CCIS link can be maintained from one MAT. The MAT used for Centralized
Maintenance is called as “Centralized-MAT for EX-FCCS”.
3. Inter-network service equivalent to CCIS features
For details of CCIS features activated through EX-FCCS networks and Enhanced CCIS networks, see 3.3
“CCIS Features Activated with EX-FCCS”.
For the basic operation or the data programming for NEAX2000 IVS
2, see other manuals specified the
NEAX2000 IVS2 system. 
						

							CHAPTER 8 ND-70185 (E)
Page 170
Revision 3.0
EX- FCCS
EX-FCCS Network Configuration
2. EX-FCCS Network Configuration
2.1 Network Configuration
The summary of network configuration classified into two types are shown in Ta b l e  8 - 1. See Table 8-1 in
conjunction with Figure 8-1 for easy understanding of network configuration. The following items and sec-
tions explain more details.
Note:[Hardware Configuration] 
For IMX to IMX connection type, both FCH and CCH cards are available.
Fo r  I V S
2 to IMX connection type, FCH card is not available. Use CCH card.
*PA-SC18 (CCH) card is not available for the EX-FCCS network establishment.
There are two connection types. 
(1) NEAX2000 IVS
2 to NEAX2400 IMX connection (Enhanced CCIS) 
(2) NEAX2400 IMX to NEAX2400 IMX connection (EX-FCCS)
Figure 8-1   Network Connection Type Table 8-1 EX-FCCS Network Type Classification
× : Available
TYPECONNECTION 
TYPEA MAXIMUM 
NUMBER OF 
TELEPHONE NUM-
BERSERVICE CENTRALIZED FUNCTION
IMX to 
IMXIVS2 to 
IMXIMX to 
IMXIVS2 to 
IMXMAINTE-
NANCEBILLING MCI
1FCCSEnhanced
CCIS120,000FCCS 
serviceCCIS 
service
×××
2EX-
FCCSEnhanced
CCIS120,000CCIS 
serviceCCIS 
service×××
(1) NEAX2000 IVS2 to 
NEAX2400 IMX
Legend
: EX-FCCS : FCCS
FCCS NETWORK 1
IVS2
(2) NEAX2400 IMX to 
NEAX2400 IMX
FCCS NETWORK 2
 IMX
IMXIMX
: Enhanced CCIS
IVS2
IMX
IMXIMX 
						

							ND-70185 (E) CHAPTER 8
Page 171
Revision 3.0
EX- FCCS
EX-FCCS Network Configuration
2.2 Conditions for Network Establishment (NEAX2000 IVS
2 to NEAX2400 IMX Connection) 
Conditions for connecting the NEAX2000 IVS2 to NEAX2400 IMX are described below.
1. All IVS
2 systems must be directly connected to an IMX. See Figure 8-2.
Figure 8-2   NEAX2000 IVS2 to NEAX2400 IMX Connection
2. The number of logical routes available (899) in the FCCS network is reduced by one for every route
provide in the NEAX2000 IVS2 when connected via Enhanced CCIS. 
Note:The above is a condition of data assignment in the NEAX2400 IMX system. The NEAX2000 IVS2 system
accommodates up to 255 nodes (including NEAX2400 IMX and NEAX2000 IVS2 systems). The number of
point codes assignable in the NEAX2000 IVS2 system is a maximum of 255, including Enhanced CCIS net-
works.
3. When directly connecting a NEAX2000 IVS
2 to a NEAX2400 IMX, one signal channel may support
multiple voice routes. However, when the Enhanced CCIS function is provided with EVENT BASED-
CCIS, a signal route must be provided per voice route.
 
NEAX2000 IVS2 (B) cannot be added to NEAX2000 IVS2
NEAX2400 IMX.
Enhanced CCIS
IMXIVS
2 (A)
IVS2 (B)
  (A) which is already connected with 
UNAVAILABLE   
						

							CHAPTER 8 ND-70185 (E)
Page 172
Revision 3.0
EX- FCCS
EX-FCCS Network Configuration
2.3 Conditions for Network Establishment (NEAX2400 IMX to NEAX2400 IMX Connection) 
Conditions for establishing a FCCS network (NEAX2400 IMX to NEAX2400 IMX) are shown below. 
1. Each Fusion Network can accommodate a maximum of 253 network IDs.
2. Each Fusion Network can accommodate a maximum of 899 logical routes.
3. The NCN and NDM exist individually in each Fusion Network.
Figure 8-3   NEAX2400 IMX to NEAX2400 IMX Connection
Network configuration of the NEAX2400IMX to NEAX2400IMX connection is as follows.
FPC1
(NCN)FPC2
FPC4 FPC3FPC1
(NCN)FPC2
FPC3 FPC4
Fusion Network (B)
In this Fusion Network,
NDM (a) is used.
In this Fusion Network,
NDM (b) is used.
FPC1
(NCN)FPC2
FPC4 FPC3
LGRT3
LGRT3 LGRT4
In this Fusion Network,
NDM (c) is used.
: EX-FCCS
: Fusion Group (FUG) : FCCS
Fusion Network (A)
Fusion Network (C)
LGRT1, 2
LGRT899
LGRT1, 2
LGRT200
LGRT100
LGRT899
Network configuration of the NEAX2400 IMX to NEAX2400 IMX connection is as follows. 
						

							ND-70185 (E) CHAPTER 8
Page 173
Revision 3.0
EX- FCCS
EX-FCCS Network Configuration
2.4 Fusion Network Group (FUG)
[Fusion Network Group (FUG)]
When connecting multiple Fusion networks using EX-FCCS, a Fusion Network group number is required
to distinguish different Fusion Network groups. A Fusion Network Group is called as “Fusion Group
(FUG)”. A maximum of 4 FUGs can be connected via EX-FCCS.
[Center Fusion Group (Center FUG)]
Identify the Center Fusion Group (Center FUG) from the FUGs in the EX-FCCS network. This is the sole
node allowed  to assign or delete Telephone Numbers within the self FUG and the other FUG. 
1. An EX-FCCS network may consist of FUGs (connected via EX-FCCS) and NEAX2000 IVS
2 sys-
tems (connected via Enhanced CCIS). All FUGs must be connected to the Center FUG within a range
of 1 or 2 EX-FCCs links or 1 or 2 Enhanced CCIS links from the Center FUG. In order for an end-to-
end connection to be established, no more than 4 EX-FCCS or Enhanced CCIS links may be used. See
Figure 8-4. 
Figure 8-4   Allowable SPAN from the Center FUG
An exam ple of EX-FCCS Network configuration is shown in this figure. In this exam ple, FUG2 is the 
Center FUG .
LEGEND
: EX-FCCS : Fusion G roup (FUG) : F C C S
FUG2
IV S2
FUG3
FUG1
FUG4
Center FUG
IV S2
IV S2
IV S2IV S2
IV S2
: Enhanced CCIS 
						

							CHAPTER 8 ND-70185 (E)
Page 174
Revision 3.0
EX- FCCS
EX-FCCS Network Configuration
2.5 Interactions
1. Conditions for PS Service
Roaming and Hand-over feature cannot be activated between FUG-FUG in an EX-FCCS network and
FUG-IVS
2 in an Enhanced CCIS network. To execute roaming service, connect other Q.931a/IS-
11572 lines.
2. Conditions for OAI/ACD Service
The OAI/ACD service in EX-FCCS Network is executed on the same condition in CCIS Network. 
						

							ND-70185 (E) CHAPTER 8
Page 175
Revision 3.0
EX- FCCS
EX-FCCS Features
3. EX-FCCS Features
3.1 Number Portability
[Operating Procedure] 
1. Log in to the NCN of the Center FUG from the Centralized-MAT for EX-FCCS.
2. Assign the Telephone Number data using AELGN command. The new data is automatically copied to
the NDM in the self-FUG and the other FUG in an EX-FCCS network. AELGN command is also
used to delete or change Telephone Number data in addition to assignment.
Note 1:AELGN command is used to operate Number Portability for Telephone Numbers used in NEAX2400 IMX
systems. For the NEAX2000 IVS2 system, several commands are required for assignment. For details, see
related NEAX2000 IVS2 manuals.
Note 2:When logging in to the node other than the NCN of the Center FUG (LN in Center FUG or LN/NCN in
other FUGs), only reading out the AELGN command data is available. 
Note 3:If the center FUG group is not “0” and FUG no.“0” is assigned to another group, AELGN command data
assignment is available for the node to be logged in only.
[Service Conditions]
1. A closed numbering network is recommended for numbering plan of the EX-FCCS network.
2. Only Telephone Number (max. 8 digits) is allowed for the extension number used in an EX-FCCS
network.