DOCS-IF-M-CMTS-MIB Table View

M-CMTS Core extensions for the DOCSIS RFI Downstream
docsIfDownstreamTable.

M-CMTS EQAM extensions for the DOCSIS RFI Downstream
docsIfDownstreamTable.

This table contains the QAM channel capabilities
for the M-CMTS Downstream Interface PHY parameters in the
EQAM device.

This table describes the rules that identify groups of
QAM channels with PHY parameters dependencies. 
A PHY parameter dependency group means that a set to 
a QAM channel parameter may affect the value of 
other QAM Channels in the group.
          
TSID is a broadcast term borrowed by the M-CMTS 
architecture to represent a unique identifier of QAM
channels in the M-CMTS architecture. 
          
TSID Group is the DEPI concept of a set of QAM channels
with a PHY parameter dependency. This module refers to 
TSID group as a PHY dependency Group.
          
This table uses the ENTITY-MIB physical component structure
to allows the managed system to describe the QAM channels'
PHY parameters dependencies. A management entity can use
the information from this table to generate the DEPI TSID
Groups.
          
Examples of PHY dependencies could be usage of adjacent
frequencies, or QAM channels of RF ports restricted, or 
same interleaver value, modulation and J.83 Annex value.
          
Additional details and rules to describe the PHY parameter
dependency is indicated in 
docsIfMCmtsEqamGroupDependencyType.
Vendors may extend via other MIB modules the usage of
docsIfMCmtsEqamGroupDependencyType.

A Table for setting multiple parameters of multiple
QAM channels.
Creating an entry in this table will set automatically
all QAM Channels in the containment tree of 
docsIfMCmtsEqamGlobCfgDownPhysicalIndex in 
entPhysicalContainsTable to the parameter values 
specified during the row creation.
          
docsIfMCmtsEqamGlobCfgDownPhysicalIndex MUST be a valid 
Physical index of entPhysicalTable.
          
The ways to configure QAM channels  parameters are:
1) Globally. 
   Using this table, docsIfMCmtsEqamGlobCfgDownTable
2) Directly. 
   Using docsIfMCmtsEqamDownstreamTable and 
   docsIfDownstreamChannelTable to change parameters 
   and lock status of individual QAM channels.
          
In general an entry in this table will set the parameters 
of QAM channels of the containment tree recursively the 
same way as doing directly as described in 2)above. It 
means, potentially there could be rejections based on 
locked parameters and/or PHY dependencies that prevent 
the sets.
          
The row creation in this table is not rejected or set in 
'inactive' or 'notInService' state due individual QAM 
channels in the group failures due the global set, instead,
an error status is reported per entry.
          
The processing of the entries in this table (e.g., at system
initialization) is sequential; therefore, it could be 
overlapping rules based on the containment tree level of
the entries.

This table configure attributes of block channels and
Controls channel Block Tests.
A channel block is an ENTITY-MIB containment of 
PhysicalClass 'module' that represent an RF connector.

The Control table for the configuration of M-CMTS
Downstream Interfaces. 
          
The M-CMTS Downstream Interface configuration information
is contained in this table.
          
Currently L2TPv3 is the defined tunnel mechanism for 
DEPI sessions. There may be other DEPI tunnel methods
defined in the future.
          
The configuration of entries with 
docsIfMCmtsDepiSessionConfigMethod equal to 'l2tpControl' 
follows the rule below:
          
Only one L2TPv3 Control Plane from a M-CMTS Core IP is 
established per EQAM IP host destination indicated in
docsIfMCmtsDepiSessionConfigRemoteAddr. There may be other
L2TPv3 Control Plane connections from different M-CMTSs
to the same EQAM IP host.

This table provides M-CMTS Downstream Interface with
DEPI session information related to the DEPI session
configuration process.

A table containing PHBIDs Resources used for DEPI
applications.
          
At the M-CMTS core these entries contain information
about the mapping of egress traffic to PHIDs and DEPI flow
IDs also known as DEPI payload encapsulation.
          
For the M-CMTS Core there are two type of entries:
o One set of entries is a preconfigured list of PHBIDs 
  used for M-CMTS requests to EQAM IP Host, e.g., the MIB 
  object docsIfMCmtsDepiSessionConfigRsrcAllocReq
  references those type of entry sets.
  In those entries the values of 
  docsIfMCmtsDepiRsrcAllocUdpPort, 
  docsIfMCmtsDepiRsrcAllocFlowId and 
  docsIfMCmtsDepiRsrcAllocPolicyScnTags
  are ignored by the M-CMTS.
          
o The second set of entries has the responses from the EQAM
  IP host to the M-CMTS when the DEPI session request is
  successful. The object 
  docsIfMCmtsDepiSessionConfigPhbIdResp in 
  docsIfMCmtsDepiSessionConfigTable references an entry of
  this type.
          
The EQAM MAY implement this table to configure the 
different queue prioritization of the DEPI flow IDs, PHBIDs
and UDP ports triplet used in the DEPI Resource allocation
response to the M-CMTS. If this table is not implemented by
the EQAM device the object 
docsIfMCmtsDepiSessionInfoRsrcAllocResp is
set to zero, and the DEPI session Resource Allocation 
response is vendor specific. Also the EQAM device MAY 
implement this table as read-only for the purpose of 
debugging the DEPI Resource Allocation Responses sent to
the M-CMTS core.

This table provides DEPI Session statistics for the
M-CMTS Downstream Interface.

This table provides accumulative measurements of the CIN
latency on the network.

The policy rules that apply to DOCSIS traffic (traffic
profiles) of a DEPI session.
Traffic Profiles are ways to discriminate specific
traffic flows for QOS treatment in the CIN and EQAM device.
          
The main function of this table is to map the DOCSIS SF 
egress traffic to the Converged Interconnect Network PHB
configuration; thus, from the M-CMTS to the EQAM IP host
Ingress port, the QOS levels are defined properly. 
          
In D-MPT mode this table is only applicable to PHB egress 
marking for the CIN.
          
In PSP mode this table is referenced PHBID CIN 
(referenced by docsIfMCmtsDepiSessionConfigCinPhbIdPolicy)
          
The CIN PHBs is operator specific. The CIN per-hub-Behavior
of this table accomplishes:
          
o DOCSIS MAPs, DOCSIS MAC messages and PacketCable VoIP 
  PHBID are configured in a reserved policy tag
  'ExpediteForwardCIN' traffic. This
  policy has a 'permanent' storage.
o Data traffic (per DOCSIS Service Flows) is assigned to 
  PBHIDs based on Admission policies rules, e.g., 
  Service Class Name, DOCSIS specific parameters, etc.
  This table only deals with policies based with SCN. 
  Other traffic descriptor rules are vendor dependent.

This table contains M-CMTS Extensions of the
DOCSIS Service Flow table to describe DEPI QOS associations
to Service Flows.
          
DEPI Connection Control Table indicates the policies to 
apply any time a new DOCSIS Service Flow is added to the
M-CMTS Downstream interface.