Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes for EX Series Switches

 

These release notes accompany Junos OS Release 18.1R3 for the EX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.

New and Changed Features

This section describes the new features and enhancements to existing features in the Junos OS main release and the maintenance releases for EX Series.

Note

The following EX Series switches are supported in Release 18.1R3: EX2300, EX3400, EX4300, EX4600, and EX9200.

Note

In Junos OS Release 18.1R3, J-Web is supported on the EX2300, EX3400, EX4300, and EX4600 switches in both standalone and Virtual Chassis setup.

The J-Web distribution model being used provides two packages:

  • Platform package—Installed as part of Junos OS; provides basic functionalities of J-Web.

  • Application package—Optionally installable package; provides complete functionalities of J-Web.

For details about the J-Web distribution model, see J-Web Application Package Release 18.1A1 for EX2300, EX3400, EX4300, and EX4600 Switches.

Release 18.1R3-S3 New and Changed Features

EVPNs

  • Support for VMTO for ingress traffic (EX9200)—Starting in Junos OS Release 18.1R3-S3, you can configure the PE device to support virtual machine traffic optimization (VMTO) for ingress traffic. VMTO eliminates the unnecessary ingress routing to default gateways when a virtual machine is moved from one data center to another.

    To enable VMTO, configure remote-ip-host routes in the [edit routing-instances routing-instance-name protocols evpn] hierarchy level. You can also filter out the unwanted routes by configuring an import policy under the remote-ip-host routes option.

    [See Configuring EVPN Routing Instances.]

  • Support for Multihomed Proxy Advertisement (EX9200)—Junos now provides enhanced support to proxy advertise the Mac address and IP route entry from all PEs that are multi-homed to a CE device. This can prevent traffic loss when one of the links to the PE fails. To support the multihomed proxy advertisement, all multi-homed PE devices should have the same multihomed proxy advertisement bit value. The multihomed proxy advertisement feature is enabled by default and Junos uses the default multihomed proxy advertisement bit value of 0x20.

    [See EVPN Multihoming Overview.]

  • Support for OSPF, IS-IS, BGP, and static routing on IRB interfaces in EVPN-VXLAN networks (EX9200)—Starting in Junos OS Release 18.1R3-S3, you can configure OSPF, IS-IS, BGP, and static routing with bidirectional forwarding detection (BFD) on an IRB interface that is used as a routed interface in EVPN. This allows protocol adjacencies to be established between an IRB on a Layer 3 gateway and a CE device connected directly to a Layer 3 gateway or to a Layer 2 leaf device in an EVPN-VXLAN network.

    [See Supported Protocols on an IRB Interface in EVPN-VXLAN .]

Release 18.1R3 New and Changed Features

  • There are no new features or enhancements to existing features for EX Series switches in Junos OS Release 18.1R3.

Release 18.1R2 New and Changed Features

Hardware

  • EX2300-24MP and EX2300-48MP switches—Starting with Junos OS Release 18.1R2, two new models of EX2300 switches—EX2300-24MP and EX2300-48MP—are available. EX2300-24MP switch models have eight 100/1000/2500 BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, 16 10/100/1000 BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, and four built-in 10-Gigabit Ethernet uplink ports. EX2300-48MP switch models have 16 100/1000/2500 BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, 32 10/100/1000 BASE-T Gigabit Ethernet ports with PoE/PoE+ capability, and six built-in 10-Gigabit Ethernet uplink ports.

    [See EX2300 Switch Hardware Guide.]

Interfaces and Chassis

  • Support for Multi-Gigabit Ethernet (EX2300)—Starting in Junos OS Release 18.1R2, the Multi-Gigabit Ethernet feature is supported on EX2300-48MP and EX2300-24MP switches. This feature fulfills the high-speed requirements for a large and mid-size campus, and branch locations for the enterprise customers.

    The mge interface is a rate-selectable (multirate) Gigabit Ethernet interface that can support speeds of 10 Gbps, 5 Gbps, and 2.5 Gbps over CAT5e/CAT6/CAT6a cables. In the EX2300, the mge interface supports 100 Mbps, 1 Gbps, and 2.5 Gbps speeds, which can be configured by using the speed configuration statement.

    Note

    Power over Ethernet (PoE) is supported on Multi-Gigabit Ethernet interfaces. PoE enables EX2300 switches to transfer electrical power through an Ethernet cable. PoE enables electric power, along with data, to be passed over a copper Ethernet LAN cable.

    [See Speed.]

  • Support for Power over Ethernet (EX2300-24MP and EX2300-48MP)—Starting in Junos OS Release 18.1R2, Power over Ethernet (PoE) is supported on EX2300-24MP and EX2300-48MP switch models, including multigigabit interfaces. (PoE) permits electric power, along with data, to be passed over a copper Ethernet LAN cable.

    EX2300 24MP switches support PoE (IEEE 802.3af) and PoE+ (IEEE 802.at) and can simultaneously deliver up to 15.4 watts of standards-based 802.3af Class 3 PoE to a maximum of 24 ports or 30 watts of standards-based 802.3at PoE+ to a maximum of 12 ports, based on a total system budget of 380 watts.

    EX2300 48MP switches support PoE (IEEE 802.3af) and PoE+ (IEEE 802.at) and can simultaneously deliver up to 15.4 watts of standards-based 802.3af Class 3 PoE to a maximum of 48 ports or 30 watts of standards-based 802.3at PoE+ to a maximum of 24 ports, based on a total system budget of 740 watts.

    [See Understanding PoE on EX Series Switches.]

Restoration Procedures Failure

  • Device recovery mode introduced in Junos OS with upgraded FreeBSD (EX Series)—In Junos OS Release 18.1R2, for devices running Junos OS with upgraded FreeBSD, provided you have saved a rescue configuration on the device, there is an automatic device recovery mode that goes into action should the system go into amnesiac mode.The new process is for the system to automatically retry to boot with the saved rescue configuration. In this circumstance, the system displays a banner "Device is in recovery mode” in the CLI (in both the operational and configuration modes). Previously, there was no automatic process to recover from amnesiac mode. A user with load and commit permission had to log in using the console and fix the issue in the configuration before the system would reboot.

    [See Saving a Rescue Configuration File.]

