SIAE BENCH TEST for end-to-end DATA and MNGT

transport solution
GILAT – PERU’

INR3764-02 - SIAE Network Planning Department Gilat-Perù

 Introduction to network end-to-end behavior
• The MW backhauling, working in Layer-2 mode, is expected to aggregate all different types of traffic coming from terminal sites
and carry it towards the Main aggregation point where a Router is supposed to be placed

• The VLAN design and configuration will be performed in order to transparently transport the downlink and uplink traffics, without
making any manipulation or change on the frames, i.e. incoming frames won’t be modified, thus they will pass transparently

• The scenario suitable for the backhauling network depending on nature of ingress traffic to be transported. According to the
Customer’s requirements, the following scenario (“Fully-Transparent with Untagged traffic”) is going to be implemented:
• Ingress Ethernet packets at CPE site are untagged Customer to each CPE site and will transported over the BH network as
tagged with VLAN ID assigned to the each CPE. The PMP is meant to tag/untag the incoming/outcoming frames
• the transport over PTP radio will be fully transparent, i.e. Ethernet packets won’t be affected/changed by MW radios involved
along the MW cluster, i.e.
• QoS polices could be enabled along the entire MW chain from access network (PMP links) to backbone (PTP links), i.e. the
VLAN forwarding will be configured in order to manage and send out incoming frames basing on IEEE 802.1q

 VLAN managing: in accordance with IP addressing explained above, for each subnet a different VLAN ID has been associated,
i.e.
o MNGT traffic : VLAN 500 is supposed to be used for all MW radios belonging to same bridge domain
o Payload Traffic: VLAN 600, 700 or whatever are supposed to be managed across the MW cluster from terminal site (CPE
point) to Main site (Router point)

Gilat-Perù 2
TEST BENCH DESCRIPTION

Gilat-Perù 3
 Bench Test description
• In this document are briefly presented a possible backhauling network scenario suitable for a bench test in SIAE laboratory. As shown in next slide the scenario foresees the
simultaneous use of the CAMBIUM’s PTP and PMP products along with SIAE ALFOplus to establish a wireless connection from the remote site (CPE/user point) to the Main
site (Router Point)

• Thus, the purpose of this bench is to carry out a list of tests to prove the feasibility of the network whereas the simultaneous use of equipments of different vendors is
foreseen. Here are the main topics the test session has been focused on:
1. CAMBIUM and SIAE interoperability (PASSED)
o Physical electrical compatibility with auto-negotiation mode enabled
o Connection Speed Test, i.e. end-to-end line speed test on both uplink and downlink directions from machine (i.e. laptop connected to one end of MW
chain) to machine (i.e. laptop connected to the other end of MW chain)
o MW radios connected to each order in different orders (1. ALFO->PTP->ePMP / 2. ALFO-> ePMP >PTP)
2. Throughput (PARTIALLY PASSED -> see comments in last slide)
o Different traffic loads -> up to the maximum available throughput on radio side
o Different Ethernet frame size -> from 64byte up to 1522byte
o Different Ethernet frame type -> Tagged and Untagged (to be further investigated for official confirmation)
o Different MIR values set on ePMP radio -> from 1000kbps up to uplink/downlink maximum throughput
3. VLAN Switching e Manipulation (PASSED)
o C-VLAN managing enabled (802.1q) up to 4xVIDs (i.e. 500 for MNGT and 600, 700, 800 for payload) with different priorities values
o Payload traffic (natively untagged) is tagged with priority 3 on ingress port. On the contrary, MNGT traffic is tagged with priority 7
4. QoS management (PASSED)
o High Priority and Low Priority queues set on CAMBIUM equipment
o Default Priority Mapping and Serving Policy set on SIAE ALFOplus equipment
o Different ACM modes by reducing the RX power level on each radio link (i.e. emulation of propagation behavior)
o Different MIR values set on ePMP radio
5. In-Band MNGT (PARTIALLY PASSED -> see comments in last slide)
o MNGT traffic transported in “In-Band” mode with VID 500
o All equipment have been addressed within the same sub-network
o Remote reachability of all NEs from Cambium ePMP LAN interface (with VLAN tag 500)
o Remote reachability of all NEs from SIAE ALFOplus LAN 2 interface (w/o VLAN tag 500)
o Remote reachability of all NEs from a LAN port reserved for MNGT on Indoor Switch (w/o VLAN tag 500)

Gilat-Perù 4
 Bench Test Scenario
Main Site Hub Site #2 Hub Site #1 Terminal Site

ALFOplus Link #1 PTP450 Link #1 ePMP1000 Link #1

MNGT VID = 500, p7 PL PoE PoE PoE

PoE PoE
C_VID = 700, p3 PL
MNGT VID = 500, p7 PL MNGT VID = 500, p7 PL
C_VID = 700, p3 PL C_VID = 700, p3 PL

Untagged MNGT PL
Untagged MNGT PL

C_VID = 600,p3 PL Untagged DATA PL

Service #2 – Service #1 –
PORT #2 PORT #1 Payload Data
MNGT Data

Gilat-Perù 5
Bench Test Scenario
ALFOplus Link #1 PTP450 Link #1 ePMP1000 Link #1
(Air Connection) (Connectorized Connection)

SIAE External Switch Ethernet Tester Laptop for Remote MNGT

Gilat-Perù 6
IP Addressing of MW equipment
ALFOplus #1.1 ALFOplus #1.2 PTP450i#1.1 (BHM) PTP450 #1.1 (BHS) ePMP1000 #1.1 (AP) ePMP1000 #1.1 (SM)

IP: 192.168.79.5 IP: 192.168.79.6 IP: 192.168.79.4 IP: 192.168.79.3 IP: 192.168.79.7 IP: 192.168.79.8
MASK: /24 MASK: /24 MASK: /24 MASK: /24 MASK: /24 MASK: /24

SIAE switch

MNGT VID = 500, p7 PL MNGT VID = 500, p7 PL

Untagged MNGT PL

Local Laptop
Cluster Subnet: Default Gateway:
IP: Broadcast-1
MASK: /24 192.168.79.0 /24 IP: 192.168.79.1 /24

• Network access from NMS server through MNGT VLAN

• Access to local and remote equipment from the Local Laptop

Gilat-Perù 7
RADIO EQUIPMENT CONFIGURATION

Gilat-Perù 8
 Basic System Configuration – SIAE ALFOplus
• System Type
• Radio Model: ALFOplus GAIxxxx (2x10/100/1000baseT)
• Firmware Version: 1.4.4 (last version)
• System Configuration
• 802.1q: Fallback (all LAN ports)
• 802.1p: Enabled (all LAN ports)
• LANxPort: Transparent Bridge
• LAN 1 Default VID and Priority: 101 with p7
• LAN 2 Default VID and Priority: 102 with p7
• VLAN Table: not necessary in case of transparent transport
• STP: Disabled
• MTU size: 1700
• Auto-negotiation: Enabled
• QoS: Enabled
• P-bit Priority Mapping: factory default (Priority vs. Queue, i.e. p1 -> q1; p2->q2 ; …; p7->q7)
• Serving Policy: factory default (Strict Priority to all queues)
• Congestion Avoidance: factory default (Tail to all queues)
• LAN 1: In Band
• LAN 2: In Band
• MNGT VLAN: ID 500 with P-bit (L2) priority 7

Gilat-Perù 9
 Basic System Configuration – CAMBIUM PTP450
