This article explains the cause and resolution for scenarios where a vLWC collector fails to collect data because it was deployed using an incorrect or mismatched account ID.

When a vLWC OVA is downloaded and deployed using the wrong account ID, the following issues may occur:

• Device groups cannot be moved from the existing vLWC to the newly deployed vLWC because the account IDs do not match.

• vLWC connection status appears blank on the JSI portal.

• Data collection does not start for any existing device groups.

The account ID used when downloading the vLWC OVA is automatically embedded and permanently associated with that vLWC instance.

• If device groups are already linked to one account ID, they cannot be reassigned or mapped to a vLWC deployed with a different account ID.

• If the account ID is different, new device groups must be created under the newly deployed vLWC with the correct account ID.
  
  

If you face any further issues, please contact JUNIPER JTAC Support for assistance.