DNS works—just not where it matters.
The RADIUS server in Miami is reachable, but the local resolver in Rio cannot resolve it. DNS appears healthy globally, yet authentication still fails at that specific site.
Network Operations & Intelligence
See the problem before it becomes a ticket. Find the cause before the search begins.
Meilleur Control brings monitoring, diagnostics, technical evidence, and reporting into one operational view. From the central NOC down to an individual access point, Control shows not only that something is wrong, but where it starts and which data supports the diagnosis.
- Scope
- Site to client
- Evidence
- Live and historical
- Services
- DNS, DHCP, NTP, RADIUS, NAC
One platform. One technical context.
From the NOC to the affected site.
01
NOC & Control
Sites, APs, clients, services, and infrastructure in one investigation instead of scattered across separate tools.
Explore the platform → 02 Control MonitorLive state, time series, and historical context down to AP, client, SSID, VLAN, and RF environment.
View Monitor → 03 Beam AgentActive service tests, local data collection, and evidence from the exact location where the issue occurs.
Explore Beam → 04 Companion AppMobile workflows for field engineers to test, compare, document, and share results.
Explore Companion →From status to cause
One glance shows the state. The next click reveals the cause.
Control keeps site, access point, client, service, RF, and infrastructure context in the same investigation. The NOC can see where an issue begins, which dependencies are affected, and what evidence supports the next useful step.
Live and historical
Service & RF
AP to client
Switch port and PoE
The question that matters
Is the visible fault the root cause—or merely the first symptom?
Slow DHCP may be a service issue—or the result of CRC errors, drops, insufficient PoE, a duplex mismatch, excessive airtime, or unstable cloud communication. Control brings all of these signals into the same scope.
Monitor Workspace
Scope, history, and operational priority
Diagnostics / Health
Prioritize issues by scope and impact
When global green is not enough
Globally healthy. Locally still broken.
What matters is what happens at the affected site: which VLAN, SSID, client, access point, and dependency are involved. Control exposes local deviations that can disappear inside a global overview.
The wireless network is active. The password has expired.
The access points are online and the SSID is being advertised. Only when a client attempts to connect does it become clear that credentials, policy, or time-limited access are no longer valid.
The cloud is available. New APs still fail to onboard.
SSL inspection alters certificate chains or a firewall blocks required destinations. Existing devices appear stable while new access points cannot reach the cloud.
Wireless is not the root cause. The cable is.
CRC errors, drops, insufficient PoE, or a speed/duplex mismatch can surface as slow DHCP, interrupted application sessions, missing telemetry, or repeated client reconnects.
From signal to action
Not just red or green—where, why, and what to do next.
Control combines live context, service tests, and infrastructure evidence in one workflow.
One investigation context
One workspace instead of data silos.
APs, clients, sites, buildings, SSIDs, VLANs, NAC, switch ports, and services stay part of the same investigation. The technical context does not disappear when you move from overview to detail.
- AP and client investigation
- RF, neighbor, and channel evidence
- NAC and RADIUS validation
- Remote sniffer and PCAP
- Findings, root cause, and reports
Historical context
What happened yesterday at 18:00?
An issue was reported but has since disappeared. Monitor preserves the timeline: client count, CPU, memory, channel utilization, retries, noise floor, CCI, service state, and available infrastructure evidence.
- Client and throughput trends
- CPU, memory, and uptime
- Airtime, retries, errors, and noise floor
- SSID, VLAN, AP, and building context
- Historical analysis by time and scope
A clean technical handoff
A finding that does not need to be explained again.
Reports keep tested services, affected infrastructure, technical evidence, root-cause correlation, and recommended next steps together. The next team receives a traceable technical finding, not an alert stripped of context.
