VMware: Installing Nasuni Edge Appliance or NMC

Installing the high-availability Edge Appliance (HA Edge) into VMware ESXi

You can install the high-availability Edge Appliance (HA Edge) in VMware ESXi 7.0 and above, using the vSphere Web Client.

Note: Nasuni supports VMware ESXi 7.0 and above.

Important: The NMC is required in order to manage a high-availability Edge Appliance (HA Edge). Ensure that an NMC has been installed before installing a high-availability Edge Appliance (HA Edge).

Warning: DO NOT attempt to restore from a virtual machine snapshot or backup. Attempting to restore from a virtual machine snapshot or backup puts the HA Edge Appliance in an unknown state in relation to the Nasuni Orchestration Center (NOC), and requires a disaster recovery process to be recovered. This might result in data loss.

Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.

In a variety of situations, the two nodes must reach a quorum about which node is to be the primary node. This process is called leader election. One vote is provided by each node and by the Nasuni-hosted Quorum Daemon, for a total of three votes.  When leader election occurs, the elected node becomes the new primary node and acts to ensure that the new secondary node does not access the shared resources, which could cause inconsistencies and data corruption. This process is called “fencing”.  A “fencing agent” is responsible for performing an API call to the vCenter API to reboot the secondary node during this process.

This section describes the installation and configuration of the fencing agent.

Note: If the HA Edge attempts to fence a node that is powered off in vCenter, the API call results in the node being powered on.  
If desired, to keep the node offline, you can power off the node again in vCenter before it POSTs and boots to the OS.

Setting up the fencing agent

• The fencing agent is installed into both of the HA Edge nodes upon setup.

• No further action is needed by the user.

Setting up the HA Edge VM folder

• Nasuni recommends creating a dedicated VM folder for each HA Edge appliance.  This folder contains both nodes of the HA Edge appliance.  

• As a best practice, creating an HA Edge parent VM folder and a sub-folder for each HA Edge instance ensures targeted and performant queries and an organized environment.

• While you can optionally create one VM folder to contain all HA Edge appliances, on a busy vCenter instance with enough VMs in the folder scope, this configuration might lead to issues with fencing agent performance and HA Edge stability.

• [TBD] Screenshots (pull them from the vcenter-automation lab)

Creating a role for the fencing agent

• Create a role in the @vsphere.local domain with the following permissions:

  • Virtual Machine
    

    • Interaction

      • Power On

      • Power Off

Creating the fencing agent account and granting it the role

• Option One:

  • Create one account with scope for all of the VM folders that are hosting nodes.

    • Pro: Simplified configuration.

    • Con: Less isolated from a security perspective.

• Option Two:

  • Create a unique account with scope for only one VM folder hosting an HA Edge Appliance’s member nodes.

    • Pro: Increased isolation marginally improves security.

    • Con: Slightly more complex configuration.

  • This is Nasuni’s recommendation.

Setting the scope and role of the fencing agent account

• To bind the account and role to the folder’s scope, right-click on the VM folder and select ‘Add Permission’ .

  • You must apply the permission to all child objects so that it applies to the VMs inside the folder.

• The specific steps are as follows:

  • Browse to the object navigator and select the folder where you want to assign permissions.

  • Click the Permissions tab for the selected folder.

  • Click the + (plus sign) icon to open the "Add Permission" dialog box.

  • In the "Users/Groups" section, select the Domain (namely, your Active Directory domain).

  • Enter the username or group name you want to assign permissions to and click Search.

  • Select the user or group from the search results.

  • From the "Assigned Role" dropdown menu, choose the role you want to assign to this user or group.

  • To apply the permissions to all subfolders and their contained objects, select the “Propagate to Children” box.

  • To save the new permission, click OK.

    The new permission appears in the Permissions tab, and the user or group has the assigned role's privileges on that object and on its children (if propagated).

