Using AAA to log all commands from users on Arista EOS

Introduction Some users of Arista Networks EOS may want to log all commands executed on a switch. This article explains how to use AAA without TACACS or RADIUS to provide accounting of all commands to the system log. The log can then be sent off to a syslog server or even sent to Splunk using the Arista EOS splunk extension. For more information about the Splunk app for Arista EOS click here. Setup First, it is important to create a user account for each switch administrator. Without a separate account for each administrator it will be impossible to retain accurate...
Continue reading →

System and Process Logging

In addition to the log provided by the ‘show logging’ CLI command, EOS, being a linux based OS, provides users with the ability to access the underlying Linux system logs as well as the individual EOS agent process logs for multiple agent instances (due to reconfiguration or in-service stateful repair). These logs can be accessed via invoking the bash Linux shell directly via the EOS CLI as follows: Arista#bash sudo tail /var/log/messages Feb 17 20:01:01 Arista CROND[32288]: (root) CMD (run-parts /etc/cron.hourly) Feb 17 20:01:01 Arista run-parts(/etc/cron.hourly)[32288]: starting 0anacron Feb 17 20:01:01 Arista run-parts(/etc/cron.hourly)[32297]: finished 0anacron Feb 17 20:01:01 Arista run-parts(/etc/cron.hourly)[32288]:...
Continue reading →

Introduction to Managing EOS Devices – Setting up Management

Note: This article is part of the Introduction to Managing EOS Devices series:      1) Setting Up Management The following management tools are available on Arista EOS for all platforms: VRF-aware management Telnet and SSH Syslog and Console Logging SNMP Versions 1 and 3 NTP DNS Local and remote user control (AAA) TACACS+, RADIUS sFlow XMPP eAPI   Note: in the following configuration examples, the commands in square brackets are optional: [optional]   1.1) VRF Aware Management As of release 4.10.1, EOS supports the ability to constrain management functions to a VRF. This enables the user to separate management based functions...
Continue reading →

7150 EOS-4.12.8 not logging to syslog server

I have a 7150 Running EOS-4.12.8 – it’s not logging to itself or sending any logging information to my syslog server. When I do a show logging the only information that shows up is 10 lines from 11 days ago. I have  logging host x.x.x.x  in my config but my syslog server show nothing coming in from it at all. I have noticed on everything in my network running EOS-4.12.8. Am I missing something!?!

Reacting to syslog-triggered events

EOS in tandem with Python scripting can provide the network operator an invaluable tool that is driven by local log entries on the switch. The script presented here continuously monitors /var/log/messages for new entries as it contains verbose, unfiltered entries. The script then searches each log entry using the built-in Python regular expression module. When a matching entry is found (this script is looking for major errors) it saves the output of ‘show tech-support’ to internal flash. For every match, the script checks for the existence of a ‘show tech-support’ file to ensure it doesn’t create a duplicate entry for...
Continue reading →

How to generate syslog messages using Python

Arista EOS extensions can be easily configured to generate syslog messages. This documents provides an overview of the APIs which can be used in order to achieve that and shows a few examples. The examples presented in the following sections were tested against EOS-4.12.0. Basic example #!/usr/bin/env python # Copyright (c) 2013 Arista Networks, Inc. All rights reserved. # Arista Networks, Inc. Confidential and Proprietary. import syslog syslog.openlog( 'myTestLog', 0, syslog.LOG_LOCAL4 ) syslog.syslog( '%%TEST-6-LOG: Log msg: %s' % 'test msg' ) Result Apr 17 07:15:40 <hostname> myTestLog: %TEST-6-LOG: Log msg: test msg See the official Python documentation for more details.