Predefined Multipoint-to-Multipoint Ethernet Service Definitions
The Connectivity Services Director application provides predefined service definitions that a service provisioner can choose from when creating a service order. This section provides information about predefined service definitions used for creating mutlipoint-to-multipoint Ethernet services. For information about predefined service definitions used to create E-Line service definitions or point-to-multipoint service definitions, see the following topics:
If none of the multipoint-to-multipoint predefined service definitions described here is appropriate for your needs, you can create a service definition as described in Creating a Multipoint-to-Multipoint E-LAN Service Definition.
The Connectivity Services Director application provides predefined service definitions for E-LAN services that use BGP switching in the network core. These services are sometimes known as E-LAN services. This section covers multipoint-to-multipoint (or full mesh) service definitions. 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, VLAN list)
VLAN normalization
Physical interface encapsulation
Logical interface encapsulation
Rate limit range
Table 1 lists each of the standard E-LAN service definitions. Each standard service definition is then described in detail in the sections that follow.
Table 1: Standard Multipoint-to-Multipoint Service Definitions
Standard Service Definition Name | Service Attributes |
|---|---|
| |
| |
| |
| |
| |
| |
|
ELAN-BGP-Dot1q-Normalized-VLAN-None Service Definition
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 1:
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; vlan-id none; 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;
vlan-id none;
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):
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;
vlan-id none;
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 Service Definition
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 1:
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 Service Definition
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 ethernet-vpls 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 (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 Service Definition
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 1:
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 Service Definition
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 1:
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;
vlan-id all;
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;
vlan-id all;
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;
vlan-id all;
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 Service Definition
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 1:
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;
vlan-id none;
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;
vlan-id none;
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;
vlan-id none;
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 Service Definition
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;
}
}
}
}