Routing Appliance Failover via Server Fingerprint Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current failover systems in computer servers rely on heartbeat monitoring, which may not detect failures rapidly enough, especially in systems with fewer redundancies, leading to potential disruptions and increased costs due to the need for multiple redundant components.

Innovation Solution

The system implements a failover mechanism using routing appliances that actively monitor the operational state of primary and secondary servers through keep-alive signals and secure tunnels, allowing for simultaneous detection of primary server failures and seamless traffic rerouting to secondary servers, with periodic challenge/response protocols and machine fingerprints for secure identification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple redundant connection paths with redundant components are used, then system reliability is improved, but system capital and operating costs increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidsystem capital and operating costs
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system pre-establishes secure communication tunnels to both primary and secondary servers before failover is needed. The routing appliance maintains active connections to backup infrastructure in advance, so when failover occurs, traffic can be redirected immediately without establishing new connections during the crisis.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The routing appliance acts as an intermediary that sits between clients and servers, intelligently directing traffic based on server availability. This mediator absorbs the complexity of redundancy management, allowing the system to maintain multiple paths without requiring each component to be fully redundant, thereby reducing overall system costs while preserving reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If heartbeat monitoring is used for failure detection, then system complexity is reduced, but failure detection speed is insufficient

Engineering Contradiction:
Improvesystem complexityVSAvoidfailure detection speed
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

Instead of periodic heartbeat checks, the routing appliance maintains continuous active communication channels (secure tunnels) with both primary and secondary servers. This continuous connection allows for real-time detection of server failures, dramatically reducing detection time while keeping system complexity manageable through the use of standardized tunneling protocols.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If rapid failover is achieved through active monitoring, then service continuity is improved, but operational overhead increases

Engineering Contradiction:
Improveservice continuityVSAvoidoperational overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system uses periodic challenge-response authentication protocols within the continuous secure tunnels to verify server liveness. This periodic verification within an otherwise continuous connection framework provides rapid failure detection while managing operational overhead through efficient, standardized authentication mechanisms rather than constant high-bandwidth communication.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9141489B2Failover procedure for server system
Publication Date: 2015.09.22 UNILOC 2017 LLC
  • US9141489B2 patent drawing
  • US9141489B2 patent drawing
  • US9141489B2 patent drawing

AI summary

A failover procedure for a computer system includes steps for routing traffic from a routing device to a first server, storing in the routing device data representing a fingerprint of the first server, receiving periodically at the routing device a status message from the first server, detecting at the routing device an invalid status message from the first server by absence of the fingerprint in a status message from the first server within a predetermined time period after last receiving a valid status message, and routing the traffic from the routing device to a second server in response to detecting the invalid status message from the first server. A redundant server system implementing the failover procedure may include servers each capable of generating its fingerprint by reading current system configuration data.