OmniCube for vSphere Client Administrator Guide 5 Federation Management Changing the Network Configuration for a Federation Contact SimpliVity Technical Support or your support provider if you need to change IP addresses and subnet masks used by all OmniCube systems in a Federation, including: + vCenter Server IP address and subnet netmask. + OmniCube ESXi Host IP address and subnet netmask. + OmniCube Federation, Storage, or Management IP addresses and subnet netmasks, You might also need to change the IP address of non-Federation hosts that access your Federation. See: Changing the IP Address on a Non-SimpliVity ESXi Host on page 114. Overview of OmniCube IP Address Changes Changing IP addresses is most likely to arise during a datacenter reorganization or upgrade. This will be a carefully scheduled operation, probably involving Federation down time, Typical reasons for changing OmmiCube IP addresses are + Network changes that affect the entire datacenter, including subnet netmask changes. + Moving one OmniCube from a Federation to a different network, + Moving the VMware datacenter to a different network. Changing the IP Address on a Non-SimpliVity ESXi Host ‘You can share SimpliVity datastores with Non-SimpliVity ESXi host using the svt—cata: CLI command, Allowing Datastore Access to Non-Federation ESXi Hosts on page 161 If you change the IP address on a Non-SimpliVity ESXi host, you must update your Federation to recognize the new IP address. This operation causes shared data to be unavailable for a short time. ‘Method A: Add a new VMkernel NIC ‘An existing shared-datastore Non-SimpliVity ESXi host has NFS exports for each interface of the Non ‘SimpliVity ESXi host on each OmniCube in the datacenter containing the datastore, 1. Add another VMKernel NIC configured with the new IP address for the Non-SimpliVity ESXi host. 2. Use the svt-datastore-shaze CLI command to crea e NFS exports for the new VMKernel NIC. 3. Delete the original VMKernel NIC, which used the old IP address. 14