Understanding CoS CLI Configuration Statements on PTX Series Routers
PTX Series Packet Transport Routers have no new Junos OS CLI configuration statements. However, some statements or statement options supported on other platforms are not supported or may not have effect on PTX Series devices. These exceptions are summarized here.
[edit chassis] Hierarchy Level
The following statement is not applicable to PTX Series Packet Transport Routers. There are always eight queues available. However, if there is a requirement to use only four of eight queues, you can do this by configuring the forwarding class to queue mapping, as appropriate.
[edit chassis fpc slot-number pic pic-number],
max-queues-per-interface (4 | 8);
The following CLI is not applicable to PICs supported on PTX Series Packet Transport Routers:
[edit chassis fpc slot-number pic pic-number],
q-pic-large-buffer {
[large-scale | small-scale]
}
On PTX Series Packet Transport Routers, buffer occupancy is computed as weighted average. However, configuration of weight at the PIC level is not supported. The default weights are applied.
[edit chassis fpc slot-number pic pic-number],
red-buffer-occupancy {
weighted-averaged [ instant-usage-weight-exponent ] weight-value;
}
The following CLI is not applicable to PICs supported on PTX Series Packet Transport Routers:
[edit chassis fpc slot-number pic pic-number],
traffic-manager {
egress-shaping-overhead number;
ingress-shaping-overhead number;
mode session-shaping;
}
[edit class-of-service] Hierarchy Level
The following CLI is not applicable to PTX Series Packet Transport Routers because there are no separate fabric queues and egress queues:
fabric {
scheduler-map {
priority (high | low) scheduler scheduler-name;
}
}
The following CLI does not support the priority and policing-priority options.
forwarding-classes {
class queue-num queue-number priority (high | low);
queue queue-number class-name priority (high | low) [ policing-priority (premium | normal) ];
}
The following statements are not supported on PTX Series Packet Transport Routers:
inet-precedencerewriteRewrite of both exp and inet-precedence fields for VPN and non-VPN traffic that use the
mpls-inet-bothandmpls-inet-both-non-vpnprotocol types.exp-push-push-pushandexp-swap-push-pushrulesinput-scheduler-mapandinput-shaping-rateThe physical interface scheduler is applied on the Packet Forwarding Engine, hence the
scheduler-map-chassisstatement is not applicable.
interfaces {
interface-name {
input-scheduler-map map-name;
input-shaping-rate rate;
scheduler-map-chassis map-name;
unit logical-unit-number {
rewrite-rules{
inet-precedence (rewrite-name | default) protocol
protocol-types;
exp (write-name | default) protocol protocol-types;
exp-push-push-push default;
exp-swap-push-push default;
}
}
}
}
In the following CLI, only the inet-precedence statement
is not supported.
rewrite-rules {
(dscp | dscp-ipv6 | exp | ieee-802.1 |ieee-802.1ad |inet-precedence) rewrite-name {
import (rewrite-name | default);
forwarding-class class-name {
loss-priority level code-point (alias | bits);
}
}
}
Classifiers on routing instances are not supported on PTX Series Packet Transport Routers because L3VPN is not supported. Hence, the following CLI is not applicable.
[edit class-of-service]
routing-instances routing-instance-name {
classifiers {
exp (classifier-name | default);
dscp (classifier-name | default);
dscp-ipv6 (classifier-name | default);
}
}
The following limitations apply to statements under schedulers on PTX Series Packet Transport Routers:
protocol (non-tcp | tcp) is not supported for drop-profile-map. The any option is supported.
excess-priority is not supported.
rate-limit is supported for transmit-rate. It is applied only when schedulers are configured as strict-high.
schedulers (CoS) { scheduler-name { buffer-size (percent percentage | remainder | temporal microseconds); drop-profile-map loss-priority (any | low | medium-low | medium-high high) protocol (any ) drop-profile profile-name; priority priority-level; transmit-rate (rate | percent percentage | remainder) <exact | rate-limit>; } }
Configurations that are supported only on Gigabit Ethernet IQ PICs, channelized IQ PICs, and so forth are not applicable to PTX Series Packet Transport Routers. These PICs are not supported on this platform. Those CLIs are not listed here.
[edit firewall] Hierarchy Level
In the following CLI, the dscp clause is not supported.
family family-name { filter filter-name { term term-name { from { match-conditions; } then { dscp 0; forwarding-class class-name; loss-priority (high | low); three-color-policer { (single-rate | two-rate) policer-name; } } } }