FlexiPacket Hub 800 Customer Release Notes R2 0 EP2 SU1 PDF

Customer Release Notes
Product Family: FlexiPacket

Product: Hub 800
Release: R2.0_2.1.0 (a.k.a. R2.0EP2 SU1)
Customer: Generic Delivery
© Nokia Siemens NetworksCompany Confidential- 1 - 1

TABLE OF CONTENTS
1. IMPORTANT NOTICE ................................................................................................................. 5
2. COMPATIBILITY, SYSTEM INSTALLATION TYPES AND INTEROPERABILITY ...... 5
2.1. SYSTEM INSTALLATION TYPES .................................................................................................. 5
 1+0 ............................................................................................................................................ 5
 1+1 with one IDU, for ODU protection only ........................................................................... 5
 2+0 with one IDU ..................................................................................................................... 5
2.2. SYSTEM TYPE COMPATIBILITY .................................................................................................. 5
2.3. INTEROPERABILITY .................................................................................................................... 5
3. WHAT’S NEW IN R2.0EP2 SU1 .................................................................................................. 6
4. WHAT’S NEW IN R2.0EP2 .......................................................................................................... 6
5. OPERATION CONSIDERATIONS AND HINTS ...................................................................... 7
5.1. LICENSE MANAGEMENT ............................................................................................................. 7
5.2. SECURITY SOFTWARE PACKAGE ................................................................................................ 7
5.3. OOB INTERFACE ........................................................................................................................ 7
5.4. PUBLIC IP ADDRESS OF DCN INTERFACE .................................................................................. 7
5.5. THE NUMBER OF SERVICES ........................................................................................................ 7
5.6. SERVICE VLAN ID RANGE FOR E-LAN AND E-LINE SERVICE.................................................. 8
5.7. NETWORK WITH LOOPS MUST RUN STP (SPANNING TREE PROTOCOL)..................................... 8
5.8. CES OVER ETHERNET SERVICE .................................................................................................. 8
5.9. CES TDM MODE SWITCHING .................................................................................................... 8
5.10. 1+1 HOT-STANDBY ODU FUNCTION ......................................................................................... 8
5.11. DEPLOYING POWER-PLUS-ETHERNET (P+E) .............................................................................. 8
6. SOLVED ISSUES IN R2.0EP2 SU1 .............................................................................................. 9
7. SOLVED ISSUES IN R2.0EP2 ...................................................................................................... 9
7.1. SYSTEM...................................................................................................................................... 9
7.2. CES ......................................................................................................................................... 10
7.3. CLOCK SYNCHRONIZATION ...................................................................................................... 10
7.4. PROTECTION ............................................................................................................................ 10
7.5. MANAGEMENT AND WEBLCT ................................................................................................. 10
8. SOLVED LIMITATIONS IN R2.0EP2 ...................................................................................... 11
9. ISSUES NEWLY FOUND IN PREVIOUS RELEASE BUT FIXED IN R2.0EP2................. 12
9.1. SYSTEM.................................................................................................................................... 12
9.2. ETHERNET SERVICE ................................................................................................................. 12
9.3. CESOP AND CLOCK SYNCHRONIZATION ................................................................................. 12
9.4. PROTECTION ............................................................................................................................ 13
9.5. OAM ....................................................................................................................................... 13
9.6. MANAGEMENT AND WEBLCT ................................................................................................. 14

10. ISSUES SOLVED IN R2.0_1.7.0 (A.K.A. R2.0EP1 PU7) ..................................................... 15
10.1. SYSTEM.................................................................................................................................... 15
10.2. LPG ......................................................................................................................................... 15
10.3. LAG ........................................................................................................................................ 16
10.4. CES ......................................................................................................................................... 16
10.5. MANAGEMENT ......................................................................................................................... 16
11. ISSUES SOLVED SINCE R2.0_1.13.0 (A.K.A. R2.0 EP1 PU6) .......................................... 17
11.1. SYSTEM.................................................................................................................................... 17
11.2. ETHERNET SERVICES ............................................................................................................... 17
11.3. CES SERVICES ......................................................................................................................... 17
11.4. CES LINEAR PROTECTION ....................................................................................................... 18
11.5. CLOCK SYNCHRONIZATION ...................................................................................................... 18
11.6. ETHERNET SERVICE PROTECTION ............................................................................................ 19
11.7. OAM ....................................................................................................................................... 20
11.8. WEBLCT AND MANAGEMENT ................................................................................................. 20
12. KNOWN LIMITATIONS ........................................................................................................ 20
12.1. KNOWN LIMITATIONS IN R2.0EP2 ........................................................................................... 20
12.1.1. CES and Clock Synchronization ..................................................................................... 20
12.1.2. OAM ................................................................................................................................ 21
12.1.3. Management and WebLCT ............................................................................................. 21
12.2. KNOWN LIMITATIONS SINCE R2.0_1.13.0 (BUILD 2.7.30 FOR R2.0 EP1 PU6) ......................... 21
12.2.1. Management .................................................................................................................... 21
12.2.2. Protection ........................................................................................................................ 21
12.2.3. Clock Synchronization .................................................................................................... 22
12.3. KNOWN LIMITATIONS SINCE R2.0_1.4.0 (BUILD VERSION 2.8.21 FOR R2.0 EP1) .................... 22
12.4. KNOWN LIMITATIONS SINCE R2.0_1.1.0 (BUILD VERSION 2.8.14 FOR R2.0 EP1) .................... 22
12.5. KNOWN LIMITATIONS SINCE R2.0_0.2.0 (BUILD VERSION 2.7.14) ........................................... 22
12.6. KNOWN LIMITATIONS SINCE R2.0 (BUILD VERSION 2.7.7) ....................................................... 23
12.6.1. System ............................................................................................................................. 23
12.6.2. QoS .................................................................................................................................. 23
12.6.3. Protection ........................................................................................................................ 23
12.6.4. OAM ................................................................................................................................ 23
12.6.5. CES ................................................................................................................................. 24
13. KNOWN ISSUES ...................................................................................................................... 24
13.1. KNOWN ISSUES IN R2.0EP2 ..................................................................................................... 24
13.1.1. CES Services and Clock Synchronization ....................................................................... 24
13.1.2. Protection ........................................................................................................................ 25
13.1.3. OAM ................................................................................................................................ 25
13.2. KNOWN ISSUES IN R2.0_1.13.0 (BUILD 2.7.30 FOR R2.0EP1 PU6) .......................................... 26
13.2.1. System ............................................................................................................................. 26
13.2.2. Protection ........................................................................................................................ 26

13.2.3. CES ................................................................................................................................. 26
13.2.5. STM-1 .............................................................................................................................. 28
13.2.6. G.8031 ............................................................................................................................. 28
13.2.7. OAM in WebLCT............................................................................................................. 28
13.2.8. WebLCT and Management ............................................................................................. 28
13.3. KNOWN ISSUES SINCE R2.0_1.1.0 (BUILD VERSION 2.8.14 FOR R2.0 EP1) .............................. 29
13.3.1. System ............................................................................................................................. 29
13.3.2. Ethernet Service Protection ............................................................................................ 29
13.4. KNOWN ISSUES SINCE R2.0_0.2.0 (BUILD VERSION 2.7.14) ..................................................... 30
13.4.1. CES ................................................................................................................................. 30
13.5. KNOWN ISSUES SINCE BUILD V2.7.7 OF R2.0 ........................................................................... 30
13.5.1. System ............................................................................................................................. 30
13.5.2. E-Line and E-LAN Service .............................................................................................. 30
13.5.3. Protection ........................................................................................................................ 30
13.5.4. CES ................................................................................................................................. 30
14. DOCUMENTATIONS ............................................................................................................. 32
Scope
The following software releases are in scope of this document:
FlexiPacket Hub 800:
Current Release: R2.0_2.1.0 (a.k.a. R2.0EP2 SU1)
Current Build Version 2.9.37
Release Date: 5 March 2013
WebLCT: 2.9.37
Previous Build Version: 2.9.36 (release R2.0_2.0.0, a.k.a. R2.0EP2)

1. Important Notice
The “system”, “FPH800” and “IDU” in this document are specifically referred to FlexiPacket Hub 800.
The limitations and issues in the previous release that are solved by later releases including this release
(R2.0_2.1.0) are written in grey color in section 12 and 13. Those in black are not fixed and still in this
release.
2. Compatibility, System Installation Types and Interoperability

2.1. System Installation Types
 1+0
 1+1 with one IDU, for ODU protection only
 2+0 with one IDU
2.2. System Type Compatibility

FPR 1.3 FPR 1.3EP1 FPR 1.4 FPMR 2.1 FPMR 2.4 FPMR 2.5
FPH800 R2.0 √ √ √ √ √
FPH800 R2.0EP1 √ √
FPH 800 R2.0EP2 √ √ √ √ √ √
FPH 800 R2.0EP2 √ √ √ √ √ √
SU1
2.3. Interoperability
A-Series FM200 R2.0 FM200 R2.0EP1

Ethernet Service √ √ √
G.8031 n/a n/a √
LAG √ √ √
xSTP √ √ √
Ethernet OAM √ √ √
E1/T1 CESoP √ √ √
E1 SAToP × √ √
STM-1 CESoP √ n/a n/a
E1 CES Linear n/a n/a √
Protection
Synchronization √ √ √
Interoperability tests have been done with:

 FlexiPacket Radio R1.3.8
 FlexiPacket MultiRadio R2.4SU2
 FlexiPacket MultiRadio R2.5 SU1
 FlexiPacket Hub A-1200/2200 R5.0
 FM200 R2.0
 FM200 R2.0EP1
3. What’s New in R2.0EP2 SU1

This release contains the new boot code that solves the missing system MAC address issue. Boot code
can be upgraded by NSN Service staffs when needed.
The other problems solved by this release are illustrated in section 6.
4. What’s New in R2.0EP2

 Support for SFP DDM (Digital Diagnostic Monitoring)
o Display in WebLCT and NetViewer the following DDM information of optical SFP
 Transmitter optical power
 Receiver optical power
 Transmitter bias current
 SFP internal temperature
 E1 Failure detection and AIS insertion to TU-12 header
o Wrong E1 frames (or those with alarm indication) must be AIS indicated and AIS is
inserted to the corresponding TU-12 header in STM-1 frame when the E1 frames are
handed off over STM-1 interface to SDH network.
 n x 64kbps grooming to E1
o n x 64kbps timeslots from multiple E1 CES services are groomed to one E1 interface on the
mainboard, and E1 on the mainboard is de-groomed to multiple E1 CES services.
 "Tagged" Mapping Rule
o A mapping rule that can map all the "tagged" frames to an Ethernet service
 Dynamic addition/deletion/change of mapping rules
o Adding or deleting or changing the mapping rules configured on an UNI without traffic hit
 Hitless addition/removal of port for E-LAN service
 Per-service Bandwidth Profile
o Bandwidth profile is applied to an Ethernet service with multiple mapping rules.
 Remote UNI Port Shutdown
o When the local UNI of a port-mapping E-Line fails, the remote UNI of the E-Line service
can be brought down if it is the only service on that UNI port.

 Security Enhancements
 Working and protection path of CESoP linear protection and G.8031 protection can be on
one NNI port (before they must be on two different NNI ports of the system)
 Removal of CVLAN range limitation (1-50)
5. Operation Considerations and Hints

5.1. License Management
Software licenses are managed by a web-based tool called CLicS. Operators need to log into CLicS via the
following URL and generate licenses according to the equipment serial number.
CLicS URL: https://online.portal.nokiasiemensnetworks.com
5.2. Security Software Package

All the licensed software features except the security features are embedded in the basic software packages and license
is required in order to activate the feature. Security features are not in the basic software package but in a separate
software package (product number T555800SE.20 for security package on e-media, and T555800SC.20 for security
package on CDROM).
If security software package on e-media is ordered, it can be downloaded from the software list of FPH800 on NOLS.
Note that security software license is required in any case to activate the security features.
5.3. OOB Interface

A local terminal can be directly connected to the OOB interface of the IDU with the IP address
192.168.254.100/24.
This IP address is not configurable.
5.4. Public IP Address of DCN Interface

DCN Port System IP address is user-configurable via WebLCT.
Default IP address: 192.168.255.100/24
The management VLAN ID must be set (permitted values 51 ~ 4094) in order to use In-Band Management.
Default management VLAN ID is 127.
G.8031 and Ethernet OAM License
It is important to note that G.8031 requires Ethernet OAM license to be installed because G.8031 detects the
failure on the working path and triggers switchover by using Ethernet OAM tools.
5.5. The Number of Services

A limited number of services, T1/E1 CESoP and Ethernet, are supported with and without linear protection
and their numbers can be calculated by the following formula.
Total Number of T1/E1 CESoP Services:
Unprotected CESoP * 2 + protected CESoP * 4 <= (58 * 4)
AND

The total number of E1's is no more than 111.
Total Number of Ethernet Services:
Unprotected E_LAN + Unprotected E_Line + Protected E_Line * 2 <= (256-14)
Note 1: “unprotected” and “protected” refer to Linear Protection only (CES and Ethernet G.8031)
Note 2: The system resources are partitioned for CES and Ethernet services, so the number of CES is
independent from the number of Ethernet services.
5.6. Service VLAN ID Range for E-LAN and E-Line Service

E-LAN Service and E-LINE Service need to use value 51~4094 for Service VLAN Tag. WebLCT can be
used to create E-LAN and E-Line service.
5.7. Network with Loops Must Run STP (Spanning Tree Protocol)
Ref. FR_0000012505 – Network with loops but not running STP may cause Management unreachable and
services interrupted
Description: Network with loops but not running STP will make ODU MAC table confused and thus
Ethernet and CES service may be interrupted and Management VLAN unreachable.
It is mandatory to run STP over the network with loops.
5.8. CES over Ethernet Service

CES Service (both CESoP and SAToP) needs to use either an E-LAN or an E-Line service as the underlying
transmit vehicle (a.k.a. pseudo-wire or PW). So when setting up a CES service, either an E-LAN or an E-
Line service must be created firstly, and then CES parameters are added to the E-LAN or E-Line service so
that the CES service is established.
Note that G.8031 cannot be applied to the Ethernet service that carries CES. Instead, CES linear protection
can be applied.
5.9. CES TDM Mode Switching

Changing TDM Mode between E1/T1 will make system reboot. Note that all the TDM configurations in the
system will be automatically deleted after rebooting if the TDM Mode in the configuration file is not
consistent with that of the system.
5.10. 1+1 Hot-Standby ODU Function

When a LPG (Link Protection Group, used for 1+1 ODU) is created, a dedicated service will also be created
for P-CCM between two ODUs (P-CCM is the OAM mechanism used by 1+1 ODU for detecting the failure
of the active ODU).
P-CCM can be enabled via the Bridge Configuration and Port Configuration.
5.11. Deploying Power-plus-Ethernet (P+E)

1. Due to the attribute of the circuitry of P+E interface, it is harmful to plug and unplug the UTP cable to and
from the P+E interface very frequently with short intervals. It is strongly suggested to leave at least 5
seconds between plugging and unplugging (and vice versa) the cable.

2. When using P+E ports of IDU to feed DC power to ODUs, please keep the P+E cable length and the DC
input voltage to IDU within the following “safe border” and the overall current to all the ODUs should be
lower than 6A:
2 x ODU 4 x ODU
100m
P+E on Mainboard
40.5V ~ 53V 80m
80m 43V ~ 53V

Power Injector Card
40.5V ~ 53V
Important Notice: The P+E solution is not compatible with Power-over-Ethernet (PoE) defined by
IEEE 802.3af and 802.3at since P+E intends to provide higher power (watts) than that provided by
the two standards. Thus, it is harmful to connect FPH800 P+E interfaces to other devices than NSN’s
FlexiPacket ODU’s.
Warning: It is forbidden to connect other P+E ports (for example, the P+E ports of the external
Power Injector) to the P+E ports of FPH800 whether the P+E function of FPH800 is disabled or
enabled.
It is also highly risky to connect SPD (Surge Protection Device) to P+E ports of FPH800. FPH800 and
its Power Injector Card have surge protection on P+E ports. External SPD will not help protecting
FPH800 but may damage it.
6. Solved Issues in R2.0EP2 SU1

 Ref. No.: 12973 – Wrong service mode and bandwidth profile in WebLCT after software upgrade
Description: Service mode (translation/transparent) and the associated bandwidth profile in WebLCT is not
right after software upgrade from R2.0EP1 to R2.0EP2.
 Ref. No.: 13062 – Batch enabling PM in WebLCT for many Ethernet services may fail
Description: Enabling performance measurement (PM) simultaneously for many Ethernet services may fail.
PM of some of the services is actually not enabled. If this takes place, you can re-enable PM for these
services.
7. Solved Issues in R2.0EP2

7.1. System
 Ref. No.: FR_0000009702 – Restore to Factory Default will force the system to warm-reboot
Description: Sometimes, Restore to Factory Default makes the system to warm reboot, but the correct
process should be “cold reboot”.
Suggestion: to make sure that the system will cold-reboot after the configuration is restored to factory
default, it is better to run “hardware reboot” in WebLCT.
Now it cold reboots after the configuration is restored to factory default.

7.2. CES
 Ref. No.:FR_0000013173 – E1 port is admin down but still raises alarms
Description: All the alarms on the E1 port that is admin down should be masked (e.g., AIS can come from
the other end of E1 link but should be masked).
 Ref. No.:FR_0000013185 – Occasionally, some T1 CES service cannot recover after radio link
deep fading
Description: after the radio link resumes from deep fading, occasionally 2 to 3 T1 CES services among
many others on the link cannot recover.
Now all the T1 CES services can recover.
 Ref. No.:FR_0000012678 – CESoP service on FlexBus card cannot resume when 19E PIU reboots
Description: When the 19E PIU connecting with the FlexBus card of FPH800 cold reboots, the E1 CESoP
services on the FlexBus card cannot come back again.
Workaround: By unplugging and plugging again the FlexBus card, CESoP on this card can be recovered.
Now FB card can resume working after 19E PIU reboots.
 Ref. No.:FR_0000012616 – CESoP traffic on 16 x E1 card does not come back after the card is
plugged out and plugged in again.
Workaround: if this problem happens, just unplug and plug the card once more.
Now CES traffic on 16xE1 card can come back after the card is plugged back in.
7.3. Clock Synchronization

 Ref. No.:FR_0000003607 – Wrong clock status when a failed clock source is added
Description: When a failed clock source is added to a system whose clock is in free-run state, the system’s
clock is changed to holdover status. According to Synchronous Ethernet standard, its state should be free-run.
This issue has no practical impact on normal operation because the system is holding over its clock onto its
own free-run clock, i.e., same as in free-run state.
Now the clock remains in free-run when a failed clock source is added.
7.4. Protection
 Ref. No.:FR_0000007342 – CIST Port state is not uniform before and after cold reboot
