Predefined Service Definitions
Connectivity Services Director provides predefined service definitions that a service provisioner can use when creating a service order.
If none of the predefined service definitions is appropriate for your needs, you can create a service definition as described in Creating an E-Line Service Definition, Creating a Point-to-Multipoint E-LAN Service Definition, or Creating a Service Definition for VPLS Access into Layer 3 Networks.
The Junos Space Connectivity Services Director product provides predefined service definitions for E-Line services and for E-LAN services. The following sections describe these service definitions:
E-Line Predefined Service Definitions
The Ethernet Activator software provides predefined service definitions for E-Line services that use LDP switching in the network core. These services are sometimes knows as E-Line Martini services. Figure 1 shows an example of such a service.
Information specific to each service instance, such as the device name, endpoint name, and customer VLAN ID, is provided in the service order. Attributes that can apply across many service instances are typically defined in the service definition. These attributes include:
Ethernet option (dot1.q, port-port, qinq, asymmetric tag depth)
Traffic type (single vlan, vlan range, all traffic, Transport vlan List)
Physical interface encapsulation
Logical interface encapsulation
Rate limit range
Table 1 lists each of the standard E-Line service definitions. Each standard service definition is then described in detail in the sections that follow.
Table 1: Standard Service Definitions
Standard Service Definition Name | Service Attributes |
|---|---|
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
ELine-Dot1q-SingleVLAN
This service definition provides a base for creating E-Line services that transport a single VLAN across an LDP network core using 802.1Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 1 {
description "Dot1q Eline Martini ";
encapsulation vlan-ccc;
vlan-id 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
protocols {
l2circuit {
neighbor 192.168.1.40
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 1 {
description "Dot1q Eline Martini ";
encapsulation vlan-ccc;
vlan-id 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
ELine-Dot1q-SingleVLAN-CCC
This service definition provides a base for creating E-Line services that transport a single VLAN across an LDP network core using 802.1Q endpoint interface types and vlan-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation vlan-ccc;
unit 513 {
description VLANCCC-SR;
encapsulation vlan-ccc;
vlan-id 513;
family ccc {
filter {
input filter_in_ge-0/1/1_513;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_513 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_513 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_513;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.513 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation vlan-ccc;
unit 513 {
description VLANCCC-SR;
encapsulation vlan-ccc;
vlan-id 513;
family ccc {
filter {
input filter_in_ge-0/1/1_513;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_513 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_513 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_513;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.513 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-Dot1q-SingleVLAN-Ext-CCC
This service definition provides a base for creating E-Line services that transport a single VLAN across an LDP network core using 802.1Q endpoint interface types and extended-vlan-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation extended-vlan-ccc;
unit 1 {
description Extended-SR;
vlan-id 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation extended-vlan-ccc;
unit 1 {
description Extended-SR;
vlan-id 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-PortBased
This service definition provides a base for creating E-Line services that transport all traffic across an LDP network core using an entire port at each endpoint using ethernet-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps to 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
encapsulation ethernet-ccc;
unit 0 {
family ccc {
filter {
input filter_in_ge-0/1/1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1 {
if-exceeding {
bandwidth-limit 10m;
burst-size-limit 6250000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.0 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
encapsulation ethernet-ccc;
unit 0 {
family ccc {
filter {
input filter_in_ge-0/1/1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1 {
if-exceeding {
bandwidth-limit 10m;
burst-size-limit 6250000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.0 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-QinQ-AllVLAN
This service definition provides a base for creating E-Line services that transport all customer traffic across an LDP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 1 {
description "AllVlanTransport";
encapsulation vlan-ccc;
vlan-tags outer 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 1 {
description "AllVlanTransport";
encapsulation vlan-ccc;
vlan-tags outer 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-QinQ-AllVLAN-CCC
This service definition provides a base for creating E-Line services that transport all customer traffic across an LDP network core using Q-in-Q endpoint interface types and vlan-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation vlan-ccc;
unit 515 {
description QinQ-ALLVLAN;
encapsulation vlan-ccc;
vlan-tags outer 515;
family ccc {
filter {
input filter_in_ge-0/1/1_515;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_515 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_515 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_515;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.515 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation vlan-ccc;
unit 515 {
description QinQ-ALLVLAN;
encapsulation vlan-ccc;
vlan-tags outer 515;
family ccc {
filter {
input filter_in_ge-0/1/1_515;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_515 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_515 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_515;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.515 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-QinQ-AllVLAN-Ext-CCC
This service definition provides a base for creating E-Line services that transport all customer traffic across an LDP network core using Q-in-Q endpoint interface types and extended-vlan-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation extended-vlan-ccc;
unit 1 {
description Ext-AllVLAN;
vlan-tags outer 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation extended-vlan-ccc;
unit 1 {
description Ext-AllVLAN;
vlan-tags outer 1;
family ccc {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.1 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-QinQ-VLANRange
This service definition provides a base for creating E-Line services that transport a range of VLANs across an LDP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 2 {
description "QinQ Eline Martini";
encapsulation vlan-ccc;
vlan-tags outer 2 inner-range 100-110;
family ccc {
filter {
input filter_in_ge-0/1/1_2;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_2 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
family ccc {
filter filter_in_ge-0/1/1_2 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_2;
accept;
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.2 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 2 {
description "QinQ Eline Martini";
encapsulation vlan-ccc;
vlan-tags outer 2 inner-range 100-110;
family ccc {
filter {
input filter_in_ge-0/1/1_2;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_2 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_2 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_2;
accept;
}
}
}
}
}
protocols {
l2circuit {
interface ge-0/1/1.2 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-QinQ-VLANRange-CCC
This service definition provides a base for creating E-Line services that transport a range of VLANs across an LDP network core using Q-in-Q endpoint interface types and vlan-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation vlan-ccc;
unit 514 {
description VLANRANGE-SR;
encapsulation vlan-ccc;
vlan-tags outer 514 inner-range 600-610;
family ccc {
filter {
input filter_in_ge-0/1/1_514;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_514 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_514 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_514;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.40 {
interface ge-0/1/1.514 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation vlan-ccc;
unit 514 {
description VLANRANGE-SR;
encapsulation vlan-ccc;
vlan-tags outer 514 inner-range 600-610;
family ccc {
filter {
input filter_in_ge-0/1/1_514;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_514 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_514 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_514;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.514 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
ELine-QinQ-VLANRange-Ext-CCC
This service definition provides a base for creating E-Line services that transport a range of VLANs across an LDP network core using Q-in-Q endpoint interface types and extended-vlan-ccc as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 1:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation extended-vlan-ccc;
unit 2 {
description Ext-VLANRange;
vlan-tags outer 2 inner-range 100-110;
family ccc {
filter {
input filter_in_ge-0/1/1_2;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_2 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_2 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_2;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.2 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z:
ge-0/1/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation extended-vlan-ccc;
unit 2 {
description Ext-VLANRange;
vlan-tags outer 2 inner-range 100-110;
family ccc {
filter {
input filter_in_ge-0/1/1_2;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_2 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family ccc {
filter filter_in_ge-0/1/1_2 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_2;
accept;
}
}
}
}
}
protocols {
l2circuit {
neighbor 192.168.1.30 {
interface ge-0/1/1.2 {
virtual-circuit-id 786;
no-control-word;
mtu 1522;
}
}
}
}
Multipoint-to-Multipoint Predefined Service Definitions
The Ethernet Activator software provides predefined service definitions for E-LAN services that use BGP switching in the network core. s. This section covers multipoint-to-multipoint (or full mesh) service definitions. Figure 2 shows an example of such a service.
Information specific to each service instance, such as the device name, endpoint name, and customer VLAN ID, is provided in the service order. Attributes that can apply across many service instances are typically defined in the service definition. These attributes include:
Ethernet option (dot1.q, port-port, qinq, asymmetric tag depth)
Traffic type (single vlan, vlan range, all traffic, transport vlan list)
VLAN normalization
Physical interface encapsulation
Logical interface encapsulation
Rate limit range
Table 2 lists each of the standard E-LAN service definitions. Each standard service definition is then described in detail in the sections that follow.
Table 2: Standard Service Definitions
Standard Service Definition Name | Service Attributes |
|---|---|
| |
| |
| |
| |
| |
| |
|
ELAN-BGP-Dot1q-Normalized-VLAN-None
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport traffic from a single VLAN on an endpoint across a BGP network core using 802.1Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. VLAN IDs are not preserved across the network—traffic passes from the single VLAN on an endpoint to any VLANs in the broadcast domain. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 2:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
ge-0/0/1 { flexible-vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-vpls; vlan-id 1; family vpls { filter { input filter_in_ge-0/0/1_1; } } } } firewall { policer policer_in_ge-0/0/1_1 { if-exceeding { bandwidth-limit 100m; burst-size-limit 62500000; } then discard; } family vpls { filter filter_in_ge-0/0/1_1 { interface-specific; term 1 { then { policer policer_in_ge-0/0/1_1; accept; } } } } } routing-instances { BestCustomer_ELAN-BGP-Dot1q-Normalized-VLAN-SR { instance-type vpls; interface ge-0/0/1.1; route-distinguisher 65410:1; vrf-target target:65410:0; protocols { vpls { no-tunnel-services; site Site_2 { site-identifier 2; site-preference primary; interface ge-0/0/1.1; } } }
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
ge-0/0/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-id 1;
family vpls {
filter {
input filter_in_ge-0/0/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/1_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-Dot1q-Normalized-VLAN-SR {
instance-type vpls;
interface ge-0/0/1.1;
route-distinguisher 65410:0;
vrf-target target:65410:0;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/0/1.1;
}
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
SJC:
ge-0/0/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-id 1;
family vpls {
filter {
input filter_in_ge-0/0/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/1_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-Dot1q-Normalized-VLAN-SR {
instance-type vpls;
interface ge-0/0/1.1;
vlan-id none;
route-distinguisher 65410:2;
vrf-target target:65410:0;
protocols {
vpls {
no-tunnel-services;
site Site_3 {
site-identifier 3;
site-preference primary;
interface ge-0/0/1.1;
}
}
}
}
ELAN-BGP-Dot1Q-SingleVLAN
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport traffic on a single VLAN across a BGP network core using 802.1Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. No VLAN mapping is performed—the VLAN ID must be the same on all endpoints. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 2:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
ge-0/0/2 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-id 1;
family vpls {
filter {
input filter_in_ge-0/0/2_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/2_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
filter filter_in_ge-0/0/2_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/2_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-Dot1Q-SingleVLAN-SR {
instance-type vpls;
interface ge-0/0/2.1;
route-distinguisher 65410:4;
vrf-target target:65410:1;
protocols {
vpls {
no-tunnel-services;
site Site_2 {
site-identifier 2;
site-preference primary;
interface ge-0/0/2.1;
}
}
}
}
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
ge-0/0/2 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-id 1;
family vpls {
filter {
input filter_in_ge-0/0/2_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/2_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
filter filter_in_ge-0/0/2_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/2_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-Dot1Q-SingleVLAN-SR {
instance-type vpls;
interface ge-0/0/2.1;
route-distinguisher 65410:3;
vrf-target target:65410:1;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/0/2.1;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
ge-0/0/2 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-id 1;
family vpls {
filter {
input filter_in_ge-0/0/2_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/2_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/2_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/2_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-Dot1Q-SingleVLAN-SR {
instance-type vpls;
interface ge-0/0/2.1;
route-distinguisher 65410:5;
vrf-target target:65410:1;
protocols {
vpls {
no-tunnel-services;
site Site_3 {
site-identifier 3;
site-preference primary;
interface ge-0/0/2.1;
}
}
}
}ELAN-BGP-PortBased
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport all traffic on an entire port across a BGP network core using E-LAN as the physical encapsulation type. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 2:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
ge-0/1/3 {
mtu 1522;
encapsulation ethernet-vpls;
unit 0 {
family vpls {
filter {
input filter_in_ge-0/1/3;
}
}
}
}
firewall {
policer policer_in_ge-0/1/3 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 15220;
}
then discard;
}
family vpls {
filter filter_in_ge-0/1/3 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/3;
accept;
}
}
}
}
}
routing-instances {
ELAN_BGP_PortBased_10_100M {
instance-type vpls;
interface ge-0/1/3.0;
route-distinguisher 65410:3;
vrf-target target:65410:1;
protocols {
vpls {
no-tunnel-services;
site Site_2 {
site-identifier 2;
site-preference primary;
interface ge-0/1/3.0;
}
}
}
}
} Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
ge-0/1/3 {
mtu 1522;
encapsulation ethernet-vpls;
unit 0 {
family vpls {
filter {
input filter_in_ge-0/1/3;
}
}
}
}
firewall {
policer policer_in_ge-0/1/3 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 15220;
}
then discard;
}
family vpls {
filter filter_in_ge-0/1/3 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/3;
accept;
}
}
}
}
}
routing-instances {
ELAN_BGP_PortBased_10_100M {
instance-type vpls;
interface ge-0/1/3.0;
route-distinguisher 65410:2;
vrf-target target:65410:1;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/1/3.0;
}
}
}
}
}Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
ge-0/2/2 {
mtu 1522;
encapsulation ethernet-vpls;
unit 0 {
family vpls {
filter {
input filter_in_ge-0/2/2;
}
}
}
}
}
firewall {
policer policer_in_ge-0/2/2 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 15220;
}
then discard;
}
family vpls {
filter filter_in_ge-0/2/2 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/2/2;
accept;
}
}
}
}
}
routing-instances {
ELAN_BGP_PortBased_10_100M {
instance-type vpls;
interface ge-0/2/2.0;
route-distinguisher 65410:4;
vrf-target target:65410:1;
protocols {
vpls {
no-tunnel-services;
site Site_3 {
site-identifier 3;
site-preference primary;
interface ge-0/2/2.0;
}
}
}
}ELAN-BGP-QinQ-AllVLAN
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport all traffic across a BGP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. No VLAN mapping is performed—customer VLAN IDs and service provider VLAN IDs must match on each endpoint that is to send or receive traffic. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 2:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
ge-0/1/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-SR {
instance-type vpls;
interface ge-0/1/1.1;
route-distinguisher 65410:13;
vrf-target target:65410:4;
protocols {
vpls {
no-tunnel-services;
site Site_2 {
site-identifier 2;
site-preference primary;
interface ge-0/1/1.1;
}
}
}
}
}
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
ge-0/1/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/1/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/1/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/1_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-SR {
instance-type vpls;
interface ge-0/1/1.1;
route-distinguisher 65410:12;
vrf-target target:65410:4;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/1/1.1;
}
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
ge-0/0/5 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/0/5_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/5_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/5_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/5_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-SR {
instance-type vpls;
interface ge-0/0/5.1;
route-distinguisher 65410:14;
vrf-target target:65410:4;
protocols {
vpls {
no-tunnel-services;
site Site_3 {
site-identifier 3;
site-preference primary;
interface ge-0/0/5.1;
}
}
}
}
}ELAN-BGP-QinQ-AllVLAN-Normalized-All
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport all traffic across a BGP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. Customer VLAN IDs are preserved across the network—traffic passes only among matching customer VLAN IDs. However, traffic can pass among any service provider VLAN ID in the broadcast domain. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 2:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
ge-0/1/0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/1/0_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/0_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/1/0_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/0_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-Normalized-All-SR {
instance-type vpls;
interface ge-0/1/0.1;
route-distinguisher 65410:10;
vrf-target target:65410:3;
protocols {
vpls {
no-tunnel-services;
site Site_2 {
site-identifier 2;
site-preference primary;
interface ge-0/1/0.1;
}
}
}
}
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
ge-0/1/0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/1/0_1;
}
}
}
}
firewall {
policer policer_in_ge-0/1/0_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/1/0_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/1/0_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-Normalized-All-SR {
instance-type vpls;
interface ge-0/1/0.1;
route-distinguisher 65410:9;
vrf-target target:65410:3;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/1/0.1;
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
ge-0/0/4 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/0/4_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/4_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/4_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/4_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-Normalized-All-SR {
instance-type vpls;
interface ge-0/0/4.1;
vlan-id all;
route-distinguisher 65410:11;
vrf-target target:65410:3;
protocols {
vpls {
no-tunnel-services;
site Site_3 {
site-identifier 3;
site-preference primary;
interface ge-0/0/4.1;
}
}
}
}ELAN-BGP-QinQ-AllVLAN-Normalized-None
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport all traffic across a BGP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. VLAN IDs are not preserved across the network—traffic passes between any customer VLAN or service provider VLAN in the broadcast domain. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 2:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
ge-0/0/3 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/0/3_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/3_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/3_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/3_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-Normalized-SR {
instance-type vpls;
interface ge-0/0/3.1;
route-distinguisher 65410:7;
vrf-target target:65410:2;
protocols {
vpls {
no-tunnel-services;
site Site_2 {
site-identifier 2;
site-preference primary;
interface ge-0/0/3.1;
}
}
}
}
}
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
ge-0/0/3 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/0/3_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/3_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/3_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/3_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-Normalized-SR {
instance-type vpls;
interface ge-0/0/3.1;
route-distinguisher 65410:6;
vrf-target target:65410:2;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/0/3.1;
}
}
}
}
}Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
ge-0/0/3 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1;
family vpls {
filter {
input filter_in_ge-0/0/3_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/3_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/3_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/3_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-AllVLAN-Normalized-SR {
instance-type vpls;
interface ge-0/0/3.1;
vlan-id none;
route-distinguisher 65410:8;
vrf-target target:65410:2;
protocols {
vpls {
no-tunnel-services;
site Site_3 {
site-identifier 3;
site-preference primary;
interface ge-0/0/3.1;
}
}
}
}
}ELAN-BGP-QinQ-Range-Normalized-VLAN
This service definition provides a base for creating multipoint-to-multipoint Ethernet services that transport traffic from a range of VLANs on an endpoint across a BGP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. Services built from this service definition must use MX Series devices on the provider edge. Customer VLAN IDs are preserved across the network—traffic passes among like customer VLAN IDs on any service provider VLAN in the broadcast domain. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data for a service with only two endpoints, SJC and SFO.
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device SJC):
ge-0/0/6 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 2 {
encapsulation vlan-vpls;
vlan-tags outer 2 inner-range 1500-2000;
family vpls {
filter {
input filter_in_ge-0/0/6_2;
}
}
}
}
firewall {
policer policer_in_ge-0/0/6_2 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/6_2 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/6_2;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-Range-Normalized-VLAN-SR1 {
instance-type vpls;
vlan-id all;
interface ge-0/0/6.2;
vlan-id all;
route-distinguisher 65410:19;
vrf-target target:65410:6;
protocols {
vpls {
no-tunnel-services;
site Site_2 {
site-identifier 2;
site-preference primary;
interface ge-0/0/6.2;
}
}
}
}
}
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SFO):
ge-0/0/1 {
flexible-vlan-tagging;
mtu 1522;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-tags outer 1 inner-range 1500-2000;
family vpls {
filter {
input filter_in_ge-0/0/1_1;
}
}
}
}
firewall {
policer policer_in_ge-0/0/1_1 {
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 62500000;
}
then discard;
}
family vpls {
filter filter_in_ge-0/0/1_1 {
interface-specific;
term 1 {
then {
policer policer_in_ge-0/0/1_1;
accept;
}
}
}
}
}
routing-instances {
BestCustomer_ELAN-BGP-QinQ-Range-Normalized-VLAN-SR1 {
instance-type vpls;
vlan-id all;
interface ge-0/0/1.1;
route-distinguisher 65410:18;
vrf-target target:65410:6;
protocols {
vpls {
no-tunnel-services;
site Site_1 {
site-identifier 1;
site-preference primary;
interface ge-0/0/1.1;
}
}
}
}
Point-to-Multipoint Service Definitions
The Ethernet Activator software provides predefined service definitions for E-LAN services that use BGP switching in the network core. This section covers point-to-multipoint (or hub and spoke) service definitions. Figure 3 shows an example of such a service.
Information specific to each service instance, such as the device name, endpoint name, customer VLAN ID, and whether a specific endpoint is a hub or a spoke is provided in the service order. Attributes that can apply across many service instances are typically defined in the service definition. These attributes include:
Ethernet option (dot1.q, port-port, qinq, asymmetric tag depth)
Traffic type (single vlan, vlan range, all traffic, transport vlan list)
VLAN normalization
Physical interface encapsulation
Logical interface encapsulation
Rate limit range
Table 3 lists each of the standard E-LAN service definitions. Each standard service definition is then described in detail in the sections that follow.
Table 3: Standard Service Definitions
Standard Service Definition Name | Service Attributes |
|---|---|
| |
|
ELAN-Hub-Spoke-QinQ-AllVLAN
This service definition provides a base for creating point-to-multipoint Ethernet services that transport all traffic on an endpoint across a BGP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. Customer VLAN IDs are preserved across the network—traffic passes among like customer VLAN IDs on any service provider VLAN in the broadcast domain. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 3:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device IND):
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):
ELAN-Hub-Spoke-QinQ-AllVLAN-No
This service definition provides a base for creating point-to-multipoint Ethernet services that transport all traffic on an endpoint across a BGP network core using Q-in-Q endpoint interface types and flexible-ethernet-services as the physical encapsulation type. VLAN IDs are not preserved across the network—traffic passes from the single VLAN on an endpoint to any VLANs in the broadcast domain. Service provisioners can limit the bandwidth of services built from this service definition to specific values from 10 Mbps through 100 Mbps.
The following sections show the configuration data on each endpoint when you use this service definition to create the service shown in Figure 3:
Configuration on Endpoint A
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A(device IND):
Configuration on Endpoint B
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device BLR):
Configuration on Endpoint Z
The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device SJC):