HANA 1909 trial using IPV6 ?

[abo]

Hello.

The goal is enabling IPV6 support for the current HANA 1909 trial on a Linux host.

In a way, this is a followup to my earlier question on adding IPV6 support to the previous trial edition.

What I have tried:

• I have modified /etc/docker/daemon.json
• I have added the SAP_IPv6_ACTIVE variable in a few places: /home/a4hadm/.cshrc , /etc/profile.local , /hana/shared/HDB/HDB02/hdbenv.sh , /hana/shared/HDB/HDB02/hdbenv.csh

The situation so far: HANA still works but port 3200 is still only open on IPV4. I will deal with exposing ports from the container once I can get HANA to listen on IPV6. At least now the container has a valid IPV6 address from the assigned network.

Former Member has suggested "un-docking" but the big advantage of that approach seems to be mostly for Windows users, because Docker Desktop on Windows doesn't do IPV6, apparently 😉

So, no real urgency since I already have one trial system on IPV6 and I can use that one when needed, but .... what am I doing wrong? Or not doing, perhaps?

[Former Member]

Hi Andrea,

Having Basis experience the biggest advantage for me was the control over the system.

Second was the disk usage. I have many TBs free on HDDs but only few GBs on my SSD. Running it on SSD now is possible.

The rest, e.g. IPv6 or accessing the system from other hosts without the need to set NAT and port-forwarding , is a positive side effect.

Probably I'm totally wrong, but for me the Docker is a big ship with thousands container on it. Now we have a huge container, trying to put it on a small boot (developers computer).

[abo]

Different perspective, not a question of right or wrong: I'm running a limited amount of containers and resources on SSD (NVMe actually) are not an issue.

[abo]

Thank you for the checks, Robert!

I am aware of the different sh / csh syntax, for example this was one of my attempts:

Now I have again added "setenv SAP_IPv6_ACTIVE 1" to the end of /home/a4hadm/.cshrc, then saved, stopped and restarted the container.

My mistake was waaaaaaaaaaaaay more embarassing than a syntax mixup: I misinterpreted the netstat output when queried without an estabilished connection! I've added an alias for the container IPV6 address and tried connecting: it worked. And it was probably working from the beginning 🙂