Represents one or more MoCA channel RF center frequencies using a hexadecimal encoded 64-bit mask.
Bit 63 (the leftmost bit of the leftmost character) is the most significant bit (highest frequency), and bit 0 (the rightmost bit of the rightmost character) is the least significant bit (lowest frequency). Not all bits are valid MoCA channels.
Each bit represents 25 MHz of spectrum, but the mapping from bits to frequencies varies with the MoCA version:
* MoCA 1.0 and MoCA 1.1: bits 63 through 32 are not used, bit 31 represents 1575 MHz and bit 0 represents 800 MHz
* MoCA 2.0 and MoCA 2.5: bit 63 represents 1975 MHz and bit 0 represents 400 MHz
For example, a MoCA 1.0 or MoCA 1.1 interface would use 0x000000001FFFC000 to represent 1150 MHz through 1500 MHz.
Note that the MoCA version is indicated by the {{param|HighestVersion}} parameter.
Represents a MoCA Node ID.
* MoCA 1.0 network can have a maximum of 8 MoCA Nodes, so Node ID is 0 to 7.
* MoCA 1.1, MoCA 2.0, or MoCA 2.5 network can have a maximum of 16 MoCA Nodes, so Node ID is 0 to 15.
Represents the transmit PHY rate in Mbps.
Represents the MAC throughput in Kbps.
Represents one decibel or 1 dB.
Represents a measure of power in mW expressed in decibels, and calculated as follows:
power = 10*log10( Vrms^2 / R * 1000 )
where Vrms is the root-mean-square Voltage of the received waveform and R is 75 ohms.
Represents the subcarrier modulation.
Binary string array (array of two hexadecimal characters) with 1 byte for each subcarrier. The value of each byte represents the subcarrier modulation for the corresponding subcarrier.
See {{bibref|MoCAv2.0|section 14.3.6.3}} and {{bibref|MOCA20-MIB|Appendix A}} for the encoding of this parameter.
Represents the MoCA Bands and sub-bands the device is configured to operate in or that the device supports. {{enum}}
See {{bibref|MoCAv2.0|section 15}}.
Represents the Power State defined by the MoCA2.0 specification.
{{enum}}
See {{bibref|MoCAv2.0|section 12}}.
Power State M0: Active.
Power State M1: Low Power Idle.
Power State M2: Standby.
Power State M3: Sleep.
Represents the MoCA 2.0 PQOS Ingress Classification Rule.
Represents the MoCA 2.0 primary or secondary channel, or MoCA 2.5 first, second, third, fourth, or fifth channel.
Represents a type of MoCA Privacy.
Cut-down version of SNMP RowStatus that supports only its "status" values, not its "control" values.
The row is available for use by the managed device.
The row exists in the Agent, but is unavailable for use by the managed device (see NOTE below); "notInService" has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device.
The row exists in the Agent, but is missing information necessary in order to be available for use by the managed device, i.e., one or more required parameter in the row have not been populated.
Not used.
Not used.
Not used.
The Node ID of the MoCA Node to transmit the EVM Probe when the parameter {{param|Type}} = {{enum|evm|Type}}.
The ACA (Alternate Channel Assessment) type is either {{enum|evm}} or {{enum|quiet}}.
The channel number under assessment, starting from 0 in increments of 25 MHz.
Specifies the MoCA Nodes that are requested to be part of the channel assessment: Setting bits corresponding to Node IDs of these MoCA Nodes to 1.
See {{bibref|MoCAv2.0|Section 6.2.1}}
dBm (-128 to +127 dBm).
Binary string array with 1 byte (represented as two hexadecimal digits) for each subcarrier. See {{bibref|MOCA11-MIB|Appendix A}} for the encoding of this object.
MoCA object that contains the {{object|Interface}} table
{{bibref|MoCAv1.0}} {{bibref|MoCAv1.1}}.
MoCA interface table (a stackable interface object as described in
{{bibref|TR-181i2|Section 4.2}}). Each table entry models the PHY and
MAC levels of a MoCA interface {{bibref|MoCAv1.0}} {{bibref|MoCAv1.1}}.
{{numentries}}
{{numentries}}
{{numentries}}
{{numentries}}
{{numentries}}
{{numentries}}
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The MAC Address of the interface.
Note: This is not necessarily the same as the Ethernet header source
or destination MAC address, which is associated with the IP interface
and is modeled via the {{param|##.Ethernet.Link.{i}.MACAddress}}
parameter.
This interface's firmware version.
This parameter is based on ''mocaIfSoftwareVersion'' from
{{bibref|MOCA11-MIB}}.
The maximum bandwidth of this interface for flows onto the MoCA
network.
This parameter is based on ''mocaIfMaxIngressNodeBw'' from
{{bibref|MOCA11-MIB}}.
The maximum bandwidth of this interface for flows from the MoCA
network.
This parameter is based on ''mocaIfMaxEgressNodeBw'' from
{{bibref|MOCA11-MIB}}.
Identifies the highest MoCA version that this interface supports.
This element MUST be in the form of dot-delimited integers, where
each successive integer represents a more minor category of
variation. For example, 1.0, where the components mean major.minor
revision number. {{pattern}}
This parameter is based on ''mocaIfMocaVersion'' from
{{bibref|MOCA11-MIB}}.
Identifies the MoCA version that the MoCA network is currently
running.
This element MUST be in the form of dot-delimited integers, where
each successive integer represents a more minor category of
variation. For example, 1.0, where the components mean major.minor
revision number. {{pattern}}
This parameter is based on ''mocaIfNetworkVersion'' from
{{bibref|MOCA11-MIB}}.
The Node ID of the current Network Coordinator (NC) for the MoCA
network.
This parameter is based on ''mocaIfNC'' from {{bibref|MOCA11-MIB}}.
The Node ID of this interface.
This parameter is based on ''mocaIfNodeID'' from
{{bibref|MOCA11-MIB}}.
The maximum network node capability supported by the interface. If
{{param}} is {{true}} then the interface supports 16 nodes (the
maximum for a MoCA 1.1 network). If {{param}} is false then the
interface supports 8 nodes (the maximum for a MoCA 1.0 network).
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The numbers of 1's in the GCD_BITMASK field reported in Type I Probe Reports. This value corresponds to the number of MoCA Nodes that this MoCA Node communicates to in the MoCA network.
This value may be smaller than the number of MoCA Nodes reported by the NC Node.
See {{bibref|MoCAv1.1|Section 3.6.3.2}}.
Whether this interface is a preferred Network Coordinator (NC).
This parameter is based on ''mocaIfPreferredNC'' from
{{bibref|MOCA11-MIB}}.
The Node ID of the backup Network Coordinator node.
This parameter is based on ''mocaIfBackupNC'' from
{{bibref|MOCA11-MIB}}.
The configured privacy mode. This indicates whether link-layer
security is enabled ({{true}}) or disabled ({{false}}) for network
admission.
Indicates whether link-layer security is enabled or disabled.
This parameter is based on ''mocaIfPrivacyEnable'' from
{{bibref|MOCA11-MIB}}.
{{deprecated|2.17|because it and {{param|PrivacyEnabledSetting}} are associated with the same underlying MIB object and it is therefore unnecessary. If implemented, it MUST return the same value as {{param|PrivacyEnabledSetting}}}}
{{obsoleted|2.19}}
{{deleted|2.20}}
Enable MAC address access control on the MoCA interface if this value is {{true}}. Disable MAC address access control on the MoCA interface if this value is {{false}}.
Access control applies to subsequent MoCA Node admission.
The minimum PHY rate.
Only one MoCA Node in the MoCA network should set {{param}} to {{true}}.
This description is replaced by those from CWMP and USP.
Only one MoCA Node in the MoCA network should set {{param}} to {{true}}.
The Target PHY Rate of the receiving MoCA 2.0 Node in order to optimize the long-term PHY rate and transmit power level between the transmitting and receiving MoCA Nodes when TPC is enabled and PERMODE = NPER.
Configure the band or sub-band for the MoCA Node to operate in (BND Managed Parameter).
See {{bibref|MoCAv2.0|section 15}}.
Controls whether the LOF is updated when joining a network (LOF_UPDATE_EN Managed Parameter).
See {{bibref|MoCAv2.0|section 8.1.1, and Table 17-1}}.
The frequencies that the interface supports.
{{datatype|expand}}
The enabled frequencies that the interface supports for network admission.
{{datatype|expand}}
The configured frequencies might not match the current operational state ({{param|FreqCurrentMask}}), since this setting is only applied during network formation or admission.
The frequencies that can be used. This is a subset of the {{param|FreqCapabilityMask}} frequencies.
{{datatype|expand}}
Current Operational Frequency. The RF frequency in Hz to which the
MoCA interface is currently tuned. This parameter is only valid when
{{param|Status}} is {{enum|Up|Status}}.
This parameter is based on ''mocaIfRFChannel'' from
{{bibref|MOCA11-MIB}}.
Last Operational Frequency. The RF frequency in Hz to which the MoCA
interface was tuned when last in the {{enum|Up|Status}} state.
This parameter is based on ''mocaIfLOF'' from {{bibref|MOCA11-MIB}}.
(LOF Managed Parameter)
This parameter is writable only for MoCA 2.0.
Enable automatic power control if this value is {{true}}. Use a fixed transmit power level if this value is {{false}}.
(TPC_EN Managed Parameter)
MoCA Password. The value consists of numeric characters (0-9).
{{pattern}}
This parameter is based on ''mocaIfPassword'' from
{{bibref|MOCA11-MIB}}.
Controls which transmission PER mode the MoCA Node uses for MPDUs not belonging to PQoS Flows, where a value of 0 indicates NPER and 1 indicates VLPER. By default PER mode is set to 1 in band E, while it is set to 0 for all other bands (PER_MODE Managed Parameter).
See {{bibref|MoCAv2.0|section 8.2 and Table 17-2}}.
Controls whether the MoCA Node operates in point-to-point Turbo Mode or not.
When set to {{true}} the turbo mode is enabled; when set to {{false}} the turbo mode is disabled (TURBO_MODE_EN Managed Parameter).
See {{bibref|MoCAv2.0|section 10 and Table 17-1}}.
Controls whether policing of PQoS Flows is enabled or disabled. When {{false}} the policy is disabled, and when {{true}} the policy is enabled (POLICING_EN Managed Parameter).
See {{bibref|MoCAv2.0|section 8.8 and Table 17-1}}.
The minimum time (in milliseconds) a MoCA Node is required to stay in the Listening Phase of the Network Search (TLP_MIN Managed Parameter).
See {{bibref|MoCAv2.0|Table 17-2}}.
The maximum time (in milliseconds) a MoCA Node is required to stay in the Listening Phase of the Network Search (TLP_MAX Managed Parameter).
Default value of {{param}} depends on the band configuration as follows:
* 20 seconds for band E
* 35 seconds for band F
* 95 seconds for Band ExD
* 10 seconds for Band D-Low
* 55 seconds for Band D-High
See {{bibref|MoCAv2.0|section 8.1}}.
Controls whether the RLAPM (Receive Level Added PHY Margin) function is enabled and the MoCA Node needs to apply it, or disabled and the MoCA Node needs to ignore it.
RLAPM function is enabled when set to {{true}}. RLAPM function is disabled when set to {{false}}.
The RLAPM function allows a Node to add a specific global PHY margin (RLAPM) to all the subcarriers' bitloadings at each estimated aggregate receive power level. This RLAPM value is obtained from the RLAPM table {{object|Device.MoCA.Interface.{i}.Rlapm.{i}.}}.
See {{bibref|MoCAv2.0|section 7.15 and Table 17-1}}.
Controls which RLAPM (Receive Level Added PHY Margin) profile is Active.
See {{bibref|MoCAv2.0|section 7.15.2 and Table 17-1}}.
Controls whether the SAPM (Subcarrier Added PHY Margin) function is enabled and the MoCA Node needs to apply it, or disabled and the MoCA Node needs to ignore it.
SAPM function is enabled when set to {{true}}. SAPM function is disabled when set to {{false}}.
The SAPM function allows a Node to add a prespecified PHY margin to each subcarrier’s bitloading (SAPM value) whenever the aggregate received power levels (ARPLs) are below a pre-specified threshold. This SAPM value is obtained from the SAPM table {{object|Device.MoCA.Interface.{i}.Sapm.{i}.}}.
See {{bibref|MoCAv2.0|section 7.15 and Table 17-1}}.
Controls which SAPM (Subcarrier Added PHY Margin) profile is Active.
See {{bibref|MoCAv2.0|section 7.15.1 and Table 17-1}}.
Carries a request to the MoCA Node to transition into a specified Power State (POWER_STATE_REQ Managed Parameter).
See {{bibref|MoCAv2.0|section 12}}.
Sequence Number used by the MR Transaction (SEQ_NUM_MR Managed Parameter).
See {{bibref|MoCAv2.0|section 7.15 and Table 17-1}}.
Used for power state message trap.
* When set to {{true}} it allows the MoCA Node to report a trap on each Power State transition.
* When set to {{false}} no trap report is generated when the MoCA Node Power State changes.
See {{bibref|MoCAv2.0|section 12}}.
Used for LMO (Link Maintenance Operation) message trap.
* When set to {{true}} it allows the MoCA Node to report a trap on transitioning to LMO.
* When set to {{false}} no trap report the MoCA Node is not transitioning to LMO.
See {{bibref|MoCAv2.0|section 12}}.
The offset in {{units}} of the primary channel relative to the beacon channel (PRIMARY_OFFSET Managed Parameter).
The offset in {{units}} of the secondary channel relative to the beacon channel (SECONDARY_OFFSET Managed Parameter).
A value of 0 indicates that there is no secondary channel.
The networkwide (see {{param|BeaconPowerMePie}}) value of Beacon transmit power in {{units}} sent by the NC (Network Coordinator) in Beacon Power PIEs (Power Information Elements).
A value of 255 indicates that no networkwide PIE is sent.
See {{bibref|MoCAv2.5|section 7.1.5 and Table 17-1}}.
The value of Beacon transmit power in {{units}} used by the Node when it transmits beacons.
The Beacon Power PIE (Power Information Element) that the ME (Management Entity) wants the NC (Network Coordinator) to send to configure the Beacon Transmit Power of the different nodes. See {{bibref|MoCAv2.5|section 7.1.5}}.
This parameter specifies if the Beacon transmit power is intended to set the Beacon Power Local (individual type) or the Beacon Power Distributed (networkwide type) of the selected nodes.
It is encoded as specified in {{bibref|MOCA25-MIB|section 4.11}}.
When this parameter is written, instructs the Node (in case of Network Coordinator) to send a set of Beacon Power PIEs (Power Information Element) with the Beacon Power PIE fields set as specified in {{param|BeaconPowerMePie}}.
See {{bibref|MoCAv2.5|section 7.1.5}}.
Controls whether the Node is allowed to configure its Beacon power (both Beacon Power Distributed and Beacon Power Local) according to the Beacon Power PIE (Power Information Element) sent by the NC (Network Coordinator).
* When set to true the Node is allowed to configure its Beacon power.
* When set to false the Node is not allowed to configure its Beacon power.
See {{bibref|MoCAv2.5|section 7.1.5 and Table 17-1}}.
The MoCA Enhanced Password using an ASCII printable character.
This value must be 12 to 64 ASCII printable characters with decimal codes in the range 33 to 126 inclusive. Access is only allowed when used with SNMPv3 protocol, but not allowed when used with SNMPv1 or SNMPv2c protocol.
If this value changes, this node will drop from the network if {{param|PrivacyEnabledSetting}} is {{true}}. If this managed object is changed, it may not be possible to change this object again via the SNMP protocol. The mechanism to change this object again is out of the scope of this MIB definition draft.
See {{bibref|MoCAv2.5|section 11.3.1}}.
The offset of the First Channel's center frequency below the center frequency of the Primary Channel. Valid values are -4 to 0.
See {{bibref|MoCAv2.5|Table 17-1}}.
Enable handoff to a MoCA 2 or MoCA 1 Node if this value is {{true}}. Disable handoff to a MoCA 2 or MoCA 1 Node if this value is {{false}}.
See {{bibref|MoCAv2.5|section 8.11.1 and Table 17-1}}.
The number of Discovery Request transmission opportunities a NN has to wait for a response to a Management Entity Response Network IE before continuing its network search.
See {{bibref|MoCAv2.5|section 8.3.3.2 and Table 17-1}}.
The payload of the Management Entity Request Network IE (when the Node is trying to join the network), or of the Management Entity Response Network IE (when the Node is the NC).
See {{bibref|MoCAv2.5|section 8.3.3 and Table 17-1}}.
struct moca25IfMgntEntityNetIePayload {
short vendorId; // 2 octets (MoCA Vendor ID)
char information[60]; // 60 octets (Up to 60 bytes of vendor specific information)
}
Controls whether the Node, during its MPS (MoCA Protected Setup) session, is allowed to accept privacy setting of Privacy Disabled from another Node when its own setting is Privacy Enabled. This parameter is valid only when {{param|MpsPrivacyReceive}} is set to {{true}}.
See {{bibref|MoCAv2.5|section 8.3.1 and Table 17-1}}.
Controls whether the Node, during its MPS (MoCA Protected Setup) session, is allowed to accept privacy settings (Privacy Enabled / Disabled and Network Password and/or Enhanced Network Password) from another Node.
See {{bibref|MoCAv2.5|section 8.3.1 and Table 17-1}}.
Resets the MPS (MoCA Protected Setup) state of the Node {{param|MpsState}} to un-Paired and reinitializes MPS local variables and relevant parameters when this parameter is written.
See {{bibref|MoCAv2.5|Section 8.3.1 and Table 17-1}}.
Signals the Node in Power State M0 (Active) or M1 (Low Power Idle) that MPS (MoCA Protected Setup) was triggered when this parameter is written.
See {{bibref|MoCAv2.5|Section 8.3.1 and Table 17-1}}.
The minimum time in {{units}} the Node is required to stay in the un-Paired state after it starts network search if the Node creates or joins a network without using MPS (MoCA Protected Setup).
See {{bibref|MoCAv2.5|Section 8.3.1 and Table 17-1}}.
The allowed time interval in {{units}} to trigger MPS (MoCA Protected Setup) on two Nodes.
See {{bibref|MoCAv2.5|Section 8.3.1 and Table 17-1}}.
Instructs the NN to join the latest network from which the NN forwarded a Management Entity Response Network IE: Yes if this value is {{true}} and No if this value is {{false}}.
See {{bibref|MoCAv2.5|Section 8.3.3 and Table 17-1}}.
Controls which Admission rule to follow.
See {{bibref|MoCAv2.5|Section 8.3.3 and Table 17-1}}.
Join no network.
Join any network.
Join only the network with a network name that matches {{param|NetworkNameNcNn}}.
Wait for management entity instructions after exchanging OSP messages.
The Network Name the Node is to use for any MoCA network it creates.
When {{param|NetworkNameAdmissionRule}} is set to {{enum|name|NetworkNameAdmissionRule}}, this object also indicates to the Node the name of the network to join.
See {{bibref|MoCAv2.5|Section 8.3.3 and Table 17-1}}.
The maximum number of 100MHz channels the Node uses when the Node forms the network.
See {{bibref|MoCAv2.5|Table 17-1}}.
Controls which PER mode the receiver Node uses for calculating the bitloading of MoCA 2.5 Unicast profiles, where a value of 0 indicates NPER and 1 indicates VLPER.
See {{bibref|MoCAv2.5|Table 17-1}}.
Controls whether MoCA 2 Enhanced Privacy, MoCA 2.0 privacy, and MoCA 1 privacy are supported when privacy is enabled.
See {{bibref|MoCAv2.5|Section 11 and Table 17-1}}.
The EtherType value of MSDUs that are allowed to transmit/receive to/from a Non-Secured Admitted Node.
See {{bibref|MoCAv2.5|Section 11.7 and Table 17-1}}.
Up to 15 pairs of {Node ID, SOURCE_NODE_BITMASK} where SOURCE_NODE_BITMASK is the value for SOURCE_NODE_BITMASK for the Node with the given Node ID in an Authorized Link PIE that the ME of the Authorization Server wants to distribute if the Node is the Authorization Server; otherwise, the value of SOURCE_NODE_BITMASK in the last received Authorized Link PIE.
See {{bibref|MoCAv2.5|Section 11.7 and Table 17-1}}.
struct moca25IfTrafficPermissionLink {
long nodeIdVector; // 8 octets; Bit value in the ith bit position indicates NodeID=(i) (LSB=bit0)
int numNodes; // 4 octets (Number of Node IDs indicated in the NodeIdVector)
struct {
short SrcNodeBitmask; // 2 octets (SOURCE_NODE_BITMASK in the latest Authorized Link PIE)
}[numNodes];
};
* When set to {{true}} it allows the MoCA Node to report a trap on the change of {{param|NumNodes}}.
* When set to {{false}} no trap report is generated when {{param|NumNodes}} changes.
* When set to {{true}} it allows the MoCA Node to report a trap on reception of a Management Entity Request/Response Network IE.
* When set to {{false}} no trap report is generated when a Management Entity Request/Response Network IE is received.
This description is replaced by those from CWMP and USP.
* When set to {{true}} it allows the MoCA Node to report a trap on reception of a new NC_PRIVACY_SUPPORTED value.
* When set to {{false}} no trap report is generated when a new NC_PRIVACY_SUPPORTED value is received.
* When set to {{true}} it allows the MoCA Node to report a trap on reception of a Network Name.
* When set to {{false}} no trap report is generated when a Network Name is received.
This description is replaced by those from CWMP and USP.
The value in dB by which to reduce the transmit power of the node from its maximum transmit power. The transmit power SHALL only be changed when {{param|Status}} is not {{enum|Up|Status}}, which means the interface is not part of a MoCA network. If changed, the parameter may not take effect until the MoCA interface is restarted.
This parameter is based on ''mocaIfTxPowerLimit'' from {{bibref|MOCA11-MIB}}.
Target PHY rate in Mbps for the power control algorithm.
The MoCA interface SHOULD have {{param|Enable}} set to {{false}} for
any change in this configuration. If the parameter is modified when
{{param|Enable}} is {{true}} then this change might take several
minutes to complete.
This parameter is based on ''mocaIfPowerControlTargetRate'' from
{{bibref|MOCA11-MIB}}.
The value in dB by which to reduce the setting of the transmit power of the Beacon from the maximum transmit power (BEACON_PWR_BACKOFF Managed Parameter). The beacon transmit power SHALL only be changed when {{param|Status}} is not {{enum|Up|Status}}, which means the interface is not part of a MoCA network. If changed, the parameter may not take effect until the MoCA interface is restarted.
This parameter is based on ''mocaIfBeaconPowerLimit'' from {{bibref|MOCA11-MIB}}.
Note that this parameter maps to different MIB objects for MoCA 1.0/1.1 and MoCA 2.0.
{{deprecated|2.17|for MoCA 2.5}}
{{obsoleted|2.19}}
{{deleted|2.20}}
The MoCA taboo channels identified for the home network.
{{datatype|expand}}
The MoCA taboo channels identified for this device.
{{datatype|expand}}
Lists all the supported bands and sub-bands by this device.
The broadcast PHY transmit rate for this interface.
This parameter is based on ''mocaIfTxGcdRate'' from
{{bibref|MOCA11-MIB}}.
Transmit Power attenuation relative to the maximum
transmit power for broadcast transmissions.
This parameter is based on ''mocaIfTxGcdPowerReduction'' from
{{bibref|MOCA11-MIB}}.
Whether this interface supports the 256 QAM feature.
This parameter is based on ''mocaIfQAM256Capable'' from
{{bibref|MOCA11-MIB}}.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The packet aggregation capability supported by the interface.
Standard values are 0 (no support), 6 (6 {{units}}) or 10 (10
{{units}}).
This parameter is based on ''mocaIfPacketsAggrCapability'' from
{{bibref|MOCA11-MIB}}.
Note that this parameter maps to different MIB objects for MoCA 1.0/1.1 and MoCA 2.0.
[XXX1: Need to modify the syntax to 'unsignedInt' because MoCA 2.0 requires a minimum of 20 packets and MoCA 2.5 requires a minimum of 80 packets.]
{{numentries}}
The 16 LSBs of a SHA1 performed on a 0-extended password ({{param|KeyPassphrase}}) concatenated with the SALT string "MocaPasswordHash". This parameter allows to remotely validate the MoCA password configuration without exposing its value. This value must be 4 hexadecimal digits long.
The maximum number of bytes in one aggregate which can be received by the MoCA Node.
Maximum number of allocation elements, excluding the TAUs and the Dummy DAUs, in one MAP the MoCA Node can process.
Maximum number of Ingress PQoS Flows supported by the MoCA Node.
Maximum number of Egress PQoS Flows supported by the MoCA Node.
The Power State capabilities of the MoCA Node (e.g., which Power States it can transition to) (POWER_STATE_CAP Managed Parameter). This value can change over time (e.g. when a MoCA 1 Node joins the network).
The support of the MoCA Node for the IEEE 802.1 Audio Video Bridge specification. AVB is supported if this value is {{true}}. AVB is not supported if this value is {{false}}.
Count of MoCA resets since the interface was enabled for this MoCA Node.
The number of times that this MoCA Node has lost link with the MoCA network since the interface was enabled.
The ID of the MoCA Node currently undergoing LMO (Link Maintenance Operation), i.e. the LMO node.
The current Link control state in the MoCA network for the MoCA Node. This network state is a MAC parameter determined by the NC (Network Coordinator) and broadcasted in the MAP to the rest of nodes.
{{enum|beginNodeAdmissionState}}, {{enum|newNodeTypeOneProbeTxState}}, {{enum|newNodeTypeOneProbeRxState}}, {{enum|newGcdDistributionState}}, {{enum|beginPhyProfileState}}, {{enum|steadyState}} refer to the Node Admission (see {{bibref|MoCAv2.5|Section 8.3}}). The admission process of a new MoCA node depends on the operation mode of the MoCA Network that it is going to join (MoCA 1 mode, MoCA 2.0 mode or Mixed Mode). The Node Admission process is completed when the NC (Network Controller) changes the network state to Steady State ({{enum|steadyState}}) at the end of the Node Admission process.
{{enum|typeThreeProbeState}}, {{enum|lmoTypeOneProbeState}}, {{enum|lmoNodeGcdDistributionState}}, {{enum|beginLmoPhyProfileState}}, {{enum|lmoGcdTypeOneProbeLinkState}}, {{enum|steadyState}} refer to the Regular Link Maintenance Operation (see {{bibref|MoCAv2.5|Section 8.9.1}}).
{{enum|alternateChannelQuietLineState}}, {{enum|alternateChannelEvmProbeState}}, {{enum|unsolicitedProbeReportState}}, {{enum|beginUnsolicitedPhyProfileState}}, {{enum|rxDeterminedProbeState}}, {{enum|steadyState}} refer to the On-Demand Link Maintenance Operation (see {{bibref|MoCAv2.5|Section 8.9.2}}).
{{enum|calibrationState}} refer to the Network Operation after a NC handoff or failover (see {{bibref|MoCAv2.5|Section 8.14}}).
"Begin Node Admission State" starts after completing the pre-admission discovery message exchange with the NC, then the joining node sends an admission request frame to the NC. During this state, the EVM (Error Vector Magnitude) probes and link acknowledgments are exchanged between the new node, the NC and the existing nodes in the network. Refer to {{bibref|MoCAv2.5|Section 8.3.4}} for details.
The NC advances the network state to "New Node Type I Probe Tx State" after receiving next link state indication from all the nodes. During this state, the Beacon Channel (in the presence of MoCA 1 nodes) from the MoCA 2 new nodes to all other existing nodes (including the NC) is characterized and the modulation used on this channel is optimized. The Primary Channel, MoCA 2.x bonded channels from the MoCA 2 new nodes to all other MoCA 2 Nodes (including NC) are characterized and the modulation on these channels is optimized. Refer to {{bibref|MoCAv2.5|Section 8.3.5}} for details.
The NC advances the network state to "New Node Type I Probe Rx State" after relaying Type I Probe Reports of all nodes, and after it has received next state indication from each node. Refer to {{bibref|MoCAv2.5|Section 8.3.6}} for details.
The NC advances the network state to "New Node GCD Distribution State" once it has received the next state indication from each node to "New Node GCD Distribution State". In this state, the GCD (Greater Common Denominator) Distribution Reports are distributed. Refer to {{bibref|MoCAv2.5|Section 8.3.7}} for details.
The NC advances the network state to "Begin PHY Profile State" when all nodes indicate “Begin PHY Profile State” in their RR (Reservation Request). Upon reception of this state, the node (new or existing) activates the new computed PHY profiles. Refer to {{bibref|MoCAv2.5|Section 8.3.8}} for details.
The node advances to "Steady State" after waiting for T15 or T16 (NC) in {{enum|beginPhyProfileState}}. Refer to {{bibref|MoCAv2.5|Section 8.3.9}} for details.
The node advances to "Steady State" after waiting for T15 in {{enum|beginUnsolicitedPhyProfileState}} or, in case of NC, after receiving “Steady State” indication from each node. Refer to {{bibref|MoCAv2.5|Section 8.9.2.2.3}}.
The node advances to "Steady State" after waiting for T15 or T16 (NC) in {{enum|beginLmoPhyProfileState}}. Refer to [Section 8.9.1.7/MoCAv2.5] for details.
During this first state of the Regular LMO, Type III Probes are exchanged between the LMO node and the rest of nodes. Refer to {{bibref|MoCAv2.5|Section 8.9.1.2}} for details.
After the exchange of the EVM Reports during the state {{enum|typeThreeProbeState}}, Type I Probes are exchanged between the LMO node and and all other 1.x nodes. This state finalizes after the LMO node receives the Composite OFDMA Probes from the MoCA 2 Nodes. Refer to {{bibref|MoCAv2.5|Section 8.9.1.3}} for details.
After state {{enum|lmoGcdTypeOneProbeLinkState}}, the LMO node distributes the new GCD Report to all nodes. Refer to {{bibref|MoCAv2.5|Section 8.9.1.5}} for details.
The NC advances the network state to "Begin LMO PHY Profile State". When a node receives the "Begin LMO PHY Profile" Link Control state notification, it can start using the newly computed PHY profiles. Refer to {{bibref|MoCAv2.5|Section 8.9.1.6}} for details.
The NC advances the network state to "GCD Type I Probe Link State". In this state, the LMO node broadcasts GCD Type I Probes to all nodes. For details, refer to {{bibref|MoCAv2.5|Section 8.9.1.4}}.
The node moves into the "Alternate Channel Quite Line State" to measure quiet line noise and interference levels in the alternate MoCA channel. Refer to {{bibref|MoCAv2.5|Section 8.9.2.5}} for details.
The node moves into the "Alternate Channel EVM Probe State" to measure EVM Probe signal level in the alternate MoCA channel. Refer to {{bibref|MoCAv2.5|Section 8.9.2.5}} for details.
The NC sets the network state to "Unsolicited Probe Report State" after a node request to move to this state in order to update a PHY Profile. Refer to {{bibref|MoCAv2.5|Section 8.9.2.2.1}} for details.
After state {{enum|unsolicitedProbeReportState}}, a node can begin using the new PHY profiles once the NC sets the network state to "Begin Unsolicited PHY Profile".{{bibref|MoCAv2.5|Section 8.9.2.2.2}}
In order to use Receiver-Determined probes, the receiver must move from {{enum|steadyState}} to "Rx Determined Probe State". Refer to {{bibref|MoCAv2.5|Section 8.9.2.1}} for details.
During network operations after switching to a new NC, the NC node sets the network state to "Calibration State". During this state, any node can request time to perform calibration by sending probes. Refer to {{bibref|MoCAv2.5|Section 8.14.1}} and {{bibref|MoCAv2.5|Section 8.14.2}}.
The offset in MHz of the primary channel relative to the beacon channel. The allowed values are -25, 0, and +25.
The offset in MHz of the secondary channel relative to the beacon channel. The allowed values are -125 and +125. A value of 0 indicates that there is no secondary channel.
Describes the reason for a MoCA link reset or failure to join a network.
Indicates the MoCA version of the NC.
This element MUST be in the form of dot-delimited integers, where each successive integer represents a more minor category of variation. For example, 1.0, where the components mean major.minor revision number. Possible patterns:
* ''\d+(\.\d+)*''
This parameter is meaningful only after a Link Failure to indicate the state of the network the at the time of the Link failure. Each of the three chars (bytes) is represented as two hexadecimal digits.
struct mocaLinkState {
char LINK_STATE; // LINK_STATE_II from the Tx/Rx MAP at the
// time of the Link Failure
char ACF_TYPE; // ACF_TYPE from the Tx/Rx BEACON
// at the time of the Link Failure
char ADD_ACF_TYPE; // ADDITIONAL_ACF_TYPE from the Tx/Rx
// BEACON at the time of the Link Failure
};
Indicates the information for each node connected in the network for up to 16 nodes.
See {{bibref|MoCAv2.5|Table 17-1}}.
struct moca25ConnectedNodesInfo {
long nodeIdVector; // 8 octets; Bit value in the ith bit position indicates NodeID=(i) (LSB=bit0)
int numNodes; // 4 octets (Number of Node IDs indicated in the NodeIdVector)
struct {
char guid[8]; // 8 octets (Node GUID MAC Address)
char mocaVersion; // 1 octet (MoCA Version)
}[numNodes];
};
Indicates the payload of the latest received Management Entity Request Network IE, or Management Entity Response Network IE.
See {{bibref|MoCAv2.5|Table 17-1}}.
struct moca25IfMgntEntityNetIePayload {
short vendorId; // 2 octets (MoCA Vendor ID)
char information[60]; // 60 octets (Up to 60 bytes of vendor specific information)
};
Indicate the MoCA Node supports MoCA 2.5 PHY if the value is {{true}}.
Indicate the MoCA Node does not support MoCA 2.5 PHY if this value is {{false}}.
See {{bibref|MoCAv2.5|section 8.3.4.1.1}}.
Reports the channel number, NC's (Network Coordinators) MoCA version, Network MPS (MoCA Protected Setup) trigger, and Network MPS parameters (if any) and Network Name of the latest MoCA network found during Initial MPS Scanning. See {{bibref|MoCAv2.5|section 8.3.1.1.1}}.
It is encoded as specified in {{bibref|MOCA25-MIB|section 4.6}}.
Indicates the MPS (MoCA Protected Setup) state of the Node: paired if the value is {{true}} and un-Paired if the value is {{false}}.
See {{bibref|MoCAv2.5|section 8.3.1}}.
The payload of the latest received Network Name from the NC.
See {{bibref|MoCAv2.5|section 8.3.3.2}}.
The latest NC_PRIVACY_SUPPORTED value received from the NC. Before any NC_PRIVACY_SUPPORTED is received, reflects the value of {{param|PrivacySupported}}.
See {{bibref|MoCAv2.5|Table 17-1}}.
Carries the response of the MoCA Node to a request (through POWER_STATEREQ) to transition into a desired Power State: yes if the value if {{true}} and no if the value is {{false}}.
See {{bibref|MoCAv2.5|section 12}}.
Reports the current Power State of the Node (POWER_STATE_STATUS Managed Parameter).
Reports the GUID(s) of the dropped EN(s) and the reason of node drop for up to 15 nodes.
This object is valid only when the Node is the NC.
See {{bibref|MoCAv2.5|Table 17-1}}.
struct moca25IfConnectedNodesDropReason {
int numNodes; // 4 octets (Number of dropped nodes)
struct {
char guid[8]; // 8 octets (Node GUID MAC Address)
char dropReason; // 1 octet (Reason of node drop:
// 0x00 Admission Failure
// 0x01 Key Response Timeout
// 0x02 Heartbeat Transmission Timeout
// 0x03 Power State M0 Transition Timeout
// 0x04 Disadvantaged Node
// 0x05 RR Transmission Timeout)
}[numNodes];
};
MoCA interface MAC access control table. This table contains a list of MAC addresses that are allowed to connect to the MoCA network. In addition to being in this access control list, a MoCA Node must have the proper {{param|#.FreqCurrentMask}}, {{param|#.PrivacyEnabledSetting}}, and {{param|#.KeyPassphrase}} before the MoCA Node can form or join a MoCA network.
Enables or disables this MAC address to be allowed to connect to the MoCA network.
If {{param|#.AccessControlEnable}} is set to {{true}}, MoCA Node with this MAC address is allowed to join the MoCA network. It is not guaranteed that the MoCA Node with this MAC address can form or join a network.
Interface RLAPM Table supporting the configuration of RLAPM (Receive Level Added PHY Margin) function parameters for the selected profile.
The pairs [{{param|GlobalAggrRxPwrLevel}} (GARPLi ), {{param|PhyMargin}} (RLAPMi)] are used to determine the subcarriers' bitloadings according {{bibref|MoCAv2.0|section 7.15.2 and Table 17-1}}.
Enables or disables this Rlamp entry.
Profile index used for the RLAPM (Receive Level Added PHY Margin) table.
Frequency (band) index used for the RLAPM (Receive Level Added PHY Margin) table.
Global Aggregated Receive Power Level (GARPL).
The parameter contains the "Ni" value, where GARPLi = -Ni dBm.
Receive Level Added Phy Margin (RLAPM).
The parameter contains the "Ni" value, where RLAPMi = 0.5*Ni dB.
Reflects the status of a row in this table.
Interface SAPM Table supporting the configuration of SAPM (Subcarrier Added PHY Margin) function parameters for the selected profile.
When the aggregate received power level (ARPL) is below the pre-specified threshold {{param|AggrRxPwrLevelThreshold}}, for each subcarrier, its corresponding value on the list {{param|PhyMargin}} will be considered to determine the subcarriers' bitloading according {{bibref|MoCAv2.0|section 7.15.2 and Table 17-1}}.
Enables or disables this Sapm entry.
Profile index used for the SAPM (Subcarrier Added PHY Margin) table.
Frequency (band) index used for the SAPM (Subcarrier Added PHY Margin) table.
Aggregate Received Power Level Threshold (ARPL_THLD).
The parameter contains the "N" value, where ARPL_THLD = -N dBm.
Subcarrier Added PHY Margin (SAPM).
List of SAPM values representing the PHY margin the Node is required to add to the bitloading of each of the available subcarriers when the received power level is below ARPL_THLD ({{param|AggrRxPwrLevelThreshold}}).
Each value contains the "Ni" value for a OFDM subcarrier "i", where SAPMi = 0.5*Ni dB.
Reflects the status of a row in this table.
Used by the managed MoCA Node to initiate MoCA Reset Transaction.
The MoCA Nodes that must respond to the MR transaction L2ME request sent by the NC except for the MR Entry Node (LSB corresponds to Node ID 0x0).
See {{bibref|MoCAv2.0|Section 6.2.1}}
Time in seconds after this parameter is written that a MoCA Node must initiate a MoCA Reset (MR).
See {{bibref|MoCAv2.0|Section 7.15}}.
This description is replaced by those from CWMP and USP.
This description is replaced by those from CWMP and USP.
The number of received Ethernet packets that have errors and are corrected by this MoCA interface.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The QoS object provides information on MoCA parameterized QoS for this
interface {{bibref|MoCAv1.1}}.
The number of QoS flows that this interface has from the MoCA
network.
This parameter is based on ''mocaIfEgressNodeNumFlows'' from
{{bibref|MOCA11-MIB}}.
The number of QoS flows that this interface has onto the MoCA
network.
This parameter is based on ''mocaIfIngressNodeNumFlows'' from
{{bibref|MOCA11-MIB}}.
{{numentries}}
The flow statistics table provides information on the MoCA
parameterized QoS flows this interface has allocated onto the MoCA
network.
The flow ID used to identify a flow in the network.
This parameter is based on ''mocaIfFlowID'' from
{{bibref|MOCA11-MIB}}.
Note that the data type has changed from ''unsignedInt'' to ''MACAddress''. This is because the original data type was an error and could not have been implemented as specified.
The Destination Address (DA) for the packets in this flow.
This parameter is based on ''mocaIfPacketDA'' from
{{bibref|MOCA11-MIB}}.
Maximum required rate in {{units}}.
This parameter is based on ''mocaIfPeakDataRate'' from
{{bibref|MOCA11-MIB}}.
Maximum burst size.
This parameter is based on ''mocaIfBurstSize'' from
{{bibref|MOCA11-MIB}}.
Flow lease time (expressed in {{units}}).
A {{param}} of 0 means unlimited lease time.
This parameter is based on ''mocaIfLeaseTime'' from
{{bibref|MOCA11-MIB}}.
The FLOW_TAG of the PQoS flow identified by {{param|FlowID}} in which this MoCA interface is an Ingress Node for this PQoS flow. The FLOW_TAG carries application specific content of this PQoS flow.
See {{bibref|MoCAv2.0|Section 6.3.13.1}}.
Flow lease time remaining (expressed in {{units}}).
If {{param|LeaseTime}} is 0 then a {{param}} of 0 means unlimited
lease time; otherwise, a {{param}} of 0 means expired.
This parameter is based on ''mocaIfLeaseTimeLeft'' from
{{bibref|MOCA11-MIB}}.
The number of packets transmitted for this flow.
This parameter is based on ''mocaIfTxPacketsFlow'' from
{{bibref|MOCA11-MIB}}.
The MAC address of the MoCA Node specified by the INGRESS_NODE_ID parameter of the flow.
See {{bibref|MoCAv2.0|Section 6.3.13.1}}.
The MAC address of the MoCA Node specified by the EGRESS_NODE_ID parameter of the flow.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The MAXIMUM_LATENCY parameter of the flow in units of milliseconds. A value of 0 indicates no value available.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The SHORT_TERM_AVERAGE_RATIO parameter of the flow.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The FLOW_PER parameter of this flow, where a value of 0 indicates NPER and 1 indicates VLPER.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The INGRESS_CLASSIFICATION_RULE parameter of the flow.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The VLAN_TAG parameter of the flow.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The DSCP_MOCA parameter of the flow.
See {{bibref|MoCAv2.0|section 6.3.13.1}}.
The destination flow ID of the flow assigned by the Ingress Node.
See {{bibref|MoCAv2.0|section 7.8.1.2}}.
This table contains information about other MoCA devices currently
associated with this MoCA interface.
Entries in this table cannot be created or deleted by the network management system. All entries are created or deleted by the device software.
The MAC address of the associated device's MoCA interface.
The Node ID of this remote device.
This parameter is based on ''mocaNodeIndex'' from
{{bibref|MOCA11-MIB}}.
Whether this remote device is a preferred Network Coordinator (NC).
This parameter is based on ''mocaNodePreferredNC'' from
{{bibref|MOCA11-MIB}}.
Identifies the highest MoCA version that this remote device supports.
This element MUST be in the form of dot-delimited integers, where
each successive integer represents a more minor category of
variation. For example, 1.0, where the components mean major.minor
revision number. {{pattern}}
This parameter is based on ''mocaNodeMocaVersion'' from
{{bibref|MOCA11-MIB}}.
The PHY transmit rate (in {{units}}) to this remote device.
This parameter is based on ''mocaMeshTxRate'' from
{{bibref|MOCA11-MIB}}.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The PHY receive rate (in {{units}}) from this remote device.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The reduction in transmitter level due to power
control.
This parameter is based on ''mocaNodeTxPowerReduction'' from
{{bibref|MOCA11-MIB}}.
{{deprecated|2.17|since it is replaced by {{param|Device.MoCA.Interface.{i}.Mesh.{i}.PowerReduction}}. See {{bibref|MOCA20-MIB}}}}
{{obsoleted|2.19}}
{{deleted|2.20}}
The power level (in {{units}}) received at the MoCA interface from
this remote device.
This parameter is based on ''mocaNodeRxPower'' from
{{bibref|MOCA11-MIB}}.
{{deprecated|2.17|since it is replaced by {{param|Device.MoCA.Interface.{i}.Mesh.{i}.Power}}. See {{bibref|MOCA20-MIB}}}}
{{obsoleted|2.19}}
{{deleted|2.20}}
The broadcast PHY transmit rate from this remote
device.
This parameter is based on ''mocaNodeTxGcdRate'' from
{{bibref|MOCA11-MIB}}.
The power level received at the MoCA interface from
this remote device.
This parameter is based on ''mocaNodeRxGcdPower'' from
{{bibref|MOCA11-MIB}}.
The number of packets transmitted to this remote device (Note:
Includes Broadcast, Multicast and Unicast packets).
The number of Unicast EPDUs received at the ECL, destined to the associated MoCA Node, and not transmitted by this MoCA interface.
The number of packets received from this remote device (Note:
Includes Broadcast, Multicast and Unicast packets).
This parameter is based on ''mocaNodeRxPackets'' from
{{bibref|MOCA11-MIB}}.
The number of Ethernet packets received by this MoCA interface that have errors and are corrected from the MoCA Node identified by {{param|MACAddress}}.
The number of errored and missed packets received from this remote
device.
This parameter is based on ''mocaNodeRxDrops'' from
{{bibref|MOCA11-MIB}}.
The MoCA Node identified by {{param|MACAddress}} supports Bonding if the value is {{true}}. The MoCA Node identified by {{param|MACAddress}} does not support Bonding if this value is {{false}}.
Whether this remote device supports the 256 QAM feature.
This parameter is based on ''mocaNodeQAM256Capable'' from
{{bibref|MOCA11-MIB}}.
This parameter MUST NOT be implemented for MoCA 2.0 because it doesn't map to a MIB object.
The packet aggregation capability supported by the remote device.
Standard values are 0 (no support), 6 (6 {{units}}) or 10 (10
{{units}}).
This parameter is based on ''mocaNodePacketsAggrCapability'' from
{{bibref|MOCA11-MIB}}.
Note that this parameter maps to different MIB objects for MoCA 1.0/1.1 and MoCA 2.0.
[XXX2: Need to modify the syntax to 'unsignedInt' because MoCA 2.0 requires a minimum of 20 packets and MoCA 2.5 requires a minimum of 80 packets.]
The signal to noise level received at this interface
from this remote device.
This parameter is based on ''mocaNodeSNR'' from
{{bibref|MOCA11-MIB}}.
{{deprecated|2.17|since it is replaced by {{param|Device.MoCA.Interface.{i}.Mesh.{i}.RxSNR}}. See {{bibref|MOCA20-MIB}}}}
{{obsoleted|2.19}}
{{deleted|2.20}}
Whether or not this remote device is currently present in the MoCA
network.
The ability to list inactive nodes is OPTIONAL. If the CPE includes
inactive nodes in this table, {{param}} MUST be set to {{false}} for
each inactive node. The length of time an inactive node remains
listed in this table is a local matter to the CPE.
The number of Ingress PQoS Flows supported by this MoCA interface from the MoCA Node identified by {{param|MACAddress}}.
The number of Egress PQoS Flows supported by this MoCA interface from the MoCA Node identified by {{param|MACAddress}}.
The maximum number of bytes that can be aggregated in a MoCA frame that this MoCA Node supports.
The maximum number of allocation elements, excluding the TAUs and the Dummy DAUs, in one MAP that this MoCA Node supports.
Power State of the MoCA Node identified by the {{param|MACAddress}}.
Power State capability of the MoCA Node identified by the {{param|MACAddress}}.
Propagation delay measured in units of 10ns between the local MoCA Node and the MoCA Node identified by the {{param|MACAddress}}.
Indicates the MoCA Node identified by {{param|MACAddress}} supports MoCA 2 Enhanced Privacy if the value is {{true}}. Indicates the MoCA Node identified by {{param|MACAddress}} does not support MoCA 2 Enhanced Privacy if this value is {{false}}.
Indicates the type of link used for unicast data transmissions between the managed MoCA Node and the MoCA Node identified by {{param|MACAddress}}.
MoCA 1 PHY.
Primary.
Bonded.
300 MHz MoCA 2.5 PHY.
400 MHz MoCA 2.5 PHY.
500 MHz MoCA 2.5 PHY.
Indicates the MoCA Node identified by {{param|MACAddress}} supports MoCA 2.5 PHY if the value is {{true}}. Indicates the MoCA Node identified by {{param|MACAddress}} does not support MoCA 2.5 PHY if this value is {{false}}.
Per channel list of Receive power levels in dBm from the MoCA Node identified by {{param|MACAddress}} to the managed MoCA Node.
The power measurement should cover the preamble and/or at least a symbol time. The averaging method employed for this measurement is implementation specific and not specified. It is recommended but not required to utilize the LMO (Link Maintenance Operation) EVM probes for this measurement.
The field numValues is a function of {{param|LinkType}}:
* MoCA 1 PHY - 1
* Primary - 1
* Bonded - 2
* 300 MHz MoCA 2.5 PHY - 3
* 400 MHz MoCA 2.5 PHY - 4
* 500 MHz MoCA 2.5 PHY - 5
struct moca25NodePowerList {
char numValues; // 1 octet (Number of Values to follow)
struct {
char power; // 1 octet (Rx Power Level in dBm)
} [numValues];
};
Per channel list of Average Receive Signal to Noise Ratio (SNR) across all available subcarriers based on the EVM probe from the MoCA Node identified by {{param|MACAddress}} to the managed MoCA Node.
The field numValues is a function of {{param|LinkType}}:
* MoCA 1 PHY - 1
* Primary - 1
* Bonded - 2
* 300 MHz MoCA 2.5 PHY - 3
* 400 MHz MoCA 2.5 PHY - 4
* 500 MHz MoCA 2.5 PHY - 5
struct moca25NodeRxSNRList {
char numValues; // 1 octet (Number of Values to follow)
struct {
char snr; // 1 octet (Rx SNR in dB)
} [numValues];
};
Per channel list of Transmit power levels in dBm from the managed MoCA Node to the MoCA Node identified by {{param|MACAddress}}. The transmit power should be max power for the channel less the Transmit Power Control.
The field numValues is a function of {{param|LinkType}}:
* MoCA 1 PHY - 1
* Primary - 1
* Bonded - 2
* 300 MHz MoCA 2.5 PHY - 3
* 400 MHz MoCA 2.5 PHY - 4
* 500 MHz MoCA 2.5 PHY - 5
struct moca25NodePowerList {
char numValues; // 1 octet (Number of Values to follow)
struct {
char power; // 1 octet (Tx Power Level in dBm)
} [numValues];
};
Per channel list of Transmit Power Control (TPC) back-off in dB used for unicast transmissions from the managed MoCA Node to the MoCA Node identified by {{param|MACAddress}}.
{{param}} is identical to the TPC back-off utilized for transmission from the TPC backoff parameter TX_POWER_ADJUSTMENT_100MHZ.
The field numValues is a function of {{param|LinkType}}:
* MoCA 1 PHY - 1
* Primary - 1
* Bonded - 2
* 300 MHz MoCA 2.5 PHY - 3
* 400 MHz MoCA 2.5 PHY - 4
* 500 MHz MoCA 2.5 PHY - 5
struct moca25NodeTxPwrReductionList {
char numValues; // 1 octet (Number of Values to follow)
struct {
char tpc; // 1 octet (TPC in dB)
} [numValues];
};
The number of PQoS flows in which this MoCA interface is an Egress Node for these PQoS flows.
The number of PQoS flows in which this MoCA interface is an Ingress Node for these PQoS flows.
MoCA mesh PHY rate table. This table contains the unicast transmit PHY rate between all pairs of MoCA Nodes in the MoCA network.
Since {{param|TxRate}} is the transmit PHY rate from {{param|TxNodeIndex}} to {{param|RxNodeIndex}}, this table does not contain any entries with {{param|TxNodeIndex}} equals {{param|RxNodeIndex}}. In addition, a MoCA network can have less than 16 Nodes, hence some values of {{param|TxNodeIndex}} and {{param|RxNodeIndex}} in the range of 0 to 15 may not exist.
Entries in this table cannot be created or deleted by the network management system. All entries are created or deleted by the device software.
The Node ID of the transmit MoCA Node is used as one of the index to order the mesh PHY rate table.
The Node ID of the receive MoCA Node is used as one of the index to order the mesh PHY rate table.
The transmit MoCA 1 PHY rate in Mbps from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}}.
The transmit normal packet error PHY Rate from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}}.
The transmit very low packet error PHY Rate from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}}.
The type of link which exists from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}}. {{enum}}
This parameter is only used for MoCA 2.0.
Per channel list of Transmit or Receive power levels in dBm. If the MoCA Node identified by {{param|TxNodeIndex}} is equal to {{param|#.NodeID}}, then indicates the unicast transmit power in dBm from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}}, else indicates the unicast receive power in dBm from the MoCA Node identified by {{param|TxNodeIndex}} at the MoCA Node identified by {{param|RxNodeIndex}}.
For transmit power, the power should be max power for the channel less the Transmit Power Control. For received power, the power measurement should cover the preamble and/or at least a symbol time. The averaging method employed for this measurement is implementation specific and not specified. It is recommended but not required to utilize the LMO (Link Maintenance Operation) EVM probes for this measurement.
The field ''numValues'' is a function of {{param|LinkType}}:
* {{enum|moca1PHY|LinkType}} - 1
* {{enum|primary|LinkType}} - 1
* {{enum|bonded|LinkType}} - 2
struct mocaPower {
char numValues; // 1 octet (Number of Values to follow)
{
char power; // 1 octet (Tx or Rx Power Level in dB)
} [numValues];
};
This parameter is only used for MoCA 2.0.
Per channel list of The Transmit Power Control (TPC) back-off in dB. If the MoCA Node identified by {{param|TxNodeIndex}} is equal to {{param|#.NodeID}}, then indicates the TPC in dB utilized to back-off transmission to the MoCA Node identified by {{param|RxNodeIndex}}. Otherwise indicates the TPC in dB that the MoCA Node identified by {{param|TxNodeIndex}} utilized to back-off its transmission.
{{param}} is identical to the TPC back-off utilized for transmission and determined from the TPC backoff parameters TPC_BACKOFF_MAJOR and TPC_BACKOFF_MINOR as follows: {{param}} = TPC_BACKOFF_MAJOR * 3 +TPC_BACKOFF_MINOR.
The field ''numValues'' is a function of {{param|LinkType}}:
* {{enum|moca1PHY|LinkType}} - 1
* {{enum|primary|LinkType}} - 1
* {{enum|bonded|LinkType}} - 2
struct mocaPowerReduction {
char numValues; // 1 octet (Number of Values to follow)
{
char tpc; // 1 octet (TPC in dB)
} [numValues];
};
This parameter is only used for MoCA 2.0.
Per channel list of average received Signal to Noise Ratio (SNR) in dB. If the MoCA Node identified by {{param|RxNodeIndex}} is not equal to {{param|#.NodeID}} or the MoCA Node identified by {{param|TxNodeIndex}} is equal to {{param|#.NodeID}}, then this parameter is not present. Otherwise indicates the average received SNR across all the available carriers based on the EVM probe from the MoCA Node identified by {{param|TxNodeIndex}}.
The field ''numValues'' is a function of {{param|LinkType}}:
* {{enum|moca1PHY|LinkType}} - 1
* {{enum|primary|LinkType}} - 1
* {{enum|bonded|LinkType}} - 2
struct mocaRxSNR {
char numValues; // 1 octet (Number of Values to follow)
{
char rx_snr; // 1 octet (Rx SNR in dB)
} [numValues];
};
This parameter is only used for MoCA 2.0.
MoCA bridge Ethernet MAC address table. This table contains an entry for every MoCA Node in the MoCA network.
Entries in this table cannot be created or deleted by the network management system. All entries are created or deleted by the device software.
The Node ID is used as an index to order the MAC entries in the MoCA bridge table.
The Ethernet MAC addresses identified by the Node ID.
MoCA mesh Subcarrier Modulation table. This table contains the Unicast transmit subcarrier modulation between all pairs of MoCA Nodes in the MoCA network.
Since {{param|Mod}} is the subcarrier modulation from {{param|TxNodeIndex}} to {{param|RxNodeIndex}}, this table does not contain any entries with {{param|TxNodeIndex}} equals {{param|RxNodeIndex}}. In addition, a MoCA network can have less than 16 MoCA Nodes, hence some values of {{param|TxNodeIndex}} and {{param|RxNodeIndex}} in the range of 0 to 15 may not exist. The {{param|ChannelIndex}} index is used to differentiate between the primary and secondary channels in a bonded channel network. The primary channel index is always present, the secondary channel index may not always be present.
Entries in this table cannot be created or deleted by the network management system. All entries are created or deleted by the device software.
The Node ID of the transmit MoCA Node is used as one of the index to order the mesh PHY rate table.
The Node ID of the receive MoCA Node is used as one of the index to order the mesh subcarrier modulation.
{{enum|primary}} or {{enum|secondary}} channel for MoCA 2.0 Node associated with {{param|Nper}} and {{param|Vlper}}. For MoCA 1 Node, the same as the {{enum|primary}} channel associated with {{param|Mod}}. In a bonded MoCA 2.0 network, the {{enum|primary}} and {{enum|secondary}} channels each have their own subcarrier modulation data.
{{enum|m25first}}, {{enum|m25second}}, {{enum|m25third}}, {{enum|m25fourth}} or {{enum|m25fifth}} channel for MoCA 2.5 Node associated with {{param|ModM25}}.
1 Byte Hex array values with no delimiters where each byte indicates the subcarrier modulation of one subcarrier from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}} for the MoCA 1 Unicast transmission PHY profile.
1 Byte Hex array values with no delimiters where each byte indicates the unicast NPER subcarrier modulation of one subcarrier from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}} for the associated {{param|ChannelIndex}}.
1 Byte Hex array values with no delimiters where each byte indicates the unicast VLPER subcarrier modulation of one subcarrier from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}} for the associated {{param|ChannelIndex}}.
1 Byte Hex array values with no delimiters where each byte indicates the MoCA 2.5 unicast subcarrier modulation for all subcarriers from the MoCA Node identified by {{param|TxNodeIndex}} to the MoCA Node identified by {{param|RxNodeIndex}} for the associated {{param|ChannelIndex}}.
For MoCA 2.5 First Channel, Second Channel, Third Channel, Fourth Channel and Fifth Channel, the total number of subcarriers is 512.
Parameters to monitor the status of the MoCA interface.
Parameters to monitor the packet statistics and the number of flows in the MoCA interface.
Parameters to monitor the PQoS flow information of the MoCA interface.
Parameters to monitor the status of other MoCA Nodes in the MoCA network.
Parameters to monitor the PHY rate of each link in the MoCA network.
Parameters to configure the MAC address access control list for the MoCA interface.
Parameters to configure RLAPM (Receive Level Added PHY Margin) for the MoCA interface.
Parameters to configure SAPM (Subcarrier Added PHY Margin) for the MoCA interface.
Parameters to control Moca Reset for the MoCA interface.
Parameters to monitor the bandwidth of the MoCA interface.
Parameters to monitor the packet drop statistics of the MoCA interface.
Parameters to monitor the PQoS flow statistics of the MoCA interface.
Parameter to monitor the packet drop statistics per link of the MoCA interface.
Parameters to monitor Power Level to or from MoCA Nodes in the MoCA network.
Parameters to monitor the MoCA bridge table of each MoCA Node in the MoCA network.