As per Relevance of the word required, we have this rfc below:
Network Working Group M.
Request for Comments: 2320 Xedia Corp
Category: Standards Track J.
Bay Networks, Inc
K.
IBM Corp
T.
Bay Networks, Inc
April 1998
Definitions of Managed Objects
Classical IP and ARP Over ATM Using SMIv
(IPOA-MIB
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
The purpose of this memo is to define the Management Information
(MIB) for supporting Classical IP and ARP over ATM as specified
Classical IP and ARP over ATM, refer to reference [3]. Support of
ATM interface by an IP layer will require implementation of
from several Management Information Bases (MIBs) as well as
enhancement in order to enable usage of ATM transports. It is
intent of this MIB to fully adhere to all prerequisite MIBs
explicitly stated. Deviations will be documented in
conformance statements. The specification of this MIB will
the Structure of Management Information (SMI) for Version 2 of
Simple Network Management Protocol Version (refer to RFC 1902,
reference [1]).
Greene, et al. [Page 1]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
Table of
1. Introduction............................................. 2
2. The SNMPv2 Network Management Framework.................. 3
2.1 Object Definitions...................................... 4
3. Structure of the MIB..................................... 4
3.1 Basic Support MIB Definitions........................... 5
3.1.1 ATM Logical IP Subnet (LIS) Table..................... 5
3.1.2 ATM Logical IP Subnet Interface Mapping Table......... 7
3.1.3 ATMARP Remote Server Table............................ 7
3.1.4 ATM VC Table.......................................... 8
3.1.5 ATM Config PVC Table.................................. 9
3.1.6 Notifications......................................... 10
3.2 Client Supported MIB Definitions........................ 10
3.2.1 ATMARP Client Table................................... 11
3.3 Server Supported MIB Definitions........................ 12
3.3.1 ATMARP Server Table................................... 12
3.3.2 Notifications......................................... 13
4. Definitions.............................................. 14
5. Security Considerations.................................. 48
6. Intellectual Property.................................... 49
7. Acknowledgments.......................................... 49
8. References............................................... 50
9. Authors' Addresses....................................... 51
10. Full Copyright Statement................................ 52
1.
This document is a product of the Internetworking Over NBMA
Group. Its purpose is to define a MIB module for extending
traditional MIBs supported by a TCP/IP implementation to
Classical IP and ARP over ATM
Many MIB related RFCs and Internet Drafts have been considered in
development of this document. The ones that are considered central
the extensions defined by this document are
o RFC 2011 - SNMPv2 Management Information Base for
Internet Protocol using SMIv2 [9]. The IP over
(IPOA) MIB provides extensions to the IP Group
handling IP over ATM flows. A basic understanding
the IP Group is essential for understanding
document
Greene, et al. [Page 2]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
o RFC 2233 - The Interfaces Group MIB (IF-MIB) using SMIv2,
reference [2]. This document is important since
provides several very useful enhancements over
interface group defined in RFC 1213 (reference [5])
that aid in handling ATM related interfaces
o RFC 1695 - Definitions of Managed Objects for ATM
[4] (ATM-MIB). Support of this MIB is REQUIRED
implementing the layers between AAL5 and ATM.
contents of this MIB will not explicitly be
here. The ATM-MIB provides a basis for managing
interface layering and management of
- ATM Switched Virtual Connections (SVCs
- ATM Permanent Virtual Connections (PVCs
The ATM Forum UNI ILMI MIB is specified by the ATM Forum in
versions of the UNI specification. The ILMI MIBs being defined
not supported via SNMP agents but via SNMP requests sent over an
network to an ATM entity encapsulated in an AAL5 header. Support
the ILMI MIB(s) is considered out of the scope of this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119,
[10].
2. The SNMPv2 Network Management
The SNMPv2 Network Management Framework consists of seven
components. They are
o RFC 1902 [1] which defines the SMI, the mechanisms used
describing and naming objects for the purpose of management
o RFC 1903 [6] defines textual conventions for SNMPv2.
o RFC 1904 [8] defines conformance statements for SNMPv2.
o RFC 1905 [7] defines transport mappings for SNMPv2.
o RFC 1906 [12] defines the protocol operations used for
access to managed objects
o RFC 1907 [13] defines the Management Information Base for SNMPv2.
o RFC 1908 [14] specifies coexistence between SNMPv1 and SNMPv2.
Greene, et al. [Page 3]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
This memo specifies a MIB module that is compliant to the SNMPv2 SMI
A semantically identical MIB conforming to the SNMPv1 SMI can
produced through the appropriate translation
2.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The object
together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience, we
use a textual string, termed the descriptor, to refer to the
type
3. Structure of the
The Classical ARP and IP over ATM (IPOA) MIB structure is split
three components
o Basic Support MIB
o Client Supported MIB
o Server Supported MIB
All IP and ARP over ATM entities, both clients and ATMARP Servers,
REQUIRED to support the MIB definitions in the Basic Support
Definitions section. Clients need to additionally support the
definitions outlined in the Client specific section and ATMARP
MUST additionally support the ATMARP Server specific MIB definitions
Implementation of the Definitions of Managed Objects for
Management [4] defines the modeling of the various layers within
ATM Interface. This modeling is assumed as a prerequisite for
IPOA-MIB. The IPOA-MIB makes no assumptions on how this layering
actually implemented within a system. Several of the MIB
defined by the IPOA-MIB, like the base TCP/IP MIBs, require that
ifIndex exist that points to an ATM Interface. Refer to the ATM-
[4] for the definition of ATM Interface layering
The use of an IP over ATM Virtual Interface layer is NOT
REQUIRED by the IPOA-MIB. The use of virtual layers above an ATM-
defined interface layer is not absolutely necessary for modeling
Greene, et al. [Page 4]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
attachment of IP to an ATM network. The IPOA-MIB refers to use of
generic ifIndex object, whose value SHOULD reflect that of
specific ATM related interface as determined by an implementation.
is up to the implementers of this MIB to determine their own
interface layering (assuming compliance with the IF-MIB and the ATM
MIB).
The Internet Assigned Numbers Authority (IANA) ifType ipOverAtm(114)
was created for use by systems that require a virtual IP over
interface layer. The IF-MIB's ifStackTable SHOULD be used to show
relationship between virtual IP over ATM interfaces and the actual
physical interface layers. The current set of ifType values can
accessed via the IANA homepage at: "http://www.iana.org/iana/".
3.1. Basic Support MIB
Basic support that MUST be implemented by both Clients and
Servers consists of
o ATM Logical IP Subnet (LIS)
o ATM Logical IP Subnet Interface Mapping
o ATMARP Remote Server
o ATM VC
o ATM Config PVC
o
3.1.1. ATM Logical IP Subnet (LIS)
The ATM Logical IP Subnet (LIS) Table defines the subnets that
system is a member of for purposes of reaching destinations over
ATM transport. The LIS table is indexed by the subnet
(ipoaLisSubnetAddr) and not ifIndex. The
described in the next section provides the mapping between Logical
Subnets and the interface layer. It is possible that the same LIS
be reached via different ATM interfaces
The ipAddrTable and the ipoaClientTable provides the mapping from
local IP address to an ATM interface. One or more ipAddrTable
can point to the same ipoaLisEntry. An ipAddrEntry's
ANDed with its ipAdEntNetMask SHOULD equal an ipoaLisEntry'
ipoaLisSubnetAddr. Given that an interface can be multi-homed,
local IP address associated with an interface requires an entry in
ipAddrTable. Each ipAddrTable entry for a local IP address
with an ATM interface SHOULD map to an entry in the ipoaLisTable
Greene, et al. [Page 5]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
The bulk of the objects in an ipoaLisEntry exists to control
for a particular LIS. In a PVC only environment it is
dependent as to whether this table should be supported
The value of an ipoaLisMaxCalls object defines the maximum number
VCs that can be established simultaneously per LIS. The value of
ipoaLisDefaultPeakCellRate object defines the best effort default
cell rate in both the forward and backward directions
establishing VCCs (Virtual Channel Connections). Refer to RFC 1755,
ATM Signaling Support for IP over ATM (reference [11]), for
definition of the use of this object's value
The ipAddrTable's ipAdEntReasmMaxSize is the "The size of the
IP datagram which this entity can re-assemble from incoming
fragmented datagrams received on this interface" and is different
the ipoaLisTable's ipoaLisDefaultMtu with is the default MTU
within an LIS. Note that this is the default MTU, not the actual
(which is represented as ipoaVcNegotiatedMtu in the ipoaVcTable).
The ipoaLisRowStatus object enables entries in the ipoaLisTable to
created or deleted via SNMP. Creation of an ipoaLisTable
results in the addition of a corresponding ipAddrTable entry and
ipoaLisIfMappingTable entry. Creation of multiple ipAddrTable
and ipoaLisIfMappingTable entries for the same LIS is not addressed
this document. When ipoaLisRowStatus is changed from active(1)
notInService(2) or from active(1) to destroy(6), this has the side
effect of removing all entries from the ipNetToMediaTable that
associated with this LIS (in other words, it flushes the entity'
ATMARP cache). It also removes the ipoaVcTable entries that
associated with those ipNetToMediaTable entries. Destroying the
removes the corresponding entries in the ipoaArpSrvrTable
ipoaArpClientTable, ipoaLisIfMappingTable, and
ipoaArpRemoteSrvrTable
Entries in both the ipNetToMediaTable and the ipoaVcTable that
associated with an ipoaConfigPvcEntry are not affected by changes
ipoaLisRowStatus
Greene, et al. [Page 6]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
3.1.2. ATM Logical IP Subnet Interface Mapping
The ipoaLisIfMappingTable maps a LIS to all ATM interfaces from
it is configured to be supported. Each entry in
ipoaLisIfMappingTable SHOULD map to an ipAddrTable entry. It is
possible for a system, most commonly a switch, to have multiple
associated with the same ATM interface
3.1.3. ATMARP Remote Server
Entries in the ipoaArpRemoteSrvrTable exists to locally configure
remote ATMARP Servers that exist on a per LIS and interface basis
Classical IP and ARP over ATM [3] requires that at least one
Server be configured per LIS where SVC traffic is intended. PVC
doesn't require use of ATMARP. No ipoaArpRemoteSrvrTable
SHOULD be configured for a LIS where only PVCs will be used. An
in the ipoaArpRemoteSrvrTable is indexed by the subnet address of
LIS (ipoaLisSubnetAddr), the ATM address of the remote ATMARP
(ipoaArpRemoteSrvrAtmAddr) and an interface
(ipoaArpRemoteSrvrIfIndex) value
The object ipoaArpRemoteSrvrIpAddr in an ipoaArpRemoteSrvrEntry is
with the IP Address of the Remote ATMARP Server when a VC to
Remote ATMARP Server is established. A value of 0.0.0.0 SHOULD
used when the IP address of the Remote ATMARP Server is not known
Once ipoaArpRemoteSrvrIpAddr is set then the ipoaVcTable can
searched using ipoaArpRemoteSrvrIfIndex and ipoaArpRemoteSrvrIpAddr
find the VC in use to the Remote ATMARP Server
ipoaArpRemoteSrvrIfIndex is defined to have the textual convention
InterfaceIndexOrZero. Adding ipoaArpRemoteSrvrIfIndex to the
clause allows a system to have a VC to a ATMARP Remote Server on a
LIS and interface basis. An entry in this table SHOULD exist for
interface on a per LIS basis. Each interface would then have
separate VC to the Remote ATMARP Server for ATMARP purposes
An implementation that wants to use a single VC MAY use
ipoaArpRemoteSrvrIfIndex value of 0 when configuring
ipoaArpRemoteSrvrEntry for the associating LIS.
ipoaArpRemoteSrvrIfIndex is 0 then an implementation dependent
MAY be used for finding the VPI and VCI of the VC in use to the
ATMARP Server. For example, search the ipoaVcTable for a
between ipNetToMediaNetAddress and ipoaArpRemoteSrvrIpAddr from
ipoaArpRemoteSrvrEntry, ignoring ipNetToMediaIfIndex. Since a
VC is being used the first match SHOULD correspond to the correct VC
Greene, et al. [Page 7]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
If a PVC is intended to be used to communicate with a remote
Server then the ipoaConfigPvcTable MUST be used to create and
the PVC prior to activating a ipoaArpRemoteSrvrEntry
The object ipoaArpRemoteSrvrRowStatus allows for row creation
deletion of entries in the ipoaArpRemoteSrvrTable. The
ipoaArpRemoteSrvrAdminStatus and ipoaArpRemoteSrvrOperStatus exist
control and reflect the operational use of a Remote ATMARP
defined by an ipoaArpRemoteSrvrEntry. The
ipoaArpRemoteSrvrOperStatus SHOULD have a value of up(1) when an
has been established to the Remote ATMARP Server or if using a
when the InATMARP reply with the IP Address of the Remote
Server has been received. The value of down(2) SHOULD be used
indicate that a VC to the Remote ATMARP Server doesn't exist
3.1.4. ATM VC
An entry in the ipoaVcTable SHOULD have at least one
ipNetToMediaTable entry. Both tables use the ipNetToMediaTable'
indexes ipNetToMediaIfIndex and ipNetToMediaNetAddress.
ipoaVcTable has the additional indexes ipoaVcVpi and ipoaVcVci.
ipoaVcEntry exists for every VC per ATM interface per destination
address. Refer to the following diagram that illustrates
relationship between ipoaVcTable and the ipNetToMediaTable
ipoaVcTable
------------------------------ ----------------------------
| ipNetToMediaIfIndex | | ipNetToMediaIfIndex |
| ipNetToMediaNetAddress | | ipNetToMediaNetAddress |
| ipoaVcVpi | | |
| ipoaVcVci | | |
| ipoaVcType | | |
| ---> use IpoaAtmAddr TC | | ipNetToMediaPhysAddress |
| ipoaVcNegotiatedEncapsType | | |
| ipoaVcNegotiatedMtu | | |
| | | ipNetToMediaType |
------------------------------ ----------------------------
ipoaVcType indicates if the entry is for an SVC or a PVC.
ipoaVcEntry, corresponding to an PVC, is created automatically when
ipoaConfigPvcEntry is created and the IP Address at the end of the
is discovered. The associating ipNetToMediaTable entry would have
ipNetToMediaType set to static(4). ipNetToMediaTable entries
during ATMARP processing have a ipNetToMediaType of dynamic(3).
process to locally configuring an ipNetToMediaTable entry and
ipoaVcTable entry for an SVC without using ATMARP is not within
scope of this document
Greene, et al. [Page 8]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
The objects ipoaVcVpi and ipoaVcVci are defined to have a MAX-
of not-accessible since they are only used for purposes of indexing
entry in the ipoaVcTable
3.1.5. ATM Config PVC
An entry in the ipoaVcTable is created after the InATMARP reply
successfully received for an ipoaConfigPvcEntry during its activation
InATMARP should return the IP Address of the other end of the PVC
order to have the needed indexes to create an ipNetToMediaEntry and
ipoaVcEntry
The corresponding ARP Cache entry SHOULD be deleted whenever a
becomes unusable
A Network Management Station wanting to create a PVC at a
system for use as an IP transport would
o use the ATM-MIB, reference [4], to create the
o use the ipoaConfigPvcTable in the IPOA-MIB to
the PVC for use by
Refer to the following diagram that illustrates the
between the ipoaVcTable and the ipoaConfigPvcTable
ipoaVcTable
------------------------------ ----------------------------
| ipNetToMediaIfIndex | | ipNetToMediaIfIndex |
| ipNetToMediaNetAddress | | |
| ipoaVcVpi | | ipoaConfigPvcVpi |
| ipoaVcVci | | ipoaConfigPvcVci |
| ipoaVcType | | |
| | | ipoaConfigPvcDefaultMtu |
| ipoaVcNegotiatedEncapsType | | |
| ipoaVcNegotiatedMtu | | |
| | | ipoaConfigPvcRowStatus |
------------------------------ ----------------------------
When the ipoaVcEntry is created its ipoaVcType will be set to pvc(1),
its ipoaVcNegotiatedEncapsType set to llcSnap(1), and
ipoaVcNegotiatedMtu set to 9180 octets by default. Classical IP
ARP over ATM [3] allows use of other MTU values for PVCs but
the selection of a value other than 9180 to be out of scope
ipoaConfigPvcDefaultMtu can be used to configure the MTU to be
for the PVC. Both ends MUST have the same value configured.
associating ipNetToMediaTable entry would have its
set to static(4).
Greene, et al. [Page 9]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
Changing ipoaConfigPvcRowStatus from active(1) to notInService(2)
from active(1) to destroy(6) has the side-effect of removing
corresponding ipNetToMediaTable, ipoaVcTable, and
entries
3.1.6.
Both ATM clients and ATMARP Servers MUST support generation of
ipoaMtuExceeded notification
3.2. Client Supported MIB
The ATMARP Client Table is the only additional MIB table that a
MUST implement
Greene, et al. [Page 10]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
3.2.1. ATMARP Client
An entry in the ipoaArpClientTable SHOULD have a
ipAddrTable entry where both are indexed by the same
value. Refer to the following diagram that illustrates
relationship between ipoaArpClientTable and ipAddrTable entries
ipoaArpClientTable
----------------------------------- ------------------------
| ipAdEntAddr | | ipAdEntAddr |
| | | ipAdEntNetMask |
| | | ipAdEntIfIndex |
| ipoaArpClientAtmAddr | | |
| ipoaArpClientSrvrInUse | | |
| ipoaArpClientInArpInReqs | | |
| ipoaArpClientInArpOutReqs | | |
| ipoaArpClientInArpInReplies | | |
| ipoaArpClientInArpOutReplies | | |
| ipoaArpClientInArpInvalidInReqs | | |
| ipoaArpClientInArpInvalidOutReqs| | |
| ipoaArpClientArpInReqs | | |
| ipoaArpClientArpOutReqs | | |
| ipoaArpClientArpInReplies | | |
| ipoaArpClientArpOutReplies | | |
| ipoaArpClientArpInNaks | | |
| ipoaArpClientArpOutNaks | | |
| ipoaArpClientArpUnknownOps | | |
| ipoaArpClientArpNoSrvrResps | | |
| ipoaArpClientRowStatus | | |
| | | ipAdEntBcastAddr |
| | | ipAdEntReasmMaxSize |
----------------------------------- ------------------------
Both tables have the same index, ipAdEntAddr. The ipAddrTable'
ipAdEntNetMask when ANDed with its corresponding ipAdEntAddr yield
subnet of the LIS which can be used as an index into the
(ipoaLisSubnetAddr). The ipAddrTable's ipAdEntIfIndex points to
interface ifTable entry via an ifIndex value. The attachment
for IP into an ATM network is via an ATM interface's ifIndex.
ipoaArpClientEntry MUST point to an ATM interface via
corresponding ipAddrEntry
ipoaArpClientAtmAddr is the local ATM address associated with
corresponding ATM ifTable entry. ipoaArpClientSrvrInUse is the
address of the ATMARP Server being used for a particular client.
SVCs are not being used then the value of this object is a zero-
OCTET STRING
Greene, et al. [Page 11]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
It is sometimes possible for a system to have multiple IP
configured within the same IP subnet. The indexing of this
would seem to preclude that. However, it is possible to
additional entries in the ipAddrTable with the same ifIndex and
the same subnet address. The mechanism for adding these
entries to the ipAddrTable (which is read-only) is beyond the scope
this document
The counter object ipoaArpClientInArpInvalidInReqs is "The number
times that this client detected an invalid InATMARP request."
object SHOULD be incremented when processing fails for an
request (e.g., for incorrect InATMARP request structure fields).
object ipoaArpClientInArpInvalidOutReqs is defined as "The number
times that this client did not receive an InATMARP reply." This
different from ipoaArpClientArpNoSrvrResps which counts the number
times no response was received from an ATMARP request
InATMARP retransmission processing is not controlled by objects in
ipoaLisTable. In general, the ipoaLisTable objects relate to
Server processing. Configuration of InATMARP
processing is considered to be implementation dependent and
defined by the IPOA-MIB
Implementations SHOULD use local policy for defining both
timeout and retry count values. This policy would be expected
differ for sending an InATMARP Request over a PVC as opposed to
SVC. For transmission of an InATMARP Request over a SVC a timeout
60 seconds with a retry count of 3 is suggested.
transmission over a PVC should differ since its retry limit may
to be infinite in order to ensure that InATMARP Request
eventually occurs
3.3. Server Supported MIB
ATMARP Servers MUST support
o ATMARP Server
o
as defined in the following sections. This table exists only on
system where at least one ATMARP Server is present
3.3.1. ATMARP Server
This table defines the list of ATMARP Servers within a LIS.
entry of the table defines each ATMARP Server's ATM address, the
it is a member of, and various InATMARP and ATMARP statistics
Greene, et al. [Page 12]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
An entry in this table provides information about an ATMARP
within a LIS and is indexed by ipAdEntAddr (a local IP Address from
IP Address Table entry) and ipoaArpSrvrAddr (an ATM Address
with the ATMARP Server).
Entries MAY be created by a management application using
ipoaArpSrvrRowStatus object. Entries in this table MAY also
created by the system and not by a management application, for
via ILMI
Entries in this table MAY be deleted by setting
ipoaArpSrvrRowStatus object to destroy(6). This includes entries
were added by the system and not by a management application
On a host that supports multiple ATMARP Servers where the local
address being associated with each ATMARP Server is the same (
example a non-multihomed host), the ATM Address (ipoaArpSrvrAddr
uniquely identifies a particular ATMARP Server. On a host
multiple ATMARP Servers having a single ATM Interface with a
ATM Address, the ipAdEntAddr MUST be used to uniquely identify
entry in the ipoaArpSrvrTable
The indexing of the ipoaArpSrvrTable does not allow entries with
same or no local IP Address (ipAdEntAddr) and the same ATM
(ipoaArpSrvrAddr) to exist. The values of the index elements
combined to index a row must be unique
3.3.2.
An ATMARP Server MUST support the following notifications
o
o
o
Generation of ipoaLisCreate and ipoaLisDelete notifications
controlled by the ipoaLisTrapEnable object. These
indicate when an ipoaLisEntry is either created or deleted.
purpose of these notifications is to enable Network
Applications to dynamically discover the existence of ATMARP
LIS participation in order to eventually determine LIS composition
subsequent SNMP queries. It is permissible for an ATM client-
system to support the ipoaLisTrapEnable object and
ipoaLisCreate and ipoaLisDelete notifications
Greene, et al. [Page 13]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
4.
IPOA-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
transmission, Integer32, IpAddress, Counter32,
Gauge32
FROM SNMPv2-
TEXTUAL-CONVENTION,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-
FROM SNMPv2-
ipNetToMediaNetAddress, ipNetToMediaIfIndex
ipNetToMediaPhysAddress,
FROM IP-
-- The following textual conventions are defined locally
-- this MIB module. They have been prefixed with 'Ipoa'
-- distinguish them from their counterparts in the ATM-TC-MIB
-- This was done so that the IPOA-MIB could be advanced
-- a standards-based MIB without waiting for the ATM-TC-MIB
-- AtmConnKind,
-- FROM ATM-TC-
InterfaceIndex,
FROM IF-
;
ipoaMIB MODULE-
LAST-UPDATED "9802090000Z" -- February 9, 1998
ORGANIZATION "IETF Internetworking Over NBMA
Group (ion)"
CONTACT-
"Maria Greene (greene@xedia.com
Xedia Corp
Jim Luciani (jluciani@BayNetworks.com
Bay
Kenneth White (kennethw@vnet.ibm.com
IBM Corp
Ted Kuo (tkuo@eos.ncsu.edu
Bay Networks
"This module defines a portion of the
Greene, et al. [Page 14]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
information base (MIB) for managing Classical IP
ARP over ATM entities."
::= { transmission 46 }
-- Textual
IpoaEncapsType ::= TEXTUAL-
STATUS
"The encapsulation type used on a VC."
SYNTAX INTEGER {
llcSnap(1),
vcMuxed(2),
other(3)
}
IpoaVpiInteger ::= TEXTUAL-
STATUS
"An integer large enough to contain the value of a VPI."
SYNTAX Integer32 (0..255)
IpoaVciInteger ::= TEXTUAL-
STATUS
"An integer large enough to contain the value of a VCI."
SYNTAX Integer32 (0..65535)
IpoaAtmAddr ::= TEXTUAL-
DISPLAY-HINT "1x
STATUS
"The ATM address used by the network entity
The semantics are implied by the length
The address types are
- no address (0 octets
- E.164 (8 octets
- NSAP (20 octets
In addition, when subaddresses are used
may represent the concatenation of address
subaddress. The associated address types are
- E.164, E.164 (16 octets
- E.164, NSAP (28 octets
- NSAP, NSAP (40 octets
Greene, et al. [Page 15]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
Address lengths other than defined in this
imply address types defined elsewhere
Note: The E.164 address is encoded in BCD format."
SYNTAX OCTET STRING (SIZE(0..40))
IpoaAtmConnKind ::= TEXTUAL-
STATUS
"The use of call control. The use is as follows
pvc(1)
Virtual link of a PVC. Should not
used in a PVC/SVC (i.e., SPVC
crossconnect
svcIncoming(2)
Virtual link established after
received signaling request to
an SVC
svcOutgoing(3)
Virtual link established after
transmitted or forwarded
request to setup an SVC
spvcInitiator(4)
Virtual link at the PVC side of
SVC/PVC crossconnect, where
switch is the initiator of the
setup
spvcTarget(5)
Virtual link at the PVC side of
SVC/PVC crossconnect, where
switch is the target of the
setup
An spvcInitiator is always cross-connected
an svcOutgoing, and an spvcTarget is
cross-connected to an svcIncoming."
SYNTAX INTEGER {
pvc(1),
svcIncoming(2),
svcOutgoing(3),
spvcInitiator(4),
spvcTarget(5)
}
-- Top-level structure of the
ipoaObjects OBJECT IDENTIFIER ::= { ipoaMIB 1 }
ipoaNotifications OBJECT IDENTIFIER ::= { ipoaMIB 2 }
ipoaConformance OBJECT IDENTIFIER ::= { ipoaMIB 3 }
Greene, et al. [Page 16]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
-- MIB
ipoaLisTrapEnable OBJECT-
SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-
STATUS
"Indicates whether ipoaLisCreate and
traps should be generated by this system
By default, this object should have the
enabled(1) for systems where ATMARP Servers
present and disabled(2) on systems where
clients reside."
::= { ipoaObjects 1 }
-- The ATM Logical IP Subnet (LIS)
ipoaLisTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"There is one entry in this table for every Logical
Subnet (LIS) of which this system is a member
The bulk of the objects in an ipoaLisEntry
to control ATMARP for a particular LIS. In a PVC
environment it is implementation dependent as
whether this table should be supported."
::= { ipoaObjects 2 }
ipoaLisEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a single LIS of which this
is a member
Membership in a LIS is independent of the actual
interfaces being used. The ipoaLisTable
all LISs that a system is a member of. The
and the ipoaClientTable provides the mapping from
IP address to ATM interface. The
provides the mappings between Logical IP Subnets
interfaces
Greene, et al. [Page 17]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
The ipoaLisTable is indexed by ipoaLisSubnetAddr (
subnet address). An entry in the ipoaLisTable
exist for each ipAddrEntry that is associated with
ATM related interface used for Classical IP and
over ATM traffic
Its ipAdEntAddr and ipAdEntNetMask when ANDed
should equal the ipoaLisSubnetAddr of the
ipoaLisEntry."
INDEX { ipoaLisSubnetAddr }
::= { ipoaLisTable 1 }
IpoaLisEntry ::= SEQUENCE {
ipoaLisSubnetAddr IpAddress
ipoaLisDefaultMtu Integer32,
ipoaLisDefaultEncapsType IpoaEncapsType
ipoaLisInactivityTimer Integer32,
ipoaLisMinHoldingTime Integer32,
ipoaLisQDepth Integer32,
ipoaLisMaxCalls Integer32,
ipoaLisCacheEntryAge Integer32,
ipoaLisRetries Integer32,
ipoaLisTimeout Integer32,
ipoaLisDefaultPeakCellRate Integer32,
ipoaLisActiveVcs Gauge32,
ipoaLisRowStatus
}
ipoaLisSubnetAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP subnet address associated with this LIS."
::= { ipoaLisEntry 1 }
ipoaLisDefaultMtu OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The default MTU used within this LIS. Note that
actual MTU used for a VC between two members of
LIS may be negotiated during connection setup and
be different than this value. The
object indicates the actual MTU in use for
particular VC."
DEFVAL { 9180 }
Greene, et al. [Page 18]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
::= { ipoaLisEntry 2 }
ipoaLisDefaultEncapsType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The default encapsulation to use on VCs created
this LIS. Note that the actual encapsulation type
be negotiated during connection setup and may
different than this value.
ipoaVcNegotiatedEncapsType object indicates the
encapsulation in use for a particular VC."
DEFVAL { llcSnap }
::= { ipoaLisEntry 3 }
ipoaLisInactivityTimer OBJECT-
SYNTAX Integer32
UNITS "seconds
MAX-ACCESS read-
STATUS
"The time, in seconds, before a call established for
ipNetToMediaEntry on a client will timeout due to
traffic being passed on the VC. A value of 0
no time out."
"RFC 1755, Sec. 3.4 VC Teardown
DEFVAL { 1200 }
::= { ipoaLisEntry 4 }
ipoaLisMinHoldingTime OBJECT-
SYNTAX Integer32 (0..65535)
UNITS "seconds
MAX-ACCESS read-
STATUS
"The minimum amount of time, in seconds, that a
will remain open. If 0 then ipoaInactivityTimer
completely determine when a call is terminated."
"RFC 1755, Sec. 3.4 VC Teardown
DEFVAL { 60 }
::= { ipoaLisEntry 5 }
ipoaLisQDepth OBJECT-
SYNTAX Integer32 (1..65535)
UNITS "packets
Greene, et al. [Page 19]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
MAX-ACCESS read-
STATUS
"The maximum number of outstanding requests that
allowed while waiting for ATMARP replies
InATMARP replies for this LIS."
DEFVAL { 1 }
::= { ipoaLisEntry 6 }
ipoaLisMaxCalls OBJECT-
SYNTAX Integer32 (1..65535)
MAX-ACCESS read-
STATUS
"The maximum number of SVCs that can be
simultaneously for this LIS."
DEFVAL { 500 }
::= { ipoaLisEntry 7 }
ipoaLisCacheEntryAge OBJECT-
SYNTAX Integer32 (60..1200)
UNITS "seconds
MAX-ACCESS read-
STATUS
"The time, in seconds, before an ipNetToMediaEntry
age out of the table. Note that the default value
be different for a client and a server. An
Server should use a default of 1200 and a client
use 900."
DEFVAL { 900 }
::= { ipoaLisEntry 8 }
ipoaLisRetries OBJECT-
SYNTAX Integer32 (0..10)
MAX-ACCESS read-
STATUS
"The number of times the ATMARP request will be
when no response is received in the timeout
indicated by ipoaLisTimeout."
DEFVAL { 2 }
::= { ipoaLisEntry 9 }
ipoaLisTimeout OBJECT-
SYNTAX Integer32 (1..60)
UNITS "seconds
MAX-ACCESS read-
Greene, et al. [Page 20]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
STATUS
"The time to wait, in seconds, before
of an ARP request."
DEFVAL { 10 }
::= { ipoaLisEntry 10 }
ipoaLisDefaultPeakCellRate OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"This object is the signalling parameter
should be used when setting up all best
VCCs (Virtual Channel Connections).
This parameter applies to the forward
backward direction on a per best effort VCC basis
A value of zero implies that no configured
exists and that local policy should be used
determine the actual default to used
call setup. ATM Signaling Support for IP over
(RFC 1755) recommends 1/10th of the ATM interface'
speed."
::= { ipoaLisEntry 11 }
ipoaLisActiveVcs OBJECT-
SYNTAX Gauge32
MAX-ACCESS read-
STATUS
"Number of active SVCs for this LIS."
::= { ipoaLisEntry 12 }
ipoaLisRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object allows entries to be created and
in the ipoaLisTable
When the ipoaLisRowStatus deleted (by setting
object to destroy(6)), this has the side-effect
removing all entries from the ipNetToMediaTable
are associated with this LIS (in other words,
flushes the entity's ATMARP cache). It also
the ipoaVcTable entries that were associated with
ipNetToMediaTable entries. Destroying the row
Greene, et al. [Page 21]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
removes the corresponding entries in
ipoaArpSrvrTable, ipoaArpClientTable
ipoaLisIfMappingTable, and ipoaArpRemoteSrvrTable
Entries in both the ipNetToMediaTable and
ipoaVcTable that are associated with
ipoaConfigPvcEntry are not affected by changes
ipoaLisRowStatus."
"RFC 1903, 'Textual Conventions for Version 2 of
Simple Network Management Protocol (SNMPv2).'"
::= { ipoaLisEntry 13 }
-- The ATM Logical IP Subnet Interface Mapping
ipoaLisIfMappingTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"There is one entry in this table for every
of ipoaLisEntry and IP over ATM interface."
::= { ipoaObjects 3 }
ipoaLisIfMappingEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Defines an entry in the ipoaLisIfMappingTable."
INDEX { ipoaLisSubnetAddr, ipoaLisIfMappingIfIndex }
::= { ipoaLisIfMappingTable 1 }
IpoaLisIfMappingEntry ::= SEQUENCE {
ipoaLisIfMappingIfIndex InterfaceIndex
ipoaLisIfMappingRowStatus
}
ipoaLisIfMappingIfIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The ipAdEntIfIndex object from an
is used as an index to this table when
ipAdEntAddr is in the subnet implied
ipoaLisSubnetAddr."
Greene, et al. [Page 22]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
::= { ipoaLisIfMappingEntry 1 }
ipoaLisIfMappingRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object allows entries to be created and
in the ipoaLisIfMappingTable."
"RFC 1903, 'Textual Conventions for Version 2 of
Simple Network Management Protocol (SNMPv2).'"
::= { ipoaLisIfMappingEntry 2 }
-- The ATMARP Client
ipoaArpClientTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The ATMARP clients running on this system."
::= { ipoaObjects 4 }
ipoaArpClientEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a single ATMARP Client.
can be started and stopped by adding and
entries from this table. An entry in
ipoaArpClientTable has a corresponding entry in
ipAddrTable. Both are indexed by ipAdEntAddr
The ifIndex and subnet mask of a client entry are
ipAddrEntry's ipAdEntIfIndex and ipAdEntNetMask
respectively
Note that adding and removing entries from this
may have the same effect on the
ipAddrTable entry. Row creation of an entry in
table requires that either the corresponding
entry exists or that ipAdEntIfIndex and
be specified in the creation of an
at a minimum in order to create the
ipAddrEntry. Specification of ipAdEntBcastAddr
ipAdEntReasmMaxSize to complete an ipAddrEntry
implementation dependent
Greene, et al. [Page 23]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
Whether a corresponding ipAddrEntry is deleted
the deletion of an ipoaArpClientEntry is
implementation dependent."
INDEX { ipAdEntAddr }
::= { ipoaArpClientTable 1 }
IpoaArpClientEntry ::= SEQUENCE {
ipoaArpClientAtmAddr IpoaAtmAddr
ipoaArpClientSrvrInUse IpoaAtmAddr
ipoaArpClientInArpInReqs Counter32,
ipoaArpClientInArpOutReqs Counter32,
ipoaArpClientInArpInReplies Counter32,
ipoaArpClientInArpOutReplies Counter32,
ipoaArpClientInArpInvalidInReqs Counter32,
ipoaArpClientInArpInvalidOutReqs Counter32,
ipoaArpClientArpInReqs Counter32,
ipoaArpClientArpOutReqs Counter32,
ipoaArpClientArpInReplies Counter32,
ipoaArpClientArpOutReplies Counter32,
ipoaArpClientArpInNaks Counter32,
ipoaArpClientArpOutNaks Counter32,
ipoaArpClientArpUnknownOps Counter32,
ipoaArpClientArpNoSrvrResps Counter32,
ipoaArpClientRowStatus
}
ipoaArpClientAtmAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ATM address of the client."
::= { ipoaArpClientEntry 1 }
ipoaArpClientSrvrInUse OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The ATM address of the ATMARP Server
ipoaArpRemoteSrvrAtmAddr, in use by this client.
zero length octet string implies that
with a Remote ATMARP Server is not in effect."
DEFVAL { ''H }
::= { ipoaArpClientEntry 2 }
ipoaArpClientInArpInReqs OBJECT-
SYNTAX Counter32
Greene, et al. [Page 24]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
MAX-ACCESS read-
STATUS
"The number of InATMARP requests received by
client."
::= { ipoaArpClientEntry 3 }
ipoaArpClientInArpOutReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of InATMARP requests sent by this client."
::= { ipoaArpClientEntry 4 }
ipoaArpClientInArpInReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of InATMARP replies received by
client."
::= { ipoaArpClientEntry 5 }
ipoaArpClientInArpOutReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of InATMARP replies sent by this client."
::= { ipoaArpClientEntry 6 }
ipoaArpClientInArpInvalidInReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that this client detected
invalid InATMARP request."
::= { ipoaArpClientEntry 7 }
ipoaArpClientInArpInvalidOutReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that this client did
receive an InATMARP reply."
Greene, et al. [Page 25]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
::= { ipoaArpClientEntry 8 }
ipoaArpClientArpInReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of ATMARP requests received by
client."
::= { ipoaArpClientEntry 9 }
ipoaArpClientArpOutReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of ATMARP requests sent by this client."
::= { ipoaArpClientEntry 10 }
ipoaArpClientArpInReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of ATMARP replies received by
client."
::= { ipoaArpClientEntry 11 }
ipoaArpClientArpOutReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of ATMARP replies sent by this client."
::= { ipoaArpClientEntry 12 }
ipoaArpClientArpInNaks OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of negative ATMARP
received by this client."
::= { ipoaArpClientEntry 13 }
ipoaArpClientArpOutNaks OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
Greene, et al. [Page 26]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
STATUS
"Total number of negative ATMARP replies sent
this client
Classic IP and ARP over ATM does not require
ATMARP client to transmit an ATMARP_NAK
receipt of an ATMARP request from another
client. However, implementation experience
shown that this error condition is somewhat
to create inadvertently by configuring one
client with an ipoaArpRemoteSrvrTable
containing an ipoaArpRemoteSrvrAtmAddr value
is the ATM address of another ATMARP client-
system
If an ATMARP client supports the transmission
ATMARP_NAKs, then it should
ipoaArpClientArpOutNaks each time it
an ATMARP_NAK. Otherwise, support of
object is considered optional."
::= { ipoaArpClientEntry 14 }
ipoaArpClientArpUnknownOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that this client
an ATMARP message with an operation code for
it is not coded to support."
::= { ipoaArpClientEntry 15 }
ipoaArpClientArpNoSrvrResps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times this client failed to
a response from a ATMARP Server within
ipoaLisTimeout value for ipoaLisRetries times
This may imply that the client will re-elect
new primary ATMARP Server for this LIS from
ipoaArpRemoteSrvrTable."
::= { ipoaArpClientEntry 16 }
ipoaArpClientRowStatus OBJECT-
SYNTAX
Greene, et al. [Page 27]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
MAX-ACCESS read-
STATUS
"This object allows entries to be created
deleted from the ipoaArpClientTable."
"RFC 1903, 'Textual Conventions for Version 2 of
Simple Network Management Protocol (SNMPv2).'"
::= { ipoaArpClientEntry 17 }
-- The ATMARP Server
ipoaArpSrvrTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The ATMARP Servers running on this system."
::= { ipoaObjects 5 }
ipoaArpSrvrEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about an ATMARP Server within a LIS.
entry in this table has two indexes: first ipAdEntAddr
which is the IP address that this system uses as
member of the LIS, and then ipoaArpSrvrAddr, which
the ATM address of the ATMARP Server
Entries may be created by a management
using the ipoaArpSrvrRowStatus object. Entries in
table may also be created by the system and not by
management application, for example via ILMI
Entries in this table may be deleted by setting
ipoaArpSrvrRowStatus object to 'destroy(6)'.
includes entries that were added by the system and
by a management application."
INDEX { ipAdEntAddr, ipoaArpSrvrAddr }
::= { ipoaArpSrvrTable 1 }
IpoaArpSrvrEntry ::= SEQUENCE {
ipoaArpSrvrAddr IpoaAtmAddr
ipoaArpSrvrLis IpAddress
ipoaArpSrvrInArpInReqs Counter32,
ipoaArpSrvrInArpOutReqs Counter32,
Greene, et al. [Page 28]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
ipoaArpSrvrInArpInReplies Counter32,
ipoaArpSrvrInArpOutReplies Counter32,
ipoaArpSrvrInArpInvalidInReqs Counter32,
ipoaArpSrvrInArpInvalidOutReqs Counter32,
ipoaArpSrvrArpInReqs Counter32,
ipoaArpSrvrArpOutReplies Counter32,
ipoaArpSrvrArpOutNaks Counter32,
ipoaArpSrvrArpDupIpAddrs Counter32,
ipoaArpSrvrArpUnknownOps Counter32,
ipoaArpSrvrRowStatus
}
ipoaArpSrvrAddr OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The ATM address of the ATMARP Server."
::= { ipoaArpSrvrEntry 1 }
ipoaArpSrvrLis OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The subnet address that identifies the LIS
which this server is associated."
::= { ipoaArpSrvrEntry 2 }
ipoaArpSrvrInArpInReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of InATMARP requests received by
ATMARP Server."
::= { ipoaArpSrvrEntry 3 }
ipoaArpSrvrInArpOutReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of InATMARP requests sent by this
Server."
::= { ipoaArpSrvrEntry 4 }
ipoaArpSrvrInArpInReplies OBJECT-
Greene, et al. [Page 29]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of InATMARP replies received by
ATMARP Server."
::= { ipoaArpSrvrEntry 5 }
ipoaArpSrvrInArpOutReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of InATMARP replies sent by this
Server."
::= { ipoaArpSrvrEntry 6 }
ipoaArpSrvrInArpInvalidInReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of invalid InATMARP requests received
this ATMARP Server."
::= { ipoaArpSrvrEntry 7 }
ipoaArpSrvrInArpInvalidOutReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that this server did not
an InATMARP reply."
::= { ipoaArpSrvrEntry 8 }
ipoaArpSrvrArpInReqs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of ATMARP requests received by
ATMARP Server."
::= { ipoaArpSrvrEntry 9 }
ipoaArpSrvrArpOutReplies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Greene, et al. [Page 30]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
"Total number of ATMARP replies sent by this
Server."
::= { ipoaArpSrvrEntry 10 }
ipoaArpSrvrArpOutNaks OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"Total number of negative ATMARP replies sent by
ATMARP Server."
::= { ipoaArpSrvrEntry 11 }
ipoaArpSrvrArpDupIpAddrs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that a duplicate IP address
detected by this ATMARP Server."
::= { ipoaArpSrvrEntry 12 }
ipoaArpSrvrArpUnknownOps OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of times that this ATMARP Server
an ATMARP message with an operation code for which
is not coded to support."
::= { ipoaArpSrvrEntry 13 }
ipoaArpSrvrRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object allows entries to be created and
from the ipoaArpSrvrTable."
"RFC 1903, 'Textual Conventions for Version 2 of
Simple Network Management Protocol (SNMPv2).'"
::= { ipoaArpSrvrEntry 14 }
-- The Remote ATMARP Server
ipoaArpRemoteSrvrTable OBJECT-
Greene, et al. [Page 31]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table of non-local ATMARP Servers associated with
LIS. An entry in this table has three indexes:
the ipoaLisSubnetAddr of the LIS for which
corresponding ATMARP Server provides ATMARP services
then the ipoaArpRemoteSrvrAtmAddr, which is the
address of the remote ATMARP Server, and finally
ifIndex of the interface on which the VC to the
Remote Server will be opened. An ifIndex value of 0
should be used when a single VC is to be shared
ATMARP purposes by multiple interfaces."
::= { ipoaObjects 6 }
ipoaArpRemoteSrvrEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about one non-local ATMARP Server."
INDEX { ipoaLisSubnetAddr, ipoaArpRemoteSrvrAtmAddr
ipoaArpRemoteSrvrIfIndex }
::= { ipoaArpRemoteSrvrTable 1 }
IpoaArpRemoteSrvrEntry ::= SEQUENCE {
ipoaArpRemoteSrvrAtmAddr IpoaAtmAddr
ipoaArpRemoteSrvrRowStatus RowStatus
ipoaArpRemoteSrvrIfIndex InterfaceIndexOrZero
ipoaArpRemoteSrvrIpAddr IpAddress
ipoaArpRemoteSrvrAdminStatus INTEGER
ipoaArpRemoteSrvrOperStatus
}
ipoaArpRemoteSrvrAtmAddr OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The ATM address of the remote ATMARP Server."
::= { ipoaArpRemoteSrvrEntry 1 }
ipoaArpRemoteSrvrRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Greene, et al. [Page 32]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
"This object allows entries to be created and
from the ipoaArpRemoteSrvrTable
Deleting an ipoaArpRemoteSrvrEntry (by setting
object to destroy(6)) may affect
entries. The object ipoaArpClientSrvrInUse in
ipoaArpClientSrvrEntry may contain the ATM
of an ATMARP Remote Server whose entry in
ipoaArpRemoteSrvrTable is being removed. In
case, any corresponding
objects should be at a minimum invalidated
setting their values to that of a zero
OCTET STRING
The value of ipoaArpRemoteSrvrOperStatus should
consistent with that of ipoaArpRemoteSrvrRowStatus
For example, successfully setting the value
this object to notInService(2) after its being
the up(1) state should result
ipoaArpRemoteSrvrOperStatus being set to down(2)
if currently up(1)."
"RFC 1903, 'Textual Conventions for Version 2 of
Simple Network Management Protocol (SNMPv2).'"
::= { ipoaArpRemoteSrvrEntry 2 }
ipoaArpRemoteSrvrIfIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The ifIndex of the interface that the VC to
Remote ATMARP Server is associated with."
::= { ipoaArpRemoteSrvrEntry 3 }
ipoaArpRemoteSrvrIpAddr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The IP Address of the Remote ATMARP Server.
value of 0.0.0.0 implies that this address isn'
known."
DEFVAL { '00000000'H }
::= { ipoaArpRemoteSrvrEntry 4 }
ipoaArpRemoteSrvrAdminStatus OBJECT-
SYNTAX INTEGER {
Greene, et al. [Page 33]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
up(1), -- use this ATMARP
down(2) -- stop using this ATMARP
}
MAX-ACCESS read-
STATUS
"The desired state for use of the ATMARP
represented by an entry in this table
ipoaArpRemoteSrvrAdminStatus values
up(1) - Attempt to activate use of
ATMARP Server represented by
entry in the ipoaArpRemoteSrvrTable
down(2) - Deactivate use of this
Server
When a managed system creates an entry in
table ipoaArpRemoteSrvrAdminStatus
ipoaArpRemoteSrvrOperStatus are initialized
down(2) by default."
DEFVAL { down }
::= { ipoaArpRemoteSrvrEntry 5 }
ipoaArpRemoteSrvrOperStatus OBJECT-
SYNTAX INTEGER {
up(1), -- eligible for
down(2) -- not eligible for
}
MAX-ACCESS read-
STATUS
"The current operational state for use of a
ATMARP Server. An up(1) entry has a
established to the respective Remote
Server
up(1) - A VC exists to Remote ATMARP
whose IP Address is stored
ipoaArpRemoteSrvrIpAddr. This VC
be determined by searching
ipoaVcTable
ipoaArpRemoteSrvrIfIndex (if not 0,
otherwise ignore
index) and ipoaArpRemoteSrvrIpAddr
An ipoaArpClientEntry should
with its
object having the same value
ipoaArpRemoteSrvrAtmAddr
Greene, et al. [Page 34]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
down(2) - Entry exists without an active VC
the Remote ATMARP Server
Transition from up(1) to down(2)
status may affect ipoaArpClientTable entries
The object ipoaArpClientSrvrInUse in
ipoaArpClientSrvrEntry may contain the ATM
of an ATMARP Remote Server whose entry in
ipoaArpRemoteSrvrTable is being deactivated.
this case, any corresponding
objects should be at a minimum invalidated
setting their values to that of a zero
OCTET STRING
If ipoaArpRemoteSrvrAdminStatus is down(2)
ipoaArpRemoteSrvrOperStatus should be down(2).
If ipoaArpRemoteSrvrAdminStatus is changed
up(1) then ipoaArpRemoteSrvrOperStatus
change to up(1) if the Remote ATMARP
entry can be activated."
DEFVAL { down }
::= { ipoaArpRemoteSrvrEntry 6 }
-- The ATM VC
ipoaVcTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A system that supports IP over ATM is an IP system
therefore MUST support all of the appropriate tables
the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233),
the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012),
the UDP-MIB (RFC 2013). This includes
ipNetToMediaTable (the ARP cache) that is
within the IP-MIB (RFC 2011). The
keeps a set of VCs for each entry in the ARP
that was put there by an IP over ATM system
as either a host or server. The ipoaVcTable doesn'
augment the ipNetToMediaTable (ARP Cache) since
the correspondence between tables is not
one-to-one
An ipNetToMediaPhysAddress object should contain
content as defined by the IpoaAtmAddr
convention when used to hold an IPOA-MIB ATM Address."
::= { ipoaObjects 7 }
Greene, et al. [Page 35]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
ipoaVcEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A VC (permanent or switched) that this host or
has opened with another member of a LIS.
information can be determined about the VC from
ATM-MIB
Entries in this table cannot be created by
applications
In an SVC environment, an entry is automatically
by the system as the result of ATMARP processing
In a PVC environment, an entry is automatically
to this table when an entry is created in
ipoaConfigPvcTable and the IP Address at the
end of the PVC is discovered using InATMARP.
entry also is added to the ipNetToMediaTable."
INDEX { ipNetToMediaIfIndex
ipNetToMediaNetAddress
ipoaVcVpi
}
::= { ipoaVcTable 1 }
IpoaVcEntry ::= SEQUENCE {
ipoaVcVpi IpoaVpiInteger
ipoaVcVci IpoaVciInteger
ipoaVcType IpoaAtmConnKind
ipoaVcNegotiatedEncapsType IpoaEncapsType
ipoaVcNegotiatedMtu Integer32 }
ipoaVcVpi OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The VPI value for the Virtual Circuit."
::= { ipoaVcEntry 1 }
ipoaVcVci OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
Greene, et al. [Page 36]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
"The VCI value for the Virtual Circuit."
::= { ipoaVcEntry 2 }
ipoaVcType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The type of the Virtual Circuit."
::= { ipoaVcEntry 3 }
ipoaVcNegotiatedEncapsType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The encapsulation type used when communicating
this circuit."
::= { ipoaVcEntry 4 }
ipoaVcNegotiatedMtu OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"The MTU used when communicating over this circuit."
::= { ipoaVcEntry 5 }
-- The ATM Config PVC
ipoaConfigPvcTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table MUST be supported when PVCs are intended
be supported in order to enable the setup of PVCs
use by IP."
::= { ipoaObjects 8 }
ipoaConfigPvcEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Defines a single PVC that exists at this host
use by IP."
Greene, et al. [Page 37]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
INDEX { ipoaConfigPvcIfIndex
ipoaConfigPvcVpi
}
::= { ipoaConfigPvcTable 1 }
IpoaConfigPvcEntry ::= SEQUENCE {
ipoaConfigPvcIfIndex InterfaceIndex
ipoaConfigPvcVpi IpoaVpiInteger
ipoaConfigPvcVci IpoaVciInteger
ipoaConfigPvcDefaultMtu Integer32,
ipoaConfigPvcRowStatus RowStatus }
ipoaConfigPvcIfIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The ifIndex of the ATM Interface that this
is associated with."
::= { ipoaConfigPvcEntry 1 }
ipoaConfigPvcVpi OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The VPI value for the Virtual Circuit."
::= { ipoaConfigPvcEntry 2 }
ipoaConfigPvcVci OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The VCI value for the Virtual Circuit."
::= { ipoaConfigPvcEntry 3 }
ipoaConfigPvcDefaultMtu OBJECT-
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-
STATUS
"Classical IP and ARP over ATM allows use
other MTU values for PVCs but considers how
value other than 9180 could be selected to be
of scope. ipoaConfigPvcDefaultMtu can be used
configure the MTU to be used for the PVC
Greene, et al. [Page 38]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
Both ends MUST have the same value configured."
DEFVAL { 9180 }
::= { ipoaConfigPvcEntry 4 }
ipoaConfigPvcRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object allows rows to be created and deleted
the ipoaConfigPvcTable. Creation of an entry in
table should eventually result in the creation of
ipNetToMediaEntry and a corresponding
after InATMARP has determined the destination
of the remote system that the PVC is connected to
Setting this object to destroy(6) should remove
corresponding ipNetToMediaTable and
entries."
"RFC 1903, 'Textual Conventions for Version 2 of
Simple Network Management Protocol (SNMPv2).'"
::= { ipoaConfigPvcEntry 5 }
--
ipoaTrapPrefix OBJECT IDENTIFIER ::= { ipoaNotifications 0 }
ipoaMtuExceeded NOTIFICATION-
OBJECTS {
}
STATUS
"A frame was received that exceeds the
MTU size. The VPI and VCI of the VC for which
condition was detected can be determined from
index values for ipoaVcNegotiatedMtu. In addition
the ifIndex and IP Address can be determined
well (refer to the ipoaVcTable)."
::= { ipoaTrapPrefix 1 }
ipoaDuplicateIpAddress NOTIFICATION-
OBJECTS {
ipNetToMediaIfIndex
ipNetToMediaNetAddress
ipNetToMediaPhysAddress
Greene, et al. [Page 39]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
}
STATUS
"The ATMARP Server has detected more than one ATM
point attempting to associate the same IP address
different ATM addresses."
::= { ipoaTrapPrefix 2 }
ipoaLisCreate NOTIFICATION-
OBJECTS {
}
STATUS
"Generation of this trap occurs when an ipoaLisEntry
created while the ipoaLisTrapEnable.0 object has
value enabled(1)."
::= { ipoaTrapPrefix 3 }
ipoaLisDelete NOTIFICATION-
OBJECTS {
}
STATUS
"Generation of this trap occurs when an ipoaLisEntry
deleted while the ipoaLisTrapEnable.0 object has
value enabled(1)."
::= { ipoaTrapPrefix 4 }
-- Conformance
ipoaGroups OBJECT IDENTIFIER ::= { ipoaConformance 1 }
ipoaCompliances OBJECT IDENTIFIER ::= { ipoaConformance 2 }
-- compliance
ipoaCompliance MODULE-
STATUS
"The compliance statement for agents that support
IPOA-MIB."
MODULE -- this
MANDATORY-GROUPS { ipoaGeneralGroup
}
GROUP
Greene, et al. [Page 40]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
"This group is mandatory for all hosts where
over ATM client support is present."
GROUP
"This group is mandatory for all hosts where
Servers are present."
GROUP
"This group is mandatory for all hosts where
Servers are present."
GROUP
"This group is mandatory for all hosts
ATMARP client only support is present
ipoaLisTrapEnable is allowed to be set
enabled(1)."
GROUP
"This group is mandatory for all entities
support IP over ATM SVCs. Support of objects
this group by IP over ATM clients which
support IP over ATM PVCs is optional."
OBJECT
MIN-ACCESS read-
"The agent is not required to allow the
to change the default MTU from the value 9180.
The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to allow the user
specify the default encapsulation type for
LIS
The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
Greene, et al. [Page 41]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to allow the
to change the default number of times an
request will be retried when no response
received from the default of 2.
The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to allow the
Greene, et al. [Page 42]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
to change the default retransmission time
the default of 10 seconds
The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"Implementations that do not support IP
ATM SVC usage are not required to allow
user to specify a best effort default peak
rate since typically the ipoaLisTable won'
exist
The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
SYNTAX INTEGER {
active(1) -- subset of
}
MIN-ACCESS read-
"The agent is not required to support a
operation to this object, and only
of the six enumerated values for
RowStatus textual convention need
supported, specifically: active(1)."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
MIN-ACCESS read-
Greene, et al. [Page 43]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
"The agent is not required to support a
operation to this object in the absence
adequate security. In this case the value
this object should be up(1) when a
exists to the Remote ATMARP Server
otherwise down(2), and the agent should
allow a SET operation to this object."
OBJECT
MIN-ACCESS read-
"The agent is not required to support a
operation to this object in the absence
adequate security."
OBJECT
SYNTAX INTEGER {
active(1) -- subset of
}
MIN-ACCESS read-
"Write access is not required, and only
of the six enumerated values for
RowStatus textual convention need
supported, specifically: active(1)."
OBJECT
SYNTAX INTEGER {
active(1) -- subset of
}
MIN-ACCESS read-
"Write access is not required, and only
of the six enumerated values for
RowStatus textual convention need
supported, specifically: active(1)."
OBJECT
SYNTAX INTEGER {
active(1) -- subset of
}
MIN-ACCESS read-
"Write access is not required, and only
of the six enumerated values for
RowStatus textual convention need
supported, specifically: active(1)."
Greene, et al. [Page 44]
RFC 2320 IP and ARP over ATM (IPOA) MIB April 1998
OBJECT
SYNTAX INTEGER {
active(1) -- subset of
}
MIN-ACCESS read-
"Write access is not required, and only
of the six enumerated values for
RowStatus textual convention need
supported, specifically: active(1)."
OBJECT
SYNTAX INTEGER {
active(1) -- subset of
}
MIN-ACCESS read-
"Write access is not required, and only
of the six enumerated values for
RowStatus textual convention need
supported, specifically: active(1)."
OBJECT
MIN-ACCESS not-
"Classic IP and ARP over ATM does not
an ATMARP client to 