Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Separate NNI 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 to the access portion of the network (for example, to an MSAN device) , you must configure the routing instances as an access routing instance. See Configuring Separate Access Routing Instances for Layer 2 Wholesale Service Retailers.

To define a retailer routing instance:

  1. Create the retailer routing instance.
  2. Specify the VLAN model that you want the retailer to follow.
  3. Specify the role that you want the routing instance to take.
  4. Specify the routing instance type for the retailer.
  5. Define the NNI ISP-facing interface for this retailer.
  6. Specify that access ports in this VLAN domain do not forward packets to each other.
  7. Specify a unique identifier attached to a route that enables you to distinguish to which VPN the route belongs.
  8. (Optional) Specify a VRF target community.

    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.
    2. Enable VPLS on the routing instance.
    3. Specify the maximum number of sites allowed for the VPLS domain.
    4. (Optional) Specify the no-tunnel-services statement if the router does not have a Tunnel Services PIC.
    5. Specify a site name.
    6. Specify a site identifier.
    7. Define the connectivity of the VPLS routing instance as permanent to keep the VPLS connection up until specifically taken down.
  10. Repeat this procedure for other retailers.