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 

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Juniper Networks Cloud CPE Solution Release 3.1R1.

  • Make sure JSM heat resource is available in Contrail/openstack on the Contrail Con. Execute cmd in contrail/openstack "Heat resource-type-list | grep JSM” if its missing , copy to find a location to post this file) to the heat plugin dir (location in /etc/heat/heat.conf) and restart heat-engine.

    For a centralized deployment, use the following command to check that the JSM Heat resource is available in Contrail OpenStack on the Contrail Controller..

    1. Log in to the Contrail Controller node as root.
    root@hostHeat resource-type-list | grep JSM

    If the file is missing,

    1. Copy the file from ????? to the directory /etc/heat/heat.conf on the Contrail Controller node.
    2. Restart the heat-engine.
  • When you use Customer Portal to activate a network service on a network link, you must configure the following settings for each VNF in the network service:
    • Hostname
    • NTP server
    • DNS name server
  • We recommend that you use the current version of the Google Chrome Web browser to access Contrail Service Orchestration GUIs.
  • When a tenant object is created through Administration Portal or the API, Contrail OpenStack adds a default security group for the new tenant. This default security group denies inbound traffic and you must manually update the security group in Contrail OpenStack to allow ingress traffic from different networks. Otherwise, the Junos Space Virtual Appliance might fail to discover a VNF or Contrail OpenStack might drop traffic.


  • Contrail Service Orchestration does not offer a single RPC to get the device identifier for a specific site. You can use multiple API calls or the license installation tool to obtain the device identifier for a specific site.


  • You can use Administration Portal to upload licenses to Contrail Service Orchestration; however, you cannot use Administration Portal to install licenses on physical or virtual devices that Contrail Service Orchestration manages. You must use the APIs or the license installation tool to install licenses on devices.


  • Contrail Service Orchestration uses RSA key based authentication when establishing an SSH connection to a managed CPE device. The authentication process requires that the device has a configured root password, and you can use Administration Portal to specify the root password in the device template.

    To specify a root password for the device:

    1. Log in to Administration Portal.
    2. Select Resources > Device Templates.
    3. Select the device template and click Edit.
    4. Specify the encrypted value for the root password in the ENC_ROOT_PASSWORD field.
    5. Click Save.


  • You can use the logs on an NFX250 device to review the status of the device’s activation through Administration Portal.


  • In Cloud CPE Solution Release 3.1R1, intrusion prevention system (IPS) is not supported. Therefore, in the IPS report, the attack name from the IPS signatures is displayed as UNKNOWN.
  • In Cloud CPE Solution Release 3.1R1, the virtual machine (VM) on which the virtual route reflector (VRR) is installed supports only one management interface.
  • In Cloud CPE Solution Release 3.1R1, high availability for ArangoDB is not supported. Therefore, ensure that the central infrastructure VM, where ArangoDB is running, is not brought down or does not fail. If the VM is down, bring it up immediately for CSO to be operational.
  • In Cloud CPE Solution Release 3.1R1, when you try to deploy a LAN segment on an SRX Series spoke device, the CSO GUI allows you to select more than one port for a LAN segment. However, for SRX Series devices, only one port for a LAN segment can be deployed; multiple ports in a LAN segment can be deployed only on NFX Series devices.
  • On the SRX Series device, the traffic for any of the following combinations does not flow because of an inability to identify the reverse route for traffic terminating through MPLS:
    • Site to site
    • Site to department or vice versa
    • Department to department

    To enable traffic, you must add a firewall rule permitting traffic from the corresponding department's zone (where the traffic was supposed to terminate) to the Trust zone on the destination site. However, we do not recommend doing this because the rule can conflict with existing firewall intents.

  • In Cloud CPE Solution Release 3.1R1, SSL proxy is not supported.
  • An SD-WAN policy deployment is successful even if there is no matching WAN link meeting the SLA. This is expected behavior and is done so that when a WAN link matching the SLA becomes available, traffic is routed through that link.
  • Tenant Administrator users cannot delete sites.
  • On a site with an NFX Series device, if you deploy a LAN segment without the VLAN ID specified, CSO uses an internal VLAN ID meant for internal operations and this VLAN ID is displayed in the UI. There is no impact on the functionality.
  • When you activate a CPE device with WAN interfaces configured for DHCP:
    • Ensure that all the WAN interfaces configured for DHCP have the IP address allocated from the DHCP server.
    • When multiple WAN links are configured for DHCP, in some cases, all DHCP servers will advertise a default route to the CPE device, which can lead to traffic being routed through an undesired WAN interface, which could then stop the GRE and IPsec tunnels from being operational.

      To avoid this scenario, configure a static route through each WAN interface to reach the tunnel endpoint through the desired WAN interface.

  • When you create LAN segments, the LAN segment table does not display the DHCP settings even though the changes are saved successfully.
  • When you trigger the ZTP workflow, we recommend that you use the activation code for the device and initiate the activation by using the Activate Device link in the CSO GUI.
  • In the SLA Performance page (Monitor > Applications > SLA Performance, the scatter plot displays the SLA name as UNKNOWN for the applications for which the SLA is not violated.

Modified: 2017-08-22