hey,
Or just use "load replace https://nms/irr.junos; && commit with new file
having:
groups {
replace: IRR {
...
}
}
--
tarko
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
❦ 13 August 2021 11:44 +03, Saku Ytti via juniper-nsp:
> You could have something like this:
>
> groups {
> IRR {
> ...
>}
> }
>
> Then always generate complete new prefix lists in NMS into a single file.
>
> And have script do:
>
> edit groups
> delete IRR
> load merge
You could have something like this:
groups {
IRR {
...
}
}
Then always generate complete new prefix lists in NMS into a single file.
And have script do:
edit groups
delete IRR
load merge https://nms/irr.junos
commit and-quit
On Thu, 12 Aug 2021 at 21:47, Alain Hebert via
I've done this with perl scripts and the Juniper NETCONF libraries. I
make the changes inside a configuration group which is inherited into
the actual prefix-list(s), then lock down the account so it is only
able to make changes to that configuration group.
groups {
AUTO-PREFIX-LIST {
Context
I'm looking for a *simple* & safe way to manage daily IRR changes
from my customers...
Right now its a simple script that push changes using command lines
thru SSH...
While it is working adequately, I wonder how long it will be
feasible =D with the current growth.
5 matches
Mail list logo
