# US 10,873,498 B2 · Server network interface level failover > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,873,498 B2 - Document ID: US10873498B2 - Status: Granted - Kind: B2 - Application number: 15/938,933 - Filed: 2018-03-28 - Published: 2019-04-25 - Granted: 2020-12-22 - Earliest claimed: 2017-10-23 - Assignees: Hewlett Packard Enterprise Development LP - Applicants: Hewlett Packard Enterprise Development LP - Inventors: Asutosh Satapathy; Krishna Babu Puttagunta; Vivek Agarwal; Rupin T. Mohan; Dheeraj Sharma - Web page: https://patentgrep.com/patent/US10873498B2 ## CPC - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - G06F 3/06: Digital input from, or digital output to, record carriers {, e.g. RAID, emulated record carriers or networked record carriers} - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 11/00: Error detection; Error correction; Monitoring (error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00) - G06F 11/2005: {using redundant communication controllers} - G06F 11/2035: {without idle spare hardware} - H04L 41/0213: Standardised network management protocols, e.g. simple network management protocol [SNMP] - H04L 41/0663: Performing the actions predefined by failover planning, e.g. switching to standby network elements - H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route - H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV - H04L 45/22: {Alternate routing} - H04L 45/28: using route fault recovery - H04L 45/64: using an overlay routing layer - H04L 49/00: Packet switching elements - H04L 49/356: for storage area networks - H04L 61/45: Network directories; Name-to-address mapping - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) - G06F 11/2028: {eliminating a faulty processor or activating a spare} - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - H04L 49/357: {Fibre channel switches} - H04L 2101/645: Fibre channel identifiers - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract 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. ## Claims ### Claim 1 A method comprising: 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 the plurality of subnets and to be a backup server for a second subnet of the plurality of subnets; determining whether a packet received by the iSNS server is associated with the first subnet or the second subnet based on an identifier of the packet; determining whether the iSNS server is a backup server or an active server for the first subnet or the second subnet determined to be associated with the packet; and processing the packet based on the determination of whether the iSNS sewer is the backup server or the active server for the first subnet or the second subnet determined to be associated with the packet. ### Claim 2 (depends on 1) The method of claim 1, wherein configuring the iSNS server comprises configuring the iSNS server to provide a plurality of instances of the iSNS server, the method further comprises: using a first instance of the plurality of instances to be the active server for the first subnet and to be the backup server for the second subnet. ### Claim 3 (depends on 2) The method of claim 2, further comprising: using a second instance of the plurality of instances to be an active server for the second subnet and to be a backup server for the first subnet. ### Claim 4 (depends on 3) The method of claim 3, further comprising: detecting a failover condition associated with the first subnet; and determining, based on the detected failover condition, whether to fail over to the second instance to allow the second instance to be the active server for the first subnet or fad over to another iSNS server to allow the another iSNS server to be an active server for the first subnet. ### Claim 5 (depends on 3) The method of claim 3, further comprising: in response to the first subnet becoming unavailable, disabling the first instance from being the active server for the first subnet and using the second instance to be an active server for the first subnet. ### Claim 6 (depends on 1) The method of claim 1, further comprising: routing a packet to a network interface of the iSNS server based on an identifier of the packet. ### Claim 7 (depends on 6) The method of claim 6, wherein the identifier associates the packet with a subnet of the plurality of subnets. ### Claim 8 (depends on 1) The method of claim 1, further comprising: inserting an a second identifier into a second packet to be transmitted by the iSNS server representing association of the second packet with a subnet of the plurality of subnets. ### Claim 9 (depends on 1) The method of claim 1, further comprising: using the iSNS server to generate identifiers to be inserted into packets communicated with the iSNS server to coordinate storage of data in a database, wherein the database comprises entries segregated according to different subnets of the plurality of subnets based on the identifiers, the identifiers including the identifier of the packet received by the iSNS server. ### Claim 10 An apparatus comprising: a network switch; and an Internet Storage Name Sendee (iSNS) server hosted by the network switch, wherein the iSNS server is associated with a plurality of network interfaces, the iSNS server provides a first instance of 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; wherein the iSNS server is to determine whether a packet received by the iSNS server is associated with the first subnet or the second subnet based on an identifier of the packet; wherein the iSNS server is to determine that first instance of the iSNS server is an active server for the packet based on a determination that the first subnet is associated with the packet; wherein the iSNS server is to determine that the second instance of the iSNS server is a backup server for the packet based on the determination that the first subnet is associated with the packet; and wherein the first instance of the iSNS server is to process the packet based on the determination that the first instance of the iSNS server is the active server for the first subnet determined to be associated with the packet. ### Claim 11 (depends on 10) The apparatus of claim 10, wherein the iSNS server provides a second instance of the iSNS server to be a backup server for the first subnet and to be an active server for the second subnet. ### Claim 12 (depends on 11) The apparatus of claim 11, wherein the first instance of the iSNS server fails over to the second instance of the iSNS server in response to the first subnet becoming unavailable. ### Claim 13 (depends on 11) The apparatus of claim 11, wherein the iSNS server: detects a failover error condition associated with the first instance of the iSNS server; and based on the detected failover error condition, the iSNS server selects to fail over from the first instance of the iSNS server to the second instance of the iSNS server or fail over to another iSNS server. ### Claim 14 (depends on 11) The apparatus of claim 11, further comprising: a node to communicate a packet with the iSNS server, wherein the iSNS server routes the packet for processing to one of the first instance or the second instance based on whether the packet is associated with the first subnet or the second subnet. ### Claim 15 A non-transitory machine readable storage medium to store machine readable instructions that, when executed by a machine, cause the machine to: for a server comprising a plurality of network interfaces, provide a plurality of server instances for the plurality of network interfaces, wherein each server instance of the plurality of server instances to serve as an active server using a different network interface of the plurality of network interfaces; configure a first server instance of the plurality of server instances to be an active server for a first subnet and be a backup server for a second subnet other than the first subnet; and configure a second server instance of the plurality of server instances to be an active server for the second subnet and be a backup server for the first subnet; determine whether a packet received by the sewer is associated with the first subnet or the second subnet based on an identifier of the packet; determine that first instance of the server is an active server for the packet based on a determination that the first subnet is associated with the packet; determine that the second instance of the server is a backup server for the packet based on the determination that the first subnet is associated with the packet; and process the packet with the first instance of the server based on the determination that the first instance of the server is the active server for the first subnet determined to be associated with the packet. ### Claim 16 (depends on 15) The non-transitory machine readable storage medium of claim 15, wherein the instructions, when executed by the machine, further cause the machine to, in response to the first server instance being unable to actively serve the first subnet, cause the first server instance to failover to the second server instance so that the second server instance actively serves the first subnet. ### Claim 17 (depends on 15) The non-transitory machine readable storage medium of claim 15, wherein the instructions, when executed by the machine, further cause the machine to compare the identifier to a subnet list of associations of the identifier to server instances. ### Claim 18 (depends on 15) The non-transitory machine readable storage medium of claim 15, wherein the server comprises an Internet Storage Name Sendee (iSNS) server.