New Features

The following features have been added to JNU Release 1.3.

Support for JNU Controllers

Table 1 shows the support for JNU Controllers in JNU 1.3R2.

Table 1: JNU Controllers Support in JNU 1.3R2

Platforms Supported in Feature-rich Mode

Platforms Supported in Port-extender Mode

MX5, MX10, MX40, MX80, and MX960 Universal Edge routers

MX5, MX10, MX40, MX80, and MX960 Universal Edge routers

EX9204, EX9208, and EX9214 Ethernet Switches

 

Support for JNU Satellites

Table 2 shows the support for JNU Satellites in JNU 1.3R2.

Table 2: JNU Satellites Support in JNU 1.3R2

Platforms Supported in Feature-rich Mode

Platforms Supported in Port-extender Mode

EX4200, EX4500, EX4550, EX3200, EX3300, and EX6200 Ethernet Switches

EX4200, EX4500, EX4550, EX3200, and EX3300 Ethernet Switches

QFX3500 device

QFX3500 device

Mixed Virtual Chassis composed of any combination of EX4200 and EX4500 switches

Mixed Virtual Chassis composed of any combination of EX4200 and EX4500 switches

ACX1000 and ACX2000 Universal Access Routers

 

MX5, MX10, MX40, and MX80 Universal Edge routers
(You can configure an MX Series router as a controller or a satellite. Satellites are managed by a controller in a JNU group.)

 

Support for Junos OS

Table 3 shows the support for Junos OS Releases in JNU 1.3R2.

Table 3: Junos OS Support in JNU 1.3R2

Platform

Junos OS Release

ACX1000 and ACX2000 Universal Access Routers

12.2R2.4, 12.3R1.7

EX4200, EX4500, EX4550, EX3200, EX3300, and EX6200 Ethernet Switches

12.2R2.4, 12.3R1.7

EX9000 Ethernet Switches

12.3R1.7

MX Series 3D Universal Edge routers

12.3R5

QFX3500 device

12.1X49-D1.2 (no MC-LAG support),

12.2X50-D20.4, 12.3X50-D10.3 (MC-LAG support),

Note: Version 1.1 of the SLAX language, which is supported in Junos OS Release 12.2 and later releases, introduces mutable variables. Unlike variables declared using the var statement, the value of a mutable variable can be modified by a script. You can set the initial value of a mutable variable at the time you declare it or at any point in the script. On MX Series controllers that run junos OS Release 12.2 and later, you can use mutable variables in the op and commit scripts.

Support for JNU Port Extender Mode

Until JNU Release 1.2, the only mode of operation of the controller and satellite devices was feature-rich mode. Through feature-rich mode, users manage the controller and the satellite devices as a single-managed device. Users modify and commit configuration changes for satellite devices only on the controller and commit the configurations to the satellites. In JNU Release 1.3R2, the JNU port-extender mode is provided in which you can configure the JNU controller and satellite devices to operate in port-extender mode. In this mode, the satellite interface resources are extended to the controller that needs to be anchored and the satellite devices behave like a line-card chassis on the controller. Port-extender mode signifies that when you configure an interface that resides physically on a satellite, the same physical interface can be extended to the controller using a service VLAN (S-VLAN) tag with a logical interface created to anchor the extended satellite interface on the controller. The advantage of port-extender mode is that all the interfaces in the JNU group of devices now reside on the controller. A JNU group that consists of the controller and a number of satellites is regarded as a single, unified network entity, with the controller owning all the interface resources including those residing on the satellites (remote line-cards) as extended ports.

When an interface that resides on the satellite is enabled within the JNU group, an S-VLAN ID or tag is used to transmit the data traffic from the remote interface of the satellite to the controller. Multiple VLANs can traverse the same satellite interface. All customer VLANs (C-VLANs) on the same satellite port are extended to the controller by encapsulating the C-VLANs with the same S-VLAN ID. Each C-VLAN is assigned a logical interface on the controller.

Features supported in feature-rich mode are supported in the port-extender mode and configured using the same configuration template names and parameter lists. However, family inet and family inet6 are supported only in the firewall filter feature and 'class-of-service' feature, which are not supported in port-extender mode.

In JNU 1.3R2, Q-in-Q tunneling functionality on the satellite interface port is not supported in port-extender mode, because the config-interface statement requires only one VLAN ID during port extension and you cannot specify two VLAN tags.

Note: Starting with Junos OS Release 12.3R5, the remote procedure call (RPC) in JNU 1.3R2 port-extender mode enables or disables the port-extender ports on the controller when the status of the satellite ports is up or down respectively. For Junos OS Releases 12.3R1 through 12.3R4, use the request system software add /var/db/scripts/pkg/jtools-12.3R3-S2_jnu.tgz command on the controller to import the RPC.

Support for EX Series Switches in a Mixed Virtual Chassis

An interconnection of different switch models is called a mixed Virtual Chassis. JNU supports a mixed Virtual Chassis composed of any combination of EX4200 and EX4500 switches. In a mixed EX4200 and EX4500 Virtual Chassis, you can configure up to 10 member switches.

You can interconnect any model of EX4200 and EX4500 switches into the same mixed Virtual Chassis, and any of these switches can assume the primary, backup, or linecard role. You can interconnect the member switches by using dedicated Virtual Chassis ports (VCPs) or VCPs that are configured from optical ports.