The following issues are resolved in Juniper Networks CSO Release 4.0.0.
After an SD-WAN CPE device is activated by using ZTP, you must install APBR licenses and application signatures before deploying SD-WAN policies through the Administration Portal GUI.
Bug Tracking Number: CXU-14799.
Hybrid-WAN and SD-WAN deployments using the same MX as a hub is not supported.
Bug Tracking Number: CXU-16547.
When you are creating an SLA Profile and want to specify the advanced configuration, then you must specify maximum upstream rate, maximum upstream burst size, maximum downstream rate and maximum downstream burst size.
Bug Tracking Number: CXU-17735.
For an AWS spoke, during the activation process, the device status on the Activate Device page is displayed as Detected even though the device is down.
Bug Tracking Number: CXU-19779.
On the Monitor > Overview page, if you select a cloud hub site and access the WAN tab, an error message is displayed.
Bug Tracking Number: CXU-20353.
In the bandwidth-optimized SD-WAN mode, when the same SLA is used in the SD-WAN policy for different departments and an SLA violation occurs, two link switch events that appear identical, because the department name is missing from the event details, are displayed.
Bug Tracking Number: CXU-20529.
On the SD-WAN Policy page, if you click the up or down arrow to reorder a policy intent, then the policy intent moves to the top of the list instead of moving one intent above or below respectively. In addition, when you click Deploy, the changes are not deployed to the device.
Bug Tracking Number: CXU-20861.
If you restart a central microservices VM or the csp.secmgt-sm Kubernetes pod on a central microservices VM when the deployment of a firewall policy or NAT policy is in progress, the deployment job fails.
In addition, after the restart is completed, if you modify the firewall or NAT policy, the changes fail to deploy.
Bug Tracking Number: CXU-21106.
In a tenant with real-time-optimized SD-WAN, the duration of the link switch violation (on the WAN tab of the Site-Name page) might be displayed incorrectly.
Bug Tracking Number: CXU-21590.
The connection of the Celery worker to RabbitMQ might be lost in some cases, such as the shutdown of the infrastructure VM, pool network, or high load on the infrastructure VMs. After the broken connection is detected, Celery is restarted. However, if an exception takes place during the restart, then the Celery worker loses the connection to RabbitMQ.
Bug Tracking Number: CXU-21823.
In a full mesh topology, if a site uses the same underlay to connect to a site and a hub, the link score of the overlay between the site and the hub is displayed as poor instead of N/A (not applicable).
Bug Tracking Number: CXU-21824.
A user with the Tenant Administrator role cannot install application signatures on the devices belonging to a tenant.
Bug Tracking Number: CXU-22064.
If you try to delete the SLA profile associated with the SD-WAN policy immediately after deleting the SD-WAN policy, then an error message might be displayed and the SLA profile is not deleted.
Bug Tracking Number: CXU-22168.
The rollback operation on a CSO setup configured on an ESXi server fails.
Bug Tracking Number: CXU-22288.
The upgrade of Network Service Controller fails.
Bug Tracking Number: CXU-22345.