FAQ

FAQ - MetroLinq - How do I download the Troubleshooting Logs?

Upon contacting support for assistance, you may be asked to retrieve the troubleshooting logs. These files contain the configuration, link, and log information often needed to discover the root cause of a problem. Below are the steps to retrieving these files. From the web GUI 1. Navigate to "System". 2. Select "Maintenance". 3. Click on the "Troubleshooting Log" button to download the files. Image: https://ignitenet.uservoice.com/assets/106836594/MLTSfilesWebgui.png From the Cloud 1. Navigate to "Devices". 2. Click on the appropriate device. 3. Click on the "Live Actions" drop-down menu. 4. Select "Fetch troubleshooting File". 5. Once the troubleshooting file task has been started, navigate to "Maintenance" in the Device Menu. 6. Click on "Download file".

FAQ - MetroLinq - Does MetroLinq support VLAN?

Yes, MetroLinq will allow VLAN traffic to pass through, and the MetroLinq also has a Management VLAN option that can be enabled in the Network -> Internet Settings. Note that the MTU size must be increased accordingly.

FAQ - MetroLinq - Does MetroLinq require Line-Of-Sight between devices?

Yes, MetroLinq requires Line-Of-Sight for the link to work properly.

FAQ - MetroLinq- Can I reset my Metrolinq to factory defaults via SSH?

Yes, you can reset your MetroLinq to factory defaults via the SSH by: 1. SSH into the device with your administrator user name and password (default pair is "root", "admin123" respectively). 2. Use the command "reset_to_defaults.sh -y" to reset your device.

FAQ - MetroLinq - What are the channel bandwidths supported by the MetroLinq's 60 GHz and 5 GHz radios?

For the 60 GHz radio, we support 2000MHz channels. For the 5 GHz radio, we support 20, 40, and 80 MHz channels.

FAQ - MetroLinq - What are the antenna beam-widths for the MetroLinq product line?

The antenna Beamwidths are: - 1 degree(s) for ML-60-35-XX - 3 degree(s) for ML-60-19-XX - 30 degree(s) for ML-60-30-18-XX -120 degree(s) for ML- 2.5G 60-BF-18

FAQ - MetroLinq- Do I need the aiming scope for my MetroLinq?

While not required, the MetroLinq Alignment Scope, ICC-SCOPE-9X50, significantly lessens the challenge of antenna alignment by providing accuracy during deployments, installations, and ongoing operations. Initial antenna position is critical during MetroLinq deployments and upgrades alike. The MetroLinq Alignment Scope saves time and money by helping to eliminate costly site re-visits and re-climbs, and is therefore highly recommended, especially for longer links.

FAQ - MetroLinq- What is the Fresnel Zone for the 60 GHz MetroLinq radio?

The Fresnel Zone represents a series of regions in which surfaces will cause a reflected wave, phase shifted by some amount, to constructively or destructively interfere with the desired Line-Of-Sight (LOS) signal at the receiver. These concentric ellipsoidal regions (F1, F2, F3, etc) of radius R -- the first (F1) having the smallest R -- are centered on the direct transmission path between two radios (Figure 1). The total phase difference between the line of sight signal and the reflected signal is determined by factors such as the shape and properties of the obstruction as well as the polarization of the incident wave. Additionally, obstructions can cause diffraction and other undesirable effects. The higher the Fresnel Zone number, the larger R is, the farther a reflected signal travels before interfering, and therefore the weaker its effect is. We are thus mostly concerned about F1. If a significant portion of F1 is obstructed, the signal at the receiving antenna can be greatly attenuated. A general rule of thumb is that to avoid the significant signal blockage, diffraction or multi-path attenuation (for your link to behave as LOS), you need at least 60% of F1 clear of obstructions, where "60% of F1" is defined as a narrower ellipsoid with a radius that is 60% of the radius of F1. Image: https://ignitenet.uservoice.com/assets/124826899/FresnelZone.png Figure 1: Fresnel Zone (not to scale) The radius of F1 is dependent upon the frequency and distance of the link, and therefore it is calculated for 62 GHz at multiple distances below: Image: https://ignitenet.uservoice.com/assets/107117070/Fresnel%20Zone.png

