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

20.1R3-S2: Software Release Notification for JUNOS Software Version 20.1R3-S2

0

0

Article ID: TSB18177 TECHNICAL_BULLETINS Last Updated: 30 Sep 2021Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, vMX, vSRX
Alert Description:
Junos Software Service Release version 20.1R3-S2 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
Risk Risk Description
Low/Notification - No defined time impact to take action Software Release Notification
Impact Impact Description
Low/Notification - Monitor the situation but no action needed Software Release Notification

Solution:

Junos Software service Release version 20.1R3-S2 is now available.

20.1R3-S2 - List of Fixed issues

PR Number Synopsis Category: Marvell based EX PFE ACL
1611480 The fxpc process might crash and generate core
Product-Group=junos
On EX4600/QFX5K platforms, the fxpc process might crash and generate core when router-advertisement-guard is configured under DHCP (Dynamic Host Configuration Protocol) forwarding-options.
PR Number Synopsis Category: EX2300/3400 PFE
1610253 DHCP packets might be received and then returned back to DHCP relay through the same interface on EX2300/EX3400/EX4300/QFX VC platforms
Product-Group=junos
On EX2300/EX3400/EX4300/QFX Virtual Chassis (VC) platforms which are connected to Dynamic Host Configuration Protocol (DHCP) server via DHCP relay, if the interface connected with DHCP relay is located on non master node, and the interface has the knob "dhcp-security" enabled under vlan, when the DHCP packets are received via DHCP relay and then need to be send out within the affected vlan through the same interface, the DHCP packets might get returned back to DHCP relay, instead of being dropped. Due to this issue, it might lead to Media Access Control (MAC) address move on DHCP relay and therefore bring potential risk of service impact.
PR Number Synopsis Category: BBE GRES related issues
1610476 The authd process and RADIUS might have stale L2BSA subscriber entries
Product-Group=junos
In subscriber management scenario, if JSU package for Broadband Edge Subscriber Management daemon (bbe-smgd) is installed on backup RE when it is syncing subscriber information from master then the authd process and RADIUS might have stale Layer 2 Bit Stream Access (L2BSA) subscriber entries which might cause subscribers logout and re-login.
1616611 Reboot of the Backup RE in a high scaled subscriber management environment may result in the system not returning to a GRES ready state
Product-Group=junos
Reboot of the Backup RE in a high scaled subscriber management environment may result in the system not returning to a GRES ready state. The backup RE will report that it is not GRES ready with errors that the "Standby mirror connection is not up" from the Master RE and that the "the replication-process subsystem is not running" from the Backup.
PR Number Synopsis Category: Border Gateway Protocol
1446499 The command "show task replication" might show BGP replication complete even before BGP NSR replication is completed
Product-Group=junos
The command "show task replication" might show BGP replication complete before NSR replication is finished.
1601163 Some routes might get incorrectly programmed in the forwarding table in the kernel with next-hop installed as DEAD
Product-Group=junos
On all platforms with high-scaled routes scenario, after Flexible PIC Concentrator (FPC) restart some routes might get incorrectly programmed in the forwarding table in the kernel with next-hop installed as "dead". This would lead to traffic impact. This is a timing issue.
1611070 The rpd may crash after a commit if there are more than one address in the same address ranges configured under 'bgp allow'
Product-Group=junos
If the 'bgp allow' feature is used and there are more than one address in the same address range, the rpd may crash on a commit with such configuration. And the subsequent commits related to BGP configuration change can cause rpd to crash as well.
PR Number Synopsis Category: BBE Remote Access Server
1600655 Subscribers might be stuck in terminated state when the radius server is unreachable
Product-Group=junos
In subscriber scenario, if RADIUS accounting backup is configured and the radius server is unavailable for more than 30 minutes, some subscribers might be stuck in terminated state and cannot be recovered even if the radius server is reachable.
1609403 Prefix duplication errors might occur for DHCPv6 over PPPoE subscribers
Product-Group=junos
On MX platforms with DHCPv6(Dynamic Host Configuration Protocol) over PPPoE(Point-to-Point Protocol over Ethernet) configured in BBE(Broadband Edge) environment, where the PPPoE sessions have delegated IPv6 prefix assigned from a local pool, when a DHCP session comes up over the PPPoE leading to a change to the PPPoE session?s address, an address-change notification would be triggered. The processing of this notification by general-authentication-service would result in wrong marking of the delegated IPv6 prefix as available. Once this happens, DHCP service might re-assign the same prefixes which would be rejected because of IP duplication.
1612196 DHCP session fails with CLI knob 'session-limit-per-username'
Product-Group=junos
On all Junos platforms with DHCP (Dynamic Host Configuration Protocol) over PPPoE (Point-to-Point Protocol over Ethernet) and 'session-limit-per-username' configured, if either interface or access configuration is modified while DHCP sessions are logged in, any new DHCP (v4/v6/PD/NA) session without authentication that uses the same access profile cannot log in.
PR Number Synopsis Category: Enhanced Broadband Edge support for cos
1607056 New subscribers might not connect due to the CR-Features service object missing on FPC
Product-Group=junos
On all MX platforms, in a subscriber management environment, new subscribers might not connect if CoS (Class of service) CR-features (Classifier Rewrite) are used by the VBF (Variable Based Flow) service. The reference count mismatching between RE (Routing Engine) and VBF is caused by VBF flow VAR CHANGE failure.
1613126 Traffic loss might be observed due to the shaping rate be adjusted incorrectly in a subscriber environment on MX platforms
Product-Group=junos
On MX platforms with subscriber management enabled, if Class of service (CoS) adjustment based on DHCP tags and Point-to-Point Protocol Over Ethernet (PPPoE) Intermediate Agent (IA) tags are enabled, and a first subscriber that triggered the creation of the interface set is Dynamic Host Configuration Protocol (DHCP), statically configured shaping rate for the parent interface set may be incorrectly adjusted to a very low value. In this case, traffic loss might be observed.
PR Number Synopsis Category: Device Configuration Daemon
1569399 ,Traffic might be interrupted while adding XE/GE interfaces as member of AE bundle
Product-Group=junos
On all Junos platforms, if XE/GE interface is having "set interfaces disable" configuration and XE/GE interface is added as a member of AE bundle and "delete interfaces disable" command is committed then in some rare scenario it might result in vmcore and cause the system to reboot. This leads to traffic impact. After vmcore system boots up and comes to normal state.
PR Number Synopsis Category: dns-proxy feature
1607867 DNS proxy functionality might not work on VRRP interfaces
Product-Group=junos
On all SRX platforms, if DNS proxy is enabled on VRRP interfaces, then DNS proxy functionality might fail to work.
PR Number Synopsis Category: JUNOS Dynamic Profile Configuration Infrastructure
1607494 Commit error: foreign file propagation (ffp) failed, reported for any type of change to dynamic-profiles.
Product-Group=junos
Commit error: foreign file propagation (ffp) failed, reported for any type of change to dynamic-profiles.
PR Number Synopsis Category: EVPN control plane issues
1600653 The device announces router-mac, target, and EVPN VXLAN community to BGP IPv4 NLRI
Product-Group=junos
On all Junos platforms, when L3VPN interoperates with EVPN(Ethernet VPN) VXLAN(Virtual Extensible LAN) instance, the device announces router-mac, target, and EVPN VXLAN community to BGP IPv4 NLRI(Network Layer Reachability Information) which is not the right routing table. As a result, the traffic to the L3VPN will be dropped.
PR Number Synopsis Category: Express PFE L2 fwding Features
1594255 ARP entry might be found missing intermittently post FPC reboot
Product-Group=junos
On some QFX series, using Ethernet Virtual Private Network (EVPN) with Virtual Extensible LAN protocol (VXLAN) when the Flexible PIC Concentrator (FPC) is rebooted, in rare occasions some of the Address Resolution Protocol (ARP) entries might be found missing intermittently on the FPC rebooted spine leading to intermittent connectivity issues.
PR Number Synopsis Category: idp flow creation, deletion,notification, session mgr intfce
1614013 High RE CPU usage occurs when routing-instance is configured under security idp security-package hierarchy level
Product-Group=junos
On all SRX Series devices, when routing-instance is configured under security idp security-package hierarchy level, several unexpected situations might occur, such as High Routing Engine (RE) CPU usage caused by the idpd process, the idpd process crash, IDP security-package update failure.
PR Number Synopsis Category: Internet Group Management Protocol
1607493 Multicast traffic might be duplicated on subscriber interface on MX platforms
Product-Group=junos
On MX platforms with distributed IGMP enabled, if a non-bbe junos interface joins the same multicast group as the subscriber interface followed by GRES/NSR switchover, then multicast traffic might be duplicated on subscriber interface.
PR Number Synopsis Category: Juniper Device Manager User Interface includes cli, mgmt
1559402 The subscriber management infrastructure daemon (smid) process might be stuck at 100%
Product-Group=junos
After performing GRES (Graceful Routing Engine Switchover) switchover several times, the smid process might be stuck at 100% on QFX/MX platforms.
PR Number Synopsis Category: Adresses NAT/NATLIB issues found in JSF
1542797 High Control-Plane CPU may be seen for uspinf process on SRX5K routing engine
Product-Group=junos
When running NAT pool related command at high rate, multiple instances of uspinfo process may cause high CPU on control plane
PR Number Synopsis Category: IPSEC/IKE VPN
1596103 The kmd process might crash when VPN peer initiates using source-port other than 500
Product-Group=junos
On SRX Series devices, when site-to-site IPsec VPN is configured with traffic-selectors, if the VPN peer initiates an IKE negotiation using source-port other than 500, and at the same time, the IPsec IKE rekey (For the same VPN tunnel as the previous VPN peer initiates) occurs on the SRX device, the kmd process might crash.
1605634 Traffic might be dropped in a corner case of IPsec VPN scenario on SRX5000 platforms with SPC3 installed
Product-Group=junos
On SRX5000 platforms with SPC3 installed and IP security (IPsec) Virtual Private Network (VPN) tunnels configured, if the gcm cipher (e.g. aes-128-gcm and aes-256-gcm) is used as the encryption algorithm, when the Internet Key Exchange Daemon (iked) process restore (e.g. caused by redundancy group 0 failover) happens, the iked process might get a wrong key being restored into the memory. After that, once there is Packet Forwarding Engine (PFE) reset/restart before the IKE Security Association (SA) rekey, traffic drop might happen due to this issue.
PR Number Synopsis Category: Layer2 forwarding on EX/NTF/PTX/QFX
1596483 Mcscnoopd might crash during deleting/adding layer-2 forwarding configuration after performing ISSU
Product-Group=junos
In layer-2 forwarding configuration with ISSU scenario, Gencfg provides a generic way for applications to store interface state information (blobs) which needs to be sent to PFE/PIC/REs/daemons. In some rare cases, after performing ISSU, the Gencfg key (handed/generated by the kernel, a kind of layer-2 token) info might be inconsistent between the l2ald and master/backup kernel due to the state sync issue, then the Gencfg might send the blobs with this wrong key to the kernel during adding/deleting the layer-2 forwarding configuration. Then the kernel might return the wrong messages (e.g. next-hop lookup) to mcsnoopd, this will cause mcsnoopd to crash, the services/functions based on multicast will be impacted.
1612738 l2ald core during routing-instance configuration change.
Product-Group=junos
when routing instance configured as ETREE LEAF, configuration change in such routing instance may cause existing dynamic mesh group readded to kernel. this cause l2ald core. but this core doesn't affect service and l2ald will return to correct state after core.
PR Number Synopsis Category: FreeBSD Kernel Infrastructure
1602005 Upgrade might fail when upgrading from legacy release
Product-Group=junos
On all platforms (For SRX, only SRX5k with RE-1800x4) while directly upgrading from Junos with FreeBSD 6 (e.g. 15.1X49 or before) to the affected releases, the system will check the USB connection. The upgrading will fail if there is no USB device detected during the upgrading process.
PR Number Synopsis Category: PTP related issues.
1618929 Clocking Solution: clksyncd crashes with 1pps output and PTP/Hybrid configured by default post upgrade to affected release.
Product-Group=junos
With 1pps measurement port output and PTP/Hybrid mode configured by default during bootup, clksyncd may crash and dump a core.
PR Number Synopsis Category: Chassis mgmt for all QFX systems - chassis MIB, alarms, CLI
1520144 SNMP trap of power failure might not be sent out.
Product-Group=junosvae
On QFX5K platforms, the SNMP trap of power failure might not be sent out when power cable is removed from PSU, and the output of CLI command 'show chassis environment' would not display the information of the power failure.
PR Number Synopsis Category: QFX5K hostpath
1610295 MAC move or MAC flap may be triggered in the QFX5k VC environment
Product-Group=junos
On all QFX5k platforms with VC (Virtual-Chassis) setup, IGMP (Internet Group Management Protocol) control packet received on a port in the backup (backup-RE) unit is forwarded back to the same port whereas split horizon is not working. Due to this, we might observe MAC (Media Access Control) move or flap. The workaround is to change the mastership between FPCs.
PR Number Synopsis Category: QFX L2 PFE
1563171 On the QFX5110-32Q switches, LACP does not come up in the non-oversubscribed mode for a set of ports.
Product-Group=junos
On QFX5110-32Q switches in non-oversubscribed mode, LACP might not come up when ports 20 to 23 are used. This might cause traffic drop on lanes 1, 2, and 3 of ports 20, 21, 22, and 23.
PR Number Synopsis Category: QFX EVPN / VxLAN
1561588 Dcpfe process might crash on after committing EVPN-VXLAN profile configuration and ARP resolution may fail causing traffic issues.
Product-Group=junos
Dcpfe process might crash on after committing EVPN-VXLAN profile configuration and ARP resolution may fail causing traffic issues.
PR Number Synopsis Category: QFX5100 Interface related issues
1555741 The Virtual Chassis Port (VCP) might not come up after upgrading to 18.4R2-S4 or later releases on EX4600 or QFX5100 platform
Product-Group=junos
In EX4600 or QFX5100 with the Virtual Chassis (VC) scenario, if the QSFP+-40G-LR4/LX4/BXSR is used as the Virtual Chassis Port (VCP), it might come up against the optical signal strength issue accidentally after upgrading to 18.4R2-S4 or later releases. Then the VCP might be brought down by the physical port driver randomly and not come up again. The functionality of VC or the Virtual Chassis Fabric (VCF) might be impacted.
PR Number Synopsis Category: RPD route tables, resolver, routing instances, static routes
1599084 IPv4 static route might still forward traffic unexpectedly even when the static route configuration has already been deleted
Product-Group=junos
On all Junos and EVO platforms with "static defaults" configured under "routing-options" hierarchy, if IPv4 static route configuration is added, and then deleted, the IPv4 static route will not be removed from routing table and still forward traffic unexpectedly due to this issue.
PR Number Synopsis Category: RPD API infrastructure
1607185 TCP traffic might be dropped on source port range 512 to 767 when the FlowSpec IPv6 filter is configured
Product-Group=junos
In the BGP FlowSpec scenario, the IPv6 filter matching icmp-type 2 only drops TCP traffic on source port range 512 to 767.
PR Number Synopsis Category: SNMP Infrastructure (snmpd, mib2d)
1606600 SNMP reflects outdated ARP entries
Product-Group=junos
When the ARP entry gets removed in the ARP table, and if there is a presence of a static route referring to the removed NH IP, the refcount will not be 0. In that case, the kernel will not send a DELETE message to mib2d. As a result, SNMP still has the ARP entry even after it's expired in the ARP cache.
PR Number Synopsis Category: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1617830 ICMP Error messages not generated when SFW and IPSEC service-set are configured on single PIC.
Product-Group=junos
On MX services scenario, traceroute generates ICMP error message like destination host unreachable and time exceeded that helps in identifying the intermediate hops. When there are multiple IPSEC service-sets are configured with knob "enable-asymmetric-traffic-processing" along with other CGNAT or SFW service-set, ICMP Error messages not able to reach the actual source.
PR Number Synopsis Category: SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1581231 Memory leak might happen due to stale NAT64 entries
Product-Group=junos
Stale Network Address Translation (NAT) 64 entries could be created if bogus IPv6 addresses match NAT64 rules. Memory space might not be successfully released when this issue happens. This issue only takes effect on Junos platforms.
1602528 Jflow-syslog for CGNAT might use 0x0000 in IPV4 Identification field for all fragments
Product-Group=junos
On all MX platforms with MS-MPC using Jflow logging, Jflow-syslog for CGNAT might use 0x0000 in IPv4 identification fields for all fragments when the Jflow-syslog packets undergo fragmentation. This issue might impact the flow monitoring.
PR Number Synopsis Category: SRX-1RU platfom related protocol, QoS, filtering features et
1613475 Interface might not come up when 10G port is connected to 1G SFP
Product-Group=junos
On SRX4600, when you connect a 1G SFP (Small form-factor pluggables) to the 10G port the interface might not come up.
PR Number Synopsis Category: Trio pfe bridging, learning, stp, oam, irb software
1607311 Multicast traffic is dropped when forwarded over VPLS via IRB
Product-Group=junos
On MX platform working as PE in MVPN, when traffic is received (from core) on upstream multicast LSI interface and then forwarded over VPLS via IRB interface, the packets are forwarded without vlan-tags, which leads to traffic drop at the remote VPLS PE (due to missing vlan-tags).
 

