Need networking help with hdp sandbox for vmware ovf

[#1]

Hi, first time using the sandbox 2.6.4

( I am extremely new to docker, but more familiar with vmware )

Recently, I tried to learn/test a backup product.

Environment:

===========

But before that, I notice the difference of ssh -p 2222 vs standard ssh

e.g.

ssh -p 2222

==========

[root@sandbox-hdp network-scripts]# ifconfig -a

eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:02

inet addr:172.17.0.2 Bcast:172.17.255.255 Mask:255.255.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1650387 errors:0 dropped:0 overruns:0 frame:0

TX packets:1557340 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

RX bytes:955319881 (911.0 MiB) TX bytes:726520084 (692.8 MiB)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:35792271 errors:0 dropped:0 overruns:0 frame:0

TX packets:35792271 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:23574288126 (21.9 GiB) TX bytes:23574288126 (21.9 GiB)

standard ssh

===========

[root@sandbox-host network-scripts]# ifconfig -a

docker0

Link encap:Ethernet HWaddr 02:42:8A:0F:5C:DD

inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0

inet6 addr: fe80::42:8aff:fe0f:5cdd/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1557361 errors:0 dropped:0 overruns:0 frame:0

TX packets:1650404 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

RX bytes:704727380 (672.0 MiB) TX bytes:955327389 (911.0 MiB)

ens32

Link encap:Ethernet HWaddr 00:0C:29:8C:91:1D

inet addr:128.222.110.164 Bcast:128.222.110.255 Mask:255.255.255.0

inet6 addr: fe80::20c:29ff:fe8c:911d/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1289914 errors:0 dropped:0 overruns:0 frame:0

TX packets:572090 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 406562254 (387.7 MiB)

lo

Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:383 errors:0 dropped:0 overruns:0 frame:0

TX packets:383 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1

RX bytes:37548 (36.6 KiB) TX bytes:37548 (36.6 KiB)

vethda55ac8

Link encap:Ethernet HWaddr EA:46:30:49:97:B3

inet6 addr: fe80::e846:30ff:fe49:97b3/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1557361 errors:0 dropped:0 overruns:0 frame:0

TX packets:1650412 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

RX bytes:726530434 (692.8 MiB) TX bytes:955328037 (911.0 MiB)

Symptom

========

After I installed a service called HDBoost service.

I was able to telnet to service port 18043 using ip 172.17.0.2

[root@sandbox-hdp ~]# telnet 172.17.0.2 18043

Trying 172.17.0.2...

Connected to 172.17.0.2.

Escape character is '^]'.

But when telnet to 128.222.110.164 I am not able to make a connection.

I cannot keep using 172.17.0.2 because I need to access it remotely from my work pc desktop which uses 128.222.110.0 subnet.

Please kindly help if you know an answer or work around.

[#2]

should I try to add an additional interface at the vmware level and configure an extra ip e.g. 128.222.110.247 ? ( I am not sure how it will show up on docker layer )

[#3 · Accepted solution]

Hey @PiAiYi

I'm a bit confused as to what you're trying to do. I'll explain a bit how the sandbox is set up and hopefully that provides a bit of context into the IPs that are in play.

When you ssh using port 22, you'll notice the hostname of the machine you log into is set to "sandbox-host". This hosts main job is to provide an environment for a Docker container (if you're new to Docker, no worries). There is a second VM (the Docker container) inside of this sandbox-host machine.

When you ssh using port 2222, you are logging into the second VM (with hostname sandbox-hdp), which again, is a VM inside the sandbox-host machine. When you play with the sandbox (Ambari, HBase, Hive, etc.), all those services are in this second VM (sandbox-hdp).

So when you are within the sandbox-hdp machine, you can ping 172.17.0.2 because that is it's own IP.

The reason you may be having trouble pinging 128.222... is because that is the IP address of the outside VM. For security (and other) reasons, you're not able to ping outside machines in this way by default. What is it you're trying to do? There might be another approach we can suggest.

[#4]

This is what I try to do , I have a deduplication appliance on the subnet 128.222.110.250

This appliance cannot talk directly to 172.17.0.2 which is a huge problem, means I could not test the backup.

If this is pure vmware environment it would be easy, all I have to do is add an interface and configure that interface to use same subnet as 128.222.110.0

But with the docker thing, which I am fairly new, I am not sure how to proceed from there . this is the crux of my problem.