FlexiPacket MultiRadio CRN_2 5_SU1.pdf

Nokia Siemens Networks Company Confidential

Customer Release Note

Product Family: FlexiPacket Microwave

Product: FlexiPacket MultiRadio

Release: 2.5 SU1

Customer: Generic Delivery

Issue:3.1 Issue date: July 2012


MWT Product Management July 2012

Page 2 of 39

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 2009. All rights reserved.


July 2012

MWT Product Management Page 3 of 39

1. SCOPE .......................................................................................................................... 7

2. PRODUCT DESCRIPTION ........................................................................................... 7

3. MAIN FEATURES ......................................................................................................... 8

3.1 Features introduced with Rel 2.1 .................................................................................................................. 8

3.2 New features introduced with SW Rel 2.4 .................................................................................................. 9

3.3 Content of SW Rel. 2.4 SU1 ............................................................................................................................ 9

3.4 New features introduced with SW Rel 2.5 .................................................................................................. 9

3.5 Content of SW Rel 2.5 SU1 Content: .......................................................................................................... 10

3.6 Hardware ........................................................................................................................................................... 12

4. COMPATIBILITIES ..................................................................................................... 12

4.1 Network Management .................................................................................................................................... 13

5. PRODUCT COMPOSITION ........................................................................................ 14

6. FIXED BUGS .............................................................................................................. 20

7. LIMITATIONS ............................................................................................................. 22

7.1 XPIC at 7 MHz ................................................................................................................................................... 22

7.2 ODU-ODU Synchronization Source ............................................................................................................ 22

7.3 Squelch and reboot of ODU needed after System Type change ........................................................ 22

7.4 Squelch of Acting Master ODU in 2+0FD/XPIC ........................................................................................ 22

7.5 Limitations in use of 2+0 FD with 7MHz Channel Spacing ................................................................... 22

7.6 Backup and restore from FPMR 2.1 (Build 644) to FPMR 2.1 SU2 (Build 5717) and 2.4 / 2.4 SU1 . ............................................................................................................................................................................. 23

7.7 Change of channel spacing in 1+1 HSBY single cable system type ................................................. 23

7.8 PM Ethernet Counters and Ethernet Throughput report bad values ................................................. 23

7.9 Wrong upload of SW Load instead of Security Add-On ....................................................................... 24


July 2012


8. HINTS AND PROCEDURES ...................................................................................... 24

8.1 ODU-ODU cables ............................................................................................................................................. 24

8.2 Correct configuration of QoS for management channel ...................................................................... 24

8.3 Licensing ........................................................................................................................................................... 25

8.4 Private interface details ................................................................................................................................. 25

8.5 Public interface detail and procedures for DCN ..................................................................................... 25

8.6 IPv4/IPv6, Address (L2/L3 Addresses), MPLS label and Ether Type based classification on FPMR ............................................................................................................................................................................. 26

8.7 XML files supported in FPMR 2.1 / 2.1 SU2 ............................................................................................. 26

8.8 CESoP traffic with Jumbo frames ............................................................................................................... 26

8.9 Upgrade of SW Release from 2.1 SU2 to 2.4 SU1/2.5/2.5 SU1 ............................................................. 27

8.10 Removal of multiple Web LCT instances from Windows Control Panel .......................................... 27

8.11 2+0XPIC / 2+0FD: system stabilization time after start up ................................................................... 28

8.12 IE8 Browser settings for correct WebLCT login ..................................................................................... 28

8.13 CCM Time Interval Configuration on ODUs and IDUs ........................................................................... 28

8.14 STP disable on IDU before execution of ODU Loopbacks ................................................................... 29

8.15 ATPC: correct settings for Min and Max TX Power ................................................................................ 29

8.16 XPIC operation when one polarization is down ...................................................................................... 29

8.17 Notice about the use of IDU FPH800 P+E Interfaces ............................................................................. 30

8.18 SW downgrade from 2.4 SU1/2.5 to 2.1 SU2 ............................................................................................ 31

8.19 Interoperability of 2+0 XPIC Ring with G.8031 Connection Protection mechanism on FPH800 2.0EP1 ............................................................................................................................................................................. 31

8.20 Use of Header Compression with CESoP services using VLAN translation option (single tag) and Dynamic MAC address assignment ................................................................................................................ 31

8.21 Use of Header Compression rules 31 and 32 for CESoP services with VLAN transparent option (double tag) .................................................................................................................................................................... 31

8.22 Notes on Header Compression rules 29-34 to be used with CESoP / SAToP / MEF8 traffic ....... 32

8.23 2+0 XPIC Ring: partial restore indication after backup and restore operation on Slave ODUs . 32

8.24 Note about SW Upload and SW Bank Switch operations ..................................................................... 33

8.25 Note about switch of Packet �� Hybrid operational mode ................................................................... 33


July 2012


8.26 Configuration of networking parameters of co-located ODU in Single Cable System Types with FPMR 2.4 ............................................................................................................................................................... 33

8.27 Swap and repair of the co-located ODU with FPMR 2.5 /2.5 SU1 ....................................................... 35

8.28 Note about the RF Loopback command ................................................................................................... 39


July 2012


History Issue Date Author Notes 1.0 February 2011 NWS MWT ProdM First Issue 1.1 February 2011 NWS MWT ProdM Errata corrige Chapter 4 Compatibility 1.2 March 2011 NWS MWT ProdM Minor revision 1.3 June 2011 NWS MWT ProdM Updated with Rel. 2.1 SU1 (Standard Update 1) 1.4 August 2011 NWS MWT ProdM Updated with Rel. 2.1 SU2 (Standard Update 2) –

updated also limitations list 2.0 October 2011 NWS MWT ProdM Updated with Rel 2.4 2.1 February 2012 NWS MWT ProdM Updated with Rel 2.4 SU1 (Standard Update 1) –

Updated Limitations and Hints and procedures chapters 3.0 March 2012 NWS MWT ProdM Updated with Rel 2.5 3.1 July 2012 MPP MWT ProdM Updated with Rel 2.5 SU1 (standard update 1)

Updated also Hints and Procedures and limitation lists.


July 2012


1. SCOPE The following SW releases are in scope of this document:

FlexiPacket MultiRadio: Release: 2.5 (build 2.5.6316)

(Previous official release: Rel. 2.5)

Release date : 13th July 2012.

The following hardware are in the scope of this document:

FlexiPacket MultiRadio:

-ETSI: 3.5, 6U, 6L, 7, 8, 11, 13, 15, 18, 23, 26, 38 GHz

- ANSI: 6L, 6U, 11, 18, 23 GHz

- Japan: 11, 15, 18 GHz

2. PRODUCT DESCRIPTION

Nokia Siemens Networks FlexiPacket Microwave is a packet microwave system designed to meet the requirements of evolved transport networks with the target of minimizing the operator Total Cost of Ownership (TCO). It joins together the benefits of an advanced scalable microwave radio and of a real carrier grade Ethernet nodal solution.

FlexiPacket Microwave is the mean to deploy a cost-effective microwave infrastructure for 3G, WiMAX and LTE backhaul, high speed wireless Internet networks, fixed broadband access backhaul and private wireless networks.

FlexiPacket Microwave is conceived both for pure packet and TDM+Packet hybrid networks.

FlexiPacket Microwave family includes the following:

- FlexiPacket Radio (ODU)

- FlexiPacket MultiRadio (ODU)

– FlexiPacket FirstMile 200 (IDU)

- FlexiPacket Hub 800 (IDU)


July 2012


FlexiPacket MultiRadio

FlexiPacket MultiRadio is the new outdoor unit of Nokia Siemens Networks FlexiPacket Microwave: a new packet microwave system designed to meet the requirements of evolved transport networks in terms of flexibility and efficiency, enhanced with new features and system types, to address both access and aggregation part of the network.

3. MAIN FEATURES Following main new features are available with FlexiPacket MultiRadio

Software

- Capacity scalable up to 450 Mbps

- Flexible channel bandwidth 7/14/28/56 MHz

- Adaptive Modulation 4/16/32/64/128/256 QAM

- ATPC

- 1+0/1+1 HSBy (CCM based)

- 10/100/1000BaseT interface

- Synchronous Ethernet

- Dual mode power feeding (P+E or direct PS)

- Configuration, Performance, Fault Management with SNMP

- File transfer with XML/FTP (performances, inventory, configuration backup/restore)

- Ethernet counters, Tx and Rx RSPI

- NetViewer Element Manager, Element manager for FlexiPacket Microwave

- Support for Installation, line-up and commissioning of FlexiPacket Microwave

3.1 Features introduced with Rel 2.1 - 2+0 XPIC

- 1+1 Freq./Space Diversity

- 2+0 radio link aggregation (load sharing) with XPIC or FD

- Header compression, capacity increase up to 600 Mbps

- E1 transport enhancement

- HW ready for Hybrid mode


July 2012


- N+0 supported with V-LAN distribution on FlexiPacket Hub or FirsMile IDUs

- Quality of Service: 8 queues, additional classification criteria (MPLS)

- Management: Ethernet counters, WebGUI – NE embedded element management

3.2 New features introduced with SW Rel 2.4

- North America standard support

- 1+1 HSBy “single cable”

- 2+0 XPIC “single cable”

- 3.5 MHz channel spacing (@3.5GHz)

- Jumbo frames support (10240 bytes)

- 2+0 XPIC / 1+1 HSBy integrated with FlexiBTS (“ HSBY standalone”)

- High Throughput profiles

- “1+0 ring” (SynchE protection)

Management

- Ethernet Performance Monitoring

Note: Supported system types for North America standard in Rel 2.4:

- 1+0 - 1+1 FD - 2+0 FD - 2+0 XPIC - 1+1 HSBY (CCM based)

3.3 Content of SW Rel. 2.4 SU1 Content: see Fixed Bugs chapter.

3.4 New features introduced with SW Rel 2.5

- New System Types:

o “2+0 XPIC Ring” (SynchE protection) o 2+2 XPIC

- Extension of the supported System Types to ANSI Profiles (see table below) - New custom profiles for Japan: 20MHz/4QAM; 20MHz/16QAM; 40MHz/64QAM - Security Add-On


July 2012


- Packet Fragmentation - Ethernet Throughput Performance Monitoring, PRx monitoring - ATPC RSL Threshold Setting capability

Here below the supported system types in Rel 2.5:

System type Hw

protection

Mode

SVR Support

Japan profiles ETSI 3.5 MHz

bandwidth

ETSI 7MHz

or ANSI 10MHz

bandwidth

All other

bandwidths

(ETSI/ANSI)

1+0 -- x x x x

1+0 Ring -- Not supported Not supported x x

1+1 FD 2c mode1 Not supported Not supported x x

1+1 SD 2c mode1 Not supported Not supported x x

2+0 FD 2c mode1 Not supported Not supported x x

2+0 XPIC 2c mode1 Not supported Not supported Not supported x

mode3 Not supported Not supported Not supported x

2+0 XPIC Ring 2c mode3 (*) Not supported Not supported Not supported x


1+1 HSBY 2c mode1 x Not supported x x

mode3 x Not supported x x

2+0 XPIC 1c -- Not supported Not supported Not supported x

1+1 HSBY 1c -- Not supported Not supported x x

2+2 XPIC 2c mode3 Not supported Not supported Not supported x Legenda:

1c= single cable (1 GE cable)

2c= double cable (2 GE cables)

Mode 1= for interoperability with IDUs which support the protection mechanism e.g. IDU FirstMile, FlexiPakcet Hub 800, A-series Indoor Units.

Mode 3 = for interoperability with a generic L2 devices which implements Learning, Forwarding and Filtering (also called „HSBY standalone“)

(*): due to a limitation in the current implementation of G.8031 Connection Protection mechanism released in FPH800 2.0 EP1, 2+0 XPIC Ring „mode 3“ must not be used in conjunction with this FPH800 functionality; in this case, 2+0 XPIC Ring „mode 1“ shall be used instead

3.5 Content of SW Rel 2.5 SU1 Content: Rel 2.5 SU1 includes bug fixing and some new functionality:

- New System Types: 2+0 FD Single Cable - Procedure for remote ODU squelch in case of local RX failures in XPIC System Types.

A new SW procedure was introduced in FPMR 2.5 SU1 to ensure stable operation with 50% capacity of XPIC systems in case of failure / power down of one ODU: this procedures automatically puts in squelch the remote TX of the ODU on the same polarization of the local


July 2012


one that has a failure or is powered off. Due to the operation times of this SW procedure, there is a typical outage of traffic of 500ms; in sporadic cases up <1.5s were measured.

Please Note: see also fixed bugs chapter for Rel 2.5 SU1 content.

Here below the supported system types in Rel 2.5 SU1:

System type Hw

protection

Mode

SVR Support

ANSI profiles

for Japan

ETSI 3.5 MHz

bandwidth

ETSI 7MHz or ANSI

10MHz bandwidth

All other

bandwidths

1+0 -- x x x x

1+0 Ring -- Not supported Not supported x x

1+1 FD 2c mode1 (*) Not supported Not supported x x

1+1 SD 2c mode1 (*) Not supported Not supported x x

2+0 FD 2c mode1 (*) Not supported Not supported x x

2+0 FD 1c -- Not supported Not supported x x

2+0 XPIC 2c mode1 (*) Not supported Not supported Not supported x


2+0 XPIC Ring 2c mode3 (**) Not supported Not supported Not supported x

mode1 (*) Not supported Not supported Not supported x

1+1 HSBY 2c mode1 (*) x Not supported x x

mode3 x Not supported x x

2+0 XPIC 1c -- Not supported Not supported Not supported x

1+1 HSBY 1c -- Not supported Not supported x x

2+2 XPIC 2c mode3 Not supported Not supported Not supported x

Legenda:

1c= single cable (1 GE cable)

2c= double cable (2 GE cables)

Mode 1= for interoperability with IDUs which support the protection mechanism e.g. IDU FirstMile, FlexiPakcet Hub 800, A-series Indoor Units.

Mode 3 = for interoperability with a generic L2 devices which implements Learning, Forwarding and Filtering (also called „HSBY standalone“)

(*): Mode 1 HW Protection must be used only with CCM Time Interval=100ms on ODU and IDU

(**): due to a limitation in the current implementation of G.8031 Connection Protection mechanism

released in FPH800 2.0 EP1, 2+0 XPIC Ring M3 must not be used in conjunction with this FPH800

functionality; in this case, 2+0 XPIC Ring M1 shall be used instead


July 2012


3.6 Hardware • FlexiPacket MultiRadio is a new hardware respect to FlexiPacket Radio.

Note: FlexiPacket MultiRadio is compatible with “SRAL XD type” antennas. An adapter is provided to adapt to “FlexiHopper type” antennas. Note: Ethernet and Power Supply connectors of FlexiPacket MultiRadio are different compared to the ones of FlexiPacket Radio.

4. COMPATIBILITIES

Compatibilities with Indoor Units

ODU →

IDU ↓

FPMR

2.1

FPMR

2.1 SU1

FPMR

2.1 SU2

FPMR

2.4

FPMR

2.4 SU1

FPMR

2.5

FPMR

2.5 SU1

FPH A1200 5.0 Drop 1/Drop2/Drop3

√ √ √ √ √ √ √

FPH A2200 5.0 √ √ √ √ √ √ √

FM 200 1.0EP1

2.0

2.0 EP1

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

√

FPH800 2.0

2.0 EP1

√ √ √

√

√

√

√

√

√

√


July 2012


4.1 Network Management Minimum Software release version of NetViewer managing FlexiPacket Multiradio 2.1/2.1 SU1 and SU2 is NetViewer 10.2. Minimum Software release version of NetViewer managing FlexiPacket Multiradio Rel 2.4/2.4 SU1 is Netviewer 10.2. Minimum Software release version of NetViewer managing FlexiPacket Multiradio Rel 2.5 is Netviewer 10.2 EP2. Minimum Software release version of NetViewer managing FlexiPacket Multiradio Rel 2.5 SU1 is Netviewer 10.2 EP2. For details on Netviewer availability and managed Equipments, please refer to Netviewer Release Note.


July 2012


5. PRODUCT COMPOSITION

The following tables describe the software components for each release and the relevant hardware compatibility. Embedded software FPMR 2.1:

Build: FPMR 2.1.644

Item Compatible Units SW version

ODU Application SW including

T557qqAx.yz--Axx (1)

2.1.5.644

BB FPGA 2.1.032

MD FPGA 2.6.016

Modem cfg. files 2.6.001

MD NIOS 1.0.050

RF Firmware 15GHz 1.1


1 NSN coding for developed equipments is T557qqKx.yz, where

- T557 is the preamble code for FlexiPacket MultiRadio units; - “qq” is the frequency band (qq=15 for 15 GHz); - “K” is the antenna interface (K=A for “north NSN”, K=B for ”south NSN”); - “x” is the shifter; - “y” is the Tx band (y=0 for low band, y=5 for the high band); - “z” is the diplexer extension - Letters after the dashes: (“A”=BB-Modem without power injector support ; “B”=BB-Modem with power injector support and

standard TX Power; “C”=BB-Modem with power injector support and increased TX power)


July 2012


Embedded software FPMR 2.1 SU1

Build: FPMR 2.1.5703


ODU Application SW

including

T557qqAx.yz--Axx

2.1.5.703

BB FPGA 170002.1.036

MD FPGA 2.6.021

Modem cfg. files

2.6.010

MD NIOS 1.0.068

Web LCT 2.01.12

RF Firmware 15GHz

1.1


Embedded software FPMR 2.1 SU2 Build: FPMR 2.1.5717


ODU Application SW including

T557qqAx.yz--Axx

2.1.5717

BB FPGA 170002.1.036

MD FPGA 2.6.022

Modem cfg. files

2.6.011

(2.6.012 for 28/128 HP)


July 2012


MD NIOS 1.0.075

Web LCT 2.01.12E

Embedded software FPMR 2.4

Build: FPMR 2.4.4017 Item Compatible Units SW version

ODU Application SW

including

vers. 2.4.021

Mop-Fpga vers. 2.4.068

Modem-Fpga vers. 2.6.022

Modem cfg. files

Config.ini (ETSI: 7/14/40/56 MHz channel - LDPC) (vers. 2.6.011)

Config.ini (ETSI: 28 MHz channel - LDPC) (vers. 2.6.012)

Config.ini (ETSI 28 MHz – 128 QAM - High Performance) (vers. 2.6.012)

Config.ini (ETSI 3.5 MHz - HT) (vers. 2.6.11)

Config.ini (ETSI 14 MHz - HT) (vers. 2.6.11)

Config.ini (ETSI 56 MHz - HT) (vers. 2.6.12)

Config.ini (ANSI 10/20/30/40/50 MHz channel - LDPC) (vers. 2.6.011)

Config.ini (ANSI 20/40 MHz - Japan) (vers. 2.6.011


July 2012


Modem-Nios vers. 1.1.6

Web LCT vers. 2.4.5

Embedded software FPMR 2.4 SU1 Build: FPMR 2.4.5001


ODU Application SW

including

T557qqAx.yz--Axx

vers. 2.4.023



Modem cfg. files

Config.ini (ETSI: 7/14/40/56 MHz

channel - LDPC) (vers. 2.6.012)

Config.ini (ETSI: 28 MHz channel - LDPC)

(vers. 2.6.013)

Config.ini (ETSI 28 MHz – 128 QAM - High

Performance) (vers. 2.6.013)

Config.ini (ETSI 3.5 MHz - HT) (vers.

2.6.13)

Config.ini (ETSI 14 MHz - HT) (vers.

2.6.14)


2.6.14)

Config.ini (ANSI 10/20/30/40/50 MHz


Modem-Nios

vers. 1.1.12

Web LCT vers. 2.4.5


July 2012


Embedded software FPMR 2.5 Build: FPMR 2.5.6206


ODU Application SW

including

T557qqAx.yz--Axx

vers. 2.5.025



Modem cfg. files




(vers. 2.6.013)




2.6.13)


2.6.14)


2.6.14)




Web LCT vers. 2.5.4c

Security package SW

(separated from

embedded sw):

Security Add-On vers. 2.5.009

(commercial name : FPMR Sec 1.0_0.0.0)


July 2012


Embedded software FPMR 2.5 SU1: Build: 2.5.6316


ODU Application SW

including

T557qqAx.yz--Axx

vers. 2.5.041



Modem cfg. files




(vers. 2.6.013)




2.6.13)


2.6.14)


2.6.14)




Web LCT vers. 2.5.6.c

Security Add-On vers. 2.5.009

(commercial name : FPMR Sec 1.0_0.0.0)


July 2012


6. Fixed Bugs

FPMR Rel 2.1 SU1 fixes the following bugs:

• RX ACM Performance Monitoring not correct in Airloss conditions

• Long synchronization transients after IDU-ODU cables disconnection and connection

• Wrong management of traffic in case of double failure on 2+0FD/XPIC System Type

• Wrong role of ODUs after system restart in protected / combined configurations


• Unwanted Acting Master to Acting Slave (and vice versa) switches could be observed too after cable reconnection: these error transients have been greatly reduced in FPMR 2.1 SU2.

• Radio In Errored Counter not significant on Acting Slave ODU: in 2+0FD/XPIC: In FPMR 2.1 with 2+0FD/XPIC System Types, the Radio In Errored Counter of the Acting Slave ODU counted as errored all the packets incoming the device: this because, in these System Types, all the payload is actually managed by the Acting Master ODU. In FPMR 2.1 SU2. this counter is no more reported by WebLCT.

• Squelch and reboot of ODU needed after System Type change. Without Commissioning Tool, it is recommended to squelch the co-located ODUs before applying any System Type change and remove the squelch command only after completion of change.


• NetViewer Performance Monitoring data collection was causing memory consumption on MWT NEs with consequent lock-up/loss of management.

• 2+0XPIC: Eth & E1 traffic errored using 14MHz HT (High Throughput profiles) and SP 256QAM for C/I >25dB


July 2012


Rel 2.5 SU1 :

The following list includes bugs and limitations of previous FPMR 2.5 fixed in FPMR 2.5 SU1:

• Limitation in use of Header Compression feature within Service CESoP Protection / G.8031 Connection Protection setups (ref. FR_0000012161); In an event of an Hw reset or configuration restore, with respect to FPMR 2.5, the outage of traffic in scenarios with CESoP Linear Protection / G.8031 Protection used in conjunction with Header Compression functionality has been reduced from about 2 minutes to <300ms.

• PM Ethernet Counters and Ethernet Throughput report bad values (ref. FR_0000012188): This problem has been fixed in FPMR 2.5 SU1.

• Wrong upload of SW Load instead of Security Add-On (ref. FR_0000012608): This problem has been fixed in FPMR 2.5 SU1.

• Strong Mode Security is lost after power down-up if it is activated after Light Mode was enabled (ref. FR_0000012732): This problem has been fixed in FPMR 2.5 SU1.

Other bugs fixed in Rel 2.5 SU1:

• FR_0000012608: FPMR 2.5: wrong upload procedure for standby.pec

• FR_0000012191: ODU FPMR SVR 2.4 SU1 : Incorrect restore operation

• FR_0000012188: FPMR 2.5: PM Ethernet Counters and Ethernet Throughput report bad values

• FR_0000012726: FPMR 2.5 - eth throughput meas. Changes if there is one connession to telnet23001

• FR_0000012688:1+1 SD: WebLCT doesn't show some values of slave ODU

• FR_0000012687: FPMR 2.5 - 2+2 XPIC with PoE

• FR_0000012628: FPMR 2.5 - 2+2 XPIC A-CCM 10 ms swap & repair with ODU SW 2.1

• FR_0000012443: FPMR 2.5 - 2+2 XPIC: sw switch on Protection ODU Master st-by sometimes causes a loss of traffic


July 2012


7. LIMITATIONS

7.1 XPIC at 7 MHz

System type with XPIC (2+0 XPIC, 2+0 XPIC single cable) is not supported in 7 MHz bandwidth.

7.2 ODU-ODU Synchronization Source

Though available in WebLCT, the synchronization source coming from the ODU-ODU channel through the interconnection cable must non be selected - This limitation has been removed in Rel 2.4.

7.3 Squelch and reboot of ODU needed after System Type change

Without Commissioning Tool, to align configurations and parameters of ODUs protection pair in protected system types, a reboot of all the ODUs is needed after System Type change to ensure correct alignment and restart of the system. It is also recommended to squelch the co-located ODUs before applying any System Type change and remove the squelch command only after completion of change.

7.4 Squelch of Acting Master ODU in 2+0FD/XPIC

If TX squelch of the Acting Master ODU is executed in 2+0FD/XPIC system types, traffic is blocked in both directions. Therefore do not use TX Squelch when working with these system types.

7.5 Limitations in use of 2+0 FD with 7MHz Channel Spacing

System Type 2+0 FD has some limitations when used with the 7MHz Channel Spacing:in case ACM is not enabled, the same modulation scheme should be used on both ODUs;in case ACM is enabled, the following limitations should be set:

- if the Highest Profile is 256QAM, the Lowest Profile shall be set not lower than 32QAM.


July 2012


- if the Lowest Profile is 4QAM, the Highest Profile shall be set not higher than 32QAM.

7.6 Backup and restore from FPMR 2.1 (Build 644) to FPMR 2.1 SU2 (Build 5717) and 2.4 / 2.4 SU1

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 SU2 (Build 5717), FPMR 2.4 / 2.4 SU1 and FPMR 2.5 / 2.5 SU1.

The same applies for configurations saved in 2.1 SU2/2.4 to be restored in 2.4 SU1 and 2.5 / 2.5 SU1; in sporadic cases the configuration file could be partially restored and the following parameters could be found at default value: ACCM Transmission Rate at 100ms; Channel Spacing and Modulation Scheme at 7MHz/4QAM. Should this happen, these parameters shall be re-entered manually

7.7 Change of channel spacing in 1+1 HSBY single cable system type

When a change of Channel Spacing in 1+1 HSBY Single Cable must be done, the following procedure has to be executed not to lose management of local and remote site:

1. On the remote site: - enter the Force Down command on the Main ODU (this is the ODU without the IDU-

ODU cable) - change the Channel Spacing of the Main ODU - change the Channel Spacing of the Protection ODU

2. On the local site: - enter TX Squelch command on both ODUs (no matter in which order) - change the Channel Spacing of both ODUs (no matter in which order) - remove TX Squelch command on both ODUs (no matter in which order)

3. On the remote site:

- remove the Force Down command on the Main ODU

WARNING: please follow the exact order in the execution of all the operations listed above.

7.8 PM Ethernet Counters and Ethernet Throughput report bad values

In some cases Perfornamce Monitoring Ethernet Counters and Ethernet Throughput values can be uncorrect.In these situations, for some intervals, the Ethernet Counters PM (Radio & Gbe) report Ingress packet values are inconsistent with the corresponding ingress byte (octets) values. Similarly, the Ethernet Throughput PM (Rx & Tx) can report bad peak (counting and %) and average (counting and %) values.


July 2012


These defects have been observed in 2+0 XPIC, 1+1 FD, 1+0 and 2+2 XPIC system types.

7.9 Wrong upload of SW Load instead of Security Add-On

If a SW Load package is chosen by mistake in place of the Security Add-On sw package and the Security Add-On Upload is activated, following attempts to upload a new SW load on the ODU will fail: the ODU shall be restarted to allow SW Upload.

8. HINTS AND PROCEDURES

8.1 ODU-ODU cables

Two different kinds of ODU-ODU cables can be used:

T557OUCB.00: ODU to ODU interconnection cable, 10m; to be used only for 1+1FD/SD and 2+0 FD system types

T557OUXPC.00: ODU to ODU interconnection cable for XPIC, 3m; to be used only for 2+0 XPIC system type

Particular care must be taken during assembling, mounting and connection of these cables to the ODUs, to avoid damage to the connector pins. Please refer to the Installation Manual for further details. ODU-ODU cables shall not be mounted when working with 1+0 and 1+1 HSBY (CCM based) system types.

8.2 Correct configuration of QoS for management channel

QoS for management:

VLAN ID Priority - The QoS for management in case VLAN ID priority is enabled;

In this case the VLAN ID management is assigned to priority queue 5 (0 minor... 7 major).

To change the priority queue for management, in the Networking panel, select the “Management Vlan” tab and change the “Management VPRI”.

The “Management VPRI” setting is used both to assign the priority queue for management VLAN ID in case of VLAN ID priority, both to set the PCP bit in the management frames generated by the ODU itself.

802.1p Priority - The QoS for management in case VLAN ID priority is enabled.


July 2012


In this case management is assigned to queue 4 or 5 by default.

This because:

PCP bit for management traffic generated by the ODU is given by Management VPRI.

PCP bit for management traffic generated by the IDU is 4 in case of A-x200

The general rule is to configure the system in order to have high bit rate traffic in queues with a lower priority than the queue used by management. This rule has to be followed for any kind of priority settings chosen.

That is:

1) set only Queues 6 and 7 in SP mode

2) low bit rate traffic in queues 6 and 7

3) high bit rate traffic only in queue 1, 2 and 3

4) queue 0 with low bit rate traffic (better if no traffic at all) to allow background protocol to run (SSM, STP...)

In this way the management traffic is forwarded.

8.3 Licensing

The co-located ODUs in 1+1 / 2+0 system types must have the same licenses (capacity included).

8.4 Private interface details

A local terminal can be directly connected using the Ethernet interface of the ODU with IP address 192.168.255.3/24.

8.5 Public interface detail and procedures for DCN

IP address is user-configurable via LCT. The management VLAN parameter must be set (permitted values 1 ÷ 4094); in order to use a local terminal, a VLAN (re)tagging of the management traffic must be applied, i.e. using an external Managed L2 Switch. The payload traffic does not need to be VLAN-tagged.

If the management VLAN parameter is changed then the ODU is permanently lost until the external switch device is reconfigured accordingly


July 2012


8.6 IPv4/IPv6, Address (L2/L3 Addresses), MPLS label and Ether Type based classification on FPMR

On FPMR, when the 802.1p classification is selected, all tagged frames match the criteria. This leads to the fact that DSCP classification, when selected, is never used for tagged frames. The only way to use IPv4/IPv6, Address (L2/L3 Addresses), MPLS label and Ether Type criteria for tagged frames is to disable the p-bit criteria.

8.7 XML files supported in FPMR 2.1 / 2.1 SU2

The xml files are stored in the ODU file system and compressed in gz format. Some of these files require the stylesheet that is stored in\ram0\styleSheet.

Name Name Location Stylesheet name

AccountLogFile.xml AccountLogFile.gz /ram0/data AccountLog.xsl

EventLog.xml EventLog.gz /ram0/data EventLog.xsl

IP_tab.xml IP_tab.gz /ram0/data IP_tab.xsl

macdb.xml macdb.gz /ram0/data MacDBView.xsl

performance.xml Performance.gz /ram0/data PMData.xsl

TestLoopResult.xml TestLoopResult.gz /ram0/data LoopTest.xsl

VLAN_tab.xml VLAN_tab.gz /ram0/data NA – not required

restore_log.xml restore_log.gz /tffs0/data RestoreLog.xsl

The TestLoopResult .xml file is available only in system type 1+0.

8.8 CESoP traffic with Jumbo frames


July 2012


If Jumbo frames are present together with CESoP traffic, using QPSK modulation in 7 MHz bandwidth, the E1 transmitted via CESoP could be unstable. It is suggested then to use at least 16QAM modulation. The issue is not present at 14/28/40/56 MHz bandwidth.

This behaviour has not been reproduced with Rel 2.5 with packet fragmentation enabled.

8.9 Upgrade of SW Release from 2.1 SU2 to 2.4 SU1/2.5/2.5 SU1

When SW Release 2.1 SU2/2.4 is running on the working bank and SW Release 2.4 SU1/2.5/2.5 SU1 is uploaded on the st-by bank and ready for SW Bank switching, the management of the ODU from WebLCT could be irregular or difficult and it could be impossible to execute the SW Switch command; in this case, the following workaround procedure can be executed to activate the new SW Load:

- Execute a SW Reset command on the ODU - Once the ODU is back on-line, open a Telnet connection on port 23001 - Enter the command DOWNINT_SwitchBank - In this way the new SW Load 2.4 SU1/2.5/2.5 SU1 is activated

Alternatively:

- Execute a SW Reset command on the ODU - Once the ODU is back on-line, open a Telnet connection to it on port 23 - Enter the command wmset fpmrCmdSwitchActiveLoad.0 1 - In this way the new SW Load 2.4 SU1/2.5/2.5 SU1 is activated

8.10 Removal of multiple Web LCT instances from Windows Control Panel

To remove unused “FPMR Web LCT” application instance do the following:

- from Control Panel click the Java icon, then - from the Java panel, in the “General” tab, section “Temporary Internet Files”, click the

“View” button, - in the new dialog window ”Cache Java Viewer”, from the drop-down menu select

“Application”, - in the listed applications select the one to be removed then, via toolbar button or local

contextual popup-menu, select “remove”. - Such a procedure, also removes the application reference inside the installed programs,

desktop shortcuts, start menu shortcuts.


July 2012


8.11 2+0XPIC / 2+0FD: system stabilization time after start up

In 2+0 XPIC/FD, the startup time needed for system stabilization (traffic, synchronization and management) is min. 5 minutes: this is the time required by the system to adjust all the internal clock signals properly.

8.12 IE8 Browser settings for correct WebLCT login

When using Internet Explorer 8, in order to avoid double WebLCT login the “Smart Screen” filter must be disabled.

8.13 CCM Time Interval Configuration on ODUs and IDUs

• CCM Time Interval must be set coherently on ODUs and IDUs: they must have the same between ODUs and IDUs and between co-located ODUs.

• When HW Protection Mode 1 is adopted (using ECCM between IDUs and ODUs), the CCM Interval on IDUs and ODUs shall be 100ms.

• When HW Protection Mode 3 is adopted (not using ECCM between IDUs and ODUs), the preferred CCM Interval on ODUs shall be 10ms.

• If for any reason the CCM Time Interval should be changed on ODUs, the following precautions shall be applied:


July 2012


ODU 1 ODU 2

T0 TI_conf=100

TI_used=100

TI_conf=100

TI_used=100

default configuration

T1 TI_conf=10

TI_used=10

TI_conf=100

TI_used=10

T2 TI_conf=10

TI_used=10

TI_conf=10

TI_used=10

TI changed on both

ODUs (should be

hitless)

T3 TI_conf=100

TI_used=10

TI_conf=10

TI_used=10

T4 TI_conf=100

TI_used=10

TI_conf=100

TI_used=10

T5 SW Reset SW Reset must be reset at the

same time (^)

T6 TI_conf=100

TI_used=100

TI_conf=100

TI_used=100

back to default

configuration

… … … …

Notes:

red shading is for alarm condition

bold is for a configuration change

(^) the ODU reset as second one must be reset before the other ODU has re-started; not

hitless at restart (switch-over could occur at restart depending on the reset sequence)

8.14 STP disable on IDU before execution of ODU Loopbacks

In order to ensure correct operation of the loopback functionalities available on FPMR, please disable STP protocols if active on the IDUs.

8.15 ATPC: correct settings for Min and Max TX Power

When working with ATPC enabled, please ensure that the Max TX Power value is higher than the Min TX Power value.

8.16 XPIC operation when one polarization is down

In case either ODU 1H or 1V are TX squelched for manual operation:


July 2012


In case the power cable of either ODU 1H or 1V and the IDU is disconnected:

In the latter case, if ACM is used, the modulation scheme in the direction right to left will set according to the S/MSE value guaranteed by the RF Link conditions (RSL and co-channel C/I).

8.17 Notice about the use of IDU FPH800 P+E Interfaces

Important Notice: the P+E solution is not compatible with Power-over-Ethernet (PoE) defined by IEEE 802.3af and 802.3at since P+E intends to provide higher power (watts) than provided by the two standards.

Thus, do not connect FPH800 or FirstMile 200 P+E interfaces to other devices than NSN’s FlexiPacket ODUs.

Warning: do not connect other P+E ports (for example, the P+E ports of the external Power Injector) to the P+E ports of FPH800 whether the P+E function of FPH800 is disabled or enabled.


July 2012


8.18 SW downgrade from 2.4 SU1/2.5 to 2.1 SU2

In case a SW Downgrade from 2.4 SU1 to 2.1 SU2 is necessary, please follow the following procedure:

- Always backup 2.1 SU2 configurations before switching to 2.4 SU1 / 2.5

- If you need to revert to the previous SW Version 2.1 SU2, restore the configurations saved while 2.1 SU2 was running

8.19 Interoperability of 2+0 XPIC Ring with G.8031 Connection Protection mechanism on FPH800 2.0EP1

Due to a limitation in the current implementation of G.8031 Connection Protection mechanism released in FPH800 2.0EP1, 2+0 XPIC Ring M3 must not be used in conjunction with this FPH800 functionality; in this case, 2+0 XPIC Ring M1 shall be used instead.

8.20 Use of Header Compression with CESoP services using VLAN translation option (single tag) and Dynamic MAC address assignment

CESoP services using VLAN translation (single tag) and Dynamic MAC address assignment need periodical ARP refresh messages to be exchanged between the end points of the connection to keep the service alive: if Header Compression is applied to these services, the new HC rules 29-30 must be used to guarantee the correct transit of ARP refresh messages.

8.21 Use of Header Compression rules 31 and 32 for CESoP services with VLAN transparent option (double tag)

When FPMR units with Header Compression (HC) rules 31-32 enabled (CESoP double-tagged suppression) interoperate with FM200 or FPH800 units with CESoP pseudowiring, service is "transparent", so the transport is double tagged: C-tag is added by the IWF (as per configuration on each PW), S-tag is added by the transport service.

Gratuitous-ARP requests/replies are single-tagged (using the S-tag value only), so if the HC with rules 31-32 is enabled on the FPMR units, the ARP messages won't be transported error-free and thus the PW will permanently go to AIS-2M at the first MAC-db flush.


July 2012


The workaround in this case is to configure the PW using a static MAC assignment on the IWFs, so no ARP messaging is exchanged.

8.22 Notes on Header Compression rules 29-34 to be used with CESoP / SAToP / MEF8 traffic

In order to make easier the Header Compression configuration process in case of typical TDM-over-Packet traffic, suppression rules 29-34 have been added to the Header Compression (HC) engine. The 6 rules cover the possible implementations and deployments of pseudowiring and transport available at the Indoor Units. In detail:

- HC "noMux" rules (rules 29, 31 and 33) shall be used to cope with CESoP 1tag / CESoP 2tag / MEF8 traffic respectively which is configured on the IDUs using the the scheme "single pseudo-wire per C-tag"

- HC "Mux" rules (rules 30, 32, and 34) shall be used to cope with CESoP 1tag / CESoP 2tag / MEF8 traffic respectively which is configured on the IDUs using the the scheme "multiple pseudo-wires per C-tag"

To be noticed that:

- CESoP 1tag / 2tag suppression rules are also compatible with the structure-unaware transport with SAToP 1tag / 2tag (supported by FM200 and FPH800 indoor units)

- MEF8 suppression rules are only compatible with the FPH Ax200 indoor units structure-unaware pseudowiring

When PWs at the Indoor units are created using static MAC address assignment for the resolution of the remote IWF, the Header Compression built-in rules 29-34 on the FPMR units may be activated with no limitations. In case of dynamic MAC address resolution, attention must be paid when FPMR radio units interoperate with FM200 / FPH800 indoor units with CESoP 2tag (or SAToP 2tag) pseudowiring: in this case the service is "transparent", so the transport is double tagged, that is: a C-tag is added by the IWF (as per configuration on each PW) and an S-tag is added by the transport service. However gratuitous-ARP requests/replies are single-tagged (using the S-tag value only), so if the HC with rules 31-32 is enabled on the FPMR units, the ARP messages won't be transported error-free and thus the PW will permanently go to AIS-2M at the first MAC-db flush. The workaround in this case is to configure the PW using a static MAC assignment at the IWFs, so no ARP messaging is exchanged.

8.23 2+0 XPIC Ring: partial restore indication after backup and restore operation on Slave ODUs

After a backup and restore operation executed on a 2+0 XPIC Ring configuration, the indication “partial restore” can be displayed by Slave ODUs and the Restore Log contains the


July 2012


“Ethernet Not OK” information: this happens because of a not optimized sequence in restoring commands, however does not lead to any malfunction as the correct operation mode is actually restored.

8.24 Note about SW Upload and SW Bank Switch operations

SW upload: from FPMR 2.4/2.4SU1 to any other (upgrade or downgrade), the ODUs belonging to the same “group” in 1+1 or 2+0 configurations must be downloaded in sequence: the first ODU, and after this has updated the SW data of the stand-by bank, the second one.

The warning above does not apply to FPMR 2.1 SU2 and FPMR 2.5.

SW Bank Switch: for all versions up to 2.4 SU1, the SW Bank Switch command must be executed on the first ODU and, once this has come back on line, on the second one. In FPMR 2.5 the SW Bank Switch command on the second ODU is automatically inhibited until the first ODU has completed its one.

8.25 Note about switch of Packet � Hybrid operational mode

It is possible to switch the ODU operational mode from FPMR 2.5 (packet) to FPMR H2.1 SU2 (hybrid) after uploading and switching the relevant SW version to the ODU.

Please refer to the Release Notes of FPMR H2.1 SU2 for further information.

8.26 Configuration of networking parameters of co-located ODU in Single Cable System Types with FPMR 2.4

In the following, a procedure is described to make the Networking Parameters in the Co-located ODU of “single cable” protected system types (1+1 HSBY 1c and 2+0 XPIC 1c) effective. This workaround is needed because, following a change in the Networking parameters of the Co_located ODU (IP_address, IP_mask, IP_gateway and M_VID) configured in the Directly_Connected ODU (and sent to the Co_located via LLDP Protocol) these new parameters are not effective. The trigger to make them effective is possible in different ways: HW Reset of the Direct_connected ODU, Disabling/Enabling of ACCM Timer and Disabling/Enabling MAC Learning in Direct Connected ODU Topology change (disconnect and reconnect the ODU-ODU cable or connect/disconnect the GbE cable of Co-located ODU)


July 2012


Obviously, these operations must be executed after the Network parameters have been modified. Three cases are considered: 1. New Installation in this case, for simplicity it is suggested to act an HW Reset on the

Directly Connected ODU as workaround for the described problem 2. Swap & Repair in this case, since it is possible that user traffic is running on the

Directly Connected ODU, it is strongly suggested not to issue the HW Reset on this ODU, but to apply the procedure described here below on the same ODU 3. Networking parameters change also in this case it is suggested to apply the

procedure described below (a part the cases where no user traffic is running on the Directly Connected ODU) Before executing the procedure below, the parameter “Transfer IP Address to co-located ODU” must be disabled. NOTE: in the following example of the procedure, 172.31.219.105 is supposed to be the Public IP address of the Directly Connected ODU. If A-CCM Transmission Rate is equal to 10ms, before installing Co-located ODU, please set A-CCM Transmission rate = 100 ms on Directed connected ODU. a) telnet 172.31.219.105 23001 (telnet connection to the Public IP address and PORT 23001) b) admin (user ID) c) sysmanager (PSWD) d) [RTP]> e) [RTP]>cmd f) [WxWorks *]# g) [WxWorks *]# rtp (will dispay a 0xabcdef register address) h) [WxWorks *]# rtp attach 0xabcdef i) [uApplication]# j) [uApplication]#func call &disableTimerClkACCM & k) wait T (5 seconds) l) [uApplication]# func call &enableTimerClkACCM & m) [uApplication]#func call &LearningDisable & n) [uApplication]#func call &LearningEnable & o) [WxWorks *]# rtp detach 0xabcdef p) [WxWorks *]#C q) [RTP]> logout After completing the swap & repairing procedure (steps a to q), please set A-CCM Transmission rate back to the initial value = 10 ms on both ODUs if this was the original value.


July 2012


8.27 Swap and repair of the co-located ODU with FPMR 2.5 /2.5 SU12

The following procedure applies when Direct connected ODU is equipped with 2.5 and the new co-located ODU: - is equipped with 2.5 - is equipped with 2.4 SU1 - is equipped with 2.4. [ point 20a was inserted ] This procedure doesn’t work if new co-located ODU is equipped with 2.1, in that case ODU must be updated to a SW ≥ 2.4

1. Power off the faulty “FlexiPacket MultiRadio”. 2. Pull out the Ethernet cable and the Power Supply cable. 3. Disconnect the ODU-ODU cable. 4. Disconnect the ground. 5. Disconnect the RF waveguide. 6. Unhook the four hooks on the FlexiPacket MultiRadio. 7. Lift the FlexiPacket MultiRadio, so as to free it from the hooks on the

support, and remove it. 8. Install the FlexiPacket MultiRadio spare part. 9. Hook the four hooks. 10. Connect the RF waveguide. 11. Connect the ground. 12. Connect the Ethernet cable, the Power supply cable and the ODU-ODU

cable. 13. Connect the PC to the Management port of the IDU. 14. If “Switching Mode” is Revertive, before power on the Co-located Odu, Set

“ Force Down “enabled” on ODU AM main. 15. Power on the FlexiPacket MultiRadio.

15a . Verify that the Co-Located ODU is up reading the Direct Connected ODU Alarm List,It takes about 4 minutes.

Odu AM main Alarm list with Co-Located Odu power down

2 Note: this procedure is inserted here for reference. The complete and detailed procuedure will be included in Customer Documentation (CuDo) in the document “FlexiPacket MultiRadio Rel. 2.5 and IDU (FM200, FPH800 and Third Party L2Bridge) procedures”


July 2012


Odu AM main Alarm list with Co-Located Odu power UP: A-CCM Loss is no more present

16. Set the IP_ADD of co-Located Odu using the “Operation Administration &

Maintenance” window : click the “Colocated odu config” menu and insert the value of IP_ADD


July 2012


17. Check the flag “transfer to colocated” and click YES

18. Verify that the operation of previous point has succeeded


July 2012


19. Remove flag detailed at point 17.

20. Open the following Telnet session a. telnet 10.10.10.24 23001 (telnet connection to the Public IP address and PORT

23001) (if security is enable use ssh2 protocol on port 23001)

b. admin (user ID) c. sysmanager (PSWD) d. [RTP]> e. [RTP]>cmd f. [WxWorks *]# g. [WxWorks *]# rtp (will dispay a 0xabcdef register address) h. [WxWorks *]# rtp attach 0xabcdef i. [uApplication]# j. [uApplication]# func call &LearningEnable & k. [WxWorks *]# rtp detach 0xabcdef l. [WxWorks *]#C m. [RTP]> logout 20a. [only for SVR 2.4 equipped on Co-Located Odu] Power down-up the Co-Located Odu

21. Now, the co-Located Odu is reachable @new_IP_ADD. Open the Web browser and enter “http:\\IP public address of the Co-located FlexiPacket MultiRadio (if security is enable use https:\\ IP public address of the Co-located FlexiPacket MultiRadio) If you have a backup file of the NE, restore it, otherwise configure the NE. If necessary, upgrade the software and the licence

22. If “Switching Mode” was Revertive (see poit 14), set “ Force Down “disable” on ODU AM main.


July 2012


8.28 Note about the RF Loopback command

The RF Loopback command must be enabled only with ATPC disabled.

Documents

FlexiPacket MultiRadio CRN_2 5_SU1.pdf