Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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 Junos Fusion Data Center.

Release 17.2R2 New and Changed Features

There are no new features or enhancements to existing features for Junos Fusion Data Center in Junos OS Release 17.2R2.

Release 17.2R1 New and Changes Features

Junos Fusion Data Center

  • Junos Fusion Data Center support (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center support is available and brings the Junos Fusion technology to data center networks. Junos Fusion Data Center uses QFX10000 switches in the aggregation device role and allows data center networks to combine numerous switches into a single, port-dense system. The system is managed from a single point (the aggregation devices) and simplifies network topologies because Junos Fusion Data Center is viewed as a single device by the larger network. Junos Fusion Data Center supports the 802.1BR standard.

    You can configure the following QFX10000 Series switches as an aggregation device in a Junos Fusion Data Center:

    • QFX10002 switches

    You can configure the following switches as satellite devices:

    • QFX5100 switches—QFX5100-24Q-2P, QFX5100-48S-6Q, QFX5100-48SH-6Q, QFX5100-48T-6Q, QFX5100-48TH-6Q, and QFX5100-96S-8Q

    • EX4300 switches—EX4300-24T, EX4300-32F, EX4300-48T, and EX4300-48T-BF

    [See Junos Fusion Data Center Overview.]

  • Dual aggregation devices (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, you can have two aggregation devices in a Junos Fusion Data Center topology to support dual homing from satellite devices.

    To configure a dual aggregation device topology, specify a chassis, redundancy group name and ID, peer chassis ID, and interchassis link interface in a redundancy group. All other ICCP parameters are automatically configured as part of the automatic ICCP provisioning of an interchassis link feature, which is enabled by default.

    [See Configuring the Dual Aggregation Device Topology.]

Hardware

  • New satellite device models (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, the new QFX5100-48SH and QFX5100-TH switch models ship from the factory with preinstalled satellite software, allowing you to deploy them in a Junos Fusion Data Center in a plug-and-play manner.

    [See QFX5100 Switch Hardware Guide.]

Class of Service (CoS)

  • Class of service support (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center supports the standard Junos class of service (CoS) features and operational commands in either a single or dual aggregation device configuration. 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.

    [See Understanding CoS in Junos Fusion Data Center.]

High Availability (HA) and Resiliency

  • Support for Virtual Routing Redundancy Protocol (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center supports the Virtual Routing Redundancy Protocol (VRRP). You can configure VRRP on dual aggregation devices to provide a common gateway for the hosts connected to the satellite devices and to provide dynamic switchover from one aggregation device to another in the event of failure. Both aggregation devices share the virtual IP address and route upstream packets independently. For protocol control, one of the aggregation devices is elected as the master and the other is placed in the backup role. To configure basic VRRP support, configure VRRP groups on the aggregated interfaces by including the vrrp-group statement at the [edit interfaces interface-name unit logical-unit-number family inet address ip-address] hierarchy level.

    [See Understanding VRRP.]

Interfaces

  • LACP support (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, LACP is supported on Junos Fusion Data Center. 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

    LACP is supported in single and dual aggregation device topologies.

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

  • Increased number of aggregated Ethernet interfaces (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, you can configure up to 1000 aggregated Ethernet interfaces for a Junos Fusion Data Center system. To configure, include the device-count statement with a value of 1000 at the [edit chassis aggregated-devices ethernet] hierarchy level and add member links in each bundle.

  • Automatic ICCP provisioning of an interchassis link in a Junos Fusion (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, automatic ICCP provisioning of an interchassis link (ICL) simplifies configuration of a Junos Fusion with dual aggregation devices by automatically provisioning the ICCP configuration within the Junos Fusion, instead of requiring the user to manually configure all ICCP parameters.

    The configuration of the redundancy group in a Junos Fusion using dual aggregation devices still requires that you specify a chassis, redundancy group name and ID, peer chassis ID, and interchassis link interface as part of the configuration process. All other redundancy group parameters are now automatically set to default values that do not have to be user-configured for a dual aggregation device topology to operate.

    Automatic ICCP provisioning is enabled by default. If a user configures a redundancy group parameter that is set by default normally, the user configuration automatically overrides the default parameter. Automatic ICCP provisioning can be disabled by entering the no-auto-iccp-provisioning statement at the [edit chassis satellite-management redundancy-groups redundancy-group-name peer-chassis-id peer-chassis-id-number] hierarchy level.

    [See Understanding Automatic ICCP Provisioning and Automatic VLAN Provisioning of an Interchassis Link.]

    Automatic VLAN provisioning on an interchassis link in a Junos Fusion (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, automatic VLAN provisioning of an interchassis link (ICL) simplifies configuration of a Junos Fusion with dual aggregation devices by allowing the ICL interconnecting the dual aggregation devices to automatically detect all VLAN traffic on the Junos Fusion and seamlessly forward VLAN information between the aggregation devices over the ICL.

    When automatic VLAN provisioning is disabled, you have to manually configure the supported VLANs on each ICL to ensure VLAN information is shared between aggregation devices.

    Automatic VLAN Provisioning is enabled by default in a Junos Fusion Data Center, and can be disabled using the set chassis satellite-management redundancy-groups redundancy-group-name peer-chassis-id peer-chassis-id-number no-auto-vlan-provisioning statement.

    Automatic VLAN Provisioning only works when the ICL is in trunk mode, and when the ICL interfaces are configured into unit 0 family ethernet-switching.

    [See Understanding Automatic ICCP Provisioning and Automatic VLAN Provisioning of an Interchassis Link.]

  • Configuration synchronization for MC-LAG (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, 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 include the peers-synchronize statement 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.

  • Uplink port pinning (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, uplink port pinning allows traffic entering an extended port on a Junos Fusion Data Center to select which uplink port or ports are used to carry the traffic from the satellite device to the aggregation device. Uplink port pinning provides more deterministic traffic control by allowing you to select how traffic is forwarded from an extended port to an aggregation device.

    When uplink port pinning is not enabled, traffic is forwarded from the satellite device to the aggregation device using all available uplink ports.

    Uplink port pinning is configured in the following steps:

    1. Create a forwarding policy in a satellite policy that includes an uplink port group by using the port-group-extended and port-group-uplink statements.

    2. Associate the uplink port group with an extended port by configuring a port group alias with the port-group-alias statement.

    3. Associate the forwarding policy with the Junos Fusion configuration using the forwarding-policy statement at the [edit chassis satellite-management] hierarchy level.

    [See Understanding Remapping Uplink Traffic Flows on a Junos Fusion Data Center.]

  • Uplink failure detection (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, 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-24T (4 ports each on PIC1 and PIC2)

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

    EX4300-32F

    PIC 0 ports 32-35

    PIC 1 ports 0-1

    PIC 2 ports 0-7

    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-2P

    PIC 0 ports 20-23

    QFX5100-48S-6Q or QFX5100-48SH-6Q (6 QSFP+ ports)

    0/48 through 0/53

    QFX5100-48T-6Q or QFX5100-48TH-6Q (6 QSFP+ ports)

    0/48 through 0/53

    QFX5100-96S-8Q (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:

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

  • Supported port types (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center 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.

    • ICL port—Provides a connection between aggregation devices to support a dual-homed topology. ICL interfaces must be configured.

    [See Understanding Junos Fusion Ports.]

  • Enhanced interface commands (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center 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

  • Local switching on satellite devices (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, you can enable local Layer 2 switching at the satellite device level. In local switching mode, all bridging traffic for which the source and destination port are local to a satellite device is forwarded by that satellite device based on the destination MAC address. Each satellite device maintains only the local destination MAC addresses that are directly connected to the device in the bridge forwarding table. Any unknown MAC address on the satellite device is forwarded to the aggregation device for forwarding. To configure a satellite device in a Junos Fusion Data Center into local switching mode, include the local-switching statement at the [edit forwarding-options satellite fpc fpc-slot-number] hierarchy level on the aggregation device, where fpc-slot-number is the FPC slot ID of the satellite device.

    [See Configuring Local Switching on Junos Fusion Data Center.]

  • VLAN autosensing (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, VLAN autosensing allows extended ports on satellite devices to provision VLANs dynamically, as needed, to preserve the VLAN memory of the aggregation device with no or minimal impact to the forwarding of VLAN traffic in the Junos Fusion.

    You configure VLAN autosensing from the aggregation device on a per-extended port basis by including the vlan-auto-sense statement at the [edit interfaces interface-name unit logical-unit-number family ethernet-switching] hierarchy level, where interface-name is the name of the extended port interface.

    For example, to enable VLAN autosensing on extended port xe-101/0/0:

    [edit]
    user@aggregation-device# set interfaces xe-101/0/0 unit 0 family ethernet-switching vlan-auto-sense

    Configuration notes for VLAN autosensing:

    • VLAN autosensing is supported on extended ports only.

    • Only single VLAN tagged packets are autosensed.

    [See Understanding VLAN Autosensing.]

  • Loop detection on extended ports (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, you can configure a Junos Fusion Data Center system to detect and break loops of unicast traffic on downstream extended ports without configuring spanning tree protocols. Typically, the loops are caused by either miswiring or by misconfiguration. Loop detection transmits special protocol data units (PDUs) periodically, and if a PDU is received on an extended port, the loop is detected and broken. Loop detection blocks the ingress port and issues a loop detection PDU error. When a port is blocked, you need to manually bring up the interface. Loop detection only responds to detect PDUs, not BPDUs.

    [See Understanding Loop Detection and Prevention on a Junos Fusion.]

  • Link Layer Discovery Protocol (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Link Layer Discovery Protocol (LLDP) is supported in a Junos Fusion Data Center. Link Layer Discover Protocol (LLDP) allows network devices to advertise their capabilities, identity, and other information onto a LAN. In a Junos Fusion topology, the LLDP protocol running on the satellite port is used for satellite device discovery and also works as a simple hello protocol between the satellite and aggregation devices to establish a two-way adjacency and detect remote-end failures.

    [See Understanding LLDP and LLDP-MED on Junos Fusion.]

  • MAC address synchronization (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, aggregation devices synchronize MAC addresses that are learned on the extended ports.

    [See Understanding MAC Address Synchronization in a Junos Fusion.]

  • VSTP enhancements (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, VSTP is supported on a QFX10000 switch acting as a single-homed aggregation device. The VSTP configuration can include native ports or extended ports in a Junos Fusion Data Center.

  • Loop detection with BPDU guard on VSTP edge ports (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center supports bridge protocol data unit (BPDU) protection for VLAN Spanning Tree Protocol (VSTP) on extended ports in a dual aggregation device topology. You can configure an extended port as a VSTP edge interface, and configure BPDU protection on the interface using the bpdu-block-on-edge statement. The exchange of BPDUs generated by VSTP prevents loops in network traffic by determining which interfaces block traffic and which interfaces forward traffic. If a BPDU is received on an edge interface with BPDU guard, VSTP will detect a loop and shutdown the interface. Other interfaces in the VLAN remain intact. To clear the interface for forwarding, issue the clear error bpdu interface command.

    [See bpdu-block-on-edge.]

Layer 3 Protocols

  • Support for Layer 3 protocols (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, the following routing protocols supported on QFX10000 switches have been extended to the satellite devices in a Junos Fusion Data Center topology.

    You can configure the following Layer 3 routing protocols on satellite device extended ports using a single aggregation device topology:

    • BGP

    • BGP for IPv6

    • IS-IS

    • IS-IS for IPv6

    • OSPF

    • OSPF version 3

Multicast Protocols

  • Local egress replication for VLAN flooding (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, for a Junos Fusion topology with dual aggregation devices, you can enable egress replication (local replication) using the local-replication statement at the [edit forwarding-options satellite] hierarchy level. Local replication helps distribute packet replication load and reduce traffic on cascade ports for multicast and flooded VLAN traffic. When local replication is enabled, packet replication behavior for VLAN flooding is as follows:

    • The aggregation device sends one copy of the packet to each satellite device that has extended ports in the VLAN.

    • The satellite device does replication for each local port in the VLAN.

    Use the show ethernet-switching flood satellite and show ethernet-switching flood next-hops satellite commands to view local replication information for flooded VLAN traffic.

    [See Egress Multicast Replication on the Satellite Devices.]

  • Egress replication for Layer 2 multicast with IGMP Snooping (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, egress multicast replication, also called local replication, is supported for Junos Fusion topologies featuring dual aggregation devices. You can optionally configure local replication for all satellite devices by including the local-replication statement at the [edit forwarding-options satellite] hierarchy level. For Layer 2 multicast traffic with IGMP snooping configured and local replication enabled, the aggregation device sends only one copy of the packet to each satellite device that has an extended port in the multicast group, and the satellite device does the replication for its local ports that are members of the multicast group. When local replication is not enabled, Junos Fusion defaults to ingress replication, where all replication is done on the aggregation devices and sent to corresponding satellite devices for each extended port receiving the multicast traffic.

    Use the following commands to display local replication information:

    • show ethernet-switching satellite device

    • show multicast ecid-mapping satellite

    • show multicast next-hops satellite

    • show multicast snooping next-hops satellite

    • show multicast snooping route satellite

    • show multicast statistics satellite

    • show multicast summary satellite

    Local replication is not compatible with port mirroring, VLAN ID tagging policies, and VPN configurations, and does not take effect (reverts to ingress replication behavior) for IPv6 traffic or Multicast Listener Discovery (MLD) snooping.

    [See Egress Multicast Replication on the Satellite Devices.]

  • Egress replication for Layer 3 multicast IRB interface traffic (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, for a Junos Fusion topology with dual aggregation devices, you can enable egress multicast replication (also called local replication) using the local-replication statement at the [edit forwarding-options satellite] hierarchy level. Local replication helps distribute multicast packet replication load and reduce traffic on cascade ports, including for Layer 3 multicast traffic being routed between VLANs on IRB interfaces. When local replication is enabled, Layer 3 multicast packet replication behavior is as follows:

    • The aggregation device replicates the data for each IRB interface in the multicast group, and sends copies to each satellite device with member ports—one copy for each VLAN where the satellite device has destination extended ports in the VLAN.

    • Each receiving satellite device replicates the data for its local extended ports in the multicast group for each VLAN.

    Local replication is not compatible with interfaces that use VLAN ID tagging policies that add processing overhead to forward egress traffic.

    [See Egress Multicast Replication on the Satellite Devices.]

  • Multicast convergence improvements using enhanced PIM dual designated router mode for dual aggregation devices (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, enhanced PIM dual designated router mode is supported to improve multicast convergence time on a Junos Fusion with dual aggregation devices in the event of designated router (DR) failure and recovery. You can optionally enable this feature by including the dual-dr enhanced statement at the [edit protocols pim interface interface-name] hierarchy level. With enhanced PIM dual designated router mode enabled, although only one aggregation device is the primary device actively forwarding multicast traffic, both devices join the multicast tree and receive multicast data. As a result, if the primary aggregation device fails, the other aggregation device quickly takes over multicast replication and forwarding. You can enable this feature with egress multicast replication (local replication).

    [See Understanding Multicast Convergence Enhancements for Dual Aggregation Devices in a Junos Fusion.]

  • Support for multicast protocols (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, many of the multicast protocols supported on QFX10000 switches 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

Network Management and Monitoring

  • Local port mirroring (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center supports local port mirroring. 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 local port mirroring to troubleshoot and monitor applications. You can mirror packets per port, and you can configure the source and mirror ports on the same satellite device.

    [See Understanding Remapping Uplink Traffic Flows on a Junos Fusion Data Center.]

  • Analyzers on extended ports (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, you can use port mirroring (analyzers) on extended ports on satellite devices in a Junos Fusion Data Center. Extended-port port mirroring copies packets entering or exiting a port or entering a VLAN and sends the copies to a VLAN for remote monitoring. 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, correlating events, and so on. When a port is ingress-mirrored, any packet received on that port is mirrored to the user-configured destination. When a port is egress-mirrored, any packet transmitted from that port is mirrored to your configured port-mirroring destination.

    In Junos Fusion Data Center, you can use analyzers on extended ports for these purposes:

    • Mirror aggregation device ports to extended ports

    • Mirror extended ports to extended ports

    • Mirror extended ports to aggregation device ports

    [See Understanding Port Mirroring on a Junos Fusion Data Center.]

  • Junos Space Service Now (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, Junos Fusion Data Center uses Service Now for failure event reporting. Service Now is an application that runs on the Junos Space Network Management Platform to automate fault management and accelerate issue resolution.

    [See Junos Space Service Now User Guide.]

  • Chassis MIB support (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, 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

    alpha 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.

    Chassis MIB support is available in single and dual aggregation device topologies.

    [See Chassis MIB Support (Junos Fusion).]

Routing Policy and Firewall Filters

  • Flow-based uplink selection (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1 on Junos Fusion Data Center, you can configure flow-based uplink selection for satellite devices to achieve better utilization of network resources. To remap specified elephant flows from satellite devices to aggregation devices, you program remapping on all or specific satellite devices to override the default 5-tuple hashing and then distribute those specified flows across uplinks toward aggregation devices. You define specific flows by using flow-based firewall filters statements, and those flows are sent to the uplink port or ports that you define.

    [See Understanding Remapping Uplink Traffic Flows on a Junos Fusion Data Center.]

Storage

  • Support for DCBX (Junos Fusion Data Center)—Starting in Junos OS 17.2R1, Junos Fusion Data Center supports Data Center Bridging Capability Exchange Protocol (DCBX), including both DCBX v1.01 and IEEE DCBX. The Junos Fusion Data Center aggregation and satellite devices function as a single logical DCBX capable switch. Configuration for DCBX on Junos Fusion Data Center is performed on the aggregation device and is the same as on a standalone device.

    The satellite device acts as a proxy for relaying DCBX messages from the aggregation device to the peer. In a dual-aggregation device setup, the satellite device automatically coordinates DCBX messages from both aggregation devices to relay to the peer, keeping the Junos Fusion Data Center appearing as a single device.

    [See Understanding DCBX.]

  • Support for PFC (Junos Fusion Data Center) — Starting in Junos OS 17.2R1, Junos Fusion Data Center supports priority-based flow control (PFC) for Fibre Channel over Ethernet (FCoE) traffic. The Junos Fusion Data Center aggregation and satellite devices function as a single logical device. Configuration for PFC on Junos Fusion Data Center is performed on the aggregation device and is the same as on a standalone device.

    [See Example: Configuring CoS PFC for FCoE Traffic.]

Software Installation and Upgrade

  • Upgrading and managing the satellite software on satellite devices (Junos Fusion Data Center)—Starting in Junos OS Release 17.2R1, 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 the satellite software manually from the aggregation device when you issue 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.

    Note

    Before you can save satellite software images on a QFX10002 switch acting as an aggregation device, you must issue a one-time command to expand the storage capacity. To expand the storage area on the aggregation device, issue the request system storage user-disk expand command.

    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—Add the satellite software and associate it with the specified upgrade group.

    • request system software delete upgrade-group—Remove the satellite software association from the specified upgrade group.

    • request system software rollback upgrade-group—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 Software in a Junos Fusion Data Center.]

Software Licensing

  • Licensing model (Junos Fusion Data Center)—Starting with Junos OS Release 17.2R1, you need to install a Junos Fusion license in addition to any other feature licenses that you install to track and activate the following models that are shipped with satellite software. These models can only be used as satellite devices:

    • QFX5100-48SH-AFO

    • QFX5100-48SH-AFI

    • QFX5100-48TH-AFO

    • QFX5100-48TH-AFI

    Note

    You do not need Junos Fusion licenses for satellite device models that were purchased as Junos OS-based top-of-rack switches.

    You install these licenses on the aggregation device. Because the configurations are synchronized between aggregation devices, you only need to purchase one license and install it on one aggregation device regardless of whether you deploy a single or dual aggregation device topology. You can purchase a single-pack license to activate one satellite device, or you can purchase a multipack license to activate multiple satellite devices.

    The following Junos Fusion Data Center SKUs are available for purchase:

    • QFX10K-C1-JFS-1

    • QFX10K-C1-JFS-4

    • QFX10K-C1-JFS-8

    • QFX10K-C1-JFS-16

    • QFX10K-C1-JFS-32

    • QFX10K-C1-JFS-64

    You can issue the request system add license, request system license delete, and request system license save commands to manage your licenses. You can also issue the show system license command to display license information.

    [See Understanding Junos Fusion Licenses.]