3FE-69054-AAAA-FMZZA-01-ISAM 5 - 2 Customer Release Note Generic

R5.
2
7302 ISAM
7330 ISAM FTTN
7360 ISAM FX
7356 ISAM FTTB REM
7357 ISAM FTTB SEM
7363 ISAM MX
7367 ISAM SX
Voice Package
Customer Release Note
3FE-69054-AAAA-FMZZA
Edition 01 - RL 2/Apr/2015
not permitted without written authorization from Alcatel -Lucent.
document, use and communication of its contents
All rights reserved. Passing on and copying of this
Status Proposal
Change Note
Title DOCP- ISAM R5.2

document, use and communication of its
contents not permitted without written
authorization from Alcatel-Lucent.
2/150 3FE-69054-AAAA-FMZZA
Contents
1 About this Document ...................................................................................6
2 Release Content ...........................................................................................7
2.1 Introduction ...........................................................................7
2.2 New Features.........................................................................7
2.3 Feature Discontinuation Announcements......................23
2.4 R5.2 Corrections/Improvements.......................................23
3 Delivery Information...................................................................................31
3.1 Delivered Software .............................................................31
3.2 Delivered Documentation ................................................32
3.2.1 Documentation Restrictions/Inconsistencies.....32
4 Supported Hardware..................................................................................34
5 Compatibility ..............................................................................................40
5.1 AMS-ISAM Compatibility....................................................40
5.2 TL1 and CLI...........................................................................40
5.2.1 CLI/TL1 commands & parameters phased out 41
5.3 SELT-NA Compatibility ........................................................41
6 Known Restrictions......................................................................................42
6.1 Generic Restrictions............................................................42
6.2 R5.2 Restrictions ...................................................................59
7 Migrations....................................................................................................68
8 Premium Packages ....................................................................................69
8.1 Premium Packages Equipment ........................................69
8.2 Premium Packages Connectivity.....................................71
8.3 Premium Package Applications Video...........................73
8.4 Premium Packages Applications Voice..........................74
8.4.1 Premium Package ISAM-V SIP .............................74
8.4.2 Premium Package Narrowband Integrated
Line Test Access SW ............................................................79
8.5 Premium Packages Transport ...........................................80
8.5.1 Premium Package SmartDSL AN/VN..................80
8.5.2 Per Line Management ..........................................81
8.5.3 Premium Package BB SELT Test Access SW .......81
8.5.4 Premium Package MultiDSL .................................82
Edition 01 - RL 2/Apr/2015 3/150
8.5.5 Premium Package ADSL Backwards
Compatibility .......................................................................82
not permitted without written authorization fro m Alcatel-Lucent.

8.5.6 Premium Package All Digital Loop .....................82
8.5.7 Premium Package Bonding.................................83

8.5.8 Premium Package Business DSL ..........................83
8.5.9 Premium Package Enhanced SHDSL .................83
8.5.10 Premium Package UPBO Policing.......................83
8.5.11 Premium Package Impulse Noise Sensor ..........84
8.5.12 Premium Package Smart DSL SRA ......................84
8.5.13 VDSL 30a Profile......................................................84
8.5.14 Premium Package Reference Timing Source ...84
8.5.15 Premium Package Smart DSL ARQ.....................85
8.5.16 Premium Package MELT .......................................85
8.5.17 Premium Package Green DSL .............................86
8.5.18 Premium Package Vectoring ..............................86
8.5.19 Premium Package Zero Touch Vectoring .........86
8.5.20 Premium Package Type-B PON Protection .......86
8.5.21 Premium Package 40 km Differential Distance
PON Operation ...................................................................87
8.5.22 Premium Package Ethernet OAM ......................87
9 Validated Voice Supplementary Services...............................................89
9.1 H.248 POTS Supplementary Services................................89
9.2 H.248 ISDN BA Supplementary Services ..........................90
9.3 SIP POTS Supplementary Service......................................91
10 Voice Package Performance ...................................................................92
10.1 H.248 POTS Performance ...................................................92
10.2 H.248 ISDN Performance....................................................93
10.3 SIP Performance..................................................................93
11 DSL Interoperability ....................................................................................95
11.1 CPEs for specific ISAM functionality.................................95
11.1.1 ADSL1/2/2plus Annex B support ..........................96
11.2 NVLT-C and NVLT-D ............................................................97
11.2.1 ADSL1 and ADSL2plus interop..............................97
11.2.2 VDSL2 interop .........................................................97
11.3 NVLT-G/H and NVLT-M .......................................................98
11.3.1 ADSL1, ADSL2 and ADSL2plus interop ................98
11.3.2 VDSL2 interop .........................................................98
11.4 Vectoring line cards ...........................................................99
11.4.1 Vectoring interop...................................................99
11.5 CPEs verified on performance regression versus
previous releases .......................................................................100
11.5.1 Performance Interop Test Coverage ...............100
11.5.2 ADSL Performance CPE test description ..........100
11.5.3 VDSL2 Performance CPE test description ........101
11.5.4 SHDSL Performance CPE test description ........101
11.5.5 Test result overview..............................................101
12 GPON Voice Interoperability...................................................................144
13 GPON Uplink Interoperability on 7363 ISAM MX ...................................145
14 APPENDIX : DSL IOP Policy .......................................................................146
14.1 Introduction .......................................................................146
14.2 Objective ...........................................................................146
14.3 Interoperability definition.................................................146
14.4 Policy Guidelines...............................................................146
14.5 Practical implementation................................................148
Edition 01 - RL 2/Apr/2015 5/150
1 About this Document

This document for products 7302 ISAM / 7330 ISAM FTTN / 7360
ISAM FX / 7356 ISAM FTTB REM / 7357 ISAM FTTB SEM / 7363
ISAM MX / 7367 ISAM SX / Voice Package provides
information for following software release:
ISAM R5.2.1.4.4
ISAM OFLMT R5.2.1.4.4
SHub OFLMT V1.75.0
ISAM Push-button Migration Tool V3.2.2
xVPS OFLMT R5.2.1.4.4
2 Release Content
2.1 Introduction
This document provides delivery information of the ISAM software release 5.2.
This delivery includes support for 7302 ISAM, 7330 ISAM FTTN, 7360 ISAM FX, 7356
ISAM FTTB REM, 7357 ISAM FTTB SEM, 7367 ISAM SX and 7363 ISAM MX for ETSI/MII
markets and for 7360 ISAM FX, 7356 ISAM FTTB REM and 7367 ISAM SX for ANSI-
markets.
This delivery includes support for FD, FX, SX and MX equipment practices, the XD
equipment practice was discontinued since release 4.0.
The ISAM Voice (also called ISAM-V) Package is included in this delivery.
2.2 New Features

A general description of the ISAM (Intelligent Service Access Manager) and its
features is given in the "System Description" which is part of the ISAM Customer
Documentation package.
Following table gives an overview of the new features supported in R5.2.
OAM Domain
Trace and debug (T&D) tool using SSH
Feature Content:
· CLI command to enable/disable SSH T&D (as it is the case with UDP)
· Access to T&D via SSH in order to have secure access throughout the
customer network.
o The possibility to connect T&D via UDP is still supported.
Value or Application:
· For security reasons, UDP/TCP ports are often closed on the firewalls. In
many cases, only SSH would be allowed to access the operational network.
So in case remote support in an operational network is needed by ALU
Customer Services, this can only be done via SSH.
RSSI support on NT ports on 7302 ISAM, 7330 ISAM FTTN and 7356 ISAM FTTB
Feature Content:
· Support of alarms when alarm thresholds or warning thresholds are
exceeded for temperature, supply voltage, bias current, transmit power
and receive power (see SFF-8472 (DDM)):
Edition 01 - RL 2/Apr/2015 7/150
o Alarm flags associated with transceiver temperature, supply voltage,
TX bias current, TX output power and received optical power. Alarm

flags indicate conditions likely to be associated with an in-operational
link and cause for immediate action.

o Warning flags associated with transceiver temperature, supply
voltage, TX bias current, TX output power and received optical
power. Warning flags indicate conditions outside the normally
guaranteed bounds but not necessarily causes of immediate link
failures.
· Monitoring health of link’s optical modules.
Remote TL1 user management on 7360 ISAM FX
Feature Content:
o Providing support for remote TL1 user management
o Configuration, retrieval, modification and deletion of TL1 operator
security related parameters via SNMP
· It will allow network managers, such as the AMS, to align it's TL1 user
configuration with the ISAM. TL1 user configuration, username and
password, can be handled via SNMP.
Restriction:
· Support via SNMPv3 only
Platform Domain
IS-IS functionality improvements
Feature Content:
· support for IS-IS advertising IPv4 and IPv6 routes by ISAM
· Multi topology IS-IS capability (M-ISIS) by maintaining two distinct routing
topologies for IPv4 and IPv6
· Enhanced support for IP Protocols.
Duplex IHUB support for IP routing protocols
Feature Content:
· This feature adds duplex IHUB support to ISIS and PIM-SSM protocols by
allowing Synchronization of the static and dynamic routing information
across both NTs.
· DHCPv4 and DHCPv6 states are also synchronized across NTs with this
feature
· Note that duplex IHUB support for OSPF and BGP were already supported in
ISAM.
· Enhanced support for IP Protocols.
IHUB: Increase maximum number of secondary subnets on IP interface
Feature Content:
· The IHUB supports multi-netting where multiple subnets can be configured
on the same IP interface. The subnets are configured as one primary subnet
plus a number of secondary subnets. This feature expands the number of
subnets from 16 to 256 subnets per IP interface. The system-wide limit is a
maximum of 1024 subnets.
f
Improved outage during MPLS-FRR uncontrolled NT switchover
Feature Content:
· Optimizes the synchronization between both NT cards to reduce NT
switchover outage for better performance.
· Increased availability of the system.
CPU and memory utilization retrieval on FGLT-B and FWLT-A
Feature Content:
· In order to assess the health of an ISAM node, two critical computer
resources can be monitored on GPON and TWDM-PON (NG-PON2) LT
cards:
o the actual OBC memory utilization, always enabled;
o the actual CPU load utilization, disabled by default but can be
started and stopped through the supported management interfaces.
o Was already supported on NGLT-A, NGLT-C and FGLT-A.
Restriction:
· This SW feature will automatically take effect on FGLT-B when and only
when FGLT-B HW is released at a future release.
Edition 01 - RL 2/Apr/2015 9/150
CPU load monitoring on 7363 ISAM MX & 7367 ISAM SX

Feature Content:

· In order to assess the health of a 7363 ISAM MX or 7367 ISAM SX node, its
actual CPU load utilization can be monitored:
o disabled by default
o can be started and stopped through the supported management
interfaces.
Restriction:
· On 7363 ISAM MX, the CPU load utilization reflects the average over all
cores of the multi-core CPU.
7363 ISAM MX: 8p/16p GE LT (RELT-A)
Feature Content:
· Introduction of 8/16 ports Ethernet Line Card (RELT-A) on 7363 ISAM MX
o Support of 8 GE/FE optical/electrical ports (via single channel SFP), or
16 GE optical ports by using dual channel cSFP technology
o Auto-negotiation of GE/FE speeds
o Up to 2 x 2.1G bi-dir aggregate throughput
Restrictions:
· A 7363 ISAM MX-shelf with RELT-A cards, and equipped with cSFP’s, can be
used upto a maximum ambient temperature of 60 C. If higher ambient
temperatures (upto 65C) are required, ‘intelligent fan’ mode of the MX fan
packs should be enabled on the MX system. No such restrictions apply
when only SFP‘s are used.
· Introduction of Ethernet LT deployment case on 7363 ISAM MX-6 system.
Support for synchronous Ethernet (SyncE) on 7363 MX and 7367 SX-48V
Feature Content:
· Support of SyncE solution for 7363 ISAM MX-6 as well as 7367 ISAM SX-48V
(ETSI variant with MELT):
· For 7363 ISAM MX, this means:
o SyncE-IN is supported from 1 or 2 sources, which can be freely
selected out of 3 eligible NT/NTIO ports (nt-a:xfp:1, nt-a:sfp:1 and nt-
b:xfp:1).
o With SyncE-OUT support on any of the 4 eligible ports (nt-a:xfp:1, nt-
a:sfp:1, nt-b:xfp:1 and nt-b:sfp:1).
o With NTR support on VDSL2 lines
o With support for region mode ETSI (region mode ANSI is not supported
yet)
o With support for the revertive mode (non-revertive mode is not
supported yet)
· For 7367 ISAM SX, the same applies but only one source can be selected (so
revertive mode is not applicable).
Restrictions:
· SSM is not yet supported (meaning: no SSM-IN, no SSM-OUT on NT links, no
SSM-OUT on VDSL ports, no SSM-OUT on the Ethernet LT ports).
· Scope is P2P(GE)-fed MX/SX nodes only, synchronization support for a
GPON-fed node is not yet included.
· Support is restricted to ETSI/MII only (no ANSI yet in this release)
· Deployment of services on 7363 ISAM MX and 7367 ISAM SX requiring
synchronisation.
7360 ISAM FX-12 shelf
Feature Content:
· Introduction of an optimized 7360 ISAM FX-12 shelf to fit within 19 inch racks.
All of the same functionality as other existing 7360 ISAM FX shelves (FX-16,
FX-8 and FX-4) is maintained.
Restrictions
· The 7360 ISAM FX-12 shelf is only available for the ANSI market and has
been validated with the FANT-F and FPXT-B.
· Customers can deploy a higher density 7360 ISAM FX shelf within 19 inch
racks.
DSL Domain
Edition 01 - RL 2/Apr/2015 11/150
Vectoring init time improvements: historical P-coder

Feature Content:

· Use of historical P-coder values in downstream (pre-coding) and upstream
(post-coding) if historic data is reliable.
· Configuration whether historic data is only used for Vectoring phase 2
(estimation of crosstalk into joining line) or vectoring phase 1 (estimation
and cancellation of crosstalk from joining line into active lines) and phase 2.
Restrictions:
· Vectoring phase-1 init time improvement is not supported in downstream
direction, only phase-2.
Vectoring phase-1 and phase-2 init time improvements are supported in
upstream direction.
· Historical P-coder for BLV is only supported on the 7367 ISAM SX platform.
· Reduction of vectoring init time.
Crosstalk cancelled SELT
Feature Content:
· SELT support without disturbing vectored lines, i.e. SELT preceded by Xtalk
estimation.
· Without cSELT, SELT spectrum must be limited to 2.2 MHz to not disturb the
vectoring.
o The maximum SELT frequency can be configured to a higher value
but vectoring can then only start from that higher frequency which
will lead to less performance.
· Running SELT in the same spectrum as vectoring without disturbing the
vectored lines, allows to benefit from the broader spectrum (e.g. better
detection of bridge taps).
Extension of VDSL DELT and CDA time
Feature Content:
· The CDA (carrier data) time is today defined to be available 10 seconds
after entering showtime. This has been increased to 30 seconds.
· The DELT completion time is today defined to be 180 seconds. This has been
increased to 240 seconds.
· Old timing values were ok for ADSL based transmission (up to 512 carriers).
However VDSL can go up to 4k carriers and includes more messaging
information.
· This can cause either the carrier data not to be available in time or the DELT
session to timeout.
G.997.1 counter LOSS
Feature Content:
· LOS (Loss Of Signal) Second-Line (LOSS-L): this parameter is a count of 1-
second intervals containing one or more LOS defects at near end.
· LOS Second-Line far-end (LOSS-LFE): this parameter is a count of 1-second
intervals containing one or more far-end LOS defects.
· Standard Line performance monitoring counter defined in ITU-T G.997.1
Allow L2 mode when CDA is configured
Feature Content:
· On lines where CDA (carrier data acquisition) is enabled the use of L2 is
currently disabled. As CDA is also needed for trouble shooting on lines with
L2, L2 must be allowed on lines with CDA enabled.
· As the Green initiative is promoting the use of L2 (low power mode), L2 must
be allowed on lines with CDA enabled as well.
Networking Domain
Edition 01 - RL 2/Apr/2015 13/150
7367 ISAM SX-12VP: Support of GE as uplink

Feature Content:

· Support of GE uplink on 7367 ISAM SX-12VP
· Supporting the GE uplink allows to use the SFP ONT in the SX-12VP for PON
deployments.
· Enables customers to deploy 7367 ISAM SX-12VP in Point-to-Point
deployments.
MAC learning control for NANT-A
Feature Content:
· Allow disabling MAC learning for cross-connect services (e.g. WiFi/business)
per uplink port.
Restrictions
· Combining VLAN's with mac learning enabled & mac learning disabled on
same uplink port is not supported. MAC learning will only be disabled on
network uplink (port/LAG).
· To overcome limitation of 11-12K MAC addresses on NANT-A.
Forwarding Domain
Closing feature gaps between FGLT-B and FGLT-A (Phase III)
Feature Content:
· Support of following features on FGLT-B:
o vMAC
o L2/L3 IPv4/L3 IPV6 ACL/CCL
o Upstream and downstream per sub-flow remarking/setting of p-bits
o OTDR SFP
o ToD
Restrictions
· Remaining feature gaps versus legacy GPON LTs:
o Type-B PON protection
o PPPoE Relay with MAC@ concentration
· This SW feature will automatically take effect when and only when FGLT-B
HW is released at a future release.
· Closing feature gaps between FGLT-B and FGLT-A/NGLT-C.
Add access loop encapsulation in PPPoE IA and DHCP relay
Feature Content:
· Add an option to the PPPoE IA / DHCP relay configuration allowing to insert
the Access Loop Encapsulation tag as defined per TR-101 Issue 2 R-164
o Applicable to:
§ 7363 ISAM MX and 7367 ISAM SX
o Applicable to:
§ PPPoE relay in bridged mode
§ PPPoE relay in PPPoE cross-connect
§ PPPoA-PPPoE cross-connect
§ DHCPv4 Option 82
§ DHCPv6 Option 17
§ PPPoE relay with MAC concentration
· Mandatory for some wholesale subscriber management models.
Fiber Domain
Universal dummy with fiber parking lots for LT/NTIO
Feature Content:
· Dummy with fiber parking lots that can be mounted in any unused LT or
NTIO slot of one of the following subracks: 7302 ISAM, 7330 ISAM FTTN and
7360 ISAM FX.
· Allows optical pre-cabling of the subrack via a maximum of 18 SC fiber
parking lots or 36 LC fiber parking lots.
Restriction:
· Only suited for SC or LC optical connectors
· Allows optical pre-cabling of the subrack for easier fiber management.
PON utilization & thresholds
Feature Content:
· Provides customers the capability to monitor the utilization on the PONs for
Edition 01 - RL 2/Apr/2015 15/150
capacity planning, trouble-shooting and the identification of PON
congestion. In addition to providing statistics, ISAM raises alarms when

certain thresholds are exceeded for specific PON utilization performance
monitoring counters.

· Collected PON and ONT PM statistics are retrievable via AMS, TL1 & CLI.
Additionally, a file for both PON and ONT collected performance data is
made available, for off-loading by a network entity, which can be used to
identify trends.
Restriction:
· Supported on GPON Line Cards
· Allows for long term trend analysis about the end user behaviour and helps
with decision process regarding the adequacy and re-planning of the
deployed BW capacity.
Selective Behavior of Service Continuity in ONT SW Management
Feature Content:
· An operator controlled security feature of ISAM allows prevention of any
ONT service activity, including provisioning and traffic, when that ONT is not
running the correct software provisioned by the operator.
Operator control of this feature is introduced in this release and it is
exercised on a per ISAM basis. As result of the operator choice for this
option ONTs are allowed or not allowed to continue to deliver service when
their planned SW version was modified to be different than their active SW
version.
· Allows flexibility in defining the operator preference for enabling or not this
security check.
New detection of alien ONT
Feature Content:
· When a non-PON “alien” device (e.g. 1GbE ONU) is placed on the PON
network, without knowledge or control of the primary operator, this alien
ONU is masked to existing PON ONUs on the PON, but may prevent new
PON ONUs from being able to be ranged on the PON. This feature is an
extension of the Rogue ONU tests procedures, identifying the unique
circumstances the Alien ONU causes and raising an alarm to the customer
allowing them to take action as necessary to prevent further disturbance to
the ONT network.
Restriction:
· Applicable only to GPON Line Cards
· Enhanced troubleshooting capability.
PON Id maintenance
Feature Content:
· As an installation and maintenance enhancement feature, a PON identifier
along with an indication of OLT optical transmit power are emitted to the
PON at regular intervals. Field technicians can use a (potentially hand held)
device to read this information to qualify and use the proper fiber for the
right ONT connectivity at the CPE side of the network.
Restriction:
· Applicable only to GPON Line Cards
· Enhanced installation practices.
CPE/ONT Configuration over OMCI
Feature Content:
· This feature introduces a mechanism that allows OLT to download and
activate pre-configuration files via OMCI.
· Voice OMCIv2 XML pre-configuration and Generic ONT pre-configuration
files are supported with a default pair for a HW type, as well as the possibility
to define additional files for variations in ONTs of the same HW type.
· The files are stored, downloaded, managed via AMS in the same way as
the ONT SW image files are.
Restriction:
· Per end-user configuration aspects are not covered.
· Reduced complexity of ONT Configuration in the absence of TR-69
mechanism
DPoE Domain
IPv6 Data transport for DPoE
Edition 01 - RL 2/Apr/2015 17/150
Feature Content:

· This feature provides the ability for DPoE provisioned ONUs to transport IPv6
packets appropriately. In particular, this feature provides the following:

o Configuration of the IP Mode (IPv4 / IPv6 / Dual-Stack) for each IP
Serving Group (IP-SG)
o IPv6 connection setup using DHCPv6 and a Lightweight DHCPv6
Relay Agent on the EPON line cards
o Use of the default circuit-id syntax used in DHCPv6 Interface-ID
(Option 18)
o Support for IPv6 classifiers: TLVs 22/23.12.1-7, drop classifiers 60.12.1-7
and ICMPv4/ICMPv6 classifiers in TLVs 22/23.16.
o Support for downstream IPv6 multicast control traffic, i.e. replicating
control packets to multiple unicast EPON LLIDs
Applicability:
· Applicable to the 1G EPON (FPLT-A) and 10G EPON (FPXT-B) LTs
· Applicable management interfaces: Supported via TLV configuration files
and CLI
Restrictions:
· The chipset of the XE-040G-A does not support IPv6 next-header/ICMP
classification in UDC/UC.
· TK3714 ONUs do not support IPv6 traffic classification on ICMP in UDC/UC,
next header does not support 256,257 correctly
Ability to have multiple IPHSD service Flows with same orig IP@ and MAC@
Feature Content:
· Based on the DPoE specification and MSO customers’ requirement of
multiple IPHSD service flows that are classified by TOS/DSCP bits and IP
protocol types from the same originating IP address and Mac address. This
feature provides the ability for the Alcatel-Lucent 7360 ISAM FX operating in
a DPoE configuration to classify traffic coming from a common IP and MAC
address into the proper queues and LLIDs based on the TOS/DSCP bit and
other classifier values. These may be from the same UNI port on the ONU or
from different UNI ports on the ONU. In the RG case there is only one UNI for
the ONU. Other UNIs may be in the RG but they are behind the RG function
and appear on the same UNI to the ONU function. They can be from the
same IPSG or on multiple IPSGs.
Applicability:
and CLI
Restrictions and Assumptions:
· Since MEF services are not IPHSD services this feature does not apply to
multiple MEF service flows at this time.
· This feature supports a maximum of 16 service flows (8 US and 8 DS) service
flows per SFG (service flow group). A service flow group is a set of service
flows. applicable to a particular UNI port on an ONU. Remember that in the
case where an ONU is integrated with the RG that all of the traffic from an
ONU will appear on one UNI to the ONU function.
· The FPXT-B downstream classifier supports an IPv6 prefix length range of 0-
64bits,>64bits is treated as 64bits. An FPXT-B downstream classifier of a 128bit
IPv6 address is not available.
· Each classifier rule only allows one classifier to be defined as a range.
DPoE SAV Phase 1
Feature Content:
· The Source Address Verification (SAV) feature is used to verify that the
source IP address of upstream packets is provisioned or allowed by the
service provider, i.e the anti-spoofing functionality based on DHCP assigned
IP addresses or statically configured IP addresses.
Applicability:
and CLI

· SAV prefix length supports ranging from /48bits to /64bits and an individual
length of /128bits. Registrations for SAV prefix lengths less than 47 bits and
from 64 to 127 bits are rejected and logged in the dml.log.
· SAV does not currently survive an LT card being removed and reinserted.
The end user will have to reinitiate a DHCP request in the event of an LT
removal or a power off situation. Persistency after an LT warm reset and an
NT reset is supported.
· The FPLT-A has resource limitations that will allow the SAV feature to have
eleven IPv4 addresses per SFG, six IPv6 addresses per SFG and in a dual
stack mode have six IPv4 anddresses and four IPv6 addresses.
Edition 01 - RL 2/Apr/2015 19/150
DPoE VACM: add support for symbolic object ids

Feature Content:

· This feature provides a hybrid MIB OID in an SNMP query and response
allowing the OID to be partially alphabetic and partially numeric instead of
only the numeric representation of the OID. The feature enhances the SNMP
ACL function.
· Translate DPoE and Ethernet MIB oids to MIB node name for display.
MSO CLI Improvements Phase 1
Feature Content:
· This feature provides improvements to the MSO CLI of the 7360 ISAM FX to
make the CLI commands more consistent to the user.
The specific improvements include:
1) 'info configure cmts' and 'info configure cm' commands now output the
entire configuration of the cmts node and the cm node respectfully. In
addition, the 'configure cmts<CR>info' and 'configure cm<CR>info'
syntax is also be supported
2) 'info configure <node> <subnode>' has been augmented to work for all
subnodes. For example 'info configure cmts bundle’ must output all
bundles. 'info configure cmts bundle 1' and 'configure cmts bundle
1<CR>info' now output all config info for bundle 1. Subnode info
support has been extended to all cmts and cm subnotes.
3) 'info configure' now produces a complete concatenated configuration
dump of all nodes on the system
4) Context sensitive help in the DPoE portion of the system is now output in
alphabetical order (ignoring any option [no] prefixes).
5) Removal of unimplemented commands, parameters and counters.
Restriction:
· Does not support ‘info’ in ‘leaf’ node in the R5.2 release.
TACACS+ Phase 1
Feature Content:
· TACACS+ Phase 1 is the implementation of the accounting of craft
commands using the TACACS+ protocol. Authentication and authorization
is performed using the Radius protocol. Authentication and authorization
using TACACS+ will be delivered in a later release.
End of support for DHCP Relay on DPoE subsystem
Feature Content:
· DHCP relay for vCMs has been moved to the IHUB subsystem in the 7360
ISAM FX from the DPoE subsystem. This was done to simplify configuration
and reduce the number of DHCP relay agents needed inside the 7360 ISAM
FX as requested by the customer base. Release 5.1.01 supports both
implementations to accommodate the transition to the new architecture.
This feature checks to see if the change has been made before an
upgrade to R5.2 can be performed as the older configuration is no longer
supported. This constraints is applicable both for IPv4 and IPv6

· The check only checks to see if the change was made in the DPoE
subsystem and does not check the associated changes in the IHUB
subsystem. The operator should check the IHUB configuration manually.
DPoE: Text based config file dump & restore for the
IPD and DPoE subsystems
Feature Content:
· This feature allows the user to upload a snapshot of the IPD and DPoE
subsystem database in readable text ASCII-format from an ISAM OLT shelf
to a remote server via TFTP. This database text file could be edited to
modify/add various parameters such as the OLT shelf’s IP address, DHCP
server, cable modem service configuration, etc., and then re-download it
back onto to a new or the same shelf and apply it. As a result, this method
could be used to create a golden configuration database text file to be
used to speed up new system turn-up time with little effort. A second use
case for this feature would be that the database text file could be used for
auditing purpose.
Restrictions:
· This feature assumes the new shelf is running the same SW version as the
reference system and it can reach a TFTP server.
· Base platform configuration such as what cards are in the system, SNMP
configuration, Syslog, System time, Clock, NTP, TACACS+ and RADIUS
configurations. That provisioning must be done manually or with separate
scripts.
Voice Services Domain
Edition 01 - RL 2/Apr/2015 21/150
ISAM-V H.248: T.38 MSAN to use voice UDP port

Feature Content:

· ISAM-V H.248 to reuse the same voice UDP port for T.38 transmission and this
behaviour is CDE configurable.
Restriction:
· NPOT-A is not supported.
· This feature enables ISAM-V H.248 to support those MGCs requiring MSANs
to reuse the G.711 UDP port for the T.38 transmission.
ISAM-V H.248: Show IP@ and port info when showing list of MGC/ASP
Feature Content:
· Adding the IP address and UDP port to the Voice Megaco MGI Status
command &
· adding the IP address and SCTP port to the Voice Megaco SGI Status
command
ISAM-V SIP: Subscriber controlled active/de-active CW
Feature Content:
· Support per line subscriber controlled active/de-active CW (Call Waiting),
provisional by VGW on SIP CVP based ISAM-V per ONT
· Subscriber control behaviour is per line configurable via CLI
· Service codes & tones for user control is CDE file configurable
· User shall hear indication tones after dial service codes
7363 ISAM MX-6 SIP: Support multiple Virtual Access Gateway (VAG)
Feature Content:
· Support of multiple VAGs on the 7363 ISAM MX-6 SIP centralized IP@ mode
Restrictions
· Support for a maximum of 4 VAGs
· All VAGs share the same signaling VLAN
· All VAGs share the same media VLAN
· All VAGs share the same Network call flows
· All VAGs share the same SIP configuration parameters
· Neither DHCP nor DNS support required
· Different subscribers on the same 7363 ISAM MX-6 node can be connected
to different SIP servers.
2.3 Feature Discontinuation Announcements
Also the PON Feeder Protection feature has been discontinued since R4.4. It has
been replaced by the enhanced Type-B Protection from R4.4.02 onwards. This
new feature allows protection of any PON link with any other across the shelf on a
different line card.
From R4.5 onwards the support of GPON with NANT-D has been deprecated.
From R4.6.02 onwards the support of the ADSL/ADSL2 Downstream PSD shaping
and ADSL Artificial noise features have been discontinued.
The ANCP/L2CP implementation was according to the pre-standard ietf-draft-
wadhwa and did not evolve to the standard RCF6320. From R5.1 onwards,
ANCP/L2CP is not supported anymore.
2.4 R5.2 Corrections/Improvements

Nr Id Rel.note entry
7363_Equipment
1 ALU02025842 Title: Restart time does not change when resetting RANT-A
Problem: When forcing the RANT-A reset, the last restart time value is
not updated.
7363_L2 Forwarding
Edition 01 - RL 2/Apr/2015 23/150
2 ALU02057965 Title: PPPoE traffic is not established for ATM AAL5 encapsulation type
Autodetect PPP
Problem: If an xDSL port on RDLT-A/B is configured with Transfer

Mode=ATM, AAL5 Encapsulation Detection = Auto Detect PPP (VCL =

8/35) and a PPP CC is created, then PPPoE sessions never get

established.
3 ALU02047266 Title: 7363 ISAM MX PtP: PPPoE PADI send from network port over CC is
discarded
Problem: A point-to-point PPPoE PADI on the 7363 ISAM MX sent from
the network port over CC is discarded.
4 ALU02048027 Title: L2CP forwarding issue on 7363 ISAM MX-6
Problem: Most of the L2CP (Layer 2 Control Protocol) messages are
not forwarded on the 7363 ISAM MX-6 even if l2cp-transparent is
configured for cross-connection.
7367_OAM
5 ALU02031027 Title: 7367: when default-ttl is modified then the mgmt ip address data
is lost
Problem: It was not possible to configure the ttl. The solution that has
been provided is to make the configuration of the ttl a separate
command from the configuration of the IP address. The new
command: configure system management default-ttl.
CLI
6 ALU02022887 Title: Can't login in CLI after changing the CLI password
Problem: The use of control characters in the CLI password will block
you to login in CLI next time
DPoE
7 ALU02018069 Title: Multiple NT Switchovers causing 2-3 minute traffic outage
Problem: Do two or more NT switchover, causing outages of 2-3
minutes. The error logs indicate that DPoE is unreachable, triggering a
warm reset.
8 ALU02062147 Title: Dpoe plt configuration lose after NT switch over
Problem: After migration from ISR4501h to ISR52, then enable DPOE
PLT,, the DPOE plt configuration lost after do switchover FANT-F.
9 ALU02020180 Title: ONU goes off-line when traffic passes through 8 IPHSD bi-
directional traffic flows
Problem: Configure 8 IPHSD service flow on ONU, after ONU get
online, send 8 IPHSD bi-directional traffic, then the ONU go to offline.
10 ALU02031462 Title: "show cable modem" output in release R5.1 show different
compare to R5.0 or lower
Problem: In R5.1 release, the output of "show cable modem" only
show half of information relate to ONU. The system added a column
for IPv6 info, but the rest of the information such as CPE, Rx power
level, EAE enable, and speed mode are no longer show
Ethernet
11 ALU02049090 Title: Actual line rate not set correctly on NELT-A
Problem: Actual line rate not set correctly on NELT-A
12 ALU02032747 Title: Wrong counter value on NELT-B when port operational down
Problem: Some counters show wrong values when a port is
operational down but in admin-state up.
13 ALU01978603 Title: Show ethernet mau is giving output for all ports
Problem: On 7360 FX, the command "show ethernet mau" is supposed
to list all ports regardless being empty or not for NELT-B boards but not
showing all.
14 ALU02051871 Title: Combo ports do not accept the configuration "no autonegotiate"
Problem: Ncnc-d combo ports do not accept "no autonegotiate"

with NANT-E
Equipment
15 ALU02036746 Title: 7330 RA: NT reset HM_T mpc_exception.c
Problem: Several NT resets on 2 different nodes
16 ALU02029204 Title: Powered down NDPS-B generates flapping board missing alarm
Problem: Powered down NDPS-B generates flapping board missing

alarm
17 ALU02044374 Title: NANT-E displays invalid temperature values
Problem: On rare occasions invalid temperature values (65544) are
reported for NANT-E
18 ALU02056910 Title: NT can not read the shelf remote inventory
Problem: In a few instances, it was noticed that the NT fails to read
the remote inventory of the shelf
19 ALU01950371 Title: SFP type is not reported correct but reported unknown
Problem: SFP type is not being reported correctly with ISAM FD for
NANT-E,NCNC-D and NELT-B where as it is ok in FX
20 ALU02035620 Title: No warning when the max-lt-link-speed is set to 10Gbps
Problem: A FGLT-A board needs at least a LT link speed of 20Gbps to
use all PONs. If only 10Gbps is configured in a 7360 FX system, then
only the first 8 PONs will work as expected. No warning is given when
configuring LT link speed to less than 20 Gbps.
21 ALU02056565 Title: Configure system auto-laser-shutdown action disable is not
functional
Problem: The "issue" detected in Rel 4.2 is disturbing, because it is used
to measure the TX power to check if the ISAM /fibers are OK.
GPON OLT
22 ALU02001796 Title: FGLT-A Cayenne CRC Error
Problem: In rare cases, traffic loss can be detected on FGLT-A board.
After an LT reboot the issue disappears.
23 ALU02032483 Title: Failed to get ONT info for some specific ONT ID
Problem: Can't get the ONT info (e.g. sw-ver and optical info, etc) for
some specific ONT ID. After changing the ONT ID to another value, it
will work fine.
24 ALU02045417 Title: "ADSL2+ Spectrum not Allowed" does not work
Problem: Even if "ADSL2+ Spectrum not Allowed" is configured in
GPON XDSL Line Spectrum Profiles, MDU still transmitted in the band
up to 2208 kHz.
GPON ONT
25 ALU02026251 Title: Last change date of VEIP port and ONT Ethernet port are not
correct
Problem: The Last change date value of VEIP port and ONT Ethernet
port cannot be correctly shown on AMS GUI, these two values will not
be changed even when VEIP port or ETH port operational state is
changed to down and up.
26 ALU02050747 Title: Status is showing OOS-AU, while the E1 traffic is up
Edition 01 - RL 2/Apr/2015 25/150
Problem: Status is showing OOS-AU, while the E1 traffic is up
H248
27 ALU02053393 Title: Few H.248 Parameters Become Default after Migration

Problem: After migration, followed parameters become to the

default: event-req-id 32, al-of-evt, al-on-evt, al-of-strict-evt, al-on-
strict-evt
L2 Forwarding
28 ALU02023975 Title: Bridge port configuration of neighbour port on NELT-B interrupts
the traffic
Problem: Neighbour port bridge, vlan configuration on NELT-B
interrupts the user traffic .
29 ALU02034467 Title: No MAC address learned on a specific NALT-E port although line
synched
Problem: Some end-users that are not being able to obtain an IP
address although their line is in synch. Investigation revealed that no
MAC address is learned on this port (other ports conencted to the
same NALT-E seem OK) until the NALT-E is reset.
30 ALU02044014 Title: ISAM is blocking DHCP RENEW ACK messages to the CPE
Problem: ISAM is blocking DHCP RENEW ACK messages to the CPE.
This causes a new session to be started.
31 ALU02028632 Title: Pkt drop occurred in IHUB NT port when downstream traffic more
than 10Gbps
Problem: Pkt drop occurred in IHUB NT port when downstream traffic
more than 10Gbps
32 ALU02055036 Title: Ppp session is going down due to session-age-out
Problem: We see a session-age-out increase on the moment the ppp
session is going down, normally this means thereis received no
downstream traffic for an amount of time bigger than the configured
cc-max-age.
33 ALU02012200 Title: Error "referred instance does not exist " might occur when
configuring multiple vlans on all lines of NELT-B
Problem: While trying to configure multiple vlans on all lines of a NELT-
B the error "referred instance does not exist " might occur on some
lines
34 ALU02020861 Title: Retrieving pppCcEngineTable OIDs very slow
Problem: On the redundant ISAM (2xNANT-A, 16xnalt-c) set, through
AMS retrieving pppCcEngineTable OIDs very slow
L3 Forwarding
35 ALU02015166 Title: Filters on IES interfaces not behaving correctly
Problem: Ingress filters are matching in both directions when applied
to IES interfaces. They should only apply to customer (PON) traffic
coming upstream and not match on downstream traffic coming from
northbound towards the customer.
MPLS
36 ALU02055186 Title: Broadcast arp messages are flooded using VPLS service
Problem: On duplex NT platform, broadcast arp messages will be
wrongly flooded using VPLS service. Such issue does not exist on
simplex NT platform.
37 ALU02058772 Title: MPLS Traffic Dropped
Problem: In MPLS network configurations involving a third party routers
as head-end for a ring topology, there is a MPLS Explicit NULL label
operation issue when ISAM is acting as LSR. As a consequence traffic
traversing this ISAM is being dropped. When ISAM acts as LER, no issue
is seen.
38 ALU02028617 Title: Downstream loss when traffic load is more than 10Gbps
Problem: Downstream traffic loss can be detected on IHUB based NT
(NANT-D, NANT-E, FANT-F) when total traffic is more than 10Gbps while
NT uplink is 2X10G LAG port.
Migration
39 ALU02021041 Title: XDSL User labels removed for NVLT-N After Migration to 4.6.03b
Problem: While migrating a A4.100 database with NVLT-N

configuration to C4.602 using OFLMT and the MJSH.exe for 4.6.03b,
the XDSL user labels are removed
40 ALU02034414 Title: ONT POTS ports oper-status disable after upgrading
Problem: After upgrading from 4.4 to 5.0.01 or higher, initially only a
few ONT POTS ports reported a minor alarm (Configuration Or
Customization Error) then almost all the services on the node report
this alarm. Even though operational status is done for POTS port,
service is not impacted.
41 ALU02034821 Title: ISAM unreachable after software activation with a dedicated
linked database
Problem: After the migration from R4.2.05e to R4.6.02a, it happens,
that the iSAM becomes unreachable. A technician has then to
manually reset the iSAM.
42 ALU02058761 Title: NVLT-S boards detected faulty after SW upgrade
Problem: NVLT-S boards are detected faulty after SW upgrade. Also
not recovered after Software Downgrade.
43 ALU02020578 Title: PBMT: MIGR_result file not updated when nodes is unreachable
after activation
Problem: MIGR_result file not updated with meaningful failure code
when node is isolated after activation
44 ALU02024018 Title: 7353 managament lost from 7360 ISAM
Problem: During migration from R4.5.0x, the IPHOST state was set
incorrectly, resulting in a loss of management
45 ALU02024021 Title: OLT not displaying the correct RF video status information
Problem: After migration, the RF video status information is wrongly
interpreted by the OLT
46 ALU02042868 Title: Some nodes unreachable after upgrade to R4.5.03l
Problem: The operator can lose the management of some of their
nodes (no IP connectivity anymore) after an upgrade from R4.5.02a
(45.295) to R4.5.03l (45.564).
47 ALU02042974 Title: OFLMT fails on 7363 MX database
Problem: OFLMT fails on 7363 MX database for RANT-A.
Multicast
48 ALU02024271 Title: MLD packet downstream is causing a high load on NSLT-A
Problem: Sending ipv6 MLD packets continuously above 600 frame
size causes high CPU load
49 ALU01996277 Title: Creating a router igmp interface causes loss of eqpt prot
Edition 01 - RL 2/Apr/2015 27/150
Problem: Creating a router igmp interface before shutting down
igmp-snooping in VPLS causes loss of eqpt prot
OAM

50 ALU02054526 Title: OLT node overloaded by alarms

Problem: Alarm soaking is not applied. In case of excessive toggling
alarms, this results in an overloaded system and could end up in a not
reachable system.
51 ALU02023807 Title: "exit all" sometimes produces two prompts
Problem: The command "exit all" sometimes produces two prompts.
This malfunction could affect external OSS systems
52 ALU02033773 Title: ISAM accepts faulty QoS configuration from AMS
Problem: Invalid QoS configuration by AMS, for dot1p parameter and
QoS Policy Profile, is accepted by ISAM causing NE failure. Problem
does not exist for CLI.
53 ALU02038391 Title: NANT-D: iHub communication lost alarm
Problem: The alarm is triggered due to parity issue in BCM L2 table.
54 ALU02045393 Title: Migration fails when invalid egress-rate is configured
Problem: Via SNMP it is possible to configure the egress-rate wrongly.
In that case, migration to a newer release will fail.
55 ALU02056771 Title: CES service ONT-controlled Maximum jitter buffer (i.e. value 0)
not accepted
Problem: When creating the CES maintenance profile, which specifies
the maximum depth of the jitter buffer, the value "0" (implies that the
MJB is under control of the ONT) is not accepted
56 ALU01981424 Title: Up-inv-prot of Trouble shooting counters are not working
Problem: Frames discarded due to protocol-filter which are IPv6 traffic
are shown in up-inv-prot
57 ALU02023415 Title: Protocol wildcard in CPU filter does not work
Problem: Wildcard feature is not supported for CPU filter. When the
protocol filter is set to udp, the dropped packet counter increases.
But, when the filter is set to * (udp+tcp), the counter does not
increase.
58 ALU02026902 Title: Same VLAN ID wrongly configured for both internal-nw-vlan and
ntr-ssmout-vlan
Problem: When configuring internal-nw-vlan with the same value of
ntr-ssmout-vlan, the first time CLI will return error prompt, this is
expected. However, for the second time, the configuration is
accepted without any error, this behavior should be wrong.
59 ALU02052943 Title: Incorrect RSSI attributes are shown for some ONT types
Problem: Wrong wavelengths are shown for some ONT types
60 ALU02059168 Title: Admin transaction configure-lock acquire does not work
Problem: The CLI command is failing because not supported
anymore. However for backward compatibility reasons, it should be
changed so that the CLI command has no impact anymore.
Redundancy
61 ALU02023709 Title: Gateway not reachable after switchover
Problem: After switchover the LAG datastructure is updated only with
the break information and not the recovery.
62 ALU02024556 Title: Bulk sync failure alarm is not getting cleared
Problem: After spontaneous reset of NGLT-A, a BulkSync Failed alarm is
raised. Reconfiguring the PG, rebooting the LT does not clear the
alarm.
SIP
63 ALU02048739 Title: Voice LT Sporadic Reset
Problem: NPOT-B/C spontaneous autonomeous resets while receving
the DNS query response with TTL=0.
64 ALU02027921 Title: Interrupted Announcement that Called Party is not available
Problem: In call scenario where the called party does not answer, an
early-media announcement was not being correctly played
(announcement was interrupted after approximate 0.5 sec).
65 ALU02036382 Title: Wrong Digitmap Processing on S#
Problem: Incorrect parsing of dialled digits when Digitmap entry was
configured that has S# (digits to be handled locally on the Voice
card).
66 ALU02044247 Title: Wrong ringing signal for NPOT-A when CLIP service is disabled for
SIP account on IMS server
Problem: When the FROM header contains NULL information for the
display name and the display number in the received UNSUBSCRIBE,
the called party connected to an NPOT-A could hear only one ring,
as incorrect CLIP processing interrupted the playout of the ringing
signal.
67 ALU02055455 Title: SDP Version Not Increased when receving an INVITE without SDP
Problem: When ISAM-v receives INVITE without SDP, it will build up new
SDP with all codecs. While in such case it is expected that the
indicated SDP version should increase with one based on the latest
local SDP version, the SDP version was reset to 0, which is incorrect.
Security
68 ALU02023702 Title: Attacks causing ECNT-C/NANT-A warm resets
Problem: ECNT-C/NANT-A warm resets when a tcp packet with bogus
header (less than 20 bytes) is encountered
69 ALU02056349 Title: 802.1x userport authentication failure
Problem: For several userports 802.1x authentication fails
70 ALU02056366 Title: 802.1x userport authentication outage
Problem: Wrong Radpolicy configuration leads to 802.1x
authentication outage
Synchronisation
71 ALU02049119 Title: BITSSHUTOFF alarm pointing to unexisting R0.S0
Problem: When migrating a node from R4.4 to R5.1.01b, the
BITSSHUTOFF alarm is raised. However The source name is incorrectly
pointing to (not existing) R0.S0 at the AMS Gui: BITS SHUTOFF:xxx-
xx:R0.S0.NTA.BITSOUT
72 ALU02018242 Title: VLAN configuration for ntr-ssmout-vlan is allowed has wrong
range
Problem: Ntr-ssmout-vlan parameter for VLAN configuration is defined
to accept the value range 0..4093. 0 is not a valid value.
VDSL
73 ALU02032009 Title: Vectored lines unable to sync (AR1-5295183)
Problem: VCE was unable to disable bitswap for one of the lines while
joining a pool of lines and the joining process got stuck.
74 ALU02037542 Title: US Attainable bit rate is too high when CPE reports very low
attainable bit rate up
Edition 01 - RL 2/Apr/2015 29/150
Problem: In some cases, the US Attainable bit rate is too high when
the CPE is reporting a very low attainable bit rate in US (e.g. CPE side
US attainable bitrate is only 10Kbps and CO CLI shows attainable bit

rate is >95Mbps).

75 ALU02038911 Title: BCM Device watchdog reset causes LT reset

Problem: When a BCM Device watchdog times out, the full LT
containing that BCM device will reset.
76 ALU02049054 Title: During very high protocol load over longer time, vectored lines
might lose sync and not train anymore (they are blocked)
Problem: Due to loss of packets in the ISAM system, there is a
mismatch between training states at VP side and DSP side. As a result,
they are both blocked and waiting for action of the other party.
77 ALU02058900 Title: Some ZTV lines are unable to sync after a while
Problem: It was observed that sometimes ZTV lines after a while are
unable to sync
XDSL
78 ALU02048940 Title: Deploy template group that contains many profiles fails on MX
Problem: Deploy template group that contains many profiles fails on

MX
79 ALU02049061 Title: EFM-bridge of bonding group reported as "operational-down"
although it is actually up and running with one line
Problem: When the group is up and running with the non master line
only and the primary line is down. The upper layers (like EFM bridge )
receieve an operational down.
3 Delivery Information
3.1 Delivered Software
Delivery Note = ALU02063650
Alcatel-Lucent Item Description
Number
SWPA 3FE 71675 AAAA SWPA-ISAM R52.1.4.4
Tar file: L6GQAA52.144.tar
CDE profile
M113AA52.001.tar
SWPA 3FE 25412 AAAA OFLMT (ISAM)
tar file: MLXAAA52.144.tgz
SWPA 3FE 61499 AAAA OFLMT (xVPS)
tar file: NBTTAA52.144.tgz
SWPA 3FE 25709 AAAA OFLMT (SHub)
tar file: Lanx_Migration_Tool1.75.0.tgz
SWPA 3FE 28567 AAAA Push-button Migration Tool (PBMT)
Operational code: migrateIsam.3.2.2.tar.gz
DOCP 3HH 12973 AAAA DOCP- ISAM R5.2 CD-ROM
Customer Software Delivery Package
Note Boards with software preinstalled in EPROMs are released

as Functional PBAs (FPBA). An FPBA groups a certain HW
release with a certain software release. The FPBA is only
meaningful for the non-downloadable software. It is the
operator's responsibility to download the correct
operational software version.
Note The version of the PBMT SW mentioned above, is the latest
version available at the moment of the ISAM DR4.
However it is highly recommended to perform the
migration with the latest version of the PBMT available. The
latest version of the PBMT SW can be downloaded from
the server ‘www.alcatel-lucent.com‘.
Note From R4.3.02 on, FOSS (Free and Open Source SW) is part
of the ISAM product. A license note containing a list of all
used FOSS and all relevant licenses is part of the SW-
package.
Edition 01 - RL 2/Apr/2015 31/150
3.2 Delivered Documentation

Number
DOCP 3HH 11970 EAAA DOCP-7302 ISAM R5.2 CD-Package (ETSI/MII)
Customer Documentation
DOCP 3HH 11971 EAAA DOCP-7330 ISAM FTTN ETSI R5.2 CD-Package (ETSI/MII)
DOCP 3HH 11972 EAAA DOCP-7360 ISAM FX R5.2 CD-Package (ETSI/MII)
DOCP 3HH 11973 EAAA DOCP-7356 ISAM FTTB REM R5.2 CD-Package (ETSI/MII)
DOCP 3HH 11974 CAAA DOCP-7357 ISAM FTTB SEM R5.1 CD-Package
DOCP 3HH 12263 EAAA DOCP-7367 ISAM SX R5.2 CD-Package (ETSI/MII)
DOCP 3HH 12278 EAAA DOCP-7363 ISAM MX R5.2 CD-Package
DOCP 3FE-45141-AAAA-PMZZA DOCP-7360 ISAM FX R5.2 CD-Package (ANSI)
DOCP 3FE-45127-AAAA-PMZZA DOCP-7356 ISAM FTTB R5.2 CD-Package (ANSI)
DOCP 3FE-45142-AAAA-PMZZA DOCP-7367 ISAM SX R5.2 CD-Package (ANSI)
3.2.1 Documentation Restrictions/Inconsistencies
„ For the ANSI-market, intelligent fan trays (BFANs) have been documented
since previous releases in the 7360 ISAM FX ANSI documentation set, but
they have not been fully tested for horizontal mounting options.
„ Although already documented in the R5.2 customer documentation, next
HW-items are not yet supported in this release:
· the FGLT-B LT board
· The local DC-powered version of the ANSI 7367 ISAM SX-12VP (3FE-
69098-BA)
„ Although already documented in the R5.2 customer documentation, next
features are not yet supported in this release:
· Duplex mode for 802.1x authentication
„ In order to allow for provisioning efficiency of Multicast Source
configurations, the command "configure mcast chn", which makes use of
the multicast ranging feature, should be used rather than the older
(obsoleted) "configure mcast channel" command. This is not properly
documented in the customer OAM guides of this release, but will be
added from next release on.
„ ANCP/L2CP is not supported anymore (see section 2.3), and any remaining
text on ANCP/L2CP descriptions, CLI commands, TL1 commands, etc) in
the customer documentation should be considered as obsolete or mistake.
Edition 01 - RL 2/Apr/2015 33/150
4 Supported Hardware

Below list gives an overview of the supported ISAM Network Termination (NT) and

Line Termination (LT) boards in the 7302 ISAM, 7330 ISAM FTTN, 7356 ISAM FTTB
REM, 7360 ISAM FX and 7363 ISAM MX systems. It doesn't pretend to be an
exhaustive list of all existing ISAM HW boards.
For a complete list of all supported board(type)s per product, please refer to the
product information manual of that specific product.
For the 7357 ISAM FTTB SEM and 7367 ISAM SX systems, the supported shelf HW-
items are listed at the bottom of this list.

Number
NTs
FPBA 3FE-26698-AA FPBA-NANT-A
FD Network Termination without BITS interface
FPBA 3FE-26698-DA FPBA-NANT-A
FD Network Termination with daisy-chaining, no BITS
FPBA 3FE-26698-AB FPBA-NANT-A
FD Network Termination with BITS interface
FPBA 3FE-26698-DB FPBA-NANT-A
FD Network Termination with daisy-chaining & BITS support
FPBA 3FE-61555-AA FPBA-NANT-D
FD 100Gbps Network Termination without BITS or SyncE
interface
FPBA 3FE-61555-AB FPBA-NANT-D
FD 100Gbps Network Termination with BITS & SyncE interfaces
FPBA 3FE-61555-CB FPBA-NANT-D
FD 100Gbps Network Termination with BITS & SyncE interfaces &
MPLS labeling
FPBA 3FE-64746-AA/BA FPBA-NANT-E
FD 320Gbps Network Termination
FPBA 3FE-64746-AB/BB FPBA-NANT-E
FD 320Gbps Network Termination with BITS & SyncE interfaces
FPBA 3FE-53701-AA FPBA-FANT-F (ETSI/MII)
FX 480Gbps Network Termination
FPBA 3FE-53701-AC FPBA-FANT-F (ETSI/MII)
FX 480Gbps Network Termination with BITS & SyncE interfaces
FPBA 3FE-53701-AD FPBA-FANT-F (ETSI/MII)
FPBA 3FE-53701-BD FPBA-FANT-F (ANSI)
FPBA 3FE-64398-AA FPBA-NRNT-A
7356 ISAM FTTB REM Network Termination with Synchronous
Ethernet
FPBA 3FE-68339-AB FPBA-RANT-A
7363 ISAM MX NT with integrated SLV support
RSA 3FE-29506-AC RSA-ERAM-A
Remote Aggregator with BITS interface containing combined
NT/NTIO (AGNT-A)
LTs/Service boards
FPBA 3FE-64279-AA FPBA-NGLT-A
8 port GPON LT
FPBA 3FE-67301-AA FPBA-NGLT-C
8 port GPON LT
FPBA 3FE-28682-AA FPBA -NELT-A
FD Ethernet LT, 16lines
FPBA 3FE-62543-AA FPBA -NELT-B
FD Ethernet LT, 36lines
FPBA 3FE-53711-AA FPBA-FPLT-A
FX EPON LT 8 port
FPBA 3FE-66876-AA FPBA-FPXT-A
FX 4 port 10G EPON LT
FPBA 3FE-68788-AA FPBA-FPXT-B
FX 8 port 10G EPON LT (not for Chinese markets in this release)
FPBA 3FE-27289-AA/AB FPBA -NALT-C
FD ADSL2plus POTS LT
FPBA 3FE-27289-BA/BB FPBA -NALT-D
FD ADSL2plus ISDN LT
FPBA 3FE-29512-AA/AB FPBA -NALT-E
FD MultiDSL POTS LT 72 lines
FPBA 3FE-61438-AA/BA/AE/BE FPBA -NALT-J
FD ADSL POTS LT 48 lines
FPBA 3FE-61584-BA/BF FPBA -NALT-K
FD ADSL ISDN LT 48 lines
FPBA 3FE-63767-AB FPBA-NALT-L
FD MultiDSL POTS LT 48 lines outdoor
FPBA 3FE-63767-BB FPBA-NALT-L
FD MultiDSL POTS LT 48 lines CO
FPBA 3FE-63423-AA FPBA-NALT-M
FD 72 PORTS ADSL WITH ILTF/MELT
FPBA 3FE-00139-AA/BA FPBA-NVLT-C
Edition 01 - RL 2/Apr/2015 35/150
FD VDSL2 ADSL2plus POTS LT 48 lines
FPBA 3FE-00140-AA/BA FPBA-NVLT-D

FD VDSL2 ADSL2plus ISDN LT 48 lines

FPBA 3FE-00162-AA/AB FPBA-NVLT-G

FD VDSL2 ADSL2plus POTS LT 48 lines (2,5 Gbps)
FPBA 3FE-00161-AA/AB FPBA-NVLT-H
FD VDSL2 ADSL2plus ISDN LT 48 lines (2,5 Gbps)
FPBA 3FE-63358-AA FPBA-NVLT-M
FD 48 PORTS VDSL WITH ILTF/MELT
FPBA 3FE-64331-AA FPBA-NVLT-P
FD VDSL2 ADSL2plus POTS LT 48 lines (2,5 Gbps)
FPBA 3FE-64332-AA FPBA-NVLT-Q
FD VDSL2 ADSL2plus ISDN LT 48 lines (2,5 Gbps)
FPBA 3FE-64333-AA FPBA-NVLT-N
3FE-64333-AB FD 48 PORTS VDSL WITH ILTF/MELT
FPBA 3FE-65820-AA FPBA-NVLT-R
FD 72 lines VDSL2 over POTS LT
FPBA 3FE-65821-AA FPBA-NVLT-S
FD 72 lines VDSL2 over POTS LT with MELT
FPBA 3FE-65830-AA FPBA-NDLT-C
FD 48 lines VDSL2 over POTS LT with BLV
EMA 3FE-65798-AA FPBA-NDLT-F
FD 48 lines VDSL2 over POTS LT with MELT and SLV
FPBA 3FE-65800-AA FPBA-NDLT-G
FD 48 lines VDSL2 over POTS LT with SLV
EMA 3FE-65728-AA FPBA-NDLS-E
FD 48 lines VDSL2 over POTS LT with integrated splitter and SLV
EMA 3FE-65728-AB FPBA-NDLS-E
FD 48 lines VDSL2 over POTS LT with integrated splitter and SLV
(ANSI)
EMA 3FE-67645-AA FPBA-NDLS-F
FD/FX Multi-DSL BLV (ANSI)
FPBA 3FE-67437-AA FPBA-NDPS-B
384-port Vectoring Processing Server
FPBA 3FE-67440-AA FPBA-NDPS-C
192-port Vectoring Processing Server
FPBA 3FE-67717-AA FPBA-NRCD-C
SB REM DC Controller with Vectoring Processing Server
functionality
FPBA 3FE-64324-AA FPBA-NVLS-A
FD integrated LT/splitter VDSL2 ADSL2plus POTS 48 lines (2,5
Gbps)
FPBA 3FE-66721-AB FPBA-FGLT-A
16p GPON LT
FPBA 3FE-56399-AA FPBA-FWLT-A
4p NG-PON2 TWDM LT
FPBA 3FE-27649-AA FPBA-NSLT-A
FD SHDSL LT
FPBA 3FE-63626-AA FPBA-NSLT-B
FD 24 PORTS SHDSL LT WITH ILTF/MELT (DRCI only)
EMA 3FE-61233-AA/AC FPBA-NALS-A
FD integrated LT/Splitter POTS outdoor 48 lines
EMA 3FE-61233-BA/BB/BC/BD FPBA-NALS-A
FD integrated LT/Splitter POTS CO 48 lines
EMA 3FE-61582-BA FPBA-NALS-B
FD integrated LT/Splitter ISDN CO 48 lines
EMA 3FE-63766-AA FPBA-NALS-C
FD integrated LT/Splitter POTS outdoor 48 lines
EMA 3FE-63766-BA FPBA-NALS-C
FD integrated LT/Splitter POTS CO 48 lines
FPBA 3FE-27420-AA/AB/AC FPBA-NPOT-A
FD 48p POTS Line Board
FPBA 3FE-60858-AA/BA FPBA-NPOT-B
FPBA 3FE-60858-AB/BB FPBA-NPOT-B
FD 72p POTS Line Board - new NGCC chipsets
FPBA 3FE-60858-CB FPBA-NPOT-B
FD 72p POTS Line Board - with integrated 72p splitter
FPBA 3FE-65455-AA FPBA-NPOT-C (ETSI/MII)
FPBA 3FE-65455-BA FPBA-NPOT-C (ANSI)
FPBA 3FE-27562-AA/AB/AC FPBA-NVPS-A
FD Universal Voice packet server
FPBA 3FE-27715-AA FPBA-NBAT-A
FD ISDN Line board supporting 2B1Q
FPBA 3FE-60609-AA FPBA-NBAT-B
FD ISDN Line board supporting 2B1Q
FPBA 3FE-60609-BA FPBA-NBAT-B
FD ISDN Line board supporting 4B3T
FPBA 3FE-60120-AA FPBA-NTAU-A
FD TAUS board
FPBA 3FE-60121-AA FPBA-NCTA-A
Edition 01 - RL 2/Apr/2015 37/150
FD 96 Line Cut-Trough board
FPBA 3FE-68315-AB FPBA-RFAN-B

7363 ISAM MX Fan Unit

FPBA 3FE-68350-AA FPBA-RDLT-A

7363 ISAM MX 32p VDSL2 SLV LT
FPBA 3FE-68864-AA FPBA-RDLT-B
7363 ISAM MX 32p VDSL2 SLV LT
FPBA 3FE-68863-AA FPBA-RDLT-C
7363 ISAM MX 32p VDSL2 SLV LT with integrated MELT
FPBA 3FE-68858-AA FPBA-RDLS-A
7363 ISAM MX 32p VDSL2 SLV LT with integrated splitters
FPBA 3FE-68425-AA FPBA-RPOT-A
7363 ISAM MX 32p POTS LT with integrated VDSL2/ADSL2 splitter
FPBA 3FE-68410-AA FPBA-RANI-A
7363 ISAM MX NTIO with integrated SLV support
FPBA 3FE-68410-BA FPBA-RPNI-A
7363 ISAM MX POTS NTIO with integrated SLV support
FPBA 3FE-68939-AA FPBA-RANI-B
7363 ISAM MX NTIO with integrated SLV support (AC-powered)
FPBA 3FE-68939-BA FPBA-RPNI-B
7363 ISAM MX POTS NTIO with integrated SLV support (AC-
powered)
FPBA 3FE-68979-AA FPBA-RELT-A
7363 ISAM MX 8p/16p P2P GE LT
Sealed boxes
FPBA 3FE-61575-AA FPBA-7357 ISAM FD-SEM AA
7357 ISAM FTTB FD-SEM shelf (LPF power supply)
FPBA 3FE-61575-AB FPBA-7357 ISAM FD-SEM AB
7357 ISAM FTTB FD-SEM shelf (AC power supply)
FPBA 3FE-67201-AA FPBA-7357 ISAM VSEM-D AA
7357 ISAM FTTB VSEM-D shelf (network power supply)
FPBA 3FE-67201-AB FPBA-7357 ISAM VSEM-D AB
7357 ISAM FTTB VSEM-D shelf (local power supply)
FPBA 3FE-67201-AC FPBA-7357 ISAM VSEM-D AC
7357 ISAM FTTB VSEM-D shelf (AC power supply)
FPBA 3FE-68354-AA FPBA-7367 ISAM SX-48V ETSI AA
7367 ISAM SX-48V shelf (ETSI/MII)
FPBA 3FE-68354-AC FPBA-7367 ISAM SX-48V ETSI AC
FPBA 3FE-68354-CT FPBA-7367 ISAM SX-48V ETSI CT
FPBA 3FE-68354-CU FPBA-7367 ISAM SX-48V ETSI CU
FPBA 3FE-68354-CV FPBA-7367 ISAM SX ETSI-48V CV
FPBA 3FE-68354-CW FPBA-7367 ISAM SX-48V ETSI CW
FPBA 3FE-68617-AA FPBA-7367 ISAM SX-48V ANSI AA
7367 ISAM SX-48V shelf (ANSI)
FPBA 3FE-69098-AA FPBA-7367 ISAM SX-12VP ANSI AA
7367 ISAM SX-12VP shelf (ANSI)
Edition 01 - RL 2/Apr/2015 39/150
5 Compatibility

5.1 AMS-ISAM Compatibility
ISAM R5.2 will be supported by AMS R9.4.01.
5.2 TL1 and CLI

All TL1 commands can be found in the R5.2 TL1 Command and Messages
Manuals.
A dedicated document exists depending on the NT in use in the system, i.e.
„ 3HH 11977 AAAA TCZZA for the FD 24 Gbps NT,
„ 3HH 11977 BAAA TCZZA for the FD 100/320 Gbps NT & FX NT and
„ 3HH 11977 CAAA TCZZA for the 7367 ISAM SX and 7363 ISAM MX.
All CLI Commands can be found in the ISAM R5.2 CLI Command Reference
Guides.
A dedicated document exists depending on the NT in use in the system, i.e.
„ 3HH-04416-ECAA-TCZZA for the FD 24 Gbps NT,
„ 3HH-08079-ECAA-TCZZA for the FD 100/320 Gbps NT & FX NT and
„ 3HH-11762-ECAA-TCZZA for the7367 ISAM SX and 7363 ISAM MX.
Most of the DPoE CLI-commands are, from R4.6.01 on, described in a dedicated
CLI Command Guide, i.e. for R5.2:
„ 3HH-11831-ECAA-TCZZA.
The CLI Command Reference Guide for the NANT-D/E FD 100/320 Gbps NT will
refer you to one of the 6 IHUB Command Guides for details on the CLI IHUB
commands, i.e.

Number
1 3HH 11982 AAAA TQZZA IHUB System Basics, Management and OAM Guide
2 3HH 11983 AAAA TQZZA IHUB Interface Guide
3 3HH 11984 AAAA TQZZA IHUB QoS Guide
4 3HH 11985 AAAA TQZZA IHUB Services Guide
5 3HH 11986 AAAA TQZZA IHUB Router Configurations and Routing Protocols Guide
6 3HH 11987 AAAA TQZZA IHUB MPLS Guide
All of these documents are part of the 7302 ISAM, 7330 ISAM FTTN, 7360 ISAM FX,
7356 ISAM FTTB, 7357 ISAM FTTB, 7367 ISAM SX and 7363 ISAM MX R5.2
documentation sets.
It should be noted that a number of commands for future features are already
part of the SW load but not yet documented in the command reference guides
and/or operations guides. These commands should not be used.
5.2.1 CLI/TL1 commands & parameters phased out

For a full list of all CLI/TL1 commands and parameters that have been phased-
out or are bound to be removed in a next ISAM release, please carefully check
the ISAM CLI Command Guide and ISAM TL1 Commands & Messages Manual
documents. Note the CLI/TL1 commands & parameters phase-out is additional to
the feature phase-out (separate “DR6”).
Note CLI and TL1 commands are not always backwards
compatible. It can be that old commands are still
accepted, but will not be executed.
5.3 SELT-NA Compatibility
For customers using SELT in the 5530 Network Analyzer with R7.0 or higher, every
ISAM build needs to be accompanied by the associated SELT calibration
package. As this package is customer specific, please contact your Alcatel-
Lucent 5530 NA representative to check if a renewal of the calibration package
is required.
Line testing is an interactive process. It will be more convenient to use 5530
Network Analyzer to do line testing. When using CLI, multiple commands need to
be executed, e.g Create Session, Start Line Test, Check if test is over, Get test
result, Destroy Session, etc.
Edition 01 - RL 2/Apr/2015 41/150
6 Known Restrictions

6.1 Generic Restrictions
Following restrictions apply to the functionality of 7302/7330/7356 ISAM in R5.2:
„ The "10Gbps per LT" license is restricted to usage of linecards in the same
shelf.
„ On the NELT-B UNI port, QoS parameters for PPPoE forwarding with MAC@
concentration are to be defined at VLAN port level and will be reused at
PPP client port level (no QoS settings at PPP client port level).
„ For non-GPON LTs, programming a burst size value (CBS) larger than the LT
capabilities is supported. The LT will configure the maximum value
supported by the HW iso the value requested by the operator (allowing to
use common profiles between different LTs). However, configuring a rate
(CIR) larger than the LT capabilities is not supported. If a higher burst size is
configured than what a line card type can handle, its maximum burst size
is used as the actual value. This actual value will not be reported back to
the operator. Instead, the configured value is reported. Please consult the
System Description documentation for the maximum burst size that a line
card can handle.
„ HPE bandplan is not supported on VDSL2 linecards.
„ Although A and B side power feeds are available for the shelf, only a rack
level power alarm is provided in case of a failure on either power source.
„ Bonding in combination with Retransmission (G.inp) is supported with
following restrictions:
· Only supported for 2p VDSL2 PTM bonding
· Supported on all VDSL2 LTs, except NVLT-C/D and NVLT-R/S
· Only validated against BCM63168 D0 ref design CPE
· As restrictions apply depending on the CPE FW release, Alcatel-
Lucent local support should be contacted before planning
trials/rollout to get the latest information (e.g. IOP results)
„ ADSL2 PTM mode is not supported
· ADSL2Plus PTM mode is supported on non-bonded lines for following
boards: NVLT-N/P/Q, NVLS-A, NDLT-C/F/G/H, NVLT-R/S and NDLS-E/F.
„ ADSL2(Plus) PTM bonding is only supported against 7705 SAR-M.
„ Bandplan 997 is not supported on NVLT-R/S.
„ Following restrictions apply to the functionality of NVLT-R/S :
· Following capabilities are not supported:
o Bonding in combination with SRA
· Following capabilities have limited support:
o VDSL SRA without dynamic Interleaver
o SELT with restrictions on reach and number of usable PSD types
o As restrictions apply for bonding (e.g. IOP results), Alcatel-
Lucent local support should be contacted before planning
trials/rollout to get the latest information
„ ATM Pseudowire support on limited set of linecards:
· The ISAM supports configuring ATM Pseudowires (ATM PWE3) on the
following DSL linecards:
o ADSL: NALT-J (AA and BA variant), NALS-A (AA, BA and BB
variant)
o SHDSL: NSLT-A
· All other linecards do not support ATM PWE3 functionality.
· The ATM PWE3 functionality can be supported in combination with
the NANT-A and NANT-D network termination cards.
„ A deployment model with PPP Cross-connect & Bridging on the same
VLAN port can be configured on the NALS-A (AA, BA and BB variant), the
NALT-J (AA and BA variant) and the NALT-K (BA variant). This deployment
model is not supported on Hi-Cap L3 VDSL LTs as well as on the NALS-A (AC,
BC and BD variant), the NALT-J (AE and BE variant) and the NALT-K (BF
variant).
„ DHCPv4/v6 session, vMAC context, IPoA address and 802.1x port
authentication data might get lost after migrating from an older release
than R4.5.01 to R5.1.x:
· A loss of DHCP and a potential loss of the MAC-vMAC mapping is
depending on the network deployment model. For instance, the
vMAC issue is not visible for a single MAC per bridge port because
the system will reassign the same vMAC.
· Impacted LT cards are NALS-A, NALT-J, NALT-K, NALS-B, NSLT-A, NSLT-
B, NALT-C, NALT-D and NGLT-x, FGLT-A and NELT-B.
· This issue will not occur anymore for future migrations from R4.5.01
onwards to R5.1 or higher releases.
Following restrictions apply to the functionality of 7302/7330/7356 ISAM-Voice

since R4.0:
„ Redundancy:
· Since the ARP table is not synchronised between active and standby
NANT-A, a NANT-A switch-over may cause a temporarily service
degradation of the SIP Centralized based or H.248 based integrated
VoIP service, should in the course of the LANX hot reset procedure
and in particular the hard-coded infixed SHUB hot reset ARP re-learn
period, the necessary ARP entries not been learnt for transmitting
upstream signaling and/or voice packets.
Following restrictions apply to the Vectoring functionality in R5.2:

„ Special Loop Diagnostics mode with Vectoring is not supported.
· Special Loop Diagnostics mode (i.e. robust initialization without
transition to showtime) is not allowed in case the legacy VDSL2 mode
Edition 01 - RL 2/Apr/2015 43/150
is disabled in the vectoring profile, or in case the legacy VDSL2 mode
is enabled in combination with ZTV.

· Special Loop Diagnostics mode (i.e. robust initialization without
transition to showtime) is allowed in case the legacy VDSL2 mode is

enabled in the vectoring profile, without enabling ZTV.
„ 997 bandplan is not supported in Vectored mode.
„ QLNc reporting is not supported.
„ Recommended configurations with vectoring:
· With vectoring, the use of G.inp and SRA is strongly recommended.
o Background: In non-vectored mode, VDSL2 self-crosstalk often
masks low-amplitude impulse noise. Because vectoring
removes self-crosstalk, vectored lines are more vulnerable to
impulse noise, as also observed in lab and field tests. G.inp,
a.k.a. ARQ (Automatic Repeat Request), is an impulse noise
protection technique based on retransmission at the physical
layer and standardized by ITU (G.998.4 or G.inp). G.inp
provides improved protection against impulse noise compared
to I-FEC (interleaved forward error correction based on the
combination of interleaving and Reed-Solomon coding).
Another advantage of G.inp compared to I-FEC is that
overhead for retransmission is only consumed if impulse noise is
actually present while with I-FEC the Reed-Solomon overhead
is always consumed. Also, with the application of extended
G.inp memory as defined in G.998.4 Amendment 2, G.inp
allows higher bit rates, up to 100 Mb/s and above (if sufficient
SNR).
o Note: G.998.4 Amd 2 contains a flaw when combined with
G.998.4 Amd 1 (SRA over G.INP). This may cause link drop
when G.998.4 Amd 2, G.INP and SRA are active simultaneously.
Broadcom and Alcatel-Lucent submitted a corrigendum for
G.998.4 Amd 2 in ITU-T. Workaround: against Broadcom based
CPEs, the proprietary implementation according to the G.998.4
Amd 2 corrigendum is activated by default. This proprietary
implementation won’t apply for the non Broadcom based
CPEs. Alternatively, disabling SRA in combination with G.INP
can also be used as workaround.
· With G.inp, it is strongly recommended to combine with the intra-DTU
block interleaver for extra protection against varying RFI or other
varying narrowband interference e.g. crosstalk from handshake
tones (G.994.1 or G.hs) on neighbouring lines.
o Background: G.inp provides improved protection against
impulse noise compared to the legacy I-FEC. However, G.inp
provides less protection against varying RFI or other varying
narrowband interference than I-FEC. In particular, crosstalk
from G.hs tones on neighbouring lines can introduce errors on
vectored lines protected with G.inp, as observed in lab and
field tests. The intra-DTU block interleaver is an additional
protection mechanism against varying RFI or other varying
narrowband interference for use in combination with G.inp.
o Note: the support of the intra-DTU block interleaver is
introduced as a proprietary implementation, only supported
against Broadcom-based CPE’s, and is enabled once G.inp
has been configured.
· With vectoring, the application of UPBO remains recommended.
o In theory, with perfect Vectoring there is no need for UPBO. In
practice however some type of UPBO may still be required,
e.g. because of residual crosstalk or dynamic range limitations
of the receiver. Also, UPBO must still be applied in case non-
vectored lines, e.g. G.vector friendly lines (G.993.2 Annex X or
Annex Y) or legacy lines (with reduced spectrum or reduced
transmit PSD to limit the impact on the vectored lines), are
mixed with vectored lines in the same cable.
o Although Alcatel-Lucent has performed successful vectoring
lab and field tests without UPBO, we still recommend the use of
UPBO with vectoring. Further lab and field tests need to show
to what extend the UPBO configuration can be relaxed with
vectoring under various conditions.
„ Zero-touch vectoring is able to cancel crosstalk from legacy VDSL2 lines
into G.vector lines. For bonded legacy VDSL2 lines, zero touch vectoring
support is limited to 2-pair bonding.
„ Vectored legacy lines (zero touch vectoring) do not perform automoding
with an open profile, similar to G.Vect lines. Although the legacy line
operates in legacy mode, the automoding functionality is currently not
possible. As workaround, a closed spectrum-profile can be used to select
the required operational mode for the legacy line.
„ Cross-DSLAM vectoring is only supported for configurations with distributed
7356 and NRCD-C (including vectored mode).
„ For reasons of robustness when starting up the SLV system (e.g. after
cold/warm reset), the VP-LT link initiation is subject to an internal defense
mechanism against HW or SW failures, which might result in longer time for
link bring-up. In exceptional cases, this can even result in the (multiple)
reset of the LT card.
„ From R4.5.02 onwards, following operational improvement has been
introduced: As long as no vectoring profiles have been assigned to any of
the LT ports, the LT ports will not resynchronize when connecting the QSFP
cable. Since the synchronization is only required for vectoring, this will only
be done once the first vectoring profile has been assigned.
„ The combination of Vectoring and Bonding is supported for up to
maximum 1 NDPS-B and 8 SLV LTs in the same shelf.
Edition 01 - RL 2/Apr/2015 45/150
„ As restrictions apply for the combination of Vectoring and Bonding
(depending on the number of bonding groups), Alcatel-Lucent local

support should be contacted before planning trials/rollout to retrieve latest
info (e.g. supported configurations).

„ Whereas it is possible to configure the disorderly leaving threshold in the
range of 0..40000 DMT symbols, the supported range is
between 1 and 32 symbols. The configured value is rounded up to the next
multiple of 8 symbols, leading to effectively 4 different
possible settings – 8, 16, 24, 32. Values above 32 are clamped to 32.
Following restrictions apply to the functionality of NELT-B in 7302/7330/7356/7360

ISAM in R5.2:
„ Deployment
· 18xFE or 18xGE ports with SFP in 7302/7330/7356/7360 ISAM.
· 36xFE or 36xGE ports with cSFP in 7302/7330/7360 ISAM.
· No cSFP in 7356 REM for thermal reasons : The mechanical class of
the 7356 FD REM is limited to class 3M3 according to ETSI standard ETS
300 019. For further information, please contact your Alcatel-Lucent
representative.
· See Hardware Installation Manual for more information.
„ QoS
· QoS session profile can be configured at the BP and VP Level, and
not at the PPP client port (Default priority and session QoS profile
cannot be attached to PPP client port).
· The pbit/DSCP match conditions for a policy action are compared
with the received pbit/DSCP values. On the NELT-A card, the
pbit/DSCP match conditions for a policy action are compared with
the remarked pbit/DSCP values.
· DSCP to P-bit alignment table can be configured on a SAP Bridge
port only (not a SAP vlan port).
· Upstream Layer 3 filters are not supported for PPPoE packets.
· The system level and the VLAN level Pbit to TC mappings must be
simultaneously used for NELT-B UNI operations. For NELT-B HC-UNI and
NNI operations, it is only required to configure the system level Pbit to
TC mappings though it might be safer to create a VLAN level Pbit to
TC mapping identical to the system level mapping to be ready for a
potential future introduction of that feature on HC-UNI and NNI.
· On the HC-UNI port type, QoS treatement is at parity with UNI with
following exceptions :
o 2r3c metering (fairness between subscribers) is supported for
upstream traffic only.
o L2 / L3 filters are supported for upstream traffic only.
· On the NNI port type,
o QoS treatement is at parity with UNI (see exception below) for
up to 8 VLAN Ports (out of the 256 supported ones), targeting
business user application (for subtending interfaces where a
higher amount of VLANs is more typical, detailed QoS handling
is performed by the subtended node).
o 2r3c metering (fairness between subscribers) is supported for
upstream traffic only.
o L2 / L3 filters are supported for upstream traffic only.
„ L2 Forwarding
· There is a maximum of 8 VP per BP on a UNI and HC-UNI.
· The HC-UNI mode only supports a subset of the UNI features as
indicated in the Product Information
· The NNI mode is defined to support an S-ISAM (Subtended ISAM) for
residential services. As such the following subscriber management
functions are expected to be performed on the S-ISAM (see Product
Information for more details) :
o vMAC
o Enhanced i-bridge (DHCP snooping, ARP relay, IP anti-
spoofing)
o PPPoE relay with MAC@ concentration
o PPPoE Relay
o L2 DHCP relay / Lightweight DHCPv6 relay
o IEEE802.3ah
o IEEE 802.1x
„ Video
· When using NELT-B for subtending applications, via NNI ports, one
needs to take into account that the NELT-B card supports up to
55…60 zap/second (i.e. a zap = join + leave) depending on the NT
card type and whether the scenario involves a root (joining a
multicast channel not present yet in the system or leaving the last
branch of multicast tree) or branch (adding/remove a branch of a
multicast tree)
„ LAG
· All port members of a given LAG must belong to either one of the
two Port Id ranges: 1...18 or 19...36
„ Counters
· NELT-B HC-UNI and NNI counters are subject to constraints and
restrictions.
Following restrictions apply to the functionality of NANT-D and NANT-E in

