Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Known Limitations in Junos OS Release 12.2 for ACX Series Routers

The following software limitations currently exist in Juniper Networks ACX Series Universal Access Routers. The identifier following the descriptions is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

Class of Service (CoS)

• When the rewrite-rules statement is configured with the dscp or the inet-precedence option at the [edit class-of-service interfaces] hierarchy level, the expectation is that the DiffServ code point (DSCP) or IPv4 precedence rewrite rules take effect only on IP packets. However, in addition to the IP packets, the DSCP or IPv4 rewrite takes effect on the IP header inside the Ethernet pseudowire payload as well. [PR664062: This is a known limitation.]

Interfaces and Chassis

• When the differential-delay number option is configured in the ima-group-option statement at the [edit interfaces at-fpc/pic/ima-group-no] hierarchy level, with a value less than 10, some of the member links might not come up and the group might remain down resulting in traffic loss. A workaround is to keep the differential delay value above 10 for all IMA bundles. [PR726279: This is a known limitation.]
• On ACX1000 and ACX2000 routers, the outbound host traffic does not show the respective interface queue statistics as per the configuration. This is due to a hardware limitation. However, the actual queuing and scheduling happens as per the configuration. PR772149: This is a known limitation.]

Multiprotocol Label Switching (MPLS)

• The scaling numbers for pseudowires and MPLS label routes published for the ACX Series routers are valid only when the protocols adopt graceful restart. In case of non-graceful restart, the scaling numbers would become half of the published numbers. [PR683581: This is a known limitation.]

Routing Policy and Firewall Filters

• On ACX Series routers, packet drops in the egress interface queue are also counted as input packet rejects under the Filter statistics section in the output of the show interface extensive command when it is run on the ingress interface. [PR612441: This is a known limitation.]
• When the statistics statement is configured on a logical interface—for example, the [edit interface name-X unit unit-Y]; when the (policer | count | three-color-policer) statements are configured in a firewall filter for the family any—for example, the [edit firewall family any filter filter-XYZ term term-T then] hierarchy level; and when the configured filter-XYZ is specified in the output statement of the logical interface at the [edit interface name-X unit unit-Y filter] hierarchy level, the counters from the configuration of another firewall family filter on the logical interface do not work. [PR678847: This is a known limitation.]
• The policing rate can be incorrect if the following configurations are applied together:
  • The policer or three-color-policer statement configured in a firewall filter—for example, filter-XYZ at the [edit firewall family any filter filter-XYZ term term-T then] hierarchy level, and filter-XYZ is specified as an ingress or egress firewall filter on a logical interface— for example, interface-X unit-Y at the [edit interface interface-X unit unit-Y filter (input|output) filter-XYZ] hierarchy level.
  • The policer or three-color-policer statement configured in a firewall filter—for example, filter-ABC at the [edit firewall family name-XX filter filter-ABC term term-T then] hierarchy level, and filter-ABC is configured as an ingress or egress firewall filter on a family of the same logical interface interface-X unit-Y at the [edit interface interface-X unit unit-Y family name-XX filter (input|output) filter-ABC] hierarchy level.

  Note: If one of these configurations is applied independently, then the correct policer rate is observed.

  [PR678950: This is a known limitation.]

Related Documentation

• New Features in Junos OS Release 12.2 for ACX Series Routers
• Errata and Changes in Documentation for Junos OS Release 12.2 for ACX Series Routers
• Outstanding Issues in Junos OS Release 12.2 for ACX Series Routers
• Resolved Issues in Junos OS Release 12.2 for ACX Series Routers
• Upgrade and Downgrade Instructions for Junos OS Release 12.2 for ACX Series Routers