Virtual Chassis

  • Virtual Chassis support (EX2300-24MP and EX2300-48MP)—Starting in Junos OS Release 18.1R2, multigigabit EX2300 switches can be interconnected into a Virtual Chassis and operate as one logical device managed as a single chassis, as follows:

    • Members can be any combination of up to four EX2300-24MP and EX2300-48MP switches.

    • Multigigabit EX2300 switches cannot be mixed with any other switch models (including any other EX2300 switches) in the same Virtual Chassis.

    • Any 10-Gbps uplink ports installed with SFP+ transceivers can be configured as Virtual Chassis ports (VCPs) to interconnect the members. Multigigabit EX2300 switches do not have any dedicated or default-configured VCPs.

    To configure a multigigabit EX2300 Virtual Chassis, use similar steps as for configuring other EX Series and QFX Series Virtual Chassis.

    [See Understanding EX2300 Virtual Chassis.]

Release 18.1R1 New and Changed Features

Hardware

  • EX9251 switches—Starting with Junos OS Release 18.1R1, EX9251 switches are available as a fixed configuration switch. It is an Ethernet-optimized switch that provides carrier-class Ethernet switching. It has a throughput of up to 400 gigabits per second (Gbps). The switch is available in two variants—with AC power supply and with DC power supply.

    [See EX9251 Switch Hardware Guide.]

Authentication, Authorization, and Accounting (AAA) (RADIUS)

  • Access control and authentication (EX2300 and EX3400 switches)—Starting with Junos OS Release 18.1R1, EX2300 and EX3400 switches support controlling access to your network using 802.1X authentication and MAC RADIUS authentication.

    • 802.1X authentication provides port-based network access control (PNAC) as defined in the IEEE 802.1X standard. QFX5100 switches support 802.1X features including guest VLAN, private VLAN, server fail fallback, dynamic changes to a user session, RADIUS accounting, and configuration of port-filtering attributes on the RADIUS server using VSAs. You configure 802.1X authentication at the [edit protocols dot1x] hierarchy level.

    • MAC RADIUS authentication is used to authenticate end devices independently of whether they are enabled for 802.1X authentication. You can permit end devices that are not 802.1X-enabled to access the LAN by configuring MAC RADIUS authentication on the switch interfaces to which the end devices are connected. You configure MAC RADIUS authentication at the [edit protocols dot1x authenticator interface interface-name mac-radius] hierarchy level.

    This feature was introduced previously in an “X” release of Junos OS.

    [See Understanding Authentication on Switches.]

  • TACACS+ authorization for operational commands using regular expressions (EX2300, EX3400, EX4300 switches and MX Series)—Starting in Junos OS Release 18.1R1, you can configure authorizations for operational mode commands using regular expressions using the allow-commands-regexps and deny-commands-regexps statements. Authorizations can also be configured remotely by specifying Juniper Networks vendor-specific attributes (VSAs) in your TACACS+ authentication server's configuration.

    [See Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands, Configuration Statements, and Hierarchies.]

Class of Service (CoS)

  • Support for Class of service (EX2300 and EX3400 switches and EX3400 Virtual Chassis)—Starting in Junos OS Release 18.1R1, when a packet traverses a switch, the switch provides the appropriate level of service to the packet using either default class-of-service(CoS) settings or CoS settings that you configure. On ingress ports, the switch classifies packets into appropriate forwarding classes and assigns a loss priority to the packets. On egress ports, the switch applies packet scheduling and any rewrite rules to re-mark packets.

    This feature was previously supported in an “X” release of Junos OS.

    [See Junos OS CoS for EX Series Switches Overview.]

High Availability (HA) and Resiliency

  • High availability features (EX3400 switches and EX3400 Virtual Chassis)—Starting with Junos OS Release 18.1R1, high availability features are supported. High availability features refer to the hardware and software components that provide redundancy and reliability for network communications.

    The following features are supported:

    • Graceful Routing Engine switchover (GRES), nonstop active routing and nonstop bridging

    • Virtual Router Redundancy Protocol (VRRP) support

      VRRP enables you to provide alternative gateways for end hosts that are configured with static default routes. You can implement VRRP to provide a high availability default path to a gateway without the need to configure dynamic routing or router discovery protocols on end hosts.

    [See High Availability User Guide.]

Layer 2 Features

  • Layer 2 features (EX3400 switches and EX3400 Virtual Chassis)—Starting with Junos OS Release 18.1R1, the following Layer 2 features are supported:

    • VLAN support

      VLANs enable you to divide one physical broadcast domain into multiple virtual domains.

    • Link Layer Discovery Protocol (LLDP) support

      LLDP enables a switch to advertise its identity and capabilities on a LAN, as well as receive information about other network devices.

    • Q-in-Q tunneling support

      This feature enables service providers on Ethernet access networks to extend a Layer 2 Ethernet connection between two customer sites.

    • Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and VLAN Spanning Tree Protocol (VSTP) support

      These protocols enable a switch to advertise its identity and capabilities on a LAN and receive information about other network devices.

    This feature was previously supported in an “X” release of Junos OS.

    [See Ethernet Switching User Guide.]

Layer 3 Features

  • Layer 3 feature support (EX2300 and EX3400 Switches)—Starting with Junos OS Release 18.1R1, the Layer 3 features supported in Junos OS Release 15.1X53-D50 are now supported on EX2300 and EX4300 Switches.

Multicast

  • Layer 2 and Layer 3 multicast support (EX2300 switches and Virtual Chassis, EX3400 switches and Virtual Chassis)—Starting in Junos OS Release 18.1R1, the following IPv4 and IPv6 multicast protocols are supported:

    • Internet Group Management Protocol (IGMP) v1, v2, and v3

    • IGMP snooping

    • Multicast Listener Discovery (MLD) protocol v1 and v2

    • MLD snooping

    • Multicast Source Discovery Protocol (MSDP)

    • Protocol Independent Multicast (PIM) sparse mode (SM), dense mode (DM), and source-specific multicast (SSM)

    These features were previously supported in an “X” release of Junos OS.

    [See Multicast Protocols User Guide.]

Network Management and Monitoring

  • Pseudohardware RPM timestamps (EX4300 switches and EX4300 Virtual Chassis)—Starting in Junos OS Release 18.1R1, you can configure a pseudo-hardware timestamp on the switch for real-time performance monitoring (RPM). RPM enables you to configure active probes to track and monitor traffic on the network. To achieve this, RPM exchanges a set of probes with other IP hosts in the network. These probes are sent from a source node to other destination devices in the network that requires tracking. To account for latency or jitter in the communication of probe messages, you can enable timestamping of the probe packets. On the EX4300 switch, RPM timestamping is performed in the software. The RPM probes at the requester and responder devices are timestamped in the Packet Forwarding Engine instead of the Junos OS process (rmpod) that runs on the Routing Engine. This timestamping method is referred to as pseudo-hardware timestamping. You must configure the switch as both the RPM client (the requester) and the RPM server (the responder) to timestamp the RPM packet. You configure pseudohardware timestamps at the [edit services rpm] hierarchy level.

    [See Understanding Real-Time Performance Monitoring on EX Series Switches.]

  • Port mirroring support (EX2300, EX2300-C, and EX3400 switches and EX3400 Virtual Chassis)—Starting in Junos OS Release 18.1R1, port mirroring is supported on EX2300, EX2300-C, and EX3400 switches and EX3400 Virtual Chassis. Port mirroring copies packets entering or exiting a port or entering a VLAN and sends the copies to a local interface for local monitoring. You can use port mirroring to send traffic to applications that analyze traffic for purposes such as monitoring compliance, enforcing policies, detecting intrusions, monitoring and predicting traffic patterns, and correlating events.

    This feature was previously supported in an “X” release of Junos OS.

    [See Understanding Port Mirroring and Analyzers on EX2300, EX3400, and EX4300 Switches.]

Port Security

  • IPv4/IPv6 source guard (EX4600 switches)—Starting in Junos OS Release 18.1R1, you can configure the IP source guard access port security feature to mitigate the effects of source IP address spoofing and source MAC address spoofing. If IP source guard determines that a host connected to an access interface has sent a packet with an invalid source IP address or source MAC address in the packet header, it discards the packet. This feature is supported for IPv4 and IPv6 source addresses.

    [See Understanding IP Source Guard for Port Security on EX Series Switches.]

  • MACsec license enforcement (EX3400, EX4300, EX4600, EX9200, QFX5100 switches and Junos Fusion Enterprise)—Starting in Junos OS Release 18.1R1, Media Access Control Security (MACsec) requires the installation of a MACsec feature license. If the MACsec license is not installed, MACsec functionality cannot be activated. You add the MACsec license using the request system license add command.

    [See Understanding Media Access Control Security (MACsec).]

Security

  • Distributed denial-of-service (DDoS) protection (EX2300 and EX3400 switches, EX2300 and EX3400 Virtual Chassis)—Starting in Junos OS Release 18.1R1, you can configure DDoS protection that enables the switch to continue functioning while under attack. DDoS attacks use multiple sources to flood a network or switch with protocol control packets. This malicious traffic triggers a large number of exceptions in the network and tries to exhaust the system resources so that valid users are denied access to the network or server. DDoS protection identifies and suppresses malicious control packets while enabling legitimate control traffic to be processed.

    [See Distributed Denial-of-Service (DDoS) Protection Overview.]

  • Support for firewall filters (EX2300 and EX3400 switches, EX2300 and EX3400 Virtual Chassis)—Starting in Junos OS Release 18.1R1, you can define firewall filters on the switch that define whether to accept or discard packets. You can use firewall filters on interfaces, VLANs, routed VLAN interfaces (RVIs), link aggregation groups (LAGs), and loopback interfaces.

    This feature was previously supported in an “X” release of Junos OS.

    [See Firewall Filters for EX Series Switches Overview.]

  • Port security features (EX2300 and EX3400 switches, EX2300 and EX4300 Virtual Chassis)—Starting in Junos OS Release 18.1R1, the following port security features are supported:

    • DHCP snooping (Pv4 and IPv6)—Filters and blocks ingress Dynamic Host Configuration Protocol (DHCP) server messages on untrusted ports, and builds and maintains a database of DHCP lease information, which is called the DHCP snooping database.

    • Dynamic ARP inspection (DAI)—Prevents Address Resolution Protocol (ARP) spoofing attacks. ARP requests and replies are compared against entries in the DHCP snooping database, and filtering decisions are made on the basis of the results of those comparisons. You enable DAI on a VLAN.

    • IPv6 neighbor discovery inspection—Prevents IPv6 address spoofing attacks. Neighbor discovery requests and replies are compared against entries in the DHCPv6 snooping database, and filtering decisions are made on the basis of the results of those comparisons. You enable neighbor discovery inspection on a VLAN.

    This feature was previously supported in an “X” release of Junos OS.

    [See Understanding Port Security Features to Protect the Access Ports on Your Device Against the Loss of Information and Productivity.]

  • Port mirroring to IP address (EX4600 switches and Virtual Chassis)—Starting with Junos OS Release 18.1R1, you can send mirrored packets to an IP address over a Layer 3 network (for example, if there is no Layer 2 connectivity to the analyzer device).

    [See Understanding Port Mirroring.]

User Interface and Configuration

  • Support for configuring the ephemeral database using the NETCONF and Junos XML protocols (EX2300, EX3400, EX4300, EX4600, and EX9200 switches)—Starting in Junos OS Release 18.1R1, NETCONF and Junos XML protocol client applications can configure the ephemeral configuration database. The ephemeral database provides a fast programmatic interface that enables multiple clients to simultaneously load and commit configuration changes on a device running Junos OS and with significantly greater throughput than when committing data to the candidate configuration database. Junos OS provides a default instance and up to eight user-defined instances of the ephemeral configuration database. The device’s active configuration is a merged view of the committed configuration database and the configuration data in all instances of the ephemeral configuration database. Ephemeral configuration data is volatile and is deleted upon rebooting the device.

    [See Understanding the Ephemeral Configuration Database.]

Virtual Chassis

  • Virtual Chassis support (EX2300, EX3400)—Starting in Junos OS Release 18.1R1, EX2300 or EX3400 switches can be interconnected into a Virtual Chassis and operate as one logical device managed as a single chassis, as follows:

    • EX2300 Virtual Chassis: Up to four EX2300 and EX2300-C member switches, interconnected using any 10-Gbps SFP+ ports configured as Virtual Chassis ports (VCPs)

    • EX3400 Virtual Chassis: Up to 10 EX3400 member switches, interconnected using the QSFP+ uplink ports (default-configured VCPs) or any SFP+ uplink ports configured as VCPs

    To configure an EX2300 or EX3400 Virtual Chassis, use similar steps as for configuring other EX Series and QFX Series Virtual Chassis.

    This feature was previously supported in an “X” release of Junos OS.

    [See Virtual Chassis User Guide for Switches.]

Changes in Behavior and Syntax

This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands from Junos OS Release 18.1R3 for the EX Series.

Release 18.1R3-S10 Changes in Behavior and Syntax

Routing Protocols

  • Enhancement to the show interfaces mc-ae extensive command—You can now view additional LACP information about the LACP partner system ID when you run the show interfaces mc-ae extensive command. The output now displays the following two additional fields:

    • Local Partner System ID-LACP partner system ID as seen by the local node.

    • Peer Partner System ID-LACP partner system ID as seen by the MC-AE peer node.

Previously, the show interfaces mc-ae extensive command did not display these additional fields.

[See show interfaces mc-ae.]

Release 18.1R3-S7 Changes in Behavior and Syntax

Routing Protocols

  • Enhancement to the show interfaces mc-ae extensive command—You can now view additional LACP information about the LACP partner system ID when you run the show interfaces mc-ae extensive command. The output now displays the following two additional fields:

    • Local Partner System ID-LACP partner system ID as seen by the local node.

    • Peer Partner System ID-LACP partner system ID as seen by the MC-AE peer node.

Previously, the show interfaces mc-ae extensive command did not display these additional fields.

[See show interfaces mc-ae.]

Release 18.1R3 Changes in Behavior and Syntax

Network Management and Monitoring

  • New context-oid option for trap-options configuration statement to distinguish the traps that come from a non-default routing instance and a non-default logical system (EX Series)—Starting in Junos OS Release 18.1R3, a new option, context-oid, for the trap-options statement allows you to handle prefixes such as <routing-instance name>@<trap-group> or <logical-system name>/<routing-instance name>@<trap-group> as an additional varbind.

    [See trap-options.]

Layer 2 Features

  • Configuration option for LLDP VLAN name type, length, and value (TLV) (EX3400, EX4300)—Starting in Junos OS Release 18.1R3, you can configure the vlan-name-tlv-option (name | vlan-id) statement at the [edit protocols lldp] hierarchy level to select whether to transmit the VLAN name or simply the VLAN ID for the Link Layer Discovery Protocol (LLDP) VLAN name TLV when exchanging LLDP messages. By default, EX Series switches running Enhanced Layer 2 Software (ELS) transmit the VLAN ID for the LLDP VLAN name TLV, and the show lldp detail command displays the default string vlan-vlan-id for an interface’s VLAN name in the Vlan-name output field. Switches that support the vlan-name-tlv-option statement behave the same as the default if you configure the vlan-id option with this statement. If you configure the name option, the switch transmits the VLAN name instead, and the show lldp detail command displays the VLAN name in the Vlan-name output field.

Security

  • Firewall warning message (EX2300 switches)—Starting in 18.1R3, a warning message is displayed whenever a firewall term includes log or syslog with the accept filter action.

Subscriber Management and Services

  • DHCPv6 lease renewal for separate IA renew requests (EX Series)—Starting in Junos OS Release 18.1R3, the jdhcpd process handles the second renew request differently in the situation where the DHCPv6 client CPE device does both of the following:

    • Initiates negotiation for both the IA_NA and IA_PD address types in a single solicit message.

    • Sends separate lease renew requests for the IA_NA and the IA_PD and the renew requests are received back-to-back.

    The new behavior is as follows:

    1. When the reply is received for the first renew request, if a renew request is pending for the second address type, the client stays in the renewing state, the lease is extended for the first IA, and the client entry is updated.

    2. When the reply is received for the second renew request, the lease is extended for the second IA and the client entry is updated again.

    In earlier releases:

    1. The client transitions to the bound state instead of staying in the renewing state. The lease is extended for the first IA and the client entry is updated.

    2. When the reply is received for the second renew request, the lease is not renewed for the second address type and the reply is forwarded to the client. Consequently, when that lease ages out, the binding for that address type is cleared, the access route is removed, and subsequent traffic is dropped for that address or address prefix.

    [See Using DHCPv6 IA_NA with DHCPv6 Prefix Delegation Overview.]

Virtual Chassis

  • New configuration option to disable automatic Virtual Chassis port conversion (EX4300 and EX4600 Virtual Chassis)—Starting in Junos OS Release 18.1R3, you can use the no-auto-conversion statement at the [edit virtual-chassis] hierarchy level to disable automatic Virtual Chassis port (VCP) conversion in an EX4300 or EX4600 Virtual Chassis. Automatic VCP conversion is enabled by default on these switches. When automatic VCP conversion is enabled, if you connect a new member to a Virtual Chassis or add a new link between two existing members in a Virtual Chassis, the ports on both sides of the link are automatically converted into VCPs when all of the following conditions are true:

    • LLDP is enabled on the interfaces for the members on both sides of the link. The two sides exchange LLDP packets to accomplish the port conversion.

    • The Virtual Chassis must be preprovisioned with the switches on both sides of the link already configured in the members list of the Virtual Chassis using the set virtual-chassis member command.

    • The ports on both ends of the link are supported as VCPs and are not already configured as VCPs.

    Automatic VCP conversion is not needed when using default-configured VCPs on both sides of the link to interconnect two members. On both ends of the link, you can also manually configure network or uplink ports that are supported as VCPs, whether or not the automatic VCP conversion feature is enabled.

    Deleting the no-auto-conversion statement from the configuration returns the Virtual Chassis to the default behavior, which reenables automatic VCP conversion.

    [See no-auto-conversion.]

Release 18.1R2 Changes in Behavior and Syntax

Interfaces and Chassis

  • EEE not supported on mge interfaces operating at 100-Mbps speed (EX2300-24MP and EX2300-48MP)—In Junos OS Releases 18.1R2, if both Energy Efficient Ethernet (EEE) and 100-Mbps speed are configured on a rate-selectable (or multirate) Gigabit Ethernet (mge) port on EX2300-24MP and EX2300-48MP switches, the port operates only at 100-Mbps speed but EEE is not enabled on that port. EEE is supported only on mge interfaces that operate at 1-Gbps and 2.5-Gbps speeds.

Multicast

  • Support for per-source multicast traffic forwarding with IGMPv3 (EX2300 and EX3400)—Starting in Junos OS Release 18.1R2, EX2300 and EX3400 switches forward multicast traffic on a per-source basis according to received IGMPv3 INCLUDE and EXCLUDE reports. In releases prior to this release, EX2300 and EX3400 switches process IGMPv3 reports, but instead of source-specific multicast (SSM) forwarding, they consolidate IGMPv3 INCLUDE and EXCLUDE mode reports for a group into one route for all sources sending to the group. As a result, with the prior behavior, receivers might get traffic from sources they didn’t specify.

    [See IGMP Snooping Overview.]

Release 18.1R1 Changes in Behavior and Syntax

Management

  • Enhancement to NPU memory sensors for Junos Telemetry Interface (EX9200 switches)—Starting with Junos OS Release 18.1R1, the format of telemetry data exported through gRPC for NPU memory and memory utilization implements prefix compression. This change reduces the payload size of data exported. The following example shows the new format:

    key: __prefix__

    str_value: /components/component[name='FPC0:NPU0']/properties/property

    key: [name='mem-util-edmem-size']/value

    uint_value: 12345

    Telemetry data is exported in key-value pairs. Previously, the data exported included the component and property names in a single key string.

    [See Guidelines for gRPC Sensors.]

  • Enhancement to LSP statistics sensor for Junos Telemetry Interface (EX9200 switches, QFX10000 switches, MX Series, and PTX Series)—Starting with Junos OS 18.1R1, the telemetry data exported for the LSP statistics sensor no longer includes the phrase and source 0.0.0.0 after the LSP name in the value string for the prefix key. This change reduces the payload size of data exported. The following is an example of the new format:

    str_value: /mpls/lsps/constrained-path/tunnels/tunnel[name='LSP-4-3']/state/counters[name='c-27810']/

Network Management and Monitoring

  • SNMP syslog messages changed (EX Series)—Starting in Junos OS Release 18.1R1, two misleading SNMP syslog messages have been rewritten to accurately describe the event:

    • OLD—AgentX master agent failed to respond to ping. Attempting to re-register

      NEW—AgentX master agent failed to respond to ping, triggering cleanup!

    • OLD—NET-SNMP version %s AgentX subagent connected

      NEW—NET-SNMP version %s AgentX subagent Open-Sent!

    [See the MIB Explorer.]

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 18.1R3 for the EX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Infrastructure

  • When the image is copied through FTP from a server to a switch, sometimes the ftpd WCPU might go high, causing the CLI to freeze for approximately 10 seconds. PR1306286

  • On rare occasions, the EX2300-MP switch panics with fatal abort. This issue is seen when the rpd process is aborted and it occurs only when dtrace is enabled with continuous rpd process killing. PR1329552

  • Issue is specific to downgrade (17.4T) and a core file is seen only once during downgrade due to timing issue in the SDK toolkit upgrade. After the upgrade, dcpfe recovers on its own and no issues will be seen after that. PR1337008

Interfaces and Chassis

  • Previously, the same IP address could be configured on different logical interfaces from different physical interfaces in the same routing instance (including the master routing instance), but only one logical interface was assigned with the identical address after commit. There was no warning during the commit, only syslog messages indicating incorrect configuration. This issue is fixed and it is now not allowed to configure the same IP address (the length of the mask does not matter) on different logical interfaces. PR1221993

Platform and Infrastructure

  • On EX4300 switches, when 802.1X single-supplicant authentication is initiated, multiple EAP Request Id Frame Sent packets might be sent. PR1163966

  • On EX4300 10G links, preexisting MACsec sessions might not come up after the following events (1) Process (pfex, dot1x) restarts or the system restarts. (2) The link flaps. PR1294526

  • LAG interfaces flap during unified ISSU when fast LACP timers are configured. This might result in traffic loss during the unified ISSU. This issue occurs because Fast LACP timers are not supported on EX-92XX during unified ISSU. The fast LACP timer support needs to be added. PR1316251

  • NSSU upgrade from Junos OS Release 15.1X53-D58 to Junos OS Release 18.1R1 will fail with ksyncd core in backup Routing Engine. PR1344686

  • When upgrading from certain release to Junos OS Release 18.1R1 statistics daemon PFED might be seen generating core files. This issue is not service impacting. The issue can be cleared by rebooting the chassis or by deleting all files from /mfs. PR1346925

Virtual Chassis

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 18.1R3 for the EX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • On an EX9200-12QS line card, interfaces with the default speed of 10 Gigabit Ethernet are not brought down even when the remote end of a connection is misconfigured as 40 Gigabit Ethernet. PR1175918

  • On an EX9200-40XS line card, if you toggle the MACsec encryption option multiple times, encryption and protected MACsec statistics might be updated incorrectly. As a workaround, restart the line card. PR1185659

  • When a configuration that offlines a Packet Forwarding Engine and another configuration that brings the Packet Forwarding Engine back online, is committed in quick succession, there could be Routing Engine and Packet Forwarding Engine out of sync errors logged in syslog. Most of the time these are benign errors, but sometimes they might result in Packet Forwarding Engine crashes. PR1232178

  • Some configurations that are valid in Junos OS Release 12.3 are not valid for Junos OS Release 15.1. When you try to upgrade from Junos OS Release 12.3 to 15.1 with such configurations, after upgrade the device goes into amnesiac mode. PR1313501

  • In a streaming telemetry scenario, if performing commit full, the na-grpd process might restart, causing disconnection of the streaming telemetry. PR1326366

  • On EX2300 and EX3400 switches with SFP, when the actual receiver signal power exceeds 0.21 mW, the output of the command show interfaces diagnostics optics might display an incorrect value for the field Receiver signal average optical power. PR1326642

  • On an EX3400 platform, when force-renew is initiated from a server, the renewing entry for the bounded client will not be displayed under show dhcp-security binding. PR1328542

  • On EX4600 platforms, in some cases, the CoS (class of Service) configuration is not properly applied in the Packet Forwarding Engine, leading to unexpected egress traffic drop on some interfaces. PR1329141

  • On an EX9251 switch, after you perform the restart chassis-control for the first time after the software image is upgraded or after the switch is rebooted, the MPC booting state changes from offline to online directly, without staying at present state during booting. This issue is seen occasionally. There is no functional impact because of this state change. PR1332613

  • On an EX9251 switch, physical links might not come up if you perform frequent port profile changes while a line card reboot is in progress. PR1340140

  • On an EX9251 switch, if there is a packet loop between aggregation devices because of a redundant link, one aggregation device in a dual aggregation device setup might reboot if you clear the DHCP relay bindings. You must remove the redundant link to prevent such a reboot. PR1347507

  • On EX2300-48MP, EX2300-48T and EX2300-48P platforms, the show virtual-chassis command might not display the model name. PR1362421

  • The show interface ge-x/x/x command indicates "Duplex: Half-duplex" when link-mode is set to automatic or is not set. This is a display issue and it works as auto. PR1364659

  • The multicast router advertisement packets coming on a VLAN need to be flooded on the ports of all FPCs belonging to the same VLAN. Packets traversing through HighGig ports need to hit the h/w filter to transmit packets to other FPCs. In issue state, filter is not applicable for highgig ports, so multicast RA packets are not traversing other FPCs. PR1370329

Infrastructure

  • The request system zeroize command will result in the device going for a continuous reboot in non-FIPS mode. The restoration is to halt the boot sequence at the loader and install the media-net package through TFTP. PR1337826

  • On EX2300, EX2300-C, and EX2300-MP platforms, if Junos OS is with FreeBSD kernel version 11 with the build date on or after 2019-02-12, the switch might stop forwarding traffic or responding to console. A reboot is required to restore the service. PR1442376

Layer 2 Features

  • No error or warning is displayed when you commit association of IRB interfaces with VLAN using set vlans VLAN150 l3-interface irb.X without configuring the actual IRB interface using set interfaces irb unit X. PR1359982

  • The eswd[1200]: ESWD_MAC_SMAC_BRIDGE_MAC_IDENTICAL: Bridge Address Add: XX:XX:db:2b:26:81 SMAC is equal to bridge mac hence don't learn message is seen in syslog every few minutes on the ERPS owner. Because the log is caused by ERPS PDU in ERPS setup, you can ignore the message. PR1372422

Platform and Infrastructure

  • On EX4300, MACsec might not work properly on PHY84756 1G SFP ports, if AN is on and MACsec is configured on those ports. On the EX4300 device, all four uplink ports (PIC 2) are attached to PHY84756. On EX4300 fiber box, the last four ports of base board (PIC 0) and 8*1G/10G uplink ports (PIC 2) are attached to PHY84756. PR1291724

  • On EX4300 switches, the filter-based forwarding (FBF) might not work properly after deactivating or activating. This issue occurs because stale entries are not being freed in ternary content addressable memory (TCAM), which leads to insufficient space in TCAM for processing filters. PR1293581

Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 18.1R3

General Routing

  • On EX2300 and EX3400 switches, the bridge-id is assigned to "02:00:00:00:00:10" irrespective of the base-mac addresses. PR1315633

  • The MAC movement within a VLAN is not working as expected when setting up 802.1X for multiple supplicant mode. PR1329654

  • After the EX9200 FPC comes online, other FPCs might have 100 percent CPU usage and a traffic loss for up to 30 seconds. PR1346949

  • A commit error is observed if the device is downgraded from Junos OS Release 18.2 to Junos OS Release 17.3R3. PR1355542

  • On EX2300, EX3400, and EX4300MP platforms in a Virtual Chassis setup, dynamic ARP inspection might fail after a Virtual Chassis switchover when VSTP is enabled along with no-mac-table-binding. PR1359753

  • On EX2300, EX3400, EX4300-MP and EX2300-MP platforms used as a transit switch, routed traffic sent out of IRB interface, uses old MAC address instead of the configured MAC address for the IRB. PR1359816

  • On EX2300MP platforms, the fan count is wrong in jnxFruName, jnxFilledDescr and jnxContainersCount. PR1361025

  • On EX4300-48MP, the dot1x protocol subsystem is taking long time to respond to management requests with the error the dot1x-protocol subsystem is not responding to management requests. PR1361398

  • A nonexistent fan tray 1 is reported by chassisd on EX2300. PR1361696

  • A unicast ARP packet loop might be observed in DAI scenario. PR1370607

  • Port access list group is not properly reallocating TCAM slices. PR1375022

  • On EX4300-48MP, the Syslog error Error in bcm_port_sample_rate_set(ifl_cmd) : Reason Invalid port is seen. PR1376504

EVPN

  • The proxy ARP might not work as expected in an EVPN environment. PR1368911

Infrastructure

  • EX4300 firewall rule ip-options used with commands other than "any" does not provide expected results. PR1173347

  • Unable to provide management when em0 interface of FPC is connected to another FPC Layer 2 interface of the same Virtual Chassis. PR1299385

  • The upgrade might fail if bad blocks occurs in the flash memory device or file system. PR1317628

  • Need support for archiving dmesg file /var/run/dmesg.boot*. PR1327021

  • Core file is generated upon attempt to commit configuration. PR1376362

Layer 2 Features

  • The dcpfe or fxpc process might crash on Packet Forwarding Engines with low memory when allocating huge memory. PR1362332

Network Management and Monitoring

  • While toggling multiple times between baseline and CFM configs, all 30 CFM sessions are not up. PR1360907

Platform and Infrastructure

  • The mismatch of VLAN ID between a logical interface and a VLAN configuration might result in traffic being silently discarded. PR1259310

  • EX4300 crashes when it receives more than 120 KPPS ARPs on me0 interface. PR1329430

  • The SNMP trap message are always sent out with log about Fan/Blower OK on EX4300-VC switch. PR1329507

  • The show spanning-tree statistics bridge command output gives 0 for all VLAN instance IDs. PR1337891

  • On MPC5, the inline-ka PPP echo requests are not transmitted when anchor-point is lt-x/2/x or lt-x/3/x in a pseudowire deployment. PR1345727

  • Running RSI through the console port might cause the system to crash and reboot. PR1349332

  • A high usage chassis alarm in /var does not clear from the EX4300 Virtual Chassis when a file is copied from fpc1 (master) to fpc0 (backup). PR1354007

  • The ports using an SFP-T transceiver might be still up after a system halt. PR1354857

  • The FPC would crash due to the memory leak caused by the VTEP traffic. PR1356279

  • Some interfaces cannot be added under the STP configuration. PR1363625

  • On EX4300 and EX4600 platforms, the l2ald process might crash in a dot1x scenario. PR1363964

  • The Packet Forwarding Engine might crash on encountering frequent MAC move. PR1367141

  • The request system zeroize command non-interactively might not erase the configuration on EX4300. PR1368452

  • NTP broadcast packets are not forwarded out on VLAN Layer 2 ports. PR1371035

  • On EX4300, lldp advertisment appears with incorrect auto-negotiation values. PR1372966

Resolved Issues: 18.1R2

