Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

New and Changed Features in Contrail Service Orchestration Release 5.1.1

 

This section describes the new features or enhancements to existing features in Contrail Service Orchestration (CSO) Release 5.1.1.

You can view and read the features that are available in the CSO Release 5.1.0 through the following link:

Install and Upgrade

  • Support for ESXi—CSO Release 5.1.0 supports only the KVM hypervisor, whereas CSO Release 5.1.1 supports KVM and ESXi version 6.7 hypervisors.

  • Supported path for upgrade from CSO Release 4.1.1 to CSO Release 5.1.1—The only supported upgrade path is from CSO Release 4.1.1 with medium deployment to CSO Release 5.1.1 with HA deployment. For details, see the Install and Upgrade guide.

  • Disk space required for upgrade from CSO Release 5.1.0 to CSO Release 5.1.1—You must have at least 40 GB disk space on the startupserver VM to run the upgrade.sh script. For details, see the Install and Upgrade guide.

SD-WAN

  • Support for full mesh on all WAN links of enterprise hubs and dual CPE Spoke sites—From CSO Release 5.1.1 onward, you can enable full mesh and configure mesh tags on up to four WAN links of an enterprise hub and dual CPE spoke sites. In releases before CSO Release 5.1.1, you can configure a maximum of three WAN links for meshing.

  • Support for advertising LAN prefixes—From CSO Release 5.1.1 onward, you can advertise the LAN prefixes of SD-WAN spoke sites to the data center through the data center department associated with the enterprise hub. This feature is applicable to dynamically routed LAN segments on the data center department and is disabled by default.

    If you disable advertising LAN prefixes of SD-WAN spoke sites, LAN routes are not advertised to the neighbor. In such cases, you must configure source NAT on the enterprise hub from the CSO UI or configure reverse routes on the routing device.

    Note

    You must avoid overlapping IP addresses between the SD-WAN LAN network and the data center network.

  • Support for multiple WAN links on the same physical interface for enterprise hub sites—From CSO Release 5.1.1 onward, for enterprise hub sites, you can configure more than one WAN link on the same physical interface. The WAN links are connected from the same physical interface to the provider edge (PE) nodes through logical subinterfaces with VLAN separation.

  • Support for SRX1500 as a spoke, a provider hub, or an enterprise hub—From CSO Release 5.1.1 onward, you can configure an SRX1500 device as a spoke, a provider hub, or an enterprise hub in SD-WAN deployments. You can use the SRX1500 device as a single CPE or dual CPE cluster in the SD-WAN deployments.

    Note
    • SRX1500 devices must run Junos OS Release 19.3R2-S1 (Beta version) to be configured as a spoke or enterprise hub.

    • In CSO Release 5.1.1, LTE and DSL links are not supported for SRX1500 devices.

SD-LAN

  • Support for adding multiple EX Series switches—From CSO Release 5.1.1 onward, you can add one or more EX Series switches to an existing SD-LAN site. Both physical, standalone EX Series switches and EX Series Virtual Chassis are supported.

    Note

    To configure more than one switch with an SD-WAN CPE or a next-generation firewall, add an SD-LAN logical site and add multiple switches to the site. You can manage the connectivity and configuration between the switches and the CPE or next-generation firewall either by using configuration templates or manually.

  • Support for preprovisioning an EX Series Virtual Chassis—From CSO Release 5.1.1 onward, you can preprovision an EX2300, EX3400, EX4300, EX4600, and EX4650 Virtual Chassis. This means that while adding an SD-LAN site, you can configure a Virtual Chassis by specifying the primary, backup, and linecard members of the Virtual Chassis in the site creation workflow.

    The members of the Virtual Chassis must be of the same device type, with the same device models or different device models.

    Note

    Mixed-mode Virtual Chassis, that is, members of different device types, is not supported in this release. For example, the members of the Virtual Chassis cannot be a combination of EX4300 and EX4600 or EX4650 devices.

  • Assigning port profiles to an EX Series Switch while onboarding—From CSO Release 5.1.1 onward, you can assign port profiles to a switch while onboarding the switch to CSO. By assigning port profiles while onboarding the switch, you can provision the switch and configure the switch ports in a single operation.

Miscellaneous

  • Support for ZTP on copper ports—From CSO Release 5.1.1 onward, the factory-default settings on NFX Series devices enable you to use cost-effective copper ports (10/100/1000BASE-T) as WAN ports and to perform zero-touch provisioning (ZTP) of the devices.

    In CSO releases before Release 5.1.1, you can use only SFP ports as the factory-default WAN ports and to perform ZTP.

    • For NFX150 devices (with platform image 19.3R2 and later), the factory-default WAN ports are the first copper port and last SFP port. You can use these ports to perform ZTP.

    • For NFX250 devices, you can use any of the ports on the front panel to perform ZTP.

  • Support for autogenerating e-mails for SD-LAN and SD-WAN alarms—From CSO Release 5.1.1 onward, SP administrators, OpCo administrators, and tenant administrators can enable e-mail notifications and specify the recipients to be notified if there are SD-LAN and SD-WAN alarms.

  • Support for LAG templates—From CSO Release 5.1.1 onward, you can configure a link aggregation group (LAG) on an EX Series switch by using the following configuration templates:

    • MC-LAG: Template for configuring a multichassis link aggregation group (MC-LAG) on an MC-LAG peer device.

    • LAG-EX-Trunk: Template for configuring a link aggregation group (LAG) on a switch when the switch is operating in trunk mode.