Deploy Global File Cache Edge instances

Contributors netapp-tonacki

After you have verified that your environment meets all the requirements, you install Global File Cache Edge software in each remote office.

Before you begin

To complete Global File Cache Edge configuration tasks, you need the following information:

  • Static IP addresses for each Global File Cache instance

  • Subnet mask

  • Gateway IP address

  • The FQDN you wish to assign to each Global File Cache server

  • The DNS suffix (optional)

  • The user name and password of an administrative user in the domain

  • The FQDN and/or IP address of the associated Core servers

  • A volume to be used as the Intelligent File Cache. It is recommended this be at least 2x the size of the active dataset. This should be formatted as NTFS and assigned as D:\.

Commonly used TCP ports

There are several TCP ports used by Global File Cache services. It is mandatory that the devices can communicate on these ports and they be excluded from any WAN optimization devices or firewall restriction policies:

  • Global File Cache Licensing TCP Port: 443

  • Global File Cache TCP Ports: 6618-6630

Deploy the Global File Cache Virtual Template

The virtual template (.OVA and .VHD) images contain the latest release of the Global File Cache software. If you are deploying Global File Cache using the .OVA or .VHD virtual machine (VM) template, follow the steps as outlined in this section. It is assumed that you understand how to deploy the .OVA or .VHD template on the designated hypervisor platform.

Ensure that VM preferences, including resource reservations, are in line with the requirements as outlined in Virtual deployment requirements.

  1. Extract the package from the template you downloaded.

  2. Deploy the virtual template. Refer to the following videos before you start the deployment:

  3. After the Virtual Template has been deployed, and you have configured the VM settings, start the VM.

  4. During initial boot, when the Windows Server 2016 or 2019 operating system is preparing for first use, complete the out-of-the-box experience by installing the correct drivers and installing the necessary components for the respective hardware.

  5. When the base install of the Global File Cache Edge instance has been completed, the Windows Server 2016 or 2019 operating system will guide you through an initial configuration wizard to configure operating system specifics such as localization and product key.

  6. After the initial configuration wizard has completed, log in locally to the Windows Server 2016 or 2019 operating system with the following credentials:

    • User name: FASTAdmin

    • Password: Tal0nFAST!

  7. Configure your Windows Server VM, join to the organization’s Active Directory domain, and proceed to the Global File Cache Edge configuration section.

Configure the Global File Cache Edge instance

The Global File Cache Edge instance connects to a Global File Cache Core to provide users at the branch office access to data center file server resources.

Note The Edge instance must be licensed as part of your Cloud Volumes ONTAP deployment prior to beginning the configuration. See Licensing for more information about licensing.

If your configuration requires more than one Global File Cache Core to be installed because of a large number of Edge instances, you will configure some Edge instances to connect to the first Core and others to connect to the second Core. Make sure you have the FQDN or IP address, and other required information, for the correct Core instance.

To configure the Edge instance, complete the following steps:

  1. Click Perform next to the unchecked Core Configuration step listed in the "Edge Configuration Steps" section of the Initial Configuration assistant. This opens a new tab, GFC Edge, and shows the section Core Instances.

  2. Provide the Cloud Fabric ID of the Global File Cache Core server. The Cloud Fabric ID is typically the NetBIOS name or the geographical location of the backend file server.

  3. Provide the FQDN/IP Address of the Global File Cache Core server:

    1. (Optional) Check the SSL box to enable SSL support for enhanced encryption from the Edge to the Core.

    2. Enter the User Name and Password, which are the credentials of the Service Account used on the Core.

  4. Click Add to confirm the addition of the Global File Cache Core appliance. A confirmation box will appear. Click OK to dismiss it.

    A screenshot showing the Edge entries that identify the Global File Cache Core that will be used.

Update Global File Cache Edge software

Global File Cache frequently releases updates to the software, either patches, enhancements, or new features/functionality. Although the virtual template (.OVA and .VHD) images contain the latest release of the Global File Cache software, it is possible that a newer version is available on the NetApp Support Download portal.

Ensure that your Global File Cache instances are up to date with the latest version.

Note This software package can also be used for pristine installations on Microsoft Windows Server 2016 Standard or Datacenter edition, or Windows Server 2019 Standard or Datacenter edition, or used as part of your upgrade strategy.

Below you can find the steps required to update the Global File Cache installation package:

  1. After saving the latest installation package to the desired Windows Server instance, double-click it to run the installation executable.

  2. Click Next to continue the process.

  3. Click Next to continue.

  4. Accept the Licensing Agreement and click Next.

  5. Select the desired Installation Destination Location.

    NetApp recommends that you use the default installation location.

  6. Click Next to continue.

  7. Select the Start Menu Folder.

  8. Click Next to continue.

  9. Verify your installation selections and click Install to begin the installation.

    The installation process will start.

  10. After the installation has completed, reboot the server when prompted.

What’s Next?

For details about Global File Cache Edge advanced configuration, see the NetApp Global File Cache User Guide.