ipoaVcTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpoaVcEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A system that supports IP over ATM is an IP system and
therefore MUST support all of the appropriate tables in
the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233),
the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012), and
the UDP-MIB (RFC 2013). This includes the
ipNetToMediaTable (the ARP cache) that is defined
within the IP-MIB (RFC 2011). The ipoaVcTable
keeps a set of VCs for each entry in the ARP cache
that was put there by an IP over ATM system acting
as either a host or server. The ipoaVcTable doesn
augment the ipNetToMediaTable (ARP Cache) since the
the correspondence between tables is not necessarily
one-to-one.
An ipNetToMediaPhysAddress object should contain the
content as defined by the IpoaAtmAddr textual
convention when used to hold an IPOA-MIB ATM Address."
View at oid-info.com
A system that supports IP over ATM is an IP system and
therefore MUST support all of the appropriate tables in
the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233),
the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012), and
the UDP-MIB (RFC 2013). This includes the
ipNetToMediaTable (the ARP cache) that is defined
within the IP-MIB (RFC 2011). The ipoaVcTable
keeps a set of VCs for each entry in the ARP cache
that was put there by an IP over ATM system acting
as either a host or server. The ipoaVcTable doesn't
augment the ipNetToMediaTable (ARP Cache) since the
the correspondence between tables is not necessarily
one-to-one.
An ipNetToMediaPhysAddress object should contain the
content as defined by the IpoaAtmAddr textual
convention when used to hold an IPOA-MIB ATM Address.
Parsed from file IPOA-MIB.mib
Module: IPOA-MIB
Automatically extracted from RFC2320
ipoaVcTable OBJECT-TYPE SYNTAX SEQUENCE OF IpoaVcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A system that supports IP over ATM is an IP system and therefore MUST support all of the appropriate tables in the SNMPv2-MIB (RFC 1907), the IF-MIB (RFC 2233), the IP-MIB (RFC 2011), the TCP-MIB (RFC 2012), and the UDP-MIB (RFC 2013). This includes the ipNetToMediaTable (the ARP cache) that is defined within the IP-MIB (RFC 2011). The ipoaVcTable keeps a set of VCs for each entry in the ARP cache that was put there by an IP over ATM system acting as either a host or server. The ipoaVcTable doesn't augment the ipNetToMediaTable (ARP Cache) since the the correspondence between tables is not necessarily one-to-one. An ipNetToMediaPhysAddress object should contain the content as defined by the IpoaAtmAddr textual convention when used to hold an IPOA-MIB ATM Address." ::= { ipoaObjects 7 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.46.1.7.1 | ipoaVcEntry | 5 | 5 | A VC (permanent or switched) that this host or server has opened with another member of a LIS. Additional information can be det… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.10.46.1.1 | ipoaLisTrapEnable | 1 | 1 | Indicates whether ipoaLisCreate and ipoaLisDelete traps should be generated by this system. By default, this object should have t… |
| 1.3.6.1.2.1.10.46.1.2 | ipoaLisTable | 1 | 14 | There is one entry in this table for every Logical IP Subnet (LIS) of which this system is a member. The bulk of the objects in a… |
| 1.3.6.1.2.1.10.46.1.3 | ipoaLisIfMappingTable | 1 | 3 | There is one entry in this table for every combination of ipoaLisEntry and IP over ATM interface. |
| 1.3.6.1.2.1.10.46.1.4 | ipoaArpClientTable | 1 | 18 | The ATMARP clients running on this system. |
| 1.3.6.1.2.1.10.46.1.5 | ipoaArpSrvrTable | 1 | 15 | The ATMARP Servers running on this system. |
| 1.3.6.1.2.1.10.46.1.6 | ipoaArpRemoteSrvrTable | 1 | 7 | A table of non-local ATMARP Servers associated with a LIS. An entry in this table has three indexes: first the ipoaLisSubnetAddr… |
| 1.3.6.1.2.1.10.46.1.8 | ipoaConfigPvcTable | 1 | 6 | This table MUST be supported when PVCs are intended to be supported in order to enable the setup of PVCs for use by IP. |