Configuring How Interface Routes Are Imported into Routing Tables

By default, IPv4 interface routes (also called direct routes) are imported into routing table inet.0, and IPv6 interface routes are imported into routing table inet6.0. If you are configuring alternate routing tables for use by some routing protocols, it might be necessary to import the interface routes into the alternate routing tables. To define the routing tables into which interface routes are imported, you create a routing table group and associate it with the router’s interfaces.

To associate an IPv4 routing table group with the router’s interfaces and specify which routing table groups interface routes are imported into, include the interface-routes statement:

To associate an IPv6 routing table group with an interface, include the interface-routes statement at the [edit routing-options] hierarchy level:

For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.

To create the routing table groups, include the passive statement at the [edit routing-options] hierarchy level. For configuration information, see Creating Routing Table Groups.

If you have configured a routing table, configure the OSPF primary instance at the [edit protocols ospf] hierarchy level with the statements needed for your network so that routes are installed in inet.0 and in the forwarding table. Make sure to include the routing table group. For more information, see Configuring Multiple Instances of OSPF.

To export local routes, include the export statement:

For a list of hierarchy levels at which you can configure these statements, see the statement summary sections for these statements.

To export LAN routes, include the lan option. To export point-to-point routes, include the point-to-point option.

Only local routes on point-to-point interfaces configured with a destination address are exportable.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.