In releases up to and including 670-02-50, the PTP topology for PTP 670 provides a Data Service that is a transparent circuit between a single wired Ethernet port at the local end of the link and a single wired Ethernet port at the remote end of the link. That works well in many applications.
PTP 670 additionally supports a Second Data Service (SDS), providing a second circuit, also between one Ethernet port at each end of the link, and isolated from the standard Data Service. The Second Data Service and the Out of Band Management Service cannot be used at the same time. There are a few applications where the SDS could be useful.
In 670-02-60, we introduce Ethernet switching between the neighbouring wired Ethernet ports at the ODU, so that it is possible to allocate between one and three of the wired ports to the Data Service at each end of the link. The internal switching is a more effective and more flexible way of connecting multiple devices at the same site. The Second Data Service is not supported in 670-02-60. In general, the additional benefit of the switching capability is significantly greater than penalty of losing the SDS.
You will need to redesign any data network using SDS before upgrading to 670-02-60.
Based on support calls, we get the impression that the SDS has not been used very extensively. If you have used SDS, and have any concerns, please contact Cambium so that we help devise a suitable solution.
The remaining features introduced for PTP links in 670-02-60 are summarised here: System Release PTP 670-02-60 available for PTP 670
Working with our customer who has purchased 30+ PTP670 units to replace older radios with Ethernet (Business) and T1 circuits (Process).
The new setup will require Dual Ethernet that is separate Primary data (Business) and Secondary data (Process) or (2 way radio comm) it is a legal requirement that they remain separate.
We have the B model of radios that were just purchased but have previously used many the Earlier A models.
We have used the SDS in the past to separate traffic for our customer.
What versions of the firmware can we use to get SDS on the B model if possible and or do we need to get A model radios?
Should we return the 30+ radios that have already been purchased?
Please use firmware version 670-01-47 to use TDM traffic and SDS on PTP 670 ODUs with Cambium Part Number ending in "B".
We no longer manufacture PTP 670 ODUs with Cambium Part Number ending in "A".
Testing with the firmware version 670-01-47 allows and SDS and shows segregated traffic.
The only disadvantage I have found after some brief testing is the SFP port does not show up as an option which may affect future projects.
We at NSTI would greatly appreciate it if a 670-02 version with full 670 support and SDS could be made available.
You should be advertising the SDS feature of these radios. Many Oil/Gas/Telecom/Production/State/Emergency companies that we work for need Isolated networks (Process/Radio/Emergency/Fire) that can not be on their business networks. Which can be difficult or impossible to install 2 separate systems on the same tower or building.
Thanks for the feedback! The user guide goes into more detail about the various management and payload data options for network traffic. I believe the reason that SFP was not a selectable choice was due to a licensing issue. In order to enable the SFP port, a license is needed. This license includes: the actual SFP module, license for use, extended gland, and instructions. I've included the part numbers for the various kits below.
|| Single Mode Optical 1000BaseLX SFP Interface per ODU
|| Multi-mode Optical 1000BaseSX SFP Interface per ODU
|| Gigabit Ethernet 1000BaseT SFP Interface per ODU
Also, in case you start searching for more PTP670 info, almost all of the references to PTP650 can be applied to the PTP670 since they are near identical. Here are a couple of good ones, in addition to our webinar archive and YouTube channel.
When it comes to TDM services, there are some additional caveats. Be sure to check the release notes, as specific firmware versions are needed. This also applies to PTP650 compatibility.
Here's some background on the Second Data Service:
The PTP 650 hardware has three wired ports. Many customers asked for Ethernet switching inside the PTP 650 so that they could make better use of the three ports. Unfortunately, the FPGA in PTP 650 is not big enough to implement an internal switch. The Second Data Service (SDS) feature was introduced in PTP 650-01-40 to address some of the applications that might have otherwise been handled by an internal switch. SDS was subsequently ported to PTP 670.
We finally implemented the embedded Ethernet switch in PTP 670-02-60. This switch allows for up to three wired ports in the Data Service, meeting most of the original demand for internal switching. We dropped support for SDS as part of the project to implement the switch. However, it appears that the SDS might (surprisingly) be a better solution than the switch for some applications, particularly where the operator wants to segregate two types of traffic.
We also discontinued support for TDM as part of the introduction of the switch.
We have alternative firmware for PTP 670 with features and performance exactly the same as PTP 650. This firmware is intended to support mixed links between PTP 670 and PTP 650 ODUs. The PTP 670 firmware (for example 670-01-47) is effectively 650-01-47 firmware compiled to execute on the PTP 670 hardware. There is no reason why you wouldn't use 670-01-47 at both ends of a link to meet a need for TDM or SDS.
We are continuing to support the 01-XX firmware with essential bug fixes. For example, 670-01-47 was released on 20 December 2018.
The following firmware is compatible with the “B” suffix PTP 670 hardware:
- 670-01-46 (B suffix ODU, TDM, SDS)
- 670-01-47 (B suffix ODU, TDM, SDS, cnMaestro)
- 670-02-60 (B suffix ODU, Ethernet switch)
- 670-02-65 (B suffix ODU, Ethernet switch)
- 670-02-67 (B suffix ODU, Ethernet switch, cnMaestro)
Older question, but still using the SDS. It seems like such a needed feature, and am still baffled why Cambium would phase this out?!
My question is "Is 670-01-50 along the same lines as * 670-01-47 (B suffix ODU, TDM, SDS, cnMaestro) in regards to an isolated SDS??? We are hitting the cnMaestro bug and would like to update if possible. Thanks in advance