> Managing Mobility Unified Reporting System Installation
> This chapter describes how to install, upgrade, and uninstall the MUR application.
> The following topics are explained in this chapter:

> • | Installing MUR

> • | Upgrading MUR

> • | Uninstalling MUR

> Important: The procedures for installation, upgrade, and uninstallation of MUR and RDP remain the same.
> Important: Please note that the terminologies “starbi”, “inPilot” and “mur” used throughout this guide mean the same.
> Installing MUR
> This section provides instructions on how to install the MUR application.
> Important: Make sure that your system meets the minimum requirements as indicated in the MUR System Requirements section in the MUR Overview chapter of this guide.
> The following MUR components are installed by MUR installer.

> • | For Solaris platform

> • | Apache v2.2.11 with mod_python v3.3.1

> • | Python v2.6.4

> • | Postgres v 8.2.0

> • | Django v1.0.2

> • | JRE v1.6.0_12

> • | Quartz Scheduler v1.6.4

> • | For RHEL platform

> • | Apache v2.2.11 with mod_python v3.3.1

> • | Python v2.6.1

> • | Postgres v 8.3.4

> • | Django v1.0.2

> • | JRE v1.5.0_11

> • | Quartz Scheduler v1.6.4

> Important: In RHEL-based deployment of MUR, L-ESS is NOT required as the ASR 5K ECS module can be configured to push the xDRs directly to the MUR reporting server. Push from ASR 5K is the Cisco recommended deployment model. Currently L-ESS is supported only on Solaris platforms. For information on the L-ESS installation instructions, refer to the Cisco ASR 5000 Series ESS Installation and Administration Guide. Existing deployments where L-ESS is installed, to pull EDRs from ASR 5K, may continue with their deployment model in the 12.0 version of MUR Software Release and later.
> Important: It is recommended that you first install the master MUR before proceeding with the RDP installation.
> Setting the Database Environment Strings
> Prior to installing the MUR components onto the server hardware, there are numerous system environment configuration settings that should be configured. While PostgreSQL will be installed during the installation procedure, these settings must be configured manually.
> Warning: Failure to configure these settings may cause data loss and will minimally cause errors in the operation.
> Settings for Solaris
> Add the following values to system file in the /etc/system directory if they are not present and restart the system before continuing with the installation of MUR components.
> set msgsys:msginfo_msgmnb=65536
> set msgsys:msginfo_msgtql=1024
> set shmsys:shminfo_shmmax=10737418240
> set shmsys:shminfo_shmmin=1
> set shmsys:shminfo_shmmni=256
> set shmsys:shminfo_shmseg=256
> set semsys:seminfo_semmap=256
> set semsys:seminfo_semmni=512
> set semsys:seminfo_semmns=512
> set semsys:seminfo_semmsl=270
> Settings for RHEL
> Add the following values to system file in the /etc/sysctl.conf if they are not present and restart the system before continuing with the installation of MUR components.
> kernel.shmmax=10737418240
> kernel.shmall=4294967296
> Pre-installation Checks
> Ensure the following checks are made before installing the MUR application.
> Important: Please note that L-ESS is required ONLY for a Solaris-based deployment of MUR. In the case of RHEL-based deployment of MUR, the ASR 5K ECS module is configured to push the xDRs directly from the chassis to the MUR reporting server via SFTP.

> Step 1 | The recommended filesystem for installation is ZFS. If Solaris-based installation is performed on any other filesystem, a warning message appears indicating the recommended filesystem.

> Important: Please note that the ZFS related recommendations mentioned throughout this guide are specific to SOLARIS ONLY and NOT for RHEL.

> Step 2 | MUR must be installed as a root user on the system. Installation with other user privileges is not recommended.

> Step 3 | Make sure no other Apache web server is running on the port being used for installation (default port is 8080). If it is, stop it before proceeding with the installation or provide a different port for Apache server. Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>

> Step 4 | Make sure no other Postgres server is running on the port being used for installation (default port is 5432). If it is, stop it before proceeding with the installation or provide a different port for Postgres server. Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>

> Step 5 | Make sure no other application/process is running on the port being used for pgBouncer (default 'Postgres port + 1'). If it is, stop it before proceeding with the installation or provide a different port for Postgres server so that the installer finds two consecutive ports free (one for Postgres and the other one for pgBouncer). Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>

> Step 6 | Make sure no other server is running on the port being used for installation for XML-RPC (default port is 9999). If it is, stop it before proceeding with the installation or provide a different port for XML-RPC server. Check if an application is running on a given port by entering the following command:

> netstat -an | grep <port number>

> Step 7 | MUR installation will ask for the Administrator login and Administrator Primary Group. Administrator login is the OS level administrator of MUR who will own the MUR installation. Administrator Primary Group is the user group of MUR to allow the interaction with external entities like L-ESS.

> Step 8 | If the Administrator login provided during MUR installation/upgrade already exists, ensure that it is not an already logged in user.

> Step 9 | L-ESS must be stopped before starting MUR installation / upgrade.

> Step 10 | If the L-ESS is installed as a root user, the ownership of L-ESS installation should be changed from root to non-root user. This new user must be added to MUR Group. For example, if L-ESS is initially running as root and new user created is essadmin, then perform the following sequence of operations.

> Step a | Stop L-ESS.

> Step b | Add the user essadmin to MUR group by entering the following command as root user - usermod -G <MUR Group> essadmin

> Step c | Verify whether the user is added correctly to MUR group using the command groups essadmin

> Step d | Change the ownership of L-ESS installation to this new user using the following command - chown -R essadmin <LESS installation directory>

> Step e | Login as essadmin with the command su essadmin

> Step f | Start L-ESS again.

> Step 11 | If the L-ESS is installed as a non-root user say essadmin, this user should be added to MUR Group.

> Step a | Stop L-ESS

> Step b | Add the user essadmin to MUR group by running the following command as root- usermod -G <MUR Group> essadmin

> Step c | Log off and relogin again as essadmin for the group addition to come into effect.

> Step d | Start the L-ESS application to continue pulling the EDR files from chassis and forwarding it to MUR.

> Step 12 | Perform the following steps only if the user wants to push EDR/UDR files from gateway to MUR server using SFTP mechanism. Otherwise, skip this step.

> Step a | Change to the /etc/ssh directory.

> Step b | Open sshd_config file from the directory using vi editor (or any other editor) and observe the default values for the following variables:

> PasswordAuthentication
> PAMAuthenticationViaKBDInt (Applicable ONLY for SOLARIS)
> UsePAM (Applicable ONLY for RHEL)

> Step c | Change the default values for the following variables as indicated here.

> PasswordAuthentication = yes
> PAMAuthenticationViaKBDInt = no (Applicable ONLY for SOLARIS)
> UsePAM = no (Applicable ONLY for RHEL)

> Step d | After updating restart SSH daemon using the following command:

> In the case of SOLARIS:
> svcadm restart ssh
> Important: Please note that the above command can be executed only in Solaris 10 environment.
> In the case of RHEL:
> service sshd restart

> Step 13 | The recommended user/group settings for MUR are:

> • | NIS-USER<->NIS-GROUP

> • | NON-NIS-USER<->NON-NIS-GROUP

> The NIS users should always be associated with NIS Groups. The non NIS users should be associated with Non NIS groups. Also, it is recommended to have separate non NIS users for MUR installation.
> MUR Installation
> The MUR installation files are distributed as a single compressed file.
> Important: In the MUR Software Releases prior to 11.0.100 build, this installation file is distributed with a .tar.gz extension. In the MUR Software Release 11.0.100 and later, this file is distributed in zip format.
> Important: The MUR application currently supports UCS Linux platform and Solaris-Sparc/Solaris-x86 platform. The installable tar file names help in identifying the platform. For example, mur.x.x.xx_rhel_x86.zip indicates that this file is for RHEL platform. Similarly, mur.x.x.xx_solaris_sparc.zip indicates that this file is for Solaris-Sparc platform.
> For information on downloading the appropriate MUR package for your requirements, contact your sales representative.
> The MUR application and its components can be installed using one of the following two methods.

> • | Installing MUR Using Scriptbased Installer

> • | Installing MUR Using GUIConsole based Installer

> Important: Please note that the terminologies “starbi”, “inPilot” and “mur” used throughout this guide mean the same.
> Installing MUR Using Script-based Installer
> Important: Please note that the legacy script-based installer is not supported in the MUR Software Release 11.0.100 and later.
> Important: To perform the installation procedure explained in this section, you must be logged into the server as a root user.
> Important: Fresh installation for backup recovery purpose should be installed on the same path where last backup is stored and also should have the same IP address and port configuration if the MUR is deployed in distributed mode. Make sure that the existing older installation is either removed or moved to a different directory because the metadata recovered from previously installed MUR will have all references as per older installation e.g. archive path, SFTP details, etc.
> After copying the installation file to the server, use the following procedure to install the MUR application.

