Understanding the "Pairing" Process
The term "pairing" refers to a critical three-step communication process required between the Secure Payment Module (SPM) and the ANTX board within the fuel dispenser. A failure to "pair" typically means a failure to complete one of these three stages.
1. SPM Pairing (Physical Connectivity and IP Assignment)
This initial stage establishes local connectivity within the dispenser unit and assigns an IP address to the SPM.
Process Overview:
The SPM broadcasts a signal.
The signal is received by the AvaLAN In-Dispenser Unit (IDSU).
The signal is forwarded to the ANTX board.
Purpose: To allow the SPM to grab a local IP address so the ANTX board can communicate with it and transfer files later.
Troubleshooting Indicators:
This step should succeed as long as the IDSU has basic configuration.
If you see multiple SPMs listed during the pairing attempt, the AvaLAN IDSU is likely unconfigured or requires a reboot.
2. SPM Network Connection Status (Network Validation)
This stage verifies that the local components can communicate across the site's broader Managed Network Service Provider (MNSP) infrastructure.
Process Overview:
Communication relies on the MNSP network configuration being correct.
Data flows from the SPM > IDSU > AvaLAN AP > MNSP Payment VLAN > Route to MNSP Media VLAN > AvaLAN AP > IDSU > Ant board.
Outcome: Successful completion of this step confirms end-to-end network connectivity. Once established, file replication is almost guaranteed to succeed.
3. File Replication (Data Transfer)
The final stage uses the validated connection from Step 2 to transfer necessary operational files from the Ant board to the SPM.
Process Overview: This is the actual data synchronization process.
Timeline: This process typically takes 6 to 10 minutes to complete successfully.
Initial Troubleshooting Steps
Before proceeding with complex network diagnostics, ensure the physical and power layers are correct:
Reboot System Components: Perform a full power cycle of all associated dispensers and their internal AvaLAN IDSUs (ideally via the circuit breakers).
Verify AvaLAN Port Mapping: Ensure the SPM and ANTX boards are connected to the correct ports on the AvaLAN IDSU. Sides A and B cannot be mixed.
Wireless Units (Right to Left):
Port 1 (next to power): SPM Side A
Port 2: ANTX Side A
Port 3 (middle): SPM Side B
Port 4 (next to uplink): ANTX Side B
Wired Units (Right to Left):
SPM A, ANTX A, Uplink (middle), SPM B, Ant B
Accumera Sites: If the site uses Accumera as an MNSP, confirm that the MAC addresses of all SPMs and ANTX boards have been whitelisted by the provider.
Scenario 1: FP Not Completing SPM Pairing / Multiple SPMs Visible
This issue is typically related to the local AvaLAN hardware configuration (AP or IDSU).
Step | Action | Notes |
1. | Verify AP Configuration | If the Access Point (AP) is not configured, visit https://avalan.com/activation to submit the onboarding form. |
2. | Verify IDSU Connection | Ensure the IDSU has signal strength lights (High, Medium, or Low) indicating it is paired to the AP. |
3. | Reboot IDSU | Perform a local reboot of the IDSU unit. |
4. | Swap Hardware | If the issue persists, swap the problematic IDSU with a known-good IDSU from a working dispenser. If the problem follows the IDSU, replace the unit. |
5. | Contact AvaLAN Support | If all local hardware appears functional, contact AvaLAN support for remote diagnostics. |
Scenario 2: All FPs Not Completing "Connection Status"
When all Fueling Positions (FPs) fail to achieve "Connection Status" (Step 2 of the pairing process), the issue is likely site-wide and network-related. Potential causes include:
MNSP (Managed Network Service Provider) misconfiguration.
AvaLAN Access Point (AP) misconfiguration.
Site-wide SPM IP conflicts.
Understanding the SPM IP Conflict Symptom
An "IP Conflict" can occur even if the statically assigned IP address entered into the SPM is correct. The SPM is detecting another device on the network using the same IP and thus does not take the IP that you assigned to it.
Crucially: You cannot visually confirm this specific conflict on the dispenser screen. The only way to definitively diagnose this issue is to contact AvaLAN support and have them remotely verify the IP address they are reading from the dispenser.
Resolution Steps
Follow these steps sequentially to isolate and resolve the network communication issue:
Step 1: Isolate a Single Dispenser
To mitigate potential site-wide IP conflicts, isolate one dispenser for troubleshooting.
Power down all FPs at the site except for the unit you designate as your starting point (e.g., FP 1).
Perform a full, hard reboot of the isolated dispenser (preferably via the circuit breaker).
Step 2: Contact AvaLAN Support for Remote Diagnostics
Contact AvaLAN (via ticket thread or phone call) to gather network information. Ask the following specific questions and document their responses:
Question for AvaLAN | Purpose & Potential Outcome |
"Is my AP checking in?" | Confirms AvaLAN's ability to see site devices remotely. If the AP is not checking in, AvaLAN has limited visibility for further troubleshooting. AvaLAN would be unable to see the IP addresses of the SPM or traffic. |
"What VLANs are you using for Payment/EMV and Media?" | Gathers required information for cross-validation with the MNSP. (Typical: 111 for Payment/EMV, 112 for Media/Ant Board). |
"What IP address are you reading from my SPM?" | Confirms if the SPM’s IP matches the IP that you set, thus testing for IP conflict. |
"Are you seeing two-way traffic on both the Payment and Media VLANs?" | This tests to make sure that the MNSP has their configuration in place, and if their configuration matches the AvaLAN’s. |
Step 3: Validate the MNSP Configuration
Use the information gathered from AvaLAN to confirm the MNSP's configuration. Refer to the official AvaLAN guide for detailed MNSP communication protocols:
Key Validation Points with the MNSP:
Configuration Item | Required State |
AP Switch Port | Must be configured as a Trunked Port. |
VLAN IDs | The MNSP's Payment/EMV and Media VLAN IDs must exactly match those provided by AvaLAN. |
Route | A route must exist between the Payment/EMV VLAN and the Media VLAN. |
Traffic Visibility | MNSP can confirm they see traffic from SPMs on the Payment VLAN and from the Ant board on the Media VLAN. |
Resolution Note: If a discrepancy is found between AvaLAN's configuration and the MNSP's established settings, it is generally faster and easier for AvaLAN to update their cloud configuration to match the MNSP. Contact AvaLAN support to request this change.
Scenario 3: Specific FPs Not Completing Connection Status (Isolated Issue)
If only one or two specific dispensers are failing while others at the site function correctly, the site-wide MNSP configuration can usually be ruled out (unless it is an Accumera site requiring MAC address whitelisting).
The issue is likely an IP conflict or a faulty IDSU.
Isolate & Pair: Power down all other FPs at the site except the problematic one. Attempt to unpair and re-pair the SPM.
Swap Hardware: Swap the IDSU with a known-good unit from another dispenser. If the problem moves with the original IDSU, replace the hardware.