Performing a Silent Installation

This appendix contains the following section:

Performing a Silent Installation

This appendix describes how to perform a silent installation, upgrade, or uninstallation of the Cisco Prime Network Registrar product. A silent installation or upgrade allows for unattended product installations based on the configuration values that are provided at the time that a silent installation response file was created.


Caution

Unpredictable results can occur if you try to use a silent-response file that does not contain the correct settings for the system undergoing the silent installation.

To generate or create a silent-response file:

Procedure

Step 1

For each silent installation or upgrade, use these commands to create a separate response file:

  • Windows: 

    setup.exe -r

    Complete the installation or upgrade steps as you normally would. This command installs or upgrades Cisco Prime Network Registrar according to the parameters that you specified.

    Note 

    If Cisco Prime Network Registrar is already installed, setup.exe uninstalls the existing version and if Cisco Prime Network Registrar is not installed, then it does the installation.

    It also generates the setup.iss silent-response file based on these parameters. Look for this file in the Windows installation directory, such as C:\WINDOWS. Each time you use the command, the file is overwritten.

    We recommend that you rename or relocate this file before running the silent process in Step 2. Rename the file to something distinguishable, such as local-nr-https-install, and relocate it to a temporary folder.

  • Linux:

    Create a text silent-response file that includes the entries listed in the table below.

    Table 1. Silent-Response File Entries for Linux
    Silent-Response File Entry Description

    BACKUPDIR=

    Path where to store the current Cisco Prime Network Registrar installation files, but only if PERFORM_BACKUP=y

    CCM_LOCAL_SERVICES=

    Services (dhcp, dns or cdns) to enable

    CCM_PORT=

    Central Configuration Management (CCM) port; default value is:

    • 1234 if CNR_CCM_MODE=local

    • 1244 if CNR_CCM_MODE=regional

    CCM_REGIONAL_IP_ADDR=

    IPv4 address of the regional server

    CCM_REGIONAL_IPV6_ADDR=

    IPv6 address of the regional server

    CCM_REGIONAL_SCP_PORT

    SCP port number on the regional server

    CNR_ADMIN=

    Superuser name. To skip configuring the superuser name, value should be CNR_ADMIN=unset.

    NRADMIN=

    Non-root user. To install Cisco Prime Network Registrar as non-root user, value must be NRADMIN=y.

    CNR_PASSWORD=

    Superuser password. To skip configuring the superuser password, value should be CNR_PASSWORD=unset.

    CNR_CCM_MODE=

    CCM mode; set to local or regional.

    CNR_CCM_TYPE=

    Reserved for GSS installation. Always set to cnr.

    CNR_EXISTS=

    If set to y (recommended), tries to kill any open CLI connections when installing or upgrading; otherwise, basically deprecated.

    CNR_LICENSE_FILE=

    Fully qualified path to the license file. Set CNR_LICENSE_FILE=unset if CNR_CCM_MODE=local.

    CNR_SECURITY_MODE=

    Security mode configuration:

    • Required. Fail if the connection cannot be secured.

    • Optional. Allow fallback to insecure connection.

    • Disabled. Do not load security modules at startup.

    DATADIR=

    Fully qualified path to the data directory.

    JAVADIR=

    Fully qualified path to the Java installation (JRE 1.8).

    KEYSTORE_FILE=

    If USE_HTTPS=y, the fully qualified path to the keystore file.

    KEYSTORE_PASSWORD=

    If USE_HTTPS=y, the password used when generating the keystore file.

    LOGDIR=

    Fully qualified path to the log file directory.

    PERFORM_BACKUP=

    Specifies whether or not to back up the current installation files, if present. Can be set to y even on a clean installation (see also BACKUPDIR).

    ROOTDIR=

    Fully qualified installation path for the product files; contains bin, classes, cnrwebui, conf, docs, examples, extensions, lib, misc, schema, tomcat, and usrbin subdirectories.

    START_SERVERS=

    Must be set to y for a full installation (with protocol servers) to assure the installation or upgrade is completed; it also results in the Cisco Prime Network Registrar product being started after the install/upgrade. For a client-only installation, must be set to n.

    TEMPDIR=

    Fully qualified path to the temp directory.

    USE_HTTP=

    Sets whether or not the web UI server listens for HTTP connections; one or both of USE_HTTP or USE_HTTPS must be set to y.

    USE_HTTPS=

    Sets whether or not the web UI server listens for HTTPS connections; one or both of USE_HTTP or USE_HTTPS must be set to y (see also KEYSTORE_FILE and KEYSTORE_PASSWORD).

    WEBUI_PORT=

    Port number that the web UI uses for HTTP traffic; default value is:

    • 8080 if CNR_CCM_MODE=local

    • 8090 if CNR_CCM_MODE=regional

    WEBUI_SEC_PORT=

    Port number that the web UI uses for HTTPS traffic; default value is:

    • 8443 if CNR_CCM_MODE=local

    • 8453 if CNR_CCM_MODE=regional

    WS_PORT=

    Port number that the web service uses for HTTP traffic; default value is:

    • 8080 if CNR_CCM_MODE=local

    • 8090 if CNR_CCM_MODE=regional

    WS_SEC_PORT=

    Port number that the web service uses for HTTPS traffic; default value is:

    • 8443 if CNR_CCM_MODE=local

    • 8453 if CNR_CCM_MODE=regional

    WEB_SERVICES= Set to y or n to enable or disable the web services (DNS ENUM and REST API).

    CNR_BYOD_ENABLE=

    Set to y or n to enable or disable the BYOD services.

Step 2

Use these commands to invoke the silent installation or upgrade for each instance:

  • Windows: 

    setup.exe -s -f1path+response-file
    Note 

    The silent installation fails if you do not specify the -f1 argument with a fully qualified path to the response file, unless the response file is located in the i386 directory and setup.exe is run from that directory.

  • Linux: 

    install_cnr -r response-file
Step 3

If you want to uninstall the product:

  • Windows—Generate an uninstallation response file and execute: 

    setup.exe -s -f1uninstall_response_file

  • Linux—Invoke the silent uninstallation (this command is noninteractive except during an error): 

    uninstall_cnr