In which configuration hierarchy must the hierarchical-scheduler parameter be applied to enable
hierarchical scheduling?
A.
[edit class-of-service]
B.
[edit class-of-service <interface_name>]
C.
[edit interfaces]
D.
[edit interfaces <interface_name>]
Explanation:
Answer is B
https://www.juniper.net/documentation/en_US/junos14.2/topics/reference/configuration-statement/hierarchical-scheduler-edit-cos.html
Can’t be B,
That is not a legitimate command.
The command would have to be
edit class-of service interfaces
I think it should be edit class-of-service.
As the command structure would be something like
[code]
root@P1# show
forwarding-classes {
queue 0 best-effort;
queue 1 ef;
queue 2 af;
queue 3 NC;
}
interfaces {
ge-0/0/1 {
scheduler-map data-smap;
}
}
scheduler-maps {
data-smap {
forwarding-class best-effort scheduler be_sch;
}
}
schedulers {
be_sch {
transmit-rate percent 10;
buffer-size {
remainder;
}
priority low;
}
}
[/code]
http://www.juniper.net/techpubs/en_US/junos12.3/information-products/topic-collections/config-guide-cos/config-guide-cos.pdf
Typo,
D
[edit interfaces interface_name]
Configuring the Interfaces
The keyword to configure hierarchical schedulers is at the physical interface level, as is
VLAN tagging and the VLAN IDs. In this example, the interface sets are defined by logical
interfaces (units) and not outer VLAN tags. All VLAN tags in this example are customer
VLAN tags.
[edit interface ge-1/0/0]
hierarchical-scheduler;
vlan-tagging;
unit 0 {
vlan-id 100;
}
unit 1 {
vlan-id 101;
}
unit 2 {
vlan-id 102;
}
unit 3 {
vlan-id 103;
}
unit 4 {
vlan-id 104;
}
answer=b
Hierarchy Level
[edit class-of-service I
Note: To enable hierarchical scheduling on MX80 routers, configure the hierarchical-scheduler statement at each member physical interface level of a particular aggregated Ethernet interface as well as at that aggregated Ethernet interface level. On other routing platforms, it is enough if you include this statement at the aggregated Ethernet interface level.
nterfaces]
Answer is D
http://www.juniper.net/techpubs/en_US/junos11.4/topics/example/cos-subscriber-access-basic.html
Configure the subscriber interface in the [edit interfaces] hierarchy. Enable hierarchical scheduling for the interface.
interfaces {
ge-2/2/0 {
hierarchical-scheduler;
vlan-tagging;
unit 100 {
vlan-id 100;
family inet {
unnumbered-address lo0.0 preferred-source-address 100.0.0.1;
}
}
}
}