Specifications

You can determine whether direct-connect is configured for particular interfaces by
issuing the show interfaces or show pppoe underlying-interfaces command.
•
ANCP agent behavior for invalid generic response messages (MX Series)—Starting
in Junos OS Release 13.3, when the ANCP agent receives an incorrect or unexpected
generic response message from an ANCP neighbor, it immediately drops the packet,
generates a system log notice message, and takes no further action.
•
Changes to ANCP show command output (MX Series)—Starting in Junos OS Release
13.3, the show ancp neighbor command displays information for all configured ANCP
neighbors regardless of operational state. In earlier releases, it displayed information
only for neighbors in the Established state. The Time field, which displays the elapsed
time since the neighbor entered its current state, has replaced the Up TIme field. An
asterisk (*) prefixed to the neighbor entry indicates that the adjacency information
might be stale.
In Junos OS Release 13.3 and later, the show ancp subscriber command displays
information for all subscribers regardless of operational state. In earlier releases, it
displayed information only for active subscribers in the Established state. An asterisk
(*) prefixed to the subscriber entry indicates that the information might be stale. Two
asterisks (**) indicate that the neighbor associated with the subscriber has lost its
adjacency.
•
Enhanced accounting statistics (M Series, MX Series, and T Series)—Starting in Junos
OS Release 13.3, the show network-access aaa statistics accounting command includes
the optional detail keyword, which provides additional information about the RADIUS
accounting statistics. You can use the enhanced details for troubleshooting
investigations.
[See Verifying and Managing Subscriber AAA Information.]
•
Support for processing Cisco VSAs in RADIUS messages for service
provisioning—Starting with Junos OS Release 13.3R3, Cisco VSAs are supported for
provisioning and management of services in RADIUS messages, in addition to the
supported Juniper VSAs for administration of subscriber sessions. In a deployment in
which a customer premises equipment (CPE) is connected over an access network to
a broadband remote access gateway, the Steel-Belted Radius Carrier (SBRC)
application might be used as the authentication and accounting server using RADIUS
as the protocol and the Cisco BroadHop application might be used as the Policy Control
and Charging Rules Function (PCRF) server for provisioning services using RADIUS
change of authorization (CoA) messages. Both the SBRC and the Cisco BroadHop
servers are considered to be connected with the broadband gateway in such a topology.
By default, service accounting is disabled. If you configure service accounting using
both RADIUS attributes and the CLI interface, the RADIUS setting takes precedence
over the CLI setting. To enable service accounting using the CLI, include the accounting
statement at the [edit access profile profile-name service] hierarchy level. To enable
interim service accounting updates and configure the amount of time that the router
waits before sending a new service accounting update, include the update-interval
minutes statement at the [edit access profile profile-name service accounting] hierarchy
level.
65Copyright © 2015, Juniper Networks, Inc.
Changes in Behavior and Syntax