Description: After xSTP is enabled and then disabled, the status of the ports in CIST list becomes
forwarding. However, after cold-reboot, the ports’ status shows “disabled”.
This issue does not affect the traffic. It is just that the port status is not consistently shown before and after
cold-reboot. When the port status is “disabled”, the port is actually still “forwarding”.
Now the port status remains in forwarding state after cold-reboot.
7.5. Management and WebLCT

 Ref. No.:FR_0000013212 – Static local trap receiver IP address gets lost after cold-reboot
Workaround: after cold-reboot, please remember to re-configure the static local trap IP address in WebLCT.
Note that by default the IP address of trap receiver is automatically set to be the IP address of NetViewer.

Now the static IP address of trap receiver is kept after cold-reboot.
 Ref. No.:FR_0000012717 – The tab title of PW Performance History in WebLCT is PM 1x 24H
Description: the correct tab title should be PM 4 x 24 Hours.
Now the tab title is 4 x 24 Hours.
 Ref. No.:FR_0000012605 – The initial status of “Current Data” of the current Ethernet Service
Performance is “false”
Description: In fact, it should be “true”. The initial “Current Data” cannot be false (it becomes false only
after the measured port is brought down for some while).
Now the initial status is “true”.
 Ref. No.:FR_0000009693 – WebLCT shows Mismatch but not Disconnected on a slot from which
an interface card is pulled out and the slot is unequipped
Description: After an interface card is pulled out from its slot and then the slot is unequipped, WebLCT
should show “disconnected” but it shows “not mismatch”.
Now the slot status is “disconnected” in this case.
 Ref. No.:FR_0000006509 – Excessive “LLDP information change” reports in the log
Description: In WebLCT Log Management, "LLDP information change" report is repeatedly generated,
which results in excessive LLDP Information Change reports in the log.
8. Solved Limitations in R2.0EP2

 Ref. No.:FR_0000013036 – The current release supports up to 4 LPG and 4 x LAG groups
Description: with two 4-port GE cards, the system should be able to support up to 6 LPG groups and 7 LAG
groups but currently it supports 4 x LPG, or 4 x LAG.
Now the system supports up to 6 x LPG, or up to 7 x LAG groups.
 Ref. No.:FR_0000012748 – Ethernet and CESoP traffic get hit by change of role of 2+0 ODU
Description: Warm rebooting the active ODU of 2+0 XPIC will change the role of ODUs (master/slave)
which will hit the Ethernet and CES traffic until LPG switch-over ends. This is because that ODU sends P-
CCM and E-CCM by CPU, so warm-rebooting one ODU will make IDU switch traffic to another ODU.
Now change of 2+0 ODU roles will not hit traffic.
 Ref. No.: FR_0000010100 – Mapping rule precedence can only use odd index number when
creating service with G.8031 protection
Description: Mapping rule precedence can only use odd number. The even index numbers are reserved for
G.8031 protection service.
Now both odd and even number can be used.
 Ref. No.:FR_0000007167 – Lack of notice when configuration is restored successfully from USB
memory
Description: When configuration is restored from the configuration file on the USB memory key, there is not
a notice on WebLCT telling the result of the restoration.
Now there is a trap on the result of configuration restoration.

9. Issues Newly Found in Previous Release but Fixed in R2.0EP2
Some new issues were found in previous releases (until R2.0EP1 PU7), but are fixed by this release
(R2.0EP2).
9.1. System
 Ref. No.: ID_11585 – Frequently cold-rebooting system may cause 4xGE card to stop forwarding
packets.
 Ref. No.: ID_11573 – Changing SFP port mode (GE vs. STM-1) does not turn down SFP component
Description: After changing the mode of a SFP port (GE vs. STM-1), the admin status of the SFP port and
the SFP component in the SFP port is turned down by default. However, the SFP component is not turned
down correctly in this case. As a result, the operation status of both ends of the link remains up (because the
SFP component on both sides is still up) even though the admin and operation status of the end that changed
the port mode are shown as “down” on WebLCT.
 Ref. No.: ID_11376 – ALS is not enabled on optical SFP as expected when ALS was disabled
before on an electrical SFP in the same port
Description: Disable ALS on an electrical SFP, then ALS will not be enabled on an optical SFP inserted to
the same port. The right behavior is that ALS is enabled by default on optical SFP.
 Ref. No.: ID_11305 – ALS and Laser Shutdown configuration are not reset to default after the slot
with 4xGE optical card is unequipped and then assigned to 4xGE optical card again
Description: After the slot is unequipped while with 4xGE optical card in the slot, it is re-assigned to 4xGE
optical card, ALS and Laser Shutdown configuration are supposed to be initialized. However, their
configuration remains unchanged.
Workaround: ALS and Laser Shutdown can be re-configured.
9.2. Ethernet Service

 Ref. No.: ID_11416 – NNI port of E-LAN service of source IP mapping forwards untagged packets
Description: all the packets on NNI port are supposed to carry S-Tag, all the untagged packets are dropped at
NNI port. However, when NNI has E-LAN services using source IP mapping, it forwards untagged frames.
In reality, NNI ports will never receive untagged frames, so this issue will not arise.
 Ref. No.: FR_0000012908 (ID_11053) – IP mapping should not take effect when netmask is 0.0.0.0.
Description: Net mask of 0.0.0.0 for IP mapping means that all the packets are sent to this service. This
mapping rule should not take effect.
9.3. CESoP and Clock Synchronization

 Ref. No.: ID_11443 – T1 AMI line coding is not supported anymore but still appears in WebLCT
 Ref. No.: ID_11404 – Deleting the Ethernet PW of E1 CESoP will be denied after pulling out the
16xE1 card and deleting CES services
Description: When there are E1 CESoP services on the 16xE1 card, deleting the underlying Ethernet PW of
the E1 CESoP services after the CESoP services are deleted and the card is pulled out will be denied.
Workaround: deleting CESoP service and Ethernet PW before pulling out the 16xE1 card.

 Ref. No.: FR_0000010443 (ID_7473) – The status of FB port whose admin status is down will turn
red after warm-reboot
Description: When the admin status is down, the FB (FlexBus) port LED is off. However, after warm-reboot,
the LED becomes red (Red LED = link down), which is wrong.
 Ref. No.: FR_0000010464 (ID_7325) – Index of CES service on FB card in alarm table is not clear
Description: The service ID of CES on FB card is confusing. For example, alarm of CES service #15 on FB
port 1 is displayed as FB1 and PW2/15, but it should be FB2/1 and PW15 (i.e., slot number should be in FB
port index, not in PW index).
9.4. Protection
 Ref. No.: ID_11660 – Revertive G.8031 protected service won’t switch back to working path
Description: if 1+1 or 2+0 ODU is switching roles (hot <-> standby) during IDU warm rebooting, revertive
G.8031 protected services won’t switch back to working path and will stay on protection path.
9.5. OAM
 Ref. No.: ID_11564 – Enabling PM on a large number of G.8031 protected services, then deleting
the services may cause system warm-reboot.
Workaround: disable PM before deleting the service.
 Ref. No.: ID_11498 – SLA PM counter for NNI port is not removed (null items)
 Ref. No.: ID_11493 – The loopback state becomes unknown after IDU warm-reboot
Description: While loopback is still in the status “in progress” (before release time expires), warm-reboot
will make its status known. The right status should be “in progress”.
 Ref. No.: ID_11461 – OAM DM interval in WebLCT is automatically modified from 10s to 1
second.
Description: the interval of Delay Measurement (DM) is either 1s or 10s. When 10s is configured, it will
always become 1s.
 Ref. No.: ID_11411 – “MEP Radio Link Down" alarm is not cleared after E-CCM is disabled
Description: in 1+1 hot-standby system type, the standby ODU may generate MEP Radio Link Down alarm
(because it turns off its radio port) but this alarm should have been masked or cleared automatically. It is
expected that disabling E-CCM could mask this alarm. However, this is not the case.
 Ref. No.: ID_11333 – Inconsistent PW index in PW performance table and in alarm table
Description: In PW performance table, PW Index is given by system when creating the CESoP service. In
Alarm table, “source” is expected to be PW index but it uses VC-12 index (in the format of SFP1 PW x/y,
x/y in Alarm table is not the same as in PW index, where x is slot number and y is port number).
 Ref. No.: ID_11233 – RMON counters count both sent and received packets
Description: RMON counters should count sent and received packets separately.
 Ref. No.: ID_11168 – Oversized frames are counted as dropped frames
Description: There is a dedicated counter for oversized frames. Oversized frames should not be counted as
dropped frames. Frames shorter than MTU, which is configurable per-port (default is 1632, max. is 9600),
are not dropped and so should not be counted as “dropped frames”.

 Ref. No.: FR_0000010841 (ID_7719) – A GE port used to be in LAG does not send OAM CCM
Description: For example, two ports are in LAG. Port 1 is used in LAG to send CCM. When LAG is deleted,
port 2 as an independent port now cannot send CCM.
Workaround: cold reboot the system.
 Ref. No.: FR_0000010747 (ID_7692) – MD with level 0 should not be in G.8031 MD list
Description: MD level 0 is for link layer OAM. For Ethernet OAM, valid value of MD level should be 1 – 7.
Note that OAM frame with MD=0 is sent untagged on NNI port and thus is dropped by intermediate node.
 Ref. No.: FR_0000010705 (ID_7565) – The MD and MA for G. 8031 can be deleted
Description: When configuring G.8031, MD and MA is automatically added (which can be seen in OAM
function in WebLCT) but they can be deleted, which should not be allowed.
 Ref. No.: FR_0000010594 (ID_7474) – the traffic class of OAM CCM message is not the same as
the priority of its associated Ethernet service
Description: The priority of G.8031 CCM message is not configurable and is fixed to 7 in R2.0EP1. In
R2.0EP2, it is configurable and the default is the same as the priority of its associated service.
9.6. Management and WebLCT

 Ref. No.: ID_11574 – System may lose management when SynchE module sends a large number of
traps
Description: When SynchE timing module sends a large number of traps, management may get lost but
services are still up and running.
 Ref. No.: ID_11570 – Downloading large event log may fail
Description: When flash memory does not have enough space to store large event logs, saving such log file
will make the file defective. When WebLCT tries to get the event log file using FTP, it fails.
Workaround: download the log file in time and delete it before it becomes too large
 Ref. No.: ID_11546 – FTP server of the system hangs after more than 6 FTP sessions are opened
 Ref. No.: ID_11550 – The sequence order of LAG member ports on WebLCT is not right
Description: port 1/2/3/4 is displayed as port 3/1/2/4.
 Ref. No.: ID_11524 – Inserting a new type of card in the slot already assigned to another type of
card may make system lose management and traffic interrupted
Description: for example, assign the slot to 16xE1 card, then insert 4xGE optical card without re-assigning,
the system and all the services will be interrupted. Network management gets lost.
Workaround: “assign” the slot to the new type of card before inserting the new card.
 Ref. No.: ID_11517 – WebLCT displays a string instead of a MAC address in OAM MEP database
 Ref. No.: ID_11457 – The card name in WebLCT in slot status is not the same as that in “assign”
menu.
Description: In Slot Inventory, card name is not consistent with that in “assign” menu.
 Ref. No.: ID_11256 – 3rd party device not shown in Remote System table of LLDP
Description: 3rd party devices cannot be shown in remote system table of LLDP.

 Ref. No.: ID_11255 – DCN port forwards LLDP PDU over the management VLAN
Description: If the DCN port is connected with a device that runs LLDP, it forwards LLDP PDUs over the
management VLAN. The right behavior is that DCN port drops LLDP PDUs.
 Ref. No.: ID_11236 – Power injector card can be unequipped directly while P+E is enabled
Description: P+E should be disabled before the power injector card is unequipped. In release R2.0EP2, there
is a message on WebLCT asking to disable P+E first.
 Ref. No.: ID_11199 – The ODU LED status on WebLCT is not in synch with the status on IDU
Description: The actual ODU LED status on IDU is not the same as that on WebLCT.
 Ref. No.: ID_11182 – No prompt for Ethernet OAM license when G.8031 license is activated
Description: G.8031 uses Ethernet OAM tools to detect failures. When it is activated, it assumes that
Ethernet OAM license is also installed. However, the system does not check this and there is no warning
message on WebLCT reminding users to activate Ethernet OAM as well.
 Ref. No.: FR_0000013722 (ID_11076) – Packets with Management VID are sent over E-Line
service.
Description: Adding UNI to Management VLAN, creating E-Line with mapping rule of “any”, the packet
with Management VID will be sent over the E-Line service.
This is due to wrong configuration of mapping rules. However, the system should never send Management
frames over Ethernet services.
10. Issues Solved in R2.0_1.7.0 (a.k.a. R2.0EP1 PU7)

10.1. System
 Ref. No.: FR_0000013137 – Electrical GE SFP cannot be turned up automatically when auto-neg
is enabled
Description: when electrical GE SFP is inserted to the SFP port on the mainboard, it cannot become up after
it is set to GE mode, auto-negotiation enabled and admin status is turned up.
Workaround was to set manually the auto-negotiation parameters (Auto-Negotiation Capability Advertized
Bits) of the SFP in WebLCT, and then it can be turned up.
This issue is solved. Now the electrical SFP can be turned up automatically after it is inserted.
10.2. LPG
 Ref. No.: FR_0000013132 – Wrong default priority of E-CCM
Description: the traffic priority of E-CCM is 0. The right priority of E-CCM should be 7.
This issue is solved. Now the priority of E-CCM frames is fixed to 7 (the highest).
 Ref. No.: FR_0000013072 – E-CCM of LPG is not sent to the port which used to be in LAG
Description: The GE ports used to be in LAG that was removed later on are now configured in LPG, but E-
CCM is sent only to one of the ports.
Workaround: cold- reboot after removing LAG, then configure LPG.
This issue is solved. Now E-CCM is sent to all the ports in LPG.

10.3. LAG
 Ref. No.: FR_0000009999 – SFP port cannot be added to LAG when the port’s admin status is
down
Description: LAG requires its member ports to be Full-Duplex. When Auto-negotiation is disabled on SFP
port, its default duplex type is sometimes null when admin is down, so LAG cannot be established with this
port.
Workaround solution: Setting admin status of the port up, the default duplex type will become non-null, and
LAG can be established. Another way around is to disable auto-negotiation and set port duplex to Full-
Duplex.
This issue is solved in R2.0EP1 PU7. Now the default port type of SFP port is not null and it can be added
to LAG even when the port’s admin status is down.
10.4. CES
 Ref. No.: FR_0000013039 – CESoP traffic is blocked occasionally in one direction when 2+0
becomes 1+1
Description: When a 2+0 link is configured to become 1+1 link, the CES traffic on the link may be blocked
occasionally in one direction.
Workaround: disable and then enable the CES service, it will resume.
In this release, CES traffic will not be blocked.
 Ref. No.: FR_0000012707/13046 – some CESoP will recover about 1 min after 1+1/2+0 link
resumes
Description: with 1+1 or 2+0 installation type, for whatever the reason the physical link either goes down or
change its status rapidly (due to multi-path signal fading, e.g.) which brings down CES services. After the
physical link for the CES services has recovered (either when 1+1/2+0 ODUs switch traffic to the one that is
available, or the whole link recovers from deep fading), it takes some (but not all) of the CES services about
1min to come back.
Note that 1+0 does not have this problem, i.e., the problem may arise only with LPG on IDU.
This is solved. In this release, CESoP service will come back right after the physical link recovers.
 T1 bit rate accuracy does not meet the standard specification
Description: the T1 bit rate accuracy of T1 CESoP service is required to be 1544 kbps ±3ppm, which does
not meet G.703 specifications (1544 kbps ±50 bits/s or ±32ppm).
In this release, T1 line rate accuracy can be 1544 kbps ±100ppm and T1 CESoP still works normally.
10.5. Management
 Ref. No.: FR_0000012646 – The default priority value of Management VLAN is not consistent
with that of ODU
Description: the traffic class for the management frames is priority 6 by default, but it should be 5.
In this release, default priority of the Management VLAN is set to 5.
 Ref. No.: FR_0000012940 – VLAN ID 4091-4094 cannot be set for the Management VLAN
In this release, VLAN ID 4091 – 4094 can be used for Management VLAN.

 Ref. No.: FR_0000012936 – The priority of the management frames is changed after passing from
one NNI port to another
Description: The frames tagged with the Management VLAN ID (i.e. the management frames) will be
tagged with the traffic class priority configured on the port for the Management VLAN. If this configuration
is different from port to port, the priority of the management frames will also change accordingly.
In this release, the priority of Management frames will be kept unchanged when they pass through NNI port.
 Ref. No.: FR_0000006212 – Refreshing Account Log raises Cross Threshold alarm
Description: Refreshing account log should not raise Cross Threshold alarm.
This issue is solved. Now the Cross Threshold alarm is not raised.
11. Issues Solved since R2.0_1.13.0 (a.k.a. R2.0 EP1 PU6)

11.1. System
 Ref. No.: FR_0000009215 – 4 x GE optical card cannot receive any packets in rare cases
Description: 4 x GE Optical card does not send and receive packets after it is plugged and unplugged many
times or the system is cold/warm rebooted many times.
 Ref. No.: FR_0000008124 – ODU Alarm LED is not supported on 4 x GE and Power Injector card
Description: this LED is always off.
In this release, the ODU Alarm LED can be turned on.
11.2. Ethernet Services
 Ref. No.: FR_0000009998 – Changing the management VLAN ID to a C-VLAN ID will make the
C-VLAN disappear in the mapping rules of an E-LAN service
Description: Modifying the Management VLAN ID to one of the C-VLANs used in the mapping rules for
an E-LAN service will generate an error message but the modification succeeds. However, the modification
makes the C-VLAN disappear from the mapping rules.
11.3. CES Services
 Ref. No.: FR_0000007901 – CES will stop working during system warm-reboot
Description: Using Reset command in WebLCT (i.e., warm-reboot) causes CES to stop working for a short
period of time and errors are generated. Note that Ethernet services are not impacted by warm-reboot.
 Ref. No.: FR_0000007767 – Warm resetting the systems at the same time on both ends of a CES
service interrupts CESoP traffic.
This issue is fixed in this release. Now CESoP traffic won’t be interrupted by warm-rebooting on both ends
of the service.
 Ref. No.: FR_0000007350 – CESoP service over E-LAN with LAG port cannot be configured or
deleted
Description: In the previous releases, it is not allowed to establish CES service over E-LAN PW that has
LAG port.

In this release, it is allowed to establish E-LAN PW with LAG port for CES. However, operator must
disable xSTP on the LAG as xSTP cannot run over LAG port in this release. Moreover, operator must make
sure that the E-LAN PW with LAG is established without any loops.
 Ref. No.: FR_0000006985 – long MSTP convergence time for CES over E-LAN PW with LPG port
Description: CES service runs on top of an Ethernet Pseudo-Wire (PW) that can be either an E-Line or an E-
LAN service. If this Ethernet PW is an E-LAN service that has LPG port on it and MSTP is run over the
E_LAN PW, the convergence time of MSTP can be as long as 20 seconds.
This issue is solved. Now the convergence time is less than 500ms in most cases.
11.4. CES Linear Protection
 Ref. No.: FR_0000009966 – LOF alarm on working path of CES Linear Protection brings down
service
Description: When LOF alarm is inserted to E1 CES traffic on the working path, it will cause traffic switch-
over to the protection path which is a correct behavior, but the service will go down abnormally.
This issue is solved. Now the service will not go down.
 Ref. No.: FR_0000009889/9802 – CES Linear Protection switch-over time may be more than 50ms
when CES traffic is between an interface card and the mainboard and between two interface
cards
Description: In this case, the switch-over time is occasionally (not always) around 60-80ms. Smaller CES
jitter buffer size and frame size has better switching performance.
This issue is solved. Now regardless of where the two interfaces are (on the mainboard and/or on the
interface card), the switchover time is the same.
11.5. Clock Synchronization
 Ref. No.: FR_0000003303 – no SSM when external clock is not configured

Description: There is no SSM packet when no external timing source is configured.
 Ref. No.: FR_000004520 & FR_000007324 – wrong clock status when switching clock source
Description: when two clock sources (Line Clock and Synch Ethernet) are configured, switching the clock
source makes the synchronization state enter “free run”. According to the Synch Ethernet standard, the state
should be Locked -> Hold-Over (optional) – Locked.
Note that services are not affected during clock source switching, which usually takes about 1 minute.
 Ref. No.: FR_0000009253 – IEEE 1588v2 clock synchronization fails when 1588v2 is disabled by
any of the upstream devices towards the clock source.
Description: For example, in the scenario below, two network devices (NE1 and NE2) are connected to
1588v2 clock source,
1588v2 clock source ------ NE1----- NE2
Note that the fix of this issue results in another minor issue with reference number of FR_0000012602 in the
next chapter.

 Ref. No.: FR_0000012490: FPH800R2.0: Frequent cold reboot causes 1588 status to be always -in
No Master status
Description: ToP status becomes No Master after frequent IDU cold reboot, and it can’t lock again.
Workaround: Cold reboot the system again.
 Ref. No.: FR_0000013508: Control protocol packets are counted into In Dropped Pkt in Ethernet
PM
Description: The packets of some control protocols (e.g., those of xSTP, 1588v2, LLDP, OAM, etc.) that are
supposed to go to CPU are counted as dropped packets in In-Dropped-Packet statistics in Ethernet
Performance Management.
This issue is solved. The packets of control protocols will not be counted as dropped packets by In-Dropped-
Packet statistics.
11.6. Ethernet Service Protection
 Ref. No.: FR_0000010008 – G.8031 APS messages cannot be sent over LPG or LAG port to remote
system
Description: if there is LPG or LAG port on the working path of the E-Line service on the local system, APS
messages cannot go through the LPG/LAG port.
 Ref. No.: FR_0000009764 – G.8031 commands of lower precedence can be applied but will not
cause problems
Description: G.8031 protection switching can be triggered manually by multiple commands but these
commands have their pre-defined precedence (or privilege). In the current release, command of lower
precedence is allowed to “apply” when the current command has higher precedence, which should be
forbidden, even though the command of lower precedence will not take effect.
Command precedence from high to low is Lockout –> SF to Protection –> Manual Switch to Protection. SF
stands for Signaled Failure, meaning that the path in SF status is made unavailable and thus switch-over
should take place.
This issue is solved. Now WebLCT does not allow the command with lower precedence than the current
command to be applied.
 Ref. No.: FR_0000009657 – G.8031 Protection status shows WTR which should be On Protection
Description: WTR (wait-to-restore) status means that the traffic is on protection path but the working path
has recovered and is waiting for the traffic to switch back after WTR timer expires (5min by default). During
this period, G.8031 APS (auto-protection switching) status in WebLCT should show “On Protection” instead
of WTR. Signaled APS status is WTR, though, which is correct.
 Ref. No.: FR_0000009530 – No alarm is raised when both the working and protection path fail
Description: System should raise APS_SWITCH_FAIL alarm in this case but it does not.
 Ref. No.: FR_0000009339 – Lack of Response alarm is wrongly raised when switch-over happens
to a large number of services
Description: When a large number of E-Line services on the same path are configured with G.8031
protection and protection switching takes place as a result of any failure on their working path, “Lack of
Response” critical alarm may show up in the system randomly. In fact, these services are not impacted, and
this alarm should be ignored.

 Ref. No.:FR_0000006640 – Performance Statistics of a port in LAG stops when the LAG is deleted
before disabled
Description: When a LAG is deleted before it is administratively disabled, the Ethernet ports in this LAG
will not have Ethernet Port performance statistics anymore. Recreating LAG on these ports does not address
the issue.
11.7. OAM
 Ref. No.: FR_0000007407 – System crashes when UTP cable is unplugged and plugged on the GE
port with a large number of OAM MEPs configured
Description: Unplugging/plugging cable generates an interrupt to CPU for each MEP and so a large number
of MEPs.
Now the issue is solved and the system won’t crash in this case.
11.8. WebLCT and Management
 Ref. No.: FR_0000012757 – the IP fragmentation bug in VxWorks may make FPH800 crash when
NetViewer is trying to repeatedly get some MIB nodes of the FPH800
Description: VxWorks is the operating system of FPH800 and this release has fixed the IP fragmentation
bug in VxWorks.
 Ref. No.: FR_0000011822 – System crash after rounds of PM data collection by NetViewer
Description: After a number of collections of performance measurement data (i.e., statistics) by NetViewer,
the system may crash. This issue is fixed by this release.
 Ref. No.: FR_0000009209 – Sometimes two login windows pop up
Description: After launching WebLCT, the user login window may pop up twice. Either of them can be used
for login, though.
 Ref. No.: FR_0000009187 – C-VLAN for CESoP service can be configured but will not be brought
into effect
Description: When creating CESoP service, WebLCT allows users to select a new C-VLAN, but it will be
ignored and the default C-VLAN will always be used for this CESoP service. As C-VLAN for CESoP is
only for internal use, this issue has no effect on the service.
12. Known Limitations

12.1. Known Limitations in R2.0EP2
12.1.1. CES and Clock Synchronization

 Ref. No.: ID_11113 –Cold-reboot of system brings clock status to hold-over but not free-run
Description: When FPH800 cold reboots after it locks its clock to an IEEE1588v2 master clock, it starts
from hold-over state to locked state. The right behavior should be that it starts from free-run state after cold-
reboot.
 Ref. No.: ID_11094 – An E-Line service cannot have two IEEE1588 master clocks

Description: two IEEE1588v2 master clocks cannot be on one E-Line service.
Workaround: if two masters need to be on the same service, the service can be an E-LAN.
 Ref. No.: FR_0000012352 (ID_9378) – CESoP traffic will get hit when it's MAC address learning
mode is changed
Description: Changing MAC Address Learning Mode (automatic/manual) of a CES service will interrupt
CES traffic for a short while but will resume normal.
12.1.2. OAM
 Ref. No.: FR_0000013508 (ID_10755) – Control protocol packets are counted as InDropped
Packets
Description: The control packets of the following protocols are counted as dropped packets in Performance
Monitoring (PM):
Link OAM, G.8031, Y.1731 Loss and Delay Measurement, Loopback, SSM ECCM, xSTP BPDU, LLDP
etc.
12.1.3. Management and WebLCT

 Ref. No.: FR_0000013734 (ID_11192) – Standard community names are accepted even if they were
previously disabled
Description: Even though it is disabled to use “public” and “private” as community names, the existing
community names can be changed to “public” or “private”. It is better not to allow changing existing
community names to “public” and “private”.
12.2. Known Limitations since R2.0_1.13.0 (build 2.7.30 for R2.0 EP1 PU6)
12.2.1. Management
 Ref. No.: FR_0000012646 – The default priority value of Management VLAN is not consistent
with that of ODU
Description: the traffic class for the management frames is priority 6 by default, but it should be 5.
 Ref. No.: FR_0000012940 – VLAN ID 4091-4094 cannot be set for the Management VLAN
 Ref. No.: FR_0000012936 – The priority of the management frames is changed after passing from
one NNI port to another
Description: The frames tagged with the Management VLAN ID (i.e. the management frames) will be
tagged with the traffic class priority configured on the port for the Management VLAN. If this configuration
is different from port to port, the priority of the management frames will also change accordingly.
12.2.2. Protection
 Ref. No.: FR_0000012748 – Ethernet and CESoP traffic get hit by change of role of 2+0 ODU
Description: Warm rebooting the active ODU of 2+0 XPIC will change the role of ODUs (master/slave)
which will hit the Ethernet and CES traffic until LPG switch-over ends. This is because that ODU sends P-
CCM and E-CCM by CPU, so warm-rebooting one ODU will make IDU switch traffic to another ODU.
 Ref. No.: FR_0000013036 – The current release supports up to 4 LPG groups

Description: with two 4-port GE cards, the system should be able to support up to 6 LPG groups but
currently it supports 4.
 Ref. No.: FR_0000008874 – Long LAG switchover time between FPH800 and Cisco7609 router
Description: LAG convergence time is more than 3 seconds when SrcMAC-XOR-DestMAC is used
between FPH800 and Cisco 7600 as load sharing algorithm.
 xSTP does not support LAG
Description: even though all the physical ports are in xSTP port list in WebLCT by default, operator must
disable xSTP on the ports when they are configured as LAG.
12.2.3. Clock Synchronization

 Ref. No.: FR_0000012602 – IEEE1588v2 clock synch has unexpected intermediate states when
IEEE1588v2 function is disabled at the system with the master clock
Description: when IEEE1588v2 function is disabled in the FPH800 that is connected with the IEEE1588
clock source (master clock), the other FPH800 systems sharing this master clock can lock to this clock after
going through some intermediate status changes (i.e., status changes from Locking  No Master  Locking
 Locked). The intermediate states are not expected but they do not pose any practical impact on the
normal IEEE1588 functions, also because that it happens only when the IEEE1588 function is disabled
shortly after the FPH800 connected with the master clock is powered up.
 E1 cross-connect function and IEEE1588v2 cannot be used at the same time
Description: Cross-connect and IEEE1588v2 cannot be used at the same time. However, there is no prompt
in WebLCT when the two functions are both configured (which should have been forbidden). In this case,
TDM traffic will not pass through the cross-connect.
Note: Cross-connect is used for the local E1 and STM-1 ports to talk to each other and it is not relevant to
CES.
12.3. Known Limitations since R2.0_1.4.0 (build version 2.8.21 for R2.0 EP1)
 Ref. No.: FR_0000010100 – Mapping rule precedence can only use odd index number when
creating service with G.8031 protection
Description: Mapping rule precedence can only use odd number. The even index numbers are reserved for
G.8031 protection service.
12.4. Known Limitations since R2.0_1.1.0 (build version 2.8.14 for R2.0 EP1)
 Ref. No.: FR_0000009936 – CESoP traffic will go down with Jumbo Frame traffic under 7/14MHz
QPSK modulation of FPMR R2.4
Description: This issue only happens when FPH800 is working with FPMR2.4, and will be solved in FPMR
2.5.
12.5. Known Limitations since R2.0_0.2.0 (build version 2.7.14)

 Ref. No.:FR_0000007167 – Lack of notice when configuration is restored successfully from USB
memory
Description: When configuration is restored from the configuration file on the USB memory key, there is not
a notice on WebLCT telling the result of the restoration.

12.6. Known Limitations since R2.0 (build version 2.7.7)
12.6.1. System
 Ref. No.: FR0000004051 – OOB port does not work with 10Mbps
Description: When the Ethernet interface of WebLCT PC is forced to 10Mbps, WebLCT will not be able to
communicate with the system.
Solution: Do not force 10Mbps on the Ethernet interface of the WebLCT PC.
12.6.2. QoS
 Ref. No.:FR_0000001740 – WRR not accurate for large frames
Description: WRR scheduling is not always accurate when frame MTU is larger than 1000 bytes, in which
case, queue 7 and queue 6 (i.e., the two highest priority queues) demonstrate the same weight regardless of
the actual weight configured for them.
 Ref. No.:FR_0000001741 – DDR not accurate for large frames
Description: DRR scheduling is not always accurate – same phenomenon as FR_0000001740.
 Ref. No.:FR_0000003490 – Odd DRR weight becomes even
Description: When DRR weight is configured with an odd number, the system will set the actual value as
odd +1.
Suggestion: operators can use even numbers for weights. For example, instead of 1, 3, and 5, operators can
use 2, 6, and 10.
 Ref. No.:FR_0000004848 – Rate limiting not accurate when Whole Traffic and BC/MC/Unknown
Traffic policing are both applied on the same port
Description: Rate limiting is not accurate when both Whole Traffic Policer and BC/MC/Unknown Policer
are applied at the same time.
Note: Whole Traffic Policer is an independent traffic policer that can be applied to a port and limit the rate
of all the traffic on this port. BC/MC/Unknown Policer is the traffic policer that limits all the Broadcast,
Multicast and Unknown-Address traffic rate on a port for all the E-LAN services on this port.
Workaround solution: In most cases, Whole Traffic Policer is not used because each service has its own
traffic policer. In this case, Whole Traffic Policer can be disabled and this problem will not appear.
12.6.3. Protection
 Ref. No.:FR_0000003311 – xSTP does not work while system is warm rebooting
Description: When the system is warm rebooting, temporary loops may exist in the network until xSTP is up
and running.
12.6.4. OAM
 Notes on CCM (Continuity Check Messages ) Scalability
Description: FPH800 supports 3.33ms CCM interval for up to 256 services. However, there should be no
more than 32 CCM of 3.33ms flows on one GE port.

Other configurable CCM intervals are 10ms, 100ms, 1sec. For these intervals, the number of CCM flows per
port is not restricted.
 Notes on Performance Measurement Scalability
Description: In the current release, service-level performance measurement (including Loss Measurement
and Delay Measurement) must be triggered manually on WebLCT. When triggered, performance
measurement function will send 32 messages continuously and there should be no more than 8 MEPs
sending these messages at the same time.
12.6.5. CES
 Ref. No.:FR_0000004032 – SSRC range not fully supported
Description: SSRC (Synchronization Source) range does not fully comply with the standard CESoPSN
(RFC5086) and SAToP (RFC4553). The supported range is 0x00000000~0x7FFFFFFF. Range 0x80000000
~ 0xFFFFFFFF is not supported.
 Ref. No.: FR_0000005647 – Non-interoperability with FM200 in UDP port range 63488 to 65535
Description: Because UDP ports 63488 to 65535 are reserved by FPH800 for TDM cross-connect which
FM200 does not support, FPH800 does not interoperate with FM200 in this UDP port range.

 Ref. No.:FR_000006917 – Clock can’t be locked when SFP port with electrical SFP is set as timing
source
Description: when the SFP port of the system is configured as GE port and electrical SFP is inserted in this
port, this port cannot be used as Synchronous Ethernet clock source.
 Ref. No.: FR_0000007335 – Warm reboot stops SSM
Description: During the time the system is warm rebooting, no SSM can be sent. This is a normal behavior
as SSM is generated by CPU.
13. Known Issues

13.1. Known Issues in R2.0EP2
13.1.1. CES Services and Clock Synchronization

 Ref. No.: ID_11602 – T1 port counters do not count the FAS or CRC errors injected to T1 traffic
coming into T1 ports on the mainboard of the system
Description: This is the same issue as FR_0000007687/9153, an existing issue since R2.0.
 Ref. No.: ID_11584 – HP alarm source ID is port ID but not VC ID
Description: In Alarm list, the source ID of STM-1 HP (High Path) alarm uses port ID instead of VC-4 ID,
for example, SFP 0/1 instead of VC4/1. Still, it can be seen that the alarm comes from the SFP port 0/1 on
the mainboard of the system.
 Ref. No.: ID_11555 – Occasionally one of TDM CC services cannot recover after cold-reboot
Description: One of the CC (cross-connect) services cannot recover after cold-reboot.

 Ref. No.: FR_0000011864 (ID_10792) – Restoring configurations on different card (e.g.,
configuration of FB card restored to 16xE1 card) does not resume CES traffic when the original
card is plugged back in.
Workaround: Re-plug the original card and the configuration will be set in it again, and CES traffic will
resume.
Suggestion: do not download configuration file to a new hardware environment. WebLCT does not check
the consistency between the hardware configurations and the software configurations.
 Ref. No.: ID_11110 – RS-TIM alarm on working path of 1+1 MSP generates HP-RDI while traffic
is on the protection path
Description: In 1+1 MSP mode, when STM-1 traffic is on the protection link and the working link has RS-
TIM alarm, the local system sends both MS-RDI and HP-RDI alarm to the remote system. In fact, it should
only send MS-RDI. HP-RDI should be ignored in this case.
 Ref. No.: FR_0000013692 (ID_11039) – Enabling TU-AIS function on STM-1 port should not send
out TU-AIS alarm when the VC channel has no CC configured
Description: TU-AIS function refers to E1 AIS replicated in TU-12 header. TU-AIS is raised only when
STM-1 port has E1 CES or E1 CC associated with it and the E1 has AIS. However, TU-AIS alarm is
generated on STM-1 port even when it has no cross-connect or CES service with any E1 ports. In this case,
TU-AIS should be ignored.
 Ref. No.: FR_0000013627 (ID_10948) – Adding timing frequency offset of 100ppm, the
downstream device becomes timing-unlocked, and clock synch state goes to free-run
Description: Adding 100ppm offset to E1 on IDU that synchronizes its clock to the E1 port and propagates
the clock via Synchronous Ethernet to other devices, the downstream device such as ODU may enter free-
run, and in some cases even hang up, which is the normal result. The right behavior is that IDU does not
send this clock to the downstream devices. In the current release, IDU does not impose any restrictions on
the clock offset of its clock source.
13.1.2. Protection
 Ref. No.: ID_11665 – In 1+1 mode, MEP Radio Link Down alarm may arise randomly
Description: this alarm should arise only when the radio link is down, but in 1+1 hot-standby mode, the
standby ODU shuts down its radio port and so generates “radio link down” alarm that should have been
masked.
 Ref. No.: ID_11635 – B-bit alarm and R-bit alarm raised at the same time
Description: In G.8031 linear protection, FPH800 supports 1:1 protection only (B-bit is always 1) and
revertive mode is configurable (R-bit can be either 0 or 1). In pure NSN environment, there should never be
B-bit alarm. However, when connecting with 3rd party device, FPH800 may generate both R-bit and B-bit
alarms.
In this case, operators should check G.8031 configurations on both FPH800 and the 3rd party device to see
whether 1:1 is configured on the 3rd party device and whether revertive/non-reviertive mode is configured
consistently in both devices.
13.1.3. OAM
 Ref. No.: ID_11632 – One record of 15min PM date is split into two records (1s and 899s)

