Configuring Rip Between The Pe And Ce Routers - Juniper ACX1000 Configuration Manual

ACX Series Universal Access Router Configuration Guide

Configuring RIP Between the PE and CE Routers

838
do not have a VPN route tag set. The LSAs are assumed to be from a disjoint backbone
area.
You can change the configuration of the PE router's routing instance to cause the PE
router to act as a non-ABR by including the
routing-instances routing-instance-name protocols ospf domain-id]
make this configuration change to the hub PE router that receives the LSAs from the
hub CE router.
By making this configuration change, the PE router's routing instance acts as a non-ABR.
The PE router then considers the LSAs arriving from the hub CE router as if they were
coming from a contiguous nonbackbone area.
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
the routing instance's
inet
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 this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name protocols]
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols]
NOTE: The
[edit logical-systems]
Series routers.
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 about how to define policies for RIP, see Example: Applying Policies to RIP
Routes Imported from Neighbors.
To specify an export policy for RIP, include the
export [ policy-names ];
You can include this statement for RIP at the following hierarchy levels:
[edit routing-instances routing-instance-name protocols rip group group-name]
disable
[edit routing-instances]
table (
instance_name.inet.0
hierarchy level is not applicable in ACX
export
statement at the
[edit
hierarchy level. You
hierarchy level are added to
).
statement:
Copyright © 2017, Juniper Networks, Inc.