20.1R3-S2 - List of Known issues

PR Number Synopsis Category: Firewall Filter
1471310 Firewall filter monitoring using SNMP might not provide accurate results
Product-Group=junos
On all Junos except MX platforms, the firewall filter monitoring using SNMP OID 1.3.6.1.4.1.2636.3.5.2.1.6 might not provide the entire output of configured filters, when configured filters are using actions or matches that are not supported by the compiled filters. Below is the list of actions and matches that are not supported by the compiled filters: actions: "then policy map", "clear-policy-map", "then encapsulate/decapsulate" matches: "payload-protocol", "gre-key", "flex-offset range/prefix", "policy-map"
PR Number Synopsis Category: JUNOS Dynamic Profile Configuration Infrastructure
1584457 After performing NSSU, "timeout waiting for response from fpc0 " error message is seen while checking version detail
Product-Group=junos
After NSSU or Image upgrade to 21.1R1, show version details fails with "timeout waiting for response from"
PR Number Synopsis Category: EVPN control plane issues
1600310 [evpn_vxlan] [evpn_instance] : mx960 ::JUNOS:JDI_FT_REGRESSION::VMX:Bridge mac-table learning entries are not as expected for EVPN-VXLAN-1 routing instance
Product-Group=junos
In a scenario with EVPN-VXLAN in the Datacenter and EVPN-MPLS is in the WAN and the stitching is done with an LT interface, then the bridge mac-table learning entries are not as expected for EVPN-VXLAN routing instance. This could occur after 'restart interface-control' is issued on gateways.
PR Number Synopsis Category: Flow Module
1572240 The srxpfe process might crash during route churn
Product-Group=junos
On the vSRX3.0 or SRX5K platforms, the flowd/srxpfe process might crash if massive configuration(route table delete) changes and pumping the traffic at the same time. Traffic loss might be seen during the flowd/srxpfe process crash and restart.
PR Number Synopsis Category: User Firewall related issues
1605933 Memory leak at the useridd process might be observed when Integrated User Firewall is configured
Product-Group=junos
On SRX-Series devices having Integrated User Firewall enabled with Active Directory as the authentication source, memory leak might be observed at the useridd process.
PR Number Synopsis Category: PFE infra to support jvision
1592704 gNMI resource path filter /interfaces/interface[name=IFD-NAME]/ is not respected if a router has MPC10/MPC11 (AFTD-TRIO) online: the data for all interfaces are streamed and not only for IFD-NAME
Product-Group=junos
gNMI resource path filter feature is not supported for AFT-based line cards. For MX series, only MPC10 and MPC11 are AFT based as of today. This implies that resource subscription for a path "/interfaces/interface/[name=INTERFACE_NAME]" could return the data not only for INTERFACE_NAME, but for all interfaces in the system. This is a product limitation and it is not fixed as of today. This limitation is applicable not only for the case when INTERFACE_NAME resides at an AFT-based MPC, but also for the case when: - INTERFACE_NAME resides at a non-AFT MPC or at RE; - There is at least one online AFT MPC in the system.
PR Number Synopsis Category: MX104 Software - Kernel
1607282 In subscriber management scenario, under a rare condition, the RE reboots and generates a vmcore
Product-Group=junos
In subscriber management scenario, under a rare condition, the kernel might crash at very rare condition due to a null pointer check when an entry lookup is performed.
PR Number Synopsis Category: Neo Interface
1541382 With hold time configuration, the ge Interfaces remain down on reboot.
Product-Group=junos
With hold time configuration, GE Interfaces from MPC cards which use MIC driver (such as MPC2E/3E NG, MPC Type 1, MPC Type 2) may go down.
PR Number Synopsis Category: FreeBSD Kernel Infrastructure
1579331 EX4400: Under some conditions, the FPGA reset reason may be incorrectly shown in console logs as 0.
Product-Group=junos
EX4400: Under some special conditions, such as boot from OAM volume following a graceful/warm reboot, the FPGA reset reason incorrectly shown in console logs as 0.
PR Number Synopsis Category: Express Chip L3 software
1590387 [isis] [ISIS] ptx5000 : :: PROTOCOLS:VPTX:ISIS adjacency is not coming up through CCC L2Circuit
Product-Group=junos
ISIS over l2circuit will not come up if the encapsulation is TCC.
PR Number Synopsis Category: KRT Queue issues within RPD
1582226 The process rpd may be stuck in 100% due to race condition
Product-Group=junos
There is a defect on the code for the processing of route entries between RE and FPC, it is due to incorrect operations of two internal threads in a race condition, resulting in a tight loop on code and high rpd CPU usage.
PR Number Synopsis Category: RPD policy options
1565629 The rpd might crash when the deletion of routing table occurs
Product-Group=junos
The rpd might crash when the deletion of routing table occurs.
PR Number Synopsis Category: All Asgard Platform Related Issues
1335526 The ppmd process might crash after an upgrade on SRX platforms
Product-Group=junos
On SRX platforms with Bidirectional Forwarding Detection (BFD) enabled for multiple protocols (such as OSPF, ISIS, BGP, PIM), the ppmd process might crash after an upgrade.
PR Number Synopsis Category: Trio pfe bridging, learning, stp, oam, irb software
1606731 The FPC might crash if 'flow-table-size' is configured on MX platforms
Product-Group=junos
On MX platforms, if knob 'set chassis fpc slot-number inline-services flow-table-size' is configured, the FPC might crash.
PR Number Synopsis Category: Junos Automation, Commit/Op/Event and SLAX
1604622 File download using "request system download" might fail
Product-Group=junos
On a EX4400 device, any files scheduled for download using the cli command "request system download" might fail due to error. The files can be downloaded using normal ftp/scp commands on the device.
PR Number Synopsis Category: PTX/QFX100002/8/16 platform software
1555386 The LCMD process might consume memory until all of the free memory available to VMHOST gets exhausted
Product-Group=junosvae
On PTX10K, MX10K, and QFX10K (exception: MX10003, PTX10001, PTX10002, QFX10002, any Junos-EVO system are NOT affected), when the Linux Chassis Manager (LCMD) polls PSMs (Power Supply Modules), the memory used for that polling does not get freed. The amount of memory not being freed depends on the number of sensors (FPCs and PICs) installed in the chassis. The LCMD process will continue to consume memory until all of the free memory available to VMHOST has been exhausted. At that point, the LCMD restarts causing the Routing Engine's mastership switchover. (Please also see https://kb.juniper.net/TSB18061 for more details.)
Modification History:
First publication 2021-09-30
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