363-206-295
About This Document
xlii
Issue 1
December 1997
Multi-Vendor OI
0
To support multi-vendor OI, DDM-2000 OC-12 R7.0 supports Target ID Address
Resolution Protocol (TARP) instead of Lucent Directory Service (LDS).
DDM-2000 OC-3 R13.0, FiberReach R3.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. TARP is the
established multi-vendor standard for SONET NEs that support TL1 OS
interfaces.
DDM-2000 OC-12 R7.0 is developed to be compatible with any other-vendor NEs
that also support TARP, OSI, IAO LAN, and TL1/X.25 as specified in Bellcore
GR-253. In addition, DDM-2000’s TARP Manual Adjacency feature enables
DDM-2000 to operate in networks that include CMISE-based NEs which may not
support TARP propagation.
DDM-2000’s compatibility with Tellabs
TITAN
*
5500/S R5.0 DCS, with
TITAN
serving as the TL1/X.25 GNE for DDM-2000 TL1-RNEs, has been confirmed
through cooperative joint testing. DDM-2000’s compatibility with some other-
vendor NEs has also been tested by independent third-parties such as Bellcore.
Because DDM-2000 OC-12 R7.0 is intended to facilitate OS-based centralized
operations, and because TL1/X.25 OS access is the key standardized multi-
vendor OI application, the following Remote NE Status features are not supported
in DDM-2000 OC-12 R7.0:
■
Remote office alarms
■
Remote CIT alarm reports
■
Remote user panel indications
■
TBOS
■
Parallel telemetry.
All of the above features depend on the proprietary exchange of information
among Lucent NEs in a subnetwork, specifically the communication of each
remote NE’s alarm status to other NEs. Although the Remote NE Status features
were supported in previous releases of DDM-2000, such Lucent-only operations
features in multi-vendor subnetworks would not include other-vendor NEs, due to
the lack of applicable standards, and thus would be incomplete.
*
TITAN is a trademark of Tellabs, Inc.