VisionHub Monitoring Guide - Qognify · NMS Network Monitoring System (NMS) is the monitoring service which monitors VisionHub components via SNMP. The SNMP trap events are logged

VisionHub Monitoring Guide

Version 4.2

January 2017

Rev. A3

Copyright © 2016 Qognify Ltd. All rights reserved.

Important Notice Qognify shall bear no responsibility or liability to a client or to any person or entity with respect to liability, loss or damage caused or alleged to be caused directly or indirectly by any Qognify product. This includes, but is not limited to, any interruption of service, loss of business or anticipatory profits or consequential damage resulting from the use or operation of any Qognify products. Information in this document is subject to change without notice and does not represent a commitment on the part of Qognify. The systems described in this document are furnished under a license agreement or non-disclosure agreement.

All information included in this document, such as text, graphics, photos, logos and images, is the exclusive property of Qognify and protected by United States and international copyright laws. Permission is granted to view and photocopy (or print) materials from this document for personal, non-commercial use only. Any other copying, distribution, retransmission or modification of the information in this document, whether in electronic or hard copy form, without the express prior written permission of Qognify, is strictly prohibited. In the event of any permitted copying, redistribution or publication of copyrighted material, no changes in, or deletion of, author attribution, trademark legend or copyright notice shall be made.

Qognify Disclaimer: For the full list of Qognify’s trademarks, visit www.Qognify.com/trademarks. All other marks used are the property of their respective proprietors.

All contents of this document are: Copyright © 2016 Qognify. All rights reserved.

Contents

1 About This Guide .................................................................................................... 1

1.1 Who Should Read This Guide ................................................................... 1

1.2 Terms and Abbreviations ......................................................................... 1

1.3 Related Documentation ............................................................................. 1

1.4 Guide Conventions .................................................................................... 2

1.5 Monitoring System Requirements ............................................................. 3

1.6 Technical Support...................................................................................... 3

2 Overview .................................................................................................................. 4

2.1 Key SNMP Concepts ................................................................................. 5

2.2 Prerequisites .............................................................................................. 6

2.2.1 PRTG Licensing 7

2.2.2 Installation of the PRTG Monitoring Server 7

2.2.3 Installation and Configuration of SNMP Agents 8

2.2.4 Installing the SNMP Services on the SVR 8

2.2.5 Configuring the PRTG IP Address 16

3 Configuring PRTG ................................................................................................ 18

3.1 Logging in to PRTG ................................................................................. 18

3.2 Deleting Default Discovered Devices ...................................................... 18

3.3 Adding a Group ....................................................................................... 18

3.4 Adding a Device ...................................................................................... 19

3.5 Editing the Device Windows Credentials................................................. 23

3.6 Adding an Auto-Discovery Group ............................................................ 23

3.7 Adding a Traps Sensor ............................................................................ 25

3.8 Configuring Retention .............................................................................. 28

3.9 Defining Thresholds for Severity Counters ............................................. 29

4 Monitoring VisionHub Using PRTG .................................................................... 31

4.1 Viewing the Home Page and Dashboards .............................................. 31

4.2 Viewing the Map ...................................................................................... 34

4.3 Viewing the Devices ................................................................................ 35

4.4 Viewing the Sensors ................................................................................ 36

4.5 Viewing the Device Sensors with Alarms ................................................ 38

4.6 Using the Enterprise Console .................................................................. 39

4.7 Viewing the Sensor Trap Receiver Messages ........................................ 40

4.8 Using Ticketing ........................................................................................ 42

5 For Advanced Users Only .................................................................................... 44

5.1 Importing the VisionHub MIB Files .......................................................... 44

5.2 Creating a Device Template .................................................................... 49

5.3 Adding SNMP Sensors ............................................................................ 50

5.4 Managing Users ...................................................................................... 52

6 Troubleshooting ................................................................................................... 55

7 SNMP Reference ................................................................................................... 57

7.1 SNMP MIBs ............................................................................................... 1

7.2 Operational Application Server MIB .......................................................... 2

7.3 Video Application Server MIB .................................................................... 4

7.4 SVR MIB .................................................................................................... 9

7.5 SVR Traps/Events ................................................................................... 13

7.6 Video Application Server Traps/Events ................................................... 23

7.7 Operational Application Server Traps/Events ......................................... 32

List of Tables

Table 1-1: Acronyms and Abbreviations ............................................................................. 1 Table 1-2: Related Documents ........................................................................................... 1 Table 1-3: Typography Conventions ................................................................................... 2 Table 3-1: Device Templates .............................................................................................. 7 Table 7-1: Qognigy MIBs .................................................................................................... 1 Table 7-2: Operational Application Server MIB Tree .......................................................... 3 Table 7-3: Video Application Server MIB Tree.................................................................... 5 Table 7-4: SVR MIB Tree .................................................................................................. 10 Table 7-5: SVR Traps/Events ........................................................................................... 13 Table 7-6: Video Application Server Traps/Events ........................................................... 23 Table 7-7: Operational Application Server Traps .............................................................. 32 Table 7-8: Operational Application Server Component Loss ............................................ 36

List of Figures

Figure 2-1: Monitoring Flow ................................................................................................ 4 Figure 2-2: Counters ........................................................................................................... 6 Figure 2-3: Monitored Services ........................................................................................... 8 Figure 2-4: NMSDataCollectionSetup Installation Wizard .................................................. 9 Figure 2-5: NMS NuDesign Installation ............................................................................... 9 Figure 2-6: NMS NuDesign Installation Folder ................................................................. 10 Figure 2-7: NMS NuDesign Configuration ........................................................................ 10 Figure 2-8: NMS NuDesign Installation ............................................................................. 11 Figure 2-9: NMS NuDesign Installation ............................................................................. 12 Figure 2-10: NMSDataCollectorSetup Installation ............................................................ 13 Figure 2-11: NMSDataCollectorSetup License Agreement .............................................. 13 Figure 2-12: NMSDataCollectorSetup Installation Folder ................................................. 14 Figure 2-13: NMSDataCollectorSetup Ready to Install .................................................... 15 Figure 2-14: NMSDataCollectorSetup Installation ............................................................ 15 Figure 2-15: NuDesign SNMPv3 Agent Service Configuration Editor .............................. 17 Figure 3-1: Paessler MIB Importer Setup Wizard ............................................................. 45 Figure 3-2: License Agreement ......................................................................................... 45 Figure 3-3: Destination Location ....................................................................................... 46 Figure 3-4: Additional Tasks ............................................................................................. 46 Figure 3-5: Complete the Setup ........................................................................................ 47 Figure 3-6: Paessler MIB Importer Window ...................................................................... 48 Figure 3-7: Import Log ....................................................................................................... 49 Figure 3-8: Add Device – Choose Parent ......................................................................... 20 Figure 3-9: Add Device – Device Details .......................................................................... 21 Figure 3-10: Qognify Devices............................................................................................ 22 Figure 3-11: Credentials for Windows Systems ................................................................ 23 Figure 3-12: Credentials for Windows Systems ................................................................ 23 Figure 3-13: Create Device Template ............................................................................... 50 Figure 3-14: PRTG Group Details ..................................................................................... 24 Figure 3-15: Group Details – Automatic Sensor Creation ................................................ 25 Figure 3-16: Add Sensor ................................................................................................... 50 Figure 3-17: Add Sensor to Device – Step 1 .................................................................... 51 Figure 3-18: Select Library File ......................................................................................... 51 Figure 3-19: Add Sensor to Device – Step 2 .................................................................... 52 Figure 3-20: Sensor Selection .......................................................................................... 26

Figure 3-21: Add Sensor to Device – Step 1 .................................................................... 26 Figure 3-22: Add Sensor to Device – Step 2 .................................................................... 27 Figure 3-23: Device Details – Overview Tab .................................................................... 28 Figure 3-24: Setup Tab ..................................................................................................... 28 Figure 3-25: Setup Tab > Core & Probes ......................................................................... 29 Figure 3-26: Counter Threshold Configuration ................................................................. 29 Figure 3-27: Error Count Critical Severity Counter ........................................................... 30 Figure 3-28: Error Count Warning Severity Counter ......................................................... 30 Figure 4-1: Welcome Page ............................................................................................... 31 Figure 4-2: Dashboard 1 ................................................................................................... 32 Figure 4-3: Dashboard 2 ................................................................................................... 33 Figure 4-4: Dashboard 3 ................................................................................................... 33 Figure 4-5: Maps ............................................................................................................... 34 Figure 4-6: Map Dashboard .............................................................................................. 34 Figure 4-7: Devices ........................................................................................................... 35 Figure 4-8: Sensors ........................................................................................................... 37 Figure 4-9: Sensors With Status Down ............................................................................. 37 Figure 4-10: Sensor Details .............................................................................................. 38 Figure 4-11: All Alarms ...................................................................................................... 38 Figure 4-12: Warning Alarms ............................................................................................ 39 Figure 4-13: Alarm ............................................................................................................ 39 Figure 4-14: Alarm ............................................................................................................ 39 Figure 4-15: Devices ......................................................................................................... 41 Figure 4-16: SNMP Trap Receiver .................................................................................... 41 Figure 4-17: SNMP Trap Receiver - Messages ................................................................ 42 Figure 4-18: PRTG Tickets ............................................................................................... 43 Figure 4-19: PRTG Ticket ................................................................................................. 43 Figure 5-1: System Administration .................................................................................... 53 Figure 5-2: User Accounts ................................................................................................ 53 Figure 5-3: New User Group ............................................................................................. 54 Figure 5-4: New User ........................................................................................................ 54 Figure 6-1: PRTG Account Page ...................................................................................... 55 Figure 6-2: PRTG Account Login Page ............................................................................ 56 Figure 6-3: PRTG Time Zone Settings Page .................................................................... 56 Figure 7-1: Qognify MIBs .................................................................................................... 1 Figure 7-2: Operational Application Server MIB ................................................................. 2 Figure 7-3: Video Application Server MIB ........................................................................... 4 Figure 7-4: SVR MIB ........................................................................................................... 9

VisionHub Monitoring Guide About This Guide

Page 1 of 57

1 About This Guide

This document describes how to monitor VisionHub using Paessler's PTRG. It also includes a full reference to the Qognify MIB and traps/events.

1.1 Who Should Read This Guide

The information and procedures described in this document are for use by VisionHub Administrators and Users.

1.2 Terms and Abbreviations

The acronyms and abbreviations used in the VisionHub documents are listed below.

Table 1-1: Acronyms and Abbreviations

Term Description

MIB The Management Information Base is a text file that defines the interface between the agents and the NMS.

NMS Network Monitoring System (NMS) is the monitoring service which monitors VisionHub components via SNMP. The SNMP trap events are logged in its database and enables ticketing and notification policies.

OPAS Operational Application Server.

PRTG Qognify is able to integrate with PRTG, Paessler's network monitoring software.

SNMP Simple Network Management Protocol. A network protocol used for managing and reporting device status and events

SVR Smart Video Recorder

VDAS Video Application Server

1.3 Related Documentation

Related documents are listed below.

Table 1-2: Related Documents

Document Name Version File Type

Date

VisionHub Installation Guide 4.1 PDF June 2016

VisionHub System Requirements 4.1 PDF June 2016

VisionHub Administrator User Guide 4.1 PDF June 2016

VisionHub Video Configurator User Guide 4.1 PDF June 2016

VisionHub Control Web Application User Guide 4.1 PDF June 2016

VisionHub Planner User Guide 4.1 PDF June 2016

VisionHub Standalone Player User Guide 4.1 PDF June 2016

VisionHub SVR Turnkey Installation Guide 4.1 PDF June 2016

VisionHub SVR Software Kit Installation Guide 4.1 PDF June 2016

VisionHub NVD Software Kit Installation Guide 4.1 PDF June 2016


Page 2 of 57

Document Name Version File Type

Date

VisionHub NVD5204 Turnkey Installation Guide 4.1 PDF June 2016

VisionHub Video Theory of Operation 4.1 PDF June 2016

VisionHub Security Guidelines 4.1 PDF June 2016

VisionHub Network Planning Guidelines 4.1 PDF June 2016

1.4 Guide Conventions

The typography conventions used in this guide are described below.

Table 1-3: Typography Conventions

Style Usage Example

Initial Capitals

+ Bold

Menus, dialog box options, field names and commands

To access the application, click Start > Programs > Accessories > Paint.

Italics File names, folder names, and file paths

Type the IP address in the Address field.

Run the setup.exe file located at: C:\Installation\Setup.

Monospace (Courier New

font) Code samples, error messages The following error message is

displayed:

Error opening database:

database is currently

in use.

UPPERCASE Code keywords and database elements

Use the INNER JOIN clause in SQL Server to join one table to another.

<Ctrl-x> Indicates a key that is pressed or a control character sequence

Press <Enter> means press the Enter key. Or, press <Ctrl-x> means press the Control key and the x key simultaneously.

This guide also contains text with special formatting to provide reference information, cautions, and warnings for the user.

NOTE: A NOTE calls attention to additional information or references related to an operation, procedure, practice, and so on.

TIP: A TIP calls attention to topics or tutorials related to an operation, procedure, practice, and so on.

CAUTION: A CAUTION denotes a hazard. It calls attention to an operation, procedure, practice, and so on, which, if not correctly performed or adhered to, could result in damage to or destruction of part or all of the system components. Do not perform any procedure denoted by a CAUTION sign until the indicated conditions are fully understood and met.


Page 3 of 57

IMPORTANT: An IMPORTANT calls attention to information the user needs to be aware about.

1.5 Monitoring System Requirements

The hardware and software equipment requirements for monitoring are described in the VisionHub System Requirements document. All hardware and integrated third party systems must be fully assembled and in place.

1.6 Technical Support

This document contains all the information necessary for correct operation of PRTG. If the information you need is not in this document, refer to the related documents or contact your technical support representative.

Qognify provides the highest level of technical support for its products. Technical support services include:

Training Services: Qognify provides both in-house and on-site training courses for system operators, technical, and system administrators.

Documentation Resources: VisionHub is supplied with comprehensive technical documentation. In addition, Qognify provides customers with periodic release notes and technical notes.

Follow-on Support: Qognify provides customers with a valuable and comprehensive maintenance and services offering. Different available options can be reviewed in the VisionHub Price List.

For more information about documentation, training, and support services, contact your local Qognify representative.

VisionHub Monitoring Guide Overview

Page 4 of 57

2 Overview

The VisionHub system may be monitored by the Paessler PRTG NMS tool. Each VisionHub component presents the SNMP MIB to the NMS server. The NMS server polls the SNMP MIB for the status and gets SNMP trap events.

There are MIBs for the following VisionHub components:

Operational Application Server

Video Application Server

SVR

The SVR connects to the server hardware management and gets the status on all the server and storage appliances. The SVR generates SNMP traps following errors or warnings on its server/storage hardware.

Figure 2-1: Monitoring Flow

The Monitoring service (on the Operational Application Server) represents the VisionHub middle tier. It monitors all the installed services that are included in the SQL DB under monitored services and reports errors to the NMS.

The Video Application Server handles traps from the database, SVR, ICM, CSS, dual recording, Video Application Server, Decoder and various external servers.

The SVR too has its own MIB for monitoring the SVR.

The NMS Web client connects to the NMS server and gets the site structure by device (VisionHub components: SVR, Video Application Server, Operational Application Server, and so on) and sensors (SNMP MIB, SNMP traps, optional performance counters, and so on). The NMS users are administrated separately within the NMS tool.

NOTE: You may integrate Qognify with a different SNMP monitoring system, if required.


Page 5 of 57

2.1 Key SNMP Concepts VisionHub supports both SNMP MIBs and traps per system component.

The MIBs include server properties along with severity counters (critical and warning). These counters count the number of open issues. Each issue that is closed reduces the count, until it is zero. When the counter is greater than zero, it is recommended to check the traps list for further investigation. The traps support an on/off state, depending on the trap, as well as a one-off message for warning traps.

Qognify provides the following MIB files:

Operational Application Server

Video Application Server

SVR

These files define which properties of the managed object within the device will be monitored.

To see more details on the MIBs, including the Object Identifiers (OIDs), SERVER-OBJECTS (or sensors) and the SERVER-NOTIFICATIONS, see SNMP Reference.

The VisionHub servers are added as devices in PRTG. Sensors are then added to the devices to allow for monitoring.

Each of the VisionHub servers (SVR, Video Application Server, Operational Application Server) has several types of sensors:

VisionHub SNMP server objects, for example, server name, server IP, server ID, server version, and error counts for warning and critical severity events.

VisionHub SNMP traps.

NOTE: There is an option to add additional sensors besides SNMP to the device, such as WMI and performance counters.

For example, the VH SVR server below has the SNMP Trap Receiver sensor, several optional performance counters (CPU Load, Pool Usage Percent, etc.) and several VisionHub server-object sensors (vh error count critical severity, vh error count warn severity, vh recorder name, etc.).


Page 6 of 57

Figure 2-2: Counters

Additional monitoring is also available for the IIS Web Server (the Web Application Pool) and SQL Database.

Qognify provides out-of-the-box device templates with the recommended sensors pre-defined. These device templates can then be used to easily set up your devices and sensors. For more details, see Configuring PRTG.

2.2 Prerequisites

The following prerequisites are required for using PRTG to monitor VisionHub

Open ports 161 and 162 for SNMP

Licensing

Installation of PRTG - Paessler's network monitoring software

Installation of SNMP agent on SVR, Video Application Server and Operations Application Server

Verifying which services on Operations Application Server to monitor (in Administrator)

Ensuring that the services are up:

NuDesign SNMPv3 Agent Service

Qognify NMS Data Collector and API (on SVR)

NOTE: SNMP uses UDP (which is prone to packet loss) for communication. Using SNMP over WAN might cause the loss of important data.


Page 7 of 57

2.2.1 PRTG Licensing

Requires a license from the Paessler web site: https://www.paessler.com/prtg/price_list

Up to 100 sensors are free.

Minimum sensors requirements are as follows:

SNMP traps

SNMP MIB severity counters (WARNING and CRITICAL)

SNMP MIB configuration – notify on configuration change in VisionHub

Additional (WMI, Performance Counters, and so on)

Minimum licenses required for VisionHub are based on a traps sensor and two severity MIB counter sensors per server:

Three for the Operations Application Server.

Three for the Video Application Server.

Three sensors per SVR.

2.2.2 Installation of the PRTG Monitoring Server

There are two steps of PRTG installation:

The PRTG software installation: the PRTG Monitoring Server should be installed by customers. It is not supplied by Qognify.

Once installed, two icons are added on the Desktop to launch the PRTG application:

PRTG Enterprise Console

PRTG Network Monitoring

Two services are added to the local services list:

PRTG Core Server Service

PRTG Probe Service

PRTG Add-Ons installation via VisionHub installation setup program.

VisionHub installation setup program installs the PRTG Add-Ons and silently configures the default port to 8088. The Qognify PRTG Add-Ons provide out-of-the-box device templates. These device templates can then be used to easily set up the recommended sensors for your devices.

Table 2-1: Device Templates

Device Template Product

VisionHub OPAS.odt VisionHub Operational Application Server

VisionHub VDAS.odt VisionHub Video Application Server

VisionHub SVR.odt VisionHub SVR

VisionHub SQL DB.odt VisionHub DB

VisionHub web.odt VisionHub Web (optional): Web API and VisionHub Application

Refer to the VisionHub Installation Guide for more details. The installation checks if PRTG software is already installed and then installs the PRTG Add-Ons. If PRTG software is not installed, the Add-Ons cannot be installed either.

https://www.paessler.com/prtg/price_list


Page 8 of 57

2.2.3 Installation and Configuration of SNMP Agents

The NuDesign SNMPv3 Agent service must be installed on the various VisionHub servers.

To install and configure SNMP agents:

Install SNMP agent on the:

SVR (see Installing the SNMP Services on the SVR)

Video Application Server (installed as part of the server installation). Refer to the VisionHub Installation Guide for more details.

Operations Application Server (installed as part of the server installation). Refer to the VisionHub Installation Guide for more details.

In Administrator, verify which services are monitored on the Operations Application Server (see the Administrator User Guide).

Figure 2-3: Monitored Services

Ensure that the following services are up and running on the servers:

NuDesign SNMPv3 Agent Service

Qognify NMS Data Collector and API (on SVR only)

2.2.4 Installing the SNMP Services on the SVR

You must install the Qognify NMS Data Collector and API service on the SVR. This installation wizard also installs the NuDesign SNMPv3 Agent Service on the SVR, if required.

To install the NMS services on the SVR:

On the SVR, double-click NMS_SVR_SNMPService.exe.


Page 9 of 57

Figure 2-4: NMSDataCollectionSetup Installation Wizard

Click Install.

Figure 2-5: NMS NuDesign Installation

Click Next.


Page 10 of 57

Figure 2-6: NMS NuDesign Installation Folder

Select an installation location, and then click Next.

Figure 2-7: NMS NuDesign Configuration


Page 11 of 57

Complete the required Community and Notify (the NMS server where to send the traps to) details and then click OK.

TIP: It is possible to work with hostname instead of IP address. Port number should be separated from IP/hostname by a colon. (For example, 192.168.123:162 or example.domain.name:162).


Click Install.


Page 12 of 57


Click Finish.


Page 13 of 57

Figure 2-10: NMSDataCollectorSetup Installation

Click Next.

Click Next.

Figure 2-11: NMSDataCollectorSetup License Agreement

Select I accept the terms in the license agreement.


Page 14 of 57

Click Next.

Figure 2-12: NMSDataCollectorSetup Installation Folder

Make sure that the NMS Data Collector is installed in the SVR installation folder (<driver letter:>\Program Files(x86)\SecuritySystem\Recorder\NMS). Otherwise, monitoring will not work properly. To change the default location, click Change, select the Recorder installation folder, and click Next.


Page 15 of 57

Figure 2-13: NMSDataCollectorSetup Ready to Install

Click Install.

Figure 2-14: NMSDataCollectorSetup Installation


Page 16 of 57

Click Finish.

2.2.5 Configuring the PRTG IP Address

In case you changed the PRTG IP address, make sure to update it in the NuDesign SNMPv3 Agent Service using the Configuration Editor. Perform this procedure on each recorder where NuDesign SNMPv3 Agent Service is installed.

However, if working with hostname and not IP, and the hostname has not changed, then this procedure is not required.

To configure the PRTG IP address:

On the SVR, navigate to the NuDesign Tools\NDT SNMPv3 Agent Service x86 directory, which is usually in the default installation folder in C:\Programs.

Different Operating Systems (32-Bit or 64-Bit) install different NuDesign versions; therefore, it may also be found in the C:\Program Files (x86) folder.

Double-click NDAgCplCfg.exe.

The NuDesign SNMPv3 Agent Service stops automatically when opening the Configuration Editor. NuDesign provides a confirmation message.

The Configuration Editor opens.

Select SNMP > Notify.

In the Target Addresses Table see the current IP address and network port.


Page 17 of 57

Figure 2-15: NuDesign SNMPv3 Agent Service Configuration Editor

Click Addr... next to the Address field.

Enter the new <IP address:port>.

IMPORTANT: Use port 162 only.

Do NOT change the default configuration of TagList, Community, Version.

Click Apply.

Click Save.

A new IP address is added to the Target Addresses Table.

TIP: Generally, it is possible to add multiple target addresses, although in this case the machine performance may degrade. To add several addresses in order to send traps from NMS to many PRTG servers, repeat steps 4 to 7 as many times as needed.

In the Target Addresses Table, select the old IP address and click Delete to delete it.

Click Quit.

The service starts up.

VisionHub Monitoring Guide Configuring PRTG

Page 18 of 57

3 Configuring PRTG

3.1 Logging in to PRTG

To login to PRTG web application, in the browser address field, type the address of the server where the PRTG is installed, for example http://<IP>:8088/welcome. Note that it is mandatory to add port 8088 to the address. Use colon between IP address and port numer. In the Login screen, click on the Default Login button.

The welcome page is your default homepage and is shown when you log in and whenever you click Home.

Figure 3-1: Welcome Page

3.2 Deleting Default Discovered Devices

Once you install PRTG and login for the first time, it automatically discovers all devices on the network. Delete them and create the necessary groups for necessary devices only.

To delete automatically discovered devices:

TBD

3.3 Adding a Group

Typically, you would add a Qognify or VisionHub group to PRTG. Once the group is added, you will add devices and their sensors.

Alternatively, you can create an auto-discovery group for a range of IP addresses. See Adding an Auto-Discovery Group.


Page 19 of 57

To add a group:

Log in to PTRG.

Select Devices > Add Group.

Select a probe or group where you want to add the group.

Click Continue.

Enter a name for the group, for example, Qognify.

Click Continue.

3.4 Adding a Device

You must add a separate device for each SVR, Operational Application Server (OPAS), and Video Application Server (VDAS), SQL, and Web Server. This helps to organize the notifications in a more convinient way. There will be a tree of a parent group with several devices under it.

To add a device:

Log in to PTRG.

Select Devices > Add Device.


Page 20 of 57

Figure 3-2: Add Device – Choose Parent

Select the required group, for example, Qognify.

Click Continue.


Page 21 of 57

Figure 3-3: Add Device – Device Details

Enter a name for the device.

Enter the device IP Address or DNS name.

Select an icon to represent the device.

Select Automatic sensor creation using specific device template(s).


Page 22 of 57

Select the required VisionHub template, for example, VisionHub OPAS.

For turnkey platforms, select Server (Dell) template in addition to the relevant VisionHub template.

Click Continue. The device is added at the bottom of selected group’s devices list.

Wait until Auto Discovery finishes. There is a progress status in percentages next to the device name. It finished once the icon of the progress disappears and all sensors appear in a tree. If something went wrong, sensors will not appear in a tree.

Figure 3-4: Qognify Devices

Add the SNMP Trap Receiver sensor manually for SVR, OPAS, and VDAS, as this is not provided in templates. Refer to Adding a Traps Sensor topic for details.


Page 23 of 57

3.5 Editing the Device Windows Credentials

By default, when you add a device, it inherent its credentials according to the tree structure.

For VisionHub Web Server and SQL Server (that use the WMI templates) the Windows credentials must be changed.

To edit the device Windows credentials:

Right click on a device in the device tree, and select Edit > Settings.

Scroll down to the Credentials for Windows Systems section.

Figure 3-5: Credentials for Windows Systems

Deselect Inherit from ….

Enter the Windows credentials.

Figure 3-6: Credentials for Windows Systems

Click Save.

3.6 Adding an Auto-Discovery Group

You can create an auto-discovery group for a range of IP addresses. PRTG scans the specified network segment for devices, assesses the device type for all devices discovered. If selected, PRTG creates sensor sets that match the discovered device types (based on device templates with recommended sensors for the device type).

NOTE: Auto-discovery will find all devices on a subnet unless you specify a specific IP address.

For more information, refer to the PRTG Manual online.

To add an auto-discovery group:

Log in to PTRG.

Select Devices > Add Auto-Discovery Group or right-click in the tree and select Add Auto-Discovery Group.


Page 24 of 57

Figure 3-7: PRTG Group Details

Enter a Group Name.

Select Automatic sensor creation using specific device templates.


Page 25 of 57

Figure 3-8: Group Details – Automatic Sensor Creation

Select all VisionHub templates, and if using a turnkey platform also select Server (Dell) template.

Enter the IPv4 Base.

Enter an IPv4 Range Start and IPv4 Range End.

Click Continue. The auto-discovery group is created and auto-discovery starts. The devices are discovered and added with the recommended sensors.

You can rename devices for more convinient use by right-clicking on a device and selecting Edit > Rename.

3.7 Adding a Traps Sensor

Once you have added a device, you can add the SNMP traps for monitoring.

For a list of available traps per device type, see:


Page 26 of 57

SVR Traps/Events

Video Application Server Traps/Events

Operational Application Server Traps/Events

To add a traps sensor:

For the selected device, click Add Sensor.

Figure 3-9: Sensor Selection

In the Search field enter trap.

Figure 3-10: Add Sensor to Device – Step 1

Select SNMP Trap Receiver and click Add This.


Page 27 of 57


Enter the sensor name.

Ensure that the Listen on Port is 162.

From the Purge Messages After drop-down list, select the number of hours or days after which to purge the traps. Typically, this is set to 5 days.

Click Continue.

NOTE: As a trap sensor is added per device, it already filters only messages related to the device. you will get messages from both Dell and , For a turnkey server

VisionHub .


Page 28 of 57

Figure 3-12: Device Details – Overview Tab

3.8 Configuring Retention

Limit the historic data purging for retention purposes. This affects the disk space of the PRTG server and because the default value is too high, we need to limit it especially if the PRTG server is installed as part of the VisionHub All in One middle tier.

To configure retention:

Click Setup.

Figure 3-13: Setup Tab

On the Setup tree, select Core & Probes.


Page 29 of 57

Figure 3-14: Setup Tab > Core & Probes

Scroll down to the HISTORIC DATA PURGING section.

Configure the data purging as required, then click Save.

3.9 Defining Thresholds for Severity Counters

You can define condition thresholds for severity counters.

For example, if a critical counter > 0, the sensor state is “down”, it appears in red.

For more information, see:

https://www.paessler.com/manuals/prtg/setting_up_a_notification_example

Figure 3-15: Counter Threshold Configuration

https://www.paessler.com/manuals/prtg/setting_up_a_notification_example


Page 30 of 57

Figure 3-16: Error Count Critical Severity Counter

Figure 3-17: Error Count Warning Severity Counter

VisionHub Monitoring Guide Monitoring VisionHub Using PRTG

Page 31 of 57

4 Monitoring VisionHub Using PRTG

4.1 Viewing the Home Page and Dashboards

To login to PRTG web application, in the browser address field, type the address of the server where the PRTG is installed, for example http://<IP>:8088/welcome. Note that it is mandatory to add port 8088 to the address. Use colon between IP address and port numer. In the Login screen, click on the Default Login button.

The welcome page is your default homepage and is shown when you log in and whenever you click Home.

Figure 4-1: Welcome Page

This page includes:

Current Alarms: Displays the number of alarms which are Down, Down (Acknowledged), Warning and Unusual, as well as a View All Alarms link, which displays a list of sensors with alarms.

Open Tickets: Displays the number of open tickets and as well as a View All Tickets link, which displays a list of the tickets.

Yesterday’s Activity: Displays the total number of Sensor Scans Performed, as well as the number of Sensor State Changes, Notifications Sent, Reports Generated and Web Pages Served.

License Status: Displays how many sensor licenses are available.


Page 32 of 57

The various Dashboard pages collate information from various parts of PRTG for display in one place. These pages include alarm information as well as the alarm priority.

The Dashboard pages include:

New Alarms

New Log Entries

Updated Tickets

Current Alarms: Displays the number of alarms which are Down, Down (Acknowledged), Warning and Unusual.

In addition, priority stars are displayed, with more stars meaning a higher priority.

To view the Dashboard:

Select Home > Dashboard 1, Dashboard 2 or Dashboard 3.

Figure 4-2: Dashboard 1


Page 33 of 57



To make a Dashboard your homepage, select Home > Make This My Homepage.


Page 34 of 57

4.2 Viewing the Map

Maps allow you to overviews of your monitored network. A map can have a background image (e.g. a network drawing) and you can place icons and graphs with your current monitoring status on the map.


https://www.paessler.com/manuals/prtg/maps

To view the map:

Select Maps.

Figure 4-5: Maps

Select the required map.

Figure 4-6: Map Dashboard



Page 35 of 57

4.3 Viewing the Devices

The Devices page lists your devices and their sensors and show you how many sensors are in Down, Warning, Up or Unusual state.

In addition, for priority stars are displayed, with more stars meaning a higher priority.

To view the devices:

Select Devices.

Figure 4-7: Devices

To drill-down, select a device or sensor.


Page 36 of 57

4.4 Viewing the Sensors

The Sensors page lists your sensors and show you how many sensors are in Down, Warning, Up or Unusual state.

In addition, for priority stars are displayed, with more stars meaning a higher priority.

Some of the SNMP data strings are not catalogued or saved in the PRTG DB, and the sensor shows the access time rather than presenting the SNMP string. The SNMP string is shown at the top of the Sensor Details page.

To view the devices:

Select Sensors.


Page 37 of 57

Figure 4-8: Sensors

To filter select Down, Warning, Up or Unusual.

Figure 4-9: Sensors With Status Down

To view more details, select a specific sensor.


Page 38 of 57

Figure 4-10: Sensor Details

4.5 Viewing the Device Sensors with Alarms

The Alarm page shows the list of sensors that are in an error or warning state. If all your systems are running correctly this page should list no sensors.

To view the device sensors with alarms:

Select Alarms > All or Alarms > Errors Only or Alarms > Warnings Only.

Figure 4-11: All Alarms


Page 39 of 57

Figure 4-12: Warning Alarms

To view more details, hover over the alarm or select the alarm.

Figure 4-13: Alarm

Figure 4-14: Alarm

4.6 Using the Enterprise Console

The Enterprise Console is an alternative interface that you can use to connect to the PRTG core server. It is a native Windows application for fast access to data and monitoring management. By default, the Enterprise Console runs in background and shows a message box whenever there are new alerts, new messages, or new tickets for your monitoring.


Page 40 of 57


https://www.paessler.com/manuals/prtg/enterprise_console

4.7 Viewing the Sensor Trap Receiver Messages

To view a list of the sensor traps, potential functionality loss and how to correct the problem see:

https://www.paessler.com/manuals/prtg/enterprise_console


Page 41 of 57

SVR Traps/Events

Video Application Server Traps/Events

Operational Application Server Traps/Events

To view sensor trap receiver messages:

Select Devices.

Figure 4-15: Devices

Select an SNMP Trap Receiver.

Figure 4-16: SNMP Trap Receiver

The Messages gauge displays the number of messages. Click Messages.


Page 42 of 57

Figure 4-17: SNMP Trap Receiver - Messages

4.8 Using Ticketing

PRTG Network Monitor includes its own ticketing system. You can use PRTG tickets to manage various issues which may appear while monitoring a network.

A ticket in PRTG contains information about recent events which need to be attended too by the administrator or support person. A ticket appears as a task for a particular PRTG user.


https://www.paessler.com/manuals/prtg/tickets

Tickets can be assigned to you by the PRTG system or by other users. You can edit, resolve, or close existing tickets, or assign them to other users.

To view tickets:

Select Tickets.

https://www.paessler.com/manuals/prtg/tickets


Page 43 of 57

Figure 4-18: PRTG Tickets

To view a specific ticket, click on the ticket.

Figure 4-19: PRTG Ticket

You can Edit, Assign, Remove or Close the ticket, as required.

VisionHub Monitoring Guide For Advanced Users Only

Page 44 of 57

5 For Advanced Users Only

5.1 Importing the VisionHub MIB Files

An OIDlib file is a PRTG-proprietary pre-compiled MIB library generated by the PRTG Paessler MIB Importer V3 tool. Qognify provides several of these.

You can copy the OIDlib file for the VisionHub components on to the server:

Qognify-VH-OPAS.oidlib: Operational Application Server

Qognify_VH_VDAS.oidlib: Video Application Server

Qognify_VH_SVR.oidlib: SVR

DellSystems.oidlib: For Turnkey Dell-based SVR.

Alternatively, you can copy the MIBs for the VisionHub components and then import the files, creating OIDlib files for PRTG:

QognifyVisionHubApplicationServer.mib: Operational Application Server

qognifyVAS.mib: Video Application Server

qognify-NVR.mib: SVR

For more information, refer to the Paessler MIB Importer User Manual:

http://download-cdn.paessler.com/download/mib_importer_manual.pdf

To install the VisionHub OIDlib files:

Copy the OIDlib files to the \snmplibs folder of your PRTG installation, typically C:\Program Files (x86)\PRTG Network Monitor\ snmplibs.

To install the VisionHub MIBs:

Copy the MIBs to the \MIB folder of your PRTG installation, typically C:\Program Files (x86)\PRTG Network Monitor\MIB.

To import a MIB:

Download the MIB Importer from www.paessler.com/tools/mibimporter.

Double-click on Paessler MIB importer V3 Setup.exe.

http://download-cdn.paessler.com/download/mib_importer_manual.pdf

http://www.paessler.com/tools/mibimporter


Page 45 of 57

Figure 5-1: Paessler MIB Importer Setup Wizard

Click Next.

Figure 5-2: License Agreement

Select I accept the agreement and click Next.


Page 46 of 57

Figure 5-3: Destination Location

Select a location and click Next.

Figure 5-4: Additional Tasks

Select whether to create icons, and then click Next.


Page 47 of 57

Figure 5-5: Complete the Setup

Click Finish.

Double-click the Paessler MIB Importer V3 icon.


Page 48 of 57

Figure 5-6: Paessler MIB Importer Window

Select Import > MIB File.

NOTE: You may need to manually delete the traps from the UI so that the OIDLIB includes only the MIB without the traps.

Navigate to and select a VisionHub MIB (in the \MIB subfolder of your PRTG installation):

qognify.mib for the Recorder

qognifyVAS.mib for the Video Application Server

QognifyVisionHubApplicationServer.mib for the Operational Application Server

Click Open.


Page 49 of 57

Figure 5-7: Import Log

Click Close.

Select File > Save to save the created Paessler SNMP Library file for PRTG.

Repeat for each of the MIBs.

Copy the SNMP library file into the \snmplibs subfolder of your PRTG installation.

5.2 Creating a Device Template

You can create a device template from an existing device in your device tree. The device template will then include all the sensors from the selected device. You can choose to exclude some of these sensors.

Qognify provides out-of-the-box device templates and icons. For more information, see Error! Reference source not found..

To create a device template:

Right click on a device in the device tree, and select Create Device Template.


Page 50 of 57

Figure 5-8: Create Device Template

Enter a file name and template name.

If required, select sensors to exclude.

Click Continue. The template is created.

5.3 Adding SNMP Sensors

You must now add SNMP sensors to the device. There are three Qognify SNMP library files available depending on the device type (SVR, Operations Application Server or Video Application Server).

Once you select an SNMP library file, you will be able to select the sensors to monitor. There are several sensors available for each of the device types.

Typically you would, as a minimum, configure a sensor for the CRITICAL severity error count and one for the WARNING error count.

NOTE: Each sensor requires a PRTG license.

To add SNMP sensors:

For the selected device, click Add Sensor.

Figure 5-9: Add Sensor

In the Search field, enter snmp.


Page 51 of 57


In the SNMP Library section, click Add This.

Figure 5-11: Select Library File

Select the required Qognify library file..

Click OK.


Page 52 of 57


Select the required sensors, and then click Continue.

5.4 Managing Users

PRTG administrator users can add, edit or delete user groups and users, and assign a user as a member of a user group. A user can also be “paused” (or “resumed”) if you want to temporarily restrict access for a user.

For more information on creating users, see:

https://www.paessler.com/manuals/prtg/user_groups_settings



PRTG can also be integrated with Active Directory.

https://www.paessler.com/manuals/prtg/user_groups_settings



Page 53 of 57


https://www.paessler.com/manuals/prtg/active_directory_integration

NOTE: PRTG does not support SSO.

To manage users:

Select Setup > System Administration.

Figure 5-13: System Administration

To configure users, select User Accounts.

Figure 5-14: User Accounts

To configure user groups, select User Groups.

To add a user group, click New User Group.

https://www.paessler.com/manuals/prtg/active_directory_integration


Page 54 of 57

Figure 5-15: New User Group

Fill in the fields, as required and then click Continue.

To add a user, click New User.

Figure 5-16: New User

Fill in the fields, as required, and then click Continue.

VisionHub Monitoring Guide Troubleshooting

Page 55 of 57

6 Troubleshooting

This topic covers various issues and their workaround.

Issue Workaround

If you noticed while working with the PRTG web client that the date/time in the bottom right corner of the webpage is incorrect, update it manually.

First, check that the server has the correct time zone/date/time configuration.

1. In the PRTG web client; select the Setup tab > Account Settings > Click on My Account (pic. 67).

2. The Log In dialog opens, click Log In.

(pic. 68)

3. On the shown page, scroll down until you see the Time Zone option. (pic. 69)

4. Select the correct time zone and click Save.

(pic. 69)

Figure 6-1: PRTG Account Page

VisionHub Monitoring Guide Troubleshooting

Page 56 of 57

Figure 6-2: PRTG Account Login Page

Figure 6-3: PRTG Time Zone Settings Page

VisionHub Monitoring Guide SNMP Reference

Page 57 of 57

7 SNMP Reference


Page 1 of 37

7.1 SNMP MIBs

Figure 7-1: Qognify MIBs

Table 7-1: Qognigy MIBs

OID MIB Tree Description

.1.3.6.1.4.1.46907.1 operationalApplicationServer MIB for the Operational Application Server.

.1.3.6.1.4.1.46907.2 videoApplicationServer MIB for the Video Application Server.

.1.3.6.1.4.1.46907.3 SVR MIB for the SVR.


Page 2 of 37

7.2 Operational Application Server MIB

Figure 7-2: Operational Application Server MIB


Page 3 of 37

Table 7-2: Operational Application Server MIB Tree

OID MIB Tree Syntax Description

SERVER-OBJECTS

.1.3.6.1.4.1.46907.1.1.1 nvServiceSiteName DISPLAYSTRING The service site name/video GW name.

.1.3.6.1.4.1.46907.1.1.4 nvServiceVersion DISPLAYSTRING The version of the server.

.1.3.6.1.4.1.46907.1.1.5 nvErrorCountCriticalSeverity INTEGER (0..2147483647) Error count for CRITICAL severity.

.1.3.6.1.4.1.46907.1.1.6 nvErrorCountWarnSeverity INTEGER (0..2147483647) Error count for WARNING severity.

.1.3.6.1.4.1.46907.1.1.7 nvMonitoredComponentsCount INTEGER (0..2147483647) Count of current monitored components.

SERVER-NOTIFICATIONS

.1.3.6.1.4.1.46907.1.2.1 asMaintananceTrap DISPLAYSTRING Operational Application Server general trap.

.1.3.6.1.4.1.46907.1.2.2 eventComponentIPAddress DISPLAYSTRING Server IP.

.1.3.6.1.4.1.46907.1.2.4 eventUniqueID DISPLAYSTRING Unique ID of the event.

.1.3.6.1.4.1.46907.1.2.5 eventType EventType (INTEGER) {recorderEvent(1),channelEvent(2), deviceEvent(3),otherEvent(4),databaseEvent(5), icmEvent(6),cssEvent(7),videoserverEvent(8), decodderEvent(9),decoderchannelEvent(10), externalserverEvent(11),vhserverEvent(20)}

Event type (operationalApplicationServerEvent)

.1.3.6.1.4.1.46907.1.2.6 eventSeverity

Event severity (normal/warn/critical/info) Event severity (normal/warn/critical/info)

.1.3.6.1.4.1.46907.1.2.7 eventDescription DISPLAYSTRING Event description.

.1.3.6.1.4.1.46907.1.2.8 eventState State (INTEGER) {off(0),on(1),notify(2)} Event state (On/Off)

.1.3.6.1.4.1.46907.1.2.9 eventFunctionLoss DISPLAYSTRING Functionality loss


Page 4 of 37

7.3 Video Application Server MIB

Figure 7-3: Video Application Server MIB


Page 5 of 37

Table 7-3: Video Application Server MIB Tree


.1.3.6.1.4.1.4

6907.2.1

SERVER-OBJECTS

.1.3.6.1.4.1.4

6907.2.1.1

vasSiteID INTEGER The unique ID of the

site

.1.3.6.1.4.1.4

6907.2.1.2

vasSiteName DISPLAYSTRING The site name

.1.3.6.1.4.1.4

6907.2.1.3

vasSiteIPAddress DISPLAYSTRING The site IP Address

.1.3.6.1.4.1.4

6907.2.1.4

vasSiteVersion DISPLAYSTRING The site version

.1.3.6.1.4.1.4

6907.2.1.5

vasErrorCountCriticalSeve

rity

INTEGER Error count for

CRITICAL severity

.1.3.6.1.4.1.4

6907.2.1.6

vasErrorCountWarnSeveri

ty

INTEGER Error count for

WARNING severity

.1.3.6.1.4.1.4

6907.2.1.7

vasNumOfRecorders INTEGER Number of

recorders in site


Page 6 of 37


.1.3.6.1.4.1.4

6907.2.1.8

vasNumOfEdgeDevice INTEGER Number of edge

devices in site

.1.3.6.1.4.1.4

6907.2.1.9

vasNumOfChannels INTEGER Number of channels

in site

.1.3.6.1.4.1.4

6907.2.1.10

vasNumOfDecoders INTEGER Number of

decoders in site

.1.3.6.1.4.1.4

6907.2.1.11

vasNumOfRSVRClusters INTEGER Number of RSVR

clusters

.1.3.6.1.4.1.4

6907.2.1.12

vasNumOfWSAServers INTEGER Number of WSA

Web servers

.1.3.6.1.4.1.4

6907.2.1.13

vasNumOfMPCServers INTEGER Number of MPC

Servers

.1.3.6.1.4.1.4

6907.2.1.14

vasNumOfSUSEServers INTEGER Number of SUSE

Web Servers

.1.3.6.1.4.1.4

6907.2.2



Page 7 of 37


.1.3.6.1.4.1.4

6907.2.2.1

vasMaintananceTrap SVR general trap

.1.3.6.1.4.1.4

6907.2.2.2

eventServerIPAddress DISPLAYSTRING Server IP

.1.3.6.1.4.1.4

6907.2.2.3

eventServerName DISPLAYSTRING Server name

.1.3.6.1.4.1.4

6907.2.2.4

eventUniqueID DISPLAYSTRING Unique ID of the

event

.1.3.6.1.4.1.4

6907.2.2.5

eventType INTEGER Event type

(recoder/channel/st

orage)

.1.3.6.1.4.1.4

6907.2.2.6

eventSeverity INTEGER Event severity

(normal/warn/critic

al/info)

.1.3.6.1.4.1.4

6907.2.2.7

eventDescription DISPLAYSTRING Event description


Page 8 of 37


.1.3.6.1.4.1.4

6907.2.2.8

eventState INTEGER Event state (On/Off)

.1.3.6.1.4.1.4

6907.2.2.9

eventFunctionLoss DISPLAYSTRING Functionality loss

.1.3.6.1.4.1.4

