| 1 |
<pre>Network Working Group M. Schoffstall |
| 2 |
Request for Comments: 1089 Rensselaer Polytechnic Institute |
| 3 |
C. Davin |
| 4 |
MIT Laboratory for Computer Science |
| 5 |
M. Fedor |
| 6 |
NYSERNet, Inc. |
| 7 |
J. Case |
| 8 |
University of Tennessee at Knoxville |
| 9 |
February 1989 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">SNMP over Ethernet</span> |
| 13 |
|
| 14 |
Status of This Memo |
| 15 |
|
| 16 |
This memo describes an experimental method by which the Simple |
| 17 |
Network Management Protocol (SNMP) as specified in [<a href="#ref-1" title=""A Simple Network Management Protocol"">1</a>] can be used |
| 18 |
over Ethernet MAC layer framing [<a href="#ref-2" title=""The Ethernet - A Local Area Network"">2</a>] instead of the Internet UDP/IP |
| 19 |
protocol stack. This specification is useful for LAN based network |
| 20 |
elements that support no higher layer protocols beyond the MAC sub- |
| 21 |
layer. Distribution of this memo is unlimited. |
| 22 |
|
| 23 |
Overview and Rational |
| 24 |
|
| 25 |
SNMP has been successful in managing Internet capable network |
| 26 |
elements which support the protocol stack at least through UDP the |
| 27 |
connectionless Internet transport layer protocol. As originally |
| 28 |
designed, SNMP is capable of running over any reasonable transport |
| 29 |
mechanism (not necessarily a transport protocol) that supports bi- |
| 30 |
directional flow and addressability. |
| 31 |
|
| 32 |
Many non-Internet capable network elements are present in local |
| 33 |
networks; for example, repeaters and wiring concentrators. They |
| 34 |
include both addressability, and programmable intelligence. These |
| 35 |
devices are widely used and increasingly important yet, for the most |
| 36 |
part, invisible except through proprietary mechanisms. |
| 37 |
|
| 38 |
Specification |
| 39 |
|
| 40 |
Almost all Internet capable network elements use the same mechanism |
| 41 |
for encapsulation of the Internet protocol stack regardless of |
| 42 |
conformity with the physical characteristics of Ethernet or 802.3, |
| 43 |
this mechanism is specified in [<a href="#ref-3" title=""A Standard for the Transmission of IP Datagrams over Ethernet Networks"">3</a>] and [<a href="#ref-4" title=""A Standard for the Transmission of IP Datagrams over IEEE 802 Networks"">4</a>]. This specification |
| 44 |
continues that style with the assignment (by XEROX) of 33100 |
| 45 |
(hexadecimal 814C) to the Ethernet Type field for SNMP. The data |
| 46 |
portion of the Ethernet frame would then be a standard SNMP message |
| 47 |
as specified in [<a href="#ref-1" title=""A Simple Network Management Protocol"">1</a>]. |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Schoffstall, Davin, Fedor & Case [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1089">RFC 1089</a> SNMP over Ethernet February 1989</span> |
| 55 |
|
| 56 |
|
| 57 |
References |
| 58 |
|
| 59 |
[<a id="ref-1">1</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple |
| 60 |
Network Management Protocol", <a href="./rfc1067">RFC-1067</a>, University of |
| 61 |
Tennessee at Knoxville, NYSERNet, Inc., Rensselaer Polytechnic |
| 62 |
Institute, and Proteon, Inc., August 1988. |
| 63 |
|
| 64 |
[<a id="ref-2">2</a>] DEC, "The Ethernet - A Local Area Network", Version 2.0, |
| 65 |
Digital Equipment Corporation, Intel Corporation, Xerox |
| 66 |
Corporation. |
| 67 |
|
| 68 |
[<a id="ref-3">3</a>] Hornig, C., "A Standard for the Transmission of IP Datagrams |
| 69 |
over Ethernet Networks", <a href="./rfc894">RFC-894</a>, Symbolics, April 1984. |
| 70 |
|
| 71 |
[<a id="ref-4">4</a>] Postel, J., and J. Reynolds, "A Standard for the Transmission |
| 72 |
of IP Datagrams over IEEE 802 Networks", <a href="./rfc1042">RFC-1042</a>, USC |
| 73 |
Information Sciences Institute, February 1988. |
| 74 |
|
| 75 |
Authors' Addresses |
| 76 |
|
| 77 |
Marty Schoffstall |
| 78 |
NYSERNET Inc. |
| 79 |
Rensselaer Technology Park |
| 80 |
165 Jordan Road |
| 81 |
Troy, NY 12180 |
| 82 |
|
| 83 |
Phone: (518) 276-2654 |
| 84 |
|
| 85 |
EMail: [email protected] |
| 86 |
|
| 87 |
|
| 88 |
Chuck Davin |
| 89 |
MIT Laboratory for Computer Science, NE43-507 |
| 90 |
545 Technology Square |
| 91 |
Cambridge, MA 02139 |
| 92 |
|
| 93 |
Phone: (617) 253-6020 |
| 94 |
|
| 95 |
EMail: [email protected] |
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Schoffstall, Davin, Fedor & Case [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1089">RFC 1089</a> SNMP over Ethernet February 1989</span> |
| 111 |
|
| 112 |
|
| 113 |
Mark Fedor |
| 114 |
Nysernet, Inc. |
| 115 |
Rensselaer Technology Park |
| 116 |
125 Jordan Road |
| 117 |
Troy, NY 12180 |
| 118 |
(518) 283-8860 |
| 119 |
|
| 120 |
Phone: (518) 283-8860 |
| 121 |
|
| 122 |
EMail: [email protected] |
| 123 |
|
| 124 |
|
| 125 |
Jeff Case |
| 126 |
University of Tennessee Computing Center |
| 127 |
Associate Director |
| 128 |
200 Stokely Management Center |
| 129 |
Knoxville, TN 37996-0520 |
| 130 |
|
| 131 |
Phone: (615) 974-6721 |
| 132 |
|
| 133 |
EMail: [email protected] |
| 134 |
|
| 135 |
|
| 136 |
|
| 137 |
|
| 138 |
|
| 139 |
|
| 140 |
|
| 141 |
|
| 142 |
|
| 143 |
|
| 144 |
|
| 145 |
|
| 146 |
|
| 147 |
|
| 148 |
|
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
Schoffstall, Davin, Fedor & Case [Page 3] |
| 165 |
</pre> |