FAQ - MetroLinq - What SNMP versions are supported?

SMNP v1 and v2.

FAQ - MetroLinq- What is the temperature range for MetroLinq radios?

Between -40 °C to +70 °C.

FAQ - MetroLinq - What is the maximum transmit power?

The absolute maximum values are 14 dBm (25mW) @ 60 GHz and 28 dBm (630mW) @ 5 GHz, but the transmit power available to a particular user may be governed by his/her country's regulations.

FAQ - MetroLinq- Can I use the second GE port of the ML for traffic purposes?

The second Ethernet port is bridged to the 60 GHz interface, but not the other Ethernet port. You can therefore pass traffic over the link, but you will not be able to see devices connected to the Eth0.

FAQ - MetroLinq- Can I use any ML device as a STA in a PTMP setup?

Yes. Typically the client devices for the PtMP scenarios are the models ML-60-35 and ML-60-19.

FAQ - MetroLinq - What is the maximum cable distance between the PoE injector and the MetroLinq?

The maximum recommended distance is 100 m using Cat 5e.

FAQ - MetroLinq- What separation distance I have to give to my MetroLinq radios installed on the same pole?

We recommend a separation of 0.5m/1.6ft.

cloud or on-premise hotspot?

Generally cloud hotspot deployment (cloudx design or some other 3rd-party cloud-based hotspot offering) is recommended for small sites, eg. F&B/Retail outlets, where there're less amount of users; and on-premise (on-premise design) is recommended for larger venues, eg. hotels, malls, stadiums and airports etc. Much of the consideration are on user experience and solution costs. Below table gives an overview on the key differences. Differences\Mode Cloud hotspot On-premise hotspot User experience This very much depends on Internet backhaul speed & performance. Generally, for smaller sites with less users and high Internet speed, this will work well. But for large number of concurrent users, due to Internet latency and potential link congestion, the login portal loading and authentication can be slow. Some devices may be unable to load portals or authentication fail due to timeout etc. Especially if local Internet link is not good, the result can be really bad. Another big dependency is where the portal is hosted, if it's hosted in a remote country without direct Internet peering with local ISP, extra latency will be multiplied. This mode works very well for all situations, because the portal is hosted locally "on-premise" inside the local gateway and authentication is done locally on HSG, the responses are fast (through local WLAN), without dependencies or effects of slow Internet. Cost consideration For small site, each location may just require HSA or small HSG, or some 3rd-party AP directly integrates with cloud portal provider, the hardware cost per site is minimized. For large site, where they're many APs, some cloud providers charge on per AP subscriptions, the total cost of ownership over a period can be significantly high, due to recurring high subscription costs. There's a one-time substantial cost for the gateway, but there's no hidden/subscription cost per AP. So it's easy to calculate long-term TCO, which is usually more cost-effective. Especially for large sites with many APs, the spreaded HSG cost (over many AP) is very minimum. Security The user data is hosted in the cloud platform. If it's your own/private cloud, eg. having HSG at DC/HQ, then it's OK; if you're using 3rd-party/external cloud provider, there's a considering on data security. Some organization security policy do not allow customer/user information hosted in 3rd-party or shared cloud servers, therefore you may fail security audit. And you are also at mercy of relying on external provider to secure your customer data. Some countries government cyber security law requires all user/customer data to be "in-country", so it's a definite no-no to use providers hosted outside your home country. The user data are kept and stored inside your own HSG gateway, which is well-secured and isolated for your own use, and you can control and safeguard customer data based on your company policy. It's also good for compliance purpose. Each of management If using HSA, they can be centrally managed by mfusion, for all device/portal/user management. So this is very easy. If using 3rd-party AP, usually you will need to access different management systems for AP, and another one for portals/users. Allows local management of users/portals, and central management of HSG. Very simple and efficient.