Specifications

ManualsBrandsMatrix ManualsExercise BikeMX-R5

is provided to the client using DHCPv6-PD, the RADIUS interim accounting message

includes the delegated prefix (IA_PD, such as /56). The

address-change-immediate-update statement is now effective for any address allocation

change after an Acct-Start message is issued (for IPv6NCP and DHCPv6). An immediate

Interim-Acct message is sent upon any subsequent DHCPv6 negotiation and allocation

when new allocated addresses are added. After IPv6NCP negotiation, DHCPv6 address

allocation and negotiation occurs.

[See RADIUS Accounting Messages for Dual-Stack Subscribers.]

•

Support for IPv6 for TACACS+ authentication (M Series, MX Series, and T Series)—

Starting with Release 13.3, Junos OS supports IPv6 along with the existing IPv4 support

for user authentication using TACACS+ servers.

•

Configurable L2TP receive window size (MX Series)—Starting in Junos OS Release

13.3, the new rx-window-size statement at the [edit services l2tp tunnel] hierarchy level

enables you to specify the size of the receive window in the range 4 through 128 on an

L2TP LAC or LNS. The default value is 4. The Receive Window Size AVP (Attribute

Type 10) is not sent in the SCCRQ message when the default value is configured on a

LAC or in the SCCRP message when configured on an LNS.

[See Setting the L2TP Receive Window Size.]

•

Clearing ANCP statistics (MX Series)—Starting in Junos OS Release 13.3, you can

clear all ANCP statistics with the clear ancp statistics command. You can clear statistics

for a particular neighbor identified by the neighbor’s IP address with the clear ancp

statistics ip-address ip-address command. You can clear statistics for a particular

neighbor identified by the neighbor’s IP address with the clear ancp statistics

system-name mac-address command.

[See Clearing and Verifying ANCP Statistics.]

•

ANCP agent support for nonzero partition IDs (MX Series)—Starting in Junos OS

Release 13.3, the ANCP agent on the router can form adjacencies with multiple logical

partitions on a neighbor when you enable the agent to learn partition IDs during

adjacency negotiation with the neighbor. If the agent receives a SYN message from

the neighbor within a configurable period, the agent learns the partition IDs and can

form adjacencies with the partitions. The agent can form an adjacency only with the

neighbor if the SYN is not received within the period, the partition ID is zero, or learning

is not enabled.

[See Configuring the ANCP Agent to Learn ANCP Partition IDs.]

•

Dynamic protocol version detection for ANCP (MX Series)—Starting in Junos OS

Release 13.3, when an ANCP neighbor opens adjacency negotiations, it indicates the

highest version of ANCP that it supports. ANCP neighbors must be able to identify the

supported versions because ANCP Version 1, defined in RFC 6320, Protocol for Access

Node Control Mechanism in Broadband Networks, is not interoperable with the earlier

version based on GSMPv3.

During negotiation, the receiving neighbor returns the value sent by the other neighbor

if it supports that version, or drops the message if it does not. You can still configure

the router to operate in pre-ietf mode for interoperability with neighbors that support

only GMSPv2.

Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series