ams-c 6-4-0-crn-ed 01 - vox technologiesmediaserver.voxtechnologies.com/filecache/alcatel-lucent...

5526 AMS (Classic)

Release 6.4.0

3EM 16129 DGAA Edition 01

C U S T O M E R R E L E A S E N O T I C E

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 registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. © 2007 Alcatel-Lucent. All rights reserved.

5526 AMS (Classic) Release 6.4.0 Release Notice

Alcatel-Lucent 3EM 16129 DGAA Edition 01 August, 2007 | 2

Contents 1 Access Management System software description ................................. 5

1.1 About this document ...................................................................... 5 1.2 Purpose ...................................................................................... 5 1.3 Release description ........................................................................ 5 1.4 Backward compatibility ................................................................... 5 1.5 Release notation ........................................................................... 6 1.6 Installation instructions ................................................................... 6 1.7 Patches and service packs ................................................................ 6

2 AMS features ............................................................................... 6 2.1 Redundancy features ...................................................................... 6

AMS server redundancy.................................................................... 6 AMS auto switchover....................................................................... 6

2.2 User interface features ................................................................... 7 ALMAP-AS.................................................................................... 7 Emptying and clearing the event database ............................................ 7 Emptying and clearing the performance monitoring database ..................... 7 Reporting enhanced for visual and audio alarm....................................... 7 TL1 cut-through to network elements .................................................. 7 Logical management of domains and alarm counts .................................. 8 System discovery ........................................................................... 8 AMS database synchronization ........................................................... 8 Equipment provisioning ................................................................... 8 Cross-connections.......................................................................... 8 Network query.............................................................................. 9 Backup, download, discovery, and command scheduling............................ 9 Network element system and node restore............................................ 9 Alarm and event date range from pull-down menus or calendar................... 9 AMS-network element communications ................................................ 9 Network element automated generic software download........................... 9 Network element system software activation........................................10 Network element PON services provisioning..........................................10 FTTU node and equipment unit resetting support...................................10 ATM profile support.......................................................................10 Blocking OSS access to systems .........................................................10 Blocking alarm reporting from systems................................................10 Acknowledge alarms per user ...........................................................10 Assigning scheduled jobs to network elements through a flat file................10 GR-303 P-phone support .................................................................11 Litespan TR-008 copper fed support ...................................................11 OC-3 and T3 facility provisioning.......................................................11 Starspan provisioning.....................................................................11 SONET transport provisioning ...........................................................11 AMS-Litespan communications ..........................................................11 Litespan SONET, DS1, and DS0 facility provisioning .................................11 Litespan-ADSL facility provisioning.....................................................12 Litespan automated generic software download ....................................12 Litespan system software activation...................................................12 AMS-ASAM communications..............................................................12



ASAM automated generic software download ........................................12 ASAM system software activation.......................................................12 ASAM ADSL, DS3, VPL, and VCL facility provisioning ................................12 IMA group support.........................................................................12 ASAM node and equipment unit resetting support...................................13 Reserving and freeing ports .............................................................13 Viewing and provisioning the next available port....................................13 ASAM ATM and ADSL line profile support..............................................13 ASAM SVC profile support ................................................................13 Switched Virtual Channel (SVC) support ..............................................13 ASAM high-speed discovery ..............................................................13 ASAM profile template ...................................................................13

2.3 Fault management features .............................................................14 Time synchronization.....................................................................14 Alarm surveillance ........................................................................14 Network alarm/event history ...........................................................14 Upstream TL1 interface..................................................................14 System alarm query.......................................................................14 Litespan alarm history....................................................................14

2.4 Performance management features ...................................................15 FTTU performance-monitoring history.................................................15 Litespan performance-monitoring history.............................................15 ASAM performance-monitoring history ................................................15 Performance-monitoring end dates ....................................................15

2.5 Security management features .........................................................15 AMS user security .........................................................................15 Basic system access security ............................................................15

2.6 Supported configurations ................................................................16 7340 FTTU (Fiber To The User) .........................................................16 7330 ISAM FTTN (Fiber To The Node) ..................................................16 General Bandwidth G6 ...................................................................16 Litespan ....................................................................................16 Starspan ....................................................................................16 ASAM (ATM Subscriber Access Multiplexer) ...........................................16 Hybrid Network Termination (HYNT) ..................................................17

3 Summary .................................................................................. 17 3.1 Release capabilities ......................................................................17

4 Details ..................................................................................... 17 4.1 Documentation delivery..................................................................17 4.2 Software delivery .........................................................................18 4.3 Software compatibility...................................................................18

Backward compatibility ..................................................................18 NE compatibility...........................................................................18 Server and client compatibility .........................................................20

4.4 Software installation .....................................................................20 4.5 SUN software and hardware notes .....................................................20

5 Release content ......................................................................... 20 5.1 Implemented features....................................................................20 5.2 Application notes .........................................................................20

Upgrade from previous version .........................................................20 AMS system notes .........................................................................21 SUN software notes .......................................................................23



SUN hardware notes ......................................................................24 7340 FTTU system notes .................................................................24 7330 ISAM FTTN system notes...........................................................25 7302 HYNT system notes .................................................................25 Litespan system notes....................................................................25 7300 ASAM system notes .................................................................26 GB G6 system notes.......................................................................28 SHUB system notes........................................................................28 X-terminal applications ..................................................................29

5.3 Restrictions ................................................................................29 5.4 New and/or changed configuration parameters .....................................29 5.5 New and/or changed environment variables .........................................29 5.6 Closed issues...............................................................................30

Major closed issues .......................................................................30 Minor closed issues........................................................................30

5.7 Open issues.................................................................................33 Major issues with 5526 AMS Classic ....................................................33 Minor issues with 5526 AMS Classic.....................................................33

6 Product documentation................................................................ 39 6.1 Customer user documentation ..........................................................39 6.2 Customer feedback .......................................................................39

7 Document release history ............................................................. 39 8 Glossary ................................................................................... 39



1 Access Management System software description 1.1 About this document

The contents of this document are intended primarily for system administrators, managers,

and engineers involved in planning, implementation, and lab testing of the Alcatel-Lucent

5526 Access Management System (AMS).

1.2 Purpose

This document introduces release 6.4.0 of 5526 Access Management System (AMS). AMS

Release 6.4.0 is the element management system for Alcatel-Lucent’s Litespan, ASAM, Fiber

to the User (FTTU), Fiber to the Node (FTTN), 7302 Hybrid Network Termination (HYNT),

and General Bandwidth’s G6 family of network elements.

1.3 Release description

The 5526 AMS Release Description describes the new features introduced with AMS Classic

6.4.0, along with software kits and Right to Use (RTU) part numbers for ordering this release

from your Alcatel-Lucent Sales Representative. The detailed technical descriptions are

available in the technical documentation available on CD-ROM and from the Alcatel-Lucent

Support Documentation Services web site. See Product Documentation in section 10 for more

information.

It should be noted that the 7302 HYNT network element type is supported at DR3P quality

from AMS. As well, the 7302 HYNT Operations and Maintenance Guide (Edition 01)

documentation is at DR3P quality. Further HYNT improvements have been made in this

release; however, HYNT remains at DR3P quality.

1.4 Backward compatibility

AMS-C 6.3.0, with or without patches or service packs, can be upgraded directly to

AMS-C 6.4.0. For AMS releases lower than AMS 6.3.0, you need to go through an

intermediate release to avoid data loss.

Please contact your Alcatel-Lucent Technical Support Representatives for assistance before

planning or performing an upgrade.



1.5 Release notation

AMS generic release numbers are represented in several different ways in various documents.

The following notations are equivalent and all refer to the same generic software version:

> Common notation: AMS release 6.4.0 or AMS-C release 6.4.0

> Extended notation: AMS release 06.04.00 or AMS-C release 06.04.00

1.6 Installation instructions

The installation of AMS software is described in the 5526 AMS Installation Guide. Its

contents are tailored to the information requirements of the engineering and lab personnel

involved in the installation and configuration of AMS.

1.7 Patches and service packs

Contact your Sales Representative for the most recent service pack and/or patch that is

relevant to this version of AMS. This is the first release for AMS 6.4.0; therefore, no service

pack needs to be installed prior to installation on server or client machines.

2 AMS features For more detailed descriptions of the new features in AMS-C 6.4.0, refer to the 5526 AMS

Release Description. The sections below describe AMS supported features.

2.1 Redundancy features

AMS supports the redundancy features described in the paragraphs below.

AMS server redundancy

AMS server redundancy continues to be supported with AMS-C, Release 6.4.0.

AMS-C 6.4.0 can be run in a redundant active-standby configuration (1 to 1). Through

this configuration, the standby server stays in sync with the active server and goes active

in case of an unrecoverable failure in the active side.

AMS auto switchover

Server switchover can be done either automatically or manually (through the AMS

System Administrator). There are specific conditions that must be satisfied before the

automatic switchover happens. For details of these conditions, please refer to the

AMS 6.4.0 User Guide.



2.2 User interface features

AMS supports the user interface features described in the paragraphs below.

ALMAP-AS

The Alcatel Management Platform - Alarm Surveillance sub-module is an alternative for

the traditional AMS Alarm management window. ALMAP-AS provides a wide range of

options for managing current and logged alarms. Users can open the ALMAP-AS window

by pressing and holding the CONTROL key while clicking on the Events icon.

Note Beginning with AMS 5.1.0, at AMS startup, ALMAP servers are set to DISABLED by default. The variable in the public.env AMS_ALMAP_MODE allows operators to enable or disable ALMAP. This prevents unnecessary delays during AMS startup for operators not using ALMAP.

Emptying and clearing the event database

AMS supports emptying the events log database of all current records and starting fresh.

Emptying and clearing the performance monitoring database

AMS supports emptying the performance-monitoring log database of all current records

and starting fresh.

Reporting enhanced for visual and audio alarm

AMS supports alarm reporting in two ways:

> You can instruct AMS to maximize the event viewer window each time a new alarm is

reported. Then, you can minimize the event viewer window on your desktop and

AMS opens it each time a new alarm is reported.

> You can instruct AMS to emit a beep or audible alarm each time a new alarm is

reported.

TL1 cut-through to network elements

All network elements can be accessed directly with TL1 using a primary or emergency

TL1 cut-through address. The cut-through mode provides expert users with a means for

troubleshooting or gaining access to network element functions not yet supported by

AMS software. Beginning with AMS 4.2, there are two ways of having a TL1 cut-through

session:

1. The traditional TL1 cut-through provides a direct link to the systems over the ATM

and IP network.



2. Another method of TL1 access is through AMS session (in-band TL1 cut-through). By

this method, the current AMS session is being used to send TL1 commands to the

network element (vs. opening a new session). A window provides a command list,

command history, connectivity status, and options to send commands from a file and

save the output in a file.

Logical management of domains and alarm counts

AMS allows domains that it is managing to be partitioned into smaller sub domains for

convenience. Sub domains are logical partitions that may be used to represent distinct

geographical management regions or individual wire centers.

Alarm notifications from lower-level components are passed up to the parent domain.

The total number of highest severity alarms is shown at the border of the parent domain.

Alarms of locked, disconnected, or unlicensed network elements are not counted (except

for network elements with an isolation alarm).

System discovery

AMS maintains a complete view of intelligent components in the domains it is managing.

All network element components are automatically and autonomously inventoried upon

initial connection to AMS.

The progress of active discovery, along with discovery history, can be checked from a

system-level window.

AMS database synchronization

The AMS database that reflects the state of network elements is synchronized (updated)

automatically by user-defined schedules, by use of the Actions->Discover command, or

by automatic database change notifications from the network elements.

Equipment provisioning

AMS allows an operator to assign and provision facilities on the network element

equipment units.

Cross-connections

AMS 6.4.0 supports creating, editing, deleting, and viewing of:

> FTTU, FTTN, HYNT, ASAM and Litespan VP and VC cross-connections

> Litespan T0 and T1 cross-connections



Cross-connections can be created, edited, and deleted from system, node, bank, shelf,

equipment, and port windows. Cross-connections are created and deleted in the AMS

graphical user interface by using drop-down list boxes to construct the access IDs for the

cross-connections.

Network query

All parameters and configurations of network element equipment, facilities, and

cross-connections can be searched. For example, AMS can produce a list of all

equipment units in a specific shelf that have a specific hardware version number.

Backup, download, discovery, and command scheduling

AMS supports creating schedules for backing up network element databases,

downloading software to systems, and discovering network element systems. Schedules

are then associated with specific systems or nodes.

AMS supports network element database backup at the system and node level through

proprietary data file transfer. The network element database backup can either be

performed on demand or scheduled to occur periodically.

Network element system and node restore

AMS supports restoring the network element system backup files to the system or node

level. Since AMS keeps track of the last two backups performed on each network element

system or node, users can choose to restore files from the latest backup, the second latest

backup, or a backup that was made external to AMS.

Alarm and event date range from pull-down menus or calendar

AMS supports choosing the alarm and event date ranges from pull-down menus. Filter

option setting dialog boxes and alarm history dialog boxes support choosing date ranges

from pull-down menus or by selecting the date from a calendar.

AMS-network element communications

AMS supports connections to network element systems via UDP/IP over an ATM

network, in-band ATM, and end-to-end ATM.

Network element automated generic software download

AMS maintains information about the software version currently active on each network

element system it is managing. AMS can distribute a new version of the network element

system software to network element systems running certain releases (see section 4.3).



Network element system software activation

AMS supports activation of network element system software loads at the equipment

unit level only.

Network element PON services provisioning

Network element operating parameters for PLT2 cards on PON services can be

provisioned from the AMS GUI.

FTTU node and equipment unit resetting support

AMS supports soft resetting on an equipment unit and node basis.

ATM profile support

AMS supports creating and deleting ATM traffic descriptor profiles (CAC, TD, Access),

and ONT profiles (AAL1, MacBridge, CES, Ethernet). Profiles can then be linked and

associated with network element facilities.

Blocking OSS access to systems

AMS supports blocking access to network element systems from upstream OSS systems.

Blocking of OSS access is chosen when the network element system is added to AMS or is

edited from the system window.

Blocking alarm reporting from systems

AMS supports blocking alarm reporting from network element systems to the AMS user

interface and upstream OSS interfaces. Blocking of alarm reporting is chosen when the

system is added to AMS or is edited from the system window.

Acknowledge alarms per user

AMS users can acknowledge incoming alarms. The AMS Current Alarm view is modified

to allow alarms to be acknowledged. Acknowledging each alarm marks the alarm record

with the operator ID by default and changes the alarm color to denote that the alarm is

under investigation. Alarms can be assigned to different operators.

Assigning scheduled jobs to network elements through a flat file

By using the enrollSchedule script a user can assign scheduled jobs (discovery, backup,

or download) to network elements from a flat file called asamSchedule.csv and

instructions are in enrollSchedule.README.



GR-303 P-phone support

(Litespan systems only) AMS supports GR-303 provisioning in support of P-phone on

EBSI equipment units, as well as support of GR-303 Interface Groups (introduced in

AMS 4.2).

Litespan TR-008 copper fed support

(Litespan systems only) AMS supports discovery and alarm viewing of TR-008 Copper

Fed Litespan systems.

OC-3 and T3 facility provisioning

(Litespan systems only) AMS supports provisioning for OC-3 and T3 facilities on OC-3B

and DS3B equipment units. T3 facilities are located in Litespan-2012 systems only.

Starspan provisioning

(Litespan systems only) AMS supports provisioning for Starspan components, including

the high-density fiber bank, ONU-24, ONU-48, ONU-96, and ENU-96.

SONET transport provisioning

(Litespan systems only) AMS supports provisioning for SONET facilities associated with

OTU/ORU, ABCU, OC-3B, OC-3H, and OC12H equipment units.

AMS-Litespan communications

(Litespan systems only) AMS supports connections to Litespan systems over X.25 data

communications networks (DCN) via a CIU-equipped Litespan system, TCP/IP via an

EIU-equipped Litespan system, and serial links. AMS generates and logs an autonomous

warning message and displays an X superimposed on AMS component graphics if this

link is lost due to DCN failure. AMS connections to a Litespan system via an X.25 DCN or

over TCP/IP to an EIU-equipped Litespan system support software download to

Litespan systems.

Litespan SONET, DS1, and DS0 facility provisioning

(Litespan systems only) Litespan operating parameters for the following facilities can be

provisioned from the AMS GUI:

> DS0

> DS1

> STS-1

> VT 1.5



> VF services (drops)

> SONET transport

Litespan-ADSL facility provisioning

(Litespan systems only) AMS supports provisioning of ADSL line unit CAP-based

(ADLUC) and ADSL line unit DMT-based (ADLUD) facilities.

Litespan automated generic software download

(Litespan systems only) AMS maintains information about the software version

currently active on each Litespan system it is managing. AMS can distribute a new

version of Litespan system software to Litespan systems running supported releases.

Litespan system software activation

(Litespan systems only) AMS supports activation of Litespan system software loads on a

system basis. Consult P-007 in the Litespan Software Upgrade document for Litespan

system software activation procedures (included in the Litespan GRD).

AMS-ASAM communications

(ASAM systems only) AMS supports connections to ASAM systems via UDP/IP over an

ATM network, in-band ATM, and end-to-end ATM.

ASAM automated generic software download

(ASAM systems only) AMS maintains information about the software version currently

active on each ASAM system it is managing. AMS can distribute a new version of ASAM

system software to ASAM systems running supported releases.

ASAM system software activation

(ASAM systems only) AMS supports activation of ASAM system software loads at the

equipment unit level only.

ASAM ADSL, DS3, VPL, and VCL facility provisioning

(ASAM systems only) ASAM operating parameters for ADSL, DS3-rate services, VPL,

and VCL entities can be provisioned from the AMS GUI.

IMA group support

(ASAM systems only) AMS supports the grouping of ASAM T1 facilities on an equipment

unit basis. T1 facilities that are associated with a D1LT equipment unit can be grouped,

and then the group can be provisioned with one set of parameters.



ASAM node and equipment unit resetting support

(ASAM systems only) AMS supports soft resetting on an equipment unit and node basis.

Reserving and freeing ports

(ASAM systems only) AMS supports reserving and freeing ports on ASAM ADSL and

ASAM T1 facilities.

Viewing and provisioning the next available port

(ASAM systems only) AMS supports viewing and provisioning the next available port on

an ASAM node.

ASAM ATM and ADSL line profile support

(ASAM systems only) AMS supports creating and deleting ATM CAC profiles, ATM

traffic descriptor profiles, ATM access profiles, and ADSL line profiles. Profiles can then

be linked and associated with ASAM facilities.

ASAM SVC profile support

(ASAM systems only) AMS supports creating and deleting SVC DSS2, SVC SAAL, SVC

line identification, and SVC performance threshold profiles. Profiles can then be linked

and associated with ASAM facilities.

Switched Virtual Channel (SVC) support

(ASAM systems only) AMS supports the creation and deletion of SVC ports, SVC

channels, and SVC profiles.

ASAM high-speed discovery

AMS supports a fast discovery that allows you to discover systems more quickly (for

those ASAM releases that do support fast audit discovery). AMS sends a high-speed

discovery command to ASAM, where one file containing all information is prepared and

sent on.

ASAM profile template

AMS provides the capability to create an ASAM ATM profile template, ASAM ATM SVC/

PVC profile template, and ASAM ADSL line profile template. It also provides the ability

to manage and activate these templates.



2.3 Fault management features

AMS supports the fault management features described in the paragraphs below.

Time synchronization

AMS supports time synchronization between the AMS server and network element

systems.

Alarm surveillance

All alarm and event information sent by network element systems is captured and

displayed at the AMS user interface. The affected unit's operating and provisioning

characteristics can also be displayed. When an alarm is cleared, the original alarm item is

removed from the event viewer window.

Network alarm/event history

All alarm and event information is stored in an event log. When configured properly, the

AMS system stores alarms for at least 30 days of continuous operation.

Upstream TL1 interface

AMS supports an upstream operation support system (OSS) that provides autonomous

alarm notification and reporting of alarms from AMS, network element systems to

upstream network management systems. The AMS administrator can assign a separate

list of users and passwords for the OSS interface.

AMS also supports assigning TL1 commands and TL1 autonomous messages to

individual OSS user accounts to facilitate communication from an OSS to network

elements.

The use of the OSS interface requires a license from Alcatel.

System alarm query

All logged alarms can be queried with user-configurable criteria. For example, AMS can

produce a list of all alarms associated with a specific equipment unit or facility.

Litespan alarm history

AMS supports retrieval of historical alarms from the Litespan system or node. Users can

enter specific Litespan component criteria, choose alarm severity, and specify transition

parameters prior to initiating a query.



2.4 Performance management features

AMS supports the performance management features described in the paragraphs below.

FTTU performance-monitoring history

AMS supports performance monitoring for Passive Optical Network (PON) facilities.

Data collected is stored in performance-monitoring logs. Reports can be generated from

the log files with specific parameters selected. In addition, reports can be viewed in chart

or table format, deleted, saved to a file, or sent to a printer.

Litespan performance-monitoring history

AMS supports creating and canceling performance-monitoring schedules for selected

Litespan facilities. Data collected is stored in performance-monitoring logs. Reports can

be generated from the log files with specific parameters selected. In addition, reports can

be viewed in chart or table format, deleted, saved to a file, or sent to a printer.

ASAM performance-monitoring history

AMS supports performance monitoring for ASAM ADSL DMT facilities, T1 facilities

(assigned type D1LT or IMA group), ASAM T3 facilities (assigned type D3NT), and OC-3

facilities. Data collected is stored in performance-monitoring logs. Reports can be

generated from the log files with specific parameters selected. In addition, reports can be

viewed in chart or table format, deleted, saved to a file, or sent to a printer.

Performance-monitoring end dates

AMS supports editing the end date and time for monitored facilities.

2.5 Security management features

AMS supports the security management features described in the paragraphs below.

AMS user security

AMS makes use of UNIX security mechanisms to provide secure user access to AMS and

to the associated network elements.

Basic system access security

The network element embedded security mechanism controls access to those systems by

an AMS system. Each managed network element must have a user ID and password that

must be entered before AMS can establish a connection.



2.6 Supported configurations

AMS supports the configurations described in the paragraphs below.

7340 FTTU (Fiber To The User)

AMS supports surveillance, provisioning, and management of 7340 FTTU systems with

feature groups FGU 1.1.0, FGU 1.1.1, FGU 2.0.0, FGU 2.1.x, FGU 2.5.x, FGU 2.6.0,

FGU 2.6.1, FGU 2.6.2, and FGU 2.6.3.

7330 ISAM FTTN (Fiber To The Node)

AMS Classic supports surveillance, provisioning, and management of 7330 ISAM FTTN

systems with feature groups FGN 1.0.0, FGN 1.1.0, FGN 2.0.0, FGN 2.1.x, FGN 3.0.x,

FGN 3.1.x, FGN 3.2.0, FGN 3.4, and FGN 3.5. (Note that FGN 3.5 was not at DR4 at the

time of AMS 6.4.0 release).

General Bandwidth G6

AMS supports surveillance, provisioning, and management of General Bandwidth G6

systems with software release v7.1.x, v9.1.x, v10.1.x and v10.2.x. Earlier G6 releases do

not have database change and are supported in AMS release 5.1.0 for software upgrade

only. No other function is offered.

Litespan

AMS supports surveillance, provisioning, and management all configurations of

Litespan-2000 and Litespan-2012 systems that are running compatible Litespan system

software. AMS supports provisioning of ADSL common equipment, ADSL digital line

units (ADLUs), and ADSL chain configuration (Litespan system software release 9.2 and

later only).

Starspan

AMS supports Litespan systems configured as Starspan® host digital terminals (HDT)

using Starspan, ENU-96, ONU-24, ONU-48, or ONU-96 distribution units.

ASAM (ATM Subscriber Access Multiplexer)

AMS supports surveillance, provisioning, and management of 1000 ASAM, 7300 ASAM,

and 7301 ASAM systems. AMS supports adding and provisioning RAM, mini-RAM,

high-density ASAM systems, low profile-high density, low profile-ultra density, and

high-density splitterless ASAM shelves.



Hybrid Network Termination (HYNT)

AMS Classic supports surveillance, provisioning, and management of 7302 HYNT

systems. Please refer to section 4.3, NE compatibility, for supported versions.

3 Summary 3.1 Release capabilities

Refer to the 5526 AMS Release Description (3EM21056ACAA) for information on the

release capabilities for AMS-C Release 6.4.0.

4 Details 4.1 Documentation delivery

Documentation for this release is available through electronic distribution and CD-ROM.

Refer to the table below for a list of available documentation for the 5526 AMS, Release

6.4.0.

Table 1: AMS 6.4.0 Documentation ordering information

Product Alcatel-Lucent part number

Customer Release Notice (CRN) 3EM 16129 DGAA

CRN CD-ROM 3EM 21773 AGAA

Documentation CD-ROM 3EM 15899 AQAA

