New and Changed Features
This section describes the new features and enhancements in this release.
Class of Service support for configuring maximum number of level 3 scheduler nodes—Starting in Junos OS Release 18.3R1, to address issues with vMX QOS performance for an interface that has a low number of learning interfaces (IFLs), a new CLI option maximum-l3-nodes has been added to hierarchical-scheduler to allow you to configure the maximum level 3 nodes for a port.
The default value for maximum-l3-nodes is 16K (16 * 1024). You can configure maximum-l3-nodes to a minimum of 2 and a maximum of 32K (32 * 1024). The configured value must be a power of 2.
For example:
content_copy zoom_out_mapuser@vmx# set interfaces ge-0/0/0 hierarchical-scheduler maximum-l3-nodes 32768
NoteThis configuration must be present before you reboot the FPC.
In addition, the scaling number has changed for the maximum-l2-nodes CLI option. The maximum level 2 scheduler nodes per port has been changed from 16 to 16K (16 * 1024).
[See Understanding Hierarchical CoS for Subscriber Interfaces.]
Nutanix Support for vMX—Starting in Junos OS Release 18.3R1, you can deploy a vMX instance on a Nutanix Acropolis Hypervisor (AHV) 5.5 cluster. Nutanix AHV is a virtualization solution included with Acropolis that delivers enterprise virtualization ready for multi-cloud environments. Nutanix nodes with AHV include a distributed VM management service responsible for storing VM configuration, making scheduling decisions, and exposing a management interface.
EVPN P2MP bud router support (MX Series and vMX)—Starting in Junos OS Release 18.3R1, Junos OS supports configuring a point-to-multipoint (P2MP) label-switched path (LSP) as a provider tunnel on a bud router. The bud router functions both as an egress router and a transit router.
To enable a bud router to support P2MP LSP, include the evpn p2mp-bud-support statement at the [edit routing-instances routing-instance-name protocols evpn] hierarchy level.
[See Configuring Bud Node Support.]
