crn flexihybrid release notes svr 4.0 cb2

NWS Product Management MWT

Nokia Siemens Networks Customer Release Note

FlexiHybrid

SOFTWARE VERSION RELEASE SVR 4.0

CODE: CRN-070911-3

ISSUE/UPDATE: 2 May 2012

SOURCE: NWS MWT Product Management


In addition to the authors named on the cover page the following persons have collaborated on this document : More information notes. <User defined>

CHANGE HISTORY

DATE REV. DRAFT CHANGE

07-09-2011 1 -- FIRST ISSUE – NOT APPLICABLE

27-10-2011 2 -- SECOND ISSUE – NOT APPLICABLE

02-05-2012 3 THIRD ISSUE-NOT APPLICABLE


TABLE OF CONTENTS

Sommario

1 INTRODUCTION .............................................................................................................................................. 4

1.1 SCOPE ....................................................................................................................................................... 4

1.2 APPLICABILITY ......................................................................................................................................... 4

1.3 TERMS, ABBREVIATIONS AND DEFINITIONS ............................................................................................. 4

2 SCOPE ................................................................................................................................................................. 6

3 APPLICABILITY ............................................................................................................................................... 6

4 PRODUCT DESCRIPTION .............................................................................................................................. 6

4.1 INTRODUTIONS ............................................................................................................................................... 6

4.2 FEATURES OF SVR 4.0 CB2 WITH RESPECT TO SVR 3.1 SU2 ....................................................................... 6

4.2 SYSTEM CONFIGURATION ............................................................................................................................. 7

5 SUPPORTED IDU COMPOSITIONS .............................................................................................................. 7

6 SUPPORTED FUNCTIONALITIES ................................................................................................................ 9

7 2XSTM1E/O SUPPORT IN EXPANDED SLOT AND SNCP-LIKE PROTECTION FOR ENHGIGE MASTER I/O MODULE ......................................................................................................................... 10

8 BER SWITCHING TRIGGERED VIA SNCP-LIKE ....................................................................................... 11

9 CONFIGURABLE MODEM OUTPUT POWER ............................................................................................ 11

10 SUPPORTED LICENSING CONFIGURATION OF R4.0 (IMPROVED SPECTRAL EFFICIENCY) ............................................................................................................................................................. 11

11 FRAMER PARITY ERROR DETECTION_RESOLVING LINK FAULT ISSUE AND FRAMER PARITY SWITCH ....................................................................................................................................................... 16

12 SYSTEM TYPE COMPATIBILITY ................................................................................................................ 16

13 PRODUCT COMPOSITION ............................................................................................................................ 18

13.1 SW UPGRADING ........................................................................................................................................ 23

14 COMPATIBILITY RULES BETWEEN HW AND SW VERSIONS .... ........................................................ 24

15 BEHAVIOR NOTES .......................................................................................................................................... 31

15.1 GENERAL FEATURES AND CONFIGURATIONS .......................................................................................... 31

15.2 ACM BEHAVIOUR AND APPLICABILITY ................................................................................................... 37

15.2.1 MODES AND PARAMETER CONFIGURATION .............................................................. 37

15.2.2 SWITCHING TIME ................................................................................................................. 40

15.2.3 Other notes about possible setting & configurations ............................................................. 41


1 INTRODUCTION

1.1 SCOPE

This document represents the System Release Note of the product FLEXIHYBRID developed by CarrierComm and Nokia Siemens Networks.

1.2 APPLICABILITY

The information contained in this document is applicable to System Release SVR 4.0 of FLEXIHYBRID and to all the organizations involved.

1.3 TERMS, ABBREVIATIONS AND DEFINITIONS

AP Alternate Pattern Polarity BB Base-Band NMS Network Manager System CC Co-Channel O&M Operation and Maintenance DA Destination Address OC ODU configuration DC/DC DC to DC power converter ODU Outdoor Unit E1 2048 Kbit/s PC Port configuration E/FE Ethernet/Fast Ethernet PCB Printed Circuit Board EMC Electro Magnetic Compatibility PDH Plesiochronous Digital Hierarchy

ETH Ethernet PM Performance Monitoring

FD Frequency Diversity QAM Quadrature Amplitude Modulation FPGA Field Programmable Gate Array QoS Quality of Service HC High Capacity RF Radio Frequency HDB3 High Density Bipolar order 3 RSOH Regenerator Section Overhead HSBY Hot Stand-By RST Regeneration Section termination

HW Hardware SCN Software configuration networking

I/O Input / Output SDH Synchronous Digital Hierarchy

IDU In Door Unit SNCP Sub Network Connection Protection

IF Intermediate Frequency SNMP Simple Network Management Protocol

i/f Interface SOH Section Overhead

IP Internet Protocol SRA 4 System Radio Access 4 LCT Local Craft Terminal SSU Synchronization Supply Unit LED Light Emitting Diode STI Single Tributary Interface LOS Loss of Signal STP Spanning Tree Protocol (Ethernet acronym) MAC Media Access Control SVR Software Version Release MSOH Multiplex Section Overhead SW Software MST Member Status VC Virtual Container

MST Multiplex Section termination (SDH acronym)

WFQ Weighted Fair Queuing

MTBF Mean Time Between Failures XPIC Cross-Polar Interference Canceller AP Alternate Pattern Polarity XPIC Cross-Polar Interference Canceller BB Base-Band NMS Network Manager System CC Co-Channel O&M Operation and Maintenance DA Destination Address OC ODU configuration DC/DC DC to DC power converter ODU Outdoor Unit E1 2048 Kbit/s PC Port configuration E3 34368 Kbit/s PCS Physical Coding Sublayer


E/FE Ethernet/Fast Ethernet PCB Printed Circuit Board EMC Electro Magnetic Compatibility PDH Plesiochronous Digital Hierarchy

ETH Ethernet PDU Protocol Data Unit length indicator FD Frequency Diversity PM Performance Monitoring FCS Frame Check Sequence PRC Primary Reference Clock FD Frequency Diversity QAM Quadrature Amplitude Modulation FPGA Field Programmable Gate Array QoS Quality of Service HC High Capacity RF Radio Frequency HDB3 High Density Bipolar order 3 RSOH Regenerator Section Overhead HSBY Hot Stand-By RST Regeneration Section termination

HW Hardware SCN Software configuration networking

I/O Input / Output SDH Synchronous Digital Hierarchy

IDU In Door Unit SNCP Sub Network Connection Protection

IF Intermediate Frequency SNMP Simple Network Management Protocol

i/f Interface SOH Section Overhead

IP Internet Protocol SRA 4 System Radio Access 4 LCT Local Craft Terminal SSU Synchronization Supply Unit LED Light Emitting Diode STI Single Tributary Interface LOS Loss of Signal STP Spanning Tree Protocol (Ethernet acronym) MAC Media Access Control SVR Software Version Release MSOH Multiplex Section Overhead SW Software MST Member Status VC Virtual Container

MST Multiplex Section termination (SDH acronym)

WFQ Weighted Fair Queuing

MTBF Mean Time Between Failures XPIC Cross-Polar Interference Canceller FHy FlexiHybrid


2 SCOPE This document describes release feature, software version components and the relevant HW and SW compatibility. 3 APPLICABILITY Information contained in this document is applicable to Release SVR 4.0 FlexiHybrid and its relation to previous version releases.

4 PRODUCT DESCRIPTION

FLEXIHYBRID , the new Hybrid (high capacity PDH + Ethernet transport in addition to pure transparent transport of STM-1) radio system, is a member of NSN’s extensive telecommunication product portfolio.

4.1 INTRODUTIONS

FLEXIHYBRID is designed for Mobile networks and Fixed / Access networks. The FLEXIHYBRID with his compatibility and high system scalability represents the ideal choice, ensuring cost effective High Capacity applications to the most typical mobile networks topologies. The multiple modulations type (SDH and PDH) over the same hardware platform makes FLEXIHYBRID a single solution for each mobile operator who needs high performances and high spectrum efficiency, but with at the same time just one platform for deploying the entire IP/Eth/SDH/PDH wireless network. FLEXIHYBRID is otherwise the ideal choice for building fixed or access networks with a total wireless approach or also, thanks to its different baseband interfaces, with an easy combination with any existing cable systems. See typical FlexiHybrid use cases:

4.2 FEATURES OF SVR 4.0 CB2 WITH RESPECT TO SVR 3.1 SU2

New features with respect to previous SVR are listed here below. � Improved Spectral Efficiency (new modulation type supported) � 256 QAM � SNCP-like and 2*STM-1 with Enh GbEth Master � BER as switching criterion � Configurable modem output power_Resolving IF Cable Length Issue � Framer Parity Error detection_Resolving Link Fault Issue � Framer parity switch � Bug fixing


4.2 SYSTEM CONFIGURATION

FLEXIHYBRID is a product combining high capacity and high bandwidth efficiency into a single radio platform. Capacity can be doubled as well as bandwidth can be optimized with simple SW operations and with different HW mini modules. The Indoor Unit system has a modular structure suitable for both N3 and 19” rack; modules can be equipped in the different chassis slots. Some modules are mandatory for all IDU configurations and other are expansion or optional. This modularity, see Table 1, ensures customers basic characteristic wireless systems: a high level of scalability.

IDU Slot Module Name

Power Supply Power supply module 611-526/70 ed. 01

Controller Controller2 Module 634-001/91 ed. 01

Modem2 Unified Modem2 612-315/42

Ma

ste

r I/O

Standard2 Master IO mdl 16E1+Eth 612-315/37 ed. 01 Enhanced2 Master IO mdl 16E1+Eth 612-315/39 ed. 01 GigE Master IO mdl 2E1+Eth 612-315/10 GigE Enhanced Master IO with Mux/Demux 612-315/15 MASTER IO MDL 42E1+ETH 612-315/30

Mini I/O STM-1 Optical Mini IO module 612-315/25 ed. 01 STM-1 Electrical Mini IO module 612-315/20 ed. 01

Exp

ansi

on

I/O

16E1 expansion IO module 612-315/05

21E1 expansion IO mdl 612-315/06

2xSTM1 Optical Expansion IO 612-315/43 2xSTM1 Electrical Expansion IO 612-315/44

Table 1 – List of modules used in SVR 3.0.appliances

5 SUPPORTED IDU COMPOSITIONS This section contains the description of all the modules supported by FlexiHybrid and the combinations of the module that are released. In brief, the same IDU compositions of SVR 2.1 are supported. The complete description is here reported for completeness. Figure 1 shows the IDU structure, and the physical position of the slots that can be equipped with different module types. Some modules are mandatory for all IDU configurations and other are expansion or optional.

PS2 Slot (Upper) Controller Slot Expansion Slot Modem West slot (Upper)

PS1 Slot (Lower) Master IO slot Mini IO

slot Modem East slot

(Lower)

Mandatory module, to be equipped for every IDU combinations Mandatory module for 1+1 and 2+0 IDU combinations Optional module, to be equipped for interface expansion

Figure 1 – IDU slots (frontal view)For each slot the Table 2 lists the available module types that can be plugged in the slot.


Table 2 – List of modules supported in FlexiHybrid appliance

IDU Slot Module

Short Name Short Module Description Part Number Identification

Code

SVR that support the

module

Chassis Chassis Wired rack 628-588/05 From SVR 1.0 Power Supply [1 or 2]

PS Power Supply 611-526/70 From SVR 1.1

Controller Controller Controller unit 634-001/81

From SVR 1.1 but not in SVR 2.0

Controller2 Controller with enhanced capabilities

634-001/91

From SVR 2.0

Modem [East or West]

Modem7-56 Wideband Modem/IF module 612-315/02 From SVR 1.2

Modem2 Unified modem 612-315/42 From SVR 3.0

Mas

ter

I/O

Standard Standard IO module with 16E1+2Ethernet

612-315/01 From SVR 1.0 but not in SVR 2.0.

Enhanced Enhanced Master I/O module 612-315/15 From SVR 1.0 but not in SVR 2.0

GigE GigE Master I/O module with 2E1+Eth

612-315/10 From SVR 1.0

EnhGigE Enhanced GigE Master IO module w/2E1+Ethernet

612-315/16 From SVR 2.1

42E1 Master 42E1 IO module w/ 42E1+Ethernet

612-315/03 From SVR 1.2

Standard2 Standard master module with improved Ethernet capabilities

612-315/37 From SVR 2.0

Ehnanced2 Enhanced master module with improved Ethernet capabilities

612-315/39 From SVR 2.0

Mini I/O STM1o STM-1 Optical Mini IO module 612-315/25 From SVR 1.0

STM1e STM-1 Electrical Mini IO module

612-315/20 From SVR 1.0

Expansion I/O

Exp 16E1 16E1 expansion IO module 612-315/05 From SVR 1.0

Exp 21E1 21E1 expansion IO module 612-315/06 From SVR 1.2

2xSTM-1 o/e

2xSTM-1 Expansion IO Module (two core)

612-315/43/612-315/44

From SVR 3.0

The combinations of modules supported in each SVR are described in Table 2.. Each combination is here named as “IDU Composition”. Each IDU composition has a short name that summarise the user payload interface and the main modules. The “ID” column is for cross reference with the feature description.


6 SUPPORTED FUNCTIONALITIES

The SVR 4.0 support modules in Table1. All ODU of HC family in AP/CC configuration are supported (6/7/8/11/13/15/18/23/26 GHz are until now certificated with SVR 1.3) and ODU HC AP 32/38GHz have been included from SVR 1.4. Following features are supported by SVR 4.0 CB2( in bold the new feature respect to the 3.1 SU2):

� Channel bandwidth: 14MHz and 28MHz,7MHz � Modulations: QPSK, 4QAM, 16QAM, 32QAM, 64QAM, 128QAM. � Payload combination: up to 63E1+Eth,Stm1,see Table 2 � System Type: Standard mode (1+0) � System Type protected diversity (1+1 Freq. Div.) � System Type Protected non-diversity (1+1 Hot StBy), revertive switch � System Type East/West mode (2+0 different destination and Protected Ring configuration) � System Type East/East (only for GigE Enhanced Master IO and Gigabit Eth Master I/O ) � RF band for B600 declaration: 7/8/11/13/15/18/23/26/32/38 GHz, see Table 3 for the expected

RSL. � HW is E1 and T1 capable. Only E1 is requested � HW is STM1 and OC3 capable. Only STM1 is requested. � STM-1 Mux/Dmux capability. � QoS functionality, tributary side and radio side( this functionality is not supported by Standard

Master IO and Enhanced Master IO). � Serviceability (ready to be used for next Sw upgrade fro SVR 2.1.1to SVR>2.1.1) � ACM (certified for 15GHz-18GHz and 23GHz) See details in the last chapter (cap 11) about the

behavior of this feature. � Fault management trough SNMP it managed by NetWiever � VLAN Functionality and Management � Performance Monitoring (Tributary quality/unavailability; RPS; Receive and Transmit Power level; Ethernet

Statistics.) � Unified Modem2 introduced to replace the old modem (no new features). Unified Modem 2 is compatible

with old modem through radio. But installing both unified modem2 and old modem on one IDU should be avoided, they can not work together in one IDU.

� HW/SW separation are introduced � SNCP-like protection introduced on Standard2, Enhanced2 and 42E1 master IO. � Longer cable support for ODU CNT type.

Cable Type Max lengths with ODU-HC AP/CC

(SDH2) Max lengths with ODU-HC AP

(Remec) CNT-300 190 m 150 m Cable 1/2” 250 m 230 m

� Store/Restore Configuration supported via WebLCT. � Six new modes are introduced. � Improved Spectral Efficiency (new modulation type supported)_New Pilot Frame for Radio enhancement � 256 QAM � SNCP-like and 2*STM-1 with Enh GbEth Master

FPGA Type SNCP-Like

2xSTM-1 Support

Mux/Demux Capability for Mini I/O

4130_CG Yes Yes No

4130_SG No No Yes � RSTP � Enhancement on Alarm processing mechanism � BER as switching criterion


� Framer Parity Error detection_Resolving Link Fault Issue � Configurable modem output power_Resolving IF Cable Length Issue � Link Evaluation_Monitoring the performance in radio link � Framer Parity Fast switch (*)

(*) This feature has been introduced in the 4.0CB2 In the following paragraphs, are illustrated some more details about the new features introduced

7 2xSTM1e/o support in Expanded Slot and SNCP-like protection for EnhGigE Master I/O module

In previous release when the Master Slot is equipped with EnhGigE master I/O module, it is not allowed to support 2STM1e/o in Expanded Slot. In SVR4.0 it is required to support 2STM1e/o with EnhGigE and SNCP like protection with EnhGigE. Due to the FPGA resource limitation of EnhGigE master I/O module, SNCP-like protection and MUX/DEMUX capability can’t be supported at the same time on the EnhGigE master I/O module Since 2xSTM-1e/o module supports the MUX/DEMUX capability on its own FPGA, when 2xSTM-1e/o is inserted in the Expanded Slot with EnhGigE master module, it can rely on 2xSTM-1e/o module to realize the MUX/DEMUX capability and have SNCP like protection. In this way, both SNCP-Like and Mux/Demux capability can be supported in the EnhGigE Master I/O+2STM1e/o.

Table 8a EnhGigE FPGA capability

FPGA Type SNCP-Like 2xSTM-1 Support

Mux/Demux Capability

4130_CG Yes Yes No 4130_SG No No Yes

For configurations with EnhGigE and STM-1 mini I/O, SNCP-Like and Mux/Demux can’t co-exist because STM-1 mini I/O’s Mux/Demux relies on the master I/O FPGA’s capability, as can be seen in Table a, there are two FPGA versions: 4130_CG can support SNCP-Like, but it can’t support Mux/Demux; 4130_SG can support Mux/Demux, but it can’t support SNCP-Like. Here’s the summary of the capability of configurations with EnhGigE:

Table 3a SNCP-Like and Mux/Demux Capability Summary for EnhGigE Configurations

Configuration FPGA version SNCP-Like Mux/Demux Capability 9o/10o/19o/20o 4130_CG Yes No

STM-1 in Mini I/O will be forced to transparent mode.

4130_SG No Yes STM-1 in Mini I/O can support Mux/Demux.

25o/26o 4130_CG Yes Yes The 2xSTM-1 in expansion IO supports Mux/Demux.

4130_SG This is not the FPGA for 25o and 26o. The SBI of SVR4.0 will contain the 4130_CG FPGA, this is in order for easy upgrading to SNCP capability of 9o/10o/19o/20o/25o/26o. In SVR3.1, configurations 9o/10o/19o/20o could support the Mux/Demux capability on Mini I/O STM-1, Mux/Demux capability will be lost if user upgrades them into the SNCP-Like function in SVR4.0, and


therefore, traffic will also be lost, user shall implement a second step upgrade to download the FPGA back to 4130_SG independently to recover the Mux/Demux capability. This kind of decision is based on two factors

8 BER switching triggered via SNCP-Like

SNCP-Like is used to protect E1 traffic in ring topology when part of the ring has failure, traffic will go through the unaffected part of the ring to achieve high availability. The main criteria to trigger SNCP-Like protection is E1 AIS. It is observed in the field that BTS’s service will not work when the E1 error rate is over 10-3, and the BTS’s service quality will be degraded when the E1 error rate is from 10-6 to 10-4. It is desired that SNCP-Like can also protect the E1 in this kind of case. The FlexiHybrid estimates the link BER. When the link BER is above a Trigger Threshold for the Holdoff duration the FlexiHybrid enters a Signal Degraded state. During the Signal Degraded state, the FlexiHybrid insert AIS on all E1 payloads received from the degraded link. While in the Signal Degraded state, if the link BER falls below a Clear Threshold for any duration the FlexiHybrid exit the Signal Degraded state. When exiting the Signal Degraded state the FlexiHybrid removes the AIS insertion on all E1 payloads received from the previously degraded link. The FlexiHybrid shall raise a Signal Degraded State alarm while in the Signal Degraded state.

9 Configurable modem output power

Starting from release 4.0 the modem output power is configurable is in order to better suit the modem cable length, two options are available: +5dbm/-5dbm, when the modem cable is longer than 100m, it is suggested to set the modem output power to +5dbm, when the modem cable is shorter than 100m, it is suggested to set the modem output power to -5dbm, the default value is -5dbm.

10 Supported licensing Configuration of R4.0 (Improved Spectral Efficiency)

SW license available for the following features

Improved Spectral Efficiency (new modulation type supported) 256 QAM

The enhanced spectral efficiency is enable on BSW 4.0 via additional license and is managed by the unified modem two only.

The licence “high spectral efficiency” released with 4.0, allows to have new modulation and channel bandwidth. The new setting introduced are the following

� Enhanced spectrum efficiency modes :32QAM and 64QAM on 7 MHz, 64QAM and 128QAM on 14MHz and 256 QAM on 28 MHz channel spacing

The procedure for upgrading to enanched spectral efficiency, is described in manual


The required combination of modulation format and channel spacing.

Table 3a: Spectral efficiency 7MHz 14MHz 28MHz XPIC

on 28MHz

QPSK X (1) X (1) X (1) 16QAM X (1) X (1) X (1) 32QAM X X (1) X (1) 64QAM X X X (1) 128QAM X X (1) 256QAM X

(1) = supported also by modem in SVR 3.0.

The SVR 4.0 with licence high spectral efficiency enabled(code 00062551 ), supported new modes ( highlighthed in bold) are shown in Table 10

ROW ID

Mode Name Modulation Channel Bandwidth

E1 Ethernet Data

(Mbps)

STM-1 Licence ETSI Class

Radio interface Capacity (Mbit/s)

1 7.4-8M QPSK 7 MHz 0 8 0 L1 2 9.58

2 7.4-2e4M QPSK 7 MHz 2 4 0 L1 2 10.58

3 7.4-4e QPSK 7 MHz 4 0 0 L1 2 9.58

4 14.4-19M QPSK 14 MHz 0 19 0 L1 2 20.53

5 14.4-2e15M QPSK 14 MHz 2 15 0 L1 2 20.53

6 14.4-4e11M QPSK 14 MHz 4 11 0 L1 2 20.53

7 14.4-8e3M QPSK 14 MHz 8 3 0 L1 2 20.53

8 7.16-17M 16QAM 7 MHz 0 17 0 L1 4L 18.58

9 7.16-2e13M 16QAM 7 MHz 2 13 0 L1 4L 19.58

10 7.16-4e9M 16QAM 7 MHz 4 9 0 L1 4L 18.58

11 7.16-8e1M 16QAM 7 MHz 8 1 0 L1 4L 18.58

22 28.4-38M QPSK 28 MHz 0 38 0 L2 2 40,38

23 28.4-2e34M QPSK 28 MHz 2 34 0 L2 2 40,38

24 28.4-4e30M QPSK 28 MHz 4 30 0 L2 2 40,38

25 28.4-8e22M QPSK 28 MHz 8 22 0 L2 2 40,38

26 28.4-16e6M QPSK 28 MHz 16 6 0 L2 2 40,38


27 28.4-18e2M QPSK 28 MHz 18 2 0 L2 2 40,38

28 14.16-38M 16QAM 14 MHz 0 38 0 L2 4L 39,52

29 14.16-2e33M 16QAM 14 MHz 2 33 0 L2 4L 39,52

30 14.16-4e29M 16QAM 14 MHz 4 29 0 L2 4L 39,52

31 14.16-8e21M 16QAM 14 MHz 8 21 0 L2 4L 39,52

32 14.16-16e5M 16QAM 14 MHz 16 5 0 L2 4L 39,52

33 14.16-18e1M 16QAM 14 MHz 18 1 0 L2 4L 39,52

34 7.32-22M 32QAM 7 MHz 0 22 0 L2 4L 23,88

35 7.32-2e18M 32QAM 7 MHz 2 18 0 L2 4L 23,88

36 7.32-4e14M 32QAM 7 MHz 4 14 0 L2 4L 23,88

37 7.32-8e6M 32QAM 7 MHz 8 6 0 L2 4L 23,88

38 7.64-27M 64QAM 7 MHz 0 27 0 L2 5B 28,74

39 7.64-2e23M 64QAM 7 MHz 2 23 0 L2 5B 28,74

40 7.64-4e19M 64QAM 7 MHz 4 19 0 L2 5B 28,74

41 7.64-8e11M 64QAM 7 MHz 8 11 0 L2 5B 28,74

49 28.16-78M 16QAM 28 MHz 0 78 0 L3 4L 80,76

50 28.16-2e73M 16QAM 28 MHz 2 73 0 L3 4L 80,76

51 28.16-4e69M 16QAM 28 MHz 4 69 0 L3 4L 80,76

52 28.16-8e61M 16QAM 28 MHz 8 61 0 L3 4L 80,76

53 28.16-16e45M 16QAM 28 MHz 16 45 0 L3 4L 80,76

54 28.16-18e41M 16QAM 28 MHz 18 41 0 L3 4L 80,76

55 28.16-32e13M 16QAM 28 MHz 32 13 0 L3 4L 80,76

56 14.32-48M 32QAM 14 MHz 0 48 0 L3 4H 50,43

57 14.32-2e44M 32QAM 14 MHz 2 44 0 L3 4H 50,43

58 14.32-4e40M 32QAM 14 MHz 4 40 0 L3 4H 50,43

59 14.32-8e32M 32QAM 14 MHz 8 32 0 L3 4H 50,43

60 14.32-16e16M 32QAM 14 MHz 16 16 0 L3 4H 50,43

61 14.32-18e12M 32QAM 14 MHz 18 12 0 L3 4H 50,43

62 14.64-58M 64QAM 14 MHz 0 58 0 L3 5B 60,10

63 14.64-2e53M 64QAM 14 MHz 2 53 0 L3 5B 60,10

64 14.64-4e49M 64QAM 14 MHz 4 49 0 L3 5B 60,10

65 14.64-8e41M 64QAM 14 MHz 8 41 0 L3 5B 60,10

66 14.64-16e25M 64QAM 14 MHz 16 25 0 L3 5B 60,10

67 14.64-18e21M 64QAM 14 MHz 18 21 0 L3 5B 60,10

74 14.128-68M 128QAM 14 MHz 0 68 0 L4 5B 70,44


75 14.128-2e63M 128QAM 14 MHz 2 63 0 L4 5B 70,44

76 14.128-4e59M 128QAM 14 MHz 4 59 0 L4 5B 70,44

77 14.128-8e51M 128QAM 14 MHz 8 51 0 L4 5B 70,44

78 14.128-16e35M 128QAM 14 MHz 16 35 0 L4 5B 70,44

79 14.128-18e31M 128QAM 14 MHz 18 31 0 L4 5B 70,42

80 14.128-32e3M 128QAM 14 MHz 32 3 0 L4 5B 70,42

82 28.32-100M 32QAM 28 MHz 0 100 0 L4 4H 103,42

83 28.32-2e95M 32QAM 28 MHz 2 95 0 L4 4H 103,42

84 28.32-4e91M 32QAM 28 MHz 4 91 0 L4 4H 103,42

85 28.32-8e83M 32QAM 28 MHz 8 83 0 L4 4H 103,42

86 28.32-16e67M 32QAM 28 MHz 16 67 0 L4 4H 103,42

87 28.32-18e63M 32QAM 28 MHz 18 63 0 L4 4H 103,42

88 28.32-32e35M 32QAM 28 MHz 32 35 0 L4 4H 103,42

89 28.32-42e14M 32QAM 28 MHz 42 14 0 L4 4H 103,42

105 28.256-160M 256QAM 28 MHz 0 160 0 L5 6A 175,04

106 28.256-2e160M 256QAM 28 MHz 2 160 0 L5 6A 171,02

107 28.256-4e152M 256QAM 28 MHz 4 152 0 L5 6A 175,04

108 28.256-8e144M 256QAM 28 MHz 8 144 0 L5 6A 175,04

109 28.256-16e128M 256QAM 28 MHz 16 128 0 L5 6A 175,04

110 28.256-18e128M 256QAM 28 MHz 18 128 0 L5 6A 175,04

111 28.256-32e100M 256QAM 28 MHz 32 100 0 L5 6A 175,04

112 28.256-42e80M 256QAM 28 MHz 42 80 0 L5 6A 175,04

