Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

17.4R2-S7: Software Release Notification for Junos Software Service Release version 17.4R2-S7



Article ID: TSB17640 TECHNICAL_BULLETINS Last Updated: 24 Sep 2019Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, Network Agent
Alert Description:
unos Software Service Release version 17.4R2-S7 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

Junos Software service Release version 17.4R2-S7 is now available.

The following are incremental changes in 17.4R2-S7.

PR Number Synopsis Description

The logical interfaces might not come up if scaled logical interfaces exist

On ACX5K platform, if scaled logical interfaces exist, the logical interfaces might not all come up.


In a BGP/MPLS scenario, if the next-hop type of label route is indirect, disabling and enabling the "family mpls" of the next-hop interface might cause the route to go into a dead state

In a BGP or MPLS scenario, if the next-hop type of label route is indirect, then the following changing events about the next-hop interface MPLS family might cause the route to be in DEAD state, and the route will remain dead even when the family MPLS is again activated. The following events occur: Deactivating and activating the interface family mpls Deleting and adding back the interface family mpls Changing maximum labels for the interface Note: When a labelled route is resolved over an interface, that interface must have family mpls configured for the route to be successfully resolved. Otherwise the route does not get resolved.


Multihop eBGP peering session exchanging EVPN routes can result in rpd core when BGP updates are sent

When eBGP multihop sessions exchanging EVPN routes are configured, a core can result due to an internal error.


Incorrect packet statistics are reported in the ifHCInUcastPkts OID.

The total number of packets is less than the sum of unicast, multicast and broadcast packets due to lag in read depending on packet rate. Now the total packets is set to the sum


i40e NVM upgrade support for PTX platforms

Adding support for i40e NVM upgrade in PTX3000 platforms


Trinity JNH memory leak when adding and removing unicast NH

Junos MPC memory leak when adding and removing unicast Next-hops


MPLS routes might be dead if MPLS is disabled/deleted from the interface and enabled/added back to the same interface or the maximum number of labels is changed in quick succession without a delay

If family MPLS is disabled/deleted from the interface and enabled/added back to the same interface or the maximum number of labels is changed in quick succession, without a delay, the routes might be dead in the forwarding table with a label using this interface as out interface. Note: It is always recommended to add a slight delay (5 seconds is recommended) for this issue. Otherwise, the current fix also might not work and routes could remain dead.


Laser receive power of extended ports is higher than the output power of the peer link

On Junos Fusion aggregate device platform, the interface diagnostics optics output of the extended ports shows the laser receive power is higher than the output power from the peer link. This is due to the Rx Optical power value received by Junos from SNOS is a raw Rx value, it has to be converted to nano-watts.


QFX5210: MPLS LSP ingress statistics not incrementing / zero

Statistics of transit traffic does not increment LSP statistics signaled by RSVP-TE.


TCP sessions might be taken down during RE switchover

On MX10K platforms enabled with Graceful Routing Engine Switchover (GRES) and Non Stop Routing (NSR), if the router runs with Transmission Control Protocol (TCP) based routing protocol (e.g. Border Gateway Protocol, BGP), and establishes TCP sessions with the remote peers, the execution of RE switchover might cause few TCP sessions being taken down and re-connected. Due to this issue, the TCP session re-connection will impact the related routing protocol session and therefore impact the traffic. This is a timing issue.


The receivers belonging to a routing instance may not receive multicast traffic in an Extranet next-generation MVPN scenario

In an Extranet next-generation MVPN scenario, a rare corner issue may be observed that the multicast traffic may not be forwarded to the receivers to a routing instance.


MAC addresses might disappear if the interface MTU of EVPN PE is changed

In EVPN Multihoming scenario, if the MTU of CE facing interface on PE (i.e., configured with ESI, 'set interfaces ae0 unit 1 esi 00:11:22:33:44:55:66:77:88:99') is changed, the MAC addresses learned from remote PE might be deleted and not added back, resulting in EVPN traffic loss.


EX4300 device chooses wrong bridge-id as RSTP bridge-id

Under RSTP scenario, EX4300 chooses wrong bridge-id as RSTP bridge-id. It might cause loops in the networks.


