close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow Junos Automation Scripts Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
play_arrow Automation Scripting Using XSLT
- play_arrow XSLT Overview
- play_arrow Standard XPath and XSLT Functions Used in Automation Scripts
- play_arrow Standard XSLT Elements and Attributes Used in Automation Scripts
play_arrow Automation Scripting Using SLAX
- play_arrow SLAX Overview
- play_arrow SLAX Statements
- play_arrow The libslax Distribution for Automation Scripting
play_arrow Automation Scripting Using Python
- play_arrow Python Overview
play_arrow Automation Script Input
- play_arrow Global Parameters in Automation Scripts
  - Global Parameters and Variables in Junos OS Automation Scripts
play_arrow Extension Functions and Named Templates for Automation Scripts
play_arrow Manage Automation Scripts
- play_arrow Store and Enable Scripts
- play_arrow Configure a Remote Source for Scripts
- play_arrow Configure the Session Protocol for Scripts
  - Understanding the Session Protocol in Automation Scripts
  - Example: Specify the Session Protocol for a Connection within Scripts
- play_arrow Control Execution of Scripts
- play_arrow Synchronize Scripts Between Routing Engines
- play_arrow Convert Scripts Between SLAX and XSLT
  - Convert Scripts Between SLAX and XSLT
play_arrow Commit Scripts
- play_arrow Commit Scripts Overview
  - Commit Script Overview
  - How Commit Scripts Work
- play_arrow Create and Execute Commit Scripts
- play_arrow Generate a Custom Warning, Error, or System Log Message Using Commit Scripts
- play_arrow Generate Persistent or Transient Configuration Changes Using Commit Scripts
- play_arrow Create Custom Configuration Syntax with Commit Script Macros
- play_arrow Commit Script Examples
- play_arrow Junos XML and XSLT Tag Elements Used in Commit Scripts
- play_arrow Troubleshoot Commit Scripts
play_arrow Op Scripts
- play_arrow Op Scripts Overview
  - Op Script Overview
  - How Op Scripts Work
- play_arrow Create and Execute Op Scripts
- play_arrow Op Script Examples
- play_arrow Provision Services Using Service Template Automation
  - Service Template Automation Overview
  - Example: Configure Service Template Automation
- play_arrow Troubleshoot Op Scripts
  - Trace Op Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Event Policies and Event Scripts
play_arrow SNMP Scripts
- play_arrow SNMP Scripts Overview
  - SNMP Scripts Overview
- play_arrow Create and Execute SNMP Scripts
- play_arrow SNMP Script Example
  - Example: Process Unsupported OIDs with an SNMP Script
- play_arrow Troubleshoot SNMP Scripts
  - Trace SNMP Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

number

date_range 13-Feb-21

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
number expression {
    format numbering-style;
    grouping-separator character;
    grouping-size number;
}


number {
    count nodes;
    format numbering-style;
    from nodes;
    grouping-separator character;
    grouping-size number;
    level "single" | "multiple" | "any";
}

Description

Generate a formatted number string, which is output to the result tree. When used with an argument, the statement formats the number given by that XPath expression. When used without an argument, the statement uses the count, from, and level options to generate the number based on the position of one or more nodes within the current XML document. In both cases, optional statements specify the formatting for that number. If needed, you can also redirect the formatted number string to a variable or output method instead of the result tree.

Attributes

number expression

XPath expression providing the number to format.

count nodes

XPath expression specifying which nodes should be counted. If count is omitted, it defaults to nodes with the same name as the current node.

format numbering-style

A string, variable, or XPath expression that defines the number formatting.

The format option can include the following:

start string–Any non-alphanumeric characters that precede the first number token in the format string. The start string is prepended to the formatted number string.
number token–One or more number tokens that indicate what numbering format to use for the included numbers. The formatted number string only includes more than one number if the level option is set to “multiple”. Table 1 lists format values and corresponding styles. The default value is “1”, which uses a decimal format style. When using decimal format, you can specify the minimum length of the formatted number string by preceding the “1” with one or more zeros.
token separator–Non-alphanumeric characters that separate number tokens in the format string. These characters are included in the formatted number string between the computed numbers.
end string–Any non-alphanumeric characters that follow the last number token in the format string. The end string is appended to the formatted number string.

Table 1: Numbering Styles for SLAX Statement number, format Option
Format Value	Style	Example
1	Decimal format	1 2 3 ...10 11 ...
01	Decimal format with a minimum output string length of 2	01 02 03 ... 10 11 ...
001	Decimal format with a minimum output string length of 3	001 002 003 ... 010 011 012 ... 100, 101
a	Lowercase alphabetic numbering	a b c ... z ... aa ab ... az ... ba bb ...
A	Uppercase alphabetic numbering	A B C ... Z ... AA AB ... BA BB ...
i	Lowercase Roman numbering	i ii iii iv v ...
I	Uppercase Roman numbering	I II III IV V ...

from nodes

XPath expression specifying from which element to start the count. When level is set to single or multiple, this option constrains the counting to only node descendants of the nearest ancestor that matches the expression. When level is set to any, this option constrains the counting to only nodes that follow the nearest ancestor or preceding node of the current node that matches the expression.

grouping-separator character

Character used to delimit groups of digits for numbers expressed in decimal format. For example, decimal notation uses a comma as the delimiter between digit groupings.

grouping-size number

Defines the number of digits in a group for numbers expressed in decimal format. Setting this option causes the formatted number to be split into multiple groups according to the grouping size, with the grouping separator delimiting the groups. For example, decimal notation often uses a grouping size of 3.

level

Specifies what type of counting to perform. Accepted values are single, multiple, and any. The default is single. Specifying single starts the counting from the first ancestor node, specifying multiple starts the counting from any ancestor node, and specifying any starts the counting from any node.

single–Perform only one count. The current node, if it matches the count expression, or the nearest ancestor that matches the count expression, is counted. The position of the node in document order, relative to its siblings that also match the count parameter, is used as the number to be formatted.
multiple–Separately count all nodes that match the count expression and are either the current node or an ancestor of the current node. The position of each node in document order, relative to its siblings that also match the count parameter, is used as one of the numbers to be formatted.
any–Perform only one count. The current node, if it matches the count pattern, or its nearest ancestor or preceding node that matches the count pattern, is counted. The position of the node in document order, relative to all other matching nodes that are ancestors or precede the node, is used as the number to be formatted.

Note:

Currently libxslt (1.1.26) does not support the “language” and “letter-value” options for the <xsl:number> element. While SLAX provides a means of encoding these XSLT constructs, they cannot be used in Junos OS.

SLAX Example

The following sample code iterates from 1 through 5. For each integer, the number statement outputs the equivalent uppercase Roman numeral value.

content_copy zoom_out_map
  for $i (1 ... 5) {
    number $i {
      format "I ";
    }
  }

content_copy zoom_out_map
I II III IV V 

The following sample code provides the string “1234567890” to the number statement, which formats the output in decimal format with a group size of 3 and a comma as a group delimiter.

content_copy zoom_out_map
number "1234567890" {
    grouping-size 3;
    grouping-separator ",";
    format "1"; 
}  

content_copy zoom_out_map
1,234,567,890

The following sample code counts all the name elements in the configuration hierarchy stored in the variable $data. The count option combined with the level "multiple" option tracks the count for any name elements under the interface, unit, and address elements.

The format option (1.A.a) includes a start string, which is an open parenthesis, and an end string, which is a close parenthesis and a space character. The number tokens are “1”, “A”, and “a”, which define the formatting of the numbers as decimal format, uppercase alphabetic numbering, and lowercase alphabetic numbering, respectively. The token separator is a period, which is also included in the output.

content_copy zoom_out_map
var $data := {
  <interfaces> {
      <interface> {
          <name> "ge-0/0/0";
          <unit> {
              <name> "0"; 
          }                  
          <unit> {
              <name> "1";
          } 
     }      
      <interface> {
          <name> "ge-0/1/0";
          <unit> {
              <name> "10";
              <family> {
                  <inet>;
              }
          }                  
      }    
      <interface> {
          <name> "ge-2/0/2";
          <unit> {
              <name> "0";
              <family> {
                  <inet> {
                      <address> {
                          <name> "10.1.1.1/24";
                      }
                  }
              }
          }  
      } 
  }
}

for-each ($data//name) {
    number {
      level "multiple";
      count interface|unit|address;
      format "(1.A.a) ";
    }
    expr . _ "\n";
}

For the generated numbers displayed in the result tree, the decimal number in parentheses is associated with a particular interface. For each interface, the uppercase letter is associated with each logical unit name, and any lowercase letter is associated with the address name element for that logical unit, which is the IP address.

content_copy zoom_out_map
(1) ge-0/0/0
(1.A) 0
(1.B) 1
(2) ge-0/1/0
(2.A) 10
(3) ge-2/0/2
(3.A) 0
(3.A.a) 10.1.1.1/24

Release Information

Statement introduced in version 1.1 of the SLAX language, which is supported in Junos OS Release 12.2 and later releases.

arrow_backward PREVIOUS mvar

NEXT arrow_forward output-method

Automation Scripting User Guide

ON THIS PAGE

number

Syntax

Description

Attributes

SLAX Example

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Automation Scripting User Guide

ON THIS PAGE

number

Syntax

Description

Attributes

SLAX Example

Release Information

Related Documentation

Stay in touch