Siemens HiPath 3000 Series, Сервисная документация

Страница: 175 / 1302

boards.fm
A31003-H3590-S100-7-7620, 06/2012
HiPath 3000/5000 V9, Service documentation
3-43
Nur für den internen Gebrauch
Boards for HiPath 3000
Central Board
Networking via Ethernet/IP (10/100 BaseT) lines:
System 1 System(s) n+1
No trunk
or analog
trunk – CMS
3
CMS or CMA
(see
Table 11-1)
No trunk
or analog
trunk – CMS
3
CMS or CMA
(see
Table 11-1)
ISDN S
0
(not al-
ways ac-
tive)
Via ISDN
S
0
trunk
connection
(if active)
CMS
3
CMS or CMA
(see
Table 11-1)
ISDN S
0
(not al-
ways ac-
tive)
Via ISDN
S
0
trunk
connection
(if active)
CMS
3
CMS or CMA
(see
Table 11-1)
ISDN S
0
(always
active)
Via ISDN
S
0
trunk
connection
– CMA
2
ISDN S
0
(always
active)
Via ISDN
S
0
trunk
connection
– CMA
2
ISDN
S
2M
Via ISDN
S
2M
trunk
connection
– CMA
2
ISDN S
2M
Via ISDN
S
2M
trunk
connection
– CMA
2
1 CMS is not necessary if the reference clock supplied by the CO is always available via the networking lines (not a trans-
parent clock).
2 CMA is not necessary if ADPCM conversion is not needed for HiPath Cordless Office (see Table 11-1).
3 CMS is not necessary but is recommended for the following reasons: Although an Ethernet link is an asynchronous con-
nection, buffer overflow/underflow can cause transmission errors. To avoid this, the clock difference between the master
and the slave systems should be as small as possible so that the receive and send buffer can be read and addressed at
the same speed on both sides. The more accurate the clock source in the relevant systems, the fewer the faults.
Table 3-19 Recommendations for CMA and CMS Utilization
Trunk
connec-
tion
Reference
clock
HiPath Cordless
Office
Trunk
connec-
tion
Refer-
ence
clock
HiPath Cordless
Office
no yes no yes