7330

CUSTOMER RELEASE NOTES
7330 ISAM FTTN

Feature Group 3.6.01
3HH-03364-EBAA-DEZZA Edition 01
IMPORTANT NOTICE: This document contains confidential information that is proprietary to

Alcatel-Lucent. No part of its contents may be used, copied, disclosed or conveyed to any party in
any manner whatsoever without prior written permission from Alcatel-Lucent.
www.alcatel-lucent.com
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners. Alcatel-Lucent assumes no
responsibility for the accuracy of the information presented, which is subject to change without
notice. 2008 Alcatel-Lucent. All rights reserved.
Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2008 Alcatel-Lucent. All rights reserved.
THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21 CFR,

1040.10, FOR A CLASS 1 LASER PRODUCT.
DANGER
Invisible laser radiation is present when the optic connector is open. AVOID DIRECT
EXPOSURE TO BEAM.
Warning
This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and, if
not installed and used in accordance with the instruction manual, may cause harmful
interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be required to correct the
interference at his own expense.
Notice
The product specification and/or performance levels contained in this document are for
information purposes only and are subject to change without notice. They do not represent any
obligation on the part of Alcatel-Lucent. Such obligations will only be committed to in a
written sales agreement signed by Alcatel-Lucent.
Technical Support Telephone Number

For technical assistance, call 1-888-252-2832 (1-888-ALCATEC).
Marks (trademarks, service marks) and trade names

The Alcatel word, the Alcatel-Lucent word, the Alcatel logo, and the Alcatel-Lucent logo are
registered trademarks and service marks of Alcatel-Lucent. No mention is made of rights with
respect to other trademarks, service marks, or trade names whether registered or not, which
may attach to certain words or signs used herein. The absence of such mention, however, in no
way implies that there is no protection of these marks, trade names, words or signs.
Other brands and names contained in this release are the property of their respective owners.
Licensing
The 7330 ISAM FTTN product contains software licensed under the GNU Lesser General Public
License (LGPL). For information about the GNU LGPL, see
http://www.gnu.org/licenses/lgpl.txt . For more information about the GNU libraries used in
the 7330 ISAM FTTN software, contact the 7330 ISAM FTTN engineering information team at
isam-engineering-info@alcatel-lucent.com.
Alcatel-Lucent 2008. All Rights Reserved.
3HH-03364-EBAA-DEZZA
Edition 01, July 2008
1. Introduction
1. Introduction
This document provides delivery information for the 7330 Intelligent Services Access
Manager Fiber to the Node (7330 ISAM FTTN), Feature Group 3.6.01, including the
known restrictions.
This Customer Release Notes (CRN) document was prepared for system administrators,
installers, and other operators of the 7330 ISAM FTTN.
2. Purpose of release
The purpose of the Feature Group 3.6.01 release is to provide a resolution to open
issues identified in Feature Group 3.6 and earlier releases.
3. Related documentation
Table A lists the documentation associated with Feature Group 3.6.01 of the
7330 ISAM FTTN. Unless otherwise specified, the documents listed in Table A are
available on the documentation CD.
Note:
All the documents in Table A are also available on the Alcatel-Lucent Support Service
website at http://www1.alcatel-lucent.com/osds/.
Table A. Related documents

Standard documentation
Product Information
3HH-05579-AAAA-TCZZA
System Description
3HH-05535-AAAA-TQZZA
Planning and Ordering
Provides general system information, features and functionality,

and hardware unit data sheets for the 7330 ISAM FTTN
Provides conceptual information for the 7302 ISAM and the
7330 ISAM FTTN
Provides information for planning and ordering the
7330 ISAM FTTN
Hardware Installation and Maintenance Provides task-oriented procedures for installing and maintaining
Practices
the 7330 ISAM FTTN hardware
Operations and Maintenance Using CLI
3HH-05536-AAAA-TQZZA
Provides task-oriented procedures for operating and maintaining

the 7302 ISAM and 7330 ISAM FTTN using the CLI
Operations and Maintenance Using the Provides task-oriented procedures for operating and maintaining
5526 AMS
the 7330 ISAM FTTN using the 5526 AMS
7330 ISAM FTTN, Feature Group 3.6.01

Customer Release Notes, Edition 01
This document is located on the 5526 AMS CD.
4. Features
Table A. Related documents (Continued)

TL1 and CLI documentation
TL1 Commands and Messages
CLI Commands
3HH-04416-CFAA-TCZZA
Describes the TL1 commands and messages for the 7302 ISAM and
the 7330 ISAM FTTN
Describes the CLI commands for the 7330 ISAM FTTN and the
7330 ISAM FTTN
Software kit (these documents are located on the software CD)

Customer Release Notes
CRN for the 7330 ISAM FTTN Feature Group 3.6.01
(This document)
Software Upgrade and Migration

Application Procedures
Provides instructions for using the automated tools for upgrading

and migrating the software for the 7330 ISAM FTTN system
Table B lists the part number of the documentation CD required for

Feature Group 3.6.01.
Table B. 7330 ISAM FTTN documentation CD
Description
Part number
7330 ISAM FTTN Feature Group 3.6 documentation CD
3HH-05955-AAAA
4. Features
This section lists the new features for the 7330 ISAM FTTN software load released in
Feature Group 3.6.
Connectivity fault management support as per 802.1ag

IGMP on multiple PVCs and VLANs per line
IGMP SSM
Port information retrieval via TL1
System log for SHub resets
5. Software delivery and installation

Table C lists the 7330 ISAM FTTN Software Kit part number. Table D lists the contents of
the Software Kit.

5. Software delivery and installation
Table C. 7330 ISAM FTTN Feature Group 3.6.01 Software Kit

