Redeploying the container to 11.2.1.9 or earlier

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 |
+------------------+----------+-------------+-----------+-----------+--------+---------------+

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.
- If you are upgrading the container to version 11.2.1.9, run:
```
./nzdeploy-remote -n nodeA -n nodeB
```
  If the VDB master node is not the connector node, run nzdeploy-remote for target control nodes other than the current VDB master node.
- If you are upgrading the container to version 11.2.1.8 or earlier:
  If the VDB master node is the connector node, run nzdeploy-remote with the -m option for target control nodes other than the current VDB master node. -m specifies the search domain that is missing in the connector node and present in e1n1.
  1. On the connector node, run:
```
cat /etc/resolv.conf
```
```
ssh e1n1 cat /etc/resolv.conf
```
  2. Note the custom domain names that are present in e1n1 but missing in the connector node resolv.conf file in the search line.
    Example:
    $ cat /etc/resolv.conf Generated by NetworkManager search mbond fbond $ ssh e1n1 cat /etc/resolv.conf Generated by NetworkManager search mbond fbond rtp.raleigh.ibm.com
    These domain name or names must be the same as the ones that you used when running the nzdeploy upgrade command on the connector node.
    ./nzdeploy-remote -n nodeA -n nodeB -n nodeC -n OTHER CONNECTOR NODES -m domain1 -m domain2
    Example:
    [root@e5n1]# ./nzdeploy-remote -n node1 -n node2 -n node3 -n e6n1 -m rtp.raleigh.ibm.com
Note: On Cloud Pak for Data System, node1, node2 and node3 are the DNS aliases for the first, second, and third control plane nodes.

Where:

-n <name>

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

-m <name>

Custom domain names that are to be added to the DNS search list in the container. For multiple domains, -m domain1 -m domain2.

-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.
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
```