A RSVP-signaled LSP might stay in down state after a link in the path flaps

In RSVP (Resource Reservation Protocol) LSP (Label Switched Path) with loose or undefined path scenario, the LSP might stay in down state due to loop detection after the link in the path flaps.


BGP IPv6 routes with IPv4 nexthop causes rpd crash

When a BGP import policy changes IPv6 routes to have IPv4 nexthop, rpd might crash during route resolution. With the fix, changing route to have nexthop with different address family will not be allowed, if the route table does not have that resolution family configured.


[ACX5k] frequent syslog message acx_cos_tcp_bind_queues:736 parent acx_cos_tcp_ifd for ifd:ae0 doesn't exist for ifl -.

On 17.3 and later releases, ACX5000, PFE syslog frequently shows the following errors messages: acx_cos_tcp_bind_queues:736 parent acx_cos_tcp_ifd for ifd:ae0 doesn't exist for ifl:549 In 17.3R3-S1 the error logs appear only from time to time, and this can be related with an interface flap. In 18.1R3, the logs appear constantly, without any interface flap. This message is related to HCOS checking (even without HCOS configured). In software fix, we should check if the aggregate interface has HCOS configured or not. If not, we should return gracefully from this function without throwing this error. This is a harmless message.


The rpd process crashes when LSP template for a provider tunnel is changed

In an MVPN scenario, when the P2MP LSP template for a provider tunnel is changed, the rpd process might crash due to the previous template not being unlinked correctly.


The BUM traffic might not be flooded in EVPN-MPLS scenario

In EVPN-MPLS (Ethernet VPN - Multiprotocol Label Switching) scenario with bridge-domains used, any configuration change which causes a BD (Bridge Domain) reincarnation (e.g. change of vlan-id-list under bridge-domains) might break the flooding of BUM (Broadcast, Unknown-unicast, Multicast) traffic. The issue leads to BUM traffic loss. All services that relying on BUM traffic might be impacted.


EVPN Type 2 MAC+IP route is stuck when the route Advertisement has 2 MPLS labels and Withdrawal has 1 label

In EVPN (Ethernet VPN) scenario, if the router receives a Type 2 MAC+IP route Advertisement having 2 MPLS labels, and then Withdrawal of the same route with only 1 label, the Withdrawal will not be processed and that route will be stuck.


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.


EVPN routes may show "Route Label: 0" in addition to the real label..

EVPN routes may show "Route Label: 0" in addition to the real label. The issue is cosmetic only and does not impact any functionality.


The rpd might crash due to a race condition with the combination of community actions done at both BGP import policy and a forwarding-table policy

On all Junos platforms enabled with Border Gateway Protocol (BGP), if BGP import policy is configured with community actions, and the forwarding-table is also applied with a policy with community actions, the rpd process might crash due to this issue. It's a very corner case which happens in a race condition.


FPC crash and slow convergence upon HMC Fatal error condition when inline-jflow is used

On MX platforms using MPC7E, MPC8E, MPC9E, MX10k-LC2101 or MX10003, when inline-jflow application is used, Fatal error on Hybrid Memory Cube (HMC) will perform "disable-pfe" action. Since Jflow records are hosted on the HMC memory partition, reading and writing to the HMC memory might trigger FPC crash and high FPC CPU utilization, causing slow convergence (adding/deleting routes or nexthops) for other PFEs on the same FPC carrier.


The rpd might crash after NSR switchover in EVPN scenario

In BGP (Border Gateway Protocol) with EVPN (Ethernet VPN) scenario, after RE (routing engine) NSR (Nonstop active Routing) switchover, the rpd might crash on the new primary RE when BGP is trying to withdraw an EVPN route which is mirrored from the old primary but not yet active created in the routing table. Traffic disruption might be seen during the rpd crash.


Dynamic profile misconfiguration along with simultaneous subscriber login might lead to orphan filters on the PFE resulting in login issues for subsequent subscribers