6907.2.2.1

vasMaintananceTrap SVR general trap


Page 9 of 37

7.4 SVR MIB

Figure 7-4: SVR MIB


Page 10 of 37

Table 7-4: SVR MIB Tree


.1.3.6.1.4.1.46907.3.1

SERVER-OBJECTS

.1.3.6.1.4.1.46907.3.1.1

nvRecorderName DISPLAYSTRING The recorder name

.1.3.6.1.4.1.46907.3.1.2

nvRecorderIPAddress DISPLAYSTRING The recorder IP Address

.1.3.6.1.4.1.46907.3.1.3

nvRecorderServerID INTEGER (1..2147483647)

The unique ID of the server

.1.3.6.1.4.1.46907.3.1.4

nvRecorderVersion DISPLAYSTRING The recorder version

.1.3.6.1.4.1.46907.3.1.5

nvErrorCountCriticalSeverity

INTEGER (0..2147483647)

Error count for CRITICAL severity

.1.3.6.1.4.1.46907.3.1.6

nvErrorCountWarnSeverity

INTEGER (0..2147483647)

Error count for WARNING severity

.1.3.6.1.4.1.46907.3.1.7

nvNumOfEdgeDevice INTEGER (0..2147483647)

Number of configured edge devices

.1.3.6.1.4.1.46907.3.1.8

nvNumOfVideoChannels INTEGER (0..2147483647)

Number of configured video channels

.1.3.6.1.4.1.46907.3.1.9

nvNumOfAudioChannels INTEGER (0..2147483647)

Number of configured audio channels


Page 11 of 37


.1.3.6.1.4.1.46907.3.1.10

nvNumOfVAChannels INTEGER (0..2147483647)

Number of configured VA channels

.1.3.6.1.4.1.46907.3.1.11

nvStorageCapacity INTEGER (0..2147483647)

Total storage capacity [GB]

.1.3.6.1.4.1.46907.3.1.12

nvEstimatedRetention INTEGER (0..2147483647)

Estimated retention [Hours]

.1.3.6.1.4.1.46907.3.1.13

nvStorageThrouputLimit INTEGER (0..2147483647)

Configured storage throughput [MB/Sec]

.1.3.6.1.4.1.46907.3.1.14

nvComputationalPowerLimit

INTEGER (0..2147483647)

Configured computational power [%]

.1.3.6.1.4.1.46907.3.2


.1.3.6.1.4.1.46907.3.2.1

svrMaintananceTrap

.1.3.6.1.4.1.46907.3.2.2

eventServerIPAddress DISPLAYSTRING Server IP

.1.3.6.1.4.1.46907.3.2.3

eventServerName DISPLAYSTRING Server name

.1.3.6.1.4.1.46907.3.2.4

eventUniqueID DISPLAYSTRING Unique ID of the event


Page 12 of 37


.1.3.6.1.4.1.46907.3.2.5

eventType EventType (INTEGER) {recorderEvent(1),channelEvent(2),deviceEvent(3),otherEvent(4)}

Event type (recorder/channel/storage)

.1.3.6.1.4.1.46907.3.2.6

eventSeverity Severity (INTEGER) {normal(2),warn(3),

critical(4)}

Event severity (normal/warn/critical/info)

.1.3.6.1.4.1.46907.3.2.7

eventDescription DISPLAYSTRING Event description

.1.3.6.1.4.1.46907.3.2.8

eventState State (INTEGER) {off(0), on(1),notify(2)}

Event state (On/Off)

.1.3.6.1.4.1.46907.3.2.9

eventFunctionLoss DISPLAYSTRING Functionality loss


Page 13 of 37

7.5 SVR Traps/Events

Table 7-5: SVR Traps/Events

Trap Description Possible Function Lost To Do

MaintenanceRecorderSystemDiskSpace Recorder {0} is low on free disk space on the system drive.

Recording may halt unexpectedly.

Free up some disk space on the Recorder system drive. Call local support.

MaintenanceRecorderVideoSystemNotShutdownOrderly

Recorder {0} was not shutdown properly. Recording on this Recorder may be lost.

Possible loss of recording. Shutdown and then restart the recording software normally. Call local support.

MaintenanceRecorderPartiallyDown Not all of Recorder {0} components are functioning.

Recording and playback may not be available

Call local support.

MaintenanceRecorderVideoSystemLockedDiskSpace (if > 27)

Recorder {0} locked disk space is close to its maximum capacity.

Recorder unable to lock future events.

Unlock old or less important sessions.

MaintenanceRecorderVideoSystemDefaultTriggerAssociation

Recorder {0} is working with default trigger settings.

Alarm capabilities may not be functioning correctly. Possible recording loss.

Reconfigure your trigger association. Shutdown and then restart the recording software normally.

MaintenanceRecorderVideoSystemDiskSpace (if FreeVideoDiskPercentage < 1)

Recorder {0}'s video system disk space is too low.

Possible unexpected halt to recording.

Check that automatic deletion is enabled for the video system.


Page 14 of 37


MaintenanceRecorderDiskError Fatal error on Recorder {0} â€“ disk is not functioning (error identified while writing to disk).

Recorder may not be able to record or playback.

Check Windows event log for location of failure. Verify that all SCSI cables are firmly connected to the SCSI connector on both the Recorder and the RAID. Shut down the Recorder System Software and shut down the Windows operating system. Open the Recorder cover and remove the SCSI card. Reinsert the SCSI card back into its original slot on the motherboard. Make sure the card is firmly installed before restarting the Recorder. Run disk self-test utility to verify integrity of storage.

MaintenanceRecorderCurrentCpuUsageTooHigh

Recorder {0}'s current CPU usage is too high.

The Recorder may fail to function properly.

Close unnecessary applications. Reduce Recorder activity (close unnecessary video streaming). Call local support.

MaintenanceRecorderCurrentStorageUtilizationTooHigh

Recorder {0}'s current storage utilization is too high.

Recording may be lost. Verify the Recorder storage devices are functioning properly. Reduce recording quality. Call local support.


Page 15 of 37


MaintenanceRecorderConfiguredComputingPowerExceeded

Recorder {0}'s configured computing power has exceeded the defined limit.

The Recorder may encounter performance problems.

Consider reducing Recorder activity (close open video streams, reduce recording quality or remove CSS associations).

MaintenanceRecorderConfiguredStorageThroughputExceeded

Recorder {0} configured storage throughput has exceeded the defined limit.

Recording cannot be guaranteed.

Check the Recorder defined storage throughput limit. Consider reducing Recorder activity (close open video streams, reduce recording quality or remove CSS associations).

MaintenanceChannelRecorderVideoErrorState

Channel {0} on Recorder {1} has an error.

Recording may be lost. Verify video signal from camera is 1V peak to peak into Recorder. Call local support.


Page 16 of 37


MaintenanceChannelRecorderVideoExceededStorageDays

The storage period of Video Channel {0} on Recorder {1} is not according to its pre-defined capacity.

Recording may be aborted on this channel.

Check that channel video quality (bit rate setting) matches the original order (compare with the original quote setting for this video channel). Check that channel activity (%) matches the original order (compare with the original quote setting for this video channel). Check that channel has been recording through the whole retention period (not in "Stop Recording" mode). Check that there are no locked recordings. If not, free some disk space by unlocking some locked recordings. Call local support.

MaintenanceDeviceRecorderVideoConnectorError

Video card number {0} on Recorder {1}'s cable is not connected. Recording capability has been lost for this video card.

Video is not being recorded. Reconnect the cable. Call local support.


Page 17 of 37


MaintenanceDeviceRecorderVideoDisconnectedError

Unable to communicate with device {0} on Recorder {1}.

Check network connectivity between the Recorder and the device. Make sure the device is up and running. Call local support.

MaintenanceRecorderSiteWasModified Recorder {0} was attached to a different site.

Channel recording parameters may have been changed.

Make sure this Recorder is enabled in only one site and disabled in any other site. Refresh the Recorder in the SiteBuilder application. Call local support.

MaintenanceRecorderVideoInitRecorderFailed

Recorder {0} failed to initialize. Possible loss of recording. Call local support.

MaintenanceRecorderVideoInitVideoProviderFailed

Recorder {0} video provider component failed to initialize.

Possible loss of recording. Call local support.

MaintenanceRecorderVideoInitMemoryManagerFailed

Recorder {0} memory manager component failed to initialize.

Possible loss of recording. Call local support.

MaintenanceRecorderVideoDeletingUnexportedFile

Recorder {0} has deleted a video file that was not exported to the central storage.

Recording. Check network connectivity from the Recorder to the Central Storage Server. Verify Central Storage Server is up and running. Call local support.


Page 18 of 37


MaintenanceRecorderVideoDeletingUnexportedSession

Recorder {0} has deleted a video session that was not exported to the central storage.

Recording. Check network connectivity from the Recorder to the Central Storage Server. Verify Central Storage Server is up and running. Call local support.

MaintenanceRecorderVideoDriveMappingFailed

Recorder {0} has failed to map a disk drive.

Recording. Verify all drives present in Windows. Reseat connections to all hard disk drives. Call local support.

MaintenanceRecorderAutomaticFailover As a result of automatic failover, Recorder {0} has taken over the functioning of the failed Recorder.

Make sure the recording software is up and running. Check network connectivity. Call local support.

MaintenanceRecorderAutoDaylightSettingChange

Recorder {0}'s automatic daylight saving settings changed.

MaintenanceRecorderClockWasModified Recorder {0}'s clock modified.

MaintenanceChannelRecorderVideoMOLStopedDueToPerformance

Video Channel {0} on Recorder {1} has stopped monitoring due to performance problems.

Verify network performance. Call local support.

MaintenanceChannelRecorderVideoConnectionAborted

Video Channel {0} on Recorder {1} playback connection has aborted.

Verify network performance. Call local support.

MaintenanceSchedulerServerReady Scheduler server on Recorder {0} is ready.


Page 19 of 37


MaintenanceSchedulerServerOff Scheduler server on Recorder {0} is down.

MaintenanceSchedulerServerFailedToInitialize

Scheduler server on Recorder {0} failed to initialize.

Possible loss of recordings. Call local support.

MaintenanceSchedulerServerFailedToInitializeTarget

Scheduler server on Recorder {0} failed to initialize target.


MaintenanceSchedulerFailedSettingProgramParamsOnTarget

Scheduler server on Recorder {0} failed to set program parameters on target.


MaintenanceSchedulerFailedSettingSpecialEventStatus

Scheduler server on Recorder {0} failed to set special event status.


MaintenanceRecorderConnectionError Unable to communicate with the recording software on Recorder {0}.

Recording and playback may not be available.

Make sure the recording software is up and running. Check network connectivity. Call local support.

MaintenanceRecorderDiskIOFailure Recorder {0} has suffered from a disk read/write failure.

DVR may not be able to record or playback.

MaintenanceRecorderVideoSystemNotShutdownOrderly

Recorder {0} was not shutdown properly. Recording on this Recorder may be lost.

Possible loss of recording. Shutdown and then restart the recording software normally. Call local support.

MaintenanceRecorderVideoSystemDefaultRecordingParameters

Recorder {0} is working with default recording parameters.

Possible loss of recording. Shutdown and then restart the recording software normally. Reconfigure your channel recording parameters.


Page 20 of 37


MaintenanceChannelRecorderVideoContentAnalisysNotEffective

Video Analytics error on channel {0} on Recorder {1}.

Video Analytics alarm capabilities may have been lost.

Wait up to three minutes. Manually reset background. Call local support.

MaintenanceChannelRecorderVideoSignalLossState

No video/audio (signal loss) on Channel {0} on Recorder {1}.

Recording may be lost. Check if cable is connected. Check if camera is connected. If it is IP Device, check its network cables and network connectivity. If it is IP Device with proper network accessibility, try to reset device (IP Camera / Encoder). Call local support.

MaintenanceChannelRecorderVideoRecordingAborted

Video channel {0} on Recorder {1} recording was aborted by the Recorder due to a technical problem.

Recording may be lost. Call local support.

MaintenanceChannelRecorderVideoCameraTamper

Camera {0} on Recorder {1} has been tampered with.

Camera may not be able to view the desired scene.

Check cause or tamper origin. Position camera to desired spot.

MaintenanceChannelRecorderNotInRecordStateStatus

Channel {0} on Recorder {1} is not recording.

Channel is not recording. Start recording on channel.

MaintenanceChannelRecorderVideoAlgorithmDark

Camera associated to channel {0} cannot be observed due to one of the following reasons: too dark/ too bright/ out of focus/ blocked.

Camera scene cannot be observed.

Check the origin of camera tampering.


Page 21 of 37


MaintenanceChannelRecorderVideoAlgorithmFocus




MaintenanceChannelRecorderVideoAlgorithmCovered




MaintenanceChannelRecorderVideoAlgorithmBright




MaintenanceChannelRecorderVideoOutOfPos

Channel {0} is suspected to be redirected from reference position.

Camera may not be able to view the desired scene.

Check cause or tamper origin. Reset camera position. Re-learn current scene position.

MaintenanceDeviceRecorderVideoInitFailed

VICO card {0} on Recorder {1} failed to initialize. Recording capability has been lost for this VICO card.

Video is not being recorded. Call local support.

MaintenanceDeviceRecorderRedundancySwitchOver

NVE1008 has performed a switch over.

Make sure the device recording software is up and running. Check network connectivity. Call local support.


Page 22 of 37


MaintenanceChannelLocalRecordingDataNotFound - alarm

Video/audio data was not found on Channel {0} on Recorder {1} (times {2} till {3}).


Make sure the device is set to record. Check network connectivity is available to the device. Call local support.

MaintenanceChannelLocalRecordingCatchupNotStarted

The Catch-Up on channel {0} on Recorder {1} was not successful for a long period (times {2} till {3}).

Check network connectivity is available to the device. Call local support.

MaintenanceChannelLocalRecordingTaskExpired

The Catch-Up on Channel {0} on Recorder {1} was cancelled due to time expiration (times {2} till {3}).


Check network connectivity is available to the device. Call local support.

MaintenanceChannelLocalRecordingDeviceNotSynched

The channel {0} on Recorder {1} is not synchronized with the Recorder.

Catch up from edge recording. Check NTP server availability. Check if camera was set to synchronize the time with NTP server. Check and adjust Recorder and edge device clocks. Call local support.


Page 23 of 37

7.6 Video Application Server Traps/Events

Table 7-6: Video Application Server Traps/Events


Database

MaintenanceDatabaseNotCorrelatedWithRecorders

Site AMS database is not synchronized with the Recorder.

Recorder synchronization.

Refresh the Recorder in the SiteBuilder application.

MaintenanceDatabaseDailyMaintenanceFailed

Auto-Deletion database job has failed.

Complete database restoration may not be possible.

Backup the database manually. Call local support.

MaintenanceDatabaseBackupFailure

Complete AMS database backup has failed.

Database may not be recoverable on failure.


MaintenanceDatabaseBackupNeverExecuted

Backup of site AMS database was never executed.

AMS database may not be recoverable on failure.


MaintenanceDatabaseSelfTestFailed

Site AMS database self-test failed. Database problems may not be reported.

Check connectivity to the database. Call local support.

MaintenanceDatabaseConnectionError

No connection to site AMS database. There may be a problem working with the system.

Check that site AMS database server is up and connected Check that SQL database services are up and running. Call local support.


Page 24 of 37


MaintenanceDatabaseMaintenanceTableExceededUsedPercentage

Site AMS database maintenance history table has exceeded its space limit.

Site AMS database maintenance history may not be written to database.

Call local support.

MaintenanceDatabaseUpdateUsageDBFailed

Defragmentation of site AMS database files failed.

Site AMS database performance may be lower than usual.

Call local support.

MaintenanceDatabaseLastMainEventPartitionsJob

The maintenance job process of the EVENTS database has failed.

The AMS database functionality will be damaged and new events may be lost.

Call local support.

MaintenanceDatabaseEnoughFreeSpace

There is not enough space on the 'EVENTS' database hard drive.

New events will not be saved and database maintenance processes will fail.

Clean up space on your hard drive. Call local support.

MaintenanceDatabaseTableHasBeenDeleted

Some events have been deleted due to lack of free disk space.

Events have been deleted from AMS database.

Clean up space on your hard drive. Call local support.

Recorder


Page 25 of 37


MaintenanceRecorderClockNotSynchronized

Recorder {0}'s clock is not synchronized with the site clock.

Synchronized playback integrity lost.

Shutdown Recorder software, then adjust Recorder clock and restart Recorder software. Follow this check list only if you are qualified to perform time adjustments otherwise you may damage the system and lose data. Check that the specified Recorder and AMS are set to the current time zone. WARNING - DO NOT CHANGE THE TIME ZONE OF THE RECORDER WHILE RECORDER SOFTWARE IS RUNNING. Check that the GMT time difference between the specified Recorder and the AMS is less than 30 seconds. If the time zone of the Recorder is wrong or if the GMT time difference is more than 30 seconds, shutdown the Recorder, adjust the time zone of the Recorder, adjust the time of the Recorder to be set at an interval of a maximum of 10 minutes from the AMS. Call local support.

MaintenanceRecorderManualFailover

As a result of manual failover, Recorder {0} has taken over the functioning of the failed Recorder.


Page 26 of 37


MaintenanceRecorderClusterVersionMismatch

The Failover Cluster Monitor Service on Recorder {0} does not match the site version.

The failover cluster may not function correctly.

Make sure the Failover Cluster Monitor Service version on the Redundant Recorder matches the Application Server version. Install the correct version of the Failover Cluster Monitor Service. Call local support.

MaintenanceRecorderVideoSystemMpcDisconnected

Recorder {0} failed to connect to its associated MPC Server.

Suspect Search data is not collected and future queries will exclude the current time (while these two servers are disconnected from each other).

Make sure the recorder is associated to an MPC Server. Check network connectivity between the Recorder and the MPC Server. Make sure the associated MPC Server is up and running. Call local support.

ICM

MaintenanceICMEngineConnectionError

Connection error with PTZ engine server {0}.

PTZ capabilities from Control application are unavailable.

Make sure PTZ engine machine is up. Make sure PTZ engine process is up and receiving commands. Check network connectivity to the PTZ engine machine. Call local support.

MaintenanceICMAgentNotConnected

PTZ Engine {0} is not connected to its agent.

PTZ capabilities from the application may be disabled.

Make sure the PTZ agent is up and running. Call local support.

MaintenanceICMAgentUpdatingError

PTZ engine {0}'s connection to one of its agents has been lost while trying to update.




Page 27 of 37


MaintenanceICMAgentCommunicationError

PTZ engine {0}'s connection to one of its agents has been lost.



MaintenanceICMAgentSerialPortError

PTZ engine {0}'s agent has an error in its serial port connection.


Make sure that the configuration of the agent's serial port is correct. Call local support.

MaintenanceICMAgentCommandQueueIsFull

PTZ Engine {0}'s agent has an overflow in its command queue.


Call local support.

CSS


Page 28 of 37


MaintenanceCSSClockNotSynchronized

Central Storage Server {0}'s clock is not synchronized with the site clock.

Synchronized playback integrity lost.

Shutdown the CSS software, then adjust the CSS clock and restart the Recorder software. Follow this check list only if you are qualified to perform time adjustments otherwise you may damage the system and lose data. Check that the specified CSS and AMS are set to the current time zone. WARNING - DO NOT CHANGE THE TIME ZONE OF THE CSS WHILE THE CSS SOFTWARE IS RUNNING. Check that the GMT time difference between the specified CSS and the AMS is less than 30 seconds. If the time zone of the CSS is wrong or if the GMT time difference is more than 30 seconds, shutdown the CSS, adjust the time zone of the CSS, and adjust the time of the CSS to be within an interval of a maximum of 10 minutes from the AMS. Call local support.

Dual recording

MaintenanceDeviceDualRecordingWrongSubset

Secondary device {0} has channels that the primary device does not have.

Dual Recording Check if scenario is correct.

Application Server


Page 29 of 37


MaintenanceApplicationServerConnectionError

No connection to Site Application server.

You may encounter system difficulties. No alarms and/or channels status available.

Check that the Application Server machine is up and running. Make sure that the Application Server service is up and running. Call local support.

MaintenanceApplicationServerState

Site Application server is up.

Decoder(VMS)

MaintenanceDecoderConnectionError

Decoder {0} connection error. Decoder synchronization. Check connection to the decoder.

MaintenanceDecoderChannelErrorState

Decoder {0} Monitor {1} error. Decoder channel synchronization.

Check connection to the decoder.

MaintenanceDecoderVersionNotMatch

Decoder {0} version does not match the Application Server version.

External Servers

MaintenanceTransactionServerConnectionError

ATM Transaction Server {0} connection error.

You may encounter system difficulties. Query transactions will not be available.

Check that the ATM Transaction Server machine is up and running. Make sure that the ATM Transaction Server service is up and running. Check ATM Transaction Server machine connection to the network. Call local support.


Page 30 of 37


MaintenanceTransactionServerVisionDBConnectionError

ATM Transaction Server {0} has no connection to site Database {1}.

There may be a problem working with the ATM transaction system.

Check that site database server is up and connected. Check that SQL database services are up and running. Check database server connection to the network Call local support.

MaintenanceTransactionServerTransactionDBConnectionError

ATM Transaction Server {0} has no connection to ATM transactions Database {1}.

ATM transactions query not available.

Check that ATM transactions database server is up and connected. Check that SQL database services are up and running. Check database server connection to the network. Call local support.

MaintenanceTransactionServerInternalError

ATM Transaction Server {0} internal error.

You may encounter system difficulties.

Reset ATM Transaction Server service. Call local support.

MaintenanceCaptureServerConnectionError

ATM Agent {0} connection error. ATM Transactions may be lost.

Check that the ATM Agent machine is up and running. Make sure that the ATM Agent service is up and running. Check ATM Agent connection to the network. Call local support.

MaintenanceCaptureServerRecorderConnectionError

ATM Agent {0} no connection to recorder {1}.

Possible loss of video recording.

Check that recorder server is up and connected. Check that recorder services are up and running. Check recorder server connection to the network. Call local support.

MaintenanceCaptureServerChannelStartRecordeFailure

ATM Agent {0} start recording for recorder {1} channel {2} failed.

Possible loss of video recording.

Check channel configuration. Call local support.


Page 31 of 37


MaintenanceCaptureServerInternalError

ATM Agent {0} internal error. You may encounter system difficulties.

Reset ATM Agent service. Call local support.

MaintenanceCaptureServerATMInactivity

ATM Agent {0} ATM {1} inactive for a long time.

ATM Transactions may be lost.

Check ATM connection and configuration. Call local support.

MaintenanceSuSeMonitorConnectionError

Monitor Server {0} connection error. You may encounter system difficulties. Query MPC will not be available.

Check MPC Server machine/Suspect Search Web Server machine connection to the network. Check that the MPC Server machine/Suspect Search Web Server machine is up and running. Make sure that the MPC Server Monitoring service/Suspect Search Web Server Monitoring service is up and running. Call local support.

MaintenanceMPCServerConnectionError

MPC Server {0} connection error. You may encounter system difficulties. Query MPC will not be available.

Check MPC Server machine connection to the network Check that the MPC Server machine is up and running. Make sure that the MPC Server service is up and running. Call local support.

MaintenanceMPCCurrentCpuUsageTooHigh

MPC Server {0} current CPU usage is too high - {1}.

The MPC Server may fail to function properly.

Reduce MPC activity (close unnecessary applications). Call local support.


Page 32 of 37

7.7 Operational Application Server Traps/Events

The function loss depends on which system component is affected.

Table 7-7: Operational Application Server Traps

Event Type State Description Possible Function Lost To Do

ServiceStatus Off Connectivity test succeeded NA NA

Service sent info event: Server is

running normally

NA NA

On (service/ DB/GW host)

Connectivity test failed; Service is

running

Service is not fully functional -

although running.

Wait a few minutes, if does not turn into

'Connectivity test succeeded'/'Server is running

normally', restart the service.


Connectivity test failed; Service is

down

Service not working, loss

according to specific service.

Window service/GW host: Start relevant service.

Database: Check SQL service and start if needed.

SQL jobs: Check both SQL service and SQL agent

and start if needed.


Service sent fatal event: Service

was stopped

Service stopped. loss according

to specific service.


Page 33 of 37



Service is down Service stopped, loss according

to specific service.


Failed to monitor service state,

could not retrieve management

object

Functionality error. Applicable too Monitoring Service.

Call support.


Failed to read service state from

management object

Functionality error. Applicable to Monitoring Service.

Call support.


Service sent warn event: {0}

On (Web Service)

Connectivity test failed on web

service

Web service failed monitoring. Applicable to Web API.

Check connectivity, configuration or if web

service is down.

On (Web Service)

Unhandled Exception Web service failed monitoring. Call support.

Initialization Off Service sent info event: Service

initialized successfully

NA NA

Off Service is back online NA NA


Page 34 of 37


Off Service logged in to the server

successfully

Applicable to Operational Service and Scheduler.

NA

On Failed to start service Service not working, loss according to specific service.

Applicable to Operational Service, Notification Service; and Scheduler.

Check connectivity, configuration, try start relevant service again, if this fails, call support.

On Failed to initialize service Service not working, loss according to specific service.

Applicable to Auto Task Server, Escalation Server, BPM Service, Triggers Server and GW host.


On Failed to start services host Service not working, loss according to specific service.

Applicable to Operational Service.


On Service sent fatal event: Failed to

login to server



Applicable to Auto Task Server, Escalation Server, Scheduler, Triggers Server and BPM Service.

Check connectivity, configuration or if service is down.

On Service sent error event: Failed to

login to server



Applicable to GW Host.

Check connectivity, configuration or if service is down.

DatabaseConnect

Off Service sent info event:

Successfully connected to the DB

NA NA


Page 35 of 37


On Failed to execute test query on

database

Error connecting to Database Applicable to SQL Server.

Check database is on, start if needed.

On Test query performed on the DB

returned with wrong results

Database is connected

-Monitoring SQL Schema failure

Applicable to SQL Server.

Call support.

Configuration Off Connectivity test succeeded Connectivity test succeeded Connectivity test succeeded

On Missing configuration Applicable to Auto Task Server, Escalation Server,

Scheduler, Triggers Server and GW host.

On Failed to configure remote server

Operation On Invalid definitions(warning) Definition invalid - some

intended functionality is lost

Applicable to BPM Service.

Fix invalid BPM rules definitions.

On Failed to retrieve next task - can't

reschedule timer

Some functionality loss Applicable to Scheduler.

Call support.

SQL Jobs Off The SQL job '{0}' succeeded. The

SQL job was invoked by Schedule.

The last step to run was step: {1}

NA NA


Page 36 of 37


On The SQL job '{0}' failed The SQL

job was invoked by Schedule. The

last step to run was step: {1}

SQL job failed Check job failure reason.

On The SQL job '{0}' failed The SQL

job was invoked by Schedule. The

last step to run was step: {1}

SQL job failed Check job failure reason.

Table 7-8: Operational Application Server Component Loss

Component Possible Function Lost

VisionHub Operational Service Critical VisionHub functionality loss and login.

VisionHub Notification Service No update on new incidents, status changes, events.

VisionHub Auto Task Server No automatic task as part of procedures.

VisionHub Triggers Server No trigger execution on tasks.

VisionHub Scheduler No action scheduling.

VisionHub Escalation Server No escalation for incidents and tasks.


Page 37 of 37

Component Possible Function Lost

VisionHub Sensor Service No state change/command update for sensors.

VisionHub Automation Service Similar to above auto task, trigger, scheduler, and

escalation.

VisionHub BPM Service No rules evaluation and execution.

SQL Server Critical VisionHub functionality loss and login.

SQL Server Jobs SQL retention and performance.

VisionHub Web API Critical VisionHub functionality loss and login.

VisionHub Sensor Gateway Host Service No access to gateway integration (sensor status and

alarm state).