iSNS Server Network Interface Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current iSNS server failover mechanisms often result in complete server downtime, even when only a single network interface fails, leading to unnecessary service disruption and resource wastage.
Innovation Solution
Implementing network interface level failover, where each iSNS server has multiple interfaces associated with different subnets, allowing seamless transfer of operations from a failed interface to another without taking down the entire server, with active and backup roles for each interface to ensure continuous service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional server-level failover is implemented, then server reliability is improved, but service continuity deteriorates due to complete server downtime
Solution Approach 1:
The patent segments the server's network functionality by creating multiple independent network interfaces (first network interface and second network interface) that can operate autonomously. Each interface is associated with different subnets and can be independently managed for failover, allowing the server to maintain service continuity on one interface while another interface fails, thus resolving the contradiction between reliability and service continuity.
2Reliability
If multiple network interfaces are implemented with active and backup roles, then service availability is improved, but device complexity increases
Solution Approach 1:
The patent implements dynamic role assignment where network interfaces can switch between active and backup roles based on operational status. The first network interface serves as active for its associated subnet, while the second network interface serves as backup. This dynamic configuration allows the system to adapt to failures automatically, improving service availability while managing complexity through structured role definition.
3Loss of energy
If network interface level failover is implemented, then resource efficiency is improved, but system complexity increases
Solution Approach 1:
The patent configures the second network interface in advance as a backup interface with pre-established associations to subnets. When the first network interface fails, the system activates the pre-configured second interface without requiring complex real-time resource allocation or reconfiguration. This preliminary setup improves resource efficiency by preventing unnecessary server shutdowns while managing complexity through advance configuration.
Data Source
AI summary
A technique includes hosting an Internet Storage Name Service (iSNS) server on a network switch to provide access to a plurality of subnets; and configuring the iSNS server to be an active server for a first subnet of a plurality of subnets and to be a backup server for a second subnet of the plurality of subnets.