In access network with more dynamic profile (such as "dp-suspend" and "dp-redirect" in this case) scenario, If "dp-suspend" is configured with some misconfiguration (such as missing "variables" and so on) and "service-filter" for some services, these services will unactivated when a subscriber attempts to log in and is authenticated by RADIUS. The race condition between "dp-redirect" (with HTTP redirect servers services) and "dp-suspend" will lead these services of these dynamic profiles to be stale state on PFE when multiple subscribers which hitting the above-unactivated services logging in simultaneously. Especially, if this login action of these subscribers for a long time, it will speed up this race condition and enlarge the impact fo login of subsequent subscribers.


MX-MPC2-3D-EQ and MPC-3D-16XGE-SFPP will now show "Exhaust A" temperature, rather than Intake temperature.

MX-MPC2-3D-EQ, MPC-3D-16XGE-SFPP and other MPCs prior to MPC5 will now show the "Exhaust A" temperature, rather than "Intake" temperature, in "show chassis fpc", "show chassis fpc detail", and via SNMP (Object Name jnxoperatingtemp, OID: Exhaust and Intake temperatures are still available in "show chassis environment". Note that MPC5, 6, 7, 8, 9 already show the "Exhaust A" temperature.


Unrelated AE interfaces might go down if committing configuration changes

On all Junos platforms, if VRRP is running upon AE interfaces while committing any configuration changes related to AE interfaces, unrelated AE interfaces might go down.


A steady increase of the PFE heap memory utilization may happen when PPPoE subscribers are flapping

On MX-Series platform with TRIO MPC installed, PFE heap memory is leaking steadily when thousands of PPPoE subscribers connected via AE (Aggregate Ethernet) interface are flapping continuously.


The vlan tag is wrongly inserted on the access interface if the packet is sent from an IRB interface

With access interface configured on MPC7E/MPC8E/MPC9E/MX10k-LC2101/MX10003/MX204, the vlan tag is wrongly inserted on the access interface if the packet is sent from an IRB interface.


Junos fusion / v44 / Incorrect power values for extended optical ports

On junos fusion setup there is no support to read rx power values considering internal calibration. Hence low rx power values are read across satellite node interfaces. This stands addressed through revised SNOS image. SNOS images carrying fix : 3.5R1.4 and 3.2R4.8 Issue would not be seen on JUNOS compatible with these images.


The snmp query may not get data in scaled l2circuits environment

When a large-scale AE interfaces are configured with a large-scale l2circuits, if executing snmpwalk on interface OID's, the query may time out and the data could not be retrieved. When the issue occurs, below error could be observed. user@router> show snmp mib walk ... ifInOctets.70781 = 75155380 Request failed: General error user@router> show snmp mib walk ifHCInOctets ifHCInOctets.831 = 340482960268874 Request failed: General error It is to be noted that all general errors are not an issue. If there are interface flaps and churns in the system during which snmp query happens on the same interface which is flapping, then general error is the way to report it because stats cannot be fetched during the churn/flap duration.


Number of inet-arp policers implemented on ACX 5k has been increased from 16 to 64

Number of inet-arp policers is increased from 16 to 64 for ACX5K.


The CPU utilization of the rpd process is stuck at 100% if BGP multipath is configured

In BGP with the indirect next-hop scenario, if BGP multipath enabled, a background job loop might be formed and the CPU utilization of rpd process might be stuck at 100%. In this software issue, JUNOS RPD daemon will flash the route even if the route has not changed. This only applies for the indirect nexthop case.


The SRRD might crash when memory corruption occurs

The SSRD (sampling Route-Record Daemon) process may restarts when it can not allocate memory.


The swap memory is not initialized on boot on ACX5048/5096

On ACX5048/5096 platforms, the swap memory is not initialized by default on boot. If SRAM is completely filled, then some inactive pages will be swapped to the swap memory. If the swap memory is not enabled then the new process might fail to start.


Traffic blackhole might be seen due to a long LSP switchover duration in RSVP-signaled LSP scenario

In RSVP-signaled LSP scenario with LSP bypass path configured, when all interfaces on a transit node along primary LSP are brought down, the LSP might not go down on the ingress node, it will take 3-4 minutes before LSP switchover begins and cause a long traffic blackhole.


Some IPsec tunnels might fail to pass traffic after GRES on MX platform

On all MX platforms running with IP security (IPsec) scenario, if Graceful Routing Engine Switchover (GRES) is executed, and some IPsec Security Associations (SAs) are going to reach the hard life time expiry just before the GRES, the new primary RE might not delete the expired IPsec SA pair entry from the kernel. Due to this issue, some IPsec tunnels might have traffic drop or ping failure after the IPsec SA re-key.


The deletion of (S,G) entry might be skipped after the PIM join timeout

On all Junos platforms enabled with Protocol Independent Multicast (PIM), the deletion of (S,G) entry might be skipped after the PIM join timeout in some rare conditions, if Multicast Virtual Private Network (MVPN) is configured in rpt-spt mode, there might be a creating problem for the affected (S,G) entry since the PIM (S,G) discard entry seems to be retained. Due to this issue, the traffic is not able to hit the MVPN installed (*,G) entry, hence it will be blocked.


The BGP session might flap after RE switchover

On MX platforms enabled with Graceful Routing Engine Switchover (GRES) and NonStop Routing (NSR), in a rare case, BGP peers might flap after the execution of RE mastership switchover or due to BGP flap in backup routing-engine.


The rpd crash might be seen if l2circuit/local-switching connections flap continuously

On all Junos platforms, if there are multiple interfaces configured under a single l2circuit/local-switching, and each of these interfaces has a description field configured under them, when l2circuit/local-switching connections flapping continuously, memory usage increment might happen, eventually, it will result in rpd crash because of running out of memory.


LDP might not update the LDP ingress route metric when inet.3 route flash happens before inet.0

LDP route metric might not match IGP route metric even with "ldp track-igp-metric" configured.


The system does not reboot or halt as configuration when encountering the disk error

When the system encounters disk error or halted system (ex. memory leak), the chassisd might go in hung state with the blow error messages even though "disk-failure-action reboot" or "disk-failure-action halt" is configured.


The rpd might crash if no-propagate-ttl is configured in BGP multipath scenario

In BGP multipath scenario with labeled-unicast (LU) enabled, if no-propagate-ttl is configured, the rpd might crash if BGP LU route's ttl action is changed after which it does not match BGP multipath cache.


Upgrade from pre 17.4R1 release results in cfmd coredump

On MX/ACX series, in CFM ethernet OAM scenario, after the upgrade from 17.4 onwards, the cfmd coredump might be seen after committing configuration on CFM (connectivity-fault-management).


The rpd might crash in PIM scenario with auto-rp enabled

In PIM scenario with auto-rp enabled, when both of a PIM session task and an auto-rp session task are being closed by rpd very near to each other, and the auto-rp task has got terminated before the PIM task is about to terminate, then the rpd process crashes.


The rpd might crash while removing multicast routes that do not have an associated (S,G) state or activating the "accept-remote-source" knob on PIM upstream interface

In MVPN scenario, the rpd might crash while removing multicast routes that do not have an associated (S,G) state or activating the "accept-remote-source" knob on PIM upstream interface.


The policer bandwidth might be wrong for the aggregate interface after activating the knob 'shared-bandwidth-policer'

On MX Series with MPC, if an AE interface is with the filter of 'shared-bandwidth-policer' and the knob 'shared-bandwidth-policer' is deactivated, after activating the knob 'shared-bandwidth-policer', the policer bandwidth might be calculated as 0 and all traffic might be dropped for the AE interface.


The rpd would core dump due to improper handling of Graceful Restart stale routes

In BGP Graceful Restart scenario, including helper mode which is enabled by default, rpd would core dump due to improper handling of BGP Graceful Restart stale routes during the BGP neighbor deleting. The rpd would crash and service/traffic impact would occur.


Traffic loss might be observed after changing configuration under "protocols mpls" in ldp-tunneling scenario

If ldp-tunneling is configured for LDP over RSVP, after changing configuration under "protocols mpls", LDP might fail to add inet.3 route over RSVP LSP, hence cause traffic to be dropped in the network.


Subscribers coming from new IFDs might not login in due to 512 entries limit in the subscriber-limit table

On MX platforms, in subscriber management scenario, if the 512 entries are exhausted in the subscriber-limit table, the subscribers which come from new IFDs might not login in.


The jdhcpd memory leak might happen on MX5/MX10/MX40/MX80/MX104 when testing DHCP subscribers log-in/out

On MX5/MX10/MX40/MX80/MX104 Series platforms with DHCP server configuration for DHCP subscribers, the jdhcpd memory leak might happen and the memory increase by 15MB which depends on the number of subscribers when testing the DHCP subscribers log-in/out.


Stale MAC addresses are present in the bridge mac-table in EVPN/MPLS scenario

In EVPN/MPLS scenario, if many MAC (about 10k) addresses move from remote to local interface, some MAC addresses might never get cleared up from the bridge table due to next-hop is not getting cleared in time within the PFE. So they might remain present in the bridge MAC table even after the aging time (default 300s).


The l2circuit traffic might be black-holed at EVPN SPINE/MPLS LSP TRANSIT device if VXLAN access interface flaps on remote PE node(QFX5110)

When there is a L2circuit connection between 2 QFX5110 established through an EVPN SPINE/MPLS LSP TRANSIT device. If the VXLAN access interface flap at one QFX5110, it will cause corruption for l2circuit at the other QFX5110. So the l2circuit traffic is blackholed at MPLS transit node.


Link flapping with QSFPP-4X10GE-LR on MPC7E/8E/9E

On MX series routers with MPC7E/8E/9E installed, if optics QSFPP-4X10GE-LR (Part number 740-054050) is used, the link might flap.


The FPC might crash after the AE boundle flapping on local device and the configuration change on peer device occur at the same time

On QFX platforms, the FPC might crash after the AE (Aggregate Ethernet) boundle flapping on local device and the configuration change on peer device which can cause the interface down occur at the same time.


The CPU utilization on a daemon might keep around 100% or backup RE might crash in race conditions

The CPU utilization on a daemon might keep around 100% or backup RE might crash in race conditions (it may get hit or triggered at times by some churn in the system, no specific trigger).


Interfaces configured with flexible-vlan-tagging might loss connectivity

On QFX5000 series platform and related products (like ACX5K and EX4600), a port configured in service provider style (flexible-vlan-tagging) might lose connectivity over the native VLAN when additional tagged VLANs are added to it. The impact is that all the hosts' traffic over the designated native VLAN might be dropped.


Targeted-distribution for static demux interface over aggregate ether interface does not take correct lacp link status into consideration when choosing primary and backup links

The value of "lacp-port-mode" (or LACP mode on child-links of AE bundle) is always "0", irrespective of whether LACP is turned ON or OFF on AE bundle. Whereas the expectation is that as per the LACP mode (OFF/ACTIVE/PASSIVE) present on AE bundle, the same should be propagated to child-links. Since the lacp mode was not propagated to child links, Device Control Daemon (DCD) used to assign the links to subscribers only based on its physical status. But there were few links which were physically UP but lacp down, so traffic disrupted.


Removing SSH Protocol version 1 from configuration

You can no longer configure "set system services ssh protocol-version v1" on this JUNOS software.


DHCP offer packets towards IRB over LT interface getting dropped in DHCP relay enviroment

In DHCP relay enviroment, the DHCP offer packets from server might get dropped towards IRB (Integrated Routing and Bridging) over LT (Logical Tunnel) interface.


The resumed multicast traffic for certain groups might be stopped in overlapping MVPN scenario

In NG-MVPN scenario, if the receiver and the source exist in the different VRF instance of the same ingress PE, Type-5 (Source active AD route) and Type-7 (Source tree join route) routes might not be removed correctly after the multicast flow stop, and during this time the RP might prune the multicast tree to an incorrect SPT (shortest-path trees) using these Type-5 and Type7 routes. Then the resumed multicast flow will be dropped due to the wrong SPT.


The chassisd is unable to power off a faulty FPC after RE switchover which leading to chassisd restart loop

In the MX router with a faulty (e.g. hardware error) FPC (Flexible PIC Concentrator) installed, performing RE (Routing Engine) switchover or restarting chassisd which may cause chassisd restart loop. This issue will cause traffic lose completely.


Interfaces on PTX might not come up after FPC restart or port flap

On PTX platform, FPC-P2 with 15x100GE/15x40GE/60x10GE QSFP28 PIC interfaces might take a long time to come up or some ports never come up after reboot/the chassisd process restart/FPC restart/port flap.


RSVP Path message with long refresh interval is dropped between Junos pre-16.1 and 16.1+ nodes

Due to Refresh-Interval Independent RSVP (RI-RSVP) feature introduced in Junos OS Release 16.1, Path messages with long refresh interval (equal to or more than 20 minutes) sent from a Junos pre-16.1 node are dropped by the receiver running Junos 16.1 or later releases.


Test aaa ppp, output enhancement.

The output of "test aaa ppp" is missing "" tag.


Detached LACP member link gets LACP State as enabled in PFE when switchover because of device reboot

If particular set of events happened the status for detached LACP link may get turned on in PFE which may later create traffic blackholing for transit traffic.


In ACX, auto exported route between VRFs might not reply for icmp echo requests

In ACX, auto exported route between VRFs might not reply for icmp echo requests


The high CPU utilization of l2ald is seen after replacing EVPN config

The l2-learning CPU utilization might get high and remain stuck forever after switching configuration files several times between EVPN and non-EVPN (e.g VRRP) by loading the corresponding configuration file. Because of that some of the data in the device is not successfully clean up, when EVPN-config (virtual-switch) is removed and the Ethernet Segment Identifier (ESI) interface is configured in a non-EVPN routing-instance.


The transit packets might be dropped if an LSP is added or changed on MX/PTX device

On MX/PTX series platforms acting as a transit router, if the "set protocol mpls sensor-based-stats" and "ldp-tunneling" are used and when an LSP is added or changed, part of its data structure might not be freed which might cause the resources to be exhausted. Once the resource is exhausted, the kernel routing table (KRT) queue will be built-up and new routes cannot be programmed in the forwarding engine, in the end, the transit packets might be lost.


The dhcp-relay knob might not work on MX10008/MX10016 platforms

On MX10008/MX10016 platforms, if the dhcp-relay knob is enabled under the forwarding-option hierachy, either in default or non-default routing-instance, the Dynamic Host Configuration Protocol (DHCP) relay feature might not work as expected. Due to this issue, all the DHCP discovery packets couldn't be relayed.


Reachability issue of the host connected to the SD might be affected in Junos Enterprise Fusion environment with EX9200 series devices as AD

In Junos Enterprise Fusion environment with EX9200 series devices as AD, when the traffic originates from a peer device connected to AD and ICL is a lag, if the cascade port in an AD is disabled, such that the traffic has to flow through the ICL lag to reach the SD. Reachability issue of the host connected to the SD might be affected if one of the cascade/uplink link goes down.


Subscribers Login Fails when PCRF Server is Unreachable

In a scaled Subscriber Mgmt Setup,when PCRF (Policy and Charging Rules Function) Server is Unreachable or when Diameter Protocol is Down, a Subscriber Login may Fail to Successfully Establish a Session or may Fail to Bind a Service Policy Provisioned by GXplus/PCRF


Loopback address exported into other VRF instance might not work on EX/QFX/ACX platforms

On EX/QFX/ACX platforms, the loopback address exported into other VRF instance might not work.


Qfx10008: FPC0 cored after running the pfe command "show cos sched-usage"

Without this fix, the PFE cli "show cos sched-usage" will restart QFX10008's forwarding plane


"show cos scheds-per-pfe" and "show cos pfe-scheduler-ifds" pfe commands will restart forwarding planes on QFX10008 switches

Without this fix, "show cos scheds-per-pfe" and "show cos pfe-scheduler-ifds" PFE cli will cause the forwarding plan to restart on QFX10008 switches. See also PR1449645


There is high temperature from "show chassis environment" output after MPC4E insert to slot 5

The temperature sensor information of the FPC is not cleared when the FPC is removed from its slot. Due to this when a new FPC type is inserted into the slot, the data of the previous MPC is still being displayed. This stale data from the previous MPC is displayed until the fresh data from the new FPC type is populated in the same structure.


Few seconds of traffic drop might be seen towards the existing receivers when another receiver joins/leaves

With "protocol igmp-snooping" configured, if some receiver joins/leaves a group, few seconds of traffic drop might be seen towards the existing receivers.

Modification History:
First publication 2019-09-23
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search