Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Predefined Point-to-Multipoint Ethernet Service Definitions

    The Network Activate software 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 point-to-multipoint services. For information about predefined service definitions used to create point-to-point service definitions or multipoint-to-multipoint service definitions, see the following topics:

    If none of the point-to-multipoint predefined service definitions described here is appropriate for your needs, you can create a service definition as described in Creating a Point-to-Multipoint VPLS Service Definition.

    The Network Activate software provides predefined service definitions for VPLS services that use BGP switching in the network core. These services are sometimes known as E-LAN services. This section covers point-to-multipoint (or hub-and-spoke) service definitions.

    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, qinq)
    • Traffic type (single VLAN, VLAN range, all traffic)
    • VLAN normalization
    • Physical interface encapsulation
    • Logical interface encapsulation
    • Rate limit range

    Table 1 lists each of the standard VPLS service definitions. Each standard service definition is then described in detail in the sections that follow.

    Table 1: Standard Point-to-Multipoint Service Definitions

    Standard Service Definition Name

    Service Attributes

    ELAN-Hub-Spoke-QinQ-AllVLAN-Normalized-All Service Definition

    • Multipoint Ethernet service for M Series or MX Series devices
    • Gigabit Ethernet interfaces
    • Customer VLAN IDs are preserved
    • Q-in-Q endpoint interface types
    • All customer traffic
    • Flexible-ethernet-services physical encapsulation type
    • Rate limiting from 10 Mbps to 100 Mbps with 10 Mbps increment

    ELAN-Hub-Spoke-QinQ-AllVLAN Service Definition

    • Multipoint Ethernet service for M Series and MX Series devices
    • Gigabit Ethernet interfaces
    • Customer VLAN IDs are not preserved
    • Q-in-Q endpoint interface types
    • All customer traffic
    • Flexible-ethernet-services physical encapsulation type
    • Rate limiting from 10 Mbps to 100 Mbps with 10 Mbps increment

    ELAN-Hub-Spoke-QinQ-AllVLAN-Normalized-All Service Definition

    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 1—a point-to-multipoint service with one hub and two spokes.

    Figure 1: Point-to-Multipoint Service with One Hub

    Point-to-Multipoint Service with
One Hub

    Configuration on Endpoint A

    The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device SFO). This device is configured as the service hub.

    interfaces {
        ge-0/0/2 {
            flexible-vlan-tagging;
            mtu 1522;
            encapsulation flexible-ethernet-services;
            unit 4 {
                encapsulation vlan-vpls;
                vlan-tags outer 4;
                family vpls {
                    filter {
                        input filter_in_ge-0/0/2_4;
                    }
                }
            }
        }
    policy-options {    
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-hm-export {
            term 1 {
                then {
                    community add export-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8;
                    accept;
                }
            }
            term 2 {
                then reject;
            }
        }
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-hm-import {
            term 1 {
                from {
                    protocol bgp;
                    community [ import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:9 import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8 ];
                }
                then accept;
            }
            term 2 {
                then reject;
            }
        }
        community export-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8 members target:65410:8;
        community import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8 members target:65410:8;
        community import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:9 members target:65410:9;
    }
    firewall {          
        family vpls {       
            filter filter_in_ge-0/0/2_4 {
                interface-specific;
                term 1 {
                    then {
                        policer policer_in_ge-0/0/2_4;
                        accept;
                    }
                }
            }
        }
        policer policer_in_ge-0/0/2_4 {
            if-exceeding {
                bandwidth-limit 10m;
                burst-size-limit 15220;
            }
            then discard;
        }
    }
    routing-instances {
        ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All {
            instance-type vpls;
            vlan-id all;
            interface ge-0/0/2.4;
            route-distinguisher 65410:15;
            vrf-import ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-hm-import;
            vrf-export ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-hm-export;
            protocols {
                vpls {
                    mac-table-size {
                        5120;
                    }
                    interface-mac-limit {
                        1024;
                    }
                    no-tunnel-services;
                    site Site_2 {
                        site-identifier 2;
                        site-preference primary;
                        interface ge-0/0/2.4;
                    }
                }
            }

    Configuration on Endpoint B

    The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device SJC). This device is a service spoke.

    interfaces {
        ge-0/0/4 {
            flexible-vlan-tagging;
            mtu 1522;
            encapsulation flexible-ethernet-services;
            unit 4 {
                encapsulation vlan-vpls;
                vlan-tags outer 4;
                family vpls {
                    filter {
                        input filter_in_ge-0/0/4_4;
                    }
                }
            }
        }
    
    policy-options {
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-export {
            term 1 {
                then {
                    community add export-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:9;
                    accept;
                }
            }
            term 2 {
                then reject;
            }
        }
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-import {
            term 1 {
                from {
                    protocol bgp;
                    community import-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8;
                }
                then accept;
            }
            term 2 {    
                then reject;
            }
        }
        community export-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:9 members target:65410:9;
        community import-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8 members target:65410:8;
    }
    
    firewall {
        family vpls {
            filter filter_in_ge-0/0/4_4 {
                interface-specific;
                term 1 {
                    then {
                        policer policer_in_ge-0/0/4_4;
                        accept;
                    }
                }
            }
        }
        policer policer_in_ge-0/0/4_4 {
            if-exceeding {
                bandwidth-limit 10m;
                burst-size-limit 15220;
            }           
            then discard;
        }
    }
    
    routing-instances {
        ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All {
            instance-type vpls;
            vlan-id all;
            interface ge-0/0/4.4;
            route-distinguisher 65410:16;
            vrf-import ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-import;
            vrf-export ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-export;
            protocols {
                vpls {
                    mac-table-size {
                        5120;
                    }
                    interface-mac-limit {
                        1024;
                    }
                    no-tunnel-services;
                    site Site_3 {
                        site-identifier 3;
                        site-preference primary;
                        interface ge-0/0/4.4;
                    }
                }

    Configuration on Endpoint Z

    The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device Beijing). Thus device is a service spoke.

    interfaces{
     ge-5/0/2 {
            unit 2 {
                encapsulation vlan-vpls;
                vlan-tags outer 2;
                family vpls {
                    filter {
                        input filter_in_ge-5/0/2_2;
                    }
                }
            }
        }               
    
    policy-options {
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-export {
            term 1 {
                then {
                    community add export-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:9;
                    accept;
                }
            }
            term 2 {
                then reject;
            }
        }
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-import {
            term 1 {
                from {
                    protocol bgp;
                    community import-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8;
                }
                then accept;
            }
            term 2 {
                then reject;
            }
        }
        community export-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:9 members target:65410:9;
        community import-comm-ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-65410:8 members target:65410:8;
    }
    firewall {
        family vpls {
            filter filter_in_ge-5/0/2_2 {
                interface-specific;
                term 1 {
                    then {
                        policer policer_in_ge-5/0/2_2;
                        accept;
                    }
                }
            }
        }
        policer policer_in_ge-5/0/2_2 {
            if-exceeding {
                bandwidth-limit 10m;
                burst-size-limit 15220;
            }
            then discard;
        }
    }
        ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All {
            instance-type vpls;
            vlan-id all;
            interface ge-5/0/2.2;
            route-distinguisher 65410:14;
            vrf-import ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-import;
            vrf-export ELAN_Hub_Spoke_QinQ_AllVLAN_Normalized_All-export;
            protocols {
                vpls {
                    mac-table-size {
                        5120;
                    }
                    interface-mac-limit {
                        1024;
                    }
                    no-tunnel-services;
                    site Site_1 {
                        site-identifier 1;
                        site-preference primary;
                        interface ge-5/0/2.2;
                    }
                }
            }
        }
    }

    ELAN-Hub-Spoke-QinQ-AllVLAN Service Definition

    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. Figure 2 shows a point-to-multipoint service with two hubs.

    The following sections show the configuration data on endpoints A, B, and Z when you use this service definition to create the service shown in Figure 2—a point-to-multipoint service with two service hubs and two spokes. The configuration for endpoint Y is not described.

    Figure 2: Point-to-Multipoint Service with Two Hubs

    Point-to-Multipoint Service
with Two Hubs

    Configuration on Endpoint A

    The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint A (device SFO). This device is configured as a service hub.

    interfaces {
        ge-0/0/2 {
            flexible-vlan-tagging;
            mtu 1522;
            encapsulation flexible-ethernet-services;
            unit 3 {
                encapsulation vlan-vpls;
                vlan-tags outer 3;
                family vpls {
                    filter {
                        input filter_in_ge-0/0/2_3;
                    }
                }
            }
        }
    
    policy-options {
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN-hm-export {
            term 1 {
                then {
                    community add export-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4;
                    accept;
                }
            }
            term 2 {    
                then reject;
            }
        }
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN-hm-import {
            term 1 {
                from {
                    protocol bgp;
                    community [ import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:5 import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 ];
                }
                then accept;
            }
            term 2 {
                then reject;
            }
        }
        community export-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 members target:65410:4;
        community import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 members target:65410:4;
        community import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:5 members target:65410:5;
    }
    
    firewall {
        family vpls {  
            filter filter_in_ge-0/0/2_3 {
                interface-specific;
                term 1 {
                    then {
                        policer policer_in_ge-0/0/2_3;
                        accept;
                    }
                }
        }
    
        policer policer_in_ge-0/0/2_3 {
            if-exceeding {
                bandwidth-limit 10m;
                burst-size-limit 15220;
            }
            then discard;
    
    }
    
        ELAN_Hub_Spoke_QinQ_AllVLAN {
            instance-type vpls;
            interface ge-0/0/2.3;
            route-distinguisher 65410:9;
            vrf-import ELAN_Hub_Spoke_QinQ_AllVLAN-hm-import;
            vrf-export ELAN_Hub_Spoke_QinQ_AllVLAN-hm-export;
            protocols {
                vpls {
                    mac-table-size {
                        5120;
                    }
                    interface-mac-limit {
                        1024;
                    }
                    no-tunnel-services;
                    site Site_2 {
                        site-identifier 2;
                        site-preference primary;
                        interface ge-0/0/2.3;
                    }
                }
            }
        }

    Configuration on Endpoint B

    The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint B (device SJC). This device is configured as a service hub.

    interfaces {
      ge-0/0/4 {
            flexible-vlan-tagging;
            mtu 1522;
            encapsulation flexible-ethernet-services
            unit 3 {
                encapsulation vlan-vpls;
                vlan-tags outer 3;
                family vpls {
                    filter {
                        input filter_in_ge-0/0/4_3;
                    }
               }
     }
    policy-options {
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN-hm-export {
            term 1 {
                then {
                    community add export-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4;
                    accept;
                }
            }
            term 2 {
                then reject;
            }
        }
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN-hm-import {
            term 1 {
                from {
                    protocol bgp;
                    community [ import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:5 import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 ];
                }
                then accept;
            }
            term 2 {
                then reject;
            }
        }
        community export-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 members target:65410:4;
        community import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 members target:65410:4;
        community import-comm-hm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:5 members target:65410:5;
    
    }
    
    firewall {
        family vpls {
            filter filter_in_ge-0/0/4_3 {
                interface-specific;
                term 1 {
                    then {
                        policer policer_in_ge-0/0/4_3;
                        accept;
                    }
                }
            }
     policer policer_in_ge-0/0/4_3 {
            if-exceeding {
                bandwidth-limit 10m;
                burst-size-limit 15220;
            }
            then discard;
        }
    
        ELAN_Hub_Spoke_QinQ_AllVLAN {
            instance-type vpls;
            interface ge-0/0/4.3;
            route-distinguisher 65410:10;
            vrf-import ELAN_Hub_Spoke_QinQ_AllVLAN-hm-import;
            vrf-export ELAN_Hub_Spoke_QinQ_AllVLAN-hm-export;
            protocols {
                vpls {
                    mac-table-size {
                        5120;
                    }
                    interface-mac-limit {
                        1024;
                    }
                    no-tunnel-services;
                    site Site_3 {
                        site-identifier 3;
                        site-preference primary;
                        interface ge-0/0/4.3;
                    }
                }
            }
        }

    Configuration on Endpoint Z

    The following statements show the interface configuration, the filter configuration, and connectivity configuration on endpoint Z (device Beijing). This device is configured as a service spoke.

    interfaces {
        ge-5/0/2 {
            flexible-vlan-tagging;
            mtu 1522;
            encapsulation flexible-ethernet-services;
            unit 1 {
                encapsulation vlan-vpls;
                vlan-tags outer 1;
                family vpls {
                    filter {
                        input filter_in_ge-5/0/2_1;
                    }
                }
            }
        }
    
    
    policy-options {
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN-export {
            term 1 {
                then {
                    community add export-comm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:5;
                    accept;
                }
            }
            term 2 {
                then reject;
            }
        }
        policy-statement ELAN_Hub_Spoke_QinQ_AllVLAN-import {
            term 1 {    
                from {
                    protocol bgp;
                    community import-comm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4;
                }
                then accept;
            }
            term 2 {
                then reject;
            }
        }
        community export-comm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:5 members target:65410:5;
        community import-comm-ELAN_Hub_Spoke_QinQ_AllVLAN-65410:4 members target:65410:4;
    }
    firewall {
        family vpls {
            filter filter_in_ge-5/0/2_1 {
                interface-specific;
                term 1 {
                    then {
                        policer policer_in_ge-5/0/2_1;
                        accept;
                    }
                }
            }
        policer policer_in_ge-5/0/2_1 {
            if-exceeding {
                bandwidth-limit 10m;
                burst-size-limit 15220;
            }
            then discard;
        }
    }
    routing-instances {
        ELAN_Hub_Spoke_QinQ_AllVLAN {
            instance-type vpls;
            interface ge-5/0/2.1;
            route-distinguisher 65410:8;
            vrf-import ELAN_Hub_Spoke_QinQ_AllVLAN-import;
            vrf-export ELAN_Hub_Spoke_QinQ_AllVLAN-export;
            protocols {
                vpls {
                    mac-table-size {
                        5120;
                    }
                    interface-mac-limit {
                        1024;
                    }
                    no-tunnel-services;
                    site Site_1 {
                        site-identifier 1;
                        site-preference primary;
                        interface ge-5/0/2.1;
                    }
                }
            }
        }

    Modified: 2017-02-02