shgandhi / networkinglab470 Goto Github PK

When entering "vagrant up server01 leaf01 leaf02 spine01 spine02" I get the folllowing:

Bringing machine 'server01' up with 'virtualbox' provider...
Bringing machine 'leaf01' up with 'virtualbox' provider...
Bringing machine 'leaf02' up with 'virtualbox' provider...
Bringing machine 'spine01' up with 'virtualbox' provider...
Bringing machine 'spine02' up with 'virtualbox' provider...
==> server01: Checking if box 'yk0/ubuntu-xenial' is up to date...
==> server01: Machine already provisioned. Run vagrant provision or use the --provision
==> server01: flag to force provisioning. Provisioners marked to run always will still run.
==> leaf01: Checking if box 'CumulusCommunity/cumulus-vx' is up to date...
==> leaf01: Clearing any previously set forwarded ports...
==> leaf01: Fixed port collision for 22 => 2222. Now on port 2202.
==> leaf01: Clearing any previously set network interfaces...
==> leaf01: Preparing network interfaces based on configuration...
leaf01: Adapter 1: nat
leaf01: Adapter 2: intnet
leaf01: Adapter 3: intnet
leaf01: Adapter 4: intnet
leaf01: Adapter 5: intnet
leaf01: Adapter 6: intnet
leaf01: Adapter 7: intnet
leaf01: Adapter 8: intnet
leaf01: Adapter 9: intnet
leaf01: Adapter 10: intnet
leaf01: Adapter 11: intnet
leaf01: Adapter 12: intnet
==> leaf01: Forwarding ports...
leaf01: 22 (guest) => 2202 (host) (adapter 1)
==> leaf01: Running 'pre-boot' VM customizations...
==> leaf01: Booting VM...
==> leaf01: Waiting for machine to boot. This may take a few minutes...
leaf01: SSH address: 127.0.0.1:2202
leaf01: SSH username: vagrant
leaf01: SSH auth method: private key
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.boot_timeout" 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.

I tried to find the config.vm.boot_timeout file it mentions but haven't been able to find it in my folders. Otherwise I'm not sure what else to try.

I'm trying to setup the topology and when running the vagrant up command I get the following error:

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "e998dffc-42a1-44d2-a2ba-edc1399a9a87", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine '1522351716_router01' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Keshav\VirtualBox VMs\1522351716_router01\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Any ideas?

when issuing "vagrant up" I'm receiving

"there are errors in the configuration of this machine:
shell provisioner:
*'path' for shell provisioner does not exist on the host system: C:/Users/jacob/networkinglab470/OSPF/helper_scripts/extra_switch_config.sh""

running this setup:
VirtualBox 5.2.26
git 2.21.0
vagrant: 2.0.2

Under verify network connectivity.

I get this when I try to run it

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "955cddff-402e-4ffe-9ddd-063c689bc7a6", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine '1522351716_router01' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\bellj\VirtualBox VMs\1522351716_router01\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

VBoxHardening.log ERROR.zip

While running vagrant up I got the following error message:

There are errors in the configuration of this machine. Please fix
the following errors and try again:

shell provisioner:

• path for shell provisioner does not exist on the host system: /Users/apple/networkinglab470/OSPF/helper_scripts/extra_switch_config.sh

Same as here: hashicorp/vagrant#10007

When trying to start Server01, receive this error:

 server01: Downloading: https://vagrantcloud.com/yk0/boxes/ubuntu-xenial/versions/201606082/providers/virtualbox.box
    server01:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054

So I followed all of the instructions and after some painful debugging I was able to get it working. However I am still little confused about what to do when I am done with the instructions. Should I keep the devices running on virtual box or do I turn them off before closing? Also what is the difference between the putty terminal and the virtual box terminal?

Command should be

sudo ifconfig eth1 10.12.2.2/24

for example for server 01.

Whenever I use this command I get this error:

Failed to locate the powershell executable on the available PATH. Please ensure powershell is installed and available on the local PATH, then run the command again.

When running "vagrant up", it times out on the SSH part.

My system information:
OS: Linux Mint 18.2 Sonya (based on Ubuntu Xenial 16.04)
Virtualbox version: 5.1.22
Vagrant version: 2.0.2

A screenshot of the error: