MARWATCH INSTALLATION AND UPGRADE GUIDE

MARWATCH INSTALLATION AND UPGRADE GUIDE For Service Providers RELEASE 5.0

Introduction Notice The information contained in this document is believed to be accurate in all respects but is not warranted by Martello Technologies Corporation. The information is subject to change without notice and should not be construed in any way as a commitment by Martello Technologies or any of its affiliates or subsidiaries. Martello Technologies and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes. No part of this document can be reproduced or transmitted in any form or by any means - electronic or mechanical - for any purpose without written permission from Martello Technologies Corporation. Trademarks MarWatch, Martello Technologies, and the Martello Technologies logo are trademarks of Martello Technologies Corporation. Windows and Microsoft are trademarks of Microsoft Corporation. Other product names mentioned in this document may be trademarks of their respective companies and are hereby acknowledged. Copyright 2015 Martello Technologies Corporation, all rights reserved. June 1, 2015 Page 2 of 11

Introduction Table of Contents Introduction... 4 MarWatch and the Mitel MiCloud Solution... 4 How to Obtain MarWatch... 4 Document Purpose and Intended Audience... 4 Documentation Conventions... 5 Pre-Installation Process... 6 Server Requirements... 6 MarWatch System Installation Procedures... 7 Additional Steps for Service Providers with Self-Signed Certificates... 8 MarWatch System Upgrade Procedures... 10 Probe Upgrade Procedures... 11 June 1, 2015 Page 3 of 11

Introduction Introduction MarWatch and the Mitel MiCloud Solution The MiCloud solution includes a suite of management applications that allow the service provider to offer a highly reliable, easy to manage service. Oria is a customer management solution enabling the delivery of multi-customer hosted communications services. It offers cost savings and effective service delivery by providing the ability to define Service Bundles, an automated provisioning process, easy to use management interfaces, and subscriber self-service. MarWatch offers fault and performance management, as an optional component of the overall Oria Service Provider Management solution suite. MarWatch equips service providers with fast actionable problem resolution so that optimal service quality levels are maintained for end customers. With MarWatch, service providers get 24/7 Performance Monitoring, Real Time Alerts, Detailed Reporting and ubiquitous accessibility with secure remote access. MarWatch consists of a number of web services running on either a cloud-hosted computing platform or on-premises computing platform. MarWatch is part of MiCloud s Premium Software Assurance and Support, purchased on an annual (Capex/license) or monthly (Opex/subscription) basis. How to Obtain MarWatch To obtain the MarWatch, place an order for part number 51303723, MarWatch for Service Provider Base Software. This item is available for purchase at no charge. License keys are then provided to download the software, to install it, and to make it operational in the service provider network environment. Purchases of Premium Software Assurance and Support enable license keys to be provided for each monitored MiCloud product as applicable. Document Purpose and Intended Audience This document is intended for MarWatch deployments where the software is hosted at the service provider or customer location. For MarWatch Software as a Service (SaaS) deployments, where the software is hosted in the cloud, refer to the MarWatch System Guide. This document is intended for service providers who want to install MarWatch on a local computing platform. This document contains instructions for: Installing a new MarWatch system Upgrading an existing MarWatch system to the latest available release For information required to administer and use a MarWatch monitoring system, refer to the MarWatch System Guide. The information in this document is current as of MarWatch Release 5.0 (April 2015). June 1, 2015 Page 4 of 11

Introduction Documentation Conventions Conventions used in this document: Description Links are underlined and colored Elements that require user input (text fields, checkboxes, etc ) are bold Buttons and tabs are in quotes Martello constructs are capitalized Important notes are called out with italics and color Example Click on the New Admin link. The Authorities section designates Click Save, click on the Locations tab Customer, Admin, Probe, Location etc. Note: A Probe June 1, 2015 Page 5 of 11

Pre-Installation Process Pre-Installation Process Service providers are requested to: Supply a URL to be used by end customers to access the MarWatch server so they can monitor their devices; for example, customer.mycompany.com Allocate a static IP address for the new MarWatch server; for example, 10.0.2.10 Configure their DNS server to resolve the URL to the static IP address Martello Technologies provides the service provider with the following: A VMware ESXi OVA that can be installed as Virtual Machine. The Virtual Machine contains an Ubuntu 14.04 Linux installation with the MarWatch server preinstalled. The MarWatch server is preconfigured to use the access URL supplied earlier (customer.mycompany.com). Linux administrator credentials for the Virtual Machine; for example: o Username: mwadmin o Password: <linux_admin_pw> Access credentials for the initial MarWatch administrator account; for example: o Username: setup@customer.mycompany.com o Password: setup Once deployed, the service provider can change the default admin password and then add containers, devices, and users to monitor networks. The initial device that is added is typically a Probe. If the service provider is using self-signed certificates, then additional configuration steps are required to avoid certificate errors between the MarWatch server and the initial Probe. Server Requirements Server requirements for the MarWatch system depend on the number of devices being monitored and whether MCD device backups are done. MCD backups are stored on the MarWatch server. So, if the network contains many MCD devices and backup is enabled, then more virtual disk space is needed for the OVA. The following table describes the virtual hardware requirements based on expected image size. Image Size CPU RAM Disk Small 2-4 virtual CPUs, each vcpu operating at 1.5 GHz 2-6 GB 50 GB Medium 2-4 virtual CPUs, each vcpu operating at 1.5 GHz 2-6 GB 70 GB Large 2-4 virtual CPUs, each vcpu operating at 1.5 GHz 2-6 GB 90 GB June 1, 2015 Page 6 of 11

MarWatch System Installation Procedures MarWatch System Installation Procedures To deploy the Virtual Machine containing the MarWatch system, do the following steps: 1. Download the OVA file. The URL to access the file is provided by Mitel or Martello Technologies. Note: File availability is typically limited to 96 hours. 2. Deploy the OVA file according to VMware instructions. 3. Launch the terminal console of the new VM. 4. Power on the VM. 5. Log into the VM using the Linux administrator credentials (mwadmin and <linux_admin_pw>). 6. Access the scripts subdirectory under the VM home directory. Use the following command: cd scripts 7. Run the following command to prepare the VM for use: sudo./sysprep_host.sh When prompted, enter the following data: System password: Linux admin password (<linux_admin_pw>) Computer name: computer name supplied previously (customer) Domain: domain supplied previously (mycompany.com) IP address static IP address for the VM (10.0.2.10) Note: The script may request that you reboot the system. Ignore this request. Do not reboot the system at this time. 8. Run the following command to configure the VM to have the correct network access: sudo./config_static_ip.sh When prompted, enter the following data: IP address static IP address for the VM (for example, 10.0.2.10) Subnet mask subnet mask (for example, 255.255.255.0) Broadcast network broadcast IP address (for example, 10.0.2.255) Gateway network gateway IP address (for example, 10.0.2.1) DNS Server1 first DNS server IP address (for example, 8.8.8.8) DNS Server2 second DNS server IP address (for example, 8.8.4.4) 9. Restart the VM. June 1, 2015 Page 7 of 11

MarWatch System Installation Procedures 10. Verify connectivity by accessing the MarWatch server. Use the following: o The MarWatch server URL (customer.mycompany.com) o The MarWatch administrator account credentials (setup@customer.mycompany.com and setup) An initial MarWatch dashboard is displayed. For a description of the UI, refer to the MarWatch System Guide. The initial MarWatch administrator account (setup@customer.mycompany.com) only has sufficient privileges to create additional user accounts. Use the setup@customer.mycompany.com account to create your own MarWatch administrator account with full privileges. Refer to the MarWatch System Guide for details. Once your own MarWatch administrator account is available, delete the setup@customer.mycompany.com account. Use your own MarWatch administrator account to add containers, devices and other users to monitor networks from the MarWatch dashboard. Additional Steps for Service Providers with Self-Signed Certificates The MarWatch system requires that you install a Probe. Probes are used by MarWatch to monitor devices. If you are using a self-signed certificate, then you must do the steps described in Certificate Preparation for a Linux Probe on page 8 or Certificate Preparation for a Windows Probe on page 9 before installing the first Probe. After preparing the certificate, follow the appropriate Probe installation procedure described in the MarWatch System Guide. If you are using a CA certificate, it can be used by the MarWatch system once it is signed. Contact support@martellotech.com for assistance. Certificate Preparation for a Linux Probe The following steps apply when installing on an MSL blade platform. Some variations may be required if you are installing the Probe on a different Linux platform. The Root Certificate file must be added to Java JRE cacerts file. To do so, do the following steps: 1. Download and extract Root Certificate file to the Linux system where the Probe will be installed. 2. Run the following command to find the location of the Java JRE cacerts file: sudo find / -name "cacerts" The following is a typical result: /usr/lib/jvm/java-6-sun-1.6.0.45/jre/lib/security/cacerts 3. Run the following command to add the Root Certificate file to the Java JRE cacerts file: sudo keytool -import -keystore <path to java jre cacerts file> -alias martelloca -file <path to the extracted Root Cert file> The following is an example: sudo keytool -import -keystore /usr/lib/jvm/java-6-sun- 1.6.0.45/jre/lib/security/cacerts -alias martelloca -file /home/voipadmin/martellorootcert.crt June 1, 2015 Page 8 of 11

