Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    show app-engine status

    Syntax

    show app-engine status<compute-cluster compute-cluster-name compute-node compute-node-name>

    Release Information

    Command introduced in Junos OS Release 12.3.

    Command introduced in Junos OS Release 13.2X51-D15 for the QFX Series.

    Description

    Show the status of a compute node.

    Options

    compute-cluster compute-cluster-name compute-node compute-node-name

    (Optional) Name of computer cluster and compute node.

    Additional Information

    In the operational mode of the CLI when you type ? for a name, for example a compute-node name, you would expect to get a list of available compute nodes plus the option to type in a name not listed. This is the auto-complete feature in the CLI. However, in JunosV App Engine, , if you specify compute cluster and compute node in the operational command, the auto-complete works only if the compute cluster is put before the compute node.

    For commands with an optional compute-cluster compute-cluster-name option, if that option is omitted, the command will be executed on all compute nodes of all compute clusters. For commands with an optional compute-node compute-node-name option, if that option is omitted, the command will be executed on all compute nodes of the specified compute cluster.

    When the compute node configuration has been updated or the jvae package is upgraded, this command shows the following note that the compute node configuration or the jvae package has been updated and the compute node needs to be rebooted for the configuration to take effect.

     NOTE: Configuration and/or jvae package updated. Please reboot to take effect.

    The note also displays the details of what exactly has been updated on the Routing Engine. Once the compute node is rebooted, the note automatically goes off.

    If the operational compute node name (hostname) is different than the administrative compute node name, then the following error message is displayed.

                            ERROR: The compute node has the following errors:
                                    - Operational node name: cn               
                                    Administrative node name: newname         
                                    Either reboot the node OR change the
                                    administrative node name to 'cn' to
                                    continue VMM operations.
    

    Where cn is the previous compute node name.

    A mismatch between the operational node name and the administrative node name could happen if you rename the compute node name in the CLI. For example:

    [edit]
    user@router# rename services app-engine compute-cluster cc compute-node cn to compute-node newname
    [edit]
    user@router# set services app-engine virtual-machines instance vmx1 compute-cluster cc compute-node newname
    [edit]
    user@router# commit
    commit complete
    [edit]
    user@router# run show app-engine status
    Compute cluster: cc  
    Compute node    Status   
    newname         Online     ERROR: The compute node has the following errors:
                               - Operational node name: cn 
                               Administrative node name: newname 
                               Either reboot the node OR change the administrative 
                               node name to 'cn' to continue VMM operations.
    [edit]
    user@router#

    If the compute node has any error messages displayed, the VM operations will not work until the error is fixed.

    user@router# run show app-engine virtual-machine instance
    VM name             Compute cluster          VM status  
    vmx1                cc                       --- VMM service is not available ---

    To fix the error, either reboot the node or change the administrative node name (in both the physical and VM configurations) back to the operational (previous) compute node name.

    Required Privilege Level

    view

    List of Sample Output

    show app-engine status
    show app-engine status compute-cluster compute-node

    Output Fields

    For a description of the output fields, see Table 1. Output fields are listed in the approximate order in which they appear.

    Table 1: show app-engine status Output Fields

    Field Name

    Field Description

    Compute cluster

    Name of compute cluster.

    Compute node

    Name of compute node.

    Status

    Online or offline.

    If the status is Offline, a note is displayed. The XX:XX:XX:XX:XX:XX variable in the note will contain the mac-address attribute of the compute node.

    Note: If you see the node as Offline, please check if the compute node is booted and is properly connected to the router.

    Sample Output

    show app-engine status

    user@host> show app-engine status
    Compute cluster: cc1
      Compute node      Status
      cn0               Online        
      Compute cluster: new-cluster
      Compute node      Status
      new-node          Offline         NOTE: Please check if the compute node
                                        with network boot interface MAC address
                                        XX:XX:XX:XX:XX:XX is UP and is properly
                                        connected to the router
    

    show app-engine status compute-cluster compute-node

    The output for the show app-engine status compute-cluster compute-node command is identical to that for the show app-engine status command except that usage information displayed is for only the compute node specified whereas the show app-engine status command displays all the compute nodes.

    Published: 2014-03-31