363-206-305
Maintenance Description
9-8
Issue 3 June 2000
DDM-2000 FiberReach is developed to be compatible with any other-vendor NEs
that also support TARP, OSI, and TL1/X.25 as specified in Telcordia Technologies
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 FiberReach supports user provisioning of
several OSI parameters to allow users to adjust their operations subnetwork, if
necessary. For example, to support subnetwork partitioning of large subnetworks,
DDM-2000 FiberReach supports user provisioning of NSAP area addresses.
DDM-2000 FiberReach does not support Level 2 Intermediate System (IS)
functionality itself.
DDM-2000 FiberReach Release 3.0 and later offer compatibility with Tellabs
TITAN
*
5500 DCS R5.0, including TL1/X.25 OS access with TITAN 5500 DCS
serving as the TL1-GNE for DDM-2000 FiberReach TL1-RNEs, has been
confirmed through cooperative joint testing between Lucent and Tellabs. DDM-
2000’s compatibility with some other-vendor NEs has also been tested by
independent third-parties such as Telcordia Technologies on behalf of the SONET
Interoperability Forum (SIF).
DDM-2000 FiberReach Release 3.0 and later are intended to facilitate OS-based
centralized operations, and TL1/X.25 OS access is the key standardized multi-
vendor OI application.
DDM-2000 FiberReach Release 4.0 supports the following Remote NE Status
features:
â–
Remote office alarms
â–
Remote CIT alarm reports.
The following Remote NE Status features are not supported in DDM-2000
FiberReach Release 4.0:
â–
Remote user panel indications
â–
TBOS
â–
Parallel telemetry
â–
Remote ACO Requests.
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.