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

No index entries found.

Outstanding Issues in Junos OS Release 12.3 for PTX Series Packet Transport Routers

The following issues currently exist in Juniper Networks PTX Series Packet Transport Routers. The identifier following the descriptions is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

General Routing

  • The PTX Series router is supposed to not generate pause frames even if it gets congestion, the behavior is to drop aggressively if it ever get queuing memory run out case. PR873028
  • This PR fixes the issue where output ifIndex being exported as 0. Unless there is a critical business need, we do not plan to backport the fix to releases earlier than 14.1. PR964745
  • Infrastructure to correct DLU SRAM parity errors on PTX Series platform. PR970797
  • In the P2MP environment with AE interface. When flapping interface continually, in rare condition, if unilist nexthop is added failure, the system does not clean up it properly, this leads to FPC crash. PR980622
  • When there is link/node protection/ECMP for RSVP/LDP transit or egress LSPs with huge scaling and continuous flapping of LSPs like auto-bandwidth case, traffic might get black-holed upon LSP re-optimizations. The issue would get triggered if the same unilist list-id (unilist list-id is a unique id for unilist nexthop) is allocated for 2 different unilist forwarding topology. This situation arises when the unilist list-id wraps around after max value of 65535. After the wraparound, if there is long living list-id (which can be due to some node/link protected LSP that has not been re-optimized for long time), the Packet Forwarding Engine assigns the same list-id during allocation (upon other LSP re-optimizations) and this will trigger the issue as the new unilist will be directed to incorrect interface. PR1043747
  • In LDP tunneling over single hop RSVP based LSP environment, after enabling "chained-composite-next-hop", the router may fail to create the chained composite next hops if the label value of VPN is equal with the label value of LDP. PR1058146
  • On egress IPv6 filter, the packets go to RE did not have the correct format. The transit packets work fine. PR1100505

MPLS

  • When issue "traceroute mpls rsvp lsp-name" from the MPLS LSP ingress node, if there are PTX routers on the LSP path, PTX would not list correct downstream router's IP in the TLV of the response packet. PR966986
  • When fast-reroute, node-link-protection or link-protection is configured, if a Shared Risk Link Group (SRLG) is associated with a link used by a LSP ingressing at a router, then on deleting the SRLG configuration from the router, the SRLG entry still stays in the SRLG table even after the re-optimization of this LSP. PR1061988
  • The point-to-multipoint (P2MP) label-switched path (LSP) is unable to re-established after certain links are down. This issue might be encountered when the links are those that contain the primary and backup LSPs for the P2MP LSP. The P2MP LSP can be restored after the links are up. PR1064710

Network Management and Monitoring

  • At some instances, the master RE fail to export some syslog facility messages to the external syslog server after RE switchover. PR898030

Routing Protocols

  • Starting in Junos OS Release 13.2, PTX Series routers accept traffic from remote sources to enable the remote source to be learned and advertised by MSDP so that receivers in other MSDP areas can join the source. To configure this feature, use the accept-remote-source configuration statement at the [edit protocols pim interface interface-name] hierarchy level. Note: On PTX Series routers requiring tunnel services, the PIM accept-remote-source configuration statement is not supported. [See accept-remote-source.] PR891500

Related Documentation

Modified: 2016-06-09