Browse Prior Art Database

SNMP over IPX (RFC1298)

IP.com Disclosure Number: IPCOM000002118D
Original Publication Date: 1992-Feb-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 5 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Wormley: AUTHOR [+1]

Related Documents

10.17487/RFC1298: DOI

Abstract

This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol. This memo provides information for the Internet community. It does not specify an Internet standard.

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

Network Working Group R. Wormley Request for Comments: 1298 S. Bostock Novell, Inc. February 1992

SNMP over IPX

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.

Abstract

This memo defines a convention for encapsulating Simple Network Management Protocol (SNMP) [1] packets over the transport mechanism provided via the Internetwork Packet Exchange (IPX) protocol [2].

Editor’s Note

As stated below and in reference [5], it is strongly advised that for interoperability, SNMP be implemented over UDP/IP and not directly on media or other protocols (such as IPX).

1. Introduction

The SNMP protocol has been specified as the official network management protocol of the Internet. Its widespread acceptance and implementation by developers, both inside and outside the Internet community, is fostering synergetic growth to a variety of protocols and platforms.

This memo addresses the use of SNMP over the IPX protocol, which has become quite widespread principally due to the popularity of Novell NetWare. Roughly equivalent to UDP in function, IPX provides connectionless, unacknowledged datagram service over a variety of physical media and protocols.

Although modifications have been made elsewhere in the NetWare protocol suite, IPX is identical to the Xerox Internet Datagram Protocol (IDP) [3]. The socket address space authority is administered by Novell.

The use of SNMP over the UDP transport [4] is today the common mode of operation in the Internet. This specification may be appropriate for some environments in which UDP transport services are not

Wormley & Bostock [Page 1]

RFC 1298 SNMP over IPX February 1992

available. SNMP implementors should be aware that the choice of underlying transport may have a significant impact on the interoperability and ubiquity of the management capability in the Internet. Considerations relevant to choosing a transport for use with SNMP are described in [5].

2. Specification

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

2.1 Socket Assignments

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.

2.2 Maximum Packet Length

Although SNMP does not require conformant implementations to accept messages whose length exceed 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 ch...

Processing...
Loading...