Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Keeping sockets on standby to provide socket connectivity when node goes off the network and come back on the network

IP.com Disclosure Number: IPCOM000203276D
Publication Date: 2011-Jan-21
Document File: 3 page(s) / 35K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is the method of keeping sockets on standby to provide socket connectivity when node goes off the network and come back on the network.When a node is off the network all the established sessions like telnet,ftp etc will be broken down and the user need to re-initiate them when the node is on the network again. The idea presented prevents reconnection by a way that when the node is off the network all the sockets in connected mode will go in to a off-network mode and the connection will not be teared down for a certain time limit.When the node is back in network the sockets in the off-network mode will be moved on to on-network mode and the connection states will remain intact. The user need not re-initate the connection and the continuity of the connection is maintained.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 47% of the total text.

Page 01 of 3

Keeping sockets on standby to provide socket connectivity when node goes off the network and come back on the network

Disclosed is the method of keeping sockets on standby to provide socket connectivity when node goes off the network and comes back on the network. When a node is off the network all the established sessions like telnet,ftp etc will be broken down, and the user need to reinitiate them when the node is on the network again. The idea presented prevents reconnection by a way that when the node is off the network all the sockets in connected mode will go in to a off-network mode and the connection will not be teared down for a certain time limit.When the node is back in network the sockets in the off-network mode will be moved on to on-network mode and the connection states will remain intact. The user need not reinitiate the connection and the continuity of the connection is maintained.

Acronyms:

PCB: Internet protocol control block

LAN: local area network

Present implementation and problems:

Use case-1: simple removal, reconnection of laptop

Suppose a user detaches his laptop by unplugging his LAN cable,

1.

Goes to conference room or some other location in his office,

2.

Plug-in the LAN cables again thus connecting his laptop back on to network.

3.

Outcome: he loses all existing telnet, rsh, ftp, and etc sessions that were running on his computer.

Desirable

      : A facility to retain these sessions would be very helpful to reduce burden on user to restart those sessions all over again.

What sessions can be lost : Applications sessions that can be lost may be telnet, ftp, tftp, rsh, etc.

N

 ote: VNC (Virtual network computing) appears to be solution. But recall that VNC server runs the software; VNC creates a screen image at the server, which can be viewed from anywhere, using the VNC Viewer .

So contrary to what seems obvious, VNC is not a solution for problem above. In this use case, sessions are running on user's laptop and they use sockets for communication with peers. These sockets will be terminated if network is unplugged.

Similar solutions:

Presently these sessions needs to be restarted.

Use case-2: Ethernet adapter swapping for systems in production environment

When a system is in production and the Ethernet adapter needs to be swapped out, the only

1.

option of doing the swapping without disrupting the applications is to have the adapter configured as an ether-channel.

But this is not a typical configuration and it adds unnecessary overhead at times when no swap is being done.

Present scenario of changing adapter with network outage, for example, a large DB2*

2.

database, can take hours to be brought down and brought up again, leading to significant downtime for the end-user. The above idea is very useful here.

Use case-3: Making HA clustering more efficient

1


Page 02 of 3

This idea would make High-Available clustering much more efficient. Currently, HA solutions such as HACMP rely on the concept of a "service IP...