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 Services > Connectivity task pane, select Service Design > Manage Service Definitions > Create E-LAN Service Definition.
Field | Action |
|---|---|
Service Definition Name | Provide a name for the E-LAN service definition you want to create. |
Service Type | Select the type of service from the menu list. To create the VPLS into Layer 3 service, use either of the following service type:
|
Description | Provide any comments or a description that will help explain the purpose of this definition. |
Instance Type | Select an instance type to choose the type of routing instance for the E-LAN service:
|
Protocol | Different protocols are available based on the instance type you select:
|
Enable L3 Access | Select the check box to create the link into Layer 3. |
Enable Multihoming | Select this check box to pair any two N-PE devices, for providing redundant connectivity. When you select this check box, a Multihoming Mode list appears if you select evpn or evpn e-tree as the protocol type. You can select either single-active or all-active as the multihoming mode. |
Route target | The Route target field is prepopulated with the Auto pick option. |
Route distingquisher | The Route distinguisher field is prepopulated with the Auto pick option. |
MAC Settings | |
MAC learning | MAC learning is on by default for E-LAN 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 Next to display the next screen, Site Settings, and continue creating the service definition.
Specifying Site or UNI Settings
Site Settings Field | Action |
|---|---|
PE-CE Interface Settings – Ethernet Encapsulation | |
VLAN Tagging | Indicate the Ethernet option to use for this E-LAN service definition. Choices are qinq, dot1q, or asymmetric tag depth. |
Customer VLANs | The only option for E-LAN service definitions is Transport single VLAN. |
VLAN normalization | All E-LAN service definitions require VLAN normalization. |
Auto Pick VLAN ID | The only option for E-LAN service definitions is Select manually. |
Physical Interface Encapsulation | The only option for E-LAN service definitions is flexible-ethernet-services |
Logical Interface Encapsulation | The only option for E-LAN 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 Finish to see the service definition inventory list.
- Click on the unpublished service definition you just created.
- Right-click on the selected service definition to choose publishing options.
- 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 Services > Connectivity task pane, select Service Provisioning.