Tag :: Syslog

This feature adds the support for a standby server to the existing syslog logging mechanism for UDP syslog servers. The user can specify a logging group and specify remote syslog servers. The first host configured will be the “active” server, which means syslogs will be forwarded to that host whenever it is reachable via ICMP. The second host will be the “standby” server, which will receive syslogs if the active server goes down. This provides more robustness for setups with multiple potential syslog servers.

The syslog export feature allows users to export audit logs to external server endpoints and monitor the status of these exports using CloudVision.

Connectivity Monitor is an EOS feature that allows users to monitor their network resources from their Arista switches. The resources being monitored may or may not be Arista devices. Connectivity monitoring is unidirectional in nature.

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.

The software for Syslog, NTP and SNMP used in EOS resolves hostnames at service start-up. It’s possible that during service operation, the configured host becomes unavailable and the configuration needs to be set to a different host to continue the service. The problem is that such change requires manual restart of the service. Even if the hostname doesn’t change and only the underlying address is updated at the DNS server, the administrator has to manually reset service configuration.

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