Description: 15 minutes equal to 900 seconds. 15 minutes of Ethernet Service PM data is somehow split into
two parts, one for 1 second and one for 899 seconds.

 Ref. No.: FR_0000012786 (ID_9797) – The SFP port with STM-1 mode should not be in Ethernet
port list.
Description: The SFP ports when configured as STM-1 show up in the port list of LLDP, or MSTP, or CCM.
Note that this issue exists in previous release as well (similar to FR_0000009148).
13.2. Known Issues in R2.0_1.13.0 (build 2.7.30 for R2.0EP1 PU6)
13.2.1. System
 Ref. No.: FR_0000012593 – The IP address of SNTP server is not set to default after the
configuration is set to factory default
Description: After “set to factory default” is operated, the IP address of the SNTP server does not go back to
factory default (0.0.0.0).
 Ref. No.: FR_0000013137 – Electrical GE SFP cannot be turned up automatically
Description: when electrical GE SFP is inserted to the SFP port on the mainboard, it cannot be turned up
automatically.
Workaround is to set manually the auto-negotiation parameters of the SFP in WebLCT, and then it can be
turned up.
13.2.2. Protection
 Ref. No.: FR_0000013072 – ECCM of LPG is not sent to the port which used to be in LAG
Description: The GE ports used to be in LAG that was removed later on are now configured in LPG, but E-
CCM is sent only to one of the ports.
Workaround: cold- reboot after removing LAG, then configure LPG.
 Ref. No.: FR_0000013132 – Wrong default priority of E-CCM
Description: the default E-CCM priority is 0. The right default priority of E-CCM should be 7.
Suggestion: it is better to change the priority of E-CCM in WebLCT to 7.
 Ref. No.: FR_0000009999 – SFP port cannot be added to LAG when the port’s admin status is
down
Description: LAG requires its member ports to be Full-Duplex. When Auto-negotiation is disabled on SFP
port, its default duplex type is sometimes null when admin is down, so LAG cannot be established with this
port.
Workaround solution: Setting admin status of the port up, the default duplex type will become non-null, and
LAG can be established. Another way around is to disable auto-negotiation and set port duplex to Full-
Duplex.
13.2.3. CES
 Ref. FR_0000012707/13046 – some CESoP will recover about 1 min after 1+1/2+0 link resumes

Description: with 1+1 or 2+0 installation type, for whatever the reason the physical link either goes down or
change its status rapidly (due to multi-path signal fading, e.g.) which brings down CES services. After the
physical link for the CES services has recovered (either when 1+1/2+0 ODUs switch traffic to the one that is
available, or the whole link recovers from deep fading), it takes some (but not all) of the CES services about
1min to come back.
Note that 1+0 does not have this problem, i.e., the problem may arise only with LPG on IDU.
 Ref. No.: FR_0000013039 – CESoP traffic is blocked occasionally in one direction when 2+0
becomes 1+1
Description: When a 2+0 link is configured to become 1+1 link, the CES traffic on the link may be blocked
occasionally in one direction.
Workaround: disable and then enable the CES service, it will resume.
 Ref. No.: FR_0000013173 – E1 port is admin down but still raises alarms
Description: All the alarms on the E1 port that is admin down should be masked (e.g., AIS can come from
the other end of E1 link but should be masked)
 Ref. No.: FR_0000012678 – CESoP service on FlexBus card cannot resume when 19E PIU
reboots
Description: When the 19E PIU connecting with the FlexBus card of FPH800 cold reboots, the E1 CESoP
services on the FlexBus card cannot come back again.
Workaround: By unplugging and plugging again the FlexBus card, CESoP on this card can be recovered.
 Ref. No.: FR_0000012616 – CESoP traffic on 16 x E1 card does not come back after the card is
plugged out and plugged in again.
Workaround: if this problem happens, just unplug and plug the card once more.
 Ref. No.: FR_0000008067 – slow fading between ODUs makes IDU E1frequency shift more than
4ppm
Description: The E1 frequency shift of 4ppm is as compared with the clock source. There is no impact on the
E1 CES traffic, though, and Unlock alarm will be raised.
 T1 bit rate accuracy does not meet the standard specification
Description: the T1 bit rate accuracy of T1 CESoP service is required to be 1544 kbps ±3ppm, which does
not meet G.703 specifications (1544 kbps ±50 bits/s or ±32ppm).
 Ref. No.: FR_0000013185 – Occasionally, some T1 CES service cannot recover after radio link
deep fading
Description: after the radio link resumes from deep fading, occasionally 2 to 3 T1 CES services among
many others on the link cannot recover.

 Ref. No.: FR_0000012697 – Synch type of E1 port is not PW Recovery when E1 is the timing
source
Description: Synchronization Type of E1 port must be PW Recovery when E1 port is configured as the
timing source. In the current release, users can configure other synch types, which should have been
forbidden.

13.2.5. STM-1
 Ref. No.: FR_0000009148 – STM-1 SFP Port appears in MSTP table
Description: when the SFP ports on the mainboard of FPH800 are configured as STM-1 ports, they still
appear in MSTP table, which is wrong.
 Ref. No.: FR_0000006372 – External commands are saved in MIB and not cleared when there is
line SF or SD
Description: When the two SFP ports on the mainboard are configured as STM-1 1+1 MSP ports, external
commands trying to switch traffic to the working path that has SF (Signal Fail) and SD (Signal Degradation)
still present as current command and are saved in MIB. The right behavior in this case is that all the external
commands be cleared and not saved in the MIB.
13.2.6. G.8031
 Ref. No.: FR_0000010063 – G.8031-protected E-Line service enters wrong status after the
working channel has recovered
Description: When the failed G.8031 working path becomes available again, both ends of the G.8031
protected service should enter WTR (wait-to-restore) state when revertive mode is enabled for G.8031
protection. However, one of the ends of the service enters hold-off status but it can switch traffic back to the
working path after WTR timer expires.
 Ref. No.: FR_0000009981 – Far-end has wrong APS status when there is G.8031 Signal Fail on the
working path
Description: when there is Signal Fail (SF) alarm on the working path, the near end has the right signaled
APS status (which is SF on Working), but the far end has “no request on protection”, which is wrong.
13.2.7. OAM in WebLCT

 Ref. No.: FR_0000012717 – the tab title of PW Performance History in WebLCT is PM 1x 24H
Description: the correct tab title should be PM 4 x 24 Hours.
 Ref. No.: FR_0000012605 – The initial status of “Current Data” of the current Ethernet Service
Performance is “false”
Description: In fact, it should be “true”. The initial “Current Data” cannot be false (it becomes false only
after the measured port is brought down for some while).
 Ref. No.: FR_0000006707 – Malformed Packets counters are reset after Payload Type Mismatch
alarm is removed.
Description: the right behavior should be that the Malformed Packet counters are intact when Payload Type
Mismatch alarm is removed.
 Ref. No.: FR_0000012589 – The Error Frame counter is not correct for FlexBus (FB) card
performance
Description: Error Frame counter does not count the right value of wrong FB frames, thus should be ignored.
This will be fixed in the next release.
13.2.8. WebLCT and Management

 Ref. No.: FR_0000009693 – Card Name and Slot Mismatch

Description: In WebLCT, interface card name does not match the display on the slot location after the card
is pulled out from the slot and unequipped in WebLCT.
 Ref. No.: FR_0000006212 – Refreshing Account Log raises Cross Threshold alarm
Description: Refreshing account log should not raise Cross Threshold alarm.
 Ref. No.: FR_0000013212 – Static local trap IP address gets lost after cold-reboot
Workaround: after cold-reboot, please remember to re-configure the static local trap IP address in WebLCT.
Note that by default the IP address of trap receiver is automatically set to be the IP address of NetViewer.
13.3. Known Issues since R2.0_1.1.0 (build version 2.8.14 for R2.0 EP1)
13.3.1. System
 Ref. No.: FR_0000009702 – Restore to Factory Default will force the system to warm-reboot
Description: Sometimes, Restore to Factory Default makes the system to warm reboot, but the correct
process should be “cold reboot”.
Suggestion: to make sure that the system will cold-reboot after the configuration is restored to factory
default, it is better to run “hardware reboot” in WebLCT.
 Ref. No.: FR_0000009149 – Status LED on Power Injector card does not work when surge occurs
Description: When electricity surge appears, the status LED on Power Injector card goes off.
13.3.2. Ethernet Service Protection

 Ref. No.: FR_0000009761 – Cold-reboot will clear G.8031 command
Description: cold-reboot will clear the latest G.8031 command (e.g., Manual Switch) that was run before the
cold-reboot.
 Ref. No.: FR_0000009648 – G.8031 APS R-Bit Mismatch alarm does not disappear when system
cannot receive APS messages
Description: After backup path is disconnected, G.8031 APS R-Bit mismatch alarm does not disappear.
Same behavior is for A-bit, B-bit, and D-bit in APS messages. These alarms can be ignored if they are raised
in this case.
 Ref. No.: FR_0000009336 – Card Absent alarm does not override CCM-LOS and Channel Fail
alarm
Description: As a rule of thumb, alarm on lower network layer should override alarm on higher network
layer so that the root cause is better suggested and excessive but unnecessary alarms can be avoided. When
G.8031 APS is configured on an interface card and this card is pulled out from the system, CCM-LOS and
Channel Fail alarm (both are on service layer) are also raised together with Card Absent alarm.

 Ref. No.: FR_0000009466 – Warm reboot of local system causes the IEEE1588 module of the
remote system to reboot
Description: When IEEE1588 clock synchronization is working over an E-LAN service, warm rebooting a
local system of the IEEE1588 service will make a remote system (the slave of IEEE1588 clock) to reboot its
IEEE1588 module and it has to relock to the clock after the local system comes back again, which may take

about 15 minutes. The right behavior of the remote system should be entering “lock” status without
rebooting its IEEE 1588 module. This issue will not arise when IEEE1588 runs over E-Line service.
13.4. Known Issues since R2.0_0.2.0 (build version 2.7.14)
13.4.1. CES
 Ref. No.: FR_0000007687/9153 – T1 port counters do not count the FAS or CRC errors injected to
T1 traffic coming into T1 ports on the mainboard of the system.
13.5. Known Issues since Build v2.7.7 of R2.0
13.5.1. System
 Ref. No.: FR0000007212 – Ethernet Port LED wrongly displayed
Description: After factory default configuration is restored, all the ports of 4xGE Card are down, but their
LED’s are still on.
13.5.2. E-Line and E-LAN Service

 Ref. No.:FR_0000001582 – Wrong MAC address aging time
Description: Actual MAC address aging time exceeds the configured aging time. For example,
When the configured aging time is 300sec, the actual aging time is 400sec.
13.5.3. Protection
 Ref. No.:FR_0000007342 – CIST Port state is not uniform before and after cold reboot
Description: After xSTP is enabled and then disabled, the status of the ports in CIST list becomes
forwarding. However, after cold-reboot, the ports’ status shows “disabled”.
This issue does not affect the traffic. It is just that the port status is not consistently shown before and after
cold-reboot. When the port status is “disabled”, the port is actually still “forwarding”.
 Ref. No.:FR_0000007085 – ECCM includes SFP ports when configured as STM-1
Description: When the two SFP ports on the base system are configured to STM-1, they still appear in
ECCM configuration table. In fact, in this case, the two SFP ports are not relevant to ECCM and should not
appear in ECCM configuration table.
 Ref. No.:FR_0000005356 – STM-1 1+1 MSP has wrong switch-over priority
Description: Manual Switch has higher priority level than SF (Signaled Failure). The right behavior is that
SF has higher priority level than Manual Switch.
13.5.4. CES
 Ref. No.: FR_0000006902 – LP_DEG alarm is raised when STM-1 1+1 MSP is switching over

Description: VC-12 LP_DEG may be generated during STM-1 1+1 MSP switch-over. While this is a normal
behavior, it can be annoying sometimes. In the future release, alarm suppression will be added so that LP-
DEG can be suppressed if configured so.
 Ref. No.: FR_0000007106 – TU-LOM can’t be displayed in HP PM
Description: TU-LOM can't be displayed in current status of HP-PM, and HP-UAS does not count for it.
 Ref. No.: FR_0000007078 – There is no status for RS-TIM and TU-LOM
Description: The "Current Status" of RS-TIM and TU-LOM is NoDefect, which does not mean anything
because these two alarms do not have counters in the system. RS-TIM and TU-LOM counter will be added
in the future release.
 Ref. No.: FR_0000007687/9153 – T1 port counters do not count the FAS or CRC errors injected to
T1 traffic coming into T1 ports on the mainboard of the system
Description: when FAS or CRC error is inserted to T1 CES service, the T1 port counter cannot count the
errors.

 Ref. No.:FR_0000003607 – wrong clock status when a failed clock source is added
Description: When a failed clock source is added to a system whose clock is in free-run state, the system’s
clock is changed to holdover status. According to Synchronous Ethernet standard, its state should be free-run.
This issue has no practical impact on normal operation because the system is holding over its clock onto its
own free-run clock, i.e., same as in free-run state.
 Ref. No.: FR_0000007867 – Wrong clock synchronization status after active ODU is cold-rebooted
Description: In the case of 1+1 ODU hot-standby, after the active ODU is cold-rebooted, the IDU
synchronization status becomes free-run. The right status should be hold-over. There is no practical impact
on clock synchronization.
 Ref. No.: FR_0000008055 – Two IEEE1588v2 masters cannot use two different E-LAN services
Description: If there are two clock masters, they cannot use two different E-LAN services. They can use
either one E-LAN service or two different E-Line services.
 Ref. No.: FR_0000008054 – Two IEEE1588v2 masters cannot share one E-Line service
Description: It is not possible to configure two IEEE1588v2 masters on the same E-Line service. Two
masters can be on two different E-Line services, or on one E-LAN service.
 Ref. No.: FR_0000007793 – “timing interface down” alarm
Description: When SSM is enabled and no clock source is configured, adding an Ethernet clock source will
generate “timing interface down” alarm for 5 seconds. This is the normal behavior.

 Ref. No.: FR_0000005994 – SLA statistics does not run if service PM is not enabled
Description: In WebLCT, menu item Statistics -> SLA (which shows the statistics of Green Packets and
Total Packets of each service) does not work if “Service Performance Measurement” (i.e., Service PM) is
not enabled. To enable service PM, operators can go to menu item Performance -> Ethernet Service ->
Switch and enable Service PM for the selected services.

 Ref. No.:FR_0000006509 – Excessive “LLDP information change” reports in the log
Description: In WebLCT Log Management, "LLDP information change" report is repeatedly generates,
which results in excessive LLDP Information Change reports in the log.
14. Documentations
 FlexiPacket Hub 800 Product Description
 FlexiPacket Hub 800 Operation and Maintenance Guide

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

capacity, or performance of the mentioned hardware or software products are given “as is”
and all liability arising in connection with such hardware or software products shall be
defined conclusively and finally in a separate agreement between Nokia Siemens Networks
and the customer. However, Nokia Siemens Networks has made all reasonable efforts to
ensure that the instructions contained in the document are adequate and free of material
errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia
Siemens Networks, explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN
NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES,
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE
USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered
trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2013. All rights reserved.

FlexiPacket Hub 800 Customer Release Notes R2 0 EP2 SU1 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

FlexiPacket Hub 800 Customer Release Notes R2 0 EP2 SU1 PDF

Caricato da

Copyright:

Formati disponibili

Customer Release Notes

Product Family: FlexiPacket

© Nokia Siemens NetworksCompany Confidential- 1 - 1

© Nokia Siemens NetworksCompany Confidential- 2 - 2

© Nokia Siemens NetworksCompany Confidential- 3 - 3

© Nokia Siemens NetworksCompany Confidential- 4 - 4

2. Compatibility, System Installation Types and Interoperability

2.2. System Type Compatibility

A-Series FM200 R2.0 FM200 R2.0EP1

Interoperability tests have been done with:

© Nokia Siemens NetworksCompany Confidential- 5 - 5

3. What’s New in R2.0EP2 SU1

4. What’s New in R2.0EP2

© Nokia Siemens NetworksCompany Confidential- 6 - 6

5. Operation Considerations and Hints

5.2. Security Software Package

5.3. OOB Interface

5.4. Public IP Address of DCN Interface

5.5. The Number of Services

© Nokia Siemens NetworksCompany Confidential- 7 - 7

5.6. Service VLAN ID Range for E-LAN and E-Line Service

5.8. CES over Ethernet Service

5.9. CES TDM Mode Switching

5.10. 1+1 Hot-Standby ODU Function

5.11. Deploying Power-plus-Ethernet (P+E)

© Nokia Siemens NetworksCompany Confidential- 8 - 8

80m 43V ~ 53V

6. Solved Issues in R2.0EP2 SU1

7. Solved Issues in R2.0EP2

© Nokia Siemens NetworksCompany Confidential- 9 - 9

7.3. Clock Synchronization

7.5. Management and WebLCT

© Nokia Siemens NetworksCompany Confidential- 10 - 10

8. Solved Limitations in R2.0EP2

© Nokia Siemens NetworksCompany Confidential- 11 - 11

9.2. Ethernet Service

9.3. CESoP and Clock Synchronization

© Nokia Siemens NetworksCompany Confidential- 12 - 12

© Nokia Siemens NetworksCompany Confidential- 13 - 13

9.6. Management and WebLCT

© Nokia Siemens NetworksCompany Confidential- 14 - 14

10. Issues Solved in R2.0_1.7.0 (a.k.a. R2.0EP1 PU7)

© Nokia Siemens NetworksCompany Confidential- 15 - 15

© Nokia Siemens NetworksCompany Confidential- 16 - 16

11. Issues Solved since R2.0_1.13.0 (a.k.a. R2.0 EP1 PU6)

11.2. Ethernet Services

11.3. CES Services

© Nokia Siemens NetworksCompany Confidential- 17 - 17

11.4. CES Linear Protection

11.5. Clock Synchronization

 Ref. No.: FR_0000003303 – no SSM when external clock is not configured

© Nokia Siemens NetworksCompany Confidential- 18 - 18

11.6. Ethernet Service Protection

© Nokia Siemens NetworksCompany Confidential- 19 - 19

11.8. WebLCT and Management

12. Known Limitations

12.1.1. CES and Clock Synchronization

© Nokia Siemens NetworksCompany Confidential- 20 - 20

12.1.3. Management and WebLCT

© Nokia Siemens NetworksCompany Confidential- 21 - 21

12.2.3. Clock Synchronization

12.5. Known Limitations since R2.0_0.2.0 (build version 2.7.14)

© Nokia Siemens NetworksCompany Confidential- 22 - 22