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 Cloud CPE Solution Release 3.0.

  • When you deploy a microservice directly on a server, you might not be able to ping infrastructure service IP addresses from inside Kubernetes pods.

    Workaround: Execute the following commands to resolve the issue:

    1. Clear the post-routing rules in iptables:
      root@host:~/# for i in $( iptables -t nat --line-numbers -L | grep ^[0-9] | awk '{ print $1 }' | tac ); do iptables -t nat -D POSTROUTING $i; done
    2. Restart the flanneld service.
      root@host:~/# service flanneld restart


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


  • 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.


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


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

    Workaround: None


  • 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.


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

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


  • 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]

  • Logs for CPE devices in Customer Portal do not specify whether or not the deployment of a VNF is successful.

    Workaround: None


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

    Workaround: None


  • If you create multiple rules for APBR and then delete them, Customer Portal still displays the first rule that you configured.

    Workaround: Click OK to close the page, then reopen it. The first rule that you created is no longer visible.


  • You can only create a single on-premise site for a tenant in Administration Portal if the WAN-0 and WAN-1 ports on the CPE device are ge-0/0/0 and ge-0/0/1 for an SRX Series Services Gateway or vSRX implementation, or ge-0/0/10 and ge-0/0/11 for an NFX250 device.

    Workaround: Use the Import Tenant option or the API to edit the configuration for the correct interfaces and to create the sites.


  • 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.


  • 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


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


  • 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.


  • 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.


  • 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.


  • 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.


  • The AMS microservice may not start when you install Contrail Service Orchestration.

    Workaround: After you install Contrail Services Orchestration, use the following procedure to check the status of the microservices and to restart AMS if necessary:

    1. Login as root into the VM or server that hosts the central microservices.
    2. Run the following command.
      root@host:~/# kubectl get pods | grep -v Running

      if the result is an empty display, as shown below, the microservices are running and you do not need to restart the AMS microservice.

      root@host:~/# kubectl get pods | grep -v Running
      NAME                                      READY        STATUS                     RESTARTS   AGE

      If the display contains an item with the status CrashLoopBackOff or Terminating, AMS is not running.

      root@host:~/# kubectl get pods
       NAME                                      READY     STATUS                     RESTARTS   AGE
       csp.ams-3909406435-4yb0l                  1/1       CrashLoopBackOff            0          8m
       csp.nso-core-3445362165-s55x8             0/1       Running                     0          8m

      The first item in the display shows the microservice and the second item shows its pod.

    3. Delete and restart the pod.
      root@host:~/# kubectl delete pods -l microservice=csp.nso-core
    4. Wait a couple of minutes, then check the status of the microservice and its pod.
      root@host:~/#kubectl get pods
      NAME                                      READY        STATUS                     RESTARTS   AGE
       csp.ams-4890899323-3dfd02                   1/1        Running                     0          1m
       csp.nso-core-09009278633-fr234f             0/1        Running                     0          1m
    5. Repeat Steps 1 through 4 for the regional microservices.


  • The configuration for a CPE device may 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 deactivate—delete the object for—an NFX device that uses the device template NFX_deployment_option_4 through Administration Portal or the API.

    Workaround: Use the API with the forced recall option to delete the CPE object. [CXU-6130]

  • 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 recreate 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 NFX device may fail because a VNF can not be activated.

    Workaround: Delete the tenant and recreate it. [CXU-6576]

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

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

  • Using Heat V2 API on Contrail 3.0.2, we support only120 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

    Workaround: Use fewer than 120 Contrail Service Orchestration instances for a centralized deployment.


  • 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.


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

    Workaround: None


  • You cannot activate an SRX Services Gateway through the device’s interface.

    Workaround: Activate the device through Customer Portal or your custom interface.

    PR1268200 ]

Modified: 2017-04-26