Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Example: Configuring a Static Subscriber Interface on a VLAN Interface over Aggregated Ethernet

date_range 06-Dec-23

This example shows how you can configure a subscriber interface using a static virtual LAN (VLAN) stacked on a two-link aggregated Ethernet logical interface. In this example, the underlying aggregated Ethernet logical interface is configured for one-to-one active/backup redundancy at the DPC level, and per-subscriber static hierarchical class-of-service (CoS) is configured by applying CoS parameters at the aggregated Ethernet logical interface.

  1. Define the number of aggregated Ethernet interfaces on the router.

    In this example, only one aggregated Ethernet logical interface is configured on the router.

    content_copy zoom_out_map
    [edit]
    chassis {
        aggregated-devices {
            ethernet {
                device-count 1;
            }
        }
    }
    
  2. Configure ae0, a two-link aggregated Ethernet logical interface to serve as the underlying interface for the static VLAN subscriber interface. In order to support hierarchical CoS, the physical ports must be on EQ DPCs in MX Series routers.

    In this example, the LAG bundle is configured for one-to-one active/backup link redundancy. To support link redundancy at the DPC level, the LAG bundle attaches ports from two different EQ DPCs.

    content_copy zoom_out_map
    [edit]
    interfaces {
        ge-5/0/3 {
            gigether-options {
                802.3ad {
                    ae0;
                    primary;
                }
            }
            ge-5/1/2 {
                gigether-options {
                    802.3ad {
                        ae0;
                        backup;
                    }
                }
            }
        }
    }
    
  3. Configure ae0 to serve as the underlying interface for the static VLAN interface.

    content_copy zoom_out_map
    [edit]
    interfaces {
        ae0 {
            hierarchical-scheduler;
            aggregated-ether-options {
                link-protection;
                minimum-links 1;
                link-speed 1g;
                lacp {
                    active;
                }
            }
        }
    }
    
  4. Configure static traffic-shaping and scheduling parameters.

    content_copy zoom_out_map
    [edit]
    class-of-service {
        forwarding-classes { # Associate queue numbers with class names
            queue 0 be;
            queue 1 e;
            queue 2 af;
            queue 3 nc;
        }
        schedulers { # Define output queue properties
            scheduler_be {
                transmit-rate percent 30;
                buffer-size percent 30;
            }
            scheduler_ef {
                transmit-rate percent 40;
                buffer-size percent 40;
            }
            scheduler_af {
                transmit-rate percent 25;
                buffer-size percent 25;
            }
            scheduler_nc {
                transmit-rate percent 5;
                buffer-size percent 5;
            }
        }
        scheduler-maps { # Associate queues with schedulers 
            smap_2 {
                forwarding-class be scheduler_be;
                forwarding-class ef scheduler_ef;
                forwarding-class-af scheduler_af;
                forwarding-class-nc scheduler_nc;
            }
        }
    }
    
  5. Attach static CoS to the physical and logical interfaces of the aggregated Ethernet interface.

    In this example, three traffic control profiles are defined, but only two profiles are applied to the static VLAN subscriber interface over aggregated Ethernet:

    • The tcp_for_ae_device_pir_500m profile defines a shaping rate, and it is applied to both of the underlying physical interfaces (ge-5/0/3 and ge-5/1/2).

    • The tcp-for-ae_smap_video_pir_20m_delay_30m profile defines a scheduler map, a shaping rate, and a delay buffer rate, and it is applied to one of the logical interfaces on the aggregated Ethernet bundle (ae0.0).

    content_copy zoom_out_map
    [edit]
    class-of-service {
        traffic-control-profiles { # Configure traffic shaping and scheduling profiles
            tcp_for_ae_device_pir_500m {
                shaping-rate 20m;
            }
            tcp_for_ae_smap_video_pir_20m_delay_30m {
                scheduler-map smap_video;
                shaping-rate 20m;
                delay-buffer-rate 30m;
            }
            tcp_for_ae_smap_video_cir_50m_delay_75m {
                scheduler-map smap_video;
                guaranteed-rate 50m;
                delay-buffer-rate 75m;
            }
        }
        interfaces { # Apply two traffic-control profiles to the LAG
            ae0 { # Two underlying physical interfaces on separate EQ DPCs
                output-traffic-control-profile tcp-for-ae_device_pir_500m;
                unit 0 { # One of the two logical interfaces on ’ae0’
                    output-traffic-control-profile tcp-for-ae_smap_video_pir_20m_delay_30m;
                }
            }
        }
    }
    
footer-navigation