Operations interworking (OI) provides the capability to access, operate, administer, maintain, and provision remote Alcatel-Lucent NEs from any Alcatel-Lucent NE with DCC connectivity in a network or from a centralized OS.
Alcatel-Lucent OI is available among NEs that are connected through the SONET DCC or IAO LAN. With this feature, users can perform OAM&P activities on a centralized basis, saving travel time and money.
OI features including the following:
The following table summarizes Alcatel-Lucent 1665 DMX OI compatibility with the products and releases specified previously.
Product |
DCC |
IAO LAN |
WaveStar® CIT Access |
TCP/IP |
Remote Software Download |
Auto Time/ Date sync |
Remote NE Status | |
---|---|---|---|---|---|---|---|---|
tl1–Gne |
tl1-rne | |||||||
Alcatel-Lucent 1665 DMX |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
Alcatel-Lucent 1665 DMXtend |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
Alcatel-Lucent 1665 DMXplore |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
Alcatel-Lucent 1850 TSS-5 |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
yes |
Alcatel-Lucent 1850 TSS-100 |
yes |
- |
- |
yes 1 |
yes 1 |
- |
- |
- |
Alcatel-Lucent 1850 TSS-320 |
yes |
- |
- |
yes 1 |
yes 1 |
- |
- |
- |
DDM-2000 OC-3 |
yes |
yes |
yes |
yes |
- |
yes |
yes |
yes |
DDM-2000 OC-12 |
yes |
yes |
yes |
yes |
- |
yes |
yes |
- |
FiberReach |
yes |
- |
yes |
yes |
- |
yes |
yes |
yes |
FT-2000 ADR |
yes |
- |
yes |
- |
- |
- |
yes |
- |
WaveStar® TDM 2.5G/10G (2-Fiber) |
yes |
yes |
yes |
yes |
yes |
- |
- |
- |
WaveStar® BandWidth Manager |
yes |
yes |
yes |
- |
yes |
- |
- |
- |
Alcatel-Lucent 1675 LambdaUnite MSS |
yes |
yes |
yes |
- |
yes |
- |
- |
- |
Ciena® Core Director |
yes |
- |
- |
yes |
- |
- |
- |
- |
OMS |
- |
yes |
- |
yes |
yes |
- |
yes |
- |
NMA |
- |
yes |
- |
yes |
yes |
- |
- |
- |
Transport (TEMS) |
- |
yes |
- |
yes |
yes |
- |
- |
- |
The Host OS Type of the TL1 TCP/IP GNE for Alcatel-Lucent 1850 TSS-100 or Alcatel-Lucent 1850 TSS-320 must be provisioned to TL1PEERCOM. All Message Types for the TL1PEERCOM OS Type must be enabled using Administration → Set TL1 Message Map.
An alarm group is a set of NEs that share status information between themselves, such as alarms, LEDs, and ACO status. The set of remote NEs that an NE can exchange status information which is determined by the value of the local alarm group parameter. This parameter is provisioned at each local NE and specifies whether that local NE does or does not exchange remote NE status with other Alcatel-Lucent NEs in the same SONET subnetwork. In Alcatel-Lucent 1665 DMX, all NEs are defaulted into the same alarm group (number 255).
Alarm groups can be nodes in a ring, nodes of a linear extension, or any other logical grouping such as a maintenance group or geographical group. For example, 24 NEs could be provisioned into three alarm groups with eight NEs that share a community of interest such as the same OC-3 low-speed optical interface.
All members of the same alarm group share NE status information but do not share information with other alarm groups.
Depending on provisioning, a member of an alarm group can:
Know the alarm/status of all members of the same alarm group and, if the NE is at the CO, activate audible office alarms for the alarm group.
List a report of the summary alarm or status condition of other NEs in the group.
Display composites of the highest alarm level among other member NEs in the same alarm group.
Members of an alarm group exchange information through one or more alarm gateway NEs (AGNEs) that are defined in the same alarm group. All Alcatel-Lucent 1665 DMX NEs use the DCC to receive and report alarm and status information to the AGNE(s). The AGNE rebroadcasts all alarm and status information from one NE to all the other NEs in the same alarm group.
This information is used to activate remote far-end summary alarm reports and remote office alarms for each NE in the alarm group. At least one NE in each alarm group must be provisioned as the AGNE. An additional AGNE can be provisioned for redundancy, but it is recommended that only one AGNE be provisioned for each alarm group. Considerations for choosing an NE as an AGNE include being central to the group to make communications links easily accessible for maintenance purposes.
The AGNE and TL1 GNE should be separate NEs. Furthermore, the AGNE is a "collection point" and does not have to be a NE in a CO.
November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |