|
|
Description:
|
mpoaMpcMibAdvancedPlusOctetsCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The AdvancedPlusOctets implementation requirements for SNMP
entities
which support MPOA Clients. This includes supporting
the 64 bit octet counters."
MODULE -- this module
MANDATORY-GROUPS {
mpoaDeviceTypeGroup,
mpoaDeviceTypeMpsMacGroup,
mpcConfigGroup,
mpcActualGroup,
mpcDataAtmAddressGroup,
mpcStatisticsGroup,
mpcProtocolGroup,
mpcMpsGroup,
mpcIngressCacheTotalPacketGroup,
mpcIngressCacheTotalOctetGroup,
mpcIngressCacheGroup,
mpcEgressCacheTotalPacketGroup,
mpcEgressCacheTotalOctetGroup,
mpcEgressCacheGroup,
mpcMpsMultipleMacAddressGroup
}
OBJECT mpcRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mpcDataAtmAddressRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mpcProtocolRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
--
-- MPC Mapping Group Compliance
--
GROUP mpcMappingGroup
DESCRIPTION
"This group is mandatory only when there is NOT a one-to-one
relationship between the MPOA Client and the LANE Client.
Optionally, a one-to-one relationship between an MPOA Client
and a LANE Client can be enforced. To enforce this
one-to-one relationship the lecIndex for the LANE Client
and the mpcIndex for the MPOA Client must have the same
value.
If this one-to-one mapping is enforced, then the
implementation
of the mpcMappingTable is unnecessary. (Since the lecIndex
and
the mpcIndex contain the same value, there is no need to
provide
a mapping of mpcIndex value to lecIndex value.)
The relationship between MPC and LEC is maintained by
ensuring that the mpcIndex is the same as the lecIndex
that is associated with it."
OBJECT mpcMappingRowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT mpcMappingIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
|
|
|
|