Description
Part number
7330 ISAM FTTN Feature Group 3.6.01 Software Kit
3HH-03364-EBAA
Table D. 7330 ISAM FTTN Feature Group 3.6.01 Software Kit contents
Description
Part number
7330 ISAM FTTN Feature Group 3.6.01 Software CD
3HH-03364-EBAA-PMZZA
7330 ISAM FTTN Feature Group 3.6.01 Customer Release Notes
(This document)
7330 ISAM FTTN Feature Group 3.6.01 software (see Table E)
7302 ISAM | 7330 ISAM FTTN Feature Group 3.6 Software Upgrade
and Migration Application Procedures
Software Upgrade Automation Tool (see Table E for version number)
The Software Kit is provided on CD-ROM media. The CD-ROM includes software version
Feature Group 3.6.01; please see Table E.
Table E. Software versions for the 7330 ISAM FTTN
Feature
group
Software versions
Package
SHub
ECNT-A
ECNT-C
SHub
NT
migration tool migration
tool
Database Software Upgrade

version
Automation Tool
FGN 3.0.03
L6GQAA24.929 LANX_R2.4.9.9
V1.17.0
MJSHAA24.exe A2.400
FGN 3.0.05
L6GQAA24.952 LANX_R2.4.99.3
V1.26.0
MJSHAA24.exe A2.400
V.1.4.39
FGN 3.0.11
L6GQAA24.659 LANX_R2.4.16.4
V1.31.0
MJSHAA24.exe A2.400
V.1.4.59
FGN 3.2.01
L6GQAA32.114 LANX_R3.1.9.0
LANX_R3.1.8.0
V1.28.0
MJSHAA32.exe A3.100
V1.4.51
FGN 3.4
L6GQAA33.027 LANX_R3.3.17.9
LANX_R3.3.19.8
V1.32.0
MJSHAA33.exe A3.300
V1.4.65
FGN 3.4.0b
L6GQAA33.225 LANX_R3.3.19.4
LANX_R3.3.22.0
V1.35.0
MJSHAA33.exe A3.300
V1.5.15
FGN 3.4.01
L6GQAA33.230 LANX_R3.3.19.4
LANX_R3.3.22.0
V1.35.0
MJSHAA33.exe A3.300
V1.5.22
FGN 3.4.01a L6GQAA33.325 LANX_R3.3.21.1
LANX_R3.3.24.0
V1.35.0
MJSHAA33.exe A3.300
V1.5.25
FGN 3.4.02
L6GQAA33.415 LANX_R3.3.21.1
LANX_R3.3.25.2
V1.35.0
MJSHAA33.exe B3.350
V1.7.3
FGN 3.5
L6GQAA34.094 LANX_R3.4.11.3
LANX_R3.4.11.3
V1.36.0
MJSHAA34.exe A3.400
V1.5.15
FGN 3.5.00a L6GQAA34.098 LANX_R3.4.11.3
LANX_R3.4.11.3
V1.36.0
MJSHAA34.exe A3.400
V1.5.22
FGN 3.5.00b L6GQAA34.098 LANX_R3.4.11.3
LANX_R3.4.11.3
V1.36.0
MJSHAA34.exe A3.400
V1.5.25
FGN 3.5.00c L6GQAA34.099 LANX_R3.4.11.3
LANX_R3.4.11.3
V1.36.0
MJSHAA34.exe A3.400
V1.5.25
FGN 3.6
L6GQAA35.125 LANX_R3.5.19.7
LANX_R3.5.19.8
V1.43.0
MJSHAA35.exe A3.500
V1.7.17
FGN 3.6.01
L6GQAA35.223 LANX_R3.5.14.7
LANX_R3.5.20.8
V1.43.0
MJSHAA35.exe A3.500
V2.0.18

6. Compatibility
6. Compatibility
6.1
AMS
The 7330 ISAM FTTN, Feature Group 3.6.01 is compatible with the Alcatel-Lucent
5526 AMS, Release 6.5.
Note:
6.2
Version file updates may be required for applications which are used to manage
the 7330 ISAM FTTN. Please consult the application's documentation set for
details on version file update requirements.
CPE
Multi-ADSL bonding modem compatibility has been qualified with the following CPEs;
see Section 7.4, Multi-ADSL bonding for more information:
Comtrend NexusLink CT-5622 LR13 (L1 3.0.11)
Netopia MiAVo 7247-03 771fc1
Within this release the EVLT-A, EVLT-F, and SEM (VSEM-A) have been qualified with the
following CPEs:
ADSL:
Netopia 3546 6.4.0 R2
Efficient Networks 5100B-v10036
Efficient Networks 5100 v 004-E141-A01-61-9
2Wire 1800HG-v371
VDSL:
2Wire 3800HGV-B 5.29.105.53 and 5.29.105.76 (Conexant FW 8.117)
VDSL2:
2Wire 3800HGV-B 5.29.133.25
7. Application notes
This section highlights some important considerations and limitations associated with
this release. These restrictions will be addressed in future releases of the product.
Section 9, Open issues should also be referred to for a list of known issues associated
with this release.
7.1
Features documented but not supported

The following features are documented in the user documentation associated with
Feature Group 3.6.01, but are not supported in the Feature Group 3.6.01 release:
CPE Remote Management
RIP
OSPF
7.2
PPPoE termination
VBAS
Spatial alarm filtering for environmental (ENV) alarms
48p VDSL2 LT-level bonding (EVLT-F)
SFP parameter retrieval
Upgrade and migration

The Software Upgrade Automation Tool is used to download, upgrade, migrate, and
commit the software on one or more 7302 ISAM or 7330 ISAM FTTN nodes.
Note:
The procedure documented in Software Upgrade and Migration Application

Procedures has been optimized for the upgrade from Feature Group 3.0 and
later to Feature Group 3.6.01 and is the recommended upgrade mechanism for
all upgrades.
Supported migration path

Feature Group 3.6.01 supports migration from Feature Group 3.0 and above to
Feature Group 3.6.01. Migration from other feature groups to Feature Group 3.6.01 can
only be executed by Alcatel-Lucent. Contact your local Alcatel-Lucent representative
for assistance.
Note:
Migration from Feature Group 3.0.02 or Feature Group 3.0.02a to

Feature Group 3.6.01 is not supported. Contact your local Alcatel-Lucent
representative for assistance.
Warning: The installation of Feature Group 3.6.01 software on a 7330 ISAM FTTN that
includes EBLT-E, EBLT-K, and EVLT-F LT cards may result in the file system
being upgraded on these LT cards. The file system upgrade requires on-line
reprogramming of the Boot PROM image for these cards. This Boot PROM
image reprogramming will increase the total time to perform the software
update by up to 3 minutes for a fully populated node. It is important that the
Boot PROM image programming be allowed to complete and should not be
mistaken for an LT unit upgrade failure. Removal of an LT unit while the Boot
PROM image is being programmed could corrupt the LT unit Boot PROM
image, which would require the card to be returned to Alcatel-Lucent for
repair.
Software Download Optimization

Feature Group 3.6.01 uses the enhanced software download management introduced in
Feature Group 3.2. With this enhancement, the system performs a discovery to identify
card types presently installed or planned in the system and downloads only the software
for those card types. This reduces the amount of software downloaded and reduces
upgrade and migration time. If software for an unplanned card needs to be downloaded,
use one of the following methods:
To download the software for the unplanned card when upgrading or migrating
the software on the system, use the --minset parameter when you run the
automated software minimization tool; see DLP 101 in the Software Upgrade
and Migration Application Procedures.

To download the software for the unplanned card when installing the card, see
DLP 110 and DLP 169 in the Hardware Installation and Maintenance Practices.
Protocol indexing formats when migrating from Feature Group 3.0

Note:
The information in this section does not apply when migrating from Feature
Group 3.0.03e.
When performing a migration from Feature Group 3.0, in order to preserve the protocol
circuit identification slot indexing format, the following parameters must be used in the
Software Upgrade Automation Tool:
1.
2.
In the configuration file (param.cfg), enable the following options (remove the
commenting character in the configuration file) and set them to the value shown:
SYS_PORT_NUM_MED = 4 (to select legacy mode)
ATM_BASED_SYNTAX =
Access_Node_ID atm Rack/Frame/Slot/Port:VPI.VCI
ETH_BASED_SYNTAX =
Access_Node_ID atm Rack/Frame/Slot/Port:0.32
Use the --confopt82 option when running the automated software migration tool
(migrate.pl). This will change the default behavior for DHCP option 82, 802.1x, and
PPPoE relay.
Changes to the Software Upgrade Automation Tool components

In version 1.7.3 and later of the Software Upgrade Automation Tool, the param.cfg
configuration file is no longer present in the Software Upgrade Automation Tool package
included in the software CD. The operator is required to run an automated parameter
configuration tool (Config.pl) before using any of the components of the Software
Upgrade Automation Tool. This automatically creates the configuration file
(param.cfg). See DLP 100 and TNG 100 in the Software Upgrade and Migration
Application Procedures for information on creating and updating the param.cfg
configuration file.
7.3
Expansion shelf support

Please be aware of the following performance characteristics for LT units in an
Expansion Shelf:
The 7330 ISAM FTTN supports the following host and expansion configurations for
Feature Group 3.6.01:
1 host 7330 ISAM FTTN and up to 5 Expansion Shelves
A maximum of 12 SEM units
A maximum of 12 remote LT units including any combination of SEM and

Expansion Shelf LT units, subject to the previous limits of up to 12 SEMs and
5 Expansion Shelves
Removal and re-insertion of an EDSE-A card with active LT units may result in those
LT units resetting and all ports on those LT units re-training.

7.4
Multi-ADSL bonding
The multi-ADSL bonding capability (chipset and LT level ATM bonding) has been tested
with both the Comtrend NexusLink CT-5622 and the Netopia MiAVo 7267 bonding
modems.
Note:
7.5
Bonding group rate changes are not immediately applied, but retained for up to
10 minutes in order to handle potential temporary linkdrops. Rate changes can
be immediately applied if necessary by resetting the bonding group, which is
done by manually placing it out of service temporarily.
VLAN association with Expansion Shelf LT units and SEM

(VSEM-A)
Feature Group 3.4 introduced support of multishelf notation for Expansion Shelf VLAN
configuration commands. In earlier releases, users were required to use single shelf
notation when configuring an Expansion Shelf VLAN. Single shelf notation is still
supported for backwards compatibility.
With multishelf notation, the CLI command configure VLAN uses the actual rack and
shelf designators for the Expansion Shelf or SEM. With single shelf notation, the CLI
command configure VLAN ignores the rack and shelf designator for the Expansion
Shelf and only considers the LT unit index.
Example
To apply the VLAN to a SEM or Expansion Shelf LT unit in rack 3, shelf 2, slot 1 that is
connected to host SFP 14, the syntax is:
using multishelf notation:

configure vlan shub id 101 egress-port lt:3/2/1
using single shelf notation:

configure vlan shub id 101 egress-port lt:1/1/16
Note:
7.6
See DLP 177 and TNG 111 in the Operations and Maintenance Using CLI for more
information.
ADSL band usage in xDSL spectrum for VDSL

In the VDSL spectrum profile, the default behavior for the ADSL band usage has
changed. In order to maintain consistent behavior with previous releases, include the
ADSL band by explicitly configuring its usage within the xDSL spectrum profile, for
example, adsl-band allow-adsl in CLI.
7.7
Circuit identification in protocols

Feature Group 3.4 introduced the ability to configure the format and content of the LT
slot identifier used to communicate circuit ID information.
The following values are supported:

Logical slot numbering: in this mode, the slots are logically numbered using the
system internal MIB index.
With this scheme, slots LT1 through LT4 in the 7330 ISAM FTTN host shelf are
identified as 1/1/03/port# to 1/1/06/port#. This is the default setting.
Position-based numbering: in this mode, the slots are numbered based on their
relative position in a shelf: left to right, and top to bottom.
With this scheme, slots LT1 through LT4 in the 7330 ISAM FTTN are identified as
1/1/05/port# to 1/1/08/port#.
This mode is not supported on the 7330 ISAM FTTN.
Type-based numbering: in this mode, the slots are numbered based on the card
type (similar to the TL1 AID scheme).
1/1/01/port# to 1/1/04/port#.
Legacy numbering: in this mode, the slots are numbered based on the legacy
numbering scheme used in CLI commands.
1/1/04/port# to 1/1/07/port#.
For example, to configure the 7330 ISAM FTTN to use a circuit ID that corresponds to
TL1 slot indexing (type-based numbering), use the following TL1 command:
set-portnumsys::com:::portnum=typenum;
Refer to the TL1 Commands and Messages guide (set-portnumsys command) or the
CLI Commands guide (configure system command) for command syntax and details.
7.8
CLI system configuration of slot ID format

Feature Group 3.2 introduced changes to the CLI operation with support for the ability
to select new equipment slot ID formats.
The slot ID format is chosen using the CLI command configure system security.
See the CLI Commands guide for the detailed syntax.
7.9
Integrated VoIP-SIP
Depending on the timing difference between the network and the local device, lengthy
call durations (that is, greater than 1 hour) for fax or modem applications using the
7330 ISAM FTTN integrated VoIP-SIP feature may occasionally experience loss of
synchronization requiring calls to be re-established.
7.10 Behavior change for TL1 dlt-vlanegport command

Feature Group 3.4 introduced a change in the behavior of the TL1 command
dlt-vlanegport. The command no longer allows deletion of a VLAN egress port while
the associated VLAN is used as the default VLAN for the underlying bridge port. The
operator should first remove references to this VLAN from the DEFAULTSVLAN and
DEFAULTCVLAN parameters of the underlying bridge port using the command
set-vlanport.

7.11 Change in xDSL line provisioning behavior

Feature Group 3.4 introduced the following changes in the xDSL line provisioning
behavior in order to make line provisioning more flexible and easier to manage.
xDSL line provisioning is no longer a pre-condition for provisioning higher layer port
configuration (for example, ATM PVC, bridge port, and so on). These can be done in
any order now.
Unprovisioning of an xDSL line no longer automatically deletes higher layer port

configuration to allow above flexibility. This means that higher layer port
configuration has to be explicitly deleted if required.
7.12 IGMP v3
Feature Group 3.4 introduced support for IGMP v3, which is now the default IGMP
operation. In order to support the pre-Feature Group 3.4 operation, the following IGMP
CLI commands must be run:
configure
configure
configure
configure
igmp
igmp
igmp
igmp
shub
shub
shub
shub
vlan-filter
vlan-filter
vlan-filter
vlan-filter
MulticastVLAN#
MulticastVLAN#
MulticastVLAN#
MulticastVLAN#
configure igmp system netw-igmp-version 2

configure igmp system user-igmp-version 2
snoop-filter
igmp-version 2
no snoop-filter
querier enabled
Compared to earlier releases, the SHub query timer syntax has changed from:
configure igmp shub vlan-router-port 4000 network-port 1 querytimer 125

to
configure igmp shub vlan-router-port MulticastVLAN# networkport port#
configure igmp shub vlan-filter MulticastVLAN# query-int 125
Please refer to the CLI Commands document for more information.
7.13 VDSL1/VDSL2 minimum rate requirements

VDSL1 and VDSL2 services on the EVLT-A and EVLT-F cards have minimum rate
requirements of 2048 kb/s downstream and 192 kb/s upstream. Service profiles that are
configured for bitrates lower than these values will be accepted by the system, but once
configured on a VDSL1/VDSL2 port, a critical configuration error alarm will be raised.
For example, in CLI the output would be: <date> <time> critical alarm
occurred for XDSL lt port x/x/x/x , near end (service affecting) :
Modem activation failed due to configuration error
7.14 White spaces in profile names

In earlier releases, profile names that contained white spaces were treated differently
by the various management interfaces available on the 7330 ISAM FTTN.
8. Supported hardware
CLI: Could not create or view profiles names that contained white spaces.
5526 AMS: Could create and view profiles names that contained white spaces.
TL1: Could view profiles names that contained white spaces. If an attempt was
made to create a profile name with a white space, the white space would be
removed but the profile name would be created.
This behavior is correct in Feature Group 3.6.01. White spaces are no longer accepted
by any of the management interfaces. Additionally, the Software Upgrade Automation
Tool will remove any white spaces and concatenate the profile name when migrating
from a release that allowed white spaces to Feature Group 3.6.01 or later.
7.15 Discontinued support for reboot with self-test

The CLI command admin equipment reboot-isam with-self-test is intended
for Alcatel-Lucent internal usage and is not intended for field usage. Although the
command is documented, it should not be used, as it may impede the proper reboot
sequence of some 7330 ISAM FTTN configurations.
Table F lists the supported hardware for 7330 ISAM FTTN Feature Group 3.6.01.
Table F. Supported hardware for 7330 ISAM FTTN Feature Group 3.6.01
Mnemonic
Part number
Shelves
ARAM-D: for cabinet deployment (no fan filter)
3FE 24319 AA
3FE 24319 AE
ARAM-D: for CO deployment (includes fan filter)
3FE 24319 AB
Cards, appliques, and fan units

AFAN-L
3FE 24322 AA
3FE 24322 AE
10
AVPC-A (with ITSC)
3FE 26509 AG
AVPC-A (without ITSC)
3FE 26509 AD
EBLT-C
3FE 21641 AA
EBLT-E
3FE 23196 AA
EBLT-K
3FE 25549 AA
ECNT-A
3FE 23086 AA
ECNT-C
3FE 25676 BA
EDSE-A
3HJ 20001 AA

