[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for URL.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for ParameterName.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Name, or with a given value for Alias.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Location, or with a given value for Alias.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias.

Status of the firmware image, as determined by the Agent. Enumeration of:

• NoImage (This Firmware Image instance is empty. This value could happen on an Agent that supports multiple firmware images, but only has a single image installed)
• Active (This Firmware Image instance is the currently active image, added in 2.14)
• Downloading (This Firmware Image instance is being downloaded)
• Validating (This Firmware Image instance has been downloaded, and is in the process of being validated)
• Available (This Firmware Image instance has been downloaded, validated, and installed, and is ready to be activated)
• DownloadFailed (The Agent has attempted to download this Firmware Image instance, but ultimately failed while retrieving it from the source URL)
• ValidationFailed (The Agent has attempted to validate a Firmware Image downloaded to this instance, but ultimately failed while validating it)
• InstallationFailed (The Agent has attempted to install a Firmware Image downloaded and validated to this instance, but ultimately failed while installing it)
• ActivationFailed (The Agent has attempted to activate this Firmware Image instance, but ultimately the activation failed)

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for URL, or with a given value for Alias, or with a given value for UUID.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

Position of the |object| entry in the order of precedence. A valueof 1 indicates the first entry considered (highest precedence).[[Order] Position of the HTTPAccess entry in the order of precedence. A value of 1 indicates the first entry to be considered (highest precedence).

When a HTTPAccess instance is created, or when an existing Order value is modified, if the value matches that of an existing entry, the Order values for the existing entry and all lower Order entries are incremented (lowered in precedence) to ensure uniqueness of this value. A deletion causes Order values to be compacted. When a value is changed, incrementing occurs before compaction.

If no Order value is supplied on creation of a HTTPAccess instance, it MUST be assigned a value that is one more than the largest current value (lowest precedence).

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries.]For each incoming connection, the highest ordered entry that matches the Host: HTTP header and path prefix is applied. All lower Order entries are ignored. When this value is set, if the value matchesthat of an existing entry, the |param| value for the existing entryand all lower |param| entries is incremented (lowered inprecedence) to ensure uniqueness of this value.|div||classes||A deletion causes |param| values to be compacted. When a value ischanged, incrementing occurs before compaction.|

The value MUST be the Path Name of a table row.

The IP or Logical Interface associated with the HTTPAccess entry. Example:

• Device.IP.Interface.1.||div||classes||Device.IP.Interface.1* Device.Logical.Interface.1.Device.Logical.Interface.1

If the value is an empty string, the CPE MUST use its routing policy (IP Forwarding table entries), if necessary, to determine the appropriate interface.

The value MUST be the Path Name of a row in the Users.User. table. If the referenced object is deleted, the parameter value MUST be set to an empty string.

The user to whom the session belongs. When the user is unknown an empty string string SHOULD be used.[

Note: This parameter was demoted to readOnly in the Device:2.17 version.]

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with the same values for both HigherLayer and LowerLayer, or with a given value for Alias.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name, or with a given value for GroupID.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Channel.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for APN, or with a given value for Interface.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias, or with a given value for Name. On creation of a new table entry, the Agent MUST choose initial values for Alias and Name such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] [docsIfDownstreamChannelTable/1.3.6.1.2.1.10.127.1.1.1.1] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias.

[Alias] [docsIfUpstreamChannelTable/1.3.6.1.2.1.10.127.1.1.2.1] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias, or with a given value for Name. On creation of a new table entry, the Agent MUST choose initial values for Alias and Name such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias, or with a given value for Name. On creation of a new table entry, the Agent MUST choose initial values for Alias and Name such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for MACAddress.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias, or with a given value for Name. On creation of a new table entry, the Agent MUST choose initial values for Alias and Name such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with the same values for all of Interface, VLANID and Queue.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias, or with a given value for Name. On creation of a new table entry, the Agent MUST choose initial values for Alias and Name such that the new entry does not conflict with any existing entries. At most one enabled entry in this table can exist with a given value for MACAddress.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Name, or with a given value for Alias.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table (regardless of whether or not it is enabled) can exist with a given value for Alias. On creation of a new table entry, the Agent MUST choose an initial value for Alias such that the new entry does not conflict with any existing entries.

The Agent MUST choose an initial value that doesn’t conflict with any existing entries.

[mocaIfEnable/1.3.6.1.4.1.31621.1.2.1.1.1.1] Enables or disables the interface.

This parameter is based on ifAdminStatus from [RFC2863].

The factory default value MUST be true.

[mocaIfStatus/1.3.6.1.4.1.31621.1.2.1.7.1.1] The current operational state of the interface (see [Section 4.2.2/TR-181i2]). Enumeration of:

• Up
• Down
• Unknown
• Dormant
• NotPresent
• LowerLayerDown
• Error (OPTIONAL)

When Enable is false then Status SHOULD normally be Down (or NotPresent or Error if there is a fault condition on the interface).

When Enable is changed to true then Status SHOULD change to Up if and only if the interface is able to transmit and receive network traffic; it SHOULD change to Dormant if and only if the interface is operable but is waiting for external actions before it can transmit and receive network traffic (and subsequently change to Up if still operable when the expected actions have completed); it SHOULD change to LowerLayerDown if and only if the interface is prevented from entering the Up state because one or more of the interfaces beneath it is down; it SHOULD remain in the Error state if there is an error or other fault condition detected on the interface; it SHOULD remain in the NotPresent state if the interface has missing (typically hardware) components; it SHOULD change to Unknown if the state of the interface can not be determined for some reason.

This parameter is based on ifOperStatus from [RFC2863].

[Alias] A non-volatile handle used to reference this instance. Alias provides a mechanism for an ACS to label this instance for future reference.

If the CPE supports the Alias-based Addressing feature as defined in [Section 3.6.1/TR-069] and described in [Appendix II/TR-069], the following mandatory constraints MUST be enforced:

• Its value MUST NOT be empty.
• Its value MUST start with a letter.
• If its value is not assigned by the ACS, it MUST start with a “cpe-” prefix.
• The CPE MUST NOT change the parameter value.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

[mocaIfMacAddress/1.3.6.1.4.1.31621.1.2.1.7.1.6] [MACAddress] 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 Ethernet.Link.{i}.MACAddress parameter.

[mocaIfSoftwareVersion/1.3.6.1.4.1.31621.1.2.1.7.1.3] This interface’s firmware version.

This parameter is based on mocaIfSoftwareVersion from [MOCA11-MIB].

The maximum MoCA PHY bit rate (expressed in Mbps).[

This parameter MUST NOT be implemented for MoCA 2.0 because it doesn’t map to a MIB object.]

[mocaIfMaxIngressNodeThroughput/1.3.6.1.4.1.31621.1.2.1.7.1.18] [MocaMacRate]

The maximum bandwidth of this interface for flows onto the MoCA network in |units|.network.

This parameter is based on mocaIfMaxIngressNodeBw from [MOCA11-MIB].

[mocaIfMaxEgressNodeThroughput/1.3.6.1.4.1.31621.1.2.1.7.1.19] [MocaMacRate]

The maximum bandwidth of this interface for flows from the MoCA network in |units|.network.

This parameter is based on mocaIfMaxEgressNodeBw from [MOCA11-MIB].

[mocaIfNetworkVersion/1.3.6.1.4.1.31621.1.2.1.7.1.5] 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. Possible patterns:

• *\d+(.\d+)**

This parameter is based on mocaIfNetworkVersion from [MOCA11-MIB].

[mocaIfNC/1.3.6.1.4.1.31621.1.2.1.7.1.10] [MocaNodeID] The Node ID of the current Network Coordinator (NC) for the MoCA network.

This parameter is based on mocaIfNC from [MOCA11-MIB].

[mocaIfNodeID/1.3.6.1.4.1.31621.1.2.1.7.1.7] [MocaNodeID] The Node ID of this interface.

This parameter is based on mocaIfNodeID from [MOCA11-MIB].

The maximum network node capability supported by the interface. If MaxNodes is true then the interface supports 16 nodes (the maximum for a MoCA 1.1 network). If MaxNodes 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.]

[mocaIfPreferredNC/1.3.6.1.4.1.31621.1.2.1.1.1.9] Whether this interface is a preferred Network Coordinator (NC).

This parameter is based on mocaIfPreferredNC from [MOCA11-MIB].

The factory default value MUST be false.

[mocaIfBackupNC/1.3.6.1.4.1.31621.1.2.1.7.1.11] [MocaNodeID] The Node ID of the backup Network Coordinator node.

This parameter is based on mocaIfBackupNC from [MOCA11-MIB].

[mocaIfPrivacyEnable/1.3.6.1.4.1.31621.1.2.1.1.1.7]

The configured privacy mode. This indicates whether link-layer security is enabled (true) or disabled (false) for network admission.|div||classes||The configured privacy setting MAY NOT match the current operationalstate (|param|PrivacyEnabled|), since this setting is only appliedduring network formation or admission.|

The factory default value MUST be false.

[mocaIfChannelSupport/1.3.6.1.4.1.31621.1.2.1.7.1.22]

HexadecimalThe encoded 64-bit mask of supported frequencies. This is thebit map of the spectrumfrequencies that the interface supports, and each bitsupports. represents 25 MHz of spectrum. The least significant bit of therightmost character corresponds to 800MHz, which is the lowestfrequency.[[MocaChannelMask] 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 HighestVersion parameter.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.]|div||classes||For example, an interface that supports 1150 MHz through 1500 MHzwould have a value of 0x000000001FFFC000.||div||classes||This parameter is based on mocaIfCapabilityMask from|bibref|MOCA11-MIB|.|

[mocaIfChannelMask/1.3.6.1.4.1.31621.1.2.1.1.1.2]

The configured hexadecimal encoded 64-bit mask of enabled frequencies that the interface supports for network admission.

[MocaChannelMask] 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 HighestVersion parameter.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.

The configured frequencies MAYmight NOTnot match the current operational state (FreqCurrentMask), since this setting is only applied during network formation or admission.

