Note:
When one Fusion Network take the configuration with FCH and without FCH together, it is necessary to
assign the routing data using both AFPC and AETH command. An example data assignment is shown in
Figure
5-35.
AF P C /AE T H (at N ode A ) - F usion w ith F C H & Fusion w ithout F C H is both configured in O ne N etw ork C ontrol
* T his exam ple show s the data assignm ent having the priority to the connection betw een N ode A
and N ode C w ith F C H card.
1
T o N ode C directly w ith FC H
A E TH
F P C : 3 (FP C N um b er of N od e C )
C _ R T
FC H N
D S T _ IP
1 0
1
0
2 0
2
0
2
T o N ode C via N ode B
A FP C
F P C : 3 (FP C N um b er of N od e C )
F C C H : 0 (F C H card is no t u sed )
P _R O U TE : 1
C N T
C _ R T
F P C N
1
11
2
2
21
2
"USE_GATE" data is automatically assigned.
Note:
STEP 4: ACAN
Assign the Fusion Connection Index Code (FCIC) and the LENs on an adjacent FPC basis.
Figure 5-36
It is not necessary to assign the same number as trunk and FCIC. However, FCIC numbers between
Note:
adjacent nodes must be identical.
N ode A
N E X T_ IP
FC H N =1
0
FC H N =2
0
C _R T : 2 0
[To N ode C ]
Figure 5-35 AFPC/AETH Sample Data Assignment
shows a sample data sheet for Node A.
NDA-24299
C _R T : 11
FPC N =2
D TI
1
D TI
FC H is not used.
C _R T : 21
C _R T : 10
FC H is used.
1
C _R T : 12
D T I
3
D T I
N ode C
DATA PROGRAMMING
Assignment of FCH Related Data
2
N ode B
D TI
2
2
D TI
[To N ode C
via N ode B]
FC H is used.
C _R T : 2 2
D TI
D TI
CHAPTER 5
Revision 1.0
Page 89