Network Element Intercepts Session State for Server Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network systems lack an efficient method to manage server failures, particularly in scenarios where servers are unable to service requests, leading to wasteful resending of requests and inefficient use of network bandwidth, especially when protocols do not provide built-in notification mechanisms.
Innovation Solution
Implementing a network element that intercepts requests and selects alternative capable servers based on application layer message indications of server unavailability, ensuring seamless failover without client awareness, using a multi-blade architecture and Application-Oriented Network Services (AONS) to manage server failover and load balancing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the client resends requests when a server fails to respond, then the client can potentially receive a response, but network bandwidth is wasted and processing overhead increases
Solution Approach 1:
A network element is introduced as an intermediary between the client and server farm. This network element monitors server availability by intercepting requests and responses, detects when servers are unable to service requests, and automatically redirects clients to alternative capable servers. This intermediary function prevents bandwidth waste from redundant client resends while ensuring reliable request delivery.
Solution Approach 2:
The network element performs preliminary detection of server unavailability by intercepting server responses before they reach the client. By detecting server failures in advance and maintaining knowledge of server capability status, the network element can proactively redirect requests to functional servers, preventing the need for client-side retry mechanisms and associated bandwidth waste.
2Reliability
If the network element intercepts and monitors application layer messages to detect server unavailability, then server failover management is improved, but device complexity increases
Solution Approach 1:
The network element autonomously monitors server availability by intercepting application layer messages and automatically detects when servers are unable to service requests. It self-manages the failover process by selecting alternative servers and redirecting clients without requiring external control or complex coordination mechanisms, thereby improving reliability while keeping operational complexity manageable.
Solution Approach 2:
The network element establishes feedback loops by intercepting server responses and using this information to update its knowledge of server capability status. This feedback mechanism enables the network element to make informed decisions about request routing and server selection, improving failover management reliability through continuous monitoring and adaptive response.
3Productivity
If multiple servers are used in a server farm, then load balancing and availability are improved, but difficulty of detecting and measuring server unavailability increases
Solution Approach 1:
The network element serves as a central intermediary that monitors all servers in the farm uniformly. By intercepting application layer messages from multiple servers, it centralizes the detection function, making it easier to measure and detect server unavailability across the entire farm while maintaining load balancing capabilities.
Solution Approach 2:
The network element implements a universal monitoring approach by intercepting and analyzing application layer messages from multiple different servers using the same detection mechanisms. This multi-functional capability allows it to detect server unavailability across diverse servers in the farm, simplifying the overall detection process while supporting load balancing across multiple servers.
Data Source
AI summary
A method is disclosed for application layer message-based network element management of server failures. According to one aspect, a network element such as a router intercepts session state information that is contained in a request from a client and locally stores the session state information. As a result, application servers to which the requests are directed do not need to store the session state information. If an application server fails, then the network element can use the session state information stored at the network element to continue the session with another application server, transparently to the client application that is involved in the session.