Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    Related Documentation




    routing-instance routing-instance-name{family inet {address ip-address;}}

    Hierarchy Level

    [edit services app-engine compute-cluster compute-cluster-name local-management], [edit services app-engine virtual-machines instance instance-name local-management]

    Release Information

    Statement introduced in Junos OS Release 13.2.


    (Optional) Configure a routing instance for the JunosV App Engine infrastructure. Packets are restricted to the specified routing instance. By specifying the routing instance, the JunosV App Engine infrastructure can be made to operate in a non-default routing instance. This feature ensures that JunosV App Engine traffic can be segregated from other traffic.

    If the routing-instance statement is absent from the [edit services app-engine virtual-machines instance instance-name local-management] hierarchy level, the virtual machine (VM) will inherit this routing instance from its [edit services app-engine compute-cluster compute-cluster-name local-management] hierarchy level.

    Note: Additional configuration under the [edit routing-instances] hierarchy level is required to ensure that the Routing Engine interface address belongs to that particular routing instance on the routing engine. Each routing instance consists of sets of the following: Routing tables, interfaces that belong to these routing tables (optional, depending upon the routing instance type), and routing option configurations.



    Name of the routing instance.

    The remaining statements are explained separately.

    Required Privilege Level

    system—To view this statement in the configuration.

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


    Related Documentation


    Published: 2014-04-04