1354rm-Phm r7 5 SRD 8dg60488aaaafmzza

Alcatel-Lucent 1830
Photonic Service Switch (PSS)

1354 RM-PhM Photonic Manager | Release 7.5 Build 22
SOFTWARE RELEASE DESCRIPTION
Alcatel-Lucent – Proprietary
This document contains proprietary information of 8DG60488AAAA
Alcatel-Lucent and is not to be disclosed or used MARCH 2010
except in accordance with applicable agreements. ISSUE 1
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are 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.
Copyright © 2008-2010 Alcatel-Lucent. All Rights Reserved.
Conformance statements
Interference Information: Part 15 of FCC Rules
This equipment has been tested and found to comply with the limits for Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interferences when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the guidelines in this document, the
equipment 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 the expense of the user.
Security statement
In rare instances, unauthorized individuals make connections to telecommunications networks through the use of remote access feature. In such an event,
applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any
allowances or give any credit for charges that result from unauthorized access.
Limited warranty
Alcatel-Lucent provides a limited warranty to this product. For terms and conditions of sale, contact your Alcatel-Lucent Account Team.
Alcatel-Lucent - Proprietary
See notice on first page.
Contents
About this document 1-1
Purpose ............................................................................................................................ 1-1
Intended audience............................................................................................................ 1-1
How to use this document ............................................................................................... 1-1
Safety information ........................................................................................................... 1-2
Related information ......................................................................................................... 1-2
Related information errata ............................................................................................... 1-2
Pg. 5-24 “1696R and 1830 PSS interoperability” ........................................................... 1-3
Document support ........................................................................................................... 1-4
Technical support ............................................................................................................ 1-4
How to order.................................................................................................................... 1-4
How to comment ............................................................................................................. 1-4
1 Features 1-5
Overview ................................................................................................................................................ 1-5
Network Element Support in Release 7.5 .............................................................................................. 1-6
New Features in Release 7.5 (since R7.0.50)......................................................................................... 1-7
New Features in Release 7.0.50 (since R7.0.2)...................................................................................... 1-7
New Features in Release 7.0.2 (since R7.0.1)........................................................................................ 1-7
New Features in Release 7.0.1 (since R7.0)........................................................................................... 1-7
New Features in Release 7.0 (since R6.1.x)........................................................................................... 1-8
Restrictions and Limitations .................................................................................................................. 1-8
Invalid SNC end points ................................................................................................... 1-8
Some commissioning wizards not supported for 1830 PSS-32....................................... 1-9
PSS-1 MD4H single fiber mode services with cross regen............................................. 1-9
PSS-1 MD4H single fiber mode to PSS-32 DWDM-CWDM regen via 11STMM10 or
4DPA4 to PSS-32 4DPA4 service................................................................................... 1-9
Upgrade ........................................................................................................................... 1-9
Service creation involving regens ................................................................................... 1-9
Service creation via xml file import .............................................................................. 1-10
Alcatel-Lucent - Proprietary iii

Issue 1 MARCH 2010 See notice on first page
Contents
Dual client port protected services on PSS-1 ................................................................ 1-10

Creation of services on 1830 PSS-32 NEs limited to R2.0 ........................................... 1-10
EPT Upload................................................................................................................... 1-10
11G quad port pluggable anyrate 4-client transponder (11QPA4)................................ 1-10
PSS-32 Network with PSS-16 spur............................................................................... 1-10
PSS-1 GBE Single fiber mode ...................................................................................... 1-10
2 Problems fixed 2-1
3 Known problems (KPL) 3-1
Overview................................................................................................................................................ 3-1
Troubleshooting ................................................................................................................................... 3-10
40G regen services ........................................................................................................ 3-10
NE Performance Monitoring......................................................................................... 3-10
SNMP v3 settings for trap forwarding from PhM......................................................... 3-10
Network element discovery using SNMP v3 ................................................................ 3-11
Service creation using a dangling OT card ................................................................... 3-11
Slow file choose in PhM Windows client ..................................................................... 3-11
SSH server on Windows ............................................................................................... 3-12
PSS-1 MD4H service discovery.................................................................................... 3-12
1696R service in partial state after discovery ............................................................... 3-12
4 Installalation 4-13
Overview.............................................................................................................................................. 4-13
System requirements............................................................................................................................ 4-14
Sun server requirements ................................................................................................ 4-14
Linux server requirements............................................................................................. 4-15
Windows server requirements....................................................................................... 4-15
Windows client requirements........................................................................................ 4-15
Solaris client requirements ............................................................................................ 4-16
Linux client requirements.............................................................................................. 4-16
Installation and upgrade instructions ................................................................................................... 4-16
Client upgrades.............................................................................................................. 4-17
Redundant server upgrade............................................................................................. 4-17
Solaris server installation .............................................................................................. 4-17
Red Hat Enterprise Linux server installation ................................................................ 4-17
iv Alcatel-Lucent - Proprietary 8DG60488AAAA

See notice on first page. Issue 1 MARCH 2010
Contents
Windows server installation .......................................................................................... 4-19

5 Miscellaneous 5-1
Overview ................................................................................................................................................ 5-1
Technical assistance ............................................................................................................................... 5-2
Overview ......................................................................................................................... 5-2
Technical support ............................................................................................................ 5-3
On-line customer support ................................................................................................ 5-3
Ask AL knowledgebase................................................................................................... 5-4
Accessing and navigating the on-line customer support (OLCS) web site ............................................ 5-7
Description ...................................................................................................................... 5-7
Accessing the OLCS web site ......................................................................................... 5-7
View an OLCS website ................................................................................................... 5-8
Ask AL knowledgebase................................................................................................... 5-9
CARES ............................................................................................................................ 5-9
Data drop box .................................................................................................................. 5-9
Documentation .............................................................................................................. 5-10
Downloads..................................................................................................................... 5-10
Alcatel-Lucent Alerts .................................................................................................... 5-11
Product Change Notices (PCNs) ................................................................................... 5-11
Return Material Authorization (RMA) (Repair and Exchange) .................................... 5-11
Other technical support services .......................................................................................................... 5-12
The technical support services expert workshop series................................................. 5-12
8DG604888AAAA Alcatel-Lucent - Proprietary v

Issue 1 MARCH 2010 See notice on first page.
About this document
Purpose
This Software Release Description (SRD) is issued to provide information on the
Alcatel-Lucent 1354RM-PhM Element Management System (EMS) Release 7.5 features,
known problems, problems fixed, software installation, and other helpful information.
Intended audience
This document is intended for individuals who are responsible for the installation,
acceptance, operations, and maintenance of the 1354RM-PhM Release 7.5.
How to use this document

This document is divided into the following chapters of information:
Chapter 1, “Features”
This chapter of the software release description provides a description of new features of
Alcatel-Lucent 1354 RM-PhM EMS Release 7.5, a summary of new and enhanced
commands, and any additional product changes.
Chapter 2, “Problems fixed”
This chapter of the software release description provides a list of problems fixed in
Alcatel-Lucent 1354 RM-PhM EMS Release 7.5.
Chapter 3, “Known problems”
This chapter of the software release description provides a list of known problems in
Alcatel-Lucent 1354 RM-PhM EMS Release 7.5.
Chapter 4, “Installation”
This chapter provides the procedures to install the software for Alcatel-Lucent 1354 RM-
PhM EMS Release 7.5 and its associated tools onto supported platforms.
Alcatel-Lucent - Proprietary 1-1

Features Overview
Chapter 5, “Miscellaneous”
This chapter provides various miscellaneous information regarding the Alcatel-Lucent
1354 RM-PhM EMS Release 7.5.
Safety information
This information contains hazard statements for your safety. Hazard statements are given
at points where risks of damage to personnel, equipment, and operation may exist.
Failure to follow the directions in a hazard statement may result in serious consequences.
SAFETY PRECAUTIONS
• For safety precautions, please see the Alcatel-Lucent 1354 RM-PhM EMS Release
Reference Guide for this release.
Related information
The following is a list of related documents:
• Alcatel-Lucent 1354 RM-PhM EMS Reference Guide (PN 8DG60013JAAA).
Related information errata

Note the following errata in the Alcatel-Lucent 1354 RM-PhM EMS Reference Guide:
1-2 Alcatel-Lucent - Proprietary 8DG60488AAAA

Features Overview
Pg. 5-24 “1696R and 1830 PSS interoperability”

The following text should be added to the text in the Reference Guide.
PSS1-GBE / 1696R 10xGE
- The PSS1-GBE must operate in full-rate operational mode.
- To interoperate with 1696R, PSS1-GBE Line port L1 must be facing
1696R 10xGE line port.
- Ensure that the following is provisioned on the PSS1-GBE line port L1
facing 1696R :
OTU2 Rate = 11.049
OUT2 FEC Mode = RSFEC
ODU2 Payload Type = 128
- Assign client port as GigE.
- Only the 1st 10 GigE clients can be used.
- The time slot assignment should follow 1696R 10xGE, i.e:
c1 <--> vts1
c2 <--> vts2
.................
c10 <--> vts10
The following text replaces the text in the Reference Guide.
PSS-32 11STGE12 / 1696R 10xGE
- Assign client port as GigE.
- Only the 1st 10 GigE clients can be used.
- Ensure that the following is provisioned on the 11STGE12 line port:
OTU2 Rate = 11.049
OUT2 FEC Mode = RSFEC
PSS-32 11STAR1 / 1696R OC192sws
- Assign 11STAR1 client port as OC192.
- Ensure that the following is provisioned on the 11STAR1 line port:
OTU2 Rate = 10.709
OUT2 FEC Mode = EFEC
PSS-32 11STAR1 / 1696R 10GigELAN
- Assign 11STAR1 client port as 10GigE.
- Set 10GigE client port attribute "Encapsulation Mode" to
"CBRLAN11.049".
- Ensure that the following is provisioned on the 11STAR1 line port:
OTU2 Rate = 11.049
8DG604888AAAA Alcatel-Lucent - Proprietary 1-3
Features Overview
OUT2 FEC Mode = EFEC

Document support
Alcatel-Lucent provides a referral telephone number for document support. Use this
number to report errors or to ask questions about the document. This is a non-technical
number. The referral number is 1 (888) 727 3615(continental United States) or +1 (630)
713 5000 (for all countries).
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://alcatel-lucent.com/support/) for contact
information.
How to order
To order Alcatel-Lucent documents and courses, contact your local sales representative
or use the Online Customer Support Site (OLCS) web site (https://support.lucent.com).
How to comment
To comment on this document, go to the Online Comment Form (http://www.lucent-
info.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).

Features Overview
1 Features
Overview
Purpose
This chapter of the software release description provides new features for Alcatel-Lucent
1354 RM-PhM Element Management System (EMS) Release 7.5
Contents
This chapter contains the following:
• Network element support in Release 7.5
• New features in Release 7.5
• New features in Release 7.0.50
• New features in Release 7.0.
• Restrictions and Limitations

Features Network Element Support in Release 7.5
Network Element Support in Release 7.5
PhM Topology View icons NE releases supported

1830 PSS-32 R1.0 R1.0.x
1830 PSS-32 R1.1 R1.1.x
1830 PSS-32 R2.0 R2.0.x
1830 PSS R2.5 R2.5.x
1830 PSS-1 R1.0 R1.0.x
1830 PSS-1 R2.0 R2.0
1830 PSS-1 R2.5 R2.5
1830 PSS-1 MD4H R1.0 R1.0
1830 PSS-1 MD4H R1.5 R1.5
1696R R5.1 R5.1
1696R R5.4 R5.4

Features New Features in Release 7.5 (since R7.0.50)
New Features in Release 7.5 (since R7.0.50)

• New PSS-16 shelf
• Low power fixed gain amplifier (ALPFGT)
• Unmanaged services (unkeyed OCH services)
• 8 channel static filter (SFD8A-D)
• Pluggable 2.5G optimized OT (4DPA2)
• Multiplexed line termination without amplification (OSCT)
• 4x10 muxponder with P-DPSK support (43STX4P)
• 40 Channel SFD (SFD40, SFD40B)
• 11G dual port pluggable GBE 12-client Mux (11DPE12 interworks with PSS-1 GBEH)
• 40G add/drop transponder with P-DPSK support (43STA1P)
• Expanded 4DPA4 capabilities
• 8-degree R/TOADM support
• 2-degree 88 channel FOADM
• 20A power option without WT support
• 23 dB amplifier (A2325A)
• Uni-directional ESNCP protection for PSS-1 GBE
• New optical modules
New Features in Release 7.0.50 (since R7.0.2)

• Y-Cable support for 43STX4
• 10GB-SR XFP support on 43STX4
New Features in Release 7.0.2 (since R7.0.1)

• Improved support for discovering services created prior to R7.0
New Features in Release 7.0.1 (since R7.0)

Interoperability (IOP)
• PSS-32 R2.0 / 1696R R5.4 mid-span meet

• PSS-1 GBE R2.0 / 1696R R5.4 OT card interop

Features New Features in Release 7.0 (since R6.1.x)
New Features in Release 7.0 (since R6.1.x)

• PSS-32 R2.0
o 88 channel services
o 4DPA4 services
o 4DPA4 Dual fiber ESNCP protection
o 11STMM10 OTU1 services
o Dual stage mux: 4DPA4 line to 11STMM10 client OTU1 services
o 40G optical transport of 10G muxed services using 43STX4
o Black & White channel services on 4DPA4.
o Services requiring CWDM cross-connects.
• PSS-1 GBE R2.0

o Fullrate services
o Subrate CIR services
o Black & White channel services
• PSS-1 MD4H R1.0

o PSS-1 MD4H services
o Dual and single fiber ESNCP protection
o Black & White channel services
Interoperability (IOP)
• PSS-32 R2.0 / PSS-1 MD4H R1.0

o Dual stage mux: PSS-1 MD4H line to 11STMM10 client OTU1 services
• PSS-32 / PSS-1 GBE (all releases)
• 1696R R5.4 / PSS-32 R2.0 OT card interop
Other features:
• Raman and EDFA network element management with respect to 1830 PSS-32 network elements.
• Ability to forward NE generated alarms directly from the PhM to configured SNMP trap receiver
destinations. Prior to R7.0, this feature only supported forwarding of PhM internally generated
alarms.
• 1830 PSS-1/32 new security features in R2.0 product family
Restrictions and Limitations

Invalid SNC end points
PhM may find invalid SNCs present in the database, particularily after an upgrade. PhM will try
to fix them on service discovery and log an error in ems_trace.log with the message

Features Restrictions and Limitations
“UNABLE TO FIND CHILD SNCS FOR THE PARENT SNC WITH END POINTS”. These
SNCs are not used and must be cleared by unmanaging the services using this port.
To unmanage the services, open the Physical Topology of the NE appended to the above error
message, right click on the corresponding network port and select view services.
Unmanage the services and rediscover them. This clears the invalid SNCs from the database.
These invalid SNCs will not affect service creation or service discovery.
Some commissioning wizards not supported for 1830 PSS-32

The following commissioning related wizards are not supported in PhM 7.0 for 1830 PSS-32
network elements: Add NE, Delete NE, Upgrade NE, Upgrade card.
PSS-1 MD4H single fiber mode services with cross regen

The PhM does not support these services - either creation or discovery from the network. Only
point-to-point single fiber mode services are supported.
PSS-1 MD4H single fiber mode to PSS-32 DWDM-CWDM regen via 11STMM10 or 4DPA4 to PSS-32
4DPA4 service
The PhM does not support these services – either creation of discovery from the network (see
KPL 32832).
Upgrade
Service import/export xml files
Service export files are not supported across PhM releases. If you exported a service to a
xml file from a prior version of PhM, you must reexport the service from the current PhM
version before attempting to import it into the current version.
Regen services after upgrade
After upgrading to PhM 7.0 or later, regen services (back-to-back 11STAR1 regen, or
11STAR1 client/line regen for PSS-1 GBE interop) will appear properly in the PhM,
however, if the services are unmanaged they will fail to discover back into the PhM. The
workaround is to manually delete the OTS cross connects and then try to discover the
service.
Service creation involving regens

In order to create a service involving one or more regen points via the PhM GUI (using the
wizard or import xml files), all regen point provisioning must be done by the user ahead of time.
The includes:
• Topology connections
• Channel assignment on client ports
• Port administration set to “up”
• Client “Domain Edge” attribute set to “false”

Similarly, when deleting a regen service from the PhM, the regen point provisioning is left
untouched.
Depending on where the regen topology lies within a network element, you may need to exclude
certain ports to force the service route over the regen. For example, the thru ports on CWR or
filter cards may need to be excluded to force service routing over the regen point.
Service creation via xml file import

The service route is not included in the export service xml file. Hence, upon import, the service
route is not guaranteed to be the same as when the service was exported.
Regen point provisioning is not included in the export service xml file. Prior to importing a
service, the regen provisioning must be performed manually.
Dual client port protected services on PSS-1

If problems are encountered creating a protected pair of diversely routed services between 2 pairs
of client ports on PSS-1 GBE or MD4H, the workaround is to create 2 unprotected services
along the desired paths.
Creation of services on 1830 PSS-32 NEs limited to R2.0

After upgrading to PhM R7.5.x, existing services on 1830 PSS-32 NEs older than R2.0 (i.e.
R1.1.2) will be discovered from the network, however, new services created (either in PhM or
another NE user interface) on NEs running pre R2.0 software loads may fail to create in the
PhM.
EPT Upload
The EMS Reference Guide mentions a feature originally planned for PhM R7.5 called EPT
Upload. This feature has been moved to release 7.5.1 of PhM.
11G quad port pluggable anyrate 4-client transponder (11QPA4)

The EMS Reference Guide mentions a feature originally planned for PhM R7.5 called 11QPA4.
This feature has been moved to release 7.5.1 of PhM.
PSS-32 Network with PSS-16 spur

PhM is not able to commission a PSS-32 TOADM with a PSS-16 DFOADM spur because EPT
does not support this design. The user will have to provision the system manually.
PSS-1 GBE Single fiber mode

PSS-1 GBE Single fiber mode service creation is supported only in the full rate mode. Sub-rate
mode is not supported.


2 Problems fixed
Problems from Release 7.0.50 Build 4 that are resolved in Release 7.5 Build 22 are listed below:
Issue Severity Problem

33396 Major Mysql backup failed during upgrade from R5.04 to R7.0.1
32860 Minor Auto discovery by IP network masking fails
Problem with the order wavelength services get deleted on MUX regen
32800 Minor cards
32776 Minor Fails to discover VF service unprotected 43STX4 (9360)
32603 Minor Entity Type Alarm Severity Assignments blank after refresh
32583 Minor Card firmware window doesn't show PSS1GBE
32367 Minor Invalid Far End Time Slots reported for 11STMM10 card
32183 Minor Cannot create NE using SNMPv1 - exception issued
Oper Mode of L2 port won't change upon chaning mode of L1 till the
31835 Minor manual resync
29838 Minor Shelves get doubled in Physical Topology tree
27103 Minor PSS1 MD4 inter-nodal topological links are not displayed on PhM
26829 Minor PHM-OPS- Signal port - Admin state not up after creating the service
26715 Minor Show DCM port in path trace for LD
26714 Minor Show VA port in path trace for 4DPA4
Problems from Release 7.0.2 Build 58 that are resolved in Release 7.0.50 Build 4 are listed below:

38014 Major Remove a check for a mysqld executable that no longer exists.
Problems from Release 7.0.1 Build 56 that are resolved in Release 7.0.2 Build 58 are listed below:

35588 Major Unable to discover services using the PhM
36114 Major Unable to discover or unmanage service

Problems fixed Restrictions and Limitations
36120 Minor Existing Logical links recreated on service discovery

36121 Minor OCH XC getting deleted from PhM database on service discovery
36365 Minor 1696R 10xGE & PSS1 Pt-to-Pt services end up in partial state upon
rediscovery
Problems from Release 7.0 Build 54 that are resolved in Release 7.0.1 Build 56 are listed below:

33109 Major PhM server stops responding during service discovery when the number
of services to be discovered from the network is more than 100
(approximately). Server must be restarted to continue discovering
services.
33267 Minor Port direction attribute missing for line and client ports on 1696R OT
cards in Inventory View.
32993 Minor Unmanaging a large number of services in bulk is very slow.
32982 Minor GE service between PSS-1 and 1696R is created without notifying user
that a FEC type mismatch exists.
32958 Minor Service creation fails to provision wavekeys (EMS keying) on 1696R
CAD in pss1-pss1-1696R configuration.
32184 Minor OTS link between 1830 and 1696 is not discovered.
Problems from Release 7.0CI Build 28 that are resolved in Release 7.0 Build 54 are listed below:

27869 Major Deleting a Topology group impacts service views:
27213 1. Only part of lightpath power shows up in service view.
2. Unmanaged services fail to discover.
27246 Major Setting PSS1MD4H Line port ITU rate to black and white channels 850,
1310 or 1550 causes NE to reset.
28980 Major Raman/EDFA alarms don't automatically clear in PhM after cleared on
network element.
29910 Minor PSS-1 MD4H single fiber mode services do not show channel number in
service list view.
29625 Minor Service creation allowed when misconfigured PSS1MD4H timeslots.
29497 Minor Service creation from PhM over 1830 PSS-32 NEs fails due to NE
returning keying error.
29432 Minor 11STMM10 service client endpoints changed upon service re-discovery.
27174 Minor Some PSS-1 MD4H PM statistics are not viewable from PhM.
27031 Minor Some problems with TCA administration on PSS-1 MD4H.
26536 Minor PSS-1 MD4H client timeslot provisioning does not always validate
against client rates.
Problems fixed Restrictions and Limitations
26408 Minor Warning after import with no keying

3 Known problems (KPL)
Overview
Purpose
This chapter provides a description and workaround for each problem known to exist in
Alcatel-Lucent 1354 RM-PhM Element Management System (EMS) Release 7.5 Build
22.
Severity classification follows TL 9000 as defined below:
Critical - Critical problems severely affect service, capacity/traffic, billing, and
maintenance capabilities and require immediate corrective action, regardless of time of
day or day of week as viewed by a customer upon discussion with the supplier.
Major - Major problems cause conditions that seriously affect system operation,
maintenance, and administration, etc. and require immediate attention as viewed by a
customer upon discussion with the supplier. The urgency is less than in the critical
situations because of a lesser immediate or impending effect on system performance,
customers, and customer's operation and revenue.
Minor - Other problems that customer does not view as critical or major are considered
minor. Minor problems do not significantly impair the functioning of the system and do
not significantly affect service to the customers. These problems are tolerable in system
use.

Known problems (KPL) Overview
Issue Severity Problem Work Around

38831 Major Several performance issues were Do not open multiple inventory
38800 identified including auto refresh in the windows with the auto refresh
36412 inventory window and discovery. option selected.
32832 Major PSS-1 MD4H single fiber mode to

PSS-32 11STMM10 or 4DPA4 regen
(client to line port) to PSS-32 4DPA4
service. The service cannot be created
from the PhM or discovered from the
network using PhM.
39460 Major Cannot perform commissioning on a Commission with a planning file
greenfield system from EPT.
39457 Minor 4DPA2 Protection group is not Rediscover the NE after assigning
discovered. the 4DPA2 protection port.
39264 Minor Client port details are not displayed for Use WebUI
the Z end of a 43STX4P Y cable
service
39173 Minor Wavelength services cannot be Make sure NEs are in the same
38484 imported if NEs are in different groups group.
39112 Minor Wavelength Service Interoperability
issues between PSS-1 to PSS-32
38894 Minor Database restore fail message during Ignore this message
audit for software downgrade
38569 Minor 4DPA2 ESNCP APS Group allows to Provision in non-revertive mode
switch from non-revertive to revertive
38184 Minor Cannot create single fiber service for Use CLI and WebUI.
37939 dual stage or CWDM-DWDM regen.
37882
37677
37396
38902
37095 Minor 11DPE12 is not found in Card Use CLI to show available profiles
Firmware
37085 Minor RAMAN IP is not saved and displayed View the IP address in the
in "RAMAN & EDFA Associations" RAMAN properties
screen
36884 Minor CIT IP address may cause EMS Change the CIT IP address to be
duplicate NE management IP address unique.
36565 Minor Client installation or upgrade causes Ignore the second window.
duplicate browsers to open.
36480 Minor Provisioning of CWR pack causes a Ignore the error. The pack is being
timeout error provisioned, but takes a long time.

36398 Minor CAD/SVAC port not put in AINS state

if alien or transponderless service is
created in AINS
36383 Minor After deleting an 11STMM10 Y-cable Unassign the port manually
service PhM will not unassign the
client port
36369 Minor Existing OCH 1696/1830 Re-enter custom fields such as
Transponderless services rediscovered Customer ID and Label.
upon service discovery
36165 Minor PhM for fault Condition List the NE Refer to the WebUI
source data are getting truncated
36048 Minor NE NTP estimated drift parameter is Refer to the NTP details.
not displayed in the NTP settings
33313 Minor Unmanaging and rediscovering a Export the service.
OPSA service results in missing ports Unmanage the service.
along service path and power trace for Import the service.
protection path only. This will need to be repeated
1. In the Service Details view should the service be unmanaged
Protection Equipment tab, the and discovered again in the future.
ILA NE and the end point NE
are missing some ports.
2. In the service power trace, the
same ports are missing in the
power chart.
33265 Minor Not able to provision a subtended shelf Use CLI or WebUI to provision
on 1830 PSS-32 R1.1.2 NE. the shelf and it will be discovered
by the PhM.
33132 Minor Cut-thru to RAMAN/EDFA Web GUI Change the MTU size on the NIC
doesn’t work when these network of the PhM server machine that is
elements are connected to a PSS-32 via used to connect to the
the PSS-32 E1 port. RAMAN/EDFA box. Refer to
1830 PSS-32 documentation for
details. The PSS-32 defect
numbers are 33110 and 33107.
33049 Minor For 1830 PSS-32 NEs, there is an

inconsistent view of the loss between
loss report after ASE adjust, loss report
no services (actually should be same as
ASE), and loss report with services.
Then loss view in lightpath trace is
inconsistent with the loss reports.

32975 Minor Incorrect routing failure messages Don’t rely solely on routing failure
during service creation. Sometimes the messages to determine why a
routing failure message is not service cannot be created.
indicative of the real cause of the Examining the physical topology
routing failure. and port exclusions may help
determine the failure reason more
accurately.
32953 Minor 1830/1696R IOP mid-span meet: If slot number shows as a number
Physical Topology connection between > 128, subtract 128 from the
1830 PSS-32 and 1696R NEs shows number and include the letter “b”
slot number improperly on the 1696R at the end for the proper slot
end. number format.
32883 Minor 1830/1696R IOP mid-span meet: After Delete the 1696R NEs and
fibering a 1830 PSS-32 NE between recreate them. Recreate the
two 1696R NEs, the old external links external links between the 1696Rs
between the 1696R NEs are not and the PSS-32 NE via the
automatically removed in the PhM Physical Topology view.
Topology view and cannot be deleted.
32822 Minor PhM fails to delete a PSS-1 GBE To delete a PSS-1 GBE service
service routed over PSS-32 NE’s. routed over PSS-32 NE's the
Service is left in a partial state. following procedure must be
followed:
1. Disable GCC on the 11STAR1
client ports used by the service
2. Admin down the 11STAR1
client ports used by the service
3. Delete the service.
4. Admin up the11STAR1 client
ports previously put admin down.
5. Enable GCC on the 11STAR1
client ports where it was
previously disabled.
32808 Minor PSS-32 11STGE12 and 11STMM10 Y- Unmanage both unprotected

Splitter services sometimes discovered services, recreate the same Z to A
as 2 separate unprotected services when fully protected service. Further
A and Z endpoints are reversed. unmanage/discoveries of the
service works correctly.
This situation can be avoided
entirely if the fully protected
services on the
11STGE12/11STMM10 card pairs
are all initially created with the
same A and Z ends.
32794 Minor Cannot recreate PSS-1 GBE subrate If these services become
CIR services via service export and unmanaged, they can be
import. The CEVLAN ids are not rediscovered from the network.
being exported and hence the service If the services are deleted they
creation fails upon import. must be recreated using the PhM
service creation wizard or
rediscovered from the network
after restoring them in the network
from NE database backups.
32789 Minor NE cross connects not always removed Manually delete the cross-
when deleting 43STX4 regen service connects from the NE using PhM
from PhM. This could be limited to the Facility Connection window.
NE containing 43STX4 regen point or
could extend to all NE’s along the
service route.
32708 Minor Attempting to delete external topology Manually open the Inventory
connection from LD line port with window for the NE containing the
Raman or EDFA associated, causes LD card and remove the
unexpected NE Inventory window to be Raman/EDFA association from
opened. there.
32707 Minor Service affecting alarm list only shows Open the service details window
alarms on A and Z end NE's. and look at either the working or
protection equipment path trace.
Any alarmed entity is shown in
this view and the Fault window
can be opened on any entity to
view the actual alarms.
32548 Minor Disabling/Deleting a logged in user To disable or delete a NE user that
results in an Unknown error message is currently logged into the NE,
use the WebUI or CLI.
32545 Minor Discovered 1830 PSS-32 appears with Do not use “New NE…” wizard to
EDFA icon in Topology Map view create EDFA NE. Instead, enter
the IP address into the “External
Amp IP Address Out” attribute for
the external Amp Line port in the
Inventory View.
32530 Minor SFTP PM file transfer fails when root In System Settings, File Transfer
is different from "/" tab, set “SFTP Filename Prefix” to
“/” (without the quotes).
32504 Minor ESNCP Protection Type terminology For a PSS-32,
differs from PSS-32 to PSS-1 for MSC “PARTIALLY_PROTECTED” in
the Service Creation Wizard is
used when either “OPSA” or
“ESNCP” protection is desired.
32423 Minor Shelf LED for PSS-1 MD4H not Resynchronize the NE or run a
updated automatically in PhM LED audit operation from the
Fault menu on the Inventory View.

32385 Minor Rediscovering an already discovered Ignore the message.

service may result in message “Can't
upload service …because it is not
between two client ports.”
32251 Minor Sometimes changing the NE name is This problem occurs when
suffixing the IP address to the new changing one or more letters in the
name. NE name from one case to another
(for example, "Chicago" to
"chicaGo"). As a workaround,
simply change the NE name to
something without the same
sequence of numbers and letters,
and then retry the originally
intended name change.
31996 Minor Trying to delete too many services in Delete the cross-connects via the
one operation may result in some cross Facility Connection View.
connects internal to the PhM (i.e. not
provisioned on the NE) not getting
deleted.
31931 Minor Not able to set 'Mapping Mode' Ignore Mapping Mode value in
attribute on 43STX4 client ports from PhM and use WebUI instead.
PhM.
The Mapping Mode can be changed in
Inventory but the change is not
reflected on the NE. If another
interface changes the value, PhM will
not reflect the new value.
31910 Minor Problems with PM baseline function Use WebUI for PM baselining on
for 43STX4. 43STX4.
31893 Minor 10GE 11STAR1 service creation Assign the client ports prior to
sometimes fails if client ports not pre- creating the service.
assigned.
31880 Minor "NE loss of Comms” alarms. These No specific workaround since the
alarms are very short in nature and issue is dependent on the control
appear to happen at similar times each network configuration and traffic
day. New larger values for 'idle patterns used in each scenario
timeout' , 'interval' and 'max failures' on
NE associations don’t’ have an impact.
In a future release, changing the
attributes on an NE association in
the PhM will have more impact.
31610 Minor Silent authentication failure when Disable 1 of the RADIUS servers
RADIUS server hostname not resolved. in System Settings in order to
determine which server is causing
the problem.
31079 Minor SFTP Database restore Fails from PhM Use WebUI or CLI to restore DB

backup on the NE using SFTP.

31061 Minor Incoming tti for OTU1ODU1 shows Treat boxes as blanks.
square boxes as oppossed to blank
30619 Minor Importing a Service with configurable Use the service creation wizard to
ODU2 parameters may fail. This may create the service.
prevent a 1830 / 1696R OT
interoperability service from being
created using the service import
feature.
29764 Minor PSS-1 GBE service through PSS-32 Select another NE on the service
NE’s may not be listed if PSS-32 NE’s route to list the service.
selected when service list view is
generated.
29650 Minor Attempting to create PSS-1 MD4H Ensure client timeslot provisioning
service when client timeslots are not matches at each end of the service
matching results in unclear routing before it is created.
failure message.
29578 Minor Service created with FEC type Before creating a service involving
mismatch. Traffic will not flow and intermediate ports with FEC type
there is no warning to the user. provisioning, ensure that the ports
Service creation only verifies the FEC at the ends of each Och trail have
types on the A and Z end OT line ports, matching FEC modes.
any intermediate ports with a FEC type Note that for a service that has no
are ignored. intermediate ports with FEC type
provisioning, PhM will
automatically set the best FEC
mode to match at the A and Z
ends.
29371 Minor Service operations may fail due to one Ensure that all NEs comprising the
or more NEs being offline. service are online before
beginning a service operation.
29349 Minor APR Active-line condition sometimes Refresh the condition window and
shown twice on PhM duplicate alarm goes away.
29183 Minor Only System Setting has effect on User There can only be 1 setting for
Session Timeout – individual user User Session Timeout for all users.
setting does not work for individual
clients.
28412 Minor PhM: AtoZ and ZtoA power traces Direction really only has meaning
sometimes are reversed between for the lightpath power trace from
Service lightpath power trace and the Service view. Ignore direction
Lightpath trace launched from Physical in the Physical Topology view.
Topology view.
27245 Minor Provision PSS-1 MD4H service Ignore Sonet values.
window layer rate contains both Sonet
and SDH rates when MD4H operating

in SDH mode.
27153 Minor PSS-1 lightpath power trace is Use the Inventory window to view
completely blank. OT Tx power.
26973 Minor Shortest path routing not supported for Use port exclusion in the Service
dual line ported OT cards. Creation Wizard to force the route
The PhM service creation algorithm is as desired.
supposed to find and use the shortest
hop path between A and Z end nodes as
the route for the service. With the
introduction of dual line ported cards
(i.e. 11DPGE12 (PSS-1 GBE) and
4DPA4/MD4H), the algorithm will
pick the first route it finds on a either
line port (typically L1) - it should
check both line ports for a valid route
and then pick the shorter one.
25178 Minor PSS-1 to PSS-32 ch deletion may leave Manually set the 11STAR1 line
alarms on 11Star. port out of service.
If you try to delete a service that goes
from PSS1 to PSS1 through the PSS32
you end up with alarms of LOS on the
line side of the corresponding
11STAR1 circuit packs.
22657 Minor Cannot set VOA attenuation in power Use the Inventory View to set the
chart views for SVAC and 4DPA4 VA “Programmed Network Output
ports. Power” on the VA port. The
effect and be seen in the power
chart view after a refresh.
22327 Minor Changing service label causes APS To change the label of a protected
direction/revertive/wait revert to service, first unmanage and
defaults. rediscover the service then set the
service label.
21639 Minor Uploading services with 1 way cross Unmanage all corrupted services
connect can corrupt existing 1696R and rediscover them via service
services upload.
20686 Minor Setting expected power to present Ignore error message about the
power for manual points for OPS- OPSA signal port.
SVAC service gives error message.
18217 Minor FTP server folder not deleted upon Manually delete the FTP server
PhM uninstall. folder creation upon PhM
installation (if user chose the
option to install the FTP server).
17091 Minor PhM redundant servers require During installation, ensure the
identical installation paths. same install path is specified on
both servers.

16693 Minor Dual Client protected service uploaded None.

as two unprotected services

Known problems (KPL) Troubleshooting
Troubleshooting
40G regen services
Should problems be encountered with services routed across back-to-back 43STX4 OT cards, the
workaround is to configure the 40G regen client port at the client rate instead of OTU2 rate and
create two point-to-point services instead of a single end-to-end regen service; also note that the
regen client ports should not be connected by a topology link because each service should be
independent with the other.
NE Performance Monitoring
Problem - Performance Monitoring (PM) statistics not available in PhM for a NE

Solution – The NE and PhM times must be synchronized (within 1 minute). The PhM does not
synchronize its time with NE time automatically, it must be done manually. This can be
accomplished and synchronized maintained by the use of a NTP server as described below for
the PhM client.
1. Go to Topology view -> Admin -> settings -> System settings -> NTP. Enable the checkbox
“Use this server as the NTP server”.
2. Select the NE, Go to Admin -> NE NTP table
Double- click on the NTP row to see "NTP Details for <NE-Name>" window.
Ensure that the time zone field is not blank.
Click on "Add EMS as NTP Server".
Once the PhM and NE times are synchronized, it may take up to 1 day for the PhM to retrieve
PMs from the NE.
NOTE: Regardless of the timezone setting on a NE, when PM data files are transferring to the
PhM, the bin start times always use GMT and are displayed in the PhM GUI using the time zone
setting on the PhM server.
If not using a NTP server – it is highly recommended that a NTP server be used to synch up time
on both the NE and PhM Server – otherwise, note the following:
• Set time manually on all NE’s and PhM (note the 1 minute difference limitation)
• Set the timezone consistently on the PhM Server and all NE’s. The default timezone on the
NE is UTC - setting the time/date without changing the timezone on the NE to match what is
set on the PhM Server (Windows OS) will result in PM data not being viewable by the PhM.
SNMP v3 settings for trap forwarding from PhM

SNMP v3 settings are the same for every trap destination and cannot be changed:
1. AutoProtocol = HMAC-MD5
2. PrivProtocol = AES128
3. EngineId. This is a 12 byte id structured as follows:
a. First 8 btyes always = 0x00001d3b000000a1

b. Final 4 bytes = IP address of SNMP agent on PhM server that sent the trap.
c. E.g. An EngineId=0x00001d3b000000a101020304 means that the PhM server that
sent the trap has IP address 1.2.3.4.
Network element discovery using SNMP v3

The defaults in the PhM, 1696R NE’s and 1830 NE’s are configured to allow PhM to discover
the NE’s properly when SNMP v2c or v3 is used. If a NE is not being discovered by the PhM,
one thing to check is that the community (v2c) and USM Users (v3) configuration has not been
inadvertently changed on the NE.
SNMP v2c configuration – as CLI admin user, check the command “config-snmpserver-
community-nms” and ensure that the “Name” matches what you are using in the PhM to create
the NE:
Community: nms
Name: nms_snmp
SNMP v3 configuration – as CLI admin user, check the command “config-admin-snmpusers”.
For the USM User credentials used in the PhM to create the NE:
• User must be “Active”
• Credentials must match (user name, authentication password, privacy password). Note
that you cannot view the passwords, but you can set them to what you are expecting.
By default, the v3DefaultUser is “Active”, has NMS access and matches the default credentials
in the PhM.
1830 NE not discovering in PhM after an upgrade from R1.x to R2.0
SNMP v3 passwords may need to be updated using the following 2 CLI commands to
update passwords for the SNMPv3 default user (v3DefaultUser):
# config admin snmpusers edit v3DefaultUser authpasswd
# config admin snmpusers edit v3DefaultUser privpasswd
1830 NE not discovering in PhM after a warm reset following a change to loopback IP address
After the warm restart following a change to the loopback IP address, the 2 CLI commands
listed above are needed to update passwords for all SNMPv3 users, including the ones for
SNMPv3 default user (v3DefaultUser). This includes the initial loopback IP address
provisioning from its default value. Note that going forward, there is no need to update
passwords when upgrading from R2.0 to a future release. Also note that if loopback IP
address change is followed immediately with clearing database (without also clearing IP
addresses), then there is no need to update SNMPv3 passwords.
Service creation using a dangling OT card

Its not possible to create a service using dangling transponder (external topology connection on
the line port) with auto wavekey assignment. You have to use “Auto Keying (EMS)” or “No
Keying” to create the service.
Slow file choose in PhM Windows client

The file chooser in a PhM client running on Windows may appear very slow when there are zip
files in the folders being viewed.. You can prevent the file chooser from drilling into the
contents of zip file by executing the command below from the CMD prompt.
C:\> regsvr32 /u %windir%\system32\zipfldr.dll
Note that this command removes the association between the .zip file extension and it’s program,
so .zip files won’t automatically open anymore from the File Explorer (you have to manually
select the program to use with the extension).
SSH server on Windows

NE backups and PM don't work consistently with freeFTPd and freeSSHd on Windows servers.
(they work with cygwin sshd).
PSS-1 MD4H service discovery

PSS-1 MD4H services will not discovered in the PhM unless cross-connects are created on the
NE. The MD4H will pass traffic with timeslot provisioning only, however, the PhM requires the
Och cross-connect as well in order to discover the service. As a workaround, always use the
PhM to create MD4H services to ensure that the Och cross-connects are created so that the
service can be discovered in the future should it become unmanaged.
1696R service in partial state after discovery

Some services between 1696R NEs may have "bad" OT port provisioning in the sense that the
line port is provisioned as uni-directional but the client port is bi-directional. Since the line and
client port directionality doesn’t match, the PhM considers this as invalid and puts the discovered
service in the "partial" state. Traffic should not be affected, however, if the user wants to get the
service out of the "partial" state, they must fix the port provisioning to make sense, i.e. uni-
directional on both client and line port with opposite directions on each (Rx on client and Tx on
line, or Tx on client and Rx on line).

Installalation Overview
4 Installalation
Overview
Purpose
This chapter provides system requirements and installation procedures for the Alcatel-
Lucent 1354 RM-PhM Element Management System (EMS) Release 7.5.
Contents
• System requirements
• Installation and upgrade instructions.

Installalation System requirements
System requirements
The Alcatel-Lucent 1354 RM-PhM consists of a server and one or more clients. The server
and clients both support Solaris x64, Windows and Red Hat Enterprise Linux. Alcatel-
Lucent recommends Solaris x64 or Red Hat Enterprise Linux for production networks.
It is recommended to configure the EMS server with an Uninterruptible Power Supply
(UPS). If a power failure occurs without a UPS, corruption of the database is possible.
Please refer to “EMS Database Backup and Restore” in Chapter 2 of the Alcatel-Lucent
1354 RM-PhM EMS Reference Guide for restoration procedures. Alcatel-Lucent also
recommends using a RAID 10 disk configuration for robustness.
EMS server sizing guidelines follow. These are based on the number of NEs being managed
by the server, and the number of simultaneously active client users. This assumes a NE has
an average of 3 shelves (or approximately 60 cards). If the average is higher or lower, the
configuration should be adjusted accordingly.
Alcatel-Lucent recommends updating the server with the OS vendor’s most recent patches
before installing the Alcatel-Lucent 1354 RM-PhM EMS.
Sun server requirements

Solaris 10 (x64) is supported.
The following hardware guidelines apply to a Sun x64 server:
100 NE 250 NE 250 NE

20 clients 25 clients 100 clients
Model / Sun Fire Sun Fire Sun Fire

CPU X2200 M2 X2270 X4270
AMD Opteron Intel Xeon Intel Xeon
2 Quad-Core AMD 2 Quad-Core Intel 2 x Quad-Core
Opteron, 2.3 GHz Xeon E5540, 2.53 X5570, 2.93 GHz
Model- 2376 GHz
Processors
RAM 8 GB 8 GB 12 GB
Disk 2 x 250 GB 2 x 500 GB 4 x 300 GB

Size*

Installalation System requirements
* Note: The disk should be set up with 2 partitions: a Swap partition = 2 x physical
memory size, and the rest of the disk in the root partition.
Linux server requirements

64-bit Red Hat Enterprise Linux Server Release 5.3 is supported.
For Linux server hardware configurations, use a processor and memory
configuration equivalent to the recommended Solaris x64 configuration. Only 64-bit
server hardware is supported.
Windows server requirements

The supported OS versions are:
· Windows 2003
· Windows XP (Service Pack 2)*
The following hardware guidelines apply to a Windows server:
50 NE 100 NE 100 NE
5 clients 10 clients 20 clients
CPU 2 x 3 GHz P4 2 x 3 GHz Xeon 2 x 3 GHz

Dual Core Xeon
RAM 4 GB 8 GB 8 GB
Free Disk 20 GB 100 GB 200 GB

Space
* Windows XP is not recommended as a server. It is supported as a client only.
Windows client requirements

The supported OS versions are:
· Windows 2003
· Windows XP (Service Pack 2).
The following is the minimum and recommended hardware configurations for a Windows
client (faster hardware will provide better response):
Minimum Configuration Recommended Configuration
CPU 1 x 2 GHz P4 1 x 3 GHz P4 or faster
RAM 1 GB 2 GB

Installalation Installation and upgrade instructions
Free Disk Space 500 MB 1024 MB
Solaris client requirements

Solaris 10 (x64) is supported.
A single Solaris client may be run on the main Solaris EMS server. A multi-client
GUI server, however, must be run on a separate computer from the main EMS
server.
The following is the minimum recommended hardware configuration for a Sun client
(faster hardware will provide better response:
Single Client Minimum 10 Client GUI Server 20 Client GUI Server

Configuration
Model / Sun Fire Sun Fire Sun Fire

CPU X2100 M2 X2100 M2 X2200 M2
AMD Opteron AMD Opteron AMD Opteron
1 x Model 1220 1 x Model 1220 2 x Model 1220
Dual Core 2.6 GHz Dual Core 2.6 GHz Dual Core 2.8 GHz
RAM 1 GB 4 GB 8 GB
Disk 34 GB 73 GB 105 GB
Size*
Linux client requirements

64-bit Red Hat Enterprise Linux Server Release 5.3 is supported.
For Linux client hardware configurations, use a processor and memory configuration
equivalent to the recommended Solaris x64 configuration. Only 64-bit server
hardware is supported.
Installation and upgrade instructions

Detailed Alcatel-Lucent 1354 RM-PhM EMS installation and upgrade instructions
are included in the “Installing the EMS” section of the Alcatel-Lucent 1354 RM-PhM
EMS Release Reference Guide for this release.
The PhM distribution media is DVD-ROM.
The PhM upgrade paths supported are:
1) PhM 5.4 -> 7.5
2) PhM 6.1.x -> 7.5
3) PhM 7.0.x -> 7.5
Client upgrades
When a client running older software connects to the upgrade server, the client user
will be presented with an error message indicating the software versions do not
match. The user is then redirected to a web page on the EMS server to download the
new client.
Redundant server upgrade

Follow this procedure if you are upgrading a redundant PhM server pair.
1. Shutdown the EMS and MySQL servers on the standby server.
2. Upgrade the active server.
3. Install the PhM on the standby server choosing “New Installation”.
If this procedure is followed then there is no opportunity for the standby to introduce
changes to the active server's database.
Solaris server installation

The EMS server cannot be installed using Solaris role-based accounts.
Red Hat Enterprise Linux server installation

SELinux and Firewall
The 1354RM-PhM EMS server will not run if either SELinux or the Firewall has
been enabled. It is acceptable for SELinux to be in “permissive” mode. However, the
system should be updated after installation so that a new policy can be installed.
Otherwise, /var/log/messages will be quickly filled with logs.
libXp
The Alcatel-Lucent 1354 RM-PhM EMS Linux server requires libXp. This can be
installed by running the following command:
yum install libXp.i386
TFTP
The 1354RM-PhM EMS requires a tftp server and client to be installed.
The server can be added at install time as tftp-server with the Servers->Legacy
Server Software group when adding packages. If the server is connected to the
Internet, it can be added after install by running the Add/Remove Programs
application or by running the following command:
yum install tftp-server
It can be installed using the following command:
rpm –-install tftp-server-0.41.1.2.1.i386.rpm

The service must be configured to use the same directory for tftp files that the
1354RM-PHM EMS server is using. You can do this by editing /etc/xinetd.d/tftp and
changing the server_args parameter to be “-s /tftpfiles”.
The service will then need to be enabled using the System-->Services GUI. Go to the
On Demand tab and ensure there that tftp has been selected. Click the Save button.
The tftp client can be added with the following command:
yum install tftp
Software Loading & NE DB backup/restore

