[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Drop Profiles

You can configure random early detection (RED) on LSQ interfaces as in other CoS scenarios. To configure RED, include one or more drop profiles and attach them to a scheduler for a particular forwarding class. For more information about RED profiles, see the JUNOS Class of Service Configuration Guide.

The LSQ implementation performs tail RED. It supports a maximum of 256 drop profiles per PIC. Drop profiles are configurable on a per-queue, per-loss-priority, and per-TCP-bit basis.

You can attach scheduler maps with configured RED drop profiles to any LSQ logical interface: an MLPPP bundle, an FRF.15 bundle, or an FRF.16 DLCI. Different queues (forwarding classes) on the same logical interface can have different associated drop profiles.

The following example shows how to configure a RED profile on an LSQ interface:

class-of-service {
drop-profiles {
drop-low {
# Configure suitable drop profile for low loss priority
...
}
drop-high {
# Configure suitable drop profile for high loss priority
...
}
}
scheduler-maps {
schedmap {
# Best-effort queue will use be-scheduler
# Other queues may use different schedulers
forwarding-class be scheduler be-scheduler;
...
}
}
schedulers {
be-scheduler {
# Configure two drop profiles for low and high loss priority
drop-profile-map loss-priority low protocol any drop-profile drop-low;
drop-profile-map loss-priority high protocol any drop-profile drop-high;
# Other scheduler parameters (buffer-size, priority,
# and transmit-rate) are already supported.
...
}
}
interfaces {
lsq-1/3/0.0 {
# Attach a scheduler map (that includes RED drop profiles)
# to a LSQ logical interface.
scheduler-map schedmap;
}
}
}

Note: The RED profiles should be applied only on the LSQ bundles and not on the egress links that constitute the bundle.

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]