Simple Network Management Protocol-SNMP
Steve Steinke
Abstract
Steve Steinke
Abstract
THE SMI \nThe SMI specifies the allowable data types in the MIB, and it spells out the ways data can be represented. Also, it defines a hierarchical naming structure that ensures unique, unambiguous \nnames for managed objects, which are the components of a MIB. Compared with the objects \nthat general purpose programmers use to build applications, SNMP-managed objects are very \nsimple and stripped down. MIB objects typically have six or so attributes. For instance, an \nobject usually has a name, such as iflnErrorsortcpAttemptFails; an object identifier in dotted \ndecimal form, such as 1.3.6.1.2.1.2.2.1.14; a syntax field, which selects one of several possible \ndata types such as Integer, IPAddress, or Counter; an access field, which selects among "notaccessible;&s; "read-only;&s; "read-write;&s; and "write-only"; a status field consisting of either \n"mandatory;&s;"optional;&s;"deprecated;&s; or "obsolete"; and a text description of the object.
OpenAlex reports 1163 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
THE SMI \nThe SMI specifies the allowable data types in the MIB, and it spells out the ways data can be represented. Also, it defines a hierarchical naming structure that ensures unique, unambiguous \nnames for managed objects, which are the components of a MIB. Compared with the objects \nthat general purpose programmers use to build applications, SNMP-managed objects are very \nsimple and stripped down. MIB objects typically have six or so attributes. For instance, an \nobject usually has a name, such as iflnErrorsortcpAttemptFails; an object identifier in dotted \ndecimal form, such as 1.3.6.1.2.1.2.2.1.14; a syntax field, which selects one of several possible \ndata types such as Integer, IPAddress, or Counter; an access field, which selects among "notaccessible;&s; "read-only;&s; "read-write;&s; and "write-only"; a status field consisting of either \n"mandatory;&s;"optional;&s;"deprecated;&s; or "obsolete"; and a text description of the object.
Key concepts: Simple Network Management Protocol, Simple (philosophy), Computer science, Protocol (science), Computer network, Network management, Medicine, Philosophy