Hi all,
In the run up to getting our CTA instance up and running on real hardware, I wanted to double check I wasn’t missing anything for the IPv6 side of things.
As far as I can tell, a dual-stack CTA instance only needs to have EOS nodes (MGMs + FSTs) accessible over IPv6, and there is no requirement for any of the CTA nodes to be dual-stack. Have I missed something?
Thanks,
Tom
Hi Tom,
You are correct : CTA communicates directly with the MGMs and FSTs, and the CTA frontend/tape servers don’t need to be exposed to the outside world.
The only other channel which communicates directly with the frontend is the cta-admin tool, but it is envisaged that this will run on the local network.
Cheers,
Michael
So currently cta-frontend and cta-cli still don’t support IPv4 protocol?
I’m not sure I understand the question. cta-frontend and cta-cli support whatever protocol is configured on the host where they are installed (IPv4 or IPv6).
Yeah. Your are right. I made a mistake. I just run the frontend with podman and the network doesn’t enable ipv6 by default…