How exactly does the node type="ASSET" work?

Document created by cdnadmin on Jan 25, 2014
Version 1Show Document
  • View in full screen mode
This document was generated from CDN thread

Created by: Jacoby Thwaites on 04-11-2013 06:07:04 AM
I am trying to decipher exactly how the VIRL node type="ASSET" is designed to be used in the all-in-one VM when designing test network topologies.

Take this tiny example in (say) foo.virl:
-----------------------------------------------------------
<node name="eth0" type="ASSET"/>

<node name="NDE1" type="SIMPLE" subtype="vios">
  <interface name="GigabitEthernet0/0"/>
</node>

<connection dst="/topology/node[1]" src="/topology/node[2]/interface[1]"/>
-----------------------------------------------------------
When I do a "vmcloud -netcreate foo.virl foo" to start this topology, I notice that the eth0 adapter in the all-in-one VM loses its IP address, and a new adapter vb_ex_eth0 is created, taking the original eth0 IP address. In my case, that eth0 is defined as a host-only adapter on the all-in-one VM virtualbox config.

The NDE user guide mutters something about interfaces in the virtual network being bridged out through this eth0 adapter, at which point I'm a bit lost...

For example, I can't ping the IP address 192.168.56.10 which is configured on the NDE1 node "/topology/node[2]/interface[1]" from my host Mac, when the vboxnet adapter on the Mac has address 192.168.56.1.

I *can* ping that NDE1 node interface from inside the all-in-one VM, however.

Can anyone help me understand how this should be used?

Subject: RE: How exactly does the node type="ASSET" work?
Replied by: Jacoby Thwaites on 04-11-2013 08:41:58 AM
Thanks Geevarghese

I'm really after an explanation of exactly how the node="ASSET" works, and what it does when a topology using it is started. That might help me understand the use case which I feel I am failing to understand.

I can already reach vios nodes within the topology from my host Mac thru the routable lan(s) defined in vmcloudrc, by adding suitable "route add" commands in the router.con files etc.

Subject: RE: How exactly does the node type="ASSET" work?
Replied by: Geevarghese Cheria on 04-11-2013 08:28:27 AM
Hi Jacoby
  Please confirm that your default route is not out of eth1. You need to be using eth0 for access to the VM.  The eth1 interface is private to the VM host (Fusion).
Thanks and Regards,
Geevarghese

Subject: RE: How exactly does the node type="ASSET" work?
Replied by: Joseph Clarke on 09-11-2013 12:48:18 PM
An ASSET is used for a connection to a physical device (or asset).  The
idea is that you specify a local Linux interface to which your physical
asset is connected.  For example, if you have a 3560 switch connected to
eth1 on your Linux machine, you can add an asset for eth1.

I haven't really used ASSETs when I create custom topologies.  I am always
happy to do the routing as you have described to be able to access my
vIOS instances from my Mac.  I'm attaching a sample 2node chain topology
I use to test things where I need a bit of routing between my VM and a
remote device.

Subject: RE: How exactly does the node type="ASSET" work?
Replied by: Jacoby Thwaites on 09-11-2013 04:31:01 PM
Many thanks Joseph that is what I needed to know. The sample config is also useful.

I notice you use ospf in those router.con files, where I have been using manual routes.

Can you point me to a reference for the configuration commands supported in the router config files?

Subject: RE: How exactly does the node type="ASSET" work?
Replied by: Joseph Clarke on 09-11-2013 04:37:43 PM
These are real IOS images.  They are running the adventerprise feature set.  So think of these as virtual ISRG2s running that feature set.  The moral of the story is that you're not very limited in terms of features.

Outcomes