Merge pull request #134436 from ekpgh/fxt-update-security

Add recommendation & instructions for BIOS setup password

Author: v-shmck

articles/fxt-edge-filer/fxt-add-nodes.md

@@ -10,19 +10,20 @@ ms.date: 06/20/2019
 
 # Tutorial: Add cluster nodes to an Azure FXT Edge Filer cluster
 
-A new Azure FXT Edge Filer cluster is created with only one node. You should add at least two more nodes and enable high availability before doing other configuration. 
+A new Azure FXT Edge Filer cluster is created with only one node. You should add at least two more nodes and enable high availability before doing other configuration.
 
-This tutorial explains how to add cluster nodes and enable the High Availability (HA) feature. 
+This tutorial explains how to add cluster nodes and enable the High Availability (HA) feature.
 
-In this tutorial, you will learn: 
+In this tutorial, you will learn:
 
 > [!div class="checklist"]
+>
 > * How to add nodes to the FXT cluster
 > * How to enable HA
 
 The steps in this tutorial take approximately 45 minutes to complete.
 
-Before you start this tutorial, power on the nodes that you want to add and [set their initial passwords](fxt-node-password.md). 
+Before you start this tutorial, power on the nodes that you want to add and [set their initial passwords](fxt-node-password.md).
 
 ## 1. Load the Cluster Nodes page
 
@@ -42,19 +43,19 @@ To add nodes, click the **Settings** tab and choose the **FXT Nodes** page in th
 
 The **FXT Nodes - Unjoined** list shows all unassigned FXT nodes (most data centers have only a few. Find the FXT nodes that you want to add to the cluster.
 
-> [!Tip] 
+> [!Tip]
 > If you cannot find the node you want on the **Unjoined** list, check that it meets these requirements:
-> 
+>
 > * It is powered on and has had a [root password set](fxt-node-password.md).
 > * It is connected to a network you can access. If you use VLANs , it must be on the same VLAN as the cluster.
-> * It can be detected with the Bonjour protocol. 
+> * It can be detected with the Bonjour protocol.
 >
 >   Some firewall settings block the TCP/UDP ports used by Bonjour, which prevents the FXT operating system from automatically detecting the nodes.
-> 
-> If the node that you want to add isn’t on the list, try these solutions: 
-> 
+>
+> If the node that you want to add isn’t on the list, try these solutions:
+>
 > * Click the **Manual Discover** button to find it by IP address.
-> 
+>
 > * Manually assign temporary IP addresses. This is rare but might be needed if you use tagged VLANs and the nodes are not on the correct network, or your network does not allow self-assigned IP addresses. Follow the instructions in the legacy version of this document to [manually set a static IP address](https://azure.github.io/Avere/legacy/create_cluster/4_8/html/static_ip.html).
 
 The node name, IP address, software version, and eligibility status are displayed in the list. Typically, the **Status** column either says “Wants to join” or describes a system or hardware problem that makes the node ineligible to join the cluster.
@@ -65,44 +66,43 @@ All of the nodes in a cluster must use the same version of the OS, but you don
 
 To learn more about the options on this page, read [**Cluster** > **FXT Nodes**](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gui_fxt_nodes.html) in the Cluster Configuration Guide.
 
-## 3. Click the "Allow to Join" button 
+## 3. Click the "Allow to Join" button
 
 Click the **Allow To Join*** button in the **Actions** column for the node that you want to add.
 
-After you click the button, the node's status might change as its software is updated in preparation for adding it to the cluster. 
+After you click the button, the node's status might change as its software is updated in preparation for adding it to the cluster.
 
 The image below shows a node that is in the process of joining the cluster (most likely, it’s getting an OS update before being added). No buttons appear in the **Actions** column for nodes that are in the process of being added to the cluster.
 
 ![one row of the node table, showing a node's name, IP address, software version, the message "Allowed to join", and a blank last column](media/fxt-cluster-config/node-join-in-process.png)
 
-After a few moments, the new node should appear in the list of cluster nodes at the top of the **FXT Nodes** settings page. 
+After a few moments, the new node should appear in the list of cluster nodes at the top of the **FXT Nodes** settings page.
 
 Repeat this process to add the other nodes to your cluster. You don’t need to wait for one node to finish joining the cluster before starting another.
 
 ## Enable High Availability
 
-After you’ve added a second node to your cluster, you might see a warning message on the control panel Dashboard that the high availability feature is not configured. 
+After you’ve added a second node to your cluster, you might see a warning message on the control panel Dashboard that the high availability feature is not configured.
 
 High availability (HA) allows the cluster nodes to compensate for each other if one goes down. HA is not enabled by default.
 
 ![Dashboard tab with the message "The cluster has more than one node, but HA is not enabled ..." in the Conditions table](media/fxt-cluster-config/no-ha-2-nodes.png)
 
-> [!Note] 
+> [!Note]
 > Do not enable HA until you have at least three nodes in the cluster.
 
-Follow this procedure to turn on HA: 
+Follow this procedure to turn on HA:
 
 1. Load the **High Availability** page in the **Cluster** section of the **Settings** tab.
 
    ![HA configuration page (Cluster > High Availability). The "Enable HA" checkbox is at the top and the submit button is at the bottom.](media/fxt-cluster-config/enable-ha.png)
 
-2. Click the box labeled **Enable HA** and click the **Submit** button. 
+2. Click the box labeled **Enable HA** and click the **Submit** button.
 
 An alert appears on the **Dashboard** to confirm that HA is enabled.
 
 ![Dashboard table showing the message "HA is now fully configured"](media/fxt-cluster-config/ha-configured-alert.png)
 
-
 ## Next steps
 
 After adding all of the nodes in your cluster, continue the setup by configuring your cluster's long-term storage.

articles/fxt-edge-filer/fxt-add-storage.md

@@ -8,35 +8,36 @@ ms.topic: tutorial
 ms.date: 06/20/2019
 ---
 
-# Tutorial: Add back-end storage and configure the virtual namespace 
+# Tutorial: Add back-end storage and configure the virtual namespace
 
-This tutorial explains how to add back-edge storage for your cache and how to set up the client-facing virtual filesystem. 
+This tutorial explains how to add back-edge storage for your cache and how to set up the client-facing virtual filesystem.
 
-The cluster connects to back-end storage systems to access the data clients request, and to store changes more permanently than in the cache. 
+The cluster connects to back-end storage systems to access the data clients request, and to store changes more permanently than in the cache.
 
-The namespace is the client-facing pseudo filesystem that allows you to swap out back-end storage without changing client-side workflows. 
+The namespace is the client-facing pseudo filesystem that allows you to swap out back-end storage without changing client-side workflows.
 
-In this tutorial you will learn: 
+In this tutorial you will learn:
 
 > [!div class="checklist"]
-> * How to add back-end storage to the Azure FXT Edge Filer cluster 
+>
+> * How to add back-end storage to the Azure FXT Edge Filer cluster
 > * How to define the client-facing path for storage
 
 ## About back-end storage
 
 The Azure FXT Edge Filer cluster uses a *core filer* definition to link a back-end storage system to the FXT cluster.
 
-Azure FXT Edge Filer is compatible with several popular NAS hardware systems, and can use empty containers from Azure Blob or other cloud storage. 
+Azure FXT Edge Filer is compatible with several popular NAS hardware systems, and can use empty containers from Azure Blob or other cloud storage.
 
 Cloud storage containers must be empty when added so that the FXT operating system can completely manage all of the data on the cloud storage volume. You can move your existing data to the cloud container after adding the container to the cluster as a core filer.
 
 Use the Control Panel to add a core filer to your system.
 
 > [!NOTE]
-> 
+>
 > If you want to use Amazon AWS or Google Cloud storage, you must install a FlashCloud<sup>TM</sup> feature license. Contact your Microsoft representative for a license key, and then follow the instructions in the legacy configuration guide for [Adding or removing feature licenses](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/install_licenses.html#install-licenses).
-> 
-> Support for Azure Blob storage is included in the Azure FXT Edge Filer software license. 
+>
+> Support for Azure Blob storage is included in the Azure FXT Edge Filer software license.
 
 For more detailed information about adding core filers, read these sections of the Cluster Configuration Guide:
 
@@ -54,7 +55,7 @@ Define a core filer by clicking the **Create** button on the **Core Filer** > **
 
 ![Clicking the create button above the list of core filers on the Manage Core Filers page](media/fxt-cluster-config/create-core-filer-button.png)
 
-The **Add New Core Filer** wizard walks you through the process of creating a core filer that links to your back-end storage. The Cluster Configuration Guide has step-by-step descriptions of the process, which is different for NFS/NAS storage and for cloud storage (links are above). 
+The **Add New Core Filer** wizard walks you through the process of creating a core filer that links to your back-end storage. The Cluster Configuration Guide has step-by-step descriptions of the process, which is different for NFS/NAS storage and for cloud storage (links are above).
 
 Subtasks include:
 
@@ -66,15 +67,15 @@ Subtasks include:
 
 * For NAS core filers, provide the fully qualified domain name (FQDN) or IP address. FQDN is recommended for all core filers, and required for SMB access.
 
-* Select a cache policy - The second page of the wizard lists the available cache policies for the new core filer. For details, read the [cache policies section of the Cluster Configuration Guide](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gui_manage_cache_policies.html). 
+* Select a cache policy - The second page of the wizard lists the available cache policies for the new core filer. For details, read the [cache policies section of the Cluster Configuration Guide](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gui_manage_cache_policies.html).
 
   ![Second page of a hardware NAS new core filer wizard; the Cache Policy drop-down menu is open, showing several disabled options and three valid cache policy options (bypass, read caching, and read/write caching).](media/fxt-cluster-config/new-nas-choose-cache-policy.png)
 
 * For cloud storage, you must specify the cloud service and access credentials, among other parameters. For details, read [Cloud service and protocol](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/new_core_filer_cloud.html#cloud-service-and-protocol) in the Cluster Configuration Guide.
 
-  ![Cloud core filer information in the New Core Filer wizard](media/fxt-cluster-config/new-core-filer-cloud3.png) 
+  ![Cloud core filer information in the New Core Filer wizard](media/fxt-cluster-config/new-core-filer-cloud3.png)
 
-  If you already have added cloud access credentials for this cluster, they appear in the list. Update and add credentials in the **Cluster** > **Cloud Credentials** settings page. 
+  If you already have added cloud access credentials for this cluster, they appear in the list. Update and add credentials in the **Cluster** > **Cloud Credentials** settings page.
 
 After filling in all of the required settings in the wizard, click the **Add Filer** button to submit the change.
 
@@ -86,14 +87,14 @@ The core filer in this screenshot is missing a vserver. You must link the core f
 
 ## Configure the namespace
 
-The Azure FXT Edge Filer cluster creates a virtual filesystem called the *cluster namespace* that simplifies client access to data stored on diverse back-end systems. Because clients request files using a virtual path, storage systems can be added or replaced without having to change the client workflow. 
+The Azure FXT Edge Filer cluster creates a virtual filesystem called the *cluster namespace* that simplifies client access to data stored on diverse back-end systems. Because clients request files using a virtual path, storage systems can be added or replaced without having to change the client workflow.
 
-The cluster namespace also lets you present cloud and NAS storage systems in a similar file structure. 
+The cluster namespace also lets you present cloud and NAS storage systems in a similar file structure.
 
-The cluster's vservers maintain the namespace and serving content to clients. There are two steps to create the cluster namespace: 
+The cluster's vservers maintain the namespace and serving content to clients. There are two steps to create the cluster namespace:
 
-1. Create a vserver 
-1. Set up junctions between the back-end storage systems and the client-facing filesystem paths 
+1. Create a vserver
+1. Set up junctions between the back-end storage systems and the client-facing filesystem paths
 
 ### Create a vserver
 
@@ -104,15 +105,15 @@ VServers are virtual file servers that control how data flows between the client
 * VServers enforce file access controls, including core filer export policies and user authentication systems
 * VServers provide SMB infrastructure
 
-Before starting to configure a cluster vserver, read the linked documentation and consult your Microsoft representative for help understanding namespace and vservers. If using VLANs, [create them](fxt-configure-network.md#adjust-network-settings) before creating the vserver. 
+Before starting to configure a cluster vserver, read the linked documentation and consult your Microsoft representative for help understanding namespace and vservers. If using VLANs, [create them](fxt-configure-network.md#adjust-network-settings) before creating the vserver.
 
 These sections of the Cluster Configuration Guide will help you familiarize yourself with the FXT vserver and global namespace features:
 
 * [Creating and Working with VServers](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/settings_overview.html#creating-and-working-with-vservers)
 * [Using a Global Namespace](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gns_overview.html)
 * [Creating a VServer](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gui_vserver_manage.html#creating-a-vserver)
 
-You need at least one vserver for your cluster. 
+You need at least one vserver for your cluster.
 
 To create a new vserver, you need the following information:
 
@@ -124,7 +125,7 @@ To create a new vserver, you need the following information:
 
 * If your network has VLANs, which VLAN to use for this vserver
 
-Use the **VServer** > **Manage VServers** settings page to create a new vserver. For details read [Creating a VServer](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gui_vserver_manage.html#creating-a-vserver) in the Cluster Configuration Guide. 
+Use the **VServer** > **Manage VServers** settings page to create a new vserver. For details read [Creating a VServer](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/gui_vserver_manage.html#creating-a-vserver) in the Cluster Configuration Guide.
 
 ![pop-up window for creating a new vserver](media/fxt-cluster-config/new-vserver.png)
 
@@ -150,7 +151,6 @@ Second, use the **VServer** > **Export Policies** page to apply the customized p
 
 Read the Cluster Configuration Guide article [Controlling Access to Core Filer Exports](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/export_rules_overview.html) for details.
 
-
 ## Next steps
 
 After adding storage and configuring the client-facing namespace, complete your cluster's initial setup: 

articles/fxt-edge-filer/fxt-additional-doc.md

@@ -14,17 +14,16 @@ Some resources outside of this docs.microsoft.com website might help you underst
 
 ## Avere vFXT for Azure cache documentation
 
-[Avere vFXT for Azure](https://docs.microsoft.com/azure/avere-vfxt/) is a similar cluster cache product that uses virtual nodes in Microsoft Azure. It is created with the Azure portal, but uses the same control panel configuration software as the Azure FXT Edge Filer hardware cache. 
+[Avere vFXT for Azure](https://docs.microsoft.com/azure/avere-vfxt/) is a similar cluster cache product that uses virtual nodes in Microsoft Azure. It is created with the Azure portal, but uses the same control panel configuration software as the Azure FXT Edge Filer hardware cache.
 
-## Legacy hardware documentation 
+## Legacy hardware documentation
 
-This technology was previously used in products from Avere Systems. User documentation for those older products is available on the [Avere Legacy Documentation website](https://azure.github.io/Avere/). 
+This technology was previously used in products from Avere Systems. User documentation for those older products is available on the [Avere Legacy Documentation website](https://azure.github.io/Avere/).
 
 Specifically, these documents might have helpful details:
 
-* [Cluster Configuration Guide](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/ops_conf_index.html) - Includes overview information about common cluster setup and management tasks, and has detailed explanations of the cluster settings pages 
+* [Cluster Configuration Guide](https://azure.github.io/Avere/legacy/ops_guide/4_7/html/ops_conf_index.html) - Includes overview information about common cluster setup and management tasks, and has detailed explanations of the cluster settings pages
 
 * [Dashboard Guide](https://azure.github.io/Avere/legacy/dashboard/4_7/html/ops_dashboard_index.html) - Explains the features of the control panel **Dashboard** tab
 
 * [FXT Cluster Creation Guide](https://azure.github.io/Avere/legacy/create_cluster/4_8/html/create_index.html) - Cluster creation guide from previous products
-