Additional Services are loaded in complement of the LoriotPro resources and default services. They are not linked to Directory objects like other Plugin. They are use to provide extended services to LoriotPro such as could be other Windows applications.

They are linked to the LoriotPro kernel therefore have no places in the Directory but in a dedicated tree. When you load a new Directory (A set of objects and a working environment) all current objects are removed but the service Plugin stay active.

Figure 12 : Arbre des plugins de services

The service tree and its options are described in other chapters of the manual. The WEB  server has been presented in a previous paragraph thus we describe hereafter only the functions and parameters of the Plugin.

Few examples of this Plugin types are provided by default, source codes are within the SDK.

Plugin : NetbiosNameResolve.sp

This Plugin finds out all Netbios name, the names used in Microsoft environment, by doing Netbios requests on the Directory host Objects.

This Plugin is a good example of use of the DSNMP Directory API within a service Plugin.

Figure 14 : Plugin NetbiosNameResolve.sp

      Warning

By using this Plugin, on demand links  (Dialup lines) could be involuntary opened.

Plugin : TraceRouteDiscover.sp

The TraceRouteDiscover Plugin discovers by means of ICMP protocol, the path between the LoriotPro hosts and any other host. The path contains the successive crossed router.

It allows the discovering of the network topology from its routing information table. It could be useful when SNMP is not available or implemented. The discovered information could be added to the Directory.

Figure 15 : Plugin TraceRouteDiscover.sp

Plugin : CHttp.sp

This service plugin provides the WEB server function integrated in LoriotPro. It supports advanced script function. Whitout this Plugin the remote access from a WEB Navigator to the LoriotPro console is impossible.

This Plugin is explained in detail in another chapter.

Figure 16 : Plugin CHttp.sp

Configuration

Table of parameters

Parameters	Functions
name	The name that should be use as SMTP sender
Address	Complementary information, Your E-mail for example. Warning Filling this field is obligatory
Server : Host name / Address	The IP address or the name of the SMTP server. Example  187.1.1.9 smtp.nodo-vide.com
Server : Port	The protocol port number used by the SMTP server. By default 25.
Scheduler : Timeout	The time between two sending.
Update Parameters	This button takes in account the new parameters each time you do a change.

Example

In the following example the file trapfilter.txt located in the /bin directory is configured to perform  the sending of an E-mail message to address ludo3@test.com when receiving a  SNMP LinkDown Trap.

File trapfilter.txt (extract)

Each time a trap of this type is received a new file is created in the

bin/smtp_out directory.

C         Remark

Refers to the chapter “Event management” to have more detailed explanations on the Trap management and about the syntax used in the trapfilter.txt file.

Figure 18 :  Répertoire smtp_out

The file created in the bin/smtp_out directory have a predefined structure:

Ø     The first line contains the EMAIL address.

Ø     The second line contains the parameters of the trapfilter.txt file.

File 1007835798.ludo@test.com.txt

The Plugin working in background mode will browse the directory at regular interval and send all waiting messages.

Plugin : LoriotNetFlowCollectorService.sp

Introduction

Cisco has developed within some of its equipment what they call the NetFlowCollector.

Netflow is a protocol use to collect on a “collector” traffic information from the devices.

This Plugin is able to receive NetFlow UDP packets of version 5 and thus works as a “collector”

All gathered information by this way could be stored in the ODBC Database if this one is configured.

This Plugin is a good example of use of the ODBC API provided within the SDK.

Figure 19 : Plugin LoriotNetFlowCollectorService.sp

Configuration

This Plugin is configured from the menu  with the Properties option or directly by clicking on the properties button in the main window.

Table of parameter

Parameters	Functions
UDP Recept Port	The UDP port is configured in the Cisco equipment (here 9999) Example: If your LoriotPro has the address 10.33.10.130 The Cisco configuration would be ip flow-cache entries 1024 ip flow-cache feature-accelerate ! interface Ethernet0  ip address 10.33.10.121 255.255.0.0  ip route-cache flow ! ip flow-export version 5 ip flow-export destination 10.33.10.130 9999
http Server URL	The URL to use for displaying the records of the database. A PHP script is provided as example in the www/www directory. bin\www\www\l_netflowmenu.html
Create loriot_netflow table	Remark Normally the Database tables are created when configuring the ODBC access. This option is here to provide examples on the API ODBC utilization within a Plugin Example MySQL : CREATE TABLE loriot_netflow (   number int(4) unsigned NOT NULL auto_increment,   timestamp int(4) unsigned NOT NULL DEFAULT '0' ,   sysuptime int(4) unsigned ,   version int(1) unsigned ,   host_id int(4) unsigned NOT NULL DEFAULT '0' ,   engine_type int(1) unsigned ,   engine_id int(1) unsigned ,   ip_src char(15) ,   ip_dst char(15) ,   srcaddr int(4) unsigned ,   dstaddr int(4) unsigned ,   nexthop int(4) unsigned ,   input int(2) unsigned ,   output int(2) unsigned ,   dPkts int(4) unsigned ,   dOctets int(4) unsigned ,   first int(4) unsigned ,   last int(4) unsigned ,   srcport int(2) unsigned ,   dstport int(2) unsigned ,   tcp_flags int(1) unsigned ,   prot int(1) unsigned ,   tos int(1) unsigned ,   dst_as int(2) unsigned ,   src_as int(2) unsigned ,   dst_mask int(1) unsigned ,   src_mask int(1) unsigned ,   flow_sequence int(4) unsigned ,   UNIQUE number (number,host_id,srcaddr,dstaddr,nexthop) );

The Analyze button starts the WEB navigator by default and displays the URL previously set.

Figure 20 : Using a PHP script

C         Remark

This Plugin supports the status color concept in the service tree.

In the screen shot above the NetFlow Collector service is green therefore operational.