app-engine

Syntax

app-engine {compute-cluster compute-cluster-name {compute-node compute-node-name {interfaces {bridge bridge-name {family inet {(address ip-address | dhcp);}interface bridge-interface-list;management;}ethernet ethernet-interface-name {enable-passthrough;family inet {(address ip-address | dhcp);}management;}}mac-address mac-address;monitor-cpu normal threshold;monitor-memory normal threshold;monitor-storage normal threshold;syslog {facility level;}}local-management {family inet {address ip-address;}}monitor-cpu normal threshold;monitor-memory normal threshold;monitor-storage normal threshold;}monitor-cpu normal threshold;monitor-memory normal threshold;monitor-storage normal threshold;virtual-machines {instance instance-name {compute-cluster compute-cluster-name {compute-node compute-node-name;}cpu cpu-number;interface interface-name {bridge bridge-name;family inet {[ address ip-address ];}host-interface interface-name {enable-passthrough;}hw-model model-name;}local-management {family (Compute Cluster) inet {address ip-address;}}memory gigabytes;package package-name;secondary-disk (hdb | hdc | hdd) disk-size gigabytes;}}}

Hierarchy Level

[edit services]

Release Information

Statement introduced in Junos OS Release 12.3.

Option monitor-cpu normal threshold introduced in Junos OS Release 13.2R2.

Option monitor-memory normal threshold introduced in Junos OS Release 13.2R2.

Option monitor-storage normal threshold introduced in Junos OS Release 13.2R2.

Description

Configure the App Engine. The [edit services app-engine] hierarchy level has two components to configure: the physical connection between the device running Junos and the hardware appliance (which is under the [edit services app-engine compute-cluster] hierarchy level) and the virtual machines, where the applications run, each on its own guest OS (the [edit services app-engine virtual-machines] hierarchy level).

SNMP traps can be set at this hierarchy level or at the [edit services app-engine compute-cluster compute-cluster-name compute-node compute-node-name] or [edit services app-engine compute-cluster compute-cluster-name] hierarchy levels. Settings at the [edit services app-engine compute-cluster compute-cluster-name] hierarchy level override those at this level and settings at the [edit services app-engine compute-cluster compute-cluster-name compute-node compute-node-name] hierarchy level override those at any other level.

Options

monitor-cpu normal threshold
—

Normal and maximum processing loads as percentages of the CPU. If the overall system CPU usage or per-CPU usage exceeds the threshold percentage, the system raises the jnxVECNProcessingLoadHigh or jnxVECNProcessorLoadHigh trap. When the system detects a jnxVECNProcessingLoadHigh or jnxVECNProcessorLoadHigh condition and then drops to or below the normal percentage, the jxnVECNProdessingLoadOk or jnxVECNProcessorLoadOk alarm is triggered.

Default: normal default is 80; threshold default is 90

monitor-memory normal threshold
—

Normal and maximum RAM usages as percentages. If the RAM usage rises above the threshold percentage, the system raises the jnxVECNMemoryLow trap. When the RAM usage rises above the maximum and then drops below the normal percentage, the jnxVECNMemoryOk alarm is triggered.

Default: normal default is 80; threshold default is 90

monitor-storage normal threshold
—

Normal and maximum storage usages as percentages. If the space usage under volume LFS (/volume/lfs) or volume SFS (/volume/sfs) rises above the threshold percentage, the system raises the jnxVECNStorageLow trap. When the storage usage recovers and drops below the normal percentage, the jnxVECNStorageOk alarm is triggered.

Default: normal default is 80; threshold default is 90

Required Privilege Level

admin—To view this statement in the configuration.

admin-control—To add this statement to the configuration.

Related Documentation

Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.