Knowledge Search


×
 

15.1R7-S3: Software Release Notification for Junos Software Service Release version 15.1R7-S3

  [TSB17504] Show Article Properties


Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, T, TX, M, MX, PTX, QFX5100
Alert Description:
unos Software Service Release version is now available for download from the Junos software download site
Download Junos Software Service Release:
  1. Go to Junos Platforms - Download Software page
  2. Input your product in the "Find a Product" search box
  3. From the Type/OS drop-down menu, select Junos SR
  4. From the Version drop-down menu, select your version
  5. Click the Software tab
  6. Select the Install Package as need and follow the prompts
Solution:

Junos Software service Release version 15.1R7-S3 is now available.

NOTE:  Due to memory constraint of EX2200 and EX2200-C platforms we do not recommend deploying JUNOS software version 15.1 on these platforms.
See: https://kb.juniper.net/TSB16779, and https://kb.juniper.net/TSB17138 for more detail.

The following are incremental changes in 15.1R7-S3.

 
PR Number Synopsis Description
1142719

l2-learning process (l2-ald) might coredump in scaled setup

The Layer 2 address learning process (l2-ald) might generate a core file in a scaled L2 setup, including bridge domain, VPLS, EVPN, and so on. The l2-ald core file usually follows a kernel page fault that recovers on its own. In some cases, a manual restart of the process is needed to recover logs: /kernel: %KERN-3-BAD_PAGE_FAULT: pid 69719 (l2ald), uid 0: pc 0x88beb5ce got a read fault at 0x6ca, x86 fault flags = 0x4 /kernel: %KERN-6: pid 69719 (l2ald), uid 0: exited on signal 11 (core dumped) init: %AUTH-3: l2-learning (PID 69719) terminated by signal number 11. A core file is generated.

1161487

Ksyncd might crash due to transient replication errors between Routing Engines.

On MX Series routers, if dynamic VLAN is used in a subscriber scenario, ksyncd might crash if subscribers log in and log out continuously. This is a timing issue due to the transient replication error for VLAN between master Routing Engine and backup Routing Engine.

1162665

With NSR enabled, rpd may core on standby RE when operations like RD modify or RD delete/RD operations are done

Symptoms: With NSR enabled, rpd may core on standby RE when operations like RD modify or RD delete/RD operations are done.(Not always observed). Impact: There is no impact on traffic or other functionality. The core occurs only once on the standby RE. Standby RE recovers completely, with all replication done fully post core.

1164101

Packet might drop due to inconsistent state in PFE

From Junos OS Release 14.1X51-D75, 15.1F4, and 15.2IB, if deactive interface, in rare condition, due to a software defect, NH is getting deleted, while there are still routes pointing to it, which leads to inconsistent states in Packet Forwarding Engine. The MPC might crash or traffic blackhole.

1182684

RPD might crash when bgp session with l2vpn/vpls signalling flaps.

RPD might crash when bgp session with l2vpn/vpls signalling flaps. RPD crash seen with the reason "assert" due to label release for L2VPN FEC 129. Detailed information is shared below: When an Application ( Ex: FEC 129) is using a label for an L2VPN/VPLS instance and when the signalling protocol BGP flaps the labels needs to be refreshed. Hence the router which is using the label provided by BGP for that FEC should free the label but due to some uncertainity it fails to release the label. The freeing of label goes through block-id library inside the Junos but fails in the debug label repository and hence this label will not be freed up. The Debug label repository usually tracks the label and the application which is using it. If the label is requested to be freed up by this FEC129 ( APP) but the label is owned by another application ( i.e., If Application A is asked to free up and before this gets deleted if Application B started using it) then it will assert the debug label repository. This will lead to RPD crash with assert condition in releasing the label. In order to avoid this in future releases engineering team has added a sanity check to catch the inconsistencies in label repository and to clear it rather than crashing the RPD.

1189194

The twamp server does not work in the routing-instance

When twamp server is configured with "routing-instance-list", and if the target-address configure on twamp client is an si- interface address on twamp server, the twamp server might not work.

1192238

Error message generated: task_get_socket: domain AF_UNIX type SOCK_STREAM protocol 0task_connect: addr /var/run/mplsoamd_control: No such file or directory

