SNMP Preference

Table of Contents

Overview
Configure

Overview

DVR and NT provide SNMP trap event transmission for the internal events. CMS can handle these SNMP trap events, translating it into general event information or forwarding it the other systems.

This feature is useful when it's impossible to keep host connections always, to execute Live Monitor, Remote Search (Search and Replay) or Local Recording by connecting to the host in case of event occurrence. For example:

  • Network rental fee depends on time rather than packet amount

  • You must monitor multiple hosts more than 100 ones simultaneously, which requires network traffic overload.

SNMP forwarding plays an role in transmitting events which are received via SNMP trap event to other CMS or SNMP manager programs. For example, in case of 1000 DVR hosts, one gateway CMS can disperse the events to others with 100 DVR hosts for each CMS

SNMP Preference

Figure 3.8. SNMP Preference


Configure

If you want to use SNMP trap server, you must check Enable SNMP trap server. To change the listen port, edit the content of Listen Port entry.

[Note] Linux Root Permission for Listen Port

You must have root permission to use SNMP trap server with default SNMP port 162 in Linux.

In order to forward received SNMP events to other SNMP trap servers, you must make the filters. By clicking Add new filter on the toolbar, you can add a new filter, and selected items will be removed if you click Delete selected filters button. Filters are applied in order until the condition matches the event. If you want to change the filter order, select the filter and click Up / Down buttons on the toolbar. You can decides whether the filter is enabled by toggling Enable checkbox.

A filter consists of Condition and Forwarding Servers, which transmit SNMP events to registered servers when it matches the condition.