Definitions of Managed Objects for Data Link Switching using SMIv2

Voir toute la rfc dans une seule page

Télécharger le PDF

RFC 2024                  DLSw MIB using SMIv2              October 1996


                           directory function.

   dlswDirLocateCompliance Defines the minimum support required of
                           implementations that support a directory
                           function and also support the ordered
                           retrieval of the entries that match a given
                           resource.

   dlswSdlcCompliance      Defines the minimum support required of
                           implementations that support SDLC-attached
                           end stations.
2.5  DLSw MIB Usage

2.5.1  Cooperative DLSw nodes

   To reduce the size of the MIB, thus the amount of data that each
   agent needs to keep, the information that usually could be made
   available in two partner nodes (e.g., information exchanged between
   them) is only defined in the MIB as the info received.  That is,
   there are no objects defined for the info sent.  In order to form the
   complete picture of the state of a resource, the manager needs to
   retrieve info from multiple DLSw nodes.  An example is that the SAP
   list, NETBIOS list and MAC list are kept at the receiving end of a
   DLSw capabilities exchange (the sender does not save what it sent to
   each partner).

   Note well:  The DLSw protocol does not specify a technique for a
   manager to correlate the transport address of the partner managed
   DLSw node and the transport address that the management protocol
   uses.

2.5.2  Setting capabilities exchange-related objects

   This MIB supports changes to DLSw variables whose change should be
   reported to DLSw partner nodes in a "run-time" capabilities exchange.
   Since a DLSw node normally unicasts these capabilities messages to
   all its active partners, frequent changes to these variables can
   result in excessive network traffic.  To avoid this problem,
   developers of network management applications using this MIB should
   try to group all such changes in a few SNMP SET requests, and should
   send them in bulk.  Agent developers should implement a technique to
   group a number of changes into a single capabilities exchange
   message.  One possible approach is to send a run-time capabilities
   message only if no capabilities-related changes have been received
   for a pre-defined period of time.






Chen, et. al.               Standards Track                     [Page 5]