Simplified Interinstance Configuration

By changing the configuration format of interinstance export policies, JUNOS 5.4 software makes it easier to share routes between VRF instances, other types of instances (such as non-forwarding instances), and IGPs.

VRF instances can share routes with the statement auto-export. When you configure auto-export, the vrf-import and vrf-export policies are compared across all VRF instances. If there is a common route target community between the different instances, the routes
are shared.

For VRF instances, such as overlapping VPNs, the basic hierarchy levels for auto-export are as follows:

[edit]

routing-instances {

    instance-name {

        routing-options {

            auto-export;

        }

    }

}

For non-forwarding instances, routes are imported into the instance so routing protocols can announce them. For more information, see Configuring Non-Forwarding Instances.

A third option for interinstance export is using an Interior Gateway Protocol (IGP), such as Open Shortest Path First (OSPF) or Intermediate System-to-Intermediate System (IS-IS). An example of the hierarchy used for IGP import and export is listed below.

[edit]

routing-options {

    instance-import;

    instance-export;

    auto-export {

        (enable | disable);

        family inet {

            unicast {

                (enable | disable);

                rib-group;

            }

            multicast {

                (enable | disable);

                rib-group;

            }

        }

    }

    traceoptions {

        file file-name;

        flag flag-type;

    }

}

When configuring interinstance route sharing, keep this information in mind:

• The instance-import and instance-export commands cannot be used with VRF instances. They are equivalent to the vrf-import and vrf-export VRF-specific commands.
• Traceoptions in the master instance apply to the rt-export task. Consequently, such traceoptions are propagated to all other instances, although they can be modified as needed.
• The auto-export statement applies to VRF and non-VRF instances.
• Use of the command instance-import automatically enables auto-export for non-VRF instances.
• Some network administrators use the instance-import functionality to create communities of interest. By setting up different VPNs and sharing routes between instances as needed, administrators can tailor services to the needs of their customers. For an example, see Configuring Non-Forwarding Instances.

To save time when configuring interinstance parameters on multiple instances, you can configure auto-export to be the default behavior for all your routing instances by means of a configuration group.

[edit]

groups {

    vrf-export-on {

        routing-instances {

            routing-options {

                auto-export;

            }

        }

    }

}

At the desired hierarchy level, you apply the configuration group and all members of the group receive the same policy:

apply-groups vrf-export-on;