ANNOUNCE: EVL4EZ Syslog Client

Information and support for EnvisaLink modules.

Moderators: GrandWizard, EyezOnRich

C'est Moi
Posts: 2
Joined: Sat Feb 15, 2020 11:35 pm

Re: ANNOUNCE: EVL4EZ Syslog Client | RPi Raspbian Considerations

Postby C'est Moi » Sun Feb 16, 2020 12:15 am

Configuring EVL4's Syslog Client under Raspbian ("V10 Buster" Linux 4.19.97-V7+) using either a Chromium (V78) or Iceweasel (i.e. Firefox V68) browser proved to be problematic. The webpage presented by EVL4's embedded web-server was not rendered correctly in either browser and therefore it was not possible to update the requisite fields (i.e. Syslog server's IP address and the Facility ID) on the form and post them correctly to the EVL4.

However, on a different PC, attached to the same network subnet, but running Ubuntu 18.04.1 LTS ("Bionic Beaver") and a Chrome V80 browser, the EVL4's console webpage was displayed correctly and it was then possible to input, post and successfully update the requisite Syslog Server information.

After changing /etc/rsyslog.conf and restarting rsyslogd, as described at https://vexxhost.com/resources/tutorial ... 14-04-lts/, and rebooting the EVL4 hardware, ENVISALINK messages then magically appeared in /var/log/messages on the RPi 2B box, running Raspbian "Buster".

Here are the pertinent configuration file settings that I'm using for the syslog daemon and logrotate process, the latter to keep /var/log svelte with a minimum of old log clutter and with minimum grind on my RPi 2B machine.

/etc/rsyslogd.conf
# provides UDP syslog reception
module(load="imudp")
input(type="imudp" port="514")
# provides TCP syslog reception
module(load="imtcp")
input(type="imtcp" port="514")

/etc/logrotate.conf
# keep this many sets of backlogs
rotate 1
#truncate the original logfile after copying it
copytruncate
# decide whether you want old log files compressed or not
nocompress
Last edited by C'est Moi on Tue Feb 18, 2020 1:40 pm, edited 2 times in total.

C'est Moi
Posts: 2
Joined: Sat Feb 15, 2020 11:35 pm

Re: ANNOUNCE: EVL4EZ Syslog Client | CID Structure ?

Postby C'est Moi » Sun Feb 16, 2020 2:00 pm

What is the structure of the CID (Contact IDs) in syslog messages? They do not seem to follow the Ademco CID field structure (Q EEE GG ZZZ) as documented in the Vista 20P Programming Guide (document K5305-1 PRV8 5/11 Rev. C) that I've got.

Please see an actual syslog (/var/log/messages) example (partially masked for security reasons), as written by an EVL4 (Firmware Version: 01.03.155A):

Feb 15 17:59:37 192.168.xxx.xxx ENVISALINK[Mac Address]: CID Event: 1131010080

Is this the sub-field structure?

1-131-01-0080 1 = New Message ? ; 131 = Alarm Perimeter ? ; partition 01 ? ; zone number 008 ? ; spurious digit ?

GrandWizard
Posts: 1980
Joined: Tue Nov 16, 2010 4:08 pm

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby GrandWizard » Mon Feb 17, 2020 1:45 pm

Yes that is correct.

vinistois
Posts: 2
Joined: Sun Apr 26, 2020 5:21 pm

Re: ANNOUNCE: EVL4EZ Syslog Client

Postby vinistois » Sun Apr 26, 2020 5:27 pm

what I did to get around the local subnet limitation is fire up a vm in the same subnet as the evl-4

I used centos8 minimal. rsyslog is installed by default. Uncomment the lines to in /etc/rsyslog.conf to enable upd on 514.

Then I forward to papertrail where more actions, including notifications to all kinds of web platforms, webhooks, etc.

Another option would be a node-red instance, there is a syslog listener module in node-red where you could configure your own actions.


Return to “EnvisaLink ( IP100D, IP170D, 2DS, 3, 4)”

Who is online

Users browsing this forum: No registered users and 12 guests