How does IPK verify if the fail-over mechanism works?

We want to assure our clients that validating the effectiveness of their fail-over mechanisms is a critical aspect of our service. To ensure the reliability and seamless functionality of the fail-over mechanisms, we employ a series of automated checks. It's important to note that the testing process is designed to be non-disruptive, causing no downtime or negative impact on the user experience.

Given that our solution operates in a cloud environment, the testing methodology differs from traditional MPLS network testing. Nevertheless, our testing procedures are robust and comprehensive. We schedule and execute various tests to ascertain the fail-over mechanism's efficacy:

Hardware Fail-over and Fail-back:

• This involves a simulated reboot of the primary Customer Premises Equipment (CPE) to assess how efficiently the fail-over mechanism handles such a scenario. The goal is to ensure a smooth transition between primary and secondary hardware without impacting services.

Internet Fail-over:

• We conduct tests specifically focused on the fail-over mechanism in the context of internet connectivity. This helps us verify that, in the event of a primary connection failure, the system seamlessly switches to an alternative connection without any service interruptions.

EtherChannel/LAG Fail-over Test:

• In situations where EtherChannel or Link Aggregation Groups (LAGs) are utilized, we schedule fail-over tests to confirm the system's ability to gracefully shift the load to the available channels in case of a link failure.

These tests collectively provide a comprehensive evaluation of the fail-over mechanisms, ensuring that they meet the high standards of reliability and performance that our clients expect. It's part of our commitment to delivering a robust and dependable solution that can effectively handle unforeseen circumstances without compromising on service quality. We prioritize transparency and collaboration to meet the unique needs of each client.