Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Resolved Issues


The following issues are resolved in Juniper Networks CSO Release 3.3.1.

  • When both the OAM and data interfaces are untagged, ZTP fails when you use an NFX Series device as a CPE device.

    Bug Tracking Number: CXU-15084

  • The tenant creation job might fail if connectivity from CSO to the VRR is lost during job execution.

    Bug Tracking Number: CXU-16884

  • The customization of AUX, LAN, and OAM subnets in device profiles (templates) is not supported. Therefore, do not modify the device profiles to change the existing subnets for AUX, LAN, and OAM. Use the default subnets provided in the device profiles.

    Bug Tracking Number: CXU-16888.

  • In the centralized deployment, after you import a POP, the CPU, memory, and storage allocation are displayed as zero.

    Bug Tracking Number: CXU-19105

  • For AppQoE-based tenants, the Application SLA Performance page does not display the application-specific round-trip time (RTT), jitter, and throughput parameters against the SLA profiles. instead, these parameters are displayed against the SLA profile named Default.

    Bug Tracking Number: CXU-20162.

  • In some cases, on the Monitor Overview page (Monitoring > Overview) for a site, the ZTP status is displayed incorrectly when you hover over the site.

    Bug Tracking Number: CXU-20226.

  • If you create firewall policy with more than 10 firewall policy intents and deploy the firewall policy on a tenant with 45 or more sites, the policy deployment fails.

    Bug Tracking Number: CXU-20292

  • If you create a NAT pool, specify the value of the Translation field as Port/Range, configure the port as a range, and enter an incorrect starting port number, then you cannot enter the ending port number, and the NAT pool is created with a single port value instead of a range.

    Bug Tracking Number: CXU-20366.

  • For hybrid WAN tenants, during site creation, all the VIMs in the system are displayed even though a specific VIM is already assigned during the tenant creation.

    Bug Tracking Number: CXU-20371.

  • In a full mesh topology, the GRE IPsec down alarms are not created for some overlays during link failure.

    Bug Tracking Number: CXU-20403.

  • If you specify an MPLS link without local breakout capability as the backup link, then Internet breakout traffic is dropped because the overlay link to hub will not be used for Internet traffic if local breakout is enabled for the site.

    Bug Tracking Number: CXU-20447.

  • The Grant RMA operation fails for a multihomed hub device.

    Bug Tracking Number: CXU-20457.

  • When you use DHCP for the activation of a dual CPE device, ZTP might fail because the device takes longer than expected to connect to the Device Connectivity Service (DCS).

    Workaround: Retry the failed ZTP job.

    Bug Tracking Number: CXU-20467.

  • When the LTE modem is disconnected or disabled in the NFX250 CPE device, an alarm is triggered. However, the underlay link status on the Sites page might not display the alarm.

    Bug Tracking Number: CXU-20492.

  • In the Configure Site workflow for a full mesh topology with multitenancy enabled, the option to connect the CPEs only to the hub is not supported; that is, if you specify false for the used_for_meshing parameter, this option is ignored.

    Bug Tracking Number: CXU-20495.

  • If you define an SLA profile for a static SD-WAN policy but do not remove the default values for the SLA parameters and deploy the policy, the policy is deployed as a dynamic SD-WAN policy.

    Bug Tracking Number: CXU-20499.

  • In a department, if there are two LAN segments with DHCP enabled, only one DHCP server setting is deployed on the device.

    Bug Tracking Number: CXU-20519.

  • If you modify the path preference of an existing SLA profile that has already been deployed and redeploy the SD-WAN policy, the path of the SLA profile is not updated on the CPE device.

    Bug Tracking Number: CXU-20540.

  • You cannot manage an MX Series cloud hub by using an Internet link. Use MPLS as the OAM link to manage the MX Series cloud hub.

    Bug Tracking Number: CXU-20544.

  • For a vSRX CPE device, the automatic deployment of a license fails with an error message indicating that no license is found even though the license exists on the vSRX instance.

    Bug Tracking Number: CXU-20558.

  • When you configure a high delay and loss on the OAM link, the link switch might be delayed or might not occur.

    Bug Tracking Number: CXU-20562.

  • For a tenant with bandwidth-optimized SD-WAN mode, the SLA performance for the site is always displayed as 0/100.

    Bug Tracking Number: CXU-20563.

  • In a dual CPE spoke device, noncacheable applications do not work when the initial path is on CPE0 and the APBR path selected is on CPE1.

    Bug Tracking Number: PR1340331

  • If the length of the tenant name exceeds 16 characters, the activation of the SRX Series hub device fails.

    Bug Tracking Number: PR1344369.