Configuring Separate Routing Instances for DHCPv6 Service Retailers
As the owner of the system, the wholesaler typically 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.user@host# edit routing-instances Retailer_Instance1
- Specify the routing instance type for the retailer.[edit routing-instances “Retailer_Instance1”]user@host# set instance-type vrf
- Specify the access profile that you want the routing instance
to use. [edit routing-instances “Retailer_Instance1”]user@host# set access-profile Retailer_Access1
- Specify the interface that faces the Retailer1 RADIUS
server.[edit routing-instances “Retailer_Instance1”]user@host# set interface ge-11/1/9.10
- Specify the loopback interface unit for this routing instance.[edit routing-instances “RetailerInstance1”]user@host# set interface lo0.1
Loopback interfaces must be unique for each routing instance.
- Repeat this procedure for other retailers.