Lidar Unit Troubleshooting

Lidar Unit Troubleshooting

            1.0            Introduction

 

This document will detail common issues with Lidar units and how to resolve them. All Lidars are segregated onto a separate network for security purposes, this is done via software called Forescout.

 

The mac addresses of the Lidars are loaded into Forescout and when they are plugged into the network, Forescout identifies the switch port the unit is plugged into and then assigns the Lidar network VLAN, this process is automated and takes roughly 1-2 minutes to apply.


       2.0            Lidar Network Information

 

Listed below are the subnet details for the Lidar network, please ensure these details are correct when applying an IP address, incomplete IP addresses will prevent access to a unit e.g. no DNS servers have been entered.

 

IP ranges - 10.10.20.0 -> 10.10.20.253 & 10.10.21.0 -> 10.10.21.254

Subnet mask: 255.255.254.0

Default Gateway: 10.10.20.254

DNS - 10.10.4.1

DHCP Range: 10.10.21.235-254

      3.0            Unable to ping unit – Basic checks

 

A common issue is being unable to ping the unit, however it is visible in Waltz, please ensure the following checks have been carried out before contacting IT:

 

1.       Change the ethernet cable

2.       Try a different network\switch port

3.       Change the IP address of the unit to ensure it’s not conflicting with another unit

4.       Restart the unit

5.       Check internal network cable

 

There is an internal cable from the motherboard of the unit, on occasion this can loose or unplugged.

 

Confirm the wall port is OK by plugging your laptop in, if you get an IP address this proves the port is patched and working. You can also try another unit, and this will achieve the same thing as using your laptop.

 

You can check the state of the unit by connecting via wireless, opening the network adaptor settings, and checking, if the status is set to “Network Cable” unplugged then there is a physical fault.


      4.0            Unable to ping a unit – Advanced Checks

 

RDP to a working unit, open a command prompt and ping the IP address of the unit having issues.

 

If you can ping the IP address and get a successful reply then this confirms the unit is online and contactable via the network and points to one of the following issues:

4.1 Check Default Gateway

 

Default gateway is incorrect – to check this, open the network adapter settings and confirm the default gateway is present:



If there is no gateway, enter the one above.

4.2 Firewall is set to local subnet only

 

Unit firewall is set to “Local Subnet”

 

Open the control panel and select “View by” in the top right-hand corner, change the view to “Small Icons”, then click on “Windows Defender Firewall”:


On the left-hand side locate and click on “Advanced settings”:



Click on “Inbound Rules” in the top left-hand corner:


Scroll down and locate the following rule name, please note this rule will appear twice and both rules need to be checked and amended:

File and Printer Sharing (Echo Request – ICMPv4-In)


Once you have located the rule, double click on it and click on the “Scope” tab, if the bottom

section labelled “Remote IP address” is set to “Local Subnet” tick the box and set it to “Any

IP address”:

Before:


After:


4.3 Check Waltz connection type

 

Confirm Waltz is set to the correct connection type:

 

If Waltz is set to “Use internal modem only” this can cause issues with the unit, and you may find that after rebooting the unit pings for a period of time and then it isn’t contactable:


Change this to the below:



4.4 VPN is connected

 

If the unit has a VPN connection that has connected then this is can take priority and cause issues talking to the unit over the network.

 

To resolve this open the network adaptor settings and located the VPN, in the example below it was called “WI”:




Right click and select “Connect\Disconnect”, this will open the settings and then click disconnect:




Should you continue to have issues after following all the checks in this document please contact IT Support via the below methods, please ensure that you have the following information:

 

·         Unit location e.g. Patio

·         IP address  e.g. 10.10.20.53



    • Related Articles

    • Softphone Troubleshooting Guide

      Introduction This is an informational document provided by the IT Team. Its purpose is to provide basic troubleshooting to staff concerning Mitel MiCollab Softphone. Softphone Activation Issue If your Softphone toggle becomes frozen, Restart the ...