You are on page 1of 13

Customer Release Note

Product Family: FlexiPacket Product: FlexiPacket Radio Delivery type: Minor Release: 1.3EP1 SU2 Id: FPR 1.3.023 Customer: generic Delivery

Nokia Siemens Networks

Company Confidential

1 (13)

Table of Contents 1. 2. 3. 4. 5. 6. 7. PRODUCT DESCRIPTION ............................................................................................................ 3 FEATURES .................................................................................................................................... 4 APPLICABILITY ............................................................................................................................. 6 PRODUCT COMPOSITION ........................................................................................................... 7 FIXED BUGS AND LIMITATIONS ................................................................................................. 8 KNOWN BUGS, LIMITATIONS AND OPEN PROBLEMS ............................................................. 9 HINTS AND PROCEDURES ........................................................................................................ 11
Contact your local Nokia Siemens Networks support

Contact:

Summary of changes:
January 2012 1.0 First version

Nokia Siemens Networks

Company Confidential

2 (13)

1. PRODUCT DESCRIPTION
FlexiPacket is the new line of point to point Carrier Ethernet fully outdoor radio relay equipments from Nokia Siemens Networks. FlexiPacket Radio is a reliable and flexible microwave radio, which efficiently transports Ethernet traffic in RF bands from 7 GHz up to 38 GHz (7, 8, 13, 15, 18, 23, 26, 28, 32 and 38 GHz currently released). FlexiPacket Radio can be used in different transmission networks: mobile networks, fixed networks or private networks. For unprotected (1+0) setups (i.e. tail sites) FlexiPacket Radio can be directly connected to the BTS or managed by an external L2 Ethernet switch through its Gigabit tributary interface.

Nokia Siemens Networks

Company Confidential

3 (13)

2. FEATURES
References: For a complete description please refer to the Customer Documentation Due a internal component technology change the new software release FPR1.3 EP1 SU2 has been developed. FPR1.3EP1 SU2 SW release is backward compatible with all FlexiPacket Radio HW Release history: FPR 1.1: introduces FlexiPacket Radio; main features:

5 modulation profiles (4 / 16 / 64 / 128 / 256 QAM) and 5 channel spacing (3.5 / 7 / 14 / 28 /56 MHz), for a total of 22 available radio modes; radio channel capacity up to 350 Mbit/s Gigabit Ethernet tributary side with auto sensing (10/100/1000baseT) and private and public DCN interfaces Internal Ethernet switch supporting Quality of Service (QoS) ATPC operation and Adaptive Modulation and Coding (ACM) Local Craft Terminal 3.0 - Commissioning of local and remote unit, including manual and temporized software upgrade, packet counters and performance monitoring

FPR 1.2 / 1.2 SU1 main features:

ACM Most Robust Mode setting configurability on FPR Mixed SP/WFQ scheduling on FPR (2SP + 2WFQ or 1SP + 3WFQ queues)

FPR 1.3 main features:

ACM Aware Service Filtering (E1 Prioritization) on FPR 1.3 Second Gateway on FPR 1.3 Physical Topology Discovery on FPR 1.3 28 and 56 MHz High Performance Profiles on FPR 1.3

FPR 1.3 EP1 / 1.3 EP1 SU1 / 1.3 EP1 SU2 main features:

Rapid shutdown feature on Ethernet interface New license management with CliCs FPR 1.3 EP1 SU1 fixes some SW malfunctions related to Performance Monitoring

FPR 1.3 EP1 SU2 has been developed due a internal FlexiPacket Radio component technology change. FPR1.3EP1 SU2 SW release is backward compatible with all FlexiPacket Radio HW

Nokia Siemens Networks

Company Confidential

4 (13)

Compatibilities: FPR 1.3 EP1 SU1/SU2

FPR vs. FPR


(radio compatibility)

FPR 1.1

FPR 1.2

FPR 1.2 SU1

FPR 1.3

FPR 1.3 EP1

FPR 1.1 FPR 1.2 FPR 1.2SU1 FPR 1.3 FPR 1.3 EP1 FPR 1.3 EP1 SU1/SU2

LCT vs. FP Release


(management compatibility)

LCT 3.2

FPR 1.3 FPR 1.3 EP1 FPR 1.3 EP1 SU1/SU2

LCT 3.2 EP1

LCT 3.3

Nokia Siemens Networks

Company Confidential

5 (13)

3. APPLICABILITY
The present document covers the following frequency bands: FlexiPacket Radio 7GHz band 154, 161, 168, 196, 245 MHz frequency shifter; FlexiPacket Radio 8Ghz band 310, 311.25 MHz frequency shifter; FlexiPacket Radio 13GHz band 266 MHz frequency shifter; FlexiPacket Radio 15GHz band both 420, 490, 644 and 728 MHz frequency shifters; FlexiPacket Radio 18GHz band 1010 and 1560 MHz frequency shifter; FlexiPacket Radio 23GHz band 1008, 1200 and 1232 MHz frequency shifter; FlexiPacket Radio 38GHz band 1260 MHz frequency shifter; FlexiPacket Radio 26GHz band 1008 MHz frequency shifter FlexiPacket Radio 28GHz 1008 MHz frequency shifter FlexiPacket Radio 32GHz 812 MHz frequency shifter

Nokia Siemens Networks

Company Confidential

6 (13)

4. PRODUCT COMPOSITION
The released software is delivered through suitable packages. Items T555BSW1.30EP1 T555BSWCD1.30EP1 Description FlexiPacket Radio SW R1.3EP1 e-media FlexiPacket Radio SW R1.3EP1 CD

Build nurmber: SW version build ODU Application SW including FPGA Modem FW Modem cfg. files 1.3.015 31.38.38 3.3.025 0.2.13

Nokia Siemens Networks

Company Confidential

7 (13)

5. FIXED BUGS AND LIMITATIONS


The following list details bugs and limitations of previous releases fixed in FPR 1.3 EP1 SU1/SU2: FR Title Release FPR 1.3 EP1 FPR 1.3 EP1 FPR 1.3 EP1 Severity Minor Minor Minor Status Closed Closed Closed

FR_0000010010 FPR 1.3: Reference clock update everyx hours when SNTP is enabled FR_0000010013 FPR 1.x: : Wrong seconds counted in FPR ACM Tx/Rx statistics FR_0000009953 FPR 1.x: wrong CollectionBeginTime tag in the performance.x

Nokia Siemens Networks

Company Confidential

8 (13)

6. KNOWN BUGS, LIMITATIONS AND OPEN PROBLEMS 6.1 FPR 1.2, FPR 1.2 SU1, FPR 1.3 EP1, FPR 1.3 EP1 SU1 are not compatible with FPR 1.1
As FPR 1.2 introduces a scrambler in FPGA, air signal is not compatible with FPR 1.1.

6.2 Broadcast-multicast traffic


In case of multicast/broadcast traffic rate > 100Mbps, there could be temporary loss of management.

6.3 About 2dB Tx power overshoot is seen when modulation is manually or dynamically changed from 16QAM to 4QAM
Time duration of the event is less than 10 ms and it does not have any impact on the traffic. Reference: FR_0000001296

6.4 When CW tone testing modality is enabled traffic is lost in Rx side too
The problem does not depend on any other RF / modem working conditions on the ODU. Reference: FR_0000001451

6.5 Performance monitoring ACM Rx seconds may be accumulated to a wrong modulation scheme under deep fading conditions
Same problem does not affect the ACM PM counters on the Tx side.

6.6 No check is present for the validity range of PM configuration parameters


All numeric values are accepted without constraints.

6.7 Errors on Ethernet cable interface


Events of error frames on the input port of the Ethernet switch have been detected, mainly with max. cable length (100m) and during temperature transients. Reference: FR_0000001026; FR_0000001494

6.8 Quality Driven ATPC is not released


Quality Driven ATPC is not released in FPR 1.3 due to poor performance in case of adjacent interferers. Reference: FR_0000001477

Nokia Siemens Networks

Company Confidential

9 (13)

6.9 Long switching times in 1+1 Hot Stand-By configuration with 56MHz channel
Switching times up to 1.5s (vs. typical 400ms) where measured with 1+1 Hot Stand-By protection and 56MHz channel bandwidth: this problem is not repetitive and its probability is depending on the RF Band in use, increasing with the RF Frequency.

6.10 FPR bank switch in Active FPR in 1 + 1 configuration


Performing a bank switch in Active FPR in 1 + 1 configuration (with traffic higher than available bandwidth), there are few errors on the traffic for about 1-2 seconds (FR_0000003700)

The following list details issues found during FPR 1.x tests and still open:
Code FR_0000001296 FR_0000001501 FR_0000001026 FR_0000003699 FR_0000001109 FR_0000000965 FR_0000001101 FR_0000001065 FR_0000001352 FR_0000001451 FR_0000001494 FR_0000000891 FR_0000001165 FR_0000001423 FR_0000001437 FR_0000001529 FR_0000001472 FR_0000001465 FR_0000001437 FR_0000001486 FR_0000001536 Title FPR 15GHz - ACM functionality - Tx spectrum mask violation due to temporary PTx overshot when modulation is changed from 16QAM to 4QAM Temporary PTx increase even greater than 15dB when maintenance release 1.1.045 is downloaded on top of 1.1.042 for ACM improvement FPR - Loss of frames at cable interface, Tx direction, when FlexiPacket Radio is working with Eth cable length = 100m and T_odu above +40 degrees FPR 1.3: Error on high priority traffic when reset the SW on active ODU RX power measure RTPC ACCURACY Cable Polarity Status Surge test - Operator action needed for traffic recovery Voltage dips Loss of Rx payload when CW single tone mode is selected FPR 18GHz - Errored frames at GE input port of Ethernet switch during temperature transients FPR 18GHz - RTPC Accuracy (ODU Phoenix 18 GHz). FPR 18GHz - RSSI Voltage sensitivity and LCT RX power indication (ODU Phoenix 18 GHz). FPR 18GHz - Tf_min and Tf_max: HW parameters settings wrong FPR 18GHz - Frames loss during 'Microphonics and Sensitivity to knocking' test. FPR 18GHz - Surge Test - Power over Ethernet interface failure ODU side Limits of PS interface (ODU Phoenix 23GHz) Voltage dips (ODU Phoenix 23GHz) Frames loss during 'Microphonics and Sensitivity to knocking' test. RSSI Voltage sensitivity and LCT RX power indication (ODU Phoenix 23GHz). RTPC Accuracy (ODU Phoenix 23 GHz). Release FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.3 EP1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 FPR 1.1 Severity major major major minor minor minor minor minor minor minor major minor minor minor minor minor minor minor minor major minor Status open open open open open open open open open open open open open open open open open open open open open

Nokia Siemens Networks

Company Confidential

10 (13)

FR_0000001428 FR_0000001430 FR_0000001443 FR_0000001083 FR_0000002585 FR_0000001298 FR_0000001438 FR_0000001172 FR_0000001500

FR_0000001492 FR_0000001485 FR_0000001126

FlexiPacket Radio 13GHz ODU LCT indication of RSSI exceeds the tolerance limits FlexiPacket Radio 13GHz ODU Surge test Operator action needed for traffic recovery RSSI Voltage sensitivity and LCT RX power indication (ODU Phoenix 7 GHz). RSSI Voltage sensitivity and LCT RX power indication (ODU Phoenix 8 GHz). Surge test - Operator action needed for traffic recovery (ODU Phoenix 26 GHz). RSSI Voltage sensitivity and LCT RX power indication (ODU Phoenix 38 GHz). FPR 38GHz - Failure of RF loopback test in 256QAM/56MHz condition affecting a small percentage of ODU population (around 20%) Surge test - Operator action needed for traffic recovery (ODU Phoenix 38 GHz). Changing Tx profile with 7MHz: when ACM is disabled and ATPC is disabled, if Tx profile changes value from 128 QAM to 256QAM, errors can be observed, depending on Prx working point. ATPC_Power_Level_driven: Hysteresis of 1 dB is not achieved with fast fading (50dB/s) ATPC_Power_Level_driven : Ptx ramp vs Ptx square We suggest to remove lldpStatsRxPortFramesErrors from the document describing the MIB of FPR (FlexiPacketMIB_1-3.doc) because it has the same meaning of lldpStatRxPortFramesDiscardedTotal

FPR 1.2 FPR 1.2 FPR 1.2 FPR 1.2 FPR 1.2 FPR 1.2 FPR 1.2 FPR 1.2 FPR 1.3

minor minor minor minor minor minor minor minor minor

open open open open open open open open open

FPR 1.3 FPR 1.3 FPR 1.3

minor minor minor

open open open

7. HINTS AND PROCEDURES 7.1 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.

7.2 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.

7.3 Caution when configuring SP as scheduling mode


BPDU-SSM packets and STP packet are untagged. In case of congestion, if the chosen Scheduling Mode is SP, these kinds of packets will be discarded. This may cause permanent loss of management or loss of synchronization. The use of either OneSPThreeWFQ or TwoSPTwoWFQ Scheduling Mode is suggested.

Nokia Siemens Networks

Company Confidential

11 (13)

7.4 Scheduling mode and traffic congestion


The traffic rate in priority queue 3, in case of OneSPThreeWFQ or TwoSPTwoWFQ, should not overcome the available bandwidth. Otherwise the management frames, in priority queue 2, will be discarded. In case ACM is enabled and either OneSPThreeWFQ or TwoSPTwoWFQ is used, the traffic rate in priority queue 3, should not overcome the minimum available bandwidth (the bandwidth of profile 1). Best effort and not shaped low priority traffic should never be set in queue 2 to avoid loss of management.

7.5 Caution when configuring OAM in a protected system


In case both the ODUs are wrongly configured as main, there could be loss of management of both ODUs. To recover from this state: on the FPH (A2200) disable one port of the LPG; possibly disable the port connected to the ODU that should remain in main role. Then via LCT connect to the other ODU and change the ODU role from MAIN to PROTECTION. Note1: the ODU wrongly activate the alarm LPG Failure and it doesnt activate the alarm LPG Cfg Error. This wrong behavior is described in CRDB00000943 HsbyConfigurationError. Note2: the same wrong behavior occurs if both the ODUs are set as protection.

7.6 Transparency of FPR to SSM messages for synchronization purposes


If FPH is using Synchronous Ethernet (Master Slave) and the FPR in between are Free Running, there is no notification of this in the SSM messages exchanged between the A2200: SSM are ok, because FPR does not process SSM. This is a wrong system configuration that must be avoided by synchronizing the FPR connected to the FPH properly: FPR connected to the SyncE Master FPH must be synchronized on Ethernet while FPR connected to the SyncE Slave FPH must be synchronized on Radio.

7.7 DSCP based classification on FPR


On FPR, 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 DSCP criteria for tagged frames is to disable the p-bit criteria. The behaviour comes from the commercial switch component used in FPR.

7.8 Synchronization settings of spare FPR units


Spare FPR units coming from the factory have the default synchronization setting (Free Running): in case of doubts about the provenience and the actual sync. configuration of spare units, it is recommended to verify it by means of local connection of the LCT to the ODU and set synchronization according to the correspondent FPH port setting (FPH port Master FPR sync. on Ethernet; FPH port Slave FPR sync. on Radio); misaligned SyncE settings may cause no connectivity between FPH and FPR.

7.9 FPR cannot be downgraded from 1.3.13 / 1.3.15 to 1.3.8 SVR


Performing a downgrade from 1.3.13 / 1.3.15 to 1.3.8 SVR, License Key cannot be set due to different encryption algorithm in 1.3.8 (only RC6 was known in 1.3.8)

Nokia Siemens Networks

Company Confidential

12 (13)

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.

Nokia Siemens Networks

Company Confidential

13 (13)