[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Multitopology Routing in Static Routes

You can configure static routes to become installed in the routing table for any configured topology. Include the rib routing-table-name statement at the [edit routing-options] hierarchy level:



[edit routing-options]



rib routing-table-name {



static {


route destination-prefix {

next-hop;
}



static-options;
}


}


}

For routing-table-name, use the following format: logical-system-name/routing-instance-name:topology-name.protocol.identifier. The routing instance string is included only if the instance is not the master. The logical system string is included only if the logical system identifier has a value other than 0 (zero). Each routing table for a topology includes a colon (:) before the topology name that also separates the routing instance name from the topology name. protocol is the protocol family, which can be inet or inet6. identifier is a positive integer that specifies the instance of the routing table. When you create a topology for an instance (master or virtual-router), a new routing table is created within the instance for that topology. For more detailed information about routing table naming conventions for Multitopology Routing, see Routing Table Naming Conventions for Multitopology Routing.

For route destination-prefix, specify the destination of the route in the following way: network/mask-length, where network is the network portion of the IP address and mask-length is the destination prefix length. You can specify an IPv4 or IPv6 address.

You can optionally specify how to reach the destination by including the next-hop statement.

In addition, you can specify static-options, which defines additional information about static routes that is included with the route when it is installed in the routing table. For more information about specific static options you can optionally configure, see Specifying Static Route Options.

[Contents] [Prev] [Next] [Index] [Report an Error]