Feature List

ACX1000
Junos OS Features
Release
18.4R1
Copyright © 2019, Juniper Networks, Inc.

Contents
Application Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Application Layer Gateways (ALGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Trivial File Transfer Protocol (TFTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Authentication and Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Local authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Support for password change policy enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
MAC RADIUS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

MAC RADIUS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
TACACS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
TACACS+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Alarms, defects, and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Alarms, defects, and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Ethernet alarm indication signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Loss of signal (LOS) alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
User-defined alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chassis management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chassis management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
DMA recovery mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

DMA recovery mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Internet Control Message Protocol (ICMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

ICMPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Internet Control Message Protocol (ICMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Precision Time Protocol (PTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Clock clients: Automatic client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Clock clients: Manual client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Clock clients: Secure client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
IEEE 1588v2 boundary clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PHY timestamping for grandmaster clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
PTP master boundary clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PTP over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PTP over User Datagram Protocol (UDP) over IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PTP slave performance metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Precision Time Protocol (PTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Precision Time Protocol (PTP) over integrated routing and bridging (IRB) interfaces . . . . . . . . . . . . . . . . . . . . . . 7
Precision Timing Protocol (PTP) - Ordinary clock (slave only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Timing–1588-v2, 1588-2008–slave clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
RFC 2544-based benchmarking tests for Layer 2 and Layer 3 Ethernet services . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Ethernet loopback support for RFC 2544-based benchmarking test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
RFC 2544-based benchmarking tests for Layer 2 and Layer 3 Ethernet services . . . . . . . . . . . . . . . . . . . . . . . . . 8
Synchronous Ethernet (SyncE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Automatic clock selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Clock Source Selection Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Combined operation of Synchronous Ethernet and Precision Time Protocol or hybrid mode . . . . . . . . . . . . . . . . 9
Configured or received clock selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Synchronous Ethernet (SyncE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Synchronous Ethernet clock synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Class of Service (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Behavior aggregate (BA) Classifiers: 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Behavior aggregate (BA) Classifiers: DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Behavior aggregate (BA) Classifiers: DSCP IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Behavior aggregate (BA) Classifiers: EXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Behavior aggregate (BA) Classifiers: IEEE 802.1ad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Experimental (EXP) bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Fixed classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Physical interface-based classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
CoS on Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
CoS for PPP and MLPPP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Eight queues per port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
TDM and ATM class-of-service (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Congestion Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Weighted random early detection (WRED) tail-drop profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Forwarding classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Up to 8 forwarding classes with one-to-one mapping to output queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Policing/Rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Per-queue committed information rate (CIR) and peak information rate (PIR) . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Physical interface policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Policing - per family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Policing - per logical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Policing/Rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
SrTCM (color aware, color blind) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tricolor marking policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Two-rate tricolor marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Rewrite Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
802.1p Rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
DSCP IPv6 rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Differentiated Services Code Point (DSCP) rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
EXP rewriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Rewrite MPLS and DSCP to different values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring the shared buffer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Internal buffer of 2 MB with per-egress queue buffer management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Scheduling with two different priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Port shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Strict priority queuing or Low Latency Queuing (LLQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Multiple strict-priority queues per port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Priority queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Strict priority queuing or Low Latency Queuing (LLQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Ethernet Switching and Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Bridge domains and virtual switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Bridge domains and virtual switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Disabling local switching in bridge domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Host protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Host protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
IEEE 802.1ah PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

E-LINE and E-LAN services in PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Integrated routing and bridging (IRB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Integrated routing and bridging (IRB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Layer 2 protocol tunneling (L2PT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Layer 2 protocol tunneling (L2PT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Multiple Spanning Tree Protocol (MSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Multiple Spanning Tree Protocol (MSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Q-in-Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Q-in-Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Rapid Spanning Tree Protocol (RSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Rapid Spanning Tree Protocol (RSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Spanning Tree Protocol (STP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

BPDU protection for spanning-tree protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Loop protection for spanning-tree protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Root protection for spanning-tree protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Spanning Tree Protocol (STP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
VLAN Spanning Tree Protocol (VSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

VLAN Spanning Tree Protocol (VSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Forwarding Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Equal-cost multipath (ECMP) flow-based forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Equal-cost multipath (ECMP) flow-based forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
IP fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
IP fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Local port mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Storm Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Storm Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Link aggregation groups (LAGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Link aggregation groups (LAGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Virtual Router Redundancy Protocol (VRRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Virtual Router Redundancy Protocol (VRRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Virtual Router Redundancy Protocol version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
IPv6 specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Dual Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Dynamic routes distribution through IS-IS and OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
IPv6 VPN Provider Edge Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IPv6 forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IPv6 over MPLS (6PE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IPv6 over generic routing encapsulation (GRE) tunnels using IPv4 transport—de-encapsulation support . . . . . . . 24
IPv6 over generic routing encapsulation (GRE) tunnels using IPv4 transport—encapsulation support . . . . . . . . . 24
IPv6 static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Layer 3 VPNs for IPv4 and IPv6 address families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Path MTU Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ATM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ATM OAM F4 and F5 cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ATM PWE3 control word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ATM PWE3 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ATM PWE3 via dynamic labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ATM VPI/VCI Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ATM idle/unassigned cell suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ATM policing and shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ATM service categories (CBR, nrt-VBR, UBR) to the UNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
ATM support for N to 1 PW Promiscuous mode: 1 PW per port and 1 PW per VPI . . . . . . . . . . . . . . . . . . . . . 28
ATM time-division multiplexing (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Inverse Multiplexing for ATM (IMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
RFC4717: S6.3 – ATM AAL5 SDU encap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
BERT algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
BERT algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
E1/T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
T1 and E1 interfaces time-division multiplexing (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
T1/E1 channelization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Inverse Multiplexing for ATM (IMA) Layer 2 encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
MLPPP encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Point-to-Point Protocol (PPP) encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

RFC4717 ATM Encapsulation: S6.1 ATM N to one cell mode (required as per standard) . . . . . . . . . . . . . . . . . . 31
T1/E1 encapsulation (SAToP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
TDM CESoPSN: CESoPSN encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Ethernet Local Management Interface (E-LMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Ethernet Local Management Interface (E-LMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Ethernet OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
OAM with Layer 2 bridging as a transport mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Ethernet OAM connectivity fault management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

802.1ag CC monitoring on active and standby pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
802.1ag Ethernet OAM connectivity fault management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
802.1ag optional type, length, and value (TLV) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Distinguish each 802.1ag connection by vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Ethernet connectivity fault management (CFM) - Connection protection for Ethernet pseudowires . . . . . . . . . . 33
Ethernet connectivity fault management (CFM) - Path protection for Ethernet pseudowires . . . . . . . . . . . . . . . 33
Ethernet frame delay measurement (ETH-DM, Y.1731) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Ethernet Delay Measurement (ETH-DM, Y.1731) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
IEEE 802.1ag and ITU-T Y.1731 OAM protocols on up MEPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ITU-T Y.1731 ETH-LM, ETH-SLM, and ETH-DM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Ethernet ring protection switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Ethernet ring protection switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Ethernet synthetic loss measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Ethernet synthetic loss measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
External and internal loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

External and internal loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Generic routing encapsulation (GRE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

IPv4 over generic routing encapsulation (GRE) tunnels—de-encapsulation support . . . . . . . . . . . . . . . . . . . . . . 35
IPv4 over generic routing encapsulation (GRE) tunnels—encapsulation support . . . . . . . . . . . . . . . . . . . . . . . . 36
Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Gigabit Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Autonegotiation on Gigabit Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Dual-speed Gigabit Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Gigabit Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Statistics collection and reporting for Gigabit Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Unicast mode (IPv4 on Gigabit Ethernet interfaces only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Global Positioning System (GPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Global Positioning System (GPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

IEEE 802.3ah Link Fault Management (LFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Dying-gasp PDU generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
IEEE 802.3ah Link Fault Management (LFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Inline service interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Inline service interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Layer 2 control packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Layer 2 control packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Local loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Local loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Logical tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Logical tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Loopback interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Loopback interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Maximum transmission unit (MTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Maximum transmission unit (MTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Media type selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Media type selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
AAL5 SDU [n-to-1 cell relay] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Cell concatenation (1 to 30 cells per packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Denied packets counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Early Packet Discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Event handling of SFP insertion and removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Explicit disabling of the physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Input policing per VC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
MAP ATM service categories to PW EXP bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
PIM and IGMP in global domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Packet/byte counters per VP and VC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Remote fault notification for 10-Gigabit Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
VC output shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Structure-aware TDM Circuit Emulation Service over Packet-Switched Network (CESoPSN) . . . . . . . . . . . . . . . 43

Structure-aware TDM Circuit Emulation Service over Packet-Switched Network (CESoPSN) . . . . . . . . . . . . . . . 43
TDM CESoPSN: CESoPSN options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
TDM CESoPSN: CESoPSN pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
TDM CESoPSN: Channelization up to the ds0 level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
TDM CESoPSN: Interfaces show commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
TDM CESoPSN: Packet latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

TDM CESoPSN: Protocol support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Time domain reflectometry (TDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Time domain reflectometry (TDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Timing and synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Timing and synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
IGMP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Multicast Listener Discovery (MLD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Multicast Listener Discovery - Version 1 (MLD v1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Multicast Listener Discovery - Version 2 (MLD v2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Unicast reverse-path forwarding (URPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Enhancements to unicast reverse-path forwarding (uRPF) check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Unicast reverse-path forwarding (URPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Multiprotocol Label Switching (MPLS) Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Exception packet handling for MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Exception packet handling for MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Fast Reroute (FRR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Fast Reroute (FRR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
IP Fast Reroute (FRR) (OSPF, ISIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Label Distribution Protocol (LDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label Distribution Protocol (LDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Label Switching Router (LSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label Switching Router (LSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Label edge router (LER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label edge router (LER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Label-switched paths (LSPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Link protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Node-link protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Multiprotocol Label Switching (MPLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

MPLS OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
MPLS ping and traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Pseudowire transport service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Uniform and pipe mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Pseudowire redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Layer 2 pseudowire redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Pseudowire redundancy - Hot and cold standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Pseudowire redundancy - Protect interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Pseudowire standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Resource Reservation Protocol (RSVP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Resource Reservation Protocol (RSVP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Static LSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Static LSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Traffic engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Diffserv traffic engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Path Computation Element Protocol for RSVP-TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Traffic engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Network Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Drop packet statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Interface Passive-monitor-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Interface byte and packet statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Interface queue statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Statistics collection and handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
NETCONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Adding non-native YANG modules to the Junos OS schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring the ephemeral database using the NETCONF and Junos OS XML protocols . . . . . . . . . . . . . . . . . 53
Device family and release in Junos OS YANG modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Multiple, smaller configuration YANG modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
YANG module that defines CLI formatting for RPC output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
YANG module that defines Junos OS operational commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Simple Network Management Protocol (SNMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

RMON events, alarms and history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
SNMP get and walk management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
SNMP support for Service OAM (SOAM) performance monitoring functions . . . . . . . . . . . . . . . . . . . . . . . . . . 55
SNMP support for the timing feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Simple Network Management Protocol (SNMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Simple Network Management Protocol (SNMP) Management Information Base (MIB) and Traps . . . . . . . . . . . . 56
Juniper Networks Enterprise-Specific MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Standard SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
IP and MAC address validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

IP and MAC address validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4096 network address or port translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Routing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Bidirectional Forwarding Detection (BFD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

BFD support for VCCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Bidirectional Forwarding Detection (BFD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Routing Policies and Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Filter-based forwarding (FBF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Filter-based forwarding for routing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Dynamic allocation of TCAM memory to firewall filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Enhancements to support log and syslog firewall filter actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Firewall filters - family ccc/any . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Firewall filters - family inet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Firewall filters on loopback interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Standard Firewall Filter Match Conditions for MPLS Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Forwarding table filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Forwarding table filters for routing instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Hierarchical policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Hierarchical policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Border Gateway Protocol (BGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

BGP Prefix Independent Convergence for inet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Multiprotocol Border Gateway Protocol (MBGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Intermediate System-to-Intermediate System (IS-IS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Intermediate System-to-Intermediate System (IS-IS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Neighbor Discovery Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Neighbor Discovery Protocol (NDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Open Shortest Path First (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Open Shortest Path First (OSPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Services Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

DHCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
DHCPv6 relay agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Extended DHCP relay agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Preserving DHCP server subscriber information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Real-time performance monitoring (RPM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Real-time performance monitoring (RPM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Two-way active measurement protocol (TWAMP) compliance with RFC 5357 . . . . . . . . . . . . . . . . . . . . . . . . . 64

Two-way active measurement protocol (TWAMP) compliance with RFC 5357 . . . . . . . . . . . . . . . . . . . . . . . . . 64
Subscriber Management and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Other Subscriber Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Counters and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
System Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Network Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
JSON format for configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Control plane DOS prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Control plane DOS prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Dual-root partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Dual-root partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Juniper Extension Toolkit for Junos (JET for Junos) provides a modern programmatic interface for developers
of third-party applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Juniper Extension Toolkit for Junos (JET for Junos) provides a modern programmatic interface for developers
of third-party applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Memory utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Memory utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Network Time Protocol (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Network Time Protocol (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Packet Forwarding Engine management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Packet Forwarding Engine management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Scripts (Op scripts, commit scripts, event scripts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Python language for commit, event, op, and SNMP scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Stylesheet language alternative syntax (SLAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Software Installation and Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Autoinstallation of a configuration file from a Disk-on-Key device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Hybrid mode of autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
System snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
System snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Unattended boot mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Unattended boot mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Virtual Private Networks (VPNs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
E-LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
E-LINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Layer 2 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Control word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Layer 2 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Layer 3 VPN (L3 VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Support to control traceroute over Layer 3 VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Virtual Private LAN Service (VPLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Hierarchical VPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Virtual private network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Edge protection using static VPWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Pseudowire Emulation Edge to Edge [PWE3 (signaled)] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Static Ethernet PWs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Features Supported on ACX1000 in Junos OS 18.4R1 Application Security
Application Security
Application Layer Gateways (ALGs)

Domain Name System (DNS)
Supported Platforms
Platform Introduced Release Hardware Components License Requirements Caveats
ACX1000 Junos OS 12.2R1
Trivial File Transfer Protocol (TFTP)

Supported Platforms
Authentication and Access Control
Local authentication
Support for password change policy enhancement
The Junos password change policy for local user accounts is enhanced to comply with additional password policies. As
part of the policy improvement, you can configure the following:
minimum-character-changes: The number of characters by which the new password should be different from the existing
password.
minimum-reuse: The number of older passwords which should not match the new password.
Supported Platforms
MAC RADIUS authentication

MAC RADIUS authentication
MAC RADIUS authentication can be used to authenticate interfaces that are connected to end devices that are not
802.1X-enabled but that you want to allow to access the LAN.
Supported Platforms
Copyright © 2019, Juniper Networks, Inc. 1

Features Supported on ACX1000 in Junos OS 18.4R1 Authentication and Access Control
TACACS+
TACACS+
TACACS+ provides access control for nodes using a centralized server or servers.
Supported Platforms
Chassis
Alarms, defects, and statistics

Alarms, defects, and statistics
Display alarms, defects, and statistics for interfaces running on the ACX Series routers
Supported Platforms
Ethernet alarm indication signal

Junos OS supports ITU-T Y.1731 Ethernet alarm indication signal function (ETH-AIS) to provide fault management for
service providers. ETH-AIS enables you to suppress alarms when a fault condition is detected. Using ETH-AIS, an
administrator can differentiate between faults at the customer level and faults at the provider level. When a fault condition
is detected, a maintenance end point (MEP) generates ETH-AIS packets to the configured client levels for a specified
duration until the fault condition is cleared. Any MEP configured to generate ETH-AIS packets signals to a level higher
than its own. A MEP receiving ETH-AIS recognizes that the fault is at a lower level and then suppresses alarms at current
level the MEP is in.
ACX Series routers support ETH-AIS PDU generation for server MEPs on the basis of the following defect conditions:
• Loss of connectivity (physical link loss detection)
• Layer 2 circuit or Layer 2 VPN down
Supported Platforms
ACX1000 Junos OS
12.3X54-D10

Features Supported on ACX1000 in Junos OS 18.4R1 Chassis
Loss of signal (LOS) alarm

A LOS alarm indicates that a signal could not be detected at the physical interface level. The LOS is generated by the
physical interface and displays a Link Up or Link Down event. To display LOS and other alarms, issue the show interfaces
interface-name extensive command.
Supported Platforms
User-defined alarms
On an ACX Series router, the alarm contact port (labeled ALARM) provides four user-defined input ports and two
user-defined output ports. Whenever a system condition occurs—such as a rise in temperature, and depending on the
configuration, the input or output port is activated.
Supported Platforms
ACX1000 Junos OS
12.3X51-D10
Chassis management
Chassis management
Supported Platforms
DMA recovery mechanism

DMA recovery mechanism
A recovery mechanism has been introduced that is triggered in case the router enters an Idle state on any DMA channels.
The recovery mechanism reboots the PFE to recover from Idle state.
The following recovery message is logged in the RE syslog message:
CHASSISD_FPC_ASIC_ERROR: <FPC 0> ASIC Error detected errorno 0x0000ffff FPC restart initiated
The following recovery message is logged in the PFE syslog message:
BCM DMA channel error detected Resetting the PFE
Supported Platforms

Internet Control Message Protocol (ICMP)

ICMPv6
Supported Platforms
Internet Control Message Protocol (ICMP)

Supported Platforms
Precision Time Protocol (PTP)

Clock clients: Automatic client
A clock client is the remote PTP host, which receives time from the PTP master and is in a slave relationship to the master.
The maximum number of configured clock clients is 512. The clock client is included in the configuration of the master
clock. Three different types of downstream clients are supported. You can configure any combination of these three types
of clients for a given master.For an automatic client, you do not need to configure the exact IP address of the host. Instead,
configure a subnet mask for the automatic client and any host belonging to that subnet can join the master clock through
a unicast negotiation. which is a method by which the announce, synchronization and delay response packet rates are
negotiated between the master and the slave before a Precision Time Protocol (PTP) session is established. To configure
an automatic client, include the clock-client ip-address local-ip-address local-ip-address statement at the [edit protocols
ptp master interface interface-name unicast-mode] hierarchy level. Include the subnet mask of the remote PTP host in
the clock-client ip-address statement and the boundary master clock IP address in the local-ip-address local-ip-address
statement.
Supported Platforms
Clock clients: Manual client

of clients for a given master. When you configure a manual client, the client immediately receives announce and
synchronization packets. To configure a manual client, include the manual statement at the [edit protocols ptp master
interface interface-name unicast-mode clock-client ip-address local-ip-address local-ip-address] hierarchy level.
Supported Platforms

Clock clients: Secure client

of clients for a given master. For a secure client, you must configure a full and exact IP address, after which it joins the
master clock through unicast negotiation. To configure a secure client, include the clock-client ip-address statement with
the exact IP address of the PTP host at the [edit protocols ptp master interface interface-name unicast-mode] hierarchy
level.
Supported Platforms
IEEE 1588v2 boundary clock

The boundary clock has multiple network connections and can act as a source (master) or destination (slave) for
synchronization messages. The boundary clock intercepts and processes all Precision Time Protocol (PTP) messages and
passes all other traffic. The best master clock algorithm (BMCA) is used by the boundary clock to select the best clock
from configured acceptable masters. On ACX Series routers, you can configure a port as a boundary slave or as a boundary
master. To configure a boundary clock, include the boundary statement at the [edit protocols ptp clock-mode] hierarchy
level.
Supported Platforms
PHY timestamping for grandmaster clock

Junos OS supports timestamping at the physical layer, also known as PHY timestamping, for the grandmaster clock. To
enable PHY timestamping on ACX Series routers, configure clock mode (ordinary clock, boundary clock, or grandmaster
clock) along with the transparent-clock statement at the [edit protocols ptp] hierarchy level.
Supported Platforms
ACX1000 Junos OS
12.3X54-D20

PTP master boundary clock

The Precision Time Protocol (PTP) master clock sends unicast packets over UDP to the clients (ordinary and boundary)
so they can establish their relative time offset from this master clock. To configure a master clock, include the master
statement and options at the [edit protocols ptp] hierarchy level. On an ACX Series router, you can configure up to 512
remote clock clients.
Supported Platforms
PTP over Ethernet

Precision Time Protocol (PTP) is supported over IEEE 802.3 or Ethernet links on ACX Series routers. This functionality is
supported in compliance with the IEEE 1588-2008 specification. PTP over Ethernet enables effective implementation of
packet-based technology that enables the operator to deliver synchronization services on packet-based mobile backhaul
networks that are configured in Ethernet rings. Deployment of PTP at every hop in an Ethernet ring using the Ethernet
encapsulation method enables robust, redundant, and high-performance topologies to be created that enables a
highly-precise time and phase synchronization to be obtained.
For the base station vendors that support only packet interfaces using Ethernet encapsulation for PTP packets for time
and phase synchronization, you can configure any node (an ACX Series router) that is directly connected to base station
to use the Ethernet encapsulation method for PTP on a master port to support a packet-based timing capability. A master
node is the router that functions as the PTP server where the master clock is located and a slave node is the router that
functions as the PTP client where the slave clock is located. PTP over Ethernet encapsulation also facilitates an easier,
optimal network deployment model than PTP over IPv4. Because PTP over Ethernet uses multicast addresses, the slave
node automatically learns about the master nodes in the network. Also, the slave node is able to immediately receive the
multicast messages from the master node and can begin sending messages to the master node without the need for any
provisioning configuration.
Supported Platforms
ACX1000 Junos OS
12.3X51-D10
PTP over User Datagram Protocol (UDP) over IPv4

The IEEE1588v2 standard specifies different transport protocols for carrying PTP packets. For example, PTP over Ethernet,
PTP over UDP over IPV4, and PTP over UDP over IPV6. The ACX Series routers support PTP over UDP over IPV4.
Supported Platforms

PTP slave performance metrics

Precision Time Protocol (PTP) slave devices are used to provide frequency and time distribution throughout large networks.
On ACX Series routers, PTP slave devices calculate performance metrics based on standard PTP timing messages. These
performance metrics include both inbound and outbound packet delay and jitter between the PTP slave and master.
Metrics are exported every 15 minutes to Junos Space. Performance metrics are also stored locally on the ACX Series
router and can be accessed with the show ptp performance-monitor [short-term | long-term] command.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Precision Time Protocol (PTP)

PTP synchronizes clocks between nodes in a network, thereby enabling the distribution of an accurate clock over a
packet-switched network. This synchronization is achieved through packets that are transmitted and received in a session
between a master clock and a slave clock.
Supported Platforms
Precision Time Protocol (PTP) over integrated routing and bridging (IRB) interfaces
Precision Time Protocol (PTP) over integrated routing and bridging (IRB) is supported. In prior releases, PTP was supported
over physical Ethernet interfaces only.
Supported Platforms
Precision Timing Protocol (PTP) - Ordinary clock (slave only)

The PTP ordinary slave clock estimates time offset from the PTP master clock and tries to align its own time and frequency
with that of the master clock. ACX Series routers support the IEEE 1588v2 compliant ordinary slave clock. To configure
a slave clock, include the slave statement and options at the [edit protocols ptp] hierarchy level.
Supported Platforms

Timing–1588-v2, 1588-2008–slave clock

Supported Platforms
RFC 2544-based benchmarking tests for Layer 2 and Layer 3 Ethernet services
Ethernet loopback support for RFC 2544-based benchmarking test
Junos OS supports configuring Ethernet loopback for performing the RFC 2544-based benchmarking test. Ethernet
loopback can be used for verifying the connectivity and identifying or isolating faults in a network. This feature can be
used for performance measurements where packets are looped back to measuring device. Ethernet loopback is supported
in the egress user-to-network interface (UNI) direction for a bridge family configuration.
Supported Platforms
ACX1000 Junos OS
12.3X54-D20
RFC 2544-based benchmarking tests for Layer 2 and Layer 3 Ethernet services
Junos OS supports RFC 2544 benchmarking tests to measure performance characteristics and efficiency of the routers,
such as throughput, bursty frames, frame loss, and latency.
• You can configure RFC 2544 tests on the following underlying services:
• Between two IPv4 endpoints.
• Between two user-to-network interfaces (UNIs) of Ethernet Virtual Connection (EVC), Ethernet Private Line (EPL, also
called E-LINE), Ethernet Virtual Private Line (EVPL), EVC (EPL, EVPL).
RFC 2544 tests are supported only in the egress direction or the user-to-network interface (UNI) direction of Ethernet
line or LAN service parameters in a bridge domain between two routers for unicast traffic.
You can run RFC 2544 benchmarking inet tests on Layer 3 VPN or virtual router.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10

Synchronous Ethernet (SyncE)

Automatic clock selection
In automatic clock selection, the system chooses up to two best upstream clock sources. The system then uses the clock
recovered from one of the sources to lock the chassis clock. If an upstream clock with acceptable good quality is not
available or if the system is configured in free-run mode, the system uses the internal oscillator.
Supported Platforms
Clock Source Selection Algorithm

Supported Platforms
Combined operation of Synchronous Ethernet and Precision Time Protocol or hybrid mode
The combined operation of Synchronous Ethernet and Precision Time Protocol (PTP) is also known as hybrid mode. In
hybrid mode, the synchronous Ethernet equipment clock (EEC) on the router derives the frequency from Synchronous
Ethernet and the phase and time of day from PTP. Time synchronization includes both phase synchronization and frequency
synchronization.
Synchronous Ethernet supports hop-by-hop frequency transfer, where all interfaces on the trail must support Synchronous
Ethernet. PTP (also known as IEEE 1588v2) synchronizes clocks between nodes in a network, thereby enabling the
distribution of an accurate clock over a packet-switched network.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Configured or received clock selection

Supported Platforms

Synchronous Ethernet (SyncE)

Supports the Ethernet synchronization messaging channel (ESMC), G.8264-like clock selection mechanism, and external
clocking on MX80 routers and MX Series routers with MPCs.
Supported Platforms
Synchronous Ethernet clock synchronization

Synchronous Ethernet clock synchronization is supported. This feature enables the selection of the best timing source
based upon the Synchronization Status Message (SSM) TLV carried in the Ethernet Synchronization Message Channel
(ESMC), specified in ITU-T G.8264. This selection process is used when primary and secondary clock sources are not
already configured by the user.
Supported Platforms
Class of Service (CoS)
Classification
Behavior aggregate (BA) Classifiers: 802.1p
Supported Platforms
Behavior aggregate (BA) Classifiers: DSCP

Supported Platforms
Behavior aggregate (BA) Classifiers: DSCP IPv6

Supported Platforms
ACX1000 Junos OS
12.3X54-D15

Features Supported on ACX1000 in Junos OS 18.4R1 Class of Service (CoS)
Behavior aggregate (BA) Classifiers: EXP

If one enables the MPLS protocol family on a logical interface, the default MPLS EXP classifier is automatically applied to
that logical interface. The default MPLS classifier maps EXP bits to forwarding classes and loss priorities.
Supported Platforms
Behavior aggregate (BA) Classifiers: IEEE 802.1ad

Rewrite rules at the physical interface level support the IEEE 802.1ad bit value. The IEEE 802.1ad classifier uses IEEE
802.1p and DEI bits together. On logical interfaces, only fixed classifiers are supported.
You can configure either IEEE 802.1p or IEEE 802.1ad classifiers at the physical interface level. You can define the
following features:
• IEEE 802.1ad classifiers (inner or outer)
• IEEE 802.1ad rewrites (outer)
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Experimental (EXP) bits

Supported Platforms
Fixed classification
One can configure fixed classification on a logical interface by specifying a forwarding class to be applied to all packets
received by the logical interface, regardless of the packet contents.
Supported Platforms
Physical interface-based classifiers

Supported Platforms

CoS on Interfaces
CoS for PPP and MLPPP Interfaces
CoS functionalities are supported on PPP and MLPPP interfaces. Up to four forwarding classes and four queues are
supported per logical interface for PPP and MLPPP packets.
The following restrictions apply when you configure CoS on PPP and MLPPP interfaces on ACX Series routers:
• For interfaces with PPP encapsulation, you can configure interfaces to support only the IPv4, Internet Protocol Control
Protocol (IPCP), PPP Challenge Handshake Authentication Protocol (CHAP), and Password Authentication Protocol (PAP)
applications.
• Drop timeout is not supported.
• Loss of traffic occurs during a change of scheduling configuration; you cannot modify scheduling attributes instantaneously.
• Buffer size is calculated in terms of number of packets, with 256 bytes considered as the average packet size.
• Only two loss priority levels, namely low and high, are supported.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Eight queues per port

Supported Platforms
TDM and ATM class-of-service (CoS)

Junos OS CoS enables you to classify traffic into classes and offer various levels of throughput and packet loss when
congestion occurs. Fixed classification is supported on the ACX Series routers. To configure fixed classification, include
the forwarding-class statement at the [edit class-of-service interfaces interface-name unit logical-unit-number] hierarchy
level.
Supported Platforms
Congestion Management
Weighted random early detection (WRED) tail-drop profiles
Weighted random early detection (WRED) for CoS is a congestion-management feature that drops overflow packets
when queue buffers become full or begin to overflow.
Supported Platforms

Forwarding classes
Up to 8 forwarding classes with one-to-one mapping to output queues
Allows you map up to eight forwarding classes with eight CoS queues.
Supported Platforms
Policing/Rate limiting
Per-queue committed information rate (CIR) and peak information rate (PIR)
Supported Platforms
Physical interface policers

Enables to define a policer for a physical interface and reference the policer in one or more firewall filters, which can then
be applied to the physical interface. This feature enables to configure a single aggregate policer for a physical interface
that can be applied to all the logical interfaces and traffic families configured on the physical interface.
Supported Platforms
Policing - per family

Supported Platforms
Policing - per logical interface

Supported Platforms
Policing/Rate limiting
Supported Platforms

SrTCM (color aware, color blind)

Supported Platforms
Tricolor marking policers

By default, TCM is enabled. On the T1600 Enhanced Scaling FPC4 (T1600-FPC4-ES), the [TCP,PLP] bits are used when
TCM is enabled to identify four drop profiles, whereas on the T4000 Type 5 FPC (T4000-FPC5-3D), only [PLP1,PLP0]
bits are used.
Supported Platforms
Two-rate tricolor marking

Enables you to configure two-rate tricolor marking (trTCM) as defined in RFC 2698, A Two Rate Three Color Marker.
TCM extends the functionality of CoS traffic policing by providing three levels of drop priority instead of two. This capability
enables you to provision more granular service-level agreements (SLAs) across the Differentiated Services (DiffServ)
domain. You configure TCM by defining tricolor marking policers, and three levels of packet loss priority (PLP) for classifiers,
rewrite rules, random early discard (RED) drop profiles, and firewall filters. The color of a packet, as used or set by a tricolor
marking policer, corresponds to the packet’s drop precedence (loss priority or PLP).
Supported Platforms
Rewrite Rules
802.1p Rewrite
Supported Platforms
DSCP IPv6 rewrite

Supported Platforms
ACX1000 Junos OS
12.3X54-D15

Differentiated Services Code Point (DSCP) rewrite

Rewrite upstream or downstream traffic and both inner and outer packet
Supported Platforms
EXP rewriting
One can now configure rewrite rules on the egress provider-edge (PE) switch to alter the CoS settings of the packets.
Rewrite rules set the value of the CoS bits within the packet’s header. Each rewrite rule reads the current forwarding
class and loss priority information associated with the packet, locates the chosen CoS value from a table, and writes this
CoS value into the packet header.
Supported Platforms
Rewrite MPLS and DSCP to different values

Supported Platforms
Scheduling
Configuring the shared buffer size
Junos OS enables you to control the amount of shared packet buffer a given queue can consume. Using this feature, you
can ensure that important queues have a higher chance of using the shared buffers than by not so important queues. To
achieve this, you can configure lower values for shared-buffer maximum CLI statement for the not so important queues,
and higher values for the shared-buffer maximum CLI statement for the important queues.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Internal buffer of 2 MB with per-egress queue buffer management

Supported Platforms

Scheduling with two different priorities

Supported Platforms
Shaping
Port shaping
Port shaping and queue shaping can be used to manage excess traffic and to avoid congestion. Port shaping defines the
maximum bandwidth allocated to a port.
Supported Platforms
Strict priority queuing or Low Latency Queuing (LLQ)

Multiple strict-priority queues per port
Supported Platforms
Priority queuing
Supported Platforms
Strict priority queuing or Low Latency Queuing (LLQ)

Strict priority queuing, or low latency queuing (LLQ), is a class-of-service (CoS) feature used to more quickly forward
certain types or classes of traffic, typically delay-sensitive traffic like voice or video, through a device.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Ethernet Switching and Bridging
Ethernet Switching and Bridging
Bridge domains and virtual switching

Bridge domains and virtual switching
Add support for Layer 2 bridge domains and virtual switches. Like a VLAN, a bridge domain spans one or more ports on
multiple devices and can be created within a user-created virtual switch or the default virtual switch. Additionally, a virtual
switch can run one of the spanning-tree protocols (see the subsequent item titled "Spanning-tree protocols support for
Layer 2 bridging and VPLS") and spanning-tree bridge protocol data units (BPDUs) can be tunneled.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Disabling local switching in bridge domains

In a bridge domain, when a frame is received from a customer edge (CE) interface, it is flooded to the other CE interfaces
and all of the provider edge (PE) interfaces if the destination MAC address is not learned or if the frame is either broadcast
or multicast.
To prevent CE devices from communicating directly include the no-local-switching statement at the [edit bridge-domains
bridge-domain-name] hierarchy level. Configure the logical interfaces in the bridge domain as core-facing (PE interfaces)
by including the core-facing statement at the [edit interfaces interface-name unit logical-unit-number family family]
hierarchy level to specify that the VLAN is physically connected to a core-facing ISP router and ensure that the network
does not improperly treat the interface as a client interface. When local switching is disabled, traffic from one CE interface
is not forwarded to another CE interface.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Host protection
Host protection
Supported Platforms

IEEE 802.1ah PBB

E-LINE and E-LAN services in PBB
To support IEEE 802.1ah provider backbone bridges (PBB), E-LINE (point-to-point) or E-LAN (point-to-multipoint) services
can be configured.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Integrated routing and bridging (IRB)

Integrated routing and bridging (IRB)
Adds support for integrated routing and bridging (IRB), which enables routing of Layer 3 traffic between a bridge domain
or VPLS routing instance and another routed interface.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Layer 2 protocol tunneling (L2PT)

Layer 2 protocol tunneling (L2PT)
This feature allows Layer 2 protocol data units to be tunneled through a network, providing a single spanning-tree domain
for subscribers across a service provider network.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Multiple Spanning Tree Protocol (MSTP)

Multiple Spanning Tree Protocol (MSTP)
EX Series switches provide Layer 2 loop prevention using a spanning-tree protocol. MSTP extends STP and RSTP
functionality by mapping multiple independent spanning-tree instances onto one physical topology.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10

Q-in-Q
Q-in-Q
Q-in-Q tunneling allows service providers on Ethernet access networks to extend a Layer 2 Ethernet connection between
two customer sites. Using Q-in-Q tunneling, providers can also segregate or bundle customer traffic into fewer VLANs
or different VLANs by adding another layer of 802.1Q tags. Q-in-Q tunneling is useful when customers have overlapping
VLAN IDs, because the customer’s 802.1Q (dot1Q) VLAN tags are prepended by the service VLAN (S-VLAN) tag.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Rapid Spanning Tree Protocol (RSTP)

Rapid Spanning Tree Protocol (RSTP)
EX Series switches provide Layer 2 loop prevention using a spanning-tree protocol. Rapid Spanning Tree Protocol (RSTP)
is an evolution of the STP IEEE 802.1D protocol designed to provide faster spanning-tree re-convergence after a switch
port, switch, or LAN failure.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Spanning Tree Protocol (STP)

BPDU protection for spanning-tree protocols
Bridge protocol data unit (BPDU) protection protects spanning-tree switch interfaces from unnnecessary updates by
blocking BPDUs from unwanted sources.
Supported Platforms
Loop protection for spanning-tree protocols

Loop protection for spanning-tree protocols increases the efficiency of STP, RSTP, and MSTP by preventing ports from
moving into a forwarding state that would result in a network loop.
Supported Platforms

Root protection for spanning-tree protocols

Root protection for spanning-tree protocols allows network administrators to manually enforce the root bridge placement
in a network using a spanning-tree protocol.
Supported Platforms
Spanning Tree Protocol (STP)

EX Series switches provide Layer 2 loop prevention using a spanning-tree protocol. Spanning Tree Protocol (STP) is a
protocol designed to intelligently avoid loops in a network by creating a tree topology (spanning-tree).
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
VLAN Spanning Tree Protocol (VSTP)

VLAN Spanning Tree Protocol (VSTP)
The VLAN Spanning Tree Protocol (VSTP) maintains a separate spanning-tree instance for each VLAN and is compatible
with the Per-VLAN Spanning Tree Plus (PVST+) and Rapid-PVST+ protocols supported on Cisco Systems routers and
switches. VLAN Spanning Tree Protocol (VSTP) is a protocol designed to to optimize network usage in small networks
with a limited number of VLANs.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10

Features Supported on ACX1000 in Junos OS 18.4R1 Forwarding Options
Forwarding Options
Equal-cost multipath (ECMP) flow-based forwarding

Equal-cost multipath (ECMP) flow-based forwarding
An equal-cost multipath (ECMP) set is formed when the routing table contains multiple next-hop addresses for the same
destination with equal cost. (Routes of equal cost have the same preference and metric values.) If there is an ECMP set
for the active route, the Junos OS software uses a hash algorithm to choose one of the next-hop addresses in the ECMP
set to install in the forwarding table.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Exception handling
Exception handling
All basic exception handling features are supported, including but not limited to option packets, TTL expiry, MTU exceeded
condition, redirect condition, and so on. In addition, Internet Control Message Protocol (ICMP) is supported to respond
to various exception conditions.
Supported Platforms
IP fragmentation
IP fragmentation
Fragmentation is in software and the number of packets fragmented is rate limited.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Forwarding Options
Port Mirroring
Local port mirroring
You can use port mirroring to facilitate analyzing traffic on an EX Series switch on a packet level. You can use port mirroring
as part of monitoring switch traffic for such purposes as enforcing policies concerning network usage and file sharing,
and identifying sources of problems on your network by locating abnormal or heavy bandwidth usage from particular
stations or applications.
Supported Platforms
Storm Control
Storm Control
Storm control is now supported on ACX Series routers. Storm control is only applicable at the IFD level for ACX Series.
When a traffic storm is seen on the interface configured for storm control, the default action is to drop the packets
exceeding the configured bandwidth. No event is generated as part of this. Storm control is not enabled on the interface
by default.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
High Availability
Link aggregation groups (LAGs)

Link aggregation groups (LAGs)
IEEE 802.3ad link aggregation enables you to group Ethernet interfaces to form a single link layer interface, also known
as a link aggregation group (LAG) or bundle.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10

Features Supported on ACX1000 in Junos OS 18.4R1 High Availability
Virtual Router Redundancy Protocol (VRRP)

Virtual Router Redundancy Protocol (VRRP)
This feature introduces VRRP for IPv4 unicast traffic. VRRP increases network resiliency by providing redundant paths
within a LAN. If a link fails on a VRRP platform configured as master, one of the backup routing platforms becomes the
new master, providing a virtual default routing platform and enabling traffic on the LAN to be routed without relying on
a single routing platform.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Virtual Router Redundancy Protocol version 2

Junos OS supports Virtual Router Redundancy Protocol (VRRP) version 2 configuration. VRRP enables hosts on a LAN to
make use of redundant routers on that LAN without requiring more than the static configuration of a single default route
on the hosts. Routers running VRRP share the IP address corresponding to the default route configured on the hosts. At
any time, one of the routers running VRRP is the master (active) and the others are backups. If the master fails, one of
the backup routers becomes the new master router, providing a virtual default router and enabling traffic on the LAN to
be routed without relying on a single router. Using VRRP, a backup router can take over a failed default router within a
few seconds. This is done with minimum VRRP traffic and without any interaction with the hosts.
Supported Platforms
IPv6
IPv6 specific
Dual Stacking
Supported Platforms
Dynamic routes distribution through IS-IS and OSPF

Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 IPv6
IPv6 VPN Provider Edge Routing

Junos OS supports IPv6 VPN Provider Edge Router (6VPE) routing functionality. 6VPE provides IPv6 forwarding over
IPv4-based MPLS network.
Supported Platforms
ACX1000 Junos OS
12.3X54-D15
IPv6 forwarding
Supported Platforms
IPv6 over MPLS (6PE)

Supported Platforms
IPv6 over generic routing encapsulation (GRE) tunnels using IPv4 transport—de-encapsulation support
Supported Platforms
IPv6 over generic routing encapsulation (GRE) tunnels using IPv4 transport—encapsulation support
Supported Platforms
IPv6 static routing

Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 IPv6
Layer 3 VPNs for IPv4 and IPv6 address families

You can configure Layer 3 virtual private network (VPN) routing instances on ACX Series routers at the [edit
routing-instances routing-instance-name protocols] hierarchy level for unicast IPv4,
multicast IPv4, unicast IPv6, and multicast IPv6 address families. If you do not explicitly specify the address family in an
IPv4 or an IPv6 environment, the router is configured to exchange unicast IPv4 or unicast IPv6 addresses by default.
Supported Platforms
Path MTU Discovery

This feature introduces support for IPv6 Path MTU Discovery. Path MTU Discovery checks the maximum transmission
unit (MTU) size on a network path between two nodes.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Interfaces
Interfaces
ATM Interface
ATM OAM F4 and F5 cells
ACX Series routers provide Asynchronous Transfer Mode (ATM) support for the following Operations, Administration,
and Maintenance (OAM) fault management cell types
• F4 alarm indication signal (AIS) (end-to-end)
• F4 remote defect indication (RDI) (end-to-end)
• F4 loopback (end-to-end)
• F5 AIS
• F5 RDI
• F5 loopback
ATM OAM is supported on ACX1000, ACX2000, and ACX2100 routers, and on 16-port Channelized E1/T1 Circuit
Emulation MICs on ACX4000 routers.
Junos OS supports the following methods of processing OAM cells that traverse through pseudowires with circuit
cross-connect (CCC) encapsulation:
• Virtual path (VP) pseudowires (CCC encapsulation)
• Port pseudowires (CCC encapsulation)
• Virtual circuit (VC) pseudowires (CCC encapsulation)
For ATM pseudowires, the F4 flow cell is used to manage the VP level. On ACX Series routers with ATM pseudowires
(CCC encapsulation), you can configure OAM F4 cell flows to identify and report virtual path connection (VPC) defects
and failures. Junos OS supports three types of OAM F4 cells in end-to-end F4 flows:
• Virtual path AIS
• Virtual path RDI
• Virtual path loopback
For OAM F4 and F5 cells, IP termination is not supported. Also, Junos OS does not support segment F4 flows, VPC
continuity check, or VP performance management functions.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
ATM PWE3 control word

Supported Platforms

ATM PWE3 support

The new ATM MIC (model number: MIC-3D-8OC3-2OC12-ATM) enables support for ATM Pseudowire Emulation Edge
to Edge (PWE3) on MX Series routers. The MIC is rate-selectable at the following rates: 2 OC12 ports or 8 OC3 ports.
The ATM MIC with SFP is supported on the following MPCs:
• MPC1 Q (MX-MPC1-3D-Q)
• MPC2 Q (MX-MPC2-3D-Q)
• MPC2 EQ (MX-MPC2-3D-EQ)
Supported Platforms
ATM PWE3 via dynamic labels

Supported Platforms
ATM VPI/VCI Swapping

Supported Platforms
ATM idle/unassigned cell suppression

Supported Platforms
ATM policing and shaping

Policing, or rate limiting, is an important component of firewall filters that lets you limit the amount of traffic that passes
into or out of an interface. Shaping uses queuing and scheduling to shape the outgoing traffic. For more information about
supported policing and shaping on the ACX Series routers, see the Firewalls section of these release notes.
Supported Platforms

ATM service categories (CBR, nrt-VBR, UBR) to the UNI

Supported Platforms
ATM support for N to 1 PW Promiscuous mode: 1 PW per port and 1 PW per VPI
Supported Platforms
ATM time-division multiplexing (TDM)

Supported Platforms
Inverse Multiplexing for ATM (IMA)

Defined by the ATM Forum IMA specification version 1.1. IMA is a standardized technology used to transport ATM traffic
over a bundle of T1 and E1 interfaces, also known as an IMA group. Up to eight links per bundle and 16 bundles for PIC
are supported.
Supported Platforms
ACX1000 Junos OS Channelized

12.3X54-D10 OC3/STM1
(Multi-Rate) Circuit
Emulation MIC with
SFP
RFC4717: S6.3 – ATM AAL5 SDU encap

Supported Platforms

Address Resolution Protocol (ARP)

Address Resolution Protocol (ARP)
Supported Platforms
BERT algorithms
BERT algorithms
Supported Platforms
E1/T1
T1 and E1 interfaces time-division multiplexing (TDM)
The ACX1000 has 8 built-in TDM ports. The ACX2000 has 16 built-in TDM ports. T1/E1 mode selection is at the PIC
level. To set the T1/E1 mode, include the framing statement with the t1 or e1 option at the [chassis fpc 0 pic slot-number]
hierarchy level. All ports can be T1 or E1. Mixing T1s and E1s is not supported.
Supported Platforms
T1/E1 channelization
Full channelization is supported. Partitioning is not supported. To configure full channelization, include the no-partition
statement at the [edit interfaces ct1-fpc/pic/port] hierarchy level or at the [edit interfaces ce1-fpc/pic/port] hierarchy
level, depending on the interface type.
Supported Platforms

Encapsulation
Inverse Multiplexing for ATM (IMA) Layer 2 encapsulation
Layer 2 encapsulation for IMA pseudowire initiation and termination on the ACX Series routers is supported. To configure
encapsulation at the logical interface level, include the encapsulation statement with the atm-ccc-cell-relay or
atm-ccc-vc-mux option at the [edit interface interface-name unit logical-unit-number] hierarchy level.
Supported Platforms
MLPPP encapsulation
You configure multilink bundles as logical units or channels on the link services interface lsq-0/0/0. With MLPPP, multilink
bundles are configured as logical units on lsq-0/0/0—for example, lsq-0/0/0.0 and lsq-0/0/0.1. After creating multilink
bundles, you add constituent links to the bundle.
With multilink PPP bundles, you can use PPP Challenge Handshake Authentication Protocol (CHAP) and Password
Authentication Protocol (PAP) for secure transmission over the PPP interfaces.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Point-to-Point Protocol (PPP) encapsulation

Point-to-Point Protocol (PPP) encapsulation provides a standard method for transporting multiprotocol datagrams over
a point-to-point link. PPP uses the High-Speed Data Link Control (HDLC) protocol for its physical interface and provides
a packet-oriented interface for the network-layer protocols.
PPP is supported on the following MICs on ACX Series routers:
• On ACX1000 routers with 8-port built-in T1/E1 TDM MICs.
• On ACX2000 and ACX2100 routers with 16-port built-in T1/E1 TDM MICs.
• On ACX4000 routers with 16-port Channelized E1/T1 Circuit Emulation MICs.
On ACX Series routers, E1, T1, and NxDS0 interfaces support PPP encapsulation.
IP class of service (CoS) is not supported on PPP interfaces. All the traffic is sent to the best effort queue (queue 0) and
CoS code points are not processed. Also, fixed classifiers are not supported. Circuit cross-connect (CCC) version of PPP
(ppp-ccc option) and translational cross-connect (TCC) version of PPP (ppp-tcc option) are not supported for configuration
with the encapsulation statement.
PPP is supported only for IPv4 networks. If you configure PPP encapsulation, you can configure an inet family by including
the family inet statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. inet6 and MPLS
families are not supported on logical interfaces if you configured PPP encapsulation.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10

RFC4717 ATM Encapsulation: S6.1 ATM N to one cell mode (required as per standard)
Supported Platforms
T1/E1 encapsulation (SAToP)

Structure-Agnostic TDM over Packet (SAToP) defined in RFC 4553 is supported. SAToP is used to transport complete
TDM frames across the transport network, creating a smooth migration from legacy TDM to the central office. Traffic is
kept at a constant bit rate of 1.544 Mbps for T1 and 2.048 Mbps plus overhead for E1 interfaces.
Supported Platforms
TDM CESoPSN: CESoPSN encapsulation

The following statements are supported at the [edit interfaces interface-name] hierarchy level :
• ct1-x/y/z partition partition-number timeslots timeslots interface-type ds
• ds-x/y/z:n encapsulation cesopsn
Supported Platforms
Ethernet Local Management Interface (E-LMI)

Ethernet Local Management Interface (E-LMI)
Enables you to configure an MX-series router with ge, xe, or ae interfaces, operating on the provider edge (PE), to send
connectivity status and configuration parameters of Ethernet services available on the customer edge (CE) port.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10

Ethernet OAM
OAM with Layer 2 bridging as a transport mechanism
The following OAM features that use Layer 2 bridging as a transport mechanism are supported: • IEEE 802.3ah LFM—IEEE
802.3ah link fault management (LFM) operates at the physical interface level and the packets are sent using Layer 2
bridging as a transport mechanism.
• Dying-gasp packets—Dying-gasp PDU generation operates at the physical interface level. Dying-gasp packets are sent
through the IEEE 802.3ah LFM-enabled interfaces.
• IEEE 802.1ag and ITU-T Y.1731 protocols on down MEPs—IEEE 802.1ag configuration fault management (CFM) and
ITU-T Y.1731 performance-monitoring OAM protocols, which are used for end-to-end Ethernet services, are supported
only on down maintenance association end points (MEPs). The ITU-T Y.1731 protocol supports delay measurement on
down MEPs but does not support loss measurement on down MEPs.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Ethernet OAM connectivity fault management (CFM)

802.1ag CC monitoring on active and standby pseudowires
Supported Platforms
802.1ag Ethernet OAM connectivity fault management (CFM)

Junos OS supports the IEEE 802.1ag standard for Operation, Administration, and Maintenance (OAM). The IEEE 802.1ag
specification provides for Ethernet connectivity fault management (CFM). CFM monitors Ethernet networks that might
comprise one or more service instances for network-compromising connectivity faults.
Supported Platforms
802.1ag optional type, length, and value (TLV) support

Provides configuration support for the Port Status TLV and the Interface Status TLV on M120, M320, and MX Series
routers.
Supported Platforms

Distinguish each 802.1ag connection by vlan-id

Supported Platforms
Ethernet connectivity fault management (CFM) - Connection protection for Ethernet pseudowires
Fault monitoring using the continuity check protocol. This is a neighbor discovery and health check protocol that discovers
and maintains adjacencies at the VLAN or link level.
Supported Platforms
Ethernet connectivity fault management (CFM) - Path protection for Ethernet pseudowires
Path discovery and fault verification using the linktrace protocol. Similar to IP traceroute, this protocol maps the path
taken to a destination MAC address through one or more bridged networks between the source and destination.
Supported Platforms
Ethernet frame delay measurement (ETH-DM, Y.1731)

Ethernet Delay Measurement (ETH-DM, Y.1731)
Enables to configure on-demand Operations, Administration, and Maintenance (OAM) for measurement of frame delay
and frame delay variation (jitter) in either one-way or two-way mode, gathering frame delay statistics, and is capable of
simultaneous statistics collection from multiple sessions.
Supported Platforms
IEEE 802.1ag and ITU-T Y.1731 OAM protocols on up MEPs

IEEE 802.1ag configuration fault management (CFM) and ITU-T Y.1731 performance-monitoring OAM protocols on up
maintenance association end points (MEPs). CFM OAM protocol is supported on link aggregation group (LAG) or aggregated
Ethernet (AE) interfaces. The ITU-T Y.1731 protocol supports delay measurement on up MEPs but does not support loss
measurement on up MEPs.
Supported Platforms

ITU-T Y.1731 ETH-LM, ETH-SLM, and ETH-DM

You can configure ITU-T Y.1731 standard-compliant Ethernet loss measurement (ETH-LM), Ethernet synthetic loss
measurement (ETH-SLM), and Ethernet delay measurement (ETH-DM) capabilities on aggregated Ethernet (AE) interfaces.
These performance monitoring functionalities are supported on devices, where the same level of support for the Ethernet
services OAM mechanisms as the level of support on non-aggregated Ethernet interfaces is available on AE interfaces.
ETH-DM is supported on MPC3E and MPC4E modules with only software timestamping. ETH-SLM is supported on
MPC3E and MPC4E modules.
Supported Platforms
Ethernet ring protection switching

Ethernet ring protection switching
Loop avoidance protocol for Ethernet rings. Ethernet ring protection switching is responsible for the setup and control
of an Ethernet ring. It helps provide highly reliable Ethernet networks by detecting Ethernet link failures and correcting
the failures in less than 50 ms.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10

Ethernet synthetic loss measurement

Ethernet synthetic loss measurement
You can trigger on-demand and proactive Operations, Administration, and Maintenance (OAM) for measurement of
statistical counter values corresponding to ingress and egress synthetic frames. Frame loss is calculated using synthetic
frames instead of data traffic. These counters maintain a count of transmitted and received synthetic frames and frame
loss between a pair of maintenance association end points (MEPs).
The Junos OS implementation of Ethernet synthetic loss measurement (ETH-SLM) is fully compliant with the ITU-T
Recommendation Y.1731. Junos OS maintains various counters for ETH-SLM PDUs, which can be retrieved at any time
for sessions that are initiated by a certain MEP. You can clear all the ETH-SLM statistics and PDU counters. The ETH-SLM
feature provides the option to perform ETH-SLM for a given 802.1p priority; to set the size of the ETM-SLM protocol
data unit (PDU); and to generate XML output.
You can perform ETH-SLM in on-demand ETH-SLM mode (triggered through the CLI) or in proactive ETH-SLM mode
(triggered by the iterator application). To trigger synthetic frame loss measurement (on-demand mode) and provide a
run-time display of the measurement values, use the monitor ethernet synthetic-loss-measurement (remote-mac-address
| mep mep-id) maintenance-domain md-name maintenance-association ma-name count frame-count wait time priority
802.1p value size xml operational mode command.
Supported Platforms
ACX1000 Junos OS
12.3X51-D10
External and internal loopback

External and internal loopback
Use loopback testing to isolate interface problems. By default, loopback is not configured.
Supported Platforms
Generic routing encapsulation (GRE)

IPv4 over generic routing encapsulation (GRE) tunnels—de-encapsulation support
Supported Platforms

IPv4 over generic routing encapsulation (GRE) tunnels—encapsulation support

Supported Platforms
Keepalives
Supported Platforms
Gigabit Ethernet interface

Autonegotiation on Gigabit Ethernet interfaces
Exchange of the following parameters is supported: speed and duplex mode. Autonegotiation can be enabled or disabled.
When autonegotiation is disabled, the speed has to be explicitly configured to 10–100 Mbps. To configure autonegotiation,
include the auto-negotiation statement at the [edit interfaces interface-name gigether-options] hierarchy level. To disable
the autonegotiation, include the no-auto-negotiation statement at the [edit interfaces interface-name gigether-options]
hierarchy level.
Supported Platforms
Dual-speed Gigabit Ethernet interface

The Gigabit Ethernet ports on the router have the capacity to work as a 1 or 10 Gigabit Ethernet interface, depending
on the type of small form-factor pluggable (SFP) transceiver inserted. When you insert an SFP+ transceiver, the interface
works at the 10 Gigabit speed. When you insert an SFP transceiver, the interface works at the 1 Gigabit speed. Configuration
is not required because the speed is determined automatically based on the type of inserted SFP transceiver. The dual-speed
interface is automatically created with the xe prefix, for example, xe-4/0/0. The same configuration statements are used
for both speeds and CoS parameters are scaled as a percentage of the port speed. To configure a dual-speed Gigabit
Ethernet interface, include the interface xe-fpc/pic/port statement at the [edit interfaces] hierarchy level. To display the
interface speed and other details, issue the show interfaces command.
Supported Platforms

Gigabit Ethernet interface

Supported Platforms
Statistics collection and reporting for Gigabit Ethernet interfaces

For Gigabit Ethernet interfaces, Packet Forwarding Engine statistics are disabled by default. To enable Gigabit Ethernet
interface statistics, you must specifically configure them. To configure Gigabit Ethernet interface statistics, include the
new statistics statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. To display statistics,
issue the show interfaces interface-name (brief-|-extensive) operational mode command.
Supported Platforms
ACX1000 Junos OS
12.3X51-D10
Unicast mode (IPv4 on Gigabit Ethernet interfaces only)

Unicast mode is a user-to-user protocol used to send a datagram to a single recipient. Unicast mode is used for transporting
PTP messages. To configure unicast mode on an interface, include the unicast-mode statement at the [edit protocols ptp
slave interface interface-name] hierarchy level.
Supported Platforms
Global Positioning System (GPS)

Global Positioning System (GPS)
GPS is a navigation aid system that uses signals from satellites to calculate the actual position of a GPS-capable receiver.
These signals are not only used for determining the position of the receiver on Earth but also as a very accurate time
base. There are GPS receivers with 10-MHz clock frequency output synchronized to a GPS satellite. The ACX Series
router has a SubMinature version B (SMB) connector that can take 10-MHz sine-wave input from a GPS receiver. To
configure this 10-MHz clock from a GPS receiver as a candidate clock source for chassis synchronization, include the gps
statement and options at the [edit chassis synchronization source] hierarchy level.
Supported Platforms

IEEE 802.3ah Link Fault Management (LFM)

Dying-gasp PDU generation
Junos OS for ACX Series Universal Access Routers supports the generation of dying-gasp protocol data units (PDUs).
Dying gasp refers to an unrecoverable condition such as a power failure. In this condition, the local peer informs the
remote peer about the failure state. When the remote peer receives a dying-gasp PDU, it takes an action corresponding
to the action profile configured with the link-adjacency-loss event.
ACX Series routers can generate and receive dying-gasp packets. When LFM is configured on an interface, a dying-gasp
PDU is generated for the interface on the following failure conditions:
• Power failure
• Packet Forwarding Engine panic or a crash
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
IEEE 802.3ah Link Fault Management (LFM)

Junos OS allows the Ethernet interfaces on these devices to support the IEEE 802.3ah standard for Operation,
Administration, and Maintenance (OAM) of Ethernet in access networks. The standard defines OAM link fault management
(LFM). One can configure IEEE 802.3ah OAM LFM on point-to-point Ethernet links that are connected either directly or
through Ethernet repeaters. The IEEE 802.3ah standard meets the requirement for OAM capabilities as Ethernet moves
from being solely an enterprise technology to a WAN and access technology, and the standard remains backward-compatible
with existing Ethernet technology.
Supported Platforms
Inline service interface

Inline service interface
An inline service interface (si-) is a virtual physical interface that resides on the Packet Forwarding Engine. The si- interface
makes it possible to provide NAT services without a special services PIC.
To configure inline NAT, you define the service interface as a type si- (service-inline) interface. You must also reserve
adequate bandwidth for the inline interface. This enables you to configure both interface and next-hop service sets used
for NAT.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10

Layer 2 control packets

Layer 2 control packets
The forwarding path supports the following types of Layer 2 control packets (excluding Operation, Administration, and
Maintenance (OAM) packets) in both directions, receiving and forwarding: Ethernet control packets—ARP, ISIS, 1588v2,
Ethernet Synchronization Messaging Channel (ESMC).
Supported Platforms
Local loopback
Local loopback
Supported Platforms
Logical tunnels
Logical tunnels
Logical tunnel (lt-) interfaces provide quite different services depending on the host router. On ACX Series routers, logical
tunnel interfaces enable you to connect a bridge domain and a pseudowire.
To create tunnel interfaces, an FPC and the corresponding Packet Forwarding Engine on an ACX Series router must be
configured to be used for tunneling services at the [edit chassis] hierarchy level. The amount of bandwidth reserved for
tunnel services must also be configured.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Loopback interface
Loopback interface
The loopback (local | remote) configuration statement is used to specify whether local or remote loopback is enabled. This
allows you to test the transceiver cable connection from the far end to the retimer interface without changing the cable.
The loopback (local | remote) configuration statement is configured at the [edit interfaces interface-name gigether-options]
hierarchy level.
Supported Platforms

Maximum transmission unit (MTU)

Maximum transmission unit (MTU)
Specify the MTU size for the interface. To configure the MTU, specify the bytes in the mtu statement at the [edit interfaces
interface-name] hierarchy level.
Supported Platforms
Media type selection

Media type selection
You can select the media type (copper or fiber for the 1-Gigabit Ethernet interfaces. To specify the media type, include
the new media-type statement with the copper or fiber option at the [edit interfaces interface-name] hierarchy level.
Media type selection is applicable to ports only in slot 2.
Supported Platforms
Other Features
AAL5 SDU [n-to-1 cell relay]
Supported Platforms
Cell concatenation (1 to 30 cells per packet)

Supported Platforms

Denied packets counter

The show interfaces command for ATM interfaces, show interfaces at-fpc/pic/port extensive supports a new field: denied
packets. The denied packets field displays the number of packets dropped due to VLAN priority deny packets or due to
an error forwarding configuration that might cause a negative frame length, that is, the stripping size is larger than the
packet size.
Supported Platforms
Early Packet Discard

Supported Platforms
Event handling of SFP insertion and removal

When you insert a small form-factor pluggable transceiver (SFP), the port needs to be configured with the correct speed
for that interface (Gigabit Ethernet or 10-Gigabit Ethernet).
Supported Platforms
Explicit disabling of the physical interface

Disable a physical interface by effectively unconfiguring it. To disable an interface, include the disable statement at the
[edit interfaces interface-name ] hierarchy level.
Supported Platforms
Input policing per VC

Supported Platforms

MAP ATM service categories to PW EXP bits

Supported Platforms
PIM and IGMP in global domain

Protocol Independent Multicast (PIM) and Internet Group Management Protocol (IGMP) messages for multicast data
delivery are supported. ACX Series routers are used as a leaf in the multicast distribution tree so that subscribers in the
global domain can directly connect to the ACX Series routers through IPv4 interfaces. ACX Series routers can also be
used as a branch point in the tree so that they are connected to other downstream ACX Series or MX Series routers and
send multicast data according to the membership established through the PIM or IGMP messaging.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Packet/byte counters per VP and VC

Most packet-level and byte-level statistics for various entities in the forwarding path available in Junos OS are supported.
The following counters and statistics are supported:
- Ingress and egress packet and byte counters for logical interfaces, Ethernet pseudowires, and MPLS transit label-switched
paths.
- Discard packets counter for system-wide global Packet Forwarding Engine statistics.
Supported Platforms
Remote fault notification for 10-Gigabit Ethernet interfaces

Notifies each end of a connection of the failure at that end. When the failure is identified, the link is brought down and
the LED light is turned off. This feature is not user configured.
Supported Platforms
VC output shaping
Supported Platforms

Structure-aware TDM Circuit Emulation Service over Packet-Switched Network (CESoPSN)

Structure-aware TDM Circuit Emulation Service over Packet-Switched Network (CESoPSN)
Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)
is a method of en-capsulating TDM signals into CESoPSN packets, and in the reverse direction, decapsulating CESoPSN
packets back into TDM signals also, referred to as Interworking Function (IWF).
Supported Platforms
TDM CESoPSN: CESoPSN options

The following statements are supported at the [edit interfaces
interface-name cesopsn-options] hierarchy level
• excessive-packet-loss-rate (sample-period milliseconds)
• idle-pattern pattern
• jitter-buffer-latency milliseconds
• jitter-buffer-packets packets
• packetization-latency microseconds
Supported Platforms
TDM CESoPSN: CESoPSN pseudowires

CESoPSN pseudowires are configured on the logical interface, not on the physical interface. So the unit logical-unit-number
statement must be included in the configuration at the [edit interfaces interface name hierarchy level. When you include
the unit logical-unit-number statement, Circuit Cross Connect (CCC) for the logical interface is created automatically.
Supported Platforms

TDM CESoPSN: Channelization up to the ds0 level

The following numbers of NxDS0 pseudowires are supported for 16 T1 and E1 built-in ports and 8 T1 and E1 built-in
ports.
16 T1 and E1 built-in ports support the following number of pseudo-wires:
• Each T1 port can have up to 24 NxDS0 pseudowires, which add up to a total of up to 384 NxDS0 pseudowires.
• Each E1 port can have up to 31 NxDS0 pseudowires, which add up to a total of up to 496 NxDS0 pseudowires.
8 T1 and E1 built-in ports support the following number of pseudo-wires:
• Each T1 port can have up to 24 NxDS0 pseudowires, which add up to a total of up to 192 NxDS0 pseudowires.
• Each E1 port can have up to 31 NxDS0 pseudowires, which add up to a total of up to 248 NxDS0 pseudowires.
Supported Platforms
TDM CESoPSN: Interfaces show commands

The show interfaces interface-name extensive command
is supported for t1, e1, and at interfaces.
Supported Platforms
TDM CESoPSN: Packet latency

The time required to create packets (from 1000 through 8000
microseconds).
Supported Platforms
TDM CESoPSN: Protocol support

All protocols, which support Structure Agnostic TDM over Packet
(SAToP), support CESoPSN NxDS0 interfaces.
Supported Platforms

Time domain reflectometry (TDR)

Time domain reflectometry (TDR)
The time domain reflectometry (TDR) test is used to determine whether a twisted-pair Ethernet cable is faulty.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Timing and synchronization

Timing and synchronization
Supported Platforms
Multicast
IGMP Snooping
IGMP Snooping
Enables to configure general multicast snooping parameters and specific IGMP snooping parameters to allow Layer 2
interfaces to "snoop" Layer 3 protocols for multicast-related information.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Multicast Listener Discovery (MLD)

Multicast Listener Discovery - Version 1 (MLD v1)
The Multicast Listener Discovery (MLD) Protocol manages the membership of hosts and routers in multicast groups. IP
version 6 (IPv6) multicast devices use MLD to learn, for each of their attached physical networks, which groups have
interested listeners.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Multicast
Multicast Listener Discovery - Version 2 (MLD v2)

Supported Platforms
Unicast reverse-path forwarding (URPF)

Enhancements to unicast reverse-path forwarding (uRPF) check
Junos OS supports uRPF check on IRB interfaces and uRPF fail filter configuration on IPv4 and IPv6 interfaces.
Supported Platforms
Unicast reverse-path forwarding (URPF)

Unicast reverse-path forwarding (RPF) helps protect the switch against denial-of-service (DoS) and distributed DDoS
(DDoS) attacks by verifying the unicast source address of each packet that arrives on an ingress interface where unicast
RPF is enabled. It also helps ensure that traffic arriving on ingress interfaces comes from a network source that the
receiving interface can reach.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Multiprotocol Label Switching (MPLS) Applications
Exception packet handling for MPLS

Exception packet handling for MPLS
The following types of exception packet handling are supported:
- Router alert
- Time-to-live (TTL) expiry value
- Virtual circuit connection verification (VCCV)
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Multiprotocol Label Switching (MPLS) Applications
Fast Reroute (FRR)

Fast Reroute (FRR)
Supported Platforms
IP Fast Reroute (FRR) (OSPF, ISIS)

Supported Platforms
Label Distribution Protocol (LDP)

Label Distribution Protocol (LDP)
Supported Platforms
Label Switching Router (LSR)

Label Switching Router (LSR)
A Label Switching Router (LSR) processes label-switched packets and forwards packets based on their labels.
Supported Platforms
Label edge router (LER)

Label edge router (LER)
The ACX Series router processes IPv4 traffic and pseudowire traffic over the MPLS network. The traffic is processed in
both ingress and egress directions. Configuring MPLS on the LER is the same as configuring an LSR.
Supported Platforms

Label-switched paths (LSPs)

Link protection
Link protection helps ensure that traffic traversing a specific interface from one router to another can continue to reach
its destination in the event that this interface fails.
Supported Platforms
Node-link protection
Node-link protection establishes a bypass LSP through a different router altogether.
Supported Platforms
Multiprotocol Label Switching (MPLS)

MPLS OAM
Supported Platforms
MPLS ping and traceroute

The ACX Series routers supports MPLS ping and traceroute to the extent supported by Junos OS. Junos OS partially
supports LSP ping and traceroute commands based on RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data
Plane Failures. However, Junos OS supports this functionality on LSP transit routers and head-end routers only. If a ping
or traceroute command is issued from a router that fully supports RFC 4379, it can propagate correctly on routers running
Junos OS.
Supported Platforms

Pseudowire transport service

A pseudowire carries Layer 1 and Layer 2 information over an IP/MPLS network infrastructure. Ethernet, ATM, and TDM
pseudowires are supported. Only similar endpoints are supported on the ACX Series routers. For example, T1 to T1, ATM
to ATM, and Ethernet to Ethernet
Supported Platforms
Uniform and pipe mode

In an MPLS network, uniform mode is the default. Uniform mode makes all the nodes that a label-switched path (LSP)
traverses visible to nodes outside the LSP tunnel. In contrast, pipe mode acts like a circuit and must be enabled. In pipe
mode, when MPLS packets traverse the network, only the LSP ingress and egress points are visible to nodes that are
outside the LSP tunnel. To configure pipe mode, include the no-propagate-ttl statement at the [edit protocols mpls]
hierarchy level on each router that is in the path of the LSP. The global no-propagate-ttl statement disables time-to-live
(TTL) propagation at the router level and affects all RSVP-signaled or LDP-signaled LSPs. Only the global configuration
of TTL propagation is supported.
Supported Platforms
Pseudowire redundancy
Layer 2 pseudowire redundancy
A redundant pseudowire acts as a backup connection between PE routers and CE devices, maintaining Layer 2 circuits
and services after certain types of failures. Pseudowire redundancy improves the reliability of certain types of networks
(metro, for example) where a single point of failure could interrupt service for multiple customers.
Supported Platforms
Pseudowire redundancy - Hot and cold standby

Hot standby enables swift cutover to the backup or standby pseudowire. Cold standby is the inclusion of the
backup-neighbor statement and the absence of the standby statement in the configuration
Supported Platforms

Pseudowire redundancy - Protect interface

A backup for the protected interface in case of failure. Network traffic uses the primary interface only so long as the
primary interface functions. If the primary interface fails, traffic is switched to the protect interface. To configure the
protect interface, specify the protect-interface statement at the [edit protocols l2circuit local-switching interface
interface-name] hierarchy level.
Supported Platforms
Pseudowire standby
A standby pseudowire can act as a backup connection between PE routers and CE devices, maintaining Layer 2 circuit
and VPLS services after certain types of failures. To configure pseudowire standby, include the backup-neighbor statement
at the [edit protocols l2circuit neighbor address interface interface-name] hierarchy level.
Supported Platforms
Resource Reservation Protocol (RSVP)

Resource Reservation Protocol (RSVP)
Supported Platforms
Static LSPs
Static LSPs
For static label-switched paths (LSPs), one must manually assign labels on all the switches that are part of the LSP (ingress,
transit, and egress). No signaling protocol is needed. Configuring static LSPs is similar to configuring static routes on
individual switches. As with static routes, there is no error reporting, liveliness detection, or statistics reporting.
Supported Platforms

Traffic engineering
Diffserv traffic engineering
Supported Platforms
Path Computation Element Protocol for RSVP-TE

The MPLS RSVP-TE functionality is extended to provide a partial client-side implementation of the stateful Path Computation
Element (PCE) architecture (draft-ietf-pce-stateful-pce). The PCE computes path for the traffic engineered LSPs (TE LSPs)
of ingress routers that have been configured for external control. The ingress router that connects to a PCE is called a
Path Computation Client (PCC). The PCC is configured with the Path Computation Client Protocol (PCEP) (defined in RFC
5440, but limited to the functionality supported on a stateful PCE only) to facilitate external path computing by a PCE.
In this new functionality, the active stateful PCE sets parameters for the PCC's TE LSPs, such as bandwidth, path (ERO),
and priority. The TE LSP parameters configured from the PCC's CLI are overridden by the PCE-provided parameters. The
PCC re-signals the TE LSPs based on the path specified by the PCE. Since the PCE has a global view of the bandwidth
demand in the network and performs external path computationsafter looking up the traffic engineering database, this
feature provides a mechanism for offline control of TE LSPs in the MPLS RSVP TE enabled network. To enable external
path computing by a PCE, include the lsp-external-controller statement on the PCC at the [edit mpls] and [edit mpls lsp
lsp-name] hierarchy levels. To enable PCE to PCC communication, configure pcep on the PCC at the [edit protocols]
hierarchy level.
Supported Platforms
Traffic engineering
Supported Platforms
Network Management and Monitoring
Interface statistics
Drop packet statistics
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Network Management and Monitoring
Interface Passive-monitor-mode
Supported Platforms
Interface byte and packet statistics

Supported Platforms
Interface queue statistics

Supported Platforms
Statistics collection and handling

Port-level input and output error statistics and the logical interface level statistics are collected automatically from the
Packet Forwarding Engine. To display statistics, issue the show interfaces interface-name (brief | extensive) operational
mode command.
Supported Platforms
NETCONF
Adding non-native YANG modules to the Junos OS schema
You can load standard (IETF,OpenConfig) or custom YANG models on devices running Junos OS to add data models that
are not natively supported by Junos OS but can be supported by translation. Doing this enables you to augment the
configuration hierarchies with data models that are customized for your operations. The ability to add data models to a
device is also
beneficial when you want to create device- and vendor-agnostic configuration models that enable the same configuration
to be used on different devices from one or more vendors. You can load YANG modules that add configuration hierarchies
by using the request system yang add operational command.
Supported Platforms

Configuring the ephemeral database using the NETCONF and Junos OS XML protocols
NETCONF and Junos XML protocol client applications can configure the ephemeral configuration database, which is an
alternate configuration database that enables multiple clients to simultaneously load and commit configuration changes
on a device running Junos OS and with significantly greater throughput than when committing data to the candidate
configuration database. Junos OS provides a default instance and up to eight user-defined instances of the ephemeral
configuration database. The device’s active configuration is a merged view of the committed configuration database and
the configuration data in all instances of the ephemeral configuration database. Ephemeral configuration data is volatile
and is deleted upon rebooting the device.
Supported Platforms
Device family and release in Junos OS YANG modules

YANG modules are specific to a device family, and each module’s namespace includes the module name, device family,
and Junos OS release string. Furthermore, each juniper-command module uses its own unique module name as the
module’s prefix. Device families include junos, junos-es, junos-ex, and junos-qfx.
Supported Platforms
Multiple, smaller configuration YANG modules

The YANG module for the Junos OS configuration schema is split into a root configuration module that is augmented by
multiple, smaller modules.The root configuration module comprises the top-level configuration node and any nodes that
are not emitted as separate modules. Separate, smaller modules augment the root configuration module for the different
configuration statement hierarchies. Smaller configuration modules enable YANG tools and utilities to more quickly and
efficiently compile and work with the modules, because they only need to import the modules required for the current
operation.
Supported Platforms

YANG module that defines CLI formatting for RPC output

Juniper Networks provides the junos-extension-odl YANG module. The module contains definitions for Junos OS Output
Definition Language (ODL) statements, which determine the CLI formatting for RPC output when you execute the
operational command corresponding to that RPC in the CLI or when you request the RPC output in text format. You can
use statements in the junos-extension-odl module in custom RPCs to convert the XML output into a more logical and
human-readable representation of the data. The junos-extension-odl module is bound to the namespace URI
http://yang.juniper.net/yang/1.1/jodl and uses the prefix junos-odl
Supported Platforms
YANG module that defines Junos OS operational commands

Juniper Networks provides the juniper-command YANG module, which represents the operational command hierarchy
and collective group of modules that define the remote procedure calls (RPCs) for Junos OS operational mode commands.
You can download Juniper Networks YANG modules from the website, or you can generate the modules by using the
show system schema format yang module juniper-command operational command on the local device. The juniper-command
module is bound to the namespace URI http://yang.juniper.net/yang/1.1/jrpc and uses the prefix jrpc.
Supported Platforms
Simple Network Management Protocol (SNMP)

RMON events, alarms and history
Junos OS supports monitoring routers from remote devices. These values are measured against thresholds and trigger
events when the thresholds are crossed. You configure remote monitoring (RMON) alarm and event entries to monitor
the value of a MIB object.
Supported Platforms

SNMP get and walk management

Junos OS supports SNMP get, get-next, and walk management capabilities for the timing features. These capabilities are
enabled through the PTP MIB and SyncE MIB objects.
You can use the show chassis synchronization extensive, show ptp lock-status detail, show snmp mib get
<MIB-timing-objects>, show snmp mib walk jnxTimingNotfObjects show commands to monitor and troubleshoot the
configuration.
Supported Platforms
ACX1000 Junos OS
12.3X54-D25
SNMP support for Service OAM (SOAM) performance monitoring functions

SNMP supports Service OAM (SOAM) performance monitoring functions that are defined in Technical Specification MEF
17, the Service OAM performance monitoring requirements specified in SOAM-PM, and the Service OAM management
objects specified in Technical Specification MEF 7.1. A new enterprise-specific MIB, SOAM PM MIB, that defines the
management objects for Ethernet services operations, administration, and maintenance for performance monitoring, has
been added and SNMP support is available for the MIB objects defined in Technical Specification MEF 36.
Supported Platforms
SNMP support for the timing feature

SNMP supports the timing feature. Currently, SNMP support is limited to defect and event notifications through SNMP
traps. A new enterprise-specific MIB, Timing Feature Defect/Event Notification MIB, has been added to monitor the
operation of PTP clocks within the network. The trap notifications are disabled by default. To enable trap notifications
for the timing feature, include the timing-event statement at the [edit snmp trap-group trap-group object categories]
hierarchy level to enable SNMP trap notifications for timing events and defects.
Supported Platforms
ACX1000 Junos OS
12.3X54-D25
Simple Network Management Protocol (SNMP)

SNMP enables the monitoring of network devices from a central location.
Supported Platforms

Simple Network Management Protocol (SNMP) Management Information Base (MIB) and Traps
Juniper Networks Enterprise-Specific MIBs
Supported Platforms
Standard SNMP MIBs

Supported Platforms
Traceroute
Traceroute
Supported Platforms
Network Security
IP and MAC address validation

IP and MAC address validation
This feature enables the router to validate that received packets contain a trusted IP source and an Ethernet MAC source
address. Configuring MAC address validation can provide additional validation when subscribers access billable services.
MAC address validation provides additional security by enabling the router to drop packets that do not match, such as
packets with spoofed addresses.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10

Features Supported on ACX1000 in Junos OS 18.4R1 Network Security
Network Address Translation (NAT)

4096 network address or port translations
Junos OS supports up to 4096 network address or port translations at a time.
Supported Platforms
ACX1000 Junos OS
12.3X54-D20
Routing Options
Bidirectional Forwarding Detection (BFD)

BFD support for VCCV
Bidirectional Forwarding Detection (BFD) support for virtual circuit connection verification (VCCV) allows you to configure
a control channel for a pseudowire, in addition to the corresponding operations and management functions to be used
over that control channel.
Supported Platforms
Bidirectional Forwarding Detection (BFD)

Provides millisecond-level detection of changes in the forwarding plane for the routing protocols.
Supported Platforms
Static routes
Static routes
Static routes are routes that are manually configured and entered into the routing table.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Routing Policies and Firewall Filters
Routing Policies and Firewall Filters
Filter-based forwarding (FBF)

Filter-based forwarding for routing instances
For IPv4 traffic only, you can use stateless firewall filters in routing instances to control how packets travel in a network.
This is called filter-based forwarding. You can define a firewall filtering term that directs matching packets to a specified
routing instance. This type of filtering can be configured to route specific types of traffic through a firewall or other
security device before the traffic continues on its path.
Supported Platforms
Firewall Filters
Dynamic allocation of TCAM memory to firewall filters
The dynamic allocation of the shared space ternary content addressable memory (TCAM) allows TCAM to be used
dynamically to support firewall filters.
Supported Platforms
ACX1000 Junos OS
12.3X54-D20
Enhancements to support log and syslog firewall filter actions

Junos OS supports log and syslog firewall filter actions in ingress and egress directions for family inet and family bridge
protocol families.
The following limitations apply:
• Broadcast, unknown unicast, and multicast (BUM) traffic is not logged for family bridge and family inet filters in egress
direction.
• For egress log and syslog actions, DSCP, TTL, and IEEE 802.1p bits are matched based on ingress values.
• For familyinet, the log and syslog filter actions do not work at egress if a packet is forwarded through the default route
entry to egress.
• For family bridge, the log and syslog filter actions do not work at egress if the filter term contains user-vlan-id,
user-vlan-pri, and user-vlan-dei match conditions.
• For family bridge and family inet, if a packet hits log or syslog actions on both the ingress and egress directions, only
one log and one syslog message are recorded.
• For family inet, if a packet hits reject action on ingress, the packet is not logged on the egress filter action.
Supported Platforms

Firewall Filters
Firewall filters provide rules that define whether to permit, deny, or forward packets that are transiting an interface on
an EX Series switch from a source address to a destination address. Policing, or rate limiting, is an important component
of firewall filters that lets you control the amount of traffic that enters an interface.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Firewall filters - family ccc/any

Supported Platforms
Firewall filters - family inet

Supported Platforms
Firewall filters on loopback interface

This feature allows firewall filters to be configured on loopback interfaces. Firewall filters provide rules that define whether
to permit, deny, or forward packets that are transiting an interface on an EX Series switch from a source address to a
destination address.
Supported Platforms
Standard Firewall Filter Match Conditions for MPLS Traffic

Supported Platforms

Forwarding table filter

Forwarding table filters for routing instances
Forwarding table filter is a mechanism by which all the packets forwarded by a certain forwarding table are subjected to
filtering and if a packet matches the filter condition, the configured action is applied on the packet. You can use the
forwarding table filter mech-anism to apply a filter on all interfaces associated with a single rout-ing instance with a simple
configuration.You can apply a forwarding table filter to a routing instance of type forwarding and also to the default
routing instance inet.0.
Supported Platforms
Hierarchical policer
Hierarchical policer
This feature is useful in provider edge applications that use aggregate policing for general traffic and when applying a
separate policer for premium traffic on a logical or physical interface.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Routing Protocols
Border Gateway Protocol (BGP)

BGP Prefix Independent Convergence for inet
BGP Prefix Independent Convergence (PIC), which was initially supported for Layer 3 VPN routers, is extended to BGP
with multiple routes in the global tables such as inet and inet6 unicast, and inet and inet6 labeled unicast. When the BGP
PIC feature is enabled on a router, BGP installs to the Packet Forwarding Engine the second best path in addition to the
calculated best path to a destination. When an IGP loses reachability to a prefix, the router uses this backup path to
minimize traffic loss until the global convergence through the BGP is resolved, thereby drastically reducing the outage
duration.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Routing Protocols
Multiprotocol Border Gateway Protocol (MBGP)

BGP is an exterior gateway protocol (EGP) that is used to exchange routing information among routers in different
autonomous systems (ASs). BGP only supports IPv4 unicast traffic; Multiprotocol BGP (MBGP) extensions enable BGP
to support unicast and multicast traffic for IPv4 and IP version 6 (IPv6). This feature introduces MBGP support for IPv4
unicast traffic.
Supported Platforms
Intermediate System-to-Intermediate System (IS-IS)

Intermediate System-to-Intermediate System (IS-IS)
IS-IS protocol is an interior gateway protocol (IGP) that uses link-state information to make routing decisions.
Supported Platforms
Neighbor Discovery Protocol

Neighbor Discovery Protocol (NDP)
This feature introduces the neighbor discovery protocol for IPv6 interfaces. Neighbor discovery is a protocol that allows
different nodes on the same link to advertise their existence to their neighbors, and to learn about the existence of their
neighbors.
Supported Platforms
Open Shortest Path First (OSPF)

Open Shortest Path First (OSPF)
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Services Applications
Services Applications
Dynamic Host Configuration Protocol (DHCP)

DHCP Client
The DHCP server, client and relay features are not supported for SRX and J-series devices, when participating in a chassis
cluster.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
DHCP Server
You can configure a J-series router or interface to act as a Dynamic Host Configuration Protocol (DHCP) server. A DHCP
server can allocate network IP addresses and deliver configuration settings to clients on a Transmission Control Protocol
(TCP)/IP network.
cluster.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
DHCPv6 relay agent

The DHCPv6 relay agent enhances the extended DHCP relay agent by providing DHCP support in an IPv6 network.
DHCPv6 relay agents eliminate the necessity of having a DHCPv6 server on each physical network. An ACX Series router
configured as a DHCPv6 relay agent passes messages between the DHCPv6 client and the DHCPv6 server, similar to
the way a DHCP relay agent supports an IPv4 network.
To configure the DHCPv6 relay agent, include the dhcpv6 statement at the [edit forwarding-options dhcp-relay] hierarchy
level. You can also include the dhcpv6 statement at the [edit routing-instances routing-instance-name forwarding-options]
hierarchy level.
Supported Platforms
ACX1000 Junos OS
12.3X54-D15

Dynamic Host Configuration Protocol (DHCP)

cluster.
Supported Platforms
Extended DHCP relay agent

Enables to configure extended DHCP relay options on the router and to enable the router to function as a DHCP relay
agent. A DHCP relay agent forwards DHCP request and reply packets between a DHCP client on a subscriber's computer
and a DHCP server.
Supported Platforms
ACX1000 Junos OS
12.3X52-D10
Preserving DHCP server subscriber information

Junos OS preserves DHCP server subscriber binding information. A device functioning as a DHCP server stores the
subscriber binding information to a file and when the router reboots, the subscriber information is read from the file and
restored.
Supported Platforms
Real-time performance monitoring (RPM)

Real-time performance monitoring (RPM)
Real-time performance monitoring (RPM) enables you to configure active probes to track and monitor traffic across the
network and to investigate network problems.
Supported Platforms
ACX1000 Junos OS
12.3X51-D10

Two-way active measurement protocol (TWAMP) compliance with RFC 5357

Two-way active measurement protocol (TWAMP) compliance with RFC 5357
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Subscriber Management and Services
Other Subscriber Features

Counters and statistics
Most packet and byte-level statistics for various entities in the forwarding path available in Junos OS are supported. The
following counters and statistics are supported:
• Ingress and egress packet and byte counters for logical interfaces, Ethernet pseudowires, and MPLS transit label-switched
paths.
• Discard packets counter for system wide global Packet Forwarding Engine statistics.
Supported Platforms
ACX1000 Junos OS
12.3X51-D10
System Basics
Network Operating System

Junos OS
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 System Management
System Management
Configuration Management
JSON format for configuration data
You can configure devices running Junos OS using configuration data in JavaScript Object Notation (JSON) format in
addition to the existing text, Junos XML, and Junos OS set command formats. You can load configuration data in JSON
format in the Junos OS CLI by using the load (merge | override | update) json command or from within a NETCONF or
Junos XML protocol session by using the <load-configuration format="json"> operation. You can load JSON configuration
data either from an existing file or as a data stream. Configuration data that is provided as a data stream must be enclosed
in a <configuration-json> element.
Supported Platforms
Control plane DOS prevention

Control plane DOS prevention
Supported Platforms
Dual-root partitioning
Dual-root partitioning
Supported Platforms

Juniper Extension Toolkit for Junos (JET for Junos) provides a modern programmatic interface
for developers of third-party applications
Juniper Extension Toolkit for Junos (JET for Junos) provides a modern programmatic interface for
developers of third-party applications
JET for Junos, an evolution of the Junos SDK, allows customers and partners to build and run applications either directly
on Junos OS devices or off-box. These applications can interact with Junos OS native features. A framework is provided
in the Python language for Python JET for Junos application developers. This framework allows your applications to run
directly on Junos OS devices. JET for Junos is based on Apache Thrift; thus, it also supports multiple languages running
off-box to interact with the same JET for Junos APIs. This gives developers true flexibility to adapt Junos OS devices to
business processes.
Supported Platforms
Memory utilization
Memory utilization
The show chassis routing-engine and the show chassis feb commands can be used to find the memory allocated for each
of the Routing Engine and Packet Forwarding Engine components.
Supported Platforms
Network Time Protocol (NTP)

Network Time Protocol (NTP)
Supported Platforms
Packet Forwarding Engine management

Packet Forwarding Engine management
The request chassis feb restart slot slot-number command is introduced to restart the specified Forwarding Engine Board
(FEB). When you enter this command, you are provided feedback on the status of your request.
Supported Platforms

Scripts (Op scripts, commit scripts, event scripts)

Python language for commit, event, op, and SNMP scripts
You can author commit, event, op, and SNMP scripts in Python on devices that include the Python extensions package
in the software image. Creating automation scripts in Python enables you to take advantage of Python features and
libraries as well as leverage Junos PyEZ APIs supported in Junos PyEZ Release 1.3.1 and earlier releases to perform
operational and configuration tasks on devices running Junos OS. To enable execution of Python automation scripts,
which the root user must own, configure the language python statement at the [edit system scripts] hierarchy level, and
configure the filename for the Python script under the hierarchy level appropriate to that script type. Supported Python
versions include Python 2.7.x.
Supported Platforms
Stylesheet language alternative syntax (SLAX)

SLAX is a language for writing JUNOS commit and operation scripts and is an alternative syntax for the XSLT language.
The XSLT language has an XML-based syntax.
Supported Platforms
Software Installation and Upgrade

Autoinstallation
Autoinstallation is the automatic configuration of a device over the network from a pre-existing configuration file that
you create and store on a configuration server—typically a Trivial File Transfer Protocol (TFTP) server. You can use
autoinstallation to automatically configure new devices and to deploy multiple devices from a central location in the
network.
Supported Platforms
Autoinstallation of a configuration file from a Disk-on-Key device

You can use a Disk-on-Key USB memory stick (“USB key”) to configure the switch, by using a configuration file in either
plain-text format or XML format.
Supported Platforms

Hybrid mode of autoinstallation

The autoinstallation mechanism allows the router to configure itself out-of-the-box with no manual intervention, using
the configuration available on the network, locally through a removable media, or using a combination of both. ACX Series
routers support the retrieval of partial configuration from an external USB storage device plugged into the router’s USB
port during the autoinstallation process. This partial configuration in turn facilitates the network mode of autoinstallation
to retrieve the complete configuration file from the network. This method is called hybrid mode of autoinstallation.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
System snapshot
System snapshot
The request system snapshot command allows you to create a copy of the currently running software on another media—for
example, a universal serial bus (USB) storage device. The system snapshot feature takes a “snapshot” of the files currently
used to run the device—the complete contents of the /config and /var directories, which include the running Juniper
Networks Junos operating system (Junos OS), the active configuration, and the rescue configuration—and copies all of
these files into an alternate memory source. Typically, this command is used prior to the upgrade of the software image
on the dual internal NAND flash device (with the da0s1 or da0s2 slices) or to remedy a bad image, thereby preventing
the bad image from rendering the system useless. A snapshot to another media ensures that the device can boot from
the other media in case the system does not boot up from the current image.
Supported Platforms
Unattended boot mode

Unattended boot mode
Unattended boot mode feature blocks any known methods to get access to the router from CPU reset till Junos OS login
prompt, thereby preventing a user to make any unauthorized changes on the router such as viewing, modifying, or deleting
configuration information.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Virtual Private Networks (VPNs)
Virtual Private Networks (VPNs)
E-LINE
E-LINE
Supported Platforms
Layer 2 Circuits
Control word
The control word is 4 bytes long and is inserted between the Layer 2 protocol data unit (PDU) being transported and the
virtual connection label. To configure the control word, include the (control-word | no-control-word) statement at the
[edit protocols l2circuit neighbor address interface interface-name] hierarchy level.
Supported Platforms
Layer 2 Circuits
Supported Platforms
Layer 3 VPN (L3 VPN)

Support to control traceroute over Layer 3 VPN
In a Layer 3 VPN topology with vrf-table-label configured and multiple customer edge (CE) routers configured in the same
VPN routing and forwarding (VRF) routing instance, when traceroute is performed to a remote provider edge (PE) router
for a CE-facing network, the ICMP time exceeded packet determines the correct IP address as the source address.
To control the traceroute over Layer 3 VPN topology with vrf-table-label configured and multiple CE routers configured
in the same VRF, you can configure allow-l3vpn-traceroute-src-select at the[edit system] hierarchy level that determines
the correct IP source address by reviewing the destination routing instance and destination IP address.
Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Virtual Private Networks (VPNs)
Virtual Private LAN Service (VPLS)

Hierarchical VPLS
Hierarchical LDP-based VPLS requires a full mesh of tunnel LSPs between all the PE routers that participate in the VPLS
service. Using hierarchical connectivity reduces signaling and replication overhead to facilitate large-scale deployments.
In a typical IPTV solution, IPTV sources are in the public domain and the subscribers are in the private VPN domain.
For an efficient delivery of multicast data from the IPTV source to the set-top boxes or to subscribers in the private domain
using the access devices (ACX Series routers in this case), P2MP LSPs and MVPN are necessary. Because VPLS and MVPN
are not supported on ACX routers, an alternative approach is used to achieve hierarchical VPLS (HPVLS) capabilities. The
subscriber devices are connected to a VPLS or a Layer 3 VPN domain on the ACX Series (access) router and they are
configured to import the multicast routes. The support for PIM snooping in Layer 3 interfaces, IGMP snooping in Layer
2 networks, IRB interfaces, and logical tunnel interfaces enables HVPLS support.
Supported Platforms
ACX1000 Junos OS
12.3X54-D10
Virtual private network (VPN)

Edge protection using static VPWS
Supported Platforms
Pseudowire Emulation Edge to Edge [PWE3 (signaled)]

Supported Platforms
Static Ethernet PWs

Supported Platforms

Features Supported on ACX1000 in Junos OS 18.4R1 Virtual private network (VPN)
Copyright © 2019, Juniper Networks, Inc. All rights reserved.
By accessing information contained in this document, you agree that:

- the information you are accessing is confidential to Juniper Networks
- you will not disclose this information to any party outside Juniper Networks
- you are authorized by Juniper Networks to access the information
The information in this document is provided "AS IS", with no warranties of any kind attached to the information. Any reliance
upon the information shall be at the user's own risk. Juniper assumes no liability for the information contained in this document.

Feature List

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Feature List

Încărcat de

Drepturi de autor:

Formate disponibile

ACX1000

Copyright © 2019, Juniper Networks, Inc.

Application Layer Gateways (ALGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Authentication and Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

MAC RADIUS authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Alarms, defects, and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

DMA recovery mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Internet Control Message Protocol (ICMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Precision Time Protocol (PTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Copyright © 2019, Juniper Networks, Inc.

Synchronous Ethernet (SyncE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Class of Service (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Copyright © 2019, Juniper Networks, Inc.

Strict priority queuing or Low Latency Queuing (LLQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Ethernet Switching and Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Bridge domains and virtual switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

IEEE 802.1ah PBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Integrated routing and bridging (IRB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Copyright © 2019, Juniper Networks, Inc.

Multiple Spanning Tree Protocol (MSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Rapid Spanning Tree Protocol (RSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Spanning Tree Protocol (STP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

VLAN Spanning Tree Protocol (VSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Equal-cost multipath (ECMP) flow-based forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Link aggregation groups (LAGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Virtual Router Redundancy Protocol (VRRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Copyright © 2019, Juniper Networks, Inc.

Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Copyright © 2019, Juniper Networks, Inc.

Ethernet Local Management Interface (E-LMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Ethernet OAM connectivity fault management (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Ethernet frame delay measurement (ETH-DM, Y.1731) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Ethernet ring protection switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Ethernet synthetic loss measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

External and internal loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Generic routing encapsulation (GRE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Gigabit Ethernet interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Global Positioning System (GPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Copyright © 2019, Juniper Networks, Inc.

Inline service interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Layer 2 control packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Maximum transmission unit (MTU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Media type selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Structure-aware TDM Circuit Emulation Service over Packet-Switched Network (CESoPSN) . . . . . . . . . . . . . . . 43

Copyright © 2019, Juniper Networks, Inc.

Time domain reflectometry (TDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Timing and synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Multicast Listener Discovery (MLD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Unicast reverse-path forwarding (URPF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Multiprotocol Label Switching (MPLS) Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Exception packet handling for MPLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Fast Reroute (FRR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label Distribution Protocol (LDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label Switching Router (LSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label edge router (LER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Label-switched paths (LSPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Multiprotocol Label Switching (MPLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Copyright © 2019, Juniper Networks, Inc.

Resource Reservation Protocol (RSVP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Network Management and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Simple Network Management Protocol (SNMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Copyright © 2019, Juniper Networks, Inc.

IP and MAC address validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56