MarWatch System Installation Procedures 4. When prompted, supply the password for the Java JRE cacerts file. The default password is changeit. Do not change the password for the Java JRE cacerts file. 5. Follow the appropriate Probe installation procedure described in the MarWatch System Guide. Certificate Preparation for a Windows Probe The Root Certificate file must be added to Java JRE cacerts file. To do so, do the following steps: 1. Download and extract Root Certificate file to the Windows system where the Probe will be installed. 2. Find the location of the Java JRE cacerts file. Typically, it is located in the Java JRE installation directory. The following is an example: C:\Program Files\Java\jre6\lib\security\cacerts 3. Open a Command Prompt window as a Windows administrator: a. Navigate to Start > All Programs > Accessories b. Right-click on Command Prompt. c. Select Run as Administrator. 4. Run the following command in the Command Prompt window to add the Root Certificate file to the Java JRE cacerts file: keytool -importcert -keystore "<path to java jre cacerts file>" -alias martelloca -file "<path to the extracted Root Cert file>" The following is an example: keytool -importcert -keystore "C:\Program Files\Java\jre6\lib\security\cacerts" -alias martelloca -file "C:\Users\rsally\Documents\martelloRootCert.crt" 5. When prompted, supply the password for the Java JRE cacerts file. The default password is changeit. Do not change the password for the Java JRE cacerts file. 6. Follow the appropriate Probe installation procedure described in the MarWatch System Guide. Note: When using the Windows keytool command, you must use quotes to specify file paths. June 1, 2015 Page 9 of 11

MarWatch System Upgrade Procedures MarWatch System Upgrade Procedures This section explains how to upgrade an on-premise MarWatch R5.x instance to the latest available release. To upgrade the MarWatch system, do the following steps: 1. Download the MarWatch R5.x release files. The URL to access the files is provided by Mitel or Martello Technologies. MarWatch R5.x consists of the following files: authorization.war central.war dashboard.war rrd.war probe.jar Note: File availability is typically limited to 96 hours. 2. Upload the.war and.jar files to the appropriate MarWatch server using your preferred software (for example, scp or WinSCP). 3. Run the following command to stop ngnix: sudo /etc/init.d/ngnix stop 4. Run the following command to stop tomcat: sudo /etc/init.d/tomcat stop 5. Copy the.war files to the appropriate location by running the following commands. Ensure you are on the right MarWatch server for each file before copying: sudo cp <downloaded authorization.war file> /etc/marwatch/marwatchauthorization-server.war sudo cp <downloaded central.war file> /etc/marwatch/marwatch-centralserver.war sudo cp <downloaded dashboard.war file> /etc/marwatch/marwatch-dashboardserver.war sudo cp <downloaded rrd.war file> /etc/marwatch/marwatch-rrd-server.war 6. Copy the.jar file to the appropriate location by running the following command. Ensure you are on the right MarWatch server for each file before copying: sudo cp <downloaded Jar file> /etc/marwatch/probesoftware/marwatch-probecore.jar 7. Change directory with the following command: cd /home/tomcat/tomcat8/webapps/ June 1, 2015 Page 10 of 11

MarWatch System Upgrade Procedures 8. Run the following command to delete old uncompressed.war files from the server: sudo rm -R authorization central dashboard rrd If your RRD server is separate, run the following command on the RRD server: sudo rm -R rrd 9. Return to your home directory with the following command: cd ~ 10. Run the following command to start tomcat: sudo /etc/init.d/tomcat start 11. Run the following command to verify that tomcat has successfully started: sudo tail -f /var/log/marwatch/catalina.err The following string indicates success startup: INFO: Server startup in <number>ms 12. Run the following command to start ngnix: sudo /etc/init.d/ngnix start 13. Access the directory where the.war and.jar files were originally uploaded to the MarWatch server in Step 2. These files are no longer needed because they were copied to their final destination in Step 5 and Step 6. 14. Run the following command to delete unneeded.war and.jar files from the MarWatch server: sudo rm *.war *.jar Probe Upgrade Procedures Probes are automatically upgraded once the MarWatch system is upgraded. Updated files are downloaded to Probe instances as required. No intervention is required to upgrade Probes. June 1, 2015 Page 11 of 11