Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

New and Changed Features

This section describes the new features and enhancements to existing features in Junos OS Release 14.2R7 for Junos Fusion Provider Edge.

Junos Fusion

  • Junos Fusion support (MX Series routers, QFX5100 switches, and EX4300 switches)—Starting with Junos OS Release 14.2R3, Junos OS supports a network system named Junos Fusion. Based on the 802.1BR standard, Junos Fusion is a combination of aggregation devices and satellite devices that appear to the rest of the network as a single device. Junos Fusion expands the port density of the aggregation device and allows it to send and receive traffic using the customer-facing ports of the directly connected satellite devices. The composite of the aggregation device and satellite devices–Junos Fusion–is configured and managed through the aggregation device.

    You can configure the following MX Series routers as an aggregation device:

    • MX80 routers
    • MX104 routers
    • MX240 routers
    • MX480 routers
    • MX960 routers
    • MX2010 3D Universal Edge Routers
    • MX2020 3D Universal Edge Routers

    You can configure the following switches as satellite devices:

    • QFX5100 switches—QFX5100-24Q, QFX5100-48S, QFX5100-48T, and QFX5100-96S
    • EX4300 switches—EX4300-24P, EX4300-24T, EX4300-32F, EX4300-48P, EX4300-48T, and EX4300-48T-BF

    [See Junos Fusion Overview.]

  • Extended satellite device support (EX4300-32F switch)—Starting with Junos OS Release 14.2R5, an EX4300-32F switch can be converted for use as a satellite device in a Junos Fusion topology. You must upgrade the switch to Junos OS Release 14.1X53-D30 or later before you convert it into a satellite device; the MX Series aggregation device must run Junos OS Release 14.2R5 or later; and the satellite device package must be version 1.0R2 or later.
  • Extended aggregation device support (MX80 and MX104 routers)—Starting with Junos OS Release 14.2R6, the MX80 and MX104 3D Universal Edge Routers can be used as aggregation devices in a Junos Fusion Provider Edge topology.
  • Environment monitoring satellite policies (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion allows you to configure environment monitoring satellite policies to define how environmental events on satellite devices, such as link-down alarms, are handled in Junos Fusion. To configure an environment monitoring satellite policy, include the environment-monitoring-policy statement at the [edit policy-options satellite-policies] hierarchy level.
  • New and enhanced chassis commands (Junos Fusion)—Starting with Junos OS Release 14.2R3, several new show chassis commands are available and several existing show chassis commands have been enhanced to display output related to Junos Fusion operations. The following new commands are now available to support Junos Fusion:
    • show chassis satellite
    • show chassis satellite extended-port
    • show chassis satellite interface
    • show chassis satellite neighbor
    • show chassis satellite software
    • show chassis satellite statistics
    • show chassis satellite unprovision
    • show chassis satellite upgrade-group

    The following existing commands have been enhanced to include the satellite option to display information about a Junos Fusion topology:

    • show chassis alarms
    • show chassis environment
    • show chassis environment fpc
    • show chassis environment pem
    • show chassis environment routing-engine
    • show chassis fan
    • show chassis firmware
    • show chassis hardware
    • show chassis led
    • show chassis routing-engine
    • show chassis temperature-thresholds
  • Enhanced system commands (Junos Fusion)—Starting with Junos OS Release 14.2R3, several existing request system commands have been enhanced to support software installation and file management procedures for Junos Fusion. The following existing request system commands have been enhanced to support Junos Fusion:
    • request system software add
    • request system software delete
    • request system software rollback
    • request system storage cleanup

    Note: The request system software rollback command does not work if you reboot the aggregation device. Instead, issue the request system software add command. For more information, see the Note in the Basic Procedure for Upgrading an Aggregation Device section of the Junos Fusion Provider Edge Release Notes.

  • Additional MPC support (MX Series routers)—Starting with Junos OS Release 14.2R6, the following Modular Port Concentrators (MPCs) are supported as Junos Fusion Provider Edge cascade ports on MX240, MX480, MX960, MX2010, and MX2020 routers:
    • MPC2E NG
    • MPC2E NG Q
    • MPC3E NG
    • MPC3E NG Q

Class of Service (CoS)

  • CoS support (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion supports the standard Junos OS CoS features and operational commands. Each extended port on a satellite device is a logical extension to the aggregation device. Therefore, the default CoS policy on the aggregation device applies to each extended port. You can also create standard CoS policies for extended ports.

    A cascade port is a physical port or interface on an aggregation device that provides a connection to a satellite device. Port scheduling is supported on cascade ports. Junos Fusion technology reserves a separate set of queues with minimum bandwidth guarantees for in-band management traffic to protect against congestion caused by data traffic.

    Support for configuring enhanced transmission selection (ETS) is also extended to MX Series routers for satellite device ports that support ETS. If ETS is configured on the MX Series aggregation device for a satellite device port that does not support ETS, the satellite device converts the ETS configuration to a port scheduler.

    [See Understanding CoS on an MX Series Aggregation Device in Junos Fusion.]

Interfaces

  • Supported port types (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion supports the following port types:
    • Cascade port—Provides a connection to a satellite device. Cascade ports on an aggregation device connect to uplink ports on the satellite device.
    • Uplink port—Provides a connection to an aggregation device. Uplink ports on a satellite device connect to cascade ports on the aggregation device.
    • Extended port—Provides a connection to servers or endpoints. Extended ports are the physical interfaces of the satellite devices. The satellite devices appear as additional FPCs on the aggregation device in a Junos Fusion topology, and extended ports appear as additional interfaces to be managed by the aggregation device.

      [See Understanding Junos Fusion Ports.]

  • Uplink failure detection (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion enables satellite devices to detect link failures on the uplink interfaces used to connect to aggregation devices. When a host device is multihomed to two satellite devices, and one of the uplink interfaces goes down, the host device can redirect traffic through the other active satellite device. All of the extended ports configured on the satellite device with the uplink interface failure are shut down.

    By default, UFD is disabled. To enable UFD for all satellite devices, include the uplink-failure-detection statement at the [edit chassis satellite-management] hierarchy level. To enable UFD for specific satellite devices, include the uplink-failure-detection statement at the [edit chassis satellite-management fpc] hierarchy level.

    EX4300 and QFX5100 switches configured as satellite devices have a default set of uplink interfaces.Table 1 shows the default set of uplink interfaces that UFD selects for failure detection.

    Table 1: UFD Default Uplink Interfaces for Satellite Devices

    Device Type

    Default Uplink Interfaces

    EX4300-24P (4 ports each on PIC1 and PIC2)

    1/0 through 1/3 and 2/0 through 2/3

    EX4300-24T (4 ports each on PIC1 and PIC2)

    1/0 through 1/3 and 2/0 through 2/3

    EX4300-32F (Miscellaneous ports on PIC0, PIC1, and PIC2)

    0/32 through 0/35, 1/0 through 1/1, and 2/0 through 2/7

    EX4300-48P (4 ports each on PIC1 and PIC2)

    1/0 through 1/3 and 2/0 through 2/3

    EX4300-48T (4 ports each on PIC1 and PIC2)

    1/0 through 1/3 and 2/0 through 2/3

    EX4300-48T-BF (4 ports each on PIC1 and PIC2)

    1/0 through 1/3 and 2/0 through 2/3

    QFX5100-24Q

    0/20 through 0/23

    QFX5100-48S (6 QSFP+ ports)

    0/48 through 0/53

    QFX5100-48T (6 QSFP+ ports)

    0/48 through 0/53

    QFX5100-96S (8 QSFP+ ports)

    0/96 through 0/103

    If you choose not to use the default set of uplinks for your satellite devices, you need to specify which uplink interfaces you want to use for UFD. To apply UFD to an uplink interface, include the ufd-default-policy statement at the [edit chassis satellite-management uplink-failure-detection] hierarchy level. You also need to configure the UFD policy. For example:

    [edit policy-options]
    satellite-policy {candidate-uplink-port-profile {ufd-default-policy {term qfx5100 {product-model QFX5100*;uplink-port-group uplink-ports;}}}port-group-alias {uplink-ports {pic 0 {port [1, 2];}pic 1 {port [3,4];}}}}

    [See Overview of Uplink Failure Detection on a Junos Fusion.]

  • Increasing number of aggregated Ethernet interfaces to approximately 1000 (Junos Fusion)—Starting with Junos OS Release 14.2R3, aggregation devices support up to 1000 aggregated Ethernet interfaces, depending on the number satellite devices included in a Junos Fusion topology.
  • LACP support (Junos Fusion)—Starting with Junos OS Release 14.2R3, LACP is supported on Junos Fusion. It provides the ability to bundle several physical interfaces to form one logical aggregated Ethernet interface. The LACP mode can be active or passive. The transmitting link is known as the actor, and the receiving link is known as the partner. If the actor and partner are both in passive mode, they do not exchange LACP packets, and the aggregated Ethernet links do not come up. If either the actor or partner is active, they do exchange LACP packets. By default, LACP is in passive mode on aggregated Ethernet interfaces. To initiate transmission of LACP packets and response to LACP packets, you must enable LACP active mode.

    You can configure Ethernet links to actively transmit PDUs, or you can configure the links to passively transmit them, sending out LACP PDUs only when they receive them from another link.

    [See Understanding Link Aggregation and Link Aggregation Control Protocol in a Junos Fusion.]

  • MC-LAG support (Junos Fusion)—Starting with Junos OS Release 14.2R3, you can configure MC-LAG between two aggregation devices in a Junos Fusion topology.

    You can also configure MC-LAG interfaces to improve the Layer 2 and Layer 3 convergence time when a MC-LAG Ethernet link goes down or comes up. To configure enhanced convergence, issue the enhanced-convergence statement at the [edit interfaces ae aggregated-ether-options mc-ae] hierarchy level for an aggregated Ethernet interface and at the [edit interfaces irb unit unit-number] hierarchy level for an IRB interface.

    [See Understanding Multichassis Link Aggregation in a Junos Fusion.]

    Note: EVPN cannot be configured simultaneously with MC-LAG.

  • Configuration synchronization for MC-LAG (Junos Fusion)—Starting with Junos OS Release 14.2R6, Junos Fusion supports the ability to easily propagate, synchronize, and commit configurations from one MC-LAG peer to another MC-LAG peer. MC-LAG configuration synchronization enables you log into any one of the MC-LAG peers to manage both MC-LAG peers, thus having a single point of management. With MC-LAG configuration synchronization, you can use configuration groups to simplify the configuration process. For example, you can create configuration groups for the local MC-LAG peers, one for the remote MC-LAG peer, and one for the global configuration, which is essentially a configuration that is common to both MC-LAG peers. You can create conditional groups to specify when a configuration is synchronized with another MC-LAG peer. Additionally, you can enable the peers-synchronize command at the [edit system commit] hierarchy level to synchronize the configurations and commits across the MC-LAG peers by default. NETCONF over SSH provides a secure connection between the MC-LAG peers, and Secure Copy Protocol (SCP) copies the configurations securely between the MC-LAG peers.
  • Enhanced interface commands (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion provides information for extended ports and uplink ports on satellite devices through operational mode commands and output. Extended port names include the extended FPC slot number, PIC slot, and port number. For example, a 10-Gigabit Ethernet extended port number might be xe-125/1/8, where 125 is the FPC slot number, 1 is the physical interface card (PIC) slot, and 8 is the extended port number.

    The following commands have been enhanced to display the extended ports and uplink ports by using either the slot or the alias. Additionally, you can now use the keyword satellite to view information about the satellite device ports:

    • show interfaces satellite-device (all | alias)
    • show interfaces extensive satellite-device (all | alias)
    • show interfaces terse satellite-device (all | alias)

Layer 2 Protocols

  • RSTP configuration supports 1024 VLAN instances on extended ports for MX Series platforms (Junos Fusion)—Starting with Junos OS Release 14.2R4, Junos Fusion supports up to 1024 VLAN instances for the Rapid Spanning Tree Protocol (RSTP) on MX Series platforms for improved scalability. Typically each VLAN corresponds with an associated spanning tree, which affects processing resources due to the number of VLANs. Increasing the number VLAN instances helps increase scalability across the MX Series platform.

Layer 3 Protocols

  • Support for Layer 3 protocols (Junos Fusion)—Starting with Junos OS Release 14.2R4, many of the routing protocols supported on MX Series routers have been extended to the satellite devices in a Junos Fusion topology. You can configure the following Layer 3 routing protocols on satellite device extended ports:
    • BGP
    • BGP for IPv6
    • IS-IS
    • IS-IS for IPv6
    • OSPF
    • OSPF version 3

    You can configure the following Layer 3 routing protocols on satellite device extended ports that are included in LAGs and MC-LAGs:

    • BGP
    • IS-IS
    • OSPF

    [See Junos Fusion Protocol Support.]

Multicast Protocols

  • Support for multicast protocols (Junos Fusion)—Starting with Junos OS Release 14.2R4, many of the multicast protocols supported on MX Series routers have been extended to the satellite devices in a Junos Fusion topology. You can configure the following multicast protocols on satellite device extended ports:
    • IGMP
    • MLD
    • PIM source-specific multicast (SSM)
    • PIM sparse mode

    [See Junos Fusion Protocol Support.]

Network Management and Monitoring

  • Chassis MIB support (Junos Fusion)—Starting with Junos OS Release 14.2R3, satellite devices in a Junos Fusion topology are represented in the chassis MIB. Satellite devices are represented as FPC slots (100, 101, 102, ...) in the aggregation device. The support is enabled using a range of container indexes, which enable the SNMP process to redirect SNMP requests to the chassis process or SPMD based on the first index entry.

    The following tables have been implemented for satellite devices:

    • jnxContainersTable
    • jnxContentsTable
    • jnxFilledTable
    • jnxOperatingTable
    • jnxFRUTable

    These tables have an index consisting of four entries–CIDX, L1, L2, and L3–where CIDX is the container index, L1 is the level-1 index (slot), L2 is the level-2 index (component within the L1 slot), and L3 is the level-3 index (subcomponent of the L2 slot). For example, an entry of 104.101.2.0 would indicate CIDX 104 is the index for fans and refers to the second fan of satellite device 100 (all indexes are 1-based). The CIDX indexes for Junos Fusion are offset by 100 from regular indexes; for example, a regular CIDX 2 (power supply) is 102 for the power supply of the satellite device. Using these indexes, you can distinguish the satellite device hardware from the aggregation device hardware.

    [See Chassis MIB Support (Junos Fusion).]

  • Satellite device system log messages (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion generates system log messages for the following major events on satellite devices:
    • Satellite device discovery
    • Satellite device offline
    • Satellite device software upgrade success or failure
    • Satellite device extended port up/down
    • Satellite device extended port addition/deletion failures
    • Satellite device extended port link down alarms raised/cleared
    • Satellite device power supply addition/removal
    • Satellite device fan addition/removal
    • Satellite device chassis alarms raised/cleared
    • Satellite device converted to a standalone switch (Junos OS)
    • Standalone switch (Junos OS) converted to a satellite device

Software Installation and Upgrade

  • Upgrading and managing the satellite software on satellite devices (Junos Fusion)—Starting with Junos OS Release 14.2R3, Junos Fusion provides the ability to manage satellite software. To convert a standalone switch to a satellite device, you can use one of the following methods:
    • Autoconversion—Automatically converts a standalone device into a satellite device when it is cabled to a cascade port on the aggregation device.
    • Manual conversion—Installs satellite software manually from the aggregation device using the request chassis satellite interface interface-name device-mode satellite command.
    • Preconversion—Installs satellite software onto a device before connecting it to a Junos Fusion topology.

    After you convert the switch to a satellite device, you can install satellite software upgrades onto a satellite device through the aggregation device.

    Satellite software upgrade groups are often needed to install satellite software. A satellite software upgrade group is a group of satellite devices that are designated to upgrade to the same satellite software version using the same satellite software package. When you add a satellite to an upgrade group that is not running the same satellite software, the satellite device is automatically updated to the version of satellite software associated with the upgrade group.

    You can use the following commands to add and associate a satellite software version with an upgrade group:

    • request system software add upgrade-group upgrade-group-name—Add the satellite software and associate it with the specified upgrade group.
    • request system software delete upgrade-group upgrade-group-name—Remove the satellite software association from the specified upgrade group.
    • request system software rollback upgrade-group upgrade-group-name—Associate an upgrade group with a previous version of satellite software.

    You can issue the show chassis satellite software command to see which software images are stored on the aggregation device and which upgrade groups are associated with the software images.

    [See Understanding Junos Fusion Components, Understanding Software in a Junos Fusion, and Configuring Junos Fusion.]

System Logging

  • System log messages to indicate checksum errors on the DDR3 interface—Starting with Junos OS Release 14.2R7, two new system log messages, XMCHIP_CMERROR_DDRIF_INT_REG_CHKSUM_ERR_MINOR and XMCHIP_CMERROR_DDRIF_INT_REG_CHKSUM_ERR_MAJOR, are added to indicate memory-related problems on the interfaces to the double data rate type 3 (DDR3) memory. These error messages indicate that an FPC has detected a checksum error, which is causing packet drops.

    The following error threshold values classify the error as a major error or a minor error:

    • Minor error— 6 to 254 errors per second
    • Major error—255 or more errors per second

VPNs

  • Support for VPNs (Junos Fusion)—Starting with Junos OS Release 14.2R4, many of the VPN protocols supported on MX Series routers have been extended to the satellite devices in a Junos Fusion topology. You can configure satellite device extended ports as CE router interfaces for the following VPNs:
    • Layer 2 circuits
    • Layer 2 VPNs
    • Layer 3 VPNs
    • Logical routers
    • Virtual private LAN service (VPLS)

    [See Junos Fusion Protocol Support.]

  • EVPN and VXLAN support (Junos Fusion)—Starting with Junos OS Release 14.2R6, Junos Fusion extends the use of EVPN with VXLAN encapsulation to satellite devices managed by MX Series routers. This feature provides Layer 2 connectivity for end stations within a virtualized network. The end stations consist of virtual hosts connected to the virtualized server, and nonvirtualized bare-metal servers connected to top-of-rack switches. The MX Series routers also function as default gateways for the internetwork traffic among end stations that belong to different virtual networks.

    Note: MC-LAG cannot be configured simultaneously with EVPN.

Related Documentation

Modified: 2017-02-20