Resolved Issues in CSO Release 6.1.0 Patch Fixes
Table 3 lists the resolved issues in CSO Release 6.1.0 patches:
Table 3: Resolved Issues in CSO Release 6.1.0 Patches
Self originated routes are relearnt from the overlay network.
CSO does not consider the services when ordering the firewall policies.
The Security Events page does not display updated information.
LAN deployment fails for the et-1/0/0 interface on SRX4600.
The edit operation fails when you change the static IP for a WAN link on an enterprise hub.
An error message displays when you access the SD-WAN Breakout Profiles and SLA Based Steering Profiles pages.
The Site Pairs field in the Add SD-WAN Site Performance Definition window does not display all the sites.
After upgrading an enterprise hub, local preference is not handled in a tenant with network segmentation disabled, resulting in a traffic blackhole.
An error message displays when you retry a failed bootstrap job on an SRX dual CPE.
When you access the Create LAG Interface page from the Devices>Configuration page, the CPE Port(s) field displays the CONTROL and FAB ports.
If you sort the Jobs List by Status in the Monitor> Jobs>All page, an error message displays.
The SD-WAN tenant performance report does not display the updates for packet loss, jitter, and latency.
The note text in the Upload CSV File window lists the maximum number of records as 200 instead of 1024.
Local Breakout (LBO) is enabled on all sites.
ZTP activation fails on a vSRX spoke.
The Configuration > SD-WAN > SD-WAN Policy page does not display the add, edit, and delete options.
LAN segment deployment on enterprise hubs fails with the error message AWS-OADH01: config-deploy FAILED - config COMMIT ERROR.
Branch site upgrade from CSO Release 5.3 to 6.0.0 fails.
The Application SLA Performance page displays an error message if you try to view the information in GRID VIEW.
The JSON file generated for a site, which has the LAN Routes to Overlay option disabled on the LAN segment, contains incorrect information.
The order of the outbound zones list is changed, resulting in an empty commit on the device.