5526 AMS Installation Guide 3EM 15897 AQAA

5526 AMS User Guide 3EM 15896 ARAA

5526 AMS Administrator Guide 3EM 19467 AGAA

5526 AMS Planning Guide 3EM 15185 ARAA

5526 AMS OSS TL1 Developer Guide 3EM 19480 AGAA

5526 AMS Release Content Description 3EM 21056 ACAA

7330 ISAM FTTN FGN 3.5 Operations and Maintenance Using AMS 3HH 05777 AAAA

7330 ISAM FTTN FGN 3.5 Operations and Maintenance Using CLI 3HH 05218 AAAA

7330 ISAM FTTN FGN 3.5 TL1 Commands and Messages 3HH 05220 AAAA

7330 ISAM FTTN FGN 3.5 CLI Commands 3HH 04416 CEAA

7330 ISAM FTTN FGN 3.5 Customer Release Notes 3HH 03364 CAAA

7302 ISAM HYNT FGN 3.2 Operations and Maintenance Guide 3HH 04098 AAAA

Litespan R13.1 Operations and Maintenance 3EM 16173 AGAA

Litespan R13.1.1 Standard Practices 3EM 13866 ACAA

Litespan R13.1.1 Customer Release Notes 3EM 19009 ABAA

7300 ASAM FG11.4 Operations and Maintenance 3FE 29265 AAAA

7300 ASAM FG11.4 Commands and Messages 3FE 29264 AAAA

7300 ASAM FG11.4 Customer Release Notes 3FE 24338 ALAA




7340 ISAM FTTU 2.6.2 Operations and Maintenance 3EM 15476 AHAA

7340 ISAM FTTU 2.6.2 TL1 Commands and Messages 3FE 50864 AAAA

7340 ISAM FTTU 2.6.2 Customer Release Notes 3FE 50484 ANAA

5526 AMS RST 3.1.1 User Guide 3EM 14897 ANAA

Jcraft for AMS 3EM 12135 AAAA

4.2 Software delivery

Software for this release is available through electronic distribution and CD-ROM. Refer

to the table below for a list of available Software Delivery Kit (SDK) items for the 5526

AMS, Release 6.4.0.

Table 2: AMS 6.4.0 Software ordering information


AMS SDK, AMS-C 6.4.0 MP SERVER 3EM22142AAAA

AMS SDK, AMS-C 6.4.0 MP SERVER UPGRADE 3EM22143AAAA

AMS SDK, AMS-C 6.4.0 SP SERVER 3EM22144AAAA

AMS SDK, AMS-C 6.4.0 SP SERVER UPGRADE 3EM22145AAAA

AMS SDK, AMS-C 6.4.0 MID-SIZE SERVER 3EM22146AAAA

AMS SDK, AMS-C 6.4.0 MID-SIZE SERVER UPGRADE 3EM22147AAAA

AMS SDK, AMS-C 6.4.0 SMALL SYSTEM STARTER PKG 3EM22148AAAA

AMS SDK, AMS-C 6.4.0, ELECTRONIC DIST 3EM22149AAAA

4.3 Software compatibility

Backward compatibility

Only AMS-C 6.3.0, with or without patches or service packs, can be upgraded directly to

AMS-C 6.4.0. For AMS releases lower than AMS 6.3.0, you need to go through an

intermediate release to avoid data loss.

NE compatibility

The 5526 AMS Release 6.4.0 is compatible with the NEs listed in the following table,

assuming an appropriate NE Management Module is installed:

Table 3: AMS 6.4.0/NE compatibility

Network element/Release

7340 FTTU Feature Group 1.1.0


7340 FTTU Feature Group 2.1.x









7330 FTTN Feature Group 1.0.0



7330 FTTN Feature Group 2.1.x

7330 FTTN Feature Group 3.0.x

7330 FTTN Feature Group 3.1.x (lab evaluation only)


7330 FTTN Feature Group 3.4

7330 FTTN Feature Group 3.5* General Bandwidth G6 V7.1.x

General Bandwidth G6 V9.1.x



7302 Hybrid NT Release 3.1.x (lab evaluation only)

7302 Hybrid NT Release 3.2.0 (lab evaluation only)

ASAM Feature Group 6.1.x












ASAM 7301 Feature Group 1.0.x

ASAM 7301 Feature Group 2.0.x

Litespan Release 10.1 (10.01.xx)







Statistics Collector Release 1.0 SP1




Statistics Collector Release 1.2

LANX -D V2.0.1.5

* This load was not at DR4 at the time of AMS 6.4.0 release.

Server and client compatibility

See the 5526 AMS Planning Guide, 3EM-15185-ARAA-AAZZA, for information on server

compatibility.

4.4 Software installation

5526 AMS-C Release 6.4.0 supports migration from AMS-C Release 6.3.0.

See the 5526 Access Management System | Release 6.4.0 Installation Guide (Classic),

3EM-15897-AQAA, for details about installing AMS-C 6.4.0.

4.5 SUN software and hardware notes

See the 5526 AMS Planning Guide, 3EM-15185-ARAA-AAZZA, for information on Sun

hardware and software requirements.

5 Release content 5.1 Implemented features

The 5526 Access Management System 6.4.0 includes the features described in

section 3.1 – Release capabilities.

5.2 Application notes

These notes provide information for system users and maintenance personnel

responsible for maintaining and implementing AMS release 6.4.0. The information

contained in this section must be clearly understood if one is to avoid any unexpected

results. AMS should be upgraded before the Network Elements are upgraded to maintain

continued communication.

Upgrade from previous version

> AMS Classic 6.4.0 supports a direct upgrade from AMS 6.3.0 with or without patches

and service packs.

> For other AMS releases not aforementioned, you need to go through an intermediate

release to avoid data loss. Alcatel-Lucent recommends all upgrades to AMS Release

6.4.0 be conducted under the direction of trained Alcatel-Lucent support personnel.



Please contact your Alcatel-Lucent Sales Support Representative to enquire about

technical support for AMS upgrades.

> The AMS license server application requires that a valid license file be present on the

AMS server prior to installation of AMS software. Please refer to section 5.2 and

contact your Alcatel-Lucent Sales Support representative to obtain a license file for

your AMS installation prior to upgrade.

AMS system notes

1. For installation procedures, see the 5526 AMS Installation Guide.

2. To acquire your license file, send an e-mail to [email protected]. You

must provide the following information:

> Host ID

> Host name

> Number of GUIs

> Number of TL1 upstream links

> Number of Event Viewers

> Redundancy (0) disabled (1) enabled

> Number of FTTUs

> Number of FTTNs

> Number of GPON FTTPs

> Number of HYNTs

> Number of General Bandwidth G6s

> Number of Litespans

> Number of ASAMs

> Number of XDSL ports

> Number of Generic DSLAMs

> Number of Generic DLCs

> Expiration date

3. After the installation of AMS, it is not possible to change the hostname (re-installation

is required).

4. See the 5526 AMS Planning Guide for specific hardware and software requirements as

well as platform and patch information.

5. AMS connects to FTTUs, FTTNs, FTTPs, HYNTs, ASAMs, Litespans, and G6s over a

network. The “serial” connection option is provided only for installation and testing of

the AMS software and for troubleshooting purposes in a laboratory environment.



6. Remote software download over an X.25 network requires support of the Call User

Data field in X.25 call packets. If non-conformant X.25 connections are used, the

remote software download protocol does not function correctly. If a TCP/IP

connection from the AMS to an X.25 device is used, AMS issues an error message and

remote software distribution is not to be allowed. Remote software download may

now also be performed over an all-TCP/IP connection.

7. The AMS OSS interface feature is used where AMS and another fault management

application are used for surveillance of network elements. If AMS and another

element management or OS system are both connected directly to a managed network

element, autonomous alarm notifications may not be received by AMS. Autonomous

alarm notification can be disabled in AMS release 3.2.1 and later. Alternatively, if AMS

receives autonomous notifications, another directly connected surveillance system

may not receive them.

8. In TL1 cut-through windows, “local echo” should be enabled or disabled based on data

communications network behaviour. Local echo is controlled from the cut- through

window menu bar. If duplicate characters are displayed, turn local echo off. If no

characters or prompts (<) are displayed, turn local echo on.

9. Exit AMS client (GUI) sessions prior to manual administration (change) of the date

and time displayed by the AMS server OSS (whether performed from UNIX or CDE).

Clients may be restarted after the time change has been administered.