FTP and SFTP are both supported for NE software upgrades and NE database
backups/restores.
FTP
Red Hat Enterprise uses the vsftpd service to support FTP requests. The
vsftpd service can be installed as part of the server services during the initial RHE
installation.
The follow steps can be used to diagnose vsftpd service problems. All of the
following commands are to be run as root user.
To verify that the vsftpd service is installed:
which vsftpd
You'll see the following response if the service is installed:
/usr/sbin/vsftpd
You can verify that the vsftpd service is running with the following command:
service vsftpd status
You'll see something like the following response if the service is running:
vsftpd (pid 6569) is running...
You can use the following command to install the vsftpd service if it is not installed
on your system (your machine must have internet connectivity):
yum install vsftpd
If vsftpd is installed, but is not active, you can activate the service as follows:
chkconfig vsftpd on
service vsftpd start
Use the following command to stop the vsftpd service:
service vsftpd stop
SFTP
ssh is installed and activated by default on RHE providing SFTP automatically.

/etc/hosts File
By default, Linux places the following line in the /etc/hosts file:
127.0.0.1 localhost.localdomain local host
The 1354RM-PHM EMS Server requires that the line read:
127.0.0.1 localhost localhost.localdomain
If “localhost” is not the first entry for 127.0.0.1, then the Alcatel-Lucent 1354
RM-PhM EMS Server will not be able to communicate with the MySQL
database. If the Alcatel-Lucent 1354 RM-PhM EMS Server has already been
started before this change is made, it will be necessary to restart the Alcatel-
Lucent 1354 RM-PhM EMS Server either by rebooting the system or running
the following commands:
/etc/init.d/ems.server stop
/etc/init.d/mysql.server stop
/etc/init.d/mysql.server start
/etc/init.d/ems.server start
Telnet Server
RHE does not install a telnet server by default because telnet is not secure since
passwords and all communications in a telnet session are sent in plaintext. A telnet
server can be added at install time by selecting telnet-server in the Servers->Legacy
Server group when adding packages. If the server is connected to the Internet, the
telnet server can be added after install by running the Add/Remove Programs
application or by running the following command:
yum install telnet-server
The service will then need to be enabled using the System->Services application. Go
to the On Demand tab and ensure that telnet has been selected, and then click Save.
NTP server
The NTP service needs to be enabled using the System->Service application. In the
Background Services tab, ensure that ntpd has been selected and click Save.
Windows server installation

