This is an interesting question and needs a lot of deep discussion.
People will consider optimizing performance settings using PTP 820C with dual core, both cores enabled, using the widest channel (80MHz), with highest modulation level available (on 80MHz - 1024 QAM), and with physical link aggregation (MC-ABC). Given these settings, if each core will give over 600Mbps, then the radio will provide 1.2Gbps, is that right?
Unfortunately, it will be a wrong answer. I will share more details tomorrow on how to do it right to get over 1Gpbs with the PTP 820 product.
Multi-Carrier Adaptive Bandwidth Control (MC-ABC) is an technology that creates logical bundles of multiple radio links and optimizes them for wireless backhaul applications. Multi-Carrier ABC enables separate radio carriers to be shared by a single Ethernet port. This provides an Ethernet link over the radio with double capacity, while still behaving as a single Ethernet interface.
For the configuration with 2 x 80 MHz channel configruation, each channel will provide 600Mbps throughput. But when have MC-ABC feature enabled, since it is mapped to a single Ethernet port, the throughput will be limited to 1 Gpbs.
In short, if you want over 1 Gpbs throughput, you shall not use MC-ABC, as it will cap the throughput to 1Gbps.
In order to exceed 1 Gbps, we need to separate the Radios. we need to create 2 x P2P Services. 1st Service from 1st GBE port toward Radio 1, and the 2nd service from another GBE port to the 2nd radio. in such setup, you will get 2 x 600Mbps, which is 1.2 Gpbs.
as the diagram shows, the De-duplicadtion is a technology by replace the packet header during the transmission and make it more effective for wireless data transfer. General speaking, the smaller the packet size, the more improvement you will be able to see. in our lab test, we can show 70% growth on 64 bytes frame.
Wihch means if customer has De-duplication features enabled, the radio throughput could easily pass over 1 Gpbs throughput though the uncompressed layer2 throughput may below 1 Gpbs.
Here is a table shows radio throughput on a 40Mbps channel,
40 MHz
Ethernet Throughput (Mbps)
Channel Size
No Compression
L2 Compression
Multi-Layer Compression
QPSK
57
57-65
60-183
8 PSK
85
86-97
89-273
16 QAM
116
117-132
121-372
32 QAM
152
154-174
160-490
64 QAM
187
189-214
197-602
128 QAM
226
228-258
238-728
256 QAM
243
245-278
256-782
512 QAM
267
269-304
280-833
1024 QAM Strong
302
305-345
318-833
1024 QAM Light
321
324-366
337-833
2048 QAM
347
350-396
365-833
I think it is good enough for today. I will continue our discussion tomorrow on what configuration is recommended if we have the air throughput over 1 Gpbs.
A summary of using PTP820C for 2+0 link configuration for over 1 Gpbs configuration, you will need two cables per radio in order to achieve over 1 Gpbs, as per port is limited to 1 Gbps.
Enabled 2nd GigE port on PTP820C (PTP 820 Act.Key - GE port is needed)
Enabled 2nd Core on PTP820C (PTP 820C Act.Key - 2nd Core Activation is needed)
Use 500Mbps or 650Mbps capacity key (PTP 820C Act.Key - Capacity 500M with ACM Enabled or PTP 820C Act.Key - Capacity 650M with ACM Enabled)
Add 2 additional SFPs and cables
During the configuration, you can go with either a multiple P2P service or a single PMP services, either way works.
With PTP820 multi-core radio, the radio can deliver over 1 Gbps Ethernet throughput using 1024 or 2048QAM on 56, 60, or 80MHz channels with following setup:
PTP820C
2+0 or 2 x (2+0) Single Polarization
2+0 or 2 x (2+0) Dual Polarization (with or without XPIC)
2x2 or 4x4 LOS MIMO
PTP820G
2+0 Single Polarization
2+0 Dual Polarization (with or without XPIC)
With header-deduplication features enabled, the Ethernet throughput over the air can further boosted. Depends on packet size, the radio may deliver over 1Gbps even customer use 28/30 MHz or wider channels.
Here, i will use PTP820C 2+0 configurations as examples show what is needed and how to setup a radio for such configuration.
Keep in mind, in order to full use over 1 Gbps throughput over the air, customer will need two Ethernet cables per PTP820 radio. Also no MC-ABC features shall be enabled, as MC-ABC (multi-carrier adaptive bandwidth control) will map the radio throughput to a single Ethernet port, which will cap the throughput to 1 Gbps even the air throughput could be much higher.
SAP –Eth 1 & SAP – Eth 2 <-> SNP Group 1 (LAG of Radio core 1 and 2)
Multipoint services are used to provide connectivity between two or more service points.
When traffic ingresses via one SAP (Service Access Point), it is directed to the SNP (Service Network Points) in the service, other than the ingress service point, according to ingress and egress tunneling rules, and based on the learning and forwarding mechanism.
Following is the typical BOM for this setup
P/N
Description
Qty
1
C110082B043A
PTP 820C Radio 11WGHz,TR500,Ch1W6,Hi,11185-11485MHz
1
2
C110082B044A
PTP 820C Radio 11WGHz,TR500,Ch1W6,Lo,10695-10955MHz
1
3
N110082L082A
PTP 820C OMT KIT 10-11GHz
2
4
N110082L092A
PTP 820 RFU-C 10_11GHz OMT Interface-Andrew
2
5
N000082L079A
PTP 820C Act.Key - Capacity 650M with ACM Enabled
4
6
N000082L027A
PTP 820C Act.Key - 2nd Core Activation
2
7
N000082L056A
PTP 820 Act.Key - XPIC
4
8
N000082L042A
PTP 820 Act.Key - GE port
2
9
N000082L022A
PTP 820 PoE Injector all outdoor, redundant DC input, +24VDC support
2
10
N000082L059A
PTP 820 SFP Optical 1000Base-LX,EXT TEMP
2
11
N000082L014A
PTP 820 Glands_x5_KIT
2
12
N000082L116A
PTP 820 GROUND CABLE FOR IDU and ODU
2
13
N000082L016A
PTP 820 CAT5E_Outdoor_100m_drum
2
14
N000082L017A
PTP 820 Grounding Kit for CAT5e F/UTP 8mm cable
4
15
N000082L073A
PTP 820 GBE_Connector_kit
2
16
N110082D072A
PTP 820 2' ANT,SP,11GHz,RFU-C TYPE&Std UBR100 - Andrew
Tried this setup on 8.2 with an 820c, but does seem to have a limitation/bug on VLANs that traverse the link. I have a trunk between two Cisco 3560G switches and it would pass traffic on a couple VLANsm but not all of them. It would pass traffic on VLAN 10, 20, 30, but not 70, 100, 700, 2010. I would remove the VLAN 10, then 70 would work. Seems to be a bug in the software. I spoke with Cambium support regarding this issue and they said they don't configure 820c radios in the same manner as posted in this thread. Any suggestions?
Two radio core are configured as a LAG group 1
One MP Ethernet services need setup
SAP –Eth 1 & SAP – Eth 2 <-> SNP Group 1 (LAG of Radio core 1 and 2)
Multipoint services are used to provide connectivity between two or more service points.
When traffic ingresses via one SAP (Service Access Point), it is directed to the SNP (Service Network Points) in the service, other than the ingress service point, according to ingress and egress tunneling rules, and based on the learning and forwarding mechanism.
The second SFP on the PTP820C is used for MIMO data-sharing. So, in normal PTP820C, you cannot use it unless you make a special order from Cambium.
Also, as long as I know, there is no bug like what you described in the previous note. If you can tell me what you want to achieve (maybe even draw a picture) I can help you.
I have a question, I have a PTP 820C with OMT, at the moment I'm using the DEMO license. Configure the link with MC ABC, created a group with both radio and created a LAG with both interfaces, also I created the P2P service with MC ABC and LAG to pass 1.3Gbps full duplex. My question is, LACP protocol that uses the 820C and that I can not make it work with my switch
We are setting up a 1.2 Gbps link for the first time and are curious about the management IP address (Platform/Management/Networking/Local) configuration
I see under Ethernet/Services the MNG service ID 257 is Operational. If I check the Service Points for this ID 257, I see that it is tied to Ethernet: Slot 1 port 1 and Radio: Slot 2 port 1.
Does this mean we lose management if this ethernet interface is lost, but the radio still passes traffic on interface two?
What's the best course of action? If we add the other interfaces to the service point, might that cause IP conflicts? Should we set up a second management interface with a different IP address?