Customer Release Note - FPCT - R1.3EP1_SU2 - V2.0

© Nokia Siemens Networks Company Confidential 1 (17)

Customer Release Note Product Family: FlexiPacket Product: FlexiPacket Commissioning Tool Release: R1.3 EP1 (SU2) Customer: Generic Delivery


Table of Contents 1. Scope ............................................................................................................................................. 3 2. Product description ......................................................................................................................... 4 3. COMPATIBILITY ............................................................................................................................ 8 4. Product composition ....................................................................................................................... 9 5. HINTS AND PROCEDURES ........................................................................................................ 10 6. Limitations .................................................................................................................................... 13

Contact: Contact your local Nokia Siemens Networks support

Summary of changes:

July 2011 1.0 First version at FPCT1.3EP1 P7 October 2011 2.0 Second version at FPCT1.3EP1 P8 February 2012 3.0 Third version for SU2 release


1. SCOPE

The following SW releases are in scope of this document: FlexiPacket Commissioning Tool: Release: 1.3 EP1 SU2 (Previous official release: 1.3 EP1) Release date: 29 February 2012


2. PRODUCT DESCRIPTION

2.1 FlexiPacket Commissioning Tool

FlexiPacket Commissioning Tool (FPCT) supports easy and guided first installation and upgrade procedures of the FlexiPacket system (IDU, ODUs). FlexiPacket Commissioning Tool configures all the appliances of the sites (IDU and ODUs) congruently with single user inputs. It can also be used without any IDU support connecting directly the laptop to the ODU. Starting from version R1.2, FP Commissioning Tool is no longer part of the LCT. FPCT is delivered as a standalone application and an independent setup application is present. FPCT set-up installs all the needed applications for all functionalities.

2.2 FlexiPacket Commissioning Tool Operation Modes

Two modes of operation are foreseen: • Assisted • Advanced

In the Assisted Mode the user is forced to follow a very well predefined sequence, answering to precise questions and filling showed fields. This modality is mainly intended for non advanced user and for site first installation phase. Assisted modality runs as offline configurator. Thus it’s not needed to be directly connected with the devices. At the end of the configuration steps, the user can decide to perform all the configurations to the devices (in this case a connection is required) or to save all the settings into a FPCT configuration file. This FPCT configuration file can be loaded in a second time to resume all the configurations into the Flexi Packet Commissioning Tool. In Advanced Mode even if the actions/views are presented in an ordered sequence to be performed from the first to the last, in the advanced modality, user can jump from one view to another one without any constraint. This modality is intended for an advanced user or for FP Commissioning Tool usage for site maintenance/troubleshooting. NOTE: In the Assisted modality the “restore” functionality for both IDU and ODUs has been removed from the items in the menu. The only possibility is to load a CT configuration file (in the log-in phase as already implemented). The “restore” functionality is always present in the Advanced mode and mainly intended for IDU Replacement in case of failure.

2.3 New supported equipments

FlexiPacket Multi Radio 2.4 (only in Assisted Mode)


2.4 Main new features and services

Configuration management - FPMR 2.4 new System Type Support O 1+0 (already supported by FPMR 2.1) O 1+0 RING O 1+1 SD 2 CABLES (already supported by FPMR 2.1) O 1+1 FD 2 CABLES (already supported by FPMR 2.1) O 2+0 FD 2 CABLES (already supported by FPMR 2.1) O 2+0 XPIC 2 CABLES (already supported by FPMR 2.1) O 1+1 HSBY - CCM BASED (SIMILAR 1+1 HSBY already supported by FPMR

2.1) O 1+1 HSBY - STANDALONE O 1+1 HSBY 1 CABLE O 2+0 XPIC 1 CABLES

2.5 Complete list of supported feature

See in the next pages




3. COMPATIBILITY

3.1 Combinations & Interworking List

Combinations & Interworking which are supported on C T1.3 EP1, they are also supported on CT 1.3SU2

Assisted Mode FlexiPacket Hub A2200 R 4.5

FlexiPacket Hub A2200 R 4.5 EP1

FlexiPacket Hub A2200 R 5.0

FlexiPacket Hub A1200 R 5.0 (drop 1)



FlexiPacket FirstM

ile 200 R 1.0 EP1

FlexiPacket FirstM

ile 200 R 2.0

FlexiPacket Hub 800 R2.0

FlexiPacket Hub 800 R2.0 EP1

FlexiPacket Hub 800 H1.0

FlexiPacket Radio R1.2 SU1

FlexiPacket Radio R1.3

FlexiPacket Radio R1.3 EP1

FlexiPacket Radio HC R1.4.6

FlexiPacket Multi Radio R2.1

FlexiPacket Multi Radio H2.1

Reduced support for FlexiPacket Multi Radio

R2.4

Supported Assisted Mode combinations

FlexiPacket Radio R1.2 SU1 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Radio R1.3 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1FlexiPacket Radio R1.3 EP1 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Radio HC R1.4.6 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Multi Radio R2.1 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Multi Radio H2.1 CT1.3

EP1


SU2

CT1.3

SU2

CT1.3

SU2

CT1.3

SU2

CT1.3

SU2

Advanced Mode FlexiPacket Hub A2200 R 4.5

FlexiPacket Hub A2200 R 4.5 EP1

FlexiPacket Hub A2200 R 5.0




FlexiPacket FirstM

ile 200 R 1.0 EP1

FlexiPacket FirstM

ile 200 R 2.0

FlexiPacket Hub 800 R2.0

FlexiPacket Hub 800 H1.0

FlexiPacket Radio R1.2 SU1

FlexiPacket Radio R1.3

FlexiPacket Radio R1.3 EP1

FlexiPacket Radio HC R1.4.6

FlexiPacket Multi Radio R2.1

FlexiPacket Multi Radio H2.1

Red

uced support for FlexiPacket Multi Radio

R2.4

Supported Advanced Mode combinations

FlexiPacket Radio R1.2 SU1 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Radio R1.3 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1FlexiPacket Radio R1.3 EP1 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Radio HC R1.4.6 CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1


EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

CT1.3

EP1

FlexiPacket Multi Radio H2.1 CT1.3

EP1 CT1.3 EP1 Supported on CT1.3 EP1, also be supported on CT1.3 SU2 CT1.3 SU2 only support on CT1.3SU2


4. PRODUCT COMPOSITION

The released software is delivered through suitable packages.

LTU= License To Use

Items SW Version

SW Build CT_1_3_SU2_00

Items DescriptionT555CTCD.13EP1 FlexiPacket Comm Tool R1.3 EP1 (CD) T555CTE.13EP1 FlexiPacket Comm Tool R1.3 EP1 (e-media) T555CTLTU13EP1 FlexiPacket Comm Tool R1.3 EP1 (LTU)


5. HINTS AND PROCEDURES

Platform FPCT runs on notebook. FPCT is released on Windows XP SP2 or higher. FPCT is released on Windows Vista SP1, Business Edition and higher ones FPCT is released on Windows 7, Professional Edition and higher ones User account When you user account with administrative rights, please follow below operation. For WinXP, can be used any name as admin account. For Win7 and Vista system admin account can be used but you user account control must be sot to low. License manager for CT CT only support License manager tool on XP system, because license manager tool cannot be installed on Win7/Vista. SW upload with win7 pack1 With win7 pack1, FM200/FPH800/FPH800H can’t upload sw. It’s NE problem, the root cause is still under investigation. Commissioning Tool assisted mode for FlexiPacket FirstMile 200 For FlexiPacket FirstMile 200, the step "Validate" doesn't check the configuration in relation to the license, user must verify the relation between license and configuration by himself. Combinations between FM200/FPH800 and FPMR2.1 So far commissioning tool can support combinations between FM200/FPH800 and FPMR2.1SU1/SU2 Alignment without traffic broken So far, due NE issues, commissioning tool can support alignment but sometimes a short-time traffic broken will happen. Detail info is below

Alignment Support

Traffic influence

FM200 R1.0EP1 Y Short‐time broken

FM200 R2.0 Y FPMR SU1: No traffic broken FPMR SU2: short‐time broken sometimes

FPH800 R2.0 Y FPMR SU1: No traffic broken FPMR SU2: short‐time broken sometimes

FPH800H R1.0 Y Short‐time TDM traffic broken and alarm appear

A1200 drop1 Y Short‐time broken



A2200 R4.5 Y 2+0 XPIC: 3 min traffic broken Other System type: short‐time broken

A2200 R4.5EP1 Y 2+0 XPIC: 3 min traffic broken Other System type: short‐time broken

A2200 R5.0 Y 2+0 XPIC: 3 min traffic broken Other System type: short‐time broken


System type for different ODU System type of FPMR R2.1 SU1 are the following:

• 1+0 • 1+1 HSBY • 1+1 FD • 1+1 SD • 2+0 FD • 2+0 XPIC

All the above mentioned system types can be configured on FM200, FH800, A1200, A2200. Notes: 1+0 Ring has been dropped from FPMR R2.1. It has been introduced in FPMR R2.4. System type of FPR R1.3 supports only

• 1+0 • 1+1 HSBY

System type of FPR HC supports only

• 1+0 • 1+1 HSBY

System type of hybrid versions (IDU and ODU) support

• 1+0 • 1+1 SD • 1+1 FD

System types of FPMR R2.4 are the following

1+0

1+0 Ring

1+1 SD 2 cables

1+1 FD 2 cables

2+0 FD 2 cables

2+0 XPIC 2 cables

1+1 HSBY - CCM Based

1+1 HSBY - Standalone

1+1 HSBY 1 cable

2+0 XPIC 1 cables

Supported System types of FPMR R2.4 standalone Assist mode are the following

1+0

1+0 Ring

1+1 HSBY - CCM Based

1+1 HSBY - Standalone1

1+1 HSBY 1 cable

1 Standalone means L2 Switch unaware. This implies the possibility to have either NSN IDUs or 3rd party ones.


Co-located IDU So far only FPH 1200 can support adding co-located IDU LLDP with FPR1.2 Because FPR1.2 don’t support LLDP function, the functions related to LLDP are not supported by Commissioning tool. For example, alignment, line-up and so on. SW version between Commissioning Tool R1.3EP1 and FPH800 R2.0 Commissioning tool EP1 P8 load can fully support FPH800R2.0 maintenance load and P8 load. For FPH800 R2.0 P7, commissioning tool can support to upgrade from P7 load to P8 load. Note: Commissioning Tool R1.3EP1 P8 load can’t support alignment, if FPH800 R2.0 use P7 load.


6. LIMITATIONS

6.1 Known Bug and No Limitation

• FR_0000009613 Commissioning Tool 1.3.42 advanced + FPR R1.3EP1 (1.3.13): license name is not friendly and detail info is empty License detail info doesn’t match license capability perfectly.

• FR_0000009565 Commissioning Tool 1.3.42 + A2200+ FPMR R2.1 (2+0)XPIC

advance: Traffic break about 3 minutes when implement alignment on 2+0 XPIC mode As in the title, it is a NE issue, because this problem still exists with Weblct.

FR_0000011984 CT 1.3.62: FP FM200 R2.0 + FPMR R2.4 Assisted mode: if add multi single cable ODU to IDU,CT will abort when upgrade the first single cable failed, This is the Commissioning Tool behavior, Commissioning Tool will not continue to add the second group single cable ODU if add the first group single cable ODU failed by any reason. Please fix the first group ODU problem and then run the commissioning Tool again.

FR_0000012148 CT 1.3.64 FPH800 + FPMR R2.4 Assisted mode: ODU down

load failed, FTP login failed or cannot create FTP client service Some times ODU download failed by FTP login failed or cannot create FTP client service on Vista OS. Please run the configuration again if you have this problem.

FR_0000011904 CT1.3.61: FPH800 + FPMR R2.4: cannot select ODU system

type to 1+0 type The default system type is 1+0, if you want to set 1+0 system type, please don’t select anything on Step)3 ODU system type setting

FR_0000011491 CT1.3.56: FPH800 R2.0 + FPMR R2.1 Assisted mode: The

OU RF port operation status is down when configuration mode is 2+0 FD or 1+1 FD When this issue happens, you must HW reset ODU to make it work. For CT, this issue happen, line-up can’t work.

FR_0000011485 CT1 1.3.56: FPH800 R2.0 + FPMR R2.4 Assisted mode:

Radio Link down, don't connect remote IDU. When this issue happens, you must HW reset ODU to make it work.

FR_0000012253 After adding directed ODU successfully and before adding

Co-located ODU. CT shows Connect direct ODU timeout (longer than 2 minutes) Completed Major Add single cable system type ODU failed on A1200 since Ping Co-located ODU failed.


6.2 LIMITATIONS caused by other products

6.2.1 Limitation caused by FTI Tool Known Issue

• FR_0000006254 Commissioning Tool R1.3.7: (A1200 Advanced mode) FTI doesn't support com4

Solution: Use com1 should be better to insert the FR related to the NE when it is possible

• FR_0000006249 Commissioning Tool R1.3.7: (A1200 Advanced mode) CT

can't identify the right IP address when run FTI When one PC has multiple card. FTI can’t identify the right network card. Solution: Make one network card available. • FR_0000006146 Commissioning Tool R1.3.5: (A1200 advanced) console

port has no response when execute FTI Solution: Restart FTI and run it again.

6.2.2 Limitation caused by FPR 1.3 Known Issue

• FPR1.3.8 Configuration ODU and plug it onto another IDU will make ODU crash Solution: Restart ODU or restore to factory default setting.

6.2.3 Limitation caused by FPMR 2.1 Known Issue

• FPR2.1.5670 Sometimes ODU port is down when configure 1+1 FD When this issue happens, ODU need to be restated to work properly • FPMR 2.1 SU1- 2+0 all - sometimes, after ODU switch sw, there is 3s of loss of

traffic ODU switch sw will cause 3 sec. of loss of traffic • FPMR 2.1SU2: Swap&repair procedure (using CT 1.3EP1) causes temporary

loss of traffic Sometimes, alignment will cause temporary loss of traffic. This is an issue of FPMR2.1, and will be fixed on FPMR2.4.

6.2.4 Limitation caused by FPMR2.4 Known Issue

• FPMR2.4 sometimes radio port is down after configure via Commissioning Tool

Solution: restart ODU

• Other known issues: Acting Master / Acting Slave ODU configuration is not always recovered after restart In 1+1FD/SD and in 2+0XPIC/FD system types, the Acting Master / Slave configurations of the ODU determines how the device should behave after a restart; however the ODU sometimes does not start according to the configured role


because of an open problem. This behavior does not affect system operation and performance as the only effect is that the ODUs start up with a negotiated role different from the configured one. Problems in backup and restore from FPMR 2.1 Build 644 to FPMR 2.1 Build 5703 Backup procedure in FPRM 2.1 Build 644 does not save some configuration parameters such as synchronization settings, Header Compression parameters, so it is not advisable to restore a configuration saved in FPRM 2.1 Build 644 on top of FPMR 2.1 SU1 Build 5703.

6.2.5 Limitation caused by FirstMile200 Known Issue

• CCM alarms always reported in active alarm list CT will show wrong alarm when HSBY Function is enabled. This is due the fact the ODU has disabled the Radio Link, so the Radio Link Down alarm will be active on FM200 Standby Port.

• FM200 EP1 Patch Load issue for reset system

After create LPG, it is needed to wait for 10s to save configuration. If not , restarting the NE configuration will be lost

Solution: In CT assisted mode it will wait for 10s, before restart NE • FM200 EP1 Patch Load issue for P-CCM loss occur in 1+1 HSBY setup after

change the port mode in IDU Adding the ODU it will be changed the port mode, this operation will make MAC table empty. Finally, PCCM will be not available. Solution: CT will let IDU to re-study MAC.

• FM200 EP1 Patch Load issue for IDU crash and not able to access WebLCT

LLDP is low priority. If NE is too busy to deal with LLDP, NE crashes. The issue will lead the CT to lose connection with IDU/ODU. Solution: NE must be restarded.

• FirstMIle200 EP1_timing: Automatic is not in the PHY master slave selection

Due the fact the CT has this option, using that unexpected result will be shown • FirstMIle200 EP1_service: CESoP service can't be deleted when doing

alignment in CT. This issue make CT alignment failed.

• Sometimes Mib can't be read or written

Sometimes WebLCT will show “load Mib node failed”, after using commissioning tool to configure FM200. Solution: Restart IDU.

• FM200R1.0EP1:Add LPG (LPG2) Failed with Commissioning Tool

Solution: Restart IDU. • FirstMIle200 R2.0_timing: No SSM message is sent out when the IDU is free

run.


FM200 doesn't send out SSM message when the system is free run, so the ODU can't lock to the IDU. This issue will make clock unlock between IDU and ODU.

• FFM200: sometimes Upgrade software failed when configure via Commissioning Tool Root Cause: Sometimes, Upgrade software failed if upgrade a lot of times. Solution: Restart IDU.

Other known issues: FM200 can’t upload sw with win7 service pack1. With other OS, it’s ok to upload sw.

6.2.6 Limitation caused by FPH800 R2.0 Known Issue

• Sometimes after configuration with assist mode, can't see ODU info with advance mode. The root cause is that LLDP doesn’t work well.

Solution: Restart IDU.

6.2.7 Limitation caused by FPH800H R1.0 Known Issue

• FPH800H: Change the port mode will make TDM traffic break down for a short time This issue will lead to a short-time traffic broken and LOF alarm, when execute alignment.

6.2.8 Limitation caused by A1200 Known Issue

:A1200R5.0 + FPMR2.4 Assisted mode: System type 1+1SD, ODU E-CCM LOSS, Radio Link down, not possible to connect remote IDU Not possible to configure 1+1 SD system type with A1200 on Commissioning Tool since E-CCM loss.

After adding directed ODU successfully and before adding Co-located ODU. CT shows Connect direct ODU timeout (longer than 2 minutes) Add single cable system type ODU failed on A1200 since Ping Co-located ODU failed.


• Disclaimer

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved.

Documents

Customer Release Note - FPCT - R1.3EP1_SU2 - V2.0