Sentinel 1.1 Standalone Readme

Last revision: 12/13/2018

Introduction

This readme document contains important information about the Sentinel 1.1 Standalone application. Review this document for general system requirements, known issues, CRs, and Sentinel documentation included in the release.

Note: The detailed Sentinel Installation Guide is available on the Sentinel download page website.

• Before you install Sentinel
• About this Release
• System Requirements
• Sentinel Installation Options
• Product Compatibility
• Known Issues
• Sentinel 1.1 Documentation

< top of document >

Before you install Sentinel

Before you install Sentinel, please review the information in this section.

Enable the .NET 4.7.2 Framework for Windows Server

Sentinel 1.1 requires an initial minimal installation of .NET Framework 4.7.2.   If .Net Framework is not detected, the installer will offer to install .Net Framework 4.7.2

1. Uninstall any Monitored Machine Agents from Sentinel Manager.
1. Refer to the Sentinel 1.0 User Gude for steps to Uninstall (Un-Monitor) current deployed Sentinel Agents

< top of document >

About This Release

Sentinel is an application that monitors and manages the performance and availability of your Wonderware system, including the core software, the engineered software application(s),license server and the related hardware and network infrastructure.

Sentinel detects messages and reports on system performance issues/errors/trends, and monitors key system attributes, and then generates alerts when those attributes exceed defined tolerance ranges.

When an attribute is out of tolerance, the customer support team (internal, systems integrator, and/or Wonderware Technical Support) is notified of the upset condition, and can respond proactively in order to prevent production interruption or downtime. The goal is to ensure that your solutions' performance meets and/or exceeds your expectations.

< top of document >

System Requirements

Sentinel 1.1 is an "on-premises" application, installed on a designated server-level computer. Sentinel must be installed without other System Platform or production software present. The following prerequisite(s) are required for implementing Sentinel System Monitoring:

Sentinel Manager (Production System)

• Microsoft Windows Windows 2008 R2 SP1 or greater
• 1 TB disk space
• 16 GB memory (minimum)
• 64-Bit Operating System
• 8 Cores (minimum production system)
• .NET 4.7.2 (Sentinel Manger and all monitored machines)
• SQL Server - Install on Management Server
• SQL 2014 Express with Tools (minimum - default SQL Server version provided in System Platform Installation)
• IMPORTANT: SQL Sentinel Manager must be installed with SQL Server and Windows Authentication ("Mixed") Mode
• SQL Server Agent Service configured with the following attributes:
• Automatic
• Running - Started
• The Agent Service provides Real Time Web functionality supporting Auto Refresh and Heartbeat services

Monitored Machines

• Determined by core product set installed on machine (use compatibility guide for reference)
• .NET 4.7.2

Hardware Requirements

The following hardware is required to support the Sentinel application.

• Super VGA (1024 � 768) or higher-resolution video adapter and monitor
• CD-ROM or DVD drive for installation or Network connection
• Keyboard
• Mouse or compatible pointing device

< top of document >

Installation requires logged in user installing Sentinel Manager sofware to be an adminitrator on the machine. Preferable to have sysadmin privileges in SQLserver.

Port List

Important: Sentinel uses listed ports by default � make sure no other applications are using the listed ports.

Port list

•   25: SMTP Email Notification (for non-secure SMTP)

• 465: SMTP Email Notification (for secure SMTP)

< top of document >

Sentinel Manager is designed as an "on-Prem" application that is installed on a Server class OS like Windows 2008 R2 SP1, Win Server 2012, or Win Server 2016. Sentinel requires Microsoft SQL Server 2014 Expressi with Tools  (minimum -suppliedwith System Platform, SQLServer 2008 R2 SP2 minimum full SQL Server), which can be installed on the Sentinel Manager node as a prerequisite.

< top of document >

Aveva Sentinel 1.1 Standalone Installation

Sentinel 1.1 Standalone requires an Activated license,  You may install the License Manager and License on the Sentinel Maanagement server or configure the system to point to a remote License Server.

The Aveva Sentinel 1.1 Standalone application Installation

• Launch Setup.exe from Sentinel 1.1 Standalone installation 
• If .Net Framework  4.7.2 is not detected,  and option to install .Net Framework 4.7.2 is displayed.  Click OK to proceed with installing the framework.  Once the framework is installed, the system will display the need to reboot the computer. 
• Once the computer has rebooted, the installation will proceed.
• The installation menu will be displayed
• Sentinel Manager should be installed on a single dedicated computer (it is recommended that no other System Platform applications be installed on this machine).
• Sentinel Agent Installation Manager (SAIM) should be installed on all machines that are to be monitored.