[mocaIfChannelSupport/1.3.6.1.4.1.31621.1.2.1.7.1.22]

HexadecimalThe encoded 64-bit mask of used frequencies. This is the bitmap of the spectrumfrequencies that can be usedused. andThis is a subset of the FreqCapabilityMask. Each bit represents 25 MHz of spectrum.The least significant bit of the rightmost character corresponds to800MHz, which is the lowest frequency.frequencies.

This parameter is based on mocaIfChannelMask from|bibref|MOCA11-MIB|.[[MocaChannelMask] 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 HighestVersion parameter.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.]

[mocaIfRFChannel/1.3.6.1.4.1.31621.1.2.1.7.1.12] Current Operational Frequency. The RF frequency in Hz to which the MoCA interface is currently tuned. This parameter is only valid when Status is Up.

This parameter is based on mocaIfRFChannel from [MOCA11-MIB].

[mocaIfLof/1.3.6.1.4.1.31621.1.2.1.1.1.18]

Last Operational Frequency. The RF frequency in Hz to which the MoCA interface was tuned when last in the Up state.

This parameter is based on mocaIfLOF from [MOCA11-MIB].[

(LOF Managed Parameter)

This parameter is writable only for MoCA 2.0.]

[mocaIfPassword/1.3.6.1.4.1.31621.1.2.1.1.1.8] MoCA Password. The value consists of numeric characters (0-9). Possible patterns:

• \d+

This parameter is based on mocaIfPassword from [MOCA11-MIB].

When read, this parameter returns an empty string, regardless of the actual value.

[mocaIfTxPowerLimit/1.3.6.1.4.1.31621.1.2.1.1.1.4] [MocaDB]

TransmitThe Power attenuationvalue in dB relativeby which to reduce the transmit power of the node from its maximum transmit power.{{replaced: unexpected argument [replaced(The, Status), ‘, which means the interface is not part of a MoCA network. If changed, the parameter may not take effect until the’] after: ||div||classes|, [’ The transmit power SHALL only be changed when ’, param(Status), ’ is not ’, enum(Up)]}} MoCA interface SHOULD have |param|Enable| set to |false| forany change in this configuration. If the parameter is modified when|param|Enable| is |true| then this change might take severalminutes to complete.restarted.

This parameter is based on mocaIfTxPowerLimit from [MOCA11-MIB].

The factory default value MUST be 0.

[mocaIfPowerControlTargetRate/1.3.6.1.4.1.31621.1.2.1.1.1.6] [MocaPhyRate] Target PHY rate in Mbps for the power control algorithm.

The MoCA interface SHOULD have Enable set to false for any change in this configuration. If the parameter is modified when Enable is true then this change might take several minutes to complete.

This parameter is based on mocaIfPowerControlTargetRate from [MOCA11-MIB].

The factory default value MUST be 630.

[mocaIfTabooChannelMask/1.3.6.1.4.1.31621.1.2.1.7.1.13]

Hexadecimal encoded 64-bit mask ofThe MoCA taboo channels identified for the home network. This is the bit map of the spectrum that theinterface supports, and each bit represents 25 MHz of spectrum. Theleast significant bit of the rightmost character corresponds to800MHz, which is the lowest frequency.

This parameter is based on mocaIfTabooChannelMask from|bibref|MOCA11-MIB|.[[MocaChannelMask] 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 HighestVersion parameter.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.]

[mocaIfNodeTabooChannelMask/1.3.6.1.4.1.31621.1.2.1.7.1.14]

Hexadecimal encoded 64-bit mask of supported frequencies. This is thebit map of the spectrum that the interface supports, and each bitrepresents 25 MHz of spectrum. The leastMoCA significanttaboo bitchannels ofidentified therightmostfor characterthis corresponds to 800MHz, which is the lowestfrequency.device.

This parameter is based on mocaIfNodeTabooChannelMask from|bibref|MOCA11-MIB|.[[MocaChannelMask] 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 HighestVersion parameter.

At most one entry in this table can exist with a given value for Alias, or with a given value for Name.]

[mocaIfTxGcdRate/1.3.6.1.4.1.31621.1.2.1.7.1.20] [MocaPhyRate]

The broadcast PHY transmit rate in |units| for this interface.

This parameter is based on mocaIfTxGcdRate from [MOCA11-MIB].

[mocaIfTxGcdPowerReduction/1.3.6.1.4.1.31621.1.2.1.7.1.16] [MocaDB]

Transmit Power attenuation in |units| relative to the maximum transmit power for broadcast transmissions.

This parameter is based on mocaIfTxGcdPowerReduction from [MOCA11-MIB].

Whether this interface supports the 256 QAM feature.

This parameter is based on mocaIfQAM256Capable from [MOCA11-MIB].[

This parameter MUST NOT be implemented for MoCA 2.0 because it doesn’t map to a MIB object.]

[mocaIfPduNumber/1.3.6.1.4.1.31621.1.2.1.7.1.17]

The packet aggregation capability supported by the interface. Standard values are 0 (no support), 6 (6 packets) or 10 (10 packets).

This parameter is based on mocaIfPacketsAggrCapability from [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.]]