Make the loss / delay sim available as an output feature - vpp

diff options

author	Dave Barach <dave@barachs.net>	2019-04-03 11:20:06 -0400
committer	Florin Coras <florin.coras@gmail.com>	2019-04-11 01:19:56 +0000
commit	7c91007e1e13b56a29236bd076891709eaa21754 (patch)
tree	e6d78635a3b53f6db4b0bfa563d98254c464da6f /test/vpp_igmp.py
parent	10dc2eabd6e8a266405aef270a819794a3ddd333 (diff)

Make the loss / delay sim available as an output feature

Add binary api and debug cli support. Rewrite for speed: enqueue vlib_buffer_t's to the wheel, instead of memcpy'ing data. Quad-loop the output feature / x-connect (interior) node. Prefetch wheel entries in the input node. Save packet-generator-based unit-test setup in extras/nsim. Simple config example: set nsim delay 20 ms bandwidth 1 gbit packet-size 1024 nsim output-feature enable-disable GigabitEthernet3/0/0 Change-Id: I852a32d4eb596e7e2aa1d9b30bf3b53525e39fd1 Signed-off-by: Dave Barach <dave@barachs.net>c

Diffstat (limited to 'test/vpp_igmp.py')

0 files changed, 0 insertions, 0 deletions

# Syslog protocol support {#syslog_doc} VPP provides [RFC5424](https://tools.ietf.org/html/rfc5424) syslog protocol logging, which is used to transport event messages across network. VPP currently suports UDP transport based on [RFC5426](https://tools.ietf.org/html/rfc5426). The syslog message has the following format: * header * structured data * free-form message The header contains, priority, version, timestamp, hostname, application, process id and message id. It is followed by structured data, which provides a mechanism to express event data in easily parsable format. Structured data can contain zero, one or multiple structured data elements. Structured data element contains name-value pairs. Structured data can by followed by free-form message. Following example explains how to use the internal APIs to genrate syslog message: ```{.c} #include <vnet/syslog/syslog.h> ... syslog_msg_t syslog_msg; /* Check if syslog logging is enabled */ if (!syslog_is_enabled ()) return; /* Severity filer test */ if (syslog_severity_filter_block (severity)) return; /* Initialize syslog message header */ syslog_msg_init (&syslog_msg, facility, severity, "NAT", "SADD"); /* Create structured data element */ syslog_msg_sd_init (&syslog_msg, "nsess"); /* Add structured data element parameters (name-value pairs) */ syslog_msg_add_sd_param (&syslog_msg, "SSUBIX", "%d", ssubix); syslog_msg_add_sd_param (&syslog_msg, "SVLAN", "%d", svlan); syslog_msg_add_sd_param (&syslog_msg, "IATYP", "IPv4"); syslog_msg_add_sd_param (&syslog_msg, "ISADDR", "%U", format_ip4_address, isaddr); syslog_msg_add_sd_param (&syslog_msg, "ISPORT", "%d", isport); syslog_msg_add_sd_param (&syslog_msg, "XATYP", "IPv4"); syslog_msg_add_sd_param (&syslog_msg, "XSADDR", "%U", format_ip4_address, xsaddr); syslog_msg_add_sd_param (&syslog_msg, "XSPORT", "%d", xsport); syslog_msg_add_sd_param (&syslog_msg, "PROTO", "%d", proto); /* Send syslog message */ syslog_msg_send (&syslog_msg); ``` Example above produces following syslog message: <134>1 2018-11-12T11:25:30.252715Z 172.16.4.1 NAT 5901 SADD [nsess SSUBIX="0" SVLAN="0" IATYP="IPv4" ISADDR="172.16.1.2" ISPORT="6303" XATYP="IPv4" XSADDR="10.0.0.3" XSPORT="16253" PROTO="6"] To add free-form message use: ```{.c} syslog_msg_add_msg (&syslog_msg, "event log entry"); ```


context:
space:
mode: