The ability to manipulate the admin distance of BGP routes provides additional route selection control.īGP Autonomous System (AS) Number per Tier-0 VRF Gateway and BGP neighbor - This release introduces the support for configuring a different BGP ASN (Autonomous System Number) per Tier-0 VRF Gateway and also per BGP neighbor. Administrative Distance is an arbitrary value assigned to each routing protocol and used for route selection. This feature provides high availability against physical switch issues, like a physical switch port remaining up but forwarding not working properly.īGP Administrative Distance - This release introduces support for changing the BGP administrative distance from the default values. More details are available below in the detailed description of added features.ĮSXi MultiTEP High Availability - When multiple TEPs are configured on a hypervisor, NSX will track the status of the TEP IP addresses and the BFD sessions to failover the overlay traffic to another uplink. In addition, many other capabilities are added in every area of the product. Online Diagnostic System helps to automate debugging and simplifies troubleshooting. Recommended actions will be provided post debugging to fix the issue and the artifacts generated related to the debugging can be downloaded for further analysis. These runbooks can be invoked by API and will trigger debugging steps using the CLI, API and Scripts.

Online Diagnostic System provides predefined runbooks that contain debugging steps to troubleshoot a specific issue. This improves usability and functionality of using NSX to manage Antrea clusters. Dynamic groups can also be created based on NSX tags and K8s labels. This is made possible by the ability for the Enterprise Admin to segment the platform into Projects, giving different spaces to different users while keeping visibility and control.Īntrea to NSX Integration improvements - With NSX 4.1, you can create firewall rules with both K8s and NSX objects. Multi-tenancy available in UI, API and alarm framework - With this release we are extending the consumption model of NSX by introducing multi-tenancy, hence allowing multiple users in NSX to consume their own objects, see their own alarms and monitor their VMs with traceflow. When the Transport Node is configured with dual-stack (IPv4 and IPv6), IPv6 communication will be always preferred. In this release, the NSX manager cluster must still be deployed in dual-stack mode (IPv4 and IPv6) and will be able to communicate to Transport Nodes (ESXi hosts and Edge Nodes) either over IPv4 or IPv6. IPv6 support for NSX internal control and management planes communication - This release introduces support for Control-plane and Management-plane communication between Transport Nodes and NSX Managers over IPv6. Highlights include new features and enhancements in the following focus areas: NSX 4.1.0 provides a variety of new features to offer new functionalities for virtualized networking and security for private, public, and multi-clouds.

Manager http error 410