Print Email PDF

Configuring IPv6 in Qumulo Core


  • Cluster running Qumulo Core version 2.6.2 and higher
  • Command line (CLI) tools installed via API & Tools tab


Qumulo Core can be configured for IPv6 networks using the qq CLI or the REST API to set the default gateway and MTU on the interface. 

  1. Specify a default gateway for both IPv6 and IPv4 traffic. Note that the IPv4 gateway is required to connect to Qumulo's cloud-based monitoring service.
    qq network_mod_interface --default-gateway \
      --default-gateway-ipv6 fe80::97:483f:234d:1e2c --mtu 1500
  1. Modify the configuration of the default network to specify IPv6 addresses for the cluster. IPv6 networks can have subnets specified using CIDR notation or standard netmask (for example, 2001:DB8/32 or ffff:ffff:ffff:ffff::).

    qq network_mod_network --network-id 1 \
      --assigned-by STATIC --netmask fdd9:bae6:81bb:fe7b::/64 \
      --ip-ranges fdd9:bae6:81bb:fe7b:0:b034:8850:0-9 \
      --floating-ip-range fdd9:bae6:81bb:fe7b:0:b034:8850:10-19 \
      --dns-servers fdd9:bae6:81bb:fe7b:0:b016:0:c084 \
      fdd9:bae6:81bb:fe7b:0:b05b:0:9864 \
  1. Verify the configuration and view which IP addresses were assigned using the following qq command.
    qq network_poll

Client machines can now mount to the cluster using the floating IPv6 addresses.

Additional Verification

Once enabled, you can check IPv6 accessibility by pinging the cluster and checking the protocol access using the following commands:

  • Windows ping
    ping fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx
    Pinging fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx with 32 bytes of data:
    Reply from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: time<1ms
    Reply from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: time<1ms
    Reply from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: time<1ms
    Reply from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: time<1ms
  • Unix using ping6 vs ping (IPv4 only)
    ping6 fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx
    PING fd00:90d:c0de:1:9d1:e99d:ca1e:57f7(fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx)
    56 data bytes
    64 bytes from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: icmp_seq=1 ttl=64 time=0.641 ms
    64 bytes from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: icmp_seq=2 ttl=64 time=0.374 ms
    64 bytes from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: icmp_seq=3 ttl=64 time=0.466 ms
    64 bytes from fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx: icmp_seq=4 ttl=64 time=0.608 ms
    --- fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3078ms
    rtt min/avg/max/mdev = 0.374/0.522/0.641/0.109 ms
  • SMB protocol
    net view \\<unc-path>
    Shared resources at \\<unc-path>
    Qumulo Share name Type Used as Comment
    Files Disk
    mixed Disk
    The command completed successfully.
  • NFS protocol
    showmount -e fd00:90d:c0de:1:9d1:e99d:ca1e:xxxx
    Export list for fd00:90d:c0de:1:9d1:e99d:ca1e:xxx:
    / (everyone)
    /home (everyone)
    /root (everyone)

Note: Consider the following when using IPv6 with Qumulo Core:

  • The Web UI displays the network configuration but you must use qq CLI or REST API to edit this configuration.
  • The Web UI doesn't display the IPv6 default gateway.
  • Like for IPv4, you can configure one IPv6 untagged network (VLAN 0) or many tagged networks (VLAN 1-4094) statically.
  • You can configure an IPv4 network alongside an IPv6 network on any VLAN.
  • Currently, Qumulo Core doesn't support VPN connections through IPv6 configurations.
    Important: This behavior doesn't affect MissionQ functionality or configuration.
Was this article helpful?
1 out of 1 found this helpful



Please sign in to leave a comment.

Have more questions?
Open a Case
Share it, if you like it.