Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 14.2R8 for the PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Class of Service (CoS)

  • When member links of an aggregated Ethernet interface scatter over multiple Packet Forwarding Engines, if the FPC where member links of the aggregated Ethernet interface reside gets reset, or interface is disabled, there might be a dip in the output of SNMP walk on the aggregated Ethernet related queue MIB (such as jnxCosQstatTxedPkts). The behavior is only intermittent. PR1122343

General Routing

  • The logical interface count is incorrect and will not be repaired until a PIC restart. PR882406
  • CCG configuration change does not reprogram hardware automatically. PR896226
  • The jnxOperatingDRAMSize MIB is deprecated because this is a 32-bit MIB in bytes and the new memory size cannot be expressed using this MIB. Instead, use jnxOperatingMemory, that gives memory size in megabytes. PR949656
  • Without explicit EXP rewrite configuration, the EXP bits of the top label are rewritten on the egress MPLS frame following the default EXP rewrite profile. PR976481
  • In rare cases, a race condition might occur — a duplicate SNMP index might be assigned to the same interface. As a result, the mib2d daemon might crash. This issue should not cause any service impact. PR1033249
  • IS-IS adjacencies start to flap at a higher scale (> 2000 adjacencies) with default timers. The issue is not seen at a lower scale (<100 adjacencies). As a workaround, increase the default timers. PR1036914
  • On PTX5000 platforms with FPC2, if the 48x10G/12x40G PIC or 4X100G PIC is inserted into the FPC, continuous pmbus_get_devaccess: fpc PMBUS dev table not initialized error logs might be seen on the device due to memory corruption. These errors are mostly seen when making the OTN-related configuration change (for example, set up OTN rates). But it is not the only trigger. For example, physical interface (IFD) disable/enable might also result in the issue. The messages might disappear for some time by restarting the FPC: however, the corruption will still exist. PR1077985
  • On FPC3, strict priority mode scheduling might not be accurate with large packet sizes. PR1099387
  • The OK LED on the CB is not lighting up in the following scenarios:
    • When you Insert only one RE/CB on the router and power on the master LED glows but the OK LED does not.
    • The problem is seen when a test is done with either RE/CB on slot 0 or slot 1, leaving the other slot empty. When both slots have the RE/CB inserted, the issue is not seen.

    PR1115148

  • In certain rare conditions, FPC VoQ will wedge, which will drop packets on the ingress Packet Forwarding Engine for the PTX Series router. Because the wedge is unable to be reproduced, detection of the wedge condition is introduced so that an alarm can be raised once the wedge condition is detected in 10 seconds. PR1127958
  • PTX Series 100GbE-LR4 interfaces might flap when the reference clock switches over from "line clock" to "holdover" which is initiated by offlining the PIC on which the line clock sources reside. When PTX Series routers use line clock sources and when they do not have any external clocks from BITS-a or BITS-b, offlining the PIC, which is recovering clock from line, brings the line clock down and the reference clock is switched from line clock to holdover. This reference clock transition might cause a large clock phase shift in the 100GbE-LR4 CFP modules, and this phase shift might cause output optical pulse waveform distortion on the 100GbE-LR4 interfaces. Hence, interface flap occurs. This issue cannot be fixed by software due to a hardware limitation. PR1130403
  • Traffic might drop during Routing Engine switchover.PR1164107
  • On PTX Series platforms, the SNMP trap jnxFruRemoval(CB) is generated when the bits external clock is down or up, although the External Source Lock Acquired message is logged. The SNMP trap jnxFruRemoval(CB) is incorrect with the bits external clock down or up. The problem is that jnxFruRemoval is used when the CB is not removed. When the trap of "external clock acquired" is generated, the correct SNMP trap is Name:"jnxExtSrcLockAcquired" OID: "1.3.6.1.4.1.2636.4.2.5". However, the SNMP trap is incorrectly reported as: Name: "jnxFruRemoval" OID: "1.3.6.1.4.1.2636.4.1.5". PR1195686

Infrastructure

  • The show system memory command does not work on 64-bit systems. The implementation requires the use of a loadable kernel module to gather data. This module has known issues and has been the root cause of numerous kernel panics. In addition the pmap utility that provides the data for the CLI command has known rare crashes on 32-bit kernels. In this case, when the pmap utility crashes, no information will be reported by the CLI command. PR883953
  • When a deleting child link from an aggregated Ethernet bundle, the output statistics for the aggregated Ethernet physical interface can return 0 from the Packet Forwarding Engine and get summed incorrectly afterwards. The aggregated Ethernet logical interface, however, has correct statistics, including the residual value from the removed child logical interface. Input statistics are displayed correctly and are unaffected by this bug. PR1098264

Interfaces and Chassis

  • During a Routing Engine switchover in which OAM-AH (LFM) is configured, the peer router might get syslog entries that indicate an LFM session with the new state of up. These logs are incorrect and harmless. Though the sylog message indicates the LFM session had been dropped, that is not the case. PR775616
  • The kernel might crash when a router running a Junos OS install with the fix to PR 937774 is rebooted. This problem will not be observed during the upgrade to the Junos OS Release 14.2R8 install. It occurs late enough in the shutdown procedure; hence it should not interfere with normal operation. PR956691
  • On dual Routing Engine platforms, when adding the logical interfaces (IFLs) and committing, the device control process (dcd) on the backup Routing Engine might fail to process the configuration and keep it in memory. In some cases, it might be observed that the memory of the dcd keeps increasing on the backup Routing Engine. PR1014098
  • During subscriber login or logout, the following error log might occur on the device configured with GRES/NSR: /kernel: if_process_obj_index: Zero length TLV! /kernel: if_pfe: Zero length TLV (pp0.1073751222). PR1058958
  • Junos OS upgrade involving Junos OS Release 14.2R5 and later maintenance releases and Junos OS Release 16.1 and later main releases with a connectivity fault management (CFM) configuration can cause cfmd to generate a core file after the upgrade. This is due to the old version of /var/db/cfm.db.PR1281073

Multiprotocol Label Switching (MPLS)

  • In an RSVP-based point-to-multipoint scenario, if a sub-LSP switchover is used to bypass an LSP caused by a PIC offline, when a new sub-LSP is established using “setup-protection”, the deletion of the old sub-LSP might result in deletion of both sub-LSPs. PR1132050
  • This issue occurs if the "setup-protection" feature is enabled. If MPLS stack packets are sent out to an LSP that uses the "setup-protection" feature, the TTL of top and bypass MPLS labels will be rewritten with the TTL value of the inner MPLS label. If the TTL value of the inner MPLS label is too small, the packet might be dropped unexpectedly. This is a PTX Series router specific issue and only happens when a PTX Series router is the PLR router. PR1196064
  • If RSVP link-protection optimize-timer is enabled, routing protocol process (rpd) memory might leak in "TED cross-connect" when a bypass LSP is being optimized. PR1198775

Platform and Infrastructure

  • Adaptive load-balance functionality is supported only for unicast traffic. If the aggregate bundle contains logical interfaces for bridge or VPLS domains, flooded traffic might be dropped. PR821237
  • On MX Series routers, parity memory errors might occur in pre-classifier engines within an MPC. Packets will be silently discarded. Because such errors are not reported, they are more difficult to diagnose. The correct behavior is for CM errors such as syslog messages and alarms to be raised when parity memory errors occur. PR1059137
  • When sampling is configured, if AS paths change over a period of time in the network, the stale AS paths might be seen in the sampler database of JNH memory. PR1189689

Routing Protocols

  • When there are two paths for the same route, the route gets pointed to the unilist next hop which in turn gets pointed to two separate unicast next hops. The route is determined by OSPF and BFD enabled on one of the paths, which runs through a Layer 2 circuit path. When the link on the l2circuit gets cut, the link flap is informed by BFD as well as through OSPF LSAs. Ideally the BFD should inform the link-down event before the OSPF LSA. But in the current situation, the OSPF LSAs update the current event just before BFD. Because of this reason, the route points to a new unilist next hop with the weights swapped. But the unicast next hop for which the L3 link is down, gets added to the unilist next hop. The BFD determines the link to be up, and hence updates the weights incorrectly, causing traffic loss. Once the BFD link down event is processed at OSPF protocol level, the route only points to the unicast next hop and hence the traffic flows through the currently active link. The traffic outage would occur for less than a second during FRR. As a workaround, this issue can be avoided if the BFD keepalive intervals are maintained around 50 ms with a multiplier of 3 as opposed to 100 ms with a multiplier of 3. PR1119253
  • In a multicast environment, when the rendezvous point (RP) is a first-hop router (FHR) and has MSDP peers, when the rpf interface on the RP changes to an MSDP-facing interface, a multicast discard route is installed and traffic loss is seen because multicast traffic is still on the old rpf interface. PR1130238

Modified: 2017-12-12