10. Do not manually change the date and time displayed by the AMS server OSS while a

scheduled operation is in progress.

11. Do not attempt to restore an AMS database from backup within 30 minutes after

manual administration (change) of the date and time displayed by the AMS server

OSS.

12. AMS software may be run in conjunction with other licensed software including SUN’s

Solstice X.25. If multiple license servers are used within the AMS computing

environment, these may interact with the AMS license server application. AMS uses

Macrovision FLEXlm for license management; FLEXlm is supplied as part of the AMS

software installation media. Consult your UNIX system administrator prior to AMS

installation with any concerns over license management in the target environment.

13. Performance monitoring log data can be printed to a file (saved), but cannot be output

to a printer from the AMS GUI.

14. Performance monitoring data collection stops if the “until” time for any performance

monitoring collection task occurs while the AMS TL1 proxy is not running.

Performance monitoring data is not available for the affected interval.

15. When an NE is “locked” from the AMS GUI, alarms are not sent to an upstream OS.



16. After upgrading the AMS from a previous release, the migrated OSS users do not have

permission to run the new provisioning commands. The AMS Administrator must add

the new commands to the profile of each OSS user. An alternative, easier way is to

delete and re-enroll the OSS users.

17. Litespan 10.2 and above has four autonomous alarm (AA) channels and one

autonomous message channel. The first AMS user to log in receives the AM channel.

Subsequent AMS systems users logging in do not receive AM messages (e.g. database

change notification).

18. At AMS startup, ALMAP servers are set to DISABLED by default. The variable in the

public.env AMS_ALMAP_MODE allows operators to enable or disable ALMAP. This

prevents unnecessary delays during AMS startup for operators not using ALMAP.

19. AMS is compatible with Citrix Metaframe Presentation server 4.0 for UNIX.

20. AMS is compatible with Citrix Presentation Server Clients - Version 10.0 with

1280 x 1024 pixels as resolution on the desktop. There may be limitations using AMS

with other resolutions. Hence, it is recommended that the customer use Citrix with

the prescribed resolution.

21. AMS-C 6.4 works with LRM (Large Scale Release Manager) tool to perform 7330

network upgrades. Refer to the 5529 LRM 1.1.0 User Guide (3EM 21990 ABAA) to

determine supported LRM compatible version.

SUN software notes

The required OS level is Solaris 2.10 (update version 01/06). To acquire the operating

system:

1. Go to the Sun page:

http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=8&PartDetailId=Sol1

0-U1-SP-G-F&TransactionId=try

You need to have an account with Sun Microsystems to continue. Creating an account

and downloading Solaris 10 is free of charge.

Note: Web contents may change in time. If the above web page is not available for

you at the time of reading this document, please contact your Alcatel-Lucent Sales

representative for guidelines on how to get the Solaris 2.10 - update version 01/06.

2. Follow the instructions on the Sun website to download Solaris 10 (update version

01/06).

Make sure you install all the Solaris 10 CDs or DVDs.



SUN hardware notes

1. Alcatel-Lucent recommends AMS be installed only on supported hardware platforms

as identified in the 5526 AMS Planning Guide. Operation on other platforms cannot

be guaranteed.

2. Please refer to the 5526 AMS Planning Guide to verify that minimum memory

requirements, disk space, and partitioning requirements are met.

3. Please refer to the 5526 AMS Planning Guide for more detailed information about the

capacity limitation of each type of client and server machine supported by AMS.

4. For information about ATM Network Interface Card (NIC) setup, please see the 5526

AMS Installation Guide.

7340 FTTU system notes

1. Each 7340 FTTU managed by a single AMS server must have a unique System ID

(SID).

2. AMS may not recognize alarm or equipment states for a 7340 FTTU node with illegal

characters in the System ID (SID).

3. Do not add a 7340 FTTU system to an AMS managed domain unless you have

acquired sufficient Node RTU licenses to account for all nodes in the system. For

instructions on how to evaluate AMS license capacity, refer to the 5526 AMS

Installation Guide.

4. An unequipped NTB card may display a software version in AMS GUI; this software

version may be ignored.

5. If a “version error” message is received while adding a new 7340 FTTU system, the

new FTTU version must be added by running the set7340Version utility.

6. The creation of a Profile Template name is case sensitive.

7. 7340 FTTU property files are independent in the AMS server and the AMS client. To

synchronize them, run the /opt/ALAams/bin/asamip.sh script. Run the script on the

server first and then on the client.

8. There are now two variants of 2GONTs: one supports 4 POTS and the other 2 POTS.

With AMS, four telephone number fields are displayed for both variants of the

2GONT.

9. When planning an ONT, AMS does not differentiate between the various third-party

vendors, only the type of ONT. The choices are Alcatel-Lucent HONT, Carrier Access

BONT, and MDU (to be supported in a future release).



10. Structural DS1 provisioning using AMS fails with ONTCES creation failure. The

problem is the sequence of operations used by AMS: The AMS service template

creates the LTVCL after the ONTCESVCLAs. As a workaround, please use TL1 and

ensure that the LTVCL is created first followed by the ONTCESVCL.

7330 ISAM FTTN system notes

There are no 7330 ISAM FTTN system notes for this release.

7302 HYNT system notes

Further HYNT improvements have been made in this release; however, 7302 HYNT is

still supported at DR3P quality by AMS. Moreover, the 7302 HYNT Operations and

Maintenance Guide documentation is at DR3P quality.

Litespan system notes

1. RST cannot be used to upgrade a Litespan system in AMS-C 6.4.0. This support will

be forthcoming in AMS-C 6.4.1. If you attempt to launch RST, this operation will not

perform any action.

2. Refer to the Litespan software Customer Release Notes provided with the Litespan

system software for a description of compatible hardware units. Only units listed as

“Supported” by a managed Litespan’s current generic version are supported by AMS.

3. Each Litespan node managed by an AMS server must have a unique System ID (SID).

4. AMS may not recognize alarm or equipment states for a Litespan node with illegal

characters in the System ID (SID). Legal characters are listed in Litespan TL1

documentation.

5. If a Litespan equipment unit is deleted (edited to “unassigned”) while it is installed in

the NE, Litespan automatically creates a default assignment (equipment SST = ADA).

Units displaying ADA in SST fields may be reassigned. This behaviour is fully

explained in the Litespan TL1 Reference Practice, OSP 363-205-502.

6. AMS reports ADSL remote unit equipment in accordance with Litespan TL1 response.

The ATU-R equipped type for CAP is reported as “ADLUC” because the information is

returned by proxy.

7. AMS no longer displays a CLEI code for the Westell ATU-R.

8. Discovery of a dual feeder Litespan system fails if the Litespan has the East node

connected to the West optics, and the West node connected to the East optics.

9. If the bulk provisioning data file is exported from Microsoft Excel, a text editor must

be used to remove the CTRL-M character at the end of each line.



10. At the time of writing this document, there is a known issue with Litespan Database

Notification that causes AMS not to get updated for the secondary service state of

datalink in Copper Fed Litespan systems (BTS 28566).

11. In Litespan Release 13.1 and 13.1.1, the MSC card is only supported on the COT.

7300 ASAM system notes

1. In case of loss of ASAM backup, the user can download the ASAM database either

directly from AMS database (ASAM System View → Actions menu → Download

Configuration → From AMS Database to NE), or by applying a previously downloaded

information to a text file (ASAM System View → Actions menu → Download

Configuration → From AMS Database to File) through TL1 cut through.

2. The Enhanced Representation of Environmental Alarms feature allows users to assign

a meaningful text to incoming alarms (e.g. "MISCALM1" to "Battery alarm"). Please

note that the selected string is shown in the GUI only and it does not affect TL1 cut-

through or TL1 upstream interface.

3. The view for Interim Local Management Interface (ILMI) in ASAM systems is not

event driven and deletion of the ILMI channel does not automatically close the view.

4. If the ADSL Line Profile view in the Profile Manager is opened, any profile that is

shown as ‘notInService’ is not updated to ‘active’ if it is activated using TL1. The

Profile Manager must be closed and re-opened to reflect the new state.

5. The following limitation exists in the flexible shelf placement feature. The AMS rack

view does not reserve a location for empty shelves. Due to this, shelves may appear to

be located in an inconsistent location (since they occupy the location of where an

empty shelf would have been).

6. AMS supports all three options of Access Control List (allow, deny, and drop).

However, ASAM FG 10.1 accepts the “allow” value only. The two other options will be

supported in later ASAM releases. Applying new values fails if user tries to include

“deny” or “drop” options in the list.

7. Programmable Alarm Filters are not logged in alm.log when Report Mode status is

modified. When ‘Alarm Report Mode’ attribute of PAF is modified from Enabled to

Disabled, the clearing of PAF Alarm is not be logged in the alm.log. And when it is

changed from Disabled to Enabled, the generation of PAF Alarm is not being logged in

the alm.log. Alarm Log Mode is an ASAM notion and does not have any influence in

the logging of alarms in alm.log.



8. The environment variable AMS_ASAM_OPST_REFRESH_TIME defines the time

period used by the GUI to automatically update the operational state of ASAM ports,

links, and cross-connections. The default value is 0 (no automatic update). All user

defined values should be ≥ 30. By modifying this environment variable to a number

greater or equal to 30 automatic updates of operational state occurs.

9. Starting in AMS 4.3.5, SNTP state is removed from ASAM node view.

10. For 7301 ASAM, from the Provision Equipment menu in Shelf View, only assigning

the card and unseating the card are possible. “Activate Software” and “Assign &

Activate Software” are disabled.

11. Discovery of a heavily loaded ASAM 7301 through classic discovery method can take

up to 5 hours.

12. Each ASAM managed by a single AMS server must have a unique System ID (SID).

13. AMS may not recognize alarm or equipment states for an ASAM node with illegal

characters in the System ID (SID).

14. Do not add an ASAM system to an AMS-managed domain unless you have acquired

sufficient Node RTU licenses to account for all nodes in the system. For instructions

on how to evaluate AMS license capacity, refer to the 5526 AMS Installation Guide.

15. Starting in ASAM FG6.2, the time reference has changed. AMS prompts the user with

the method to use for time synchronization. Depending on the ASAM release, it is

recommended to use the SNTP service or the AMS proprietary time synchronization.

If the warning is ignored and the wrong selection is made, the time is off by 70 years.

16. An unequipped NTB card may indicate a software version in AMS GUI; this software

version may be ignored.

17. If a “version error” message is received while adding a new ASAM system, the new

ASAM version must be added by running the setAsamVersion utility.

18. Occasionally, ASAM systems delay in sending the changeOccuredTrap, with removal

of LT cards that have been equipped, but unassigned. The wait is approximately 4

minutes in duration.

19. ASAM FG6.2 and later should not use AMS for time synchronization (it should be

SNTP) although the feature is available to the operator in case time synchronization is

required.

20. The creation of a profile template name is case sensitive.

21. ASAM property files are independent in the AMS server and the AMS client. To

synchronize them, run the /opt/ALAams/bin/asamip.sh script. Run the script on the

server first and then on the client.



22. To open multiple sessions of Jcraft from a single Exceed (7.0) instance, a patch is

required from Hummingbird. To obtain this patch, please contact Hummingbird and

ask for exceed.exe patch, version 7.0.0.10. Contact information for North America is

800-486-0095. Contact information worldwide is 1-416-496-2200. The e-mail

address is [email protected].

23. AMS does not support configuring the SERV (GELT, THSA and IPGW) cards using

the ASAM Configuration Template.

24. Verify that ASAMs on the same subnet do not have duplicate hardware addresses. The

DHCP daemon experiences problems in this scenario. Duplicate hardware addresses

are allowed when ASAMs are on different subnets.

25. Bonding is not available for ports 3 and 4 or 9 and 10 on the ABLT-A/B due to

restrictions in the chipset.

GB G6 system notes

1. Because the Call Trace data is transient data that has value for a short time only, there

is a limit in the GUI of 5000 records for the Call Trace data.

2. The logged Events Query is also limited to 5000 events.

3. AMS supports the value range of 1 to 127 for the APS wait to restore attribute (WTR).

To set values above 127, use CLI.

4. When pre-configuring or planning an ANM-MM card, the assigned type displayed is

ANM – not ANM-MM. This is seen only when the slot is not equipped. Trying to

assign the ANM-MM card when it is equipped with the ANM-MM card, the responses

are correct.

5. Beginning with G6 v9.1, GENBAND has removed support for TPM-1 cards. TPM-1

cards need to be removed and replaced with TPM-2 cards for the upgrade from v7.1.1

to v9.1 to be successful.

6. AMS Release 6.4.0 has been tested with G6 Release 9.1.2 and 10.1.4.

SHUB system notes

1. Before connecting to the SHUB, the user must configure the access control list and the

community string. Refer to the 5526 AMS User Guide for details on these

configuration procedures.

2. The SHUB/SHUB ASAM ports are 1-18. They have a default PVID (default VLAN in

AMS terminology) of 1; this value is not meant to be changed and this is prevented

from the CLI. However, AMS VLAN Manager does not perform validation and allows

the default to be changed.



X-terminal applications

1. Certain X-terminal displays do not reflect card names in graphical displays of

equipment units due to font scaling problems. X-terminals deployed with the AMS

must be compatible with Sun X Display Manager Control Protocol release 5. X-

terminals not complying with this standard may exhibit non-standard behaviour. For

details on X Display Manager compatibility, contact Sun Microsystems.

For optimal performance, X-terminals should be equipped with random access

memory (RAM) equivalent to that required for an AMS client workstation. Less

memory may result in increased virtual memory (disk-swap) usage and a consequent

reduction in performance.

5.3 Restrictions

RST cannot be used to upgrade a Litespan system in AMS-C 6.4.0. This support will be

forthcoming in AMS-C 6.4.1.

5.4 New and/or changed configuration parameters

The 5526 Access Management System Release 6.4.0 has no changed configuration

parameters.

5.5 New and/or changed environment variables

1. AMS_7340_SHUB_LINK_OP_STATE_REFRESH_TIME, default value 30 seconds,

valid for server and client.

Description: If Auto Refresh for Oper State of 7340 SHUB Port is enabled, the Oper

State will be retrieved by AMS at regular intervals defined by this environment. The

default value here is 30, and the refresh for this attribute will happen every 30

seconds.

2. AMS_7330_SHUB_LINK_OP_STATE_REFRESH_TIME, default value 30 seconds,

valid for server and client.

Description: If Auto Refresh for Oper State of 7330 SHUB Port is enabled, the Oper

State will be retrieved by AMS on regular intervals defined by this environment. The

default value here is 30, and the refresh for this attribute will happen every 30

seconds.

3. AMS_G6_PM_COLLECTION, default value disabled, valid for server only.

Description: This environment variable enables the G6 PM collection when set to

enabled.



4. TCLLIBPATH, default value is /opt/ALAams/otherdata/pups/scriptslib, valid for

server – client.

Description: This environment variable describes the path of the TCL script library

used by the Litespan post upgrade provisioning scripts.

5.6 Closed issues

The issues listed in the tables below have been closed for AMS 6.4.0.

Major closed issues

Table 4: Major closed issues

Issue # Platform

Affected

Description

56845-1 G6 Large G6 SID names cause G6 backups to fail.

57084-1 ISAM GUI crashes when looking at remote unit list.

57310-1 Platform purgeMib won't run. The database has millions of deleted objects left in it.

57605-1 ISAM FTTN-DB change is not happening for VLAN Port association/deassociation and modification.

58566-1 ASAM Download Configuration from AMS Database to NE on ASAM 1000's fails

58580-1 ISAM GUI crashes while creating VLAN port in FG3.0.10/11 NE.

58623-1 Platform purgeMib hung. Can't bring up any GUIs due to conflicting client.

59064-1 Platform verifyDb reporting pointer errors.

60866-1 7340 SSC-AMS interface for policy push is not changing PCR value for 7340.

Minor closed issues

Table 5: Minor closed issues

Issue # Platform

Affected

Description

51163-1

51163-2

51163-3

ASAM The AMS.log default message needs to be changed due to Multi DSL conversion script reporting errors for non-provisioned ports on a card.

54417-1 ASAM Need dbase restore failure error message changed.

54913-1 ASAM Download configuration from AMS to NE fails on ADSL 7300 profiles.

55362-1 BPON LT slot view should provide port names.

55839-1 BPON 7340 FTTU ONT and 7340 FTTU ONT (FG>=2.5) query types should be merged.

56009-1 BPON TL1 cut-through syntax is wrong for several 7340 commands.

56107-1 PLATFORM alarm_report.sh no longer works in 6.x.

56289-1 ISAM Option to edit IGMP channel should be removed.



Issue # Platform

Affected

Description

56290-1 PLATFORM cliAddSystem script does not correctly set Time Sync.

