Tag :: Logging

This feature allows the logging of packets matching deny rules in ingress ACLs applied on subinterfaces. This behavior can be enabled by using the log keyword when configuring an ACL deny rule. A copy of the packet matching those ACL rules is sent to the control plane, where a syslog entry of the packet header is being generated.

This document describes how to prefix syslog messages with a custom string value. Previously, syslog messages were constrained to being prefixed with either the device’s hostname, IPv4 address or fully qualified domain name. This can be controlled with the command “logging format hostname ( fqdn | ipv4 )”. Support has now been added for prefixing the syslog messages with a custom comment. This provides users with greater freedom when deciding the format of their syslog messages including those which are sent to syslog servers.

This feature allows generating the syslog message for the packets matching rules in egress ACLs. This can be enabled using the log keyword when configuring an ACL rule. A copy of the packet matching such an ACL rule is sent to the control plane, where a syslog entry for the packet header is generated.

The EOS Event Manager feature, introduced in 4.17.0F,  provides the ability to specify a condition and an action

This feature allows the logging of the packets matching rules in ingress ACLs. This behavior can be enabled by using the log keyword when configuring an ACL rule. A copy of the packet matching those ACL rules is sent to the control plane, where a syslog entry of the packet header is being generated.

This feature adds the support for tracking the number of syslog messages sent to the server and the number of syslog messages received on the server, along with other log forwarding action statistics, continuously within the existing syslog logging mechanism.

This feature adds TLS support to the existing syslog logging mechanism. With the new added CLI commands, the user can