• [TBD] Screenshots.  Unfortunately, I cannot get a screenshot of applying the permission to the folder because I lack the required permissions in the vCenter-automation environment. Kevin Pease should be able to get that screenshot.  It is possible I shared a set of screenshots a couple of months ago from a lab in the IBM cloud that is now torn down.

Installing using the vSphere Web Client

You can install the Nasuni Highly Available (HA) Edge Appliance in VMware ESXi 7.0 and above, using the vSphere Web Client. The vSphere Web Client enables you to connect to a vCenter Server system to manage one or more ESXi hosts through a browser.

The vSphere Web Client uses the OVF virtual appliance format for installing the Nasuni HA Edge Appliance.

Tip: If you install the Nasuni HA Edge Appliance into VMware ESXi using the vSphere Web Client, ensure that the ESXi Embedded Host Client is running version 1.24 or higher.

• Performance Best Practices for VMware vSphere 7.0

• Performance Best Practices for VMware vSphere 8.0

To install the Nasuni HA Edge Appliance into VMware ESXi using vSphere Web Client, follow these steps to deploy each member node:

1. Download and unzip the Nasuni HA Edge Appliance software in OVF format, as explained in ““Downloading the Nasuni HA Edge Appliance” ” above.

2. Open a web browser and log into the vCenter Server or ESXi host.

3. In the left-hand browser pane, right-click the host  or cluster onto which the OVF is to be deployed. A drop-down menu appears.
   
   

4. From the drop-down menu, select Deploy OVF Template. The Deploy OVF Template page appears.
   

5. Select Local file, then click Upload Files and navigate to the location where the unzipped Nasuni HA Edge Appliance software installation files are.
   

6. Select the NasuniFiler.ovf, NasuniFiler-disk1.vmdk, NasuniFiler-disk2.vmdk, and NasuniFiler-disk3.vmdk files, then click Open.

7. In the Deploy OVF Template window, ensure that the correct number of selected files appears, then click Next.

8. The “Select a name and folder” pane appears. Enter a name for the “Virtual machine name”. From the “Select a location for the virtual machine” list, select an installation location. This installation location must be within the scope of the user that you provided for use by the fencing agent during the Setup Wizard. See “Configuring the fencing agent”. Click Next.
   

9. If deploying the OVF on a vCenter server, the “Select a compute resource” pane appears. Select a specific hypervisor or compute cluster resource, then click Next.
   

   Important: If you are deploying on an ESXi host instead of on a cluster, you must ensure that the two HA Edge Appliance nodes are deployed to different ESXi hosts, as a best practice.

10. The “Review details” pane appears. Review the template details, then click Next.
    

11. The “Select storage” pane appears. Select a datastore onto which to deploy the Virtual HA Edge Appliance, then click Next.
    

    Caution: Nasuni recommends selecting a highly available datastore when deploying Nasuni HA Edge appliances. See “Selecting storage for high-availability Edge Appliances (HA Edges)” .

12. The “Select networks” pane appears. From the Destination Network drop-down menu, select the port group onto which to deploy the Virtual HA Edge Appliance.
    

    Important: The Destination Network must provide the following functionality:

    • DHCP.

    • At least one static IP address, for use as the virtual IP address (VIP), which should be excluded from the DHCP range or reserved.

    • Connectivity to the Nasuni NOC on port 443.

    • Connectivity to the vCenter API server on port 80 or 443.

13. As an alternative to using the default COW disk, you can use RDM disks to configure SAN LUNs as the COW disk. See ““Using RDM disks to configure SAN LUNs as the cache disk”.

14. The “Ready to complete” pane appears. Review the details. To change any item, click Back.          
    To begin deploying the appliance, click Finish.
    

15. Two tasks appear at the bottom of the vCenter browser window: Import OVF Package and

    Deploy OVF Template. Allow these tasks to complete.
    

    The new Nasuni HA Edge Appliance virtual machine is deployed.

16. Nasuni strongly recommends disabling VMware snapshots, because attempting to restore from a VMware snapshot can ruin the installation and cause data loss.

Warning: DO NOT attempt to restore from a virtual machine snapshot or backup. Attempting to restore from a virtual machine snapshot or backup puts the HA Edge Appliance in an unknown state in relation to the Nasuni Orchestration Center (NOC), and requires a disaster recovery process to be recovered. This might result in data loss.

1. After the virtual HA Edge Appliance has deployed, locate the virtual machine  in the left-hand pane, and right-click it. The Actions drop-down menu appears.
   

2. Click Edit Settings. The Edit Settings window appears.
   

100. Click the VM Options tab at the top of the window. The VM Options pane appears.
     

500. Click Advanced, then scroll down to Configuration Parameters, and click Edit Configuration. The Configuration Parameters pane appears.
     

5. Click Add Configuration Params. The Add New Configuration Params section appears.

6. In the Name field, enter snapshot.MaxSnapshots. Set the Value field to 0.
   

7. To save the configuration, click OK.

17. For a high-availability Edge Appliance (HA Edge), for the first node, create a cache disk, which is shared by the second node, by following these steps:

a. Locate the first virtual machine in the left-hand pane, and right-click it. The Actions drop-down menu appears.

2. Click Edit Settings. The Edit Settings window appears.
   

3. Click the Virtual Hardware tab. The virtual hardware configuration items appear.

4. Select the cache disk. This is labeled “Hard Disk 2” and it has a default size of 250 GB. The cache disk entry expands.
   Note the location of the Disk File for later reference.

5. From the Sharing drop-down list, select Multi-writer.

6. From the Disk Mode drop-down list, select Independent-Persistent.

7. Ensure that the Virtual Device Node is SCSI Controller 1.

8. From the SCSI Bus Sharing drop-down list below SCSI Controller 1, select Physical.

9. To save the configuration, click OK.

18. For a high-availability Edge (HA Edge), for the second node, remove the original second node cache disk, then create a hard disk that points to the configured cache disk of the first node, by following these steps:

a. Locate the second virtual machine in the left-hand pane, and right-click it. The Actions drop- down menu appears.

2. Click Edit Settings. The Edit Settings window appears.
   

3. Click the Virtual Hardware tab. The virtual hardware configuration items appear.

4. Select the default cache disk. This is labeled “Hard Disk 2” and it has a default size of 250 GB.
   The cache disk entry expands.

5. Remove the default cache disk.
   Click the X symbol to the right of the default cache disk.
   Click “Delete files from datastore”.
   Click the return symbol. The disk is removed.

6. From the Add New Device drop-down list, select "Existing Hard Disk". The Select File dialog box appears.
   Use the Select File dialog box to navigate to the cache disk of the first node, which you created above.
   Click OK.
   For this new hard disk, the location of the Disk File should match the cache disk of the first node.
   

7. From the Sharing drop-down list, select Multi-writer.

8. From the Disk Mode drop-down list, select Independent-Persistent.

9. Ensure that the Virtual Device Node is SCSI Controller 1.

10. From the SCSI Bus Sharing drop-down list below SCSI Controller 1, select Physical.

11. To save the configuration, click OK.
    This new hard disk matches the cache disk of the first node.

19. On the page for the Nasuni HA Edge Appliance virtual machine, from the Actions drop-down menu, select Power, then Power On. This powers on the new Nasuni HA Edge Appliance virtual machine.
    

    For a high-availability Edge (HA Edge), perform this step on both the first node and the second node, in this order:

1. Power on the first node.

2. For the first node, continue the installation procedure through step 23 .

3. For the second node, perform this installation procedure and power on at this step.

20. On the Summary tab of the page for the Nasuni HA Edge Appliance virtual machine, in the Guest OS pane, click Launch Web Console.

21. The Web Console display opens. The Nasuni HA Edge Appliance installation progress screen appears with a plain bar on the bottom that indicates the progress of the installation.
    

22. After a few moments, the Nasuni HA Edge Appliance console screen appears.
    

    Tip: The first boot of a Nasuni HA Edge Appliance might take slightly longer than subsequent boots.

23. If DHCP is available on the network, make note of the “Assigned IP Address” that appears on the console screen. You use this IP address to access the Nasuni HA Edge Appliance user interface.
    Alternatively, if DHCP is not available, log into the console service screen. Click anywhere on the console screen to enable keyboard input.
    Then press Enter and sign in. The default login username is “service”, and the default password is “service”.

    Note: For security, use the changepassword command to change the password for the service console.

1. Enter the command: editnetwork.

2. Enter the command: setall static.

3. Enter a new IP address for the Nasuni HA Edge Appliance. Note this IP address. You use this IP address to access the Nasuni HA Edge Appliance user interface.

24. The Nasuni HA Edge Appliance is now installed and ready to access using the IP address.
    If this is the first node of an HA Edge, you can now perform the same procedure for the second node.

Connecting with the Nasuni HA Edge Appliance

where <IP address> is the IP address.

Tip: When you attempt to access the Nasuni HA Edge Appliance Home page for the first time, a message might appear indicating that the security certificate is not trusted. You can still access the site to proceed with the initial configuration procedure.

You can either add a security certificate, or proceed without adding a security certificate.

Using RDM disks to configure SAN LUNs as the cache disk and the COW disk

As an alternative to using the default cache disk and COW disk, you can use RDM disks to configure SAN LUNs as the COW disk. For Edge Appliances that are NOT high-availability HA Edge Appliances, you can also use RDM disks to configure SAN LUNs as the cache disk.

Important: With a high-availability Edge Appliance (HA Edge), you can use RDM disks for the COW disk. However, to avoid an outage, if the system is already fully installed and operational, then you should perform this procedure on one node at a time. Perform failovers as necessary to ensure that you are always working on the standby node.

To use RDM disks for the cache disk and the COW disk, follow these steps:

1. Use the Edit Settings pane to remove Hard disk 2 (the existing COW disk) and Hard disk 3 (the existing cache disk).

   

2. To add the COW disk, follow these steps:

   1. Click Add New Device.

   2. Select RDM Disk.

   3. From the Select Target LUN dialog box, select the COW disk for hard disk 2.

3. For Edge Appliances that are NOT high-availability Edge Appliance, to add the cache disk, follow these steps:

   1. Click Add New Device.

   2. Select RDM Disk.

   3. From the Select Target LUN dialog box, select the cache disk for hard disk 3.

4. Continue with the procedure.

Installing the Nasuni Management Console (NMC) into VMware ESXi

You can install the Nasuni Management Console (NMC) in VMware ESXi 7.0 and above, using either the vSphere Web Client or the vSphere Client. We provide instructions for both methods.

Note: Nasuni supports VMware ESXi 7.0 and above.

Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP. ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.

Important: Installing third-party software on Nasuni appliances is not allowed.

Installing using the vSphere Web Client

You install the Nasuni Management Console (NMC) in VMware ESXi 7.0 and above, using the vSphere Web Client. The vSphere Web Client enables you to connect to a vCenter Server system to manage an ESXi host through a browser.

The vSphere Web Client uses the OVF virtual appliance format for installing the Nasuni Edge Appliance.

Tip: If you install the NMC into VMware ESXi using the vSphere Web Client, instead of using the vSphere Client, ensure that the ESXi Embedded Host Client is running version 1.24 or higher.

For further information, also see:

• Performance Best Practices for VMware vSphere 7.0

• Performance Best Practices for VMware vSphere 8.0

Important: Installing third-party software on Nasuni appliances is not allowed.

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

To install the NMC into VMware ESXi using vSphere Web Client:

1. Download and unzip the NMC software in OVF format, as explained in “Downloading the Nasuni Edge Appliance or NMC Software”.

2. Open a web browser and log into the vCenter Server or ESXi host.

3. In the left-hand browser pane, right-click the host or cluster onto which the OVF is to be deployed. A drop-down menu appears.

   

4. From the drop-down menu, select Deploy OVF Template. The Deploy OVF Template page appears.

   

5. Select Local File, then click Browse, and navigate to the NasuniNMC.ovf file, located in the NMC folder of the unzipped NMC software.

   

6. Select the NasuniNMC.ovf and NasuniNMC-disk1.vmdk files, then click Open.

7. In the Deploy OVF Template window, ensure that “2 files selected” appears beside the Browse button, then click Next.

   

8. The “Select a name and folder” pane appears. Enter a name for the “Virtual machine name”. From the “Select a location for the virtual machine” list, select an installation location. Click Next.

   

9. If deploying the OVF on a vCenter server, the “Select a compute resource” pane appears. Select a specific hypervisor or compute cluster resource, then click Next.

   

10. The “Review details” pane appears. Review the template details, then click Next.

    

11. The “Select storage” pane appears. Select a datastore onto which to deploy the Virtual Edge Appliance.

    

12. From the “Select virtual disk format” drop-down list, select the disk format “Thick Provision Eager Zeroed“. Then click Next.

13. The “Select networks” pane appears. From the Destination Network drop-down menu, select the port group onto which to deploy the Virtual Edge Appliance.

    

14. The “Ready to complete” pane appears. Review the details.

    To change any item, click Back.

    To begin deploying the appliance, click Finish.

    

15. Two tasks appear at the bottom of the VMware browser window: Import OVF Package and Deploy OVF Template. Allow these tasks to complete.

    

    The new NMC virtual machine is deployed.

16. Nasuni strongly recommends disabling VMware snapshots, because attempting to restore from a VMware snapshot can ruin the installation and cause data loss.

    Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP. ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

    1. After the Virtual Edge Appliance has deployed, locate the virtual machine in the left-hand pane, and right-click it. The Actions drop-down menu appears.

       

    2. Click Edit Settings. The Edit Settings window appears.

       

    3. Click the VM Options tab at the top of the window. The VM Options pane appears.

       

    4. Click Advanced, then scroll down to Configuration Parameters, and click Edit Configuration. The Configuration Parameters pane appears.

       

17. Click Add Configuration Params. The Add New Configuration Params section appears.

18. In the Name field, enter snapshot.MaxSnapshots. Set the Value field to 0.

19. To save the configuration, click OK.

20. Right-click the new NMC virtual machine, then, from the drop-down menu, select Power, then Power On. This powers on the new NMC virtual machine.

    Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

    “Nasuni recommends running the Management Console on ESX 7.0 or later.”

21. Right-click the NMC virtual machine, then, from the drop-down menu, expand Console, then select Open Browser Console. The NMC screen appears with a plain bar on the bottom that indicates the progress of the installation.

    

22. After a few moments, the NMC console screen appears.

    

    Tip: The first boot of a NMC might take slightly longer than subsequent boots.

23. If DHCP is available on the network, make note of the “Assigned IP Address” that appears on the console screen. You use this IP address to access the NMC user interface.

    Alternatively, if DHCP is not available, log into the console service screen by pressing Enter and signing in. The default login username is service, and the default password is service.

    Note: For security, use the changepassword command to change the password for the service console.

    1. Enter the command: editnetwork.

    2. Enter the command: setall static.

    3. Enter a new IP address for the NMC. Note this IP address. You use this IP address to access the NMC user interface.

24. The NMC is now installed and ready to access using the IP address. See the Nasuni Management Console Guide for instructions on completing the configuration of the NMC.

    Tip: To access the NEA or NMC appliance using the serial console, instead of using the IP address obtained when installing the appliance, follow one of these procedures:

    • If the appliance is running on Amazon EC2, see instructions in EC2 Serial Console for Linux instances.

    • If the appliance is running on Google Cloud, see instructions in Troubleshooting using the serial console.

    • If the appliance is running on Microsoft Azure, see instructions in Azure Serial Console.

All supported hypervisors include a serial console that works with Nasuni. For other hypervisors, consult your vendor’s documentation for connection instructions.

Installing using the vSphere Client

You can install the NMC in VMware ESXi 7.0 and above, using the vSphere Client. The vSphere Client can connect either directly to a host running VMware ESXi, or to vCenter Server, which is used to manage a group of hosts running ESXi.

The vSphere Client uses the OVF virtual appliance format for installing the NMC.

Note: You should install the VMware vSphere Client before performing this procedure. If you need more information, see your VMware documentation.

Tip: If you install the NMC into VMware ESXi using the vSphere Web interface, instead of using the vSphere Client, ensure that the ESXi Embedded Host Client is running version 1.24 or higher.

Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.

Important: Installing third-party software on Nasuni appliances is not allowed.

For further information, also see:

• Performance Best Practices for VMware vSphere 7.0

• Performance Best Practices for VMware vSphere 8.0

Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

“Nasuni recommends running the Management Console on ESX 7.0 or later.”

To install the NMC into VMware ESXi using vSphere Client:

1. Download and unzip the NMC software in OVF format, as explained in “Downloading the Nasuni Edge Appliance or NMC Software”

2. Launch the VMware vSphere Client. The Login window appears.

3. Log in to the vSphere Client with a valid IP address and your user name and password.

4. From the File menu, select Deploy OVF Template. The Deploy OVF Template window appears.

5. Navigate to the NasuniNMC.ovf file, located in the NMC folder of the unzipped NMC software. Click Next.

6. Continue with the Deploy OVF Template wizard, accepting all default values. When prompted, enter a Name for the virtual machine.

   Note: If necessary, at a later point, you can change the memory, the number of CPU processors, and the pass-through disks. See “Configuring the Virtual Platform,”.

7. On the last Deploy OVF Template wizard screen, click Finish. The Deploying dialog box appears.

8. When the message “Completed Successfully” appears, click Close. The new NMC virtual machine appears in the Inventory list in the left pane.

9. Nasuni strongly recommends disabling VMware snapshots, because attempting to restore from a VMware snapshot can ruin the installation and cause data loss.

   Warning: DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP. ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.

   1. To disable VMware snapshots, right-click the NMC virtual machine and click Edit Settings.

   2. Click the Options tab, click General, then select Configuration Parameters.

   3. Click Add Row. In the Name and Value columns, type these values: snapshot.MaxSnapshots 0

   4. Click OK to save the changes.

      

10. In the Inventory list in the left pane, select the name that you specified for the new NMC virtual machine.

11. Right-click the new NMC virtual machine, then, from the drop-down menu, select Power, then Power On. This powers on the new NMC virtual machine.

    Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:

    “Nasuni recommends running the Management Console on ESX 7.0 or later.”

12. Click the Console tab. The NMC screen appears with a plain bar on the bottom that indicates the progress of the installation.

    

13. After a few moments, the NMC console screen appears.

    

    Tip: The first boot of a NMC might take slightly longer than subsequent boots.

14. If DHCP is available on the network, make note of the “Assigned IP Address” that appears on the console screen. You use this IP address to access the NMC user interface.

    Alternatively, if DHCP is not available, log into the console service screen by pressing Enter and signing in. The default login username is service, and the default password is service.

    Note: For security, use the changepassword command to change the password for the service console.

    1. Enter the command: editnetwork.

    2. Enter the command: setall static.

    3. Enter a new IP address for the NMC. Note this IP address. You use this IP address to access the NMC user interface.

15. The NMC is now installed and ready to access using the IP address. See the Nasuni Management Console Guide for instructions on completing the configuration of the NMC.

    Tip: To access the NEA or NMC appliance using the serial console, instead of using the IP address obtained when installing the appliance, follow one of these procedures:

    • If the appliance is running on Amazon EC2, see instructions in EC2 Serial Console for Linux instances.

    • If the appliance is running on Google Cloud, see instructions in Troubleshooting using the serial console.

    • If the appliance is running on Microsoft Azure, see instructions in Azure Serial Console.

All supported hypervisors include a serial console that works with Nasuni. For other hypervisors, consult your vendor’s documentation for connection instructions.