Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [ ] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [ ] We need to add a new document to an existing section

3. - [ ] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/clusters/cluster_mce_overview#on-prem-creating-your-cluster-with-the-cli-nmstateconfig

4. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.

Description: Addition of nmstate config examples while creating cluster using ACM with nmstate config, bond configuration using DHCP:true. Consider the below issue.

Issue:  While installing for customer, the infra env did not register the node with the below error:

* at least one interface for host 0 must be provided * mac-interface mapping for interface lacp-0 is missing and not a physical interface

As a resolution we suggested to add the mac address in the nmstate configuration.

Source: $ oc explain nmstateconfig.spec.interfaces

The api explanation for nmstate shows as below:

Interfaces is an array of interface objects containing the name and MAC address for interfaces that are referenced in the raw nmstate config YAML. Interfaces listed here will be automatically renamed in the nmstate config YAML to match the real device name that is observed to have the corresponding MAC address. At least one interface must be listed so that it can be used to identify the correct host, which is done by matching any MAC address in this list to any MAC address observed on the host.

Would be good to have few examples which are satisfying the following requirement.