<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>

<!--
     ASCII to XML transformation by Invisible Worlds, Inc.
     http://invisible.net/
     Last transformation: 03-Feb-1999, 02:08:02

     Cannonical version of this document is at:
     http://info.internet.isi.edu/in-notes/rfc/files/rfc2013.txt

     Implementors should verify all content with
     cannonical version.  Failure to do so may result in
     protocol failures.
-->

<rfc number="2013"
     category="std"
     updates="1213">
<front>
<title abbrev="UDP MIB">SNMPv2 Management Information Base for the User Datagram Protocol using SMIv2</title>
<author initials="K." surname="McCloghrie" fullname="Keith McCloghrie">
<organization>Cisco Systems, Inc.</organization>
<address>
<postal>
<street>170 West Tasman Drive</street>
<street>San Jose</street>
<street>CA  95134-1706</street>
<country>US</country>
</postal>
<phone>+1 408 526 5260</phone>
<email>kzm@cisco.com</email>
</address>
</author>
<date month="November" year="1996"/>
<area>Transport</area>
<area>Management</area>
<keyword>Management Information Base</keyword>
<keyword>datagram</keyword>
<keyword>simple network management protocol version 2</keyword>
<keyword>structure of management information version 2</keyword>
<keyword>user datagram protocol</keyword>
<note title="IESG Note">
<t>
   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 RFC
   1902, SMI for SNMPv2.)  They do not support the new 128-bit IPv6
   internet addresses.
</t>
</note>
</front>
<middle>
<!-- RFC original section: (1.) -->
<section title="Introduction">
<t>
   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.
</t>
<t>
   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.
</t>
<t>
   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&apos;s
   Abstract Syntax Notation One (ASN.1) <xref target="_XREF_1"/>, termed the Structure of
   Management Information (SMI) <xref target="_XREF_2"/>.
</t>
<t>
   This document is the MIB module which defines managed objects for
   managing implementations of the User Datagram Protocol (UDP) <xref target="_XREF_3"/>.
</t>
<t>
   The managed objects in this MIB module were originally defined using
   the SNMPv1 framework as a part of MIB-II <xref target="_XREF_4"/>.  This document defines
   the same objects for UDP using the SNMPv2 framework.
</t>
</section>
<!-- RFC original section: (2.) -->
<section title="Definitions">
<figure><artwork>
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 &quot;9411010000Z&quot;
    ORGANIZATION &quot;IETF SNMPv2 Working Group&quot;
    CONTACT-INFO
            &quot;        Keith McCloghrie


             Postal: Cisco Systems, Inc.
                     170 West Tasman Drive
                     San Jose, CA  95134-1706
                     US


             Phone:  +1 408 526 5260
             Email:  kzm@cisco.com&quot;


    DESCRIPTION
            &quot;The MIB module for managing UDP implementations.&quot;
    REVISION      &quot;9103310000Z&quot;
    DESCRIPTION
            &quot;The initial revision of this MIB module was part of MIB-
            II.&quot;
    ::= { mib-2 50 }


-- the UDP group


udp      OBJECT IDENTIFIER ::= { mib-2 7 }


udpInDatagrams OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            &quot;The total number of UDP datagrams delivered to UDP users.&quot;
    ::= { udp 1 }


udpNoPorts OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            &quot;The total number of received UDP datagrams for which there
            was no application at the destination port.&quot;
    ::= { udp 2 }


udpInErrors OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            &quot;The number of received UDP datagrams that could not be
            delivered for reasons other than the lack of an application
            at the destination port.&quot;
    ::= { udp 3 }


udpOutDatagrams OBJECT-TYPE
    SYNTAX      Counter32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            &quot;The total number of UDP datagrams sent from this entity.&quot;
    ::= { udp 4 }


-- the UDP Listener table


-- The UDP listener table contains information about this
-- entity&apos;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
            &quot;A table containing UDP listener information.&quot;
    ::= { udp 5 }


udpEntry OBJECT-TYPE
    SYNTAX      UdpEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
            &quot;Information about a particular current UDP listener.&quot;
    INDEX   { udpLocalAddress, udpLocalPort }
    ::= { udpTable 1 }


UdpEntry ::= SEQUENCE {
        udpLocalAddress  IpAddress,
        udpLocalPort     INTEGER
    }


udpLocalAddress OBJECT-TYPE
    SYNTAX      IpAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            &quot;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.&quot;
    ::= { udpEntry 1 }


udpLocalPort OBJECT-TYPE
    SYNTAX      INTEGER (0..65535)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            &quot;The local port number for this UDP listener.&quot;
    ::= { udpEntry 2 }


-- 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
            &quot;The compliance statement for SNMPv2 entities which
            implement UDP.&quot;
    MODULE  -- this module
        MANDATORY-GROUPS { udpGroup
                           }
    ::= { udpMIBCompliances 1 }


-- units of conformance


udpGroup OBJECT-GROUP
    OBJECTS   { udpInDatagrams, udpNoPorts,
                udpInErrors, udpOutDatagrams,
                udpLocalAddress, udpLocalPort }
    STATUS    current
    DESCRIPTION
            &quot;The udp group of objects providing for management of UDP
            entities.&quot;
    ::= { udpMIBGroups 1 }


END
</artwork></figure>
</section>
<!-- RFC original section: (3.) -->
<section title="Acknowledgements">
<t>
   This document contains a modified subset of RFC 1213.
</t>
</section>
<!-- RFC original section: (4.) -->
<section title="References (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;References.&quot;
</t>
</section>
<!-- RFC original section: (5.) -->
<section title="Security Considerations">
<t>
   Security issues are not discussed in this memo.
</t>
</section>
<!-- RFC original section: (6.) -->
<section title="Editor&apos;s Address (BOILERPLATE)">
<t>
This RFC contained boilerplate in this section which has been moved
to the RFC2223-compliant unnumbered section &quot;Author&apos;s Address.&quot;
</t>
</section>
</middle>
<back>
<!-- BEGIN INCLUDE REFERENCES ** DO NOT REMOVE -->
<references>
<reference anchor="_XREF_1">
<front>
<title abbrev="Information processing systems - Open Systems">Information processing systems - Open Systems Interconnection Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization.  International Standard 8824</title>
<author>
<organization/>
</author>
<date month="December" year="1987"/>
</front>
</reference>
<reference anchor="_XREF_2">
<front>
<title abbrev="Structure of Management Information">Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2,  Cisco Systems</title>
<author initials="K." surname="McCloghrie" fullname="K. McCloghrie">
<organization/>
</author>
<date month="January" year="1996"/>
</front>
<seriesInfo>RFC 1902</seriesInfo>
</reference>
<reference anchor="_XREF_3">
<front>
<title>User Datagram Protocol,  USC-ISI</title>
<author initials="J." surname="Postel" fullname="J. Postel">
<organization/>
</author>
<date month="August" year="1980"/>
</front>
<seriesInfo>STD 6</seriesInfo>
<seriesInfo>RFC 768</seriesInfo>
</reference>
<reference anchor="_XREF_4">
<front>
<title abbrev="Management Information Base for Network">Management Information Base for Network Management of TCP/IP-based internets: MIB-II</title>
<author initials="K." surname="McCloghrie" fullname="K. McCloghrie">
<organization/>
</author>
<author initials="M." surname="Rose" fullname="M. Rose">
<organization/>
</author>
<date month="March" year="1991"/>
</front>
<seriesInfo>STD 17</seriesInfo>
<seriesInfo>RFC 1213</seriesInfo>
</reference>
</references>
<!-- END INCLUDE REFERENCES ** DO NOT REMOVE -->
</back>
</rfc>
