EasyManua.ls Logo

Lucent Technologies FiberReach DDM-2000 - Page 437

Lucent Technologies FiberReach DDM-2000
1896 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
363-206-305
Maintenance Description
Issue 3 June 2000
9-7
performance monitoring with OSs such as Telcordia Technologies's Network
Monitoring and Analysis (NMA). The DDM-2000 supports service provisioning
with memory administration OSs such as Lucent’s ITM SNC
*
or Telcordia
Technologies's OPS/INE. (FiberReach 4.0 will be supported by TEMS.) The
DDM-2000 also supports remote recovery and control functions, installation
provisioning, and security over the TL1/X.25 link. The TL1 message set used has
been updated to offer full remote reporting and control capabilities. This functional
equivalency between the CIT and TL1 allows the option of using either the CIT or
TL1 for provisioning tasks, whichever is more convenient. See 824-102-151,
DDM-2000 Multiplexers Operations Systems Engineering Guide,
for more
information about OS interfaces.
The OS can use more than one NE as a GNE to provide redundancy and/or to
distribute TL1 message volume across multiple X.25 links. The TL1/X.25 GNE
serves as a single interface to the OS for the NEs in the same subnetwork. The
TL1/X.25 GNE receives operations information from of all the NEs through the
DCC and reports this information, as well as its own information, to the OS. The
operations information is in the form of TL1 messages. Through the GNE, the OS
can send TL1 commands to any NE in the subnetwork. FT-2000 OC-48 Lightwave
Systems can serve as the TL1/X.25 GNE for DDM-2000 NEs. For DDM-2000
FiberReach 3.0 and later, OC-3 R13.0 and R15.0, and OC-12 R7.0, Tellabs TITAN
5500/S R5.0 DCS, or other-vendor NEs that adhere to Telcordia Technologies
GR-253, can be the TL1/X.25 GNE. DDM-2000 FiberReach can not be a TL1/
X.25 GNE itself.
Multi-Vendor OI
9
To support multi-vendor OI, DDM-2000 FiberReach Release 3.0 and later
supports Target ID Address Resolution Protocol (TARP) instead of Lucent
Directory Service (LDS). DDM-2000 OC-3 R13.0 or later, OC-12 R7.0, and FT-
2000 OC-48 R8.0 also support TARP, thus Lucent 2000 Product Family OI
compatibility is still supported but not OI compatibility with previous releases of
DDM-2000 and FT-2000. (Refer to the OI Software Compatibility table in Chapter
8.) Both LDS and TARP are directory services that provide NSAP-TID
translations. LDS supports additional Lucent-only features, but TARP is the
established multi-vendor standard for SONET NEs that support TL1 OS
interfaces. DDM-2000 supports the TARP Data Cache (TDC) function to reduce
the frequency of TARP propagation throughout the subnetwork and to improve
performance. No DSNE is required for TARP.
* The Integrated Transport Management SubNetwork Controller (ITM SNC) is an element
management system that supports SONET NEs. ITM SNC provides fault, provisioning,
configuration, and security management functions via a GUI.

Table of Contents

Related product manuals