The statements are organized alphabetically.
control-cores control-number;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
control-number—Number of control cores. At least one core must be a control core.
data-cores data-number;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
data-number—Number of data cores. Although it is not mandatory to dedicate any cores as data cores, it is advisable, depending on the nature of the application, to dedicate a minimum of five as data cores to achieve good performance.
data-flow-affinity {
hash-key (layer-3 | layer-4);
}
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
The statements are explained separately.
extension-provider
destination destination;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider syslog facility severity]
/var/log directory on the Routing Engine. Enhancements to the existing infrastructure make debugging on the Multiservices PIC easier by giving the user the option of redirecting log messages. When the syslog destination statement is configured to redirect the log messages, you can use the set system syslog command, a command available in the native JUNOS Software CLI, to override the syslog settings made on the Multiservices PIC.destination—Choose one of the following options:
routing-engine—Forward log messages to the Routing Engine.pic-console—Forward log messages to the console of the PIC.
extension-provider {
control-cores control-number;
data-cores data-number;
data-flow-affinity {
hash-key (layer-3 | layer-4);
}
forwarding-db-size size;
object-cache-size value;
package package-name;
policy-db-size size;
syslog {
facility {
severity;
description description;
}
}
wired-process-mem-size size;
}
[edit chassis fpc slot-number pic slot-number adaptive-services service-package]
extension-provider is first configured, the PIC will reboot.The statements are explained separately.
extension-service service-name {
provider-defined rules;
[edit services service-set service-set-name], [edit forwarding-options sampling output]
extension-service statement is specified, the service-order statement is mandatory.provider-defined rules—Subhierarchy for services created by the provider.
service-name—Name of service.
service-order
extensions {
providers {
provider-id;
}
resource-limits {
package package-name {
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
}
process process-ui-name {
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
}
}
)
[edit system]providers provider-id statement to enable SDK application packages to be deployed and run on the router.The statements are explained separately.
forwarding-db-size size;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
forwarding-options sampling statement for the FDB to be created.size—Size of the FDB, in MB. The size of the FDB and the policy database together must be less than the size of object cache.
hash-key (layer-3 | layer-4);
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
data-flow-affinity statement is enabled, you may need to choose the hashing distribution. Modifying this statement will cause the PIC to reboot.layer-4 layer-3—3-tuple hashing (source IP address, destination IP address, and IP protocol).
layer-4—5-tuple hashing (3-tuple plus source and destination TCP or UDP ports). This is the default.
<<<<<<< .mine
license-type license deployment-scope [ deployments ];
[edit system extensions providers providers-id]
license—Type of license. Obtain correct value from the application’s provider.
deployment—Scope of license’s deployment. You can configure a set of deployment scopes. Obtain correct value from the application’s provider.
||||||| .r373337 =======
license-type license deployment-scope [ deployments ];
[edit system extensions providers providers-id]
license—Type of license. Obtain correct value from the application’s provider.
deployment—Scope of license’s deployment. You can configure a set of deployment scopes. Obtain correct value from the application’s provider.
>>>>>>> .r374513
object-cache-size value;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
value—Amount of object cache, in MB. Only values in increments of 128 MB are allowed. wired-process-mem-size of 512 MB, the maximum value of object-cache-size is 128 MB. wired-process-mem-size of 512 MB, the maximum value of object-cache-size is 512 MB.
package package-name;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
package-name—Name of the package to be loaded on the PIC. There can be up to eight packages loaded on a PIC; however, only one data package is allowed per PIC. An error message is displayed if more than eight packages are specified.
package package-name {
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
}
[edit system extensions resource-limits]
package-name—Name of the JUNOS SDK application package.The statements are explained separately.
policy-db-size size;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
size—Size of the policy database, in MB. The size of the FDB and the policy database together must be less than the size of object cache.
process process-ui-name {
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
}
[edit system extensions resource-limits]
process-ui-name—Name of the process.The remaining statements are explained separately.
process-monitor {
disable;
traceoptions {
file filename files number match regex size size (world-readable | no-world-readable);
flag flag;
level level;
no-remote-trace;
}
}[edit system processes]disable— Disable process health monitor process.The remaining statements are explained separately.
traceoptions (Process Monitor)
providers {
provider-id {
license-type license deployment-scope [ deployments ];
}
}
[edit system extensions]
provider-id—Provider ID for the SDK application package. The provider ID identifies the provider of the application to the system. The provider ID must be activated on the router to allow the SDK application to be deployed on the router and run.The remaining statements are explained separately.
resource-cleanup {
disable;
traceoptions {
file filename files number match regex size size (world-readable | no-world-readable);
flag flag;
level level;
no-remote-trace;
}
}
[edit system processes]traceoptions is the only CLI statement for resource-cleanup.disable—Disable resource cleanup process.The remaining statements are explained separately.
traceoptions (Resource Cleanup)
resource-limits {
package package-name {
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
}
process process-ui-name {
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
}
}
[edit system extensions]The statements are explained separately.
resources {
cpu {
priority number;
time seconds;
}
file {
core-size bytes;
open number;
size bytes;
}
memory {
data-size bytes;
locked-in bytes;
resident-set-size bytes;
socket-buffers bytes;
stack-size bytes;
}
}
[edit system extensions resource-limits package package-name], [edit system extensions resource-limits process process-ui-name]
bytes—Maximum size of each file, in kilobytes (KB) or megabytes (MB).
cpu—CPU resources.
priority number—Highest priority number (nice level) at which the process can run.time seconds—Maximum amount of CPU time that can be accumulated.file—File system resources.
core-size bytes—Maximum size of a core file that can be created.open number—Maximum number of simultaneous open files.size bytes—Maximum size of a file that can be created.memory—Memory resources.
data-size bytes—Maximum size of the data segment.locked-in bytes—Maximum number of bytes that can be locked into memory.resident-set-size bytes—Maximum amount of private or shared memory at any given moment.socket-buffers bytes—Maximum amount of physical memory that may be dedicated to the socket buffers.stack-size bytes—Maximum size of the stack segment.process
service-order {
forward-flow [ service-name1 service-name2 ];
reverse-flow [ service-name1 service-name2 ];
}
[edit services service-set service-set-name]
service-order statement must include all services defined in the service set.
extension-service statement is specified, the service-order statement is mandatory.forward-flow—Order of services in service set to be applied in forward flow. It is mandatory to specify the forward-flow service order.
reverse-flow—Order of services in service set to be applied in reverse flow. If you want the order to be the reverse of that specified for forward flow, this is optional. But if, for example, you want the order to be the same regardless of direction of flow, you need to include this statement. (The exception to this is for the sampling service set type. If a service set is a sampling service set and the reverse-flow service order is not configured, all sampled traffic is considered to be forward traffic.)
extension-service
syslog {
facility {
severity;
destination destination;
}
}
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
daemon and kernel (for facility) introduced in JUNOS Release 9.5./var/log directory.facility—Group of messages that are either generated by the same software process or concern a similar condition or activity. Possible values:
daemon—Various system processes.external—Local external applications.kernel—PIC kernel.pfe—Packet Forwarding Engine.severity—Classification of effect on functioning. Possible values are the same as for the native JUNOS software. See the JUNOS System Basics Configuration Guide. Possible values include the following:
any—Include all severity levels.none—Disable logging of the associated facility to a destinationemergency—System panic or other condition that causes the routing platform to stop functioning.alert—Conditions that require immediate correction, such as a corrupted system database.critical—Critical conditions, such as hard errors.error—Error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels.warning—Conditions that warrant monitoring.notice—Conditions that are not errors but might warrant special handling.info—Events or nonerror conditions of interest.extension-provider
traceoptions {
file filename files number match regex size size (world-readable | no-world-readable);
flag flag;
level level;
no-remote-trace;
}[edit system processes process-monitor]file—Information you want to specify about the trace file or files. See the JUNOS System Basics Configuration Guide for information about configuring this file information.
flag flag—Area of the process health monitor for which you want to enable tracing. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
all—Enable tracing in all areas.heartbeat—Trace heartbeat updates.process-tracking—Trace process life-cycle events and parent-child pedigree changes.ui—Trace user interface operations.level level—Level of debugging output:
all—Match all levels.error—Match error conditions.info—Match informational messages.notice—Match conditions that should be handled specially.verbose—Match verbose messages.warning—Match warning messages.match regex—(Optional) Refine the output to include lines that contain the regular expression.
no-remote-trace—Disable remote tracing.
size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum file size, you also must specify a maximum number of trace files with the files number option.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB
world-readable | no-world-readable—(Optional). Grant all users permission to read log files, or restrict the permission only to the root user and users who have the JUNOS maintenance permission.
process-monitor
traceoptions {
file filename files number match regex size size (world-readable | no-world-readable);
flag flag;
level level;
no-remote-trace;
}
[edit system processes resource-cleanup]file—Information you want to specify about the trace file or files. See the JUNOS System Basics Configuration Guide for information about configuring this file information.
flag—Specify which tracing operation to perform. To specify more than one tracing operation, include multiple flag statements. You can include the following flags:
all—Enable all trace options flags.events—Trace process state change and cleanup events.gencfg—Trace GENCFG blobs recorded for cleanup.module—Trace module code.sysvsem—Trace SYSV semaphores recorded for cleanup.sysvshm—Trace SYSV shared memory segments recorded for cleanup.tracking—Trace tracking code.ui—Trace user interface operations.match regex—(Optional) Refine the output to include lines that contain the regular expression.
no-remote-trace—Disable remote tracing.
size size—(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum file size, you also must specify a maximum number of trace files with the files number option.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB
world-readable | no-world-readable—(Optional). Grant all users permission to read log files, or restrict the permission only to the root user and users who have the JUNOS maintenance permission.
wired-process-mem-size size;
[edit chassis fpc slot-number pic slot-number adaptive-services service-package extension-provider]
mem-size—Size of the reserved wired process memory, in MB. The only size you can set for this statement is 512 MB.
Guidelines for Configuring SDK Applications