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 known issues in Juniper Networks CSO Release 5.0.0.

SD-WAN

  • When you add or remove any intent on the SD-WAN Policy page, a +0 is added after every element even though you selected only one element.

    Workaround: This does not have any functional impact. The +0s disappear when you refresh the page.

    CXU-32068

Site and Tenant Workflow

  • Adding sites using a site template that is a cloned template which was edited to remove the LAN segment part of the template fails.

    Workaround: Instead of cloning a site template and editing out the LAN segment part, create a new site template that does not have the LAN segment configuration.

    Bug Tracking Number: CXU-35374

  • On the Device Activation page, the status is incorrectly shown as activating even though the bootstrap job has failed.

    Workaround: Check the device activation status on the Monitor > Jobs page.

    Bug Tracking Number: CXU-34907

  • ZTP for a next-generation firewall device fails at the install default trusted-ca stage.

    Workaround: Reboot the SRX device (next-generation firewall device) and retry the ZTP job. To retry the ZTP job, go to the Job Management page and select the failed ZTP job and click Retry.

    Bug Tracking Number: CXU-34472

  • During ZTP, boot strap job times out if the device takes a long time to connect to CSO.

    Workaround: Delete and re-add the site and then, retry ZTP.

    Bug Tracking Number: CXU-34298

  • Status of an SRX device that is activated in CSO does not change to Connected.

    Workaround: Reboot the device.

    Bug Tracking Number: CXU-32815

General

  • Though you can delete an SRX cluster device from the Sites page of the CSO portal, the device fails to zeroize.

    Workaround: There is no known workaround.

    Bug Tracking Number: CXU-35481

  • Monitoring page for EX Series switches might not be displaying the latest data as the page does not auto-refresh.

    Workaround: Manually refresh the page to view the latest data.

    Bug Tracking Number: CXU-35362

  • In next-generation firewall sites with LAN, the recall of EX2300 and EX3400 devices with the zeroize option does not work. This issue occurs because EX2300 and EX3400 do not support zeroize.

    Workaround: Manually clean up the EX2300 and EX3400 devices.

    Bug Tracking Number: CXU-35208

  • ZTP of SRX devices fails because the default CA certificate is not installed on the device.

    Workaround: Install the certificates on the device by using the CLI, reboot the device, and then, retry ZTP.

    Bug Tracking Number: CXU-34578

  • At times, recall with recovery configuration fails to revert EX2300 and EX3400 devices to the recovery configuration because some devices do not have the /var/db/scripts/events directory.

    Workaround: Keep a copy of the recovery configuration and use the load override recovery filename command to revert the required configuration on EX2300 or EX3400.

    Bug Tracking Number: CXU-34430

  • The job log for an EX device reboot does not show details of the reboot job.

    Workaround: View the progress of the reboot job from the Monitor > Jobs page.

    Bug Tracking Number: CXU-35366

  • Last login details of users are not available in the Administration > Users page.

    Workaround: Use the Login and Context option in the Administration > Audit Logs page to view details of user logins.

    Bug Tracking Number: CXU-35317

  • If you create an audit log purge with a recurring schedule and select the Run Now option, the recurrence fails to get scheduled.

    Workaround: When you schedule an audit log purge with a recurring schedule, use the Schedule at a later time option instead of the Run Now option.