Navigation
Supported Platforms
Configuring Separate Routing Instances for PPPoE Service Retailers
As the owner of the system, the wholesaler uses the default routing instance. You must create separate routing instances for each individual retailer to keep routing information for individual retailers separate and to define any servers and forwarding options specific to each retailer.
To define a retailer routing instance:
- Create the retailer routing instance.[edit]user@host# edit routing-instances PPPoE_Retailer_Instance1
- Specify the routing instance type for the retailer.[edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set instance-type vrf
- Specify the access profile that you want the routing instance
to use. [edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set access-profile PPPoE_Retailer_Access1
- Specify the interface that faces the Retailer1 RADIUS
server.[edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set interface ge-11/1/9.10
- Specify the loopback interface unit for this routing instance.[edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set interface lo0.5
Note: Loopback interfaces must be unique for each routing instance.
- Specify an identifier to distinguish the VPN to which
the route belongs. [edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set route-distinguisher 1:1
- Specify how routes are imported into the local PE router’s
VPN routing table from the remote PE router.[edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set vrf-import policyImport
- Specify which routes are exported from the local instance
table to the remote PE router.[edit routing-instances “PPPoE_Retailer_Instance1”]user@host# set vrf-export policyExport
- Repeat this procedure for other retailers.
