363-206-285
Maintenance Description
Issue 3 June 2001
9-7
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.
DDM-2000 OC-3 R13.0 and R15.0 still support the following Lucent proprietary OI
applications between Lucent NEs in multi-vendor subnetworks:
â– Remote Craft Interface Terminal (CIT) login
â– Remote software download and copy
â– Remote NE-to-NE automatic time/date synchronization at start-up.
For more information about DDM-2000 OC-3 R13.0 and R15.0 OI, refer to 824-
102-144,
Lucent Technologies 2000 Product Family Multi-Vendor Operations
Interworking Guide.
SEO Network Element Status Using Alarm Gateway
NE 9
The Remote NE status feature is supported by OC-3 Release 15.0. It partitions a
subnetwork into maintenance domains (alarm groups). In partitioned large
networks, each Level 1 area can be identified as a separate Alarm Group, as long
as it does not exceed the 50 NE limitation. Provisioning of one alarm gateway NE
(AGNE) is required in order to support remote office alarms and summary alarm
information of remote NEs in the local alarm report.
By default, the subnetwork contains a single Alarm Group of all NEs. At least one
AGNE needs to be provisioned per subnetwork. A second AGNE can be
provisioned as a backup. Additional AGNEs will degrade the network
performance.
An Alarm group is a set of NEs that share status information between themselves.
Alarm Groups can be nodes in a ring, or in any other logical grouping such as a
maintenance group or a geographical group. All NEs are defaulted into an Alarm
Group (number 255). Users provision NEs into Alarm Groups by assigning each
member an Alarm Group number to support operations interworking, large
networks, and to avoid sending unnecessary information to every NE. For
example 24 NEs could be provisioned into three Alarms Groups of 8 NEs each.
Every NE broadcasts its network status (through the AGNE) to all other NEs in the
same alarm group. (All members of the same Alarm Group share NE status
information through their AGNEs, but do not share information with other Alarm
Group members).
Depending on provisioning a member of an Alarm group can:
To Next Page
Loading...
Need help?
General
