extensions
Syntax
extensions {
extension-service {
application {
file script-name {
arguments arguments;
cert-file path;
checksum hash-algorithm hash-value;
daemonize;
interpreter (bash | python | python3);
optional; refresh;
refresh-from;
routing-instance;
source;
start {
start-options {
mem-factor percentage;
}
}
traceoptions {
file <filename> <files number> <match regex> <size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
username username;
}
max-datasize max-datasize;
start {
start-options {
mem-factor percentage;
}
}
traceoptions {
file <filename> <files number> <size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
}
}
providers {
provider-id {
license-type license deployment-scope [ deployments ];
}
}
}
Hierarchy Level
[edit system]
Description
Configure extensions to Junos OS.
You must configure the providers statement to enable application packages developed using the
Junos SDK to be deployed and run on the router.
You must configure the extension-service statement to
enable application packages developed using the Juniper Extension
Toolkit (JET) to be deployed and run on the device.
The remaining statements are explained separately. See CLI Explorer.
This configuration is optional in Junos OS Evolved. You can run JET applications directly using a Python interpreter instead of configuring and invoking them in the CLI.
Required Privilege Level
admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 9.0.
extension-service option introduced in Junos OS Release
16.1.