Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
It already does the job it needs to do, so it will keep on doing it. 01 version 1.1; 02 03 ns junos = "http://xml.juniper.net/junos/*/junos"; 04 ns xnm = "http://xml.juniper.net/xnm/1.1/xnm"; 05 ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0"; 06 07 import "../import/junos.xsl"; 08 09 match configuration ( 10 /* Insert code here */ 11 ) As you can see, the only actual change is a shift in the version number from 1.0 to 1.1
Use the check-ldp Script to Enforce LDP-IGP Consistency For SLAX version 1.0 and higher, you can use the check-ldp script to enforce enforce LDP - IGP consistency
This page also compares/contrasts the SLAX 1.1 boilerplate against the SLAX 1.0 boilerplate
You can also compare and contrast this boilerplate with the boilerplate for SLAX 1.0
This applies to SLAX version 1.0 and higher
This applies to SLAX version 1.0 and higher...version 1.0; ns junos = "http://xml.juniper.net/junos/*/junos"; ns xnm = "http://xml.juniper.net/xnm/1.1/xnm"; ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0"; import "
Configure Any Interface with 'Core' in Description with MTU Length For SLAX version 1.0 and higher, you can use this commit script to check that any interface with "CORE" or "core" in the description is configured with an MTU of 4484 (in this example)