This module defines a portion of the management information base (MIB) for managing Classical IP and ARP over ATM entities. read-write current 1.3.6.1.2.1.10.46.1.1 Indicates whether ipoaLisCreate and ipoaLisDelete traps should be generated by this system. By default, this object should have the value enabled(1) for systems where ATMARP Servers are present and disabled(2) on systems where only clients reside. 1 2 read-write current 1.3.6.1.2.1.10.46.1.1 Indicates whether ipoaLisCreate and ipoaLisDelete traps should be generated by this system. By default, this object should have the value enabled(1) for systems where ATMARP Servers are present and disabled(2) on systems where only clients reside. 1 2 not-accessible current 1.3.6.1.2.1.10.46.1.2.1 Information about a single LIS of which this system is a member. Membership in a LIS is independent of the actual ATM interfaces being used. The ipoaLisTable defines all LISs that a system is a member of. The ipAddrTable and the ipoaClientTable provides the mapping from local IP address to ATM interface. The ipoaLisIfMappingTable provides the mappings between Logical IP Subnets and interfaces. The ipoaLisTable is indexed by ipoaLisSubnetAddr (IP subnet address). An entry in the ipoaLisTable should exist for each ipAddrEntry that is associated with an ATM related interface used for Classical IP and ARP over ATM traffic. Its ipAdEntAddr and ipAdEntNetMask when ANDed together should equal the ipoaLisSubnetAddr of the corresponding ipoaLisEntry. not-accessible current 1.3.6.1.2.1.10.46.1.3.1 Defines an entry in the ipoaLisIfMappingTable. not-accessible current 1.3.6.1.2.1.10.46.1.4.1 Information about a single ATMARP Client. Clients can be started and stopped by adding and removing entries from this table. An entry in the ipoaArpClientTable has a corresponding entry in the ipAddrTable. Both are indexed by ipAdEntAddr. The ifIndex and subnet mask of a client entry are the ipAddrEntry's ipAdEntIfIndex and ipAdEntNetMask, respectively. Note that adding and removing entries from this table may have the same effect on the corresponding ipAddrTable entry. Row creation of an entry in this table requires that either the corresponding ipAddrTable entry exists or that ipAdEntIfIndex and ipAdEntNetMask be specified in the creation of an ipoaArpClientEntry at a minimum in order to create the corresponding ipAddrEntry. Specification of ipAdEntBcastAddr and ipAdEntReasmMaxSize to complete an ipAddrEntry is implementation dependent. Whether a corresponding ipAddrEntry is deleted during the deletion of an ipoaArpClientEntry is considered implementation dependent. not-accessible current 1.3.6.1.2.1.10.46.1.5.1 Information about an ATMARP Server within a LIS. An entry in this table has two indexes: first ipAdEntAddr, which is the IP address that this system uses as a member of the LIS, and then ipoaArpSrvrAddr, which is the ATM address of the ATMARP Server. Entries may be created by a management application using the ipoaArpSrvrRowStatus object. Entries in this table may also be created by the system and not by a management application, for example via ILMI. Entries in this table may be deleted by setting the ipoaArpSrvrRowStatus object to 'destroy(6)'. This includes entries that were added by the system and not by a management application. not-accessible current 1.3.6.1.2.1.10.46.1.6.1 Information about one non-local ATMARP Server. not-accessible current 1.3.6.1.2.1.10.46.1.7.1 A VC (permanent or switched) that this host or server has opened with another member of a LIS. Additional information can be determined about the VC from the ATM-MIB. Entries in this table cannot be created by management applications. In an SVC environment, an entry is automatically added by the system as the result of ATMARP processing. In a PVC environment, an entry is automatically added to this table when an entry is created in the ipoaConfigPvcTable and the IP Address at the remote end of the PVC is discovered using InATMARP. An entry also is added to the ipNetToMediaTable. not-accessible current 1.3.6.1.2.1.10.46.1.8.1 Defines a single PVC that exists at this host for use by IP. read-only current 1.3.6.1.2.1.10.46.1.2.1.1 The IP subnet address associated with this LIS. read-write current 1.3.6.1.2.1.10.46.1.2.1.2 The default MTU used within this LIS. Note that the actual MTU used for a VC between two members of the LIS may be negotiated during connection setup and may be different than this value. The ipoaVcNegotiatedMtu object indicates the actual MTU in use for a particular VC. read-write current 1.3.6.1.2.1.10.46.1.2.1.3 The default encapsulation to use on VCs created for this LIS. Note that the actual encapsulation type may be negotiated during connection setup and may be different than this value. The ipoaVcNegotiatedEncapsType object indicates the actual encapsulation in use for a particular VC. 1 2 3 read-write current 1.3.6.1.2.1.10.46.1.2.1.4 "seconds" The time, in seconds, before a call established for an ipNetToMediaEntry on a client will timeout due to no traffic being passed on the VC. A value of 0 implies no time out. read-write current 1.3.6.1.2.1.10.46.1.2.1.5 "seconds" The minimum amount of time, in seconds, that a call will remain open. If 0 then ipoaInactivityTimer will completely determine when a call is terminated. read-write current 1.3.6.1.2.1.10.46.1.2.1.6 "packets" The maximum number of outstanding requests that are allowed while waiting for ATMARP replies and InATMARP replies for this LIS. read-write current 1.3.6.1.2.1.10.46.1.2.1.7 The maximum number of SVCs that can be established simultaneously for this LIS. read-write current 1.3.6.1.2.1.10.46.1.2.1.8 "seconds" The time, in seconds, before an ipNetToMediaEntry will age out of the table. Note that the default value will be different for a client and a server. An ATMARP Server should use a default of 1200 and a client should use 900. read-write current 1.3.6.1.2.1.10.46.1.2.1.9 The number of times the ATMARP request will be retried when no response is received in the timeout interval indicated by ipoaLisTimeout. read-write current 1.3.6.1.2.1.10.46.1.2.1.10 "seconds" The time to wait, in seconds, before retransmission of an ARP request. read-write current 1.3.6.1.2.1.10.46.1.2.1.11 This object is the signalling parameter that should be used when setting up all best effort VCCs (Virtual Channel Connections). This parameter applies to the forward and backward direction on a per best effort VCC basis. A value of zero implies that no configured default exists and that local policy should be used to determine the actual default to used during call setup. ATM Signaling Support for IP over ATM (RFC 1755) recommends 1/10th of the ATM interface's speed. read-only current 1.3.6.1.2.1.10.46.1.2.1.12 Number of active SVCs for this LIS. read-write current 1.3.6.1.2.1.10.46.1.2.1.13 This object allows entries to be created and deleted in the ipoaLisTable. When the ipoaLisRowStatus deleted (by setting this object to destroy(6)), this has the side-effect of removing all entries from the ipNetToMediaTable that are associated with this LIS (in other words, it flushes the entity's ATMARP cache). It also removes the ipoaVcTable entries that were associated with those ipNetToMediaTable entries. Destroying the row also removes the corresponding entries in the ipoaArpSrvrTable, ipoaArpClientTable, ipoaLisIfMappingTable, and ipoaArpRemoteSrvrTable. Entries in both the ipNetToMediaTable and the ipoaVcTable that are associated with a ipoaConfigPvcEntry are not affected by changes to ipoaLisRowStatus. 1 2 -- the following value is a state: -- this value may be read, but not written 3 -- the following three values are -- actions: these values may be written, -- but are never read 4 5 6 read-write current 1.3.6.1.2.1.10.46.1.3.1.2 This object allows entries to be created and deleted in the ipoaLisIfMappingTable. 1 2 -- the following value is a state: -- this value may be read, but not written 3 -- the following three values are -- actions: these values may be written, -- but are never read 4 5 6 read-write current 1.3.6.1.2.1.10.46.1.4.1.1 The ATM address of the client. "1x" read-only current 1.3.6.1.2.1.10.46.1.4.1.2 The ATM address of the ATMARP Server, ipoaArpRemoteSrvrAtmAddr, in use by this client. A zero length octet string implies that communication with a Remote ATMARP Server is not in effect. "1x" read-only current 1.3.6.1.2.1.10.46.1.4.1.3 The number of InATMARP requests received by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.4 The number of InATMARP requests sent by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.5 The number of InATMARP replies received by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.6 Total number of InATMARP replies sent by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.7 The number of times that this client detected an invalid InATMARP request. read-only current 1.3.6.1.2.1.10.46.1.4.1.8 The number of times that this client did not receive an InATMARP reply. read-only current 1.3.6.1.2.1.10.46.1.4.1.9 Total number of ATMARP requests received by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.10 Total number of ATMARP requests sent by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.11 Total number of ATMARP replies received by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.12 Total number of ATMARP replies sent by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.13 Total number of negative ATMARP replies received by this client. read-only current 1.3.6.1.2.1.10.46.1.4.1.14 Total number of negative ATMARP replies sent by this client. Classic IP and ARP over ATM does not require an ATMARP client to transmit an ATMARP_NAK upon receipt of an ATMARP request from another ATMARP client. However, implementation experience has shown that this error condition is somewhat easy to create inadvertently by configuring one ATMARP client with an ipoaArpRemoteSrvrTable entry containing an ipoaArpRemoteSrvrAtmAddr value which is the ATM address of another ATMARP client-only system. If an ATMARP client supports the transmission of ATMARP_NAKs, then it should increment ipoaArpClientArpOutNaks each time it transmits an ATMARP_NAK. Otherwise, support of this object is considered optional. read-only current 1.3.6.1.2.1.10.46.1.4.1.15 The number of times that this client received an ATMARP message with an operation code for which it is not coded to support. read-only current 1.3.6.1.2.1.10.46.1.4.1.16 The number of times this client failed to receive a response from a ATMARP Server within the ipoaLisTimeout value for ipoaLisRetries times. This may imply that the client will re-elect a new primary ATMARP Server for this LIS from the ipoaArpRemoteSrvrTable. read-write current 1.3.6.1.2.1.10.46.1.4.1.17 This object allows entries to be created and deleted from the ipoaArpClientTable. 1 2 -- the following value is a state: -- this value may be read, but not written 3 -- the following three values are -- actions: these values may be written, -- but are never read 4 5 6 read-write current 1.3.6.1.2.1.10.46.1.5.1.2 The subnet address that identifies the LIS with which this server is associated. read-only current 1.3.6.1.2.1.10.46.1.5.1.3 The number of InATMARP requests received by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.4 The number of InATMARP requests sent by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.5 The number of InATMARP replies received by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.6 The number of InATMARP replies sent by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.7 The number of invalid InATMARP requests received by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.8 The number of times that this server did not receive an InATMARP reply. read-only current 1.3.6.1.2.1.10.46.1.5.1.9 Total number of ATMARP requests received by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.10 Total number of ATMARP replies sent by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.11 Total number of negative ATMARP replies sent by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.12 The number of times that a duplicate IP address was detected by this ATMARP Server. read-only current 1.3.6.1.2.1.10.46.1.5.1.13 The number of times that this ATMARP Server received an ATMARP message with an operation code for which it is not coded to support. read-write current 1.3.6.1.2.1.10.46.1.5.1.14 This object allows entries to be created and deleted from the ipoaArpSrvrTable. 1 2 -- the following value is a state: -- this value may be read, but not written 3 -- the following three values are -- actions: these values may be written, -- but are never read 4 5 6 read-write current 1.3.6.1.2.1.10.46.1.6.1.2 This object allows entries to be created and deleted from the ipoaArpRemoteSrvrTable. Deleting an ipoaArpRemoteSrvrEntry (by setting this object to destroy(6)) may affect ipoaArpClientTable entries. The object ipoaArpClientSrvrInUse in an ipoaArpClientSrvrEntry may contain the ATM address of an ATMARP Remote Server whose entry in the ipoaArpRemoteSrvrTable is being removed. In this case, any corresponding ipoaArpClientSrvrInUse objects should be at a minimum invalidated by setting their values to that of a zero length OCTET STRING. The value of ipoaArpRemoteSrvrOperStatus should be consistent with that of ipoaArpRemoteSrvrRowStatus. For example, successfully setting the value of this object to notInService(2) after its being in the up(1) state should result in ipoaArpRemoteSrvrOperStatus being set to down(2) if currently up(1). 1 2 -- the following value is a state: -- this value may be read, but not written 3 -- the following three values are -- actions: these values may be written, -- but are never read 4 5 6 read-only current 1.3.6.1.2.1.10.46.1.6.1.4 The IP Address of the Remote ATMARP Server. A value of 0.0.0.0 implies that this address isn't known. read-write current 1.3.6.1.2.1.10.46.1.6.1.5 The desired state for use of the ATMARP Server represented by an entry in this table. ipoaArpRemoteSrvrAdminStatus values: up(1) - Attempt to activate use of the ATMARP Server represented by this entry in the ipoaArpRemoteSrvrTable. down(2) - Deactivate use of this ATMARP Server. When a managed system creates an entry in this table ipoaArpRemoteSrvrAdminStatus and ipoaArpRemoteSrvrOperStatus are initialized as down(2) by default. 1 -- use this ATMARP Server 2 -- stop using this ATMARP Server read-only current 1.3.6.1.2.1.10.46.1.6.1.6 The current operational state for use of a Remote ATMARP Server. An up(1) entry has a VC established to the respective Remote ATMARP Server: up(1) - A VC exists to Remote ATMARP Server whose IP Address is stored in ipoaArpRemoteSrvrIpAddr. This VC can be determined by searching the ipoaVcTable using ipoaArpRemoteSrvrIfIndex (if not 0, otherwise ignore ipNetToMediaIfIndex index) and ipoaArpRemoteSrvrIpAddr. An ipoaArpClientEntry should exist with its ipoaArpClientSrvrInUse object having the same value as ipoaArpRemoteSrvrAtmAddr. down(2) - Entry exists without an active VC to the Remote ATMARP Server. Transition from up(1) to down(2) status may affect ipoaArpClientTable entries. The object ipoaArpClientSrvrInUse in an ipoaArpClientSrvrEntry may contain the ATM address of an ATMARP Remote Server whose entry in the ipoaArpRemoteSrvrTable is being deactivated. In this case, any corresponding ipoaArpClientSrvrInUse objects should be at a minimum invalidated by setting their values to that of a zero length OCTET STRING. If ipoaArpRemoteSrvrAdminStatus is down(2) then ipoaArpRemoteSrvrOperStatus should be down(2). If ipoaArpRemoteSrvrAdminStatus is changed to up(1) then ipoaArpRemoteSrvrOperStatus should change to up(1) if the Remote ATMARP Server entry can be activated. 1 -- eligible for use 2 -- not eligible for use read-only current 1.3.6.1.2.1.10.46.1.7.1.3 The type of the Virtual Circuit. 1 2 3 4 5 read-only current 1.3.6.1.2.1.10.46.1.7.1.4 The encapsulation type used when communicating over this circuit. 1 2 3 read-only current 1.3.6.1.2.1.10.46.1.7.1.5 The MTU used when communicating over this circuit. read-write current 1.3.6.1.2.1.10.46.1.8.1.4 Classical IP and ARP over ATM allows use of other MTU values for PVCs but considers how a value other than 9180 could be selected to be out of scope. ipoaConfigPvcDefaultMtu can be used to configure the MTU to be used for the PVC. Both ends MUST have the same value configured. read-write current 1.3.6.1.2.1.10.46.1.8.1.5 This object allows rows to be created and deleted in the ipoaConfigPvcTable. Creation of an entry in this table should eventually result in the creation of an ipNetToMediaEntry and a corresponding ipoaVcEntry after InATMARP has determined the destination address of the remote system that the PVC is connected to. Setting this object to destroy(6) should remove the corresponding ipNetToMediaTable and ipoaVcTable entries. 1 2 -- the following value is a state: -- this value may be read, but not written 3 -- the following three values are -- actions: these values may be written, -- but are never read 4 5 6 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 IpoaAtmAddr may represent the concatenation of address and subaddress. The associated address types are: - E.164, E.164 (16 octets) - E.164, NSAP (28 octets) - NSAP, NSAP (40 octets) Address lengths other than defined in this definition imply address types defined elsewhere. Note: The E.164 address is encoded in BCD format. "1x" The encapsulation type used on a VC. 1 2 3 The use of call control. The use is as follows: pvc(1) Virtual link of a PVC. Should not be used in a PVC/SVC (i.e., SPVC) crossconnect. svcIncoming(2) Virtual link established after a received signaling request to setup an SVC. svcOutgoing(3) Virtual link established after a transmitted or forwarded signaling request to setup an SVC. spvcInitiator(4) Virtual link at the PVC side of an SVC/PVC crossconnect, where the switch is the initiator of the SPVC setup. spvcTarget(5) Virtual link at the PVC side of an SVC/PVC crossconnect, where the switch is the target of the SPVC setup. An spvcInitiator is always cross-connected to an svcOutgoing, and an spvcTarget is always cross-connected to an svcIncoming. 1 2 3 4 5 An integer large enough to contain the value of a VCI. An integer large enough to contain the value of a VPI.