113 28.256-63e38M 256QAM 28 MHz 63 38 0 L5 6A 175,04

114 28.256-1s16M 256QAM 28 MHz 0 16 1 L5 6A 175,24

119 28.64-16e88M 64QAM 28 MHz 16 88 0 L5 5B 124,45

120 28.64-18e83M 64QAM 28 MHz 18 83 0 L5 5B 124,45

129 28.128-16e100M 128QAM 28 MHz 16 100 0 L5 5A 151,24

130 28.128-26e100M 128QAM 28 MHz 26 100 0 L5 5A 139,61

131 28.128-2e136M 128QAM 28 MHz 2 136 0 L5 5A 157,68

132 28.128-4e136M 128QAM 28 MHz 4 136 0 L5 5A 151,24

133 28.128-8e128M 128QAM 28 MHz 8 128 0 L5 5A 151,24

134 28.128-16e112M 128QAM 28 MHz 16 112 0 L5 5A 151,24

135 28.128-18e104M 128QAM 28 MHz 18 104 0 L5 5A 151,24

136 28.128-32e80M 128QAM 28 MHz 32 80 0 L5 5A 151,24

137 28.128-42e60M 128QAM 28 MHz 42 60 0 L5 5A 151,24


138 28.128-63e18M 128QAM 28 MHz 63 18 0 L5 5A 151,24

139 28.128-1s 128QAM 28 MHz 0 0 1 L5 5A 158,16

140 28.128-P46-100M 128QAM 28 MHz 0 46 100 L5 5A 151,24

141 28.128-P74-72M 128QAM 28 MHz 0 74 72 L5 5A 151,24

142 28.128-4eP72-72M 128QAM 28 MHz 4 72 72 L5 5A 157,68

143 28.128-8eP68-67M 128QAM 28 MHz 8 68 67 L5 5A 157,68

144 28.128-12eP64-63 128QAM 28 MHz 12 64 63 L5 5A 157,68

145 28.128-16eP60-60 128QAM 28 MHz 16 60 60 L5 5A 157,68

150 28.256-P100-69M 256QAM 28 MHz 0 100 69 L5 6A 175,04

151 28.256-P85-84M 256QAM 28 MHz 0 85 84 L5 6A 175,04

152 28.256-4eP80-80M 256QAM 28 MHz 4 80 80 L5 6A 175,04

153 28.256-8eP76-76M 256QAM 28 MHz 8 76 76 L5 6A 175,04

154 28.256-12eP72-72 256QAM 28 MHz 12 72 72 L5 6A 175,04

155 28.256-16eP68-68 256QAM 28 MHz 16 68 68 L5 6A 175,04

Table 10. FHY IDU supported modes-payload combination

RowID: It is the ID assigned to the row and it univocally identifies the mode (License masking is based on this number and link configuration negotiates this number)

Mode Name: It is the name of the mode displayed by Web LCT in the choice list. Mode Name can have a

maximum of 16 characters from this list only: “ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 -.” For this reason the following convention has been adopted:

<bandwidth>.<modulation>-<number of E1>e<Eth Mbit/s>M<number of STM1>s

Where: <bandwidth>= Bandwidth value in MHz <modulation> = Modulation levels, 4 for QPSK, 16 for 16QAM, Etc… e = short notation for E1 M = short notation for Mbit/s s = short notation for STM1 Examples:

� 28.128-8e128M = 28MHz bandwidth, 128QAM that transports 8E1 and 128Mbit/s of Ethernet payload

� 56.128-16e100M1s = 28MHz bandwidth, 128QAM that transports 16E1, 100Mbit/s of Ethernet and 1 STM1.

There is one exception: the PLUS modes are named by inserting “Plus” after modulation. The “Plus” tag is followed by the Mbit/s configured for Port1 and Port2 respectively: <bandwidth>.<modulation>-P<Eth Mbit/s for Port1>-< Eth Mbit/s for Port2>M


11 Framer Parity Error detection_Resolving Link Fault Issue and Framer parity switch

The FHY implement a two-stage mechanism to detect errors that may occur between the Modem module and theMaster IO module within the FHY chassis. Stage 1-Framer Parity Error detection: Detect errors and provide local error correction. Stage 2-Framer parity switch: Detect uncorrectable errors and initiate higher level protection mechanisms. The Stage 1 and Stage 2 mechanisms are independent. In the event that the Stage 1 mechanism is unable to correct bit errors or is not in use, the Stage 2 mechanism will detect uncorrected bit-errors and initiate higher level protection mechanisms. The higher level protection mechanisms may include: 1. AIS insertion on E1 channels, 2. Spanning-Tree topology change, or 3. Remote 1+1 Hot-Standby protection switch. The Stage 1 and Stage 2 mechanisms are shown in Figure 1. Details on the feature implementation are in the manual

12 SYSTEM TYPE COMPATIBILITY

SVR 4.0 System types

Units Code 1+0 (std) Est/West 2+0 est/est 1+1 FD 1+1 HSBY

IDU FHY 16E1-Eth 1+0 705-400/47B,D,E ed 01

x


x

IDU FHY 2E1-GigE 1+0 705-400/49D,E ed 01

x


x

IDU FHY STM1e-16E1-Eth 1+0 705-400/51D,E ed 01

x

IDU FHY STM1o-16E1-Eth 1+0 705-400/52D,E ed 01

x

IDU FHY 16E-Eth 1+1 705-400/53B,D,E ed 01

x

x

x

x


x

x

x

x


x

x

x

x

x

IDU FHY 18E1-GigE 1+1 x

x

x

x

x


705-400/56D,E ed 01

IDU FHY STM1e-16E1-Eth 1+1 705-400/57D,E ed 01

x

x

x

x

x

IDU FHY STM1o-16E1-Eth 1+1 705-400/58D,E ed 01

x

x

x

x

x

IDU FHY 42E1-Eth1+0 705-400/59D,E ed 01

x

IDU FHY 63E1-Eth1+0 705-400/60D,E ed 01

x

IDU FHY 42E1-Eth1+1 705-400/61D,E ed 01

x

x

x

x

x

IDU FHY 63E1-Eth1+1 705-400/62D,E ed 01

x

x

x

x

x

IDU FHy STM1o-18E1-EnhGigE 1+0 705-400/44D,E ed 01

x

IDU FHySTM1o-18E1-EnhGigE 1+1 705-400/46D,E ed 01

x x x x x

IDU FHySTM1e-18E1-EnhGigE 1+0 705-400/43D,E ed 01

x

IDU FHySTM1e-18E1-EnhGigE 1+1 705-400/45D,E ed 01

x x x x x

IDU FHy 2xSTM1e-16E1-Eth 1+0 705-400/63D, E ed 01

x

IDU FHy 2xSTM1e-16E1-Eth 1+1 705-400/64D, E ed 01

x x x x x

IDU FHy 2xSTM1o-16E1-Eth 1+0 705-400/65D, E ed 01

x

IDU FHy 2xSTM1o-16E1-Eth 1+1 705-400/66D, E ed 01

x x x x x

IDU FHy 2xSTM1o-EnhGigE 1+0 705-400/67D, E ed 01

x

IDU FHy 2xSTM1o-EnhGigE 1+1 705-400/68D, E ed 01

x x x x x

IDU FHy 2xSTM1e-EnhGigE 1+0 705-400/69D, E ed 01

x

IDU FHy 2xSTM1e-EnhGigE 1+1 705-400/69D, E ed 01

x x x x x

ODU HC AP/CC : 7 GHz 735-221/07

x

x

x

x

x

ODU HC AP/CC : 8 GHz 735-221/08

x

x

x

x

x

ODU HC AP/CC : 11 GHz 735-221/11

x

x

x

x

x

ODU HC AP/CC : 13 GHz 735-221/13

x

x

x

x

x

ODU HC AP/CC 15 GHz 735-221/15

x

x

x

x

x


x

x

x

x

x


x

x

x

x

x


x

x

x

x

x


ODU HC AP 32 GHz 735-231/32

x

x

x

x

x

ODU HC AP 38 GHz 735-231/38

x

x

x

x

x

Controller Unit 634-001/91

x

x x

x

x

Table 4 – HW/Configuration compatibility

13 PRODUCT COMPOSITION

The following table describes the software components for the SVR 4.0 and the relevant hardware compatibility.

FLEXIHYBRID : S.V.R. 4.0 WITHOUTENANCHED SPECTRAL EFFICIENCY

Units Code sw edit.

code ext.

IDU FHY 16E1-Eth 1+0 705-400/47B ed 01, /47D ed 01,

/47E ed 01 SVR 4.0 CB2 -


/53E ed 01 SVR 4.0 CB2 -


/48E ed 01 SVR 4.0 CB2 -


/54E ed 01 SVR 4.0 CB2 -

IDU FHY STM1e-16E1-Eth 1+0 705-400/51D ed 01, /51E ed 01

SVR 4.0 CB2 -


SVR 4.0 CB2 -

IDU FHY STM1o-16E1-Eth 1+0 705-400/52D ed 01, /52E ed 01

SVR 4.0 CB2 -


SVR 4.0 CB2 -

IDU FHY 2E1-GigE 1+0 705-400/49D ed 01, /49E ed 01

SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -

IDU FHY 42E1-Eth1+0 705-400/59D ed 01, /59E ed 01

SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -



SVR 4.0 CB2 -

IDU FHySTM1e-18E1-EnhGigE 1+0 705-400/43D ed 01, /43E ed 01 SVR 4.0 CB2 -


IDU FHy STM1o-18E1-EnhGigE 1+0 705-400/44D ed 01, /44E ed 01 SVR 4.0 CB2 -

IDU FHySTM1o-18E1-EnhGigE 1+1 705-400/46D ed 01, /46E ed 01 SVR 4.0 CB2 -

IDU FHy 2xSTM1e-16E1-Eth 1+0 705-400/63D ed 01, /63E ed 01 SVR 4.0 CB2 -


IDU FHy 2xSTM1o-16E1-Eth 1+0 705-400/65D ed 01, /65E ed 01 SVR 4.0 CB2 -


IDU FHy 2xSTM1o- EnhGigE 1+0 705-400/67D ed 01, /67E ed 01

SVR 4.0 CB2 -


SVR 4.0 CB2 -

IDU FHy 2xSTM1e- EnhGigE 1+0 705-400/69D ed 01, /69E ed 01

SVR 4.0 CB2 -


SVR 4.0 CB2 -

Controller2 Unit 634-001/91 ed 01

SVR 4.0 CB2 -

Unified MODEM2 612-315/42 ed 01

U-3.3.4 -

2xSTM-1 Optical Expansion IO 612-315/43 ed 01 4312_EX03.01.15 -

2xSTM-1 Electriccal Expansion IO

612-315/44 ed 01 4312_EX03.01.15 -

ODU HC AP/CC: 06L/6U, 07,08 GHz

735-221/06, */07,*/08 5.7

507 � (***)

ODU HC AP/CC: 11,13 GHz 735-221/11,*13 5.7

507 � (***)

ODU HC AP/CC: 15,18,23,26 GHz 735-221/15, */18, */23, */26 5.7

507 � (***)


ODU HC AP : 32, 38 GHz 735-231/32, */38

6.97 697 �

(#)

CD for “ SW GROUP FLEXIHYBRID ” (SW IDU)

(SW ODU-HC-AP/CC) (SW ODU-HC-AP)

00062549(SI)

00062549CB.01 (VI)

Available with CD

Table 5-1 – Product HW/SW composition

FLEXIHYBRID : S.V.R. 4.0 CB2 WITH ENANCHED SPECTRAL EFFICIENCY

Units Code sw edit.

code ext.


/47E ed 01 SVR 4.0 CB2 -


/53E ed 01 SVR 4.0 CB2 -


/48E ed 01 SVR 4.0 CB2 -


/54E ed 01 SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -




IDU FHy STM1o-18E1-EnhGigE 1+0 705-400/44D ed 01, /44E ed 01 SVR 4.0 CB2 -

IDU FHySTM1o-18E1-EnhGigE 1+1 705-400/46D ed 01, /46E ed 01 SVR 4.0 CB2 -






SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -


SVR 4.0 CB2 -

Controller2 Unit 634-001/91 ed 01

SVR 4.0 CB2 -

Unified MODEM2 612-315/42 ed 01

U-3.3.4 -

2xSTM-1 Optical Expansion IO 612-315/43 ed 01 4312_EX03.01.15

2xSTM-1 Electriccal Expansion IO

612-315/44 ed 01 4312_EX03.01.15

ODU HC AP/CC: 06L/6U, 07,08 GHz

735-221/06, */07,*/08 5.7

507 � (***)

ODU HC AP/CC: 11,13 GHz 735-221/11,*13 5.7

507 � (***)

ODU HC AP/CC: 15,18,23,26 GHz 735-221/15, */18, */23, */26 5.7

507 � (***)

ODU HC AP : 32, 38 GHz 735-231/32, */38

6.97 697 �

(#) (*)Licence for enanched spectral

efficiency 00062551.03

(VI) License for Enhanced

Spectral efficiency e-media


(immaterial delivery Available in NOLS)

00062567CB.01 (VI)

License for Enhanced Spectral efficiency on cd

(material delivery)

Table 5-2 – Product HW/SW composition

(1) Note: SVR 4.0 is compatible also with N2-V7C-W2 ( mode file).In case of upgrading in field and the customer wants to

use standard (not pilot) mode, If you have already in field the mode file N2-V7C-W2 ( available with R3.X),It is not necessary to update the modes file.

(2) If the enanched spectral efficiency is needed, the new modes file available with the licence “enanched spectral efficiency”has to be loaded (**) : firware SW edition.

(***) : SW extension related to the SW loaded into the SW Group Code and IF Subunit and not into the 735-221/xy; the extension will be written as simple text into the label 216-36/177 foreseen into the 735-221/xy ext-HW list. (****) : 6.00 minimum version of “Microsoft Internet Explorer” is required (#):ODU HC AP : : SW extension related to the SW loaded into the Outdoor Unit ; the extension will be written as simple text into the label as descripted into 735-231/xy_PA document

(*) IDU SVR 4.0 CB2 components: Component Reprogramming Screen Version

Kernel 0.3.5

Application 2.11.76x

ODU N2-2.11.76

Modes (without pilot) N2-V7C-W3

Modes (pilot) N2-V8C-W3

Channels CN-1

ODU HC AP-CC East/West Firmware 5.7

ODU HC AP East/West Firmware 6.97

Bootloader 1.3.3

Modem East/West firmware W-1.1.19v8

Modem East/West FPGA 18

Unified Modem2 East/West firmware U-3.3.4

Unified Modem2 East/West FPGA 4700_PI02.03.01

Standard2 Master IO (612-315/37) 4101_ST03.13.00

GigE Master IO (612-315/10) 4110_GE03.13.00

GigE Enhanced Master IO (612-315/16) Support Mux/demux

4130_SG03.13.00

GigE Enhanced Master IO (612-315/16) Support SNCP-like

4130_CG03.13.00

Enhanced2 Master IO (612-315/39) 4121_ST03.13.00

16E1 expansion IO (612-315/05) 4132_EX03.01.02

42E1 Master IO (612-315/03) 4142_SP03.13.00

21E1 expansion IO (612-315/06) 4163_EX03.01.02

Controller2 (634-001/91) 4501_v8


Component Reprogramming Screen Version

2xSTM-1 fiber expansion IO(612-315/43) 4312_EX03.01.15

2xSTM-1 electrical expansion IO (612-315/44)

4312_EX03.01.15

(**) : firware SW edition.

(***) : SW extension related to the SW loaded into the SW Group Code and IF Subunit and not into the 735-221/xy; the extension will be written as simple text into the label 216-36/177 foreseen into the 735-221/xy ext-HW list. (****) : 6.00 minimum version of “Microsoft Internet Explorer” is required (#):ODU HC AP : : SW extension related to the SW loaded into the Outdoor Unit ; the extension will be written as simple text into the label as descripted into 735-231/xy_PA document

Table 6 – SVR 4.0 CB2 version composition

13.1 SW UPGRADING

SW GROUP FLEXIHYBRID ” (SW IDU)

(SW ODU-HC-AP/CC) (SW ODU-HC-AP)

00062548 (SI)

00062548.03 (VI)

Available in NOLS

Table 8-1 –Sw upgrading (without enhanced spectral efficiency)

If the enanched spectral efficiency is required, the Licence for enanched spectral efficiency has to be ordered with SW upgrading(00062548.03). The licence is available with material and immaterial delivery.

00062551.03 (VI)

00062551 (SI)

License for Enhanced Spectral efficiency e-media

(immaterial delivery Available in NOLS)

00062567CB.01 (VI)

00062567 (SI)

License for Enhanced Spectral efficiency on cd

(material delivery)


14 COMPATIBILITY RULES BETWEEN HW AND SW VERSIONS

NOTE:From SVR 3.0 Codes 7.x(*) is no longer used. Please refer to table 5 for IDU composition.

FHy– SW/HW Cross-Compatibility for upgrade

SVR (System Version Release)

1.2 1.3 1.4 2.1.1 2.2 3.0 3.1 3.1SU1 3.1 SU2 4.0 4.0 CB2

SW issue SW issue SW issue SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

705-400/03A,

/03B, /03C 7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*)

SVR SVR SVR SVR SVR SVR

3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

705-400/03D, /03E, /03F

705-400/04A,

/04B, /04C 7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*)


3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

705-400/04D, /04E, /04F

705- 7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*) SVR SVR SVR SVR SVR SVR

CNSt

CNGig

CN42E1

2

CNEn Se

CNSt

1

CN42E1

CNGig

1

CNEn So

16E

32E1

STM1

STM1

42E1

63E1

GigE

GigE+18E1

1+0/1+1

Se

1

So

CNTSt

CNTSt

CNTEnh

CNTEnh

S

Gig

42E12

En Se

S1

42E1

Gig1

En So

CNT

CNT

CNT

CNT

CNT

CNT

CNT

CNT

Se

So

CNTEnh

CNTEnh

CNTne

Enhne

St

ne

New Controller 4501

New Enhanced Master 4121

New Standard Master 4101

1+0/1+1 1+0/1+1

HW configuration supported in SVR 3.1 and back Hw modules compatibility


400/13A, /13B, /13C

3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

705-400/13D, /13E, /13F

705-400/15A,

/15B, /15C 7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*)


3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

705-400/15D, /15E, /15F

705-400/16A,

/16B, /16C 7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*)


3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

705-400/16D, /16E, /16F

705-400/18A,

/18B, /18C 7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*)


3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

705-400/18D, /18E, /18F

634-001/81

7.3(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*) SVR SVR SVR SVR SVR SVR 3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

634-001/91

N/A N/A N/A N/A N/A SVR SVR SVR SVR SVR SVR

3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

612-315/30

W-1.1.2 (**)

W-1.1.2.1.1(**)

W-1.1.2.1.10 (**)

W-1.1.13 (**)

W-1.1.13 (**)

W-1.1.19

W-1.1.19

W-1.1.19

W-1.1.19v6

W-1.1.19v8

W-1.1.19v8

612-315/42

N/A N/A N/A N/A N/A U-3.0.0.4

U-3.0.8

U-3.0.8

U-3.0.8v2 U-3.3.2 U-3.3.2

735-221/06

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/07

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/08

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/11,*13

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/15

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/18,

*/23 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/18,

*/26 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-231/32,

*/38 ns ns 6.97 6.97 6.97 6.97 6.97 6.97 6.97 6.97 6.97

1.2 1.3 1.4 1.6 1.7 1.8 1.9 1.1 1.11 1.12

Table 9 – HW/SW compatibility for upgrade


NOTE:SVR 1.1 and SVR 1.0 are not present in the table below,because the Sw upgrade need also an Hw upgrade of the modem unit.After this HW upgrade follow the procedure described in TRPR-WDPE09287-1 (R1 D.1) document , that include also the memory expantion of the controller unit.

FHy– SW/HW Cross-Compatibility for upgrade from SVR 2.0


2 2.1.1 2.2 3 3.1 3.1SU1 3.1SU2 4.0 4.0

UNITS SW issue

SW issue SW issue SW issue SW issue SW issue SW issue SW issue SW issue

IDU FHY 16E1-Eth 1+0

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/27A,

/27B, /27C

705-400/27D, /27E, /27F


7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/28A,

/28B, /28C

705-400/28D, /28E, /28F

IDU FHY 2E1-GigE 1+0

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/29A,

/29B, /29C

705-400/29D, /29E, /29F


7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/30A,

/30B, /30C

705-400/30D, /30E, /30F

IDU FHY STM1e-16E1-

Eth 1+0

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2


705-400/31A, /31B, /31C

705-400/31D, /31E, /31F

IDU FHY STM1o-16E1-

Eth 1+0

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/32A,

/32B, /32C

705-400/32D, /32E, /32F

IDU FHY 16E-Eth 1+1

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/33A,

/33B, /33C

705-400/33D, /33E, /33F


7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/34A,

/34B, /34C

705-400/34D, /34E, /34F


7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/35A,

/35B, /35C

705-400/35D, /35E, /35F


7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/36A,

/36B, /36C

705-400/36D, /36E, /36F


IDU FHY STM1e-16E1-

Eth 1+1

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/37A,

/37B, /37C

705-400/37D, /37E, /37F

IDU FHY STM1o-16E1-

Eth 1+1

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/38A,

/38B, /38C

705-400/38D, /38E, /38F

IDU FHY 42E1-Eth1+0

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/39A,

/39B, /39C

705-400/39D, /39E, /39F

IDU FHY 63E1-Eth1+0

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/40A,

/40B, /40C

705-400/40D, /40E, /40F

IDU FHY 42E1-Eth1+1

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2 705-400/41A,

/41B, /41C

705-400/41D, /41E, /41F

IDU FHY 63E1-Eth1+1

7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2

705-400/42A, /42B, /42C


705-400/42D, /42E, /42F

Controller Unit 7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1

SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2

634-001/81

Controller2 Unit N/A N/A N/A SVR 3.0 SVR 3.1

SVR 3.1SU1

SVR 3.1SU2

SVR 4.0 SVR 4.0 CB2

634-001/91

MODEM WB 7-56 1.5

(**) 1.8 (**) 1.8 (**) 1.9(**)

W-1.1.19 (**)

W-1.1.19 (**)

W-1.1.19v6 (**)

W-1.1.19v8 (**)

W-1.1.19v8 (**)

612-315/30

Unified MODEM2

N/A N/A N/A U-3.0.4 U-3.0.8 U-3.0.8 U-3.0.8v2 U-3.3.2 U-3.3.2

612-315/42

ODU HC AP/CC: 06L/U

GHz

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/06

ODU HC AP/CC: 07

GHz 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/07

ODU HC AP/CC: 08

GHz 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/08

ODU HC AP/CC: 11,13

GHz 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/11,*13

ODU HC AP/CC: 15

GHz 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/15

ODU HC AP/CC:

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/18, */23

ODU HC AP/CC:

5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7 5.7

735-221/18, */26

ODU HC AP/CC:

6.97 6.97 6.97 6.97 6.97 6.97 6.97 6.97 6.97


735-231/32, */38

CD for “ SW GROUP FHy ”

1.5 1.6 1.7(*) 1.8(*) 1.9(*) 1.10(*) 1.11(*) 1.12(*)

GENERAL NOTES: SW issued introduced by a specific SVR release are referenced in bold;; with previous SVRs, all the relate new functionalities are not available. SW upgrade procedure is described in TRPR-WDPE09287-1_4_0 document available in IMS No new hardwares are introduced in SVR 4.0 CB2, upgrade and downgrade between SVR 3.1and SVR 4.0 CB2 requires no hardware change. In SVR 3.0 unified modem 2 and 2xSTM1 expansion IO are introduced. Upgrade from SVR2.2 to SVR 3.0 requires no hardware change. Downgrade from SVR 3.1 to SVR 3.1SU1 should be avoided when unified modem 2 or 2xSTM1 expansion IO is present.

FHy – SW for PC Cross-Compatibility


1.2 1.3 1.4 1.5 2.2 3.0 3.1 3.1SU1 3.1SU2 4.0 4.0 CB2

UNITS SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

SW issue

FHy - SW for PC (****) (****) (****) (****) (****) (****) (****) (* ***) (****) (****) (****)

FTP client:FileZilla 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32 2.2.32

Java platform 1.6.0_03 1.6.0_03 1.6.0_03 1.6.0_03 1.6.0_17 1.6.0_17 1.6.0_17 1.6.0_17 1.6.0_17 1.6.0_17 1.6.0_17

Table 10 – SW for PC compatibility

(****) : 6.00 minimum version of “Microsoft Internet Explorer” is required HANDBOOKS Starting with R2.1 we are going to deliver Operating Documentation only via online channel and therefore no codes has to be assigned


15 BEHAVIOR NOTES

15.1 GENERAL FEATURES AND CONFIGURATIONS

Some notes about the behavior of FlexiHybrid are shown in Table 13,for more details see [1] and[2].

ID num Families Description and Consequences

1 System

configuration

In Protected diversity configuration (1+1 FD) the user can not manually force the Rx side in 1+1 systems. It can be a limitation for maintenance.

2 System

configuration Alarm severity is not shown neither by a led on FlexiHybrid front panel or in alarm history. It is sent to SysLog and in SNMP traps.

3 System

configuration

APC (Automatic Power Control) function does not respect the ATPC functionality described by ETSI. Its architecture is not designed for fast fading compensation cause initial long (3 – 4 seconds) delay in PTx variation application.

4 System

configuration

There aren't ODU connected and ODU disconnected alarm indications as in IDU SRA4. When the ODU is disconnected the ODU alarms shown are ODU fault and ODU Comm Failure.

5 System

Configuration

In 1+1 configuration, the hitless switch correctly swap without errors, but it does not allow to identify what is the commutation criteria which activate the swap (For receive 1+1 protection switching, demodulated and decoded data is processed by the FlexiHybrid Framer which passes on the higher quality DataStream on a frame by frame basis. The Framer receives a demodulated frame from each Modem/IF Module. Each frame includes a flag to indicate whether it was error free or not. The error indication is computed by the decoder. The decoding algorithm determines whether there are bit errors in frame or not. If there are errors, it determines whether they are correctable or not. Error free or correctable frame is passed to the Framer with an indication there are no residual bit errors. An uncorrectable frame is passed to the Framer with indication of uncorrectability (which means bit errors are present). Given a choice between a frame with no residual bit errors or one with bit errors the Framer selects the error-free frame and passes it along to the data interface. If both frames are error-free or both frames have bit errors, the Framer continues to process the stream it has been using).

6 System

Configuration In Protected RING configuration, the protection gets enable only for link radio breakdown or heavy anomaly (as DEM unlock) and not for error rate.

7 System

Configuration In Ring configuration it is not possible to configure some E1 flows in Point to Point configuration, but all in Ring one.

8 System

Configuration In Protected not diversity configuration, a TX ODU switch is performed for each activation or interruption of the Local Modem Loopback when APS is enable.

9 System

Configuration Security configuration Command Line Interface "Disable" will disable the ability to connect to the CLI through Telnet or SSH.

10 System

Configuration Every 10 seconds a "click" noise is heard in the VOW interface.

11 System

Configuration

FlexiHybrid does not support connecting STM-1 directly from a STM-1 module to itself in loopback or a STM-1 module in another SDIDU. There is no synchronization source when the FlexiHybrids are connected module to module. The STM-1 modules do not have an internal clock. A device that regenerates the STM-1 signal and has an internal clock has to be in the path in order for these test scenarios to operate.


ID num

Families Description and Consequences

12 System

configuration / Networking

FlexiHybrid can be configured with any IP address, included the ones reserved for multicast, broadcast, and not allowed in IDU SRA4.

13 System


In Mux-Demux configuration, in event of STM-1 LOS, STM-1 LOF or AU-AIS alarm, the status control panel shows "Connection Lost" for about 5 seconds

14 System


If the Auto-negotiation of NMS ports is enable, it is not possible to enable or disable the flow control

15 System

Configuration / Ports

There is the automatic shut down of the optical SFP module only in event of a link fault if the feature Shutdown for link failure is enabled. There is not the automatic shut down of the optical STM-1 interface.

16 System


There is not an Ethernet port physical loop. In order to loopback the ethernet payload, it is possible only to perform a modem loop which however loops all the other LIU ports. Besides, the rate of the looped Ethernet payload is equal to the ethernet radio rate chosen by the configuration and not to the radio port rate.

17 System


Modes with more than 100Mbps of Radio Ethernet payload require the GigE Master IO module (except for "Plus" modes) because for Standard2, Enhanced2 and 42E1 Master IO modules, the limitation of Ethernet payload is 100Mbps for each radio. For this reason when a configuration with a Radio Ethernet rate over 100Mbps is performed using Standard2, Enhanced2 and 42E1 Master modules, a wrong value of Ethernet Datarate is shown in Configuration Summary (28.128-2e144M -> 14M; 28.128-4e136M -> 14M; 28.128-8e128M -> 13M; 28.128-16e112M -> 11M; 28.128-18e112M -> 11M).

18 Alarms / Alarms After an IDU reboot or controller reboot or extracting and inserting the controller card in the Alarm History an IDU power up set and reset is showed.

19 Alarms / Payload

alarm

In case of AIS signal in one or more E1 channels coming from RF side, T1/E1 Channel Alarm Ch x is not active in alarm list. This is because in the current software architecture, there is no way to handle multiple AIS alarms. T1/E1 channel AIS is active only in case of AIS signal in one or more E1 channels coming from LIU side. In the "Alarm Configuration" screen, the entry "T1/E1 Channel Disconnect" is used to configure two alarms - T1/E1 Disconnect and T1/E1 AIS.

20 Alarms / Payload

alarm

Some alarms are posted in alarm list and into external alarm connector after a variable amount of time up to 40 seconds. This is due to the polling method used to sample the various alarm conditions.

21 Software

Management

FlexiHybrid software is composed by different modules (kernel, application, FPGA, ODU, Modes, channel, modem EST/WEST). When unuse the one packet SW download procedure, Each one can be separately downloaded but some one requires an IDU reboot which causes payload loss.The entire FlexiHybrid SW upgrade procedure can takes in the worst case 30 minutes; in the worst case the traffic loss is 115 seconds.

22 Software

Management In a Protected not diversity configuration the reboot of the active transmitting ODU causes the transmitting ODU switch.

23 Ethernet

In FlexiHybrid only the following Ethernet counters are present: - RX and TX byte - RX and TX frame - RX and TX byte/sec - RX and TX frame/sec - Errors and Errors/sec - Collisions and Collisions/sec

24 Ethernet Ethernet ports can not be manually disabled, so their alarms remain active until they are masked in the alarm configuration section of WEB LCT.


ID num


25 Ethernet If the Ethernet ports are automatically shut down in event of a link fault (if the feature is activated), the Ethernet Payload Disconnected alarms are shown in WEB LCT Active Alarms.

26 Ethernet There are not VLAN counters.

27 Ethernet

In Ring Configuration, using the Standard Master IO (612-315/01) and Enhanced Master IO (612-315/15) modules, the STP needs 318 seconds in order to reconfigure the ethernet data and NMS path. This is because the Ethernet switch that is used on both the Controller (634-001/81) card/NMS and the Standard/Enhanced Master IO modules, is the same. The switch has a non-programmable MAC table aging time of 268 seconds: by adding this aging time to the normal time for Spanning Tree to re-form the network (about 50 seconds) it is normal to see a 318 seconds time for all flows with MAC addresses already listed in the MAC table. There is no programmable way to reduce the aging time on this Ethernet switch. There is no programmable function in the switch to clear the MAC table. However, Ethernet switches used in the GigE Master IO (612-315/10), GigE Enhanced Master IO (612-315/16) and 42E1 Master IO (612-315/03) have a null aging time.

28 Ethernet

MAC table is not available for the user, so User can not inspect it and can not manually set entries. In event of no input traffic, the association between MAC address and Ethernet port in the MAC table is erased after 300 seconds.

29 Ethernet With Standard Master IO (612-315/01) and Enhanced Master IO (612-315/15) modules, when the system is configured to work in Ethernet plus mode, ethernet starts to flow through the port 2 after about 5 minutes.

30 Ethernet

Ethernet payload across the link is disabled in the event of a one-way link (for example when an ODU is mute). This is done because Ethernet expects to be able to send and receive data. This is especially important for Spanning Tree and for keeping MAC tables updated.

31 Ethernet / QoS

With Standard Master IO (612-315/01) and Enhanced Master IO (612-315/15) modules, when the 802.1Q tag priority or IPv4 TOS priority are enabled, in presence of more VLAN flows or more IPv4 TOS in ONLY ONE port, the priority queue ratio is not exactly 1:2, but it is about 1:2 and it depends on the configuration mode. This is caused by a packet discarding feature in the Standard/Enhanced Ethernet switch that is applied at utilization thresholds. So as the Datarate increases, three tiers of packet discarding occur on the low queue to ensure the high queue can continue to process at 100% utilization. With low datarates, there is no packet discarding. As the Datarate increases the first packet discarding level is 50% for the low queue and 0% for the high queue. If the Datarate increases to the next level, the discard level for the low queue is 75% and 0% for the high queue.

32 Ethernet / QoS The QoS via radio does not work in any cases for Standard (612-315/01) and Enhanced (612-315/15) master IO modules.

33 Ethernet / QoS The QoS via radio Port Based in East/west radio ethernet aggregation using Standard2 (612-315/37), Enhanced2 (612-315/39) and 42E1 (612-315/03) master IO modules does not work fine in some configuration cause a switch limitation.

34 Ethernet / QoS

In east/west mode, when the QoS via radio is disable, the payload coming from the west radio directed to the east radio is not treated as best effort using Standard2 (612-315/37), Enhanced2 (612-315/39) and 42E1 (612-315/03) master IO modules cause a switch limitation.

35 Ethernet / QoS QoS prioritization is not supported for Jumbo Frames (>1518 bytes) for GbE modules.

36 SNMP The informations in the Plug-in about System and ODU configurations are updated only if the "normal" mode is active instead than the "wizard" mode.


ID num


37 SNMP FlexiHybrid does not send any trap when an alarm is masked in Alarm configuration section of WEB LCT.

38 Performance monitoring

All the performance monitoring is not supported for E1 and STM-1 payload. A subset is available only for STM1 mux / demux module.

39 Operation and Maintenance

Modem FW and FPGA are housed on the modem module, so in event of modem replacement if the FW and the FPGA on board of the new modem are different from those ones on old modem, it is necessary a FW and FPGA upgrade which causes a payload loss.


The IP address is also stored in a FLASH memory of the controller, so a controller unit cold replacement could make the FlexiHybrid unreachable. It could be necessary to configure the new IP address using the serial connection.


The system configuration is also stored in a FLASH memory of the controller, so a controller unit cold replacement could cause Payload Error if the spare controller is not a "clone" of the Controller unit to be replaced. "Clone" means that the same versions of software components (Application, Kernel, FPGA of the equipped units etc.) reside in the same banks as are in the Controller being replaced.


A controller unit hot replacement must be carefully done in the Protected not diversity configuration because the controller plays a role in the automatic protection switching logic and hence need to be present to have the automatic protection switch work predictably.


The voltage level of the external alarm in the alarms connector can be selected high or low by physically moving the position of a jumper in the controller board and not only via software.


When replacing a faulty Master IO unit with a spare Master IO unit, a FPGA mismatch alarm appears, always re-download the FPGA with the running version also if in the Reprogramming screen the version is correct. When replacing a faulty Expansion IO unit with a spare Expansion IO unit, always re-download the FPGA with the running version also if in the Reprogramming screen the version is correct.


When you replace an ODU with another one with different radio frequency the FlexiHybrid works with the previous parameters and to make working the new parameters (f.i. the spectrum inversion) you need turn off/on or re-configure the link. No action is taken if you turn off/on the ODU only.


In event of a short circuit in IF cable, the protection circuitry does not power on the ODU in order to provide maximum protection to the equipment in the field. It is necessary to disable and enable the ODU again.


In event of VoiceOrderWire loop or MUX demux Facility and Terminal loop there are no active alarms which indicates this condition.

48 Vlan Management Strict priority cannot be guaranteed using when using the Standard2, Enhanced2 and 42E1 modules. A small percentage of lower priority frames may be prioritized over higher priority frames.

49 Vlan Management

In S+C tag mode, when a single tagged frame (C-tagged) enters a Network port it is forwarded on the base of the Inner VLAN tag instead of the outer. This issue is present in Enhanced2, Standard2 and 42E1 Master IO.It is not present in the GigE and EnhGigE module. The limitation can be considered as acceptable because if the network is properly configured then when enabling S+C mode, single C-tagged frames should not be present at Network interface (an outer S-Tag is added to all frames entering via User port).

50 Vlan Management In GigE and EnhGigE Master module , the value of the p-bit of the added VLAN-tag is determined on the base of the Port priority (and not independently as required).


ID num


51 Vlan Management In 42E1, Standard2 and Enhanced2 Master modules. Enabling more than one QoS criteria at the same time (Port based, p-bit, Diff-Serv) the p-bit of the incoming frames maybe overwritten.

52 Vlan Management Qos criteria about DiffServ Priority does not works in some case.


CVS instead of BBE is used for SDH side PM. So it is not strictly G.826 protocol.


Performance mornitoring in radio side is not accurate. In this release the Radio side PM is not commited and it will be improved in future release..

55 System

Configuration

Due to the FPGA resource limitation of EnhGigE master I/O module, SNCP-like protection and MUX/DEMUX capability can’t be supported at the same time on the EnhGigE master I/O module

56 System

Configuration

Protection Lockout doesn’t match the standard. The traffic can’t be switch back to working path and the device can’t interwork with other SDH device in this special scenario.

57 Ethernet For standard 2 Master IO module, the 2048 bytes traffic only can reach 99% throughput. But for frames below 1600 bytes traffic, it can reach 100% throughput. Minor issue.

58 System

Configuration E1 wander will be a little above Mask when over 2 hops. While there is no E1 err for traffic.

59 Alarms / Alarms After PDH ring in SVR2.1/SVR3.0 upgrade to SNCP-Like of SVR3.1, PDH Ring Switch Alarm wrongly reported. Only Power off/on Controller can clear it. No traffic is affected.

60 System

Configuration

The interworking between SVR2.1 and SVR3.1SU1 in Radio/Air is not supported. E.g for one hop, it is not supported when one end is SVR2.1 SW and the other end is SVR3.1 SW.

61

STM-mode upgrade from

SVR2.1 to SVR3.1SU1

STM-mode upgrading from SVR2.1 to SVR 3.1SU1 is not supported well. After you upgrade from SVR2.1 to SVR3.1SU1 in 1s mode(STM-1 Transparent), you need 2 steps to recover the traffic: 1, Disable the Mux/DMUX of ST 2. Recreate the STM-1 Channel: MA1,E1.

62 TDM Long convergence time for wander after system reboot; reconfiguration; reconfigure channel map; traffic down.

63 TDM traffic blocked in 2 link modes (14.4-2e13m 7.16-2e13m)

64 TDM Two more minutes of traffic sync loss will be cost in "Dual Port Mode" after reconfiguration and sometimes, traffic is in bit error for both Ethernet and TDM; Reboot IDU in WebLct can recover it.

65 Timing Automatic Synchronization mode can’t be use.

66 Frame Parity Disable the stage 2 alarm and Remote Transmitter switch ON Detect under the configuration of 1+1.

Table 13: Notes about the behaviour of FlexiHybrid


REBOOT The payload loss time values for each unit reboot and turn on IDU are shown in the following table(same with SVR2.1).

Unit

Configuration

Standard Mode

Protected diversity

Protected not diversity East / West East / East

Controller reboot

Error free Error free Error free Error free 30s only Ethernet

Framer reboot

20s 15s 15s 15s 15s

IDU reboot 105s 115s 115s 115s 115s

East ODU reboot

30s in TX direction

Error free

1 AIS if East ODU is active Error free if West ODU is active

30s in East TX direction Error free in West direction

30s in lower modem TX direction Error free for upper modem direction

West ODU reboot

- Error free

Error free if East ODU is active 1 AIS if West ODU is active

Error free in East direction 30s in West TX direction

Error free for lower modem direction 30s in upper modem TX direction

East Modem reboot

50s 1 AIS

1 AIS if East modem transmitter is active Error free if West modem transmitter is active

60s in East direction Error free for West direction

60s in lower modem direction Error free for upper modem direction

West Modem reboot

- 1 AIS

Error free if East modem transmitter is active 1 AIS if West modem transmitter is active

Error free for East direction 60s in West direction

Error free for lower modem direction 60s in upper modem direction

Turn on IDU

180s 135s 135s 135s 135s

Table 14: Payload loss time after reboot

Rapid-Spanning-Tree (RSTP) Ethernet protection feature in ring configuration.


Table 15: RSTP Configuration

1. There shouldn't be any active loop in the network which can be confirmed w.r.to the STP port state of the radio/FP ports in switch statistics page

2. There shouldn't be any Broadcast storm in the network causing the whole network and corresponding devices inaccessible and resulting in packet loss.

3. The network should converge to a stable topology without any active loop after topology change.

4. The convergence time should be less than or equal to 3*Hello Time

5. After topology change , the modified root path cost and root bridge ID should reflect in the BPDU packets sniffed.

** RSTP should be configured on NMS port too.

15.2 ACM BEHAVIOUR AND APPLICABILITY

No Modification is made for ACM in SVR 3.1.So the same behaviour with SVR2.1. For detailed information refer to former release note.

15.2.1 MODES AND PARAMETER CONFIGURATION To have the expected ACM behaviour and switch time, a limited subset of ACM setting criteria have to be set. Following table shows the set of parameter that have been certified with 15and 18GHz RF_band:


Bandwidth Configurable ACM levels Criteria Reference mode (for Certification)

28MHz Level1: 128QAM Level2: 32QAM Level3: QPSK(*)

10^-6 & Revertive margin Medium Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled

128QAM

Level1: 64QAM Level2: 16QAM Level3: QPSK


64QAM

14MHz Level1: 32QAM Level2: 16QAM Level3: QPSK


32QAM

7MHz Level1: 16QAM Level2: QPSK

10^-6 & Revertive margin Low(**) Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled

16QAM

Table 16-15/18 GHz ACM parameter cfg

Following table shows the set of parameter that have been certified with 23 GHz RF_band:


Bandwidth Configurable ACM levels Criteria Reference mode (for Certification)

28MHz Level1: 128QAM Level2: 32QAM Level3: QPSK(*)

Levels 1, 2: CER = 1e-4; Revertive Margin = HIGH. Levels 2, 3: CER = 1e-4; Revertive Margin = HIGH. Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled

128QAM

Level1: 64QAM Level2: 16QAM Level3: QPSK

Levels 1, 2: CER = 1e-4; Revertive Margin = HIGH. Levels 2, 3: CER = 1e-4; Revertive Margin = HIGH. Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled

64QAM

14MHz Level1: 32QAM Level2: 16QAM Level3: QPSK

Levels 1, 2: CER = 1e-5; Revertive Margin = HIGH. Levels 2, 3: CER = 1e-4; Revertive Margin = MEDIUM. Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled

32QAM

7MHz Level1: 16QAM Level2: QPSK

Levels 1, 2: CER = 1e-4; Revertive Margin = HIGH. Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled

16QAM

Table 17-23 GHz ACM parameter cfg

(*):16QAM at Level 3 is also allowed, QPSK has been certified because of is the worst condition. (**):10^-6 & Revertive margin Medium or High is critical: in 1+0 it could be that the system can not return to level 1 when receiver power level came back at nominal values.

!!!NOTE!!!: configuration not allowed are setting as adjacent level the following combination:128QAM/QPSK; 128QAM/16QAM ;64QAM/QPSK.These setting could affect the possibility to switch at the upper level ! All the other configurations have to be defined and used with TS support only in case of specific customer scenario optimizations. Different behavior and performances for different RF band is possible. The reason is that the ACM algorithm needs to estimate some parameters whose actual value depends on the ODU noise characteristics. This characteristic varies with the RF band and the real link set-up in field.


15.2.2 SWITCHING TIME The typical switching time is 300ms when the speed fading is <= 2dB/s. Longer time switches can occasionally occur. Empiric test results can show the statistic of this occurrence. Using the parameters and modulation below, with 15GHz RF band and the modes in the following table, we can estimate the percentage of time switch more than 300ms:

CS Level 1 Level 2 Level 3 Test case 28 28.128.18e112M 28.32.8e78M 28.16.4e66M 1 28 28.128.18e112M 28.32.8e78M 28.4.4e26M 2 28 28.64.16e86M 28.16.8e57M 28.4.4e26M 3 14 14.32.8e30M 14.16.8e20M 14.4.4e9M 4 7 7.16.8e 7.4.4e 5

After stressing the system with 2dB/s for 1920switchs: Test case 1: Standard configuration : 4% Protected configuration: 10% Test case 2: Standard configuration : 6% Protected configuration: 10% Test case 3: Standard configuration : 8% Protected configuration: 20% Test case 4: Standard configuration : 4% Protected configuration: 10% Test case 5: Standard configuration : 30% Protected configuration: 50% The percentage indicate time switch from 1 sec up to 2sec. After stressing the system with 2dB/s for 120switchs: Test case from 1 to 4 didn’t show any switch time more than 300ms. Instead of the result of test case 5 that are confirmed. Additional test with 23GHz showed that switching time at 7Mhz can reach up to 3sec frequently. !!!NOTE1: with IF cable less than 80m and If_Rx=-10 dBm during ACM switch some spurious violating the ETSI mask could occur.With short cable and IF_RX= -16dBm the issue should not occur.In any case ETSI certification is not possible until this behaviiour is valid!!!! NOTE2: ACM performances reported in this chapter are guarantee for the following range of parameters: Ptx\ Fr_band 15GHz 18GHz 23GHz PTx max +18dBm +17dBm +18dBm PTx min +3dBm +2dBm +3dBm


NOTE3: In order to reach target values maximum power allowed for various RF bands foreseen in SVR 4.0 CB2 is as follows:

Frequency Band [GHz]

Max PTX1 [dBm]

Max PTX with 256QAM2 [dBm]

7/8 23 23 15 20 17 18 19 16 23 18 17

15.2.3 Other notes about possible setting & configurations

• In protection non diversity Remote TX switch should be disabled when ACM is enabled to avoid switch time longer than expected and spurious TX switch.

• ACM and ATPC have not to be enabled at the same time: these two functionality are not supported at the same

time.

• Manual Switch is suggested to be used only for debug purpose: it could cause LOS of traffic for 2-3 sec.

1 ODU HW edition: (to be added) 2 These values are subject to change after I&V tests.

crn flexihybrid release notes svr 4.0 cb2

Documents

microsoft

enanched spectral

enhanced spectral

improved spectral

e1 payloads

42e1 master

enhanced master

signal degraded