The compliance statement for SNMP entities
which support MPOA Clients and Servers.
For a host to conform to this MIB, it must also implement
- RFC 1213 - MIB II.
- The AToM MIB (RFC 1695 - Definitions of Managed Objects
for ATM Management), according to the conformance
statements defined in that RFC.
- LAN Emulation Client MIB - af-lane-0038.000.mib
according to the conformance statements defined in
that specification.
Optionally, a host can choose to enforce a one-to-one
relationship between MPOA Client and LANE Client
- If this one-to-one mapping is enforced, then it is
not necessary to implement the mpcMappingTable.
The relationship between MPC and LEC is maintained by
ensuring that the mpcIndex is the same as the lecIndex
that is associated with it.
Optionally, a host can choose to enforce a one-to-one
relationship between MPOA Server and LANE Client
- If this one-to-one mapping is enforced, then it is
not necessary to implement the mpsMappingTable.
The relationship between MPS and LEC is maintained by
ensuring that the mpsIndex is the same as the lecIndex
that is associated with it.
Parsed from file MPOA100.MIB.txt
Company: None
Module: MPOA-MIB
mpoaMpcMibBasicCompliance OBJECT IDENTIFIER ::= { mpoaMIBCompliances 1 }
Vendor: ATM Forum
Module: MPOA-MIB
[Automatically extracted from oidview.com]
mpoaMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which support MPOA Clients and Servers. For a host to conform to this MIB, it must also implement - RFC 1213 - MIB II. - The AToM MIB (RFC 1695 - Definitions of Managed Objects for ATM Management), according to the conformance statements defined in that RFC. - LAN Emulation Client MIB - af-lane-0038.000.mib according to the conformance statements defined in that specification. Optionally, a host can choose to enforce a one-to-one relationship between MPOA Client and LANE Client - If this one-to-one mapping is enforced, then it is not necessary to implement the mpcMappingTable. The relationship between MPC and LEC is maintained by ensuring that the mpcIndex is the same as the lecIndex that is associated with it. Optionally, a host can choose to enforce a one-to-one relationship between MPOA Server and LANE Client - If this one-to-one mapping is enforced, then it is not necessary to implement the mpsMappingTable. The relationship between MPS and LEC is maintained by ensuring that the mpsIndex is the same as the lecIndex that is associated with it." MODULE MANDATORY-GROUPS { mpcConfigGroup, mpcStatusGroup, mpcStatisticsGroup, mpcProtocolGroup, mpcMappingGroup, mpcIngressCacheGroup, mpcEgressCacheGroup, mpcMPSGroup, mpsConfigGroup, mpsStatusGroup, mpsStatisticsGroup, mpsProtocolGroup, mpsMappingGroup, mpsAddressResGroup, mpsImpositionsGroup, mpoaConnGroup} OBJECT mpcMappingRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required. See note in mpoaMIBCompliance description to determine under which condition this is read-only" OBJECT mpcMappingIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. See note in mpoaMIBCompliance description to determine under which condition this is read-only" OBJECT mpsMappingRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required. See note in mpoaMIBCompliance description to determine under which condition this is read-only" OBJECT mpsMappingIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. See note in mpoaMIBCompliance description to determine under which condition this is read-only" ::= { mpoaMIBCompliances 1 }
mpoaMpcMibBasicCompliance OBJECT IDENTIFIER ::= { mpoaMIBCompliances 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.353.5.8.1.2.2.2 | mpoaMpcMibAdvancedCompliance | 0 | 0 | None |
| 1.3.6.1.4.1.353.5.8.1.2.2.3 | mpoaMpcMibAdvancedPlusOctetsCompliance | 0 | 0 | None |
| 1.3.6.1.4.1.353.5.8.1.2.2.4 | mpoaMpsMibBasicCompliance | 0 | 0 | None |
| 1.3.6.1.4.1.353.5.8.1.2.2.5 | mpoaMpsMibAdvancedCompliance | 0 | 0 | None |