Professional Documents
Culture Documents
CODE: SOURCE:
In addition to the authors named on the cover page the following persons have collaborated on this document :
1 2 3
---
TABLE OF CONTENTS
Sommario
1 INTRODUCTION .............................................................................................................................................. 4 1.1 1.2 1.3 2 3 4 SCOPE ....................................................................................................................................................... 4 APPLICABILITY......................................................................................................................................... 4 TERMS, ABBREVIATIONS AND DEFINITIONS............................................................................................. 4
SCOPE ................................................................................................................................................................. 6 APPLICABILITY ............................................................................................................................................... 6 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 6
7 2XSTM1E/O SUPPORT IN EXPANDED SLOT AND SNCP-LIKE PROTECTION FOR ENHGIGE MASTER I/O MODULE ......................................................................................................................... 10 8 9 BER SWITCHING TRIGGERED VIA SNCP-LIKE ....................................................................................... 11 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 15.2 GENERAL FEATURES AND CONFIGURATIONS .......................................................................................... 31 ACM BEHAVIOUR AND APPLICABILITY ................................................................................................... 37 15.2.1 15.2.2 15.2.3 MODES AND PARAMETER CONFIGURATION .............................................................. 37 SWITCHING TIME ................................................................................................................. 40 Other notes about possible setting & configurations ............................................................. 41
1 1.1
INTRODUCTION 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
AP BB CC DA DC/DC E1 E/FE EMC
NMS
O&M OC
ODU PC
PCB PDH PM QAM QoS RF RSOH RST SCN SDH SNCP SNMP SOH SRA 4 SSU
ETH FD
FPGA HC HDB3 HSBY
HW I/O
IDU IF i/f IP LCT LED LOS MAC MSOH MST MST MTBF AP BB CC DA DC/DC E1 E3
STI
STP
SVR SW
VC WFQ
ODU PC
PCS
E/FE EMC
PCB PDH PDU PM PRC QAM QoS RF RSOH RST SCN SDH SNCP SNMP SOH SRA 4 SSU
Printed Circuit Board Plesiochronous Digital Hierarchy Protocol Data Unit length indicator Performance Monitoring Primary Reference Clock Quadrature Amplitude Modulation Quality of Service Radio Frequency Regenerator Section Overhead Regeneration Section termination Software configuration networking Synchronous Digital Hierarchy Sub Network Connection Protection Simple Network Management Protocol Section Overhead System Radio Access 4 Synchronization Supply Unit
ETH FD
FCS FD FPGA HC HDB3 HSBY
HW I/O
IDU IF i/f IP LCT LED LOS MAC MSOH MST MST MTBF
STI
STP
SVR SW
VC WFQ
XPIC
FHy
FlexiHybrid
SCOPE
This document describes release feature, software version components and the relevant HW and SW compatibility.
APPLICABILITY
Information contained in this document is applicable to Release SVR 4.0 FlexiHybrid and its relation to previous version releases.
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 NSNs 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
Mini I/O
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 STM-1 Optical Mini IO module
612-315/25 ed. 01
Master I/O
Expansion I/O
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) PS1 Slot (Lower) Controller Slot Master IO slot Expansion Slot Mini IO slot Modem West slot (Upper) 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.
IDU Slot
Chassis PS Controller
Wired rack Power Supply Controller unit Controller with enhanced capabilities Wideband Modem/IF module Unified modem Standard IO module with 16E1+2Ethernet Enhanced Master I/O module GigE Master I/O module with 2E1+Eth Enhanced GigE Master IO module w/2E1+Ethernet Master 42E1 IO module w/ 42E1+Ethernet Standard master module with improved Ethernet capabilities Enhanced master module with improved Ethernet capabilities STM-1 Optical Mini IO module STM-1 Electrical Mini IO module 16E1 expansion IO module 21E1 expansion IO module 2xSTM-1 Expansion IO Module (two core)
From SVR 1.0 From SVR 1.1 From SVR 1.1 but not in SVR 2.0 From SVR 2.0 From SVR 1.2 From SVR 3.0 From SVR 1.0 but not in SVR 2.0. From SVR 1.0 but not in SVR 2.0 From SVR 1.0 From SVR 2.1 From SVR 1.2 From SVR 2.0 From SVR 2.0 From SVR 1.0 From SVR 1.0 From SVR 1.0 From SVR 1.2 From SVR 3.0
Enhanced Master I/O GigE EnhGigE 42E1 Standard2 Ehnanced2 STM1o Mini I/O STM1e Exp 16E1 Exp 21E1 Expansion I/O 2xSTM-1 o/e
612-315/15 612-315/10 612-315/16 612-315/03 612-315/37 612-315/39 612-315/25 612-315/20 612-315/05 612-315/06 612315/43/612315/44
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.
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.
Max lengths with ODU-HC AP/CC Max lengths with ODU-HC AP (SDH2) (Remec) 190 m 150 m 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 SNCPLike 2xSTM-1 Support Mux/Demux Capability for Mini I/O No Yes
4130_CG Yes Yes 4130_SG No No 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 cant 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.
For configurations with EnhGigE and STM-1 mini I/O, SNCP-Like and Mux/Demux cant co-exist because STM-1 mini I/Os Mux/Demux relies on the master I/O FPGAs capability, as can be seen in Table a, there are two FPGA versions: 4130_CG can support SNCP-Like, but it cant support Mux/Demux; 4130_SG can support Mux/Demux, but it cant support SNCP-Like. Heres the summary of the capability of configurations with EnhGigE:
4130_SG
No
25o/26o
4130_CG
Yes
4130_SG
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
The required combination of modulation format and channel spacing. Table 3a: Spectral efficiency 7MHz 14MHz 28MHz XPIC on 28MHz X (1) X (1) X (1) QPSK X (1) X (1) X (1) 16QAM X X (1) X (1) 32QAM X X X (1) 64QAM X X (1) 128QAM X 256QAM (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)
7.4-8M
QPSK
7 MHz
L1
9.58
2 3 4 5 6 7 8 9 10 11 22 23 24 25 26
7.4-2e4M 7.4-4e 14.4-19M 14.4-2e15M 14.4-4e11M 14.4-8e3M 7.16-17M 7.16-2e13M 7.16-4e9M 7.16-8e1M 28.4-38M 28.4-2e34M 28.4-4e30M 28.4-8e22M 28.4-16e6M
QPSK QPSK QPSK QPSK QPSK QPSK 16QAM 16QAM 16QAM 16QAM QPSK QPSK QPSK QPSK QPSK
7 MHz 7 MHz 14 MHz 14 MHz 14 MHz 14 MHz 7 MHz 7 MHz 7 MHz 7 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz
2 4 0 2 4 8 0 2 4 8 0 2 4 8 16
4 0 19 15 11 3 17 13 9 1 38 34 30 22 6
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
L1 L1 L1 L1 L1 L1 L1 L1 L1 L1 L2 L2 L2 L2 L2
2 2 2 2 2 2 4L 4L 4L 4L 2 2 2 2 2
10.58 9.58 20.53 20.53 20.53 20.53 18.58 19.58 18.58 18.58 40,38 40,38 40,38 40,38 40,38
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 74
28.4-18e2M 14.16-38M 14.16-2e33M 14.16-4e29M 14.16-8e21M 14.16-16e5M 14.16-18e1M 7.32-22M 7.32-2e18M 7.32-4e14M 7.32-8e6M 7.64-27M 7.64-2e23M 7.64-4e19M 7.64-8e11M 28.16-78M 28.16-2e73M 28.16-4e69M 28.16-8e61M 28.16-16e45M 28.16-18e41M 28.16-32e13M 14.32-48M 14.32-2e44M 14.32-4e40M 14.32-8e32M 14.32-16e16M 14.32-18e12M 14.64-58M 14.64-2e53M 14.64-4e49M 14.64-8e41M 14.64-16e25M 14.64-18e21M 14.128-68M
QPSK 16QAM 16QAM 16QAM 16QAM 16QAM 16QAM 32QAM 32QAM 32QAM 32QAM 64QAM 64QAM 64QAM 64QAM 16QAM 16QAM 16QAM 16QAM 16QAM 16QAM 16QAM 32QAM 32QAM 32QAM 32QAM 32QAM 32QAM 64QAM 64QAM 64QAM 64QAM 64QAM 64QAM 128QAM
28 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 7 MHz 7 MHz 7 MHz 7 MHz 7 MHz 7 MHz 7 MHz 7 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz
18 0 2 4 8 16 18 0 2 4 8 0 2 4 8 0 2 4 8 16 18 32 0 2 4 8 16 18 0 2 4 8 16 18 0
2 38 33 29 21 5 1 22 18 14 6 27 23 19 11 78 73 69 61 45 41 13 48 44 40 32 16 12 58 53 49 41 25 21 68
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
L2 L2 L2 L2 L2 L2 L2 L2 L2 L2 L2 L2 L2 L2 L2 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L3 L4
2 4L 4L 4L 4L 4L 4L 4L 4L 4L 4L 5B 5B 5B 5B 4L 4L 4L 4L 4L 4L 4L 4H 4H 4H 4H 4H 4H 5B 5B 5B 5B 5B 5B 5B
40,38 39,52 39,52 39,52 39,52 39,52 39,52 23,88 23,88 23,88 23,88 28,74 28,74 28,74 28,74 80,76 80,76 80,76 80,76 80,76 80,76 80,76 50,43 50,43 50,43 50,43 50,43 50,43 60,10 60,10 60,10 60,10 60,10 60,10 70,44
75 76 77 78 79 80 82 83 84 85 86 87 88 89 105 106 107 108 109 110 111 112 113 114 119 120 129 130 131 132 133 134 135 136 137
14.128-2e63M 14.128-4e59M 14.128-8e51M 14.128-16e35M 14.128-18e31M 14.128-32e3M 28.32-100M 28.32-2e95M 28.32-4e91M 28.32-8e83M 28.32-16e67M 28.32-18e63M 28.32-32e35M 28.32-42e14M 28.256-160M 28.256-2e160M 28.256-4e152M 28.256-8e144M 28.256-16e128M 28.256-18e128M 28.256-32e100M 28.256-42e80M 28.256-63e38M 28.256-1s16M 28.64-16e88M 28.64-18e83M 28.128-16e100M 28.128-26e100M 28.128-2e136M 28.128-4e136M 28.128-8e128M 28.128-16e112M 28.128-18e104M 28.128-32e80M 28.128-42e60M
128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 32QAM 32QAM 32QAM 32QAM 32QAM 32QAM 32QAM 32QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 64QAM 64QAM 128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 128QAM
14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 14 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz
2 4 8 16 18 32 0 2 4 8 16 18 32 42 0 2 4 8 16 18 32 42 63 0 16 18 16 26 2 4 8 16 18 32 42
63 59 51 35 31 3 100 95 91 83 67 63 35 14 160 160 152 144 128 128 100 80 38 16 88 83 100 100 136 136 128 112 104 80 60
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0
L4 L4 L4 L4 L4 L4 L4 L4 L4 L4 L4 L4 L4 L4 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5
5B 5B 5B 5B 5B 5B 4H 4H 4H 4H 4H 4H 4H 4H 6A 6A 6A 6A 6A 6A 6A 6A 6A 6A 5B 5B 5A 5A 5A 5A 5A 5A 5A 5A 5A
70,44 70,44 70,44 70,44 70,42 70,42 103,42 103,42 103,42 103,42 103,42 103,42 103,42 103,42 175,04 171,02 175,04 175,04 175,04 175,04 175,04 175,04 175,04 175,24 124,45 124,45 151,24 139,61 157,68 151,24 151,24 151,24 151,24 151,24 151,24
138 139 140 141 142 143 144 145 150 151 152 153 154 155
28.128-63e18M 28.128-1s 28.128-P46-100M 28.128-P74-72M 28.128-4eP72-72M 28.128-8eP68-67M 28.128-12eP64-63 28.128-16eP60-60 28.256-P100-69M 28.256-P85-84M 28.256-4eP80-80M 28.256-8eP76-76M 28.256-12eP72-72 28.256-16eP68-68
128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 128QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM
28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz 28 MHz
63 0 0 0 4 8 12 16 0 0 4 8 12 16
18 0 46 74 72 68 64 60 100 85 80 76 72 68
0 1 100 72 72 67 63 60 69 84 80 76 72 68
L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5 L5
5A 5A 5A 5A 5A 5A 5A 5A 6A 6A 6A 6A 6A 6A
151,24 158,16 151,24 151,24 157,68 157,68 157,68 157,68 175,04 175,04 175,04 175,04 175,04 175,04
Mode Name:
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
705-400/56D,E ed 01 IDU FHY STM1e-16E1-Eth 1+1 705-400/57D,E ed 01 IDU FHY STM1o-16E1-Eth 1+1 705-400/58D,E ed 01 IDU FHY 42E1-Eth1+0 705-400/59D,E ed 01 IDU FHY 63E1-Eth1+0 705-400/60D,E ed 01 IDU FHY 42E1-Eth1+1 705-400/61D,E ed 01 IDU FHY 63E1-Eth1+1 705-400/62D,E ed 01 IDU FHy STM1o-18E1-EnhGigE 1+0 705-400/44D,E ed 01 IDU FHySTM1o-18E1-EnhGigE 1+1 705-400/46D,E ed 01 IDU FHySTM1e-18E1-EnhGigE 1+0 705-400/43D,E ed 01 IDU FHySTM1e-18E1-EnhGigE 1+1 705-400/45D,E ed 01 IDU FHy 2xSTM1e-16E1-Eth 1+0 705-400/63D, E ed 01 IDU FHy 2xSTM1e-16E1-Eth 1+1 705-400/64D, E ed 01 IDU FHy 2xSTM1o-16E1-Eth 1+0 705-400/65D, E ed 01 IDU FHy 2xSTM1o-16E1-Eth 1+1 705-400/66D, E ed 01 IDU FHy 2xSTM1o-EnhGigE 1+0 705-400/67D, E ed 01 IDU FHy 2xSTM1o-EnhGigE 1+1 705-400/68D, E ed 01 IDU FHy 2xSTM1e-EnhGigE 1+0 705-400/69D, E ed 01 IDU FHy 2xSTM1e-EnhGigE 1+1 705-400/69D, E ed 01 ODU HC AP/CC : 7 GHz 735-221/07 ODU HC AP/CC : 8 GHz 735-221/08 ODU HC AP/CC : 11 GHz 735-221/11 ODU HC AP/CC : 13 GHz 735-221/13 ODU HC AP/CC 15 GHz 735-221/15 ODU HC AP/CC 18 GHz 735-221/18 ODU HC AP/CC 23 GHz 735-221/23 ODU HC AP/CC 26 GHz 735-221/26 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x
x x x
x x x
x x x
x x x
x x x
13 PRODUCT COMPOSITION
The following table describes the software components for the SVR 4.0 and the relevant hardware compatibility.
Units Code
IDU FHY 16E1-Eth 1+0 705-400/47B ed 01, /47D ed 01, /47E ed 01 IDU FHY 16E1-Eth 1+1 705-400/53B ed 01, /53D ed 01, /53E ed 01 IDU FHY 32E1-Eth 1+0 705-400/48B ed 01, /48D ed 01, /48E ed 01 IDU FHY 32E1-Eth 1+1 705-400/54B ed 01, /54D ed 01, /54E ed 01 IDU FHY STM1e-16E1-Eth 1+0 705-400/51D ed 01, /51E ed 01 IDU FHY STM1e-16E1-Eth 1+1 705-400/57D ed 01, /57E ed 01 IDU FHY STM1o-16E1-Eth 1+0 705-400/52D ed 01, /52E ed 01 IDU FHY STM1o-16E1-Eth 1+1 705-400/58D ed 01, /58E ed 01 IDU FHY 2E1-GigE 1+0 705-400/49D ed 01, /49E ed 01 IDU FHY 2E1-GigE 1+1 705-400/55D ed 01, /55E ed 01 IDU FHY 18E1-GigE 1+0 705-400/50D ed 01, /50E ed 01 IDU FHY 18E1-GigE 1+1 705-400/56D ed 01, /56E ed 01 IDU FHY 42E1-Eth1+0 705-400/59D ed 01, /59E ed 01 IDU FHY 42E1-Eth1+1 705-400/61D ed 01, /61E ed 01 IDU FHY 63E1-Eth1+0 705-400/60D ed 01, /60E ed 01
sw edit.
SVR 4.0 CB2
code ext.
-
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 SVR 4.0 CB2 SVR 4.0 CB2 SVR 4.0 CB2 SVR 4.0 CB2
705-400/70D ed 01, /70E ed 01 Controller2 Unit 634-001/91 ed 01 Unified MODEM2 612-315/42 ed 01 2xSTM-1 Optical Expansion IO 612-315/43 ed 01 2xSTM-1 Electriccal Expansion IO 612-315/44 ed 01 ODU HC AP/CC: 06L/6U, 07,08 GHz
735-221/06, */07,*/08
4312_EX03.01.15 4312_EX03.01.15
6.97
697 (#)
00062549CB.01 (VI)
Available with CD
00062549(SI)
Units Code
IDU FHY 16E1-Eth 1+0 705-400/47B ed 01, /47D ed 01, /47E ed 01 IDU FHY 16E1-Eth 1+1 705-400/53B ed 01, /53D ed 01, /53E ed 01 IDU FHY 32E1-Eth 1+0 705-400/48B ed 01, /48D ed 01, /48E ed 01 IDU FHY 32E1-Eth 1+1 705-400/54B ed 01, /54D ed 01, /54E ed 01 IDU FHY STM1e-16E1-Eth 1+0 705-400/51D ed 01, /51E ed 01 IDU FHY STM1e-16E1-Eth 1+1 705-400/57D ed 01, /57E ed 01 IDU FHY STM1o-16E1-Eth 1+0 705-400/52D ed 01, /52E ed 01 IDU FHY STM1o-16E1-Eth 1+1 705-400/58D ed 01, /58E ed 01 IDU FHY 2E1-GigE 1+0 705-400/49D ed 01, /49E ed 01 IDU FHY 2E1-GigE 1+1 705-400/55D ed 01, /55E ed 01 IDU FHY 18E1-GigE 1+0 705-400/50D ed 01, /50E ed 01 IDU FHY 18E1-GigE 1+1 705-400/56D ed 01, /56E ed 01 IDU FHY 42E1-Eth1+0 705-400/59D ed 01, /59E ed 01 IDU FHY 42E1-Eth1+1 705-400/61D ed 01, /61E ed 01 IDU FHY 63E1-Eth1+0 705-400/60D ed 01, /60E ed 01 IDU FHY 63E1-Eth1+1 705-400/62D ed 01, /62E ed 01
sw edit.
SVR 4.0 CB2
code ext.
-
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
SVR 4.0 CB2 SVR 4.0 CB2 SVR 4.0 CB2 SVR 4.0 CB2
705-400/70D ed 01, /70E ed 01 Controller2 Unit 634-001/91 ed 01 Unified MODEM2 612-315/42 ed 01 2xSTM-1 Optical Expansion IO 612-315/43 ed 01 2xSTM-1 Electriccal Expansion IO 612-315/44 ed 01 ODU HC AP/CC: 06L/6U, 07,08 GHz
735-221/06, */07,*/08
4312_EX03.01.15 4312_EX03.01.15 507 (***) 507 (***) 507 (***) 697 (#) License for Enhanced Spectral efficiency e-media
00062567CB.01 (VI)
(immaterial delivery Available in NOLS) License for Enhanced Spectral efficiency on cd (material delivery)
Reprogramming Screen Version 0.3.5 2.11.76x N2-2.11.76 N2-V7C-W3 N2-V8C-W3 CN-1 5.7 6.97 1.3.3 W-1.1.19v8 18 U-3.3.4 4700_PI02.03.01 4101_ST03.13.00 4110_GE03.13.00 4130_SG03.13.00 4130_CG03.13.00 4121_ST03.13.00 4132_EX03.01.02 4142_SP03.13.00 4163_EX03.01.02 4501_v8
Component 2xSTM-1 fiber expansion IO(612-315/43) 2xSTM-1 electrical expansion IO (612315/44) (**) : 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
13.1 SW UPGRADING
SW GROUP FLEXIHYBRID
00062548.03 (VI)
Available in NOLS
00062548 (SI)
00062551
(SI)
00062567
(SI)
14 COMPATIBILITY RULES BETWEEN HW AND SW VERSIONS HW configuration supported in SVR 3.1 and back Hw modules compatibility
1+0/1+1 16E 32E1 STM1 STM1 42E1 63E1 GigE
CN St CN St CN En Se CN En So CN 42E1 CN 2 42E1 1
1+0/1+1
CNT S
1+0/1+1
CNT St CNT St CNT Enh Se CNT Enh So
ne
En Se
CNT
ne
St
ne
CN Gig 1 Gig
Enh
GigE+18E1 CN
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) SW issue 705400/03A, /03B, /03C 7.3(*) 705400/03D, /03E, /03F 705400/04A, /04B, /04C 7.3(*) 705400/04D, /04E, /04F 7057.4(*) 7.5(*) 7.7(*) 7.8(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*) 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
SVR 3.0
SVR 3.1
SVR 3.1SU1
SVR 3.1SU2
SVR 4.0
7.3(*)
7.4(*)
7.5(*)
7.7(*)
7.8(*)
SVR
SVR
SVR
SVR
SVR
SVR
400/13A, /13B, /13C 705400/13D, /13E, /13F 705400/15A, /15B, /15C 7.3(*) 705400/15D, /15E, /15F 705400/16A, /16B, /16C 7.3(*) 705400/16D, /16E, /16F 705400/18A, /18B, /18C 7.3(*) 705400/18D, /18E, /18F 634001/81 634001/91 612315/30 612315/42 735221/06 735221/07 735221/08 735221/11,*13 735221/15 735221/18, */23 735221/18, */26 735231/32, */38 1.2 5.7 5.7 5.7 5.7 5.7 7.3(*) N/A W1.1.2 (**) N/A 7.4(*) N/A W1.1.2.1.1(**) N/A 5.7 5.7 5.7 5.7 5.7 5.7 7.5(*) N/A W1.1.2.1.10 (**) N/A 5.7 5.7 5.7 5.7 5.7 5.7 7.7(*) N/A W1.1.13 (**) N/A 5.7 5.7 5.7 5.7 5.7 5.7 7.8(*) N/A W1.1.13 (**) N/A 5.7 5.7 5.7 5.7 5.7 5.7 7.4(*) 7.5(*) 7.7(*) 7.8(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*) 7.4(*) 7.5(*) 7.7(*) 7.8(*)
3.0
3.1
3.1SU1
3.1SU2
4.0
4.0 CB2
SVR 3.0
SVR 3.1
SVR 3.1SU1
SVR 3.1SU2
SVR 4.0
SVR 3.0
SVR 3.1
SVR 3.1SU1
SVR 3.1SU2
SVR 4.0
SVR 3.0
SVR 3.1
SVR 3.1SU1
SVR 3.1SU2
SVR 4.0
SVR 3.0 SVR 3.0 W1.1.19 U3.0.0.4 5.7 5.7 5.7 5.7 5.7 5.7
SVR 3.1 SVR 3.1 W1.1.19 U3.0.8 5.7 5.7 5.7 5.7 5.7 5.7
SVR 3.1SU1 SVR 3.1SU1 W1.1.19 U3.0.8 5.7 5.7 5.7 5.7 5.7 5.7
SVR 3.1SU2 SVR 3.1SU2 W1.1.19v6 U3.0.8v2 5.7 5.7 5.7 5.7 5.7 5.7
SVR 4.0 SVR 4.0 W1.1.19v8 U-3.3.2 5.7 5.7 5.7 5.7 5.7 5.7
SVR 4.0 CB2 SVR 4.0 CB2 W1.1.19v8 U-3.3.2 5.7 5.7 5.7 5.7 5.7 5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
ns
ns 1.3
6.97 1.4
6.97 1.6
6.97 1.7
6.97 1.8
6.97 1.9
6.97 1.1
6.97 1.11
6.97 1.12
6.97
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 SVR (System Version Release) 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 705-400/27A, /27B, /27C 705-400/27D, /27E, /27F IDU FHY 32E1-Eth 1+0 705-400/28A, /28B, /28C 705-400/28D, /28E, /28F IDU FHY 2E1GigE 1+0 705-400/29A, /29B, /29C 705-400/29D, /29E, /29F IDU FHY 18E1-GigE 1+0 705-400/30A, /30B, /30C 705-400/30D, /30E, /30F SVR 3.1SU1 SVR 3.1SU2 SVR 4.0 CB2 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 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 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 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
7.6(*)
7.7(*)
7.8(*)
SVR 3.0
SVR 3.1
SVR 4.0
705-400/31A, /31B, /31C 705-400/31D, /31E, /31F IDU FHY STM1o-16E1Eth 1+0 705-400/32A, /32B, /32C 705-400/32D, /32E, /32F IDU FHY 16EEth 1+1 705-400/33A, /33B, /33C 705-400/33D, /33E, /33F IDU FHY 32E1-Eth 1+1 705-400/34A, /34B, /34C 705-400/34D, /34E, /34F IDU FHY 2E1GigE 1+1 705-400/35A, /35B, /35C 705-400/35D, /35E, /35F IDU FHY 18E1-GigE 1+1 705-400/36A, /36B, /36C 705-400/36D, /36E, /36F 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 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 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 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 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
IDU FHY STM1e-16E1Eth 1+1 7.6(*) 705-400/37A, /37B, /37C 705-400/37D, /37E, /37F 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1 SVR 3.1SU2 SVR 4.0 SVR 4.0 CB2
IDU FHY STM1o-16E1Eth 1+1 7.6(*) 705-400/38A, /38B, /38C 705-400/38D, /38E, /38F IDU FHY 42E1-Eth1+0 705-400/39A, /39B, /39C 705400/39D, /39E, /39F IDU FHY 63E1-Eth1+0 705-400/40A, /40B, /40C 705400/40D, /40E, /40F IDU FHY 42E1-Eth1+1 705-400/41A, /41B, /41C 705400/41D, /41E, /41F IDU FHY 63E1-Eth1+1 705-400/42A, /42B, /42C 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 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 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 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1 SVR 3.1SU2 SVR 4.0 SVR 4.0 CB2
7.6(*)
7.7(*)
7.8(*)
SVR 3.0
SVR 3.1
SVR 3.1SU1
SVR 3.1SU2
SVR 4.0
705-400/42D, /42E, /42F Controller Unit 634-001/81 Controller2 Unit 634-001/91 MODEM WB 7-56 612-315/30 Unified MODEM2 612-315/42 7.6(*) 7.7(*) 7.8(*) SVR 3.0 SVR 3.1 SVR 3.1SU1 SVR 3.1SU1 SVR 3.1SU2 SVR 3.1SU2 W1.1.19v6 (**) SVR 4.0 SVR 4.0 CB2 SVR 4.0 CB2 W1.1.19v8 (**)
N/A
N/A
N/A
SVR 3.0
SVR 3.1
SVR 4.0
1.5 (**)
1.8 (**)
1.8 (**)
1.9(**)
W-1.1.19 (**)
W-1.1.19 (**)
W1.1.19v8 (**)
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
ODU HC AP/CC: 06L/U GHz 735-221/06 ODU HC AP/CC: 07 GHz 735-221/07 ODU HC AP/CC: 08 GHz 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
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
ODU HC AP/CC: 11,13 GHz 735-221/11,*13 ODU HC AP/CC: 15 GHz 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
5.7
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 735-221/18, */26 ODU HC AP/CC: 6.97
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
5.7
6.97
6.97
6.97
6.97
6.97
6.97
6.97
6.97
735-231/32, */38 1.5 CD for SW GROUP FHy 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.4 1.5 2.2 3.0 3.1
1.2
1.3
3.1SU1
3.1SU2
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
FHy
- SW for PC
(****)
(****)
(****)
(****)
(****)
(****)
(****)
(****)
(****)
(****)
(****)
FTP client:FileZilla
Java platform
2.2.32
1.6.0_03
2.2.32
1.6.0_03
2.2.32
1.6.0_03
2.2.32
1.6.0_03
2.2.32
1.6.0_17
2.2.32
1.6.0_17
2.2.32
1.6.0_17
2.2.32
1.6.0_17
2.2.32
1.6.0_17
2.2.32
1.6.0_17
2.2.32
1.6.0_17
HANDBOOKS Starting with R2.1 we are going to deliver Operating Documentation only via online channel and therefore no codes has to be assigned
System Configuration
6 7 8 9 10
System Configuration System Configuration System Configuration System Configuration System Configuration
11
System Configuration
ID num 12
Families System configuration / Networking System configuration / Networking System configuration / Networking System Configuration / Ports System Configuration / Ports
Description and Consequences FlexiHybrid can be configured with any IP address, included the ones reserved for multicast, broadcast, and not allowed in IDU SRA4. 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 If the Auto-negotiation of NMS ports is enable, it is not possible to enable or disable the flow control 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. 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. 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.1282e144M -> 14M; 28.128-4e136M -> 14M; 28.128-8e128M -> 13M; 28.12816e112M -> 11M; 28.128-18e112M -> 11M). 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. 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. 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. 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. In a Protected not diversity configuration the reboot of the active transmitting ODU causes the transmitting ODU switch. 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 Ethernet ports can not be manually disabled, so their alarms remain active until they are masked in the alarm configuration section of WEB LCT.
13
14
15
16
17
18
Alarms / Alarms
19
20
21
Software Management
22
Software Management
23
Ethernet
24
Ethernet
ID num 25 26
Description and Consequences 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. There are not VLAN counters. 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 nonprogrammable 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 (612315/10), GigE Enhanced Master IO (612-315/16) and 42E1 Master IO (612315/03) have a null aging time. 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. 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. 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. 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. The QoS via radio does not work in any cases for Standard (612-315/01) and Enhanced (612-315/15) master IO modules. 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. 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. QoS prioritization is not supported for Jumbo Frames (>1518 bytes) for GbE modules. 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.
27
Ethernet
28
Ethernet
29
Ethernet
30
Ethernet
31
Ethernet / QoS
32 33
34
Ethernet / QoS
35 36
ID num 37 38
Families SNMP Performance monitoring Operation and Maintenance Operation and Maintenance
Description and Consequences FlexiHybrid does not send any trap when an alarm is masked in Alarm configuration section of WEB LCT. All the performance monitoring is not supported for E1 and STM-1 payload. A subset is available only for STM1 mux / demux module. 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. 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. 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). In GigE and EnhGigE Master module , the value of the p-bit of the added VLANtag is determined on the base of the Port priority (and not independently as required).
39
40
41
42
43
44
45
Operation and Maintenance Operation and Maintenance Operation and Maintenance Vlan Management
46 47 48
49
Vlan Management
50
Vlan Management
ID num 51 52 53 54
Families Vlan Management Vlan Management Performance monitoring Performance monitoring System Configuration System Configuration
Description and Consequences In 42E1, Standard2 and Enhanced2 Master modules. Enabling more than one QoS criteria at the same time (Port based, p-bit, DiffServ) the p-bit of the incoming frames maybe overwritten. 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.. Due to the FPGA resource limitation of EnhGigE master I/O module, SNCP-like protection and MUX/DEMUX capability cant be supported at the same time on the EnhGigE master I/O module Protection Lockout doesnt match the standard. The traffic cant be switch back to working path and the device cant interwork with other SDH device in this special scenario. 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.
E1 wander will be a little above Mask when over 2 hops. While there is no E1 err for traffic.
55
56
57
Ethernet
58
System Configuration
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. 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. 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. Long convergence time for wander after system reboot; reconfiguration; reconfigure channel map; traffic down.
60
61
62
63
TDM
traffic blocked in 2 link modes (14.4-2e13m 7.16-2e13m) 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. Automatic Synchronization mode cant be use.
64
TDM
65
Timing
66
Frame Parity
Disable the stage 2 alarm and Remote Transmitter switch ON Detect under the configuration of 1+1.
REBOOT
The payload loss time values for each unit reboot and turn on IDU are shown in the following table(same with SVR2.1). Configuration Unit Standard Mode Error free 20s 105s Protecte d diversity Error free 15s 115s Protected not diversity Error free 15s 115s 1 AIS if East ODU is active East ODU reboot 30s in TX direction Error free Error free if West ODU is active Error free if East ODU is active 1 AIS if West ODU is active 1 AIS if East modem transmitter is active 50s 1 AIS Error free if West modem transmitter is active Error free if East modem transmitter is active 1 AIS 1 AIS if West modem transmitter is active on 180s 135s 135s East / West Error free 15s 115s 30s in direction Error free direction East TX East / East 30s only Ethernet 15s 115s 30s in modem direction lower TX
in
West
in
East
Error free for upper modem direction Error free for lower modem direction 30s in modem direction upper TX
Error free
West
TX
60s in lower modem direction Error free for upper modem direction
for
East
Error free for lower modem direction 60s in upper modem direction
Turn IDU
135s
135s
Criteria
10^-6 & Revertive margin Medium Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled 10^-6 & Revertive margin Medium Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled 10^-6 & Revertive margin Medium Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled 10^-6 & Revertive margin Low(**) Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled
64QAM
14MHz
32QAM
7MHz
16QAM
Following table shows the set of parameter that have been certified with 23 GHz RF_band:
Criteria
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 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 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 Levels 1, 2: CER = 1e-4; Revertive Margin = HIGH. Switch delay and Revertive Switch delay = 1000 ms Revertive Mode:Enabled
64QAM
14MHz
32QAM
7MHz
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.
CS 28 28 28 14 7
Test case 1 2 3 4 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%
After stressing the system with 2dB/s for 120switchs: Test case from 1 to 4 didnt 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 PTx max PTx min 15GHz +18dBm +3dBm 18GHz +17dBm +2dBm 23GHz +18dBm +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 Max PTX1 Max PTX with 256QAM2 [GHz] [dBm] [dBm] 7/8 23 23 15 20 17 18 19 16 23 18 17
15.2.3
1 2
ODU HW edition: (to be added) These values are subject to change after I&V tests.