New and Changed Features in Contrail Service Orchestration Release 4.0.2

This section describes the new features or enhancements to existing features in Contrail Service Orchestration (CSO) Release 4.0.2. For new and changed features in CSO Release 4.0.0, see the CSO 4.0.0 Release Notes at information-products/ pathway-pages/4.0/index.html.

  • CHAP authentication support for PPPoE—From Release 4.0.2 onward, Contrail Service Orchestration enables you to choose CHAP authentication for PPPoE. You can now choose either PAP or CHAP as the authentication protocol for PPPoE when you configure a site. PPPoE is available only on ADSL and VDSL links and in previous releases supported only PAP authentication.

  • ZTP of NFX250 over ADSL and VDSL links—From Release 4.0.2 onward, Contrail Service Orchestration supports ZTP of NFX250 devices with static and DHCP-based addressing over ADSL and VDSL links. The staging script (dsl-pre-staging.tgz) performs the configuration based on input YAML and configures JDM, JCP, and GWR for provisioning ADSL and VDSL links. After this, ZTP can be done over the link.

    Note In CSO Release 4.0.2, ZTP is not supported with PPPoE over ADSL and VDSL links.

Resolved Issues

The following issues are resolved in Juniper Networks CSO Release 4.0.2.

  • In device redundancy mode, while creating a NAT pool, the Routing Instance field is not displayed.

    Bug Tracking Number: CXU-25880

  • On a Dual CPE device, the deployment of the AllSite_AUTONAT_Policy policy fails.

    Bug Tracking Number: CXU-25855

  • The ZTP of an NFX250 device fails.

    Bug Tracking Number: CXU-25822.

  • For some sites, the Configure Site operation fails and the following error message is displayed:

    Policy is out of sync between RE and PFE fpc0. Please resync before commit.

    Bug Tracking Number: CXU-25808.

  • While upgrading CSO from Release 3.3.1 to Release 4.0.1, if link-interface or link-name mappings in Redis are lost, the link utilization graph is not displayed.

    Bug Tracking Number: CXU-25728.

  • After you upgrade CSO to Release 4.0.1, you cannot delete tenants that are created in CSO Release 3.3.1.

    Bug Tracking Number: CXU-25716.

  • In CSO Release 4.0.1, the site upgrade fails for sites with vSRX as a CPE device.

    Bug Tracking Number: CXU-25713.

  • The operation to delete tenants fails and the following error is displayed:

    PMTask Fail {"status_code": "409", "error_tag": "Refs Exist", "error_message": "Operation can not be completed since the resource is still being referred to. ", "error_app_message": "Delete when resource still referred: [u'/topology-service/termination-point/edea81b3-fc95-4d19-beea-e56ecfce3fb3', u'/topology-service/termination-point/1ba769cc-00d6-4ad3-914e-913cb4d707eb', u'/topology-service/termination-point/a74ff397-6993-437f-ba67-4ef0d57620bc', u'/topology-service/termination-point/b9a5dd21-3025-4cce-b8a9-7df6d32cf51f', u'/topology-service/termination-point/89c9f27d-4f68-4972-9c10-7ab68805d146', u'/topology-service/termination-point/6afba242-6905-4d3e-8295-4b7b5e791fdd', u'/topology-service/termination-point/e627802b-ec97-4343-8f5c-4c53415d3353']", "error_diag": "This error occurs when a resource is attempted for modification or deletion when there are child resources still referring to it. ", "error_code": "40006"}

    Bug Tracking Number: CXU-25686.

  • On an MX Series device, after you apply the stage-2 configuration, the BGP route is hidden.

    Bug Tracking Number: CXU-25665.

  • When you delete an SD-WAN policy, the custom application group associated with the SD-WAN is not deleted.

    Workaround: Log in to the device, and delete the custom application group.

    Bug Tracking Number: CXU-25657.

  • On a gateway router, the application identification license and the application signature that are installed are lost.

    Bug Tracking Number: CXU-25641.

  • The activation of an NFX250 as an SD-WAN CPE device with an ADSL or VDSL WAN link fails if you set the global parameter USE_SINGLE_SSH of the device template to False.

    Bug Tracking Number: CXU-25573.

  • After you upgrade CSO from Release 3.3.1 to Release 4.0.1, the widgets are not displayed in the Dashboard.

    Bug Tracking Number: CXU-25405.

  • While you are editing a role, when you clear an object, the implied capabilities that are listed under the object are cleared.

    Bug Tracking Number: CXU-25386.

  • For an Application Quality of Experience (AppQoE) tenant, an SLA profile with only the Throughput parameter is not supported.

    Bug Tracking Number: CXU-25378.

  • The tenant name cannot be the same across different operating companies.

    Bug Tracking Number: CXU-25225.

  • The POP location on the geographical map is incorrect if you do not validate the address while you are creating a POP.

    Bug Tracking Number: CXU-25060.

  • On the Monitor Overview Page page, a green check mark appears even though the operational state of a device that is going through the RMA process is Down, Expected, or RMA.

    Bug Tracking Number: CXU-24933.

  • The site upgrade for a dual CPE site fails because CSO does not support image upgrade.

    Bug Tracking Number: CXU-24823.

  • When you generate reports for operating companies and their tenants, the customized logo is not displayed.

    Bug Tracking Number: CXU-24729.

  • If all the infrastructure VMs are not up, reports cannot be generated.

    Bug Tracking Number: CXU-24560.

  • The class-of-service scheduler configuration does not take effect on the CPE device.

    Bug Tracking Number: CXU-20708

  • After you upgrade a site with an NFX250 device, the monitoring page does not display any data. This is because the telemetry agent is uninstalled during the site upgrade.

    Bug Tracking Number: CXU-19455.

  • CSO might not come up after a power failure.

    Bug Tracking Number: CXU-16530