> Step 1 | Change to the directory in which the file is stored.

> Step 2 | Unzip the file by entering the following command:

> tar -xvf mur_x.x.xx.tar.gz
> x.x.xx is the version of the MUR installation file.
> Important: After un-zipping the installation file, set the permission of .tar file to 700 using the following command and then continue with the installation process. - chmod 700 starbi_<release no>_<platform>.tar
> Decompressing the installation file results in the following files:

> • | README: A text file containing information pertaining to the release.

> • | install_starbi: A script to install the MUR application.

> • | starbi.tar: A compressed file containing all the application files required for MUR installation.

> • | inst: A GUI/Console based installer to install the MUR application.

> • | In_Pilot_Installer.bin: The executable used by inst to install MUR application.

> Step 3 | Execute the script by entering the following command:

> ./inst
> Important: The installation script checks the disk space in the system. If the available disk space is lesser, then the script will give an error and abort the installation process.

> Step 4 | Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.

> Parameter | Description | Default Value
> System Environment Variable Prompt
> | This dialog or script asks the user to check the variable values in system file. If one or more entries are missing, update the system file and restart the system to re-run installer. For more information, refer to the Setting the Database Environment Strings section. | N/A
> MUR Installation
> Want to proceed | Type (y)es to proceed with the installation of MUR application. | yes
> MUR Installation Directory | Type the directory on the server in which the MUR application is to be installed. | <current_directory>
> The following warning appears if the user performs installation on non-ZFS (UFS) partition path. ZFS is the recommended filesystem for installation. Warning! Path provided lies in ufs filesystem. Recommended filesystem for mur is zfs. Do you still want to continue? [no] ? Type (y)es or (n)o to proceed with the MUR installation. Important: Please note that the ZFS/UFS related warning messages are specific to SOLARIS ONLY and NOT for RHEL. | no
> Do you want to install MASTER or RDP | Type i or press Enter to install the MUR application. To install RDP type r. Refer to the following table for the parameters associated with the RDP installation. Important: Make sure that you first install the master MUR and then proceed with the RDP installation. | MASTER
> Administrator login | Type an administrator name for the Operating System (OS) level administrator of MUR. Important: Please note that you should not login as a root user. Important: The Administrator user created should be manually activated with a password once the MUR installation is complete. This can be done by entering the following command as root user: passwd <adminusername> Upon executing this command, the user will be asked to enter a suitable administrator password. | muradmin
> Administrator uid | Type the Administrator User ID for the MUR Administrator login. Important: This input will be asked only if the Administrator login name provided does not exist. | 100014
> Administrator Primary Group | Type the Primary Group name for the Administrator. Important: If the Administrator login name provided already exists, the Primary Group of this login will be considered as the MUR User Group. Otherwise, the user will be asked to enter the Primary Group information. | murgroup
> Postgres Login | This is a read-only parameter. The Postgres login name will be the same as the Administrator login name provided earlier. | muradmin
> Postgres Password | Type the password for accessing the PostgreSQL database. | N/A
> Postgres Port | Type the port number over which PostgreSQL communication will occur with MUR. Important: Ensure that no other application/process is running on configured port as well as on next consecutive port (as this port will be used for pgBouncer). | 5432
> Apache Port | Type the port number over which Apache web server communication will occur with MUR. Important: Be sure no other Apache web server is running on port which you are using while installation. If the port is being used, abort the installation. For RHEL: Apache port provided should be > 1024. RHEL does not allow port 80 to be used by non-root users. However, Apache web server requests made on Port 80 can be redirected to a port >1024 defined by the operator, with the following two commands. For example, to redirect requests made on port 80 to port 8080: iptables -t nat -A PREROUTING -p tcp --dport 80 -i eth0 -j REDIRECT --to-port 8080 iptables -t nat -A OUTPUT -p tcp --d 127.0.0.1--dport 80 -j REDIRECT --to-port 8080 For Solaris: For using the Apache port < 1024, run the following command as root user once the installation is complete, and restart the Apache server. usermod -K defaultpriv=basic,net_privaddr <MUR admin user> For example: usermod -K defaultpriv=basic,net_privaddr muradmin Important: This poses a major security concern as it will allow muradmin to use all standard ports < 1024. | 8080
> RPC Port | Type the port number over which XML-RPC server communication will occur with MUR. Important: Be sure no other XML-RPC server is running on configured port. | 9999
> Archive Directory | Type the directory path for archiving parsed files. | <mur_install_dir>/archive
> The following warning appears if the user performs installation on non-ZFS (UFS) partition path. ZFS is the recommended filesystem for installation. Warning! Path provided lies in ufs filesystem. Recommended filesystem for mur is zfs. Do you still want to continue? [no] ? Type (y)es or (n)o to proceed with the MUR installation. Important: Please note that the ZFS/UFS related warning messages are specific to SOLARIS ONLY and NOT for RHEL. | no
> MUR Configuration Confirmation
> Proceed with installation | Type (y)es to proceed with MUR installation. | yes
> Do you want to start the MUR components | Type (y)es to start the MUR components immediately after installation. | yes

> ‌

> Parameter | Description | Default Value
> Administrator login | Type an administrator name for the Operating System (OS) level administrator of RDP. Important: Please note that you should not login as a root user. Important: The Administrator user created should be manually activated with a password once the MUR installation is complete. This can be done by entering the following command as root user: passwd <adminusername> Upon executing this command, the user will be asked to enter a suitable administrator password. | muradmin
> Administrator uid | Type the Administrator User ID for the MUR Administrator login. Important: This input will be asked only if the Administrator login name provided does not exist. | 100014
> Administrator Primary Group | Type the Primary Group name for the Administrator. Important: If the Administrator login name provided already exists, the Primary Group of this login will be considered as the MUR User Group. Otherwise, the user will be asked to enter the Primary Group information. | murgroup
> Postgres Login | This is a read-only parameter. The Postgres login name will be the same as the Administrator login name provided earlier. | muradmin
> Postgres Password | Type the password for the Postgres database administration. | N/A
> Postgres Port | Type the port number over which PostgreSQL communication will occur with RDP. Important: Ensure that no other application/process is running on configured port as well as on next consecutive port (as this port will be used for pgBouncer). | 5432
> Apache Port | Type the port number over which Apache web server communication will occur with RDP. Important: Be sure no other Apache web server is running on port which you are using while installation. If the port is being used, abort the installation. For RHEL: For RHEL, Apache port provided should be > 1024. RHEL does not allow port 80 to be used by non-root users. However, Apache Web server requests made on port 80 can be redirected to a port >1024 defined by the operator, with the following two commands. For example, to redirect requests made on port 80 to port 8080: iptables -t nat -A PREROUTING -p tcp --dport 80 -i eth0 -j REDIRECT --to-port 8080 iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --dport 80 -j REDIRECT --to-port 8080 For Solaris: For using the Apache port < 1024, run the following command as root user once the installation is complete, and restart the Apache server. usermod -K defaultpriv=basic,net_privaddr <MUR admin user> For example: usermod -K defaultpriv=basic,net_privaddr muradmin Important: This poses a major security concern as it will allow muradmin to use all standard ports < 1024. | 8080
> RPC Port | Type the port number over which XML-RPC server communication will occur with RDP. Important: Be sure no other XML-RPC server is running on configured port. | 9999
> Archive Directory | Type the directory path for archiving parsed files. | <rdp_install_dir>/archive
> The following warning appears if the user performs installation on non-ZFS (UFS) partition path. ZFS is the recommended filesystem for installation. Warning! Path provided lies in ufs filesystem. Recommended filesystem for mur is zfs. Do you still want to continue? [no] ? Type (y)es or (n)o to proceed with the RDP installation. Important: Please note that the ZFS/UFS related warning messages are specific to SOLARIS ONLY and NOT for RHEL. | no
> RDP Configuration Confirmation
> Proceed with installation | Type (y)es to proceed with RDP installation. | yes
> Do you want to start the RDP components | Type (y)es to start the RDP components immediately after installation. | yes

