Creating a Service Definition for VPLS Access into Layer 3 Networks
You can configure an Integrated Routing and Bridging (IRB) interface to provide access from VPLS Layer 2 networks and services into Layer 3 networks. If the IRB interface configured as a Layer 3 interface is being used in a routing instance, that routing instance will specifically declare it as routing-interface rather than a regular VPLS interface (which acts like the interface on a specific VPLS site). This feature requires a normalized VLAN (vlan-id=xxx which is the same as the unit name on which the inet4 address is specified)
Junos Space uses the two peer subinterfaces of the IRB to create the link between an existing VLAN and the Layer 3 network. An extra VPLS node is required to support the IRB interface which allows the rest of the VPLS nodes to be able to access all Layer 3 networks reachable through that interface. Providing the VPLS access into Layer 3 networks enhances basic VPLS services. Because this feature requires a normalized VLAN, it is available only on the Juniper Networks MX 3D Router series.
Prerequisites for VPLS Access into Layer 3 Networks
The PE device with the IRB must be a Juniper Networks MX 3D Series Router to accommodate the normalized VLAN requirement.
In addition to the PE device used for the IRB, 2 or more PEs must exist on the VPLS network for a minimum of 3 PE devices.
A VLAN must already exist to configure this feature.
To begin the configuration of the IRB interface, in the Network Activate task pane, select Service Design > Manage Service Definitions > Create VPLS Service Definition.
Provide a name for the VPLS service definition you want to create.
Select the type of service from the menu list. To create the VPLS into Layer 3 service, use either of the following service type:
Provide any comments or a description that will help explain the purpose of this definition.
Enable L3 Access
Check the box to create the link into Layer 3.
- Click Next to display the next screen, UNI Settings, and continue creating the service definition.
Specifying UNI Settings
UNI Settings Field
Traffic Treatment Settings
Indicate the Ethernet option to use for this VPLS service definition. Choices are qinq or dot1q.
Customer traffic type
The only option for VPLS service definitions is Transport single VLAN.
VLAN ID selection
The only option for VPLS service definitions is Select manually.
Physical IF encapsulation
The only option for VPLS service definitions is flexible-ethernet-services
Logical IF encapsulation
The only option for VPLS service definitions is vlan-vpls.
Default MTU (Bytes)
This field is populated with the default MTU value of 1522. If you are not using the default value, enter the MTU value in bytes.
MTU range (Bytes)
If you are specifying a custom MTU value, indicate the range of values in bytes.
- Click Next to continue creating the VPLS service definition and specify the connectivity settings.
Specifying Connectivity Settings
Connectivity Settings Field
The Route target field is prepopulated with the Auto pick option.
The Route distinguisher field is prepopulated with the Auto pick option.
All VPLS service definitions require VLAN normalization.
If you are using multihoming features, check the box.
MAC Security Settings
MAC learning is on by default for VPLS service definitions.
Interface MAC limit
The default value for Interface MAC limit is 1024. If you are using a different value, enter that value.
MAC table size
The table size is predetermined to correspond to the default MAC limit. If you are using a value other than the default, specify that value.
- Click Finish to see the service definition
- Click on the unpublished service definition you just created.
- Right-click on the selected service definition to choose
- Select the service definition and click Publish to save and publish the definition.
- The next step is to create the service order. In the Network Activate task pane, select Service Provisioning.