Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary

Navigation Back up to About Overview

[+] Expand All

[-] Collapse All

Contrail Service Orchestration 3.2.1 Release Notes
- Introduction
- Installation
- New and Changed Features in Contrail Service Orchestration Release 3.2.1
- Servers, Software, and Network Devices Tested
- Hardware, Software, and Virtual Machine Requirements for the Contrail Service Orchestration
  - Minimum Hardware Requirements for the Contrail Service Orchestration
  - Software and Virtual Machine Requirements
- VNFs Supported
- Licensing
- Accessing GUIs
- Changes in Behavior
- Known Behavior
- Known Issues
- Resolved Issues
- Documentation Updates
- Requesting Technical Support
- Revision History

Download This Guide

Download this guide: Contrail Service Orchestration 3.2.1 Release Notes

Resolved Issues

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

Whenever a new site is added and auto-NAT is enabled, a NAT policy job is triggered for all existing sites as well as for the new site. There is no impact to functionality; however, you will see additional jobs listed in the system.
Site-to-site traffic in the reverse direction in the hub-and-spoke topology mightnot take the desired path from the hub to the originating spoke. [CXU-16070]
The WAN link status does not change in the Site Management page of the Administration Portal when there are Link Up and LInk Down alarms. [CXU-16636]

Modified: 2018-05-24

Previous Page Next Page