SNMP over IPX

Network Working Group                                        S. Bostock
Request for Comments: 1420                                 Novell, Inc.
Obsoletes: <a href="./rfc1298">1298</a>                                              March 1993


                             <span class="h1">SNMP over IPX</span>

Status of this Memo

   This RFC specifies an IAB standards track protocol for the Internet
   community, and requests discussion and suggestions for improvements.
   Please refer to the current edition of the "IAB Official Protocol
   Standards" for the standardization state and status of this protocol.
   Distribution of this memo is unlimited.

Abstract

   This document defines a convention for encapsulating Simple Network
   Management Protocol (SNMP) [<a href="#ref-1" title=""Simple Network Management Protocol"">1</a>] packets over the transport mechanism
   provided via the Internetwork Packet Exchange (IPX) protocol [<a href="#ref-2" title=""NetWare System Technical Interface Overview"">2</a>].

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>

   The Simple Network Management Protocol (SNMP) as defined in [<a href="#ref-1" title=""Simple Network Management Protocol"">1</a>] is
   now used as an integral part of the network management framework for
   TCP/IP-based internets.  Together with its companion standards, which
   define the Structure of Management Information (SMI) [<a href="#ref-3" title=""Structure and Identification of Management Information for TCP/IP-based internets"">3</a>,<a href="#ref-4" title=""Concise MIB Definitions"">4</a>], and the
   Management Information Base (MIB) [<a href="#ref-5" title=""Management Information Base for Network Management of TCP/IP-based Internets"">5</a>], the SNMP has received
   widespread deployment in many operational networks running the
   Internet suite of protocols.

   The success of SNMP in the TCP/IP environment has led to its
   deployment in non TCP/IP-based internets. This specification
   describes the mapping of SNMP onto the Internetwork Packet Exchange
   (IPX) protocol [<a href="#ref-2" title=""NetWare System Technical Interface Overview"">2</a>] used in Novell NetWare environments.

   As noted in [<a href="#ref-6" title=""SNMP Communications Services"">6</a>], the preferred mapping for SNMP is onto UDP [<a href="#ref-7" title=""User Datagram Protocol"">7</a>].  As
   such, this specification is intended for use in environments where
   UDP transport is not available.  No aspect of this specification
   should be construed as a suggestion that, in a heterogeneous
   transport environment, a managed agent should support more than one
   mapping. Conversely, management stations are strongly encouraged to
   support mappings of SNMP onto all popular transports.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Mapping SNMP onto IPX</span>

   Mapping SNMP onto IPX is straight-forward since IPX provides a
   datagram service very similar to that provided by IP/UDP.



<span class="grey">Bostock                                                         [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc1420">RFC 1420</a>                     SNMP over IPX                    March 1993</span>


   Although modifications have been made elsewhere in the NetWare
   protocol suite, IPX is identical to the Xerox Internet Datagram
   Protocol (IDP) [<a href="#ref-8" title=""Internet Transport Protocols"">8</a>].  The socket address space authority is
   administered by Novell.

   SNMP packets will always set the Packet Type field in the IPX header
   to 4 (i.e., Packet Exchange Packet).

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>  Socket Assignments</span>

   SNMP protocol entities will receive GetRequest-PDU, GetNextRequest-
   PDU, and SetRequest-PDU messages on socket 36879 (Destination Socket
   field set to hexadecimal 900F), and Trap-PDU messages on socket 36880
   (Destination Socket field set to hexadecimal 9010).

   GetResponse-PDU messages will be addressed to the IPX address and
   socket from which the corresponding GetRequest-PDU, GetNextRequest-
   PDU, or SetRequest-PDU originated.

<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>  Traps</span>

   When SNMP traps are sent over IPX, the agent-addr field in the Trap-
   PDU contains the IP-address "0.0.0.0".  An SNMP manager may ascertain
   the source of the trap based on information provided by the transport
   service

<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>  Maximum Message Size</span>

   Although SNMP does not require conformant implementations to accept
   messages whose length exceeds 484 bytes, it is recommended that
   implementations support a maximum SNMP message size of 546 bytes (the
   maximum size allowed under IPX).  Furthermore, this limit is the
   maximum packet length guaranteed to traverse IPX routers which do not
   provide fragmentation.  Implementors may choose to use longer packet
   lengths if the maximum is known, which depends on the intermediate
   routers and/or intermediate datalink layer protocols.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Document Procurement</span>

   This section provides contact points for procurement of selected
   documents.

   A complete description of IPX may be secured at the following
   address:







<span class="grey">Bostock                                                         [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc1420">RFC 1420</a>                     SNMP over IPX                    March 1993</span>


        Novell, Inc.
        122 East 1700 South
        P. O. Box 5900
        Provo, Utah 84601 USA
        800 526 5463

        Novell Part # 883-000780-001

   The specification for IDP (part of XNS) may be ordered from:

        Xerox System Institute
        475 Oakmead Parkway
        Sunnyvale, CA 94086
        Attn.: Fonda Pallone
        (415) 813-7164

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Acknowledgments</span>

   This specification was derived from <a href="./rfc1298">RFC 1298</a>, based on discussions in
   the IETF's "SNMP over a Multiprotocol Internet" Working Group.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  References</span>

   [<a id="ref-1">1</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
       Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, SNMP Research,
       Performance Systems International, Performance Systems
       International, MIT Laboratory for Computer Science, May 1990.

   [<a id="ref-2">2</a>] Novell, Inc., "NetWare System Technical Interface Overview", part
       number 883-000780-001, June 1989.

   [<a id="ref-3">3</a>] Rose M., and K. McCloghrie, "Structure and Identification of
       Management Information for TCP/IP-based internets", STD 16, <a href="./rfc1155">RFC</a>
       <a href="./rfc1155">1155</a>, Performance Systems International, Hughes LAN Systems, May
       1990.

   [<a id="ref-4">4</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
       STD 16, <a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN
       Systems, March 1991.

   [<a id="ref-5">5</a>] Rose M., and K. McCloghrie, Editors, "Management Information Base
       for Network Management of TCP/IP-based Internets", STD 17, <a href="./rfc1213">RFC</a>
       <a href="./rfc1213">1213</a>, Hughes LAN Systems, Inc., Performance Systems
       International, March 1991.

   [<a id="ref-6">6</a>] Kastenholz, F., "SNMP Communications Services", <a href="./rfc1270">RFC 1270</a>,
       Clearpoint Research Corporation, October 1991.




<span class="grey">Bostock                                                         [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc1420">RFC 1420</a>                     SNMP over IPX                    March 1993</span>


   [<a id="ref-7">7</a>] Postel J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>,
       USC/Information Sciences Institute, August 1980.

   [<a id="ref-8">8</a>] Xerox System Integration Standard, "Internet Transport
       Protocols", XSIS 028112, Xerox Corporation, December 1981.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Security Considerations</span>

   Security issues are not discussed in this memo.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Author's Address</span>

   Steve Bostock
   Novell, Inc.
   2180 Fortune Drive
   San Jose, CA 95131

   Phone: 408 473 8203
   Fax:   408 435 1706
   Email: [email protected]































Bostock                                                         [Page 4]