SLAX and XSLT Commit Script Tag Elements to Use When Generating Messages
Junos OS commit scripts can generate custom warning, error, or system log messages during a commit operation to alert you when the configuration does not comply with custom configuration rules. Table 1 summarizes the tag elements that you can include in a custom warning, error, or system log message in SLAX and XSLT commit scripts. For examples, see Example: Generating a Custom Warning Message, Example: Generating a Custom Error Message, and Example: Generating a Custom System Log Message.
Table 1: Tags and Attributes for Creating Custom Warning, Error, and System Log Messages
Data Item, XML Element, or Attribute | Required or Supported | Description |
---|---|---|
Container Tags and Attributes | ||
| Required for system log messages | Indicates that a system log message is going to be recorded. |
| Required for error messages | Indicates that the server has encountered a problem while processing the client application’s request. |
| Required for warning messages | Indicates that the server has encountered a problem while processing the client application’s request. |
| Supported in warning and error messages | Names the XML namespace for the contents of the tag element.
The value is a URL of the form |
| Required for warning and error messages. The | Names the XML namespace for child tag elements that have
the |
Content Tags | ||
| Supported in warning and error messages only | Identifies the element that caused the error by specifying
its position as the number of characters after the first character
in the line specified by the |
| Supported in error messages only | Provides information about the users currently editing the configuration. |
| Supported in warning and error messages only | Specifies the level in the configuration hierarchy where
the problem occurred, using the CLI configuration mode banner. We
recommend combining the |
| Supported in warning and error messages only | Names the configuration file that was being loaded. |
| Supported in warning and error messages only | Specifies the line number where the error occurred in
the configuration file that was being loaded, which is named by the |
| Required in warning, error, and system log messages | Describes the warning, error, or system log message in a natural-language text string. |
| Supported in error messages only | Indicates that there was a syntactic error in the request submitted by the client application. |
| Supported in warning and error messages only | Describes the reason for the warning or error message. |
| Supported in warning and error messages only | Names the Routing Engine on which the process named by the |
| Supported in warning and error messages only | Names the Junos OS module that was processing the request in which the warning or error message occurred. |
| Supported in warning and error messages only | Specifies the configuration statement in effect when
the problem occurred. We recommend combining the |
| Supported in warning and error messages only | Names the element in the request that caused the warning or error message. |
| Supported in warning and error messages only | Emits an If the problem is not at the current position in the XML hierarchy,
you can alter the edit path by passing the |
| Supported in warning and error messages only | Emits a If the problem is not at the current position in the XML hierarchy,
you can alter the statement by passing the |