Creating second network adapter causes issues

[pgaltieri]

I booted up the CML 2.0 ova and created a second host only adapter configured as 172.16.2.133.  I was able to ping other VMs on that network.  When I rebooted the VM the CML UI showed that it was accessible via 172.16.2.133 and not 172.16.192.133 which is what it showed for the web console.  Even after deleting the second adapter this VM was hopelessly messed up.  Any attempt to get a license showed either "Out of Compliance," "Signature authorization failed," or it couldn't reach the server at all.  When I booted up a new CML 2.0 VM everything started to work.  Is it possible to create additional network adapters on the VM and configure them as host only?

Paolo

[balaji.bandi]

yes you can add as mentioned in the document :

https://www.cisco.com/c/en/us/td/docs/cloud_services/cisco_modeling_labs/v200/admin/guide/b_cml_admin_guide_2-0/m_networking.html

[pgaltieri]

Balaji,
 thank you for the pointer, but it's not what I was looking for. What I
want is to configure the second adapter as a host only adapter so I can
communicate between my other VMs that are on the 172.16.2.x network. 
The information you pointed me to shows how to setup a second interface
to the host, the first bridged the second NAT.  In my configuration the
first adapter can't be in bridged mode because there is no one to assign
an address so I have to put it NAT mode so it gets it's address from
VMware's dhcp server running on that interface.  I can setup the second
adapter as host-only, but it causes problems.

Thank's
Paolo

[balaji.bandi]

That is the only example you to understand- you can create 1 as the Host adaptor does not configure any Gateway. or you can add a static route for that subnet. (in general, any VM should work as expected) - let me test on CML2.0 later tonight.