Definitions of Managed Objects for APPN
RFC 2455

information about network usage and performance, as corporate assets;
   such enterprises may wish to restrict SNMP access to most of the
   objects in the MIB.

   Four of the read-write objects in the MIB can affect network
   operations; it is recommended that SNMP access to these objects be
   restricted.  The four objects are:

   o    appnNodeNnSafeStoreFreq:  Setting this object to 0, or to a very
        large value, effectively turns off safe storing of topology
        data.

   o    appnPortCommand, appnLsCommand:  These two objects allow an APPN
        port or link station to be activated, deactivated, or recycled
        via an SNMP operation.  The latter two operations may disrupt
        current users of the network.

   o    appnIsInSessState:  Setting this object to 'inactive' causes an
        active SNA session to be deactivated.

        Other read-write objects control the gathering of network
        management data; controlling access to these objects is less
        critical.

6.  Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11 [16].  Copies
   of claims of rights made available for publication and any assurances
   of licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementers or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.

Clouston & Moore            Standards Track                   [Page 136]
RFC 2455                        APPN MIB                   November 1998

7.  Acknowledgments

   This MIB module is the product of the IETF SNA NAU MIB WG and the AIW
   APPN/HPR MIBs SIG.  Thanks to Wayne Clark, Cisco Systems; Jim Cobban,
   Nortel; Rich Daugherty, IBM Corporation; Mark Regan, Cisco Systems;
   and Leo Temoshenko, IBM Corporation, for their contributions and
   review.

8.  References

   [1]  Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
        Describing SNMP Management Frameworks", RFC 2271, January 1998.

   [2]  Rose, M., and K. McCloghrie, "Structure and Identification of
        Management Information for TCP/IP-based Internets", STD 16, RFC
        1155, May 1990.

   [3]  Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
        RFC 1212, March 1991.

   [4]  Rose, M., "A Convention for Defining Traps for use with the
        SNMP", RFC 1215, March 1991.

   [5]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Structure of Management Information for Version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1902, January 1996.

   [6]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
        Conventions for Version 2 of the Simple Network Management
        Protocol (SNMPv2)", RFC 1903, January 1996.

   [7]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Conformance Statements for Version 2 of the Simple Network
        Management Protocol (SNMPv2)", RFC 1904, January 1996.

   [8]  Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
        Network Management Protocol", STD 15, RFC 1157, May 1990.

   [9]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Introduction to Community-based SNMPv2", RFC 1901, January
        1996.

   [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Transport Mappings for Version 2 of the Simple Network
        Management Protocol (SNMPv2)", RFC 1906, January 1996.

Clouston & Moore            Standards Track                   [Page 137]
RFC 2455                        APPN MIB                   November 1998

   [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
        Processing and Dispatching for the Simple Network Management
        Protocol (SNMP)", RFC 2272, January 1998.

   [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
        for version 3 of the Simple Network Management Protocol
        (SNMPv3)", RFC 2274, January 1998.

   [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
        Operations for Version 2 of the Simple Network Management
        Protocol (SNMPv2)", RFC 1905, January 1996.

   [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
        2273, January 1998.

   [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
        Control Model (VACM) for the Simple Network Management Protocol
        (SNMP)", RFC 2275, January 1998.

   [16] Hovey, R., and S. Bradner, "The Organizations Involved in the
        IETF Standards Process", BCP 11, RFC 2028, October 1996.

   [17] Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [18] IBM, Systems Network Architecture Technical Overview, GC30-3073.

   [19] IBM, Systems Network Architecture APPN Architecture Reference,
        SC30-3422

   [20] IBM, Systems Network Architecture Formats, SC30-3346.

   [21] Allen, M., Clouston, B., Kielczewski, Z., Kwan, W., and B.
        Moore, "Definition of Managed Objects for APPC", RFC 2051,
        December 1995.

   [22] Kielczewski, Z., Kostick D., and K. Shih, "Definition of Managed
        Objects for SNA NAUs using SMIv2", RFC 1666, August 1994.

   [23] Clouston, B., and B. Moore, "Definitions of Managed Objects for
        DLUR", RFC 2232, November 1996.

   [24] Clouston, B., and B. Moore, "Definitions of Managed Objects for
        HPR", RFC 2238, November 1996.

Clouston & Moore            Standards Track                   [Page 138]
RFC 2455                        APPN MIB                   November 1998

   [25] SNA DLC Services MIB Working Group, Hilgeman, J., Nix, S.,
        Bartky, A., and W. Clark, "Definitions of Managed Objects for
        SNA Data Link Control (SDLC) using SMIv2", RFC 1747, January
        1995.

   [26] SNA DLC Services MIB Working Group, Berl, S., Nix, S., and W.
        Clark, "Definitions of Managed Objects for SNA Data Link
        Control: LLC", May 1995.

   [27] Chen, D., Gayek, P., and S. Nix, "Definitions of Managed Objects
        for Data Link Switching using SNMPv2", RFC 2024, October 1995.

   [28] IBM, Systems Network Architecture Management Services Formats,
        GC31-8302.

   [29] Clouston, B., and B. Moore, "Definitions of Managed Objects for
        APPN", RFC 2155, June 1997.

9.  Authors' Addresses

   Bob Clouston
   Cisco Systems
   7025 Kit Creek Road
   P.O. Box 14987
   Research Triangle Park, NC 27709, USA

   Phone: +1 919 472 2333
   EMail: clouston@cisco.com

   Robert Moore
   Dept. BRQA/Bldg. 501/G114
   IBM Corporation
   P.O.Box 12195
   3039 Cornwallis
   Research Triangle Park, NC 27709, USA

   Phone: +1 919 254 4436
   EMail: remoore@us.ibm.com

Clouston & Moore            Standards Track                   [Page 139]
RFC 2455                        APPN MIB                   November 1998

10.  Full Copyright Statement

   Copyright (C) The Internet Society (1998).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Clouston & Moore            Standards Track                   [Page 140]