This section describes how to install and configure a SSH service on a PhM Windows server to
support the use of SFTP for NE software loading, NE database backups/restores and PM file
transfer.
On Windows you can use cygwin or OpenSSH (which is the cygwin server and clients, but
doesn't require a full cygwin install).
OpenSSH Install
Download OpenSSH from http://sshwindows.sourceforge.net/

Run the setup program and accept the defaults (all categories).
This will install the OpenSSH server and client in an appropiate place.
OpenSSH Configuration
1. Open a command prompt and change to the installation directory (Program
Files\OpenSSH is the default).
2. CD into the bin directory.
3. Use mkgroup to create a group permissions file. For local groups, use the "-l" switch.
For domain groups, use the "-d" switch. For both domain and local, it is best to run
the command twice (remember to use >>, not >). If you use both, make sure to edit
the file to remove any duplicate entires.
mkgroup -l >> ..\etc\group (local groups)
mkgroup -d >> ..\etc\group (domain groups)
4. Use mkpasswd to add authorized users into the passwd file. For local users, use the "-
l" switch. For domain users, use the "-d" switch. For both domain and local, it is best
to run the command twice (remember to use >>, not >). If you use both, make sure to
edit the file to remove any duplicate entires.
mkpasswd -l [-u <username>] >> ..\etc\passwd (local users)
mkpasswd -d [-u <username>] >> ..\etc\passwd (domain users)
NOTE: To add users from a domain that is not the primary domain of the
machine, add the domain name after the user name.
NOTE: Omitting the username switch adds ALL users from the machine or
domain, including service accounts and the Guest account.
5. Start the OpenSSH server.
net start opensshd
6. Test the server. Using a separate machine as the client is best. If you connect but the
connection immediately gets dropped, reboot the machine with the server and try
connecting again.

5 Miscellaneous
Overview
Purpose
This chapter provides various miscellaneous information concerning Alcatel-Lucent 1354
RM-PhM Element Management System (EMS).
Contents
• Technical Assistance
• Accessing and navigating On-Line Customer Support (OLCS) web site
• Other Technical Support Services.

Miscellaneous Technical assistance
Technical assistance
Overview
Alcatel-Lucent provides the following Technical Support services:
• Remote Technical Support (RTS) – remote technical support to troubleshoot and
resolve system problems.
• On-site Technical Support (OTS) – on-site assistance with operational issues and
remedial maintenance.
• Repair and Replacement (R&R) – technical support services for device
repair/return or parts replacement
• Alcatel-Lucent On-Line Customer Support (OLCS) – online access to information
and services that can help resolve technical support requests.
Note: Technical Support Services are available 24 hours a day, 7 days a week.
For additional information regarding Alcatel-Lucent Worldwide services, refer to the
Alcatel-Lucent website at http://www.alcatel-lucent.com/solutions.
Select the appropriate category:
• Service Providers
• Enterprise
Note: Use the appropriate steps below for the above categories:
Service Providers:
1. Select Service Providers.
2. Select Services.
3. Select Network Support and Maintenance Services located in the
Maintenance section.
Note: An overview of services provided is displayed. If more detailed
information on a particular category is needed, then select the appropriate
information from the top tabs displayed.
Enterprises:
1. Select Enterprises.
2. Under the Evaluate selection at the bottom of the page, select Products
and Services.

3. At the Products and Services page, select Services.

Note: An overview of services provided is displayed. For more information,
select one of the three categories shown at the bottom of the pag: Consult &
Design, Maintain & Operate, or Integrate & Deploy.
Technical support
Many of our customers have established their own support procedures. These procedures
usually involve escalation within their own companies. However, some instances may
require additional assistance from Alcatel-Lucent. Alcatel-Lucent has been and continues
to be committed to providing excellence in technical support for its products and services.
Therefore, we provide a hierarchical support structure ready and available to solve any
Alcatel-Lucent product technical issue. When additional assistance is required, the
Alcatel-Lucent Welcome Center is the first point of contact. An Alcatel-Lucent Welcome
Center operator can direct the request to engineers that are highly trained and skilled in
resolving issues, involving Alcatel-Lucent products. Technical assistance is available 24
hours a day, 7 days a week.
Alcatel-Lucent Welcome Center

1 866 582 3688, prompt 1 (continental U.S.)
+1 (630) 224 4672 (outside continental U.S.)
(24 hours a day, 7 days a week)
By using the Alcatel-Lucent Welcome Center as the entry point for Alcatel-
Lucent support, customers will be assured of a timely and effective technical
support service.
On-line customer support
Overview
On-Line Customer Support (OLCS) is the Customer Support web site for our customers’
technical support needs. This customer web access tool provides an easy method to
access data about Alcatel-Lucent products using the World Wide Web. A customer must
first request access to this web site to gain access to the following customer support
features:
• Ask AL Knowledgebase
• Customer Assistance Request Entry System (CARES)
• Data Drop Box

• Documentation
• Downloads
• Alcatel-Lucent Alerts
• Product Change Notices
• RMA (Repair and Exchange)
Ask AL knowledgebase
The Ask AL Knowledgebase web interface feature connects you to the Knowledge
Management solutions database. The Ask AL Knowledgebase feature lets you search for
solutions by using natural language queries. Many products have an extensive set of
Solutions available. Solutions are created by technicians to provide customers with a
method to resolve issues without calling for assistance. Solutions are displayed, showing
the percentage weight or percent match, based on search criteria. Searches can be
performed on all products that are entitled, through the level of service contract customer
has for RTS services.
CARES
The CARES web interface feature makes it easy for you to submit an Assistance Request
(AR), subscribe to AR Notifications (be notified when an AR is updated), and view all
the customer ARs. The CARES feature lets you open an AR for low severity issues or
questions. Any high severity issue should be called into CTAM. Users can stay informed
about their ARs by using the flexible AR Notification subscriptions. Users can choose a
method for receiving updates: email, text messaging messages, or none. Users can choose
when updates are wanted (when the state of the AR changes, any update to the
investigation field occurs, or any time any text field is modified). Users can log into the
OLCS web site and view ARs 24 hours a day, 7 days a week.
Data drop box

The Data Drop Box feature allows Alcatel-Lucent support technicians to provide
customers with a quick method to share files. The Data Drop Box allows a technician to
provide or receive a file from a customer quickly. These files remain in place for 7 days.
Documentation
The Documentation feature on the OLCS web site contains three areas: Manuals and
Guides, Technical Notes, and Release Information.
• Manuals and Guides
This section contains the documents that are available in paper or electronic copy and are
distributed with a new product. These are the documents that are available within the
Alcatel-Lucent Product Documentation web site. The OLCS web site contains links to

the actual documents at the Customer Information Center (CIC) web site. The following
is a list of possible documents that are available from this site:
– Administration Guide
– Applications Planning Guide (APG)/Applications Planning and Ordering Guide
(APOG)
– Getting Started Guide
– Installation Manual (IM)/Installation Guide (IG)
– Modification Implementation Procedure (MIP)
– User Guide
– Alarm Messaging and Trouble Clearing Guide (AMTCG)
– Framework User Guide
– Graphical User Interface (GUI) Guide
– Maintenance Guide, Provisioning Guide
– User Operations Guide (UOG)
• Technical Notes
This section contains documents that are specific to the product and are technical in
nature. Most of these documents will provide information in product data sheets or white
papers, which are technical documents that explain the operation of a particular part of
the system. The following documents are available in this section:
– Change Notice (CN)
– Ethernet Management Guide
– Method of Procedure (MOP)
– Planning Guide
– Service Assurance Guide
– Engineering Change Procedure (ECP)
– Feature Contents
– Operations Interworking (OI) Guide
– Screen Help
– White Papers
These documents will vary from product to product.
• Release Information

This section contains documents that are specific to the release of a product. The
following documents are available in this section:
– Acceptance Documents
– Software Release Descriptions (SRD)
– Specific SRD sections
– White Papers (release specific)
– Software Compatibility
– Upgrade Paths
Downloads
Note: This may not apply to all products.

The Downloads area allows Alcatel-Lucent support technicians to provide access to
software downloads that are specific to a customers contract. This feature is only allowed
through negotiation with the Account Team and the Product Manager of the product.
Alcatel-Lucent alerts
The Alcatel-Lucent Alerts tool is a subscription-based tool that provides the same
information that our Product Notifications (PNs) did previously provide. This new
method of communication is a vehicle to share product and support issues that are of
informational, maintenance, or preventive nature. Alcatel-Lucent Alerts contain detailed
text descriptions and urgency of Alcatel-Lucent product issues that need to be quickly
communicated to customers after the deployment of a release or product.
Product change notices

The Product Change Notices (PCN) area provides information on hardware changes for a
product. There is a selection of choices to help you search for Change Notices (CNs) or
Customer Change Notices (CCNs).
Return Material Authorization (RMA) (Repair and Exchange)
Note: This may not apply to all products.

The RMA area provides a list of contact information on all Alcatel-Lucent products.
There is a “request an RMA number” on-line for most Alcatel-Lucent products. An RMA
number is required for all returned parts and this feature provides you with an easy
method to obtain the RMA number. Please check the warranty status before submitting a
request.

Miscellaneous Accessing and navigating the on-line customer support (OLCS) web site
Accessing and navigating the on-line customer support (OLCS)

web site
Description
This section provides the method to access the On-Line Customer Support (OLCS) web
site, obtain a login (if necessary), and navigate to each feature listed in this document.
Accessing the OLCS web site

To access the Alcatel-Lucent OLCS web site, enter: www.alcatel-lucent.com/support.
Once you are at this web page, select Lucent Global Support. This will bring you to the
web site where you can log in to gain access to the entitled products. Obtaining a login
for OLCS
To request a login, a customer must register, and then an email confirmation is sent
within 2 business days. The following steps tell you how to register for a login:
1. Select “Register Here” on the top right (just below the Login and Password boxes) of
the Online Customer Support (https://support.lucent.com/portal/olcsHome.do) web
site.
2. Follow this registration process:
• Select the role and accept the terms of use.
• Provide a business identification, and enter in all of the required information.
• Validate your email address.
• Confirm your business identity and set a password.
• Select content. (This will be verified against the current contract agreements.)
• Register for the selected content.
3. An email confirmation of the registration and the site access privileges is sent within 2
business days.
4. Customize the web view once you have gained access to the OLCS web site.
• After logging in, a personalized view of the Customer Support Home page
displays. This view is based on the user's and company support entitlements.

Need help while registering?
From the U.S. 1 (866) 582 3668 prompt 7
From outside the U.S. +1 (630) 218 7688
In Asia/Pacific Please contact the in-country

technical support hotline
Via email Use the email address

olcshelp@alcatel-lucent.com or use
the site’s “Contact Us” form
Use the OLCS help desk number for OLC access problems, registration
questions, password resets, navigation questions, etc.
View an OLCS website

After you have logged into the OLCS web site, a personalized view of the Customer
Support Home page is displayed. This view is based on the user's and company support
entitlements.
To set Customer Support as the default, if it is the primary destination on the
www.alcatel-lucent. com website, click “Select default home page” on the left column.
The “My Products” section provides you with quick navigation to the entitled products
and also quick access to the CARES tool. While navigating through the various tools, you
can establish bookmarks to certain tools, documents, or web pages (within OLCS) by
clicking “Add to Bookmarks.”
The Customer Support home page can be customized by selecting “Customize page
layout” and adjusting the fields to be displayed (uncheck the boxes to de-select those
elements). These fields can be adjusted at any time. The changes take effect immediately.
There are two methods to find product information. Click “My Products” to choose a
product, or click “Documentation” or “Downloads” to display a complete product listing.
When the full product list is displayed, use the alphabetic listing (default) or the category
list, whichever you prefer. Once a product is selected, a “Product Summary Page” is
displayed, which describes all of the tools and features available for this product.
Note: If content has been posted, but contract entitlements do not allow access, then the
following padlock icon is displayed:

Ask AL knowledgebase
The Ask AL web page can be accessed from the left column on the Customer Support
homepage (unless you changed the view), from the “Technical Support” section in the
center of the page, or from the “My Bookmarks” section (if it was added there). Once at
the Ask AL Knowledgebase web page, enter a question or phrase using natural language,
click the check boxes for only the products that should be searched; otherwise, all
products checked will be searched. The results that return show a percentage weight or
percent match based on the search criteria. To refine a search, add more details to the
question or phrase and answer the other questions displayed. Once you find a solution of
interest, select that solution, and the complete solution will display.
Many of the solutions are based on generated ARs or Known Problems from the SRD. To
provide quality information, solutions go through a review process before being posted.
Content can grow daily as solutions move through the review cycle.
CARES
CARES ARs are accessed from the left column on the Customer Support homepage
(unless this view was changed), under the “Technical Support” section in the center of
the page, from the “My Bookmarks” section (if CARES was added there), or from the
Quick Link section “CARES Assistance Requests,” at the bottom of the Customer
Support homepage. Product Notifications and Solutions can also be selected in this
section. These are both legacy tools. The new tools, Alcatel-Lucent Alerts and Ask AL
Knowledgebase, are discussed in other sections of this document.
When you select CARES, a general web page displays. From that page, a particular
function can be selected from the left column. To provide more information on the
selected tool, select “More” from the center column.
ARs can be viewed (using “Find an AR” or “Advanced query”), created (using “Create
an AR”), or used to report a warranty defect (using “Report a warranty defect”). The
CARES web interface has features that keep you informed about the progress of ARs.
With the flexible AR Notification subscriptions, CARES can email or send text messages
on a variety of activities regarding an AR. A notification is sent when the AR state is
changed to Created, Resolved, Closed, or Pending Customer Action. Other conditions
that generate notifications are if the following fields are updated: Investigation, Short
Description, Current Summary, Description, and Resolution. You can set up (subscribe),
remove (unsubscribe), or change these conditions at any time.
Data drop box

You can access the Data Drop Box from the left column on the Customer Support
homepage (unless your view was changed), from the “Technical Support” menu in the
center of the page, or from the “My Bookmarks” section (if Data Drop Box has been
added there). Click the “Upload a file” button in the Data Drop Box window to send a file
to the Alcatel-Lucent support technician. An email address can also be entered so that the
Alcatel-Lucent technician will be notified when the file has been sent. Click the
“Download a file” button from the Data Drop Box if the Alcatel-Lucent technician has
sent a file to be downloaded. These files will remain on the site for 7 days.
Documentation
You can access documentation by selecting a product from the “My Products” area.
Alternatively, documentation can also be accessed from the left column on the Customer
Support home page (unless this view has been changed), from the “Technical Support”
section in the center of the page, or from the “My Bookmarks” section (if Documentation
has been added there). If accessing Documentation by means other than the “My
Products” area, choose the product whose documentation you wish to access by selecting
the product from the alphabetical listing or the category list.
Once you are on the product web page, select “Manuals and Guides” from the list under
the “Documentation and downloads” section. The “Manuals and Guides” link brings you
to the Library of Manuals and Guides for the product you have chosen. The document
links bring you to the document stored in the Alcatel-Lucent Customer Information
Center (CIC) web site or to another OLCS webpage that contains the product
documentation.
Within the “Documentation and Downloads” area, the “Technical Notes” link brings you
to a web page which contains documents that are not release specific and are technical in
nature.
Also, within the “Documentation and Downloads” area, the Release Information link
brings you to a Library of Release Notes web page that contains documents which are
release specific and are listed by release. Click on these links to download or open a PDF
file.
Downloads
Important! This may not apply to all products.
You can access downloads by selecting a product from the “My Products” section.
Downloads can also be accessed from the left column on the Customer Support
homepage (unless this view has been changed), from the “Technical Support” section in
the center of the page, or from the “My Bookmarks” section (if Downloads was added
there). If accessing Downloads by means other than the “My Products” area, choose the
product whose Downloads you wish to access by selecting the product from the
alphabetical listing or the category list.
Once you are on the product web page, click the “Downloads: Electronic Delivery” link
from the list under the “Documentation and Downloads” area. Select the appropriate
release to be downloaded from the drop-down list, and click “Next.” Select the file to be

downloaded and click “Next.” On the next web page, enter the path where the file should
be downloadede and click “Download.”
Alcatel-Lucent Alerts
You can access Alcatel-Lucent Alerts from the left column on the Customer Support
homepage (unless this view has been changed), from the “Technical Support” section in
the center of the page, or from the “My Bookmarks” section (if Alcatel-Lucent Alerts is
added there).
Once you are on the Alcatel-Lucent Alerts web page, a list of products are displayed.
Click on a product to see a list of Alerts for that product. Alternatively, use the “Enter the
number of the Alert” field to find a specific Alert, or use the text search to search for
Alerts with certain words.
To subscribe to Alcatel-Lucent Alerts, click the “Alerts Subscription Page” link. Once at
the “Alcatel-Lucent Alerts Subscription” page, fill out the form and choose the product
whose alerts you would like to subscribe to.
You have the option to click “Modify Subscription” or “Cancel Subscription.” Modify
Subscription allows you to modify the Urgency, Type, and/or Products selected. “Cancel
Subscription” will stop future Alcatel-Lucent Alerts email messages.
Product Change Notices (PCNs)

You can access Product Change Notices (PCNs) from the left column on the Customer
Support home page (unless this view has been changed), from the “Technical Support”
section in the center of the page, or from the “My Bookmarks” section (if PCNs were
added there).
Once on the PCN web page, a list of PCNs is displayed. You can search PCNs by
clicking one of the following links:
• PCN cross-reference
• Search for specific text in Class A PCNs
• PCNs added or updated within the past 30 day
• Change Notice summary report
Return Material Authorization (RMA) (Repair and Exchange)
Important! This may not apply to all products.

Return Material Authorization (RMA) can be accessed from the left column on the
Customer Support home page (unless this view has been changed), from the “Technical
Support” section in the center of the page, or from the “My Bookmarks” section (if it was
added there).

Miscellaneous Other technical support services
Once on the RMA web page, a table with contact information is displayed. Use the
contact information provided or choose to fill in the online RMA request form at the
bottom of that web page.
Other technical support services

The technical support services expert workshop series
Audience: Technicians, installers, maintenance engineers, technical support personnel,
product evaluators, and anyone who has a working knowledge of the products involved
and is interested in a hands-on workshop covering advanced troubleshooting issues.
Description: The same engineers that resolve the Assistance Requests (ARs) have
developed a series of advanced, hands-on workshops that can be customized to the
unique network applications. Individual product modules will provide the knowledge and
skills to perform troubleshooting and fault-finding activities at the equipment site or from
a remote operations center. There are lab exercises using Alcatel-Lucent network
management systems to simulate real-world provisioning and troubleshooting scenarios.
In addition, general technology modules will round out the understanding of the network
element (NE) troubleshooting performed.
Objectives: Each module has specific objectives. Some overall series objectives are
listed below:
• Understand advanced network element security features
• Setup and understand interworking between Alcatel-Lucent network elements
• Perform provisioning operations and remote trouble-shooting using CIT, EMS and
TL1 interfaces.
• Analyze Performance Monitoring Data
• Understand alarm handling / alarm management
• Provision and understand system synchronization techniques
• Provision and understand protection schemes (BLSR, UPSR, 1+1 APS)
• Understand network communication issues (OSI and TCP/IP interfacing)
Length: Product Modules are scheduled for 3 days. Technology Modules are scheduled
for 1 day.
Expected Foundation Knowledge: Suggested prerequisites are listed on each module's
workshop description. Generally, customers should have a basic understanding of digital
fundamentals and lightwave transmission systems. In addition, customers should have

Miscellaneous Other technical support services
taken a previous Alcatel-Lucent Operating & Maintenance course or have equivalent

experience with operations and maintenance issues related to the product
Activities Prior to Workshop Delivery: The effectiveness of this workshop series relies
on the fact that it allows a customer to address the issues experienced in their network
today. To achieve this, prior to the workshop, a conference call will be set up with the
engineers that will facilitate the workshop. During this call, the logistics of simulating the
customer's network environment will be discussed.
Workshop Location: This workshop will be delivered in the Customer Advocate System
Test Labs in Westford, MA. The format is 75% hands-on lab exercises, reinforced with
25% classroom instruction.
How to Sign Up:
To enroll in the training course:
• Within the United States,
– Visit https://training.alcatel-lucent.com
– Call 1 (888) 582 3688: Prompt 2.
• Outside the continental United States,
– Visit https://training.alcatel-lucent.com
– Contact your in-country training representative
– Call: +1 (407) 767 2798
– Fax: +1 (407)767 2677
• Enter “Advanced Workshops” in the search menu and click “Go.”
• Choose which Advanced Maintenance Workshop you’d like to register for by clicking
on the link.
• Read the workshop description(s) and follow the links to register.


1354rm-Phm r7 5 SRD 8dg60488aaaafmzza

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1354rm-Phm r7 5 SRD 8dg60488aaaafmzza

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent 1830

Photonic Service Switch (PSS)

SOFTWARE RELEASE DESCRIPTION

Copyright © 2008-2010 Alcatel-Lucent. All Rights Reserved.

Interference Information: Part 15 of FCC Rules

Alcatel-Lucent - Proprietary iii

Dual client port protected services on PSS-1 ................................................................ 1-10

iv Alcatel-Lucent - Proprietary 8DG60488AAAA

Windows server installation .......................................................................................... 4-19

8DG604888AAAA Alcatel-Lucent - Proprietary v

How to use this document

Alcatel-Lucent - Proprietary 1-1

Related information errata

1-2 Alcatel-Lucent - Proprietary 8DG60488AAAA

Pg. 5-24 “1696R and 1830 PSS interoperability”

OUT2 FEC Mode = EFEC

1-4 Alcatel-Lucent - Proprietary 8DG60488AAAA

8DG604888AAAA Alcatel-Lucent - Proprietary 1-5

Network Element Support in Release 7.5

PhM Topology View icons NE releases supported

1-6 Alcatel-Lucent - Proprietary 8DG60488AAAA

New Features in Release 7.5 (since R7.0.50)

New Features in Release 7.0.50 (since R7.0.2)

New Features in Release 7.0.2 (since R7.0.1)

New Features in Release 7.0.1 (since R7.0)

• PSS-32 R2.0 / 1696R R5.4 mid-span meet

8DG604888AAAA Alcatel-Lucent - Proprietary 1-7

New Features in Release 7.0 (since R6.1.x)

• PSS-1 GBE R2.0

• PSS-1 MD4H R1.0

• PSS-32 R2.0 / PSS-1 MD4H R1.0

Restrictions and Limitations

1-8 Alcatel-Lucent - Proprietary 8DG60488AAAA

Some commissioning wizards not supported for 1830 PSS-32

PSS-1 MD4H single fiber mode services with cross regen

Service creation involving regens

8DG604888AAAA Alcatel-Lucent - Proprietary 1-9

Service creation via xml file import

Dual client port protected services on PSS-1

Creation of services on 1830 PSS-32 NEs limited to R2.0

11G quad port pluggable anyrate 4-client transponder (11QPA4)

PSS-32 Network with PSS-16 spur

PSS-1 GBE Single fiber mode

1-10 Alcatel-Lucent - Proprietary 8DG60488AAAA

8DG604888AAAA Alcatel-Lucent - Proprietary 1-11

Issue Severity Problem

Issue Severity Problem

Issue Severity Problem

Alcatel-Lucent - Proprietary 2-1

36120 Minor Existing Logical links recreated on service discovery

Issue Severity Problem

Issue Severity Problem

26408 Minor Warning after import with no keying

8DG604888AAAA Alcatel-Lucent - Proprietary 2-3

Alcatel-Lucent - Proprietary 3-1

Issue Severity Problem Work Around

32832 Major PSS-1 MD4H single fiber mode to

3-2 Alcatel-Lucent - Proprietary 8DG60488AAAA

36398 Minor CAD/SVAC port not put in AINS state

33049 Minor For 1830 PSS-32 NEs, there is an

8DG604888AAAA Alcatel-Lucent - Proprietary 3-3

32808 Minor PSS-32 11STGE12 and 11STMM10 Y- Unmanage both unprotected

8DG604888AAAA Alcatel-Lucent - Proprietary 3-5