# Setting Up Cache Services

Request a Connected Cache node from CCM IT, then review the local provisioning sequence. The source requires the hostname, cache mount path and size, plus scripts and a command supplied in response to the ticket.

!!!warning Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
!!!

## Configure a Node in Azure

1.  Submit a ticket to CCM IT requesting Microsoft Connected Cache node configuration. You must supply the following:
2.  Server Hostname
3.  Mount Path of the MCCData Disk. (e.g. /mnt/mccdata)
4.  Size in GB Cache Disk Size. (e.g. 500GB)
5.  A Zip file – \<school code\>\_mccscripts.zip and a provisioning command to execute will be sent in response to the ticket.

## Configure the Local Cache Server

1.  Copy the zip file to the cache server /tmp; it will not be needed after installation is complete.
2.  scp \<path to downloaded zip file\> \<user@CacheServer_ip\>:/tmp
3.  SSH to the local server
4.  ssh \<user@CacheServer_ip\>
5.  Unzip \<school code\>\_mccscripts.zip. You will need to install unzip on a new server.
6.  sudo apt install unzip
7.  cd /tmp
8.  unzip mccscripts_duncc.zip
9.  It unzips to a new folder in /tmp called MccScripts.
10. Make all scripts executable.
11. Cd into MccScripts folder (case sensitive)
12. sudo chmod +x \*.sh
13. Run the provisioning command provided in your ticket respone. E.g.
14. sudo ./provisionmcc.sh customerid="customerid" cachenodeid="cachenodeid" customerkey="customerkey" registrationkey="registrationkey" drivepathandsizeingb="/mnt/mccdata,465"
15. Wait at least 30 minutes for the system to fully download, install and configure the cache services.

## Related guidance

- [Topic overview](Introduction.md)
- [Source review status](../../review/Review-status.md)