Mike,
I'd be very interested in the particulars of your issues.
What sorts of boot-time issues are you seeing? I'm not sure what
you mean by "leaves the configs visible identical". Do you have a
PR or support case already open?
FWIW, you might be better off doing the "commit to git" script as
I would not use that commit script if I were you, and I wrote it.
We don't anymore.
On single devices it might be OK but we use a lot of J/SRX clusters and all
sort of nastiness occurs when they reboot.
JUNOS issues a commit during boot, it's easy to blindly accept it in the
commit script but it
On 11/11/14 8:16 am, "Stefan Cioata" wrote:
>
>c) I would like to implement git. That will require at minimum to have
>the
>user on the ".gz transferred file.
You can have an event script triggered by UI_COMMIT_COMPLETE and the
script can get you this info.
Thanks,
Pallavi
_
We use an in-house script that checks the archive directory and if there
are new files then:
1) it logs in to a juniper host via ssh
2) asks for "show system commit" (the only command it can issue)
3) gets username and comments for previous commits
4) pushes everything new to git, adding username/
Hello everyone,
The only partial reference to my problem that I found on the net was posted
by:
Author Message
Mike Williams
PostPosted: Thu Mar 20, 2014 1:50 pmPost subject: configuration
archival, commit comments
Here is my challenge:
a) I use system archival
stefan@stefan_test_deskto
I managed to find an hour or so today to look at this further.
A commit script is the result. My very first!
match configuration {
var $comment = $junos-context/commit-context/commit-comment;
if( jcs:empty ($comment)) {
{
"No comment speci
On 03/20/2014 09:50 AM, Mike Williams wrote:
Hi all,
Random thought for the day.
You can archive the entire config after each commit (archival configuration
transfer-on-commit).
You can apply a comment to each commit (# commit comment "blah")
How do you archive that comment?
/var/db/commi
Hi all,
Random thought for the day.
You can archive the entire config after each commit (archival configuration
transfer-on-commit).
You can apply a comment to each commit (# commit comment "blah")
How do you archive that comment?
It's not included in the config.
Thanks
--
Mike Williams
__
8 matches
Mail list logo
