This post explains how to resolve issues where the VxRail Deployment Wizard fails to load or the VMware Marvin service does not start because of an IPv6 address conflict.

Troubleshooting command for startup failures, crashes, or runtime issues with the VMware Marvin component:

journalctl -xeu vmware-marvin.service

On the vxrail manager in /var/log/messages there are events indicating a duplicate IPv6 address is detected & kubernates fails to deploy:

cat /var/log/messages | grep "IPv6 duplicate address"

A duplicate IPv6 address on VxRail Manager will absolutely cause Kubernetes (including the internal “marvin” service) to fail during deployment or bring-up, because several internal components rely on stable IPv6 addressing for etcd, Kubernetes pods, and service mesh communications.

systemctl status runjars.service

systemctl status vmware-marvin.service

Modify the IPV6 address on VxRail Manager (SUSE-based OS) using:

vi /etc/sysconfig/network/ifcfg-eth0

IPADDR0=’fd39:3939:3939:3939::180‘

Save & exit :wq!

systemctl restart network

Reboot VXRM.

After ~10 minutes check that kubernates “helium” pods havd been deployed:

• kubectl get pods
• kubectl get pods -A
• kubectl get pods -o wide
• kubectl get deployments

Confirm services are active or start if not:

systemctl status runjars.service
systemctl status vmware-marvin.service
systemctl start vmware-marvin
systemctl start runjars