FlexiPacket FirstMile200 Customer Release Notes R2.0 1.1.0 v2

(1)

Customer Release Notes

Product Family: FlexiPacket

Product: FirstMile 200

Release: R2.0_1.1.0(R2.0 EP1 SU1)

Customer: Generic Delivery

(2)

T

ABLE OF

C

ONTENTS

1.

1. IMPORTANT NOTICE IMPORTANT NOTICE ... 4... 4

1.1.

1.1. W

W

HATHAT

’’

S NEW INS NEW IN

R2.0_1.1.0(R2.0EP1 SU1)

R2.0_1.1.0(R2.0EP1

SU1) ...

...

... 4

4

2.

2. COMPATIBILITY AND ICOMPATIBILITY AND INTEROPERABILITY NTEROPERABILITY ... 4... 4

2.1.

2.1. SYSTEM TYPE

SYSTEM

TYPE COMPATIBILI

COMPATIBILITY ...

TY ... 4

4

2.2.

2.2. INTEROPERABILITY

INTEROPERABIL

ITY ...

... ...

...

... 4

4

3.

3. HARDWARE CHANGE BY THIS HARDWARE CHANGE BY THIS RELEASE RELEASE ... ... 4... 4 4.

4. PRODUCT FEATURE SET PRODUCT FEATURE SET ... 5... 5

4.1.

4.1. M

M

AIN FEATURES TILL PREVIOUS RELEASEAIN FEATURES TILL PREVIOUS RELEASE

(R2.0)

(R2.0) ...

... ...

... 5

5

4.2.

4.2. N

N

EWEW

F

EATURES IN RELEASEEATURES IN RELEASE

R2.0_1.0.0

R2.0_1.0.0 ...

... ... 7

... 7

5.

5. OPERATION CONSIDERATIONS OPERATION CONSIDERATIONS AND HINTS AND HINTS ... 7... 7

5.1.

5.1. O

O

PERATING THEPERATING THE

S

YSTEMYSTEM

... 7

5.2.

5.2. L

L

ICENSEICENSE

M

ANAGEMENTANAGEMENT

...

... ...

... 7

5.3.

5.3. OOB

OOB II

NTERFACENTERFACE

...

... ...

... 8

5.4.

5.4. P

P

UBLICUBLIC

IP

IP A

A

DDRESS OFDDRESS OF

DCN

DCN II

NTERFACENTERFACE

...

... ... 8

... 8

5.5.

5.5. S

S

ERVICEERVICE

VLAN

VLAN ID

ID R

R

ANGE FORANGE FOR

E-LAN

AND AND

E-L

INEINE

S

ERVICEERVICE

...

... 8

8

5.6.

5.6. CES

CES

OVER OVER

E

THERNETTHERNET

S

ERVICEERVICE

...

... 8

8

5.7.

5.7. CES

CES TDM

TDM M

M

ODEODE

S

WITCHINGWITCHING

...

... ...

... 8

8

5.8.

5.8. 1+1

1+1 H

H

OTOT

-S

TANDBYTANDBY

ODU

ODU F

F

UNCTIONUNCTION

...

... 8

5.9.

5.9. P

P

OWEROWER

-P

LUSLUS

-E

THERNETTHERNET

(P+E)

(P+E) D

D

EPLOYMENTEPLOYMENT

...

... ... 8

... 8

6.

6. SOLVED ISSUES IN R2.0_1.1.0 AND R2.0_1.0.0 ... 8SOLVED ISSUES IN R2.0_1.1.0 AND R2.0_1.0.0 ... 8

6.1.

6.1. M

M

ANAGEMENT ANDANAGEMENT AND

W

EBEB

LCT

LCT ...

... ... 9

... 9

7.

7. SOLVED ISSUES IN R2.0 ... 9SOLVED ISSUES IN R2.0 ... 9

7.1.

7.1. S

S

YSTEMYSTEM

...

... 9

7.2.

7.2. E-LAN S

E-LAN

S

ERVICEERVICE

... 9

7.3.

7.3. P

P

ROTECTIONROTECTION

... 9

7.4.

7.4. CES ... 10

CES ... 10

7.5.

7.5. C

C

LOCKLOCK

S

YNCHRONIZATIONYNCHRONIZATION

...

... 10

10

7.6.

7.6. M

M

ANAGEMENT ANDANAGEMENT AND

W

EBEB

LCT

LCT ...

... ... 10

... 10

8.

8. KNOWN ISSUES OR LIMITATIONS IN KNOWN ISSUES OR LIMITATIONS IN R2.0_1.1.0 AND R2.0_1.0.0 ... 11R2.0_1.1.0 AND R2.0_1.0.0 ... 11

8.1.

8.1. E-LAN S

E-LAN

S

ERVICEERVICE

... 11

8.2.

8.2. CES ... 11

CES ... 11

9.

9. KNOWN ISSUES OR LKNOWN ISSUES OR LIMITATIONS IN R2.0_1.0.0 IMITATIONS IN R2.0_1.0.0 ... ... 11... 11

9.1.

9.1. S

S

YSTEMYSTEM

...

... 11

9.2.

(3)

9.3. Q

O

S ... 13

9.4. P

ROTECTION

... 13

9.5. OAM ... 13

9.6. CES ... 14

9.7. C

LOCK

S

YNCHRONIZATION

... 14

9.8. M

ANAGEMENT AND

W

EB

LCT ... ... 15

10. SOLVED ISSUES UNTIL R1.0 EP1 ... 16

11. KNOWN ISSUES IN R1.0 EP1 ... 16

11.1. S

YSTEM

... 16

11.2. E-LAN S

ERVICE

... 17

11.3. Q

O

S ... 17

11.4. P

ROTECTION

... 17

11.5. CES ... 18

11.6. C

LOCK

S

YNCHRONIZATION

... 18

11.7. M

ANAGEMENT AND

W

EB

LCT ... ... 18

12. DOCUMENTATIONS ... 19 SCOPE

The following software releases are in scope of this document: FlexiPacket FirstMile 200:

Current Release: 2.0_1.1.0 Current Build Version: 2.1.11 Release date: 30 March 2012 WebLCT: 2.1.11

(4)

1. Important Notice

The “system”, “FM200” and “IDU” in this document are specifically referred to FlexiPacket FirstMile

200. 1.1. What’s new in R2.0_1.1.0(R2.0EP1 SU1)

In the previous release R2.0_1.0.0 (R2.0 EP1), the management of FM200 by NetViewer may get lost

after NetViewer runs a few times of the operations of collecting performance data or statistics counters

from FM200. This issue is solved by this release. It is highly recommended that the customers using

R2.0_1.0.0 (R2.0 EP1) to upgrade the software of FM200 to this release.

2. Compatibility and Interoperability

2.1. SYSTEM TYPE COMPATIBILITY

FPR 1.3 FPR 1.3EP1 FPMR 2.1 FPR(HC) 1.4.5 FPMR 2.4 FM200 R1.0 √ × × × × FM200 R1.0EP1 √ √ √ √ × FM200 R2.0 √ √ √ √ √ FM200 R2.0_1.0.0 √ √ √ √ √

2.2. INTEROPERABILITY

A-Serials FPH800 Cisco MWR 2904 Ethernet Services √ √ √ E1/T1 CESoP √ √ √* E1 SAToP × √ × Clock Synchronization √ × × Ethernet OAM √ × × xSTP √ √ √ CES Protection × √ √

* E1 CESoP interworking with Cisco2904 is OK.

3. Hardware Change by This Release

There is no hardware change in this release:

(5)

4. Product Feature set

4.1. Main features till previous release(R2.0)

•

General Features



Extended indoor temperature range (-5 to +55°C)



Extended temperature range (-40 to +55°C) in FOC with pre-heater



Low power consumption



On field MTBF > 100 years



Installation in FlexiOutdoor Case (FOC)



19-inch and 23-inch ETSI rack mounting



-48V DC inputs

•

Interfaces on The Base System



4x 10/100/1000Base-T, supporting Synchronous Ethernet, and two of them support P+E



2 x SFP interfaces, can be configured either as GE or as STM-1 ports



8 x E1/ T1 CESoPSN and SAToP



1 x local management port (out-of-band or OOB), 1 x DCN port



Dry contact port with 2 inputs and 2 outputs



Interface for memory key

•

Ethernet Services



E-Line Service



E-LAN Service



Basic traffic classification rules: port, tagged/untagged, customer VLAN ID, customer

802.1p bits, and customer DSCP bits



Advanced traffic classification rules: source/destination MAC address, EtherType, Inner

VLAN ID, Inner 802.1p bits, Source/Destination IP address, IP protocol,

Source/Destination TCP/UDP port, etc.



VLAN Tag manipulation supports Translation and Transparent mode



Jumbo frame (up to 9600-byte MTU)



Automatic and configurable MAC address aging time



Support for static MAC addresses (not subject to MAC address aging)



MAC address flushing per VLAN

(6)



802.1Q



802.1ad

•

Ethernet QoS



Traffic policing supporting CIR and PIR bandwidth profile



8 priority queues per port



Queue Scheduling: SP, SP+WRR, SP+WDRR



Support for Multi-QoS (i.e., multiple priorities per service)



Traffic Shaping per port and per queue



Congestion management with sRED



Rate limit on broadcast/multicast/unknown traffic per port for E-LAN service

•

Ethernet OAM



End-to-end performance monitoring according to Y.1731



End-to-end fault management according to 802.1ag



End-to-end performance of services per port:



RMON/RMON2



Service (E-Line/E-LAN) Statistics



16 * 15 minutes and 4 * 24 hours period statistics



UNI port shutdown on service failure

•

Protection



1+1 ODU hot-standby on one IDU



xSTP for E-LAN service



Link OAM for xSTP



802.1ad LAG support on UNI ports



1+1 MSP over STM-1 interfaces on the base system

•

TDM Circuit Emulation Service (CES)



E1/T1 CESoPSN



SAToP for E1 and STM-1



E1 cross-connect and grooming to STM-1

•

Clock Synchronization



Differential Clock Recovery



Synchronous Ethernet, supporting SSM

(7)

•

Management and Security



SNMPv3 with encryption, SSH, SFTP

•

ANSI Support



ANSI support (regulatory, T1)

•

Licenses and License Management

The following functions require software license.



From Basic to 6 Interfaces + Hot Stand By



MSTP/RSTP



Ethernet OAM



Security

License Management is via CLicS. See section License Management.

4.2. New Features in release R2.0_1.0.0

•

Ethernet features



Configurable shaping burst size



Configurable buffer allocation

•

Protection



xSTP improvement



CES Linear Protection

•

New Licenses



CES Linear Protection

5. Operation Considerations and Hints

5.1. Operating the System

It is strongly recommended not to frequently plug and unplug the memory key with short interval. This

interval must be at least 1 minute.

Whenever the system is booting up, it takes some time to read the memory key. Please make sure that

the current active software image is up and running for at least 6 minutes before switching to the

backup software image.

5.2. License Management

In previous releases (R1.0 and R1.0 EP1), License Tool, a standalone software application, is used to

create license key. License Tool can be downloaded from NOLS.

Starting from release R2.0, 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

(8)

Please note that the old licenses generated in previous releases can continue to be used in this release.

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.

5.5. 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.6. 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-E-LAN or

E-Line service so that the CES service is established.

WebLCT can be used to create CES service.

5.7. CES TDM Mode Switching

Changing TDM Mode between E1/T1/J1 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.8. 1+1 Hot-Standby ODU Function

When a LPG is created, a dedicated service will also be created for P-CCM between two ODUs.

P-CCM can be enabled via the Bridge configuration and Port Configuration.

5.9. Power-Plus-Ethernet (P+E) Deployment

Important Note: 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 than that provided by the two standards. Thus, it is harmful to connect FM200 P+E interfaces to other devices t han 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 FM200 whether or not the P+E function of FM200 is disabled or enabled.

6. Solved Issues in R2.0_1.1.0 and R2.0_1.0.0

The following issues in the previous release have been solved in this release.

(9)

6.1. Management and WebLCT

 Ref. No.:FR_0000011739 – E1 port name interface is confusable (R2.0_1.1.0) Description: In WebLCT, E1 port name has been redefined

From: To:

TDM 11  E1 0/1 or T1 0/1, TDM 12  E1 0/2 or T1 0/2, TDM 13  E1 0/3 or T1 0/3, etc.

 Ref. No.: FR_0000008657 – Do NOT connect equipment which runs spanning tree protocol with the DCN port (R2.0_1.0.0)

Description: When an equipment which runs spanning tree protocol (STP) on the port connected to FM200 DCN port, the DCN port of FM200 receives STP BPDUs and transfers them to CPU, which will cause recalculation of STP of the S-VLANs and/or the Management VLANand make the network unstable.

7. Solved Issues in R2.0

The following issues in the previous release have been solved in this release.

7.1. System

 Ref. No.:FR_0000003087 – Telnet does not need password

Description: Password is not required when using telnet with FM200.

 Ref. No.:FR_0000003530 – Do NOT plug in and out Memory key frequently

Description: Plugging in and out the memory key frequently causes the system to raise “Wrong Memory Key Type" alarm.

 Ref. No.:FR_0000003549 – R1.0 memory key will cause alarm

Description: Inserting R1.0 memory key in the system will cause "Wrong Memory Key Type" alarm.  Ref. No.:FR_0000003752 – Do NOT power off/on system during its warm restart

Description: Powering off/on the system during its warm restart may cause the system’s flash memory to be defective.

 Ref. No.:FR_0000003850 – Flash memory may become defective in rare cases

Description: In rare cases (1~2%), powering off the system may cause some parts of the flash memory defective, but the system will continue to work.

7.2. E-LAN Service

 Ref. No.:FR_0000003676 – Dynamically learned MAC addresses are not immediately cleared

Description: Dynamically learned MAC addresses are not immediately cleared after the port’s admin status is set “down “.

(10)

 Ref. No.: FR_0000002934 – “Standby ODU RF down" alarm is always sent mistakenly Description: "Standby ODU RF down" alarm is always sent, but should not be sent.

7.4. CES

 Ref. No.:FR_0000003143 – PW “Packet Re-ordering” performance counter increases falsely

Description: Even if CESoP service works normally, PW (pseudo-wire) "Packet Re-ordering" performance counter continues to increase.

 Ref. No.:FR_0000003152 – G.826 performance measurement continues wrongly when E1 Port is administratively down

Description: When E1 Port is administratively down, G.826 performance measurement continues and does not stop.

7.5. Clock Synchronization

 Ref. No.:FR_0000003460 – System’s clock may be “locked” and “clock loop” may be formed

Description: When an Ethernet port of a system is configured as the Synchronous Ethernet master port that is intended to provide clock to the downstream network elements, and it is wrongly configured as the clock source of this system as well, the system’s clock will be “locked” to this master port and “clock loop” will form, in which the system and all the downstream network elements will not be synchronized with the actual clock reference. It is reminded here that in the current release such wrong configuration does not cause alarm.

7.6. Management and WebLCT

 Ref. No.:FR_0000003153 – Port is not highlighted in WebLCT when it is up or down

Description: If a port is up or down, this port should be highlighted in WebLCT in a unique color.

 Ref. No.:FR_0000003899 – A GE port will be removed from the Management VLAN when its port type is changed from UNI to NNI

Description: When a GE port is on the Management VLAN, changing its type from UNI to NNI will make it removed from the Management VLAN. It can be then added to the Management VLAN manually.

 Ref. No.:FR_0000003780 – Bit Error may occur on some of E1 services under certain circumstances when the management plane with loops goes through a few ODUs and E1 CESoP services are established through these ODUs (Corrected in R2.0_1.0.0)

Description: When the management plane with loops goes through a few ODUs and E1 CESoP services are established through these ODUs, errors may occur on some of the E1 services under certain circumstances. If the network topology is stable and there is no change on the management plane, then no errors may arise. An example is shown below. The trigger of the error event is when some changes take place on the management plane, say, the management IP address of IDU is changed and the ARP table of IDUs must be relearned, then error may occur once over the green E1 service.

(11)

Purple: CESoP service 1 Green: CESoP service 2

Red: Management traffic (a loop exists, but is broken by STP)

8. Known Issues or Limitations in R2.0_1.1.0 and R2.0_1.0.0

8.1. E-LAN Service

 Ref. No.:FR_0000011099 – When IP mapping is used, ARP packet will be dropped. (R2.0_1.0.0) Description: When IP mapping is used, ARP is usually run over IP mapped service to get the MAC address of the mapped IP address. The ARP packet will be dropped on the UNI port. So PC can’t ping each other successfully in this scenario.

8.2. CES

 Ref. No.:FR_0000012451 – E1 port counter can not clear after warm rebooting (R2.0_1.1.0)

Description: In E1 port performance, when UAS counter is more than 12 and EB counter is more than 2000, UAS will be 12 and EB will be 2000 after warm rooting..

 Ref. No.:FR_0000012695 – E1 port 8 cannot used as timing source. (R2.0_1.1.0) Description: When E1 port 8 is used as timing source, timing cannot lock.

9. Known Issues or Limitations in R2.0

9.1. System

 Ref. No.:FR_0000002942 – Old FlexiPacket Radio requires no lower than 42.5VDC power input to IDU in order to get powered by P+E port of IDU

Description: When a P+E port of IDU is working under 40.5VDC input and is connected with the old HW Packet Radio (FPR) that requires minimum 32VDC power input, the FPR can’t be powered on. This is a normal behavior. If the IDU DC power input is increased above 42.5VDC, there will be no such problem. The new FPR that supports 28VDC can be powered up by FM200 via P+E port with 40.5VDC input. Supported maximum P+E cable length is:

For old FPR (32VDC), it can be 65m. For new FRP (28VDC), it can be 100m.

 Ref. No.: FR_0000004051 – WebLCT May Lose Communication with The System

FlexiPacket Radio ODU FlexiPacket Radio ODU FirstMile200 FlexiPacket Radio ODU FlexiPacket Radio ODU FirstMile200 E1 E1 E1 E1

(12)

Description: When the speed of the Ethernet interface of the PC running WebLCT is forced (by manual configuration) to 10Mbps, the PC will not be able to communicate with the system.

Solution: Do not manually configure 10Mbps on the network interface of the PC.

 Ref. No.: FR_0000007980 – Back-to-back connected IDU can be powered up by port GE3 or GE4 of the other IDU

Description: When two IDUs are connected together via Ethernet ports, in case one of the ports between the two IDUs is P+E port and P+E function is enabled on one IDU, the other IDU can be powered up unexpectedly by this P+E port.To avoid this issue, the two IDUs can be connected via non-P+E ports or P+E function is disabled.

 Ref. No.: FR_0000009990 – SW file is not able to copy directly between Win7 SP1 and WindowsXP Sometimes directly copying SW file between Windows XP and Win7, the file size may be changed. It will be failed to download the file with changed size to NE.

Workaround: Compress the SW file by winRAR or winZip firstly. Copy this compressed file between winXP and win7 won’t change the file size.

 Ref. No.: FR_0000010021 – The LAG protection on the SFP port needs ALS enabled and the switch time is long.

When SFP ports configure LAG protection, the ALS must to be enabled. Otherwise the protection doesn’t work. The protection switch time will over 500ms, it is because it takes time that ALS Tx shutdowns switch.

9.2. E-LAN Service

 Ref. No.: FR_0000005453 – Rebooting the system shortly after a service is created may cause service “disabled”

Description: Rebooting the system in less than 10 seconds after a service is created or service configuration is changed, the service will become “disabled”. This is because the system has not finished saving the configurations when it is reboot.

Suggestion: Do not reboot the system right away after creating or reconfiguring a service.

 Ref. No.:FR_0000001582 – Actual MAC address aging time exceeds the configured 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.

When the configured aging time is 1000sec, the actual aging time is 1600sec. When the configured aging time is 5000sec, the actual aging time is 9000sec.

 Ref. No.:FR_0000011099 – When IP mapping is used, ARP packet will be dropped.

Description: When IP mapping is used, ARP is usually run over IP mapped service to get the MAC address of the mapped IP address. The ARP packet will be dropped on the UNI port. So PC can’t ping each other successfully in this scenario.

(13)

9.3. QoS

 Ref. No.:FR_0000001740 – WRR scheduling is not always accurate

Description: WRR scheduling is not always accurate when frame MTU is larger than 1000 bytes, in which case, queue 7 and queue8 demonstrate the same weight regardless of the actual weight configured for them.  Ref. No.:FR_0000001741 – DRR scheduling is not always accurate

Description: DRR scheduling is not always accurate – same phenomenon as FR_0000001740.  Ref. No.:FR_0000003490 – The actual DDR weight cannot be odd number

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, 5, operators can use 2, 6, 10.

 Ref. No.:FR_0000004848 – Rate limiting is not accurate

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 Known-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 is disabled and this problem will not appear.

9.4. Protection

 Ref. No.:FR_0000003311 – Temporary loops may exist when system is warm restarting

Description: When the system is warm restarting, temporary loops may exist in the network until xSTP is up and running.

 Ref. No.:FR_0000006640 – Ethernet port performance statistics is lost if LAG on this port is deleted firstly

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.

Solution: Disable the admin status of LAG before deleting it.

9.5. OAM

 Ref. No.:FR_0000006567 – Too short Y.1731 OAM message interval or too many MEPs may induce system’s CPU overwhelmed

Description: System’s CPU may be overwhelmed when too short Y.1731 OAM message interval or too many MEPs are configured.

Suggestion: configure OAM message interval and the number of MEPs according to the following rules:

For CCM,

8 (sec)

.

≤

∑

Interval MEP No

when Interval is at least 1 second. When Interval is 0.1 second, only one MEP can be configured.

(14)

For example, when six (6) MEP of 1-second CCM are configured, additional twenty (20) MEPs of 10-second CCM can be configured as well.

For DM, LM and LBM, minimum OAM message interval is one (1) second, and can be applied to no more than eight (8) services.

FM200 supports the following scalability numbers:

• Total of 64 MDs

• Total of 256 MAs

• Total of 256 MEPs

• Total of 256 RMEPs, and each MEP has up to 16 RMEP

• All MEP can be allocated to a single MA, and all MAs can be a llocated to a single MD  Ref. No.:FR_0000007938 – Spanning Tree enabling/disabling sometimes causes E-CCM loss

Description: E-CCM is the continuity check message between IDU and ODUs to detect the status of the ODUs working in 1+1 hot-standby mode. E-CCM is generated by the CPU of the system. As the operation of enabling or disabling xSTP may make CPU very busy, E-CCM could get lost for a short period of time, which will force the active and standby ODU to switch their roles, and switch again when xSTP gets converged.

 Ref. No.:FR_0000008853 – Loss Measurement and Service Statistics can’t be enabled at the same time

Description: Loss Measurement and Service Statistics can’t be enabled at the same time. Enabling one of them will stop the other automatically. This is because that they are using the same counters and enabling one function will clear the counters, making the counter values inaccurate for the other function.

 Ref. No.: FR_0000008687 – Service PM disable/enable will cause packet dropping

Description: When service performance measure (PM) is disabled or enabled, there will be a loss of few packets. This is because enabling/disabling service PM will cause the switch chip to re-apply the mapping rules.

9.6. CES

 Ref. No.:FR_0000002938 – Bit error is caused by plugging/unplugging E1 cable

Description: When loopback is configured on a remote E1 port, plugging and then unplugging E1 cable at the E1 port causes bit errors.

 Ref. No.:FR_0000004032 – SSRC range doesn’t fully comply with the standard CESoPSN and SAToP 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.

9.7. Clock Synchronization

 Ref. No.:FR_0000003303 – There is no SSM packet when no external timing source is configured Description: There is no SSM packet when no external timing source is configured.

(15)

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 effect 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_0000003603 – The synchronization state is locked while both 2 clock sources are in WTR Description: When both of the two clock sources are in Wait-to-Restore (WTR) state, the system clock still locks to one of them (the right behavior is that the system should get in hold-over or free-run mode).

 Ref. No.:FR_000004520 – Switching the 2 timing sources keeps the synchronization state in free-run for a while

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 switch which usually takes about 1 minute.  Ref. No.:FR_000005165 – Inserting AIS to line clock does not unlock the timing source

Description: When clock source is Line Clock, inserting AIS to the E1/T1/J1 line that is used as clock

source, the clock is still locked. The right behavior should be that the timing source should be unlocked, and the system enters hold-over, and then selects the backup clock.

 Ref. No.:FR_000006917 – SFP port with electrical SFP cannot be used as timing source

Description: when the SFP port of the system is configured as GE port and electrical SFP is inserted in this port, it cannot be used as Synchronous Ethernet clock source.

9.8. Management and WebLCT

 Ref. No.:FR_0000006652 –WebLCT runs slowly when OAM message interval is set to 100ms for two or more services

Description: WebLCT runs slowly when OAM message interval is set to 100ms for two or more services. WebLCT screen may freeze for a long time (up to 10’s of seconds) before displaying any contents.

 Ref. No.:FR_000003930 – too many MAC addresses will by displayed on WebLCT very slowly

Description: when the system learns a large number of MAC addresses, it may take a few to tens of seconds for WebLCT to display all the MAC addresses.

 Ref. No.: FR_0000005994 – Menu item Statistics -> SLA does not work if “Service Performance Measurement” 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_000009179 – LPG Admin and Operation status disappear after NE is upgraded from R1.0EP1 to R2.0

Description: When the LPG is configured in R1.0 EP1 with Admin status “enable” and Operation status “up”, the Admin status and Operation status disappear after the NE is updated to R2.0. The traffic is not impacted and the LPG remains unchanged. The abnormal status can be e liminated after removing and re-configuring the LPG in R2.0.

(16)

10. Solved Issues until R1.0 EP1

The following issues listed in Release 1.0 EP1 Notes have been resolved:  Ref. No.: FR_0000002789

Description: When LOF is inserted at local E1 port, the remote E1 port reports "PW Down" alarm and the service is interrupted in both directions. This issue has been resolved in this release. When LOF is inserted at local E1 port, the remote E1 port reports AIS alarm and traffic from the remote E1 to the local E1 port remains normal.

 Ref. No.: FR_0000002829

Description: The "admin status" of a GE port is "Down", but it reports "SFP LOS" alarm.  Ref. No.: FR_0000002895

Description: Radio Link Down alarm is not shown on WebLCT.  Ref. No.: FR_0000002896

Description: When the system has multiple alarms, its "system status" in WebLCT does not reflect the most severe alarm. In this release, the “system status” in WebLCT is now synchronized with the most sever alarm.  Ref. No.:FR_0000002786

Description: After missing SSM packet for 5 seconds, FM200 remains in "lock" status instead of getting into hold-over status.

 Ref. No.:FR_0000002809

Description: When an Ethernet port is configured to be timing source, its port speed and mode are forced to be 1000Mbps and full-duplex. In this release, the port mode and speed will not be changed when configured as timing source.

 Ref. No.:FR_0000002827

Description: When an Ethernet port is configured to be timing source, its “admin status” is forced to be up. In this release, the port’s admin status will not be changed when configured as timing source.

11. Known Issues in R1.0 EP1

11.1. System

 Ref. No.:FR_0000003087 - Telnet does not need password Description: password is not required when telnet the equipment.

 Ref. No.:FR_0000003530 – Do NOT plug in and out Memory key frequently

Description: Plugging in and out the memory key frequently causes the system to raise “Wrong Memory Key Type" alarm.

 Ref. No.:FR_0000003549 – R1.0 memory key causes alarm

Description: Inserting R1.0 memory key in the system will cause "Wrong Memory Key Type" alarm.  Ref. No.:FR_0000003752 – Do NOT power off/on system during its warm restart

(17)

Description: Powering off/on the system during its warm restart may cause the system’s flash memory to be defective.

 Ref. No.:FR_0000003850 – Flash memory may become defective in rare cases

Description: In rare cases (1~2%), powering off the system may cause some parts of the flash memory defective, but the system will continue to work.

 Ref. No.:FR_0000002942 – Powering up old FlexiPacket Radio via P+E port of IDU requires at least 42.5 VDC input to IDU

Description: When a P+E port of IDU is working under 40.5VDC input and is connected with the old HW Packet Radio (FPR), the FPR can’t be powered on. This is a normal behavior. If the IDU DC power input is increased above 42.5VDC, there will be no such problem.

Supported maximum P+E cable length is: For old FPR, it can be 65m.

For new FRP, it can be 100m.

11.2. E-LAN Service

 Ref. No.:FR_0000003676 – Dynamically learned MAC addresses are not immediately cleared

Description: Dynamically learned MAC addresses are not immediately cleared after the port’s admin status is set “down “.

 Ref. No.:FR_0000001582 – Actual MAC address aging time exceeds the configured 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.

When the configured aging time is 1000sec, the actual aging time is 1600sec. When the configured aging time is 5000sec, the actual aging time is 9000sec.

11.3. QoS

 Ref. No.:FR_0000001740 – WRR scheduling is not always accurate

Description: WRR scheduling is not always accurate when frame MTU is larger than 1000 bytes, in which case, queue 7 and queue8 demonstrate the same weight regardless of the actual weight configured for them.  Ref. No.:FR_0000001741 – DRR scheduling is not always accurate

Description: DRR scheduling is not always accurate – same phenomenon as FR_0000001740.  Ref. No.:FR_0000003490 – The actual DDR weight cannot be odd number

Description: When DRR weight is configured with an odd number, the system will set the actual value as odd +1.

11.4. Protection

 Ref. No.: FR_0000002934 – “Standby ODU RF down" alarm is always sent mistakenly Description: "Standby ODU RF down" alarm is always sent, but should not be sent.

 Ref. No.:FR_0000003311 – Temporary loops may exist when system is warm restarting

Description: When the system is warm restarting, temporary loops may exist in the network until xSTP is up and running.

(18)

11.5. CES

 Ref. No.:FR_0000002938 – Bit error was caused by plugging/unplugging E1 cable in certain cases Description: When loopback is configured on a remote E1 port, plugging and then unplugging E1 cable at the E1 port causes bit errors.

 Ref. No.:FR_0000003143 – “Packet Re-ordering” performance counter increases falsely

Description: Even if CESoP service works normally, PW "Packet Re-ordering" performance counter continues to increase.

 Ref. No.:FR_0000003152 – G.826 performance measurement continues wrongly When E1 Port is administratively down

Description: When E1 Port is administratively down, G.826 performance measurement continues and does not stop.

11.6. Clock Synchronization

 Ref. No.:FR_0000003303 – There is no SSM packet when no external timing source is configured Description: There is no SSM packet when no external timing source is configured.

 Ref. No.:FR_0000003460 – System’s clock may be “locked” and “clock loop” may be formed

Description: When an Ethernet port of a system is configured as the Synchronous Ethernet master port that is intended to provide clock to the downstream network elements, and it is wrongly configured as the clock source of this system as well, the system’s clock will be “locked” to this master port and “clock loop” will form, in which the system and all the downstream network elements will not be synchronized with the actual clock reference. It is reminded here that in the current release such wrong configuration does not cause alarm.

 Ref. No.:FR_0000003607 – System is in holdover status when a failed timing source is added

Description: When a failed clock source is added to a system whose clock is in free-run status, the system’s clock is changed to holdover status. According to Synchronous Ethernet standard, its status should be free-run. This issue has no practical effect on normal operation, because the system is holding over its clock onto its own free-run clock, i.e., same as in free-run status.

 Ref. No.:FR_0000003603 – The synchronization state is locked while both 2 clock sources are in WTR Description: When both the two clock sources are in Wait-to-Restore (WTR) state, the system clock still locks to one of them (the right behavior is that the system should get in hold-over or free-run mode).

11.7. Management and WebLCT

 Ref. No.:FR_0000003153 – Port is not highlighted in WebLCT when it is up or down

Description: If a port is up or down, this port should be highlighted in WebLCT in a unique color.

 Ref. No.:FR_0000003899 – A GE port will be removed from the Management VLAN in case it is changed from UNI to NNI

(19)

Description: When a GE port is on the Management VLAN, changing it from UNI to NNI will make it removed from the Management VLAN. It can be then added to the Management VLAN manually.

12. Documentations



FlexiPacket FirstMile 200 Product Description

(20)

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.