@joeunta wrote:

Hi All,
I'm trying to use and configure Ostinato on my simulation but not having much success connecting to the lxc via the GUI.

I Log in via ssh into the Osintato lxc but find no drone process running. Netstat doesn't state that port 7878 is open and being listened to either.

I have found 2 instances of drone and the /lxc/usr/bin/drone is the only one I can get to work.

When I start up ostinato its like the local drone connects to all the ports on the VM (127.0.0.1:7878 - 117 connections). When I go to connect the gui to the LXC is stating its already taken. I have tried closing the local copy of drone but this crashes the gui also.

I have followed the video instruction on the Cisco VIRL youtube channel but no luck.

I have tired with and without the auto config generation.

Have I missed something with the config of the Ostinato lxc?

Any thoughts would be great
Cheers

Posts: 1

Participants: 1

Read full topic

@aadsfljasdfljasdfasd wrote:

virl only creates an interface if it is connected to something. For testing purpose I would like to have some extra ports with config on it but does not need to come up. So how can I have more ports on the node without wasting adding extra nodes?
I understand that I can add some nodes but do not start them with the simulation, but still adding extra ports should be made easier.

Posts: 5

Participants: 2

Read full topic

@aadsfljasdfljasdfasd wrote:

When I stopped the simulation, there was a checkbox to automatically close all telnet sessions. Doesn't it include console sessions?

Posts: 1

Participants: 1

Read full topic

@aadsfljasdfljasdfasd wrote:

Duplicate connection from node "iosvl2-5" to network(s) "unmanagedswitch-1": problem of VIRL file at line 643.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1475, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1461, in dispatch_request
return self.view_functionsrule.endpoint
File "", line 2, in simengine_launch
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/std/implementation.py", line 267, in middleware
File "", line 2, in simengine_launch
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/common/utils.py", line 90, in measurer
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/std/implementation.py", line 1171, in simengine_launch
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/std/management.py", line 1511, in add
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/std/management.py", line 2210, in _create
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/server/model.py", line 49, in session_scope
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/std/management.py", line 2210, in _create
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/std/management.py", line 2197, in _create
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/low_level/implementation.py", line 896, in add
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/low_level/implementation.py", line 1186, in _create
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/low_level/implementation.py", line 6661, in topology
File "/home/jenkins/jenkins/jobs/VIRL_CORE_build/workspace/test-virl-repo/virl/topology/__init__.py", line 395, in init
ParserException: Duplicate connection from node "iosvl2-5" to network(s) "unmanagedswitch-1": problem of VIRL file at line 643.

Is this a bug? I want 2 connections from a node to an unmanaged switch.

Posts: 1

Participants: 1

Read full topic

@aadsfljasdfljasdfasd wrote:

Current ios release should automatically create the vlan if it does not exist already, is this a bug in iosvl2?

Posts: 1

Participants: 1

Read full topic

@iamjeffvader wrote:

I have two licences, a 20 and a 30, on my mac and bare metal respectively. I dont use the mac one much so I might just move it to the server. Any issues with running them both off the server at the same time? Specifically thinking about the 172.16.x.0 subnets. Presume I will need to hard code if addressing.
The only other topic I found on this suggests a potential issue with autonetkit. I dont really use that so no problem there.

Can I merge the licences in to one?

Posts: 1

Participants: 1

Read full topic

@Keegs wrote:

Hi, please could someone help with showing me how to setup default gateways for different Lxc-iperf nodes eg...
Lxc-iperf 1: IP 10.0.10.10/24 GW: 10.0.10.1/24
Lxc-iperf 2: IP 10.0.20.10/24 GW: 10.0.20.1/24
Etc...

Posts: 2

Participants: 2

Read full topic

@leszcs wrote:

I had a simulation in the stopping state, and someone rebooted the server in the middle of the stop. I have 1 node that wont stop now (stuck in deleting). I've tried stoping the simulation from VM maestro, and UXadmin. I tried deleting the node in uxadmin, and have tried the nova command line. I also can't start other simulations now as well. Any help is appreciated. Thanks!

Posts: 1

Participants: 1

Read full topic

@jherbert wrote:

Screen Shot 2016-02-22 at 3.43.43 PM.png632x684 56.9 KB

Need help figuring out why my services will not connect. All seems fine on VIRL server.

Posts: 2

Participants: 2

Read full topic

@beyond-1 wrote:

Have downloaded the latest xrv9000 image and imported it, once I fire the node up though and its finished booting it doesnt appear to have any interfaces. Presumably im missing something obvious?

Posts: 1

Participants: 1

Read full topic

@aadsfljasdfljasdfasd wrote:

Same problem as reported here
https://supportforums.cisco.com/discussion/12920581/different-ports-show-vlan-and-show-vlan-id

(vios_l2-ADVENTERPRISEK9-M), Version 15.2(4.0.55)E

Posts: 1

Participants: 1

Read full topic

@crosson wrote:

Did some forum searching and couldn't find the answer to this. In case anyone was wondering if you ever wanted your server nodes to have an assigned IP prior to launching a simulation then add these lines at the bottom of your ANK config.

runcmd:
- ip route del default
- sudo /sbin/dhclient eth1 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhclient/dhclient.eth1.lease

This deletes the nodes default route learned from the OOB allowing your node to learn an alternate default via your lab's DHCP server. This assumes you are running a dhcp server in your simulation. Or statically assign the ip like so.

runcmd:
- ifconfig eth1 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255
- route add default gw 192.168.0.1

Posts: 2

Participants: 2

Read full topic

@quevedolopezmateo wrote:

Hi,

I can't start ASAv or IOSvL2 nodes the error output,

(ERROR) [Feb/23/2016 15:18:04] Node "asav-1" state changed from ABSENT to ERROR with message: No valid host was found. Exceeded max scheduling attempts 3 for instance afac9511-eb92-4ef2-8abc-79ee1061c3e9. Last exception: [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2248, in _do: File "/usr/lib/python2.7/dist-packages/nova/conductor/manager.py", line 669, in build_instances

(ERROR) [Feb/23/2016 15:18:28] Node "iosvl2-1" state changed from ABSENT to ERROR with message: No valid host was found. Exceeded max scheduling attempts 3 for instance a113ca92-672e-471e-b026-5412ed580918. Last exception: [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2248, in _do: File "/usr/lib/python2.7/dist-packages/nova/conductor/manager.py", line 669, in build_instances

I've run this commands and those are the ouputs,

virl@virl:~$ nova service-list
+----+------------------+------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+----+------------------+------+----------+---------+-------+----------------------------+-----------------+
| 1 | nova-scheduler | virl | internal | enabled | up | 2016-02-23T15:09:11.000000 | - |
| 2 | nova-cert | virl | internal | enabled | up | 2016-02-23T15:09:12.000000 | - |
| 3 | nova-consoleauth | virl | internal | enabled | up | 2016-02-23T15:09:12.000000 | - |
| 4 | nova-conductor | virl | internal | enabled | up | 2016-02-23T15:09:11.000000 | - |
| 5 | nova-compute | virl | nova | enabled | up | 2016-02-23T15:09:04.000000 | - |
+----+------------------+------+----------+---------+-------+----------------------------+-----------------+
virl@virl:~$ neutron agent-list
+--------------------------------------+--------------------+------+-------+----------------+---------------------------+
| id | agent_type | host | alive | admin_state_up | binary |
+--------------------------------------+--------------------+------+-------+----------------+---------------------------+
| 24905ad8-cf00-4183-8587-2147b4e65d01 | Metadata agent | virl | | True | neutron-metadata-agent |
| 5d2fc58b-380f-4f84-93c0-62067695694c | L3 agent | virl | | True | neutron-l3-agent |
| 6b22f808-7ecf-4ed5-89a8-bff3a727e9ba | Linux bridge agent | virl | | True | neutron-linuxbridge-agent |
| e39ad06b-990f-43dd-af0e-fc73f60d65e7 | DHCP agent | virl | | True | neutron-dhcp-agent |
+--------------------------------------+--------------------+------+-------+----------------+---------------------------+

Thanks advanced.

virl_health_status_192.168.2.120_2016-02-23.txt (13.3 KB)

Posts: 1

Participants: 1

Read full topic

@Ippy98 wrote:

This happens everytime I try to run the 1000v image. I have updated it to the latest version but it did it in previous versions too.
After the it boots up, the interfaces appear to come up as normal, but then the log spits out a PHY register error for every interface, and they no longer communicate
Logs below. (Yes the other interface is up and configured)

Router#sho int g6
GigabitEthernet6 is up, line protocol is up
Hardware is CSR vNIC, address is 0000.ab7c.6c05 (bia 0000.ab7c.6c05)
Internet address is 63.45.67.90/30

Router#ping 63.45.67.89
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 63.45.67.89, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router#sho ip arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 63.45.67.89 0 Incomplete ARPA
Internet 63.45.67.90 - 0000.ab7c.6c05 ARPA GigabitEthernet6

Router#sho ip route 63.45.67.89
Routing entry for 63.45.67.88/30
Known via "connected", distance 0, metric 0 (connected, via interface)
Routing Descriptor Blocks:
* directly connected, via GigabitEthernet6

*Feb 23 18:04:06.657: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up
*Feb 23 18:04:06.681: %LINEPROTO-5-UPDOWN: Line protocol on Interface LI-Null0, changed state to up
*Feb 23 18:04:06.689: %LINK-3-UPDOWN: Interface LIIN0, changed state to up
*Feb 23 18:04:06.695: %LINK-3-UPDOWN: Interface GigabitEthernet1, changed state to down
*Feb 23 18:04:17.243: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to down
*Feb 23 18:04:19.324: %LINK-3-UPDOWN: Interface GigabitEthernet3, changed state to down
*Feb 23 18:04:19.349: %LINK-3-UPDOWN: Interface GigabitEthernet4, changed state to down
*Feb 23 18:04:19.454: %LINK-3-UPDOWN: Interface GigabitEthernet5, changed state to down
*Feb 23 18:04:19.498: %LINK-3-UPDOWN: Interface GigabitEthernet6, changed state to down
*Feb 23 18:04:19.634: %LINK-3-UPDOWN: Interface GigabitEthernet7, changed state to down
*Feb 23 18:04:20.733: %LINK-3-UPDOWN: Interface GigabitEthernet8, changed state to down
*Feb 23 18:04:20.980: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up
*Feb 23 18:04:20.981: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up
*Feb 23 18:04:20.982: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up
*Feb 23 18:04:20.983: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to up
*Feb 23 18:04:20.984: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to up
*Feb 23 18:04:20.985: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to up
*Feb 23 18:04:20.986: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4, changed state to up
*Feb 23 18:04:20.986: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet5, changed state to up
*Feb 23 18:04:20.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet6, changed state to up
*Feb 23 18:04:21.078: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7, changed state to up
*Feb 23 18:04:21.767: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet8, changed state to up
*Feb 23 18:02:28.978: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi1: e1000_phy_read_status: Error reading PHY register
*Feb 23 17:55:12.619: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:55:22.611: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:55:32.639: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:55:42.679: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:55:52.705: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:56:02.752: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:56:12.779: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:56:22.827: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:56:32.842: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:56:34.845: %CPPDRV-4-CPU_FEATURE: F0: cpp_driver-0: CPP0: CPU lacks feature (AES HW-Assist (AES-NI)). Performance may be sub-optimal.
*Feb 23 17:56:42.917: %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED: F0: cmand: Reloading F0 because it has failed to become ready for packet processing
*Feb 23 17:57:08.069: %EVENTLIB-3-RUNHOG: F0: fman_fp_image: undefined: 4315ms, Traceback=1#a86a3ae97c0d1784897e003fd5b0d5d4 evlib:7F49DCA46000+B242 evlib:7F49DCA46000+93B4 cpp_common_os:7F49D8F5E000+17099 evlib:7F49DCA46000+BB8F evlib:7F49DCA46000+E200 :400000+550D4E c:7F49C89FF000+1E514 :400000+1AA9A9
*Feb 23 17:57:08.139: %EVENTLIB-3-HISTSUMM: F0: fman_fp_image: dispatch start: 994611ms elapsed time: 21258ms detected hog: 1 set count: 1
*Feb 23 17:57:08.158: %EVENTLIB-3-HISTELEM: F0: fman_fp_image: elem[1] event: Unset -> HOG set: 994614ms unset: 1015371ms hog check: -1 caller: 0x7f49d8f6fc04 app-info: SMC comp_id(0x0054) msgno(23) rx_async_count(25)
*Feb 23 18:02:29.202: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi2: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:02:29.450: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi3: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:02:30.077: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi4: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:02:30.386: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi5: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:02:30.921: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi6: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:02:31.243: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi7: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:02:31.589: %IOSXE-4-PLATFORM: R0/0: kernel: e1000: Gi8: e1000_phy_read_status: Error reading PHY register
*Feb 23 18:05:27.502: %VUDI-6-EVENT: [serial number: 9C72RRO7SXX], [vUDI: CSR1000V:9C72RRO7SXX], A new vUDI has been generated
*Feb 23 18:05:27.526: %VUDI-6-EVENT: [serial number: 9C72RRO7SXX], [vUDI: CSR1000V:9C72RRO7SXX], The current vUDI has been invalidated by FP notification
*Feb 23 18:05:28.144: Step 3. deletion of NOT-in-use licenses
*Feb 23 18:05:28.145: Step 4. deletion of in-use licenses
*Feb 23 18:05:28.654: %LICENSE-2-UDI_CHANGED: UDI of this instance changed from OLD: CSR1000V:9C8ZXSRDHOR to New: CSR1000V:9C72RRO7SXX
*Feb 23 18:05:40.855: %IOSXE_OIR-6-INSCARD: Card (rp) inserted in slot R1
*Feb 23 18:05:40.898: %IOSXE_OIR-6-INSCARD: Card (fp) inserted in slot F0
*Feb 23 18:05:40.920: %IOSXE_OIR-6-ONLINECARD: Card (fp) online in slot F0
*Feb 23 18:05:45.649: %LINK-3-UPDOWN: Interface GigabitEthernet8, changed state to up
*Feb 23 18:05:45.703: %LINK-3-UPDOWN: Interface GigabitEthernet6, changed state to up
*Feb 23 18:05:45.754: %LINK-3-UPDOWN: Interface GigabitEthernet3, changed state to up
*Feb 23 18:05:45.772: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up
*Feb 23 18:05:45.808: %LINK-3-UPDOWN: Interface GigabitEthernet1, changed state to up
*Feb 23 18:05:49.287: %LINK-3-UPDOWN: Interface GigabitEthernet4, changed state to up
*Feb 23 18:05:49.308: %LINK-3-UPDOWN: Interface GigabitEthernet5, changed state to up
*Feb 23 18:05:49.359: %LINK-3-UPDOWN: Interface GigabitEthernet7, changed state to up

Posts: 1

Participants: 1

Read full topic

@keroger2k wrote:

Is there any sort of timeline on when the IOSv device will be upgraded?

Posts: 1

Participants: 1

Read full topic

@sb68 wrote:

Hi, due to lack of a PC that is powerful enough for VIRL I was going to use the VIRL launcher app for packet.net on an old laptop running Linux Mint 17.3 (386). I followed the instructions provided on the website and in the tutorial. Unfortunately I got stuck when I tried to launch the guest vm (virl boxcutter) by "vagrant up". Vagrant attempts to launch it, but is unable to communicate with the box.

sb68@laptop ~/virl_boxcutter $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'boxcutter/ubuntu1404' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key

... after some time (2 minutes or so) ...

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boottimeout" value) time period._

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot__timeout") value.

The VM seems to run somehow. If I attempt to start vagrant again, the following message appears:
sb68@laptop ~/virl_boxcutter $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'boxcutter/ubuntu1404' is up to date...
==> default: VirtualBox VM is already running.

Any ideas or suggestions? There are no error messages or something else that gives an indication of what is going wrong. Should the "config.vm.boot__timeout" value be changed? If yes, in which file and what is a reasonable value?

Thanks a lot in advance.

Posts: 1

Participants: 1

Read full topic

@nnichols wrote:

I don't know if I'm missing something obvious or if its not possible.

Let's say you create a topology with devices and have autonetkit generate the configs. You work with that topology for a time and later want to add a few more routers.

Can you add new devices in the design view and have autonetkit create initial configurations for the new devices without disturbing the existing device configurations that it created earlier?

Posts: 3

Participants: 2

Read full topic

@aadsfljasdfljasdfasd wrote:

My simple topology with 2 iosv and 5 iosvl2 running on ESXi 6 suddenly became a cpu hog, sucking up all the CPU resources from a i5-4670K. Normally the usage is about 25%.

What tools can I use to troubleshoot misbehaving nodes?

Posts: 1

Participants: 1

Read full topic

@Jason123 wrote:

While trying to install VIRL on Packet.net I got the following error during the install process (step 18 terraform plan);

Error loading config: Error parsing /home/vagrant/virl_packet/settings.tf: At 13:15: illegal char

Any help would be appreciated. Thanks!

Posts: 2

Participants: 2

Read full topic

@CBurns wrote:

Virl running on ESXi VM and working fine last week. Back to work after the weekend and now the Salt Status indicates the last successful contact was 2/19. Verified that Vm has connection to Salt servers. Not sure what to try next.

Posts: 1

Participants: 1

Read full topic