Redeploying the container to 11.2.1.10 or later

Deployment options: Netezza Performance Server for Cloud Pak for Data System

Learn how to redeploy the Netezza Performance Server container.

Procedure

As root, log in to the e1n1 bare metal node.

Identify the VDB master node.

ap node -d

In the example, e1n2 is the VDB master node.

[root@suyos01b ~]# ap node -d
+------------------+----------+-------------+-----------+-----------+--------+---------------+
| Node             |    State | Personality | Monitored | Is Master | Is HUB | Is VDB Master |
+------------------+----------+-------------+-----------+-----------+--------+---------------+
| enclosure1.node1 |  ENABLED | CONTROL     |       YES |        NO |    YES |            NO |
| enclosure1.node2 |  ENABLED | CONTROL     |       YES |       YES |     NO |           YES |
| enclosure1.node3 |  ENABLED | CONTROL     |       YES |        NO |     NO |            NO |
| enclosure1.node4 |  ENABLED | WORKER      |       YES |        NO |     NO |            NO |
| enclosure2.node1 |  ENABLED | WORKER      |       YES |        NO |     NO |            NO |
| enclosure2.node2 |  ENABLED | WORKER      |       YES |        NO |     NO |            NO |
| enclosure2.node3 | DISABLED | UNSET       |       YES |        NO |     NO |            NO |
| enclosure2.node4 | DISABLED | UNSET       |       YES |        NO |     NO |            NO |
+------------------+----------+-------------+-----------+-----------+--------+---------------+

Optional: If the VDB master node is not e1n1, ssh to the VDB master node, the node where container upgrade was done.

Go to the folder, in which nps-container-11.2.X.X-unpack was unpacked during container upgrade.

cd /opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.x.x

Example:

cd /opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.0.0

Run nzdeploy-remote.
On Cloud Pak for Data System, node1, node2 and node3 are the DNS aliases for the first, second, and third control plane nodes.
- If the VDB master node is not the connector node, run the command for target control nodes other than the current VDB master node:
```
./nzdeploy-remote -n nodeA -n nodeB
```
  Example:
```
[root@e1n1]# ./nzdeploy-remote -n node2 -n node3
```
- If the VDB master node is the connector node, run the command for the control nodes and the other connector node:
```
./nzdeploy-remote -n nodeA -n nodeB -n nodeC -n connector node
```
```
[root@e5n1]# ./nzdeploy-remote -n node1 -n node2 -n node3 -n e6n1
```
  In the example, you run the nzdeploy-remote command on Cloud Pak for Data System that has 2 connector node: e5n1 and e6n1.
Where:

-n <name>

The node on which the container needs to be redeployed. For multiple nodes, -n node1 -n node2.

-C <name>

The container name. The default is: ipshost1.

-d <path>

The base directory path. The default is: /opt/ibm/appliance/storage/ips.

-s <path>

The directory path to save the container. The default is: /opt/ibm/appliance/storage/ips/ips1_deployment.

-I <interface>

The network interface. The default is: fbond.4079.
Example:
```
[root@e5n1]# ./nzdeploy-remote -n node1 -n node2 -n node3 -n e6n1
```
In the example, you run nzdeploy-remote on Cloud Pak for Data System that is equipped with two connector nodes: e5n1 and e6n1. Also, the ipshost1 container is active on connector node e5n1.
Important: If you are upgrading replication environment as described in Upgrading Netezza Performance Server and Persistent Transient Storage (PTS), do not start Netezza Performance Server and do not proceed with next steps. Ignore this note, if upgrade is not for a replication environment system.
When the script finishes redeploying the container, log in to the container, and as the nz user start the system.
```
nzstart
```