1. Apply the QoS schedulers/queues to the at-1/0/0 interface that has the ppp
session. (Since the 'ppp' interface isn't real).
Queues are generally only associated with the physical interface hardware. This
is what we do for our managed xDSL connections:
class-of-service {
interfaces {
at-1/0/0 {
scheduler-map QoS;
}
}
}
show interfaces queue at-1/0/0
Physical interface: at-1/0/0, Enabled, Physical link is Up
Interface index: 146, SNMP ifIndex: 527
Description: ADSL 2+ Annex M - 20M/3M
Forwarding classes: 8 supported, 4 in use
Egress queues: 8 supported, 4 in use
2. VLANs - Not quite sure what you're after here. a 'vlan.xxx' interface isn't
physical either. (see #1 above)
It's only if the L2 VLAN associated with the L3 vlan.xxx interface egresses the
box on a physical port would you place your queues.
i.e. fe-0/0/2, fe-0/0/3 etc..
class-of-service {
interfaces {
fe-* {
scheduler-map QoS;
}
ge-* {
scheduler-map QoS;
}
}
}
- CK.
On 2012-03-31, at 6:47 AM, Thomas Eichhorn wrote:
But it seems I neither have classes (ingress or egress) on
vlan-interfaces nor on pp interfaces, eg.
te@gw.ber2 show interfaces queue pp0
Egress queue statistics are not applicable to this interface.
Maybe I am stuck with the concept, but how do I achieve to control
traffic leaving a pp0 interface? I have some DSL with PPPoE on this box
and would like to prioritize ssh.
Any tips?
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
