Configuring Separate Routing Instances for DHCP 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 RetailerInstance1
- Specify the routing instance type for
the retailer.[edit routing-instances “RetailerInstance1”]user@host# set instance-type vrf
- Specify the access profile that you want
the routing instance to use. [edit routing-instances “RetailerInstance1”]user@host# set access-profile Retailer1
- Specify the interface that faces the
Retailer1 RADIUS server.[edit routing-instances “RetailerInstance1”]user@host# set interface ge-11/1/9.10
- Specify the interface that faces the
Retailer1 DHCP server.[edit routing-instances “RetailerInstance1”]user@host# set interface ge-11/1/10.100
- Specify the loopback interface unit for
this routing instance.[edit routing-instances “RetailerInstance1”]user@host# set interface lo0.1
Note: Loopback interfaces must be unique for each routing instance.
- Access the DHCP Relay forwarding options hierarchy
for the routing instance.[edit routing-instances “RetailerInstance1”]user@host# edit forwarding-options dhcp-relay
Note: The configuration for this wholesale solution uses DHCP Relay. However, you can also configure DHCP Proxy Relay or DHCP Local Server for the DHCP Layer 3 wholesale network.
- Specify that you want to configure authentication
options and use external AAA authentication services.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay]user@host# edit authentication
- (Optional) Configure a password that authenticates the username to the external authentication service.
- (Optional) Configure optional features to create a unique username.
- Specify the default dynamic profile that you want
to attach to DHCP subscriber for this retailer.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay]user@host# set dynamic-profile Subscriber_Profile_Retail1
- Specify any overrides for the default
DHCP Relay configuration.
See Overriding the Default DHCP Relay Configuration Settings.
- Configure a named server group for the retailer.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay]user@host# edit server-group Retailer1_Group
- Specify the DHCP server address for the
retailer group.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay server-group “Retailer1_Group”]user@host# set 10.10.100.1
- Specify the retailer group as the active
server group for this routing instance.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay]user@host# set active-server-group Retailer1_Group
- Configure a group you can use to define
the retailer dynamic profile and DHCP access interface.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay]user@host# edit group Retailer1_Group
- Specify the dynamic profile that the
retailer DHCP subscribers use.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay group “Retailer1_Group”]user@host# set dynamic-profile Subscriber_Profile_Retailer1
- Specify the retailer interface that the
retailer DHCP subscribers use.[edit routing-instances “RetailerInstance1” forwarding-options dhcp-relay group “Retailer1_Group”]user@host# set interface ge-2/3/0.2
- (Optional) Configure any passwords that authenticate the username to the external authentication service for the retailer groups that you created.
- (Optional) Configure any unique username values for the retailer groups that you created.
- (Optional) Specify any overrides for any of the
DHCP Relay group configurations that you created.
See Overriding the Default DHCP Relay Configuration Settings.
- Repeat this procedure for other retailers.
