Topics

Intel/Wind River Lab Move Update - New VPN IP


Gooch, Stephen
 

Hello,

 

The Intel/Wind River lab was relocated into a new data center last week.   The only change required to connect to the new location is to update the VPN IP in the .ovpn file.  Here is the change:

 

[sgooch@atl-sgooch-lx ~]$ diff -u pod-onap-01.ovpn.org pod-onap-01.ovpn

--- pod-onap-01.ovpn.org   2020-01-13 13:03:03.960856010 -0500

+++ pod-onap-01.ovpn 2020-01-09 18:27:03.560549576 -0500

@@ -5,7 +5,7 @@

client

dev tun

proto tcp

-remote 192.55.48.241 443

+remote 146.152.204.133 443

resolv-retry infinite

auth-nocache

nobind

 

The lab is accessible, but there is a firewall update that Intel IT is working on to allow VMs to communicate with the Internet.   I’ll send out a follow up email when the firewall rules have been updated.

 

Br,

- Stephen

 

Stephen Gooch | Solutions Engineering | Wind River

+1.510.965.7909 , Skype ID: stephen.gooch

 


Marco Platania
 

Stephen,

 

Thanks!

 

I was able to connect to the VPN and access the Horizon portal. I guess we’ll need to wait for the firewall to be updated to download the latest ONAP containers, but having the lab back in business is a good news!

 

Marco

 

From: <onap-discuss@...> on behalf of "Gooch, Stephen" <stephen.gooch@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "stephen.gooch@..." <stephen.gooch@...>
Date: Monday, January 13, 2020 at 1:20 PM
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] Intel/Wind River Lab Move Update - New VPN IP

 

146.152.204.133


Marco Platania
 

Stephen,

 

VMs in the Windriver lab seem to have connection to the internet as best I can tell:

 

root@sb00-nfs:~# ping google.com

PING google.com (172.217.14.238) 56(84) bytes of data.

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=1 ttl=51 time=5.14 ms

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=2 ttl=51 time=5.09 ms

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=3 ttl=51 time=5.10 ms

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=4 ttl=51 time=5.06 ms

 

root@sb00-nfs:~# ping nexus.onap.org

PING cloud.onap.org (199.204.45.137) 56(84) bytes of data.

64 bytes from compute-199-204-45-137.ca-ymq-1.vexxhost.net (199.204.45.137): icmp_seq=1 ttl=48 time=84.3 ms

64 bytes from compute-199-204-45-137.ca-ymq-1.vexxhost.net (199.204.45.137): icmp_seq=2 ttl=48 time=84.2 ms

64 bytes from compute-199-204-45-137.ca-ymq-1.vexxhost.net (199.204.45.137): icmp_seq=3 ttl=48 time=84.1 ms

 

However, the VM that we use as APT and docker proxy is either down or not connected to the internet. Its IP is 10.12.5.2:

 

root@sb00-nfs:~# apt-get -y update

Err:1 http://nova.clouds.archive.ubuntu.com/ubuntu bionic InRelease

  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease

  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

Err:3 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates InRelease

  Unable to connect to 10.12.5.2:8000:

Err:4 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-backports InRelease

  Unable to connect to 10.12.5.2:8000:

Reading package lists... Done

W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Unable to connect to 10.12.5.2:8000:

W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Unable to connect to 10.12.5.2:8000:

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

 

Could you please check when you have the chance?

 

Thanks,

Marco

 

From: <onap-discuss@...> on behalf of "Gooch, Stephen" <stephen.gooch@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "stephen.gooch@..." <stephen.gooch@...>
Date: Monday, January 13, 2020 at 1:20 PM
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] Intel/Wind River Lab Move Update - New VPN IP

 

Hello,

 

The Intel/Wind River lab was relocated into a new data center last week.   The only change required to connect to the new location is to update the VPN IP in the .ovpn file.  Here is the change:

 

[sgooch@atl-sgooch-lx ~]$ diff -u pod-onap-01.ovpn.org pod-onap-01.ovpn

--- pod-onap-01.ovpn.org   2020-01-13 13:03:03.960856010 -0500

+++ pod-onap-01.ovpn 2020-01-09 18:27:03.560549576 -0500

@@ -5,7 +5,7 @@

client

dev tun

proto tcp

-remote 192.55.48.241 443

+remote 146.152.204.133 443

resolv-retry infinite

auth-nocache

nobind

 

The lab is accessible, but there is a firewall update that Intel IT is working on to allow VMs to communicate with the Internet.   I’ll send out a follow up email when the firewall rules have been updated.

 

Br,

- Stephen

 

Stephen Gooch | Solutions Engineering | Wind River

+1.510.965.7909 , Skype ID: stephen.gooch

 


Marco Platania
 

+ Eddy, as Stephen is on a business trip.

 

Eddy,

 

Is it possible for you to give a look at the problem below when you have the chance please?

 

Thanks,

Marco

 

From: <onap-discuss@...> on behalf of "PLATANIA, MARCO (MARCO)" <platania@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "PLATANIA, MARCO (MARCO)" <platania@...>
Date: Thursday, January 16, 2020 at 4:27 PM
To: "onap-discuss@..." <onap-discuss@...>, "stephen.gooch@..." <stephen.gooch@...>
Subject: Re: [onap-discuss] Intel/Wind River Lab Move Update - New VPN IP

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.


Stephen,

 

VMs in the Windriver lab seem to have connection to the internet as best I can tell:

 

root@sb00-nfs:~# ping google.com

PING google.com (172.217.14.238) 56(84) bytes of data.

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=1 ttl=51 time=5.14 ms

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=2 ttl=51 time=5.09 ms

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=3 ttl=51 time=5.10 ms

64 bytes from sea30s02-in-f14.1e100.net (172.217.14.238): icmp_seq=4 ttl=51 time=5.06 ms

 

root@sb00-nfs:~# ping nexus.onap.org

PING cloud.onap.org (199.204.45.137) 56(84) bytes of data.

64 bytes from compute-199-204-45-137.ca-ymq-1.vexxhost.net (199.204.45.137): icmp_seq=1 ttl=48 time=84.3 ms

64 bytes from compute-199-204-45-137.ca-ymq-1.vexxhost.net (199.204.45.137): icmp_seq=2 ttl=48 time=84.2 ms

64 bytes from compute-199-204-45-137.ca-ymq-1.vexxhost.net (199.204.45.137): icmp_seq=3 ttl=48 time=84.1 ms

 

However, the VM that we use as APT and docker proxy is either down or not connected to the internet. Its IP is 10.12.5.2:

 

root@sb00-nfs:~# apt-get -y update

Err:1 http://nova.clouds.archive.ubuntu.com/ubuntu bionic InRelease

  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease

  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

Err:3 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-updates InRelease

  Unable to connect to 10.12.5.2:8000:

Err:4 http://nova.clouds.archive.ubuntu.com/ubuntu bionic-backports InRelease

  Unable to connect to 10.12.5.2:8000:

Reading package lists... Done

W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Unable to connect to 10.12.5.2:8000:

W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Unable to connect to 10.12.5.2:8000:

W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Could not connect to 10.12.5.2:8000 (10.12.5.2). - connect (111: Connection refused)

 

Could you please check when you have the chance?

 

Thanks,

Marco

 

From: <onap-discuss@...> on behalf of "Gooch, Stephen" <stephen.gooch@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "stephen.gooch@..." <stephen.gooch@...>
Date: Monday, January 13, 2020 at 1:20 PM
To: "onap-discuss@..." <onap-discuss@...>
Subject: [onap-discuss] Intel/Wind River Lab Move Update - New VPN IP

 

Hello,

 

The Intel/Wind River lab was relocated into a new data center last week.   The only change required to connect to the new location is to update the VPN IP in the .ovpn file.  Here is the change:

 

[sgooch@atl-sgooch-lx ~]$ diff -u pod-onap-01.ovpn.org pod-onap-01.ovpn

--- pod-onap-01.ovpn.org   2020-01-13 13:03:03.960856010 -0500

+++ pod-onap-01.ovpn 2020-01-09 18:27:03.560549576 -0500

@@ -5,7 +5,7 @@

client

dev tun

proto tcp

-remote 192.55.48.241 443

+remote 146.152.204.133 443

resolv-retry infinite

auth-nocache

nobind

 

The lab is accessible, but there is a firewall update that Intel IT is working on to allow VMs to communicate with the Internet.   I’ll send out a follow up email when the firewall rules have been updated.

 

Br,

- Stephen

 

Stephen Gooch | Solutions Engineering | Wind River

+1.510.965.7909 , Skype ID: stephen.gooch