[Fixed in 2.1.0] Syslog messages as diffs in Juniper backups

Unimus support forum
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Thu May 27, 2021 9:02 am

When looking at diffs for Juniper equipment backups, there are a lot of "false positive" diffs that consist of syslog messages to the device terminal. When logged in to a Juniper device, you can normally turn off syslog output to terminal by Esc-Q. Is it possible for Unimus to do this before issuing a "show configuration", to avoid these messages in the backup files?

Example from device backup:

1 Message from syslogd@test1 at Apr 11 02:12:36 ...
2 -
3 -
test1 inetd[1319]: /usr/sbin/sshd[95543]: exited, status 255
4 -
5 1set version...
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Fri Jun 11, 2021 7:33 am

Is there any possibility to look into this for a future version? It makes finding actual config diffs very difficult.
User avatar
Tomas
Posts: 1121
Joined: Sat Jun 25, 2016 12:33 pm

Mon Jun 28, 2021 4:19 pm

Just an update: we have added handling for this to our JunOS driver. This will be available in 2.1.0 stable release. Before backup, a "monitor stop" command will be sent (this is the same as ESC+Q). Since this is a per-session setting, the device will not be affected in any way.

You can also deal with this using the new Backup Filters: https://unimus.net/blog/backup-filters-unimus-210. These are available in the 2.1 Betas already if you want to test this.
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Tue Jun 29, 2021 6:12 am

That's great!
Thanks for taking the time to look at this.
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Wed Feb 16, 2022 6:34 am

Hi again,

Sorry to wake up an old thread, but it seems that "monitor stop" does not work exactly the same as "esc-q". I still get log output in backups, and for devices with a lot of terminal syslog output, discoveries and/or backups will fail intermittently. Is there a possibility to send an actual "esc-q" before attempting discovery/backup? I have debug device logs for failed backups (INTERACTION_ERROR), if needed.

Edit: I'm on 2.2.0-Beta3
Vik@Unimus
Posts: 143
Joined: Thu Aug 05, 2021 6:35 pm

Wed Feb 16, 2022 2:03 pm

Hello,

It is on of our developer's queue and I will update you when I get more information.
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Tue Jun 07, 2022 10:41 am

Hi,

Is there any news on this topic? I get quite a few devices that fail their backups intermittently, due to terminal syslog output disturbing the discovery/backup process.
Vik@Unimus
Posts: 143
Joined: Thu Aug 05, 2021 6:35 pm

Tue Jun 07, 2022 11:43 am

Hello,

We don't have an update for this particular issue yet, but I reckon this will be a part of the next major version 2.3.0. That one is planned for Q3 '22, but I expect this could go out before in one of prior beta releases.

As always, as soon as this gets out I will update this thread.
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Tue Jun 07, 2022 11:44 am

Hi again,

Thank for the quick reply, nice to know it's being worked on!
User avatar
Tomas
Posts: 1121
Joined: Sat Jun 25, 2016 12:33 pm

Tue Jun 07, 2022 12:48 pm

ptorbjornsson wrote:
Tue Jun 07, 2022 11:44 am
Hi again,

Thank for the quick reply, nice to know it's being worked on!
Edit: please see later post for updates

As a small update - the "ESC+Q" handling is currently implemented. Could you please test if that doesn't stop logging on your device (just log in to the device manually and sent ESC+Q).

From all the JunOS manuals we read, "ESC+Q" should be the same as "monitor stop".
Post Reply