Specifications

You can configure the router to collect time statistics, or both volume and time statistics,
for the service accounting sessions being managed by AAA. To configure the collection
of statistical details that are time-based only, include the statistics time statement at
the [edit access profile profile-name service accounting] hierarchy level. To configure
the collection of statistical details that are both volume-time-based only, include the
statistics volume-time statement at the [edit access profile profile-name service
accounting] hierarchy level.
•
Specifying the UDP port for RADIUS dynamic-request servers—Beginning in Junos
OS Release 13.3, you can define the UDP port number to configure the port on which
the router that functions as the RADIUS dynamic-request server must receive requests
from RADIUS servers. By default, the router listens on UDP port 3799 for dynamic
requests from remote RADIUS servers. You can configure the UDP port number to be
used for dynamic requests for a specific access profile or for all of the access profiles
on the router. To define the UDP port number, include the dynamic-request-port
port-number statement at the [edit access profile profile-name radius-server
server-address] or the [edit access radius-server server-address] hierarchy level.
•
DCHP Relay subscriber and proxy-mode support (MX Series)—Starting with Junos
OS Release 13.3, when DHCP Relay Agent for subscriber management is configured in
proxy-mode, DHCP Request packets for which no client/subscriber state exists on the
Relay Agent (stray requests) behave according to RFC 2131 Section 4.3.2: “If the DHCP
server has no record of this client, then it MUST remain silent, and MAY output a warning
to the network administrator. This behavior is necessary for peaceful coexistence of
non-communicating DHCP servers on the same wire.” Such behavior also occurs when
multiple, non-communicating, proxy-mode Relay Agents are processing DHCP Request
packets from the same client or subscriber. In some network configurations, Relay
Agent can send a NAK to the client or subscriber when Relay Agent is not configured
to act on bind-on-request. The NAK prevents Relay Agent from forwarding the DHCP
Request to the server or, in the case of a client move, when the packet is not directed
to the proxy-mode Relay Agent that receives it. DHCP Relay Agent for subscriber
management no longer generates a NAK in place of the server in response to stray
requests but relies on the server to respond appropriately to the client or subscriber.
For those cases when packets are configured not to be forwarded to the server
(no-bind-on-request is configured), or when the packet is determined not to be directed
to the receiving Relay Agent, those packets are silently discarded in accordance with
RFC 2131 Section 4.3.2.
•
Addition of pw-width option to the nas-port-extended-format statement—Starting in
Junos OS Release 13.3R4, you can configure the number of bits for the pseudowire field
in the extended-format NAS-Port attribute for Ethernet subscribers. Specify the value
with the pw-width option in the nas-port-extended-format statement at the [edit access
profile profile-name radius options] hierarchy level. The configured fields appear in the
following order in the binary representation of the extended format:
aggregated-ethernet slot adapter port pseudo-wire stacked-vlan vlan
The width value also appears in the Cisco NAS-Port-Info AVP (100).
•
LAC configuration no longer required for L2TP tunnel switching with RADIUS
attributes (MX Series)—Starting in Junos OS Release 13.3R6, when you use Juniper
Networks VSA 26-91 to provide tunnel profile information for L2TP tunnel switching,
Copyright © 2015, Juniper Networks, Inc.66
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series