Browse Prior Art Database

Active Discovery of Node using Framework on TCP/IP Stack

IP.com Disclosure Number: IPCOM000112574D
Original Publication Date: 1994-Jun-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 30K

Publishing Venue

IBM

Related People

Holt, VS: AUTHOR [+2]

Abstract

Once the NETMON discovery discovers a node, it sends the TCP/IP host address of the machine to the Topology Integration Services. Topology Integration Services must then discern whether or not the Lan Netview System Agent is present on the node, as well as if the framework is running. Secondly, if Topology Integration Services performs an XMP Get Request to the System agent, there is a window of time that the System Agent returns the information on what objects are present to Topology Integration Services and any object that comes up and generates an object creation event. Topology Integration Services will not know the existence of that object because of this window.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Active Discovery of Node using Framework on TCP/IP Stack

      Once the NETMON discovery discovers a node, it sends the TCP/IP
host address of the machine to the Topology Integration Services.
Topology Integration Services must then discern whether or not the
Lan Netview System Agent is present on the node, as well as if the
framework is running.  Secondly, if Topology Integration Services
performs an XMP Get Request to the System agent, there is a window of
time that the System Agent returns the information on what objects
are present to Topology Integration Services and any object that
comes up and generates an object creation event.  Topology
Integration Services will not know the existence of that object
because of this window.

      The solution is for Topology Integration Services, upon
receiving the address from NETMON discovery, to attempt to create a
remote sieve on the node.  If Topology Integration Services receives
a confirm on the remote sieve creation, it knows that the framework
is running on the node.  It will also receive any object-creation
notices while attempting to get the current object creation from the
System Agent on that node.  Therefore, the window for objects just
being created is eliminated.  A failure to create a remote sieve will
simply mean that the framework is not running.