Browse Prior Art Database

ISDN Physical Problem Correlator

IP.com Disclosure Number: IPCOM000100449D
Original Publication Date: 1990-Apr-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 4 page(s) / 134K

Publishing Venue

IBM

Related People

Brabec, N: AUTHOR [+3]

Abstract

When an error occurs while two nodes are communicating, the error could be in either node or in the communication link between both nodes. It is possible that both nodes will detect the error, each in its own way. It is also possible that both nodes will report the error condition that each has detected to a management focal point. In Fig. 1 an error in the adapter in NT2X could affect the links 1 and 3. Nodes A, B and X detect this error against different resources: nodes A and X detect problems with a link on the D channel, i.e., link 1, nodes A and B detect problems with the link on the B channel, i.e., link 3. Data on the problems could be stored locally and/or sent by the node, e.g., as an alert, to the problem management focal point.

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

ISDN Physical Problem Correlator

       When an error occurs while two nodes are communicating,
the error could be in either node or in the communication link
between both nodes.  It is possible that both nodes will detect the
error, each in its own way.  It is also possible that both nodes will
report the error condition that each has detected to a management
focal point.  In Fig. 1 an error in the adapter in NT2X could affect
the links 1 and 3. Nodes A, B and X detect this error against
different resources:  nodes A and X detect problems with a link on
the D channel, i.e., link 1, nodes A and B detect problems with the
link on the B channel, i.e., link 3.  Data on the problems could be
stored locally and/or sent by the node, e.g., as an alert, to the
problem management focal point. In the figure, the unique identifier,
H#1, is associated with link 1, H#2 is associated with link 2, and
H#3 is associated with link 3.  When the alerts are sent to the focal
point by both the TE A and TE B, H#3 must be included as shown
in flows 3 and 4 of the same figure.  There is a requirement then for
the management focal point to know that those alerts from different
nodes that contain the same unique identifier are related. In other
words, flows 1 and 2 are related, flows 3 and 4 are also related.
This article deals with a mechanism for generating this unique
identifier or correlator based on an existing invention.  The
mechanism of correlating alerts reported by the same node due to a
failure which effects several resources is beyond the scope of this
article, e.g., no mechanism is provided to correlate the alerts for
the flows 2 and 3 shown in Fig. 1.

      There is a proposal to define the problem correlator as a
contiguous bit string which consists of the configuration information
of both communicating products.  When two nodes start communicating,
configuration information will be exchanged between these two nodes.
This configuration data includes the model number, serial number,
manufacturer ID, call connection identifier (telephone number), etc.
The configuration data exchange is shown in Fig. 2.  Each node, upon
the receipt of the partner's configuration data, will go through a
pre- agreed mechanism, i.e., to arrange both configuration data in
such order that the same bit string be presented to the management
focal point.

      This mechanism, while conceptually sound, has presented several
problems as listed below:
      1.   The length of the bit string is unreasonably long; it
could be in excess of 100 bytes.
      2.   Enforcement of the agreement such that the same bit string
will be presented to the management focal point from the two
communicating nodes.
      3.   Using hardware configuration information to generate
problem correlator is very static.  Two communicating nodes will have
the identical correlator for different instances.
      4.   The existing mechanism is symmetrical, eve...