Beruflich Dokumente
Kultur Dokumente
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 M artello
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.
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 MiClouds Premium Software Assurance and Support, purchased on an annual
(Capex/license) or monthly (Opex/subscription) basis.
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.
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:
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
Example
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
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
Small
Medium
Large
June 1, 2015
CPU
2-4 virtual CPUs, each vCPU operating at 1.5 GHz
2-4 virtual CPUs, each vCPU operating at 1.5 GHz
2-4 virtual CPUs, each vCPU operating at 1.5 GHz
RAM
2-6 GB
2-6 GB
2-6 GB
Disk
50 GB
70 GB
90 GB
Page 6 of 11
June 1, 2015
Page 7 of 11
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.
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.
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"
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>
June 1, 2015
Page 8 of 11
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.
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
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
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>
server.war
/etc/marwatch/marwatch-central-
/etc/marwatch/marwatch-dashboard-
/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
June 1, 2015
Page 10 of 11
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
11. Run the following command to verify that tomcat has successfully started:
sudo tail -f /var/log/marwatch/catalina.err
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
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