7302/7330 ISAM and to FANT-F in 7360 ISAM FX in R5.2:
„ The ISAM Voice package (ISAM-V) is supported on FANT-F with NPOT-C
ANSI, and SIP only.
„ NCNC-B, in conjunction with NANT-D, will support 100FX and 100BT
interfaces using the relevant SFP’s.
Edition 01 - RL 2/Apr/2015 47/150
„ SyncE input and BITS input is supported for synchronisation on NANT-D,
NANT-E and FANT-F and also on the relevant NTIO’s in combination with

these NTs, but with following generic restrictions:
· SyncE input and SyncE output is supported on optical 1 GE interfaces

and on optical 10GE interfaces, but not on other interfaces.
· NCNC-D provides a limited support of Synchronous Ethernet: SyncE IN
is not supported. SyncE OUT is only available on SFP6/SFP7.
· NT redundancy in combination with synchronisation is only supported
with following restrictions: When BITS input is used for synchronisation,
then the same clock must be provided to both BITS inputs (one on
each NT) The clock on the standby NT can not be monitored. (This
BITS related restriction does not apply for NANT-D.) SyncE inputs are
then only supported when connected to the NTIO interfaces. In all
these cases, during switchover from one NT to the other NT, there will
be a larger phase jump, i.e. not compliant to ITU-T G.813 (2003)
Section 10.1 and ITU-T G.8262 (2007) Section 11.1 (Short-term phase
transient response (Option 1)).
· Redundancy for synchronization in case of dual BITS inputs is
supported, but redundancy for synchronization in case of dual SyncE
inputs, one per NT, is not supported.
· Redundancy for synchronization in case of dual IEEE1588 inputs, one
per NT, is supported on FANT-F, but not on NANT-E, nor on NANT-D.
„ Customer specific features not relevant for NANT-D, NANT-E and FANT-F
deployments and consequently not supported in R5.2:
· PCCP
· Support for Cluster management
· TTL=0 forwarding
· L3 DHCP relay together with L2 forwarding
„ Video
· IGMP Resource Admission Control (or CAC) on the uplink not
supported on NANT-D, NANT-E and FANT-F
· The ISAM does not support Performance Monitoring counters for
multicast traffic on a v-VPLS service. When configuring a v-VPLS
service instance and attaching SAPs to that service, it is not possible
to count the egress L2 switched or L3 routed multicast traffic on that
SAP. This is a hardware limitation. The ISAM is only able to count
egress multicast traffic on SAPs attached to a true VPLS service
instance.
„ No support of NCNC-D in redundant NANT-D/E configurations.
„ In an Ethernet Ring Protection Switch (ERPS), with an ALU 7750 SR as Ring
Protection Link (RPL) owner, the ERPS switchover time increases in function
of the number of SAPs configured on the ALU 7750 SR.
„ Y.1731
· L2 ACL's cannot be combined with Y.1731 on same VPLS/V-VPLS
service.
· On NANT-D, SAP statistics and Y.1731 monitoring cannot be enabled
simultaneously on same VPLS/V-VPLS service.
· When Y.1731 is enabled on LAG with ports from active & standby
NT's, loss measurement with LMM may contain inaccuracies when
adding/removing standby NT ports to LAG while measurement is in
progress. The inaccuracy of packet counters is only for duration
when ports are being added or removed from LAG.
Following restrictions apply to the functionality of NANT-D and NANT-E

redundancy in 7302/7330 ISAM and to FANT-F redundancy in 7360 ISAM FX in
R5.2:
„ Synchronisation:
· NANT-D/E and FANT-F redundancy in combination with SyncE is
limited in functionality (as already explained in more detail higher in
this chapter for simplex NANT-D/E configuration).
„ Forwarding:
· The following L3 forwarding functionality is not supported (and so
should not be configured) in a duplex NANT-D/E or FANT-F system:
o ISIS, RIP, PIM-SSM and BFD
„ Spanning Tree:
· The use of Spanning Tree protocols (STP, RSTP, MSTP) in configurations
combining NANT-D/E or FANT-F redundancy and dual homing.
· Fully supported when the uplinks are connected to the NT I/O.
· Suffers from the following limitations when the uplinks are directly
connected to the two NTs (e.g. first uplink connected to NT-A and
second uplink connected to NT-B):
o MAC address conflicts (duplicate MAC addresses) will
temporarily occur during switchover.
o Slow traffic restoration after switchover: the xSTP dynamic
states are not synchronized between the active and the
standby NT, hence the protocol will need to build up the
spanning tree again after switchover. This may result in a longer
(>1 sec) traffic outage for large spanning tree groups.
Following restrictions apply to the functionality of the 7360 ISAM FX in R5.2:

„ LT backplane load sharing towards NT; no support for 80Gbps per LT slot
(FANT-F).
„ User-port level commands for PPPoE L2 Statistics do not report actual data
in this release.
„ Although A and B side power feeds are available for the shelf, only a rack
level power alarm is provided in case of a failure on either power source.
„ For NGLT-A, packets discarded by the Traffic Manager (QOS processor) are
not taken into account for the trouble-shooting counters.
„ A Rogue ONT may not be detected when the signal level on
corresponding ONT is too low. However, in many cases a rogue ONT with
Edition 01 - RL 2/Apr/2015 49/150
such low level signals may not cause disturbance for other ONTs on the
PON.

„ An unprovisioned rogue ONT with an optical signal level lower than that of
other ONTs on the PON may result in disruption on some ONTs without being

automatically detected as rogue as the disruption level is low. Such ONTs
are detected by on-demand tests.
„ The Active/Standby (A/S) configuration of the FNIO-A (i.e. all NTIO ports are
controlled by single NT) is reserved for a later release. In this release the
FNIO-A only supports the Active/Active configuration. For the A/S
configuration, FNIO-B can be used.
„ The NG-PON2 portion of the ISAM software in the present release is only
delivered at DRCI level for customer demo and evaluation purposes. On
the other hand, Customer Documentation including related portions of the
command manuals have been made available in anticipation of the DR4
at a release in the near future and in order to help operators with their
internal planning. Related SW should not be exercised without explicit ALU
agreement regarding the definition of the demo or evaluation context.
„ Configuration via TL1 is not supported for TWDM-PON (NG-PON2)
management.
Following restrictions apply to the functionality of GPON in 7302/7330/7360 ISAM in

R5.2:
„ It is advised to configure only connected UNIs on PON ports as the startup
time of the system will scale with the amount of configured users. As the
theoretical density of configured GPON users can be significantly higher
than the typical density of connected users, this approach will avoid an
unnecessary increase in startup time.
„ CIR+AIR upstream bandwidth is limited to maximum 836 Mbps per PON.
„ When an S-VLAN tunnel configuration is trying to set the S-VLAN tag pbit to
a specific value but is using eight pbit to traffic class mappings then packet
drops are observed.
· When using the S-VLAN tunnel mode, the OLT inserts an S-VLAN tag in
upstream frames. The dot1p priority in the S-VLAN tag can be either:
o Case 1: copied from the C-VLAN tag priority, or
o Case 2: set to a configured value, the same for all frames.
Note that in Case 2, the traffic carried by the tunnel is regarded as
belonging to a single traffic class. Therefore the ingress QoS profile
associated with the S-VLAN tunnel should be configured with all
dot1p priority values mapped to a single traffic class. If not
configured with a single traffic class, there is the possibility that some
upstream frames will be dropped.
„ The historical previous-15min PM counters introduced in OMCIv2 are not
supported.
„ Virtual Noise and E-side/DPBO on VDSL2 ONT MDUs is covered in the
customer documentation, but not supported in this release.
„ It is possible to configure up to 768 UNI per PON for all PONs on a GPON line
card. Number of UNIs at system level is limited to 32K.
„ Sharing of a QoS BW profile is not supported at the ONT level when the ONT
queues are configured in strict priority or with a mix of strict priority and
weighted fair queuing scheduling.
„ The following functionality cannot be activated at the same time:
"Downstream UNI rate shaping including multicast" and "UNI shaping based
on queue parameters".
„ When configuring E1 Circuit Emulation Services the Delay Tolerance value
must be carefully set; In addition, as the system default may internally be
adjusted on a case by case basis, the operator is strongly advised not to
rely on this value but apply careful network planning to determine the
appropriate DT value for specific services on the PONs.
„ Background Rogue ONT tests are disabled by default on the PON
interfaces and need to be turned on explicitly if the operator chooses to
do so. For systems migrating to this release from an older release where this
functionality was enabled previously, the prior setting is preserved on the
PONs that already existed in the previous release. For newly created PONs
however, the default disabling will be set.
„ On the GPON LTs a PON upstream bandwidth profile can be configured
with the command "configure qos profiles bandwidth". Apart from CIR, AIR
and EIR (Committed, Assured and Excessive Info Rate), this command has
a parameter delay-tolerance. The Delay Tolerance (DT) can have
significant impact on the upstream service quality. DT specifies the grant
periodicity in terms of 125us frame times, e.g. DT=8 specifies that a TCONT
should receive grants at least every millisecond. The default value of DT is
1; in normal circumstances DT=8 is often a good choice but the service
characteristics need to be taken into account. In order to satisfy physical
layer constraints, in case of a conflict between the provisioned bandwidth
and the provisioned delay tolerance, the GPON OLT may adjust the grant
periodicity to a smaller number to meet the bandwidth requirements. The
corresponding show command reflects the adjusted delay tolerance
value if applicable. In no cases the requested bandwidth is adjusted
downwards to comply with the configured delay tolerance. In certain
service scenarios, the delay of upstream packets may influence also
downstream performance; e.g. in case of large network latency combined
with a large DT value, the downstream TCP performance can become
low. For such reasons, the Delay Tolerance value must be carefully chosen,
considering both upstream and downstream factors.
„ An operator controlled security feature of ISAM allows prevention of any
ONT service activity, including provisioning and traffic, when that ONT is not
running the correct software provisioned by the operator. Operator control
of this feature, introduced in R5.2, is exercised on a per ISAM basis. As result
of the operator choice for this option ONTs are allowed or not allowed to
Edition 01 - RL 2/Apr/2015 51/150
continue to deliver service when their planned SW version was modified to
be different than their active SW version.

„ When using Type-B protection on PONs with the I-010G-S ONT, the alarm
'Port protection not available' after a switchover may take several minutes

to clear, which may cause issues in case a next switchover would be
triggered during that time.
„ In PON redundancy configurations, if OLT loses the contact with the last
remaining ONT on the PON for any reason, including as a result of an ONT
power-off event, a Type-B switchover may be initiated prior to the
reception of the corresponding PLOAM message.
· Customers should take care of their provisioning as well as physical
wiring such that no more than 16 simultaneous switchovers are
needed as a result of an equipment failure or accidental cut in the
physical plant in order to avoid service interruption.
„ In GPON, the feature "Type-B Protection" is not compatible with the feature
PPPoE relay with MAC address concentration.
„ TC-Layer PM counters are intended to be used in pairs, with one instance
at the OLT and one instance at the ONT, in order to detect impairments of
the TC layer connectivity. This determination is made based on significant
discrepancies between blocks/fragments reported as transmitted from one
end and reported as received from the other in the same timeframe.
However ALU OLT and ONT may report small differences between these
counts even in the absence of a noteworthy problem.
„ Downstream p-bit remarking as a result of policing is not supported on
NGLT-C and FGLT-A. (Note, on the other hand, that upstream remarking as
a policer action is support on all GPON line cards).
„ Queue mode can only be configured per pair of PONs on FGLT-A/NGLT-C.
„ Prior to ISR4.6 the “config voice ont mgc-config” CLI command allowed
the optional “pri-mgcuri-profid” and “sec-mgcuri-profid” parameters to be
defaulted to a null pointer. These defaults would prevent proper setup of of
voice service. Starting ISR4.6 these parameters are made mandatory to
prevent unintentional operator errors (Note that the problem did not exist in
TL1 interface).
„ Protocol tracing is not supported for downstream ARP messages.
„ Protocol tracing is supported for upstream ARP messages, provided that
either Secure Forwarding or MAC address translation is enabled on that
VLAN (applies to both iBridge and VLAN cross-connect).
„ DHCP protocol tracing is not supported on a cross-connect VLAN in case
Secure Forwarding is disabled on that VLAN.
„ In cases where the VoIP IP-Host service is already created and the
associated POTS line is made ISNR, if the Operator deletes the related
Bridgeport, ISAM proceeds to auto-deletion of higher layer entities. As part
of this, the VoIP IP-Host service is also automatically deleted. No additional
service mismatch alarm is raised.
„ 7360 ISAM FX only supports 802.1X in simplex mode. 802.1X authentication
data are not synchronized between active NT and standby NT.
CFM is only supported for a subset of GPON ONTs. Please check ONT
Specifications.
Following restrictions apply to systems using the FPLT-A DPoE or EPON profiles in
the 7360 ISAM FX in R5.2:
„ QoS restrictions on FPLT-A:
· CCL and ACL
o Only support of maximum 4 fields QoS classfication.
o CCL and IP address for IP-antispoofing share maximum 8
entries per flow.
o Only support of the following actions: Pass/Discard/P-bits
marking.
· Shaping
o Only 'Single Token Two Rate' supported.
o The Committed Burst Size is fixed 255 Kbytes no matter what
you enter in the CLI.
· No policing
„ Cross-VLAN multicasting is not supported.
„ Unprovisioned ONU alarms may take up to 2 minutes and 30 seconds to
clear.
„ Specific restriction on ANSI:
· The EPON ONU MAX MAC value should be manually set to the
appropriate value according to the ONU chipset.
„ For third party ONU support information please contact your Alcatel-Lucent
representative.
· For ONUs using Broadcom 3711 chipsets, R141 software must be used.
· For ONUs using Broadcom 3714 chipsets, R227/E262 (E262
14.93661)/R263 software must be used. IOP with R251 software is not
supported.
„ The CAcert authorization does not examine the trusted or untrusted state at
this time.
„ Only tpids 0x88a8 and 0x8100 are supported.
Following restrictions apply to systems using the 10G EPON FPXT-A in the 7360
ISAM FX in R5.2:
„ QoS restrictions on FPXT-A:
· No CCL/ACL
· Shaping
o Only 'Single Token Two Rate' supported.
o The Committed Burst Size is fixed 255 Kbytes no matter what
you enter in the CLI.
Edition 01 - RL 2/Apr/2015 53/150
Following restrictions apply to systems using the FPLT-A DOCSIS profile (DPoE) in

the 7360 ISAM FX in R5.2:
„ Commands intended for the DOCSIS environment do not function for

boards in the non-DOCSIS environment.
„ CLI command failures are not recorded in syslog. Only successful CLI
commands are logged to the syslog.
„ A segregated pool of VLANs is needed between DOCSIS and non-DOCSIS
environments. In order to prevent duplication of VLANs, the customer
should assign a range of VLANs to be used in each environment.
„ For third party ONU support information please contact your Alcatel-Lucent
representative
· For ONUs using Broadcom 3714 chipsets, R227/E262 (E262
14.93661)/R263 software must be used.
„ Once an ONU has been removed from the whitelist, it cannot be re-added
without resetting the ONU. This cannot be done remotely as the ONU can
no longer register.
„ Once one ONU has been added to the white list, all other ONUs will not
register until they are added to the white list.
„ I-BEB configuration: not supported PBB for ALU DPoE
„ System SAV (IP anti-spoofing) : SAV not supported yet
„ DPoE authentication is only supported on DPoE OAM. ONUs running other
OAM (e.g. Tk) will register regardless of the DPoE authentication methods
used.
„ Some R4.6.01a DPoE CLI commands, that were changed in R4.6.02, are not
supported in R5.2 any more, please refer to the DPoE CLI Command Guide
for more details.
„ CMTS/vCM MIB is not fully supported,please contact your Alcatel-Lucent
representative
Following restrictions apply to the functionality of DPoE in 7360 ISAM FX in R5.2

(see also Product Information Guide table 1-19):
„ System local logging: log file size is not controllable yet
„ CLI security login: Terminal Access Controller Access-Control system Plus
(TACACS+) not supported
„ CLI logging: can not log through TACACS+ server
Following restrictions apply to the functionality of the 7363 ISAM MX in R5.2:

„ Network links:
· In case LAG is not configured, only 1 physical network link can be
active. This link can be freely chosen from nt-a:xfp:1, nt-a:sfp:1 or nt-
b:xfp:1 (nt-b:sfp:1 is not supported). In particular, it is not possible to
activate any of the other network links either as independent uplink
or downlink, in daisy chain topologies or in ring topologies.
· High capacity counters on LAG are not supported in “show interface
port la-group” command.
· To operate the network link in 2.5G mode, autonegotiation must be
disabled on both sides. If autonegotiation is enabled on both sides,
the operational speed of the port will default to 1G.
· In the event that an operator wants to migrate from GPON to PTP
uplink, the integrity of the interface stack on top of the uplink shall be
guaranteed by following manual procedure:
o Breakdown the interface stack on top of the uplink ([LAG], BP,
VP…).
o Swap the SFP & restart the system.
o Rebuild the interface stack on top of the uplink ([LAG], BP,
VP…).
„ Equipment:
· System memory usage status is not supported.
· It is advised to keep a minimum guard time of 5 seconds between
the hot extraction and re-insertion of an NTIO or LT board.
· Following two 1 Gb/s Ethernet 1000Base-BX40 SFPs (3FE-65571-AA and
3FE-65571-AB) are supported on the 7363 ISAM MX-6 boards, but only
compliant with EMC Class A.
· Whereas there is minimal SW support for RELT-B (3FE-68979-BA) in this
release, only RELT-A (3FE-68979-AA) is fully supported.
„ xDSL:
· Bonding is supported on the RDLT-B, RDLT-C and RDLS-A LTs with
following restrictions:
o Only 2-pair PTM bonding is supported (no ATM bonding, no 8-
pair PTM bonding).
o Interoperability of a non-bonding capable CPE connected to
a bonded user port is only supported when the non-bonding
capable CPE is connected to the primary line of the bonding
group. The bonding group will not become operational when
the CPE is connected to the secondary line.
o Only bonding groups configured with 2 pairs can be set admin
up. A bonding group configured with only 1 pair cannot be set
admin up.
o Creation/deletion of a bonding group may lead to a short
period of traffic loss on some of the other lines of the LT card.
The same may occur when switching between a bonding-
capable CPE and a non-bonding capable CPE or when
powering-down or powering up a non-bonding capable CPE
connected to a bonded user port.
o When creating more than 10 bonding groups (and setting the
group admin up) on the same LT, there is a risk the creation of
Edition 01 - RL 2/Apr/2015 55/150
a new bonding group (and setting the group admin up) may
exceptionally lead to a resynchronization of one or more

bonding groups configured on the same LT card.
· Bonding is not supported on the RDLT-A LT.

„ Forwarding and Protocols:
· The function of an IGMP snooper with proxy reporting on the level of
the NT is not supported. Every LT presents itself as an independent
IGMP proxy to the network. Multicast streams will be correctly
replicated to 7363 MX node by the upstream aggregation node, but
this one will see a higher load of IGMP messages from the 7363 MX
node than if an IGMP snooper function were present.
· Static infeed of multicast channels into the 7363 ISAM MX is not
supported.
· Secure forwarding (IP-antispoofing, ARP antispoofing) is not
supported.
„ QoS:
· Traffic management parameters of uplink queues (scheduler priority
and weight, BAC profile) are fixed by hardware default and not
configurable.
· Port and queue shapers are not supported.
· trTCM policer is not supported (single token bucket is supported).
· Queue counters on uplink queues are not supported.
· Performance monitoring counters on bridgeports, vlanports provide
octet counts only. Packet counts are not supported.
· Traffic counters on PPPoX client ports (packet counts) are not
supported. If a PPP client port maps 1:1 to a vlanport, vlanport
counters (octet counts) can be monitored instead. Control frames
counts are supported.
· Downstream QoS queue counters provide packet counts only. Octet
counts are not supported.
· VLAN pbit counters are not supported.
· At any one time, troubleshooting counters (summary and extended)
can be activated on a single DSL line/PVC and up to 16 vlanports on
that DSL line/PVC per system only.
· The system does not accept configuration of a default p-bit or a QoS
profile on a VLANport of type 'any'. When configuring a default p-
bit/qos profile for a S-VLAN tunnel forwarder, the p-bit/qos profile
should be provisioned on the bridgeport that has the 'any' vlanport.
The workaround is restricted to cases where the S-VLAN tunnel is not
combined with another forwarding model (e.g. C-VLAN bridge or C-
VLAN cc) on the same bridgeport.
· The aggregate throughput in US over all LTs is currently restricted to
about 3.6 Gbps. Traffic loss may occur if the overall US traffic
exceeds 3.6 Gbps.
„ Voice:
· Voice traffic mirroring is not supported.
· External path forwarding is not supported.
· 12k/16k metering is not supported.
· Per board statistics is not supported.
· POTS Narrowband Line Test: only 1 NBLT session can run at a time.
· MELT is not supported.
„ Management:
· TL1 support is restricted to the commands for which applicability is
specified in the TL1 commands and Messages Guide.
· CLI support is restricted to the commands for which procedure
applicability is specified in the OAM using CLI Guide.
· Operator authentication using Radius is supported under the
restriction that the Radius server must be reachable over the ISAM
management VLAN.
· Viewing of troubleshooting stats on the management interface
(ICMP, ARP, TCP, UDP) is not supported.
· The loopback interface is not supported.
· The 7363 ISAM MX contains some management protection
mechanisms to increase IP security:
o Packets with invalid data (e.g. invalid source IP address) are
dropped.
o Packets in invalid state (e.g. TCP RST when no SYN has been
detected) are dropped.
o Packets are rate limited (e.g. ICMP ping, ECHO).
o Setup of new connections is monitored (e.g. to detect port
scanning tools). When more than 20 new connection attempts
per second are detected from a particular source IP address,
then new connection requests (e.g. telnet, ssh) from that
source IP address will be blocked during 120 seconds.
Following restrictions apply to the functionality of the 7367 ISAM SX in R5.2:

„ Uplinks: no dual uplink, LAG, daisy chaining.
„ 802.1ag & Y.1731 restricted to ETH-SLM/LM responder/initiator, ETH-DM
responder, Loopback, Link race and Continuity Check messages on VDSL2
ports. Only UP MEP on UNI interace supported (down MEP not supported).
„ Number of VLAN’s (RB + CC) that can be configured is 256.
„ Number of MAC addresses that can be learned on the uplink is 1024.
„ S-VLAN tunnel is not supported.
„ Bridgeport counters and vlanport counters on uplinks are not supported
(MAC based counters on port level are supported).
„ Queue counters on uplinks are not supported.
„ View status of system memory is not supported.
„ Operator authentication using Radius is supported under the restriction that
the Radius server must be reachable over the ISAM management VLAN.
Edition 01 - RL 2/Apr/2015 57/150
„ View troubleshooting statistics on the management interface (ICMP, ARP,
TCP, UDP) is not supported.

„ Generic restriction related configuration details are already included in the
CLI/TL1 command guides for future readiness.

„ The same management protection mechanisms to increase IP security, as
described for 7363 ISAM MX, apply to 7367 ISAM SX.
„ ANSI qualification of the 7367 ISAM SX-48 (3FE-68617-AA) is pending. The
system is only available for lab use in this release. The qualifications
pending are:
· Safety: UL/CSA 60950-1, 21, 22
· EMC: FCC part 15 Class A
· Telcordia SR-3580 NEBS Level 1
· Telcordia GR-63-CORE
· Telcordia GR-1089-CORE
Following restrictions apply to the functionality of the 7360 ISAM FX and 7367 ISAM
SX in R5.2:
„ MAC movement is not working, i.e. Learning a MAC address on two
network interfaces or two LT / subtending (/ user) interfaces or two BP:
perform MAC movement, i.e. the last one takes priority. The implication is
that the ISAM will not perform the role of detecting and preventing DUP
MAC@ within a VLAN.
Following restrictions apply to the functionality of the 7367 ISAM SX-12VP in R5.2:
„ The USB craft port of the 7367 ISAM SX-12VP requires driver software when
used with a Windows® operating system. On a computer connected to the
Internet, this driver will be installed automatically by Windows®. If the
computer cannot be connected to the Internet, the driver files can be
retrieved beforehand from the URL
http://www.exar.com/common/content/document.ashx?id=1596
(accurate as of this writing).
„ The 7367 ISAM SX-12VP requires two software items, one for the DSLAM SW-
item, one for the GPON ONT SW-item. When the software is loaded via
AMS, the GPON ONT SW-item is not loaded automatically. For an upgrade
of the GPON ONT part, that software must be loaded as described in
Appendix B.
6.2 R5.2 Restrictions
Nr Id Rel. note entry

7363_GPON
1 ALU02037947 Title: Multicast traffic blocked in NNI transparent mode
Problem Description : In NNI transparent mode, the7363 MX registers
to the FX 7360, both the 7360 OLT and the 7363 MX, enable igmp
proxy, then join 1024 multicast group. When the multicast group is
being removed and rejoined, the multicast traffic gets blocked
Workaround : leave multicast group and join 1024 multicast group
again Impact : multicast traffic is blocked
2 ALU02040265 Title: Sometimes ONT re-ranges after switchover from pon1 to pon2
Problem: Sometimes ONT re-ranges after switchover from pon1 to

pon2. This causes traffic outage time between 5 to 15 seconds which
is the time to re-range to new PON.
Workaround: None, traffic recovers after ONT is re-ranged.
7363_L2 Forwarding
3 ALU02034177 Title: Trouble shooting counter is direction (US/DS) unaware on MX
Problem: Trouble shooting can be activated only on one line. Once
activated it shall count particular events. This counting is performed
through a single set of counters. If a frame is received from the user
then it is an up frame. If a frame is received from the network it is a
down frame. But for any received frame (with the same error) the
same counter is updated. This leads to confusion as for frames
received from the network an up counter is incremented.
4 ALU02040223 Title: IOP : ATM PPPoX crossconnect failure against ZTE H368N CPE
Problem: When two ATM PPPoA crossconnect sessions are setup using
a ZTE H368N modem, it may take several retries before the session
becomes stable (max 30 sec). This is not seen consistently.
7363_QoS
5 ALU02062586 Title: RELT-A: all US packets are handled as if they have the same prio
Problem: All US packets are handled as a single pipe, there is

prioritization using the pbits indication. High priority packets may be
dropped if there is a congestion on the backplane.
7363_Synchronisation
6 ALU02052824 Title: SyncE on 7363 MX has an inconsistent port naming in alarm
occurance and in alarm report
Problem: Port identification in CLI is inconsistently displayed in CLI
alarm report as nt-a:xfp:1 and in the alarm event as nt:xfp:1, while
these notations should line up.
7363_TL1
7 ALU02044040 Title: TL1 - Configuration of qos DEFPRIORITY on vlanegport is not
applied
Problem: The configuration of DEFPRIORITY on vlanegport does not
take any effect. The qos priority is not displayed on vlanport in CLI
and the configured priority in TL1 is not applied on US packets, instead
the default qos priority is applied.
Edition 01 - RL 2/Apr/2015 59/150
7367_CLI
8 ALU02051648 Title: Configuring ipv6-mcast-ctrl on S vlan gets denied
Problem: When, through CLI, the command ipv6-mcast-ctrl on S+C

vlan is launched, it gets denied. But when it is tried on outer S vlan, it

gets enabled successfully.
7367_OAM
9 ALU02045967 Title: Duplicate mac alarm is not raised
Problem Description: When a static MAC Address is configured from a
user port, and the same source Mac Address flow from GE uplink port
is created, the Duplicate mac alarm is not raised.
Workaround: None Impact : Duplicate mac alarm is not raised
ADSL
10 ALU02040096 Title: Slower initialization time for ADSL2+ PTM bonding
Problem: The initialization for an ADSL2+ PTM bonded group has
increased by approximately 40 to 60 seconds, over the range of loop
lengths.
CLI
11 ALU02044443 Title: CLI command error message is not clear
Problem: Command "configure pppox-relay cross-connect client-port
vlan-port:1/1/12/1:302 default-priority 4 vlan-id 302 " reports "referred
instance does not exist" . They should report like "PPPox-relay cross-
connect engine does not exist."
12 ALU02051543 Title: Mac-learn-ctrl parameter is using numbers instead of more
readable text values
Problem: This issue is about a newly introduced R5.1 CLI command
(mac-learn-ctrl) which is not conforming with the CLI standards. mac-
learn-ctrl is used along with numbers 1,2,3 instead of enabled,
disabled, bridge-port-inherited.
13 ALU02059589 Title: Unable to assign the default value to param-a in case of VDSL
and VDSL2 for all PBO band(from 1-5)
Problem: In Cli,Range for power back off parameters for each
upstream band (from 1 to 5 ) for parameter a is (0,4000-8095) with
unit: 0.01 dBm/Hz but in MIB and TL1 it is showing as (4000-8095) with
unit 0.01dBm/Hz.
DPoE
14 ALU02030054 Title: When greater than 256 cmts bundles exist, retrieval of cmts or cm
configurations may not contain the entire list
Problem: When greater than 256 cmts bundles exist, retrieval of cmts
or cm configurations may not contain the entire list.
15 ALU02032473 Title: The downstream classifier can only classify on up to 64 bits of
IPv6 addresses
Problem: While the range of prefix addresses is 0 to 128, the FPXT-B
can only classify on up to 64 bits of IPv6 addresses. Anything above 64
bits will be treated as 64.
16 ALU02053382 Title: Show dpoe service vpls ip-addr does not display IPv6 address
Problem: Show dpoe service vpls ip-addr does not display IPv6
address, only IPv4 addresses are supported
17 ALU02056609 Title: FPLT-A pon operational state is showing down when retrieved via
snmp or via CLI
Problem: When retrieving pon operational state via snmp on the FPLT-
A, as in snmpget ifOperStatus, or snmpwalk of ifTable, the operational
status is being returned as INTEGER: down(2). When retrieved via CLI
with the command 'show interface dpoe pon' it shows 'line protocol:
down.' However, the pon is operating normally and transporting error-
free traffic. This problem is not present on the FPXT-B.
Workaround: The user can assess pon health by using the results of
'show cable modem' and various pon/cable modem statistics.
18 ALU02059839 Title: Some upstream packets dropped in FX-12 shelf
Problem: When upstream traffic load is 9.2-9.8Gb/s with fixed packet
sizes of 256 or 512 bytes towards one NT uplink, there are some frames
dropped by the FANT-F card. The packet loss rate is E-5. If packet size
is 1024 or 1518, there is no packet loss.
19 ALU02061441 Title: When operating in dual stack mode, and the IPv6 server is not
available, ONU FW downloads with statically provisioned vCMs will
take much longer than expected
Problem: If the IPv6 tftp server is unreachable for ONU FW download
when operating in dual stack mode, every ONU will wait 4 minutes
before trying the IPv4 tftp server. This issue is not applicable for
dynamically provisioned vCMs.
Workaround: Make sure the IPv6 tftp server is reachable in dual stack
mode when using statically provisioned vCMs.
20 ALU02062165 Title: During SNMP walk, with view-base control module enabled,a
number of time-outs are observed
Problem: When View-based Control Module (VACM) is enabled and
a view family is associated with a community string and that contains
one or more view sub trees, snmp walk might time out when walking
a view sub tree.
Workaround: For each SNMP view family that contains sub trees,
create a new rightmost subtree in this view family. When all existing
subtrees in this view family are on the left of this added subtree this
issue won t occur.
21 ALU02062776 Title: CLI command "info configure cm" can not display ipv6-classif-pf
configurations
Problem: CLI command "info configure cm" can not display ipv6-
classif-pf configurations.
Workaround: Use "info configure cm ipv6-classif-pf" to retrieve
configurations.
22 ALU02049405 Title: Cofiguring tpid 0x88a8 requires the service tpid list to also be
updated
Problem: After modifying the port tpid to 0x88a8, 0x8100 traffic
doesnot pass
Workaround: When the Port tpid is configured, the tpid list of the Port
is overwritten with port tpid. Add this to port tpid list in addition to
service tpid which this port is a part of.
Equipment
23 ALU02036122 Title: SFP not detected in FNIO-A port
Problem: After performing a high number of consecutive NT
switchovers, it was seen that the SFP 3FE55743AA in one of the FNIO-A
ports was not detected. Problem disappears after plug-out/plug-in of
the SFP
Workaround: Use SFP 3FE55743AA in NT faceplate port
Edition 01 - RL 2/Apr/2015 61/150
24 ALU02040523 Title: Electrical uplink SFP can not recover in cage one
Problem: The electrical uplink SFPs in cage 1 do not operate properly
in 100M configuration. There are no issues for optical SFPs

Workaround: Use other uplink ports for electrical SFPs

25 ALU02040868 Title: Sfp port not responding after several resets
Problem: Using a copper SFP in one of combo ports of the lower 4
ports (5-8) in FNIO-B, after many successive iterations of NT Reset/SWO
data traffic may be impacted and ISAM may become unreachable.
Workaround: Use either fiber SFP or in case RJ45 is needed, use direct
the RJ45 port rather than the combo port
26 ALU02049097 Title: IPv6 traffic pushing CPU load to 100%
Problem: When IPv6 (ND,MLD,DHCPv6) packets are sent downstream
at a high rate (600 pps) CPU load of LT reaches 100 %
Workaround: Apply filters in NT to block all IPv6 traffic if possible
GPON OLT
27 ALU01943546 Title: If Type B protection is used then the C+ SFP link gain is reduced
by 0.7 dB to ~31.3 dB
Problem: When Type B protection is enabled and C+ SFPs are used
with FEC enabled, then ~31.3dB optical link budget is achievable
instead of the regular 32dB. This is due to a stricter optical burst
detection needed to meet the Type B switchover requirements.
Workaround: If the FEC gain decrease would pose a real problem for
an operator, it is possible to modify the burst detection strictness via
T&D, however with an increased risk of Type B protection switchover
issues (depending on the used type of C+ SFP). Please contact
product support if this would need to be considered.
28 ALU02026438 Title: PON and ONT utilization counts do not reflect downstream drops
on the NGLT-A card
Problem: The frame and packet counters used for PON and ONT
utilization are incremented for frames that would otherwise be
forwarded downstream but are ultimately discarded in the traffic
manager (such as when exceeding the bandwidth contract). Such
frames should be counted as dropped rather than forwarded, but
are not on this particular board. This problem is not present in other
GPON LT cards.
29 ALU02040862 Title: After continuous NT switch-overs, a port may stay down
Problem: After continuous NT switch-overs, a port on the NTIO may
stay down. Issue was seen after more than 100 switch-overs.
Workaround: Perform another NT swo or reboot the NT on which the
port is located.
30 ALU02043418 Title: The received signal strength measurement is not working with
10G EPON optics
Problem: The RSSI parameter olt-rx-sig-level, indicating the incoming
signal strength at OLT side, cannot be used.
Workaround: Read optical values on ONU side.
31 ALU02054197 Title: PON-utilization DBA congestion period values are inconsistent if
more than 512 TCONTs
Problem: PON-utilization DBA congestion period (dbacongperiod)
values shown with the "show pon utilization current/previous-interval"
commands are inconsistent when 512 or more TCONTs are
provisioned on a PON interface. If the provisioning model uses 512 or
more TCONTs per PON, threshold crossing alerts should be used with
sufficient security factor (around 10%).
32 ALU02054454 Title: There is no inactive alarm when ONT reboot
Problem: In case of reboots, as long as the ONT comes back in
service within a very short period of time, no INACT alarm may be
raised, due to alarm suppression.
33 ALU02055065 Title: ONT INACT Alarms After LT Re-Seat
Problem: Sometimes after an LT re-seating, unexpected ONT INACT
alarms may be observed. These alarms clear on their own and ONTs
recover the service.
34 ALU02060742 Title: PON-Utilization: all ONT utilizations may not be shown if ONT
index not specified
Problem: The CLI commands "show equipment ont utilization current-
interval" and "show equipment ont utilization previous-interval" should
show all ONT utilization values, when enabled, if no ont-index is
specified. However, in the case that a PON is configured with no
ONTs, some subsequent ONTs may be omitted.
Workaround: When a specific ont-index is given in the above
commands then the values are properly displayed. Eg., "show
equipment ont utilization current-interval 1/1/1/1/1" or "show
equipment ont utilization previous-interval 1/1/1/1/1"
35 ALU02064493 Title: Power shedding feature: configuration not ONU reset-safe
Problem: The pwd-override field can be configured on a UNI port by
a command like: configure ethernet ont 1/1/9/1/1/1/1 pwr-override
enable. When thus configured, the OLT will send the right pwd-
override value in ME, however, after ONU reboot, the OLT will send
the default pwd-override value in ME.
L2 Forwarding
36 ALU02039313 Title: Enabling l2cp-transparent option blocks frames that are
transported with setting disabled
Problem: Enabling l2cp-transparent option in ASEoLS VLAN blocks
traffic that was transported with setting disabled. Traffic blocked from
LT to NT includes frames with destination MAC addresses:
01:80:C2:00:00:11 - 01:80:C2:00:00:1F 01:00:0C:CC:CC:CC
01:00:0C:CC:CC:CD 01:00:5E:00:01:28 09:00:2B:00:00:05
01:80:C2:00:00:14 01:80:C2:00:00:15 01:00:5E:00:00:02 or any multicast
MAC address
37 ALU02042941 Title: Automatic:ipoe-ppp not fully working
Edition 01 - RL 2/Apr/2015 63/150
Problem: The encapsulation "automatic:ipoe-ppp" intends to cover
the auto-detection of 4 encapsulations LLC-SNAP-bridge, VCMUX-
bridged, LLC-nlpid, VCMUX-PPPoA. The auto-detection of a particular

type only makes sense in case there is the corresponding forwarding

configuration. The forwarding configuration for the bridged

encapsulation methods requires (amongst others) the configuration
of a BridgePort and a PortVlan. The forwarding configuration for the
PPPoA encapsulation (includes llc-nlpid) requires the configuration of
a PPP client port. With such a full configuration the system forwards
the packets as intended. If however the auto-detection is planned to
detect only between the 2 bridged encapsulations and
correspondingly only a BridgePort and a PortVlan is created, then the
autodetection does not work.
Workaround: Configure also a PPP client port. However, this does not
do exactly what is intended: in case PPP is detected on top of one of
the bridged encapsulations (PPPoE), then the packets are forwarded
along the PPP client port which basically means a new PPP session is
established from the system with the source MAC address of the
system.
L3 Forwarding
38 ALU02042063 Title: Storm of ICMPv6 neighbor solicitation packages got overloading
LTs and traffic lost
Problem: When sending a lot (600pps) of IPv6 Neighbor solicitation
packets downstream, the load on the LT is getting very high.
39 ALU02049083 Title: received MLD at user side is dropping to zero
Problem: Received MLD at user side is dropping to zero
LineTest
40 ALU02058758 Title: MELT Feature blocked on NVLT-N with release ISAM R4.5.03h
Problem: When performing a MELT test with Group Test option
(without enabling PPA detection), the MELT feature is not working on
some NVLT-N in ISAM FD in 4.5.03h. The result of the test status is
reported as Unknown value(0) on AMS.
MPLS
41 ALU02017674 Title: MPLS FRR revertive behavior is not hitless
Problem: In case of revertive behavior, once the failure is cleared, the
working path is automatically re-established. However the resulting
switchover to the primary LSP is not hitless: there is a 25 ms impact on
traffic.
42 ALU02017867 Title: MPLS FRR revertive behavior results in temporary duplicate
unknown unicast traffic
Problem: In case of revertive behavior, once the failure is cleared, the
working path is automatically re-established. A Make-Before-Break
(MBB) mechanism is used to avoid traffic impact. However for a short
time, unicast frames with an unknown destination MAC address will
be duplicated
43 ALU02047636 Title: EPIPE service does not add the MPLS header after reboot or
switchover
Problem: After reboot or switchover in a redundant NT system, the
MPLS header is not added to egress traffic out of a spoke-sdp of an
EPIPE service. This may happen in case the SAP and SDP of an EPIPE
service belong to different NT units.
Workaround: While configuring an EPIPE service in a redundant NT
system, first configure the SAP and then bind the SDP to the EPIPE
service only after the SAP is operational. In addition, in case the
operator sees the SAP is not operational after reboot, the EPIPE
members can be removed (since the service is already down due to
SAP being down) and then re-configured in suggested order.
Migration
44 ALU02055437 Title: Sporadic rollback failure from R5.2 to R5.1
Problem: In the scenario of upgrading from R5.1 to R5.2 followed by
roll back to R5.1, it happens sporadically that the rollback fails due to
a race condition.
Workaround: Execute rollback again
45 ALU02055837 Title: Misleading download failure error during ONT SW download
Problem: Depending of number of ONTs and size of the ONT SW load,
the step ontDownloadandActivate in PBMT migration script may fail
with an error : "Download failures exceeds The Warning Threshold"
due to timeout. However download will still complete successfully.
Workaround: Increase timeout-values
ONT_DWLD_PROGRESS_TIMEOUT=2600 and
ONT_DOWNLOAD_TIMEOUT=2700 in file param.cfg
Multicast
46 ALU02040837 Title: MCASTLOSS alarm did not clear after deleting corresponding
mcast monitor
Problem: MCASTLOSS alarm did not clear after deleting mcast
monitor when two mcast channel monitoring configured and they
have same mcast groups
Workaround: Clear the alarm by deleting the other mcast monitor
(same group, but different vlan)
47 ALU02059544 Title: : Compress MC source table during migration NOK
Problem: Doing migration from a R4503 database towards R52 the
multicast-source table isn't compressed.
Workaround: Replacing the table manually after the migration with
service impact.
OAM
48 ALU01996535 Title: Delay of greater than 5000 microsec can be observed for MULTI
NT lag DM sessions
Problem: When ports from Active and Standby ports form a lag and a
DM session is enabled on MEP over the lag sap or DM session is
enabled on MEP over standby port sap, a max delay of greater than
5000 microsec may be reported.
49 ALU02040174 Title: Queue-drop alarm is getting triggered even if tca dis-frame-th
parameter is not configured
Problem: Even if the tca dis-frame-th is not configured, the queue-
drop alarm could be raised.
50 ALU02046368 Title: Sporadically LT may not boot successfully when upgrade LT from
NGLT-A to NGLT-C
Problem: Sometimes the LT may not boot when doing the upgrade in
following order : replan the board from NGLT-A to NGLT-C, then
unplug NGLT-A and insert NGLT-C into same slot. This is not the
rcommended order. Preferred order : first replace the old board with
the new one, and then replan the board.
Edition 01 - RL 2/Apr/2015 65/150
Workaround: Reboot new board (NGLT-C) by CLI
51 ALU02052498 Title: Invalid Data Flag will be set in LM Proactive in a 15-min interval if
no LMRs are received from the peer throughout the interval

Problem: In the LM Pro-active implementation in LT,in a 15-min interval
if there are no LMRs received from the peer throughout the
interval,then the Invalid Data Flag will be set to 1 in the prev-15 min
stats of that particular interval,even though the measured time of the
interval is not 910 secs.
52 ALU02060233 Title: ONT card creation failure under stress test
Problem: In a stress test scenario, performing configuring and
unconfiguring the following entities in quick succession, sometimes
ONT card creation failure might be observed : FGLT-A, PON, ONT,
Bridge Port, VLAN Port, IGMP channel
Workaround: ... None.
Redundancy
53 ALU02031862 Title: ONT inactive alarm problems with Type-B protection
Problem: In two cases inactive alarm reporting and clearance have
been observed not to be as expected. First case, in A2A protect
group, primary pon fiber cut and the secondary pon admin down,
ont inactive alarm couldn t be cleared. Second case, A2A protect
group, both pon admin down, ont inactive alarm cleared. The ont
inactive alarm couldn t be triggered to re-occur as expected when
primary pon is admin-up.
Workaround: In the first case, if both primary pon and secondary pon
admin down, the ont inactive alarm could be cleared. In the second
case, after both pon admin down, the ont inactive alarm could be
triggered to re-occur by first admin up the pon who caused the ont
inactive alarm clear.
54 ALU02061736 Title: UNI port is OOS when NT switchover and Type-B protection
switchover at same time
Problem: In case Type-B protection switchover is triggered
simultaneously while NT switchover is happening, it may happen that
some UNI ports become OOS
Workaround: Admin dn/up UNI
Security
55 ALU02063203 Title: 802.1x - continuous authentication/logoff at high frequency may
lead to NT reset
Problem: Performing continuously authentication/logoff at high
frequency (> 20 sessions per second) may lead to NT reset
Synchronisation
56 ALU02040807 Title: IEEE1588 PTP packets dropped during congestion with partial LAG
failure
Problem: IEEE1588 PTP clock synchronization packets may be
dropped incorrectly during traffic congestion at NT when a Link
Aggregation Group has some but not all links disconnected.
Workaround: The clock synchronization is restored when the traffic
overload condition is removed, or when the full LAG group is restored.
VDSL
57 ALU02052016 Title: IOP : sporadic re-init of BLV vectored lines against Sagemcom
5310
Problem: When the vce profile is set with vce-gain-mode during-
showtime and many lines orderly leaves, we see a number of other
lines leaving showtime on the Vectored group, equipped with the
Sagemcom 5310 FW 7_247D (PHY 39f2) .
58 ALU02062835 Title: Carrier-data-mode could not be enabled on 7363 MX
Problem: Carrier-data-mode could not be enabled on 7363 MX,
when we get a VP LT links connection error or when the VPLT links
status change after changing VCE profile.
59 ALU02063855 Title: No sync when connecting non-vectoring capable bonding CPE
in ZTV mode
Problem: The bonded lines of a non-vectoring capable bonding CPE
are not coming in showtime when these lines are part of a vectoring
group using the ZTV (Zero Touch Vectoring) mode. Work-around: use
a G.Vector compliant CPE Impact Customer: All customers using non
G.Vector capable Bonding modems and applying a ZTV profile
Edition 01 - RL 2/Apr/2015 67/150
7 Migrations

Migration to R5.2 is supported from:
„ R4.3 releases
„ R4.4 releases
„ R4.5 releases
„ R4.6 releases
„ R5.0 releases
„ R5.1 releases
Detailed SW Installation Guidelines for the ISAM Software are described in the
ISAM SW Installation Guide: 3HH-07196-AAAA-RJZZA.
8 Premium Packages
Premium Package concept:
„ Premium Packages are bundles of features allowing operators to extend
the ability to deliver premium services to the subscribers.
„ Premium packages require separate licenses (refer to PPP), which give
the customer the right to use the features in the contained packages for
the corresponding amount of lines. Therefore the features of these
packages are not part of the current Release SW-update specified in the
roadmap.
„ The features of the Premium Packages are defined in the specific
roadmap for each customer.
„ The number of customer “Right to Use” is limited to a contractually
committed number.
„ Premium Package features may be checked (audit) at the customer
site. If the number of “Right to Use” is exceeded the customer is obliged
to purchase additional SW licences.
„ These additional features within the Premium Packages will only receive
technical support if the “Right to Use” is not above the contractually
committed numbers.
„ The Premium Packages desribed are applicable for:
o 7302 ISAM
o 7330 ISAM FTTN
o 7360 ISAM FX
o 7356 ISAM FTTB REM
o 7357 ISAM FTTB SEM
o 7363 ISAM MX
o 7367 ISAM SX
Depending on specific platform characteristics or applications (xDSL, GPON,
equipment resiliency, …) a specific package might not apply.
Note: In case of GPON application, the features as described in the below

sub-sections are subject to the support of the respective ONT being used.
This is especially the case for the ONT-based DSL and Voice Services. Please
refer to the ONT Customer documentation if the respective feature is being
supported by the ONT.
8.1 Premium Packages Equipment
Edition 01 - RL 2/Apr/2015 69/150
ISAM Redundancy
„ ISAM Redundancy license for NANT-A on 7302 FD and 7330 FD; for NANT-

D/E and FANT-F, NT Load Sharing SW license is applicable.

„ The following architecture can be supported.
NT Load Sharing
„ NT Load Sharing license for high capacity NTs on 7302/7330 FD and 7360
FX
„ The features enabled with this licence cover:
o NT redundancy, active-active
o sub-1s switching capability
o NT load sharing
o LT load sharing
2.5 G per LT
„ Increase the data-rate per line or per user
„ Between a high capacity NT (NANT-D/E), FANT-F and NRNT-A and a high
capacity LT (e.g. NVLT-P/Q or NGLT-A/B) the internal link speed can be
increased from 1 Gbps to 2.5 Gbps.
„ To effectively increase this internal link speed , this “2.5 Gbps per LT”
license is required. Else it will be limited to 1 Gbps for even these high
capcity boards.
„ This capability is enabled per ISAM/System or shelf, and can not be
enabled per LT or slot.
„ This license is also applicable for remote LTs in a REM and connected via
a 2.5G optical link to an NT/NTIO in 7330.
10 G per LT
„ Between a high capacity NT (NANT-E/FANT-F) and a high capacity LT,
the internal link speed can be increased from 1 Gbps to 10 Gbps.
„ To effectively increase this internal link speed , this “10 Gbps per LT”
capcity boards.
20 G per LT
„ Between redundant high capacity NTs (e.g. NANT-E) and a high
capacity LT, the internal link speed can be increased from 1 Gbps to 20
Gbps.
„ To effectively increase this internal link speed , this “20 Gbps per LT”
capcity boards.
40 G per LT
„ Increase the data-rate per line or per user by synchronising the LTs with
NTs (either simplex or duplex) at 40 Gbps
„ Between a high capacity 480 Gbps NT (FANT-F) and a high capacity LT,
the internal link speed can be increased from 1 Gbps to 40 Gbps
„ To effectively increase this internal link speed, this “40 Gbps per LT”
capcity boards
enabled per LT or slot
8.2 Premium Packages Connectivity

Connectivity includes licenses
„ PPPoX Relay, license per subscriber: enabling either PPPoA to PPPoE
relay or PPPoX relay with MAC@ concentration
Edition 01 - RL 2/Apr/2015 71/150
„ Subscriber Authentication, license per subscriber: Authentication of
subscribers based on 802.1x and Radius server

„ IPv4 Security, license per subscriber: all mechanisms enforcing IPv4

security: vMAC, IPv4 address anti-spoofing,ARP relay / proxy and IP filters

(ACL)
„ IPv6 Security, license per subscriber: IPv6 antispoofing, ICMPv6 filtering
„ IPoA encapsulation, license per subscriber: Enabling IPoA encapsulation
for either VLAN-CC or IP routing, IP Routing Re-factoring (IPoA)
„ IPv4 Forwarding, license per subscriber: enabling basic routing at ISAM
level, including IGP protocols (RIP, OSPF,IS-IS); practically, this means
enabling IPv4 routing at NT
„ IPv6 Forwarding, license per subscriber: Enabling IPv6 routing at ISAM
level, including IGP protocols (OSPFv3); Practically, this means enabling
IP routing at NT
„ BFD, license per node, for IHUB NTs only: used for IP routing and MPLS
resiliency schemes to get a faster detection of the broken link
„ MPLS, license per node, for IHUB NTs only: MPLS for residential & business
users
„ MPLS+, license per node, for IHUB NTs only: DOD, LDP support for Inter-
area LSPs
„ MPLS OAM, license per node, for IHUB NTs only: MPLS ping, MPLS
traceroute, etc
„ MPLS Advanced Resiliency, license per node, for IHUB NTs only: MPLS LSR,
MPLS FRR
„ PIM-SSM, license per node, for IHUB NTs only: this is a specific routing
protocol for multicast traffic.
„ Enhanced Subscriber Management Lawfull Intercept, license per node:
this license is part of the Enhanced Subscriber Management Package.
When enabled, it allows for monitoring a limited set of lines.
„ User-to-User Communication, license per node: allows for user to user
communication via the ISAM only
„ BGPv4 routing protocol
o Content: BGP allows to integrate the ISAM in a network where route
advertisements are performed through an IGP (e.g. IS-IS or OSFP)
and an EGP (BGP), typically in a Multi-VRF environment
o Applicable Standards: RFC4271, RFC1997
Available (optional) license / network model:

PPP Subscriber
IP IP
Network Model concent Authenticati IPoA Comment
security routing
ration on
PPP Subscriber
IP IP
Network Model concent Authenticati IPoA Comment
security routing
ration on
PPP Concentration only
required if PPPoA or
PPP based HSI ü - - - -
PPPoX concentration is
used
Subscriber
DHCP HSI/Multi-
Authentication untypical
Media - ü ü - -
IP Security : untypical
VLAN-CC
(potentially vMAC)
Subscriber
DHCP HSI/Multi- Authentication : not
Media - ü ü - - deployed today
i-bridge IP Secure Forwarding
advised (E-i-Bridge)
IP Secure Forwarding / IP
DHCP HSI/Multi-
Routing required
Media - - ü - ü
IPoA untypical
IP routing
Optional BGP
Business L2VPN - - - - - Transparency required
Two approaches :
· PPP based with
potential PPPoA
Business L3VPN ü - - ü - relay or MAC@
concentration
· IP based with
potential IPoA encap
8.3 Premium Package Applications Video

Video License, including IGMPv3
„ Video License; license per subscriber;
„ Supports IGMPv3, DoS protection for IGMPv3, Increase mcast source
table, IGMP echo client/IGMP msg forking
Video Statistics
„ Video Statistics; license per subscriber;
„ Call Data Records (CDR), accessible via FTP, record all zapping actions
of the end user, by tracking user-id, channel-id and timing information.
The CDR generation can be customized (minimum viewing time before
a CDR is generated, use of intermediate CDRs, etc.).
„ Call Data Records available via Syslog, in near real-time.
Video Wholesale
Edition 01 - RL 2/Apr/2015 73/150
„ Video Wholesale; license per subscriber;
„ Cross-VLAN multicast: infeed of channels from multiple VLANs. Service

from different providers is segregated in the network.

