A user can remotely retrieve, on request, information of an electronic label of an NTU or SRU. The LTU keeps this information in its database. The GUI can display the information on request; it is not used by the LTU for any other purpose.
The following information can be retrieved:
The performance of SHDSL segments that are terminated on the LTU, SRU and NTU can be monitored. The SHDSL standard (ITU-T Rec. G.991.2) prescribes a set of parameters that needs to be monitored and stored in 15 minute and 24 hour bins for near-end Performance Monitoring. The following table provides an overview of the PM parameters:
Parameter |
Name |
Definition |
---|---|---|
CV/BBE |
Code Violation/background Block Error |
Each CRC6 anomaly is counted a CV/BBE during non-SES and non-UAS seconds |
ES |
Errored Seconds |
Each second with one or more CRC6 anomaly is counted as an ES, unless that second is UAS |
SES |
Severely Errored Second |
Each second with 50 or more CRC6 anomalies (> 30%)or one or more LOSW events is counted as an SES, unless that second is UAS |
LOSWS |
Loss of SyncWord Second |
Each second in which LOSW is declared as LOSWS |
UAS/US |
Unavailable Second |
Each second that is part of unavailable time (UAT) is counted as UAS. UAT is declared at the begin of 10 consecutive SES and cleared at the begin of 10 consecutive non-SES. |
OFS/AIS |
OOF or AIS Second |
Second containing ab LOSW or AIS event |
CRC6 |
CRC6 anomaly |
Number of CRC6 block errors (same as BBE, but not inhibited by SES or UAS) |
TMP |
Total Measurement Period |
Elapsed time in current interval |
The default thresholds of the parameters are fix preset and cannot be changed. For more details, please refer to the User Operations Guide, Chapter Performance monitoring concepts - Available PM data.
For SHDSL, a performance monitoring block coincides with an SHDSL frame. Since the SHDSL frame length is 6 ms, there are 1662/3 blocks per second. The following definitions are applicable for PM parameters that are used for SHDSL segment termination points:
Each second that is part of unavailable time is counted as a UAS. Unavailable time starts after 10 consecutive SESs. These 10 seconds are part of unavailable time. Unavailable time stops after 10 consecutive non-SESs. These 10 seconds are not part of unavailable time.
Each second in which 50 or more CRC-6 words are in error or in which a LOSW defect is active is counted as a Severely Errored Second, provided the second is not a UAS. An SES detection threshold of 30% is equivalent to 50 errored blocks.
Each second in which one or more CRC-6 word is errored or in which a LOSW defect is active is counted as an Errored Second, provided the second is not a UAS.
Each SHDSL frame with an errored CRC-6 word is counted as a Background Block Error (Code Violation), provided the second in which the error occurs is not an SES or a UAS. Hence, the maximum possible number of BBEs per second is 49.
Three types of 2 Mbit/s services can be provided over SHDSL links, which can be selected from the user interface per NTU. These features work only for NEs which support QD2.
In this case there is a leased-line connection between two end-user sites providing 2048 kbit/s throughput. This signal remains unmonitored and does not have G.704 framing. From a TS0 processing and monitoring point of view this is a trivial case: TS0 is not monitored and transparently passed through.
In this case there is a “traditional” ISDN-PRI connection between the end-user on one end and a 64 kbit/s PSTN switch with ISDN features on the other. The effective throughput is 1920 kbit/s (30 B-channels). TS0 is used for monitoring and maintenance purposes by the operator. TS16 is used for signaling between the switch and the end-user client equipment. From a transport perspective TS16 is transparently transported. Compared with the ISDN-LL mode, the ISDN terminating equipment on both ends of the ISDN link have a different role (ET or TE); it is asymmetric.
ISDN-LL: In this case there is a leased-line connection between two end-user sites providing 1984 kbit/s throughput. TS0 is used for monitoring and maintenance purposes by the operator. Compared with the ISDN-PRI mode, the ISDN terminating equipment on both ends of the ISDN link have the same role (TE); it is symmetric. The role of the LTU is to translate request and response messages between the management system and the NTUs regarding the provisioning of the TS0 functions.
It is possible for the user to provide certain AIS options via the GUI. This feature works only for NEs which support EOC-ext..
The following options are possible:
Force S-interface or customer interface AIS – enable/disable: This command is applicable in all modes and forces an all ones AIS pattern on the outgoing E1 interface in the end-user direction.
Channel AIS conversion – enable/disable: This command is applicable in both ISDN modes and controls whether a Channel AIS request in Sa6 (“1100”) received from the LTU direction is converted to an all ones pattern on the E1 output towards the end-user or is transparently passed through as channel AIS.
Force U-interface or network interface AIS – enable/disable: This command is applicable in all modes and forces an AIS pattern according to the selected format on the P12 logical interface towards the LTU.
AIS Signaling Method for ISDN – Channel AIS (“1100”), Channel AIS (“1000”): This command is applicable in both ISDN modes and controls the sa6 Alarm Code to be used towards the network in case a failure is detected on the incoming E1 signal from the end-user or when AIS is forced via management. Channel AIS is defined as an all-ones pattern in TS 1-31 and a valid TS0 (regenerated CRC-4 and E-bits based on signal from network; A-bit set to “0”; Sa5 set to “1”), with an Sa6 bit-pattern of “1100” or “1000”, whichever is selected.
Channel AIS/Full AIS selection – This command is available in both ISDN modes and determines whether “channel AIS” or “full AIS (all ones)” is sent to the network during E1 input failures or when AIS is forced by management.
For maintenance operations, the user has the option to activate and release loopbacks via the management systems on the following interfaces:
SRU: Supports an SHDSL outloop (loop on the customer side of the SRU)
E1 NTU in E1 mode (E1 over SHDSL): Supports an SHDSL outloop (on the SHDSL side of the E1 NTU) and supports an outloop on the customer interface (on the E1 side of the modem)
E1 NTU (NT2M) in TU12 mode (TU12 over SHDSL): Supports an outloop on the customer interface (on the E1 side of the TU12 mode E1 NTU)
Ethernet NTU (NT10ETH): Supports an inloop on the Ethernet NTU (on the SHDSL side of the Ethernet NTU)
An NT2M modem has two functions for which a synchronization reference signal is necessary:
Supplying a 2048 kHz timing output signal (according to G.703-13), 120W symmetrical.
Retiming the outgoing 2048 kbit/s E1 signal towards the end-user.
To be able to provide these synchronization services, the NT2M derives the synchronization reference signal from the incoming SHDSL signal. This timing signal can be traced back immediately to the LTU internal clock, since this clock is used to generate the timing for the outgoing SHDSL links on the LTU. Possible SRUs in the link will not change the traceability of the timing, since they always operate in through-timed mode. In order for the NT2M to know the quality of the recovered clock signal, the LTU sends the current quality level (SSM) to the NTU on a regular basis, but certainly after each completed inventory phase and each time the Quality Level of the internal clock changes in the LTU.
The NT2M will declare the recovered reference as insufficient, when the quality level is SEC or worse. So a 1643 Access Multiplexer AM/1643 Access Multiplexer Small AMS clock that is free-running or in hold-over will not be accepted by the NT2M. For the 2048 kHz output of the NT2M, the following requirements are important. It is turned-off (squelched) as long as the SHDSL link is not functioning and when the level of the reference is SEC or worse. Finally, it is possible to turn-off the timing output by management command.
On NT10ETH the following PM parameters are monitored: TxOctets, RxOctets and RxDiscardedFrames. They are supported on both Ethernet ports and on the single WAN port. The support includes threshold alarms for discarded frames.
The following sections describe Ethernet NTU support features for SHDSL configurations.
The 1643 AM/1643 AMS supports a 2 port Ethernet SHDSL modem as an NTU, which is connected via 1 to 4 parallel TU12s over SHDSL mapped links. For increased bandwidth, the Ethernet traffic is encapsulated in GFP-F and uses VC12-Xv virtual concatenation with LCAS support.
The 1643 AM/1643 AMS supports the following Enhanced NTU Ethernet ports PM counters via the QD2-Lite extension.
Ethernet Forwarded Discarded Frames due to overflow in egress direction (eFDFO).
Ethernet Outgoing Discarded Frames due to lifetime end (eODFT).
Note that the above Ethernet Traffic and Error PM bins are applicable for both LAN and WAN ports of the NTU. However, the WAN port does not support pPPS, eINFC, and eONFC counters.
Note: The PM counters -pCbR, -pCbS and -ppDE are supported since 1643 AM/1643 AMS Release 6.1.
The 1643 AM/1643 AMS supports bridge mode provisioning to the Ethernet NTU.
The following bridge modes are supported.
The 1643 AM/1643 AMS provides enhanced PM support for third party NTUs. It supports a two port Ethernet SHDSL modem (NTU) which is connected via 1 to 4 parallel TU-12s over SHDSL mapped links. The Enhanced NTU ETH LAN port PM counters are available via the QD2-Lite extension. The Ethernet traffic bandwidth is optimized by GFP-F encapsulation and VC-12-Xv virtual concatenation using LCAS.
When an NTU works in V-LAN bridge mode (IEEE802.1Q), the NTU's V-LAN table is used to assign the VID to ETH ports and WAN ports. The QD2-Lite message is only used to write to the table; a readout of the existing entries is not provided. The network element is the configuration master and retains a V-LAN table of its own. It ensures by corresponding commands that the V-LAN table in the NTU matches the V-LAN table in the AM.
Using the V-LAN Entry command, individual entries in the table can be added, modified or deleted. This command is used when individual V-LAN entries are changed by the EMS.
A table entry for a VID is deleted by a V-LAN Table Entry command in which all WAN(x) bits and LAN(x) bits are set to "0". The V-LAN Table command can be used to copy the entire V-LAN table from the AM to the NT10ETH. The entire V-LAN table is deleted by an "empty" V-LAN Table command that contains no table entry. The length of such a message is L=2.
After the restoration of an SDSL link, the NE (AM) must refresh the entire V-LAN table with the V-LAN Table command. Refreshing the V-LAN table with the V-LAN Table command is not allowed to result in the interruption of individual or of all V-LANs.
The 1643 AM/1643 AMS supports Link Pass Through (LPT) functionality via EOC commands.
Users can enable or disable LPT using the following parameters.
The 1643 AM/1643 AMS provides enhanced PM support for third party NTUs. It supports a two port Ethernet SHDSL modem (NTU) which is connected via 1 to 4 parallel TU-12s over SHDSL mapped links. The Enhanced NTU ETH LAN port PM counters are available via the QD2-Lite extension. The Ethernet traffic bandwidth is optimized by GFP-F encapsulation and VC-12-Xv virtual concatenation using LCAS.
The 1643 AM/1643 AMS supports the following NTU Ethernet QoS functions.
The 1643 AM/1643 AMS provides enhanced PM support for third party NTUs. It supports a two port Ethernet SHDSL modem (NTU) which is connected via 1 to 4 parallel TU-12s over SHDSL mapped links. The Enhanced NTU ETH LAN port PM counters are available via the QD2-Lite extension. The Ethernet traffic bandwidth is optimized by GFP-F encapsulation and VC-12-Xv virtual concatenation using LCAS.
The 1643 AM/1643 AMS can use up to four SHDSL links in parallel via z-bits to download NTU software.
The OMS of the 1643 AM/1643 AMS can be used to set user passwords for the NTU web interface.
The 1643 AM/1643 AMS provides enhanced PM support for third party NTUs. It supports a two port Ethernet SHDSL modem (NTU) which is connected via 1 to 4 parallel TU-12s over SHDSL mapped links. The Enhanced NTU ETH LAN port PM counters are available via the QD2-Lite extension. The Ethernet traffic bandwidth is optimized by GFP-F encapsulation and VC-12-Xv virtual concatenation using LCAS.
The 1643 AM/1643 AMS supports the following enhanced NTU configuration.
Enhanced NTU SDH port configuration:
Note that these configurations are supported in Release 6.0.
Enhanced NTU Ethernet port configuration
Enhanced NTU Ethernet WAN port configuration:
Note that the following configurations are supported in Release 6.0.
NTU Ethernet Bridging Configuration
The 1643 AM/1643 AMS provides enhanced PM support for third party NTUs. It supports a two port Ethernet SHDSL modem (NTU) which is connected via 1 to 4 parallel TU-12s over SHDSL mapped links. The Enhanced NTU ETH LAN port PM counters are available via the QD2-Lite extension. The Ethernet traffic bandwidth is optimized by GFP-F encapsulation and VC-12-Xv virtual concatenation using LCAS.
The 1643 AM/1643 AMS supports the following enhanced NTU alarms and status reports.
Note that dEQP, dINTB, dNAE, dDEG-N, dAIS-U, dLOP-U, dPLM-V, dTIM-V, dRDI-V, dDEG-V, and dUNEQ-V are supported in Release 6.0.
Note that dANM and dLOS are supported in Release 6.0.
Updated Encaps and VCG status: TLCR, PLCR, FOPR, TLCT, PLCT, FOPT, LOA
Note that dLOF-G, dPLM-G, SQM
The 1643 AM/1643 AMS manages an external Remote SHDSL Power Supply (RPS) box via the MDI/MDO interfaces. Note that remote power supply must be set to 'managed mode' by the DIP switch=ON in the power box.
The Alcatel-Lucent OMS can also be set to 'managed mode' for the remote power supply.
The 1643 Access Multiplexer AM/1643 Access Multiplexer Small AMS supports the following remote power supply provisioning functions.
Enable/Disable RPS related alarms (per port and not per alarm). This provisioning is used to suppress alarms generated by the RPS module.
The 1643 Access Multiplexer AM/1643 Access Multiplexer Small AMS remote power supply module supports the following alarms.
Note that the external power supply module has a maximum number of 12 SHDSL ports.
Note that the MDI interfaces 1...4 and MDO interfaces 1...4 will not function as normal when the RPS is set to managed mode.
Alcatel-Lucent – Proprietary
Use pursuant to applicable agreements