### JunosE 12.1.0 Release Notes

> ### Release Highlights

> Release 12.1.0 includes the features described in this section.

> Category | Feature
> --- | ---
> AAA | Configuration of AAA-Specific Attributes per DCM Profile on page 7
> IPv6 | IPv6 Support for LAG Interfaces on page 7 IPv6 Support for Frame Relay and Multilink Frame Relay Interfaces on page 8
> RADIUS | Configuration of RADIUS-Specific Attributes per DCM Profile on page 8
> Subscriber Interfaces | Support for Multiple Subscribers with the Same IP Address on page 9
> Unified ISSU | Unified ISSU Support for IPv6 on page 10 Application Support for Unified ISSU for DHCPv6 Local Server and Local Address Pool on page 10

> #### AAA

> - Configuration of AAA-Specific Attributes per DCM Profile

> JunosE Software now enables you to configure AAA-specific attributes for subscribers attached to a specific PPP profile. If a per-profile list is configured, then only the attributes specified in the per-profile list are processed. If the per-profile list is not configured, then the existing standard attributes are configured.

> | Informational Note: The attributes supported by the per-profile list take precedence over the standard AAA attribute configuration. By default, the inclusion of all attributes is disabled in the per-profile list.

> Currently, this feature enables you to configure the following AAA attributes:

> - tunnel ignore nas-port
> - tunnel ignore nas-port-type

> For information on configuring RADIUS-specific attributes per DCM profile see, Configuration of RADIUS-Specific Attributes per DCM Profile on page 8.

> The following new commands have been introduced to support the filtering of AAA attributes per DCM profile:

> aaa per-profile-attr-list | attributes
> aaa-perprofilelist-name | show aaa per-profile-attr-list
> action type |

> The output of the following commands has been changed to support this feature:

> show configuration | show aaa profile

> As a part of this feature, the aaaServerGeneral log has been modified to support the configuration of AAA-specific attributes per DCM profile.

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, the configuration of AAA attributes was chassis-wide.

> #### IPv6

> - IPv6 Support for LAG Interfaces

> You can now configure IPv6 prefix addresses for a LAG bundle and for VLAN and PPPoE subinterfaces that are members of a LAG bundle. In environments in which an independent or a dual-stack IPv6 subscriber exists, the PPP link between the customer premises equipment (CPE) and the provider edge (PE) device or router might require both IPv4 and IPv6 for transmission of data. In such networks, you can use LAG bundles configured with IPv6 addresses for effective usage of bandwidth and reduced administrative costs.

> For IPv6 traffic, the hash value is calculated using the IPv6 source and destination addresses. One of the links, based on the hashed value, is used to send the packets out of the router.

> The following line module combinations on E Series routers support the configuration of IPv6 addresses on VLAN and S-VLAN subinterfaces in a LAG bundle:

> - On ERX14xx models, ERX7xx models, and the ERX310 router
> - OC48 line modules with an OC48 FRAME APS I/O module
> - GE-2 and GE-HDE line modules
> - On E120 and E320 routers
> - ES2 4G line modules with ES2-S1 GE-8 IOA
> - ES2 10G line modules with ES2-S1 GE-8 IOA
> - ES2 10G ADV line modules with ES2-S1 GE-8 IOA
> - ES2 10G line modules with ES2-S3 GE-20 IOA
> - ES2 10G ADV line modules with ES2-S3 GE-20 IOA

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, you could configure only IPv4 addresses for VLAN and S-VLAN member subinterfaces of a LAG bundle.

> - IPv6 Support for Frame Relay and Multilink Frame Relay Interfaces

> You can now configure IPv6 prefix addresses on Frame Relay interfaces on a packet over SONET (POS) physical interface. IPv6 traffic is forwarded over Frame Relay circuits and the database of the forwarding controller is updated with IPv6 as an upper-layer interface to the Frame Relay layer.

