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
An incorrect SSO server is used when multiple wildcard patterns are configured for user authentication with different SSO servers.
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.
At times, ZTP on NFX250 and SRX320 devices fails when you deploy a LAN segment with DHCP.
Resource utilization graph is not populated for an SRX cluster.
At times, correct firewall policies are not matched by the traffic due to incorrect order.
SD-WAN policy deployment fails if you use application names that do not contain the junos keyword.
An error message displays when you edit a site group (Resources > Site Group).
At times, the AutoNAT job fails when the IP address on a DHCP WAN interface is changed or assigned.
SD-WAN policy intent ordering is incorrect when you use applications and services in two different intents with two different traffic steering profiles.
Firewall deployment issues with CSO predefined services and service groups.
At times, retry of a failed AutoNAT job is not successful.
While creating a service, the Create Protocol page lists only some of the ALGs supported on the device.
At times, the traffic from a Regular-LAN on an enterprise hub is unable to reach the data center LAN deployed on another enterprise hub.
At times, signature installation fails even though licenses are installed on the device.
At times, the spoke might not be able to reach the Internet (DNS or NTP) when the primary WAN link fails.
At times, auto SD-WAN deployment jobs result in empty commits with no change on the devices.
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.
Manual resync configuration is not working for provider hub devices ( Resources > Devices > Device Details > Configuration > Running Configuration).
Alarms pertaining to provider hubs, which should be visible only to the global administrators, are visible to tenants.
Even after a site is deleted from its site group and the associated firewall policy is redeployed, the policy does not get deleted from the site.
When the primary and secondary enterprise hubs are down, the provider hub does not advertise the LAN segment route of the spoke with the correct local preference.