Failover Server: Configuration

Transcription

1 SeMSy III is a high-performance and future-proof video management system with optimum user friendliness. It offers a comprehensive range of functions, including the display of live images, various search options within the footage, the control of PTZ cameras and easy archiving of relevant sequences. The SeMSy III Failover Server Software is a failover (hot standby) for network-based Dallmeier recording systems. The software permanently monitors the availability of all recording systems in the SeMSy III video management system. When the recording of a system is interrupted (fail of the device, loss of the network connection, HDD or RAID failure), the Failover Server switches all streams for the recording on the defined spare recording system. A failover server is configured and controlled via the configuration file config.xml. This allows to adjust setup options (e.g. connection settings, manual failover etc.). Use the config.xml file in an appropriate editor (such as Visual Studio Code or Notepad ++) to edit the XML elements and attributes in the configuration file. The configuration file is stored on a failover server in the following directory: C:\ProgramData\Dallmeier\Failover\FailoverMngr Open the config.xml file from the corresponding directory in an editor: Overview of Element Nodes in config.xml : Element david logfile history infoservice database config confighistory pguardinterface manualfailover pool areacodes Description Settings for various timeouts and keep-alive intervals, for example for restoring connections or triggering delays for failover actions Setting the number and size of logging files Element is no longer used Activation of the status information that can be evaluated via the FailoverManagerClient Setting connection attempts to the server database File directory and retention period for old configuration files File directory for old configuration files Activation of the PGuard interface for sending messages in the event of failover events Activation of the function for manually triggering failover activities Entering the pool IDs for which the failover manager is to be responsible Entering the area code for which the failover manager is responsible; in addition, the address of the PGuard server for messages for failover activities can be entered here Click on the respective element to display further information.

2 Element Reference This handout describes the default settings of a config.xml file for a failover system. Customize the default values to suit your requirements. Save the config.xml file with the changed settings. Elements are displayed in blue; corresponding attributes in red. david Node: propertydownloadinterval Interval (in hours) for downloading the configuration data of the main recording systems. In the event of failover, these configurations are transferred to the corresponding spare recording systems. <propertydownloadinterval hint= Interval in hours - Default 12 value= 12 /> keepaliveinterval Interval (in seconds) in which keep-alive queries are sent to recording devices. <keepaliveinterval hint= Interval in seconds - Default 30 value= 30 /> reconnectonkeepalivetimeout A new connection attempt after a keep-alive timeout before a failover event is triggered. <reconnectonkeepalivetimeout hint= Re-connect to device after KeepAlive timeout - Default 1 value= 1 /> Permissible values: 1 = function enabled; 0 = function disabled reconnectinterval Interval (in seconds) after which an attempt is made to reconnect to a recording system. <reconnectinterval hint= Re-connect interval - Default 5 seconds value= 5 /> reconnectattempt If the connection to a recording system is rejected during recovery, the failover event is only triggered after the number of attempts entered here. <reconnectattempt hint= Re-connect attempts - Default 0 value= 0 /> connecttimeout Timeout (in seconds) for connecting to recording systems. <connecttimeout hint= Connect timeout - Default 4 seconds value= 4 /> Commanddelay Element is no longer used. <commanddelay hint= Delay between two commands in miliseconds - Default 200 miliseconds - Max 5000 value= 200 />

3 tcpkeepalivetime Timeout (in milliseconds) for keep-alive requests from TCP/IP socket interfaces after which a failover event is triggered. <tcpkeepalivetime hint= TCP/IP Socket KeepAlive Timeout - Default 5000 miliseconds - 0 = Off - Max value= 5000 /> tcpkeepaliveinterval Interval (in milliseconds) in which keep-alive requests are sent to TCP/IP sockets. <tcpkeepaliveinterval hint= TCP/IP Socket KeepAlive Interval - Default 250 miliseconds - Max 1000 value= 250 /> reconnectoverlappingdelay After re-establishing the connection to a main device, the failover event is only cleared after the time period (in seconds) specified here to ensure that the recording on the main device has been resumed. <reconnectoverlappingdelay hint= Delay (in seconds) between re-connect and end of Failover - Default 120 value= 120 /> startupdelay Failover events are only triggered after the time period set here (in seconds) after the FailoverManager has been started. This can prevent incorrect events that are only caused by high load at startup. <startupdelay hint= Delay (in seconds) between startup and first Failover event - Default 0 value= 0 /> logfile Node maxparts The maximum number of log files that can be stored for evaluations can be defined here. <maxparts hint= Maximum number of log files - Default 10 value= 10 /> maxpartsize The maximum size of a log file can be defined. <maxpartsize hint= Maximum log file size in KB - Default 5120 value= 5120 /> debugdavid If actions and events of the DaVid interface are to be logged, this can be activated here. <debugdavid hint= Log DaVid communication - Default 0 value= 0 /> Permissible values: 1 = function enabled; 0 = function disabled host This element contains the address of the server to be logged. <host value= localhost />

4 port This element contains the required communication port. <port value= 3434 /> infoservice Node enabled Enable the web service to display status information in the FailoverManagerClient. <enabled hint= REST webservice for status information - Default = true value= true /> Permissible values: true = web service enabled; false = web service disabled port Port number for status web service. <port hint= HTTP port - Default 8080 value= 8080 /> database Node re-connect Setting the number of connection attempts to the failover database until a timeout occurs. This prevents client connections from being overloaded during a failover event by a series of connection attempts in quick succession. <re-connect hint= Number of connect retries - Default 10 value= 10 /> config Node folder Specifies the directory in which configuration files of the recording systems managed by the failover system are stored. <folder hint= Folder for local configuration and device configuration value= /> Example: <folder... value= C:\ProgramData\Dallmeier\Failover\FailoverMngr\Config /> history The configuration files of the recording systems are stored in the directory specified under the element propertydownloadinterval and stored in the folder defined above. The function here now makes it possible to save the file history of the configurations and to delete the files only after a certain time again. The enabled element activates the file history and lifetime specifies the retention period (in days). <enabled hint= Use history for device configuration value= true /> Permissible values: 1 = function enabled; 0 = function disabled <lifetime hint= Maximum lifetime in days - Default 90 value= 90 />

5 confighistory Node folder If the file history for configuration files has been activated, a folder for the files can be set up here. <folder hint= Folder for history value= /> Example: <folder... value= C:\ProgramData\Dallmeier\Failover\FailoverMngr\Config\History /> pguardinterface Node The PGuardInterface allows failover events to be sent as PGuard messages to specific recipients. Please note that the PGuardInterface software must be installed separately (installation file available from Dallmeier support). This function can be activated in this node. The corresponding PGuard7 server is defined in the node areacodes (see section areacodes Node). enabled Activation of the PGuard function for failover events. <enabled value= false /> Permissible values: true = function enabled; false = function disabeld host Specifies the host computer on which the PGuardInterface software is installed. <host value= localhost /> port The port number required for communication with the PGuard interface host. The default setting does not normally need to be changed. <port value= 8181 /> subalarmid The subalarm ID is required for camera-related PGuard messages. The default setting does not normally need to be changed. <subalarmid value= 1001 />

6 manualfailover Node In the FailoverManagerClient a failover for a recording system can also be triggered manually. This function can be activated here. In addition, a new password can be set up, which has to be entered in the event of a manual failover. enabled In this element, the manual failover function can be activated or deactivated. <enabled hint= Allow manual Failover value= true /> Permissible values: true = function enabled; false = function disabeld password Password protection is enabled by default (default password: failover12345). The password is stored here in encrypted form and can be changed (see below). <password hint= Manual Failover password value= D B BA- 00F A1163C53E83D07DFE0BE F9BCE2B2E7DF9FA4AA F60A673 /> Proceed as described here to change the password: Enter the new password in plain text as value and also the encrypt attribute. Example: <password hint= Manual Failover password value= newpassword encrypt= true /> Save and close the config.xml file. Then start the FailoverManagerClient. The new password is encrypted and activated for manual failover. pool Node pool A failover server can monitor multiple pools of recording systems. These pool IDs, for which the failover server is to be responsible, has to be entered here. <pool hint= Pool 1 value= /> areacodes Node The areacodes node is displayed in the config.xml file if the required system areas were previously activated in the FileManagerClient application via the menu (File > SeMSy Area > select required area codes). In addition, the IP address of the PGuard7 server can be entered in the area element (see also the section pguardinterface Node). area The area codes are automatically displayed here if they have been activated via the FailoverManagerClient as described above. The address of a PGuard7 server is entered with the pguard attribute. <area hint= 1 value= 1 pguard= />