Tricolor Marking Limitations

The following limitations apply to TCM:

• When you enable TCM on a 10-port Gigabit Ethernet PIC or a 10-Gigabit Ethernet PIC, for queues 6 and 7 only, the output of the show interfaces queue interface-name command does not display the number of queued bytes and packets, or the number of bytes and packets dropped due to RED. If you do not configure tricolor marking on the interface, these statistics are available for all queues.
• When you enable TCM, Transmission Control Protocol (TCP)-based configurations for drop profiles are rejected. In other words, you cannot include the protocol statement at the [edit class-of-service schedulers scheduler-name drop-profile-map] hierarchy level. The result is that drop profiles are applied to packets with the specified PLP and any protocol type.
• On Gigabit Ethernet IQ PICs, for IEEE-802.1 rewrite rules, only two loss priorities are supported. Exiting packets with medium-high loss priority are treated as high, and packets with medium-low loss priority are treated as low. In other words rewrite rules corresponding to high and low apply instead of those corresponding to medium-high and medium-low. For IQ PICs, you can only configure one IEEE 802.1 rewrite rule on a physical port. All logical ports (units) on that physical port should apply the same IEEE 802.1 rewrite rule.
• When some PICs with Frame Relay encapsulation mark a packet with high loss priority, the packet is treated as having medium-high loss priority on T-series and M320 platforms with Enhanced II FPCs and the T640 platform with Enhanced Scaling FPC4.
• TCM is not supported on aggregated Ethernet and aggregated SONET/SDH interfaces.
• In a single firewall filter term, you cannot configure both the loss-priority action modifier and the three-color-policer action modifier. These statements are mutually exclusive.

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.