Professional Documents
Culture Documents
This document provides information for the Cambium Networks PTP 650 Series System Release PTP
650-01-49.
https://support.cambiumnetworks.com/files/ptp650/
The information in this document is subject to change without notice. The recommendations,
technical data, configurations and statements in this document are believed to be reliable and
accurate, but are presented without implied or express warranty. Users must take full responsibility
for their applications of any product specified in this document. The information in this document is
proprietary to Cambium Networks Ltd.
2 Released products
2.1 Hardware
No new hardware has been introduced in this release.
• 650-01-49
PTP-SYNC:
• Firmware, v00.09
2.3 Upgrades
No new upgrades have been introduced in this release.
The interface between the ODU and the cnMaestro server allows the following parameters to be
configured:
• The IPv4 address or Fully Qualified Domain Name (FQDN) of the target host machine
• The size of the ICMP echo request payload, 1..1023 octets or bytes
Note The troubleshooting command that causes the ODU to generate pings is not yet
included in released cnMaestro server software..
The problem occurs when the ODU receives an unexpected duplicate Success Response message
after already transitioning to the Connected state, and consequently returns to the Approval Pending
state.
In 650-01-49, the cnMaestro interface in the ODU silently discards a Success Response message
received in the Connected state, and the problem is avoided.
The problem arises because the Device Agent (DA) firmware for the cnMaestro interface does not
handle the wrap of the 32-bit elapsed time indicator correctly at 2^32 milliseconds, resulting in failure
of the DA to respond to the watchdog.
The problem is corrected in System Release 650-01-49, by ensuring that the DA correctly handles
the counter wrap.
When spectrum management is configured for DSO, the receiver in the Slave ODU scans channels in
the Regulatory Band searching for an acquisition signal from the Master. If the receive signal is large,
the Slave ODU can detect the acquisition signal in channels adjacent to the wanted signal. In the
existing wireless interface, the Slave ODU does not attempt to establish a link if the acquisition signal
is up to three channels either side of the wanted channel. This approach is generally sufficient, but at
very high receiver power it is sometimes possible for the receiver to detect a signal at four channels
below or above the wanted channel. In this case, the ODU may attempt to establish a link. This
attempt to establish a link ultimately fails, but in doing so extends the scan period unnecessarily.
In System Release 670-01-49, the wireless interface has been modified to avoid establishing a link at
an offset of four channels.
In System Release 650-01-49, the ODU discards any buffered data when the connection to the server
is closed, avoiding the problem described above.
This occurs because the server requests a list of statistics, some of which are not supported in 650-
01-47. The expected behavior in this scenario is for the ODU to return an error message relating to
the unsupported statistics, while correctly returning values for the supported statistics. In 650-01-47,
there is a problem in the firmware with responding to a request that contains unsupported statistics,
and consequently the ODU fails to provide any data at all.
Link drops when barring DSO channels including the active channel
In earlier releases, a link can sometimes drop if several channels are barred at the same time in the
Spectrum Expert page, in the case where the list of barred channels includes the active channel. The
problem arises because of the order of channel moving and barring operations in ODU firmware.
The DA has incorrectly used the standard “blocking” socket API, resulting in an indefinite wait for the
missing message. The remedy is to configure a “non-blocking” socket.
The problem is corrected in System Release 650-01-49, where the DA correctly handles missing
messages.
In System Release 650-01-49, the TDD Frame Offset acts to advance frame timing for both
synchronization sources.
The problem is cleared by restarting the ODU. It might be possible to restart remotely using telnet if
this interface is enabled before the web interface becomes unresponsive.
We believe that this problem is significantly more likely to occur if the ODU is used in link with fading
wireless conditions.
The bandwidth of the tracking loop in PTP 650 is somewhat greater than the 0.1 Hz requirement for
EEC Option 2 networks, and consequently PTP 650 does not comply with the wander transfer limits
in Table 13 of G.8262. This is not likely to be a problem in typical applications of PTP 650, where the
number of Synchronous Ethernet nodes is small.
6 Technical Support
https://support.cambiumnetworks.com
Our award-winning Point to Point (PTP) radio solutions operate in licensed, unlicensed and defined
use frequency bands including specific FIPS 140-2 solutions for the U.S. Federal market. Ruggedized
for 99.999% availability, our PTP solutions have an impeccable track record for delivering reliable
high-speed backhaul connectivity even in the most challenging non-line-of-sight RF environments.
Our flexible Point-to-Multipoint (PMP) solutions operate in the licensed, unlicensed and federal
frequency bands, providing reliable, secure, cost effective access networks. With more than three
million modules deployed in networks around the world, our PMP access network solutions prove
themselves day-in and day-out in residential access, leased line replacement, video surveillance and
smart grid infrastructure applications.
Cambium Networks solutions are proven, respected leaders in the wireless broadband industry. We
design, deploy and deliver innovative data, voice and video connectivity solutions that enable and
ensure the communications of life, empowering personal, commercial and community growth
virtually everywhere in the world.
www.cambiumnetworks.com
Cambium Networks and the stylized circular logo are trademarks of Cambium Networks, Ltd. All
other trademarks are the property of their respective owners.