Install 
DX Platform

This section provides the following information:
dxp10
This section provides the following information:
Download the Installer Distribution File
The 
DX Platform
 installer is bundled with the DX APM distribution zip file (DX Application Performance Management - <version>). This distribution file includes the 
DX Platform
 files for:
  • Online installation:
     Use this method when the installing host has access to the Internet. In this mode, download the online version of the installer from the  site. The installer connects to the public registry using the access token and downloads the latest product images. For online installation credentials, contact your 
    Customer Success Associate (CSA) or Broadcom Support
    .
  • Offline installation:
     Use this method when the installing host does not have access to the Internet. In this mode, download the offline version of the installer from the  site. The downloaded installation package contains all the images, binaries, and dependencies. The installer retrieves the product images from a file which is included in the offline version of the install script.
Follow these steps:
  1. Create a directory named 
    install_directory
     on a host that has access to the Kubernetes cluster.
  2. Log in to the 
    Support
     site using your credentials.  
  3. Navigate to the 
    DOWNLOAD MANAGEMENT
     section. 
  4. Search for 
    Application Performance Management
    .
  5. In the 
    Product Downloads
     section, select the version.
  6. Click 
    Download
     to download the zip file to the 
    install_directory
     folder.
    • Online Installer
      DXCommonPlatformInstaller-<version>-online 
       (About 50 MB)
    • Offline Installer
      DXCommonPlatformInstaller-<version>-offline 
       (About 20 GB)
  7. Extract the downloaded zip file.
    • Online Installer
      DXCommonPlatformInstaller-<version>-online.tar.gz 
    • Offline Installer
      DXCommonPlatformInstaller-<version>-offline.tar.gz 
Run the Installer
Before you run the installer, consider the following points:
You can run the installer in one of the following ways:
  • Interactive Console Install Mode:
     In this mode, you must provide the inputs at the prompt for the installation.
  • Silent Install Mode:
     In this mode, the 
    DX Platform
     is installed using the values mentioned in the 
    dxi.input.vars.yml
     file. This file is available in the root installation folder. To install in silent mode, we recommend running the installer in the Interactive Console Install mode first to generate the 
    dxi.input.vars.yml
     file. 
If you are installing the 
DX Platform
 for the first time, you must run the installer in the 
Interactive Console Install
 mode. Perform the following steps to install the 
DX Platform
 in the Interactive Console Install mode.
Before you install the 
DX Platform
, you can use the Environment validation flag (
--validate
) to verify if the hardware resources (requirements) are available and if the NFS directory is created.
Online Installation:
./install.sh -u=<username> -p=<password> --ignore-errors --validate
Offline Installation:
./install.sh --ignore-errors --validate
The 
--ignore-errors
 flag enables the installer to continue with the installation even if the pods do not start in the given time frame.
Follow these steps:
  1. Navigate to the install directory.
    cd <install directory>
  2. Initiate the installer:
    • Online Install:
       If you use this option, the installer pulls the images from the Bintray repository. For the online installation credentials, contact your 
      Customer Support Associate (CSA) or Support
      .
      ./install.sh -u=<username> -p=<password> --ignore-errors
    • Offline Install:
       If you use this option, the installer loads images from the local file.
      ./install.sh --ignore-errors
    The --ignore-errors flag enables the installer to continue with the installation even if the pods do not start in the given time frame.
    Additional flags supported by the installer:
    • --silent
       - Use this flag to run the installer in the Silent mode. The Silent mode requires the 
      dxi.input.vars.yml
       file to be located in the installer directory with the necessary values. To install in the 
      Silent mode
      , we recommend running the installer in the 
      Interactive Console Install
       mode first to generate the 
      dxi.input.vars.yml
       file. 
    • --skip-ssl
       - Use this flag to skip validating the self signed certificates for HTTPS communication.
    • --skip-checks
       - Use this flag to skip all the user input validations. We do not recommend using this flag.
  3. Provide the required information at the prompt:
    1. Accept the terms of the CA End-User License Agreement: 
      • Y:
         Type Y to proceed with the installation.
      • N:
         Type N to quit the installation.
    2. Installation type: 
      • 1. 
        Kubernetes:
         Type 1 for Kubernetes-based installation. In this release, only Kubernetes is supported. 
    3. Registry installation: 
      • 1. install:
         Type 1 to install a registry in the cluster using the installer. If a registry already exists, t
        he installer displays a message to select the 
        use_existing
         option.
      • 2. use_existing:
         Type 2 to provide the URL of your own registry. For more information about setting up the private docker registry, see the 
        Set Up and Configure the Private Docker Registry
         section.
        • (Conditional) Specify the registry URL: 
          Specify the private docker registry URL of your organization. If this URL requires authorization, then the installer prompts for the username and password.
          Validation:
           Installer pushes an image to the registry to validate the access.
    4. Specify the Kubernetes namespace for installation:
       Specify the Kubernetes namespace. All the pods are deployed in the namespace you specify here.
      Validation:
       The namespace must contain alphanumeric characters in lowercase. The namespace must start and end with an alphanumeric character and can be separated by '-'. For example, '
      my-name
      '. 
      After you specify the namespace, the installer displays the Master IP from the kube config file. 
    5. (Conditional) Choose Kubernetes cluster:
       This prompt is displayed only if multiple clusters are mentioned in the kube config file. Choose the cluster for the installation. 
    6. (Conditional) Choose Kubernetes user:
       This prompt is displayed only if multiple users are mentioned in the kube config file. Choose the user for the installation. 
      The installer supports both the following Kubernetes account types: 
      • client-certificate/client-key
      • username/password
      To use the Kubernetes account, the user should exist in the Kubernetes cluster. This user should have cluster admin privileges to create a namespace and PV. This user should also be mentioned in the kube config file.
      For example,
      users:
      - name: minikube
      user:
      client-certificate: /root/.minikube/client.crt
       client-key: /root/.minikube/client.key
      - name: someuser 
      user: 
      password: <password> 
      username: <username>
      Validation:
       The installer validates the Nginx Ingress Controller version (0.23.0 or higher). If the version is incorrect, the installer exits.
    7. Specify the Wildcard DNS:
       Enter the wildcard DNS of the node running the Ingress Controller or the load balancer.
      Validation:
       Installer verifies if this host is reachable by pinging this host.
    8. Do you want secure routes:
       
      • Y:
         Type 
        Y
         to enable the secure route for HTTPS encrypted communication. We recommend using the secure route for every installation. 
        • (Conditional)
           Do you want to provide your own SSL certificate and key?
          Ensure that the generated 
          .crt
           and 
          .key
           files are placed in the 
          tls_certs
           folder in the installer directory.
          • Y:
             Type 
            Y
             to provide your own SSL certificate and key files:
            • Provide the .crt file name.
            • Provide the corresponding .key file name.
          • N:
             Type 
            N
             to generate the files using the installer. The installer generates the SSL certificate and the key in the 
            tls_certs
             folder under the install directory.
      • N: 
        Type N for no encryption using HTTP.  
    9. Specify the name of NFS server IP/host:
       Type the host name or IP address of the node where the NFS server runs. For more information, see the 
      Configure the NFS Base Directory
       section.
      Validation:
       Installer verifies if the NFS server is reachable.
    10. Specify the NFS folder: 
      Specify the name of the NFS base directory that you created in the Kubernetes cluster. For example, 
      /nfs/ca/dxi
       
      Validation:
       Installer verifies that all the nodes can read/write to this NFS base folder.
    11. (Conditional) Specify the installation size:
       Select the installation size depending on how many nodes are labeled as Elasticsearch nodes. Small installation can be used for demo and Medium installation for standard installation. 
      • 1. Small Installation: One Elasticsearch Hot node is labeled:
         Type 1 for small installation. 
      • 2. Medium Installation: Three Elasticsearch Hot nodes are labeled:
         Type 2 for medium installation. 
    12. Do you want to enable OI: 
      • Y:
         Type
         Y 
        to enable DX Operational Intelligence
      • N:
         Type 
        N
         to enable DX Operational Intelligence later. You can always enable DX OI later. For more information, see the  section.
      Validation:
       The installer validates the Max Open Files Limit, Max Map Count on all the nodes, and the Elasticsearch prerequisites. The installer also validates the hardware requirements for the installation. 
    13. (Optional) Specify the SMTP server details: 
       You can specify the SMTP server details during or after the installation. To skip this step during the installation, press ENTER. Run the 
      update-smtp-details.sh
       script to provide this information post installation.
      • Specify the SMTP service URL
         in the following format: 
        smtp/smtps://<Service_URL>:587
         
        Validation:
         None
      • (Conditional)
         
        Specify the SMTP account: 
        Specify the username.
      • (Conditional)
         
        Specify the SMTP credential: 
        Specify the password. 
        Validation: 
        The installer also validates if this SMTP server is reachable from the cluster.
    14. (Only for DX App Experience Analytics) Do you want to use the Symbolicator:
       Specify the Symbolicator IP and port. For more information, see the 
      Install and Configure Symbolicator
       section.
    15. Enter the password for the master admin: 
      Enter a password for the Master Administrator. This account allows you to create tenants and manage the DX Platform deployment. If the admin password reset fails, the default password (master1234!) is used.
      Validation:
       The password must be 6 - 25 characters long. The password must be a combination of all the following characters:
      • at least one uppercase character
      • at least one lowercase character
      • at least one number, and
      • at least one special character ((!, @, #, $, %, ^, &, *, _, +))
    16. Re-Enter the password for the master admin: 
      Re-enter the same password.
      Validation:
       The password must match the password that was entered in the previous step.
    On successful installation, the installer displays the confirmation message and the URL (
    http://apmservices-gateway.<domain>/dxiportal
    ) to log in to the Cluster Management console (DX Platform). 
    Verify the Installation
    After the installation, run the following command to verify the status of the pods. The status must display as Running or Completed (you may have to wait a few minutes).
    kubectl get pods -n <namespace>
    If some of the pods are not in the 
    Running
     or 
    Completed
     state even after a couple of minutes, contact the Broadcom support. 
    For initiation logs, you can check the 
    <host>:/nfs/ca/dxi/dxi-platform-init-pod/dxi-platform-init-pod.log
     file. This log file lets you know if the master admin has been reset and if the global admin account was created successfully. 
    Login to the Cluster Management
    After you have installed and verified the installation, log in to the Cluster Management console as a Master Administrator.
    Follow these steps:
    1. Open the URL that was displayed after the installation: 
      http://apmservices-gateway.<domain>/dxiportal
    2. Provide the following details:
      • Tenant Id: masteradmin
      • Username: masteradmin
      • Password: The master admin password that you provided during the installation. If the password does not work, try 
        master1234!
         which is the default password. If the password gets locked after several attempts, see the 
        Troubleshooting the Installation
         section.
    Once logged in, proceed with the steps described in the 
    Post Installation Tasks
     section.