top of page

Case study: Instant Network Fault Mapping

Updated: 16 hours ago

In this case study, four parties are involved: the carrier aggregator, a local service provider, the customer, and Bumblebee Networks. The carrier aggregator partners with the local service provider, which provides the internet circuit with an on-site broadband modem and Ethernet switch at the customer's site. The carrier aggregator deploys a Bumblebee NID at the customer's site behind the switch. This is a typical deployment in the 'wholesale' market, where multiple service providers collaborate to provide internet service to clients.


Instant Network Fault Mapping
site edge deployment

In past years with a different carrier aggregator, the customer had no access to or visibility into their internet connectivity status. They only discovered outages when employees or IT staff began to complain, prompting the customer to call the service provider to troubleshoot. Valuable time passed, and business losses were incurred. The customer became frustrated. When the contract renewal time came, they switched to the current carrier aggregator.


With the Bumblebee platform, the customer is granted access to the system. They can view a map of their deployed sites, monitor WAN health, track link utilization and application performance, and receive alerts when an outage occurs


Recently, a few outages occurred. There is no longer panic among the customer, the carrier aggregator, and the service provider. The Bumblebee platform provides instant network fault mapping, alerting the service provider and customer when an outage is detected. This network fault mapping identifies which segment of the network is at fault, directing energy and focus to the right target immediately.


Bumblebee outage alert message
Bumblebee Alert message example

In a DIA circuit, the network is divided into two segments: the last mile and the middle mile, as shown in the diagram below.


Last mile and middle mile in DIA circuit
Network segment for DIA circuit

If the alert message indicates a Last mile issue, the focus should be on the modem, Ethernet switch, and Bumblebee NID to ensure they are powered on and cables are properly connected. On-site IT or a dispatch may need to be scheduled for recovery.


If the alert message indicates a Middle mile issue, the focus should be directed to the local service provider's default gateway, the service provider's network, and its peering partners. There is no need to spend time on the on-site equipment.


As it turns out, the recent outages were caused by issues in the middle mile, and the local service provider clearly has more work to do to stabilize their connectivity. However, instead of casting wild blame on everyone, there is clear focus on what to zoom in at the onset of an outage.


In addition, Bumblebee platform keeps the outage history record for 3 years to facilitate post which brings benefits as outlined below:


  • Trend Analysis and Pattern Identification: Access to three years of outage data allows the customer, carrier aggregator, and service provider to identify recurring issues, such as frequent last-mile or middle-mile failures, enabling proactive measures to address underlying causes.

  • Improved Troubleshooting Efficiency: Historical records provide context for current outages, helping IT teams or service providers quickly pinpoint whether issues are related to specific equipment (e.g., modem, Ethernet switch, or Bumblebee NID) or network segments, reducing resolution time.

  • Informed Decision-Making: Long-term data supports strategic decisions, such as evaluating the reliability of the local service provider or peering partners, aiding in contract renewals or provider switches.

  • Accountability and Collaboration: Detailed records foster transparency among parties, reducing misdirected blame and encouraging collaborative problem-solving by clearly documenting fault locations and past resolutions.

  • Performance Benchmarking: The outage history allows customers to assess network performance over time, ensuring service providers meet agreed-upon standards and identifying areas for infrastructure upgrades.

  • Compliance and Reporting: Maintaining records for three years supports compliance with industry regulations or internal audits, providing a verifiable log of network performance and incidents.

Comentários


bottom of page