• System Type
• Radio Model: PTP450 (slightly different from PTP450i)
• Firmware Version: 15.0.1 (last version)
• System Configuration
• TDD Frame size: 5ms
• Uplink/Downlink ratio: 50%
• Data VLAN: Enabled
• Accept QinQ: Disabled
• QinQ EtherType: 0x88a8 (default value)
• Default Port VID: 1 (but not used since all incoming traffic is expected to be tagged only)
• Default Port Priority: 7 (but not used since all incoming traffic is expected to be tagged only)
• MTU size: 1700
• Ethernet Port Configuration: Enabled
• Port Speed: Auto
• Port Duplex Mode: Auto
• STP: Disabled
• QoS: Enabled
• VOIP Enable: Enabled
• QoS Table: VLAN 500 – High Priority Level
• Transport Mode: In Band
• MNGT VLAN: ID 500 with P-bit (L2) priority 7

Gilat-Perù 10
 Basic System Configuration – CAMBIUM ePMP1000
• System Type
• Radio Model: ePMP1000 at both sides (i.e. AP + AP set as SM)
• Firmware Version: 3.2 (last version)
• Switch Configuration
• TDD Frame size: 5ms
• Uplink/Downlink ratio: 50%
• Data VLAN: Enabled
• Default Port VID: 700 (to be agreed with the Customer)
• Default Port Priority: 3 (to be agreed with the Customer)
• VLAN Membership (VLAN table): Empty (unless tagged traffic different from VID and MNGT VLAN is expected)
• MIR: 10000kbits downlink / 10000kbits uplink (to be agreed with the Customer)
• MTU size: 1700
• Ethernet Port Configuration: Enabled
• Port Speed: Auto
• Port Duplex Mode: Auto
• STP: Disabled
• QoS: Enabled
• STA Priority: Low (to be agreed with the Customer)
• Broadcast Priority: Low Priority
• Multicast Priority: Low Priority
• VOIP Enable: Enabled
• QoS Table: onVLAN basis (i.e. 500) with High Priority Level
• Transport Mode: In Band
• MNGT VLAN: ID 500 with P-bit (L2) priority 7

Gilat-Perù 11
RESULTS AND CONCLUSIONS

Gilat-Perù 12
 BUGS AND FURTHER OBSERVATIONS
• DATA Plane:
• The ePMP radio works in auto-negotiation mode even in case the “manual” option is enabled
• Because a limited PPS (packet per second) rate on CAMBIUM radio, in case a huge amount of small-size packets is injected into the
radio, the most of them is then dropped by the radio PTP. This phenomenon is more evident in case of 64byte are sent out from the
tester
• In case of simultaneous activation of MIR limit and QoS management on ePMP radio and the injected traffic is significantly higher than
the MIR set, the packet dropping statistics turns out to be almost balanced (60% for High priority vs. 40% for Low Priority) among the
two streams regardless of their own inner L2 priority
• Very often whether the setup of a radio parameter is changed on CAMBIUM equipment, the radio alignment between local and remote
is lost and the traffic cut (both payload and MNGT) until the radio connection returns alive despite the change made should be “hitless”
(no system reboot or frame re-alignment)
• In case the VLAN data option is set in “Disabled” mode on the ePMP SM device, the untagged traffic at ingress port is not allowed to
pass through (to be further investigated for official confirmation)
• MNGT Plane:
• Depending on Laptop configuration, it could happen that the web browser interface won’t open for the ePMP radio even in case the
“ping test” on relevant IP via command prompt is successful
• All radio devices are unreachable from laptop connected to LAN port on ePMP SM radio even though the “Ethernet and Wireless”
option is enabled into MNGT connectivity section of ePMP AP radio

IMPORTANT NOTES:
• the above bugs and non-ideal behavior could be no longer true in case of use of different ePMP and PTP product models, e.g. ePMP
FORCE180 and PTP450i. Therefore, a further investigation is recommended before starting the network deployment
• due to unpredictability of CAMBIUM behavior whenever applying changes on the equipment configuration at both radio and switch levels, we
strongly suggest to setup in advance each device before to proceed with its installation. In order to do this, it’s worth to agree and standardize
with the Customer the main guidelines and relevant system parameters of all radio device involved

Gilat-Perù 13
Gilat-Perù