1 2 Previous Next 16 Replies Latest reply: May 9, 2017 9:26 PM by Godfred RSS

    Cannot connect to any VIRL servers

    Zac.Esa

      I'm pulling all my hair out right now because of VIRL. It's causing me so much issues. Basically, my VIRL just can't connect to the Cisco servers. I'm not sure what the issue is. I've already followed all the troubleshooting steps at T-Shoot: Failed to collect current salt contact status but, I'm passing at all the checks yet, VIRL still doesn't want to connect. See below for more information.

       

      Screen Shot 2017-04-19 at 6.33.15 PM.pngScreen Shot 2017-04-19 at 6.36.30 PM.png

       

      As you can see from the above screenshots, it just doesn't want to connect to any of the servers even though I can reach them at Port 4505 and 4506!

       

      virl@virl:~$ nc -zv us-1.virl.info 4505-4506

      Connection to us-1.virl.info 4505 port [tcp/*] succeeded!

      Connection to us-1.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv us-2.virl.info 4505-4506

      Connection to us-2.virl.info 4505 port [tcp/*] succeeded!

      Connection to us-2.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv us-3.virl.info 4505-4506

      Connection to us-3.virl.info 4505 port [tcp/*] succeeded!

      Connection to us-3.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv us-4.virl.info 4505-4506

      Connection to us-4.virl.info 4505 port [tcp/*] succeeded!

      Connection to us-4.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv eu-1.virl.info 4505-4506

      Connection to eu-1.virl.info 4505 port [tcp/*] succeeded!

      Connection to eu-1.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv eu-2.virl.info 4505-4506

      Connection to eu-2.virl.info 4505 port [tcp/*] succeeded!

      Connection to eu-2.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv eu-3.virl.info 4505-4506

      Connection to eu-3.virl.info 4505 port [tcp/*] succeeded!

      Connection to eu-3.virl.info 4506 port [tcp/*] succeeded!

      virl@virl:~$ nc -zv eu-4.virl.info 4505-4506

      Connection to eu-4.virl.info 4505 port [tcp/*] succeeded!

      Connection to eu-4.virl.info 4506 port [tcp/*] succeeded!

       

      I even tried the commands from the troubleshooting guide and all of it succeeded!

       

      When I get ID, I'm getting the correct ID!

       

      virl@virl:~$ sudo salt-call -l debug test.ping

      [DEBUG   ] Reading configuration from /etc/salt/minion

      [DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf'

      [DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf

      [DEBUG   ] Including configuration from '/etc/salt/minion.d/extra.conf'

      [DEBUG   ] Reading configuration from /etc/salt/minion.d/extra.conf

      [DEBUG   ] Including configuration from '/etc/salt/minion.d/openstack.conf'

      [DEBUG   ] Reading configuration from /etc/salt/minion.d/openstack.conf

      [DEBUG   ] Configuration file path: /etc/salt/minion

      [WARNING ] Insecure logging configuration detected! Sensitive data may be logged.

      [DEBUG   ] Reading configuration from /etc/salt/minion

      [DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf'

      [DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf

      [DEBUG   ] Including configuration from '/etc/salt/minion.d/extra.conf'

      [DEBUG   ] Reading configuration from /etc/salt/minion.d/extra.conf

      [DEBUG   ] Including configuration from '/etc/salt/minion.d/openstack.conf'

      [DEBUG   ] Reading configuration from /etc/salt/minion.d/openstack.conf

      [WARNING ] /usr/lib/python2.7/dist-packages/salt/grains/core.py:1493: DeprecationWarning: The "osmajorrelease" will be a type of an integer.

       

      [INFO    ] Got list of available master addresses: ['us-1.virl.info', 'us-2.virl.info', 'us-3.virl.info', 'us-4.virl.info']

      [DEBUG   ] Connecting to master. Attempt 1 of 1

      [DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'AXXXXXXX.virl.info', 'tcp://147.75.64.189:4506')

      [DEBUG   ] Generated random reconnect delay between '1000ms' and '11000ms' (9500)

      [DEBUG   ] Setting zmq_reconnect_ivl to '9500ms'

      [DEBUG   ] Setting zmq_reconnect_ivl_max to '11000ms'

      [DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'AXXXXXXX.virl.info', 'tcp://147.75.64.189:4506', 'clear')

      [DEBUG   ] salt.crypt.verify_signature: Loading public key

      [DEBUG   ] salt.crypt.verify_signature: Verifying signature

      [DEBUG   ] Successfully verified signature of master public key with verification public key master_sign.pub

      [INFO    ] Received signed and verified master pubkey from master us-1.virl.info

      [DEBUG   ] Decrypting the current master AES key

      [DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem

      [DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem

      [DEBUG   ] Determining pillar cache

      [DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'AXXXXXXX.info', 'tcp://147.75.64.189:4506', 'aes')

      [DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'AXXXXXXX.virl.info', 'tcp://147.75.64.189:4506')

      [DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem

      [DEBUG   ] LazyLoaded jinja.render

      [DEBUG   ] LazyLoaded yaml.render

      [DEBUG   ] LazyLoaded test.ping

      [DEBUG   ] Initializing new AsyncZeroMQReqChannel for ('/etc/salt/pki/minion', 'AXXXXXXX.virl.info', 'tcp://147.75.64.189:4506', 'aes')

      [DEBUG   ] Initializing new AsyncAuth for ('/etc/salt/pki/minion', 'AXXXXXXX.virl.info', 'tcp://147.75.64.189:4506')

      [DEBUG   ] LazyLoaded nested.output

      local:

          True

       

      As you can see, even my license is not rejected by the server! I've even tried reinstalling it 4 times but, all the times, still the same issue. I've checked the checksum for the ISO, I've redownloaded the ISO and checked the checksum again, all to no avail. What's weird to me is that it worked for me when I installed it on ESXi but now, when I'm trying to get it on a bare-metal server, it just refuses to work properly. I'm trying to convince my boss to fight for a refund cause VIRL has been nothing but problems for me.

        • 1. Re: Cannot connect to any VIRL servers
          alejo-VIRL Support

          Hello Zac.Esa, please run VIRL Server Config Validation script and attach it to your response. Also, have you tried to run any simulations?

          If you have made configuration changes to your server via CLI, make sure they are reflected in UWM. If they are not, re-enter the same information via UWM and apply changes.

          • 2. Re: Cannot connect to any VIRL servers
            Zac.Esa

            First off, when I look at the overview screen, it's showing me the below screenshot;

            Screen Shot 2017-04-20 at 8.37.02 AM.png

            When I point at the exclamation mark, it's saying, "Available Version: null"

             

            Whenever I try to reset keys and ID, I get the following error;

            Screen Shot 2017-04-20 at 8.46.17 AM.png

            So, I thought that it's an issue with the NTP Servers and when I run ntpq -p, I get the below results;

            virl@virl:~$ sudo ntpq -p

                remote          refid      st t when poll reach  delay  offset  jitter

            ==============================================================================

            asterix.fraho.e .INIT.          16 u    -  64    0    0.000    0.000  0.000

            tilia.zsx.hu    .INIT.          16 u    -  64    0    0.000    0.000  0.000

            213.251.52.217  .INIT.          16 u    -  64    0    0.000    0.000  0.000

            hadb1.smatwebde .INIT.          16 u    -  64    0    0.000    0.000  0.000

            utcnist2.colora .INIT.          16 u    -  64    0    0.000    0.000  0.000

            So, I went through T-Shoot: NTP errors and connectivity on VIRL but, as you can see below, I can connect to the NTP servers using ntpdate but the NTP daemon just doesn't want to connect to the NTP Servers. It's weird because no outgoing traffic is blocked on my firewall so, why is it that the NTP daemon cannot sync to the public NTP pool.

            virl@virl:~$ sudo ntpdate -d pool.ntp.org

            20 Apr 08:52:42 ntpdate[27111]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)

            Looking for host pool.ntp.org and service ntp

            host found : ntp.tuxfamily.net

            transmit(212.85.158.10)

            transmit(51.174.171.7)

            receive(212.85.158.10)

            receive(51.174.171.7)

            transmit(193.6.176.19)

            receive(193.6.176.19)

            transmit(194.177.4.1)

            receive(194.177.4.1)

            transmit(212.85.158.10)

            transmit(51.174.171.7)

            receive(51.174.171.7)

            transmit(193.6.176.19)

            receive(212.85.158.10)

            receive(193.6.176.19)

            transmit(194.177.4.1)

            receive(194.177.4.1)

            transmit(51.174.171.7)

            receive(51.174.171.7)

            transmit(212.85.158.10)

            transmit(193.6.176.19)

            receive(193.6.176.19)

            transmit(194.177.4.1)

            receive(212.85.158.10)

            receive(194.177.4.1)

            transmit(51.174.171.7)

            receive(51.174.171.7)

            transmit(193.6.176.19)

            receive(193.6.176.19)

            transmit(212.85.158.10)

            transmit(194.177.4.1)

            receive(194.177.4.1)

            receive(212.85.158.10)

            server 212.85.158.10, port 123

            stratum 2, precision -21, leap 00, trust 000

            refid [212.85.158.10], delay 0.28719, dispersion 0.00024

            transmitted 4, in filter 4

            reference time:    dca28235.f73d657c  Thu, Apr 20 2017  8:41:25.965

            originate timestamp: dca284e6.8bdb6f2e  Thu, Apr 20 2017  8:52:54.546

            transmit timestamp:  dca284e6.7bdcea40  Thu, Apr 20 2017  8:52:54.483

            filter delay:  0.28719  0.28917  0.28732  0.28723

                    0.00000  0.00000  0.00000  0.00000

            filter offset: -0.06814 -0.06788 -0.06860 -0.06836

                    0.000000 0.000000 0.000000 0.000000

            delay 0.28719, dispersion 0.00024

            offset -0.068141

             

            server 51.174.171.7, port 123

            stratum 2, precision -23, leap 00, trust 000

            refid [51.174.171.7], delay 0.20976, dispersion 0.00044

            transmitted 4, in filter 4

            reference time:    dca28015.1b03d157  Thu, Apr 20 2017  8:32:21.105

            originate timestamp: dca284e6.28ddb872  Thu, Apr 20 2017  8:52:54.159

            transmit timestamp:  dca284e6.1570e669  Thu, Apr 20 2017  8:52:54.083

            filter delay:  0.20990  0.20976  0.20981  0.21011

                    0.00000  0.00000  0.00000  0.00000

            filter offset: -0.01569 -0.01656 -0.01612 -0.01640

                    0.000000 0.000000 0.000000 0.000000

            delay 0.20976, dispersion 0.00044

            offset -0.016567

             

            server 193.6.176.19, port 123

            stratum 2, precision -23, leap 00, trust 000

            refid [193.6.176.19], delay 0.19823, dispersion 0.00017

            transmitted 4, in filter 4

            reference time:    dca284c3.3843fe15  Thu, Apr 20 2017  8:52:19.219

            originate timestamp: dca284e6.5a3d3621  Thu, Apr 20 2017  8:52:54.352

            transmit timestamp:  dca284e6.48a7059f  Thu, Apr 20 2017  8:52:54.283

            filter delay:  0.19853  0.20001  0.19824  0.19823

                    0.00000  0.00000  0.00000  0.00000

            filter offset: -0.01735 -0.01826 -0.01770 -0.01763

                    0.000000 0.000000 0.000000 0.000000

            delay 0.19823, dispersion 0.00017

            offset -0.017633

             

            server 194.177.4.1, port 123

            stratum 2, precision -20, leap 00, trust 000

            refid [194.177.4.1], delay 0.21434, dispersion 0.00034

            transmitted 4, in filter 4

            reference time:    dca284dd.7c7d131b  Thu, Apr 20 2017  8:52:45.486

            originate timestamp: dca284e6.87588c46  Thu, Apr 20 2017  8:52:54.528

            transmit timestamp:  dca284e6.7be9a865  Thu, Apr 20 2017  8:52:54.484

            filter delay:  0.21434  0.21729  0.21494  0.21651

                    0.00000  0.00000  0.00000  0.00000

            filter offset: -0.05027 -0.05067 -0.04994 -0.05081

                    0.000000 0.000000 0.000000 0.000000

            delay 0.21434, dispersion 0.00034

            offset -0.050275

             

            20 Apr 08:52:54 ntpdate[27111]: adjust time server 193.6.176.19 offset -0.017633 sec

            I tried changing the NTP Server via UWM but, whenever I try to change anything, I'm getting the below error;

            Screen Shot 2017-04-20 at 8.44.11 AM.png

            I tried changing the NTP server at /etc/virl.ini but, it doesn't affect the NTP servers that the NTP daemon uses so, I tried changing it at /etc/ntp.conf and strangely, the NTP daemon syncs properly with my own NTP servers but, whenever I try to reset keys and ID, the /etc/ntp.conf will change back to the original NTP server used. I even tried changing the NTP server at /etc/virl.ini and /etc/ntp.conf but, everytime I try to reset keys and ID, it will revert /etc/ntp.conf back to using pool.ntp.org. So, you can see my problem here, I can't change NTP configuration due to no salt connectivity check, neither can I connect to salt servers due to NTP issue. The only way I was able to reset keys and ID without any errors was to point pool.ntp.org to the IP of my own NTP servers but even then, it's still not able to connect to the salt servers.

             

            Next, the SrvValTest.txt file, you can find the file attached. I've redacted the IP address on my network interface. Another problem I see is that, my server has 4 NICs but, when I run ifconfig, I can only see eth0 and eth1, I don't see eth2 and eth3. Even in the SrvValTest, it's showing that eth2 and eth3 has no MAC and HW addresses configured.

             

            As you can see, my VIRL is being riddled with a multitude of problems and it's driving me insane!

             

            EDIT: To answer your question, no, I've not tried to run any simulations yet as I have not even set the configuration properly. Also, the IP which I set at /etc/network/interfaces is not being reflect in the UWM too. Do note that all these issues persisted even after 4 reinstallations.(2 via optical drive, 2 via ISO image through the server's remote management controller)

            Screen Shot 2017-04-20 at 9.08.45 AM.png

            • 3. Re: Cannot connect to any VIRL servers
              Zac.Esa

              alegalle Any updates on this issue?

              • 4. Re: Cannot connect to any VIRL servers
                alejo-VIRL Support

                There are still a couple of steps which have not been completed. Take a look at the bare-metal instructions Installing VIRL and follow the steps for configuring the dummy interfaces. Once you have set the dummy interfaces you should be able to correct the connectivity errors. Once that is complete, the NTP errors should correct themselves albeit the peering problem is not being interfered by your ISP.

                 

                Also How To: Configure Static IP Address Manually should assist with correctly configuring your static IP address.

                • 5. Re: Cannot connect to any VIRL servers
                  Zac.Esa

                  Hi alegalle, my server has 4 ports, I don't understand why the VIRL isn't detecting my other two ports. From the /var/log/dmesg, I can see that it's detecting the interface and then renaming the interface. That's why I only configure dummy interface for one interface(eth4).

                   

                  [    3.662576] e1000e 0000:04:00.0 eth0: (PCI Express:2.5GT/s:Width x4) xx:xx:xx:xx:xx:xx

                  [    3.662584] e1000e 0000:04:00.0 eth0: Intel(R) PRO/1000 Network Connection

                  [    3.662672] e1000e 0000:04:00.0 eth0: MAC: 5, PHY: 5, PBA No: FFFFFF-0FF

                  [    3.711034] e1000e 0000:04:00.1 eth1: (PCI Express:2.5GT/s:Width x4) xx:xx:xx:xx:xx:xx

                  [    3.711038] e1000e 0000:04:00.1 eth1: Intel(R) PRO/1000 Network Connection

                  [    3.711114] e1000e 0000:04:00.1 eth1: MAC: 5, PHY: 5, PBA No: FFFFFF-0FF

                  [    3.890415] e1000e 0000:0b:00.0 eth2: (PCI Express:2.5GT/s:Width x4) xx:xx:xx:xx:xx:xx

                  [    3.890434] e1000e 0000:0b:00.0 eth2: Intel(R) PRO/1000 Network Connection

                  [    3.890518] e1000e 0000:0b:00.0 eth2: MAC: 0, PHY: 4, PBA No: C83246-002

                  [    4.068970] e1000e 0000:0b:00.1 eth3: (PCI Express:2.5GT/s:Width x4) xx:xx:xx:xx:xx:xx

                  [    4.068976] e1000e 0000:0b:00.1 eth3: Intel(R) PRO/1000 Network Connection

                  [    4.069057] e1000e 0000:0b:00.1 eth3: MAC: 0, PHY: 4, PBA No: C83246-002

                  [    4.181967] e1000e 0000:0b:00.0 p32p1: renamed from eth2

                  [    4.196962] e1000e 0000:0b:00.1 p32p2: renamed from eth3

                  [    4.197025] systemd-udevd[168]: renamed network interface eth2 to p32p1

                  [    4.208296] systemd-udevd[169]: renamed network interface eth3 to p32p2

                  [   18.167991] device eth1 entered promiscuous mode

                  [   20.311609] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

                  [   21.075790] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

                  EDIT: I've renamed the interfaces, p32p1 and p32p2 to eth2 and eth3 using /etc/udev/rules.d/70-persistent-net.rules, when I run ifconfig, it shows the interface now but, all the same issues still persist. Nothing has changed.

                  • 6. Re: Cannot connect to any VIRL servers
                    alejo-VIRL Support

                    You don't need to rename the interfaces for the system to function. That is only needed for personal sanity and ease of configuration.

                    Lets get back in sync so I can better understand exactly what you have so far.

                     

                    Re-run the validation script and attach the output text file.

                    Copy and paste the following code and respond with the output -- this will provide a list of your interfaces and their MAC address so we can ensure they are mapped correctly.

                     

                    printf "\n%10s\t [%s]:\t\t%s\t\t%10s (%s)\n" "Interface" "MAC" "IP Addr" "Driver" "Status"
                    for f in /sys/class/net/*; do
                       dev=$(basename $f)

                      driver=$(readlink $f/device/driver/module)

                      iaddr=$(ip addr show dev $dev | awk '$1 == "inet" { sub("/..", "", $2); print $2}')

                       if [[ -z $iaddr ]]; then
                       iaddr=$(printf "No IP Address")

                       fi
                      if [ $driver ]; then
                       driver=$(basename $driver)

                       fi
                       addr=$(cat $f/address)

                      operstate=$(cat $f/operstate)

                       if [[ ! -z $driver ]]; then
                       printf "%10s [%s]: %s\t%10s (%s)\n" "$dev" "$addr" "$iaddr" "$driver" "$operstate"
                       fi
                    done

                     

                    Once I am able to get an idea of how your system is connected, I will be able to provide better guidance as to why you are still not able to complete configuration. As for your other ports, are they connected to your network and show link light?

                    • 7. Re: Cannot connect to any VIRL servers
                      Zac.Esa

                      It was either I renamed it in /etc/network/interfaces or, in the system. I was afraid that VIRL would only recognize eth* interfaces so, I renamed it on the system.

                       

                      Please see attached for the script output.

                       

                      The output of the command;

                       

                      eth0 [00:1e:68:49:b2:e8]: xxx.xx.xx.xx

                      172.16.10.250        e1000e (up)

                            eth1 [00:1e:68:49:b2:e9]: No IP Address        e1000e (up)

                            eth2 [00:1e:68:49:b2:ea]: No IP Address        e1000e (up)

                            eth3 [00:1e:68:49:b2:eb]: No IP Address        e1000e (up)

                       

                      Yes, my other ports are connected to my network and shows the link lights.

                      • 8. Re: Cannot connect to any VIRL servers
                        alejo-VIRL Support

                        So we see that dummy is configured and has received a system generated MAC but we do not see this interface configured by the system. The output from the interfaces script shows us that interface dummy1 does not exist. It also shows that your 'eth' interfaces are not correctly configured. They show connected, but there is no IP address associated to any of the interfaces except 'eth0'

                         

                        dummy1 CONFIGURED
                        MAC: 76:c8:c4:a3:d3:ed
                        HW:  76:c8:c4:a3:d3:ed
                        IP: 172.16.10.250
                        
                        
                        eth0 CONFIGURED
                        MAC: 00:1e:68:49:b2:e8
                        HW:  00:1e:68:49:b2:e8
                        IP: xxx.xx.xx.xx
                        172.16.10.250
                        
                        
                        eth1 CONFIGURED
                        MAC: 00:1e:68:49:b2:e9
                        HW:  00:1e:68:49:b2:e9
                        IP:
                        
                        
                        eth2 CONFIGURED
                        MAC: 00:1e:68:49:b2:ea
                        HW:  00:1e:68:49:b2:ea
                        IP:
                        
                        
                        eth3 CONFIGURED
                        MAC: 00:1e:68:49:b2:eb
                        HW:  00:1e:68:49:b2:eb
                        IP:
                        

                         

                        Resolution:

                        So what we need to decide is wether we will keep the current 'eth' interface names or revert back to default, it does not matter we just need to make sure that the names match everywhere. I will leave this up to you,  but if your interface renaming is not correct it will be extremely difficult for me to see that.

                        Also decide if your connected NICs will be used for external connectivity. Meaning, will the external VIRL networks of Flat and Flat1 be valid on your physical network? If they are then no changes to those interfaces needed. If they will not be used for physical connectivity then I would suggest to disconnect them and turn them into dummy interfaces.

                         

                        Adjust /etc/network/interfaces as needed and remove the last line shown below

                         

                        auto eth0
                        iface eth0 inet static
                            address xxx.xx.xx.xx
                            netmask 255.255.255.0
                            gateway xxx.xx.xx.x
                            dns-nameservers xxx.xx.xx.xxx xxx.xx.xx.xx
                            up ip addr add 172.16.10.250/24 dev eth0      <<<<=== You can remove this line as it will not be needed
                        

                         

                        Adjust System interface as shown below

                         

                        auto dummy3
                        iface dummy3 inet static
                            address 172.16.10.250
                            netmask 255.255.255.0
                           mtu 1500
                            post-up ip link set dummy3 promisc on
                        

                         

                        Adjust /etc/virl.ini for System Interface as shown below

                         

                        dummy_int: True
                        internalnet_controller_hostname: controller
                        internalnet_controller_IP: 172.16.10.250
                        internalnet_port: dummy3
                        internalnet_IP: 172.16.10.250
                        internalnet_network: 172.16.10.0
                        internalnet_netmask: 255.255.255.0
                        internalnet_gateway: 172.16.10.1
                        

                         

                        Reboot your server

                        sudo reboot now

                         

                        Update Openstack configuration and make changes permanent

                        sudo vinstall rehost

                        sudo reboot now

                         

                        Let me know if you have any questions, and if the issue persists please rerun the scripts once you have completed all of the steps outlined above and attach output.

                         

                        For Reference: How To: Configure Static IP Address Manually

                        • 9. Re: Cannot connect to any VIRL servers
                          Zac.Esa

                          If I remove,

                           

                          up ip addr add 172.16.10.250/24 dev eth0

                           

                          I won't be able to ping 172.16.10.250. And according to the guide, Installing VIRL to Bare-Metal using an ISO Boot Image, I'm supposed to put that line in. I've decided to switch all my interfaces except eth0 to dummy interfaces but I think it's worse now.

                           

                          EDIT: I ran sudo ip li add dummy[1-4] type dummy and now ifconfig is showing the dummy interfaces. Will update later.

                          • 10. Re: Cannot connect to any VIRL servers
                            Zac.Esa

                            alegalle Update, I'm still having issues connecting to the cisco servers.

                             

                            I've reinstalled my VIRL, then I set up my static IP on eth0, disconnected all other interfaces and used dummy interfaces for all 4 other interfaces yet, it's still showing that I'm not connected to the cisco servers.

                             

                            Screen Shot 2017-05-03 at 2.32.50 PM.png

                             

                            It's showing the X beside the Connect for all the hosts.

                             

                            Since it was version 1.2.84, I wasn't able to change any settings. I would get the error;

                            Operation will attempt to downgrade core components. Downgrades of core components are not supported.

                            So, I followed the instructions at State changed from Building/Absent to Error and did the commands;

                             

                            sudo salt-call --local grains.get virl_release

                            sudo salt-call grains.setval virl_release 1.2.83

                            sudo service virl-uwm restart

                             

                            After that, whenever I tried to change any settings, I would get the error message below;

                             

                            Screen Shot 2017-05-03 at 2.44.49 PM.png

                             

                            It was also showing that the "AutoNetKit-Cisco" had a new version so, I tried to update it but, got the same results as when I tried changing the settings.

                             

                            Regardless, of all this, I tried running a simulation and I think I was able to. So, the question is, why can't my VIRL server contact the cisco hosts? If it helps, my VIRL server is using a public IP, thus why I have to remove the IP from the SrvValTest file. Do I need to allow inbound connection from the cisco hosts to my VIRL server? If so, what are the ports I need to allow and from what IP address? All outbound connections are not blocked.

                             

                            UPDATE: Simulations cannot run. The error below come up;

                             

                            (INFO) [May/03/2017 15:02:10] simulation "testsimulation-QtSzII": nodes can start

                            (INFO) [May/03/2017 15:03:45] Starting node "~mgmt-lxc"

                            (WARNING) [May/03/2017 15:03:46] Node "~mgmt-lxc" state changed from ABSENT to SHUTOFF

                            (INFO) [May/03/2017 15:04:10] Starting node "csr1000v-1"

                            (INFO) [May/03/2017 15:04:29] Starting node "iosv-1"

                            (INFO) [May/03/2017 15:04:41] Node "csr1000v-1" state changed from ABSENT to BUILDING

                            (INFO) [May/03/2017 15:04:50] Starting node "iosv-2"

                            (INFO) [May/03/2017 15:04:56] Node "~mgmt-lxc" state changed from SHUTOFF to ACTIVE

                            (INFO) [May/03/2017 15:05:07] Starting node "iosv-3"

                            (INFO) [May/03/2017 15:05:28] Node "iosv-1" state changed from ABSENT to BUILDING

                            (INFO) [May/03/2017 15:05:33] Node "iosv-2" state changed from ABSENT to BUILDING

                            (INFO) [May/03/2017 15:05:40] Node "iosv-3" state changed from ABSENT to BUILDING

                            (ERROR) [May/03/2017 15:07:16] Node "csr1000v-1" state changed from BUILDING to ERROR with message: No valid host was found. Exceeded max scheduling attempts 3 for instance 2d74c30d-9a7a-47b4-8f90-263966389a20. 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) [May/03/2017 15:07:16] Node "iosv-1" state changed from BUILDING to ERROR with message: No valid host was found. Exceeded max scheduling attempts 3 for instance 4cc71f74-7b98-4c29-ad8d-a7f6e2af6662. 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) [May/03/2017 15:07:53] Node "iosv-2" state changed from BUILDING to ERROR with message: No valid host was found. Exceeded max scheduling attempts 3 for instance 64467b46-e92f-47c6-a1f8-c36ac9f4f07c. 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) [May/03/2017 15:07:55] Node "iosv-3" state changed from BUILDING to ERROR with message: No valid host was found. Exceeded max scheduling attempts 3 for instance 70b3e6c5-3b5a-4172-b270-52bb35efed90. 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

                            • 11. Re: Cannot connect to any VIRL servers
                              alejo-VIRL Support

                              Zac.Esa  Sent you an IM as well.

                               

                              Based on the validation text, your configuration looks completely correct and it also shows that your VIRL server is able to authenticate its license. If you made the changes via CLI, did you also run the 'rehost' command?

                              • 12. Re: Cannot connect to any VIRL servers
                                Zac.Esa

                                alegalle Yes, I've run 'vinstall rehost' whenever I make changes via CLI.

                                • 13. Re: Cannot connect to any VIRL servers
                                  Godfred

                                  zac.esa Check your salt version.

                                   

                                  This worked for me.

                                  _______________________________________________________________________

                                  OK check if you have proper version of salt via command pip freeze  | grep salt


                                  If the salt version is newer than (2015.8.x) then you must downgrade (sudo pip install salt==2015.8.8). After downgrade restart virl-uwm and vil-std services (sudo service virl-uwm restart)

                                  _______________________________________________________________________

                                  Failed to load package versions: internal server error

                                  • 14. Re: Cannot connect to any VIRL servers
                                    Zac.Esa

                                    Thanks for the suggestion GodfredAhuma but, it didn't change anything. I'm still experiencing the same issues.

                                     

                                    Screen Shot 2017-05-09 at 1.53.26 PM.png

                                     

                                    Screen Shot 2017-05-09 at 1.52.46 PM.png

                                    1 2 Previous Next