Cambium Networks V5000 Backhauled by V5000 DAC Cable User Manual

V5000 Backhauled by V5000 DAC Cable User Manual

V5000 Backhauled by V5000 DAC Cable

Figure 45: V5000 backhauled by V3000 using a DAC cable
Optical cable and connectors
Order an optical cable with LC connectors from a specialist fabricator, quoting the specification shown in the Optical optic cable and connector specification. It must be the correct length to connect the ODU to the other device. LC connectors should be supplied with dust caps to prevent dust build- up.
Figure 46: Optical optic cable and connector specification

Table 26: Optical cable part numbers

System Planning

Site planning
This section describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection, and equipment location for the ODU and PSU.
Grounding and lightning protection
Warning
Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this guide, when followed correctly, give the user the best protection from the harmful effects of EMD. However, 100% protection is neither implied nor possible.
Structures, equipment, and people must be protected against power surges (typically caused by lightning) by conducting the surge current to the ground via a separate preferential solid path. The actual degree of protection required depends on local conditions and applicable local regulations. To adequately protect a 60 GHz Wave installation, both ground bonding and transient voltage surge suppression are required.
Full details of lightning protection methods and requirements can be found in the International Standards IEC 61024-1 and IEC 61312-1, the U.S. National Electric Code ANSI/NFPA No. 70-1984, or section 54 of the Canadian Electric Code.
Note
International and national standards take precedence over the requirements in this guide.
Lightning protection zones
Use the rolling sphere method (Rolling sphere method to determine the lightning protection zones) to determine where it is safe to mount equipment. An imaginary sphere,  ypically 50 meters in radius, is rolled over the structure. Where the sphere rests against the ground and a strike termination device (such as a finial or ground bar), all the space under the sphere is in the zone of protection (Zone B). Similarly, where the sphere rests on two finials, the space under the sphere is in the zone of protection.
Figure 47: Rolling sphere method to determine the lightning protection zones

Warning
Never mount equipment in Zone A. Mounting in Zone A may put equipment, structures and life at risk.
Site grounding system
Ensure that the site has a correctly installed grounding system on a common ground ring with access points for grounding ODU.
If the outdoor equipment is to be installed on the roof of a high building, refer to the Installation section.
Ensure that the system meets the following additional requirements:

• A grounding conductor is installed around the roof perimeter to form the main roof perimeter lightning protection ring.
• Air terminals are installed along the length of the main roof perimeter lightning protection ring, typically every 6.1 m (20 ft).
• The main roof perimeter lightning protection ring contains at least two down conductors connected to the grounding electrode system. The down conductors should be physically separated from one another, as far as practical.

ODU location
Find a location for the ODU (and external antenna for connectorized units) that meets the following requirements:

• The equipment is high enough to achieve the best radio path.
• People can be kept a safe distance away from the equipment when it is radiating.
• The equipment is lower than the top of the supporting structure (tower, mast, or building) or its lightning air terminal.
• If the ODU is connectorized, select a mounting position that gives it maximum protection from the elements, but still allows easy access for connecting and weather proofing the cables. To minimize cable losses, select a position where the antenna cable lengths can be minimized. If diverse or two external antennas are being deployed, it is not necessary to mount the ODU at the mid-point of the antennas.

Drop cable grounding points
To estimate how many grounding kits are required for each drop cable, refer to site installation and use the following criteria:

• The drop cable shield must be grounded near the ODU at the first point of contact between the drop cable and the mast installation, tower or building.

• The drop cable shield must be grounded at the building entry point.
  For mast or tower installations installation, use the following additional criteria:

• The drop cable shield must be grounded at the bottom of the tower, near the vertical to the horizontal transition point. This ground cable must be bonded to the tower or tower ground bus bar (TGB) if installed.

• If the tower is greater than 61 m (200 ft) in height, the drop cable shield must be grounded at the tower midpoint, and at additional points as necessary to reduce the distance between ground cables to 61 m (200 ft) or less.

• In high lightning-prone geographical areas, the drop cable shield must be grounded at the spacing between 15 to 22 m (50 to 75 ft). This is especially important on towers taller than 45 m (150 ft).
  For roof installations, use the following additional criteria:

• The drop cable shield must be bonded to the building grounding system at its top entry point (usually on the roof).

• The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room.

ODU wind loading
Ensure that the ODU and the structure on which it is mounted are capable of withstanding the prevalent wind speeds at a proposed site. Wind speed statistics should be available from national meteorological offices.
The ODU and its mounting bracket are capable of withstanding wind speeds of up to 325 kph (200 mph).
Wind blowing on the ODU subjects the mounting structure to significant lateral force. The magnitude of the force depends on both wind strength and the surface area of the ODU. Wind loading is estimated using the following formulae:

• Force (in newtons) = 0.5 × ρ × V 2 × A × Cd
• V” is the density of air ( 1.225 kg/m 3 )
• V” is the wind speed in meters per second
• “A” is the projected surface area of the ODU in square meters
• “Cd” is the drag coefficient = 1.385.

The drag co-efficient has been measured when the cover plate or antenna is perpendicular to the air flow.
Applying these formulae to the brainwave ODU at different wind speeds, the resulting wind loading are shown in the following ODU wind loading (newtons) table:
Table 27: ODU wind loading (newtons)

Type of ODU

| Max surface area (square meters)|

Wind speed (km/h Newtons)

---|---|---
200*| 225| 250| 275| 300| 325
V1000| 0.017544| 67| 85| 105| 127| 151| 177
v3000**| 0.1764| 462| 583| 719| 871| 1036| 1216
V5000| 0.052597188| 118| 148| 185| 224| 266| 312

Equivalent results in US customary units are shown in following ODU wind loading (pounds force) table:
Table 28: ODU wind loading (pounds-force)

Type of ODU

| Max surface area (square meters)|

Wind speed (km/h lbf)

---|---|---
200*| 225| 250| 275| 300| 325
V1000| 0.017544| 15| 19| 24| 28| 34| 40
v3000**| 0.1764| 104| 131| 162| 196| 233| 273
V5000| 0.052597188| 27| 33| 42| 50| 60| 70

• 200 km/h is from measured data and used to calculate the remaining figures.
  Worst case setup with the product in -30° tilt position.
  PSU DC power supply
  Use Cambium Networks recommended DC PSU for wireless nodes and ensure the power cords and cables are appropriately rated and in accordance with the regulations of the country of use.
  PSU AC power supply
  Use Cambium recommended AC power supply for wireless nodes and ensure the power cords and cables are appropriately rated and in accordance with the regulations of the country of use.
  PSU location
  Find a location for the PSU that meets the following requirements:
  DC PoE power injector**

  • DC power injector can be mounted on a flat surface.
  • PSU is installed in a dry location where no condensation, flooding or rising damp is possible.
  • The PSU is located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling and placed not close to any fire source.
  • PSU can be connected to the ODU drop cable and network terminating equipment.
  • PSU can be connected to a compatible power supply.

Outdoor AC/DC PSU
Find a location for the PSU that meets the following requirements:

• The PSU is installed in a dry location where no flooding or rising damp is possible.
• The PSU is located in an environment where it is not likely to exceed its operational temperature rating, allowing for natural convection cooling and placed not close to any fire source.
• The PSU is not stacked and placed adjacent to the heat-generating equipment.
• The PSU shall be connected to protective earth.
• The PSU shall be connected to ODU drop cable using cable joiner and appropriately rated cables sould be used.

Lightning Surge Protection Units (LPU)

All drop cables connected to the ODU (e.g. PSU and AUX drop cables) requires their own Lighting Protection Unit (LPU) or Gigabit Surge Suppressor installed close to the ODU and close to the enclosure/building entry point. The copper SFP drop cable also requires surge protection. Optical cables do not require lightning surge protection or ground cables. Guidance on the positioning of required lighting surge protection is given in the Lightning Surge Protection Units Location.
Drop cable grounding points
To estimate how many grounding kits are required for each drop cable, use the following criteria:

• The drop cable shield must be grounded near the ODU at the first point of contact between the drop cable and the mast, tower or building.

• The drop cable shield must be grounded at the building entry point.
  For mast or tower installations, use the following additional criteria:

• The drop cable shield must be grounded at the bottom of the tower, near the vertical to the horizontal transition point. This ground cable must be bonded to the tower or TGB, if installed.

• If the tower is greater than 61 m (200 ft) in height, the drop cable shield must be grounded at the tower midpoint, and at additional points as necessary to reduce the distance between ground cables to 61 m (200 ft) or less.

• In high lightning-prone geographical areas, the drop cable shield must be grounded at the spacing between 15 to 22 m (50 to 75 ft). This is especially important on towers taller than 45 m (150 ft). For roof installations, use the following additional criteria:

• The drop cable shield must be bonded to the building grounding system at its top entry point (usually on the roof).

• The drop cable shield must be bonded to the building grounding system at the entry point to the equipment room.

Lightning Surge Protection Units location
Lightning Surge Protection Units or Gigabit Surge Suppressors must be installed at two points on drop cables:

• There is room to mount the LPU, either on the ODU mounting bracket or on the mounting pole below the ODU.

• The drop cable length between the ODU and top LPU must not exceed 600 mm.

• There is access to a metal grounding point to allow the ODU and top LPU to be bonded in the following ways: top LPU to ODU; ODU to a grounding system.
  Find a location for the bottom LPU that meets the following requirements:

• The bottom LPU can be connected to the drop cable from the ODU.

• The bottom LPU is within 600 mm (24 in) of the point at which the drop cable enters the building, enclosure or equipment room within a larger building.

• The bottom LPU can be bonded to the grounding system.

Deployment Considerations

This section provides a brief information specific to the deployment of 60 GHz cnWave series of products. This section covers the following topics:

• Key deployment guidelines
• Sector and alignment
• Minimum CN spacing
• Near-far radio
• Early weak interference
• Avoiding the tight angle deployment
• Avoiding the straight line interference
• When two V5000 devices are co-located at a site
• Polarity
• Link Adaptation and Transmit Power Control (LATPC)

Key deployment guidelines
Following are some of the key guidelines that you must consider for the deployment of 60 GHz cnWave series of products:

• Mounting accuracy: Cambium Networks has three different Stock Keeping Units (SKUs). These three SKUs have different requirements in terms of alignment coverage, as shown in Table 29.

Table 29: Details of alignment coverage – 60 GHz cnWave products

60 GHz cnWave product version| Azimuth (in degrees)| Elevation (in degrees)
---|---|---
V5000| +/-70 per sector| +/-20
V3000| +/-2| +/-1
V1000| +/-40| +/-20

• Minimum deployment distance: A typical minimum deployment distance is based on the maximum receive signal strength of -40dBm, as listed:
• 25 meters for V1000 and V5000
• 150 meters for V3000
• In case of deployments where the range is less than 25 meters (for V1000 and V5000) or 150 meters (for V3000), a short range or long range specific check box is provided in the user interface (UI) to allow this.
• Deployment frequency range: 60 GHz cnWave products support the use of CHG to CHI (channels).
  Deployment in these channels depends on the allowed channels in that region. Each channel is 2.16 GHz wide and the raster frequencies supported are – 58.32 GHz, 60.48 GHz, 62.64 GHz, and 64.8 GHz.

Sector and alignment

Each sector is an independent radio or a baseband unit. Each sector has 2 RF tiles connected to provide extended azimuth scan range, as shon in Figure 48.
Maximize the pole or box height during the deployment. This action minimizes the ground bounce and avoids channel fluctuations, especially for links with long distances. The suggested height is >5m.
You must consider the orientation of a DN node in PIMP. For example, orient the V5000 to the foresight of the RF tile to the longest link (where possible). The optimal beam angle to achieve the maximum antenna gain is at foresight of the active tile face (as shown in Figure 49 using the Red dotted line).
Figure 49: Optimal beam angle

Consider the following deployment specific points:

• Avoid sticking any metallic labels on the radome.
• The 60 GHz cnWave antenna tiles are located on the four marked faces.
• The GPS antenna is located at the middle of the top face of the radome that is pointed to the sky.

Minimum CN spacing
Consider the following key points for the minimum CN spacing at a sector intersction:

• Up to 15 CNs can be installed on a single sector. Time Division Multiple Access scheme (TDMA) dynamically schedules the time slots for each wireless link on an access point, such that they do not interfere with one another.
• When CNs are installed in multiple sectors, more than one CN can be talking at a given time as the sectors have independent schedulers.
  If both CNs installed in different sectors are located within the highlighted 20 degree range, then configure the two sectors to be on different channels to avoid interference.
  Figure 50 shows the minimum CN spacing at a sector intersection.

Near-far radio

Near-far ratio for links from different sectors on the same pole is based n the following factors:

• Scenario:
• One wireless link on DN sector 1 at long range, link 2
• One wireless link on DN sector 2 at short range, link 1
• Narrow angular separation between link 1 and link (less than 20 degrees)
• Configured for the same channel
• Problem:
• The TG system utilizes the active Transmit Power control.
• The transmit powers for link 1 is automatically set to a low level.
• The transmit powers for link 2 is automatically set to a high level.
• Due to narrow angular separation, the sidelobes of link 2 is interfered with link 1. As a result, the Signal-to-Noise Ratio (SNR) of link 1 could degrade and this might cause the transmit power of link 1 to be boosted to a much higher level. This problem ends up in a cycle resulting in both links eventually transmitting at full power by causing network interference.
• Solution:
• Perform traffic test on one link at a time and then simultaneously.
• If the simultaneous traffic results show degradation along with transmit power that is railed high to maximum, consider the following tasks:
  o Setting the two sectors on different channels or
  o Capping the maximum power of the short range link.

Figure 51 illustrates the problem and the solution for near-far radio.
Figure 51: Near-far radio – Problem and solution

Early weak interference
Early weak interference occurs when the receiver correlates to a preamble from an unwanted node, with the same Golay code (as desired). If the receiver starts decoding the preamble from the wrong node, it may be too late to recover the preamble from the correct node for that cycle.
Terragraph has four Golay codes to mitigate this interference. Users can select the Golay codes {1,2,3}.
Note
Golay 0 is used for another purpose. Therefore, avoid selecting the Golay 0 (The use of Golay 0 has been deprecated in System Release 1.2).
Consider the following points specific to the Golay codes in 802.11ad/ay:

• The 802.11ad/ay frame consists of PHY preamble, which consists of short training frame (STF) and Channel Estimation Symbol (CES).
• The STF and CES are made up of complimentary Golay codes. Due to the repetition of the Golay codes, the signal can be correlated with even low SNRs.
• This PHY preamble is used for frequency synchronization, timing synchronization, and channel estimation.

Avoiding the tight angle deployment

Avoid tight P2MP angles in the deployment for the following reasons:

• In Figure 52 (shown as an example), a downlink data transmission from the DN1 to CN1 can interfere with the uplink data reception at CN2 to DN2. This interference can be both down to main lobe in very tight angles or sidelobes with up to 20 degrees delta between two CNs.
• The level of interference depends on the link distances between DN1->CN1 versus DN->DN2 versus CN2->DN2.
• In most cases, the main interference is due to the early weak interference.
• To mitigate this early-weak interference, different Golay code assignment could be used. This issue only relates to the two links transmitting at the same time in the same physical direction.

Avoiding the straight line interference
It is recommended to avoid the straight line interference. When the desired link and interference link angles are the same, there is no assistance from the beam forming interference suppression.
It is recommended to assign appropriate Golay codes to mitigate early-weak interference. In Figure 54, the red and orange arrows show the possible weak interference. The code assignment must be in the form of 2-2-1-1 or 1-1-2-2 but not in the 1-2-1-2 form.

When two V5000 devices are co-located at a site
When two V5000 devices are co-located at the same site, it is recommended that one must use different channels on the two V5000 devices to start with.
Evaluate the issues specific to near-far radio and Tight Angle deployment. Then, you have to configure two different channels for the two sectors or consider option 2, as shown in Figure 55.
Figure 55: When two V5000 devices are co-located at the same site

Where local regulations allow the usage of four channels, it is advisable to choose CHA and CHB such that there are two channels apart. Example: Consider that CHA = 1 or 2 CHB = 3 or 4. The reason is that it may be easier to upgrade to Channel bonding (CB2) in the future and still experience the channel isolation.
Note
It is important to use the same polarity at the same site. For more details about the polarity, refer to the Polarity section.

Polarity

60 GHz CnWave uses TDD, which is synchronized across the network. As one sector is in the transmit phase, the neighbor sector is in the receive phase. The transmit and receive phases of the sectors are determined by the EVEN or ODD polarity.
All sectors with a common polarity in a network could be transmitting or receiving at the same time.
Hybrid polarity is when a node uses an EVEN polarity on one sector and an ODD on another sector.
Although the hybrid polarity is possible through configuration, you must avoid this unless the installer is sure that the two links on the sectors are orthogonal. Figure 56 shows an example of the hybrid polarity.
Link Adaptation and Transmit Power Control (LATPC)
The modulation and code scheme (MCS) rate and transmit power are both adaptive values. These values are set at the transmitter, independently, for every link and for both directions. The adaptive MCS selection procedure is referred to as link adaptation (LA) and the transmit power procedure as transmit power control (TPC).
There are two versions of this adaptation, data traffic, and standby, as described:

• When there is data traffic, adaptation is driven by block error rate (BLER) reported every SF (1.6ms). A lower BLER causes the algorithm to adapt the transmit power or MCS
•  When there is no data traffic, the algorithm is driven by the short training frame (STF) SNR as reported by each management packet. The SNR is compared to an MCS table. If the SNR is greater or lesser than table value, the transmit power or the MCS rate is adapted accordingly.

There is a maximum TX power per MCS mode (which is defined in the configuration section).
During the adaptation process, the transmit power is either increased or decreased first to:

• increase the power till the maximum per MCS power is reached or
• reduce the power if there is enough headroom.

If the maximum power for the MCS mode has been reached, the MCS mode is reduced.

Radio spectrum planning

General wireless specifications
The following 60 GHz cnWave wireless specifications (all variants) table lists the wireless specifications that apply to all 60 GHz cnWave frequency bands:
Table 30: 60 GHz cnWave wireless specifications (all variants)

maximum EIRP can be set lower than the default power limit.
Integrated antenna type| •V3000 44.5 dBi gain and 40.5 dBi gain
•V1000 22.5 dBi gain
Duplex schemes| Symmetric 50:50 fixed and asymmetric fixed
Range| 100 m to 2 KMs, depends on the following factors:
•Frequency selected
•Rain condition
•Availability
•EIRP limitation
Over-the-air encryption| AES 128-bit
Weather sensitivity| Highly sensitive due to rain range conditions. For more information in range, refer .
Rain and attenuation table.

Regulatory limits

Many countries impose EIRP limits (allowed EIRP) on products operating in the bands used by the 60 GHz cnWave. These are commonly identified by limitations on conducted transmit power or by antenna gain. For example:
Table 31: ERC recommendation (70-03)

transmit power of 27 dBm at the antenna port/ports.
c3| 57-71 GHz| 55 dBm E.I.R.P., 38 dBm/MHz E.I.R.P. density and transmit antenna gain >30 dBi.

CFR47 Part 15.255(c)(ii):
For fixed point-to-point transmitters located outdoors, the average power of any emission shall not exceed 82 dBm and shall be reduced by 2 dB for every dB that the antenna gain is less than 51 dBi. The peak power of any emission shall not exceed 85 dBm, and shall be reduced by 2 dB for every dB that the antenna gain is less than 51 dBi.
Link planning
This section describes factors that must be considered when planning links, such as range, obstacles path loss, and throughput. It is highly recommended to use Cambium LINKPlanner software when planning the links.
LINKPlanner
The Cambium LINKPlanner software and user guide may be downloaded from the support website (see https://support.cambiumnetworks.com/files/linkplanner/ ).
LINKPlanner imports path profiles and predicts data rates and reliability over the path. It allows the system designer to try different antenna heights and RF power settings. It outputs an installation report that defines the parameters to be used for configuration, alignment, and operation. Use the installation report to compare predicted and actual link performance.
Exclusion zones for the 59 – 63.9 GHz band
In the three geographical areas outlined in 59 – 63.9 GHz Transmission Exclusion Zones (UK IR 2078 Section 4 and IR 2030 IR2030/7/4 (2018/316/UK)), no transmissions are permitted.
Table 32: 59 – 63.9 GHz transmission exclusion zones

Site Name| Site Location|

Radius of exclusion zone from the center of site location

---|---|---
Site 1| 07° 23’ 36.6” W, 57° 21’ 3.6” N| 6 Km
Site 2| 04° 58’ 21” W, 51° 37’ 16.8” N| 6 Km
Site 3| 00° 36’ 22.8” W, 52° 38’ 1.8” N| 6 Km

Range and obstacles
Calculate the range of the link and identify any obstacles that may affect radio performance.
Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to assess the risk of interference. This information is necessary to achieve an accurate link feasibility assessment. The 60 GHz cnWave radios are designed to operate in Line-of-Sight (LoS) environments.
The 60 GHz cnWave radios operate at ranges from 15 m (49 ft) to 2000 m (1.2 miles). The operation of the system depends on the frequency channel chosen.
Path loss
Path loss is the amount of attenuation the radio signal undergoes between the two ends of the link. The path loss is the sum of the attenuation of the path if there were no obstacles in the way (Free Space Path Loss), the attenuation caused by obstacles (Excess Path Loss) and a margin to allow for possible fading of the radio signal (Fade Margin). The following calculation needs to be performed to judge whether a particular link can be installed:

Table 33: Input details for the link calculation

At 60 GHz cnWave the oxygen absorption is a key component of the free space path loss and varies substantially depending on the frequency channel selected. Use LINKPlanner to calculate the oxygen absorption component for the required path and frequency channel.

Data network planning

This section describes factors to be considered when planning 60 GHz cnWave data networks.
60 GHz cnWave network can be deployed as point-to-point backhaul-bridge, Point-to-Multipoint coverage network and mesh network that provide network rebound. Regardless of the network topology, the underlining routing protocol between cnWave radios is always IPv6 with OpenR routing protocol.
By default, the cnWave operates in IPv6 layer 3 network mode, requiring IPv6-based routing gears etc.
While underlying routing in the cnWave network relies on IPv6 OpenR routing, the network can be designed to operate in pure IPv4 network mode, transporting layer two traffic (VLAN tagged and untagged) with GRE tunnels built-in by the system.
There is no fundamental difference between configurations of PTP vs. PMP vs. Mesh because the underlying routing mechanism of the cnWave network is always IPv6-based OpenR routing.
In a PTP network, you have one PoP DN and a CN to form a link. In a PMP network, you have one PoP DN and multiple CNs (up to 30 CNs if V5000 is used) to form a PMP cluster. You can have multiple PMP clusters to form a coverage area network.
Users can have one PoP node with multiple DNs or CNs. If DNs are connected, the user gets a mesh network. User can them have multiple PoPs and DNs and if the link with each other and form a complex mesh network.

Point to Point-based single link Ethernet bridge

A Point to Point cnWave link can be configured to work as an Ethernet bridge. The operator needs to configure one end as PoP DN, and the other end as CN.
Enable Layer 2 Bridge. While the radios still run on IPv6, the Layer 2 Bridge configuration allows user Layer 2 data (VLAN tagged and untagged) to be transmitted transparently through the link.
IPv6 address of the PoP and CN can be automatically generated and they do not need to be routable through the external network as long as the E2E is collocated with the PoP DN or within the same VLAN of the PoP DN. The operator can assign IPv4 addresses to the radios for management purposes.

IPv4/L2 based PMP and mesh network planning

The operator can build a complete IPv4-based network without the need for any IPv6 routers. The following figure shows the network:

60 GHz cnWave IPv6 IP address is generated automatically by the system.

1. Single PoP, E2E resides in the PoP DN When configuring the PoP E2E, the operator can configure the IPv6 address to be generated automatically.
2. Multiple PoPs, E2E controls all the PoPs cnMaestro generates the IPv6 configuration for all the PoPs. The user can download the config file from cnMaestro. This config file contains all the PoPs IPv6 configuration. The IPv6 configuration is associated with the MAC address of each PoP DN. When loading the config file to the PoP DN during initial configuration, the PoP DN chooses the IPv6 address by matching its MAC address, so there is no IPv6 address conflict.
   The PoP DNs automatically use the E2E controller as the default gateway of IPv6 traffic. Since IPv6 traffic is used only for management purposes, there may be no concern about overloading the E2E. (IPv6 payload traffic should be disabled in the radio configuration).
   The E2E chooses any one of the active PoP DN as the IPv6 default gateway. If the E2E detects that the default gateway PoP DN is down, it selects another PoP DN as a default gateway. Control traffic from E2E to all cnWave radios will be sent to the default gateway PoP, which relies on OpenR to route through correlated POP to the target radio. Select the Relay Port Interface for the PoP DN’s Ethernet interface for inter-PoPs OpenR routing to work.

Note
IPv6 routers in the network are not required. Ensure that the PoP DNs and the E2E be in the same VLAN.
Configure the IPv4 address of the radios manually. The CPE IPv4 address can be manually configured or use a DHCP server sitting in the core network. Depending on the complexity of the network, IPv4 based router may be required to route the IPv4 traffic from the CPEs.
Mixture of IPv4 and IPv6 support
The operator can design the network so that both IPv4 and IPv6 user data are supported. In this case, an IPv6 router is required at the core network. Ensure that if Layer 2 Bridge is enabled, by default all the user traffic including IPv6 is encapsulated in the GRE tunnel. The IPv6 user traffic is passed through the cnWave network in the GRE tunnel so that it does not be routed by the cnWave radios, but rather by an external IPv6 router.

The operator can choose certain of the radio Ethernet port to be SLAAC based port or (CPE interface), user traffic from this port is only IPv6 based and does not be encapsulated into the GRE layer two bridge when transmitted over the wireless network. Although this reduces overhead, it is not recommended since this adds complexity to the network design (the operator may need to add a BGP router to the network).

IPv6 Mode network planning

If the operator chooses to have the network completely run on IPv6 mode, then GRE Layer 2 Bridge is not required and a BGP router is usually required to route traffic between the wireless network and the external network.

IPv6 Network design consideration
There are two sets of networks while designing the IPv6 network. one set is for the OpenR subnets (e.g. prefix of 56 bits and partition into multiple 64 bits subnet). Each cnWave node is assigned with a subnet. Each PoP node, besides being part of the OpenR mesh network, has a subnet assigned to it and has an IPv6 address assigned to it as PoP interface IPv6 address.
If the operator lets the system automatically generates IP address configuration, the IP address always be in the format of FD00:xxxxxxx, which is a standard routable private IPv6 address.

Reserved IPv6 address space
If the operator let the system automatically generate the IPv6 addresses for the network, the following private IPv6 address spaces are reserved:

• FD00:CEED::0/32 for seed prefix of the mesh network
• FD00:BA5E::0/32 for all the PoP nodes and the E2E Controller

E2E and cnMaestro deployment consideration
While the E2E and cnMaestro are two separate entities, they can be hosted on separate computers or the same computer. While the E2E communicates with the cnMaestro using IPv4, the E2E communicates with the cnWave radios using IPv6.
Ethernet bridging or IP routing
Layer2 Bridging
L2 Bridge employs Ethernet over GRE (EoGRE) to carry the customer traffic across the Terragraph network. when L2 Bridge is enabled, all CNs and DNs automatically create an EoGRE tunnel with their PoP node and the PoP node creates a tunnel back to each of those CNs/DNs. The tunnel is capable of carrying both IPv4 and IPv6 customer traffic between CN and PoP. The IPv6 over the tunnel can be optionally disabled from the UI.
Broadcast/Multicast control
The downstream broadcast can be controlled by explicitly disabling it from the UI. Disabling IPv6 over the tunnel also reduces the downstream multicast traffic.
Limitations

• In bridge mode, the V5000 PoP node can forward 1.8 Gbps of TCP traffic and 2.0 Gbps of UDP traffic in the down-link direction.

Layer 2 Bridge support in multi-PoP deployments
Note
Multi-PoP deployment is not recommended if on board E2E is enabled.
This feature applies to Layer 2 bridging and Deterministic Prefix Allocation (DPA) are configured to be used in the network.
In the Terragraph network, CNs and DNs are allocated prefixes from a seed prefix. There are various ways for allocating prefixes. In DPA, the controller assigns prefix zones to PoPs based on the network topology to allow PoP nodes to take advantage of summarizing the route and helps in load balancing ingress traffic.
CNs and DNs get prefixes from the respective PoP zone which is allocated by the controller. CNs and DNs see multiple PoP nodes in the mesh, they select PoP to form GRE tunnel, by matching their lo IPv6 address with PoPs lo IPv6 address. The longest prefix match is selected as the best PoP for L2 GRE
Tunnel establishment. The multi-PoP setup gives the advantage that user data traffic can take alternate routes if the best route is unavailable for some reason. Open/R makes this selection to route the traffic. If PoP is unavailable, CNs and DNs switch to the next best PoP. They however keep track of their primary PoP availability and switch to it once it becomes online.
External Layer 2 Concentrator support
The external device can be used as an L2 GRE Concentrator. Concentrator could be a Linux server or any router or switch supporting IPv6 L2 GRE tunnels. Example: Juniper MX 100.
Select the Static tunnel concentrator option and provide an IPv6 address to configure the external concentrator IPv6 address.
Figure 62: Layer 2 Tunnel Concentrator

Multi-PoP deployments
The following aspects must be taken care of in cnWave multi-PoP deployments:

• Layer 2 domain
• Open/R on the PoP interface port
• MTU of upstream switch ports
• Prefix allocation

Layer 2 domain
All cnWave PoP nodes must be connected to the same Layer 2 broadcast domain. PoP nodes learn about other PoP nodes using IPv6 multicast packets, which do not cross broadcast domain.
This allows cnWave PoP nodes to forward traffic to other cnWave PoP nodes via a wired connection when the routing path of the other PoP node is closer to the traffic’s destination. This concept is called Tromboning, as the traffic enters one PoP node and then leaves to another PoP node.
Open/R on the PoP interface port
PoP interface port must be configured to run the Open/R protocol. To enable this option, select MultiPoP/
Relay port Interface.
MTU of upstream switch ports
PoP ports use a 2000 MTU size. So, all the switch ports must be at least 2000 MTU size. Even if the user traffic is limited to 1500 sized packets, switch ports should allow the higher MTU size. The following packets exchanged between the PoPs that can be of higher size:

• Open/R packets,
• L2GRE packets (in Layer 2 mode), and
• Software download packets.

Prefix allocation
It is recommended to select the Deterministic Prefix Allocation option for multi-PoP deployments.

Layer two control protocols

60 GHz cnWave identifies layer two control protocols (L2CPs) from the Ethernet destination address or Ethertype of bridged frames. The QoS classification can be separately configured for these protocols.
Ethernet port allocation
The user must decide how the three ODU Ethernet ports are allocated to the data service, management service and Local Management Service based on the following rules:

• Map the Data Service to at least one of the available wired Ethernet ports.
• Map the Management Service to In-Band, or any combination of the remaining unused Ethernet ports. If the Management Service is mapped to In-Band, it shares all the ports selected for the Data Service. The Management Service can be disabled by mapping to None.
• Map the Local Management Service to any combination of the remaining unused Ethernet ports.
  The Local Management Service can be disabled by mapping to None.
  The LAN configuration page ensures that the management agent can always be reached using either the management service or the local management service.

IP Interface
Select the IP version for the IP interface of the ODU management agent. 60 GHz cnWave can operate in IPv4 mode (via L2 tunneling), IPv6 mode. Choose one IPv4 address and/or one IPv6 address for the IP interface of the ODU management agent. The IP address or addresses must be unique and valid for the connected network segment and VLAN.
Find out the correct subnet mask (IPv4) or prefix length (IPv6) and gateway IP address for this network segment and VLAN.
Ensure that the design of the data network permits bidirectional routing of IP datagrams between network management systems and the ODUs. For example, ensure that the gateway IP address identifies a router or another gateway that provides access to the rest of the data network.
Daisy-chaining 60 GHz links
When connecting two or more 60 GHz cnWave links together in a network (daisy- chaining), do not install direct copper CAT5e connections between the PSUs. Each PSU must be connected to the network terminating equipment using the LAN port. To daisy-chain 60 GHz cnWave links, install each ODU-toODU links using one of the following solutions:

• A copper CAT5e connection between the Aux ports of two ODUs.
• A copper CAT5e connection between the Aux port of one ODU and the SFP port of the next ODU (using a copper SFP module).
• Optical connections between the ODUs (SFP ports) using optical SFP modules at each ODU.

Installation Safety

Warning
To prevent loss of life or physical injury, observe the following safety guidelines. In no event shall Cambium Networks be liable for any injury or damage caused during the installation of the Cambium 60 GHz cnWave radio nodes. Ensure that only qualified personnel install 60 GHz cnWave radios.
Power lines
Exercise extreme care when working near power lines.
Working at heights
Exercise extreme care when working at heights.
PSU
Always use one of the approved power supply options. Failure to use the Cambium supplied PSUs can result in equipment damage and will invalidate the safety certification and may cause a safety hazard.

Grounding and protective earth

The cnWave radios must be properly grounded to protect against lightning. It is the user’s responsibility to install the equipment in accordance with national regulations. In the USA follow the requirements of the National Electrical Code NFPA 70-2005 and 780-2004 Installation of Lightning Protection Systems.
In Canada, follow Section 54 of the Canadian Electrical Code. These codes describe correct installation procedures for grounding the outdoor unit, mast, lead-in wire, and discharge unit, size of grounding conductors, and connection requirements for grounding electrodes. Other regulations may apply in different countries and therefore it is recommended that installation of the outdoor unit be contracted to a professional installer.
AC Supply
Always use an appropriately rated and approved AC supply cord-set in accordance with the regulations of the country of use.
Powering down before servicing
Before servicing 60 GHz cnWave equipment, always switch off the power supply and unplug it from the PSU.
Do not disconnect the RJ45 drop cable connectors from the radio while the PSU is connected to the power supply. Always remove the AC or DC input power from the PSU.
Primary disconnect device The primary disconnect device is the main power supply.
External cables
Safety may be compromised if outdoor rated cables are not used for connections that are exposed to the outdoor environment.
Drop cable tester
The PSU output voltage may be hazardous in some conditions such as wet weather. Do not connect a drop cable tester to the PSU, either directly or via LPUs.
RF Exposure near the antenna
Strong Radio Frequency (RF) fields are present close to the antenna when the transmitter is ON. Always turn off the power to the radio before undertaking maintenance activities in front of the antenna.
Minimum separation distances
Ensure that personnel is not exposed to unsafe levels of RF energy. The units start to radiate RF energy as soon as they are powered up. Never work in front of the antenna when the radio is powered. Install the radios to provide and maintain the minimum separation distances from all persons. For minimum separation distances, see Calculated distances and power compliance margins.
Grounding and lightning protection requirements
Ensure that the installation meets the requirements defined in the Installation section.
Grounding cable installation methods
To provide effective protection against lightning-induced surges, observe these requirements:

• Grounding conductor runs are as short, straight and smooth as possible, with bends and curves kept to a minimum.
• Grounding cables must not be installed with drip loops.
• All bends must have a minimum radius of 200 mm (8 in) and a minimum angle of 90°. A diagonarun is preferable to a bend, even though it does not follow the contour or run parallel to the supporting structure.
• All bends, curves and connections must be routed towards the grounding electrode system, ground rod/ground bar.
• Grounding conductors must be securely fastened.
• Braided grounding conductors must not be used.
• Approved bonding techniques must be used for the connection of dissimilar metals.

Siting radios
Radios are not designed to survive direct lightning strikes. For this reason they must be installed in Zone
B as defined in Lightning protection zones. Mounting in Zone A may put equipment, structures, and life at risk.
60 GHz cnWave radios and mounting bracket options Mounting bracket options
The 60 GHz cnWave series supports eight mounting bracket options. Select the optimum mounting bracket arrangement based on the ODU type and the choice of wall or pole mounting. The wall mount plate for V1000 and V5000 are included with the ODU. Order the remaining brackets separately.
Table 34: ODU mounting bracket part numbers

Bracket| Pole diameter| ODU variants|

Bracket part number

---|---|---|---
V1000 pole mount| 25 mm to 70 mm (1 inch to 2.75 inches)| V1000| Included with V1000
V1000 wall mount| Wall mount| V1000| Included with V1000
V1000 adjustable pole mount| 25 mm to 70 mm (1 inch to 2.75 inches)| V1000| N000900L022A
V3000 precision bracket| 25 mm to 70 mm (1 inch to 2.75 inches)| V3000| C000000L125A
V3000 tilt bracket assembly| 25 mm to 75 mm (1 inch to 3 inches)| V3000, V5000| N000045L002A
V3000 tilt bracket assembly with band clamps| The diameter range depends on the clamps used.| V3000, V5000| N000045L002A + third-party band clamps
V5000 pole mount| 25 mm to 75 mm (1 inch to 3 inches)| V5000| C000000L137A
V5000 wall mount| Wall mount| V5000| C000000L136A

Installing the cnWave radio nodes
To install the radio, use the following procedure and guidelines:

1. Typical installation
2. ODU interface with LPU on the pole
3. SFP and Aux Ethernet interfaces
4. Attach ground cables to the radio
5. Mounting the ODU on the mast or wall

Typical installation
V1000
V1000 typical installation figure shows a typical installation of cnWave CN on a mast and powered through PoE Power Injector.

1. Use recommended grounding and Surge Suppressor connections.
2. Use recommended cables for interfacing ODU (refer to the supported power supply and cable length details in the Power supply units (PSU) section).
3. Always install ODU 0.5 meters below the tip of the pole.

References

• Log In / Cambium Networks Support

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>