„ Channel package policing. Allows offering end-users restricted access
to a specific set of channels from a selected subset of content providers.
„ Bundles of channels, BW management and SLA per provider. This
supports the BW management for wholesale environments, both in a L2
and in a L3 aggregation network.
„ Statistics on service fulfilment per channel and per bundle. Feedback on
SLA and service fulfilment per provider.
„ IGMP Source Specific Multicast :
· Distinguishes multicast channels by group IP-address and source IP-
address, the client (STB) sends IGMP messages that not only specify
the group IP-address but also the source IP-address of the video
server.
· Video service wholesale (L2), different service providers can
choose group IP-address for their channels independently. Group
IP-address from different providers may overlap.
8.4 Premium Packages Applications Voice
8.4.1 Premium Package ISAM-V SIP

The ISAM-V SIP Premium Package delivers the ETSI SIP PSTN (POTS) equipment
practices.
This SW package is only applicable for voice line boards inside ISAM shelves (so-
called ISAM-V). It is not applicable for voice on ONTs.
The IP address and VLAN scheme in SIP architecture is delivered with a CDE
profile.
There is support of “SIP restoration”, “SIP-session timer”, “POTS T38 Fax over IP”,
“Lawful Interception” and supplementary POTS-services: such as third party
conference and explicit call transfer.
SIP PSTN (POTS) for ETSI equipment practices

„ The ETSI Equipment Practice will support POTS Basic call &
Supplementary services based on SIP protocol.
„ The value of this Application is that the Network evolution to complete
SIP based architecture is an obvious trend in the ETSI markets. It allows
migration to SIP on current and future H.248 installed base via SW
upgrade preserving customer HW investments. No new LT type is
necessary for this.
„ The Applicable Standards refer to RFC SIP (Session Initiation Protocol).
Evolution of POTS SIP to Tispan compliance

„ Key Business drivers for IMS/TISPAN are:
· Distributed architecture: Functional decomposition with
standardized interfaces allows for better scalability, geographical
distribution and multi-vendor network integration.
· Open Interfaces: Open interfaces allow for interoperability
between multi-vendor network elements and multi-operator
networks.
· Centralized Database: The home subscriber server acts as a
centralized subscriber and service database, providing OPEX
savings and allowing for more flexible service integration.
· Flexible AS integration: The standardized SIP-ISC interface with
multiple application servers triggering allows for fast introduction of
new applications and services.
· Enabler for Fixed Mobile Convergence: The converged IMS/TISPAN
architecture gives Access agnostic core, Multi-Access architecture,
Fixed Mobile network interworking, Converged applications,
Terminal independence, etc.
Note : The Applicable Standards refers to TISPAN (Telecoms & Internet
converged Services & Protocols for Advanced Networks) standard for SIP
Pots.
IP address & VLAN scheme in SIP architecture

„ The Basic SIP architecture is a distributed SIP UA for SIP protocol
termination, different from centralized server card in a H.248 case with
VLAN & IP address scheme for Signalling, Voice & OAM.
„ This implicates:
· Flexibility to support either distinct or shared VLAN approach for
Signalling and Voice traffic.
· Flexibility to support either distinct or shared IP address approach
for Signalling and Voice traffic.
· Flexibility to support either multiple or single SIP Signalling/Voice IP
address per system (per Node) in public or private IP address
range.
Edition 01 - RL 2/Apr/2015 75/150
· External OAM VLAN & IP address kept separated from Voice and
Signalling for security reasons.

„ The value of this Application is delivering a good performance and

reliability and the Flexibility for deployment model in terms of Subnet & IP

address scheme.
Downloadable country specific voice parameters

„ The CDE profile can be downloaded with country-specific voice
parameters. The download strategy for SIP is aligned with H.248.
„ The value of this application is that One SW package can support
multiple customers as CDE.
Downloadable SIP Service Profile

„ Allows to configure the following service related parameters:
· SIP call flow related parameters for loosely coupling / tightly coupling
services
· SIP headers (session-ID, PANI header, more in the future)
· Mapping on SIP methods/messages for distinctive ringing, MWI (more
in the future)
· Mapping on the tones for different call terminated scenarios
· Mapping on the tones with error code received from SIP server
Carrier Grade Applications
„ SIP POTS Termination ID Provisioning
· Termination ID can be generated with subscriber line physical info.
· Termination ID is generated according to data configured by the
operator / management system.
· Termination IDs is regenerated through updating syntax in profile;
System support to store and read out the generated Termination ID.
The Value of this Application is that it is easy and flexible to
·
generate with subscriber line physical info and it will also fasten the
provisioning and identification of the physical position of
Termination ID
„ SIP restoration
· SIP restoration improves the reliability for integrated services
supported in an IMS network architecture requiring the support of
Failover and Failback functionality for both equipment and
network related failures regardless of the physical location of
components such as the voice server in the network.
SIP restoration is specified by the TIPSPAN R2 (Feature Server 5000,
·
CPE Interface Specification, QDI ID 28575 reference sections 4.11
and 4.17 and TS 0373/96, Teil 4 Multi-Service Access Node (MSAN),
reference sections 2.2.1.1.12 and 2.9.4).
„ Lawful Interception
· The Lawful Interception (via Media Server) (LI) is a requirement in
most countries towards telecom operators. Operators are required
by law to provide intercepted communication data based on
legal warrants and procedures enacted by the host country.
· The value for this Application is that the lawful interception
function enables the telecom operators to meet the needs of
authorized organizations that are entitled to monitor subscriber’s
telecommunications activities.
The principle is the use of a Media Server as centralized Call Content
copy point.
„ SIP POTS 12/16 kHz Metering
· Provide the 12/16 kHz metering signal for SIP POTS users
Voice Functionality
„ SIP E2E negotiation of Dynamical payload type
· Dynamic payload number negotiation (range from 96…127) per
RFC3264.
· Following media type is able to have dynamic payload type in this
feature: telephone-event/8000 or DTMF relay with named
telephony events.
The Value for this application is that its guarantees a better
·
Interoperation among different devices on one network
„ SIP Subscriber control for POTS (PIN).
„ Support of SIP session timer
· The session time is conforming to RFC4028, used for a periodic
refresh of SIP sessions through a re-INVITE or UPDATE request.
The refresh allows both user agents and proxies to determine
·
whether the SIP session is still active and synchronize the session
state.
„ POTS T38 Fax over IP
· The Support of T38 (FAX over IP) allows for POTS service, support the
procedures for real time group 3 facsimile communication over IP
networks based on the SIP signalling protocol, compliant with ITU-T
T38 and IETF draft/V.152.
The performance of this feature is kept same as H.248 T38 feature.
·
„ POTS overlap dialling & open numbering
Edition 01 - RL 2/Apr/2015 77/150
· Support the overlap dialling mode with multi-invite method.
· When overlapped dialling mode is selected, the ISAM-V sends the

initial INVITE upon detecting a digit match, then, additional digit

input is acXDted on which an associated and subsequent INVITE

may be issued.
Supplementary service: POTS

Third Party Conference
„ The third party conference provides valued service for users to setup
third party conference in the user’s premises.
„ The third party conference is a useful C5 supplementary service, with the
function enabled in IMS solution, user can easily apply it as like it would
be used in legacy PSTN but with more flexible in service deployment.
„ Either use a Media Server as centralized Y-function point or the NPOT-B
as audio mixer with the loosely coupled mode.
Explicit Call Transfer
„ The feature Explicit Call Transfer (ECT) provides 3 modes for the
application service:
· Consultative call transfer – transferor has a communication with
transfer target before hang-up.
· Call transfer from a 3-way call – third party call is setup before
transfer or hangs up.
· Blind call transfer – transferor has no communication with transfer
target before the hang-up and doesn’t know if the service is setup
or not.
„ This is an important and useful C5 supplementary service, and provides
added-value for customer service deployment in IMS solution.
Call Waiting
„ Calling termination presses the flash-hook (and dials an additional digit)
to switch between the current called termination and a 3rd party.
Call Hold
„ Hard Hold: Allowing calling termination to Flash Hook once to put the
called termination on hold, and to Flash Hook once again to resume the
call with the hold termination.
„ Call Hold Consultation: Allowing calling termination to put an existing
call on hold and to initiate a second call to a 3rd party.
8.4.2 Premium Package Narrowband Integrated Line Test

Access SW
H248/SIP POTS
„ Support Group Test

„ Support AC voltage of user's line (AB, AG, BG)
„ Support DC voltage of user's line (AB, AG, BG)
„ Support Insulating resistance of user's line (AB, BA, AG, BG, A-Bat, B-Bat)
„ Support Capacitance of user's line (AB, BA, AG, BG)
„ Support Impedance of user's circuit ( AB, AG, BG)
„ Support Termination (M Socket detection)
„ Support AC & DC Current Test Normal Test
„ Support Feeding current (AB)
„ Support Dial Tone Delay of user's circuit
„ Support Howler Test Under Normal Test Condition
„ Support Howler Test Terminated by Test Operator
„ Support Rejection Error Code & Message Returned for Wrong Command
input
„ Support Status monitored
„ Support Resistance of user's loop (AB)
„ Support Block/Continuous Reading Tests
„ Support Line Reverse Normal Test
„ Support Line Reverse Test Terminated by Test Operator
„ Support Feeding Voltage in the line
„ Support Subscriber Private Meter Pulses Test
„ Support Talking with Subscriber Test normal test
„ Support Talking with Subscriber Test Terminated by Test Operator
„ Support Ring Subscriber with Auto Ring Trip Normal Test
„ Support Ring Subscriber with Auto Ring Trip Terminated by Test Operator
„ Support DP/DTMF Signal Normal Test
Edition 01 - RL 2/Apr/2015 79/150
„ Support DP/DTMF Signal Test Terminated by Test Operator
„ Support Cable pair identification tone test

H248 ISDN BA

„ Complete loopback with test pattern

• Loopback of full bit stream (B1 and B2 and D channel)
„ Loopback at ISDN LT and NT/NT1
• Self test on layer 1 by the ISAM-V: ISAM-V generates a test pattern and
activates a loopback at the LT + verification and evaluation of received
test pattern.
• Test towards the NT/NT1: ISAM-V generates a test pattern and activates
a loopback at the NT + Verification and evaluation of received test
pattern.
„ Electric line tests on the ISDN line card:
o Foreign DC voltage (A&B,A&G,B&G)
o Foreign AC voltage (A&B,A&G,B&G)
o Resistance (A&B,B&A,A&G,B&G)
o Capacitance (A&B,B&G,A&G)
8.5 Premium Packages Transport
8.5.1 Premium Package SmartDSL AN/VN
Virtual noise
„ Line stability has a huge impact on the Quality of Experience. An
unstable xDSL line, caused by crosstalk variations for example, can result
in service degradation and even service interruption. In a typical DSL
network, up to 25% of lines can be unstable leading to higher
operational costs, lower ARPU, and increased churn. The traditional
approach to stabilize lines, increasing the noise margin, results in a
significant bit rate loss.
„ The Smart DSL Virtual Noise (VN) is supported on 48p VDSL2 ETSI cards, for
VDSL2. VN is a technology invented by Alcatel-Lucent, that allow
operators to stabilize VDSL lines with minimal bit rate loss. Virtual Noise is
part of the VDSL2 ITU-T standard (G.993.2) and works with any standards-
compliant Customer Premise Equipment (CPE) that supports Virtual
Noise.
„ Alcatel-Lucent not only offers VN support in its ISAM product line, but also
offers consultancy services related to VN and the 5530 Network Analyzer
(NA), which is a line analysis and management system to support VN
deployments. Use of the 5530 NA for Smart DSL is optional.
8.5.2 Per Line Management

„ Allows overruling a selective set of parameters in the xDSL spectrum and
service configuration profile individually and per line without changing
the line profile itself.
„ Facilitates deployment of features such as Virtual Noise and Artificial
Noise in a customer-care environment.
8.5.3 Premium Package BB SELT Test Access SW
ISAM Broadband Simultaneous SELT measurements Package

„ Allows concurrent SELT (Single-Ended-Line-Testing) measurements per
ISAM and per LT: up to 5 per LT where the current ‘Lite’ SELT
implementation only supports 1 concurrent SELT per NT
„ Provides enhanced error codes when SELT test fails
„ Provides SELT state management to prevent conflicting actions triggered
by independent applications Example: SELT inspection started by
5530NA while line is being reconfigured by EMS
„ Scope: all ADSLx and VDSL2 LTs that support SELT on ISAM FD and XD
„ Advantage = Support of multiple concurrent SELT inspections per NT
enables, Usage of SELT in a helpdesk environment, Proactive use of SELT
inspections, Enhanced error codes facilitate integration of 5530 NA SELT
into operator’s OSS and brings SELT implementation in ISAM at same
level as SELT implementation in ASAM
„ Known chipset limitations in terms of number parallel SELT inspections:
· 48p ADSLx LTs: up to 5 concurrent SELT inspections per LT without
limitation.
· 72p ADSLx LT (NALT-E): up to 5 concurrent SELT inspections per LT
but max 1 SELT inspection per DSP. A 2nd simultaneous SELT request
on the same DSP is rejected with ‘out of resources' error code.
· NVLT-C/D: up to 5 concurrent SELT inspections per LT but max 1
SELT inspection per DSP. A 2nd simultaneous SELT request on same
DSP is rejected with ‘out of resources' error code.
· NVLT-P/Q: up to 5 concurrent SELT inspections per LT without
limitation.
Edition 01 - RL 2/Apr/2015 81/150
8.5.4 Premium Package MultiDSL

ISAM Support of 24k Downstream Interleaver for ADSL2plus MultiDSL SW Package

„ Extend support of downstream interleaver memory to 24k for ADSL2plus
mode of multi-DSL LTs
„ 24k Interleaver for ADSL2plus mode of NALT-E
„ 24k interleaver memory enables higher data rates with high impulse
noise protection
Integer INP 0 to 16 for ADSL2/ADSL2plus

„ Add support of INP_min values 3, 5, 6, 7, 9, 10, 11, 12, 13, 14, 15 and 16 for
ADSL2/plus on all multi-DSL LTs
„ Impulse Noise Protection (INP) is used to protect the DSL transmission
from impulse noise.
„ The INP_min is the minimum number of DMT symbols that can be
protected from an impulse of length (number of DMT symbols -1).
„ It offers also an increased protection against impulsive noise and a finer
control of INP_min settings. This allows to have higher bitrates than when
only powers-of-2 were supported
Support D_max up to 511 for ADSL2/ADSL2plus

„ D_max is the maximum interleaver depth supported by the system
„ Higher D values result in increased bitrates for higher INP setting. These
high INPs are becoming more common in video-grade deployments
8.5.5 Premium Package ADSL Backwards Compatibility

ADSL backwards compatibility
„ ADSL Backwards Compatibility license for VDSL ports is a license per
configured ADSL subscriber on a VDSL port;
8.5.6 Premium Package All Digital Loop

ISAM All Digital Loop SW Package
„ With Annex-J support on Multi-DSL LT (or ADL = all digital loop) the
POTS/ISDN baseband service is removed. This allows the US band to be
extended to lower frequencies, hence increasing US capacity.
„ All US PSD masks are supported, except masks ADLU-32 and ADLU-36 on
ISDN front-ends.
„ With this feature the operator can switch to ADL when voice services
become integrated into DSL transport (VoIP). Annex-J allows offering
increased US bandwidth in such case and Lowpass splitters are no
longer required and can be removed, saving cost and space.
„ Optimal performance is reached on the ADSL linecard optimized for
Annex-J operation, the NALT-M.
8.5.7 Premium Package Bonding

Bonding can be used to increase the rate or extend the reach, when two or
more pairs are available.
ISAM ADSLx Bonding

„ license per ADSLx bonding configured port
ISAM VDSL2 bonding

„ license per VDSL2 bonding configured port
8.5.8 Premium Package Business DSL

ISAM Business DSL Package
„ ISAM Business DSL SW Package is a license per configured Annex-M
subscriber;
8.5.9 Premium Package Enhanced SHDSL

ISAM Enhanced SHDSL Package
„ Enhanced SHDSL (G.SHDSL.bis) is a license per configured subscriber;
8.5.10 Premium Package UPBO Policing

ISAM UPBO policing Package
„ UPBO Policing is solving the problem of having lower performance on
long loops: a strong upstream signal on a short loop interferes with
weaker upstream signals on long loops.
„ With UPBO a lower Tx PSD on short loops will be introduced and a
stronger Tx PSD on long loops which gives a performance equalization –
similar upstream performance on short & long loops
Edition 01 - RL 2/Apr/2015 83/150
„ UPBO Policing is a license per configured subscriber where UPBO
policing can be used.

„ Scope : only for VDSL LTs

8.5.11 Premium Package Impulse Noise Sensor
ISAM Impulse Noise Sensor Package
„ Impulse Noise Protection sensor will provide a more accurate
configuration which results in higher bitrates.
„ ISAM Impulse Noise Sensor Package is a license per configured
subscriber;
„ Current approach to estimate IN is CRC Count: too coarse to measure IN
duration and inter-arrival time. The impulse Noise Sensor will define in
VDSL2 Amendment2 as optional feature the measurement of Impulse
Noise statistics in down- & upstream and will store histograms in DSLAM.
„ The advantages are :
· long term stats and monitoring of link quality
· more accurate configuration of INP (INP_min and Delay_max)
8.5.12 Premium Package Smart DSL SRA

Smart DSL SRA
Seamless Rate Adaptation license is for VDSL2 ports only, and per configured
subscriber. This license is part of the of the smart DSL family of features. Seamless
Rate Adaptation is standard included for ADSL.
8.5.13 VDSL 30a Profile

VDSL 30a
License per configured 30a profile on a VDSL port. Applicable for very short line
(f.i. 50m or max 100m) to offer bandwidth approaching 100Mbps DS.
8.5.14 Premium Package Reference Timing Source

SyncE Reference Timing Source
„ License per NT port on which SyncE is activated
„ ISAM can accept synchronization input not only via E1/T1 BITS, but also
via Synchronous Ethernet, for which this license is required
„ Synchronization input has three main applications:
o Mandatory to achieve the clock accuracy for mobile backhaul over
ISAM (in combination with NTR over xDSL)
o Mandatory for many customers for ISAM-V, where it allows for long
fax & modem calls, and increases achievable modem speeds
o More cost-effective for leased lines deployments using pseudo-wire
Synchronization input via synchronous Ethernet (as opposed to BITS) is
also possible in places where there is no BITS network (e.g. in cabinets).
„ Applicable standards : ITU-T G.8261/Y.1361 (formerly G.pactiming)
"Timing and Synchronization Aspects in Packet Network
Note: Use of BITS or SyncE external clock at the NT is required for GPON
applications
ToD (Time of Day) Reference Timing Source

„ License per ToD external input source configured as ToD reference
„ ToD reference source as input is used for phase/ToD synchronization,
mainly applied on Mobile Backhaul application for base-station sync.
8.5.15 Premium Package Smart DSL ARQ

Smart DSL ARQ
The standard ARQ license per configured subscriber is part of the of the smart
DSL family of features.
8.5.16 Premium Package MELT

MELT functionality
„ MELT functionality is applicable for dry DSL deployment where no POTS
or ISDN voice lines are offered. The default line test functionality is
SELT/DELT. NBLT on NPOT boards offer similar function (so MELT is not
applicable for ISAM-V solution)
„ The general strategy is to support integrated test solutions:
- DELT/SELT for lines that run DSL services
- Combined with NBLT in case these lines also run Voice/POTS services
- Combined with MELT in case pro-active maintenance of ADL (or dry
DSL) lines is needed
Edition 01 - RL 2/Apr/2015 85/150
8.5.17 Premium Package Green DSL

ISAM Green DSL L2

„ license for all lines or for a subset of all lines (e.g. for all video lines);
„ Allows the operator to reduce power consumption on multiADSL lines
8.5.18 Premium Package Vectoring

ISAM Vectoring Package
„ Vectoring is a noise-cancellation technology addressing the gap
between the theoretical maximum rate and the speeds that service
providers can deliver in typical field conditions.
„ Vectoring takes full advantage of existing copper binders by making
conditions in the field as close to ideal as possible.
„ ISAM Vectoring Package is a license per configured subscriber; i.e. per
line with a vectoring profile (BLV or SLV) associated
„ Applicable standards : ITU-T vectoring standard, G.993.5 (G.vector)
„ Scope: VDSL2 only; applicable for both Board Level Vectoring (BLV) and
System Level Vectoring (SLV)
8.5.19 Premium Package Zero Touch Vectoring

ISAM Zero Touch Vectoring Package
„ Crosstalk cancellation on legacy VDSL2 lines (i.e. on the non-vectored
and non-vector-friendly lines): this functionality allows to have vectored
lines in combination with legacy lines
„ Can be enabled/disabled per subscriber line
„ ISAM Zero Touch Vectoring Package is a license per configured
subscriber, i.e. per subscriber line with Zero Touch Vectoring enabled
„ Scope: all vectoring boards, be it Board Level Vectoring (BLV) or System
Level Vectoring (SLV) boards
8.5.20 Premium Package Type-B PON Protection

ISAM Type-B PON Protection Package
„ Large bundles of feeders in a cable or duct increase the risk of
intolerable repair times in case of a breach or an accident
„ Also the increasing number of split ratios and deployment of business
critical services highlight the importance of implementing PON
protection schemes.
„ ITU-T specification G984.1 describes multiple PON protection schemes.
ISAM GPON line cards implement Type-B PON protections defined in this
standard which addresses route diversity to the first splitter in a 1:1
arrangement.
„ The PON links of the ISAM can be configured in protection pairs on the
PON boards across the shelf (inter-card protection among cards of the
same type). In case of an active PON link failure, all traffic is switched to
the associated protection without service loss.
„ ISAM Type-B PON Protection Package is a license per configured PON
Protection Group
„ Scope: NGLT-A, NGLT-C and FGLT-A in combination with a FANT-F
8.5.21 Premium Package 40 km Differential Distance PON

Operation
40 km Differential Distance PON Operation
„ The differential distance refers to the relative position of the closest and
farthest ONTs on a PON with respect to the Central Office. Standard
PON operations are supported for ONTs placed on the PON across this
range. In normal operations a differential distance of 20 km is expected
to be deployed. In this scheme, the closest ONT distance is a
provisioned parameter.
„ The present premium feature allows to extend PON deployments to a 40
km differential range where the closest ONT distance is still a
provisionable parameter between 0 and 20 km. So in essence, the
farthest ONT on a PON can be placed at a 60 km distance from the
CO.
„ This behavior is defined on a per PON basis
„ The actual performance may depend on the power and sensitivity
characteristics of the ONTs that are deployed. Please check related
ONT documentation.
8.5.22 Premium Package Ethernet OAM

ISAM Ethernet OAM Package
„ Ethernet Connectivity Fault Management provides capabilities for
connectivity verification, as well as detection, verification & isolation of
connectivity failures, using specific maintenance points on LT user ports &
NT uplinks.
„ Applicable Standards: IEE802.1ag and ITU-T Y.1731
Edition 01 - RL 2/Apr/2015 87/150
„ ISAM Ethernet OAM Package is a license per MEP
„ Scope: all IHUB-based NT’s (NANT-D/E, FANT-F) and DSL LT’s

„ This license does not apply to xPON LT’s

9 Validated Voice Supplementary Services
The following is a list of representative POTS supplementary services that are
available via the ISAM Voice working in conjunction with the ALU MGC/IMS
iAGCF products for H248 and IMS/5420 CTS products for SIP. More extensive
treatment of the supplementary services supported is available in the
associated ALU IMS documentation.
Interoperability of the ISAM Voice with the 3rd party MGC or IMS cores is also
possible through commercial agreement.
The following relates to Voice on Voice LTs inside the ISAM shelves, not to voice
on ONTs.
9.1 H.248 POTS Supplementary Services
Supplementary Service 5020MGC12 5020AGCF

Hold For Enquiry [HFE] / Call Hold [CH] Y Y
Call Forwarding Unconditional (CFU) Y Y
Call Forwarding Busy (CFB) Y Y
Call Forwarding No Reply (CFNR) Y Y
Hot Line/Delay Hot Line Y Y
Calling Line Identification Restriction Y Y
Malicious Call Identification Y Not tested
Calling Line Identification Presentation Y Y
Outgoing Call Barring (OCB) Y Y
Do not disturb Y Y
Anonymous Call Rejection Y Y
Abbreviated Address (AA) Y Not tested
Incoming Call Barring (ICB) Y Y
Inhibition of Incoming Forwarded Calls

Y Y
(IIFC)
Administrative Call Barring Y Not tested
Alarm call Y Not tested

Call Waiting Y Y
Call Return Y Y
Edition 01 - RL 2/Apr/2015 89/150
Explicit Call Transfer Y Y

Three Party Service Y Y

CWID service Y Not tested
Distinctive Ring Y Not tested
Special Dialtone Y Not tested
VMWI via H248.3 ind package Y Not tested
9.2 H.248 ISDN BA Supplementary Services

Supplementary Service 5020MGC12
Change Password
Y
Calling Line Identification Presentation (CLIP) Y
Calling Line Identification Rejection (CLIR) Y
Connected Line Identification Pres. (COLP) Y
Connected Line Identification Rej. (COLR) Y
Call Forwarding Unconditional (CFU)
Y
Call Forwarding on Busy (CFB) Y
Call Forwarding on No Reply (CFNR)
Y
Incoming Call Barring (ICB) Y
Malicious call Identification (MCID)
Y
Outgoing Call Barring (OCB)
Y
Subaddressing (SUB)
Y
CLIR-O
Y
COLR-O
Y
Call Waiting (CW)
Y
Third Party Call
Y
Conference Call
Y
Hotline
Y
DDI (Direct Line)
Y
Call Hold [Retrieve] Y
UUS (User-User Signalling) Y
TP (Terminal Portability) Y
Alarm Call
Y
Do not disturb
Y
Multiple Subscriber number (MSN)
Y
Abbreviated Address
Y
Call completion to busy subscriber (CCBS)
Y
9.3 SIP POTS Supplementary Service
SIP POTS Supplementary service CTS 5420

Call Hold(CH) Y
Call Forwarding Unconditional(CFU) Y
Call Forwarding Busy(CFB) Y
Call Forwarding No Reply(CFNR) Y
Calling Line Identification Restriction(CLIR) Y
Calling Line Identification Presentation(CLIP) Y
Call Waiting(CW) Y
Explicit Call Transfer Y
Three Party Service Y
Call Barring (outgoing) Y
Call Blocking (incoming) Y
Hot Line Y
Anonymous Call rejection Y
Inhibit Call Forwarding Y
Edition 01 - RL 2/Apr/2015 91/150
10 Voice Package Performance

10.1H.248 POTS Performance
Note: The performance figures heavily depend on H.248 signaling call flows. The
data below is tested with ALU 5020 MGC12 as reference. The performance could
be different while IOT-ing with other softswitches according to the signaling
processing and behavior of different softswitches.
POTS Performance NVPS AC :
Standard Call Load Model Supp Performance Call Loss

