Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Resolved Issues

The following issues are resolved in Juniper Networks Cloud CPE Solution Release 3.1.2.

  • You cannot edit the settings for a customer in Administration Portal. [CXU-4538]
  • You can view only one network service at a time on a CPE device in Customer Portal. [CXU-4551]
  • During activation, the NFX250 device reboots and requests that you enter the activation code twice, because there is no default value for the HugesPages count in the Linux Kernel on the device. [CXU-5601, PR1254219]
  • After you install CSO, the username and password that CSO uses to access Contrail Analytics might not match the corresponding username and password in Contrail Analytics. [CXU-5873]
  • The configuration for a CPE device might not be removed when you deactivate the device in Administration Portal. [CXU-6059]
  • You cannot edit the deployment type (vCPE-Only or uCPE-Only) in a request that you create with Network Service Designer. [CXU-6474]
  • Traffic not classified by SD-WAN policies follows the default routing behavior. [CXU-10716]
  • In some cases, an operation might fail, with the Authentication required error message, because of an expired token. [CXU-10809]
  • In some cases, when multiple system log messages (syslogs) or queries are being processed, the Contrail Analytics Node (CAN) crashes (Docker restarts). [CXU-10838]
  • When a session is transferring more than 2 GB of data, the unit of throughput is incorrectly reported as terabits per second (Tbps) in the CSO GUI. [CXU-11556]
  • When you remove a cloud hub from a tenant, the corresponding router is removed from the All Tenants scope. [CXU-11796]
  • If the central infrastructure node that created the SAML 2.0 session goes down and you log out of the CSO GUI, the SAML 2.0 session logout fails. [CXU-11867]
  • When the deployment of a LAN segment on a device fails, the device status is changed from PROVISIONED to PROVISION_FAILED. However, when you redeploy the LAN segment and the deployment is successful, the device status is not changed to PROVISIONED. Therefore, when you attempt to deploy an SD-WAN or a firewall policy on the device, the deployment fails with the error message [get_policy_info_list: method execution failed]Site/ Device information not found. [CXU-11874]
  • In some cases, traffic fails to flow over an overlay tunnel. [CXU-11921]
  • When you log in to CSO as a Tenant Administrator user, the Configure Site workflow is not available. [CXU-11922]
  • ZTP activation of an SRX Series device by using the phone home client (PHC) fails. [CXU-11926]
  • You see an import error message when you use the license tool, because the tssmclient package is missing from the license tool files. [CXU-12054]
  • When you deploy a firewall policy, the deployment fails with the message Fail to invoke mapper to create snapshot with reason null. [CXU-12151]
  • When you onboard an NFX series device by using the default configuration, in some cases there is a connectivity issue between Juniper Device Manager (JDM) and Junos Control Plane (JCP). [CXU-12396]
  • By default, CSO uses Heat V2 APIs to bring up network services on Contrail. However, because a bug in CSO, the policy configured does not exchange routes and therefore traffic does not flow through the service chain. [CXU-12863]
  • If you modify the default configuration of an SRX340 device to get the IP address by using DHCP, the device activation fails. [CXU-13446]
  • During the failover of a link between an NFX Series spoke device and a vSRX hub device, the BGP session goes down even though the virtual route reflector (VRR) is reachable. [CXU-13517]
  • If you configure DHCP on an NFX Series or an SRX Series spoke device, in some cases, the spoke might fail to establish a connection to CSO and might fail to send syslog messages to the CAN. [CXU-13567]
  • In some cases, one or more security management microservices take more than 20 minutes to come up and are stuck in the same state. [CXU-13726]
  • Reports are not generated in HA deployment scenarios. [CXU-14039]
  • If you try to activate an SRX300 CPE device by using the redirect server, the phone home activation process does not start. [CXU-14162]
  • The reverse path taken by traffic on the hub is different from the forward path. [CXU-14330]
  • The Contrail Collector service (Contrail Analytics Release 4.0.2) crashes several times intermittently. However, the service recovers after some time. [CXU-15802]
  • BGP routes are withdrawn 10–15 minutes after a BGP session goes down, even though the hold-timer value is set to 65,535. When BGP routes are withdrawn, traffic flow is impacted. [PR 1312702]
  • Sometimes the IBGP session with the VRR is broken temporarily and comes back up automatically. During that period there might be issues related to link switch. [PR 1312863]

Modified: 2017-12-15