Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Resolved Issues in Junos OS Release 12.3 for ACX Series Routers

The following issues have been resolved in Junos OS Release 12.3 for Juniper Networks ACX Series routers. The identifier following the descriptions is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

Resolved Issues

There are no resolved issues in Junos OS Release 12.3R12.

Previous Releases

Release 12.3R11

There are no resolved issues in Junos OS Release 12.3R11.

Release 12.3R10

General Routing

  • In case of any problem during boot-up, box will automatically reboot to Alternate slice and give customer chance to recover the primary slice by snapshot command. If autosnapshot is enabled, snapshot will be taken automatically on successful boot to Alternate slice. PR839286
  • CFM MEP over L2VPN/L2 circuit on ACX Series no longer requires no-control-word to be configured under L2VPN or l2-circuit hierarchy. PR864317
  • When 16xCHE1/T1 MIC is online Routing Engine driven BFD sessions may flap. PR892011
  • AI-Scripts bundle install fails on ACX Series platform running Junos OS release 12.3X52. PR925102
  • Image download via FTP on to ACX Series through inband takes a long time when compared to FXP. Changing the receive rate towards the CPU has helped in improving the transfer rate. PR979858

Release 12.3R9

Layer 2 Features

  • If "maintain-subscriber" knob is enabled on the router, DHCPv6 server/relay might be unable to process any packet if deactivate and then activate the routing instance, which means the subscribers can not get the IPv6 addresses. Note, even with the fix, the results of this scenario are also expected if with "maintain-subscriber" knob enabled, Consider using the workaround to avoid this issue. PR1018131: This issue has been resolved.

MPLS

  • When the size of a Routing Engine generated packet going over an MPLS LSP is larger than MTU (i.e. MTU minus its header size) of an underlying interface, and the extra bytes leading to IP-fragmentation are as small as <8 bytes, then that small-fragment will be dropped by kernel and lead to packet drop with kernel message "tag_attach_labels(): m_pullup() failed". For example - If SNMP Response with specific size fall into above mentioned condition, then small fragment will be dropped by kernel and eventually the SNMP response will fail. PR1011548: This issue has been resolved.

Release 12.3R8

General Routing

  • jdhcpd crash triggered by DHCP client re-discovering on different vlan. PR913823: This issue has been resolved.

Release 12.3R7

There are no resolved issues in Junos OS Release 12.3R7.

Release 12.3R6

Interfaces and Chassis

  • On ACX Series-based FPC, one-way packet loss might occur when bridge-domain is stitched to l2circuit via logical tunnel (LT) interface. PR922375: This issue has been resolved.

Release 12.3R5

Junos Scope

  • Heater status shows to be on under normal operating temperatures. This is a cosmetic issue. PR898079: This issue has been resolved.
  • This is just an SNMP Trap generated due to inconsistency in temperature parameters and thresholds. PR859507: This issue has been resolved.

Release 12.3R4

Interfaces and Chassis

  • When you issue the show system memory command on ACX routers, the "unable to load pmap_helper module: No such file or directory" error message is displayed in the output of the command. PR737616: This issue has been resolved.
  • CFM MEP over L2VPN/L2 circuit on ACX no longer requires no-control-word to be configured under L2VPN or l2-circuit hierarchy. PR864317 and PR801746: This issue has been resolved.
  • When the data-tlv size is set to <=54 then DM frames are considered as invalid. PR800605: This issue has been resolved.

MPLS

  • When an ACX Series router is working as a transit router in an MPLS network, then the traceroute response from router provides "nexthop" information as "Unhelpful". PR669005: This issue has been resolved.

Release 12.3R2

Interfaces and Chassis

  • A commit for configuration change that simultaneously disables RSVP and a point-to-point interface, such as so, t1, and atm, might generate a core file on the routing protocol process. To solve this issue, do not commit a configuration change that simultaneously disables RSVP and a point-to-point interface. Instead, disable RSVP and point-to-point interfaces in separate config commits. PR782174: This issue has been resolved.
  • On an L2circuit, when any one of the logical interfaces on the PE routers is disabled after changing VLAN-tagging to flexible VLAN tagging or vice versa on a CE router, the pseudowires return an mtu mismatch error. As a workaround, disable and then enable all the logical interfaces on the PE routers. PR834466: This issue has been resolved.

Related Documentation

Modified: 2016-06-09