How to Communicate with MNSPs

How to Communicate with MNSPs

Communicating with Managed Network Service Providers (MNSPs)

As a fuel technician, engaging with Managed Network Service Providers (MNSPs) can sometimes present challenges, particularly when dealing with complex network configurations. The following guidance is intended to help streamline communication and ensure that sites are set up correctly the first time.

Initial Contact

When first contacting an MNSP, it's important to clearly communicate the type of configuration needed. You should request the Anthem configuration.

Be sure to specify that the site is an Anthem or AX site. For clarity, note that Ovations with AX boards function similarly to Anthem dispensers, although they are smaller in scale. Additionally, always mention the site's brand (e.g., BP, Shell, etc), as configurations may vary depending on the brand of the site.

If Reconfiguration Is Required

If the site was not configured correctly during the initial setup and you need to call back, be prepared to provide more detailed information. Specifically, inquire about the profile configuration being applied.

To ensure proper dispenser functionality, the MNSP switch configuration should include:

  • EMV/Payment VLAN ID

  • Media VLAN ID

  • AP VLAN ID

Confirm that both the EMV and Media VLANs are trunked to the port where the Access Point (AP) is connected. Ask the MNSP to provide the VLAN IDs for EMV and Media, and document these values. It's also important to understand the distinction between an IP address (e.g., 172.29.1.101) and a VLAN ID (e.g., 111)—the latter is a static number that identifies a specific VLAN.

Troubleshooting AP Connectivity

Once the network configuration is confirmed, getting the AP online may still require additional steps. If you encounter issues at this stage, it's often helpful to request escalation:

  1. Ask to speak with a Level 2 (L2) technician, and politely request that they engage a Level 3 (L3) technician to review the switch template that has been applied correctly. Often, this step resolves configuration mismatches.

  2. If the AP continues to remain offline, ask the MNSP to verify whether the AP is receiving DHCP and DNS services. You can also request that they check whether any outbound traffic from the AP is visible on their network.

This will help determine whether the AP is successfully attempting to communicate with external services (e.g., the AvaLAN Cloud) or if it's being blocked entirely.