System information

FCD 901 48
Issue R2A, 07.2009
XMP1 Release 5.5 System Description
Single-user system
Page 6-6 Proprietary Information Aastra
Splitup into sub-networks
The XMP1 network can be split up into sub-networks (areas). These areas
must be connected via Ethernet. For performance reasons, one area should
not be assigned more than 70 nodes. In the Access Points to the individual
areas, the Central Units (> Version 3.0) must be equipped with an additional
module for IP connection.
The individual sub-networks (areas) still form the overall XMP1 network.
However, each area has its own management access for SOX referred to
as Access Point. A redundant management connection of the area via
further Access Points is possible. In this case, Access Point priorities must
be configured. Only the highest priority Access Point is active.
The management information is transmitted only inside an area in ECC8 of
the system channel TS0 and not between the individual areas.
E1 connection between areas
Traffic data are still transmitted via E1 connections between the individual
areas. The ECC8 in Sa-bits 7/8 of TS0 must not be transmitted between
areas. For this reason, ECC8 transmission must be inhibited at the 2 Mbit/s
interfaces of the E1 connection.
The transmission of the clock priority in Sa-bit 5 of TS0 can be adjusted in
compliance with the clock concept.
(~ 20 nodes)
XMP1
(~ 50 nodes)
XMP1
XMP1 overall network
Area 2
Area 2
Area 3
Area 3
E1
E1
SOX-NMS
+ SQL database
Operator
Terminal
TCP/IP via Ethernet LAN
1) Add. module on Central Unit (>V3.0)
for direct IP connection
1) 1)
AP AP
AP: Access Point to a Area
(~ 30 nodes)
XMP1
Area 1
Area 1
1)
AP
Sub-network 1
Sub-network 2
Sub-network 3
SOX-LCT
Figure 6.2: SOX single-user system, several areas