• Select the application(s) to be installed.
• Selecting the Sentinel System Monitor will select :
• Sentinel Manager
• Sentinel Agent Installation Manager
• AVEVA Enterprise Licensing Platform (x86)
• ASB Runtime Components            

• Selecting the Sentinel Agent Installation Manager will select:
• Sentinel Agent Installation Manager
• AVEVA Enterprise Licensing Platform (x86)
• ASB Runtime Components

• Click Next to continue with the installation.
• The Master EULA will be displayed.
• 

• Click the checkbox indicating you have read and you accept the terms of the  license agreements(s).
• THe Agree button will be enabled.
• Click to proceed with the installation.
• The Ready to Install dialog will be displayed.

• Click Install to proceed with installation of the displayed applications.                   

• The selected applications will be installed.  
• Following application installation, Configure the applications by running the Configurator.
• Refer to the Sentinel User Guide for setting configuration details:
• Sentinel Manager Name or IP address
• SMTP Email Notification setup
• Advaned Sentinel Secuirty settings
• HTML
• HTMLS
• Configration finished.
• Sentinel Services are installed and running.
• Refer to the Sentinel User Guide for:
• Launching the Sentinel Manager Console from a browser
• Step by Step instructions to manage system monitoring.
• Once configured, the Sentinel Agent Installation Manager (SAIM) will connect with the Sentinel Manager server.
• Once connected, the Sentinel Manager/SAIM will transfer and install the Sentinel Agent
• The Sentinel Agent service will start and will connect with the Sentinel Manager
• The Sentinel Manifest wil be transfered to the agent machine,  The Manifest contains the Out of Box Rules and  Discovery instructions for the Agent..
• The Sentinel Manager Console Monitored Machine page will display machines that have an installed agent.

s

< top of document >

Aveva Sentinel 1.1 Standalone Documentation

The Aveva Sentinel 1.1 Standalone application includes the following documentation set:

• Aveva Sentinel 1.1 Standalone Readme (html) (this file).
• The Help library consists of an online .html file set that is installed on the Sentinel Management Server and can be accessed from the Sentinel Console User Interface.

These documents are also available from the product installation files and from the Sentinel download page.

< top of document >

< top of document >

Known Issues

The following issues have been identified for resolution in the next release:

•  4317  Alerts Grid:  Ensure column alignment and text wrapping

• 4910   Resolution State sorting is being applied on Created Date

• 4945   Notify user when alerts are ignored (due to too many alerts).  When there is a large ingress of alerts coming from a single machine, the Agent will stop reporting those alerts to prevent excessive resource usage.  When alert ingress has gone back to normal, the Agent begins reporting alerts again.  The user should receive a notification when the Agent has stopped reporting alerts.  The notification does not get sent. 

• 5366   Add SMTP secure configuration to the Silent Install response file

  Workaround:  SMTP will be configured as non-secure during silent install.  If secure SMTP required, update secure SMTP details in the Sentinel Configurator or the Sentinel Manager UI.

• 5480   On original install, the Manifest version listed on the Rules grid should show 1 because the out-of-the-box manifest is immediately published.  Instead the UI shows that the manifest has already been published more than once.

• 5708   Sentinel 1.1 stand alone build should support installation on Win 2008 R2 SP1 operating system and SQLServer 2008 R2 SP2

• 5881   In Simplified chinese, Japanese, French and German operating systems - Discovered Date is incorrect on Monitored Machines screen.

• 5886   In Workgroup environment, can not add local user that exists in OS.  Get error that user does not exist. 

• 5889   In Simplified chinese, Japanese, French and German operating systems -  Sentinel  SQL reports fail to install and are not available in the Sentinel UI.

• 5900   In Simplified chinese, Japanese, French and German operating systems - Refresh button doesn't work on Galaxy Diagram screen.

• It may take up to five minutes for the Galaxy Diagram to reflect Alert changes to the Galaxy shape in Sentinel Manager.  

• 1110669  Following the running of the resource-intensive functions Galaxy Restore, and Galaxy Migrate and Deploy, Sentinel may issue a logger error message: ExceptionType: IndexOutofRangeExceptionMesage was outside bonds of the array. 

• Before running Galaxy Restore, or Galaxy Migration and Deploy, we recommend that you stop the Sentinel Agent on each Galaxy node. To stop the Sentinel Agent(s):

  1.   Log into the Sentinel Manager Console.

  2.   Open the Monitored Machine page

  3.   Select all machines by checking the checkbox(es) to the left.

  4.    Stop the Agent(s) by clicking on the Agent Stop icon at the upper right of the Monitored Machine grid.

  5.    When the Galaxy function is completed, restart the agent(s) by clicking on the Agent Start icon at the upper right of the Monitored Machine grid.