Merge pull request #6 from amymzhou/nidos_working

Nidos working

windows/deployment/do/mcc-isp-create.md

@@ -24,7 +24,8 @@ ms.topic: article
 <br/>
 
 > [!IMPORTANT]  
-> Before you can create your Microsoft Connected Cache, you will need to complete the sign up process here.
+
+> Before you can create your Microsoft Connected Cache, you will need to complete the sign up process [here](windows\deployment\do\mcc-isp-signup.md).
 
 <br/>
 <br/>
@@ -33,5 +34,22 @@ ms.topic: article
 <br/>
 
 
+1. Navigate to 'Cache nodes' under Settings and click 'Create Cache Node'.
+
+<br/>
+ :::image type="content" source="images/createcachenode.png" alt-text="createcachenode":::
+<br/>
+
+<br/>
+
+2. Provide a name for your cache node and click 'Create' to create your cache node.
+<br/>
+
+:::image type="content" source="images/cachenodename.png" alt-text="cachenodename":::
+
+<br/>
+
+Once your cache node is created follow the instructions on [Provisioning and Deploying MCC](windows\deployment\do\mcc-isp-provision-deploy.md) to provision and deploy the cache node.
+
 
 

windows/deployment/do/mcc-isp-faq.md

@@ -27,7 +27,7 @@ Yes. Microsoft Connected Cache is a free service.
 
 <br/>
 	
-**2. What will MCC do for me? How will it impact our customers?**  
+**2. What will Microsoft Connected Cache do for me? How will it impact our customers?**  
 As an ISP, your network can benefit from reduced load on your backbone and improve customer download experience for supported Microsoft static content. It will also help you save on CDN costs.  
 
 <br/>

windows/deployment/do/mcc-isp-provision-deploy.md

@@ -23,8 +23,66 @@ ms.topic: article
 
 <br/>
 
-## Provision Cache Node
-<br/>
 
 > [!IMPORTANT]  
-> Before you can create your MCC, you will need to complete the sign up process.
+> Before you can provision and deploy your cache node, you will need to complete the sign up process [here](windows\deployment\do\mcc-isp-signup.md) and create a cache node [here](windows\deployment\do\mcc-isp-create.md).
+
+<br/>
+
+## Provisioning cache node
+
+1. Click on the cache node you want to provision and deploy.  
+<br/> 
+:::image type="content" source="images/cachenodecreated.png" alt-text="cachenodecreated":::
+<br/>
+<br/>
+
+1. Enter the max allowable egress that your hardware can support.  
+<br/> 
+:::image type="content" source="images/cachenodeconfig.png" alt-text="cachenodeconfig":::
+<br/>
+<br/>
+
+3. Under Cache storage, specify the location of the cache drives to store content along with the size of the cache drives in Gigabytes.  
+You can add upto nine cache drives.  
+<br/>
+:::image type="content" source="images/cachenodeconfig.png" alt-text="cachenodeconfig":::
+<br/>
+<br/>
+4. Under Routing information, select the routing source you would like to use. For more information see client routing [here](windows\deployment\do\mcc-isp-client-routing.md).  
+<br/>
+    - If you choose Manual routing, enter Address range/CIDR blocks and the number of IP space.  
+<br/>
+:::image type="content" source="images/cachenodeconfig.png" alt-text="cachenodeconfig":::
+<br/>
+<br/>
+    - If you choose BGP routing, enter the ASN and IP addresses of the neighborship.  
+<br/>
+:::image type="content" source="images/bgp.png" alt-text="bgp":::
+<br/>
+<br/>
+ 
+5. Under Server provisioning, you will see a provisioning script for your cache node.  
+Download this script to your server.
+<br/>
+:::image type="content" source="images/cachenodeprovisioning.png" alt-text="cachenodeprovision":::
+
+<br/>
+
+6. Open a terminal window and run the following command to change the access permission to the Bash script.  
+<br/>
+
+    ```bash
+    sudo chmod +x installmcc.sh
+    ```
+<br/>
+<br/>
+
+7. Run the provisioning script that is shown for your cache node.  
+<br/>
+:::image type="content" source="images/cachenodeprovisioning.png" alt-text="cachenodeprovision":::
+<br/>
+<br/>
+
+8. If there were no errors, you have set up your cache node. To verify the server is set up correctly, follow the steps verification steps [here](windows\deployment\do\mcc-isp-verify-cache-node.md).
+

windows/deployment/do/mcc-isp-signup.md

@@ -28,8 +28,10 @@ ms.topic: article
 
 <br/>
 
-1. Search for 'Microsoft Connected Cache' and go through the process of creating a resource by selecting the region and enter a name for your Cache resource name. 
+1. Search for 'Microsoft Connected Cache' and go through the process of creating a resource by selecting the region and enter a name for your cache resource name.  
-<pic>
+
+:::image type="content" source="images/searchmcc.png" alt-text="searchmcc":::
+
 
 <br/>
 
@@ -40,12 +42,17 @@ After your resource has been created, we need some information to verify you net
 <br/>
 
 2. Add your organization ASN below. The NOC contact email will be used to send verification information. Additionally, please include any ASN(s) for downstream network operators that you may transit traffic for.  
-<pic>
 
-1. Once we verify the information entered, a verification code will be sent to the NOC email address provided on Peering DB. In the Azure portal operator verification blade enter the verification code sent to the NOC email address.  
+:::image type="content" source="images/signup1.png" alt-text="sign up for mcc":::
-**TBD Note:** The verification code will expire in 24 hours. You will need to generate a new code if it expires.
+
-<pic>
+<br/>
+
+3.  Once we verify the information entered, a verification code will be sent to the NOC email address provided on Peering DB. In the Azure portal operator verification blade enter the verification code sent to the NOC email address.  
+**Note:** The verification code will expire in 24 hours. You will need to generate a new code if it expires.  
+
+:::image type="content" source="images/verification.png" alt-text="operatorverification":::
 
 <br/>
 <br/>
-Once verified follow the instruction on [Provisioning and Deploying MCC] to create and install the cache node.
+Once verified follow the instruction on [Create Microsoft Connected Cache for ISP](windows\deployment\do\mcc-isp-create.md) to create your cache node.
+

windows/deployment/do/mcc-isp-uninstall.md

@@ -14,7 +14,6 @@ Within Azure portal, navigate to **Cache Nodes**, then select the cache node you
 ## Run the uninstall script to cleanly remove MCC from your server
 In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Only run it if you're facing issues with MCC installation.
 
-
 The **uninstallmcc.sh** script removes the following components:
 
 - IoT Edge

windows/deployment/do/mcc-isp-verify-cache-node.md

@@ -1,6 +1,5 @@
 # Verify cache node functionality
 
-
 ### Verify functionality on Azure portal
 
 Log into Azure portal and navigate to the Overview page. Select the **Monitoring** tab to verify the functionality of your server(s) by validating the number of healthy nodes shown. If you see any **Unhealthy nodes**, select the "Diagnose and Solve" link to troubleshoot and resolve the issue.
@@ -9,7 +8,6 @@ Log into Azure portal and navigate to the Overview page. Select the **Monitoring
 
 It can take a few minutes for the container to deploy after you've saved the configuration.
 
-
 To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `<CacheServerIP>` with the IP address of the cache server.
 
 ```bash