Browse Prior Art Database

Method for Gathering Network Management Data Traversing Multiple Adapters

IP.com Disclosure Number: IPCOM000111290D
Original Publication Date: 1994-Feb-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 4 page(s) / 150K

Publishing Venue

IBM

Related People

Carriker, CA: AUTHOR [+2]

Abstract

A method for gathering network management data traversing multiple adapters is disclosed. Each routing protocol environment maintains network management for a given session if the environment contains the primary path control instance for the session. Whenever the network management agent/subagent queries a given environment, the routing protocol will either return all or none of the network management data-objects for a given session.

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

Method for Gathering Network Management Data Traversing Multiple
Adapters

      A method for gathering network management data traversing
multiple adapters is disclosed.  Each routing protocol environment
maintains network management for a given session if the environment
contains the primary path control instance for the session.  Whenever
the network management agent/subagent queries a given environment,
the routing protocol will either return all or none of the network
management data-objects for a given session.

      One of the key network management functions for any routing
protocol is resource/session performance and accounting.  Customers
have long required routing protocols to provide performance and
accounting data.  This network management data is typically then used
as input into the customers billing, performance, capacity planning
and/or problem determination applications.

      Network management data for a specific protocol resource, e.g.,
session, consists of a group of data-objects.  This group of
data-objects can be viewed as a performance/accounting record.
Typically within this group of data-objects will be one or more names
and two sets of counters, e.g., resource1-to-resource2 counters and
resource2-to-resource1 counters.  Each set of counters in turn will
consist of one or more package (PIU) counters and one or more byte
counters.

      Traditionally the network management agent/subagent code will
reside in the same environment as the network routing protocol.  Thus
the network management agent/subagent is easily able to retrieve the
resource counters from the network routing protocol through some
agreed to interface.

      The network routing protocol may choice to distribute its
function on to multiple environments within the same physical box.
Node B in Figure 1 illustrates this for the Advanced Peer to Peer
Network (APPN) routing protocol.  Node B actually has three
environments, e.g., the System Card, Adapter 1 and Adapter 2.  The
network routing protocol resides in two environments (Adapter 1 and
Adapter 2).  The network management agent/subagent resides in a third
environment (the System Card) which is separated from the network
routing protocols environments.  It should be noted that data which
originates at Node A and is being sent to through Node B to Node C
has a different path through Node B than the data which originates at
Node C and is being sent to through Node B to Node A.

      A variety of problems need to be addressed in order to allow
the network management agent/subagent to retrieve the data-objects
for a given session/resource from the network routing protocol which
is running in multiple environments within the same physical box.
These problems include:

1.  Each routing protocol environment will have incomplete knowledge
    of the network management data-objects for the session.

    o   Each Session Connector Manager (SCM) or Session Connector
...