> ‌
> After you have provided the inputs, the installation script starts the MUR components and you receive a message indicating that MUR installation is completed.
> Installing MUR Using GUI/Console based Installer
> Important: To perform the installation procedure explained in this section, you must be logged into the server as a root user.
> Important: Fresh installation for backup recovery purpose should be installed on the same path where last backup is stored and also should have the same IP address and port configuration if the MUR is deployed in distributed mode. Make sure that the existing older installation is either removed or moved to a different directory because the metadata recovered from previously installed MUR will have all references as per older installation e.g. archive path, SFTP details, etc.
> Important: In the MUR Software Releases prior to 11.0.100 build, this installation file is distributed with a .tar.gz extension. In the MUR Software Release 11.0.100 and later, this file is distributed in zip format.
> Follow the instructions below to install MUR using the GUI/Console based installation wizard.

> Step 1 | Change to the directory in which the file is stored.

> Step 2 | Unzip the file by entering the following command:

> unzip mur.x.x.xx_os_arch.zip
> x.x.xx is the version of the MUR installation file.
> os indicates the Operating System on which the MUR application is running. It can be either RHEL or Solaris.
> arch indicates the architecture either Sparc or x86.
> Important: To unzip the .gz package file, use tar -xvf <file_name> command.
> Decompressing the installation file results in the following files:

> • | inst: A GUI/Console based installer to install the MUR application.

> • | setup.bin: The executable used by inst to install MUR application.

> Step 3 | Execute the script by entering the following command:

> ./inst [MODE]
> where [MODE] is optional.
> Two installation modes are supported namely:

> • | gui

> • | console

> The command ‘inst/uninst -help' provides usage of the scripts. This script installs the Apache, Postgres and Scheduling servers functionality. The display must be set for running in GUI mode, else the installation will run in Console mode.
> The following MUR Installer dialog appears displaying the MUR version getting installed.

> Step 4 | Click Next to proceed.

> Step 5 | Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.

> Parameter | Description | Default Value
> PostgreSQL System Settings screen
> | This dialog asks the user to check the variable values in system file. If one or more entries are missing, click Cancel to update the system file and restart the system to re-run installer. For more information, refer to the Setting the Database Environment Strings section. | N/A
> MUR Installation Directory screen
> Enter MUR Directory Path | Enter the base directory path where MUR is to be installed. Click Browse to change the installation path. | <current_directory>
> A Component Type screen appears showing the components for installation. This screen allows you to select either Master MUR or RDP for installation. Important: Make sure that you first install the master MUR and then proceed with the RDP installation.
> MUR Administrator and Group Configuration screen
> Administrator Login | Enter an administrator name for the Operating System (OS) level administrator of MUR. Important: Please note that you should not login as a root user. Important: The Administrator user created should be manually activated with a password once the MUR installation is complete. This can be done by entering the following command as root user: passwd <adminusername> Upon executing this command, the user will be asked to enter a suitable administrator password. | muradmin
> Administrator User ID | Type the Administrator User ID for the MUR Administrator login. Important: This input will be asked only if the Administrator login name provided does not exist. | 100014
> Administrator Primary Group | Type the Primary Group name for the Administrator. Important: If the Administrator login name provided already exists, the Primary Group of this login will be considered as the MUR User Group. Otherwise, the user will be asked to enter the Primary Group information. | murgroup
> PostgreSQL Server Configuration screen
> Postgres Login | This is a read-only parameter. The Postgres login name will be the same as the Administrator login name provided earlier. | muradmin
> Postgres password | Enter the password for the Postgres database administration. | N/A
> Postgres Port | Enter the port number on which PostgreSQL communication will be running. Important: Ensure that no other application/process is running on configured port as well as on next consecutive port (as this port will be used for pgBouncer). | 5432
> Enter data directory path | Enter the data directory path of postgres being used. Click Browse to change the installation path. | <mur_install_dir>/starbi/postgres/data
> MUR Port Configuration screen
> Apache Port | Type the port number over which Apache web server communication will occur with MUR. Important: Ensure that no other Apache web server is running on the port being used for installation. If the port is being used, abort the installation. For RHEL: For RHEL, Apache port provided should be > 1024. RHEL does not allow port 80 to be used by non-root users. However, Apache Web server requests made on port 80 can be redirected to a port >1024 defined by the operator, with the following two commands. For example, to redirect requests made on port 80 to port 8080: iptables -t nat -A PREROUTING -p tcp --dport 80 -i eth0 -j REDIRECT --to-port 8080 iptables -t nat -A OUTPUT -p tcp -d 127.0.0.1 --dport 80 -j REDIRECT --to-port 8080 For Solaris: For using the Apache port < 1024, run the following command as root user once the installation is complete, and restart the Apache server. usermod -K defaultpriv=basic,net_privaddr <MUR admin user> For example: usermod -K defaultpriv=basic,net_privaddr muradmin Important: This poses a major security concern as it will allow muradmin to use all standard ports < 1024. | 8080
> RPC Port | Type the port number over which XML-RPC server communication will occur with MUR. Important: Ensure that no other XML-RPC server is running on the configured port. | 9999
> MUR Archive Directory Configuration screen
> Enter archive directory path | Enter the directory path for archiving parsed files. Click Browse to change the installation path. | <MUR_install_dir>/archive
> Pre-installation Summary screen
> The pre-installation screen displays the product name, install location, other product configurations, and disk space information before installing the product. Click Cancel to stop installation or Install to continue installation.
> Installing MUR screen
> The screen shows all the contents being loaded on the machine during installation. Click Cancel to stop installation.
> MUR Server Startup screen
> Start All Servers After Installation | Select the option to start all servers after installation. Click Next to proceed. | Yes
> Install Complete screen
> | The screen shows whether installation is successful or failed. Click Done to quit the installer. | N/A

