363-206-295
Technical Specifications
Issue 1 December 1997 10-31
TL1/X.25 Interface 10
The DDM-2000 Multiplexer supports a TL1/X.25 interface for communication
between local and remote DDM-2000 (and FT-2000) NEs and alarm surveillance
and provisioning operations systems (OS) such as Bellcore's NMA and OPS/INE
OSs. The DDM-2000 OC-12 Multiplexer TL1/X.25 interface is based on Bellcore
TR-TSY-000833, Issue 5. The DDM-2000 supports up to nine X.25 permanent
virtual circuits (PVCs) and up to nine switched virtual circuits (SVCs) assigned by
default as shown in Table 10-16. The user may assign a maximum of nine VCs
using any combination of PVCs and SVCs.
Table 10-16. TL1/X.25 Interface — VC Assignments
All VCs support command/response messages. The autonomous maintenance
messages are all TL1 autonomous messages except REPT DBCHG.
If the default assignments in Table 10-16 do not meet the user’s OS needs,
DDM-2000 allows users to specify the routing of TL1 autonomous message types
to VCs. This is done in two steps:
1. Each TL1 autonomous message type (e.g., REPT ALM, REPT DBCHG,
REPT PM, etc.) can be mapped to any OS type (using the
ent-tl1msgmap command at every DDM-2000 in the subnetwork). The
OS types are tl1Maintenance, tl1MemoryAdministration, tl1test,
tl1PeerComm, tl1Other1 and tl1Other2.
2. Each OS type can be mapped to any of the VCs (using the ent-osacmap
command at the DDM-2000 TL1 GNE). The combination of Step #1
(mapping TL1 autonomous message types to OS types) and Step #2
(mapping OS types to VCs) accomplishes the desired mapping of TL1
autonomous message types to VCs.
PVC
ID
SVC
ID
Logical
Group #
Logical
Channel # Default Use
1 0 1 User Definable
2 0 2 Autonomous Maintenance Messages,
User Definable
3 0 3 Autonomous Provisioning Messages
(REPT DBCHG)
User Definable
1 0 16 User Definable
2 0 17 User Definable
3 0 18 User Definable
4 0 19 User Definable
5 0 20 User Definable
6 0 21 User Definable
To Next Page
Loading...
Need help?
General
