Prepare to Install NetOps Portal

Complete these requirements before you install.
capm360
HID_Prepare_to_Install_CAPC
To ensure that your
NetOps Portal
installation is successful, complete the requirements before you install
NetOps Portal
:
2
Verify the Prerequisites
Complete the following prererequisites before you install
NetOps Portal
:
  • You can install the software in any filesystem to which the root user has write access. The default installation directory is
    <installation_directory>
    /PerformanceCenter
    . You can select another location while running the setup program.
  • Verify that Security Enhanced Linux (SELinux) is disabled on the server where you plan to install
    NetOps Portal
    . By default, some Linux distributions enable this feature, which does not allow the product to function properly.
    For more information about how to configure an SELinux security policy, see the Red Hat documentation.
  • By default, the MySQL database is installed in the
    /opt/CA/MySql/
    directory, but you can select another directory during the installation. Verify that the selected filesystem has enough allocated disk space to support a database.
  • To avoid database corruption, exclude the installation directory, and all its subdirectories, from antivirus scans. Prevent scanning by a local instance of an antivirus client and scanning by a remote antivirus instance. Exclude the following directories:
    • /opt/CA
      /MySql/
    • /opt/CA
      /MySql/bin
    • /opt/CA
      /MySql/data
    • /opt/CA/CA/MySql/tmp
    • <installation_directory>
      /PerformanceCenter
  • NetOps Portal
    requires DNS resolution. If you do not have DNS configured, add system entries to the
    /etc/hosts
    file on your server.
  • Verify that the
    /tmp
    location has at least 4 GB of space available.
  • The installer requires the zip and unzip packages. If you do not have these packages installed, install them using one of the following commands:
    yum -y install zip unzip
    SLES:
    zypper install -y zip unzip
  • NetOps Portal
    requires the wget package. If you do not have this package installed, install it using one of the following commands:
    yum -y install wget
    SLES:
    zypper install -y wget
  • Some of the available scripts require Perl. Verify that it is installed.
Set the Limit on the Number of Open Files
Verify that the user account that is installing
NetOps Portal
has a value of at least 65536 on the number of open files. Set this value permanently.
For systems where a sudo user installs
NetOps Portal
, the user installing might not have the required permissions to complete this procedure. Work with the system administrator to configure the limit.
Follow these steps:
  1. Log in to the
    NetOps Portal
    host.
  2. Edit the
    /etc/security/limits.conf
    file.
  3. Add the following lines to the file:
    # Added by Performance Center
    * soft nofile 65536
    # Added by Performance Center
    * hard nofile 65536
  4. Restart the login session.
  5. Verify that the number of open files is set properly by issuing the following command:
    ulimit -n
    The command returns the limit that you have specified.
Verify Communication Ports
DX NetOps Performance Management
uses multiple ports to communicate with various components, particularly data sources. In addition, some of the products and components that integrate with
DX NetOps Performance Management
have specific port requirements. For
DX NetOps Performance Management
to work correctly in a firewall-protected environment, certain ports must be open.
Verify the ports that must be open:
  • The ports that allow
    NetOps Portal
    services to communicate with
    NetOps Portal
    .
  • The ports that allow users to contact
    NetOps Portal
    .
  • The ports that allow other data sources to contact
    NetOps Portal
    for eventing and OpenAPI single sign-on.
  • For any firewall that protects the
    DX NetOps Performance Management
    server, the ports and protocols for the data sources that you are deploying.
  • The ports that the other data sources use.
    For more information about the list of required ports and protocols, see the documentation for each data source.
For a detailed list of these ports, see Review Installation Requirements and Considerations.
Verify Time Synchronization
Time synchronization using the Network Time Protocol (NTP) daemon is required for
NetOps Portal
and is recommended for all data source consoles. On Linux servers, the NTP daemon ensures that the clocks on the hosts are synchronized for timing purposes. Verify that the daemon is running on the
NetOps Portal
host server.
Verify on SLES Systems
Follow these steps:
  1. Open a console and issue the following command:
    $ systemctl status ntpd
  2. Verify that the NTP daemon is in an active (running) state.
  3. Start and enable the NTP daemon manually by issuing the following command:
    $ systemctl start ntpd
    $ systemctl enable ntpd
The daemon is started.
Verify on RHEL 7.x or OL 7.x Systems
RHEL 7.x and OL 7.x. run NTP with
chronyd
.
Follow these steps:
  1. Open a console and issue the following command:
    $ systemctl status chronyd
  2. Verify that the
    chrony
    daemon is in an active (running) state.
  3. Start and enable the
    chrony
    daemon by issuing the following command:
    $ systemctl start chronyd
    $ systemctl enable chronyd
The daemon is started.
Verify on RHEL 6.x Systems
Follow these steps:
  1. Open a console and issue the following command:
    $ chkconfig --list ntpd
    If the NTP daemon is installed, the output resembles the following example:
    ntp 0:off 1:off 2:on 3:on 4:off 5:on 6:off
    The output indicates the runlevels where the daemon runs.
  2. Verify that the current runlevel of the system (usually 3 or 5) has the NTP daemon set to 'on'. If you do not know the current runlevel, find it by issuing the following commands:
    $ runlevel
    N 3
    If the current runlevel does not have the NTP daemon enabled, enable it by issuing the following command:
    $ chkconfig --level
    current_runlevel
    ntpd on
    Example:
    $ chkconfig --level 3 ntpd on
  3. Start the NTP daemon by issuing the following command:
    $ service ntpd start
The daemon is started.
(Optional) Configure the Sudo User Account for
NetOps Portal
If you do not have root access to install and run
NetOps Portal
, configure the sudo user account.
With the sudo user configured, you can add the sudo prefix to all commands to install
NetOps Portal
.
Example:
sudo ./CAPerfCenterSetup.bin
Follow these steps:
  1. Locate the following file on the
    NetOps Portal
    host:
    /etc/sudoers
  2. Add a command alias with the following permissions to the file:
    • /tmp/CAPerfCenterSetup.bin
    • /etc/init.d/caperfcenter_console
      (for RHEL 6.x)
    • /etc/init.d/caperfcenter_devicemanager
      (for RHEL 6.x)
    • /etc/init.d/caperfcenter_eventmanager
      (for RHEL 6.x)
    • /etc/init.d/caperfcenter_sso
      (for RHEL 6.x)
    • /etc/init.d/mysql
    • <installation_directory>
      /PerformanceCenter/PC/bin/caperfcenter_console
      (for RHEL 7.x, SLES, OL)
    • <installation_directory>
      /PerformanceCenter/DM/bin/caperfcenter_devicemanager
      (for RHEL 7.x, SLES, OL)
    • <installation_directory>
      /PerformanceCenter/EM/bin/caperfcenter_eventmanager
      (for RHEL 7.x, SLES, OL)
    • <installation_directory>
      /PerformanceCenter/sso/bin/caperfcenter_sso
      (for RHEL 7.x, SLES, OL)
    • <installation_directory>
      /PerformanceCenter/Tools/bin/npcshell.sh
    • <installation_directory>
      /PerformanceCenter/SsoConfig
    • <installation_directory>
      /PerformanceCenter/Uninstall_MySql
    • <installation_directory>
      /PerformanceCenter/Uninstall_PerformanceCenter
    • <installation_directory>
      /PerformanceCenter/Uninstall_SSO
    • /sbin/service
    • /opt/CA/MySql/bin/mysql
    • /opt/CA/MySql/bin/mysqldump
    • <installation_directory>
      /PerformanceCenter/sso
    • <installation_directory>
      /PerformanceCenter/PC
    • <installation_directory>
      /PerformanceCenter/PC/webapps/pc/apps
    • <installation_directory>
      /PerformanceCenter/PC/webapps/pc/css/CA-Blue/images
    • <installation_directory>
      /PerformanceCenter/PC/webapps/pc/css/CA-Gray/images
    • /usr/bin/vim
    • /opt/CA/jre/bin/keytool
    • <installation_directory>
      /PerformanceCenter/RemoteEngineer/re.sh
    • <installation_directory>
      /PerformanceCenter/SslConfig
    Separate the permissions with commas and place all permissions on a single line.
    Example:
    Cmnd_Alias CAPERFCENTER = /tmp/CAPerfCenterSetup.bin,
    <installation_directory>
    /PerformanceCenter/PC/bin/caperfcenter_console,
    <installation_directory>
    /PerformanceCenter/DM/bin/caperfcenter_devicemanager,
    <installation_directory>
    /PerformanceCenter/EM/bin/caperfcenter_eventmanager,
    <installation_directory>
    /PerformanceCenter/sso/bin/caperfcenter_sso,/etc/init.d/mysql,
    <installation_directory>
    /PerformanceCenter/Tools/bin/npcshell.sh,
    <installation_directory>
    /PerformanceCenter/SsoConfig,
    <installation_directory>
    /PerformanceCenter/Uninstall_MySql,
    <installation_directory>
    /PerformanceCenter/Uninstall_PerformanceCenter,
    <installation_directory>
    /PerformanceCenter/Uninstall_SSO,/sbin/service,/opt/CA/MySql/bin/mysql,/opt/CA/MySql/bin/mysqldump,
    <installation_directory>
    /PerformanceCenter/sso,
    <installation_directory>
    /PerformanceCenter/PC,
    <installation_directory>
    /PerformanceCenter/PC/webapps/pc/apps,
    <installation_directory>
    /PerformanceCenter/PC/webapps/pc/css/CA-Blue/images,
    <installation_directory>
    /PerformanceCenter/PC/webapps/pc/css/CA-Gray/images,/usr/bin/vim,/opt/CA/jre/bin/keytool,
    <installation_directory>
    /PerformanceCenter/RemoteEngineer/re.sh,
    <installation_directory>
    /PerformanceCenter/SslConfig
    sudouser
    ALL = CAPERFCENTER
    • sudouser
      Specify the user who can run the sudo commands.
Configure UTF-8 Support
Configure
NetOps Portal
host to support UTF-8 encoding. Enable UTF-8 encoding to ensure that characters display properly during the installation.
The appropriate language packs are also required to support localized deployments.
Some scripts that are used in the installation of selected components are not localized and run in English. For more information, see the
Localization Status Readme
file.
Follow these steps:
  1. Do
    one
    of the following steps:
    1. Type the following command from a Korn or bash shell:
      export LANG=
      LANG_value
      ; export LC_ALL=$LANG
      LANG_value
      specifies the language that you want the product to support. The following variables are supported:
      • English:
        en_US.utf8
      • French:
        fr_FR.utf8
      • Japanese
        :
        ja_JP.utf8
      • Simplified Chinese:
        zh_CN.utf8
      • Traditional Chinese:
        zh_TW.utf8
      For example:
      export LANG=zh_TW.utf8 ; export LC_ALL=$LANG
    2. Issue the following command from a Bourne Shell:
      LANG=
      LANG_value
      ; export LANG
      LC_ALL=
      LANG_value
      ; export LC_ALL
      For example:
      LANG=zh_CN ; export LANG
      LC_ALL=zh_CN ; export LC_ALL
The language variable is set.
Install the Required and Non-English Fonts
For the installer to run, and for
NetOps Portal
to generate PDF files, follow the standard instructions for installing the necessary fonts on your operating system.
NetOps Portal
and its data sources support multiple languages. The administrator can select a preferred language for each unique product operator. Language packs take advantage of operating system support for localized environments.
Product operators with some language preferences may not be able to view dashboard data in reports by default. To support these language preferences, install the fonts on the
NetOps Portal
host.
Follow these steps:
  1. Log in to the
    NetOps Portal
    host.
  2. Install the fonts by issuing
    one
    of the following commands:
    yum groupinstall fonts
    SLES:
    zypper install dejavu-sans-fonts dejavu-fonts-common arphic-ukai-fonts arphic-uming-fonts ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts baekmuk-bitmap-fonts baekmuk-ttf-fonts liberation-fonts
  3. Rebuild the font caches by issuging the following command:
    fc-cache –v
    SLES:
    fc-cache -fv
  4. Restart
    NetOps Portal
    .
The required and non-English fonts are installed on the
NetOps Portal
host.