### JunosE 11.3.0 Release Notes

> ### Release Highlights

> Release 11.3.0 includes the features described in this section.

> Category | Feature
> --- | ---
> DHCP | Support for RADIUS-Provisioned DHCP Options in DHCP Local Server Standalone Authentication Mode on page 7
> Documentation | Enhanced ERX End-of-Life Module Guide on page 8
> RADIUS | Inclusion of RADIUS IETF Framed-Route Attribute [22] in RADIUS Accounting Messages on page 9
> System | Support for Conventional Upgrade on ES2 10G LMs on page 9
> Tunneling | Support for IP Reassembly for Dedicated Tunnel Server Configured on an ES2 10G ADV LM on page 10

> #### DHCP

> - Support for RADIUS-Provisioned DHCP Options in DHCP Local Server Standalone Authentication Mode

> You can now configure DHCP Local Server to receive DHCP options returned by RADIUS server from AAA. DHCP Local Server now includes the DHCP options returned by RADIUS, along with other default or requested DHCP options, in DHCP OFFER and ACK responses. This feature is only supported in DHCP Standalone Authentication Mode.

> By default, inclusion of DHCP options returned by RADIUS as part of DHCP OFFER and ACK responses is disabled. To enable DHCP Local Server to include the DHCP options returned by RADIUS, use the radius-dhcp-options keyword with the ip dhcp-local auth include command. For example:

> host1(config)# ip dhcp-local auth include radius-dhcp-options

> DHCP Local Server can support up to 312 bytes of DHCP options data in DHCP packets. While DHCP Local Server gives precedence to DHCP options returned by RADIUS over locally configured DHCP options, inclusion of the DHCP options returned by RADIUS is based on the space available in the DHCP options buffer. As a result, some options may be dropped while the others are included in DHCP OFFER and ACK responses.

> The following DHCP options configured from RADIUS are not supported:

> 0 - Pad Option | 77 - User class
> 1 - Subnet Mask | 80 - Rapid commit
> 13 - Boot File Size Option | 81 - client FQDN
> 50 - Requested IP Address | 82 - Relay Agent Information Option
> 51 - IP Address Lease time | 90 - Authentication
> 52 - Option Overload | 93 - client system
> 53 - DHCP Message Type | 94 - client NDI
> 54 - Server Identifier | 98 - User Auth
> 55 - Parameter Request List | 116 - Auto Config
> 56 - Message | 118 - Subnet Selection
> 57 - Maximum DHCP Message Size | 122 - Code CCC
> 58 - Renewal Time Value | 124 - Vendor Identifying Vendor class
> 59 - Rebinding Time Value | 125 - Vendor Specific Information
> 60 - Vendor class identifier | 128 - TFTP Server IP Address
> 61 - Client-identifier | 129 - Call Server IP Address
> 66 - TFTP server name | All options beyond 132
> 67 - Bootfile name |

> The following commands have been enhanced to support the inclusion of RADIUS-returned DHCP options as part of OFFER and ACK responses.

> ip dhcp-local auth include | show ip dhcp-local auth config

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, DHCP Local Server did not include DHCP options returned from the RADIUS server as part of OFFER and ACK responses. This is no longer the case.

> #### Documentation

> - Enhanced ERX End-of-Life Module Guide

> Beginning with JunosE Release 11.3.0, the title of the ERX End-of-Life Module Guide has changed to the E Series End-of-Life Module Guide.

> The E Series End-of-Life Module Guide has been updated to include end-of-life modules that are no longer orderable for ERX routers, E120 routers, and E320 routers.

> The following table lists the EOL modules have been moved to the E Series End-of-Life Module Guide from the ERX Module Guide and the E120 and E320 Module Guide:

> Module Name | Module Type
> --- | ---
> cOC3/STM1multimode | ERX
> cOC3/STM1 single-mode intermediate reach | ERX
> cOC3/STM1 single-mode long reach | ERX
> cOC12/STM4multimode without APS/MSP redundancy | ERX
> cOC12/STM4 single-mode intermediate reach without APS/MSP redundancy | ERX
> cOC12/STM4 single-mode intermediate reach with APS/MSP redundancy | ERX
> cOC12/STM4 single-mode long reach | ERX
> CT3/T3 12 (12 ports) | ERX
> E3 Frame (12 ports) | ERX
> IPSec Service Module | ERX
> SRP 5G+(2 GB) | ERX
> T3 Frame (12 ports) | ERX
> 10GE IOA | E120 and E320

> Change in existing behavior: In lower-numbered releases, we included only ERX modules that are end-of-life. This is no longer the case.

> #### RADIUS

> - Inclusion of RADIUS IETF Framed-Route Attribute [22] in RADIUS Accounting Messages

> You can now specify that RADIUS accounting messages include the RADIUS IETF Framed-Route attribute [22]. You can use the radius include command from Global Configuration mode to configure inclusion of this RADIUS attribute in Acct-Start, Acct-Stop, and Interim-Acct messages. When included in Acct-Stop messages, the attribute is also included in Interim-Acct messages. The attribute is excluded by default from the Acct-Start, Acct-Stop, and Interim-Acct messages.

> As a part of this feature, the framed-route keyword has been added to the radius include command.

> The following command has been modified to support this feature:

> radius include

> The output of the following command has been modified to support this feature:

> show radius attribute-included

> Change in existing behavior: New feature added as described here.

> #### System

> - Support for Conventional Upgrade on ES2 10G LMs

> JunosE Software now supports field programmable gate array (FPGA) upgrades on REV-02 ES2 10G line modules. You must perform the upgrade using a conventional software upgrade process; you cannot use the unified ISSU process to perform the upgrade. In lower-numbered releases, you were not able to use a conventional software upgrade or a unified ISSU process on REV-02 ES2 10G LMs.

> In this release, design enhancements enable you to perform a stateless upgrade (non-unified ISSU method, with router-wide outage for users) from JunosE releases numbered lower than Release 11.3.0 to JunosE Release 11.3.0. You cannot run a unified ISSU procedure from JunosE releases that do not contain the design changes for control and status register (CSR) FPGA functionality if the router chassis contains ES2 10G LMs or REV-02 ES2 10G LMs.

> The following design improvements to FPGA have been made in this release:

> - FPGA modifications for resolving fabric-related problems related to SFM redundancy on ES2 4G LMs, ES2 10G LMs, ES2 10G ADV LMs, SRP-100, and SRP-320 modules
> - CSR FPGA changes on ES2 10G LMs and REV-02 ES2 10G LMs to enable FPGA upgrades

> If your network contains routers installed with LMs other than ES2 10G LMs or REV-02 ES2 10G LMs, a preferred suggestion is to transfer subscribers configured on the ES2 10G LMs or REV-02 10G LMs to other LMs available in your environment when you perform unified ISSU. This transfer of subcribers to other LMs avoids disruption of user sessions owing to the limitation that exists with performing a unified ISSU operation on ES2 10 LMs and REV-02 10G LMs.

> Change in existing behavior: Existing feature extended as described here. You can now perform a conventional upgrade from releases numbered lower than Release 11.3.0 to Release 11.3.0, if the router chassis contains ES2 10G LMs or REV-02 versions of the ES2 10G LM. In lower-numbered releases, you could only download the image from serial Programmable Read-Only Memory (PROM), which was a factory image. You still cannot perform a unified ISSU operation from releases numbered lower than Release 11.3.0 to Release 11.3.0, if the router chassis contains ES2 10G LMs.

> #### Tunneling

> - Support for IP Reassembly for Dedicated Tunnel Server Configured on an ES2 10G ADV LM

> An ES2 10G ADV LM and Service IOA combination provides a dedicated tunnel server. When packets larger than the MTU of the tunnel interface are sent through the tunnel, they may be fragmented. However, tunnel processing requires each packet to be a complete packet, the way it was before it got fragmented.

> To support this, fragmented packets are now reassembled on an ES2 10G ADV LM before they are sent for tunnel processing.

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, the IP reassembly for dedicated tunnel-server was supported only when configured on the ES2 4G LM.

Copyright © 2010, Juniper Networks, Inc. Report An Error