> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-outside-emv/configuring-outside-emv/configuring-gilbarco/local-area-network-configuration.md).

# Local Area Network Configuration

The LAN needs to be configured for Gilbarco CRIND. In the Gilbarco configuration, the Commander is the CLIENT and the Gilbarco CRIND is the SERVER. The Outdoor EMV DCR IP traffic must be routed from Commander through the network IP of 192.168.31.31. Depending on which device specific IP configuration is selected for the site. Device Specific network routes might need to be added.

{% hint style="info" %} <img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FNLe9TN08wjroLCcyrXzq%2Fimage.png?alt=media&amp;token=c234457c-3309-4b03-9811-8f06f922c044" alt="" data-size="line"> For Shell branded sites, see Appendix D at the back of the document for Shell Verifone Zone settings.
{% endhint %}

## Isolated Payment NIC

1. In Configuration Client, navigate to Initial Setup > Local Area Network Configuration.
2. Click on Isolated Payment NIC in the Device Specific IP Configuration.
3. Verify with your network provider if the "Default Route" parameter needs to be checked. If the parameter is checked, then continue with the next steps. If not checked, then skip to the EPS Global Configuration Section.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FWZy34dwhhaW3PHlTeG3q%2Fimage.png?alt=media&amp;token=d05083dd-b9da-4966-9029-cc9cb3a7c9e5" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Using the IP address entered in the EMV Parameter in DCR configuration, add a network destination route with the 4th octet (last) set to ZERO. i.e. 10.5.55.0. This should cover all the IP ranges from 10.5.55.1 through10.5.55.255.
{% endhint %}

If Default Route is checked, then add New Route Config to the Device Specific Routes per site.

* **Route Type**: Network
* EMV Parameter IP Address (Forecourt > DCR > DCR Position Attributes) with the 4th octet set to 0.
* **Gateway**: 192.168.31.31
* **Netmask**: 255.255.255.0

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/K5SvVC61Gxo8JZeIQRbP/Unknown%20image)

Save the configuration changes and reboot Verifone Commander.

## EPS Global Configuration

{% hint style="info" %}
For Shell branded sites, EPS Global Configuration is controlled by Wincor. This should be pre-configured and enabled prior to converting the site for outdoor EMV. No changes are needed in EPS Global Configuration. Proceed to Fuel and DCR Initialization.The EMV Configuration tab of the EPS Global Configuration screen contains options for both inside and outside EMV use.
{% endhint %}

The EMV Configuration tab of the EPS Global Configuration screen contains options for both inside and outside EMV use.

1. Navigate to **Configuration Client > Payment Controller > EPS Global Configuration > EMV Configuration**.

   <figure><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/JcpJ0ZJnoLHFyOjbd6IQ/Unknown%20image" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/yzh5q3AdLqijHTT4eMk3/Unknown%20image" alt=""><figcaption></figcaption></figure>
2. From the Config Type drop down menu, select OUTSIDE.
3. In the Terminal Configuration section and from the EMV Enable Status drop down menu, select the parameter CONTACT or CONTACT AND CONTACTLESS.
4. Select Save.

## Fuel and DCR Initialization

1. After configuring Managed Modules for Fuel and DCR, perform a Fuel and DCR initialization.
2. Navigate to Configuration Client > Tools > Refresh Configuration.
3. To initialize Fuel, navigate to **Configuration Client > Forecourt > Initialization** and then select Fuel.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FxP8y2iYrZj9u6yWnnl0d%2Fimage.png?alt=media&amp;token=2b4150d2-4575-4510-b573-4d0a93d880da" alt=""><figcaption></figcaption></figure>
4. A message stating Fuel Initialization Successfully Sent displayed. Select Ok.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FXUe8T3VMTZH56xuqoLpe%2Fimage.png?alt=media&amp;token=2005af43-a2a8-4b75-991e-d064f1223c3d" alt=""><figcaption></figcaption></figure>
5. To initialize the Fuel Driver, navigate to Configuration Client > Forecourt > Initialization and then select Fuel Driver.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FagwkJreSNaz7YQBflGon%2Fimage.png?alt=media&amp;token=74f90126-79c1-4533-b1c9-89107f201687" alt=""><figcaption></figcaption></figure>
6. A message stating Fuel Driver Initialization Successfully Sent displayed. Select Ok.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FAsdToMjeSoU5uVWFKmSY%2Fimage.png?alt=media&amp;token=9ec5aa90-aa7f-4a62-9bb2-3840d6841eb8" alt=""><figcaption></figcaption></figure>
7. To initialize DCR Driver, navigate to Configuration Client > Forecourt > Initialization and then select DCR Driver.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FywmTdQyMbuMUO8Jh71EQ%2Fimage.png?alt=media&amp;token=60dc26cf-1003-4db0-9dd7-7919c30c6507" alt=""><figcaption></figcaption></figure>
8. A message stating DCR Driver Initialization Successfully Sent displayed. Select Ok.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FX8LsyARAuZAirdyK5R2p%2Fimage.png?alt=media&amp;token=bab260aa-7908-49ae-949e-d30dd11704db" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Check the dispensers to verify that they are loaded.

After the dispensers are all loaded, perform second DCR Driver initialization.
{% endhint %}

## EMV Initialization

{% hint style="danger" %}
For Shell branded sites, Shell will enable Outdoor EMV on the Wincor device prior to the EMV installation. EMV Initialization is controlled by Wincor. This should take place when Wincor and Commander sync and exchange information.
{% endhint %}

After Commander has established communications with the Gilbarco FlexPay™ CRIND positions, it will require an EMV Initialization to be performed. This action sends required Gilbarco EMV resource files to the selected CRIND positions.

{% hint style="info" %}
A DCR Driver Initialization must have been performed before starting the following steps. This will add DCR IDs to the Available POP List which can then be selected to receive the EMV Initialization.

An EMV Initialization does not perform a DCR Driver Initialization or a DCR Initialization.
{% endhint %}

1. Navigate to the **Configuration Client > Payment Controller > EPS Global Configuration > EMV Initialization**.
2. From the Initialize POP section locate the Available POP List.
3. For the CRIND(s) requiring initialization, select the required CRIND ID and click the Add >> button to move it to the Selected POP List.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Outdoor card readers will be identified as POP 101, 102, 103, etc.</p></div>

   <figure><img src="https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Hj5qJ29L7H9l7gb2m2JQ/Unknown%20image" alt=""><figcaption></figcaption></figure>
4. Repeat steps 2 and 3 for any additional CRIND IDs.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2F9SOk0JwsvixkxFJmsSPF%2Fimage.png?alt=media&amp;token=180140be-af85-4c83-a04a-034ba950de7a" alt=""><figcaption></figcaption></figure>
5. When finished selecting POP positions to be initialized, click Save. This performs an EMV POP initialization of the selected CRIND positions.
6. If another EMV Initialization is required, first perform a Refresh Configuration.
7. Navigate to **Configuration Client > Tools > Refresh Configuration**. This updates the Available POP List contents. Repeat the EMV Initialization steps 1 through 5 above.<br>

   <figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FBapainv2eP4elqnxgYDY%2Fimage.png?alt=media&amp;token=9116ec5b-78fe-44db-b667-1e6af67005a9" alt=""><figcaption></figcaption></figure>

## Verification of Forecourt Status

Use the following steps to verify IP based communications to the DCRs.

Navigate to Configuration Client > Tools > Helpdesk Diagnostics > Forecourt. The DCR Status should appear as "Online." If they are offline, then communications to the DCRs have not been established. Recheck the connections and verify TCP/IP connectivity.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fv0MzNStfgbmh2RisVhRO%2Fimage.png?alt=media&amp;token=937565c3-d50d-4ef7-8874-b1d7c1f230c1" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/emv-outside-emv/configuring-outside-emv/configuring-gilbarco/local-area-network-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
