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

Configuring RIP Between the PE and CE Routers

For a Layer 3 VPN, you can configure RIP on the PE router to learn the routes of the CE router or to propagate the routes of the PE router to the CE router. RIP routes learned from neighbors configured at any [edit routing-instances] hierarchy level are added to the routing instance’s inet table (instance_name.inet.0).

To configure RIP as the routing protocol between the PE and the CE router, include the rip statement:

rip {
group group-name {
export policy-names;
neighbor interface-name;
}
}

You can include the rip statement at the following hierarchy levels:

By default, RIP does not advertise the routes it receives. To advertise routes from a PE router to a CE router, you need to configure an export policy on the PE router for RIP. For information on how to define an export policy, see the JUNOS Policy Framework Configuration Guide.

To specify an export policy for RIP, include the export statement:

export [ policy-names ];

You can include the export statement for RIP at the following hierarchy levels:

To install routes learned from a RIP routing instance into multiple routing tables, include the rib-group and group statements:

rib-group inet group-name;
group group-name {
neighbor interface-name;
}

You can include these statements at the following hierarchy levels:

To configure a routing table group, include the rib-groups statement:

rib-groups group-name;

You can include the rib-groups statement at the following hierarchy levels:

To add a routing table to a routing table group, include the import-rib statement. The first routing table name specified under the import-rib statement must be the name of the routing table you are configuring. For more information about how to configure routing tables and routing table groups, see the JUNOS Routing Protocols Configuration Guide.

import-rib [ group-names ]

You can include the import-rib statement at the following hierarchy levels:

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

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