General Routing

  • The hawkeye alarmd transient error is observed on MX240, MX480, MX960, EX9200, and SRX5000 platforms. PR1312336

  • On an EX3400 switch, MACsec is not supported on 10G uplink ports. PR1325545

  • Traffic going through the aggregated Ethernet interface might be dropped if mastership changes. PR1327578

  • The EX3400 switch floods unicast ARP replies in the VLAN when dynamic ARP inspection is enabled. PR1331928

  • On an EX9200 switch, when an anchor FPC has no active child, bridge protocol data units (BPDUs) are not sent out to the other active child. PR1333872

  • All the DHCP-Reply or DCHP-Offer packets might be discarded by the DHCP snooping if the DHCP snooping is not enabled in that VLAN. PR1345426

  • On an EX2300 running Junos OS Release15.1X53-D56 with the fxpc process, issuing the accept-source-mac command causes the CPU usage to spike up to 90 percent on an idle chassis. PR1345978

  • The statistics PFED process might generate a core file on an upgrade between certain releases. PR1346925

  • Starting in Junos OS Release 18.1R2, there is support for OPSFv3 authentication on EX Series switches.PR1347630

  • Different behavior on the tagging of interfaces before and after reboot without any change in configuration. PR1349712

  • On EX2300 and EX3400 switches, the lacp mac re-write protocol sends duplicate Link Aggregation Control Protocol (LACP), bridge protocol data unit (BPDU) with different destination MAC addresses. PR1350329

  • After an EX2300 switch reboots, if you have ECMP next hop configured, the ECMP group might only be created on one Packet Forwarding Engine. PR1351418

Forwarding and Sampling

  • After an EX9251 switch is set to factory default by zeroize, the DHCP service crashes.PR1329682

Infrastructure

  • EX4300 firewall rule ip-options with knobs other than "any" doesn't provide expected results. PR1173347

  • On an EX4600 switch, priority-based flow control (PFC) frames might not work. PR1322439

  • The interface LED status might stay green even after disabling the interface and removing the cable. PR1329903

Interfaces and Chassis

  • Some PoE devices might not receive PoE power from EX2300 or EX3400 switches due to a false report of Underload Latch.PR1345234

  • On EX4600, the MC-lag after reboot of VRRP Master and Back up discards traffic to downstream switches. PR1345316

Platform and Infrastructure

  • On the EX4300 Virtual Chassis switch , the FPC might crash and a PFEX core file might get generated. PR1261852

  • Multicast receiver connected to the EX4300 switch might not be able to get the multicast streaming. PR1308269

  • Autonegotiation is not working as expected between EX4300 and SRX5800. PR1311458

  • IGMPv3 on EX4300 does not have the correct outgoing interfaces in the Packet Forwarding Engine that are listed in the kernel. PR1317141

  • On an EX4300 platform, a MAC learning issue and new VLANs creation failure might occur for some VLANs. PR1325816

  • On an EX4300 platform, when exhausting TCAM, the table filter is still programmed.PR1330148

  • Internet Group Management Protocol (IGMP) packets are forwarded out of the redundant trunk group (RTG) backup interface. PR1335733

  • MSTP might not work normally after permitting a commit. PR1342900

  • On EX4300, the loopback filter is not blocking unauthorized BGP peers. PR1343402

  • The firewall filter might not be programmed in the Packet Forwarding Engine even though TCAM entries are available. PR1345296

  • The VLAN translation feature does not work for the control plane traffic. PR1348094

  • Traffic drop might occur if LLC packets are sent with DSAP and SSAP as 0x88 and 0x8e. PR1348618

Routing Protocols

  • Open Shortest Path First (OSFP) routes cannot be added to the routing table until the lsa-refresh timer expires. PR1316348

  • The igmp-snooping protocol might be enabled unexpectedly. PR1327048

Resolved Issues: 18.1R1

Authentication and Access Control

  • The LLDP-MED cannot forward the correct POE class. PR1296547

  • The dot1x process might stop authenticating if continuous dot1x client reauthentication requests cannot get processed. PR1300050

  • EX2300-C is missing the dot1xd_usr_authenticated help string. PR1311465

EVPN

  • Split horizon label is not allocated after switching the configuration of ESI from 'single-active' to 'all-active'. PR1307056

Infrastructure

  • Reboot logs are not shown on the mini-USB console even though set system ports auxiliary port-type mini-usb is configured. PR1192388

  • The file system might be corrupted multiple times during image upgrade or commit operation. PR1317250

  • PFC feature might not work on EX4600. PR1322439

  • The ifinfo might generate core files on the EX4600 Virtual Chassis. PR1324326

Interfaces and Chassis

  • On EX2300 and EX3400 IPV6 neighborship is not created on the IRB interface. PR1198482

  • On the EX4300 Virtual Chassis: LACP flap is observed, after rebooting the master FPC with PDT configurations. PR1301338

  • The interface might not work properly after the FPC restarts. PR1329896

MPLS

  • QFX5100 and EX4600: Unified ISSU is not supported with MPLS configuration. PR1264786

Platform and Infrastructure

  • After access is rejected, the dot1x process might crash due to memory leak. PR1160059

  • On EX3400 and EX2300, LLDP, LACP, and MVRP protocols are not available under the mac-rewrite configuration. PR1189353

  • The I2C log error message is printed. PR1251604

  • EX3400 Virtual Chassis has tail drops on multicast queues due to incorrect shared buffer programming. PR1269326

  • Traffic loss might be observed for about 10 seconds if the master member FPC reboots. PR1283702

  • Doing load replace terminal and attempting to replace the interface stanza might terminate the current CLI session and leave the user session hanging. PR1293587

  • Some packets might be dropped after GRE encapsulation on EX4300. PR1293787

  • Syslogs contain messages with %PFE-3: fpc0 ifd null, port 28 dc-pfe: %USER-3: ifd null, port 28 : %PFE-3: fpc0 ifd null, port 29 dc-pfe: %USER-3: ifd null, port 29. PR1295711

  • Eswd core file might be observed if apply-groups is configured under interface-range. PR1300709

  • On EX4300 switches, when unknown unicast ICMP packets are received by an interface, packets are routed, so TTL is decremented. PR1302070

  • Unknown IPv6 multicast traffic are dropped if mld-snooping is enabled. PR1304345

  • The show snmp mib walk CLI command used for jnxMIMstMstiPortState does not display anything in Junos OS Release 17.1R2 on the EX4600 platform. PR1305281

  • On EX2300 and EX3400 Virtual Chassis or standalone chassis, IP routing fails for destination routes (IPv4 or IPv6 routes) with prefix length of 32 or 128 when they point to ECMP nexthops. PR1305462

  • Inconsistent IEEE P-bit marking occurs in 802.1Q header for OSPF packets. PR1306750

  • The me0 link might stay up after the link is disabled. PR1307085

  • Multicast receiver connected to EX4300 might not be able to get the multicast streaming. PR1308269

  • Multicast receiver connected to EX4300 might not be able to receive the multicast streaming. PR1308269

  • VLAN rewrite is not working on aggregated Ethernet interface for EX2300/3400. PR1309998

  • Traceroute is not working in EX9200 device for routing instances running on Junos OS Release 17.1R3. PR1310615

  • Traffic loss is observed while performing NSSU. PR1311977

  • IGMP snooping might not learn multicast router interface dynamically. PR1312128

  • The DHCP security binding table might not get updated. PR1312670

  • The PoE-enabled port does not come up after reboot of the line card member in EX3400 Virtual Chassis. PR1312983

  • A memory leak is seen for dot1xd. PR1313578

  • The interface with 1G SFP might go down if no-auto-negotiation is configured. PR1315668

  • Policer does not work for 224.0.0.X MC traffic to the kernel on EX4300s. PR1313251

  • On EX2300 and EX3400 switches, access ports might incorrectly send VLAN-tagged traffic. PR1315206

  • Need to replace the show vlans evpn command with the show ethernet-switching evpn command for EX92xx and QFX Series switches. PR1316272

  • Image upgrade fails with the error message ERROR: Failed to add Junos-. PR1317425

  • EX2300 interface statistics shows an incorrect bits-per-second (bps) value when the interface has line-rate traffic at 10 Gbps. PR1318767

  • L2cpd core files might be seen if the interface is disabled under VSTP and enabled under RSTP. PR1317908

  • A vmcore file might be seen, and the device might reboot after the ICL is changed from an aggregated Ethernet to a physical interface. PR1318929

  • High latency might be observed between the Master Routing Engine and the other FPC. PR1319795

  • EX3400 changes FAN speed frequently with Over Temperature alarm after a software upgrade. PR1320687

  • VLAN might not be processed, which leads to improper STP convergence. PR1320719

  • On the EX2300-48 platform, known unicast might be flooded if the source MAC address is on PFE1 and the destination MAC address is on PFE0. PR1321612

  • Multicast traffic might not be forwarded to one of the receivers. PR1323499

  • EX3400: MACsec not supported on 10G uplink ports. PR1325545

  • L2cpd might create a core file. PR1325917

  • EX Series switches do not send RADIUS request after modifying the interface-range configuration. PR1326442

  • Packets with the DEI bit set in the L2 header are not forwarded on the EX3400 switches. PR1326855

  • EX4600, QFX5100, and ACX5000: Major Alarm Fan & PSU Airflow direction mismatch is seen after removing the management cable. PR1327561

  • DHCP packet duplication issue is seen on EX2300/EX3400. PR1326857

  • New operational status detail command is added in show poe interface. PR1330183

  • EX3400 CPU have hog when Continuous Telnet EC command are sent on more than 75 concurrent telnet session. PR1331234

  • IP Directed broadcast traffic forwarding does not work on EX3400/EX2300 platform. Applications such as Wakeup-on-lan do not work without this support. PR1331326

  • EX3400 floods unicast ARP replies when DAI is enabled. PR1331928

  • EX2300-48T: "Base power reserved" value seen is higher than "Total power supplied" in show chassis power-budget-statistics command. PR1333032

  • Group unknown is seen on show filter hw 1 show_term_info CLI after adding tcam-group-optimization CLI. PR1333367

  • EX9200 -- Major Errors - MQSS Error code: 0x2203cb. PR1334928

  • IGMP traffic going out of RTG backup link is causing a loop. PR1335733

  • VLAN rewrite might not work properly on trunk ports. PR1336174

Routing Protocols

  • An mcsnoopd core file is seen at core @ __raise,abort,__task_quit__,task_quit,task_terminate_timer_callback,task_timer_dispatch,task_scheduler_internal (enable_slip_detector=true, no_exit=true) at ../../../../../../src/junos/lib/libjtask/base/task_scheduler.c:275.PR1305239

User Interface and Configuration

  • EX2300 Virtual Chassis committing from J-Web causes PHP process to spike high. PR1328323

Documentation Updates

This section lists the errata and changes in Junos OS Release 18.1R3 for the EX Series switches documentation.

New Simplified Documentation Architecture

  • With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make it easier for you to find information and know that you can rely on it when you find it. In the past, we organized documentation about Junos OS software features into platform-specific documents. In many cases, features are supported on multiple platforms, so you might not easily find the document you want for your platform.

    With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For example, if you want to find documentation on OSPF, there is only one document regardless of which platform you have. Here are some of the benefits of our new simplified architecture:

    • Over time, you will see better search results when looking for Juniper documentation. You will be able to find what you want faster and be assured that is the right document.

    • If a software feature is supported on multiple platforms, you can find information about all the platforms in one place.

    • Because we have eliminated many documents that covered similar topics, you will now find one document with all the information.

    • You can know that you are always getting the most current and accurate information.

Migration, Upgrade, and Downgrade Instructions

This section contains the upgrade and downgrade support policy for Junos OS for the EX Series. Upgrading or downgrading Junos OS can take several hours, depending on the size and configuration of the network. For information about software installation and upgrade, see the Installation and Upgrade Guide.

Note
  • : EX2300 or EX3400 switches running Junos OS Software Release 15.1X53-D57 or earlier revisions cannot be directly upgraded via CLI to Junos OS Software Release 18.1R1 because of configuration incompatibilities between the two releases related to the uplink port configurations. For example: Any configuration having interfaces on the uplink module (xe-0/2/*) will throw errors during the upgrade process. To work around this problem, please specify the validate option in the upgrade command to check for these errors, then remove the configuration that results in the errors, and use the no-validate option to do the upgrade.

    Alternately, an intermediate upgrade to 15.1X53-D58 can be performed by keeping the configuration intact and then a subsequent upgrade to 18.1R1 is possible.

  • NSSU is not supported on EX2300-VC/EX3400-VC from Junos OS Release 15.1X53 to Junos OS Release 18.1R1 or later releases. For example, NSSU is not supported from Junos OS Release 15.1X53-D58 to Junos OS Release 18.1R1 or Junos OS Release 15.1X53-D57 to Junos OS Release 18.2R1.

Upgrade and Downgrade Support Policy for Junos OS Releases

Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.1, 17.2 and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from Junos OS Release 17.1 to Release 17.3.

You cannot upgrade directly from a non-EEOL release to a release that is more than three releases ahead or behind. To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For more information about EEOL releases and to review a list of EEOL releases, see https://www.juniper.net/support/eol/junos.html.

Product Compatibility

Hardware Compatibility

To obtain information about the components that are supported on the devices, and the special compatibility guidelines with the release, see the Hardware Guide for the product.

To determine the features supported on EX Series switches in this release, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. Find Feature Explorer at https://pathfinder.juniper.net/feature-explorer/.

Hardware Compatibility Tool

For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms, see the Hardware Compatibility tool.