IBM DataPower Operations Dashboard v1.0.20.x

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Configuration for Appliance Firmware Upgrade

Note: In a cell environment, the DPOD server mentioned below is the Cell Manager.

In order to use the appliance firmware upgrade feature, some special configuration needs to be done:

  1. Change the "Firmware Upgrade - Repository Path" in the system parameters page to a new dedicated mount point on DPOD server.

  2. Change the "Firmware Upgrade - Local Node IP Address" in the system parameters page to the IP address of the DPOD server that monitored gateways should use to access it via SSH.
    Make sure the gateways can access the DPOD server using this IP address and port 22, and that no firewall or routing issues prevent that.

  3. Change the "Firmware Upgrade - OS User Name" and "Firmware Upgrade - OS User Password" in the system parameters page to the DPOD server user and password that will be used to access the DPOD server via SSH.

    1. For Appliance Installation - The user is initially locked, you will need to unlock the user, change its password and update the system parameter:

      1. Login to the DPOD server as root user.

      2. Unlock the user by issuing the command: "passwd -u productuser1 -f"

      3. Change the user's password by issuing: "passwd productuser1", the maximum password length is 30 characters.

      4. Update the system parameters mentioned above.
    2. For Non Appliance installation or Docker container installations:

      1. The system administrator should create a user called "productuser1. An example of an OS command for creating the OS user:

        useradd -md /home/productuser1 -s /bin/bash productuser1


      2. Update the system parameters mentioned above.

  4. Verify that the password configured above is not expired by manually logging in to the DPOD server using SSH with the configured user name and password.

  5. Verify that the user configured above has access to the repository path configured above. The access to the directory should include “x” (executable), so the user is able to list the files in the directory.
    While connected with the user, try to list (ls) the repository path and make sure it works.



Copyright © 2015 MonTier Software (2015) Ltd.