Before you proceed, ensure that you have performed the following tasks:

  • Create an Address Record (A Record) and a Pointer Record (PTR) for both forward and reverse resolution in the DNS using the hostname and IP address. VMware Pulse IoT Center generates a self-signed certificate based on this DNS.

    VMware Pulse IoT Center recommends using host names that are resolvable through DNS. Select an appropriate hostname for your VMware Pulse IoT Center server and add it to the DNS record for both forward and reverse lookup. It involves creating an A Record that maps the hostname to the IP address of the VMware Pulse IoT Center server, and a PTR that maps the IP address to the hostname of the VMware Pulse IoT Center server. You can test the configuration using the nslookup command for Windows operating systems and dig command for Linux or Mac operating systems.

    Example: Assuming that the hostname is pulse-iot-110-11.test.com and the corresponding IP address is 192.0.2.255, the following commands ensure that these records are set up correctly by your network administrator. You can test the setup from an existing Windows or Linux operating system in the vCenter Server environment where VMware Pulse IoT Center is being deployed.
    On Windows operating system: Forward look up (Hostname to IP address).
    >>> nslookup pulse-iot-110-11.test.com
    
    
    Server:  UnKnown
    Address:  198.51.100.0
    
    Name:    pulse-iot-110-11.test.com.localdomain
    Addresses:  192.0.2.255
              192.0.2.255
    On Windows operating system: Reverse look up (IP address to hostname).
    >>> nslookup 192.0.2.255
    
    
    Server:  UnKnown
    Address:  198.51.100.0
    
    Name:    pulse-iot-110-11.test.com
    Address:  192.0.2.255
    On a Linux/Mac operating system: Forward look up (Hostname to IP address).
    $ dig pulse-iot-110-11.test.com
    
    ; <<>> DiG 9.10.6 <<>> pulse-iot-110-11.test.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16081
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;pulse-iot-110-11.test.com. IN    A
    
    ;; ANSWER SECTION:
    pulse-iot-110-11.test.com. 3600 IN A      192.0.2.255
    
    ;; Query time: 3 msec
    ;; SERVER: 10.112.64.1#53(10.112.64.1)
    ;; WHEN: Wed May 22 12:55:15 IST 2019
    ;; MSG SIZE  rcvd: 76
    
    On a Linux/Mac operating system: Reverse look up (IP address to hostname).
    $ dig -x 192.0.2.255
    
    ; <<>> DiG 9.10.6 <<>> -x 10.196.177.90
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46182
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;90.177.196.10.in-addr.arpa.       IN            PTR
    
    ;; ANSWER SECTION:
    90.177.196.10.in-addr.arpa. 3600 IN        PTR        pulse-iot-110-11.test.com
    
    ;; Query time: 2 msec
    ;; SERVER: 10.112.64.1#53(10.112.64.1)
    ;; WHEN: Wed May 22 12:57:28 IST 2019
    ;; MSG SIZE  rcvd: 100
    
  • Ensure that the vCenter access is set up with at least 100 GB of hard disk space for a single node deployment. For information related to capacity, see the VMware Pulse IoT Center 2.0.0 Sizing Guide.
  • Ensure that network objects are created and configured in vSphere to deploy the virtual machine. For ports exposed and to be controlled, refer to the Topology Diagram.
  • If you do not intend to use the default SSL certificates that the OVA generates during deployment, ensure that the SSL certificates from trusted certificate authorities (CAs) or private CAs are present. SSL certificates must be packaged in the PKCS12 format with the complete certificate chain in the order of intermediate to root, and must follow the signing hierarchy. It is recommended that a certificate is valid for at least two years.
  • To access the VMware Pulse IoT Center console and the VMware Pulse IoT Administration console, you must enable port numbers 443 and 8443 in the network. VMware Pulse IoT Center instance consists of multiple nodes (VMs) where the application services are exposed on port 443 and the VMware Pulse IoT Center Administration console is exposed on the port 8443. The port 8443 is used only by administrators who are installing and configuring the VMware Pulse IoT Center and is not meant for users who are accessing features of VMware Pulse IoT Center.
  • Ensure that port 25, the default SMTP port, is reachable from the VMware Pulse IoT Center server to the SMTP server, and the connections are TLS enabled.
  • Ensure that you have a valid license key. Evaluation period is for 30 days.

Application-Specific OVF Properties

The following table lists the OVF properties used during deployment.
Property Name Description
Pulse IoTC Host Name The external host name for the Pulse IoTC Server as FQDN.
Admin Password for Node Management The node password for the VMware Pulse IoT Center Administration console. The user name is nodeadmin and is consistent across all nodes.

You can reset the nodeadmin password using the script /etc/bootstrap/utils/reset_nodeadmin_password.sh.

Initial root password

The initial root password used to access the nodes shell through the SSH login.

Note: The password cannot be recovered if lost. Ensure that you safeguard the password.
Join Pulse Instance For Node 1, leave this text box blank.

For Node 2 and 3, enter the IP address or FQDN of Node 1.

Default Gateway The default gateway address for the virtual machine. Leave this text box blank if you prefer DHCP.
Domain Name The domain name of the virtual machine. Leave this text box blank if you prefer DHCP.
Domain Name Servers The comma-separated IP addresses of the domain name servers for the virtual machine. Leave this text box blank if you prefer DHCP.
Domain Search Path The comma separated or space separated domain search path for the virtual machine. Leave this text box blank if you prefer DHCP.
Network 1 IP Address The IP address for the interface. Leave this text box blank if you prefer DHCP.
Network 1 Netmask The netmask or prefix for the interface. Leave this text box blank if you prefer DHCP.

Supported VMware Pulse IoT Center Load Balancer Port

The VMware Pulse IoT Center load balancer currently exposes the following load balancer ports:
Table 1. Supported Load Balancer Ports
Port Description
8443 - Load balancer administration port Refers to the VMware Pulse IoT Center Administration console used to install or configure the VMWare Pulse IoT Center load balancer node (VM) post deployment.

Access is restricted only to administrators who own and maintain the VMware Pulse IoT Center and the VMWare Pulse IoT Center load balancers.

443 - The load balancer port Accepts all incoming requests to the VMware Pulse IoT Center console using browsers, APIs and VMware Pulse IoTC Agents, for a multi-node deployment. The request is SSL terminated and forwarded to the backend VMware Pulse IoT Center instances for high availability.

Supported VMware Pulse IoT Center Node Ports

The VMware Pulse IoT Center nodes currently expose the following ports:
Table 2. VMware Pulse IoT Center Node Ports
Port Description
8443 - VMware Pulse IoT Center administration console port The administration console port 8443 in the VMware Pulse IoT Center nodes refers to the VMware Pulse IoT Center Administration console. The port is used to install or configure the VMware Pulse IoT Center load balancer node (VM), console UI user name and password, and SMTP server details post deployment.

Access is restricted only to administrators who own and maintain the VMware Pulse IoT Center and the VMware Pulse IoT Center load balancers.

443 - VMware Pulse IoT Center console port Accepts all incoming requests to the VMware Pulse IoT Center console using browsers, APIs, VMware Pulse IoTC agents, for a single and a multi-node deployment.

The access to this port is limited for the traffic coming from the VMware Pulse IoT Center load balancers.

Note: The Vmware Pulse IoT Center node also exposes additional port for database level clustering. But they are never exposed out side the internal network where the VMware Pulse IoT Center nodes are installed.