> You can use the ipv6 address command in Subinterface Configuration mode to add an IPv6 address to a Frame Relay PVC over a POS subinterface. You can also use the ipv6 address command in Interface Configuration mode to add an IPv6 address on an interface with Frame Relay as the encapsulation method that operates as data communications equipment (DCE), data terminal equipment (DTE), or network-to-network interface (NNI).

> For MLFR interfaces, you can configure IPv6 addresses on Frame Relay subinterfaces in an MLFR bundle that contains serial interfaces as member links. You can use the ipv6 address command in Subinterface Configuration mode to add an IPv6 prefix to a Frame Relay subinterface in an MLFR bundle that contains serial member links.

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, an error message was displayed when you attempted to configure IPv6 addresses on Frame Relay and MLFR interfaces and the setting was not saved.

> #### RADIUS

> - Configuration of RADIUS-Specific Attributes per DCM Profile

> JunosE Software now enables you to configure RADIUS-specific attributes for the subscribers attached to a specific PPP profile. If a per-profile list is configured, then only the attributes specified in the per-profile list are processed. If the per-profile list is not configured, then the existing standard attributes are configured.

> | Informational Note: The attributes supported by the per-profile list take precedence over the standard RADIUS attribute configuration. By default, the inclusion of all attributes is disabled in the per-profile list.

> Currently, this feature enables you to configure the following RADIUS attributes:

> - override nas-ip-addr
> - calling-station-id

> For information on configuring AAA-specific attributes per DCM profile see, Configuration of AAA-Specific Attributes per DCM Profile on page 7.

> The following new commands have been introduced to support the filtering of RADIUS attributes per DCM profile:

> action type | radius perprofilelist name
> attributes | request type
> radius per-profile-attr-list | show radius per-profile-attr-list

> The output of the following commands has been changed to support this feature:

> show configuration | show aaa profile

> As a part of this feature, the radiusSendAttributes log has been modified to support the configuration of RADIUS-specific attributes per DCM profile.

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, the configuration of RADIUS attributes was per virtual router.

> #### Subscriber Interfaces

> - Support for Multiple Subscribers with the Same IP Address

> IP Subscriber Manager and Dynamic Configuration Manager now allow more than one subscriber to have the same IP address across different virtual routers without taking into account the dynamic subscriber interface (DSI) configuration. In the DSI configuration, the virtual router name gets appended to the DSI name.

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

> ip auto-configure append-virtual-router-name

> The output of the show profile name command has been updated to include the new configuration option.

> As part of this feature, the ipSubscriberMgr log event has been modified to store information about support for multiple subscribers with the same IP address across virtual routers.

> Change in existing behavior: Existing feature extended as described here. In lower-numbered releases, IP Subscriber Manager allowed only one subscriber with a particular IP address. The configuration of a pool with the same network on two different DHCP Local Server instances across different virtual routers resulted in disallowing the second subscriber entry in the IP Subscriber Manager database.

> #### Unified ISSU

> - Unified ISSU Support for IPv6

> IPv6 is now ISSU safe and compliant. You can now upgrade E Series routers using ISSU without disconnecting IPv6 subscriber connections and with minimal disruption in IPv6 traffic forwarding through the chassis.

> Change in existing Behavior: Existing feature extended as described here. In lower-numbered releases, IPv6 was considered ISSU unsafe. With this feature, IPv6 is considered ISSU safe and compliant.

> - Application Support for Unified ISSU for DHCPv6 Local Server and Local Address Pool

> DHCPv6 local server and local address pools (LASv6) for IPv6 are now ISSU safe and compliant. You can now upgrade ISSU when DHCPv6 local server or LASv6 applications are configured on the server. This ensures that DHCPv6 local server is available to handle critical error messages even during an ISSU upgrade.

> As part of this feature, the dhcpv6LsGeneral log has been modified to capture the debug messages generated when ISSU is running on a DHCPv6 application server and the errors generated while processing ISSU signals or while mirroring.

> Change in existing Behavior: Existing feature extended as described here. In lower-numbered releases, DHCPv6 and LASv6 were considered ISSU unsafe. With this feature, DHCPv6 and LASv6 are declared ISSU safe and compliant.

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