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 6.0.0:

  • Fortinet and Ubuntu service chaining instance fails on NFX250.

    Bug Tracking Number: CXU-52817

  • The Initiate RMA option is disabled if the bootstrapping of the device fails and if the device status is Bootstrap_Failed.

    Bug Tracking Number: CXU-52896

  • When you upgrade an image from 15.1X49-D173.1 to 19.3r2.s3.3 Release, it was observed that the upgrade of Gateway Router (GWR) without staging takes about 1 hour and 30 minutes, which is very high when compared to the manual upgrade.

    Bug Tracking Number: CXU-48845

  • After you reboot the server, the docker process in the CAN node stops working.

    Bug Tracking Number: CXU-48126

  • After you reboot the server, all MS nodes change to Pending state and return to 1/1 Running state when the node is ready. However, the secmgt-sm and monitoring pods are seen in 0/1 Running state occasionally.

    Bug Tracking Number: CXU-48125

  • After you reboot the server, the docker process is not started automatically and is in Loaded state instead of Running state. Hence, if you run the kubectl get nodes command, those nodes are in NOT READY state.

    Bug Tracking Number: CXU-48027

  • After you reboot the server, Rocks engine database corruption occurs.

    Bug Tracking Number: CXU-47812

  • After you reboot the server, a few of pods in kube-system such as etcd and kube-api are seen in CrashLoopBackOff state.

    Bug Tracking Number: CXU-46754

  • On a chassis cluster, when you reboot one of the servers, workflows such as configure site or delete site fails with an error: “vhost '/' is down or inaccessible”.

    Bug Tracking Number: CXU-46490

  • During a server reboot, the calico pod might remain in 0/1 Init:0/3 or CrashLoopBackOff state if the IP_AUTODETECTION_METHOD environment variable is not configured.

    Bug Tracking Number: CXU-44871

  • Active-Active mode is not supported with cloud breakout for GRE tunnels.

    Bug Tracking Number: CXU-43757

  • When you install the license on the backup node of an SRX dual CPE cluster, the installation fails.

    Bug Tracking Number: CXU-43085

  • On CSO Release 5.1.1 on-premise chassis cluster, the CSO installation fails due to CAN installation failure.

    Bug Tracking Number: CXU-42965

  • On NFX250 devices, Fortinet service chaining instantiation fails.

    Bug Tracking Number: CXU-42188

  • EX4600 and EX4650 switches running Junos OS Release 18.4R2 do not support ZTP,

    Bug Tracking Number: CXU-41608

  • When you add a second switch under the Site, the Site state changes from PROVISIONED to CONFIGURED.

    Bug Tracking Number: CXU-40647

  • Zero touch provisioning of an EX Series switch fails if you add an EX Series switch behind an enterprise hub.

    Bug Tracking Number: CXU-38994

  • For an EX Series switch, if you enable or disable a port from the UI, the port status is reflected in Port Chassis View and Port Grid only after an approximate time of 5 minutes.

    Bug Tracking Number: CXU-37846

  • For a site-to-site tunnel, if the WAN link on one site is marked as active and the WAN link for the other site is marked as backup, then the tunnel is not considered as a backup tunnel for the site with the WAN link marked as active.

    Bug Tracking Number: CXU-51919

  • While creating an IPsec tunnel between an Internet link that is behind NAT in a spoke to an MPLS link in an ENT hub, wrong NAT interface is configured on the IPsec tunnel. Therefore, the tunnel fails to be created.

    Bug Tracking Number: CXU-46185

  • After you upgrade from CSO Release 4.1.1 to CSO Release 5.1.2, the Firewall Policy and SDWAN policy pages show incorrect count for undeployed intents.

    Bug Tracking Number: CXU-45171

  • Installation of licenses on SRX1500 and SRX4200 dual CPE clusters by using CSO is failing.

    Bug Tracking Number: CXU-40522