Setting Up the Panzura Filer

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

• Name
• Email

Administrator username and password for the Master Filer.

Default for most platforms: admin, admin

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

Note: For AWS AMI and Microsoft Azure VM versions of the filer, the filer 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.

Function that the filer will serve:

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

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 filer is connected to the network by separate LAN (GB1) and WAN (GB2) interfaces.
• One‐arm: In a one‐arm deployment, the filer is connected to the network through a single interface. The filer 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.

The filer'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:

• Filer IP address
• Subnet Mask
• Default Gateway
• Primary DNS
• Secondary DNS

For inline deployment only:

• Host IP address of filer
• Subnet Mask
• Default Gateway

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

• Master Filer's hostname
• Login username and password for the Master Filer's WebUI

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 filer, please contact Panzura or your Panzura representative.

Cache Sizing

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 Filer 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 Filer 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).

• S3 bucket path
• S3 access key
• S3 secret key
• S3 bucket name cloud size (TB)
• Cloud host IP address or hostname

• 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 filer.

• 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

• S3 Access Key
• Bucket
• Cloud Size Unit
• Cloud Host IP/Name
• S3 Secret Key
• Path
• Cloud Size

• Path
• User name
• Password (secret access key)
• Bucket
• Cloud size (in TB)
• Cloud host IP address or hostname

• Path
• User name
• Password (secret access key)
• Bucket
• Cloud size (in TB)
• Cloud host IP address or hostname

• Path
• User
• Shared secret
• Subtenant ID
• Cloud size (in TB)
• Cloud host IP address or hostname

• Path
• User name
• Password
• Bucket name
• Cloud size (in TB)
• Cloud host IP address or hostname

• Path

• Access Key ID

• Secret Access Key

• Vault
• Hostname

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

• Path
• User name
• Password
• Vault
• Hostname

• Path
• User name
• Password
• Container
• Hostname
• AuthPath

• Path
• User name
• Password (secret access key)
• Bucket
• Cloud size (in TB)
• Cloud host IP address or hostname

• Path
• Storage account name
• Access key
• Container name
• Cloud size (in TB)
• Cloud host IP address or hostname