Introduction

This document is a step-by-step installation guide for Zentera installation and programming a ZNS node on physical, private, Azure or EC2 virtual machines.

Generic Installation Procedure for New ZNS Node on Azure VM

Launch a VM from Azure's portal by following below settings and steps

• CentOS 7.4

• Create a new cloud service

• Set endpoints

  Name

  Protocol

  Public Port

  Private Port

  SSH

  TCP

  22

  22

  HTTPS

  TCP

  443

  443

  ZNS

  TCP

  4433

  4433

*The public and private port for ZNS default control channel port may differ which depends on setting in ZOL Admin or physical gateway.

SSH login the VM and sudo to root

$ sudo -i

Download the installation package from Zentera's ZenDesk Support Pages

$ wget --no-check-certificate ".../zns_node_install.tar.gz"

Extract the downloaded file:

$ tar -xzf zns_node_install.tar.gz

Change directory to zns_install

$ cd zns_install

Execute the install shell

$ ./install_zns_azure.sh

Delete the download files when the environment is confirmed

Generic Installation Procedure for New ZNS Node on EC2 VM

When using ZNS Nodes in Amazon AWS, Zentera provides pre-installed machine images in these regions:

AMI Name: zns-3.2.2-3.6-x86_64

Default Login: ztu / zentera-zns

Launch an VM from EC2's portal by following below settings and steps

Choose AMI "zns-3.2.2-3.6-x86_64" from "My AMIs"
(From customer view, they may have to search the AMI from community AMIs with the AMI ID list above). Then click "Next: Configure Instance Details".

You must use a VPC from "Network" and subnet (Create a new one if not have or full). Click "Next" until you are on the "Configure Security Group" tab.

Add HTTPS (port 443 will be given by default) and Custom TCP Rule with 4433 (the port number may differ by the setting in ZOL Admin or physical gateway). Click "Launch".

Select proceed without a key pair and check for the acknowledge

On the left panel, under "Network & Security," click on "Elastic IP,"

"Allocate New Address" and choose "VPC" from the drop-down menu and click "Yes"

Select the Elastic IP, click "Actions" above and choose "Associate Address"

Choose the VM you want to associate the IP with (using the VM's "Instance ID") and click "Associate"

SSH login the VM with [ztu:zentera-zns]

Enable zCLI ( password : zentera-zns-enable )

1. 

   Upgrade zCLI and ZNS to latest version

Generic Download and Upgrade Procedure for zCLI & ZNS

Generic Installation Procedure for physical Server or private VM

1. Have a clean installation of CentOS 6.5 minimal.

2. Make sure the Internet is available.

3. Make sure the machine have a public IP associated with, and TCP on ports 22, 443, and 4433 are allowed on firewall.

*The 4433 port is reserved for ZNS default control channel port, but may differ by the setting in ZOL Admin or physical gateway.

SSH login the VM and sudo to root

$ sudo -i

Download the installation package from Zentera's ZenDesk Support Pages

$ wget --no-check-certificate ".../zns_node_install-3.5.1.tar.gz"

Extract #3 file:

$ tar -xzf zns_node_install-3.5.1.tar.gz

Change directory to zns_install

$ cd zns_install

Execute the install shell

$ ./install_zns_generic.sh

Delete the download files when the environment is confirmed

Generic Configuration and Provisioning Procedure

1. In a ZOL-provisioned VA or zCenter PA, on the left panel, expand "Service Management" and select "ZNS Clustering"

2. If no ZNS Cluster show up, click "Create ZNS Cluster"

3. Click "Add ZNS Node"

Add "IP / Hostname" of the ZNS node you created earlier in this document

You will get a ZNS ID. Make sure you save this off for later reference.

Enable ZNS cluster from zCLI of ZNS Node VM

Login to the target ZNS node if you are not on it already (ztu - zentera-zns). If you are on the ZNS node, see next line.
$ su - ztu
$ enable
$ service
$ cluster enable [MCG*_Host DNS:Port or IP:Port] [ZNS_ID] [Control_Channel_Port]

*MCG = Master Controller Gateway (which is the ZOL Gateway or CoIP Controller controlling the cluster), port # of MCG_Host IP not necessary unless it is not standard port 443.

MCG Host/DNSControl Channel PortZNS ID

Confirm if ZOL has connected to ZNS node successfully in the target ZOL or zCenter under "Service Management" -> "ZNS Clustering"

Generic Download and Upgrade Procedure for zCLI & ZNS

ZNS and zCLI may need manual attend to upgrade after major release.
Current zCLI and ZNS are newer than those in this document.

Enable zCLI and go to gateway with commands

$ enable
$ gateway

1. 

   Check current zCLI and ZNS version with command

$ show version

Download latest version of zCLI & ZNS rpm file with command

$ upgrade download "zCLI file https link"
Command shown in screenshot is "upgrade download <Url>"

$ upgrade download "ZNS file https link"
Command shown in screenshot is "upgrade download <Url>"

Check the download files with command

$ upgrade list

1. 

   Upgrade zCLI to latest version with command

$ upgrade deploy cli "zCLI rpm file name"

Note: You will have to exit to ztu and enable zCLI again after upgrading the zCLI

Upgrade ZNS to latest version with command

$ upgrade deploy zns "ZNS rpm file name"
If you haven't done so, remember to configure and enable ZNS clustering on the ZNS node
Generic Configuration and Provisioning Procedure

ZNS Node Function Validation

1. In the target zCenter, enable ZNS Clustering, set target ZNS Cluster as default with at least one ZNS node registered and available.

Check the public IP of target ZNS node on Azure/EC2 portal or by command.

$ nslookup "domain-name" if applicable for ZNS node

1. Launch 2 VMs on different Cloud Domain on target VA/zCenter

2. Make an application profile with WAN Type 1 rule for the 2 VMs launched in the previous step (see image below)

1. 

   Ping the CoIP address from of VM2 from VM1

2. Check the connection by command from VM1 or VM2

$ netstat -an | grep :443
There should be 2 established connections, 1 with MCG's ip which stands for the control channel and the other one with ZNS node's ip stands for the data channel.
If you only see MCG's ip for both connections it means the ZNS node is not serving.