Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

This guide is designed to help you determine which steps to take, and when.

Requires server version 20230801 or newer.

Before you start troubleshooting, make sure you're familiar with the concept of pairing:


Quick jump

My Terminal firmware version is:


Terminal with version 20230801 and newer

Pairing Steps (before approving the pairing request in CAS)

Deployment Scenario

Terminal State

Actions to Take

Topology A

  • Previously paired, and

  • VPN configured.

  1. Set Server IP on the BATM,

  2. confirm the pairing code,

  3. approve the pairing request in CAS.

Topology A

  • Never paired, and

  • No VPN.

  • e.g. new Terminals

  1. Create Terminal in CAS,

  2. generate the VPN config,

  3. set Server IP on the BATM.

Topology B

  • Never paired

  1. Create Terminal in CAS,

  2. set Server IP on the BATM.

Topology B

  • Previously paired

  1. Set Server IP on the BATM

Unpairing Steps

Deployment Scenario

Terminal State

Actions to Take

Topology A

Paired and connected

Unpair via Terminal list action menu.

Topology B

Paired and connected

As above.


Terminal with a version newer than 20190130 but older than 20230801

Pairing Steps

Upgrade the Terminal to version 20230801 first. The good news is that the gate service should handle this automatically.

Deployment Scenario

Terminal State

Actions to Take

Notes

Topology A

Previously paired, VPN configured

Set the Terminal server's host/IP via advanced admin. Look for error screen with pairing code.

In CAS, approve new pairing request.

Topology A

Never paired, No VPN

Create Terminal in CAS, generate VPN config. Set host/IP.

As above.

Topology B

Never paired

Create Terminal in CAS, set host/IP.

As above.

Topology B

Previously paired

Set host/IP.

As above.


Terminal with version 20190130 or older

Pairing Steps

You're working with a pretty old machine here. Upgrade the Terminal twice. Again, the gate service should handle this.

Deployment Scenario

Terminal State

Actions to Take

Notes

Topology A

Previously paired, VPN configured

Set the Terminal server's host/IP via advanced admin. Look for error screen with pairing code.

In CAS, approve new pairing request.

Topology A

Never paired, No VPN

Create Terminal in CAS, generate VPN config. Set host/IP.

As above.

Topology B

Never paired

Create Terminal in CAS, set host/IP.

As above.

Topology B

Previously paired

Set host/IP.

As above.


Troubleshooting

Topology A

BATM displays “VPN connection error”: means that you probably didn’t generate a VPN configuration.

Topology B

This topology deploys hardware for the VPN infrastructure, which eliminates VPN software as a possible problem.

  • No labels