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 Issues

This section lists known issues for the Juniper Networks Cloud CPE Solution Release 3.0.

  • When you install the Contrail Service Orchestration software, you must deploy the microservices and infrastructure services separately and not simultaneously.

    [CD-925]

  • Administration Portal might take a short while to update data fields after you delete objects.

    [CXU-1806]

  • Some notifications about the success or failure of create and delete operations in Administration Portal are difficult to understand.

    Workaround: Monitor the create, update, or delete status of the object in the object table.

    [CXU-2364]

  • Connectivity between the regional microservices server and a CPE device might fail with a timeout error.

    Workaround: None

    [CXU-2995]

  • You cannot add a firewall rule for the UTM function in a network service that uses the vSRX VNF.

    [CXU-2846]

  • Deactivating an SRX Series Services Gateway acting as a CPE device might not remove all configuration settings from the device.

    Workaround: Manually delete the configuration settings from the SRX Series Services Gateway.

    [CXU-3754]

  • You cannot deploy two network services simultaneously on a CPE device.

    Workaround: Deploy only one network service on a CPE device.

    [CXU-3756]

  • The device profile srx-deployment-option-1 assigns OAM traffic to the fxp0 interface, which is not available on the SRX Series Services Gateway.

    Workaround: Edit the stage 1 configuration for the CPE device in Customer Portal to use an interface other than fxp0 for OAM traffic. [CXU-3779]

  • The traffic rate value does not change when you monitor a service on an SRX Series Services Gateway in Customer Portal.

    Workaround: None

    [CXU-3822]

  • The NFX250 device does not receive communications to block unicast reverse path forwarding (uRPF) because two interfaces on the NFX250 device communicate separately with one interface on the regional microservices server.

    Workaround: Disable the uRPF check in JDM on all interfaces for each NFX Series device.

    [CXU-3854]

  • You must use a different router for a PE in a distributed deployment and an SDN gateway in a centralized deployment. You cannot use the same router for both of these functions.

    Workaround: None

    [CXU-4173]

  • You must configure the VLAN settings for an NFX250 device before you configure the Silver Peak VX VNF in Customer Portal.

    [CXU-4402]

  • An end user cannot change the password for Customer Portal if the current password is not available.

    Workaround: Delete and re-create the customer with Administration Portal or the API.

    [CXU-4537]

  • You cannot edit the settings for a customer in Administration Portal.

    Workaround: Use Administration Portal to import a JSON file that contains the correct data for the customer. [CXU-4538]

  • You can only view one network service at a time on a CPE device in Customer Portal.

    [CXU-4551]

  • When you configure the MX Series router as an IPsec concentrator in a distributed deployment, you must specify the Internet Gateway of the IPsec concentrator in the default routing instance. Otherwise, the IPsec tunnel is not established.

    [CXU-4566]

  • You must specify a target URL if you select http-get for the probe type when you configure IP monitoring for a CPE device in Customer Portal, Network Service Designer, or the APIs. Otherwise, the configuration fails.

    [CXU-4571]

  • During activation, the NFX250 devicereboots 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.Workaround: Before you activate the NFX250 device, specify the HugePages count on the device and reboot it.

    [CXU-5601, PR1254219]

  • The configuration for a CPE device might not be removed when you deactivate the device in Administration Portal.

    Workaround: To deactivate the CPE device, first delete the configuration from the CPE device with Customer Portal, and then deactivate the device with Administration Portal. [CXU-6059]

  • You cannot edit or delete login credentials that you configure for a tenant when you create the tenant in Administration Portal.

    Workaround: Delete the tenant and re-create it. [CXU-6217]

  • You cannot edit the Deployment Type (vCPE-Only or uCPE-Only) in a request that you create with Network Service Designer.

    Workaround: Create a new request. [CXU-6474]

  • Remote activation of an NFX250 device might fail because a VNF can not be activated.

    Workaround: Use Administration portal to delete the device and then re-configure its activation data. [CXU-6576, PR1260255]

  • After you have assigned a device template to a CPE device in Administration Portal, you might not be able to change the device template.

    Workaround: Use Administration Portal to delete the on-premise site for the CPE device and then re-create the site. [CXU-6648]

  • Using Heat v2 API on Contrail 3.0.2, we support only 120 Contrail Service Orchestration instances for a centralized deployment. Use of more Contrail Service Orchestration instances for a centralized deployment results in high latency and timeout issues due to Contrail bug https://bugs.launchpad.net/juniperopenstack/+bug/1676983.

    Workaround: Use fewer than 120 Contrail Service Orchestration instances for a centralized deployment with Heat v2 API or use Heat v1 APi for larger numbers of Contrail Service Orchestration instances.

    [CXU-6697]

  • After you complete an operation in Customer Portal, the GUI might not update to show the latest status.

    Workaround: Refresh the Web page in Customer Portal.

    [CXU-6701]

  • When you activate a CPE device in Customer Portal, there is no indicator for the status of the activation.

    Workaround: None

    [CXU-6705]

Modified: 2017-04-27