Supported Platforms
Related Documentation
- ACX, EX, M, MX, SRX, T Series
- How Macros Work
- ACX, EX, M, MX, PTX, SRX, T Series
- Creating a Macro to Read the Custom Syntax and Generate Related Configuration Statements
- ACX, M, MX, PTX, T Series
- Example: Creating Custom Configuration Syntax with Macros
Overview of Creating Custom Configuration Syntax with Macros
Using commit script macros, you can create a custom configuration language based on simplified syntax that is relevant to your network design. This means you can use your own aliases for frequently used configuration statements.
Commit scripts generally impose restrictions on the Junos OS configuration and automatically correct configuration mistakes when they occur (as discussed in Overview of Generating Persistent or Transient Configuration Changes). However, macros are useful for an entirely different reason. Commit scripts that contain macros do not generally correct configuration mistakes, nor do they necessarily restrict configuration. Instead, they provide a way to simplify and speed configuration tasks, thereby preventing mistakes from occurring at all.
For a detailed example of how macros can save time and effort, see Example: Automatically Configuring Logical Interfaces and IP Addresses.
Related Documentation
- ACX, EX, M, MX, SRX, T Series
- How Macros Work
- ACX, EX, M, MX, PTX, SRX, T Series
- Creating a Macro to Read the Custom Syntax and Generate Related Configuration Statements
- ACX, M, MX, PTX, T Series
- Example: Creating Custom Configuration Syntax with Macros
Published: 2013-03-05
Supported Platforms
Related Documentation
- ACX, EX, M, MX, SRX, T Series
- How Macros Work
- ACX, EX, M, MX, PTX, SRX, T Series
- Creating a Macro to Read the Custom Syntax and Generate Related Configuration Statements
- ACX, M, MX, PTX, T Series
- Example: Creating Custom Configuration Syntax with Macros
