Setting Up the Panzura Node

The setup wizard will guide you through the initial setup and configuration of the node. When completed, your node will have the necessary information to start file services and connect users.

Gather Information

Node Information

To prepare for installation and deployment of the Panzura node, gather your site's values for the deployment settings listed in this table.

Deployment Setting Your Value
End User License Agreement (EULA) and Admin Info

You will need to agree to the EULA, and enter the following contact information:

  • Name
  • Email
 
Login Credentials for the node(s)

Administrator username and password for the Master node.

Default for most platforms: adminadmin

After initial deployment using the setup wizard, all nodes within the CloudFS require the Master node's admin username and password for login.

Note: For AWS AMI and Microsoft Azure VM versions of the node, the node does not have a default password. Instead, the initial password for the admin login comes from either of the following sources:

  • AMI: The initial admin password is dynamically generated by encrypting the key file (*.pem).
  • Azure: The password is entered by the user during Azure VM deployment.
 
Configuration Mode

Function that the node will serve:

  • Master: The managing node for a group of distributed nodes. All licenses and configuration settings are added to the Master node and automatically propagate to the Subordinate nodes.
  • Subordinate: By default, all nodes are set as Subordinates, and are managed by the designated Master.
  • HA‐Local: The node will be a standby for another, active node. The HA-Local node is a dedicated backup for only one other node, and both nodes must be in the same IP subnet.
  • HA‐Global: The node will be a backup for n active nodes. The active nodes can be located remotely or in the same subnet as the HA-Global node.
 

Type of network deployment (one‐arm or inline):

  • Inline: This is the recommended deployment option, provided that the cloud traffic and client traffic are on different networks. In an inline deployment, the node is connected to the network by separate LAN (GB1) and WAN (GB2) interfaces.
  • One‐arm: In a one‐arm deployment, the node is connected to the network through a single interface. The node is not directly in the traffic path between the internal and external networks. Use this method only if the cloud and client traffic are on the same network.
 
LAN (Client-side) Addresses

The node's IP address can be assigned by DHCP or statically.

Tip Best practice is to use static addressing. For static addressing, gather the following information:

  • node IP address
  • Subnet Mask
  • Default Gateway
  • Primary DNS
  • Secondary DNS
 
WAN (Cloud) Addresses

For inline deployment only:

  • Host IP address of node
  • Subnet Mask
  • Default Gateway
 
System Settings
Host Name  
node Location  
Contact Email  
DNS Domain  

Master node information (if the node you are setting up is not the Master):

  • Master node's hostname
  • Login username and password for the Master node's WebUI
 
Hostname/IP address and filesystem name of the active node, if this node is an HA‐Local standby.  
Licenses

You can install Panzura licenses using a license token or individual license files.

  • License Token: A license token contains the license to operate, along with licenses for additional storage services. During setup, the wizard communicates with the license server to validate the token. This is the simpler method and is recommended for new deployments.
  • Individual License Files: The license files apply to individual features. A typical installation requires multiple license files.

To obtain a license token or individual license files for your node, please contact Panzura or your Panzura representative.

 

Cache Sizing

Cloud Storage To Allocate: Estimate how much storage will be moved to the cloud. The default is 1TB.  
Percentage of Cache: Estimate the percentage of cloud-stored data to keep in the node's cache for local access. This depends upon the use case typically 10% is a good starting point.  
Virtual Disk Settings (VM nodes only)

For VM platforms, you will need information to assign disk capacity for metadata and cache.

You will need the private key file, AWS access key and AWS secret key.

Make sure that you added disk capacity when setting up the VM. For information on setting up a VM in Azure, see the installation guide for your Panzura node platform.

You will need the ESX host IP address or hostname, username and password to access the host. ESX host must be managed by a vCenter/vSphere. The username and password ESX credentials are required to access the vCenter/vSphere server to provide and choose a list of datastores. They are not used to access the host (through SSH).

  • Amazon: You will need the private key file, AWS access key and AWS secret key.
  • Azure: Make sure that you added disk capacity when setting up the VM. For information on setting up a VM in Azure, see the installation guide for your Panzura node platform.
  • VMware: You will need the ESX host IP address or hostname, username and password to access the host. ESX host must be managed by a vCenter/vSphere. The username and password ESX credentials are required to access the vCenter/vSphere server to provide and choose a list of datastores. They are not used to access the host (through SSH).
 
Cloud Provider
Gather the information required for your cloud provider, as listed in the table in Cloud Provider Information.  

Cloud Provider Information

Gather the information listed in the following table for your cloud storage provider (CSP).

CSP Settings Your Value
Amazon  
  • S3 bucket path
  • S3 access key
  • S3 secret key
  • S3 bucket name cloud size (TB)
  • Cloud host IP address or hostname
 
AT&T
  • Folder name
  • User ID
  • Subtenant ID

Subtenant ID:serviceclass=Policy

Policy can be :serviceclass=policy1 or :serviceclass=policy2.

Example:

Subtenant ID:serviceclass=policy2

The policy types are case sensitive, and they all must be lowercase.

Refer to AT&T for information regarding policy1 and policy2.

Note: Changing this setting requires a reboot of the node.

  • Shared secret
  • Atmos node name
  • Your Atmos (RMG) Resource
  • Mgmt Group site node name
  • Shared secret
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 
CleverSafe
  • S3 Access Key
  • Bucket
  • Cloud Size Unit
  • Cloud Host IP/Name
  • S3 Secret Key
  • Path
  • Cloud Size

 

 
Dell EMC—ECS
  • Path
  • User name
  • Password (secret access key)
  • Bucket
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 
Dell EMC—Virtustream
  • Path
  • User name
  • Password (secret access key)
  • Bucket
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 
EMC Atmos
  • Path
  • User
  • Shared secret
  • Subtenant ID
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 
Google
  • Path
  • User name
  • Password
  • Bucket name
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 
IBM Cloud Object Storage—S3 Interface
  • Path
  • Access Key ID

  • Secret Access Key

  • Vault
  • Hostname

Note: The node supports access directly or through load balancing. The redirect option is not supported.

 
IBM Cloud Object Storage—Native Interface
  • Path
  • User name
  • Password
  • Vault
  • Hostname
 
IBM Cloud Object Storage—Swift Interface
  • Path
  • User name
  • Password
  • Container
  • Hostname
  • AuthPath
 
IIJ
  • Path
  • User name
  • Password (secret access key)
  • Bucket
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 
Microsoft Azure
  • Path
  • Storage account name
  • Access key
  • Container name
  • Cloud size (in TB)
  • Cloud host IP address or hostname
 

Bringing Up a node for the First Time

Power on the node to begin the setup process. After powering on a node, you can use the setup wizard to begin configuration. To access the setup wizard, use a browser to navigate to the node's WebUI IP address.

Static node IP Address Recommendation

Panzura recommends setting the node's IP address to a static IP address.

node IP Address Assignment

The LAN ports on physical platform nodes are configured for DHCP by default. If a DHCP server is not available, the node uses the following default addresses:

  • Management (WebUI, CLI, API): 192.168.88.88
  • iDRAC interface: 192.168.88.89

VM platform nodes receive their IP settings from the VM host.

Finding the node IP Address

You will need to know the node's IP address in order to access the WebUI and start the setup wizard.

  • VM platforms: If your node is deployed on a virtual machine, obtain the assigned IP address from the management interface on your virtual machine host.
  • Physical platforms: For a physical node platform, you must connect to the console to obtain the address.

Use an Ethernet cable to connect a laptop PC to the iDRAC port on the node. Set the laptop IP address statically to the 192.168.88.00 network. Point your browser to https://192.168.88.89 and log in to the console using the default credentials admin/admin.

The assigned IP address is displayed when you access the console.


  • Either static or DHCP address assignment is supported. However, for all node platforms, Panzura recommends using a static address.
  • Setup of a physical platform node's IP address requires either a direct Ethernet connection to the node (to the iDRAC port), or access to the IP subnet of the WebUI IP address. If you plan to change the IP addresses using the setup wizard, configure your laptop to join the 192.168.88.0 subnet. The node's default WebUI and iDRAC addresses are in this subnet.
  • When you deploy an AMI or Azure node, a private IP address is required to access the node's setup wizard. This is because Secure Private Network Mode, which is enabled by default, blocks public IP access. After you disable Private Secure Network Mode from within the wizard, you can change to a public IP address.

Accessing the Setup Wizard *

After an IP address is assigned to the node, use the Chrome web browser (version 59.03071 or above) to navigate to the node's IP address to log onto the setup wizard.

See the Installation Guide for your Panzura node platform for detailed instructions.

After you complete the setup wizard, the browser redirects to the node's regular WebUI. You have the option to use another wizard (configuration wizard) within the regular WebUI. If preferred, you can perform configuration without the configuration wizard.

Configuration Wizard *

The configuration wizard manager opens when you click Continue with Optional Wizards at the end of the setup wizard. See the wizard's online help for details.

* Only pertains to Panzura version 7 nodes