Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring Separate Routing Instances for DHCPv6 Service Retailers

date_range 06-Dec-23

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:

  1. Create the retailer routing instance.
    content_copy zoom_out_map
    [edit]
    user@host# edit routing-instances Retailer_Instance1
    
  2. Specify the routing instance type for the retailer.
    content_copy zoom_out_map
    [edit routing-instances “Retailer_Instance1”]
    user@host# set instance-type vrf
    
  3. Specify the access profile that you want the routing instance to use.
    content_copy zoom_out_map
    [edit routing-instances “Retailer_Instance1”]
    user@host# set access-profile Retailer_Access1
    
  4. Specify the interface that faces the Retailer1 RADIUS server.
    content_copy zoom_out_map
    [edit routing-instances “Retailer_Instance1”]
    user@host# set interface ge-11/1/9.10
    
  5. Specify the loopback interface unit for this routing instance.
    content_copy zoom_out_map
    [edit routing-instances “RetailerInstance1”]
    user@host# set interface lo0.1
    
    Note:

    Loopback interfaces must be unique for each routing instance.

  6. Repeat this procedure for other retailers.
footer-navigation