Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Known Issues

 

This section lists the known issues in hardware and software in Junos OS Release 15.1R7 for the M Series, MX Series, and T Series.

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

General Routing

  • Syslog rate limit value is always shown as zero in show services service-sets statistics syslog. This is a display issue. PR900301

  • Performance is dropped by 50 Kpps because of the addition of new functionality from the previous release. PR935393

  • When the bcm0 interface goes down, the Routing Engine should switch over on the M320. PR949517

  • If the ICMP echo response is sent with an incorrect sequence number, the flow lookup passes and the counter gets incremented, but the packet is discarded by the ICMP ALG. PR971871

  • When a MAC address moves from one virtual tunnel endpoint (VTEP) to another VTEP, it is not learned behind the new VTEP until the old VTEP ages out this MAC address. This causes traffic for this MAC address to be silently dropped or discarded until it ages out on the old VTEP. PR988270

  • An NSX controller occasionally overrides an existing local MAC with a remote MAC of the same address. If a hardware VTEP in a Junos OS network detects such a condition (that is, it receives a remote MAC from the NSX controller that conflicts (matches) with an existing local MAC), the hardware VTEP in a Junos OS network accepts the remote MAC and stops publishing the local MAC to the NSX controller. PR991553

  • This issue occurs when the configured global-mac limit is less than the interface-mac limit and the same interface is configured with a packet action. When the traffic is sent with a higher packet rate, all the MAC entries are learned by the Packet Forwarding Engine. The Routing Engine later trims this traffic to the global-mac limit configuration statement. When the traffic is sent with a lower packet rate, the Routing Engine learns more than the global-mac limit configuration statement and subjects the remaining packets (with newer MACs) to the configured drop action. PR1002774

  • On MX Series routers with multiple MPCs (for example, 10 MPCs), during a unified ISSU, some of the MPCs might get offline permanently because the upgrading process takes more time. PR1005030

  • CoS scheduler names cannot be added or changed through the service COAs. The schedulers can be added at subscriber login using client dynamic profiles. PR1015616

  • There is an existing optimization in the Routing Engine kernel where the add IPCs of interface objects (IFD/IFL/IFF/IFA) are not sent to the FPCs (that is, these IPCs get suppressed) when the corresponding physical interface (IFD) no longer has the IFDF_PRESENT flag set. The idea is that because chassisd has already removed this flag from the physical interface, all processes (daemons) start cleaning up the entire hierarchy and subsequently DCD deletes IFAs/IFFs/IFLs under it, before deleting the physical interface itself. The kernel keeps track of which objects have the add IPC suppressed for which FPC peer (a per-object bit vector), and it also suppresses the delete IPC for those objects. This logic does not exist for the route target and next-hop objects, so sometimes FPCs might receive a next-hop IPC for which the parent logical interface gets suppressed in the kernel. As a result, errors are generated. PR1015941

  • In an MPLS L3VPN scenario, if the ingress is hosted on an MX Series router with an MPC line card and the egress is hosted on an MX Series router with DPC line cards, the packets are truncated if an MPLS experimental (EXP) rewrite rule is applied with a mpls-inet-both-non-vpn or mpls-inet-both configuration on the egress and the chained-composite-next-hop statement is configured. PR1018851

  • On MX Series routers that run enhanced Layer 2 software (ELS), when an interface is removed from a private VLAN (PVLAN) and then added back, the corresponding MAC entry might not be deleted from the Ethernet table. PR1036265

  • The time required to reboot T Series platforms has increased over several releases. Junos OS Release 14.2 (standalone T Series) takes 3 minutes and 39 seconds. Junos OS Release 15.1 takes 4 minutes and 18 seconds (a difference of 40 seconds). Junos OS Release 14.2 (TX Matrix multichassis) takes 5 minutes and 17 seconds. Junos OS Release 15.1 takes 7 minutes and 18 seconds (a difference of 2 minutes). PR1049869

  • When using the mpls-ipv4-template sampling template for non-IP traffic encapsulated in MPLS, log messages such as the following can be seen frequently (depending upon the rate of traffic, it could be in the range of few messages to 2000-3000 messages per minute): Feb 18 09:28:47 Router-re0 : %DAEMON-3: (FPC Slot 2, PIC Slot 0) ms20 mspmand[171]: jflow_process_session_close: Could not get session extension: 0x939d53448 sc_pid: 5 Depending on the frequency of the messages per second the, eventd process (daemon) utilization can shoot up processing these syslogs at the Routing Engine. Eventually. high CPU utilization is observed at the Routing Engine that can by checked by the commands "show chassis routing-engine" or the freebsd "Top" command under the shell. CPU states: % user, % nice, % system, % interrupt, % idle <<<<< user cpu % (top command) "show chassis routing-engine" Routing Engine status: <> CPU utilization: User percent <<<<<<<<<<<<< Background percent Kernel percent Interrupt percent Idle percent. PR1065788

  • BGP protocol next hop using next-table inet.0 under inet.3 causes a route lookup loop. BGP tries to use inet.3 to perform next-hop resolution. With the current configuration next-table, requires performing resolution from the inet.0 again. From a packet flow point of view, when the packet lookup occurs on inet.0, then it receives a next-table inet.0 instruction, which means that you need to start from inet.0 to perform the lookup again, which is the Step 1 of the lookup. This is causing the loop. PR1068208

  • On MX Series routers with MPC-based line cards in a setup involving Packet Forwarding Engine fast reroute (FRR) applications, when the BFD session flaps, the next-hop program in the Packet Forwarding Engine might get corrupted. This might result in incorrect selection of the next hop or traffic being dropped or silently discarded. PR1071028

  • When an FI: Cell underflow or a FI: Aliasing on allocates error occurs, the system logs error messages but does not create a CMERROR to raise an alarm. PR1076299

  • Some type of error, warning, or log messages might be reported on the backup Routing Engine when performing a commit synchronize action without configuring GRES. This shows up in one way or the other for any feature that relies on replication to function. For example, when using the mic-aware-power management in a non-GRES environment with commit synchronize configured, you might see the following message logged from the backup Routing Engine following a commit-sync: 'chassis' warning: WARNING: MPC reboot or chassis reboot is required to use MIC aware dynamic power management feature on already plugged-in MPCs. configuration check succeeds. PR1077442

  • The MACsec is configured on MX80 routers or FPC slots other than slot 0 of MX104 routers. MACsec using a static secure association key (SAK) security mode does not work properly on MX80 routers with FPC slots other than slot 0 on MX104 routers. PR1086117

  • The run show subscribers vpi 2 vci 40 command throws the following error Invalid argument: command is missing . PR1103607

  • On MX Series routers with MS-MPC or MS-MIC, memory leaks might be seen with jnx_msp_jbuf_small_oc object, upon sending millions of Point-to-Point Tunneling Protocol (PPTP) control connections (3 through 5 million) alone at higher calls per second (cps) (greater than 1,50,000 cps). This issue is not seen with up to 50,000 control connections at 10,000 through 30,000 cps. PR1087561

  • On the MX104 platform, when using snmpbulkget or snmpbulkwalk (for example, used by the SNMP server) on a chassisd-related component (for example, jnxOperatingEntry), chassis process (chassisd) high CPU usage and slow response might be seen because of a hardware limitation, which might also lead to a query timeout on the SNMP client. In addition, the issue might not be seen while using an SNMP query for interface statistics.

    As a workaround, to avoid the issue, use either of the following approaches:

    • Use snmpget or snmpwalk instead of snmpbulkget or snmpbulkwalk and include the -t 30 options when doing the SNMP query. For example, snmpget -v2c -c XX -t 30.

    • Use the -t 30 option with snmpbulkget or snmpbulkwalk. For example, snmpbulkget -v2c -c XX -t 30. PR1103870

  • In certain rare conditions, an FPC VoQ wedge condition occurs and packets are dropped on the ingress Packet Forwarding Engine for the MX Series router. Because the wedge is unable to be reproduced, detection of the wedge condition is introduced so that an alarm is raised once the wedge condition is detected within 10 seconds. PR1127958

  • In a service profile, the same variable is used by the filter and CoS. For example, in the profile RLinternet, the variable OutFilter is used by both the out filter and the CoS TCP. This is an incorrect concept because the filter and the CoS should have different variables. As a workaround, the following actions can be performed:

    • In service profiles, add variable for CoS TCP. For example, in profile RLinternet, add OutTcp for TCP

    • In JSRC, add value for TCP varible OutTcp. For example, OutTcp:any="1M”.

    • In JSRC, change value of out filter to distinguish from TCP. For example, OutFilter:any="1M-out"

    • Modify out-filter-name. For example, from "1M" to "1M-out" PR1154982

  • The speed configuration statement auto-10m-100m allows you to autonegotiate the speed maximum to 100 Mbps. PR1155196

  • Stacked logical interface and the underlying logical interface cannot be part of the same iflset. PR1162805

  • On MS-MIC, starting from Junos OS Release 15.1R3 and later, the J-Flow or sampling scaling comes down to 12.5 million active flows. PR1163976

  • Source-prefix filtering and protocol filtering of the CGNAT sessions are incorrect. For example, show services sessions extensive protocol udp source-prefix <0:7000::2> displays incorrect filtering of the sessions. PR1179922

  • If the MIC-3D-4XGE-XFP is used with MPC2E-3D-NG or MPC3E-3D-NG, the interfaces on the MIC-3D-4XGE-XFP connected to a DWDM device might flap continuously. PR1180890

  • The rdd (a daemon used by MS-DPC/MS-MPC/AE) might crash after performing certain operations on dual Routing Engine MX Series platforms with the aggregated Ethernet interface configured and a non-MX Series FPC installed. PR1188832

  • It is possible to see a bbe-smgd core file generated on the standby after a Packet Forwarding Engine restarts with certain specific configurations. This issue occurs when a new configuration renews or logs in before the states for Packet Forwarding Engine have been restored completely. Hence, the core file is generated on the standby; however, no disruption in service is expected and system recovers from this condition. PR1194144

  • A dynamic tunnel gets timed out every 15 minutes by default, and then retries to create another tunnel. This happens if the route obtained from IGP is nonforwarding. PR1202926

  • Various common situations lead to different views of forwarding information between kernel and Packet Forwarding Engines. For example: fpc7 KERNEL/PFE APP=NH OUT OF SYNC: error code 3 REASON: NH add received for an ifl that does not exist ERROR-SPECIFIC INFO: nh_id=562 , type = Hold, ifl index 334 does not exist TYPE-SPECIFIC INFO: none. No service impact has been seen in MPC2 and MPC3 type cards. PR1205593

  • In scenarios with local source and with ASM MoFRR enabled, the default MDT traffic loops back to the originating router on the MoFRR backup interface, thereby causing continuous IIF_mismatches. PR1206121

  • In certain interface scaling scenarios, during configuration commit/rollback, you might see an fpcx error message. You can safely ignore this message because of the FPGA monitor mechanism on DPC cards for logical interface mapping (ifl_map). Between the deletion of a physical interface and the monitoring event, this mechanism checks through the stored logical interfaces. While the mechanism tries to find the family of a recently deleted logical interface that was not cleaned from the ifl_map, harmless messages might populate the log file. PR1210877

  • On M Series, MX Series, and T Series routers, enabling the VRRP delegate-processing aggregated Ethernet IRB feature might cause VRRP and BFD to flap. PR1219882

  • The master Control Board (CB) or Routing Engine going offline or online insertion and removal (OIR) could lead to a link going down between SFB2 and the control board during link reset. As a result, some Switch Fabric Boards (SFBs) could go to check status followed by fabric healing. With the fix, the software retries five times to help the graceful link go up. When this issue occurs, the chassis alarm Minor Check plane <idx> Fabric Chip is seen, in which <idx> is the SFB slot number. PR1219890

  • An enhancement is added upon disable-pfe action on all fabric streams for the affected Packet Forwarding Engine that get disabled. The following CLI command request chassis fabric pfe [pfe-id] fpc [slot] offline initiates the Packet Forwarding Engine disable action and offlines all fabric streams. PR1220409

  • In certain situations, when the circuit breaker is turned on and off for a DC PEM multiple times, the craft interface shows the PS LED as RED even when that DC PEM is online and green with no alarms. There is no operational impact. PR1220693

  • Error logs on terminal display and messages logs are seen on setting the set system syslog user *any critical and commit command. After rebooting the router, the following error message is seen: router-re0 /kernel: GENCFG: op 34 (CLKSYNC blob) failed; err 7 (Doesn't Exist) <<<<<<<< . PR1223518

  • There is no unified ISSU from Junos OS Release 15.1 and earlier releases to Junos OS Release 16.2R1. PR1222540

  • Module voltage goes off 10 times when checking CFP diagnostics optics on 2X100GE CFP2 OTN MIC. PR1233307

  • The CLI command show route provides an incorrect format of output displaying the next-hop information in the following format rather than displaying it on the next line: validation-state: unverified, > to 2001:7f8:4::272a:2 via xe-0/0/3.0. PR1254675

  • On MX Series platforms, specific MPC cards drop traffic when late_cell counter is reported at 65,000 for each polling interval or high values are seen after the MPCs experience a transient hardware error. PR1262868

  • In a subscriber management environment, starting from Junos OS Release 15.1R4, new generation architecture is used (also known as Tomcat). In these new releases, if the dynamic VLAN profile does not have an IFF configuration (for example, either family PPPoE or family inet), even if a firewall filter configuration is present in the dynamic profile, it would not be programmed properly at the Packet forwarding Engine. PR1264367

  • On an MX Series Virtual Chassis system in a scaled subscriber management scenario, if a unified ISSU is performed while the BGP protocol sessions are active and such BGP sessions are clients of BFD, then these BGP sessions might go down and come back up again, causing traffic loss. PR1265407

  • On MPC2E-NG, MPC3E-NG, MPC5E, MPC6E, MPC7E, MPC8E, and MPC9E cards, a firewall performance feature “fast-lookup-filter" can be activated. Due to a transient parity error, the packet is dropped within the PPE with a sync xtxn error message. This issue affects the traffic, which in turn might eventually affect the service. PR1266879

  • On all Junos OS platforms and in an L3VPN environment, the IPv6 ping does not work after route leaking policy deployment is done between two L3VPN routing instances, through the IPv4 ping works fine. Topology: vrf1 CE1 ---- PE1 ---- P ---- PE2 |vrf2 | CE2. Using the route leaking policy between VRF, the IPv6 prefix learned through vrf2 is installed in the vrf1 routing table. When trying to ping the same IPv6 prefix from the vrf1 instance, ICMP echo requests go out of the PE1-CE2 interface, and CE2 sends echo replies. The PE1-CE2 interface also receives echo replies when capturing packets through the monitor traffic interface. However, the IPv6 ping from the vrf1 instance is not successful. PR1274339

  • The lc, pfh, and pfe interface do not come up on RE1 on the MX104 platform when the router boots with a single Routing Engine in slot1. PR1285606

  • When reaching the fire alarm threshold, the chassis might trigger a shutdown with an incorrect high temperature timer log message that does not indicate a fire condition. In the case of a fire condition, chassis shutdown wait time is 5 seconds. However, in the case of high temperature, it is 240 seconds. PR1298414

  • The lo0.0 interface should be used by default VRF for subscriber services. PR1303254

  • FPC crash is observed when a route has unilist next hops that contain primary or backup paths while interfaces related to unilist members go down when set protocol rsvp load-balance bandwidth is configured. PR1315228

  • In MX Series Virtual Chassis after adding a VCP link, the CoS configuration is not being programmed to the Packet Forwarding Engine. This leaves this VCP with default CoS configuration which does not match other VCP links and drop packets because of the tail-drops. PR1321184

  • After successive flaps on core interfaces in AA multihoming EVPN-VXLAN, some race conditions can trigger constant high CPU usage on the backup Routing Engine. In this scenario the rpd process shows high CPU usage, the rpd process subsystem does not respond, and the NSR task does not complete. During multiple EVPN and VXLAN core interface flaps, the rpd process does not process the learned next-hop entries by L2 learning in Junos OS and goes into an infinite loop, causing 98 percent CPU usage on the backup Routing Engine. PR1334235

  • On MX Series platform with 100M SFP used on MIC-3D-20GE-SFP-E/MIC-3D-20GE-SFP-EH, SFP might not work if it is third party. . PR1344208

  • In some circumstances some PPPoE sessions might not be totally cleaned up. This might cause the new PPPoE users fail to login. PR1346226

  • The error message indicates that the filter index as identified in the message failed to bind to the BBE subscriber's logical interface dfw_bbe_filter_bind:1125 BBE Filter bind type 0x84 index 167806617 returned 1. In some circumstances some PPPoE sessions might not get completely cleaned up. This might cause the new PPPoE users fail to login. PR1354435

  • When a DEMUX interface is brought over static pseudowire underlying interface, then configuration change is made to delete and read the static pseudowire underlying interface, which leads to tearing down of pseudowire interface and DEMUX interface, it was noticed that subscribers could not log back when the configuration was added. PR1356980

Class of Service (CoS)

  • COSD memory leaks when you do an snmpwalk for get-next jnxCosIfqStatsTable or jnxCosQstatTable. PR1012412

  • After the router restarts, the CoS wildcard configuration might be applied incorrectly. PR1325708

EVPN

  • When two or more Ethernet VPN (EVPN) PE devices are connected to a multihomed CE device, after switching the router-id between the PE devices, the nondesignated forwarder (DF) PE device forwards broadcast, unicast unknown, and multicast (BUM) traffic back to the Ethernet segment identifier (ESI). PR1108107

  • An incorrect PE router is attached to an ESI when the router receives two copies of the same AD/ESI route (for example, one through eBGP and another one received from an iBGP neighbor). This causes a partial traffic black hole and stale MAC entries. You can confirm the issue by checking the members of the ESI: user@router> show evpn instance extensive ... Number of ethernet segments: 5 ESI: 00:13:78:00:00:00:00:00:00:01 Status: Resolved Number of remote PEs connected: 3 Remote PE MAC label Aliasing label Mode 87.233.39.102 0 0 all-active 87.233.39.1 200 0 all-active <<<< this PE is not part of the ESI 87.233.39.101 200 0 all-active. PR1231402

Forwarding and Sampling

  • When VRRP is configured on MX Series routers with MPC/MIC interfaces, static MAC entries are installed on the Packet Forwarding Engine in the MAC database as part of the MAC filter installations. The MIB walk on some object identifiers (OIDs) triggers a walk over the MAC MIB entry (walk over the static MAC entries with no OIDs), resulting in an error message. During the walk, it is expected that no entries are read from static MAC database entries; however, the EODB is not set to indicate that the MAC database walk has ended. This error log does not have any functional impact on the MIB walk: mib2d[xxx]: MIB2D_RTSLIB_READ_FAILURE: check_rtsock_rc: failed in reading mac_db: 0 (Invalid argument) mib2d[xxx]: SNMP_GET_ERROR1: macStatsEntry getnext failed for interface: index1 ge-*/*/* (Invalid argument) The following oid might trigger the issue: 1/ Rpf related oid 2/ AtmCos related oid 3/ Mac related oid , such as jnxMacStatsEntry 4/ PMon related oid 5/ jnxSonetAlarmTable 6/ Scu related oid 7/ jnxCmRescueChg 8/ jnxCmCfgChgEventLog 9/ jnxIpv4AdEntReasmMaxSize. PR1042610

  • If a bandwidth-percent-based policer is applied on an aggregated Ethernet bundle without the shared-bandwidth-policer configuration statement, traffic hits the policer even if the traffic has not exceeded the configured bandwidth. As a workaround, configure the shared-bandwidth-policer configuration statement under the policer. PR1125071

  • The pfed process utilization stays at above 90 percent when you use accounting-profile for firewall filters in a scaled environment. PR1134667

  • The default-arp-policer option is applied to every relevant logical interface to rate-limit the ARP traffic. You can disable the default-arp-policer option by running the command set firewall disable-arp-policer. Improper application leads to the Routing Engine getting overloaded with a bulk of ARP traffic, leading to a typical DoS scenario. The issue is that even after you disable default-arp-policer, it still affects the logical interface when the router is rebooted or when a new logical interface is created. PR1198107

  • In a subscriber management environment, starting from Junos OS Release 15.1R4, a new generation architecture is used (also known as Tomcat). In these new releases, if the dynamic VLAN profile does not have an IFF configuration (for example, either family PPPoE or family inet), the corresponding idle dynamic VLAN interface is not declared as idle after expiration of the idle timeout and is not removed. PR1263199

  • In some stress test conditions, the sampled process crashes and generates a core file when connecting to L2BSA and EVPN subscribers aggressively. PR1293237

  • FPC crashed after applying the FW filter on 10,000 interfaces. PR1300500

  • Heap memory leaks occur on DPC when the flow specification route is changed. PR1305977

Infrastructure

  • Syslog messages are observed when one of the following CLI commands is executed: system syslog file messages kernel any or system syslogfile messages any any. These syslog messages do not indicate any functionality, breakage, or impact. If you need to enable “anyany”, then you would need to skip these logs with an appropriate match condition. PR1239651

  • When the configuration statement set system ports console log-out-on-disconnect is enabled, the Junos OS eventd process (daemon) blocks the console-open(). However, during this stage with the syslog console configured (always logs on console), any logging continues even if the console session is ended. When the console logging continues to be in the waiting status, the eventd syslog rotation freezes and some processes directly involved in logging in to the system would also go into the wait status, causing undesirable behavior. PR1253544

  • The kernel might fail to finish all input or output before shutdown during updating. Also, the upgrade might not succeed with the following reason: Could not find installation package. PR1298749

  • After upgrading to Junos OS Release 15.1 and later releases, Juniper Networks Routing Engines with the Hagwara CF card installed, report the following failure message (every 30 minutes): root@router> show log messages| match ada1 Jan 15 21:18:28 router smartd[4357]: Device: /dev/ada1, failed to read SMART Attribute Data Jan 15 21:48:28 router smartd[4357]: Device: /dev/ada1, failed to read SMART Attribute Data Jan 15 22:18:28 router smartd[4357]: Device: /dev/ada1, failed to read SMART Attribute Data <...> Issue related with Smartd daemon reading the SSD attributes with HAGIWARA SYS-COM MFD10 Compact Flash. Routing Engine 0 REV 05 740-031116 xxxxxxxxxxx RE-S-1800x4 <...> ada1 3671 MB HAGIWARA SYS-COM MFD10 xxxxxxxxxxxx Compact Flash. PR1333855

  • On Juniper Networks Routing Engines with Hagiwara CompactFlash cards installed, after upgrade to Junos OS 15.1 and later releases, the following failure message is reported (every 30 minutes): root@host> show log messages| match ada1 Jan 15 21:18:28 router smartd[4357]: Device: /dev/ada1, failed to read SMART Attribute Data Jan 15 21:48:28 router smartd[4357]: Device: /dev/ada1, failed to read SMART Attribute Data Jan 15 22:18:28 router smartd[4357]: Device: /dev/ada1, failed to read SMART Attribute Data <...> Issue related with Smartd daemon reading the SSD attributes with HAGIWARA SYS-COM MFD10 Compact Flash. Routing Engine 0 REV 05 740-031116 xxxxxxxxxxx RE-S-1800x4 <...> ada1 3671 MB HAGIWARA SYS-COM MFD10 xxxxxxxxxxxx Compact Flash. PR1333855

Interfaces and Chassis

  • MX Series chassis control interrupt storm might be falsely reported when a field-replaceable unit (FRU) is removed, inserted, or the Front Panel Module (FPM) button is pushed. A FRU might not be recognized or booted, resulting in chassis operational failure. PR823969

  • The internal management Ethernet interfaces (em-) might fail autonegotiation after a reboot if one of the em interfaces is in a link-down condition. It might hold back the line cards from booting after the Routing Engine reboots and kernel memory keeps increasing. Any platform using em interfaces might experience a kernel memory leak of devbuf buffers when the interface is administratively marked up, but the physical link is down. Once the kernel devbuf allocation exceeds an internal threshold, warning messages are recorded in the message file: kernel: kmem type devbuf using <X> K, exceeding limit <Y> K. These logs remain until the Routing Engine is restarted. PR829521

  • Online insertion and removal (OIR) is not supported on a PIC (PD-4XGE-XFP) currently. When pulling out a PIC (PD-4XGE-XFP) from an FPC that is not offline, the FPC crashes, generating a core file. PR874266

  • 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 the memory. In some cases, the memory of the dcd keeps increasing on the backup Routing Engine. PR1014098

  • Configuring ODU FRR under otn-options for 2x100G DWDM PIC is an unsupported command on MX Series routers. Incorrectly adding such a configuration could result in an FPC crash and restart. PR1038551

  • After changing the MTU on the physical interface, an IPv6 link local address is missing on the static VLAN demux interface. PR1063404

  • During failure notification state machine, CFM does not correctly transit from DEFECT CLEARING state to RESET once the error indication has been cleared. As a consequence, all the forthcoming errors will be considered post errors and are reported immediately without incurring the fngAlarmTime. This is a cosmetic problem. PR1096346

  • When using the Ethernet Operation, Administration, and Maintenance (OAM) connectivity fault management feature, if the remote end deactivates the protocols oam ethernet connectivity-fault-management maintenance-domain configuration, the interface goes down as expected. However, once the remote end activates the configuration, the local interface stays down. (The defect is introduced in Junos OS Release 15.1F5 branch and occurs in Junos OS Release 15.1F5-S3 or later.) PR1231315

  • DWDM 1x100G MIC FPC restart with a next-generation MPC results in a core file being generated. An interruption is observed when the forward error correction(FEC) mode is changed, resulting in an FPC crash. PR1232392

  • In a VPLS multihoming scenario, the CFM packets are forwarded over the standby PE device link, resulting in duplicate packets or a loop between the active and standby link. PR1253542

  • In a subscriber management scenario with dynamic demultiplexing (demux) interfaces configured, in the case where subscribers belonging to one aggregated Ethernet interface are migrated to a newly configured aggregated Ethernet interface, subscribers might fail to access the device after deleting the old aggregated Ethernet configuration. PR1322678

J-Web

  • When you open a J-Web interface session using HTTPS, enter a username and a password, and then click the Login button, the J-Web interface takes 20 seconds longer to launch and load the dashboard page than it does if you use HTTP. PR549934

  • When the J-Web interface is launched using HTTPs, the time shown in the View Events page (Monitor >Events And Alarms > View Events) differs from the actual time in the switch. As a workaround, set the correct time in the box after the J-Web interface is launched. PR558556

Layer 2 Ethernet Services

  • IPv4 and IPv6 long VRRP convergence delay and unexpected packet loss might occur when a MAC move for the IRB interface occurs (for example, when flapping the Layer 2 interface that is the underlying interface of IRB on the master VRRP). PR1116757

  • While doing the unified ISSU with specific configurations, a few LACP events are missing or PPMAN is not processing the incoming packet meant for LACP. There is one more possibility that the peer might not be responding to the negotiation packets. One of the mentioned reason is causing the interface to be stuck in fast periodic state and component which are dependent on the LACP state gets impacted. PR1354949

MPLS

  • When the edit-protocols-mpls-traffic-engineering statement is configured, the user cannot downgrade from Junos OS Release 14.2 to prior releases. In order to downgrade, the user must delete the traffic-engineering stanza and reconfigure it after the downgrade. PR961717

  • When using mpls traffic-engineering bgp-igp-both-ribs with LDP and RSVP both enabled, CSPF for interdomain RSVP LSPs cannot find the exit area border router (ABR) when there are two or more such ABRs. This causes interdomain RSVP LSPs to break. RSVP LSPs within the same area are not affected. As a workaround, you can either run only RSVP on OSPF ABR or IS-IS L1/L2 routers and switch RSVP off on other OSPF area 0/IS-IS L2 routers, or avoid LDP completely and use only RSVP. PR1048560

  • The multi-instance RSVP feature might not work in specific scenarios on MX Series devices with MPC cards when the core facing interface of the virtual routing instance and VPLS pseudowire termination is simultaneously configured on the master instance. As a workaround, configure the import-label-route statement at the [edit routing-instances <routing-instance-name> protocols vpls] hierarchy level to resolve this issue. PR1080714

  • In a BGP Prefix-Independent Convergence (PIC) edge scenario, when the ingress route (the primary route) fails, the LDP might fail to send the session down-event to the Packet Forwarding Engine correctly. The Packet Forwarding Engine might still use the primary path to forward traffic (in some cases, 3-5 seconds for 30,000 prefixes) until the global convergence is completed by the interior gateway protocol (IGP). This issue might also be seen when the delay-delete CLI command is configured. In this scenario, the session-down event is sent to the Packet Forwarding Engine. However, due to local reversion, the primary path might also be chosen as the forwarding path when it is deleted. PR1097642

  • Benign error messages can occur when bringing up new interfaces or line cards; they can be ignored. PR1136033

  • In some interoperable scenarios, sometime a new label is advertised without withdrawing the old label by peer and Junos OS rejects the new label advertised (as per RFC 3036 behavior). The following logs are generated: LDP: LabelMap FEC L2CKT NoCtrlWord ETHERNET VC 40347 label 53 - received unsolicited additional label for FEC, releasing new label. PR1168184

  • In a CE-CE setup, traffic loss might be observed over the secondary LSP on primary failover. PR1240892

  • When MPLS builds the next hop for an mpls.0 route for the scenario with IDP over RSVP LSP over the bypass tunnel and the IDP label is implicit-NULL, the label stack constructed for the next hop might be incorrect, with an invalid bottom label value of 1048575. PR1270877

Network Management and Monitoring

  • Eventd uses event library for signal handling. A core file is generated because of a race condition/synchronization issue in the event library while handling signals. The event library is not signal safe and thus it is vulnerable to such issues. Eventd handles the following different kinds of signals (through signal handlers):

    • SIGHUP (on commit)

    • SIGTERM (on killing eventd)

    • SIGCHLD (on termination of event script execution)

    • SIGUSR1 & SIGUSR2 (on log rotation)

    If one signal handler is preempted by another signal handler, then it might corrupt waitList structures (and this can cause the core file to be generated). This might happen when eventd receives a new signal while processing another signal. This situation might not occur every time and hence core files are observed rarely. PR1122877

  • Traps are sent as AgentX messages type (AGENTX_MSG_NOTIFY) from the subagent to the master agent. The subagent expects a response in the form of an ACK from snmpd after sending these AGENTX_MSG_NOTIFY messages upstream. If an ACK is not received from snmpd within 1 second (current timeout value), the sub-agent resends the trap. After the router reboots or after GRES, a lot of upstream communication is triggered from subagent to snmpd (traps and MIB registration messages). This time the snmpd process might not be able to send the downstream ACK within the 1 second period. This might trigger the subagent to resend the trap, which is seen as a duplicate trap on the NMS. PR1164848

Platform and Infrastructure

  • When next-ip is defined as the action and there is no ARP for the IP address specified under next-ip, the traffic is not forwarded. A manual ping needs to be initiated for itto work. PR864861

  • FPC reports the following errors and is not able to connect any subscriber: Pkt Xfer:** WEDGE DETECTED IN PFE 0 TOE host packet transfer: %PFE-0: reason code 0x1. Also, the MQ FI might be wedged and the following log might be seen: Apr 11 12:09:11.945 2013 NSK-BBAR3 fpc7 MQCHIP(0) FI Reorder cell timeout Apr 11 12:09:11.945 2013 NSK-BBAR3 fpc7 MQCHIP(0) FI Enqueuing error, type 1 seq 404 stream 0 Apr 11 12:09:11.945 2013 NSK-BBAR3 fpc7 MQCHIP(0) MALLOC Pre-Q Reference Count underflow - decrement below zero. PR873217

  • When there is huge logical interface (IFL) scaling on aggregated Ethernet interfaces (500 or more) with more than 32 member links and when all FPCs are restarted one by one, followed by member link addition to the link aggregation group (LAG), the state dependency evaluation in the kernel takes a long time when the scale involved is given. As a result, the FPCs do not get all the states from the Routing Engine. This is an uncommon sequence of events or conditions. PR938592

  • The overhead values need to be represented with 8 bits to cover the range "-120 to 124", but the microcode is only using the last 7 bits. PR1020446

  • When TCP authentication is enabled on a TCP session, the TCP session might not use the selective ACK (SACK) TCP extensions. PR1024798

  • When using show | compare method to commit, part of the configuration might be treated as noise and return a syntax error. PR1042512

  • IPv6 packet loss occurs and traffic degrades because the MX Series router has a restrictive rate limit on sending ICMPv6 packet too big messages. PR1042699

  • Once the Traffic Offload Engine (TOE) thread is stalled due to a memory error at the lookup chip, all statistics collection from the interfaces hosted by the Packet Forwarding Engine stops getting updated. PR1051076

  • In configurations with IRB interfaces, during times of interface deletion (for example, FPC reboot), the Packet Forwarding Engine might log errors stating nh_ucast_change:291Referenced l2ifl not found. This condition should be transient, with the system reconverging on the expected state. PR1054798

  • On MX Series routers, parity memory errors might occur in preclassifier engines within an MPC. Packets are silently discarded because such errors are not reported and hence more difficult to diagnose. CM errors such as syslog messages and alarms should be raised when parity memory errors occur. PR1059137

  • Juniper Networks VSA length above 2000 bytes is not supported. Using authorization parameters above this length would result in an incorrect authorization setting for the user. PR1072356

  • When deleting some uncommitted configurations on the active Routing Engine, the rpd process on the backup Routing Engine might restart because of the following error: Unable to proceed with commit processing due to SIGHUP not received. Restarting to recover. PR1075089

  • In XM-based multi-LU systems (MX Series platform with MPC3E, MPC4E, MPC5E, MPC6E, NG-MPC3, NG-MPC2, or T4000 with T4000-FPC5-3D linecard), there are multiple LUs representing the same Packet Forwarding Engine complex. But once the BFD processing is designated to a dedicated LU (LU0), called the “anchor LU”, and the remaining LUs (LU 1, LU 2, LU 3) are non-anchor LUs. When the inline BFD packets punt from non-anchor LU to the anchor LU, the interface-group is not populated in the packet context, so the packets might not match the related filter term. PR1084586

  • On MX Series routers with MPCs and MICs, the BFD session over the IRB interface with the static client might not come up with the VRRP configuration. PR1085599

  • Service chaining of inline softwire and NAT is not supported. Currently, when softwire rules and NAT rules are configured under the same service set on the SI interface, the commit is successful without displaying an error. . PR1136717

  • A maximum of 1024 softwire concentrators is supported with inline-6rd. When more than 1024 SCs are configured (for example, 1025 SCs), a commit error message that is not informative is seen. PR1153092

  • On MX Series routers with MPCs/MICs, the system might try to access a NULL pointer returned form hardware state lookup of the logical interface when the system runs out of memory, which might result in FPC crash. PR1163606

  • The delegated BFD session over aggregated Ethernet interface failed to come up after FEB switchover with FEB redundancy group (1:1 and 1:N). PR1169018

  • With sampling configured, if AS paths change, over time, the stale AS paths might be seen in the sampler database of JNH memory. PR1189689

  • If an operation related to configuration modification like load merge, load override, commit check, or a commit is done for large configuration files, then mustd crashes and the following error message is seen: error: Child /usr/sbin/mustd dumped core (0x86). PR1200813

  • Several files are copied between Routing Engines during the ffp synchronize phase of the commit (such as /var/etc/mobile_aaa_ne.id, /var/etc/mobile_aaa_radius.id). These files are copied even if there was no corresponding change in the configuration, thus unnecessarily increasing commit time. PR1210986

  • After IPv6 traffic islearned on an L2, bridge, or multilink interface, when it has been traversed through MPLS, core random packets might get classified incorrectly by the fabric, resulting in a packet loss. PR1223566

  • Configuration changes under a logical system with a LSYS user do not take effect on a single commit with fast-synchronize enabled. PR1265139

  • This issue occurs when 120 bridge domains (among a total of 1000 bridge domains) have XE/GE links toward the downstream switch and LAG bundles as uplinks toward upstream routers. The XE/GE link is part of the physical loop in the topology. Spanning-tree protocols such as VSTP, RSTP, and MSTP are used for loop avoidance. Some MAC addresses are not learned on the router when LAG bundles that are part of such bridge domains are flapped and other events such as spanning tree root bridge changes occur. PR1275544

  • When you see T3 with regard to hardware timestamps, and when you see T4 < T1 and T3-T2 because of NTP synchronization, those samples for any measurements (including round-trip time,and ingress and egress jitter and delays) are not considered. However, they are reported under error statistics. In these cases, probes are received from the real-time performance monitoring server with correct timestamps and hence they are marked as successful probes. However, they are not used for any measurements. PR1300049

  • When an MPLS unicast next hop gets removed (for example, because of a network convergence event), the statistics associated with that next hop can be erroneously added to the output statistics of the respective physical interface, causing false abrupt increments in output packet and byte count. Logical interface statistics and CoS queue counters are not affected by this problem and still provide accurate data. PR1338581

  • On MX Series platforms, the MPC5-inline-ka PPP echo requests are not transmitted when anchor-point is lt-x/2/x or lt-x/3/x in a pseudowire deployment. PR1345727

Routing Protocols

  • The multicast next-hop show multicast nexthop shown for the master and backup Routing Engines for the same flow could be different if the next hop is a hierarchy MCNH. During a nonstop active routing (NSR) switch, however, there is no traffic loss caused by this show command difference. PR847586

  • In rare cases, rpd might generate a core file with error rt_notbest_sanity: Path selection failure on .... The core is soft, which means there should be no impact to traffic or routing protocols. PR946415

  • On MX Series routers, when an instance type is changed from VPLS to EVPN, and in the same commit an interface is added to the EVPN instance, the newly added EVPN interface might not be able to come up. PR1016797

  • In scaled configurations toggling from 64 bit to 32 bit, rpd runs at the same time that Rosen MVPN routing instances are deleted, resulting in a kernel core file on the backup Routing Engine. PR1022847

  • The static/static access routes pointing to an unnumbered interface are getting added in the routing table even if the interface is down. In this case, when GRES is disabled, this type of route will never be added in the routing table after Routing Engine switchover. PR1064331

  • When multiple addresses are configured on an interface, if the interface has interface-type p2p configured under OSPF and the router does not receive any OSPF packets from one of the IFAs, the OSPF state will not go down for the corresponding adjacency. It should have no impact on route learning, but it might cause confusion for troubleshooting, when peering with Cisco devices, which have multiple addresses configured as secondary addresses. PR1119685

  • A few seconds of traffic loss is seen on some of the flows when the PE-CE interface comes up and the PE device starts learning 70,000 IPv4 prefixes and 400 IPv6 prefixes the CE device during L3VPN convergence. PR1130154

  • 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

  • The generated route does not inherit the next hop from the contributing route in an L3VPN case, in which the contributing route is learned through MP-BGP. The next hop remains as rejected for the generated route. PR1149970

  • With Shared Risk Link Group (SRLG) enabled under corner conditions, after executing the command clear isis database, the rpd might crash because the IS-IS database tree gets corrupted. PR1152940

  • Junos OS marks hidden routes with a negative route preference. The router policy-statement explicitly sets a preference value for the BGP routes, including the hidden routes, while the routes are imported into the VRF routing table, overriding the negative one, but not checking for AS_PATH loops within the VRFcontext. This results in the hidden routes become active in the VRF routing table. PR1165781

  • Here are the results when L1 is disabled for Lo0: {master}[edit] user@router# run show isis interface IS-IS interface database: Interface L CirID Level 1 DR Level 2 DR L1/L2 Metric lo0.0 3 0x1 Disabled Passive 0/0. Here are the results when L2 is disabled for Lo0: {master} user@router> show isis interface IS-IS interface database: Interface L CirID Level 1 DR Level 2 DR L1/L2 Metric lo0.0 3 0x1 Passive Disabled 0/0. PR1202216

  • When multiple labels become stale in stale-label-holddown-duration (default 60 seconds), the timer restarts and all the stale labels are accumulated without being deleted. This might cause memory for allocating labels to be exhausted, and then MPLS traffic might be affected due to abnormal/failing label allocation. PR1211010

  • In the context of a large number of configured VPNs, routes changing in the midst of a bgp path-selection configuration change might sometimes lead to an rpd core file. This core file has been seen with the removal of the always-compare-med option. PR1213131

  • The rpd might crash if the IS-IS process tries to send out packets when flow control is not ready. PR1214947

  • On Junos OS devices with the the graceful restart, the restarting node might send an End-of-RIB marker too soon to its helper nodes, before the actual routes updates are completed, thereby causing traffic loss. PR1225868

  • The routing protocol process (rpd) on the backup Routing Engine might restart unexpectedly upon the addition of a new L2VPN routing instance. Following a major change in the configuration of an L2V PN routing instance (such as changing instance type on-the-fly, or routing instance rename), the routing instance and all its data structures get successfully deleted/changed on the master Routing Engine. On the backup Routing Engine, however, this might not get done, and therefore, the backup might still hold the routing instance with the original name (or original type), in addition to another newly created routing instance reflecting the configuration change. As a result, one of the routing instance parameters, the "sync-id" is freed on the master Routing Engine, but remains in use on the backup. Later (can be much later), another routing instance gets added in an unrelated provisioning activity. If the sync-id that gets allocated for the new instance is the same as the one for the instance that was not properly deleted in the first change, then rpd on the backup Routing Engine will crash due to an assert, and then restart. PR1233514

  • The distributed Bidirectional Forwarding Detection (BFD) sessions (such as multihop BFD, BFD over AE or MPLS OAM) need to select an anchor Packet Forwarding Engine. If the connection between Periodic Packet Management Process (ppmd on Routing Engine) and Periodic Packet Manager (ppman on the Packet Forwarding Engine) breaks and reconnects for some reason, the newly chosen anchor FPC might be different than the previous one, it is possible that the stale BFD sessions might be seen on the previous anchor FPC. PR1246363

  • LDP OSPF are “in sync” state because "IGP interface down" with ldp-synchronization is enabled for OSPF: user@host> show ospf interface ae100.0 extensive Interface State Area DR ID BDR ID Nbrs ae100.0 PtToPt 0.0.0.0 0.0.0.0 0.0.0.0 1 Type: P2P, Address: 10.0.60.93, Mask: 255.255.255.252, MTU: 9100, Cost: 1050 Adj count: 1 Hello: 10, Dead: 40, ReXmit: 2, Not Stub Auth type: MD5, Active key ID: 1, Start time: 1970 Jan 1 00:00:00 UTC Protection type: None Topology default (ID 0) -> Cost: 1050 LDP sync state: in sync, for: 00:04:03, reason: IGP interface down config holdtime: infinity. "IGP interface down" is observed as the reason because although LDP notified OSPF that LDP synchronization was achieved, OSPF was not able to take note of the LDP synchronization notification, because the OSPF neighbor was not up yet. PR1256434

  • In a BGP configuring scenario, the following log entry might be seen in the message logs under normal operation and should be ignored: rpd[11156]: %DAEMON-3: bgp_rt_send_msg_attr: too big attributes: avail 123 .PR1276758

  • If a router works as a graceful restart helper during a peering establishment, the newly established peer might lose some of the negotiated capabilities and might interpret the updates incorrectly. This can cause peer drops or invalid routes to be received. PR1293174

  • Multicast flow interruption might be observed on a transit router in a Protocol Independent Multicast scenario such as the following: (*,G) join is received on one interface, and (*,G) join and (S,G,RPT) prune are received on another interface, which then receives a (*,G) prune. Multicast flows on the first interface get reset and are interrupted for a short period of time (for example, 1 second). PR1293900

  • If the statement egress-te is configured for BGP and the BGP flaps, the rpd might crash. If the statement switchover-on-routing-crash and NSR are not enabled on the device, while rpd recovers, there is an unexpected routing protocol disruption. PR1295062

  • When BGP family inet labeled-unicast protection is configured, a BGP bypass route might be installed in inet.2. At the same time, if inet.2 is used as the RPF table, the bypass route might be used to perform an RPF check, which will lead to RPF check failure. PR1310036

  • BGP prefixes with three levels of recursion for resolution will get stuck with a stale next hop at the first level after a link-down event, even though the second and the third level routes have updated next hops. PR1314882

  • When two route reflector (RR) routers use Prefix-Independent Convergence (PIC) to protect each other's BGP-LU (labeled-unicast) LSP, endless label oscillation might be seen. PR1318093

  • When route target filtering (RTF) is configured for VPN routes and multiple BGP session flaps, there is a slight chance that some of the peers might not be able to receive the VPN routes after the flapped sessions come up. PR1325481

  • With BGP/LDP/IS-IS configurations, deleted IS-IS routes might still be present in the RIB. This situation does not affect or have any impact on route selection or other rpd functionality, however, IS-IS routes do not get removed with specific configurations. PR1329013

  • With EBGP or BFD and GR configured, link disable on the peer might cause inadvertent GR helper mode. PR1342328

Services Applications

  • In the NAT environment, the jnxNatSrcPoolName object identifier is not implemented in jnxSrcNatStatsTable. PR1039112

  • Session counters for clear text traffic are not updated after decryption. Decrypted packet count can, however, be obtained by running the show security group-vpn member ipsec statistics command. PR1068094

  • This issue occurs in a typical scaling scenario, where there are a high number of simultaneous updates from the Routing Engine to the Packet Forwarding Engines. If there is a request for packet mirroring, this message might get delayed because of the other pending messages, resulting in overall delay in mirroring of the requested flows. PR1244849

  • This issue occurs in an Apache Tomcat LI implementation. Enabling this support requires considerable effort. As a workaround, to disable the drop policy, first delete the LI service if customers want to disable the drop policy, then they can delete the LI service via DTCP delete and then add the LI service back by DTCP add without the drop policy. PR1252079

  • This issue occurs with multiservices PICs. When you retain SAs in kmd (ipsec-key-management daemon) when the PIC is offline and set them as "not installed”, and if you reinstall those SAs when the PIC comes online, sometimes reverse routes have reference count problems if the SAs are retained during PIC restart. This issue causes incorrect next hops on the reverse routes. PR1285907

  • During a login or logout test for 1000 PPPoA subscribers, the subscribers faced a login failure when they tried to log in again. For example, on the logical interface, at-4/0/3.90325190: user@host> show ppp interface at-4/0/3.90325190 extensive Sep 06 10:57:45 Session at-4/0/3.90325190, Type: PPP, Phase: Establish LCP State: Starting Last started: 2017-08-31 12:32:41 CEST <<<<<<<<<<<<<<< <shows-that> show interfaces at-4/0/3.90325190 | match packets | refresh 5 Sep 06 10:57:55 ---(refreshed at 2017-09-06 10:57:55 CEST)--- Input packets : 132702 Output packets: 2753 Input packets : 132702 Output packets: 2753 ---(refreshed at 2017-09-06 10:58:00 CEST)--- Input packets : 132703 Output packets: 2753 Input packets : 132704 Output packets: 2753 user@host> show configuration interfaces at-4/0/3.90325190 Sep 06 10:59:41 encapsulation atm-ppp-vc-mux; no-traps; vci 25.190; ppp-options { dynamic-profile client-pppoa; chap; pap; } keepalives interval 15; family inet { address 192.168.144.1/32; } family inet6 { unnumbered-address lo0.0; }. So, while there is no L2TP session established, the Packet Forwarding Engines are processing the packet as if the L2TP session is in place. PR1306211

  • The CLI command show services l2tp destination lists each tunnel separately, not the summary of tunnels and sessions. PR1312954

Subscriber Access Management

  • During software upgrade or downgrade using request system software add, the netstat utility might crash because of software version incompatiblities. Generating a core file has no effect on the upgrade or downgrade results, and does not adversely effect the upgrade or downgrade operation. Because the crash has no adverse effect on the upgrade, we suggest that you ignore and delete the crash file. PR911232

User Interface and Configuration

  • In the J-Web interface, selecting the monitor port for any port on the Chassis Viewer page takes you to the common port monitoring page instead of the corresponding monitoring page of the selected port. PR446890

  • In the J-Web interface, when you select Configure > Routing> OSPF> Add and then click the Interface tab you see the following three interfaces by default: pfh-0/0/0.16383, lo0.0, and lo0.16385. To overcome this issue and to configure the desired interfaces to the associated OSPF area-range, set the following statements from the CLI: set protocols ospf area 10.1.2.5 area-range 12.25.0.0/16 and set protocols ospf area 10.1.2.5 interface fe-0/3/1. PR814171

  • In J-Web, on the Configure > Cli tools > Point and click > System > Advanced > Deletion of saved core page, the No option is not available. PR888714

  • Basic value entry format error check is not present at Configure >Security >IPv6 Firewall Filters, but the error check is present on the IPv4 Firewall Filters page. However, it throws an error when you try to commit the incorrect format data entered. PR1009173

  • The transfer-on-commit statement does not work on vMX. The issue is specific to vMX with Junos OS Release 15.1 or later. PR1131586

VPNs

  • In a dual Routing Engine scenario with NSR enabled, when L2Circuit, L2VPN, or VPLS is enabled, due to race conditions in different messages and events between master and backup Routing Engines, if label-reuse occurs in the master Routing Engine rpd, the backup Routing Engine rpd might handle messages and events unsuccessfully and crash. There is no functional impact. PR1119684

  • For a next-generation MVPN using ingress replication provider tunnels, if both IPv4 and IPv6 are configured, when the receiver PE router advertises different labels for IPv4 and IPv6 in type-1 BGP route, the source PE router creates two provider tunnels to carry IPv4 and IPv6 traffic, both causing duplicated multicast traffic. PR1128376

  • In a next-generation MVPN scenario, when forwarding-cache timeout never non-discard-entry-only is configured for an MVPN instance, the cache lifetime is shown as forever in the output of the CLI command show multicast route instance X extensive and the route disappears after 7-8 minutes. PR1212061