On EX Series Switches, configuring MPLS might result in the following messages being logged. These messages do not imply operational impact and can safely be ignored. Jun 15 15:11:04 Switch rpd[1420]: task_get_socket: domain AF_UNIX type SOCK_STREAM protocol 0task_connect: addr /var/run/mplsoamd_control: No such file or directory

1205546

SMID daemon stopped responding to the management requests

SMID daemon has stopped responding to the management requests after a jl2tpd (L2TP daemon) crash on an MX960 BNG.

1222250

2017-07 Security Bulletin: Junos OS: SRX Series: Cluster configuration synch failures occur if the root user account is locked out (CVE-2017-10604)

When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Refer to JSA10806 for further details.

1249770

Interim accounting records are being sent every 5 minutes post SSD upgrade or configuration change

On MX Series routers, after GRES or configuration change that leads to Packet Forwarding Engine process (pfed) generating a core file and restarting, the routers might send for every single session 5 AcctInterim update.

1289943

On EX3400, the PHP process consumes 100% of the CPU load during VLAN-ID list creation via a J-Web session

The PHP process on the switch consumes 100% CPU load during VLAN-ID list creation via a J-web session

1303491

The kysncd process might crash after removing and inserting backup RE in analytics and "mpls sensor" scenario

On all junos platforms with JVision, Multiprotocol Label Switching (MPLS) stats sensor and graceful routing engine switchover (GRES) configured. The kysncd process might crash when the backup RE is removed/inserted.

1311158

Qfabric: cosd coredump generated during electrical power off of master member RSNG

On QFabric, coredump of cosd can be observed on RSNG/NNG some times if the configuration includes FCset configurations applied with non-wild card on all interfaces that includes AE interfaces. Sample non-wild card configurations is as follows: set class-of-service interfaces ae0 forwarding-class-set fcoe_fc_set output-traffic-control-profile fcoe_tc_profile set class-of-service interfaces ae0 congestion-notification-profile fcoe_cn_profile set class-of-service interfaces ae0 unit 0 classifiers ieee-802.1 fcoe_cl The known trigger for the core dump are: * COSD crashes when manually restarted twice after boot. Later it can crash on every restart * On RSNG/NNG, if cosd gets restarted once on active device and later RE switch-over then COSD on new master RE crashes. COSD crashes on subsequent switchovers too. To recover from this issue, the RSNG needs to be rebooted.

1312286

The MPC1/2 or the builtin MPC in MX5/10/40/80 might crash due to CPU hogging after the chip fails to initialize

The qxchip_pre_init() waits on the PLL lock for which it waits for lock_reg register value to have locks for PCIE, HSL2, and core registers. Qxchip_read_u32() which reads the above lock register does a pio i2c access which in turn has delays for the transmit to complete. This can trigger the CPU thread for any process after the chip fails to initialize.

1329932

The rpd might crash on backup RE after BGP peer is deleted

If Nonstop active routing (NSR) is configured, after a Border Gateway Protocol (BGP) peer is deleted, the peer is not removed from the BGP import evaluation list on backup Routing Engine (RE). When the import evaluation background job is scheduled, it would access this freed BGP peer and the rpd would crash on backup RE. This is a day-1 timing issue.

1334966

The IPsec rule might not work if both IPv4 ANY-ANY term and IPv6 ANY-ANY term are configured for it

When IPsec service is configured on MS-MPC/MS-MIC, the IPsec rule might not work if both IPv4 ANY-ANY term and IPv6 ANY-ANY term are configured for it. This is because of rule matching without type check. It is a day-1 issue.

1336455

Momentary dip in traffic when a GRES is performed

On GRES the implicit filters set by DFWD are cleared by DCD. Hence we are seeing a momentary dip in traffic.

1337591

Some IGMP groups might have wrong upstream interface due to discard route is installed in PIM

On all Junos platforms enabled with Protocol Independent Multicast(PIM) sparse mode and Internet Group Management Protocol(IGMP), when it is connected with the upstream PIM node via two interfaces A and B, in which A is the Reverse Path Forwarding (RPF) interface with the multicast traffic flowing through, and B is the non RPF interface(for example, a Layer 2 integrated routing and bridging interface), if there is some network change which leads to all PIM status cleanup, and causes the multicast traffic starting to flow through B instead of A, some IGMP groups might still have upstream interface A due to discard route is wrongly installed in PIM and couldn't get timeout.

1342019

Configuring the same DHCP server in different routing-instances is not supported in DHCP relay scenario

In DHCP relay scenario, commit error is printed when trying to configure the same DHCP server in different routing-instances.

1345296

A firewall filter might not be programmed in PFE even though TCAM entries are available

On EX4300 platforms, when changing the prefix list of the firewall filter, the firewall filter might not be programmed in PFE even though PFE shows enough TCAM entries are available. The system might go into the error state and the failed filter might not work.

1345994

If CVLANs range is 16 it might not pass traffic in a Q-in-Q scenario

If CVLAN (customer virtual local area network) range 16 (e.g., vlan-id-list 30-45) is configured in a Q-in-Q (i.e., 802.1ad) scenario, all the 16 VLANs might not pass traffic.

1348618

On EX4300 platforms, traffic drop might happen if LLC packets are received with DSAP and SSAP as 0x88 and 0x8e

On EX4300 platforms, traffic drop might happen if LLC packets are received with DSAP and SSAP as 0x88 and 0x8e respectively. On other platforms, traffic drop might happen when dot1x is configured.

1348698

The RE might get into amnesiac mode after restarting if 'excess-bandwidth-share' is configured

If 'excess-bandwidth-share' is configured under 'class-of-service interfaces', the mgd will fail to validate the configuration during the Routing Engine (RE) reboot. And the validation failure will cause the RE to go into amnesiac mode.

1348846

In certain scenario on MX-VC with L2TP LNS the DHCPv6 Solicit packet might be dropped

If the L2TP LNS is deployed on an MX Series Virtual Chassis (MX-VC) and the Virtual Chassis Port (VCP) is configured on MPC3E/MPC4E/MPC5E/MPC6E/MPC2E-NG/MPC3E-NG, the DHCPv6 Solicit packet might be dropped on L2TP LNS when the packet is received over a VCP port and the anchor Inline Service Interfaces (si-) exist on the same Packet Forwarding Engine (PFE) as the VCP port.

1350098

The MPC might crash when the MIC is removed

When the MIC is removed from the MPC, the MPC might crash.

1351765

In dual stack subscribers scenario with NDRA pool configured, the linked pools are not used when the first NDRA pool is exhausted

On MX and M platforms, dual stack subscribers are configured to use Neighbor Discovery Router Advertisement (NDRA) pools, if the first NDRA pool is exhausted, the linked NDRA pools are not used.

1353471

DHCP relay agent will discard DHCP request message silently if the requested IP address has been allocated to the other client

On all Junos platforms which support Dynamic Host Configuration Protocol (DHCP) relay agent, if a DHCP client sends a DHCP request message which contains the requested-IP option, and the requested IP address has already been allocated to the other client, the DHCP request message will be discarded silently by the DHCP relay agent. Due to this issue, the DHCP client will keep sending DHCP request messages and can't receive any reply packets. It is a corner case.

1354738

Nondeterministic load balancing of RE generated traffic is observed

RE generated traffic routed over NH is randomly sent via all available LSP paths when CBF configured.

1356868

The fxpc cores might be observed after deleting/deactivating sFlow interface on QFX5100 platforms

On QFX5100 platforms with sFlow enabled, when deleting/deactivating the sFlow interface, all other interfaces might go down and fxpc cores will be observed.

1357427

RE switchover during backup RE being not GRES ready might cause linecard restart, RE kernel crash and multiple chassisd crashes

On all Junos platforms with dual Routing Engines (RE), if Graceful Routing Engine Switchover (GRES) is enabled to provide High Availability (HA) protection, the backup RE (RE1) might be out of synchronization with the master RE (RE0), and the kernel state in the backup RE (RE1) is not cleaned due to a software defect. After staying in such status for a long time, once the keepalive timeout is detected between the master and backup RE, the backup RE (RE1) will take over the mastership. All the line cards will be restarted when they are connected to the new master RE (RE1) after switchover due to the missing of master-backup synchronization. Then the new master RE (RE1) might crash due to some data structure field overflows in the kernel since the kernel state has not been cleaned for a long time. After that the original master RE will take the mastership back again. The issue will cause complete traffic loss.

1358339

When attempting to scale clients saw sdbsts_lock_holder.bbe-smgd.pid10686.core cores.

When attempting to scale clients saw sdbsts_lock_holder.bbe-smgd.pid10686.core cores. These types of core dumps are result of a rare timing of locking deadlock between SDB secondary table and STS hash lock.

1360216

MC-LAG peer does not send ARP request to the host.

On EX4300/EX4600/EX9200/QFX3500/QFX3600/QFX5000 Series switches, MC-LAG peer might not send ARP request to the host.

1361617

VC-Bm can't sync with VC-Mm when the Virtual-Chassis splits then reforms

In MX-VC scenario, if any events that might cause the Virtual-Chassis to splits then reforms such as VCP port flapping or backup restart etc happens, Master Routing Engine in Virtual Chassis backup router (VC-Bm) might not sync with Master Routing Engine in Virtual Chassis master router (VC-Mm).

1362542

L2TP Access Concentrator (LAC) tunnel connection request packets may be discarded on LNS device

In subscriber management environment where LNS is deployed, if frequently changing the "local-gateway" of an L2TP tunnel on LNS device using "replace" command, the gateway may not be operational and the tunnel connection request packets sent by the corresponding LAC devices (having "remote-gateway" matching the LNS's gateway) may be discarded on LNS device.

1363408

The process rpd may crash during P2MP LSPs churn

In MPLS scenario with RSVP-signaled point-to-multipoint (P2MP) LSPs configured, rpd may crash during P2MP LSPs churn.

1364657

The parity errors in Layer 3 IPv4 table in the PFE memory might cause traffic blackhole

On QFX5100/EX4600 platforms, the device might get into an improper state where it is unable to correct parity errors in the PFE memory. Traffic blackholing might be seen for specific destination IPs.

1364811

[ACX] Commit error seen when configuring "mac-table-size" under bridge domain after upgrade to 15.1R7

On ACX1x00/ACX2x00/ACX4x00 running in 15-releases previous to 15.1R8, when configuring "mac-table-size" under bridge-domain, a wrong commit error appear not allowing the commit to pass.

1366746

The chassisd might crash after issuing the CLI "show chassis hardware"

* On QFX5000 Series switches in VC/VCF scenario, the chassisd might crash after issuing the CLI "show chassis hardware". This can result in VCP down and traffic drop.

1368258

Hashing does not work for the IPv6 packet encapsulated in VxLAN scenario

On QFX5000 Series switches, IPv6 traffic over VxLAN tunnel does not hash, this might result in some unexpected issue in ECMP scenario.

1368913

On QFX5k Series switches ISIS adjacency with Cisco might go down

On QFX5k Series, If ISIS packet is received with DMAC as 09:00:2b:00:00:05 (ISO 9542, All Intermediate System Network Entities Address) and Jumbo frame with EtherType as 0x8870 (non-standard, used by Cisco), such packet will be dropped, resulting in failure in the adjacency.

1369424

When native-vlan-id is configured for AE LACP session to multihomed server goes down

When native-vlan-id is configured for AE LACP session to multihomed server goes down if you have irb.0 configured. This causes incorrect parameters being pushed to PFE causing LACP PDUs to not egress correctly.

1369785

MAC move might occur in DHCP security scenario

On EX4300/EX4600/QFX Series switches except QFX10000, in DHCP security with override no-option82 scenario, if the DHCP packets from DHCP clients are received from the DHCP snooping trust interface (by default, all trunk ports on the switch are trusted), such packets might be sent back on the same interface, resulting in the MAC move of the source MAC on the other L2 devices.

1373053

Dot1x memory leak is seen if 'no-mac-binding' is configured

On EX2200/EX2500/EX3200/EX3300/EX4200/EX4500/EX6200/EX8200 Series switches in dot1x scenario, if the trunk port is used with 'no-mac-binding' configured, a memory leak (125 Bytes per dot1x event) can be seen.

1374295

Address pool does not correctly cycle to the beginning of the pool when linked-pool-aggregation parameter is defined

In subscriber scenario, when "linked-pool-aggregation" is enabled on MX platform, the address pool might not cycle to the beginning of the pool and it might report "Out of Addresses" even though not all addresses are in use.

1375189

The 802.1P rewrite may not work on inner VLAN

If a logical interface (IFL) is configured with 802.1P rewrite-rules (for both outer and inner VLAN) and fixed classification, after deactivating Class of Service (CoS) on any other IFL, the packets sent from this IFL may still have the original 802.1P bit set in the inner VLAN without being rewritten.

1375716

The 'accept-remote-source' knob configured on the core interface might cause traffic outage

In MVPN environment, the 'accept-remote-source' knob is designed to configure under a vrf instance where the traffic is coming. If it is configured on the core interface where traffic is not expected, some unusual things would happen and it might cause traffic outage or failure.

1377298

The auto-negotiation interface might go down if the opposite device supports only 10/100M auto-negotiation

On the QFX5100 platform, the auto-negotiation interface might go down if the peer device supports only 10/100M auto-negotiation

1377521

DHCP Discover packets might be dropped if there is VXLAN configured

On QFX5000/EX4600 platforms, if changing an interface from Virtual Extensible Local Area Network (VXLAN) to a member of an Aggregated Ethernet (AE) interface, the Dynamic Host Configuration Protocol (DHCP) relay would not work and the DHCP client would not get IP address normally.

1377525

Dot1x dynamic VoIP VLAN assignment might cause mac limit exceed if voip-mac-exclusive configured

In interface security and VoIP scenario with mac-limit and voip-mac-exclusive enabled, on EX2200/3200/3300/4200/4500/4550/6200/8200 platforms, if Dot1x supplicant receives dynamic VoIP VLAN from RADIUS server using JUNIPER_VOIP_VLAN attribute and local VoIP VLAN is different from the dynamic VoIP VLAN (or no local VoIP VLAN), the voip-mac-exclusive is invalid and the MAC limit might exceed on interfaces. The issue might result in unexpected interface security action like shutdown.

1377690

Duplicate IP cannot be configured on both SONET (so-) interface and other interfaces

On MX platform, if configuring duplicate IP on both SONET (so-) interface between other type interface, other type interface might not get the IP address.

1379936

The DHCP packet might be incorrectly flooded /replayed back out of the interface it is received

On EX6200/EX8200 platform with examine-dhcp, the DHCP packet might be incorrectly flooded /replayed back out of the interface it is received, this might lead to incorrect 'mac-move' errors (on the device connected to EX6200/EX8200) and loss of traffic for the client MAC.

1380991

[ EX4550 ] / [ 15.1R6-S2.1 ] Post upgrade to Junos OS 15.1R6 one of the port (ge-0/0/22) is not coming up

Post upgrade to Junos OS 15.1R6-x one of the port (ge-0/0/22) is not coming up on standalone ex4550 switch. The reason being MACSec bypass is not set on the port for unknown reason. As suggested by Vendor, a workaround is added to enable macsec bypass if not set during PHY init.

1381888

SSD lifetime might be shorten in OVSDB environment

In Open vSwitch Database (OVSDB) environment with Solid State Drive (SSD) installed on the backup RE side, master RE copies /var/db/ovsdatabase to backup RE in very short interval (e.g. every 10 seconds), and the backup RE might write the whole ovsdatabase file to the SSD card frequently. Therefore, the SSD lifetime might be shorten due to the exceeded amount of read/write. Due to this issue, the SSD card failure might be observed.

1382191

L2PT is not working as expected when using Lag interface with more than one child interface for STP traffic with Cisco switch

Issue is specific to case where the STP packet ingress interface is AE and L2PT is configured. As part of MACSEC feature(15.1), there is an option to configure eapol-address to be provider group address (01:80:C2:00:00:00) which uses STP MAC. These packets needs to be sent to interface and not on AE. To handle this, there is an implementation not to populate aggregate IFD index if the packet destination MAC is "01:80:C2:00:00:00". Due to the above change, the STP packet flooded on the customer VLAN, had the source IFL not of AE(trunk). If the flooded STP packet choose the interface different from the ingress interface among the AE(possibly when the Peer is not juniper due to different hash logic), local port filtering did not happen(expected).

1382531

Flows are getting exported before the expire of the configured active timeout value

The export of the Jflow records is seen at the collector before the expire of the configured active timeout value. This export result might not be the expected.

1382857

dcd restarted unexpectedly after committing a configuration with static demux interface stacking over ps interface

The static demux interface stacking over ps interface is not supported and can cause the dcd process to restart. The commit process should not allow such configuration.

1382893

On EX4300 loss-priority high set to multicast packets is overridden

On EX4300 platform, if loss-priority high is set to multicast packets by a classifier at ingress interface, it will be then overridden by storm-control filter. Hence subsequent CoS (Class-of-Service) stages, such as rewrite rules at egress, might fail to work due to incorrect loss-priority value.

1383964

Twice NAT not supported on FTP ALG causes MS-PIC crash

FTP ALG (Application Layer Gateway) is not supported with Twice NAT (Network Address Translation). When an unsupported translation type is configured on an M or MX series platform working as FTP ALG, the Multiservices PIC crashes. With the fix of this PR, a syslog message will be displayed instead of triggering a crash.

1384362

To provide an option to disable lldp/ptopo traps per interface

 

1386873

The rpd might crash after issuing operational command "show route detail" for RIP route

The rpd might crash and core after issuing operational command "show route x.x.x.x/xx detail" for RIP route, the routing table will become unstable during the crash.

1387746

Penultimate-hop router does not install BGP LU label causing traffic blackhole

On the penultimate-hop router in BGP LU (labeled unicast) scenario using PHP (penultimate-hop popping), when a link flap causes the next-hop of a label received from the egress router to change, once the link comes back, the penultimate-hop router might fail to install the clone route (S=0) entry for that label and result in traffic blackhole.

1388595

The bbe-smgd might not respond the NS message for the SLAAC client on dynamic VLAN

On all MX-Series with dynamic VLAN and NDRA deployment for the subscriber access, the SLAAC (Stateless Address Autoconfiguration) client might not get the gateway MAC address from the BNG (Broadband Network Gateways), as a result, the SLAAC client will not get a link-local prefix and the IPv6 global connectivity will not be established.

1388867

The bbe-smgd process generates repeated core-dumps and stops running as a result of long term session database shared memory corruption.

On MX platforms, if committing config involving changes to dynamic profiles, the bbe-smgd process might generate repeated core-dumps and stop running as a result of the corruption of database session shared memory.

1389444

Keep running some VTY command may crash the QFX5100's PFE due to micro-kernel memory leak

Keep running some VTY command may crash the QFX5100's PFE due to micro-kernel memory leak

1389461

The interface-control process thrashes and dcd does not restart after adding an invalid demux interface to the configuration

On M120 and MX platform, if an invalid non demux0 interface, such as demux1, is committed to the configuration, the interface-control process will thrash and the dcd process will not restart.

1391411

Usage-Monitoring-Information AVP as part of PCRF gx-plus provisioning is causing service accounting activation.

Usage-Monitoring-Information AVP as part of PCRF gx-plus provisioning is causing service accounting activation.

1391753

IGMP query packets might be duplicated between L2 interfaces

IGMP query packets might be duplicated between L2 interfaces with IGMP Snooping is enabled.

1391767

The rpd core file may be dropped due to a soft assert if non-BGP protocol route with an AS_PATH is used

Rpd's route selection mechanism has multiple user-configurable mechanisms by which route ordering may be changed. To assist with debugging issues with defects in the route selection code, a function would generate a low priority soft core that didn't crash rpd when route selection was incorrect. However, there have been circumstances wherein not-best was incorrectly being determined. One such situation that is addressed in this PR involves when routes are learned or redistributed from non-BGP protocols and had an AS_PATH attribute. Using BGP route selection rules, if a BGP route and a non-BGP route had a leading AS_PATH with the same AS, BGP MED selection rules for grouping were being applied. Such MED election should only be done using BGP-only routes. Such a situation can come from various BGP carried VPN protocols wherein routes from the VPN protocol generated IPv4 routes when redistributed from one routing instance to another. An example of this would be an EVPN route.

1391847

L2TP subscribers might be stuck in init state in a corner case

On MX platforms enabled with Next Generation Subscriber Management, if Layer 2 Tunneling Protocol (L2TP) is configured, when there is an IP connectivity loss between L2TP Access Concentrator (LAC) and L2TP Network Server (LNS), which will lead to tunnels teardown and re-negotiation, in addition to that, the bbe-smgd process restart at the same time, some affected L2TP subscribers might be stuck in init state and can't login successfully in this corner case.

1402483

The PFEM might crash on EX2200 and EX3300 when adding class-of-service scheduler-maps and firewall configurations

On EX2200/EX3300 Series platforms, the PFEM core might be seen when adding class-of-service scheduler-maps and firewall configurations, which might cause all the interfaces to flap.

1404325

The FPC might crash in a CoS scenario

If MPC1/MPC2 are used ("Trio" based MPCs) in HCoS scenario, the FPCs might crash due to an invalid IFL referred by the dynamic bbe subscriber interface.

Related Links: