2013
PROPOSED STANDARD
SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2 (Obsoleted)
Authors: K. McCloghrie
Date: November 1996
Working Group: snmpv2
Stream: IETF
Abstract
This document is the MIB module which defines managed objects for managing implementations of the User Datagram Protocol (UDP). [STANDARDS-TRACK]
RFC 2013
Obsoleted by: 4113 PROPOSED STANDARD
Network Working Group K. McCloghrie, Editor
Request for Comments: 2013 Cisco Systems
Updates: <a href="./rfc1213">1213</a> November 1996
Category: Standards Track
<span class="h1">SNMPv2 Management Information Base</span>
<span class="h1">for the User Datagram Protocol using SMIv2</span>
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
IESG Note:
The IP, UDP, and TCP MIB modules currently support only IPv4. These
three modules use the IpAddress type defined as an OCTET STRING of
length 4 to represent the IPv4 32-bit internet addresses. (See <a href="./rfc1902">RFC</a>
<a href="./rfc1902">1902</a>, SMI for SNMPv2.) They do not support the new 128-bit IPv6
internet addresses.
Table of Contents
<a href="#section-1">1</a>. Introduction ................................................. <a href="#page-1">1</a>
<a href="#section-2">2</a>. Definitions .................................................. <a href="#page-2">2</a>
<a href="#section-2.1">2.1</a> The UDP Group ............................................... <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a> Conformance Information ..................................... <a href="#page-5">5</a>
<a href="#section-2.2.1">2.2.1</a> Compliance Statements ..................................... <a href="#page-5">5</a>
<a href="#section-2.2.2">2.2.2</a> Units of Conformance ...................................... <a href="#page-5">5</a>
<a href="#section-3">3</a>. Acknowledgements ............................................. <a href="#page-6">6</a>
<a href="#section-4">4</a>. References ................................................... <a href="#page-6">6</a>
<a href="#section-5">5</a>. Security Considerations ...................................... <a href="#page-6">6</a>
<a href="#section-6">6</a>. Editor's Address ............................................. <a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
A management system contains: several (potentially many) nodes, each
with a processing entity, termed an agent, which has access to
management instrumentation; at least one management station; and, a
management protocol, used to convey management information between
the agents and management stations. Operations of the protocol are
carried out under an administrative framework which defines
authentication, authorization, access control, and privacy policies.
<span class="grey">McCloghrie Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc2013">RFC 2013</a> SNMPv2 MIB for UDP November 1996</span>
Management stations execute management applications which monitor and
control managed elements. Managed elements are devices such as
hosts, routers, terminal servers, etc., which are monitored and
controlled via access to their management information.
Management information is viewed as a collection of managed objects,
residing in a virtual information store, termed the Management
Information Base (MIB). Collections of related objects are defined
in MIB modules. These modules are written using a subset of OSI's
Abstract Syntax Notation One (ASN.1) [<a href="#ref-1" title="(December">1</a>], termed the Structure of
Management Information (SMI) [<a href="#ref-2" title=""Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)"">2</a>].
This document is the MIB module which defines managed objects for
managing implementations of the User Datagram Protocol (UDP) [<a href="#ref-3" title=""User Datagram Protocol"">3</a>].
The managed objects in this MIB module were originally defined using
the SNMPv1 framework as a part of MIB-II [<a href="#ref-4" title=""Management Information Base for Network Management of TCP/IP-based internets: MIB-II"">4</a>]. This document defines
the same objects for UDP using the SNMPv2 framework.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Definitions</span>
UDP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32,
IpAddress, mib-2 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
udpMIB MODULE-IDENTITY
LAST-UPDATED "9411010000Z"
ORGANIZATION "IETF SNMPv2 Working Group"
CONTACT-INFO
" Keith McCloghrie
Postal: Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
US
Phone: +1 408 526 5260
Email: [email protected]"
<span class="grey">McCloghrie Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc2013">RFC 2013</a> SNMPv2 MIB for UDP November 1996</span>
DESCRIPTION
"The MIB module for managing UDP implementations."
REVISION "9103310000Z"
DESCRIPTION
"The initial revision of this MIB module was part of MIB-
II."
::= { mib-2 50 }
-- the UDP group
udp OBJECT IDENTIFIER ::= { mib-2 7 }
udpInDatagrams OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams delivered to UDP users."
::= { udp 1 }
udpNoPorts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of received UDP datagrams for which there
was no application at the destination port."
::= { udp 2 }
udpInErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of received UDP datagrams that could not be
delivered for reasons other than the lack of an application
at the destination port."
::= { udp 3 }
udpOutDatagrams OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of UDP datagrams sent from this entity."
::= { udp 4 }
<span class="grey">McCloghrie Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc2013">RFC 2013</a> SNMPv2 MIB for UDP November 1996</span>
-- the UDP Listener table
-- The UDP listener table contains information about this
-- entity's UDP end-points on which a local application is
-- currently accepting datagrams.
udpTable OBJECT-TYPE
SYNTAX SEQUENCE OF UdpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing UDP listener information."
::= { udp 5 }
udpEntry OBJECT-TYPE
SYNTAX UdpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a particular current UDP listener."
INDEX { udpLocalAddress, udpLocalPort }
::= { udpTable 1 }
UdpEntry ::= SEQUENCE {
udpLocalAddress IpAddress,
udpLocalPort INTEGER
}
udpLocalAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local IP address for this UDP listener. In the case of
a UDP listener which is willing to accept datagrams for any
IP interface associated with the node, the value 0.0.0.0 is
used."
::= { udpEntry 1 }
udpLocalPort OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The local port number for this UDP listener."
::= { udpEntry 2 }
<span class="grey">McCloghrie Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc2013">RFC 2013</a> SNMPv2 MIB for UDP November 1996</span>
-- conformance information
udpMIBConformance OBJECT IDENTIFIER ::= { udpMIB 2 }
udpMIBCompliances OBJECT IDENTIFIER ::= { udpMIBConformance 1 }
udpMIBGroups OBJECT IDENTIFIER ::= { udpMIBConformance 2 }
-- compliance statements
udpMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement UDP."
MODULE -- this module
MANDATORY-GROUPS { udpGroup
}
::= { udpMIBCompliances 1 }
-- units of conformance
udpGroup OBJECT-GROUP
OBJECTS { udpInDatagrams, udpNoPorts,
udpInErrors, udpOutDatagrams,
udpLocalAddress, udpLocalPort }
STATUS current
DESCRIPTION
"The udp group of objects providing for management of UDP
entities."
::= { udpMIBGroups 1 }
END
<span class="grey">McCloghrie Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc2013">RFC 2013</a> SNMPv2 MIB for UDP November 1996</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Acknowledgements</span>
This document contains a modified subset of <a href="./rfc1213">RFC 1213</a>.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
[<a id="ref-1">1</a>] Information processing systems - Open Systems Interconnection
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization. International
Standard 8824, (December, 1987).
[<a id="ref-2">2</a>] McCloghrie, K., Editor, "Structure of Management Information
for version 2 of the Simple Network Management Protocol
(SNMPv2)", <a href="./rfc1902">RFC 1902</a>, Cisco Systems, January 1996.
[<a id="ref-3">3</a>] Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>, USC-ISI,
August 1980.
[<a id="ref-4">4</a>] McCloghrie, K., and Rose, M., "Management Information Base for
Network Management of TCP/IP-based internets: MIB-II", STD 17,
<a href="./rfc1213">RFC 1213</a>, March 1991.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Security issues are not discussed in this memo.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Editor's Address</span>
Keith McCloghrie
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
US
Phone: +1 408 526 5260
EMail: [email protected]
McCloghrie Standards Track [Page 6]
Annotations
Select text to annotate