As per Relevance of the word february, we have this rfc below:
Network Working Group R.
Request for Comments: 1298 S.
Novell, Inc
February 1992
SNMP over
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
This memo defines a convention for encapsulating Simple
Management Protocol (SNMP) [1] packets over the transport
provided via the Internetwork Packet Exchange (IPX) protocol [2].
Editor's
As stated below and in reference [5], it is strongly advised that
interoperability, SNMP be implemented over UDP/IP and not directly
media or other protocols (such as IPX).
1.
The SNMP protocol has been specified as the official
management protocol of the Internet. Its widespread acceptance
implementation by developers, both inside and outside the
community, is fostering synergetic growth to a variety of
and platforms
This memo addresses the use of SNMP over the IPX protocol, which
become quite widespread principally due to the popularity of
NetWare. Roughly equivalent to UDP in function, IPX
connectionless, unacknowledged datagram service over a variety
physical media and protocols
Although modifications have been made elsewhere in the
protocol suite, IPX is identical to the Xerox Internet
Protocol (IDP) [3]. The socket address space authority
administered by Novell
The use of SNMP over the UDP transport [4] is today the common
of operation in the Internet. This specification may be
for some environments in which UDP transport services are
Wormley & Bostock [Page 1]
RFC 1298 SNMP over IPX February 1992
available. SNMP implementors should be aware that the choice
underlying transport may have a significant impact on
interoperability and ubiquity of the management capability in
Internet. Considerations relevant to choosing a transport for
with SNMP are described in [5].
2.
SNMP packets will always set the Packet Type field in the IPX
to 4 (i.e., Packet Exchange Packet).
2.1 Socket
SNMP protocol entities will receive GetRequest-PDU, GetNextRequest
PDU, and SetRequest-PDU messages on socket 36879 (Destination
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
socket from which the corresponding GetRequest-PDU, GetNextRequest
PDU, or SetRequest-PDU originated
2.2 Maximum Packet
Although SNMP does not require conformant implementations to
messages whose length exceed 484 bytes, it is recommended
implementations support a maximum SNMP message size of 546 bytes (
maximum size allowed under IPX). Furthermore, this limit is
maximum packet length guaranteed to traverse IPX routers which do
provide fragmentation. Implementors may choose to use longer
lengths if the maximum is known, which depends on the
routers and/or intermediate datalink layer protocols
2.3 The agent-addr Field for the Trap-
The agent-addr field in a Trap-PDU emitted by an SNMP agent
contain the IpAddress 0.0.0.0. An SNMP manager may ascertain
source of the trap by querying the transport layer
2.4 IPX Transport Address
There are occasions when it is necessary to represent a
service address in a MIB. For instance, the SNMP party MIB [6]
an OBJECT IDENTIFIER to define the transport domain (IP, IPX, etc.)
and an OCTET STRING to represent an address within that domain.
following definitions are provided for use in such a scheme
Wormley & Bostock [Page 2]
RFC 1298 SNMP over IPX February 1992
RFC1298-MIB DEFINITIONS ::=
enterprises FROM RFC1155-SMI
novell OBJECT IDENTIFIER ::= { enterprises 23 }
transportDomains OBJECT IDENTIFIER ::= { novell 7 }
ipxTransportDomain OBJECT IDENTIFIER ::= { transportDomains 1 }
-- Authoritatively names the IPX Transport
IpxTransportAddress ::= OCTET STRING (SIZE (12))
-- A textual convention denoting a transport service address
-- the ipxTransportDomain. An IpxTransportAddress is 12
-- long and comprises 3 fields, each in network-byte (high-low
-- order
-- The first field is 4 octets long and contains the
-- number
-- The next field is 6 octets long and contains the
-- address of the node. Since IPX can run over a variety
-- subnet architectures, the physical node address may
-- require all 6 octets. As specified in [2], the
-- node address will occupy the least significant portion
-- the field and the most significant octets should be
-- to zero
-- The last field is 2 octets long and contains the
-- number
3. Document
This section provides contact points for procurement of
documents
A complete description of IPX may be secured at the
address
Novell, Inc
122 East 1700
P. O. Box 5900
Provo, Utah 84601
800 526 5463
Wormley & Bostock [Page 3]
RFC 1298 SNMP over IPX February 1992
Novell Part # 883-000780-001
The specification for IDP (part of XNS) may be ordered from
Xerox System
475 Oakmead
Sunnyvale, CA 94086
Attn: Fonda
(415) 813-7164
4.
[1] Case J., Fedor M., Schoffstall M., and J. Davin, "A
Network Management Protocol (SNMP)", RFC 1157, SNMP Research
Performance Systems International, Performance
International, and MIT Laboratory for Computer Science, May 1990.
[2] Novell, Inc., "NetWare System Technical Interface Overview",
1989.
[3] Xerox System Integration Standard, "Internet
Protocols", XSIS 028112, Xerox Corporation, December 1981.
[4] Postel, J., "User Datagram Protocol," RFC 768, USC/
Sciences Institute, 28 August 1980.
[5] Kastenholz, F., "SNMP Communications Services," RFC 1270,
Clearpoint Research Corporation, October 1991.
[6] McCloghrie, K., Davin, J., and J. Galvin, "Definitions of
Objects for Administration of SNMP Parties", RFC in preparation
5. Security
Security issues are not discussed in this memo
Wormley & Bostock [Page 4]
RFC 1298 SNMP over IPX February 1992
6. Authors'
Raymond Brett
Novell, Inc
2180 Fortune
Mail Stop F5-91-2
San Jose, CA 95131
Phone: 408 473 8208
EMail: bwormley@novell.
Steve
Novell, Inc
2180 Fortune
Mail Stop F5-91-2
San Jose, CA 95131
Phone: 408 473 8203
EMail: steveb@novell.
Wormley & Bostock [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
