Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Known Limitations

Learn about known limitations in this release for MX Series routers.

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

General Routing

  • When do a snmpwalk on chassisd-related mib (for example: jnxOperatingTable) on MX104, the chassisd cpu may go up to 70%. In MX104 device total number of entries fetched during this walk is about 1000 entries and above. This snmpwalk takes more time to complete the SNMP polling. Due to MX104 available memory and processor we could see chassisd spike during snmpwalk. PR1604901

  • The time delay on GNF reconnect is due to socket drop on alarmd and chassis went for a reconnect, during this reconnect process the ready messages from GNFs are ignored until the chassis reconnect timer is expired. The socket drop on alarmd and reconnect is expected while performing GRES. PR1771319

  • The error message Received IFD attach for interface name with PIC in Offline or Offline wait state.Ignore it , IFFPC: ifd detach returned error 7 is usually observed when a PIC reconfiguration is triggered while the IFDs are still getting installed at the linecard. PIC reconfiguration is mainly due to a PIC mode change. Before triggering a pic mode change, in addition to checking the state of the pic mode i.e if the PIC is online, also verify that the IFDs are attached correctly either by allowing adequate delay between PIC bounce (approximately 3 to 5 minutes) or observing logs.PR1774974

  • The error message is observed when a PIC reconfiguration is triggered while the IFDs are still getting installed at the linecard. PIC reconfiguration is mainly due to a pic mode change. Before triggering a pic mode change, in addition to checking the state of the pic mode i.e if the PIC is online, also verify that the IFDs are attached correctly either by allowing adequate delay between PIC bounce (~3-5mins) or observing logs.PR1780251

  • If there is i2cs upgrade failure , do not run online reload command. please re run the jfirmware upgrade. in case if you executed online reload command after I2cs upgrade failure please jack out jack in the line card before running the jfirmware upgrade again. PR1783364

  • If SGRP over subscription is configured for a BNG-UP port which hardware doesn't support over subscription it still accepts the port into the SGRP. The result is subscribers are not handled properly. PR1791676

  • 1PPS performance drop is seen during clksyncd process restart with 1588 default profile. Its a baseline Mx Aloha line card behaviour. PR1796244

  • show system license output does not display hardware based licensing details. show system license bandwidth flex-only output displays linecard specific bandwidth details. It makes the calculation very complicated to add advance/premium details to this output. Tier can be chassis, linecard or port based. Bandwidth details is for all ports of the linecard irrespective of the tier of each port.PR1797309

  • 40g interface doesnt support EM policy feature but it will still display in the cli output of show chassis temp-threshold as it gets created as "et" interface. PR1807219

Layer 2 Ethernet Services

  • Issue was seen when test was done back to back GRES within 5mins time. this is expected behavior from the system as per current architecture. Suggestion is to wait for sometime before maybe 10 minutes or so for subsequent GRES. PR1801234

Platform and Infrastructure

  • When global level changes are made like changing Mac-age, with large scale and high CPU a watchdog core is generated without any functional impact. The config change is pushed from l2alm to pfe, which loops through all the RTTs and associated bd and ifbd. If the process is not yielded within 240sec, the pfeman watchdog is called in and writes a core. PR1775966

Services Applications

  • In Junos OS Release 17.4 and later, subscriber sessions on the LNS that send an ICRQ that includes RFC5515 AVPs may fail to establish a session. The client will receive a CDN error "receive-icrq-avp-missing-random-vector" in response. PR1493289