> ‌
> Confirming Successful Installation
> Verify that the MUR application is running and accessible by entering the following URL in your Web browser:
> http://<MUR_installation server name or IP address>:<apache port>
> For information on logon details, refer to the Launching the MUR GUI section in the Mobility Unified Reporting System Administration and Management chapter of this guide.
> For information on using the MUR GUI, see the Cisco Mobility Unified Reporting System Online Help documentation.
> Upgrading MUR
> This section provides instructions on how to upgrade the installed MUR application.
> Important: In RHEL-based deployments, L-ESS is NOT required as the ASR 5K Enhanced Charging Services (ECS) module can be configured to push the xDRs directly to the MUR reporting server. Push from ASR 5K is the Cisco recommended deployment model. Currently L-ESS is supported only on Solaris platforms. For information on the L-ESS installation instructions, refer to the Cisco ASR 5000 Series ESS Installation and Administration Guide. Existing deployments where L-ESS is installed, to pull EDRs from ASR 5K, may continue with their deployment model in the 12.0 version of MUR Software Release and later.
> Important: To perform the upgrade procedure explained in this section, you must be logged into the server as a root user.
> The upgrade procedure ensures that the database content is retained in the new installation. It also ensures that if there are any pending files to be processed in the old installation, then those file are also made available in the new installation.
> Important: If MUR is being upgraded from a version in which backup and purging features are not available, to a version in which backup and purging features are supported, then it is recommended that you enable backup feature and take one complete successful snapshot of backup before enabling purging feature. If the backup feature is disabled then enabling purging will cause removal of data without waiting for it to be backed up. If the backup is being taken for the first time after upgrade, then it may take considerable time for first backup.
> Important: Before performing the upgrade process, ensure that the browser cache is cleared.
> Caution: Please contact your local support representative to ensure compatibility prior to upgrading.
> Important: If the previous installation is MUR then the installation script will cause upgrading the software to MUR and if the previously installed component is RDP then the script will cause upgrading to RDP.
> When upgrading to MUR software version 12.2, file parsing configurations are NOT synced automatically at all RDPs. As a result, EDR file parsing does not happen at RDPs.
> To overcome this, peform the following steps in the MUR GUI:

> 1. | After the upgrade, manually attach appropriate RDPs to all relevant gateways.

> • | Create appropriate RDP regions through the System menu.

> • | Attach all RDPs to their respective regions through Edit RDP page viewed by clicking RDP from Admin tab.

> • | Attach appropriate gateways to their corresponding RDPs and regions through Edit Gateway page viewed by clicking GATEWAYS from Admin tab.

> 2. | Navigate to System > File-Parsing Configs menu and then manually save the file parsing configurations for all the gateways which are attached to RDPs.

> The MUR upgrade process is carried out in two steps:

> 1. | Online Upgrade

> 2. | Offline Upgrade

> The online upgrade is the conventional upgrade process. It will upgrade only last 7 days of available data i.e. it will get the latest date for which data is available and upgrade the last 7 days data only from that date.
> Once the online upgrade is complete, offline upgrade starts in the background and it will upgrade all the remaining data older than last 7 days.
> During the offline upgrade, there is a possibility of data outage. So, the reports older than last 7 days might be inaccessible from GUI during this period. Once the offline upgrade is over, these reports will be visible again.
> Please note the following key points:

> • | Once MUR is upgraded and if any schemas support additional counter then you should reconfigure schema for that gateway.

> • | After upgrade is over, the previous data and the schemas displayed earlier for the gateway will be shown on the GUI.

> • | If you want to perform schema configuration for the gateways which were added prior to upgradation, then you should configure the schemas through the GUI by accessing Bulkstat Schema Configuration screen and disable the earlier file format used on the gateway.

> The following steps describe how to upgrade the MUR application:

> Step 1 | Stop the L-ESS by running the following command from the <LESS_install_dir>/ess directory:

> ./serv stop

> Step 2 | Stop the MUR application using the following command from the <MUR_install_dir>/starbi/bin directory:

> ./serv stop
> Important: For all MUR software versions 9.0.16 and later, use the serv stop command.
> or
> ./shutdown.sh
> Important: For all MUR software versions 9.0.15 and lower, use the shutdown command.
> Then, check the status of processes using the following command:
> ./serv status
> Important: For all MUR software versions 9.0.16 and later, use the serv status command.
> or
> ./status.sh
> Important: For all MUR software versions 9.0.15 and lower, use the status command.
> Important: Make sure that none of the processes is running.

> Step 3 | Install the new release of MUR.

> MUR is upgradable from:

> • | Earlier script installer based version to newer script installer based version

> • | Earlier script installer based version to GUI/Console installer based version

> • | Earlier GUI/Console installer based version to subsequent GUI/Console installer based version

> For instructions on different MUR installers, refer to the MUR Installation section.
> In case of the first two upgrade options mentioned above, make sure that you enter the old installation path (<install_dir>) for upgrade when prompted for the 'MUR Installation directory'. In case of the third upgrade option, it automatically detects the old installation path through registry information. The installation automatically detects earlier setup and reads required configuration for Apache, Postgres and RPC port, etc. You will be prompted with a confirmation message before proceeding with the upgrade process.
> After upgrade, the log files are generated at /starbi/logs/ directory.
> Important: The installation script will check if the Administrator user and Primary Group information is already present in database. If it does not exist, it will ask the user to enter this information and then continue with the upgrade.

> Step 4 | After the installation is done, start all the MUR related processes using the following command from the <MUR_install_dir>/star/bin directory:

> ./serv start
> Then, start the L-ESS using the following command from the <LESS_install_dir>/ess directory:
> ./serv start

> Step 5 | Modify the L-ESS configuration or HDD configuration to reflect the changes in the MUR installation path.

> Step 6 | Restart the EDR file generation or HDD file push as needed.

> Important: The RDP should be upgraded manually. If the version of the RDP is not compatible with the MUR, then MUR may ignore the data sent by RDP. Thus, RDP should always be upgraded if it is not in sync with the MUR. For change in mode from RDP to MUR or vice-versa, re-installation is required.
> Uninstalling MUR
> This section provides instructions on how to uninstall the MUR application.
> The MUR application and its components can be uninstalled using one of the following two methods:

> • | Uninstallation Using Script-based Uninstaller

> • | Uninstallation Using GUIConsolebased Uninstaller

> Important: The Administrator user and Primary Group configured during installation / upgrade will not be deleted during uninstallation. These have to be deleted manually by entering the following commands as root user: userdel <ADMINUSER> and groupdel <ADMINGROUP>
> Uninstallation Using Script-based Uninstaller
> Important: Please note that the legacy script-based uninstaller is not supported in the MUR Software Release 11.0.100 and later.
> Important: To perform the uninstallation procedure explained in this section, you must be logged into the server as a root user.
> This method must be used if installation has been done using install_starbi script.
> Execute the script by entering the following command:
> ./uninstall_starbi
> Uninstallation Using GUI/Console-based Uninstaller
> This method must be used if installation has been done using GUI/Console based installer (using inst).
> Important: To perform the uninstallation procedure explained in this section, you must be logged into the server as a root user.

> Step 1 | Change to the <mur_install_dir>/starbi directory and enter the following command:

> ./uninst [MODE]
> where [MODE] is optional.
> Two modes are supported namely:

> • | gui

> • | console

> The display must be set for running in GUI mode, else the uninstallation will run in Console mode.
> The following MUR Uninstaller dialog appears.

> Step 2 | Click Uninstall to proceed.

> This uninstall script stops all the servers if it is running and all the data is wiped off.
> Important: The uninstall script does not cleanup the archive directory.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883