Mercury Intelligent Controller Network Requirements

To make sure your Mercury Intelligent Controller operates reliably with the Alocity Control Center, meet the network requirements below.

1. Ethernet Connection

• Connect each Mercury controller to the network with a wired Ethernet connection.
• Use DHCP. To keep the same address, create a DHCP reservation for the controller's MAC address. Its not recommended to set a static IP on the controller.
• Avoid isolated VLANs or guest networks unless they are routed to the internet.
• The MR62e connects over Ethernet and must be reachable from its master controller.

2. Firewall Settings

Mercury controllers connect outbound to the Alocity cloud, so no inbound port forwarding or public IP is needed. Allow the following outbound ports on both local and upstream firewalls:

IMPORTANT: Don't apply SSL/TLS inspection to the controllers' traffic. They connect to the cloud with mutual TLS (certificate-based) authentication.

3. Recommended Internet Speed

• Upload: 2 Mbps per controller
• Download: 2 Mbps per controller
• Jitter: under 30 ms, to prevent heartbeat timeouts
• Latency: under 50 ms, so cloud unlocks happen immediately

4. Downstream Boards and Readers

• Controllers: LP1501, LP1502, LP2500, LP4502, MP1501, MP1502, MP2500 and MP4502.
• RS-485 sub-panels: MR50, MR52-S3B/S4, MR16IN and MR16OUT, on 24 AWG shielded twisted pair up to 4,000 ft. See Installing Mercury Hardware.
• Readers: Wiegand or OSDP.

5. Network Testing Recommendations

• Measure jitter: keep it under 30 ms to avoid false offline alerts.
• Inspect wiring: use Cat5e or Cat6 and check for damage or weak terminations.
• Direct connection testing: when troubleshooting, temporarily connect the controller directly to the main router.

For questions or assistance, please contact your account manager or email support@alocity.com.