Automation

 View Only
Expand all | Collapse all

Cannot define NetworkConnectionSection in OVF file descriptor

  • 1.  Cannot define NetworkConnectionSection in OVF file descriptor

    Posted 26 days ago
      |   view attached

    Hi,

    I'm having trouble defining NetworkConnectionSection section for my VMs inside a vApp template.

    I guess I'm not sure where to exactly put or define this section within my OVF descriptor. My end goal is to set all Network Connections to "none" because I'm trying to deploy a VM directly from a template to an existing vApp but I encountered the same issue as in this ticket:

    https://community.broadcom.com/vmware-cloud-foundation/discussion/new-civm-throws-unknown-ip-addressing-mode-manual-connected-to-network-none

    I've tried adding it in different places but either the validation fails, or there is no effect once the template is deployed, and the connection type still says "DHCP" instead "NONE".

    Please find attached my general OVF structrure without NetworkConnectionSection.

    Thanks.

    Attachment(s)

    xml
    template_OVF.xml   25 KB 1 version


  • 2.  RE: Cannot define NetworkConnectionSection in OVF file descriptor

    Posted 25 days ago

    Partial solution:

                    <ovf:Item>
                        <rasd:AddressOnParent>10</rasd:AddressOnParent>
                        <rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>
                        <rasd:Connection vcloud:ipAddressingMode="NONE">network_nam</rasd:Connection>
                        <rasd:Description>VMXNET3 ethernet adapter</rasd:Description>
                        <rasd:ElementName>Network adapter 4</rasd:ElementName>
                        <rasd:InstanceID>15</rasd:InstanceID>
                        <rasd:ResourceSubType>VMXNET3</rasd:ResourceSubType>
                        <rasd:ResourceType>10</rasd:ResourceType>
                        <vmw:Config ovf:required="false" vmw:key="wakeOnLanEnabled" vmw:value="true" />
                    </ovf:Item>

    The original issue from ticket mentioned above yet remains. While deploying a VM from a vApp template, it's entire network configuration information is wiped clean except for the ip addressing mode. Which leads to an error caused by trying to connect a DHCP connection to a "none" network, since the original network from the template is wiped.

    Still no solution for this tho.