JunoScripts
Post script on 50 lines, of course, is ridiculous, but considering that this script on SLAX, I hope that does not laugh. Because users JunOS in my view much more than those who wrote the scripts. Well, writing / debugging much more difficult than perl or bash (at least for I).
In general, the script - displays "show bgp sum" in a slightly different format and with additional information. Format - one row for each feast (after raising the usual IPv6 "Show bgp sum" began painting peers in two lines, because of what did not work to use " 100, respectively, it is desirable to have the same terminal lines were longer than 80 characters. Maybe someone will prove useful. script .
script should be put in / var / db / scripts / op / and config register "set system scripts op file show-bgp-sum.slax", after which the team will work "op show-bgp-sum".
UPD:
ver 0.2 - Process groups inheritance, support route-instances (replaced the first version of this)
ver 0.2.1 - Show advertised prefix count - Cougar 20100513
ver 0.2.2 - Added local interface name
ver 0.3 - Get additional info by "show bgp group", not from config (based on 0.2.1)
ver 0.3.1 - Add local interface information
If information about local interfaces do not need, version 0.3.1 and 0.2.2 use makes no sense, it is better instead to take 0.3 or 0.2. 1.
Versions 0.3 and 0.3.1 do not require human reader configuration by the user. Accordingly, work out correctly uses of commit-scripts. But it does not show information about the route-instance (only bgp group).
Versions 0.2.1 and 0.2.2 works a little slower than 0.2, because make an additional request (get-bgp-neighbor).
version 0.3.1 are a bit slower than the 0.3 for the same reason.
What is faster - 0.2.x or 0.3.x - to the different cases differently.
Choose the most suitable variant for you. :) Personally, I myself have been using 0.2.2 with the ejected out the work with bgp instances (for acceleration, I do not use).
0 comments:
Post a Comment