Technical Documentation

Configuring a Static VLAN Subscriber Interface over Aggregated Ethernet

You can configure static or dynamic hierarchical class of service (CoS) on a subscriber link represented by a static virtual LAN (VLAN) stacked on a two-link aggregated Ethernet logical interface.

To configure a subscriber interface using a static VLAN interface over a two-link aggregated Ethernet logical interface:

  1. Define the number of aggregated Ethernet interfaces on the router:
    [edit]
    chassis {
    aggregated-devices {
    ethernet {
    device-count number;
    }
    }
    }
  2. Configure the two-link aggregated Ethernet logical interface to serve as the underlying interface for the static VLAN subscriber interface.
    [edit]
    interfaces {
    ethernet-interface-name { # Configure the first link
    (fastether-options | gigether-options) { # Specify the EQ DPC port type
    802.3ad { # Specify the aggregated Ethernet logical interface
    aex; # Specify 0 through 15
    primary; # Optional: to support 1:1 active/backup redundancy
    }
    }
    }
    ethernet-interface-name { # Configure the second link
    (fastether-options | gigether-options) {
    802.3ad {
    aex;
    backup; # Optional: to support 1:1 active/backup redundancy
    }
    }
    }
    }

    Note: Optionally, you can configure the aggregated Ethernet logical interface to support one-to-one active/backup link redundancy. However, you cannot configure the aggregated Ethernet logical interface to support load balancing with hierarchical CoS. For more information about configuring aggregated Ethernet interfaces, see the JUNOS Network Interfaces Configuration Guide.

  3. Configure the two-link aggregated Ethernet logical interface to serve as the underlying interface for the static VLAN interface.

    For the static VLAN interface to support static or dynamic hierarchical CoS, the link aggregation (LAG) bundle must operate in hierarchical scheduler mode, both links must operate in link-protect mode, and the Link Aggregation Control Protocol (LACP) must be active:

    [edit]
    interfaces {
    aex { # Configure the LAG bundle
    hierarchical-scheduler; # Enable hierarchical scheduler mode
    aggregated-ether-options {
    link-protection; # Enable static link protection
    minimum-links number;
    link-speed speed;
    lacp { # LACP “active” for hierarchical CoS
    active; # But LACP “passive” for firewall filters and policy filters
    }
    }
    }
    }
  4. Attach static or dynamic traffic shaping and scheduling parameters at the aggregated Ethernet logical interface or its underlying physical interface:
    class-of-service { # H-CoS on AE with 1:1 link protection
    schedulers {
    scheduler-name { # Configure a scheduler
    ... scheduler_configuration ...
    }
    ... additional_scheduler_configurations ...
    }
    scheduler-maps {
    scheduler-map-name { # Configure a scheduler map
    forwarding-class class-name scheduler scheduler-name;
    ... additional_queue_configurations ...
    }
    ... additional_scheduler_map_configurations ...
    }
    traffic-control-profiles {
    profile-name { # Configure a traffic-control profile
    scheduler-map scheduler-map-name;
    ... other_traffic_shaping_parameters ...
    }
    ... additional_traffic_control_profile_configurations ...
    }
    interfaces {
    aex { # Attach CoS parameters this AE bundle
    output-traffic-control-profile profile-name; # Underlying physical interface(s)
    unit logical-unit-number {
    output-traffic-control-profile profile-name; # Logical interface
    }
    }
    }
    }

    You can include the statements at the following hierarchy levels:

    • [edit]
    • [edit dynamic-profiles profile-name]

Published: 2009-07-16