Hold orted (BHCA)
Times Users
ETSI 90 sec Load 20k 5000 40k 1.00E-04

A
Load 27k
B
POTS Performance NVPS AB :

Hold orted (BHCA k)
Times Users
ETSI 90 sec Load 20k 5000 30k 1.00E-04

A
Load 27k
B
7363 ISAM MX H.248 POTS Performance :

Hold orted (BHCA k)
Times Users
ETSI 90 sec Load 768 192 5.1k 1.00E-04

A
Load 1.1k
B
Note Load A(Nominal load) : BHCA=n subscribers
*0.1Erl*3600/hold time
Note Load B(High load): BHCA=n subscribers *0.1Erl*3600/hold
time * 1.35
Note Performance is measured as BHCA
10.2H.248 ISDN Performance
ISDN Performance NVPS-A AC NBAT-B :
Standard Call Load Model Suppo Performance Call Loss

Hold rted
Times Users
ETSI 90 sec Load A 10k 2500 17k 1.00E-04
Load B 13.5k
ISDN Performance NVPS-A AB NBAT-B :
Standard Call Load Model Suppo Performance Call Loss

Hold rted (BHCA)
Times Users
ETSI 90 sec Load A 10k 2500 13.5k 1.00E-04
Load B 13.5k
10.3SIP Performance
ISAM-V SIP POTS Performance(SIP over UDP)

Call Hold Performance
Call Mode Call Loss
Time (BHCA)
36 call 36(NPOT-B) 5K 1.00E-04
24 call 24(NPOT-A) 90 sec 5K 1.00E-04
24 call 24(NPOT-C) 5K 1.00E-04
7363 ISAM MX SIP POTS Performance(SIP over UDP)

Call Hold Performance
Call Mode Call Loss
Time (BHCA)
Edition 01 - RL 2/Apr/2015 93/150
94/150
48 call 48 (3 RPOT-A)
16 call 16 (1 RPOT-A)
90 sec
5K
5K
1.00E-04
1.00E-04
11 DSL Interoperability
ALU preserves the right to implement IOP changes without being reflected in this
overview.
11.1CPEs for specific ISAM functionality

The table below lists the CPEs that Alcatel-Lucent has used to test the indicated
features.
ADSL Features
DT W503V Support of Annex-J masks
U-R compliance
Support of Annex-J masks
AVM 7270 G.994.1 amd 3 Annex-J
U-R compliance
DT W700V U-R compliance
G.994.1 amd 3 Annex A
Technicolor TG585nv2
Annex-A regression
G.994.1 amd 3 Annex B
Technicolor TG585inv2
Annex-B regression
Annex-M regression
Technicolor TG585v8
G.994.1 amd 3 Annex M
SagemCom F@ST 3504 Annex-A regression
Comtrend CT-5631E ATM bonding (ISDN)
Comtrend CT-5631 ATM bonding (POTS)

Cellipe 7130RG
Enhanced L2 mode
6Ae.A2101DmA/B
VDSL Features
TR-114 Region B Type A compliance
CellPipe 7130RG 5Ve.A2000 VDSL Region B Type B on Pots HW
VDSL Region B regression
TR-114 Region B Type B compliance
CellPipe 7130RG 5Ve.B2000 VDSL Region B regression
VDSL Type B on Pots HW
Motorola 7357 VDSL regression
AVM 7570 TR-114 Region B Type B compliance
Technicolor TG789nv TR-114 Region B Type A compliance
Technicolor TG789inv VDSL Region B regression
Edition 01 - RL 2/Apr/2015 95/150
SagemCom F@st3462v2 VDSL Region B Type B on Pots HW
TR-114 compliance

Comtrend CT5374 VDSL regression
G993.2 amd 3

CellPipe 7130RG 6Ve.A4111 PTM bonding
Sagemcom F@ST 4320 PTM bonding
ALU 7705 SAR-M 8-port VDSL2 bonding
Vectoring Features
SagemCom F@ST 5310 VDSL2 vectoring (SRA, g.INP)
SagemCom F@ST 3864 VDSL2 vectoring (SRA, g.INP)
Sagemcom F@ST 4320 VDSL2 vectoring (bonding)
SHDSL Features
Technicolor TG605s/ST620s SHDSL regression
ATM 4-wire bonding
Technicolor TG605s/ST620s
EFM 4-wire bonding
IMA 4-wire bonding
RAD LA-110
IMA 8-wire bonding
ATM 4-wire bonding
Technicolor TG628s
EFM 4-wire bonding
RAD LA-110PW NTR
1521 CLEM (Hatteras) Repeater
Elcon ZWR2MSKUDS Repeater
11.1.1 ADSL1/2/2plus Annex B support

The POTS 48p ETSI VDSL2 line cards support ADSL Annex B (ISDN) operating
modes. This allows that both POTS and ISDN CPEs to be connected to the same
line card if no ISDN overlay is present.
For ISDN CPEs, the same IOP restrictions apply as if it was connected to the ISDN
48p ETSI VDSL2 line card.
11.2NVLT-C and NVLT-D
11.2.1 ADSL1 and ADSL2plus interop

Minimum interoperability tests have been performed against the Alcatel-Lucent
ADSLx CPE wall (category 3). For these CPEs, full ADSLx functionality and optimal
performance cannot be guaranteed in the mentioned ISAM release.
Due to a common front-end for VDSL2 and ADSLx, the upstream sensitivity is
somewhat less, such that especially for long loops in the upstream direction and
with low noise the TR-100 and TR-67 performance requirements are not achieved.
Following performance TARGETS were set on straight PE04 loops (1).
In ADSL2plus (G.992.5) Annex-A mode on NVLT-C in interleaved mode:
„ Maximum reach under ETSI-FB noise (TR-100) of 3000m, compared to
3250m per TR-100.
„ Downstream bit rate under ETSI-FB noise within 95% of TR-100 (2).
„ Upstream bit rate under ETSI-FB noise within 90% of TR-100 (2).
In ADSL1 (G.992.1) Annex-A mode on NVLT-C in interleaved mode:
„ Maximum reach under ETSI-FB noise (TR-67) of 2750m, compared to
3000m per TR-67.
„ Upstream bit rate under ETSI-FB noise within 90% of TR-67 (2).
In ADSL2plus (G.992.5) Annex-B mode on NVLT-D in interleaved mode:
„ Maximum reach under ETSI-FB noise (TR-100) of 3000m as per TR-100.
„ Upstream bit rate under ETSI-FB noise max. 32 kbps below TR-100 (2).
In ADSL1 (G.992.1) Annex-B mode on NVLT-D:
„ Not tested
Important notes:
(1)Observation is that most listed CPEs in categories 1 and 2 get close to
the TARGETS but some CPEs may fall short. No performance
statement can be made for CPEs outside categories 1 and 2.
(2)Except for possible dips at some loop lengths.
11.2.2 VDSL2 interop

NVLT-C/D is not planned to be interoperable with CPEs based on former-
Connexant and Metanoia chipsets.
Edition 01 - RL 2/Apr/2015 97/150
For NVLT-C bitswap to and from 0 bits has successfully been tested in VDSL2
mode against CPEs based on a Broadcom BCM6368 chipset with 32a FW version.

Bitswap to 0 bits is not supported on Broadcom CPEs with older FW versions.

The NVLT-C is interoperable with Ikanos, Broadcom and Lantiq based CPEs but
only for certain tested CO and CPE combinations. General IOP can not be
guaranteed.
Before introducing a new VDSL2 CPE in the network, we advice careful IOP
testing upfront. Also specific CPE tuning against a particular CO SW version is not
recommended as it will prohibit introduction of more recent releases later on.
11.3NVLT-G/H and NVLT-M
11.3.1 ADSL1, ADSL2 and ADSL2plus interop

The ADSLx functionality has been extensively tested against following “reference
test CPE´s”:
„ Sagem F@ST3404 and Sagem F@ST3304 (ADSL2plus Annex A) for NVLT-G
only
„ Speedtouch 536i (ADSL2plus Annex B) for NVLT-H only
Also functional and performance tests have been performed against other ADSLx
CPEs (see IOP list). However, the test coverage was less than for the above three
CPEs.
Due to a common front-end for VDSL2 and ADSLx, the sensitivity is somewhat less,
such that especially for long loops in the upstream direction and with low noise
the TR100 and TR67 performance requirements are not achieved.
11.3.2 VDSL2 interop

The VDSL2 functionality has been extensively tested against following VDSL2 CPEs:
„ Comtrend CT5372 (based on BCM chipset) – NVLT-G only
„ Sagem BBOX2 (based on BCM chipset) – NVLT-G only
„ Netopia 7356 (based on IKA chipset) – NVLT-H only
Also functional and performance tests have been performed against other VDSL2
CPEs (see IOP list). However, the test coverage was less than for the above two
CPEs.
NVLT-G/H is not planned to be interoperable with CPE based on Ikanos CPE-4
VDSL2 chipset.
11.4Vectoring line cards
11.4.1 Vectoring interop

Reference CPE for vectoring is the SagemCom F@ST 5310, based on BCM63168
chipset. Alternative is SagemCom F@ST 3864, based on the same chipset.
Basic IOP has been achieved with following CPE types:
„ Technicolor TG789vn (BCM6368)
„ Pirelli ADB V226N1W (BCM6368)
„ Arcadyan VGV7519
„ ZTE ZXV10 H220 N
„ ZTE ZXHN H368N
„ T-HOME Speedport W 724V Type A
„ T-HOME Speedport W 724V Type B
„ T-HOME Speedport W 724V Type C
„ T-HOME Speedport W921V
„ AVM Fritzbox 7490
Based on its own testing, Alcatel-Lucent recommends CPE Software based at

least on 39f2 Broadcom Firmware.
Basic interoperability against Lantiq-based chipsets has been performed. Limited

vectoring tests were done in combination with SRA and in combination with
g.998.4 amd 2.
Based on its own testing, Alcatel-Lucent recommends CPE Software based at
least on R7 Lantiq Firmware.
Basic interoperability against non-Broadcom or non-Lantiq can not yet be

declared. Consequently, Alcatel-Lucent doesn’t recommend to deploy
vectoring in front of non-Broadcom or non-Lantiq based CPEs. Further vectoring
interop exercises with other chipsets depend on availability of a stable g.Vector-
capable firmware.
Reference CPE for vectoring on bonded lines is the SagemCom F@ST 4320.
Edition 01 - RL 2/Apr/2015 99/150
11.5CPEs verified on performance regression versus
previous releases

11.5.1 Performance Interop Test Coverage
A selection of modems from the Alcatel-Lucent CPE Wall and shown below has
been tested against the line cards as indicated below according to the Alcatel-
Lucent Performance interop test package. This Performance test package
consists of a "rate/reach" tests.
The table below contains the number of different CPE vendors and different CPE
products tested during the 7302 ISAM validation. Please note that per CPE vendor
different CPE products could be tested. As a CPE product is defined by a
combination of hardware and software, the same hardware product could be
present several times in the wall with different software releases. Each hw/sw
combination has an assigned mnemonic.
For example: 2WIR-HP1000HW-v357 represents
CPE Vendor: 2Wire
CPE Product: HomePortal 1000HW - HW/SW: 3.57
Important remark:
Some boards supported in this release may not be tested because of similarity
with one or more tested boards.
11.5.2 ADSL Performance CPE test description

This test is a pure performance test. It uses an accurate line simulator and a noise
generator. A rate/reach test from 0 to 6km with a 400m step is performed. The
profile is configured as fast and rate adaptive mode with target noise margins
0/6/max.
The modem is connected and must sync within 60sec. After initialisation some
measured values are read out, such as current bitrate, max. attainable bitrate,
noise margin and attenuation. Then the port is locked and the line simulator
length is set to the next step. The rate/reach test is performed with noise injected
at both ATU-C and ATU-R side. Each time, the modem pair is kept in showtime for
10 seconds. Then the line is shut down, some recovery time for the CPE is allowed,
and then the next initialisation is started.
Interoperability criterion: Test is ok if the performance is equal or above the
reference for this modem for each measured point. See also the IOP Policy
appendix of this document.
100/150 3FE-69054-AAAA-FMZZA
11.5.3 VDSL2 Performance CPE test description
This test will measure the upstream and downstream bit rate of the modem under
TR-114 conditions. Bandplans 8b and 17a are tested. Bandplan 30a is not tested
as this bandplan is not supported.
Interoperability criterion: Test is ok if the performance is equal or above the
reference for this modem for each measured point.
11.5.4 SHDSL Performance CPE test description

This test is a pure performance test. It uses a SHDSL PE04 line simulator, the test is
executed with dual sided white noise injection. A rate/reach test from 0 to 5.4km
with a 200m step is performed. The profile is configured as rate adaptive. The
modem is connected and must sync within 300sec. After initialisation some
measured values are read out, such as current bitrate, noise margin and
attenuation. Then the port is locked and the line simulator length is set to the next
step.
Interoperability criterion: The modem has to initialise within 300 sec on each
initialisation. A reach of at least 5000m is expected for modems supporting the
PMMS implementation. Other should initialise always at 2302kbps until at least
3800m.
11.5.5 Test result overview

11.5.5.1 Test result overview ADSL line cards
Loop tests with port set for Adaptive Rate:Interleaved, White noise
Modem LT-Board Status
2WIRE-HP1000S-v355 NALS-A-AAAA OK
ALU-ST330-vxxx NALS-A-AAAA OK
CISCO-827H-v1224YA2 NALS-A-AAAA OK
THMSN-USB330-v330 NALS-A-AAAA OK
TMM-ADNTH-v290 NALS-A-AAAA OK
TMM-ST330-v1010 NALS-A-AAAA OK
TMM-STHOME-v270 NALS-A-AAAA OK
USRBT-9003A-v42E2EA1 NALS-A-AAAA OK
ZYXEL-642M-v250 NALS-A-AAAA OK
ZYXEL-P650HW31-v340 NALS-A-AAAA OK
ZYXEL-P660M61-v340 NALS-A-AAAA OK
Loop tests with port set for Adaptive Rate:Fast, FB noise

2WIRE-HP1000S-v355 NALS-A-AAAA OK
ALU-ST330-vxxx NALS-A-AAAA OK
Edition 01 - RL 2/Apr/2015 101/150
CISCO-827H-v1224YA2 NALS-A-AAAA OK
THMSN-USB330-v330 NALS-A-AAAA OK
TMM-ADNTH-v290 NALS-A-AAAA OK


TMM-STHOME-v270 NALS-A-AAAA OK
USRBT-9003A-v42E2EA1 NALS-A-AAAA OK
ZYXEL-642M-v250 NALS-A-AAAA OK
ZYXEL-P650HW31-v340 NALS-A-AAAA OK
ZYXEL-P660M61-v340 NALS-A-AAAA OK
Loop tests with port set for Adaptive Rate, A2_RA_I1/2_16000k,White noise
Alice-GateW2-v3.2.4 NALS-A-AAAA OK
Alice-L1-v452 NALS-A-AAAA OK
Alice-S1-v450 NALS-A-AAAA OK
CISCO-877-v3014 NALS-A-AAAA OK
CISCO-887V-vxxx NALS-A-AAAA OK
CTD-5361-vxxx NALS-A-AAAA OK
INTNT-X5668M-v312 NALS-A-AAAA OK
INTX-IX78-v530F2 NALS-A-AAAA OK
SIE-SS4200-vD240A6E NALS-A-AAAA OK
SIE-SS6520-vE752A1Z NALS-A-AAAA OK
THMSN-ST546-v62292 NALS-A-AAAA OK
THMSN-ST585v6-v54014 NALS-A-AAAA OK
THMSN-ST585v8-v82PG NALS-A-AAAA OK
THMSN-TG585v7-v7427 NALS-A-AAAA OK
THMSN-TG784-v8CH2 NALS-A-AAAA OK
THMSN-TG787-v8.8.B.6 NALS-A-AAAA OK
THMSN-TG789V-V8CH2 NALS-A-AAAA OK
TMM-ST536v6-v54014 NALS-A-AAAA OK
ZYXEL-660H61-v340 NALS-A-AAAA OK
ZYXEL-660HD1-v340 NALS-A-AAAA OK
ZYXEL-660HWD1-v34AHF NALS-A-AAAA OK
ZYXEL-660R61C-v340 NALS-A-AAAA OK
Loop tests with port set for Adaptive Rate, A2_RA_I1/2_16000k,FB noise
102/150 3FE-69054-AAAA-FMZZA
Loop tests with port set for Adaptive Rate, A2P_RA_I_30000k,FB noise
Loop tests with port set for Adaptive Rate, A2P_RA_F_30000k,FB noise
Edition 01 - RL 2/Apr/2015 103/150


Loop Tests with port set for Adaptive Rate, A2P_RA_I4_30000k,FB noise
2WIRE-HP1000S-v355 NALT-C-AAAA OK
ALU-ST330-vxxx NALT-C-AAAA OK
CISCO-827H-v1224YA2 NALT-C-AAAA OK
TMM-ADNTH-v290 NALT-C-AAAA OK
104/150 3FE-69054-AAAA-FMZZA
TMM-ST330-v1010 NALT-C-AAAA OK
TMM-STHOME-v270 NALT-C-AAAA OK
USRBT-9003A-v42E2EA1 NALT-C-AAAA OK
ZYXEL-P650HW31-v340 NALT-C-AAAA OK

2WIRE-HP1000S-v355 NALT-C-AAAA OK
ALU-ST330-vxxx NALT-C-AAAA OK
CISCO-827H-v1224YA2 NALT-C-AAAA OK
TMM-ADNTH-v290 NALT-C-AAAA OK
TMM-ST330-v1010 NALT-C-AAAA OK
TMM-STHOME-v270 NALT-C-AAAA OK
USRBT-9003A-v42E2EA1 NALT-C-AAAA OK
ZYXEL-P650HW31-v340 NALT-C-AAAA OK
ALU-CP5Ae2013-vB030m NALT-C-AAAA OK
Alice-GateW2-v3.2.4 NALT-C-AAAA OK
Alice-L1-v452 NALT-C-AAAA OK
Alice-S1-v450 NALT-C-AAAA OK
BTEC-X2301-v748 NALT-C-AAAA OK
CISCO-877-v3014 NALT-C-AAAA OK
CTD-5361-vxxx NALT-C-AAAA OK
DLINK-500B-v1037512 NALT-C-AAAA OK
DLINK-D500BGER-v11CT NALT-C-AAAA OK
EFCNT-SS4100-vA3V NALT-C-AAAA OK
ONEAC-100M-v7R11E14 NALT-C-AAAA OK
SAGEM-1201v2-v344 NALT-C-AAAA OK
SAGEM-LB3FR-vxxx NALT-C-AAAA OK
SIMNS-4200-vD240A36 NALT-C-AAAA OK
THMSN-LBMINI-v7298 NALT-C-AAAA OK
THMSN-LIVEBOX-v5815 NALT-C-AAAA OK
THMSN-ST510v5-v427 NALT-C-AAAA OK
THMSN-ST546-v62292 NALT-C-AAAA OK
THMSN-ST585v8-v82PG NALT-C-AAAA OK
THMSN-ST608WL-v627 NALT-C-AAAA OK
THMSN-TG585v7-v7427 NALT-C-AAAA OK
THMSN-TG784-v8CH2 NALT-C-AAAA OK
ZTE-ZXDSL831-v31018 NALT-C-AAAA OK
ZTE-ZxV10W300-v200 NALT-C-AAAA OK
Edition 01 - RL 2/Apr/2015 105/150
ZYXEL-660HWD1-v34AHF NALT-C-AAAA OK
ZYXEL-660R61C-v340 NALT-C-AAAA OK


106/150 3FE-69054-AAAA-FMZZA
Edition 01 - RL 2/Apr/2015 107/150


2WIRE-HP1000S-v355 NALT-J-AAAA OK
108/150 3FE-69054-AAAA-FMZZA
2WIRE-HP1000S-v355 NALT-J-AAAA OK
ALU-CP5Ae2013-vB030m NALT-J-AAAA OK
BTEC-X2301-v748 NALT-J-AAAA OK
CISCO-877-v3014 NALT-J-AAAA OK
DLINK-500B-v1037512 NALT-J-AAAA OK
DLINK-D500BGER-v11CT NALT-J-AAAA OK
EFCNT-SS4100-vA3V NALT-J-AAAA OK
ONEAC-100M-v7R11E14 NALT-J-AAAA OK
SAGEM-1201v2-v344 NALT-J-AAAA OK
SAGEM-LB3FR-vxxx NALT-J-AAAA OK
SIMNS-4200-vD240A36 NALT-J-AAAA OK
THMSN-LBMINI-v7298 NALT-J-AAAA OK
THMSN-LIVEBOX-v5815 NALT-J-AAAA OK
THMSN-ST510v5-v427 NALT-J-AAAA OK
THMSN-ST546-v62292 NALT-J-AAAA OK
THMSN-ST585v8-v82PG NALT-J-AAAA OK
THMSN-ST608WL-v627 NALT-J-AAAA OK
THMSN-TG585v7-v7427 NALT-J-AAAA OK
THMSN-TG784-v8CH2 NALT-J-AAAA OK
ZTE-ZXDSL831-v31018 NALT-J-AAAA OK
ZTE-ZxV10W300-v200 NALT-J-AAAA OK
Edition 01 - RL 2/Apr/2015 109/150


110/150 3FE-69054-AAAA-FMZZA
Edition 01 - RL 2/Apr/2015 111/150
11.5.5.2 Test result overview VDSL line cards


2WIRE-HP1000S-v355 NVLS-A-AAAA OK
THMSN-USB330-v330 NVLS-A-AAAA OK
TMM-ST510-v427160 NVLS-A-AAAA OK
ZYXEL-642M-v250 NVLS-A-AAAA OK
ZYXEL-P660M61-v340 NVLS-A-AAAA OK

2WIRE-HP1000S-v355 NVLS-A-AAAA OK
THMSN-USB330-v330 NVLS-A-AAAA OK
TMM-ST510-v427160 NVLS-A-AAAA OK
ZYXEL-642M-v250 NVLS-A-AAAA OK
ZYXEL-P660M61-v340 NVLS-A-AAAA OK
CISCO-877-v3014 NVLS-A-AAAA OK
CISCO-887V-vxxx NVLS-A-AAAA OK
INTNT-X5668M-v312 NVLS-A-AAAA OK
INTX-IX78-v530F2 NVLS-A-AAAA OK
THMSN-ST546-v62292 NVLS-A-AAAA OK
THMSN-ST585v6-v54014 NVLS-A-AAAA OK
THMSN-ST585v8-v82PG NVLS-A-AAAA OK
THMSN-TG585v7-v7427 NVLS-A-AAAA OK
THMSN-TG784-v8CH2 NVLS-A-AAAA OK
THMSN-TG787-v8.8.B.6 NVLS-A-AAAA OK
THMSN-TG789V-V8CH2 NVLS-A-AAAA OK
ZYXEL-660H61-v340 NVLS-A-AAAA OK
ZYXEL-660HD1-v340 NVLS-A-AAAA OK
112/150 3FE-69054-AAAA-FMZZA
Edition 01 - RL 2/Apr/2015 113/150
RA performance tests for BA8B : interleaved


RA performance tests for BA12A : fast

RA perf tests for BA17a with D&UPBO : fast

RA perf tests for BA17a with D&UPBO : Intlv

ACD-ARV7519-v5711017 NVLT-G-AAAA OK
ALU-CP5Ae2013-vB030m NVLT-G-AAAA OK
AVM-F7340-v603 NVLT-G-AAAA OK
AVM-FRZ7170-v540482 NVLT-G-AAAA OK
BTEC-X2301-v748 NVLT-G-AAAA OK
CISCO-877-v3014 NVLT-G-AAAA OK
CISCO-887V-vyb5 NVLT-G-AAAA OK
CTD-5361-vxxx NVLT-G-AAAA OK
CTD-CT5372-v9731 NVLT-G-AAAA OK
DLNK-DSL2640B-v307 NVLT-G-AAAA OK
EFCNT-SS4100-vA3V NVLT-G-AAAA OK
HUAWE-HG655d-vBO19 NVLT-G-AAAA OK
ONEAC-100M-v7R11E14 NVLT-G-AAAA OK
Philips-3PRed-POTS NVLT-G-AAAA OK
SAGEM-1201v2-v344 NVLT-G-AAAA OK
SAGEM-BBOX1-v107r58 NVLT-G-AAAA OK
SAGEM-BBOX3-v35M NVLT-G-AAAA OK
SAGEM-LB3FR-vxxx NVLT-G-AAAA OK
SIMNS-SX551-v1478 NVLT-G-AAAA OK
TECH-BBOX3-v39f2 NVLT-G-AAAA OK
THMSN-LBMINI-v7298 NVLT-G-AAAA OK
THMSN-LIVEBOX-v5815 NVLT-G-AAAA OK
THMSN-ST510v5-v427 NVLT-G-AAAA OK
114/150 3FE-69054-AAAA-FMZZA
THMSN-ST608WL-v627 NVLT-G-AAAA OK
THMSN-TG789V-V842U NVLT-G-AAAA OK
TMM-ST510v5-v527 NVLT-G-AAAA OK
ZTE-H220N-v2T09 NVLT-G-AAAA OK
ZTE-ZxV10W300-v200 NVLT-G-AAAA OK
ZYXEL-660HWD1-v34AHF NVLT-G-AAAA OK
ZYXEL-660R61C-v340 NVLT-G-AAAA OK
ZYXL-660HWD1-v340AHF NVLT-G-AAAA OK
Edition 01 - RL 2/Apr/2015 115/150


ZYXL-660HWD1-v340AHF NVLT-G-AAAA NOK
116/150 3FE-69054-AAAA-FMZZA
Edition 01 - RL 2/Apr/2015 117/150



ZYXEL-P870HW-vBKAb25 NVLT-G-AAAA OK


118/150 3FE-69054-AAAA-FMZZA

ARES-1060HUEA-v6104 NVLT-G-AAAA OK
CISCO-827H-v1224YA2 NVLT-G-AAAA OK
TMM-ADNTH-v290 NVLT-G-AAAA OK
USRBT-9003A-v42E2EA1 NVLT-G-AAAA OK
ZYXEL-P650HW31-v340 NVLT-G-AAAA OK

ARES-1060HUEA-v6104 NVLT-G-AAAA OK
CISCO-827H-v1224YA2 NVLT-G-AAAA OK
TMM-ADNTH-v290 NVLT-G-AAAA OK
USRBT-9003A-v42E2EA1 NVLT-G-AAAA OK
ZYXEL-P650HW31-v340 NVLT-G-AAAA OK
Loop Tests with Ports Set for Adaptive Rate, B2P_RA_I_30000k, White noise
Philips-3PWhite-ISDN NVLT-G-AAAA OK
SIMNS-SX552i-v1478 NVLT-G-AAAA OK
THMSN-ST546iv6-v6196 NVLT-G-AAAA OK
THMSN-TG789ivn-v843U NVLT-G-AAAA OK
Loop Tests with Ports Set for Adaptive Rate, B2P_RA_F_30000k, FB noise
Philips-3PWhite-ISDN NVLT-G-AAAA OK
SIMNS-SX552i-v1478 NVLT-G-AAAA OK
THMSN-ST546iv6-v6196 NVLT-G-AAAA OK
RA performance tests for BB8B : interleaved

SAGEM-BBOX2-v5512 NVLT-G-AAAA OK
Edition 01 - RL 2/Apr/2015 119/150

RA performance tests for BB12A : fast

RA perf tests for BB17a with D&UPBO : fast

RA perf tests for BB17a with D&UPBO : Intlv

AVM-7270-v540505 NVLT-M-AAAA OK
Fritzbox 7490 NVLT-M-AAAA OK
SAGEM-5311-v039b NVLT-M-AAAA OK
SP- W724V Typ-A NVLT-M-AAAA OK
SP-AVM-W503-v660479 NVLT-M-AAAA OK
SPARC-W723-v12600 NVLT-M-AAAA OK
Speedport W921V NVLT-M-AAAA OK
THOME-SP723VA-v10092 NVLT-M-AAAA OK
AVM-7270-v540505 NVLT-M-AAAA OK
SP-AVM-W503-v660479 NVLT-M-AAAA OK

120/150 3FE-69054-AAAA-FMZZA
Sp- W724V Typ- B NVLT-M-AAAA OK
THOME-SP300HS-v130 NVLT-M-AAAA OK
THOME-SP721V-v640474 NVLT-M-AAAA OK



SIE-SS4200-vD240A6E NVLT-M-AAAA OK
SIE-SS6520-vE752A1Z NVLT-M-AAAA OK
TMM-ST536v6-v54014 NVLT-M-AAAA OK
Edition 01 - RL 2/Apr/2015 121/150






ALU-CP5Ae2013-vB030m NVLT-P-AAAA OK
BTEC-X2301-v748 NVLT-P-AAAA OK
122/150 3FE-69054-AAAA-FMZZA
CISCO-877-v3014 NVLT-P-AAAA OK
CTD-5361-vxxx NVLT-P-AAAA OK
CTD-CT5372-v9731 NVLT-P-AAAA OK
DLINK-500B-v1037512 NVLT-P-AAAA OK
DLINK-D500BGER-v11CT NVLT-P-AAAA OK
DLNK-DSL2640B-v307 NVLT-P-AAAA OK
EFCNT-SS4100-vA3V NVLT-P-AAAA OK
ONEAC-100M-v7R11E14 NVLT-P-AAAA OK
Philips-3PRed-POTS NVLT-P-AAAA OK
SAGEM-1201v2-v344 NVLT-P-AAAA OK
SAGEM-BBOX1-v107r58 NVLT-P-AAAA OK
SAGEM-BBOX3-v35M NVLT-P-AAAA OK
SAGEM-LB3FR-vxxx NVLT-P-AAAA OK
SIE-SS4200-vD240A6E NVLT-P-AAAA OK
SIE-SS6520-vE752A1Z NVLT-P-AAAA OK
SIMNS-4200-vD240A36 NVLT-P-AAAA OK
TECH-BBOX3-v39f2 NVLT-P-AAAA OK
THMSN-LBMINI-v7298 NVLT-P-AAAA OK
THMSN-LIVEBOX-v5815 NVLT-P-AAAA OK
THMSN-ST510v5-v427 NVLT-P-AAAA OK
THMSN-ST546-v62292 NVLT-P-AAAA OK
THMSN-ST608WL-v627 NVLT-P-AAAA OK
THMSN-TG585v7-v7427 NVLT-P-AAAA OK
TMM-ST510v5-v527 NVLT-P-AAAA OK
ZTE-ZXDSL831-v31018 NVLT-P-AAAA OK
ZTE-ZxV10W300-v200 NVLT-P-AAAA OK
ZYXEL-660HWD1-v34AHF NVLT-P-AAAA OK
ZYXEL-660R61C-v340 NVLT-P-AAAA OK
ZYXL-660HWD1-v340AHF NVLT-P-AAAA OK
Edition 01 - RL 2/Apr/2015 123/150


124/150 3FE-69054-AAAA-FMZZA
Edition 01 - RL 2/Apr/2015 125/150


126/150 3FE-69054-AAAA-FMZZA
ALU-CP5VeA2000-v1290 NVLT-P-AAAA OK
ALU-CP6VzA2131-v1521 NVLT-P-AAAA OK
ZYXEL-P870HW-vBKAb25 NVLT-P-AAAA OK



ARES-1060HUEA-v6104 NVLT-P-AAAA OK
CISCO-827H-v1224YA2 NVLT-P-AAAA OK
TMM-ADNTH-v290 NVLT-P-AAAA OK
USRBT-9003A-v42E2EA1 NVLT-P-AAAA OK
ZYXEL-P650HW31-v340 NVLT-P-AAAA OK

ARES-1060HUEA-v6104 NVLT-P-AAAA OK
CISCO-827H-v1224YA2 NVLT-P-AAAA OK
TMM-ADNTH-v290 NVLT-P-AAAA OK
Edition 01 - RL 2/Apr/2015 127/150
USRBT-9003A-v42E2EA1 NVLT-P-AAAA OK
ZYXEL-P650HW31-v340 NVLT-P-AAAA OK


ALU-CP5VeA2000-v1290 NVLT-R-AAAA OK
ALU-CP6VzA2131-v1521 NVLT-R-AAAA OK



DLINK-500B-v1037512 NVLT-R-AAAA OK
DLINK-D500BGER-v11CT NVLT-R-AAAA OK
SAGEM-1201v2-v344 NVLT-R-AAAA OK
SIMNS-4200-vD240A36 NVLT-R-AAAA OK
THMSN-ST510v6-v6105 NVLT-R-AAAA OK
THMSN-ST546-v62292 NVLT-R-AAAA OK
THMSN-TG585v7-v7427 NVLT-R-AAAA OK
ZTE-ZXDSL831-v31018 NVLT-R-AAAA OK
128/150 3FE-69054-AAAA-FMZZA

ZTE-ZXDSL931I-v150a NVLT-R-AAAA OK



AVM-7270-v540505 NVLT-S-AAAA OK
Edition 01 - RL 2/Apr/2015 129/150
Fritzbox 7490 NVLT-S-AAAA OK
SAGEM-5311-v039b NVLT-S-AAAA OK
SP- W724V Typ-A NVLT-S-AAAA OK

SP-AVM-W503-v660479 NVLT-S-AAAA OK

SPARC-W723-v12600 NVLT-S-AAAA OK
Speedport W921V NVLT-S-AAAA OK
THOME-SP723VA-v10092 NVLT-S-AAAA OK
AVM-7270-v540505 NVLT-S-AAAA OK
SP-AVM-W503-v660479 NVLT-S-AAAA OK
CISCO-827H-v1224YA2 NVLT-S-AAAA OK
TMM-ADNTH-v290 NVLT-S-AAAA OK
USRBT-9003A-v42E2EA1 NVLT-S-AAAA OK
ZYXEL-P650HW31-v340 NVLT-S-AAAA OK

CISCO-827H-v1224YA2 NVLT-S-AAAA OK
TMM-ADNTH-v290 NVLT-S-AAAA OK
USRBT-9003A-v42E2EA1 NVLT-S-AAAA OK
ZYXEL-P650HW31-v340 NVLT-S-AAAA OK
CTD-5361-vxxx NVLT-S-AAAA OK
SIE-SS4200-vD240A6E NVLT-S-AAAA OK
SIE-SS6520-vE752A1Z NVLT-S-AAAA OK
TMM-ST536v6-v54014 NVLT-S-AAAA OK
ZYXEL-660HWD1-v34AHF NVLT-S-AAAA OK
ZYXEL-660R61C-v340 NVLT-S-AAAA OK
130/150 3FE-69054-AAAA-FMZZA
ZYXEL-660HWD1-v34AHF NVLT-S-AAAA NOK

Sp- W724V Typ- B NVLT-S-AAAA OK
THOME-SP300HS-v130 NVLT-S-AAAA OK
THOME-SP721V-v640474 NVLT-S-AAAA OK

Edition 01 - RL 2/Apr/2015 131/150





ZYXEL-P870HW-vBKAb25 NVLT-S-AAAA OK


132/150 3FE-69054-AAAA-FMZZA
11.5.5.3 Test result overview vectoring line cards

ALU-ST330-vxxx NDLT-C-AAAA OK
TMM-ST330-v1010 NDLT-C-AAAA OK
TMM-STHOME-v270 NDLT-C-AAAA OK

ALU-ST330-vxxx NDLT-C-AAAA OK
TMM-ST330-v1010 NDLT-C-AAAA OK
TMM-STHOME-v270 NDLT-C-AAAA OK
Alice-GateW2-v3.2.4 NDLT-C-AAAA OK
Alice-L1-v452 NDLT-C-AAAA OK
Alice-S1-v450 NDLT-C-AAAA OK
CISCO-877-v3014 NDLT-C-AAAA OK
Edition 01 - RL 2/Apr/2015 133/150


SAGEM-5310-v039b NDLT-F-AAAA OK




ACD-ARV7519-v5711017 NDLT-G-AAAA OK
AVM-F7340-v603 NDLT-G-AAAA OK
AVM-FRZ7170-v540482 NDLT-G-AAAA OK
CISCO-887V-vyb5 NDLT-G-AAAA OK
134/150 3FE-69054-AAAA-FMZZA
CTD-5361-vxxx NDLT-G-AAAA OK
HUAWE-HG655d-vBO19 NDLT-G-AAAA OK
Philips-3PRed-POTS NDLT-G-AAAA OK
SAGEM-BBOX1-v107r58 NDLT-G-AAAA OK
SAGEM-BBOX3-v35M NDLT-G-AAAA OK
SIE-SS4200-vD240A6E NDLT-G-AAAA OK
SIE-SS6520-vE752A1Z NDLT-G-AAAA OK
SIMNS-SX551-v1478 NDLT-G-AAAA OK
TECH-BBOX3-v39f2 NDLT-G-AAAA OK
THMSN-ST780WL-v74327 NDLT-G-AAAA OK
THMSN-TG789V-V842U NDLT-G-AAAA OK
TMM-ST536v6-v54014 NDLT-G-AAAA OK
ZTE-H220N-v2T09 NDLT-G-AAAA OK
ZYXEL-660HWD1-v34AHF NDLT-G-AAAA OK
ZYXEL-660R61C-v340 NDLT-G-AAAA OK
Edition 01 - RL 2/Apr/2015 135/150


ZYXEL-660R61C-v340 NDLT-G-AAAA NOK
136/150 3FE-69054-AAAA-FMZZA

ZYXEL-P870HW-vBKAb25 NDLT-G-AAAA OK


AVM-F7340-v603 NDLT-G-AAAA NOK

CISCO-827H-v1224YA2 NDLT-G-AAAA OK
TMM-ADNTH-v290 NDLT-G-AAAA OK
USRBT-9003A-v42E2EA1 NDLT-G-AAAA OK
Edition 01 - RL 2/Apr/2015 137/150
ZYXEL-P650HW31-v340 NDLT-G-AAAA OK


CISCO-827H-v1224YA2 NDLT-G-AAAA OK
TMM-ADNTH-v290 NDLT-G-AAAA OK
USRBT-9003A-v42E2EA1 NDLT-G-AAAA OK
ZYXEL-P650HW31-v340 NDLT-G-AAAA OK
11.5.5.4 Test result overview bonding line cards

RR test 2p bonding, no ds delay optimiz, ilv_4_16 profile, 998ADE 12a, white noise -140
ALU-6VZA4111-vxxx NDLT-G-AAAA OK
ALU-SARM-vB-6.0.R2 NDLT-G-AAAA OK
ALU-SARWx-vB6.1.R3 NDLT-G-AAAA OK
SAGEM-4320-v7.23 NDLT-G-AAAA OK
ZTE-ZXHNH368N-v00T09 NDLT-G-AAAA OK
ZXEL-VMG4325-vAAFQ NDLT-G-AAAA OK
RR test 2p bonding, ds delay optimiz by CO, ilv_2_8 profile, 998ADE 12a, equal loops, white noise -
140
RR test 2p bonding, ds delay optimiz by CO, ilv_4_8 profile, 998ADE 12a, white noise -140
RR test 2p bonding, no ds delay optimiz, fast profile, 998ADE 8b, equal loops, white noise -140
ARCD-VFV7519-v131t21 NDLT-G-AAAA OK
138/150 3FE-69054-AAAA-FMZZA
RR test 2p bonding, ds delay optimiz by CO, 1 line fixed to 300m, ilv_4_8 profile, 998ADE 12a, white
noise -140
RR test 2p bonding, no ds delay optimiz, 1 line fixed to 300m, ilv_4_8 profile, 998ADE 12a, white
noise -140
140
RR test 2p bonding, no ds delay optimiz, ilv_2_8 profile, 998ADE 17a, equal loops, white noise -140
RR test 2p bonding, no ds delay optimiz, fast profile, 998ADE 17a, equal loops, white noise -140
RR test 2p bonding, Annex A, no ds delay optimiz, fast profile, equal loop lengths, white noise -140
ALU-SARM-vB-6.0.R2 NDLT-G-AAAA NOK
Edition 01 - RL 2/Apr/2015 139/150

RR test 2p bonding, Annex A, no ds delay optimiz, ilv 2 / 16ms DS & 0.5 / 16ms US, equal loop
lengths, white noise -140
RR test 2p bonding, Annex A, ds delay optimiz by CO, ilv 2 / 16ms DS & 0.5 / 16ms US, equal loop
ALU-6VZA4111-vxxx NVLT-P-AAAA OK
ZTE-ZXHNH368N-v00T09 NVLT-P-AAAA OK
140
noise -140
noise -140
140/150 3FE-69054-AAAA-FMZZA
140
ALU-6VZA4111-vxxx RDLT-B-AAAA OK
ALU-SARM-vB-6.0.R2 RDLT-B-AAAA OK
ALU-SARWx-vB6.1.R3 RDLT-B-AAAA OK
SAGEM-4320-v7.23 RDLT-B-AAAA OK
ZTE-ZXHNH368N-v00T09 RDLT-B-AAAA OK
ZXEL-VMG4325-vAAFQ RDLT-B-AAAA NOK
140
Edition 01 - RL 2/Apr/2015 141/150
ARCD-VFV7519-v131t21 RDLT-B-AAAA OK


noise -140
noise -140
140
142/150 3FE-69054-AAAA-FMZZA
RR test 2p bonding, Annex A, no ds delay optimiz, fast profile, equal loop lengths, white noise -140
ALU-SARM-vB-6.0.R2 RDLT-B-AAAA NOK
RR test 2p bonding, Annex A, no ds delay optimiz, ilv 2 / 16ms DS & 0.5 / 16ms US, equal loop
RR test 2p bonding, Annex A, ds delay optimiz by CO, ilv 2 / 16ms DS & 0.5 / 16ms US, equal loop
Edition 01 - RL 2/Apr/2015 143/150
12 GPON Voice Interoperability

Please refer to the applicable 7368 ISAM Home Devices Release (HDR) CRN for

more details on the supported devices and voice IOP tests successfully
completed.
144/150 3FE-69054-AAAA-FMZZA
13 GPON Uplink Interoperability on 7363 ISAM
MX
GPON OLT interop releases for the 7363 ISAM MX-6:
„ 7360 ISAM FX R4.4 DR5 / R4.5.03 / R4.6.02 / R5.0.01/ R5.1 / R5.2
„ 7342 ISAM FTTU FGU4.8.30 / FGU4.8.10 / FGU4.8.06/ FGU4.9.01 (GLT8-A)
Edition 01 - RL 2/Apr/2015 145/150
14 APPENDIX : DSL IOP Policy

14.1Introduction
In view of the fast rollout of DSL lines in many countries around the world, there is
a fast growth in the number of CPE (DSL modems, IAD’s …) that are being
introduced in the market by different vendors. In order to ensure that the volume
rollout of DSL lines can proceed efficiently, the aspect of interoperability between
ISAM’s and CPE’s requires a dedicated attention and follow-up.
By this document Alcatel-Lucent would like to outline how we propose to
manage this aspect of interoperability, in close co-operation with our customers.
14.2Objective
The objective of this policy is to reach a common agreement with our customers
on the short-term actions, as well as the longer-term strategy, to manage the
interoperability between successive releases of our ISAM product, the Alcatel-
Lucent 73xx ISAM, and the growing range of CPE, which are deployed in the
field.
14.3Interoperability definition
Interoperability means that

„ The interworking between the Alcatel-Lucent 73xx ISAM and 3rd party CPE
equipment meets basic functional and performance (e.g.
bandwidth/reach) requirements, and
„ When new releases of the Alcatel-Lucent 73xx ISAM are introduced, then
for each CPE in the interoperability wall maintained by Alcatel-Lucent as
defined below, the interworking between this CPE and the new version of
the ISAM continues to meet these functional and performance
requirements.
14.4Policy Guidelines
Ultimately Alcatel-Lucent wants to come to the situation that we can rely on it
that a particular ISAM and a particular CPE are interoperable, when this ISAM
and this CPE are each separately formally verified by an officially certified party
that applies this standardised methodology.
As the longer-term strategy to be implemented, Alcatel-Lucent supports the
current initiatives by standardisation bodies and industry forums to establish an
objective standardised methodology to establish the interoperability between a
146/150 3FE-69054-AAAA-FMZZA
ISAM and a CPE. The main references of these standards are TR-067, TR-100, TR-
105, TR-114 and TR-115 (Broadband Forum www.broadband-forum.org).
Until we are able to reach this future situation, we need to manage the still
growing installed base of CPE in the market. For this legacy CPE a dedicated
action is required, since the aspect of interoperability was not formally assessed in
this objective standardised way, but established in more ad hoc ways.
In order to deal with this short term situation Alcatel-Lucent propose the following
strategy for the installed base of CPE equipment, and for new CPE’s that are to
be introduced in its customer networks:
„ We propose to establish with our customers a formal agreement on the list
of CPE that are officially deployed in their network (i.e. with formal
approval by our customer to their end-users). The maximum supportable
size of this list is 20 CPE. If the list is full and new CPE are added to the list,
then it must be agreed which one shall be removed. From this list at
maximum 3 CPE can be marked as ‘high priority’ CPE. These CPE will be
used for the ‘customer Focus Testing” (CFT) if the Network operator is part
of the first off customers of a release.
„ For all legacy CPE’s which are included on this list and which are made
available to Alcatel-Lucent, Alcatel-Lucent will do its best to ensure
continued interoperability with the Alcatel-Lucent 73xx ISAM, in case of
hardware or software upgrades to the installed base of Alcatel-Lucent 73xx
ISAM, and new ISAM deployments.
„ For new ADSL1 CPE types to be introduced in the customer’s network,
these will only be added to the officially agreed list mentioned in point 1
above after having passed an interoperability test. To this end either the
CPE Vendor or the Network Operator needs to provide an interoperability
conformance test report. This report can be issued by a Broadband Forum
approved ITL according to TR-067, or by the Network Operator according
to TR-067 or a mutually agreed test list.
„ For new ADSL2 and ADSL2plus CPE types to be introduced in the
customer’s network, these will only be added to the officially agreed list
mentioned in point 1 above after having passed an interoperability test. To
this end either the CPE Vendor or the Network Operator needs to provide
an interoperability conformance test report. This report can be issued by a
Broadband Forum approved ITL according to TR-100, or by the Network
Operator according to TR-100 or a mutually agreed test list.
„ For new VDSL2 CPE types to be introduced in the customer’s network, these
will only be added to the officially agreed list mentioned in point 1 above
after having passed an interoperability test. To this end either the CPE
Vendor or the Network Operator needs to provide an interoperability
conformance test report. This report can be issued by a Broadband Forum
approved ITL according to TR-114 and TR-115, or by the Network Operator
according to TR-114 and TR-115 or a mutually agreed test list.
Edition 01 - RL 2/Apr/2015 147/150
„ Alcatel-Lucent wishes to make clear that for all existing and new ISAM
deployments it can only ensure interoperability for the CPE used in

customer’s networks in case these CPE are conforming to the specification
as described above.

14.5Practical implementation
Alcatel-Lucent will strive to capture as many as possible interop issues during the
test and integration process of the Alcatel-Lucent 73xx DLAM development,
according to the implementation guidelines described below. However, Alcatel-
Lucent cannot and will not certify, guarantee interoperability or assume any
liability of operation of CPE products.
„ Alcatel-Lucent will do its best to ensure continued interoperability of new
ISAM releases with the existing installed base of CPE’s by carefully
regression testing new ISAM releases against the currently deployed and
interoperable CPE.
„ To this intent Alcatel-Lucent maintains a ‘CPE Wall’ (i.e. a wall in which the
legacy CPE’s are stacked for interworking testing with the ISAM)
· The objective is to have in this CPE Wall the modems that are field
deployed with the Alcatel-Lucent 73xx ISAM’s
· To build out the CPE Wall the Network Operator provides 5 samples
of all CPE types (unique HW and SW version) that are on the agreed
list of CPE being deployed against the Alcatel-Lucent 73xx ISAM.
· In order that the CPE Wall is an accurate representation of the
modems being deployed in the field it is important that Alcatel-
Lucent is kept informed on new CPE versions being deployed in the
customer’s network (i.e. the agreed CPE list needs to be kept up to
date). If not informed, Alcatel-Lucent will use the latest available CPE
list.
· Alcatel-Lucent reserves the right to remove modems that have been
present in the modem wall for more then 3 years (after integration
date), in order to limit the modem wall size and create room for
integration of newer CPE types.
„ In order to ensure that there is sufficient time available for new modems to
be included in the interop regression test of the next ISAM product release,
these modems should be made available at least 3 months before the
planned ISAM release date.
„ A new CPE will only be integrated if the there is a different physical layer
implementation. This means that a CPE with only a different end user
interface compared to a modem already in the modem wall, will NOT be
integrated.
148/150 3FE-69054-AAAA-FMZZA
„ A new CPE will only be integrated if al information regarding chipset
vendor, chipset version, firmware and software versions etc. is provided (i.e.
there will be no black box testing). If CPE’s are provided without this
information they will NOT be integrated. The information can be provided
on request.
„ Before making a new ISAM release available a set of dedicated interop
tests will be performed
· Before the initial Customer Product Release (‘DR4 milestone’) of a
new main ISAM release (release x.y) at maximum 3 ‘high priority’
CPE’s from the agreed CPE list and available modems in the CPE
Wall of first-off customers will be verified for continued
interoperability. These interoperability tests are done by a “customer
focus team” and use a customer specific test plan.
· For maintenance releases (release x.y.z), a full CPE modem wall run
will not be done. It is expected that the number of fixes in a
maintenance release does not drastically change the
interoperability behaviour compared to the corresponding main
ISAM release. Limited interoperability regression tests will be run on a
best effort basis for the target customers of the release. These
interoperability tests are done by a “customer focus team” with
focus on a maximum of 2 ‘high priority’ CPE’s from the agreed CPE
list and available modems in the CPE Wall. These tests are based on
a subset of a customer specific test plan.
· For emergency fix (EF) release (x.y.za), interoperability is not re-tested.
The number of fixes is very small compared to the corresponding
maintenance release and therefore the interoperability behaviour is
not expected to change. Only those CPE’s for which fault reports
are being fixed will be retested.
· Before the General Availability Release (‘DR5 milestone’) of a new
ISAM release all modems present in the CPE Wall will be verified for
continued interoperability as described in section [7]. In practice
these test occur may also before DR4 and as such may span several
FW deliveries
„ The CPE Wall regression test is performed according to the following
scenario:
· A general interop regression test is performed which covers the
initialisation aspects, with in addition performance, stability,
functional and traffic tests. In case a interop test fails, a fault report
will be made.
Edition 01 - RL 2/Apr/2015 149/150
· Next to the general CPE Wall tests, more detailed interop tests will be
executed on a representative subset of the modems in the CPE Wall.

The set of modems may vary for each new ISAM release, depending
on the release content and impact on modem related hardware

and software. The focus of these tests is mainly on performance
under noise conditions.
Note: Regression test results are valid for the specific HW and FW
versions of that CPE
„ Alcatel-Lucent has established a close relation with the major Chipset and
CPE vendors to be able to detect more interoperability issues in an earlier
stage of product development, and ensure there is a process in place so
that any corrections will be efficiently implemented.
„ Alcatel-Lucent will facilitate public CPE-Interop qualification via the
Broadband Forum Independent Test Labs (ITL), by ensuring that the ITL
have up-to-date ISAM hardware and software. Currently Alcatel-Lucent is
working closely with the following ITL: LAN (France) and KTL (UK).
„ Alcatel-Lucent is a member of the DSL Testing Consortium of the University
of New Hampshire interoperability lab (USA).
(http://www.iol.unh.edu/services/testing/ dsl/). UNH-IOL is a neutral, third-
party laboratory dedicated to testing data networking technologies. Apart
from participating to Broadband Forum plugfests, our ISAM products are
available at UNH for testing by CPE manufacturers.
150/150 3FE-69054-AAAA-FMZZA

3FE-69054-AAAA-FMZZA-01-ISAM 5 - 2 Customer Release Note Generic

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3FE-69054-AAAA-FMZZA-01-ISAM 5 - 2 Customer Release Note Generic

Uploaded by

Copyright:

Available Formats

R5.

Title DOCP- ISAM R5.2

All rights reserved. Passing on and copying of this

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

not permitted without written authorization fro m Alcatel-Lucent.

2.2 New Features

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

Remote TL1 user management on 7360 ISAM FX

Duplex IHUB support for IP routing protocols

IHUB: Increase maximum number of secondary subnets on IP interface

CPU and memory utilization retrieval on FGLT-B and FWLT-A

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

7363 ISAM MX: 8p/16p GE LT (RELT-A)

Support for synchronous Ethernet (SyncE) on 7363 MX and 7367 SX-48V

7360 ISAM FX-12 shelf

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

Crosstalk cancelled SELT

G.997.1 counter LOSS

Allow L2 mode when CDA is configured

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

MAC learning control for NANT-A

Add access loop encapsulation in PPPoE IA and DHCP relay

PON utilization & thresholds

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

Selective Behavior of Service Continuity in ONT SW Management

New detection of alien ONT

CPE/ONT Configuration over OMCI

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

DPoE SAV Phase 1

Restrictions and Assumptions:

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

MSO CLI Improvements Phase 1

End of support for DHCP Relay on DPoE subsystem

Restrictions and Assumptions:

Voice Services Domain

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

ISAM-V SIP: Subscriber controlled active/de-active CW

2.3 Feature Discontinuation Announcements

2.4 R5.2 Corrections/Improvements

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

All rights reserved. Passing on and copying of this

Problem: Ncnc-d combo ports do not accept "no autonegotiate"

Problem: Powered down NDPS-B generates flapping board missing

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

Problem: While migrating a A4.100 database with NVLT-N

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

not permitted without written authorization fro m Alcatel-Lucent.

document, use and communication of its contents

All rights reserved. Passing on and copying of this

Problem: Deploy template group that contains many profiles fails on

Note Boards with software preinstalled in EPROMs are released