CMS v8 Administrator Guide
Aventura CMS Manual
Administrator Guide
Version 8
Rev. 10/1/2011
© 2011 Aventura
Aventura CMS Manual
© 2011 Aventura
All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or
mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the
written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks of the
respective owners. The publisher and the author make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the author assume no
responsibility for errors or omissions, or for damages resulting from the use of information contained in this document
or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be
liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or
indirectly by this document.
Printed: October 2011
Contents
I
Table of Contents
Part I
Introduction
2
................................................................................................................................................. 3
Overview
................................................................................................................................................. 4
Components
.................................................................................................................................................
5
System
Requirements
Part II
Getting Started
7
................................................................................................................................................. 8
Installation
.................................................................................................................................................
9
System
Settings
Part III
Configuration & Use
11
.................................................................................................................................................
11
Event
Monitoring
........................................................................................................................................13
Export
Archive........................................................................................................................................13
Mail To........................................................................................................................................14
........................................................................................................................................15
Acknowledge
........................................................................................................................................15
Add Note
........................................................................................................................................16
Properties
Find ........................................................................................................................................17
........................................................................................................................................18
Settings
19
User.................................................................................................................................................
& Group Management
................................................................................................................................................. 21
Levels
................................................................................................................................................. 23
Devices
................................................................................................................................................. 25
Email
.................................................................................................................................................
27
Matrix
& Display
.................................................................................................................................................
29
Camera
Aggregation
Part IV Appendix
31
.................................................................................................................................................
31
Important
Port Numbers
................................................................................................................................................. 32
Glossary
© 2011 Aventura
Part
I
Introduction
2
Introduction
Aventura Central Management Server (CMS) allows administrators to tie together multiple Aventura systems
for convenient centralized management and new enterprise-level features. Cameras from DVR Servers
connected with the CMS are aggregated so clients no longer need to manually connect to specific servers.
Global virtual matrix and display groups greatly reduce configuration time. Centralized user and group
management includes support for Microsoft Active Directory and gives administrators complete access control
for their systems in a single location.
© 2011 Aventura
3
Aventura CMS Manual
Overview
Control: Aventura CMS brings the centralized management capability of Enterprise-level I.T. systems to video
security applications.
Security: Extensive permissions management with the integrated user and group management tools.
Intelligence: Monitor events from all over the system from a single location.
Ease-of-Use: Global display groups & Emaps automatically deliver updates to all users logged into the system.
© 2011 Aventura
Introduction
4
Components
Aventura CMS consists of 4 primary components:
Event Monitoring
The main CMS window gives administrators an instant head-up look at the entire security system. User logins,
loss-of-video messages, changes to local settings and more are displayed in user-selectable color based on
event type and priority.
Users & Group Management
Complete access control with Microsoft Active Directory (not required) integration gives administrators the
power to instantly and easily manage permissions down to the camera-level and beyond.
Centralized Configuration Options
Create and manage global virtual matrix settings, display groups, and Emaps that will instantly become
available for new users to access or existing users to update to. Centralized configuration options make it easy
to roll out changes and enforce consistency throughout a system while also being an incredible time-saver.
Camera Aggregation
On systems with two or more DVR Servers without a CMS it can be confusing for users to find a specific camera.
Aventura CMS aggregates cameras from all connected servers and delivers one list to client machines, so
operators can find the camera they're looking for right away every time.
© 2011 Aventura
5
Aventura CMS Manual
System Requirements
Aventura Central Management Server (CMS)
Aventura Central Management Server (CMS) is designed for use only on Aventura Servers. Modifications to the
operating system, installation, removal or reconfiguration of software (other than as outlined in this manual),
or modifying any hardware components of an Aventura Server (e.g. RAM, Hard Drives, CPU, etc) may result in
CMS malfunction and invalidate any existing warranty.
Aventura CMS Client Software
Minimum System Requirements:
Intel Core2 Duo 2.93 GHz Processor
1 GB RAM
ATI Radeon 4350 Video Card
Windows 7 Professional (32 or 64 bit)
Minimum System Recommendation:
Intel Core2 Quad 2.5 GHz Processor
2 GB RAM
ATI Radeon 4350 Video Card
Windows 7 Professional (32 or 64 bit)
© 2011 Aventura
Part
II
7
Aventura CMS Manual
Getting Started
Aventura CMS comes pre-installed and configured, so clients and servers can begin connecting to the CMS right
out of the box, but there are many benefits CMS can provide which administrators will wish to customize. All
interaction with the CMS is conducted using the Aventura CMS Client Software.
© 2011 Aventura
Getting Started
8
Installation
Aventura CMS Client Software is provided on CD or through FTP with every Aventura CMS system. Running the
installer is extremely simple as there are no configuration options. Follow the on-screen instructions until the
installation is complete, then run the software using the start menu or desktop shortcut provided.
If the software prompts for a login, press cancel and then click the Settings button in the top-right portion of
the window. Once the settings window is open, click System on the left-hand side to view the system settings.
Once a CMS server has been added and an administrator has logged in, the client software can be used to
configure the system.
© 2011 Aventura
9
Aventura CMS Manual
System Settings
Before configuring the CMS the client software must be configured to connect to it. Clicking Add... at the
bottom of the window will bring up a dialog box asking for the CMS connection information. Administrators
must enter the IP address, connection port, and name for the CMS they are connecting to. Once this
connecting is established, administrators will be able to log into the CMS through the client software and begin
customizing the configuration.
Systems using Microsoft Active Directory should check the Active Directory box on the top-right and fill out the
necessary information to connect to the Active Directory server.
© 2011 Aventura
Part
III
11
Aventura CMS Manual
Configuration & Use
Event Monitoring
Aventura CMS gives administrators the ability to see what is happening on their system with a single glance at
any given moment. The main window displays events from all machines connected to the CMS. Events logged
include informational notifications, such as a user entering a setup screen, as well as system warnings and
errors that can indicate potential problems.
Alarm ID
This is a sequential number assigned to each alarm when it occurs. Each alarm has a unique ID so it can be
identified and referenced later on.
Level
Alarms can be assigned a specific icon and color in the Level section of the Settings window. This allows
administrators to quickly identify different types of information with a quick look and prioritize the most
important events first.
Occurred At
Time at which an event was logged.
Device
Name of the server, client, or camera where the event originated.
User
The user who generated the event. Events not generated by a user are marked "System".
© 2011 Aventura
Configuration & Use
12
Description
Verbose description of the event.
Attachment
Administrators can attach files (such as video snapshots) to events. If an event has an existing attachment it
will be listed in this column.
Acknowledged By
The name of the administrator who acknowledged the event.
Acknowledged At
The time the event was acknowledged.
Note: To sort by a column, simply click the name of the column. An arrow will appear next to the column name,
indicating whether the column is being sorted in ascending or descending order. Clicking the name of the
column again will reverse the sort order.
© 2011 Aventura
13
Aventura CMS Manual
Export
Clicking the Export button brings up a standard dialog box administrators can use to select a file save name and
location. The exported file is saved in a Comma Separated Value (CSV) format and can be opened with most
spreadsheet applications. The exported file will contain all of the active (not-yet archived) events in the list.
Archive
Clicking the Archive button at the top of the main window brings up the Archive screen. Archiving events
allows administrators to move older or unimportant events out of the main event manager window. Events
are archived automatically by age, but the number of days before automatically archived can be set by the
administrator. Administrators also have the option to manually archive all acknowledged events, or all events
in the current selection.
© 2011 Aventura
Configuration & Use
14
Mail To
By clicking the Mail To button at the top of the main window administrators can generate an email alert.
Recipients are chosen by clicking the Recipients button and selecting from the list of users. By default the
email alert will contain information pertaining to the currently selected event(s). Email content and subject
can be customized before sending.
Note: Sender Options in the Email Settings window must be configured in order for the CMS to send email
alerts.
© 2011 Aventura
15
Aventura CMS Manual
Acknowledge
Clicking Acknowledge while an event is selected will bring up the acknowledgement window. Administrators
can optionally include a comment when flagging an event as acknowledged.
Add Note
Administrators can attach notes and comments to an event by clicking the Add Note button at the top of the
event manager window while an event is selected. Notes will be included in the event properties along with
the administrator and time each note was made. This can be useful for passing information between shifts for
events that are in-progress or have not yet been resolved.
© 2011 Aventura
Configuration & Use
16
Properties
An event's properties can be viewed by double-clicking on the event itself or by clicking the Properties button
at the top of the event manager window while an event is highlighted. This displays all of the information
visible in the event manager window as well as additional information. Administrators can view any notes or
attachments added to the event as well as having the option to click Add to include additional notes or
attachments. Notes and attachments are displayed on separate tabs, selected by clicking the appropriately
named tab (located below the event description). Events can also be acknowledged on the properties screen
by clicking the Acknowledge button located at the bottom of the window.
© 2011 Aventura
17
Aventura CMS Manual
Find
The event finder is a very powerful tool that can be accessed through the Find button at the top of the event
manager window. The event finder allows administrators to search for events based on event level, event
device, even user, even time, or events containing specific keywords. The ability to include only active or
archived events can be used for even more specific searches.
© 2011 Aventura
Configuration & Use
18
Settings
Emap File
The Aventura Emap module is included with all Aventura VMS and CWS machines. Using this module, a topdown view of a security network can be created. Once designed, an Emap can be exported for use with
Aventura CMS. Clicking the button next to the Emap FIle text-box will allow administrators to browse to an
exported Emap file and select it. The Emap selected here will then be made available to all machines
connected to the CMS.
Active Directory
Aventura CMS supports integration with Microsoft Active Directory. If the CMS is located on a Microsoft
Windows network with an Active Directory Server the CMS can be configured to connect to it and use the
Users and Groups defined in Active Directory for authentication within the security system.
CMS Connections
Add, edit or delete connections to Central Management Servers (CMS) in the Connections portion of the
window. The CMS Client must be connected and logged into a CMS server in order to view or modify event
logs, users, groups, and other system settings.
© 2011 Aventura
19
Aventura CMS Manual
User & Group Management
User and Group management are accomplished through the "Users" and "Group" settings windows
respectively. These screens provide a straightforward way to manage access to the devices connected to the
CMS. There are two authentication themes available for use by administrators who wish to enforce security
policy. The optional configurations are:
CMS User/Group Management: All users on the system authenticate through the CMS and administrators can
add/edit/delete users and groups within the CMS interface.
CMS User/Group Management with Microsoft Active Directory integration: The CMS uses the existing Active
Directory users and groups to assign permissions. Users are able to use their Microsoft Windows login to
authenticate, and permissions are governed by the CMS. When Active Directory integration is enabled, only
user permissions can be modified within the CMS. All other modifications (password, group membership) is
accomplished through the standard Microsoft Active Directory interface.
© 2011 Aventura
Configuration & Use
20
Users
Users represent individuals who are authorized to access all or part of the security system within administratordefined limitations. They can be added/edited using the controls at the bottom of the Users window.
Groups
Groups represent collections of individuals who share the same access profile. They can be added/edited using
the controls at the bottom of the Groups window.
User/Group Permissions
Permissions can be individually assigned for each camera, with separate per-camera permissions for live
viewing, PTZ controls, playback, and video download/backup. Each settings menu can be individually allowed
or denied for specific users and groups, along with specific permissions for numerous other features.
Automatic Logout Timer
When password protection is enabled the administrator can optionally set an Auto Logout timer, which will
require a user to re-authenticate if they are inactive for the specified time period.
Maximum Login Attempts: Administrators can set a maximum number of failed login attempts before a user
account is automatically locked, preventing the user account from logging in even if the correct password is
subsequently entered. This offers additional security to prevent unauthorized access to a legitimate user's
account.
Lockout Timer: This determines how many minutes a user account will be automatically locked for if it exceeds
the defined number of failed login attempts. If desired, this can be set to "Disable Account", which requires
users who are locked out to contact an administrator to have their account re-enabled.
© 2011 Aventura
21
Aventura CMS Manual
Levels
The Levels screen allows administrators to add, edit, or delete event alert levels, colors and icon selects. This
can be especially useful for applications where some event types are significantly more important than others,
as it allows the user to spot relevant events quickly in the event manager window.
© 2011 Aventura
Configuration & Use
Administrator-Defined levels can be given unique colors, symbols, and sounds.
© 2011 Aventura
22
23
Aventura CMS Manual
Devices
© 2011 Aventura
Configuration & Use
24
Device Type Options
This section of the Devices window allows administrators to add, edit, or delete defined device types that will
be connecting to the CMS. Standard devices include machines running Aventura VMS, Aventura CWS, and
Aventura CMS Clients (Alarm Visualization), but additional device types can be supported.
Device Options
When a device connects to the CMS it is automatically listed here in this screen. Some devices, such as IP
cameras, must be added manually using the Add/Edit/Delete buttons at the bottom of the Device Options
window.
© 2011 Aventura
25
Aventura CMS Manual
Email
© 2011 Aventura
Configuration & Use
26
Sender Options
The email sender options must be configured in order for the CMS to send alert emails (both manual and
automatically generated). The fields must be filled out similar to any email client, with information provided by
the internet service provider or network administrator. Once entered, email settings can be tested to be sure
they are functioning properly using the button to the right.
Email Alert Options
Administrators can set up basic rules which can instruct the CMS to automatically generate alert emails under
specific circumstances. Emails can be generated based on alert levels and server name.
Note: Sender Options in the Email Settings window must be configured in order for the CMS to send email
alerts.
© 2011 Aventura
27
Aventura CMS Manual
Matrix & Display
Virtual Matrix and Display Groups defined in the Matrix & Display window become global groups that can be
accessed by machines running Aventura Client Workstation Software (CWS) that are connected to the CMS.
Individual user and group permissions still apply when camera connects are requested by the client. This
means users will only be able to view the camera feeds they have permissions to view, even if they attempt to
view a display group to cameras for which they lack permissions.
Matrix Options
The Virtual Matrix allows control over video sent to external monitors and requires the optional Matrix
Decoder Card to be installed in the system.
Display Options
Creating display groups is a way to customize the CWS Live View and create shortcuts to specific groups of
cameras and video window arrangements.
Configuring Matrix & Display Groups
Group: Select the group to modify or examine. Groups can be added or removed with the +/- buttons.
© 2011 Aventura
Configuration & Use
28
Group Name: Unique name for the group. This will be displayed in the Matrix & Display tab in the Live View.
Output Type: This setting is unique to the Virtual Matrix. Choose NTSC or PAL, dependant on the video
monitor being used to display the matrixed cameras.
Split Layout: The number of video windows for the selected view.
Selecting Cameras
Region Name / Window: This represents where the video from the selected camera will be displayed.
MatrixRegion1/Window1 represents the top-left video spot on the monitor. Regions/Windows are numbered
from left-to-right and begin from the left again once a new row of video is started. The precise placement
varies based on the video split layout selected.
Server: The connected device from which the desired video stream is being served.
Camera: Once a server is selected, a list of cameras on that server will become available. Select the desired
camera to add it to the group in this Matrix Region / Video Window.
© 2011 Aventura
29
Aventura CMS Manual
Camera Aggregation
Cameras connected to a VMS machine on the system are listed in the Cameras window on the Settings screen.
Each camera initially displays the name of the DVR server it is on and its identity on that server.
Administrators can then manually define other properties, such as a secondary backup server and the camera
number associated with an analog matrix. When a secondary server is defined for a camera, that secondary
camera is removed from the automatically generated list to avoid duplicates. Matrix ID numbers can be used
to call up cameras or playback footage on Client Workstation machines for users who may know the Matrix ID
but may not know the camera name.
Names are automatically filled in by the connected DVR servers, however this can be changed for uniqueness
or descriptive properties at the administrator's discretion.
© 2011 Aventura
Part
IV
31
Aventura CMS Manual
Appendix
Important Port Numbers
Aventura Systems use a number of ports for network communication. In order for the software to work
properly, network administrators may need to unblock or forward these ports to the appropriate machines.
Below are the various services and the default ports used for each.
Client Workstation Port: 5100
Used to connect to Live Video feeds on DVR Servers running Aventura VMS.
Playback Port: 8731
Used to connect to a the Playback Service on DVR Servers running Aventura VMS.
Event Manager Port: 5300
Used to connect to the Event Manager Service on DVR Servers running Aventura VMS.
CMS: 7600
Used to connect to an Aventura Central Management Server (CMS).
Web Browser Port: 8000
Used to serve live video and/or playback to browser-based plugins.
© 2011 Aventura
Appendix
32
Glossary
Bandwidth – The rate of data transfer supported by your network.
Baud rate – The speed at which information is sent over a line.
Bitmap – An uncompressed type of image file used to store digital pictures.
Bitrate – The amount of data used to make up an image or video. A higher bitrate will give better quality.
COM (Communication) Port – A serial port interface on a computer.
CPU (Central Processing Unit) – Computer chip that is used to run applications.
DVR (Digital Video Recorder) – System that runs the Aventura server software.
FPS (Frames Per Second) – The rate at which unique consecutive images are viewed/recorded.
GB (Gigabyte) – A computer storage unit (1,000,000,000 bytes). This is larger than a MB.
IP (Internet Protocol) Address – A numerical identification assigned to devices on a computer network.
JPEG – A compressed type of image file used to store digital pictures.
Kbps (Kilobits Per Second) – A data rate for network transmission (1,000 bits per second).
KB(Kilobyte) – A computer storage unit (1,000 bytes). This is smaller than a MB and GB.
LAN (Local Area Network) – A computer network covering a small area such as a home, office, or small group
of buildings.
MB (Megabyte) – A computer storage unit (1,000,000 bytes). This is larger than a KB, but smaller than a GB.
NTSC (National Television System Committee) – Video standard generally used in North America, north and
west parts of South America, Japan, South Korea, and Taiwan.
NVR (Network Video Recorder) – Software that allows viewing/recording of video from the DVR over the
LAN/WAN.
OSD (On Screen Display) – Text that appears over the camera video.
PAL (Phase Alternating Line) – Video standard generally used in Europe, Asia, and everywhere else not listed
under NTSC.
Port – A numerical identifier where communication takes place between network devices.
POS (Point of Sale) – Advanced system used for cash register monitoring.
© 2011 Aventura
33
Aventura CMS Manual
Protocol – A standard of communication.
PTZ (Pan/Tilt/Zoom) – Advanced camera that has the ability to turn left/right, up/down, and zoom in/out.
Resolution – The level of detail on an image.
SSL (Secure Sockets Layer) – A secure communication protocol for internet data.
SMTP (Simple Mail Transfer Protocol) Server – A type of server for sending outgoing emails.
WAN (Wide Area Network) – A computer network covering a broad area, generally referred to as the Internet.
© 2011 Aventura
180 Adams Avenue,
Hauppauge, NY 11788
Phone : (631) 300-4000
Fax: (631) 434-7000
www.aventuracctv.com
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement