rpcbind.socket will not start with IPv6 disabled and as a result storage pool may not be online once the Hyperscale node is rebooted. In such situations disable the IPv6 communication.
Procedure
-
Set the MediaAgents associated with the nodes in the Maintenance mode. For more information, see Setting the MediaAgent on Maintenance Mode.
-
If IPv6 was already enabled as described in Enabling IPv6 Communication on HyperScale Nodes, make sure to revert the changes in the appropriate
ifcfg-*files. -
Add the following entry in
/etc/sysctl.conffile.net.ipv6.conf.all.disable_ipv6 = 1 -
Rebuild the initial ramdisk image ( initrd or initramfs) using the following command to incorporate the changes made to
/etc/sysctl.confinto the initramfs.dracut -v -f -
Stop the HyperScale cluster on the node. For more information, see Stopping and Starting the Cluster.
-
Restart the node. For more information, see Stopping and Starting a Node.
You will see the rpcbind.socket running with IPV6 in disabled state.
-
Repeat steps 2 to 6 on the other nodes in the storage pool.
-
Disable IPv6 communication in the MediaAgents associated with the nodes. For more information, see Enabling CommCell Communication Using IPv6 After Installation.
-
Restart the services on both the CommServe and the MediaAgent nodes after setting the registry keys. For more information, see Restarting Services on a File Server or a Server.
-
Ping and check network connectivity between the CommServe server and the MediaAgent nodes.
-
Perform a readiness check to the MediaAgent nodes. For more information, see Checking Readiness.
-
Remove the Maintenance mode from the MediaAgents. For more information, see Setting the MediaAgent on Maintenance Mode.