Table F. Supported hardware for 7330 ISAM FTTN Feature Group 3.6.01 (Continued)
Mnemonic
Part number
EVLT-A
3FE 23526 AA
EVLT-F
3FE 25389 AA
GENC-E
3FE 24324 AB
GENC-F
3FE 26770 AA
3FE 26770 AC
HCUT-C
3FE 22695 AC
HHLA-G
3FE 22695 AB
HLPC-H
3FE 22693 AA
HLPC-J
3FE 24331 AA
POLT-B
3FE 27372 AA
PTPC-A
3FE 24709 AA
PWIO-B
3FE 24323 AA
3FE 24323 AB
3FE 24323 AC
3FE 24323 AD
SATU-A
3HJ 20005 BA
SMLT-K 1
3FE 28799 AB
VPSC-D
3FE 24318 AF
SEM (VSEM-A)
3EM 17671 AB
3EM 17671 AD
3EM 17671 AJ
3EM 17671 AS
SEM (ASEM-B)
3EM 19073 AA
3EM 19073 AB
SFP modules
Gigabit Ethernet optical 1000Base-CWDM 1471 nm
3FE 25771 AA
3FE 25771 AB
3FE 25771 AC
3FE 25771 AD
3FE 25771 AE
3FE 25771 AF
3FE 25771 AG
3FE 25771 AH

11
9. Open issues
Table F. Supported hardware for 7330 ISAM FTTN Feature Group 3.6.01 (Continued)
Mnemonic
Part number
Gigabit Ethernet optical 1000Base-BX10-U
3FE 25772 AA
Gigabit Ethernet optical 1000Base-BX10-D
3FE 25772 AB
Gigabit Ethernet optical 1000Base-SX
3FE 25773 AA
Gigabit Ethernet optical 1000Base-SX
3FE 25773 CA
Gigabit Ethernet optical 1000Base-LX
3FE 25774 AA
Gigabit Ethernet optical 1000Base-EX
3FE 25775 AA
Gigabit Ethernet optical 1000Base-ZX
3FE 25776 AA
Gigabit Ethernet optical 1000Base-ZX
3FE 25776 BA
Fast Ethernet optical 100Base-FX 2
3FE 29625 DA
1. This card has software support in this release but the hardware has not yet reached DR4
availability. When ready, hardware introduction will be announced by a Product Information
Bulletin.
2. Support of this module is limited to approved customer applications pending final hardware
qualifications for this component.
9. Open issues
The following items are identified as the known open issues at the time of release of
this document. Each open issue is tracked by one or more problem tracking numbers.
Problems are tracked by Alcatel-Lucent internal problem report numbers, and by CTR
number, if applicable.
The open issues are designated with severity levels 1 to 3. See Section 11, Glossary and
abbreviations list for the definition of Problem Severity Levels.
9.1
Level 1 open issues
There are no severity 1 open issues for this release.
12

9.2
9. Open issues
Level 2 open issues
Table G. Severity level 2 open issues

Item
Problem number
Synopsis
1.
ANTms58043
Title: Maximum NMR in VDSL and VDSL2 does not work properly
Problem: The maximum noise margin parameter, defined in the xDSL spectrum profile for
the EVLT-A, EVLT-F, and VSEM-A, does not function properly. In VDSL, the resolution of
maximum NMR is in 0.5 dB increments instead of 0.1 dB increments, and in VDSL2 the
function is not operational.
Workaround: The transmit power can be limited via several mechanisms including VDSL2
custom PSD masks and defining a maximum aggregate power or level in the associated
xDSL spectrum profile.
2.
ANTmt06982
Title: MAC address conflict alarm not cleared

Problem: When there is a MAC address conflict alarm on the SHub, the alarm does not
clear after the aging timer expires.
Workaround: Configure a static MAC with the conflicting MAC address then remove it. For
example:
configure vlan shub unicast-mac 00:00:00:00:00:01 vlan-id 101
forward-port lt:1/1/5
configure vlan shub no unicast-mac 00:00:00:00:00:01 vlan-id 101
This will remove the duplicate MAC alarm on both LT and SHub.
3.
ANTmt10947
Title: SHub LA statistics counters reporting incorrectly using TL1

Problem: The TL1 command REPT-OPSTAT-SHUBLAPORT is reporting incorrect
statistics. The counters are not displayed properly.
Workaround: Use CLI command show la network-port-info detail.
4.
ANTmt12403
Title: Link aggregation configuration is not removed when reconfiguring an uplink to a

downlink
Problem: When reconfiguring a port from uplink to downlink, the LA configuration is not
removed automatically.
Workaround: Remove the entire LA configuration before reconfiguring it to a downlink.
9.3
Level 3 open issues
Table H. Severity level 3 open issues

Item
Problem number
Synopsis
1.
ANTms11388
Title: EVLT-F: ADSL traffic affected after switch from VDSL or VDSL2
Problem: After changing the port configuration from VDSL or VDSL2 to ADSL, the user
may experience delays with small traffic flow.

13
9. Open issues
Table H. Severity level 3 open issues (Continued)

Item
Problem number
Synopsis
2.
ANTms16991
Title: Some VDSL2 DELT data is not available
ANTms57870
Problem: When using the EVLT-A, EVLT-F, and VSEM-A, some VDSL2 DELT data is not
available, including signal attenuation, HLIN, and aggregate output power.
ANTms38821
Title: EVLT-A, EVLT-F, and VSEM-A: SELT echo measurement time ignored
3.
Problem: If the SELT echo measurement time is configured to a value other than the
default value, the configured value is ignored.
Workaround: Use the default value (240 seconds).
4.
ANTms52385
Title: VDSL or VDSL2 NE-LOS alarm delayed

Problem: The VDSL or VDSL2 NE-LOS alarm can be delayed up to 17 seconds on the
EVLT-A, EVLT-F, and VSEM-A.
5.
ANTms57353
Title: VDSL2 signal attenuation not accurate on EVLT-A, EVLT-F and VSEM-A
Problem: The VDSL2 upstream signal attenuation value is not reliable from the EVLT-A,
EVLT-F or VSEM-A.
6.
ANTmt00534
Title: Link aggregation traffic statistics counters return incorrect data

Problem: The link aggregation statistics counter CLI command show la aggregatorinfo returns incorrect values for the parameters rx-error-frames and rxdiscard-frames.
7.
ANTmt11219
Title: Port-level alarm severity defaults after reset

Problem: The configured value for port alarm reporting severity is not restored after an
NT reset, resulting in it being set to its default value.
8.
ANTmt13676
Title: Link aggregation partner information not removed from a previous primary port
that is operationally down
Problem: If a new port is added to the LA group and this port becomes the primary port,
the partner-sys-id and partner key are not removed from the previous primary port even
though the port is operationally down.
Workaround: Bring the port operational up and down again.
9.
BDFhw72161
Title: Statistics retrieval on 7330 ISAM FTTN may show data out of order
Problem: When retrieving statistics related to slot-port info (show igmp module, show
xdsl operational-data, show security pae), the related data may be reported
in the wrong order of slot sequence (for example, slot 1/1/6 ports data may be reported
before slot 1/1/4 data).
10.
BDFhw79151
Title: EVLT-A, EVLT-F, and VSEM-A: Configure ADSL maximum transmit power
Problem: When the EVLT-A, EVLT-F, or VSEM-A is configured in ADSL mode, if the
maximum transmit power is configured to a negative value, then a modem activation
failure alarm occurs. Values above the boards capabilities (14.5 dBm) can also cause this
situation.
Workaround: Keep the ADSL maximum transmit power value within the range of 0.0 dBm
to 14.5 dBm.
14

10. Closed issues
10.Closed issues
The following items are known and customer-reported issues that are closed in
Feature Group 3.6.01. Each closed issue is tracked by one or more problem tracking
numbers. Problems are tracked by Alcatel-Lucent internal problem report numbers and
by CTR number, if applicable.
The closed issues are designated with severity levels 1 to 3. See Section 11, Glossary
and abbreviations list for the definition of Problem Severity Levels.
10.1 Level 1 closed issues

There are no severity level one issues closed in this release.

Table I. Severity level 2 closed issues
Item
Problem number
Synopsis
1.
ANTms62179
Title: Incomplete VLAN port listing provided with CLI command show interface
stack
Problem: The CLI commands show interface stack and show interface stack
detail only display the first VLAN port identifier assigned to a bridge port.
Resolution: CLI subsystem modifications resolved the issue.
2.
ANTms76597 1
Title: The CLI command show pppox-relay cross-connect session clientport incorrectly reports number of sessions
Problem: The CLI command show pppox-relay cross-connect session clientport indicates only one session when there are two sessions present.
3.
ANTms84174 1
Title: VDSL2 can have unstable showtime with U0 band

Problem: There is an upstream receiver timing issue in the modem code when the port
selects to use the U0 band (typically around 3300 ft or 1 km, 26 AWG). This timing
problem can result in a large number of CRC errors on the port and possibly in a drop of
the line out of showtime after a period of time.
Resolution: xDSL subsystem modifications resolved the issue.
4.
ANTms85071 1
Title: Upstream re-marking requires special configuration when traffic is tagged on user
line
Problem: When traffic is received tagged from the end-user, configuring upstream remarking by means of an up-marker profile does not work.
Resolution: QoS subsystem modifications resolved the issue.

15
10. Closed issues
Table I. Severity level 2 closed issues (Continued)

Item
Problem number
Synopsis
5.
ANTms85245
Title: NT unit switchover causing EBLT-C resets
1-1746632
Problem: NT unit switchovers are causing LT unit resets. The boards fully recover, but
service is interrupted. During the NT switchover, the EBLT-C detects a buffer overrun on
the MSF, and stops processing all traffic until the NT detects a loss of communication to
the LT and resets the LT. The service outage of an individual customer on an affected LT
would be the detection time (~5 minutes) plus the LT reset time and modem retraining
times. This is 100% reproducible when running traffic during a switchover.
Resolution: Equipment subsystem modifications resolved the issue.
6.
ANTms86592
Title: NT unit reset causing switchover
1-1746632
Problem: Intermittent NT unit resets are causing NT unit switchovers in the network.
7.
ANTms87103 1
Title: Locking VLAN port after duplicate MAC address alarm doesn't work
Problem: When a duplicate MAC address is seen on different user ports coupled to the
same iBridge, then a duplicate MAC address alarm is generated and the offending VLAN
port is locked until the MAC aging timer expires. If, in addition, the operator manually
locks the VLAN port, this locking should remain effective, even after the MAC aging timer
expires. However, this is not the case.
Resolution: VLAN subsystem modifications resolved the issue.
Closed in this release.

Table J. Severity level 3 closed issues
Item
Problem number
Synopsis
1.
ANTms06699
Title: Primary service state of LTVCL displayed incorrectly

Problem: Primary service state of LTVCL is displayed as OOS-AU in situations where it
should display OOS-AUMA.
Resolution: TL1 subsystem modifications resolved the issue.
2.
ANTms22704
Title: EVLT-A, EVLT-F, and VSEM-A: FE_SES and FE_UAS not updated properly
Problem: The VDSL FE_SES counter value is not added to the FE_UAS counter when the
line loses showtime, also the FE_SES counter is not decremented by 10 seconds.
Resolution: VDSL2 subsystem modifications resolved the issue.
3.
ANTms42193
Title: VDSL2 FE UAS count is not available

Problem: The Far End Unavailable Second count is not available with the EVLT-A, EVLT-F,
and VSEM-A.
16

10. Closed issues
Table J. Severity level 3 closed issues (Continued)

Item
Problem number
Synopsis
4.
ANTms59636
Title: No error handling for VLAN protocol groups in TL1

Problem: TL1 always allows the user to execute the command ent-protocol-group
even though a protocol group is already present on the VLAN port. Editing of the existing
protocol group fails. TL1 is not showing any error or warning message if the user tries to
create several VLAN protocol groups on the same VLAN port.
5.
ANTms59868
Title: Committed burst size is limited to 160 kbytes

Problem: The maximum value of the committed burst size is limited to 160 kbytes
(instead of 256 kbytes).
Resolution: QoS subsystem modifications resolved the issue.
6.
ANTms60702
Title: VDSL custom PSD mask causes configuration error

Problem: When a custom PSD mask is defined on the EVLT-A, EVTL-F, or VSEM-A in VDSL
mode, a configuration error alarm is raised.
7.
ANTms60889
Title: PPPoX statistics reported incorrectly

Problem: The generic-err-cnt field is reported incorrectly in CLI (show pppox-relay
cross-connect monitor-statistics engine). This counter is not incremented.
Resolution: PPPoX subsystem modifications resolved the issue.
8.
ANTms61348
Title: LT restart count increments when provisioning an LT unit

Problem: When the system is started, all the LT units are reported with a restrt-cnt
value of 1 instead of 0.
9.
ANTms61350
Title: Minor VDSL alarm (NE NCD) not available with CLI with EVLT-F, EVLT-A, and VSEM-A
Problem: When the VDSL connection to the CPE is disconnected, an LOS and NE NCD
alarm is generated for both the TL1 and 5526 AMS interfaces, but only the LOS for the CLI
interface. Note that NE NCD (Near End No Cell Delineation) is a minor DSL alarm.
10.
ANTms62905
Title: Syntax error in DLP 176 of Operations and Maintenance Using CLI document
Problem: In step 3, the command show aggregator-list should be show
aggregate-list.
Resolution: Documentation was updated to resolve the issue.
11.
ANTms62907
Title: Syntax error in DLP 176 of Operations and Maintenance Using CLI document
Problem: In step 7, the command show qos statistics fan-out should be show
qos statistics ltcos.

17
10. Closed issues

Item
Problem number
Synopsis
12.
ANTms64099
Title: System reset not required on the GENC-E and GENC-F after configuring SFP ports
Problem: The Operations and Maintenance Using CLI indicates that a system reset is
required after configuring SFP ports on the GENC-E or GENC-F (DLP 177, step 3). This
step is not required when configuring SFP ports on a GENC-E or GENC-F card.
13.
ANTms70394 1
Title: No traffic after reconfiguring line from ADSL to VDSL

Problem: After reconfiguring the line from ADSL to VDSL on an EVLT- F, the line comes up
but no traffic flows. Problem is seen for both L2 and L3 configurations.
14.
ANTms84543 1
Title: TL1 command to retrieve SFP data may return invalid information
Problem: When SFP data is requested using TL1 for an SFP that is physically not present,
invalid data is returned and no error is given.
15.
ANTms85583 1
Title: Environmental alarms are not suppressed using CLI session through Telnet
Problem: Using CLI command environment inhibit-alarms via Telnet does not
suppress the environmental alarms.
16.
ANTms86063 1
Title: LTSFP access identifier missing for REPT-OPSTAT-SFP

Problem: TL1 command REPT-OPSTST-SFP is missing the access identifier LTSFP for
SFP. Instead, ETHPORT is listed as one of the access identifiers, which is not correct.
17.
ANTms86687 1
Title: IGMPv3 tracing for unconfigured multicast groups in VLAN cross-connect mode is
not working
Problem: The IGMPv3 protocol tracing feature is only supported for configured multicast
groups in VLAN cross-connect mode. IGMPv2 tracing for unconfigured multicast streams is
working properly.
Resolution: IGMP subsystem modifications resolved the issue.
18.
ANTms87301 1
Title: Link aggregation parameter shows wrong range in CLI

Problem: When configuring link aggregation on the network port the parameter "actorport-prio" shows the range as 0...65535 but the values are accepted only in the range of
0...255.
Workaround: Values need to be configured only between 0...255
19.
ANTms87884 1
Title: Receive counters are not working for LACP packets

Problem: When LACPDU packets are received from network side, the receive counters
are decrementing instead of incrementing as expected.
18

11. Glossary and abbreviations list

Item
Problem number
Synopsis
20.
ANTms88084 1
Title: SHub commands are running slow
AR1-1871822
Problem: SHub-related CLI commands are executing slower than usual.

Resolution: SHub subsystem modifications resolved the issue.
21.
BDFhw79893
Title: EVLT-A, EVLT-F, and VSEM-A: VDSL target noise margin not working properly for
values less than 1 dB
Problem: The target noise margin must be at least 1 dB.
Resolution: xDSL subsystem modifications resolved the issue for VDSL2.
Closed in this release.
11.Glossary and abbreviations list

This section contains an alphabetized list of terms, acronyms, and abbreviations used
within this document.
Term
Definition
ADSL
Asymmetric Digital Subscriber Line
AMS
Access Management System
ATM
Asynchronous Transfer Mode
BAC
Buffer Acceptance Control
BER
Bit Error Rate
CD
Compact Disk
CDC
Carrier Data Collection
CFR
Code of Federal Regulations
CLI
Command Line Interface
CMP
Communication Problem
CNF
Configuration Not Feasible
CO
Central Office
CPE
Customer Premises Equipment
CRC
Cyclic Redundancy Check

19
20
Term
Definition
CRN
Customer Release Notes
CTR
Customer Trouble Report
CV
Code Violation
CWDM
Coarse Wavelength Division Multiplexing
DELT
Dual-Ended Line Testing
DHCP
Dynamic Host Control Protocol
D.H.H.S.
Department of Health and Human Services
DLP
Detailed Level Procedure
DSCP
Differentiated Services Control Point
DSL
Digital Subscriber Line
DSLAM
Digital Subscriber Line Access Multiplexer
EAPOL
Extensible Authentication Protocol Over LAN
EOC
Embedded Operations Channel
EQPT
Equipment
FCC
Federal Communications Commission
FE
Far End
FTTN
Fiber to the Node
IGMP
Internet Group Management Protocol
IP
Internet Protocol
ISAM
Intelligent Services Access Manager
ITSC
Integrated Test and Sealing Current
ITU
International Telecommunications Union
LA
Link Aggregation
LACP
Link Aggregation Control Protocol
LAN
Local Area Network
LANX
7330 ISAM FTTN network termination card Ethernet switch (also known as
SHub)

Term
Definition
LOL
Loss of Link
LOM
Loss of Margin
LOS
Loss of Signal
LPR
Loss of Power
LT
Line Termination
LTVCL
Line Termination Virtual Channel Link
MAC
Media Access Control
MIB
Management Information Base
MSTP
Multiple Spanning Tree Protocol
Multi-ADSL
Multi-Asymmetric Digital Subscriber Line
NE
Near End
NMR
Noise Margin Ratio
NT
Network Termination
OOS
Out-of-service
OSPF
Open Shortest Path First
OSS
Operations Support System
PM
Performance Monitoring
PPPoE
Point-to-Point Protocol over Ethernet
Problem Severity Level 1
Critical problems that severely affect service, capacity/traffic, billing,

and maintenance capabilities.
Major problems that cause conditions that seriously affect system

operation, maintenance, and administration, etc. The urgency is less than
in level 1/critical situations because of a lesser immediate or impending
effect in system performance, customers, and the customers operation
and revenue.
Minor problems do not significantly impair the functioning of the system

and do not significantly affect service to customers.
PROM
Programmable Read-Only Memory
PSD
Power Spectral Density
PVC
Permanent Virtual Connection

21
22
Term
Definition
QLN
Quiet Line Noise
QoS
Quality of Service
RFI
Radio Frequency Interference
RG
Residential Gateway
RIP
Routing Information Protocol
SELT
Single-Ended Line Testing
SEM
Sealed Expansion Module
SES
Severely Errored Seconds
SFP
Small Form-factor Pluggable
SHDSL
Symmetric High-speed Digital Subscriber Line
SHub
7330 ISAM FTTN and 7302 ISAM Network Termination card Ethernet switch
(also known as LANX)
SNMP
Simple Network Management Protocol
SNR
Signal to Noise Ratio
SRA
Seamless Rate Adaptation
TL1
Transaction Language 1
TNG
Training Document
UAS
Unavailable Second
UDP
User Datagram Protocol
UPBO
Upstream Power Back-Off
VBAS
Virtual Broadcast Access Server
VDSL
Very High Bit Rate Digital Subscriber Line
VLAN
Virtual Local Area Network
VoIP-SIP
Voice over Internet Protocol-Session Initiation Protocol
xDSL
Digital Subscriber Loop (multi-ADSL or VDSL)

Alcatel-Lucent. All rights reserved.


7330

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

7330

Transféré par

Droits d'auteur :

Formats disponibles

CUSTOMER RELEASE NOTES

7330 ISAM FTTN

IMPORTANT NOTICE: This document contains confidential information that is proprietary to

THIS PRODUCT COMPLIES WITH D.H.H.S. RADIATION PERFORMANCE STANDARDS 21 CFR,

Technical Support Telephone Number

Marks (trademarks, service marks) and trade names

Alcatel-Lucent 2008. All Rights Reserved.

Table A. Related documents

Provides general system information, features and functionality,

Provides task-oriented procedures for operating and maintaining

7330 ISAM FTTN, Feature Group 3.6.01

This document is located on the 5526 AMS CD.

Table A. Related documents (Continued)

Software kit (these documents are located on the software CD)

CRN for the 7330 ISAM FTTN Feature Group 3.6.01

Software Upgrade and Migration

Provides instructions for using the automated tools for upgrading

Table B lists the part number of the documentation CD required for

7330 ISAM FTTN Feature Group 3.6 documentation CD

Connectivity fault management support as per 802.1ag

5. Software delivery and installation

7330 ISAM FTTN, Feature Group 3.6.01

5. Software delivery and installation

Table C. 7330 ISAM FTTN Feature Group 3.6.01 Software Kit

7330 ISAM FTTN Feature Group 3.6.01 Software Kit

7330 ISAM FTTN Feature Group 3.6.01 Software CD

7330 ISAM FTTN Feature Group 3.6.01 Customer Release Notes

7330 ISAM FTTN Feature Group 3.6.01 software (see Table E)

Software Upgrade Automation Tool (see Table E for version number)

Database Software Upgrade

FGN 3.4.01a L6GQAA33.325 LANX_R3.3.21.1

FGN 3.5.00a L6GQAA34.098 LANX_R3.4.11.3

FGN 3.5.00b L6GQAA34.098 LANX_R3.4.11.3

FGN 3.5.00c L6GQAA34.099 LANX_R3.4.11.3

7330 ISAM FTTN, Feature Group 3.6.01

Comtrend NexusLink CT-5622 LR13 (L1 3.0.11)

Netopia MiAVo 7247-03 771fc1

Netopia 3546 6.4.0 R2

Efficient Networks 5100B-v10036

Efficient Networks 5100 v 004-E141-A01-61-9

2Wire 3800HGV-B 5.29.105.53 and 5.29.105.76 (Conexant FW 8.117)

2Wire 3800HGV-B 5.29.133.25

Features documented but not supported

CPE Remote Management

Spatial alarm filtering for environmental (ENV) alarms

48p VDSL2 LT-level bonding (EVLT-F)

SFP parameter retrieval

Upgrade and migration

The procedure documented in Software Upgrade and Migration Application

Supported migration path

Migration from Feature Group 3.0.02 or Feature Group 3.0.02a to

Software Download Optimization

7330 ISAM FTTN, Feature Group 3.6.01

Protocol indexing formats when migrating from Feature Group 3.0

SYS_PORT_NUM_MED = 4 (to select legacy mode)

Changes to the Software Upgrade Automation Tool components

Expansion shelf support

1 host 7330 ISAM FTTN and up to 5 Expansion Shelves

A maximum of 12 SEM units

A maximum of 12 remote LT units including any combination of SEM and

7330 ISAM FTTN, Feature Group 3.6.01

VLAN association with Expansion Shelf LT units and SEM

using multishelf notation:

using single shelf notation: