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

FibeAir IP-10 (R1)
High Capacity IP Wireless Network

Solution
IDU Software
I6.3.2
Release Notes

Including:
IDU Version (Package): 2.9.26

June 2011

IP-10 (R1) Software Release Notes Version 2.9.26
2
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
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
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 introduction
2. 1.5.4 Jan 2009 IP-10 R1 product release I6.0.1
3. 2.7.10 Mar 2009 IP-10 R1 product release I6.1
4. 2.7.12 Apr 2009 IP-10 R1 product release I6.1.1
5. 2.8.25.0 Aug 2009 IP-10 R1 product release I6.2
6. 2.8.31.0 Dec 2009 IP-10 R1 product release I6.2.3
7. 2.8.32.0 Feb 2010 IP-10 R1 product release I6.2.5
8. 2.8.33.0 Apr 2010 IP-10 R1 product release I6.2.6
9. 2.9.6 Sep 2010 IP-10 R1 product release I6.3
10. 2.9.9 Apr 2011 IP-10 R1 product release I6.3.1
11. 2.9.26 June 2011 IP-19 R1 product release I6.3.2

5
PROPRIETARY
2.2. Synonyms & Acronyms

AIS Alarm Indication Signal
ACM Adaptive Coding and Modulation
AES Advanced Encryption Standard
BER Bit Error Rate
BPDU Bridge Protocol Data Unit
CA Certificate Authority
CFM Connectivity Fault Management (Protocol)
CN Customer Network (Port)
DST Daylight Saving Time
EFM Ethernet in the First Mile (Protocol)
EOW Engineering Order Wire
EXC BER Excessive BER
FD Frequency Diversity
FE Fast Ethernet
FTP (SFTP) File Transfer Protocol (Secured File Transfer Protocol)
GbE / GBE Gigabit Ethernet
GMT Greenwich mean time
IDC In Door Controller
IFG / IPG Inter Frame/Packet Gap
HTTP (HTTPS) Hypertext Transfer Protocol (Secured HTTP)
LAG Link Aggregation Group
LOC Loss Of Carrier
LOF Loss Of Frame
LOS Loss Of Signal
LTM Link-Trace Message (CFM)
LTR Link-Trace Response (CFM)
MA Maintenance Association (CFM)
MAC (Ethernet) Media Access Control
MAC (Security) Message Authentication Code
MAID Maintenance Association (MA) Identifier (ID)
MEP Maintenance End Point (CFM)
MHC MAC Header Compression
MIB Management Information Base
MIP Management Intermediate Point (CFM)
MRMC Multi Rate Multi Constellation
MSE Minimum Square Error
NTP Network Time Protocol
NSV New Software Version
OAM Operation Administration & Maintenance (Protocols)
PIRL Port Ingress Rate Limiting
PM Performance Monitoring
PN Provider Network (Port)
PV PolyView
QoS Quality of Service
RSL Received Signal Level
SD Space Diversity
S/N Serial Number
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
STP / xSTP Spanning Tree Protocol
SSH Secured Shell (Protocol)
UC User Channel
UTC Universal Time Coordinated
WSC Wayside Channel
XPIC Cross Polarization Interference Cancellation

6
PROPRIETARY

3. Supported Systems and Configurations

3.1. Supported Systems

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

* Two ACM-28M scripts appear in the MRMC table. The first script that appears
in 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 QPSK 256QAM
9. ACM-10M 13 - 61 10 (9) FCC QPSK 256QAM
10. ACM-14M 21 - 87 14 (12.5) ETSI QPSK 256QAM
11. ACM-20M 28 - 124 20 (18) FCC QPSK 256QAM
12.
ACM-28M *
38 - 181 28 (26) ETSI QPSK 256QAM
13.
ACM-28M *
39 - 185 28 (27) ETSI QPSK 256QAM
14. ACM-30M 39 - 198 30 (28) FCC QPSK 256QAM
15. ACM-40M 56 - 255 40 (36) ETSI/FCC QPSK 256QAM
16. ACM-50M 67 - 337 50 (47) FCC QPSK 256QAM
17. ACM-56M 76 - 367 56 (52) ETSI/FCC QPSK 256QAM

7
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 HSB External Protection Yes
4.
1+1 space diversity (SD) Yes With RFU-HP
5.
ACM Yes

3.3. Channel Separation to MRMC translation Table

Channel
Separation
(MHz)
ETSI
/FCC
MRMC Script Name ACM Bit Rate
(Mbps)
Occupied
BW (MHz)
Modulation
(QAM)
7 ETSI 10Mbps-6.5MHz-QPSK-Grade-1 No 10 6.5 QPSK
20Mbps-6.5MHz-16QAM-Grade-1 No 20 6.5 16
39Mbps-6.5MHz-256QAM-Grade-1 No 39 6.5 256
ACM-42Mbps-6.5MHz-256QAM-Grade-1 Yes 10 - 42 6.5 QPSK - 256
10 FCC 47Mbps-9MHz-64QAM-Grade-1 No 47 9 64
ACM-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 - 256
27.5 , 28 ,
29 , 29.65 ,
30
ETSI 38Mbps-26MHz-QPSK-Grade-1 No 38 26 QPSK
155Mbps-26MHz-128QAM-Grade-1 No 155 26 128
181Mbps-26MHz-256QAM-Grade-1 No 181 26 256
30 FCC ACM-198Mbps-28MHz-256QAM-Grade-1 Yes 39 - 198 28 QPSK - 256
40 ETSI /
FCC
50 FCC ACM-337Mbps-47MHz-256QAM-Grade-1 Yes 67 - 337 47 QPSK - 256
56 ETSI /
FCC

8
PROPRIETARY
4. SW/HW Configurations and Compatibility

4.1. Supported HW Configurations

IDU available HW configurations:
ETH only
ETH + Auxiliary channels
ETH + 16xE1
ETH + 16xE1 + Auxiliary channels
ETH + 16xT1
ETH + 16xT1 + Auxiliary channels

4.2. Supported Licensing Configurations

SW license available for the following features:
ACM (IP-10 IDU SW license: ACM)
Switch (IP-10 IDU SW license: Managed Switch / Metro Switch)
Capacity (IP-10 IDU SW license: Capacity x)

Every IDU is delivered with basic capacity rate of 10Mbps.
Available capacities for upgrade: 25, 50, 100, 150, 200, 300, 400 (all) Mbps.

4.3. IDU-ODU/RFU Compatibility

IDU compatibility with different ODU/RFU types:

# IDU ODU/RFU
FibeAir 1500P 1500HP 1500SP RFU-HS 1500SP
Wide
RFU-C

1 IP-10 No Yes* Yes** Yes** Yes** Yes*** Yes

Notes:
The compatibility refers to IDUs loaded with this release
MRMCs (radio scripts) in both sides of the link need to have the same Grade.

9
PROPRIETARY
(*) 1500P ODUs support for 7MHz scripts should be checked with Ceragon
Support based on ODUs P/N
(**) 1500HP, 1500SP & RFU-HS support scripts up to 30.5MHz occupied
bandwidth
(***) 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 HW
revision when connected to RFU-C RFUs (no limitation when
connected to other ODU/RFU types). In general, IP-10 IDUs
with Part Number revision of 09-Axxx-6 or lower do not support
256QAM. IDUs with P/N of 09-Axxx-7 or above support
256QAM scripts.

RFU-C compatibility for 256QAM
Operation in 256QAM modulation scripts depends on RFU-C
HW revision and limitations may be applied. Contact Ceragon
support for confirmation and upgrade steps for RFU-C Part
Number confirmation.
ACM-56MHz: RFU-C should have version 1.97 (or higher) for
proper functionality of this script.

RFU-C compatibility for Adaptive TX Power
RFU-C should have version 2.01 (or higher) for proper
functionality of Adaptive TX Power feature. If lower RFU-C
SW 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
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 R1
releases across the link. It is highly recommended to have the same SW
version on both ends of the link.
In protection 1+1 (Hot Standby), it is mandatory to have the same SW version
at Local & Mate units (at the same link end).

11
PROPRIETARY
5. NSV Content

IP-10 IDU SW version is released as zipped RPM package (RPM, Red Hat Package
Manager, is the software package file 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.26
aidu-idc
2.9.26
aidu-management
2.8.52
aidu-modem-fw
3.3.18
aidu-fpga-fw
7.209
aidu-mrmc-scripts
2.44
L2protocols
7.5.1.aidc.t139.1.6
kernel
2.6.14.7-aidc.2.1
kernel-modules
0.2.1-2.6.14.7_aidc.2.1
aidu-setup
2.4.3
aidu-atp
2.3

MIB version: 6.7.0.45.2 (CERAGON-MIB_6.7.0.45.2.mib)

12
PROPRIETARY
6. New Features

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

# 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 partys user network.

This capability can be enabled or disabled, and by default is disabled.
This feature is available via the private MIB.

13
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 state
that 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
PROPRIETARY
8. Limitations / Features not Supported

# Subject Limitation Description/Notes
1. ACM Minimum ACM profile & Maximum
ACM profile configurations.
User must configure the Minimum ACM profile as
well as the Maximum ACM profile to be identical in
both link sides, in order to get the required
performance end to end.
2. ACM Minimum ACM profile The only MRMC scripts that currently support this
feature are the following ones:
FCC-10M: ACM-61Mbps-9MHz-256QAM-Grade-1
3. Ethernet Auto negotiation / speed & duplex This configuration must be similar on the IP-10 and
the device connected to it (the default is 1000 full
on the optical interface and auto-negotiation on" on
10/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). The
following cables should be used when "auto-
negotiation" is issued on both sides of the Ethernet
link:
1. IP-10 port to IP-10 port cross cable
2. IP-10 port to external switch port cross
cable
3. IP-10 port to external HUB straight cable
4. IP-10 port to PC cross cable.
5. RFU 1500P 11GHz ODU Separate ODU SW version (O5.52g) different from all
other 1500P ODUs (O5.52f)
6. CLI (CQ08720/20087)
Serial connection and Telnet
Serial connection and Telnet is supported with VT100
protocol.
7. Protection (CQ15547)
GbE Copper (10/100/1000) port in
protection.
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. When
standby unit is powered down and up again, Active
traffic may be affected.

8. Protection Ethernet ports in Protection Electrical (Copper) Ethernet ports' (10/100 or
10/1000/1000) LOC will not serve as protection
switchover triggers.
9. WEB (CQ20683)
WEB browser
Recommended to use Internet Explorer 7.0, 8.0 or
Mozilla Firefox 3.0. 3.5, 3.6.
10. WEB (CQ12684)
When using Mozilla Firefox WEB
browser, F5 function does not issue
a refresh as it is issued when using
Internet Explorer WEB browser.

11. WSC TDM capacity due to Wide WSC
configuration.
When activating WSC Wide, it consumes
2.048Mbps of the radio BW.
12. Configuration
Download
(CQ14545)
Configuration file has no unique name
Downloaded configuration files from different IDUs
should be saved in separated folders.
13. CLI (CQ12929)
Procomm SW definitions:
"Procomm" screen for IP-10 should be 80x24, while
default 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 be
considered no.

15
PROPRIETARY
15. Automatic State
Propagation
(CQ11348)
Single pipe application: Automatic
State Propagation (previously called
GbE Tx-mute): Local LOC is
enabled.
LOC on local Electrical GbE (10/100/1000) will
NEVER cause "shut-down" or "Tx-Mute" on remote
end. This behavior avoids dead-lock:
If remote end is shut-down due Local-LOC, and now
remote cable is disconnected, then local port will be
shut-down, and Ethernet link will never be able to
recover.
16. Ethernet (CQ10564)
MAC Learning capability
Switch is capable of learning up to 8K (8192)
random MAC addresses.
17. T1 (CQ 18154)
T1 line code.
T1 line code should be configured to
be the same (AMI or B8ZS) on both
ends of the link. If the line coding is
not the same on both ends, errors
might appear without raising any
alarm.
User should configure the same T1 line coding on
both ends of the link.
Packets with SA of Broadcast
(MAC=FF-FF-FF-FF-FF-FF) or
Multicast (MAC bit [40] is set) will be
forwarded.

System does not discard frames with
DA of 00:00:00:00:00:00

When a VLAN, which is attached to a
port, is deleted, no warning message
appears.

21. CFM (CQ17682)
CFM protocol uses several entries of
the Forwarding table - when the table
is 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.1ag
standard to loopback remote unit
before activating Link-Trace.

23. CFM (CQ17189)
It is highly recommended to loopback
protection 1+1 IDUs by MEP ID and
not by MAC address.
When a switchover occurs, the new active IDU
introduces different MAC address to the network. A
loopback which was initially addressed to the old
active IDU (which is now the new standby IDU) will
not be reachable.
24. CFM See detailed limitations list under CFM
section.

25. Security - SFTP (CQ15340 / 15536 1)
When setting up SFTP connection, for
download/upload files operations (e.g.
software download, configuration file,
download a certificate file, etc.), the
IDU (client side) wont authenticate the
SFTP server based on server's public
key.

26. Security - SFTP (CQ15536 2)
SFTP server authenticates user based
on user name and password.
Public Key authentication of the
target IDU is not supported
(authentication method that do not
require password).

16
PROPRIETARY
27. Security (CQ15536 3)
Upload/download file from/to the IDU
requires the following parameters: host
IP, host-path, user name, and
password. Additional parameters are
required for IDU digital certificate, or
CA certificate: file-name, security file
type and security file format. Due to
the fact that the IDU can be managed
simultaneously by a few connections,
some conflicts may appear:
1. One connection configures
the parameters for one
purpose and another
connection configures them
for another purpose. The
"apply" command of both
connections will probably be
failed.
2. One connection (C1) starts
an operation
(upload/download) and
another connection (C2)
changes parameters related
to the first connection
operation. C1 operation might
fail without any alarm or
notification.

28. Security (CQ15826 1)
web-protocol parameter, for
determining the web protocol
(http/https), won't be copied to mate
system in protection mode, due to the
following facts:
a. Applying https protocol requires
the installation of a digital certificate.
IDU digital certificate is unique per IDU
(based on IDU key pairs). If the digital
certificate is not installed, the
parameter's set will be failed.
b. Security considerations: Eliminate
the option to override security
definitions from one unit (with lower
security privileges) to another one
(with higher security privileges).

29. Security CA
Certificate
(CQ15826 2)
Due the fact that there are some WEB
browsers (e.g. Mozilla Firefox) that
require WEB servers CA certificate (in
addition to IDU certificate), new
configuration is required to enable this
option (see details under HTTPS
section).
web-ca-certificate-admin parameter
should be set to enable (the default is
disable) this option. When this option
is enabled, CA certificate file should
already be installed and valid in the
IDU. This parameter will not be copied
to mate when activating copy to
mate.

17
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-band
management, the management VLAN needs to be
first configured in the remote Standby unit. See
further information under "Product and Features
Description" and "External Protection" sections.

31. Management (CQ8139)
In-band management disruptions with
traffic max throughput when
Management VLAN is not at highest
priority.

Set Management VLAN at highest priority
32. Management (CQ11003 / 12878)
When managing 1+1 units (Active &
Standby) via external switch, when
powering off Active unit, or when a
switchover is initiated, units might not
be reachable for ~5 minutes.
This only happens in Active power off, and can be
resolved by the following:
1. Disable learning feature of the external switch (or
use 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 "best
effort" and may be discarded.
34. Ethernet Ethernet maximum (100%) throughput. Packet loss when using 100% throughput. This is a
theoretical case in a laboratory when there is a
difference in the clock source of the testing
equipment and the IDU (up to 100 ppm).
When the throughput is at 99.99% - there is no
packet loss.
Packets with VID=0
Packets with VID=0 are considered un-tagged and
pass through access ports.
Frames tagged with VID=4091
In single-pipe application, 4091 tag is removed, and
the frame will egress untagged at remote end.
User should avoid using VLAN 4091.
37. Protection

(CQ16813)
When upgrading SW version in
protection, both IDUs (local & mate)
should be upgraded to have the same
SW version.

38. WEB/
Security
(CQ15165)
Internet Explorer should be
configured to Medium-High or Low
security level when interfacing WEB
application.
In case it is not possible, WEB
browser should have the element IP in
the trusted IPs table.

39. WEB/
Security
(CQ24328)
Special characters (!@#$%^...) cannot
be used in password through the WEB
interface.
Only the following characters should be used for
password:
a..z, A..Z, 0..9
40. PM (CQ16770)
Ethernet frame error rate PM
resolution is 1%. 0% means less than
1% error rate.

41. ATPC (CQ13228)
When enabling (or disabling) ATPC to
remote by using local-remote
channel, only the remote units ATPC
is enabled (or disabled) - Just setting
one end does not automatically set the
other.
For proper ATPC functionality, both links ends
should be enabled (or disabled). Local ATPC should
be enabled (or disabled) as well.

18
PROPRIETARY
42. Protection

(CQ15623)
On Standby unit, interface Ethernet #2
(Copper- GbE 10/100/1000) will not
raise the alarm Ethernet Loss of
carrier if its cable is disconnected.
This port is shutdown on Standby unit.

43. Protection

(CQ15624)
Protection Lockout and Protection
Force Switch do not persist after cold
reset.

19
PROPRIETARY
9. Corrected Bugs

None

20
PROPRIETARY
10. Open Bugs

#
Subject Description Workaround
1. WEB Cable disconnection during RFU upload will
display the download as if it were continuing.
Another upload will solve this issue.
2. WEB Create unit configuration via WEB process
takes 3.5 minutes, and connection to web is
lost.
Re-open web window.
3. WEB
(CQ 15189)
After upgrading SW version, WEB does not
respond correctly.

Close WEB browser and reopen it.

4. WEB
(CQ 15653)
When upgrading or downgrading SW, Main
View page might display the older Main
View.
Delete Internet Temp Files (Clear
Cache/Cookie) in the WEB browser, and
reopen the Main View Page.
5. WEB
(CQ16436/15845/15845/15957/18202/18202/1
9523/19574)
WEB response issues:
1. Refreshing browser page by pressing
F5 returns unexplained error.
2. Invalid text appears in the WEB
browser.
3. Units tree does not appear at the left
side of the page.
4. "Cannot open the Internet site" error
message appears.
Close and then reopen WEB, or Refresh by
Ctrl+F5 and re-login.
6. WEB
(CQ19509/19813/20001/20005)
WEB browser window size issues, that might
appear when window size < 100%:
1. Might not be possible to create archive
configuration.
2. Might not be possible create archive
unit-info.
3. Gibberish on the window.
4. Improper appearance of tables.
These WEB issues are related to the WEB
browser. User should use only window size of
100%.

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

This is the BER that the TDM port reflects
when the port is disabled, as there is no BER
calculation.
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 strings
should not contain any spaces:
1. VLAN Name
2. Policer Name
3. Class-map Name
4. Association Name
5. Domain Name
Avoid using <space> characters. The
character _ (underscore) can be used
instead.
11. Ethernet-
RMON
(CQ9497 / 10035)
RMON 1024 Octets/In FCS errors counters
These counter also increment on oversize
packets

21
PROPRIETARY
12. Ethernet-
RMON
(CQ11863)
RMON counters at "standby" unit display
unclear values, due to the fact that Ethernet
ports at "standby" unit are blocked.
RMON counters at the "Active" unit are the
relevant ones.
13. Ethernet-
RMON
(CQ10729)
RMON counters in radio excessive BER
In "Excessive BER" scenario (BER~1e-5)
RMON counters might count frames with
different lengths, which are also counted as
"FCS frames received".
14. Ethernet-
RMON
(CQ13077) (limitation)
RMON Bad octets received counts only 1632
bad octets even when ingress frame length is
above 1632 bytes.

15. Ethernet-
CFM
(CQ 18203)
While working with CFM, in case an RDI or LDI
is raised, a general Ethernet Service Failure
alarm is raised. Once the alarm is raised, if
user removes all the MAIDs configurations
from the unit, the Alarm might stay as raised.
In order to avoid this user should delete the
MAIDs one by one (avoid deletion of a group
of MAIDs).
If a group of MAIDs is removed at once, and
Ethernet Service Failure alarm is raised, a
cold reset will remove it when system is up.
16. Protection Excessive BER in Protection When there is excessive BER for less than
one second, the system will not initiate a
protection switch.
Protection switchover due to protection cable
disconnection.
Protection cable disconnection might trigger,
in a very low probability, a protection switch.
To resolve this, first power off the one IDU
and then disconnect protection cable.
Additional unnecessary protection switchovers
in 'Protection' with Optical interface enabled,
but without SFP in cage.
Insert SFP in cage prior to enabling
protection.
Protection cold reset switch reason
Protection switch due to a cold reset
command will be described as a manual
switch in the alarm log.
20.
Protection Configuration during "Copy-2-mate" and/or
MRMC change (radio script change)
The user should refrain from changing
configuration during these two processes.
21. Protection
(CQ12563)
Frequency setting in protection.
Prior to setting frequencies on local and
remote sides, enforce lockout to insure
action.
22. Protection

(CQ13622)
Simultaneous cold reset to both active and
standby units (e.g. site power down) causes
several consecutive protection switches.
Traffic goes back to normal after the
protection switches. Intentionally cold reset,
should be done 1st to the Standby unit, wait
until it is up and running, and then to the
Active unit.

23. Protection

(CQ12608)
Configuration mismatch alarm is not cleared
after issuing a copy-to-mate command.
Issue additional copy-to-mate command in
the Active unit.
24. Protection/
SW upgrade

(CQ18081)
A Configuration mismatch alarm might
appear when upgrading SW in protection
setup.
When upgrade is completed, issue additional
copy-to-mate command in the Active unit
(see more details under External Protection
section.
25. Protection &
Security
(CQ19960)
When managing Active unit by HTTPS
protocol, the hyperlink in the Acitve units to
open Mate IDU (Standby) WEB does not
function.
Open new WEB browser page, and issue:
https://<IP_Addr-of-the-Standby-unit>.

22
PROPRIETARY
26. Configuration
Download
(CQ16245)
The following configurations parameters will
remain default when uploading configuration
from I6.0 IDU and downloading to I6.1/I6.2
IDU:

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

The parameters list:
1. Trap admin
2. Trap manager
3. Trap port
4. Community
5. Filter by severity

These parameters should be set again when
a 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 setting
the same value via the WEB.

When SW error alarm appears, the user is
instructed (by the corrective actions) to set
again a legal value of the parameter. This
cannot be done via the WEB since the WEB
does not perform the set operation if the
current value is identical to the previous one.
This operation should be done via the CLI
only.
Please refer to SW Downgrade limitations
and open bugs for further details.
28. Alarms /
Events
(CQ17513)
At single pipe application with Ethernet #2
(Copper-GbE, 10/100/1000) interface enabled
and Automatic state propagation is enabled.
When LOF alarm is raised the port will be
shutdown. When LOF is cleared, the port will
be enabled but additional LOC raised and
cleared events will be appeared at the log
file.
LOC raise and clear events should be
ignored.
29. MAC Header
Compression
(CQ14658)
Enabling or disabling MAC Header
Compression cause a few frames to be lost.

23
PROPRIETARY
30. SW
Downgrade
(CQ16455 / 17562 / 18550)
When downgrading SW version, from newer
SW version back to an older one, SW error
alarm might appear (when system rises with
the older version) due to feature configurations
that were set in the newer version, that are not
valid (or does not exist) at the older one.

For example: if system is up and running with
6.1 SW version, it might be running with ACM
script. 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 the
user:
1. Check in the Event log which
parameters have not been set and
are the ones that raised the SW
Error alarm.
2. Log into the CLI, and set
independently each parameter
(follow the described path of the
parameter as it is appeared in the
event log, in order to find it in the
CLI tree) that appeared at the Event
log.
3. Issue cold reset. When system is
up, SW error alarm should be
cleared.
For example: Assume the following SW
Error alarms appear at the event log:
SW error: parameter
management/mng-
protocols/snmp/trap-severity-filter[1]
set failed
SW error: parameter
management/mng-
set failed
User should follow the path displayed in each
one of the SW Error events and set the
parameters, for example:
set management/mng-
major
set management/mng-
critical

It is also possible to clear SW Error alarm
by issuing a set-to-default command.
Under External Protection (1+1)
configuration, if a SW Error alarm appears
at the Standby unit, a copy-to-mate
command initiated at the Active unit, will
clear the alarm at the Standby, as soon as
Standby is up (after the reset). If SW Error
alarm appears at both Active and Standby
units, user can issue the procedure above to
the Standby first, then initiate a switchover
and issue the same for the new Standby.
Note: User should be aware that any
downgrade operation might raise SW Error
alarms. The described workaround above
solves only current downgrade SW Errors.
This workaround should be followed any
time SW Error alarm is raised.

24
PROPRIETARY
31. SW Upgrade /
Downgrade
(CQ21373)
SW Package files must be downloaded to the
IDU before issuing any SW upgrade or SW
downgrade operation.
User should not rely on previous files that
may or may not reside inside the IDU.
32. Flow Control
(CQ14592)
10/100/1000, or 10/100 Ethernet ports: setting
Flow Control configuration to enable or
disable, might cause momentary shut down
to the port.

33. Flow Control
(CQ19814)
Optical GbE interface (SFP) does not
advertise, during auto negotiation handshake,
its capability to send PAUSE frames (TX
PAUSE). Only its RX capability (react to
PAUSE) is advertised.
Optical GbE interface is capable to generate
PAUSE (TX PAUSE) or react (RX PAUSE) to
PAUSE.
34.
WEB
(CQ15715)
Web indicates SW download is in progress
when management cable is disconnected
during SW downloading.
Do not disconnect cable during SW download
35. Ethernet
(CQ19807)
When Optical GbE (SFP) auto-negotiation is
not converged successfully, port status is
reported to be: 10Mbps half, although Optical
GbE is capable of only 1000Mbps full.

Resume (e.g. disconnect then reconnect)
auto-negotiation process.
36. Ring RSTP
(CQ15731)
When Ethernet cable is disconnected from
non-edge port, copper GbE interface and FE
interface might return path cost of
20,000,000, which is not the configured value.

When cable is disconnected, path cost of
copper GbE and FE should be ignored.
When cable is connected back, path cost
values are reliable.
37. CFM
(CQ19783)
When adding a new lower level domain, into
an already existent MAID which has higher
level domain, which is in monitoring state, the
outer 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 Ethernet
fiber is not connected (no Ethernet link), a
switchover might occur due to LOC alarm on
that 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-mate
operation didnt take place.

In general, it is recommended to issue
Protection Lockout, before enabling any
new interface (Ethernet or TDM) in a
protected (1+1) radio.
It is recommended to connect the Ethernet
fiber prior to configuring it to Enable.

39. Protection
(CQ20925)
FTP parameters in the Standby unit (that can
be accesses via pages: SW management,
Configuration management and Security
configuration) are configurable, but should be
read only
Active unit FTP parameters are the ones
that should be configured. Standby units
FTP parameters should be ignored, and
treated as read only.
40. WSC
(CQ19994)
When using WSC in Managed Switch
application, any tagged frame carrying ether-
type different than 0x8100 will be stripped at
the egress.

25
PROPRIETARY
41. Management
& WSC
(CQ21158)
When managing a protected (1+1) link with
out-of-band via WSC, narrow WSC might be
too narrow to manage the link, and
management 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 new
Standby unit might fail to send a trap (the
new Active unit always sends a trap).

43. SNMP
(CQ20300)
Upon setting a value to the MIB table, an
immediate "get" is performed, and the values
that are affected by the set may not have
sufficient time to be updated. Thus, a new
table is brought with just the newly-set value
updated, and is cached. Consequently, for the
next 30 sec. the cached table will be presented
and thus the other values won't be updated. (In
this case - MaxTx is updated, but Tx is not).
Only after this time the "correct" (updated)
value is presented.
Reducing the caching interval improved the
speed of update, but it is a significant change
that affects all the SNMP tables.

44. SW
compatibility
IP-10 IDU release I6.2 is compatible with all
previous IP-10 releases across the link.
However, it is highly recommended to have the
same SW version on both ends of the link.
Minor bugs appear, such as (not limited to)
setting remote frequency, traffic hit when
enabling/disabling/changing capacity of
WSC, traffic hit when enabling/disabling
E1/T1s.

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

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

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

Uploaded by

Copyright:

Available Formats

FibeAir IP-10 (R1)

High Capacity IP Wireless Network

You might also like