Description

LWC/vLWC has stopped collecting data and the last collection date shows an older date.

Symptoms

Data has not been refreshed in the Dashboard of JSI.

The last collection date is shown as an older date.

Solution

LWC/vLWC collects data from the device groups managed by JSI at 2 A.M. based on the customer's time zone. The Dashboard is reflected with the data once it has been collected by the LWC/vLWC and sent to the cloud for further processing.

 

The last collection date shows the date when the data was collected from the device groups. If the last collection date is showing an older date, it can happen due to any of the below reasons.

 

  1. LWC/vLWC is disconnected from either cloud or the devices
  2. Data collection failed to happen

If the LWC/vLWC is disconnected from the cloud or the devices, please login to the captive portal using the serial number of the LWC/vLWC using the below methods.

 

For LWC:

 

The correct way to access the captive portal is available under the header “To configure the LWC” in the link : Captive Portal Access.

 

For vLWC:

 

The correct way to access the captive portal for vLWC is available under the header "To configure the network settings on vLWC" in the link : Captive Portal Access.

 

Please check the connection status for the internal and external networks along with the cloud connection. They should all show green. If you are seeing red for any of the connection status of the external network and cloud, please download the extensive and light RSI and provide the same to JTAC by opening a ticket.

 

If you are seeing red for the internal network, please check if the connectivity to the internal networks is allowed from the LWC / vLWC. To check the same, please try deploying a dummy VM in the same subnet as the internal network and check if you can perform an SSH to the device IP-Addresses provided in the device groups.

 

If all of the above connection status are showing green but device collection is still failing, please check the email notifications received from the LWC / vLWC for any errors or failures.  As a last ditch effort, you can also try rebooting the VM from vSphere (in case some backend process is not starting up correctly).

 

 

Modification History

2025-05-26 : Article Created