command-forwarding

Mode: Operational Mode

Syntax:

To allow remote command execution, a command must have the command-forwarding statement defined.

    command-forwarding {
        chassis-selector [<default-chassis-selector>];
        re-selector;
        lr-selector [<default-lr-selector>];
        vc-selector [<default-vc-selector>];
        exclude-targets <exclude-targets>+;
        re-timeout <timeout-value>;
        dynamic-argument <argument-name>;
        fpc-slot-argument <argument-name>;
        flag <flags>+;
        help <help-string>;
    }
   
       
    default-chassis-selector: all-chassis | local | primary
    
    default-lr-selector: all-lr | main 

    exclude-targets: multi-chassis | multi-re | chassis-selector
                     hobson | scc |                    (TX Matrix, Hobson)
                     absolut | sfc |                   (TX Plus, Absolut)
                     cluster |                         (Voyager/Viking, cluster)
                     system-domain | rsd | psd |       (JCS/Safari, system domain)
                     all-members |                     (EX-series/Hurricane, virtual chassis)
                     multi-lr                          (Logical system)

    re-timeout: possible arguments are all positive numbers

    dynamic-argument: possible arguments are all argument names currently existing

    fpc-slot-argument: possible arguments are all argument names currently existing

    flags: daemon-processed | async | primary-last | hide-args |
           forward-to-rsd | allow-from-rsd | allow-from-psd | include-rsd-on-psd

Description:

Command Forwarding provides a mechanism to invoke commands on remote systems/REs. Valid values are:

for exclude-targets:

for flags:

Example:

    command version {
        command-forwarding {
          chassis-selector all-chassis;
          exclude-targets multi-chassis;
          help "Show software version on %s";
        }
           ...
    }

Display:

Voyager
        regress@router1> show version ?
        Possible completions:
           node                   Cluster node

        regress@router1> show version node ?
        Possible completions:
           all                    All node
           local                  Local node
           primary                Primary node
           <node-id>              Node id (0..1)

TX Matrix (Hobson)

        regress@router1> show version ?
        Possible completions:
          routing-engine               Specify routing engine
          re0                          Routing engine 0 
          re1                          Routing engine 1
          all-chassis                  SCC and all LCC chassis
          all-lcc                      All LCC chassis
          scc                          SCC chassis
          lcc                          Specify LCC chassis

        regress@router1> show version lcc ?
        Possible completions:
            <lcc>                      LCC number (0..3)

        regress@router1> show version lcc 0 ?
        Possible completions:
          routing-engine               Specify routing engine
          re0                          Routing engine 0 
          re1                          Routing engine 1

        regress@router1> show version lcc 0 routing-engine ?
        Possible completions:
          local                        Local routing engine
          other                        Other routing engine
          master                       Master routing engine
          backup                       Backup routing engine
          both                         Both routing engines

See also

Reference (to programmers guide/style guide):


2007-2008 Juniper Networks, Inc. All rights reserved. The information contained herein is confidential information of Juniper Networks, Inc., and may not be used, disclosed, distributed, modified, or copied without the prior written consent of Juniper Networks, Inc. in an express license. This information is subject to change by Juniper Networks, Inc. Juniper Networks, the Juniper Networks logo, and JUNOS are trademarks of Juniper Networks, Inc.
Generated on Sun May 30 20:23:13 2010 for DDL Reference Guide by doxygen 1.4.5