Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.3. UDP
The ip.buffer is unique in that it allows collection of UDP data. Some devices, such as the
Cisco Call Manager Express, send local data using the syslog protocol. The ip.buffer can
collect this syslog data and treat it as normal data.
Allow
“blank” = any incoming UDP source
To restrict to one device (or a list), enter a name, IP address, or
wildcarded IP address
[blank]
UDP Port
The UDP/IP port number.
1813 or 1646 = RADIUS accounting collection.
514 = syslog service.
162 = SNMP trap collection
[2001]
,
[2002]
, etc
Packet
“
ASCII + CR/LF
” – takes the UDP packet and only stores
readable characters. Appends a carriage return & line
feed.
“
Length (LSB/MSB) + Binary
” – stores a two byte length in
little endian format, and then the binary packet data.
“
Binary
” – stores just the pure, untouched, UDP packet data.
[ASCII + CR/LF]
There are special considerations for the specific ports 514 (syslog) and 162 (SNMP trap).
10.3.1. Syslog Collection
Set the port to 514 (syslog). You can only select the UDP packet type of “ASCII + CR/LF”.
10.3.2. SNMP Trap Collection
Set the port to 162 (SNMP trap). The “Packet” mode decides what is stored:
●
“ASCII+CR/LF” - the SNMP trap is decoded into a single ASCII line and stored
Internally the data is presented as ASCII data with 1 CR/LF. The decoded string
includes the IP address of the sending device.
●
“Length (LSB/MSB) + Binary” - the trap is stored as it was received with a length
prefix.
●
“Binary” - the trap is stored as it was received.
Additionally, a section appears for SNMP trap collection:
12
e.g. “192.168.0.*, device.scannex.com, 192.168.*”. Wildcards are “*” for anything, and “?” for
any single character.
13
Prior to v1.63.48 only the binary modes were available for SNMP trap storage.
Page 66
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.3. UDP
The ip.buffer is unique in that it allows collection of UDP data. Some devices, such as the
Cisco Call Manager Express, send local data using the syslog protocol. The ip.buffer can
collect this syslog data and treat it as normal data.
Allow
“blank” = any incoming UDP source
To restrict to one device (or a list), enter a name, IP address, or
wildcarded IP address
[blank]
UDP Port
The UDP/IP port number.
1813 or 1646 = RADIUS accounting collection.
514 = syslog service.
162 = SNMP trap collection
[2001]
,
[2002]
, etc
Packet
“
ASCII + CR/LF
” – takes the UDP packet and only stores
readable characters. Appends a carriage return & line
feed.
“
Length (LSB/MSB) + Binary
” – stores a two byte length in
little endian format, and then the binary packet data.
“
Binary
” – stores just the pure, untouched, UDP packet data.
[ASCII + CR/LF]
There are special considerations for the specific ports 514 (syslog) and 162 (SNMP trap).
10.3.1. Syslog Collection
Set the port to 514 (syslog). You can only select the UDP packet type of “ASCII + CR/LF”.
10.3.2. SNMP Trap Collection
Set the port to 162 (SNMP trap). The “Packet” mode decides what is stored:
●
“ASCII+CR/LF” - the SNMP trap is decoded into a single ASCII line and stored
Internally the data is presented as ASCII data with 1 CR/LF. The decoded string
includes the IP address of the sending device.
●
“Length (LSB/MSB) + Binary” - the trap is stored as it was received with a length
prefix.
●
“Binary” - the trap is stored as it was received.
Additionally, a section appears for SNMP trap collection:
12
e.g. “192.168.0.*, device.scannex.com, 192.168.*”. Wildcards are “*” for anything, and “?” for
any single character.
13
Prior to v1.63.48 only the binary modes were available for SNMP trap storage.
Page 66
