Subject: [netmod] syslog-model-05: terminal logging vs session logging

From: "Sterne, Jason (Jason)" <[email-masked]>
Date: Wed, 28 Oct 2015 18:50:32 +0000

Hi all,

One of the syslog destinations in the model is the "terminal" (for all users or specific users).

Isn't logging to a terminal more typically enabled on a CLI *session* basis rather than configured against a particular user ?

I believe it is also typical for session logging to stop/disappear when that session is ended (i.e. it is not persistent config).

I'm not sure it is typical to have configuration in a device that basically instructs the device to enable logging to the terminal for "user x" whenever that user later logs in (and if they had multiple login sessions then presumably log events would be delivered to each session).

I think session logging is something that is really purely CLI (i.e. interactive sessions with human users) and maybe not even applicable to configuration via NETCONF (since we'd never want to send a stream of syslog events as text to the NETCONF client/session like we do to the terminal for a CLI user).

In section 5 of the draft it mentions that syslog:log-actions/terminal maps to Cisco NXOS "logging monitor 2".  I believe that is intended to enable logs to a particular *session* (not user).   IOS-XR behavior is similar.  The ALU SR OS logging config has the concept of sending (enabling) log events to a particular session (but not configured against a user).

Jason