Configuring CoS in Junos Fusion Enterprise
Junos Fusion significantly expands the number of available network interfaces on an aggregation device by allowing the aggregation device to add interfaces through interconnections with satellite devices. The entire system—the interconnected aggregation device and satellite devices—is called Junos Fusion. Junos Fusion simplifies network administration by appearing in the network topology as a single device, and the single device is managed from a single IP address.
This topic describes how to configure CoS on the different types of ports in Junos Fusion.
This topic covers:
Configuring Behavior Aggregate Classifiers on Satellite Device Extended Ports
Normally, you apply a behavior aggregate (BA) classifier to
a logical interface on an EX9200 device at the [edit class-of-service
interfaces interface-name unit logical-unit-number]
hierarchy level. When traffic from a satellite device extended
port reaches the aggregation device, the BA classifier configured
for the logical interface level of the satellite device extended port
is applied the same as it is for traffic from other non-extended ports
to help determine the forwarding class of the traffic; policers and
multifield classifiers can also factor in determining the forwarding
class of the traffic. When the aggregation devices sends the traffic
out to the satellite device, the forwarding class is carried in the
801.2BR header. The satellite device then uses the forwarding class
to select the output queue at the egress extended port.
You can also apply a BA classifier at the physical interface level of an extended port. This classifier is used to determine the output queue at the uplink port of the satellite device.
IP precedence classifiers are not supported on extended ports at the physical interface level. DSCP classifiers are supported, however.
You cannot apply a physical interface-level classifier on an EX9200 local port.
To add a behavior aggregate classifier to the physical interface level of a satellite device extended port in Junos Fusion:
In the above configuration example, packets entering port xe-100/0/33
with a DSCP value of 001010
will be assigned a forwarding
class of best-effort-3
to select the output queue at the
uplink port as the packet travels from the satellite device to the
aggregation device.
See Also
Configuring Rewrite Rules on Satellite Device Extended Ports
You apply rewrite rules to logical interfaces on satellite device extended ports.
To add a rewrite rule to a satellite device extended port in a Junos Fusion:
In Junos OS, rewrite rules only look at the forwarding class
and packet loss priority of the packet (as assigned by a behavior
aggregate or multifield classifier at ingress), not at the incoming
CoS value, to determine the CoS value to write to the packet header
at egress. The above configuration means that, for any packet exiting
the xe-108/0/47.0 interface that has a forwarding class of best-effort
and a packet loss priority of low
, the ieee-802.1 CoS
value will be rewritten to 010
.
See Also
Changing the Default Scheduling Policy on an Aggregated Device Cascade Port
When a cascade port is created, two logical interfaces are automatically created:
One in-band management logical interface (assigned unit 32769) for traffic that only flows between the aggregation device and the satellite devices, such as keepalives, for provisioning information, and for software updates.
One for data logical interface (assigned unit 32770) for regular traffic that flows into and out of Junos Fusion.
Let’s say, for example, that interface xe-0/0/1 is configured
as a cascade port. The command show interfaces xe-0/0/1 terse
produces output similar to the following:
user@ex9200-agg-device# run show interfaces xe-0/0/1 terse Interface Admin Link Proto Local Remote xe-0/0/1 up up xe-0/0/1.32769 up up inet 10.0.0.5/30 xe-0/0/1.32770 up up bridge
The control logical interface (unit 32769) is automatically assigned an internal traffic control profile (__cp_control_tc_prof) that guarantees 50 Mbps of bandwidth for the logical interface, a 10 percent shaping rate, and the default scheduling policy. The default scheduling policy is applied to the data logical interface. For example:
user@ex9200-agg-device# run show class-of-service interface xe-0/0/1 Physical interface: xe-0/0/1, Index: 144 Maximum usable queues: 8, Queues in use: 4 Scheduler map: <default>, Index: 2 Congestion-notification: Disabled Logical interface: xe-0/0/1.32769, Index: 344 Object Name Type Index Traffic-control-profile __cp_control_tc_prof Output 17227 Classifier ipprec-compatibility ip 13 Logical interface: xe-0/0/1.32770, Index: 343 Object Name Type Index Scheduler-map <default> Output 2
and:
user@ex9200-agg-device# run show class-of-service scheduler-hierarchy interface xe-0/0/1 Interface/ Shaping Guarnteed Guaranteed/ Queue Excess Resource name rate rate Excess weight weight kbits kbits priority high/low xe-0/0/1.32770 10000000 0 1 1 BE 10000000 0 Low Low 118 NC 10000000 0 Low Low 6 xe-0/0/1.32769 1000000 50000 62 62 BE 1000000 47500 Low Low 118 NC 1000000 2500 Low Low 6
You can create custom forwarding classes and schedulers for the data logical interface by applying a customer scheduler map to that logical interface. For example, to apply a customer scheduler policy to the data logical interface: