DPOD’s appliance installation is packaged as an ISO file, in order to support installation on both physical and virtual servers. It includes 2 two steps:
Operating System The operating system installation (a CentOS Rocky Linux operating system that ), which is pre-loaded in the ISO file and is managed by DPOD).
Software The DPOD application deployment.
...
Info |
---|
Do not install any packages |
...
(RPMs) on the operating system that is managed by DPOD ( |
...
e.g.: by executing |
...
Do not update the |
...
Rocky Linux version or any other component within DPOD using external repositories ( |
...
e.g.: by executing |
Prerequisites
Allocate CPU and RAM according to the chosen deployment profile as listed in Hardware and Software Requirements.
DPOD requires 3 disks (LUNs / physical / virtual):
1 disk for the operating system
1 disk for the application and logs
At least 1 disk for the data
The sizes of the disks are described in Hardware and Software Requirements.
Obtain the Software and the Activation Key
Download the ISO file and its md5 checksum file from Passport Advantage (file name is
DPOD_Appliance_<VERSION>.iso
).
Verify the ISO file integrity by calculating its md5 checksum and comparing it to the downloaded md5 checksum file.Download the activation key file from Passport Advantage (file name is
DPOD-full-version-activation-key-<KEY-VERSION>.zip or DPOD
orDPOD-api-calls-activation-key-<KEY-VERSION>.zip
):The activation key is included in the download assembly for the program you purchased. In Passport Advantage, make sure to select version “1.0.x” (and not the specific DPOD version).
For the full version, please apply the activation key found in eAssembly "IBM DataPower Operations Dashboard V1.0.x Full Version Activation eAssembly" (G071VEN/M088JEN).
For the API calls version, please apply the activation key found in eAssembly "IBM DataPower Operations Dashboard V1.0.x API Calls Version Activation eAssembly" (G071TEN/M088HEN).The activation key file is a password-protected zip file. Do not try to unzip the activation key zip file.
OS Deployment
Prerequisites
The server needs to have 3 disks, as documented in Hardware and Software Requirements.
...
Deploy the Operating System
Launching the Installation
Set the DPOD ISO file on as your virtual/physical server's DVD.
Make sure the server is boots using the Legacy BIOS UEFI firmware (and not UEFI, as currently the ISO file does not support UEFIthe Legacy boot).
Make sure the DVD is configured correctly in the server’s boot order.
Power on the virtual/physical server.
On the OS launch screen, choose “Install Appliance” DPOD Appliance - Standard” to start the automatic OS installation for Standard Edition (the Developer Edition should have a slightly different launch screen stating this is the Developer Edition):
the Standard Edition:The required packages will now be installed. Wait for the installation to complete before proceeding (this should take a few minutes).
Network Configuration
When the OS installation completes, you will be presented with the Network Configuration screen, used to provide DPOD with the network information it requires.
Enter DPOD's the host name, e.g. dpod25min : dpod-server (you may add the host name to your organization's DNS).
Enter the IPv4 address, e.g.: 192.168.65.170
Enter the network netmask, e.g.: 255.255.255.0
Enter the default gateway: e.g.: 192.168.65.2
Enter primary and secondary DNS server IP addresses (not mandatory)
.
When the network data entry process is complete, DPOD echoes it back on the screen for verification and displays an 'Is this correct [y/n]' prompt. :
Enter “y” to confirm the network details as entered or “n” to re-enter the information.
Setting Passwords
Set The installation will prompt for passwords for the following users:
Change DPOD's OS administrative user (productadm) password:
Change root user passwor:
dpodadm
- an administrative user used to log in to the server via SSH, and has permission to usesudo
.root
- the root user (which is denied from connecting via SSH).
OS Installation Finalization
When you've completed all the steps above, before you press ENTER to restart the machine, you should disable/eject your DVD in from the virtual or /physical server so to make sure the installation is not launched again after the restart. Press ENTER and wait for the server to restart.
...
Application Deployment
Log in to the DPOD's server console with the user
root
dpodadm
(e.g.: using SSH, VMware console, a KVM switch, or the physical server console).Do not use SSH to connect to the DPOD server, as for security reasons, SSH sessions are limited to 300 seconds and your session might time out during installation. If you must use SSH, you can configure the timeout limit by following the steps in SSH Session to DPOD Disconnects Often.run
Login again as root or just use thelsblk
and make sure the three required disks were mounted, and are in the correct order (OS, Install and Data disks, as explained on Hardware and Software Requirements).
Run theinstallApp
command to start the product installationRun the following command to launch the DPOD application deployment:su -
commandCode Block language bash installApp
Adjust the date, time and time zone if required:
If you choose to change the current time zone configuration, you will be prompted for time zone selection. Select your country's region and country.
DPOD will suggest a time zone based on your country selection, and display an 'Is the above information OK?' prompt. You may confirm the time zone configured by choosing 1 for “yes” or 2 for “no”.On the next screen you may configure the NTP (Network Time Protocol) servers DPOD will use. Keeping the internal clocks of DPOD and the monitored appliances in sync is important - as DPOD reports the time as logged by the devices themselves.
Enter the NTP servers information.
After you finish entering the NTP data, DPOD echoes it back on the screen for verification and displays an 'Is this correct [y/n]' prompt.
Enter “y” to confirm NTP details as entered or “n” to re-enter the information.Choose an environment name for this DPOD installation, each DPOD installation must have a unique 4-character environment name.
Choose whether you use SSD storage
Read the End User License Agreement (EULA) and if you accept the term please press 1 to accept it. You may also press 0 to decline the agreement and abort the installation.
On the following screen, choose the deployment profile that fits your requirements (see Hardware and Software Requirements page):
Note that the list might change, and the options available to you may not match those shown above.
tWait for the installation to finish.
Any errors will be logged to the installation log file, displayed at the end of the installation process.
The /installs/logs directory contains detailed install logs for each component.After displaying the messages "Stopping/Starting ...", the installation will work in silent mode - without any further messages for ~ 5 minutes, this is a normal behavior.
When the installation is completed, you should see the following output:
r in screenshotsudo /opt/APPL-setup
Follow the instructions and provide any required information (such as environment name, time zone, etc.):
Do not interrupt the software update process after you confirmed it and the background process has started.
If SSH connection is lost during upgrade, the upgrade will still continue. Reconnect to the server and check the log files for the process status and outcome.