56301-1 PLATFORM Event viewer does not sort received time correctly if showing multiple years.

56344-1 PLATFORM AMS installs/uses Acrobat Reader 4 to view documentation.

56474-1 BPON AMS does not sort VC cross connects in numerical order when ONT AID is selected.

56505-1 PLATFORM Font color should be changed in user activity report.

56526-1 ISAM Problems with AID on DUPMACADRS alarm.

56785-1 PLATFORM Importing OSS users fails when using the GUI if the CSV file contains a "#" character.

56797-1 ISAM SHub Port Manager shows all Oper State entries as Not Available after discovery.

56809-1 PLATFORM ams.log shows entries that identify a 7340 as a 7330.

56813-1 ISAM Customer requesting refresh option wording be changed for SHub Port Manager.

56918-1 ISAM For FTTN FGN 3.0.11, and FGN 3.4, the XDSL Carrier Load opened from remote view on port for VDSL2 does not show the complete data for upstream and downstream when the NE has huge data. The AMS displays only 10% of the data that the NE has.

56949-1 PLATFORM alarm_overview.sh does not work for 7330 and 7340.

57235-1 ASAM Alarm Template view closes while trying to apply or de-associate a template.

57322-1 PLATFORM Clicking on Exit should not close any window until "Yes" is selected.

57351-1 BPON Getting backup alarms for NE that is locked.

57511-1 ISAM OSS does not report autonomous messages properly for some alarms.

57683-1 ISAM FTTN- ATM Virtual Link manipulate options are not enabled on VDSL ports.

58577-1 PLATFORM DBChanges from LRM are not handled properly in AMS GUI for two states.

58658-1 PLATFORM Need changes to Itemized Activity view.

58878-1 ISAM Customer wants to add FG.3.11 option when performing a set7330Version.

58881-1 ISAM FTTN Operational Mode Query does not display any results.

58883-1 PLATFORM Add Predefined query in user activity report without bin or scheduled activities.

58885-1 PLATFORM Update NE Version Config from client gives an error even though it works.

58888-1 ISAM Retrieve QoS Statistics on 7330 creates an SNMP mapping error.

58890-1 PLATFORM Trimlogs should clean up logs on standby server.

58892-1 ISAM When performing a set*Version, the new entries do not line up with default ones.

58894-1 PLATFORM Warning dialog is not raised if system is added through cliaddsystem.

58895-1 G6 G6 CLI should be an xterm of ddterm window to allow cut and paste and tab features.

58896-1 PLATFORM Core file on ./S99ams start and remove message /var/tmp/AMSC- on standby.

58898-1 PLATFORM GR303 EOC/TMC alarms are not mapped to an object in the event viewer.

58899-1 BPON The link between the G6 and 7340 in PSTN tab changes color.

58900-1 PLATFORM Customer wants "share -F nfs /opt/" from /etc/dfs/dfstab on AMS installations.

58901-1 PLATFORM System Licenses and Server Capacity view is not correct for Sun-Fire V880s.



Issue # Platform

Affected

Description

58902-1 PLATFORM Everything in AMS Administration under "Users" does not go to the correct parent.

58905-1 ISAM Second column is too narrow in 7330 FTTN Env. Alarm Names view.

58906-1 BPON AMS allows user to successfully deactivate service multiple times without a dialog.

58908-1 BPON 7340 FTTU End to End Data Paths View - GigE Port Description rename.

58909-1 PLATFORM Query Results view should have both options under action removed.

58912-1 PLATFORM User should only be able to run amsUserUtility on the active server.

58913-1 PLATFORM Core file generated while selecting the tree in main launcher bar.

58916-1 BPON Remove Open Parent Node option under ONT view.

58917-1 G6 Find CPE does not work when copied and pasted from a terminal window.

58920-1 BPON Customers wants PONVLANPORT total count of GigE Applique.

58923-1 BPON Add labels to applique and PON ports in FTTU Equipment Unit View.

58924-1 BPON Add G6-7340 Association Object type in Query.

58926-1 Platform purgeMib is not deleting all stale objects from the database.

58927-1 G6 AMS is unable to set the G6 BITs clock.

58928-1 ISAM The windows do not resize for Module Statistics in IGMP manager.

58930-1 BPON Core file created when deleting a 7340 system from client.

59040-1 ISAM 7330: would like OSWPAAxx.yyy terminology to go away and use FGNx.y.z instead.

59042-1 ISAM Would like to be able to set 7330 and SHub version from AMS client machine.

59061-1 ISAM 7330 FTTN Alarm Configuration Template - Copy feature takes 10 minutes.

59120-1 ISAM Changing the IP address of a 7330 does not invoke the Needs Discovery indication.

59121-1 ISAM 7330: core file if PMs are started and the corresponding 7330 is deleted.

59122-1 ISAM Invalid 7330 software for set7330Version causes core file.

59685-1 PLATFORM Tool tip is not proper for some attributes in H248 Tab.



5.7 Open issues

The issues listed in the table below remain unresolved for AMS 6.4.0.

Major issues with 5526 AMS Classic

Table 6: Major open issues

Issue # Platform

Affected

Description Workaround

56533-1 BPON The following alarm description mismatch exists between OSS and AMS for 7340 FTTU FG 2.6.1:

OSS: 1031 70-01-01 21:17:04 * 678 REPT ALM ATMPORT “LTATM-1-1-1-1:MN,CELLDSCUP,NSA,1-1,21-17-2:\”Upstream cell discard\”” ; AMS: 1031 70-01-01 13:17:02 * 0 REPT ALM ATMPORT “PON-1-1-1-1:MN,CELLDSCUP,NSA,1-1,13-17-2,NEND: \”Upstream cell discard\””

No impact to OSS as this problem still meets Telcordia compliance requirements.

No workaround.

57495-1

ISAM For 7330 FGN 3.4, DBchange is not happening for editing of MSTP general attributes, MSTP instance-vlan associations/dissociations, MSTP port attributes either through OSS session or TL1 session even though a trap was received and noted in SNMP.log. As a result, the GUI is not updated with these edits.

Discover the NE and the GUI is updated.

Minor issues with 5526 AMS Classic

Table 7: Minor open issues

Issue # Platform

Affected


54692-1 PLATFORM AmsAppServer pegging the CPU which was seen on the AMS 4.5.1 release. It was reported that this problem was seldom seen.

Restart the AppServer in question.

54824-1 BPON Configuration template issues:

• Rename NE Configuration Template to 7340 Conf Template.

• Consolidate the NE Configuration Template to 1 Manager like ASAM does.

• Add option to View ASAM Config Template under View Menu Item.

No workaround.



Issue # Platform

Affected


56703-1 ASAM HD Shelf View scrollbar problems. HD Shelf View, there are no scrollbars shown though needed.

No workaround.

56742-1 ASAM In ASAM Configuration Template: View a template with more than one shelf with cards causing the need for a scroll bar. If user clicks on several gadgets and no changes are made, when closing the view it asks to save the changes.

No workaround.

56841-1 ISAM There is a discrepancy in XDSL Line profile attributes between AMS and TL1.

The following FGN 3.0.11 XDSL line profiles depict attributes without any values in profile manager since they are not shown in CLI or TL1:

• Target Noise Margin Upstream

• Total Max. Aggr.Transmit Power Reduction

• Rate Adaptation Upshift Noise Margin Downstream

• Adaptation Upshift Noise Margin Upstream

• Min.Upshift Rate Adaptation Interval Downstream

• Min.Upshift Rate Adaptation Interval Upstream

• Rate Adaptation Downshift Noise Margin Downstream

• Rate Adaptation Downshift Noise Margin Downstream

• Min.Downshift Rate Adaptation Interval Downstream

• Min.Downshift Rate Adaptation Interval Upstream.

For FGN 3.0.11, the XDSL line profile window does not display Power Management mode attributes like PWRMGMTMODE,L0TIME,L2TIME and L2ATPR=3 but these attributes are displayed through TL1 and CLI.

No workaround.



Issue # Platform

Affected


56870-1 ISAM ATM VCLs present for VDSL configured ports

Configure the xDSL port by changing XDSL Line TP/TC mode to ATM Mode, and then create ATM VCLs on the port.

Change the XDSL Line TP/TC mode to PTM.

Delete all the VCLs on the port and try to view the existing VCLs. The deletion will be successful but deleted VCLs can be still viewed. In this case VCLs are not deleting properly from AMS.

