Known Issues

This section lists known issues for the Cloud CPE Centralized Deployment Model Release 1.5.

• Service and Infrastructure Monitor may become unavailable.

  Workaround: Restart Service and Infrastructure Monitor. [CD-296]

• Notification Engine may fail to provide some information to Service and Infrastructure Monitor.

  Workaround: None [CD-304]

• Service and Infrastructure Monitor may display some VNFs without the associated site name.

  Workaround: None [CD-323]

• Service and Infrastructure Monitor may fail to retrieve site information from cloud CPE Tenant, Site and Service Manager.

  Workaround: None [CD-325]

• Service and Infrastructure Monitor may display incorrect information about a network service chain.

  Workaround: None [CD-331]

• Administration Portal may not automatically update settings when they change.

  Workaround: Use the web browser to refresh the page. [CV-631]

• You cannot add multiple EMS instances with Administration Portal.

  Workaround: Use API calls to add multiple EMS instances. [CV-634]

• You cannot remove or disassociate network service profiles from customers in Administration Portal.

  Workaround: Use API calls to remove or disassociate network service profiles from customers. [CV-635]

• In a configuration with multiple VIMs, activation of a network service for a customer site fails if the VIM associated with the corporate transport network is different to the VIM associated with the customer site.

  Workaround: Specify a corporate transit network associated with the same VIM as the customer site. [CXU-1060]

• Sophos AV and EWF do not work with vSRX in the Cloud CPE Centralized Deployment Model.

  Workaround: Use Sophos AV and EWF with vSRX as a standalone virtual application. PR1173491

• In Customer Portal, deleting configuration settings for a network service may not be successful.

  Workaround: Deactivate the network service for the site, reactivate the network service, and reconfigure it. PR1174640

• When you configure the vSRX UTM VNF in Customer Portal or Network Service Designer, if you accept the default value (Yes) for all UTM settings and do not specify a blacklist or whitelist, the configuration fails.

  Workaround: When you configure the vSRX UTM VNF, specify a blacklist or whitelist. PR1178863

• In a redundant Contrail Service Orchestration installation, some of the VNFs may not start for a network service that contains multiple VNFs.

  Workaround: Wait a few minutes and the network service recovers automatically. PR1185755

• A network service may fail to start if the VM for a Contrail Service Orchestration component reboots during the network service activation. The status of the network service is then recorded as an input/output error in Service and Infrastructure Monitor.

  Workaround: Wait a few minutes and reactivate the network service. PR1186867

• A network service that uses multiple VNFs may recover with an incorrect combination of VNFs in the service chain.

  Workaround: Deactivate the network service and reactivate it. PR1186928

• Contrail Issue: Instance failed network setup due to exception.PortInUse Bug 1586437
• Contrail Issue: Sometime deleting heat stack fails. Bug 1427157