The following issues are resolved in Juniper Networks CSO Release 5.1.2:
RFC-1918 subnets cannot be used in LAN subnets and LAN segments.
Bug Tracking Number: CXU-44158
After upgrading from CSO Release 4.1.1 to CSO Release 5.1.1, you must modify the IP address of the virtual route reflector (VRR) configuration.
To modify the IP address of the VRR, connect to VRR-1 VM and change the public IP address of VRR-1 to 192.168.10.29/32. Similarly, connect to VRR-2 VM and change the IP address of VRR-1 to 192.168.10.30/32.
Bug Tracking Number: CXU-43157
While upgrading from CSO Release 4.1.1 to CSO Release 5.1.1, to avoid issues because of user or group permissions, you must run the following commands on all the infrastructure nodes to back up Elasticsearch data:
service elasticsearch stop usermod -u 2001 elasticsearch groupmod -g 2001 elasticsearch chown -R elasticsearch:elasticsearch /var/log/elasticsearch chown -R elasticsearch:elasticsearch /usr/share/elasticsearch/ chown -R elasticsearch:elasticsearch /var/lib/elasticsearch chown -R elasticsearch:elasticsearch /mnt/data/elasticsearch chown -R elasticsearch:elasticsearch /home/elasticsearch chown -R root:elasticsearch /etc/elasticsearch service elasticsearch restart
Bug Tracking Number: CXU-43277
After you upgrade to CSO Release 5.1.1, you must change the etcd values of the hostname and IP address of the south-bound load balancer (SBLB) host to the match the values in CSO Release 4.1.1 to maintain the same connections between the nodes as in CSO Release 4.1.1.
To update the etcd values, execute the following commands in the startup server:
Bug Tracking Number: CXU-43570
When you back up an SD-WAN report generated in CSO Release 4.1.1 and restore it in CSO Release 5.1.1, an error appears when you try to download the report, and the report is not downloaded.
Bug Tracking Number: CXU-42395
Provisioning an SRX Series device as next-generation firewall by using CSO is failing.
Bug Tracking Number: CXU-43362
In an high availability installation of CSO, when a server is restarted, the node on which RabbitMQ is running does not join the cluster.
Bug Tracking Number: CXU-43726
If you have installed CSO Release 5.1 on a single node and if there is a power failure, the UI is not accessible even if the power resumes.
Bug Tracking Number: CXU-41460