Execute ‘RTRV-VCL’ through TL1 and observe that the VCLs will not be listed for ports that are configured as PTM.

When the port is ATM mode, the VCLs are deleted correctly.

No workaround.

56914-1 ISAM On FTTN FGN 3.2, the 7330 ARP Table has Launcher as parent view instead of the VLAN Manager view.

From shelf view, clicked View + VLAN Manager, and opened 7330 FTTN VLAN Manager. Clicked View + ARP Table, opened ARP Table. This view has no system name, SID on the title bar. Clicked on the green up arrow; it brought AMS GUI launcher to focus.

No workaround.



Issue # Platform

Affected


58084-1 ISAM On FTTN FGN 3.4. the Bonding group admin state is not updated properly when created through OSS. When Bonding groups are created through OSS with admin state as unlocked, the AMS does not show the admin states properly for the created bonding groups. The AMS shows admin state as locked for some bonding ports and unlocked for others. This problem is observed when bonding groups are created through OSS/TL1 but when these groups are created through AMS there is no problem.

NE->FTTN FGN3.4(L6GQAA99.266) LTs EBLT-K and EBLT-C are assigned and equipped in 1st and 3rd slots respectively.

Create XDSL bonding groups for all the ports in EBLT-K and EBLT-C through OSS using the below commands. ed-xbond:162:xbond-1-1-1-1&&-48::::XBONDPROFID=1,XBONDPROFNM=:is; ed-xbond:162:xbond-1-1-3-1&&-48::::XBONDPROFID=1,XBONDPROFNM=:is;

Observe the created bonding groups in FTTN shelf view through View->XDSL Bonding Groups

Observe the Admin state, for some ports it is locked and for some others it is unlocked.

No workaround.

58401-1 PLATFORM “Unhandled exception” message is seen on console while doing server switchover. However, there is no problem with the actual server switchover.

No workaround.

58440-1 ISAM Alarm Description and AID mismatch between OSS and AMS for 7330 FTTN FGN 3.4.

No workaround.

58458-1 ISAM On FTTN FGN >= 3.2, a wheat-colored strip is seen while opening VLAN-InterworkingPort from equipment and first column cannot be seen.

Navigate to EVLT-A equipment view Click on View -> VLAN-InterworkingPort, observe that wheat color patch is seen in vlanport id in VLAN-InterworkingPort list window.

Refresh.

58511-1 ISAM On 7330 FTTN FGN3.4, the PSS (primary service state) always not available in 7330 FTTN VC links window, even though the PSS is IS-NR in the port view.

No workaround.



Issue # Platform

Affected


58525-1 ISAM 7330 FTTN L3 Filter profile is not getting imported through import QOS profiles.

Create 7330 FTTN L3 Filter profile in system1.

In system 2 ,from view->7330 FTTN System QOS manager view.

Click Actions->import QOS profiles

Select the node types as NT, and profile as 7330 FTTN L3 Filter profile and then system and apply.

No workaround.

60631-1 DOCUMENTATION

DLP-269:Create/edit/delete a VLAN IP interface

Documentation BTS - No workaround.

60780-1 ISAM FGN 3.5

The Port Protocol Version is not being displayed in the 802.1x Configuration view of 7330. This attribute is listed in the PAE Port tab when the user chooses 802.1 configuration. The problem has been reported in FTTU also; however, FTTU supports this attribute only from feature group 2.6 and upwards. In these feature groups, this attribute will be displayed after the user performs a View-Refresh.

As mentioned in the description, select View->Refresh from the 802.1x Configuration view.

60867-1 ISAM, all FGNs

Whenever the user tries to create a Bonding group profile with a name containing spaces in it, AMS throws an invalid error message: "Scope not available in the attribute list."

The user must manually check if there are any errors in the parameters supplied for the creation of the Bonding profile as error reporting is incorrect.

60871-1

ISAM FGN 3.5

When the user creates a Bonding profile from the AMS GUI, the version number shown in the CLI is 0, which is not valid.

This attribute is not managed in AMS and is not useful for the Bonding profile. Hence, incorrect values will not impact performance.

This attribute is a read-only attribute that cannot be modified in any way.

In addition, the problem is an NE issue and DDTS ANTms61909 has been raised against ISAM FGN 3.5.

61027-1 7340 GUI crashes if SSC-AMS interface specifies invalid BW parameters.

Need to create the LAN service again using the ENT-SRVC-LAN command.



Issue # Platform

Affected


ISAM Some of the attributes related to 7330 modem operational statistics are not shown in the AMS GUI. The 7330 NE is not correctly providing requested SNMP information to the AMS. As a result, the GUI cannot be updated with the missing attributes for the following windows for xDSL Port Statistics:

7330 FTTN XDSL Port Downstream Status

7330 FTTN XDSL Port Upstream Status

7330 FTTN Remote View on Port

The missing attributes are highlighted in the example below in bold underline.

ANTms32037

<rept-opstat-xlnecom:fttn-156:xdsl-1-1-4-24; IP 0 < FTTN-156 06-10-05 17:40:39 M 0 COMPLD /* rept-opstat-xlnecom:fttn-156:xdsl-1-1-4-24 */ "XDSL-1-1-4-24:STATUSNE,\",,,,,,,RATETH\"" "XDSL-1-1-4-24:STATUSFE,\"NORMAL\"" "XDSL-1-1-4-24:LASTCHNGDATE,10-5" "XDSL-1-1-4-24:LASTCHNGTIME,10-42-55" "XDSL-1-1-4-24:ACTMODE,\"G9921POTSNOS\"" "XDSL-1-1-4-24:NECPMODEA,H'0005" "XDSL-1-1-4-24:NECPMODEA2,H'00000000" "XDSL-1-1-4-24:NECPMODEV,H'0000" "XDSL-1-1-4-24:NECMODEA2M,H'0000" "XDSL-1-1-4-24:NECMODEV2,H'0000" "XDSL-1-1-4-24:FECPMODEA,H'0005" "XDSL-1-1-4-24:FECPMODEA2,H'00000000" "XDSL-1-1-4-24:FECPMODEV,H'0000" "XDSL-1-1-4-24:FECMODEA2M,H'0000" "XDSL-1-1-4-24:FECMODEV2,H'0000"

The TL1 command (REPT-OPSTAT-XLNECOM) via the Telnet OSS window does show all of the attributes correctly.



6 Product documentation 6.1 Customer user documentation

The Support Documentation Service gives customers online access to the latest Alcatel-

Lucent customer user documentation. For a wide range of documentation, including

product manuals and documentation updates, visit:

http://www.alcatel-lucent.com/osds/ and log in.

6.2 Customer feedback

We value your feedback. Please direct questions or comments about Alcatel-Lucent

documentation to: [email protected].

7 Document release history

Release Date Reason for re-issue

AMS Classic 6.4.0 August, 2007 First issue

8 Glossary Term Definition

AM Application Module

AMP AMS Modular Platform

AMS Access Management System

ANM Access Network Module

ANSI American National Standards Institute

ASAM Advanced Services Access Manager

ATM asynchronous transfer mode

CAC connection admission control

CLI command line interface

CPE customer premises equipment

DHCP Dynamic Host Configuration Protocol

DS1 digital signal level one (1.544 Mb/s)

FCAPS TMN fault, configuration, accounting, performance, and security management

FTP File Transfer Protocol

FTTC fiber-to-the-curb

FTTH fiber-to-the-home

FTTN fiber-to-the-node

FTTP fiber-to-the-premises

FTTU fiber-to-the-user



Term Definition

GUI graphical user interface

HYNT Hybrid Network Termination card

IP Internet protocol

IWF Inter-working function

L2 layer 2 OSI reference model data link layer

L3 layer 3 OSI reference model network link

LT Line Termination

NE Network Element

NT Network Termination

OC3 optical carrier level 3 (155 Mb/s)

OSI open system interconnect

OSMINE Operations System/Modification for Integration of Network Elements

OSS operation support system

PVC permanent virtual connection

QoS quality of service

SCU system communication unit

SHUB Service Hub

SSH Secure Shell Protocol

T1 two-pair 1.544-Mb/s electrical signal

TCP Transmission Control Protocol

TL1 Telecommunications Language 1

TMN telecommunications management network

VDSL very-high-bit-rate digital subscriber line

VLAN Virtual Local Area Network(s)

VPI virtual path indicator

End of document

ams-c 6-4-0-crn-ed 01 - vox technologiesmediaserver.voxtechnologies.com/filecache/alcatel-lucent...

Documents