IP-10 I6 3 2 Release Notes - Ver 2 9 26

8/12/2019 IP-10 I6 3 2 Release Notes - Ver 2 9 26

1/25

FibeAir IP-10 (R1)

High Capacity IP Wireless NetworkSolution

IDU SoftwareI6.3.2

Release Notes

Including:

IDU Version (Package): 2.9.26

June 2011


2/25

IP-10 (R1) Software Release Notes Version 2.9.262

PROPRIETARY

Contents

1. Document Control 3

2. Introduction 4

3. Supported Systems and Configurations 6

4. SW/HW Configurations and Compatibility 8

5. NSV Content 11

6. New Features 12

7. Modified Features 13

8. Limitations/Features not Supported 14

9. Corrected Bugs 19

10. Open Bugs 20


3/25


PROPRIETARY

1. Document Control

Ceragon Networks Ltd.

Project: IP-10, I6.3.2 release.

Document Name: IP-10 High Capacity IP Wireless Network Solution Release

Publication History

Release Revision Date Author Notes

2.9.26 Rev 0.1 19/June/2011 Oded Navi Internal Review

2.9.26 Rev 0.2 21/June/2011 Oded Navi Distribution


4/25


PROPRIETARY

2. Introduction

2.1. Project Release History

IP-10 R1 product line release history:

# NSV SW

Package

Version &

Date

Main Features

1. 1.4.5 Aug 2008 IP-10 R1 I6.0 - product introduction2. 1.5.4 Jan 2009 IP-10 R1 product release I6.0.13. 2.7.10 Mar 2009 IP-10 R1 product release I6.14. 2.7.12 Apr 2009 IP-10 R1 product release I6.1.15. 2.8.25.0 Aug 2009 IP-10 R1 product release I6.26. 2.8.31.0 Dec 2009 IP-10 R1 product release I6.2.37. 2.8.32.0 Feb 2010 IP-10 R1 product release I6.2.58. 2.8.33.0 Apr 2010 IP-10 R1 product release I6.2.69. 2.9.6 Sep 2010 IP-10 R1 product release I6.310. 2.9.9 Apr 2011 IP-10 R1 product release I6.3.111. 2.9.26 June 2011 IP-19 R1 product release I6.3.2


5/25


PROPRIETARY

2.2. Synonyms & Acronyms

AIS Alarm Indication SignalACM Adaptive Coding and ModulationAES Advanced Encryption StandardBER Bit Error RateBPDU Bridge Protocol Data UnitCA Certificate AuthorityCFM Connectivity Fault Management (Protocol)CN Customer Network (Port)DST Daylight Saving TimeEFM Ethernet in the First Mile (Protocol)EOW Engineering Order WireEXC BER Excessive BERFD Frequency Diversity

FE Fast EthernetFTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)GbE / GBE Gigabit EthernetGMT Greenwich mean timeIDC In Door ControllerIFG / IPG Inter Frame/Packet GapHTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)LAG Link Aggregation GroupLOC Loss Of CarrierLOF Loss Of FrameLOS Loss Of SignalLTM Link-Trace Message (CFM)LTR Link-Trace Response (CFM)MA Maintenance Association (CFM)

MAC (Ethernet) Media Access ControlMAC (Security) Message Authentication CodeMAID Maintenance Association (MA) Identifier (ID)MEP Maintenance End Point (CFM)MHC MAC Header CompressionMIB Management Information BaseMIP Management Intermediate Point (CFM)MRMC Multi Rate Multi ConstellationMSE Minimum Square ErrorNTP Network Time ProtocolNSV New Software VersionOAM Operation Administration & Maintenance (Protocols)PIRL Port Ingress Rate LimitingPM Performance Monitoring

PN Provider Network (Port)PV PolyViewQoS Quality of ServiceRSL Received Signal LevelSD Space DiversityS/N Serial NumberSNMP Simple Network Management ProtocolSNTP Simple Network Time ProtocolSTP / xSTP Spanning Tree ProtocolSSH Secured Shell (Protocol)UC User ChannelUTC Universal Time CoordinatedWSC Wayside ChannelXPIC Cross Polarization Interference Cancellation


6/25


PROPRIETARY

3. Supported Systems and Configurations

3.1. Supported Systems

Supported system MRMC (Multi-Rate-Multi-Constellation) configurations (determinedby modem configuration scripts):

*Two ACM-28M scripts appear in the MRMC table. The first script that appearsin line 12 in the list above, is the ACM radio script for channel spacing of 28MHz

that was released in previous IP-10 6.1.x, 6.2.x, for backward compatibility. The

second ACM radio script that appears in line 13, is an enhanced capacity and

latency script for channel spacing of 28MHz.

# Modem Script Bit Rate

[Mbps]

Channel Spacing

(Occupied BW)

[MHz]

ETSI/FCC Modulation

1. 1528 155 28 (26) ETSI 128QAM

2. 0107 10 7 (6.5) ETSI QPSK

3. 0407 39 7 (6.5) ETSI 256QAM

4. 0207 20 7 (6.5) ETSI 16QAM

5. 4410 47 10 (9) FCC 64QAM

6. 0428 38 28 (26) ETSI QPSK

7. 1828 181 28 (26) ETSI 256QAM

8. ACM-7M 10 - 42 7 (6.5) ETSI QPSK256QAM

9. ACM-10M 13 - 61 10 (9) FCC QPSK256QAM10. ACM-14M 21 - 87 14 (12.5) ETSI QPSK256QAM

11. ACM-20M 28 - 124 20 (18) FCC QPSK256QAM

12. ACM-28M * 38 - 181 28 (26) ETSI QPSK256QAM

13. ACM-28M * 39 - 185 28 (27) ETSI QPSK256QAM

14. ACM-30M 39 - 198 30 (28) FCC QPSK256QAM

15. ACM-40M 56 - 255 40 (36) ETSI/FCC QPSK256QAM

16. ACM-50M 67 - 337 50 (47) FCC QPSK256QAM

17. ACM-56M 76 - 367 56 (52) ETSI/FCC QPSK256QAM


7/25


PROPRIETARY

3.2. Supported Radio Configurations

# Configuration Supported

[Yes/No]

Notes

1. RFU support Yes 1500P/HP/SP, RFU-C

2. 1+0 Yes

3. 1+1 HSBExternal Protection Yes

4. 1+1 space diversity (SD) Yes With RFU-HP

5. ACM Yes

3.3. Channel Separationto MRMCtranslation Table

ChannelSeparation

(MHz)

ETSI/FCC

MRMC Script Name ACM Bit Rate(Mbps)

OccupiedBW (MHz)

Modulation(QAM)

7 ETSI 10Mbps-6.5MHz-QPSK-Grade-1 No 10 6.5 QPSK20Mbps-6.5MHz-16QAM-Grade-1 No 20 6.5 1639Mbps-6.5MHz-256QAM-Grade-1 No 39 6.5 256ACM-42Mbps-6.5MHz-256QAM-Grade-1 Yes 10 - 42 6.5 QPSK - 256

10 FCC 47Mbps-9MHz-64QAM-Grade-1 No 47 9 64ACM-61Mbps-9MHz-256QAM-Grade-1 Yes 13 - 61 9 QPSK - 256

13.75 , 14 ,14.5 , 15

ETSI ACM-87Mbps-12.5MHz-256QAM-Grade-1 Yes 21 - 87 12.5 QPSK - 256

20 FCC ACM-124Mbps-18MHz-256QAM-Grade-1 No 28 - 124 18 QPSK - 25627.5 , 28 ,29 , 29.65 ,

30

ETSI 38Mbps-26MHz-QPSK-Grade-1 No 38 26 QPSK155Mbps-26MHz-128QAM-Grade-1 No 155 26 128181Mbps-26MHz-256QAM-Grade-1 No 181 26 256ACM-181Mbps-26MHz-256QAM-Grade-1 Yes 38 - 181 26 QPSK - 256ACM-185Mbps-27MHz-256QAM-Grade-1 Yes 39 - 185 27 QPSK - 256

30 FCC ACM-198Mbps-28MHz-256QAM-Grade-1 Yes 39 - 198 28 QPSK - 25640 ETSI /

FCCACM-255Mbps-36MHz-256QAM-Grade-1 Yes 56 - 255 36 QPSK - 256

50 FCC ACM-337Mbps-47MHz-256QAM-Grade-1 Yes 67 - 337 47 QPSK - 25656 ETSI /

FCCACM-367Mbps-52MHz-256QAM-Grade-1 Yes 76 - 367 52 QPSK - 256


8/25


9/25


PROPRIETARY

(*) 1500P ODUs support for 7MHz scripts should be checked with CeragonSupport based on ODUs P/N

(**) 1500HP, 1500SP & RFU-HS support scripts up to 30.5MHz occupiedbandwidth

(***) 1500SP Wide support scripts with occupied bandwidth (24MHz BW 56MHz)

4.4. HW Compatibility in a Link

IDU compatibility for 256QAM

Operation in 256QAM modulation scripts depends on IDU HWrevision when connected to RFU-C RFUs (no limitation whenconnected to other ODU/RFU types). In general, IP-10 IDUswith Part Number revision of 09-Axxx-6 or lower do not support256QAM. IDUs with P/N of 09-Axxx-7 or above support256QAM scripts.

RFU-C compatibility for 256QAM

Operation in 256QAM modulation scripts depends on RFU-CHW revision and limitations may be applied. Contact Ceragon

support for confirmation and upgrade steps for RFU-C PartNumber confirmation.

ACM-56MHz: RFU-C should have version 1.97 (or higher) forproper functionality of this script.

RFU-C compatibility for Adaptive TX Power

RFU-C should have version 2.01(or higher) for properfunctionality of Adaptive TX Power feature. If lower RFU-CSW version is used, this feature should be disabled.

IDU compatibility in a Link

IP-10 IDU should work with IP-10 IDU across the link.

No compatibility with 1500P IP-MAX/IP-MAX2 IDUs.

ODU/RFU compatibility in a Link

According to ODU/RFU release


10/25


PROPRIETARY

4.5. SW Compatibility and Upgrade Limitation

This release can be downloaded to any IP-10 IDU.

IP-10 R1 releases compatibility

IP-10 IDU release I6.2.x or above is compatible with all previous IP-10 R1releases across the link. It is highly recommended to have the same SWversion on both ends of the link.

In protection 1+1 (Hot Standby), it is mandatory to have the same SW versionat Local & Mate units (at the same link end).


11/25


PROPRIETARY

5. NSV Content

IP-10 IDU SW version is released as zipped RPM package (RPM, Red Hat PackageManager, is the software packagefile format in Linux).

ODU/RFU versions are separated from the IDU RPM.

The NSV package includes the following components:

Package Name New Version

aidu 2.9.26aidu-idc 2.9.26aidu-management 2.8.52aidu-modem-fw 3.3.18aidu-fpga-fw 7.209aidu-mrmc-scripts 2.44L2protocols 7.5.1.aidc.t139.1.6kernel 2.6.14.7-aidc.2.1kernel-modules 0.2.1-2.6.14.7_aidc.2.1aidu-setup 2.4.3aidu-atp

2.3

MIB version: 6.7.0.45.2(CERAGON-MIB_6.7.0.45.2.mib)
http://en.wikipedia.org/wiki/File_formathttp://en.wikipedia.org/wiki/File_format


12/25


PROPRIETARY

6. New Features

The new features are relative to the previous GA IP-10 R1 version IP-10 6.3.1 (SWversion).

# Feature Description/Notes

1.Ethernet Services Support Ethernet services is NMS feature, allowing the user to use the PolyView

NMS to provision end-to-end Ethernet services over the network.

Note: It is essential to verify whether the used PolyView NMS version

supports IP-10 (R1) platform.

2.Blocking management towards line Available only in Single Pipe applications.

This feature is required by carrier of carrier customers that provide

Ethernet leased lines to a third party user. The 3rd party user connects

his equipment to the Ethernet interface of the IP-10, while all the other

network interfaces, particularly the radios are managed by the carrier

of carrier user.

In that case, management frames that are sent throughout the network

to manage the carrier of carrier equipment must not egress the line

interfaces that are used by the 3rd party customer since these frames

are spamming the 3rd partysuser network.

This capability can be enabled or disabled, and by default is disabled.

This feature is available via the private MIB.


13/25


PROPRIETARY

7. Modified Features

# Feature Description/Notes

1.Minimum ACM profile Added MIB support

2.MSE PM calculation This feature is modified to support R1 HW that initially did not support MSE PM

calculation.

3.Ethernet Interfaces Speed& Duplex

values display to the user.

This feature is modified to display only the Ethernet interfaces speed &

duplex operational state as follows:

1. When auto-negotiation is OFF: the speed & duplex operational statethat will be displayed are the ones set by the configuration of the user.

2. When auto-negotiation is ON: the speed & duplex operational state

that will be displayed are the ones that are resolved by the auto-negotiation mechanism.


14/25


PROPRIETARY

8. Limitations / Features not Supported

# Subject Limitation Description/Notes

1. ACM Minimum ACM profile & MaximumACM profile configurations.

User must configure the Minimum ACM profileaswell as the Maximum ACM profileto be identical inboth link sides, in order to get the requiredperformance end to end.

2. ACM Minimum ACM profile The only MRMC scripts that currently support thisfeature are the following ones:FCC-10M: ACM-61Mbps-9MHz-256QAM-Grade-1

FCC-30M: ACM-198Mbps-28MHz-256QAM-Grade-1

FCC-40M: ACM-255Mbps-36MHz-256QAM-Grade-1

3. Ethernet Auto negotiation / speed & duplex This configuration must be similar on the IP-10 andthe device connected to it (the default is 1000 full

on the optical interface and auto-negotiation on" on10/100 or 10/100/1000 interfaces)

4. Ethernet Ethernet ports cross-over System does NOT support automatic Ethernet cross-over (commonly called Automatic MDI/MDIX). Thefollowing cables should be used when "auto-negotiation" is issued on both sides of the Ethernetlink:

1. IP-10 port to IP-10 portcross cable2. IP-10 port to external switch portcross

cable3. IP-10 port to external HUBstraight cable4. IP-10 port to PCcross cable.

5. RFU 1500P 11GHz ODU Separate ODU SW version (O5.52g) different from allother 1500P ODUs (O5.52f)

6. CLI (CQ08720/20087)Serial connection and Telnet

Serial connection and Telnet is supported with VT100protocol.

7. Protection (CQ15547)GbE Copper (10/100/1000) port inprotection.

This port can be split with Y splitter (or patch panel)in protection, only if configured to Autoneg OFF,100 Full.Note: Splitting this port is not recommended. Whenstandby unit is powered down and up again, Activetraffic may be affected.

8. Protection Ethernet ports in Protection Electrical (Copper) Ethernet ports' (10/100 or10/1000/1000) LOC will not serve as protectionswitchover triggers.

9. WEB (CQ20683)WEB browser

Recommended to use Internet Explorer 7.0, 8.0 orMozilla Firefox 3.0. 3.5, 3.6.

10. WEB (CQ12684)When using Mozilla Firefox WEBbrowser, F5 function does not issuea refresh as it is issued when usingInternet Explorer WEB browser.

11. WSC TDM capacity due to Wide WSCconfiguration.

When activating WSC Wide, it consumes2.048Mbps of the radio BW.

12. ConfigurationDownload

(CQ14545)Configuration file has no unique name

Downloaded configuration files from different IDUsshould be saved in separated folders.

13. CLI (CQ12929)Procomm SW definitions:

"Procomm" screen for IP-10 should be 80x24, whiledefault is 80x25

14. CLI In CLI, Yes/No confirmation Yes/No confirmation requires typing "yes" or "no"(and not 'Y' or 'N'). Any other text than yes will beconsidered no.


15/25


PROPRIETARY

15. Automatic StatePropagation

(CQ11348)Single pipe application: Automatic

State Propagation (previously calledGbE Tx-mute): Local LOC isenabled.

LOC on local Electrical GbE (10/100/1000) willNEVER cause "shut-down" or "Tx-Mute" on remote

end. This behavior avoids dead-lock:If remote end is shut-down due Local-LOC,and nowremote cable is disconnected, then local port will beshut-down, and Ethernet link will never be able torecover.

16. Ethernet (CQ10564)MAC Learning capability

Switch is capable of learning up to 8K (8192)randomMAC addresses.

17. T1 (CQ 18154)T1 line code.T1 line code should be configured tobe the same (AMI or B8ZS) on bothends of the link. If the line coding isnot the same on both ends, errorsmight appear without raising anyalarm.

User should configure the same T1 line coding onboth ends of the link.

18. Ethernet (CQ10425)Packets with SA of Broadcast(MAC=FF-FF-FF-FF-FF-FF) orMulticast (MAC bit [40] is set) will beforwarded.

19. Ethernet (CQ10479)System does not discard frames withDA of 00:00:00:00:00:00

20. Ethernet (CQ15343)When a VLAN, which is attached to aport, is deleted, no warning messageappears.

21. CFM (CQ17682)CFM protocol uses several entries of

the Forwarding table - when the tableis loaded with 8k MAC addresses(static or dynamic MAC addresses)CFM capability may be limited

22. CFM (CQ16708 / 17903)It is highly recommended by 802.1agstandard to loopback remote unitbefore activating Link-Trace.

23. CFM (CQ17189)It is highly recommended to loopbackprotection 1+1 IDUs by MEP ID andnot by MAC address.

When a switchover occurs, the new active IDUintroduces different MAC address to the network. Aloopback which was initially addressed to the oldactive IDU (which is now the new standby IDU) willnot be reachable.

24. CFM See detailed limitations list under CFM

section.25. Security - SFTP (CQ15340 / 155361)

When setting up SFTP connection, fordownload/upload files operations (e.g.software download, configuration file,download a certificate file, etc.), theIDU (client side) wont authenticate theSFTP server based on server's publickey.

26. Security - SFTP (CQ155362)SFTP server authenticates user basedon user name and password.Public Key authentication of thetarget IDU is not supported(authentication method that do notrequire password).


16/25


PROPRIETARY

27. Security (CQ155363)Upload/download file from/to the IDU

requires the following parameters: hostIP, host-path, user name, andpassword. Additional parameters arerequired for IDU digital certificate, orCA certificate: file-name, security filetype and security file format. Due tothe fact that the IDU can be managedsimultaneously by a few connections,some conflicts may appear:

1. One connection configuresthe parameters for onepurpose and anotherconnection configures themfor another purpose. The"apply" command of both

connections will probably befailed.

2. One connection (C1) startsan operation(upload/download) andanother connection (C2)changes parameters relatedto the first connectionoperation. C1 operation mightfail without any alarm ornotification.

28. Security (CQ158261)web-protocol parameter, fordetermining the web protocol

(http/https), won't be copied to matesystem in protection mode, due to thefollowing facts:a. Applying https protocol requiresthe installation of a digital certificate.IDU digital certificate is unique per IDU(based on IDU key pairs). If the digitalcertificate is not installed, theparameter's set will be failed.b. Security considerations: Eliminatethe option to override securitydefinitions from one unit (with lowersecurity privileges) to another one(with higher security privileges).

29. SecurityCA

Certificate

(CQ158262)

Due the fact that there are some WEBbrowsers (e.g. Mozilla Firefox) thatrequire WEB servers CA certificate (inaddition to IDU certificate), newconfiguration is required to enable thisoption (see details under HTTPSsection).web-ca-certificate-admin parametershould be set to enable (the default isdisable) this option. When this optionis enabled, CA certificate file shouldalready be installed and valid in theIDU. This parameter will not be copiedto mate when activating copy to

mate.


17/25


PROPRIETARY

30. Management (CQ10994 / 11727)Management VLAN setting in Inband

and Protection.See further details under"management configuration" section.

When the system is configured to In-bandmanagement, the management VLAN needs to be

first configured in the remote Standby unit. Seefurther information under "Product and FeaturesDescription" and "External Protection" sections.

31. Management (CQ8139)In-band management disruptions withtraffic max throughput whenManagement VLAN is not at highestpriority.

Set Management VLAN at highest priority

32. Management (CQ11003 / 12878)When managing 1+1 units (Active &Standby) via external switch, whenpowering off Active unit, or when aswitchover is initiated, units might notbe reachable for ~5 minutes.

This only happens in Active power off, and can beresolved by the following:1. Disable learning feature of the external switch (oruse hub).2. Reduce external switch "aging time".3. Issue "flush dynamic entries" in external switch,after switchover.4. Issue "arp" in PC after switchover.

33. WSC (CQ11827)WSC capacity

Wide WSC capacity should not exceed 1.9Mbps.Frames above this limitation are taken care as "besteffort" and may be discarded.

34. Ethernet Ethernet maximum (100%) throughput. Packet loss when using 100% throughput. This is atheoretical case in a laboratory when there is adifference in the clock source of the testingequipment and the IDU (up to 100 ppm).When the throughput is at 99.99% - there is nopacket loss.

35. Ethernet (CQ10376)Packets with VID=0

Packets with VID=0 are considered un-tagged andpass through access ports.

36. Ethernet (CQ13017)Frames tagged with VID=4091

In single-pipe application, 4091 tag is removed, andthe frame will egress untagged at remote end.User should avoid using VLAN 4091.

37. Protection (CQ16813)When upgrading SW version inprotection, both IDUs (local & mate)should be upgraded to have the sameSW version.

38. WEB/Security

(CQ15165)Internet Explorer should beconfigured to Medium-High or Lowsecurity level when interfacing WEBapplication.In case it is not possible, WEB

browser should have the element IP inthe trusted IPs table.39. WEB/

Security(CQ24328)Special characters (!@#$%^...) cannotbe used in password through the WEBinterface.

Only the following characters should be used forpassword:a..z, A..Z, 0..9

40. PM (CQ16770)Ethernet frame error rate PMresolution is 1%. 0% means less than1% error rate.

41. ATPC (CQ13228)When enabling (or disabling) ATPC toremote by using local-remotechannel, only the remote units ATPCis enabled (or disabled) - Just setting

one end does not automatically set theother.

For proper ATPC functionality, both linksendsshould be enabled (or disabled). Local ATPC shouldbe enabled (or disabled) as well.


18/25


PROPRIETARY

42. Protection (CQ15623)On Standby unit, interface Ethernet #2

(Copper- GbE 10/100/1000) will notraise the alarm Ethernet Loss ofcarrier if its cable is disconnected.This port is shutdown on Standby unit.

43. Protection (CQ15624)Protection Lockout and ProtectionForce Switch do not persist after coldreset.


19/25


PROPRIETARY

9. Corrected Bugs

None


20/25


PROPRIETARY

10. Open Bugs

# Subject Description Workaround

1. WEB Cable disconnection during RFU upload willdisplay the download as if it were continuing.

Another upload will solve this issue.

2. WEB Create unit configuration via WEB processtakes 3.5 minutes, and connection to web islost.

Re-open web window.

3. WEB (CQ 15189)After upgrading SW version, WEB does notrespond correctly.

Close WEB browser and reopen it.

4. WEB (CQ 15653)

When upgrading or downgrading SW, MainView page might display the older MainView.

Delete Internet Temp Files (ClearCache/Cookie) in the WEB browser, andreopen the Main View Page.

5. WEB (CQ16436/15845/15845/15957/18202/18202/19523/19574)WEB response issues:

1. Refreshing browser page by pressingF5 returns unexplained error.

2. Invalid text appears in the WEBbrowser.

3. Unitstree does not appear at the leftside of the page.

4. "Cannot open the Internet site" errormessage appears.

Close and then reopen WEB, or Refresh byCtrl+F5 and re-login.

6. WEB (CQ19509/19813/20001/20005)WEB browser window size issues, that mightappear when window size < 100%:

1. Might not be possible to create archiveconfiguration.

2. Might not be possible create archiveunit-info.

3. Gibberish on the window.4. Improper appearance of tables.

These WEB issues are related to the WEBbrowser. User should use only window size of100%.

7. E1/T1 (CQ10151)When E1/T1 port disabled, port-current-ber =1e-10

This is the BER that the TDM port reflectswhen the port is disabled, as there is no BERcalculation.

8. Ethernet (CQ11025)MAC entry in 'forwarding table' is flushed

averagely within 260 (4.3 min) to 300 seconds(5 min) of the ageing time.

9. Ethernet (CQ11840)Whenever Auto-negotiation is being changed,PHY power is being set to default which is UP.

10. Ethernet (CQ16586 / 21192)The following bridge related free text stringsshould not contain any spaces:

1. VLAN Name2. Policer Name3. Class-map Name4. Association Name5. Domain Name

Avoid using characters. Thecharacter _ (underscore) can be usedinstead.

11. Ethernet-

RMON

(CQ9497 / 10035)

RMON 1024 Octets/In FCS errors counters

These counter also increment on oversize

packets


21/25


PROPRIETARY

12. Ethernet-RMON

(CQ11863)RMON counters at "standby" unit display

unclear values, due to the fact that Ethernetports at "standby" unit are blocked.

RMON counters at the "Active" unit are therelevant ones.

13. Ethernet-RMON

(CQ10729)RMON counters in radio excessive BER

In "Excessive BER" scenario (BER~1e-5)RMON counters might count frames withdifferent lengths, which are also counted as"FCS frames received".

14. Ethernet-RMON

(CQ13077) (limitation)RMON Bad octets received counts only 1632bad octets even when ingress frame length isabove 1632 bytes.

15. Ethernet-CFM

(CQ 18203)While working with CFM, in case an RDI or LDIis raised, a general Ethernet Service Failurealarm is raised. Once the alarm is raised, if

user removes all the MAIDs configurationsfrom the unit, the Alarm might stay as raised.

In order to avoid this user should delete theMAIDs one by one (avoid deletion of a groupof MAIDs).

If a group of MAIDs is removed at once, andEthernet Service Failure alarm is raised, acold reset will remove it when system is up.

16. Protection Excessive BER in Protection When there is excessive BER for less thanone second, the system will not initiate aprotection switch.

17. Protection (CQ10767)Protection switchover due to protection cabledisconnection.

Protection cable disconnection might trigger,in a very low probability, a protection switch.To resolve this, first power off the one IDUand then disconnect protection cable.

18. Protection (CQ12300)Additional unnecessary protection switchoversin 'Protection' with Optical interface enabled,but without SFP in cage.

Insert SFP in cage prior to enablingprotection.

19. Protection (CQ12259)Protection cold reset switch reason

Protection switch due to a cold resetcommand will be described as a manualswitch in the alarm log.

20. Protection Configuration during "Copy-2-mate" and/orMRMC change (radio script change)

The user should refrain from changingconfiguration during these two processes.

21. Protection (CQ12563)Frequency setting in protection.

Prior to setting frequencies on local andremote sides, enforce lockout to insureaction.

22. Protection (CQ13622)Simultaneous cold reset to both active andstandby units (e.g. site power down) causesseveral consecutive protection switches.

Traffic goes back to normal after theprotection switches. Intentionally cold reset,should be done 1st to the Standby unit, waituntil it is up and running, and then to the

Active unit.

23. Protection (CQ12608)Configuration mismatch alarm is not clearedafter issuing a copy-to-mate command.

Issue additional copy-to-mate commandinthe Active unit.

24. Protection/

SW upgrade

(CQ18081)A Configuration mismatch alarm mightappear when upgrading SW in protectionsetup.

When upgrade is completed, issue additionalcopy-to-mate command in the Active unit(see more details under External Protectionsection.

25. Protection &Security

(CQ19960)When managing Active unit by HTTPSprotocol, the hyperlink in the Acitve units toopen Mate IDU (Standby) WEB does not

function.

Open new WEB browser page, and issue:https://.


22/25


PROPRIETARY

26. ConfigurationDownload

(CQ16245)The following configurationsparameters will

remain default when uploading configurationfrom I6.0 IDU and downloading to I6.1/I6.2IDU:

All parameters reside at the WEB path:Configuration General Trap Configuration

The parameters list:1. Trap admin2. Trap manager3. Trap port4. Community5. Filter by severity

These parameters should be set again whena configuration that was uploaded from I6.0

IDU and downloaded into I6.1/I6.2 IDU.

27. Alarms /Events

(CQ16074)SW Error alarm cannot be cleared by settingthe same value via the WEB.

When SW error alarm appears, the user isinstructed (by the corrective actions) to setagain a legal value of the parameter. Thiscannot be done via the WEB since the WEBdoes not perform the set operation if thecurrent value is identical to the previous one.This operation should be done via the CLIonly.

Please refer to SW Downgrade limitationsand open bugs for further details.

28. Alarms /Events

(CQ17513)At single pipe application with Ethernet #2(Copper-GbE, 10/100/1000) interface enabledand Automatic state propagation is enabled.

When LOF alarm is raised the port will beshutdown. When LOF is cleared, the port willbe enabled but additional LOC raised andcleared events will be appeared at the logfile.

LOC raise and clear events should beignored.

29. MAC HeaderCompression

(CQ14658)Enabling or disabling MAC HeaderCompression cause a few frames to be lost.


23/25


PROPRIETARY

30. SWDowngrade

(CQ16455 / 17562 / 18550)When downgrading SW version, from newer

SW version back to an older one, SW erroralarm might appear (when system rises withthe older version) due to feature configurationsthat were set in the newer version, that are notvalid (or does not exist) at the older one.

For example: if system is up and running with6.1 SW version, it might be running with ACMscript. When downgrading it to 6.0 SW version(an older one), SW error will appear, because

ACM scripts are not valid at 6.0 SW version.

The following steps should be followed by theuser:

1. Check in the Event log whichparameters have not been set andare the ones that raised the SWErroralarm.

2. Log into the CLI, and setindependently each parameter(follow the described path of theparameter as it is appeared in theevent log, in order to find it in theCLI tree) that appeared at the Eventlog.

3. Issue cold reset. When system is

up, SW error alarmshould becleared.

For example: Assume the following SWError alarms appear at the event log:

SW error: parametermanagement/mng-protocols/snmp/trap-severity-filter[1]set failed

SW error: parametermanagement/mng-protocols/snmp/trap-severity-filter[2]set failed

User should follow the path displayed in eachone of the SW Error events and set theparameters, for example:

set management/mng-protocols/snmp/trap-severity-filter[1]major

set management/mng-protocols/snmp/trap-severity-filter[2]critical

It is also possible to clear SW Error alarmby issuing a set-to-defaultcommand.

Under External Protection (1+1)configuration, if a SW Error alarm appearsat the Standby unit, a copy-to-matecommand initiated at the Active unit, willclear the alarm at the Standby, as soon asStandby is up (after the reset). If SW Erroralarm appears at both Active and Standbyunits, user can issue the procedure above tothe Standby first, then initiate a switchoverand issue the same for the new Standby.

Note: User should be aware that anydowngrade operation might raise SW Erroralarms. The described workaround abovesolves only current downgrade SW Errors.

This workaround should be followed anytime SW Error alarm is raised.


24/25


PROPRIETARY

31. SW Upgrade /Downgrade

(CQ21373)SW Package files must be downloaded to the

IDU before issuing any SW upgrade or SWdowngrade operation.

User should not rely on previous files thatmay or may not reside inside the IDU.

32. Flow Control (CQ14592)10/100/1000, or 10/100 Ethernet ports: settingFlow Control configuration to enable ordisable, might cause momentary shut downto the port.

33. Flow Control (CQ19814)Optical GbE interface (SFP) does notadvertise, during auto negotiation handshake,its capability to send PAUSE frames (TXPAUSE). Only its RX capability (react toPAUSE) is advertised.

Optical GbE interface is capable to generatePAUSE (TX PAUSE) or react (RX PAUSE) toPAUSE.

34. WEB (CQ15715)Web indicates SW download is in progresswhen management cable is disconnectedduring SW downloading.

Do not disconnect cable during SW download

35. Ethernet (CQ19807)When Optical GbE (SFP) auto-negotiation isnot converged successfully, port status isreported to be: 10Mbps half, although OpticalGbE is capable of only 1000Mbps full.

Resume (e.g. disconnect then reconnect)auto-negotiation process.

36. Ring RSTP (CQ15731)When Ethernet cable is disconnected fromnon-edge port, copper GbE interface and FEinterface might return path costof20,000,000, which is not the configured value.

When cable is disconnected, path cost ofcopper GbE and FE should be ignored.When cable is connected back, path costvalues are reliable.

37. CFM (CQ19783)When adding a new lower level domain, intoan already existent MAID which has higherlevel domain, which is in monitoring state, theouter domain might report short RDI alarm,and then go back to monitoring.

38. Protection (CQ18189)In protection (1+1), in case the SFP port(Ethernet #1) is enabled, while the Ethernetfiber is not connected (no Ethernet link), aswitchover might occur due to LOC alarm onthat port.When a switchover occurs under this scenario,the SFP port should be enabled again, but now

on the new active unit, since copy-to-mateoperation didnt take place.

In general, it is recommended to issueProtection Lockout, before enabling anynew interface (Ethernet or TDM) in aprotected (1+1) radio.It is recommended to connect the Ethernetfiber prior to configuring it to Enable.

39. Protection (CQ20925)FTP parameters in the Standby unit (that canbe accesses via pages: SW management,Configuration management andSecurityconfiguration) are configurable, but should beread only

Active unit FTP parameters are the onesthat should be configured. Standby unitsFTP parameters should be ignored, andtreated as read only.

40. WSC (CQ19994)When using WSC in Managed Switchapplication, any tagged frame carrying ether-type different than 0x8100 will be stripped atthe egress.


25/25

PROPRIETARY

41. Management& WSC

(CQ21158)When managing a protected (1+1) link with

out-of-band via WSC, narrow WSC might betoo narrow to manage the link, andmanagement might be very slow.

When managing a protected link out-of-band via WSC, it is recommended to use

wide WSC.

42. Protection &SNMP

(CQ17489)When protection switchover occurs, The newStandbyunit might fail to send a trap (thenew Active unit always sends a trap).

43. SNMP (CQ20300)Upon setting a value to the MIB table, animmediate "get" is performed, and the valuesthat are affected by the set may not havesufficient time to be updated. Thus, a newtable is brought with just the newly-set valueupdated, and is cached. Consequently, for thenext 30 sec. the cached table will be presentedand thus the other values won't be updated. (Inthis case - MaxTx is updated, but Tx is not).Only after this time the "correct" (updated)value is presented.Reducing the caching interval improved thespeed of update, but it is a significant changethat affects all the SNMP tables.

44. SWcompatibility

IP-10 IDU release I6.2 is compatible with allprevious IP-10 releases across the link.However, it is highly recommended to have thesame SW version on both ends of the link.

Minor bugs appear, such as (not limited to)setting remote frequency, traffic hit whenenabling/disabling/changing capacity ofWSC, traffic hit when enabling/disablingE1/T1s.

IP-10 I6 3 2 Release Notes - Ver 2 9 26

Documents

Transcript of IP-10 I6 3 2 Release Notes - Ver 2 9 26