Upgrading the container to 11.2.1.9 or earlier

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

Learn how to upgrade the Netezza Performance Server container to 11.2.1.9 or earlier.

Before you begin

Ensure that you completed the steps that are described in Before you begin upgrading to Netezza Performance Server 11.2.1.9 or earlier.
Ensure that your Cloud Pak for Data System is on version 1.0.4.1 or later, but it is suggested to be the most recent one.

Procedure

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

Identify the VDB master node if there is one.

ap node -d

Example if connector node is present:

# 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       | NO        | NO     | NO            | 
| enclosure1.node3 | ENABLED | CONTROL       | YES       | NO        | NO     | NO            |
| enclosure1.node4 | ENABLED | UNSET         | YES       | NO        | NO     | NO            |
| enclosure2.node1 | ENABLED | NRS_NODE[nrs] | YES       | NO        | NO     | NO            |
| enclosure2.node2 | ENABLED | NRS_NODE[nrs] | YES       | NO        | NO     | NO            |
| enclosure2.node3 | ENABLED | NRS_NODE[nrs] | YES       | NO        | NO     | NO            |
| enclosure2.node4 | ENABLED | NRS_NODE[nrs] | YES       | NO        | NO     | NO            |
| enclosure5.node1 | ENABLED | CN,VDB_HOST   | YES       | YES       | NO     | YES           |
| enclosure6.node1 | ENABLED | CN,VDB_HOST   | YES       | NO        | NO     | NO            |
+------------------+---------+---------------+-----------+-----------+--------+---------------+

Example if connector node is not present:

# ap node -d

+------------------+---------+-------------+-----------+-----------+--------+---------------+
| Node             | State   | Personality | Monitored | Is Master | Is HUB | Is VDB Master |
+------------------+---------+-------------+-----------+-----------+--------+---------------+
| enclosure1.node1 | ENABLED | CONTROL     | YES       | YES       | YES    | YES           |
| enclosure1.node2 | ENABLED | CONTROL     | YES       | NO        | NO     | NO            |
| enclosure1.node3 | ENABLED | CONTROL     | YES       | NO        | NO     | NO            |
| enclosure1.node4 | ENABLED | UNSET       | YES       | NO        | NO     | NO            |
| enclosure2.node1 | ENABLED | UNSET       | YES       | NO        | NO     | NO            |
| enclosure2.node2 | ENABLED | UNSET       | YES       | NO        | NO     | NO            |
| enclosure2.node3 | ENABLED | UNSET       | YES       | NO        | NO     | NO            |
| enclosure2.node4 | ENABLED | UNSET       | YES       | NO        | NO     | NO            |
+------------------+---------+-------------+-----------+-----------+--------+---------------+

If the VDB master node is not e1n1, ssh to the VDB master node and make sure ipshost1 container is running on that node.
```
docker ps
```
Download the nps-container-11.2.1.X-unpack self-extracting archive from Fix Central.
You can save it at /opt/ibm/appliance/storage/ips/ips1_deployment.

Run the following command and accept the default extraction location.

/opt/ibm/appliance/storage/ips/ips1_deployment/nps-container-11.2.1.X-unpack

Replace 11.2.1.X with your version number.

Example:

[root@e1n1 /]# /opt/ibm/appliance/storage/ips/ips1_deployment/nps-container-11.2.1.1-unpack

-----------------------------------------------------------

IBM NPS -- IBM Netezza Performance Server 11.2.1.1

(C) Copyright IBM Corp. 2020 All Rights Reserved.

-----------------------------------------------------------

Where would you like to extract the container? /opt/ibm/appliance/storage/ips/ips1_deployment

Unpacking into /opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1

..........................................

Unpacking of NPS Container is done, Please find files in /opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1

To deploy a new NPS container, run

/opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1/nzdeploy -i

Or, to upgrade an existing container, run

/opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1/nzdeploy -u

Or, to upgrade an existing container and extract the NPS software package, run

/opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1/nzdeploy -U

Run the nzdeploy command with the -U option to upgrade the container and extract the NPS software package:
- If the VDB master node is not the connector node OR if VDB is the master node and you are upgrading to 11.2.1.9, run:
```
/opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1/nzdeploy -U
```
- If the VDB master node is the connector node and you are upgrading to 11.2.1.8 or earlier:
  1. On 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
  3. Run the command with -U option and -m option with missing domain name on CN to upgrade the container and extract the NPS software package.
    /opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1/nzdeploy -U -m domain1 -m domain2
    Example:
    /opt/ibm/appliance/storage/ips/ips1_deployment/v11.2.1.1/nzdeploy -U -m rtp.raleigh.ibm.com

What to do next

Upgrade the software to 11.2.1.9 or earlier.