> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/run-the-platform/nas/nas-service.md). # Add a NAS Service The NAS feature provides file-level storage/access within a VergeOS system. NAS functionality can be added by downloading and implementing an instance of the standard NAS VM Recipe. ## Implement an Instance of the NAS VM Recipe 1. From the Cloud Dashboard, select **NAS** from the left menu. 2. Select **NAS Services** from the left menu. 3. Select **New** from the left menu. 4. If the Recipe requires a download: a message will appear including a download link; **Click the Link to download** the NAS VM Recipe. Select **Download** from the left menu. Click the **Yes** button to Confirm downloading this VM Recipe. The status will display as "Downloading" while it is in progress. When the download is complete, the status will display "Online" and the "Downloaded" checkbox will display as checked. 5. Enter a ***Name*** for the new NAS Service.

The New NAS Service will be a VM; therefore it cannot have a name that is in use by another VM in the same VergeOS Cloud.

6. The default setting for ***Cores*** is 4; this setting is suitable for typical, general-purpose NAS workloads. Heavy antivirus operations and/or frequent sync activity may affect core needs.

There can be many factors involved in NAS Service resource needs; consult VergeOS Implementation Services or VergeOS Support if guidance is needed.

7. The default setting for ***RAM*** is 4 GB; this setting is suitable for typical, general-purpose NAS workloads. Heavy file caching operations can affect RAM needs. 8. The system-defined-default ***Cluster*** is automatically selected. If desired, a different Cluster can be selected on which to run the NAS Service. 9. Select the ***Network*** on which the NAS should run. * Options will include Internal and External networks defined in this VergeOS Cloud. 10. Select ***IP Address Type*** for the NAS Service. Options include **DHCP** and **Static** * If the NAS service is hosted on a VergeOS Internal network, it is generally recommended that you select DHCP and define a static IP address for the NAS VM within the network's IP settings. * For networks controlled externally, Static vs DHCP would be selected, depending upon factors of the particular network. * When utilizing DHCP, it is recommended to configure a static reservation so that the IP address will remain constant. * When utilizing a Static address, care should be used to avoid conflicting with other static IP addresses or DHCP lease scope * When **Static** is selected, ***IP Address***, ***Gateway***, and ***DNS Server list*** should also be specified. 11. Define a ***Hostname*** for the NAS Service VM. (Hostname defaults to "nas") {% hint style="success" %} **Hostname tips:** * Typically, it is best to use the same value for *Hostname* and *Name* to avoid confusion in future administration. * When a NAS service is joined to a Windows AD Domain, the computer object will appear with its hostname (rather than NAS name) in AD Computers and Users. {% endhint %} 12. Enter a ***domain (optional).*** CIFS/Samba functionality will require a domain. If the Domain field is left blank, the system will default the domain to "workgroup". If the NAS Service will be used to serve out CIFS shares, the AD Domain in use should be specified. 13. ***Timezone*** will default to the default time zone for the VergeOS Cloud. If needed, a different timezone can be defined for the NAS Service. 14. Generally, the **default** ***NTP Servers*** setting is recommended. This defines the Network Time Protocol(NTP) servers list (used for keeping the NAS service time synchronized.) If needed, the default NTP server list can be overridden, in order to explicitly define the NTP server list to be used. 15. (Optional) Enter the address of a ***Remote Syslog server.*** 16. (Optional) Enter a ***Remote Syslog Template.*** 17. Click **Submit** to save the settings and create the New NAS Service. 18. The new NAS will now appear in the **NAS Service list**. **Double-click the Service** within the list to bring up the Dashboard for the Service. 19. Select **Power On** from the left menu to start the NAS. 20. Click the **Yes** button to confirm power on. 21. To utilize the NAS service, at least one **Volume** will need to be implemented. Information regarding Volumes along with links to instructional pages provided below. ## Volumes A NAS service will consist of one or more volumes. Each volume is a separate directory structure with its own settings for security, snapshots, storage tier, max size, antivirus, and sharing. * **Local Volumes** are file systems stored within VergeOS and consume storage in the VergeOS vSAN. See [**NAS Local Volumes**](/run-the-platform/nas/nas-local-volumes.md) for instructions on creating Local Volumes. * **Remote Volumes** are external file systems that are mounted to the VergeOS system and presented as if local. See [**NAS Remote Volumes**](/run-the-platform/nas/nas-remote-volumes.md) for instructions on creating Local Volumes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.vergeos-demo.com/run-the-platform/nas/nas-service.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.