Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring Separate Access Routing Instances for Layer 2 Wholesale 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.

When creating separate routing instances, it is important to understand the role that the router plays in the Layer 2 Wholesale network and specify that role (either access or NNI) in the routing instance configuration. If the router connects directly to an ISP network (or ISP-controlled device), you must configure the routing instances as an NNI routing instance. See Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers.

1. Create the retailer routing instance.
   [edit]user@host# edit routing-instances RetailerInstance1
2. Specify the VLAN model that you want the retailer to follow.
   [edit routing-instances RetailerInstance1]user@host# set vlan-model one-to-one
3. Specify the role that you want the routing instance to take.
   [edit routing-instances RetailerInstance1]user@host# set instance-role access
4. Specify the routing instance type for the retailer.
   [edit routing-instances RetailerInstance1]user@host# set instance-type l2backhaul-vpn
5. Specify the access interface for the retailer.
   [edit routing-instances RetailerInstance1]user@host# set interface ge-2/3/0.0
6. Specify that access ports in this VLAN domain do not forward packets to each other.
   [edit routing-instances RetailerInstance1]user@host# set no-local-switching
7. Specify a unique identifier attached to a route that enables you to distinguish to which VPN the route belongs.
   [edit routing-instances RetailerInstance1]user@host# set route-distinguisher 10.10.1.1:1
8. (Optional) Specify a VRF target community.
   [edit routing-instances RetailerInstance1]user@host# set vrf-target target:100:1

   Note: The purpose of the vrf-target statement is to simplify the configuration by allowing you to configure most statements at the [edit routing-instances] hierarchy level.

9. Define the VPLS protocol for the routing instance.

   1. Access the routing instance protocols hierarchy.
      [edit routing-instances RetailerInstance1]user@host# edit protocols
   2. Enable VPLS on the routing instance.
      [edit routing-instances RetailerInstance1 protocols]user@host# edit vpls
   3. Specify the maximum number of sites allowed for the VPLS domain.
      [edit routing-instances RetailerInstance1 protocols vpls]user@host# set site-range 10
   4. Specify the size of the VPLS MAC address table for the routing instance.
      [edit routing-instances RetailerInstance1 protocols vpls]user@host# set mac-table-size 6000
   5. Specify the maximum number of MAC addresses that can be learned by the VPLS routing instance.
      [edit routing-instances RetailerInstance1 protocols vpls]user@host# set interface-mac-limit 2000
   6. (Optional) Specify the no-tunnel-services statement if the router does not have a Tunnel Services PIC.
      [edit routing-instances RetailerInstance1 protocols vpls]user@host# set no-tunnel-services
   7. Specify a site name.
      [edit routing-instances RetailerInstance1 protocols vpls]user@host# set site A-PE
   8. Specify a site identifier.
      [edit routing-instances RetailerInstance1 protocols vpls site A-PE]user@host# set site-identifier 1
10. Repeat this procedure for other retailers. In this example, you must configure a routing instance for Retailer 2.