Juniper JUNOS OS 10.4 - RELEASE NOTES REV 6, JUNOS OS 10.4 Release Note

Junos®OS 10.4 Release Notes

Release 10.4R2 11 February 2011 Revision 6

These release notes accompany Release 10.4R2 of the Junos operating system (Junos OS). They describe device documentation and known problems with the software. Junos OS runs on all Juniper Networks M Series, MX Series, and T Series routing platforms, SRX Series Services Gateways, J Series Services Routers, and EX Series Ethernet Switches.

You can also find these release notes on the Juniper Networks Junos OS Documentation Web page, which is located at http://www.juniper.net/techpubs/software/junos.

Contents

Junos OS Release Notes for Juniper NetworksM Series Multiservice Edge Routers,

MX Series Ethernet Service Routers, and T Series Core Routers . . . . . . . . . . . . 6

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series

Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Interfaces and Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Junos OS XML API and Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Layer 2 Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

MPLS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

MX Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Routing Policy and Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Services Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Subscriber Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

System Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Changes in Default Behavior and Syntax in Junos OS Release 10.4 for M

Series, MX Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Forwarding and Sampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Interfaces and Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Junos OS XML API and Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

MPLS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Platform and Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

JUNOS OS 10.4 Release Notes

Services Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Subscriber Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

User Interface and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series

Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Current Software Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Previous Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Errata and Changes in Documentation for Junos OS Release 10.4 for M

Series, MX Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Changes to the Junos OS Documentation Set . . . . . . . . . . . . . . . . . . . . . 77

Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Upgrade and Downgrade Instructions for Junos OS Release 10.4 for M Series,

MX Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Basic Procedure for Upgrading to Release 10.4 . . . . . . . . . . . . . . . . . . . . 83

Upgrading a Router with Redundant Routing Engines . . . . . . . . . . . . . . 86

Upgrading Juniper Network Routers Running Draft-Rosen Multicast

VPN to Junos OS Release 10.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Upgrading the Software for a Routing Matrix . . . . . . . . . . . . . . . . . . . . . . 88

Upgrading Using ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Upgrading from Junos OS Release 9.2 or Earlier on a Router Enabled

for Both PIM and NSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Upgrade Policy for Junos OS Extended End-Of-Life Releases . . . . . . . . 90

Downgrade from Release 10.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Junos OS Release Notes for Juniper Networks SRX Series Services Gateways

and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

New Features in Junos OS Release 10.4 for SRX Series Services Gateways

and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Hardware Features—SRX210, SRX220, and SRX240 Services

Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Hardware Features—SRX220 Services Gateway with Power Over

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Hardware Features—SRX1400 Services Gateway . . . . . . . . . . . . . . . . . . 119

Hardware Features—SRX3400 and SRX3600 Services Gateways . . . . 122

Advertising Bandwidth for Neighbors on a Broadcast Link Support . . . . . . . 123

Group VPN Interoperability with Cisco’s GET VPN . . . . . . . . . . . . . . . . . . . . . 123

Changes in Default Behavior and Syntax in Junos OS Release 10.4 for SRX

Series Services Gateways and J Series Services Routers . . . . . . . . . . . . 124

Application Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Application Layer Gateways (ALGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

AppSecure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Chassis Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Command-Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Dynamic VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Flow and Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Integrated Convergence Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Interfaces and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . 133

J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Management and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Multilink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Power over Ethernet (PoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Virtual LANs (VLANs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Wireless LAN (WLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Unsupported CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Accounting-Options Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

AX411 Access Point Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Chassis Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Class-of-Service Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Ethernet-Switching Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Firewall Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Interfaces CLI Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Protocols Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Routing Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Services Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

SNMP Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

System Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

IPv6 and MVPN CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Known Limitations in Junos OS Release 10.4 for SRX Series Services

Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . 148

AppSecure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Chassis Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Command-Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

DOCSIS Mini-PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . 150

Dynamic VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Flow and Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Interfaces and Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . 154

IPv6 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

NetScreen-Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Point-to-Point Protocol over Ethernet (PPPoE) . . . . . . . . . . . . . . . . . . . 156

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Unified Threat Management (UTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

VPNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Wireless LAN (WLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

JUNOS OS 10.4 Release Notes

Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J

Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Outstanding Issues In Junos OS Release 10.4 for SRX Series Services

Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . 158

Resolved Issues in Junos OS Release 10.4 for SRX Series Services

Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . 175

Errata and Changes in Documentation for Junos OS Release 10.4 for SRX

Series Services Gateways and J Series Services Routers . . . . . . . . . . . . 178

Changes to the Junos OS Documentation Set . . . . . . . . . . . . . . . . . . . . 178

Errata for the Junos OS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 179

Errata for the Junos OS Hardware Documentation . . . . . . . . . . . . . . . . 186

Hardware Requirements for Junos OS Release 10.4 for SRX Series Services

Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . 189

Transceiver Compatibility for SRX Series and J Series Devices . . . . . . . 189

Power and Heat Dissipation Requirements for J Series PIMs . . . . . . . . . 189

Supported Third-Party Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

J Series CompactFlash and Memory Requirements . . . . . . . . . . . . . . . . 190

Maximizing ALG Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Integrated Convergence Services Not Supported . . . . . . . . . . . . . . . . . . . . . 192

Upgrade and Downgrade Instructions for Junos OS Release 10.4 for SRX

Series Services Gateways and J Series Services Routers . . . . . . . . . . . . 192

Upgrade Policy for Junos OS Extended End-Of-Life Releases . . . . . . . . 192

Junos OS Release Notes for EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . 194

New Features in Junos OS Release 10.4 for EX Series Switches . . . . . . . . . . 194

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Class of Service (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Fibre Channel over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Management and RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Packet Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Changes in Default Behavior and Syntax in Junos OS Release 10.4 for EX

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Limitations in Junos OS Release 10.4 for EX Series Switches . . . . . . . . . . . . 197

Access Control and Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Layer 2 and Layer 3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Spanning Tree Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Outstanding Issues in Junos OS Release 10.4 for EX Series Switches . . . . . 202

Access Control and Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Layer 2 and Layer 3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Management and RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Resolved Issues in Junos OS Release 10.4 for EX Series Switches . . . . . . . . 206

Access Control and Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Layer 2 and Layer 3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Management and RMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Errata in Documentation for Junos OS Release 10.4 for EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

J-Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Virtual Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Upgrade and Downgrade Instructions for Junos OS Release 10.4 for EX

Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Upgrading Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Upgrade Policy for Junos OS Extended End-Of-Life Releases . . . . . . . . 212

Upgrading or Downgrading from Junos OS Release 9.4R1 for EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Upgrading from Junos OS Release 9.3R1 to Release 10.4 for EX Series

Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Junos OS Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

JUNOS OS 10.4 Release Notes

Junos OS Release Notes for Juniper Networks M Series Multiservice Edge Routers, MX Series Ethernet Service Routers, and T Series Core Routers

•

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers on page 6

•

Changes in Default Behavior and Syntax in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers on page 42

•

Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routerson page 55

•

Errata and Changes in Documentation for Junos OS Release 10.4 for M Series, MX Series, and T Series Routers on page 77

•

Upgrade and Downgrade Instructions for Junos OS Release 10.4forM Series, MX Series, and T Series Routers on page 83

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

The following features have been added to Junos OS Release 10.4. Following the description is the title of the manual or manuals to consult for further information.

Class of Service

•

Hierarchical policer functionality extended to Modular Interface Cards (MICs) (MX Series routers)—Provides hierarchical policer feature parity with Enhanced Intelligent

Queuing (IQE) PICs. This is useful in provideredge applications using aggregate policing for general traffic and when applying a separate policer for premium traffic on a logical or physical interface.

Hierarchical policing on MICs supports the following features:

•

Ingress traffic is first classified into premium and non-premium traffic before a policer is applied.

•

The hierarchical policer contains two policers: premium and aggregate.

Premium trafficis policed by both the premium policer and the aggregate policer. While the premium policer rate-limits premium traffic, the aggregate policer only decrements the credits but does not drop packets. Non-premium traffic is rate-limited by the aggregate policer only, resulting in the following behavior:

•

Premium trafficis assured to have the bandwidth configuredforthe premium policer.

•

Non-premium traffic is policed to the specified rate limit.

For a list of supported MICs, refer to:

http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/ general/mic-mx-series-supported.html.

The logical-interface-policer and physical-interface-policerstatements provide additional hierarchical policer parameters beyond those of the IQE PICs.

You can apply the policer at the inet, inet6, or mpls family level, as follows:

[edit interfaces ge-0/1/0 unit 0 family (inet | inet6 | mpls)] input-hierarchical-policer Test-HP;

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

By making a hierarchical policer a logical-interface-policer, you can achieve aggregation within a logical interface. A hierarchical policer configured as a physical-interface-policer supports aggregation within a physical interface. Please note that you still apply the hierarchical policer at the interface and traffic of the families that do not have the hierarchical policer will be policer. This is different from IQE PICs, where you apply a hierarchical policer at the logical or physical interface.

For hierarchical policing of all traffic through a logical interface, a hierarchical policer can be made a logical-interface-policerand applied to all families in the logical interface. Similarly, you can achieve aggregation at the physical interface level.

[Network Interfaces, Class of Service, Policy]

•

DSCP classification for VPLS at the ingress PE (M320 with Enhanced Type III FPC and M120)—Enables you to configure DSCP classification for VPLS at an ingress PE

for encapsulation types vlan-vpls (IQ2 or IQ2E PICs) or ATM II IQ PIC. To configure, define the DSCP classifier at the [edit class-of-service classifiers dscp dscp-name] hierarchy level and apply the DSCP classifier at the [edit interfaces at-fpc-pic-port

unit-logical-unit-numberclassifiers]hierarchylevel.The ATM interfacemust be included

in the routing instance.

[Class of Service]

•

Traffic Control Profile (TCP) support at the FRF.16 physical interface level—FRF.16 bundle interfaces support multiple data-link connection identifiers (DLCIs). The bandwidth of each of these DLCIs was previously limited to one of the following:

•

An aggregate value based on the number of DLCIs under the FRF.16 interface

•

A specific percentage through a traffic control profile (TCP) configuration applied at the logical interface level

When there is a small proportion of traffic or no traffic on an individual DLCI, the respective member link interface bandwidth is underutilized. Support for TCP features on the FRF.16 bundle (physical) interface level in Junos OS Release 10.4R2 addresses this limitation. The supported features include:

•

Peak Information Rate (PIR)

•

scheduler-map

•

delay-buffer

To enable traffic control profiles to be applied at FRF.16 bundle (physical) interface level, disable the per-unit scheduler, which is enabled by default, by including the

no-per-unit-scheduler statement at the [edit interfaces interface-name] hierarchy level.

To specify traffic control profile features applicable to FRF.16 bundle physical interfaces, include the shaping-rate, delay-buffer-rate, and scheduler-map statements at the [edit

class-of-service traffic-control-profiles profile-name] hierarchy level. The shaping-rate

and delay-buffer-rate must be specified as a percentage.

To apply the TCP configuration to an FRF.16 bundle (physical) interface, include the

output-traffic-control-profile statement at the [edit class-of-service interfaces interface-name] hierarchy level.

JUNOS OS 10.4 Release Notes

To view the TCP configuration for an FRF.16 bundle, enter the show class-of-service

traffic-control-profile command.

user@host> show class-of-service traffic-control-profile

Traffic control profile: lsq-2/1/0:0, Index: 35757

Shaping rate: 30 percent

Scheduler map: sched_0

Delay Buffer rate: 30 percent

The following is a complete configuration example:

interfaces {

lsq-0/2/0:0 {

no-per-unit-scheduler; encapsulation multilink-frame-relay-uni-nni; unit 0 {

dlci 100; family inet {

address 18.18.18.2/24;

}

class-of-service {

traffic-control-profiles {

rlsq_tc {

scheduler-map rlsq; shaping-rate percent 60; delay-buffer-rate percent 10;

} } interfaces {

lsq-0/2/0:0 {

output-traffic-control-profile rlsq_tc;

} }

} scheduler-maps {

rlsq {

forwarding-class best-effort scheduler rlsq_scheduler;

forwarding-class expedited-forwarding scheduler rlsq_scheduler1; }

} schedulers {

rlsq_scheduler {

transmit-rate percent 20;

priority low; } rlsq_scheduler1 {

transmit-rate percent 40;

priority high; }

}

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

[Class of Service]

Interfaces and Chassis

•

Extend support for 64-bit Junos OS to include RE-1800 Series Routing Engines (M120, M320, MX960, MX480, and MX240 routers)—Supported Routing Engines

include:

•

RE-1800x2-A—Supports 64-bit Junos OS on M120 and M320 routers.

•

RE-1800x2-S—Supports 64-bit Junos OS on MX240, MX480, and MX960 routers.

•

RE-1800x4-S—Supports 64-bit Junos OS on MX240, MX480, and MX960 routers.

[System Basics]

•

Ethernet encapsulation for ATM scheduler (M7i, M10i, M120, and M320 [with Enhanced III FPC] routers)—Enables support for the configuration of an ATM scheduler

map on an Ethernet VPLS over a bridged ATM interface.

[Network Interfaces]

•

Synchronous Ethernet (SyncE) on MX80 routers and MX Series routers with MPCs—Supportsthe Ethernet synchronization messaging channel (ESMC), G.8264-like

clock selection mechanism, and external clocking on MX80 routers and MX Series routers with MPCs. Wireless backhaul and wireline transport services are the primary applications for these features.

The following features are supported:

•

On MX80 routers and MX Series routers, MPCs based on G.8261 and G.8262. This feature does not work on the fixed configuration version of the MX80 routers.

•

All Ethernet type ports are supported on MX80 routers and MX Series routers with MPCs

•

ESMC support as per G.8264

•

CLI command selection of clock sources

•

Monitoring clock sources (maximum of two clock sources can be monitored simultaneously)

•

Revertive and nonrevertive modes

To configure SyncE, include the synchronization statement and its substatements at the [edit chassis] hierarchy level.

[Network Interfaces, Interfaces Command Reference]

•

Enhanced container interface allows ATM children for containers—M Series and T Series routers with ATM2 PICs automatically copy the parent container interface configuration to the children interfaces. Container interfaces do not go down during APS switchovers, thereby shielding upper layers. This feature allows the various ATM features to work over the container ATM for APS.

JUNOS OS 10.4 Release Notes

To specify ATMchildrenwithin a container interface, use the container-list cin statement and (primary | standby) option at the [edit interface at-fpc/pic/slot container] hierarchy level.

To configure a container interface, including its children, use the cin statement and its options at the [edit interface ci-n] hierarchy level.

Container ATM APS does not support inter-chassis APS. MLPPP over ATM CI is also not supported.

[Network Interfaces]

•

Signaling neighboring routers of fabric down on T1600 and T640 routers—The signaling of neighboring routers is supported when a T640 or T1600 router is unable to carry traffic due to all fabric planes being taken offline for one of the following reasons:

•

CLI or offline button pressed

•

Automatically taken offline by the SPMB due to high temperature.

•

PIO errors and voltage errors detected by the SPMB CPU to the SIBs.

The following scenarios are not supported by this feature:

•

All PFEs get destination errors on all planes to all destinations, even with the SIBs staying online.

•

Complete fabric loss caused by destination timeouts, with the SIBs still online.

When chassisd detects that all fabric planes are down, the router reboots all FPCs in the system. When the FPCs come back up, the interfaces will not be created again, since all fabric planes are down.

Once you diagnose and fix the cause of all fabric planes going down, you must then bring the SIBs back online. Bringing the SIBs back online brings up the interfaces.

Fabric down signaling to neighboring routers offers the following benefits:

•

FPCs reboot when the control plane connection to the Routing Engine times out.

•

Extends a simple approach to reboot FPCs when the dataplane blacks out.

When the router transitions from a state where SIBs are online or spare to a state where there are no SIBs are online, then all the FPCs in the system are rebooted. An ERRMSG indicates if all fabric planes are down, and the FPCs will reboot if any fabric planes do not come up in 2 minutes.

An ERRMSG indicates the reason for FPC reboot on fabric connectivity loss.

The chassisd daemon traces when an FPC comes online, but a PIC attach is not done because no fabric plane is present.

A CLI warning that the FPCs will reboot is issued when the last fabric plane is taken offline.

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

You will need to bring the SIBs online after determining why the SIBs were not online. When the first SIB goes online, and link training with the FPCs completes, the interfaces will be created.

Fabric down signaling to neighboring routers functionality is available by default, and no user configuration is required to enable it.

No new CLI commands or alarms are introduced for this feature. Alarms are already implemented for when the SIBs are not online.

[Network Interfaces, System Basics]

•

New enterprise-specific MIB to support digital optical monitoring (MX960, MX480, MX240, and 10-Gigabit Ethernet LAN/WAN PIC with XFP on T640 and T1600 routers)—Junos OS Release 10.4 introduces JUNIPER-DOM-MIB, a new

enterprise-specific MIB to extend MIB support for digital optical monitoring.

JUNIPER-DOM-MIB supports the SNMP Get request for statistics and SNMP Trap

notifications for alarms.

JUNIPER-DOM-MIB is part of the JUNIPER-SMI MIB hierarchy level.

The following MIB objects are supported by JUNIPER-DOM-MIB for digital optical monitoring:

•

jnxDomCurrentTable

•

jnxDomAlarmSet

•

jnxDomAlarmCleared

[SNMP MIBs and Traps Reference]

•

Logging improvements—You can now control logging speed at the interface level. To rate-limit the syslogs generated from a service PIC, include the message-rate-limit statement at the [edit interfaces interface-name services-options syslog] hierarchy level. This option configures the maximum number of syslog messages per second that can formatted and sent from the PIC to either the Routing Engine (local) or to an externalserver (remote). The default rates are 10,00 for the Routing Engine and 200,00 for an external server.

[Network Interfaces]

•

Support for SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP (M320, MX240, MX480, MX960, T640 and T1600 routers)Supports a 4-port SONET/SDH

OC48 Enhanced IQ (IQE) PIC (Type 3) with per data-link connection identifier (DLCI) queuing. Supported FPCs include T640-FPC3-ES, M320-FPC3-E3, and MX-FPC3. Classof service (CoS) enables enhanced egress queuing, buffering, and trafficshaping.

CoS supports eight queues per logical interface, a per-unit scheduler, and two shaping rates: a Committed Information Rate (CIR) and Peak Information Rate (PIR) per data-link connection identifier (DLCI). Other CoS features include, but are not restricted to, sharing of excess bandwidth among logical interfaces, five levels of priorities (including Strict High), ingress behavior aggregate (BA) classification, queue rate-limit policer, ingress rewrite, egress rewrite, and a forwarding class to queue remapping per DLCI.

JUNOS OS 10.4 Release Notes

The SONET/SDH OC48/STM 16 PIC supports CoS features similar to those in IQ2E PICs, in terms of behavior and configurationstatements. This PIC supports the following Layer 2 protocols: PPP, Frame Relay, and Cisco HDLC encapsulations.

For more information, see the PC-4OC48-STM16-IQE-SFP documentation for your router:

•

SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP (T1600 Router)

•

SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP (T640 Router)

•

SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP (MX Series Routers)

•

SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP (M320 Router)

[PIC Guide, Network Interfaces, Class of Service]

•

IPv6 statistics from IQ2 and IQ2E PICs on M320 routers with Enhanced III FPCs and T Series routers—Support statistical accounting for IPv6 traffic traversing the IQ2 and

IQ2E PICs on M320 routers with Enhanced III FPCs and T Series routers.

For IQ2 and IQ2E PIC interfaces,the IPv6 trafficthat is reported will be the total statistics (sum of local and transit IPv6 traffic) in the ingress and egress direction. The IPv6 traffic in the ingress direction will be accounted separately only if the IPv6 family is configured for the logical interface.

Statistics are maintained for routed IPv6 packets in the egress direction.

Byte and packet counters are maintained in the ingress and egress direction.

Differences in IPv6 statistics for IQ2 interfaces and all other interfaces are as follows:

•

IQ2 and IQ2E PIC interfaces report the total statistics for the IPv6 traffic. For other interfaces, the transit statistics are reported.

•

IQ2 and IQ2E PIC interfaces report all IPv6 traffic received on the logical interface. For all other interfaces, only the routed traffic is accounted.

•

IQ2 and IQ2E PIC interfaces report IPv6 statistics for the Layer 2 frame size. For all other interfaces, the Layer 3 packet size is accounted.

The IPv6 statistics can be viewed by logging in to the individual IQ2 PIC or IQ2E PIC, or by using the CLI.

Local statistics are not accounted separately.

To display total IPv6 statistics for IQ2 and IQ2E PICs, use the show interfaces extensive command.

NOTE: The reported IPv6 statistics do not account for the traffic manager

drops in egress direction or the Packet Forwarding Engine/traffic manager drops in the ingress direction. Transitstatistics are not accountedseparately because the IQ2 and IQ2E PICs cannot differentiate between transit and local statistics.

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

[Network Interfaces]

•

100-Gigabit Ethernet PIC interoperability with VLAN steering—Supports interoperability with similar PICs from other vendors using a VLAN steering forwarding option. Previously, the PICs required interconnection to the same model PIC. Interoperabilitywith interfacesfromother vendors was not supported.Junos OS Release

10.4 introduces a new VLAN steering algorithm to configure 100-Gigabit Ethernet PIC interoperation with similar interfaces from other vendors.

Two packet forwarding modes exist under the forwarding-mode statement.SA multicast mode, for proprietary connection of two Juniper Networks 100-Gigabit Ethernet PICs, uses the Ethernet header SA MAC address multicast bit to steer the packets to the appropriate PFE. VLAN steering mode allows the PIC to connect to non-Juniper Networks equipment. On ingress, the PIC compares the outer VLAN ID against a user-defined VLAN ID and VLAN mask combination and steers the packet accordingly. Modifying the forwarding mode config reboots the PIC.

VLAN steering overview:

•

In VLAN steering mode, the SA multicast bit is not used for packet steering.

•

In SA multicast bit steering mode, VLAN ID and VLAN mask configuration is not used for packet steering.

•

Configuration of packet forwarding mode and VLAN steering mode uses CLI commands that result in a PIC reboot.

•

There are three tag types for ingress packets:

•

Untagged ingress packet–The packet is sent to PFE1.

•

Ingress packet with one VLAN–The packet forwards based on the VLAN ID.

•

Ingress packet with two VLANs–The packet forwards based on the outer VLAN ID.

•

VLAN rules describe how the router forwards packets. For VLAN steering, you must use one of the two rules available in the CLI:

•

Odd-even rule–Odd number VLAN IDs go to PFE1; even number VLAN IDs go to PFE0.

•

High-low rule–1 through 2047 VLAN IDs go to PFE0; 2048 through 4096 VLAN IDs go to PFE1.

•

When configured in VLAN steering mode, the PIC can be configured in two physical interface mode or in aggregated Ethernet (AE) mode:

•

Two physical interface mode–When the PIC is in two physical interface mode, it creates physical interfaces et-x/0/0:0 and et-x/0/0:1. Each physical interface can configure its own logical interface and VLAN. CLI enforces the followingrestrictions on commit:

•

The VLAN ID configuration must comply with the selected VLAN rule.

JUNOS OS 10.4 Release Notes

•

The previous restriction implies that the same VLAN ID cannot be configured on both physical interfaces.

•

AE mode–In AE mode, the two physical interfaces on the same PIC are aggregated into one AE physical interface. PIC egress traffic is based on the AE internal hash algorithm. PIC ingress traffic steering is based on the customized VLAN ID rule. CLI enforces the following restrictions on commit:

•

The PIC AE working in VLAN steering mode includes both links of this PIC, and only the links of this PIC.

•

The PIC AE working in SA multicast steering mode can include more than one PIC to achieve more than 100-gigabit capacity.

To configure the PIC forwarding mode, include the forwarding-mode statement and its options at the [edit chassis fpc number pic number] hierarchy level.

[Network Interfaces]

•

New control queue disable feature (T Series routers with 10-Gigabit Ethernet PIC with oversubscription)—Providesa new CLI statement for disabling the control queue

feature for the 10-Gigabit Ethernet PIC with oversubscription. To disable the control queue, use the no-pre-classifier statement at the [chassis] hierarchy level.

When the no-pre-classifier statement is set, the control queue feature will be disabled for all ports on that 10-Gigabit Ethernet PIC with oversubscription. Deleting this configuration results in the control queue feature being re-enabled on all the ports of that PIC.

[edit chassis]

fpc 2 {

pic 0 {

no-pre-classifier;

}

NOTE:

1. This feature is applicable in both oversubscribed and line-rate modes.

2. The control queue feature is enabled by default in both oversubscribed

and line-rate modes, which can be overridden by the user configuration.

3. CLI show commands remain unchanged. When the control queue is

disabled, various show queue commands continue to show the control queue in the output. However, all control queue counters are reported as zeros.

4. Enabling or disabling the control queue feature results in the PIC being

bounced (offline/online).

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

Once the control queue feature is disabled, then the Layer 2 and Layer 3 controlpackets are subject to queue selection based on the BA classification. However, the following control protocol packets are not classified using BA classification, as they might not have a VLAN, MPLS, or IP header:

•

Untagged ARP packets

•

Untagged Layer 2 control packets such as LACP or Ethernet OAM

•

Untagged IS-IS packets

When the control queue feature is disabled, untagged ARP/IS-IS and other untagged Layer 2 control packets will go to the restricted queue corresponding to the forwarding class associated with queue 0.

[Network Interfaces]

•

Microcode remap (M320 and M120 routers)—M320 routers with E3 type-1 FPCs and M120 routers with a single type-1 FPC mapped to an FEB, support a new microcode map to resolve microcode overflow resulting in bad PIC combinations.

On M320 routers, the new microcode map is enabled by default and is the only option available.

On M120 routers, you can enable the new microcode map by using the

ucode-imem-remap statement at the [edit chassis feb slot number] hierarchy level. On

M120 routers, the default microcode map remains configured if the ucode-imem-remap statement is not configured.

[edit chassis] feb

slot number

ucode-imem-remap {

}

NOTE: On M120 routers, the FEB is automatically restarted once the

ucode-imem-remap statement is configured and committed.

[System Basics]

Junos OS XML API and Scripting

New Junos OS XML API operational request tag elements—Table 1 on page 16 shows

the Junos OS Extensible Markup Language (XML) operational request tag elements that are new in Junos OS Release 10.4 along with the corresponding CLI command and response tag element for each one.

JUNOS OS 10.4 Release Notes

Table 1: Junos OS XML Tag Elements and CLI Command Equivalents New in Junos OS Release

10.4

Response Tag ElementCLI CommandRequest Tag Element

NONErequest dhcpv6 server reconfigure<requestdhcpv6-serverreconfigure-information>request_dhcpv6_ server_reconfigure_information

NONErequest system license update<request-license-update> request_license_update

NONErequest system software nonstop-upgrade<request-package-nonstop-upgrade> request_package_nonstop_upgrade

<amt-instance-statistics>show amt statistics<get-amt-statistics> get_amt_statistics

<amt-summary>show amt summary<get-amt-summary> get_amt_summary

get_amt_tunnel_information

get_rps_chassis_information

get_bios_version_information

congestionnotificationinformation> get_cos_congestion_notification_information

get_firewall_log_information

get_interface_information

identifier-origininformation> get_isis_context_ identifier_origin_information

<amt-tunnel-information>show amt tunnel<get-amt-tunnel-information>

<rps-chassis-information>show chassis redundant-power-supply<get-rps-chassis-information>

NONEshow chassis routing-engine bios<get-bios-version-information>

<cos-congestion-notification-information>show class-of-service congestion-notification<get-cos-

<firewall-information>show firewall filter version<get-firewall-log-information>

<ingress-replication-information>show ingress-replication<get-interface-information>

<isis-context-identifier- information>show isis context-identifier<get-isis-context-

get_isis_database_information

get_mpls_cspf_information

get_authentication_pending_table

<isis-context-identifier-origin-information>show isis context-identifier identifier<get-isis-database-information>

<mpls-context-identifier-information>show mpls context-identifier<get-mpls-cspf-information>

<domain-map-statistics>show network-access domain- map statistics<get-authentication-pending-table>

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

Table 1: Junos OS XML Tag Elements and CLI Command Equivalents New in Junos OS Release

10.4 (continued)

Response Tag ElementCLI CommandRequest Tag Element

<ospf-context-id-information>show ospf context-identifier<get-ospf-database-information> get_ospf_database_information

<rps-led-information>show redundant-power-supply led<get-rps-power-supply-information> get_rps_power_supply_information

<rps-power-supply-information>showredundant-power-supply power-supply<get-rps-status-information> get_rps_status_information

<rps-status-information>show redundant-power-supply status<get-rps-version-information> get_rps_version_information

<rps-version-information>show redundant-power-supply version<get-rip-general-statistics-information> get_rip_general_statistics_information

get_idp_policy_template_information

<get-service-border-signalinggateway-charging-status> get_service_border_signaling_ gateway_charging_status

<get-service-bsg-denied-messages> get_service_bsg_denied_messages

accounting-statistics-information> get_services_l2tp_radius_acco unting_statistics_information

get_service_softwire_statistics _information

conversation_ information> get_service_sfw_conversation _information

sfw_flow_analysis_ information> get_service_sfw_flow_analysi s_information

charging statistics

charging status

show services softwire flows<get_service_

<idp-policy-commit-status>show security idp policy-commit-status<get-idp-policy-template- information>

<bsg-charging-statistics>show services border-signaling-gateway

<bsg-charging-status>show services border-signaling-gateway

<service-l2tp-destination-information>show services l2tp destination<get-services-l2tp-radius-

<msp-session-table>show services sessions<get-service-softwire-statistics-information>

<service-softwire-table- information>show services softwire<get_service_sfw_

<service-fwnat-flow-table-

information>

flow_table_information> get_service_sfw_flow_table_i nformation

<service-softwire-statistics-information>show services softwire statistics<get_service_sfw_

JUNOS OS 10.4 Release Notes

Table 1: Junos OS XML Tag Elements and CLI Command Equivalents New in Junos OS Release

10.4 (continued)

Response Tag ElementCLI CommandRequest Tag Element

<service-sfw-flow-analysis-information>show services stateful-firewallflow-analysis<get_service_sfw_sip_registerinformation> get_service_sfw_sip_register_i nformation

<clock-synchronization- statistics>show synchronous-ethernet esmc statistics<get_synchronous_ethernet_esmc-statistics> get_synchronous_ethernet_esmc-statistics

get_synchronous_ethernet_esmc_transmit

<get_synchronous_ethernet_global_information> get_-synchronous_ethernet_global_information

processes_information> get_system_resource_cleanup_ processes_information

get_rollback_information

get_dhcp_binding_information

<clear_synchronous_ ethernet_esmc_ statistics>clear_synchronous_ ethernet_e smc_ statistics

Layer 2 Ethernet Services

•

Feature support for Trio 3D MPCs and MICs (MX Series routers)—Enables you to configurethe following features through Junos OS Release 9.1: load balancing, Ethernet OAM IEEE 802.1ag Phase 4 MIP support, LLDP, BPDU guard and loop guard, IRB support for interworking of LDP-VPLS and BGP-VPLS, BGP multihoming for Inter-AS VPLS, VPLS Ethernet as a core-facing interface, and limitations on next-hop flooding.

show synchronous-ethernet esmc transmit<get_synchronous_ethernet_esmc_transmit>

global-information

clear synchronousethernet esmc statistics

<clock-synchronization-

esmc-transmit>

NONEshow synchronous-ethernet

<relay-group-information>show system relay group<get_system_resource_cleanup_

<relay-group-member>show system relay member<get_rollback_information>

<relay-summary>show system relay summary<get_dhcp_binding_information>

<clock-synchronization-

clear-output>

[Layer 2 Configuration]

•

Ethernet CFM support on Trio 3D MPCs and MICs (MX Series routers)—Enables support for Ethernet connectivity fault management (CFM) defined by IEEE 802.1ag for family bridge interfaces.However, MEP configuration is not supported on aggregated Ethernet interfaces.

[Layer 2 Configuration]

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

MPLS Applications

•

MPLS support on services PICs—Adds MPLS label pop support for services PICs on Junos OS routers. Previously all MPLS traffic would be dropped at the services PIC. No changes are required to CLI configurations for this enhancement. In-service software upgrade (unified ISSU) is supported for tag next hops for MPLS on services PIC traffic, but no support is provided for tags over IPv6 packets or labels on multiple gateways.

[MPLS]

•

Adding descriptions for bypass LSP—You can now add a text describing a bypass LSP using the description option at the [edit protocols rsvp interface interface-name

link-protection bypass bypass-lsp-name] hierarchy level. Enclose any descriptive text

that includes spaces in quotation marks (" "). Any descriptive text you include is displayed in the output of the show rsvp session bypass command and has no effect on the operation of the bypass LSP.

[MPLS]

Multicast

•

Nonstop active routing PIM support for IPv6—Starting with Release 10.4, Junos OS extends the nonstop active routing support for Protocol Independent Multicast (PIM), which is already supported on IPv4, to include the IPv6 address families. The extension of nonstop active routing PIM support to IPv6 enables IPv6 routers to maintain self-generation IDs, multicastsession states, dynamic interface states, list of neighbors, and RPSets across Routing Engine switchovers.

The nonstop active routing support for PIM on IPv6 is similar to the nonstop active routing PIM support on IPv4 except for the following:

•

Nonstop active routing support for PIM on IPv6 supports an embedded rendezvous point (RP) on non-RP routers.

•

Nonstop active routing support for PIM on IPv6 does not support auto-RP,as auto-RP is not supported on IPv6.

For more information about nonstop active routing PIM support on IPv4 and IPv6, see the Junos OS High Availability Configuration Guide.

[High Availability, Multicast]

MX Series

•

Support for MX Series—While these features have been available on the MX Series routers in the past, we have now qualified the following features on the Trio chipset.

For MPLS, RSVP, and LDP:

•

BFD session failure action for LDP LSPs (including ECMP)

•

RSVP Graceful Restart interop with Cisco using Nodal Hello support

•

Failure action on BFD session down of RSVP LSPs in JUNOS

•

RSVP transit

JUNOS OS 10.4 Release Notes

•

L3VPN testing using RSVP

•

NSR: RSVP ingress

•

BFD via LDP

For Multicast:

•

OSPF

•

OSPF Database Protection

•

RFC 4136 OSPF Refresh and Flooding Reduction in Stable Topologies

•

PIM SSM in provider space (Draft-Rosen 7)

•

NG MVPN - PIM-SSM I-PMSI and deployment scenario testing

•

MVPN C-PIM in plain ASM mode

•

NGEN MVPN hub and spoke support with GRE S-PMSI transport

•

PIM Join suppression support

•

Translating PIM states to IGMP/MLD messages

•

Disable PIM for IPv6 via CLI

•

IPv6 multicast support over L3VPNs

•

PIM neighbor should be maintained wherever possible

•

Data MDT SAFI (draft-rosen-l3vpn-mvpn-profiles)

•

Inter-provider Option A support with Rosen 7

•

Rosen 7 interoperability with Cisco IOS

For VPNs:

•

VPLS: Configurable label block size (min 2)

•

Interoperate LDP-VPLS and BGP-VPLS with FEC 128

•

LDP-VPLS

•

Interprovider VPLS Option "E": EBGP redistribution of labeled routes

Miscellaneous:

•

Support to commit configuration from op/event scripts

•

Per PFE per packet load balancing

•

Next Hop Handling Enhancements (Phase 3)

•

Support local-as alias hidden command

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

•

MIB Enhancements for Manual Bypass Tunnel Management

•

ISIS LFA

•

Improve IGMPv3 performance using bulk updates

•

Improve IGMPv3 performance using bulk updates - with snooping

•

Allow ASM group override of SSM ranges

Routing Policy and Firewall Filters

•

Point-to-multipoint (P2MP) LSP load balancing across aggregated Ethernet links (M Series except M320)—Enables you to load-balance VPLS multicast and P2MP

multicast traffic over link aggregation. This feature also re-load-balances traffic after a change in the next-hop topology. Next-hop topology changes might include but are not limited to:

•

Layer 2 membership change in the link aggregation

•

Indirect next-hop change

•

Composite next-hop change

No new configuration is required to configure this feature. The load balancing over aggregated links is automatically enabled with this release. For a sample topology and configuration example, see Junos OS Policy Framework Configuration Guide.

[Policy]

•

New routing policy system log message—Junos OS Release 10.3 supports a new routing policy system log message. The RPD_PLCY_CFG_NH_NETMASK system log message provides information about ignored netmasks. If you have a policy statement with a term that contains a next-hop address with a netmask, the netmask is ignored. The following sample shows the new systemlog message (depending on your network configuration, the type of message you see might be different):

Jun 18 11:22:43 pro5-d rpd[1403]: RPD_PLCY_CFG_NH_NETMASK: Netmask ignored for

next hop: 10.0.0.1/24.

[System Log Messages Reference]

•

Support for displaying the firewall filter version information—You can display the version number of the firewall filter installed in the Routing Engine. The initial version number is 1 and increments by one when you modify the firewall filter settings or an associated prefix action. To show the version number of the installed firewall filter, use the show firewall filter version operational mode command.

[Routing Protocols and Policies Command Reference]

Routing Protocols

•

Support for disabling traps for passive OSPFv2 interfaces—You can now disable interface state change traps for passive OSPF interfaces. Passive OSPF interfaces advertise address information as an internal OSPF route, but do not run the actual protocol. If you are only interested in receiving notifications for active OSPF interfaces,

JUNOS OS 10.4 Release Notes

disabling traps for passive OSPF interfaces reduces the number of notificationsreceived and processed by the SNMP server. This allows you to more quickly and easily scan the logs for potential issues on active OSPF interfaces.

To disable and stop receiving notifications for statechanges in a passiveOSPF interface, include the no-interface-state-traps statement at the following hierarchy levels:

•

[edit logical-systems logical-system-name protocols ospf area area-id interface

interface-name]

•

[edit logical-systems logical-system-name routing-instances routing-instance-name

protocols ospf area area-id interface interface-name]

•

[edit protocols ospf area area-id interface interface-name]

•

[edit routing-instances routing-instance-name protocols ospf area area-id interface

interface-name]

[Routing Protocols]

•

Behavior change for BGP-independent AS domains—Independent domains use the transitive path attribute 128 (attribute set) messages to tunnel the independent domain’s BGP attributes through the internal BGP (IBGP) core. In Junos OS Release

10.3 and later,if you have not configured an independent domain in any routing instance, BGP treats the received attribute 128 message as an unknown attribute. The AS path field in the show route command has been updatedto display an unrecognized attribute and associated hexadecimal value if you have not configured an independent domain. The following is a sample output of the AS path field (depending on your network configuration, the output might be different):

AS path: [12345] I Unrecognized Attributes: 40 bytes AS path: Attr flags e0 code 80: 00 09 eb 1a 40 01 01 00 40 02 08 02 03 fd e9 fd e9 01

2d 40 05 04 00 00 00 64 c0

[Routing Protocols]

•

Support for disabling the attribute set messages on independent AS domains for BGP loop detection—BGP loop detection for a specific route uses the localautonomous

system (AS) domain for the routing instance. By default, all routing instances belong to a single primary routing instance domain. Therefore, BGP loop detection uses the local ASs configured on all of the routing instances. Depending on your network configuration, this default behavior can cause routes to be looped and hidden.

To limit the local ASs in the primary routing instance, configure an independent AS domain for a routing instance. Independent domains use the transitive path attribute 128 (attribute set) messages to tunnel the independent domain’s BGP attributes through the internal BGP (IBGP) core. If you want to configure independent domains to maintain the independence of local ASs in the routing instance and perform BGP loop detection only for the specified local ASs in the routing instance, disable attribute set messages on the independent domain. To disable attribute set messages, include the independent-domain no-attrset statement at the following hierarchy levels:

•

[edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options autonomous-system autonomous-system]

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

•

[edit routing-instances routing-instance-name routing-options autonomous-system

autonomous-system]

[Routing Protocols]

Services Applications

•

NAT-PT with DNS ALG support (M Series and T Series routers)—You can configure Domain Name Service (DNS) application-level gateways (ALGs) using NAT with protocol translation (NAT-PT) for IPv6 to IPv4. The implementation is described in RFC 2766 and RFC 2694.

When you configure NAT-PT with DNS ALGsupport, you must configure two NAT rules. The first NAT rule ensures that the DNS query and response packets are translated correctly. For this rule to work, you must configure a DNS ALG application and reference it in the rule. The second rule is required to ensure that NAT sessions are destined to the address mapped by the DNS ALG.

•

To configure the correct translation of the DNS query and response packets, include the dns-alg-pool dns-alg-pool or dns-alg-prefix dns-alg-prefix statement at the [edit

services nat rule rule-name term term-name then translated] hierarchy level.

•

To configure the DNS ALG application, include the application application-name statement at the [edit applications] hierarchy level, then reference it at the [edit

services nat rule rule-name term term-name from] hierarchy level.

•

To configure destination translation with the DNS ALG address map, use the

use-dns-map-for-destination-translation statement at the [edit services nat rule rule-name term term-name then translated] hierarchy level. This statement correlates

the DNS query or response processing done by the first rule with the actual data sessions processed by the second rule.

You can also control the translation of IPv6 and IPv4 DNS queries in the following ways.

•

For translation control of IPv6 DNS queries, use the

do-not-translate-AAAA-query-to-A-query statement at the [edit applications application application-name] hierarchy level.

•

For translation control of IPv4 queries, use the

do-not-translate-A-query-to-AAAA-query statement at the [edit applications application application-name] hierarchy level.

NOTE: The above two statements cannot be configured together. You can only configure one at a time, but not both.

To check that the flows are established properly, use the show services

stateful-firewall flows command or the show services stateful-firewall conversations

command.

JUNOS OS 10.4 Release Notes

[Services Interfaces]

•

Enhancements to active flow monitoring—Add support for extraction of bandwidth usage information for billing purposes in PIC-based sampling configurations. This capability is supported on M Series, MX Series, and T Series routers and applies only to IPv4 and IPv6 traffic. It is enabled only at the global instance hierarchy level and is not available for per Packet Forwarding Engine instances. To configure the sampling of traffic for billing purposes, include the template as-peer-billing-template-name statement at the [edit forwarding-options sampling family (inet | inet6) output

flow-server server-name version version-number] hierarchy level. To define the peer-AS

billing functionality, include the peer-as-billing-template statement at the [edit services

flow-monitoring version9 template template-name] hierarchy level. For a list of the

template fields, see the Junos OS Services Interfaces ConfigurationGuide. You can apply the existing destination class usage (DCU) policy option configuration for use with this feature.

In addition, the MPLS top label IP address is added as a new field in the existing MPLS-IPv4 flow template. Youcan use this field to gather MPLS forwarding equivalence class (FEC) -based traffic information for MPLS network capacity planning. These ALGs that use Junos Services Framework (JSF) (M Series) is a PIC-only feature applied on sampled traffic and collected by the services PIC or DPC. You can define it for either global or per Packet Forwarding Engine instances for MPLS traffic.

The show services accounting aggregation template operational command has been updated to include new output fields that reflect the additional functionality.

[Services Interfaces, System Basics and Services Command Reference]

•

Support for the RPM timestamp on the Services SDK (M Series, MX Series, and T Series)—Real-time performance monitoring (RPM), which has been supported on the

Adaptive Services (AS) interface, is now supported by the Services SDK. RPM is supported on all platforms and service PICs that support the Services SDK.

RPM timestamping is needed to account for any latency in packet communications. You can apply timestamps on the client, the server, or both the client and server. RPM timestamping is supported only with the icmp-ping, icmp-ping-timestamp, udp-ping, and udp-ping-timestamp probe types.

To specify the Services SDK interface, include the destination-interface statement at the [edit services rpm probe probe-owner test test-name] hierarchy level:

destination-interface ms-fpc/pic/port.logical-unit-number;

To specify the RPM client router and the RPM server router, include the rpm statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level:

rpm (client | server);

To enable RPM on the Services SDK on the AS interface, configure the object-cache-size,

policy-db-size, and package statements at the [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-provider] hierarchy level. For

the Services SDK, package-name in the package package-name statement is

jservices-rpm.

user@host# show chassis

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

fpc 1 {

pic 2 {

adaptive-services {

service-package {

extension-provider {

control-cores 1;

data-cores 1; object-cache-size 512; policy-db-size 64; package jservices-rpm; syslog daemon any;

}

[Services Interfaces]

•

ALGs using Junos OS Services Framework (JSF) (M Series with Multiservices PICs and MX Series with MS DPCs)—Application-level gateways (ALGs) intercept and

analyze specified traffic, allocate resources, and define dynamic policies to permit traffic to pass securely through a device. Beginning with Junos OS Release 10.4 on the specified routers, you can use JSF ALGs with the following services:

•

Stateful firewall

•

Network Address Translation (NAT)

To use JSF to run ALGs, you must configure the jservices-alg package at the [edit

chassis fpc slot pic slot adaptive-services service-package extension-provider package]

hierarchy level. In addition, you must configure the ALG application at the [edit

applicationsapplicationapplication-name] hierarchylevel,and referencethe application

in the stateful firewall rule or the NAT rule in those respective configurations.

[Services Interfaces]

•

Enhancements to port mirroring with next-hop groups (MX Series only)—Adds support for binding up to two port-mirroring instances to the same MX Series Packet FowardingEngine. This enables you to choose multiple mirror destinations by specifying different port-mirroring instances in the filters. Filters must include the

port-mirror-instanceinstance-name statementat the [edit firewall filter filter-name term term-name then] hierarchy level. You must also include the port-mirror-instance instance-name statement at the [edit chassis fpc number] hierarchy level to specify the

FPC to be used.

Inline port mirroring allows you to configure instances that are not bound to the FPC specified in the firewall filter then port-mirror-instance instance-name action. Instead, you can define the then next-hop-group action. Inline port-mirroring aims to decouple the port-mirror destination from the input parameters, such as rate. While the input parameters are programmed in the Switch Interface Board (SIB), the next-hop destination for the mirrored packet is available in the packet itself.

A port-mirroring instance can now inherit input parameters from another instance that specifies it. To configure this option, include the input-parameters-instance

JUNOS OS 10.4 Release Notes

instance-name statement at the [edit forwarding-options port-mirror instance instance-name] hierarchy level.

You can also now configure port mirroring to next-hop groups using a tunnel interface.

[Services Interfaces]

•

Multiple IDP detector support (MX Series routers, M120 routers, and Enhanced III FPCs in M320 routers)—TheIDP detectorprovidesinformationabout services, contexts,

and anomalies that are supported by the associated protocol decoder.

The specified routers now support loading multiple IDP detectors simultaneously. When a policy is loaded, it is also associated with a detector. If the new policy being loaded has an associated detector that matches the detector already being used by the existing policy, the new detector is not loaded and both policies use a single associated detector. However, if the new detector does not match the current detector, the new detector is loaded along with the new policy. In this case, each loaded policy will then use its own associated detector for attack detection. Note that with the specified routers, a maximum of four detectors can be loaded at any given time.

Multiple IDP detector support for the specified routers functions in a similar way to the existing IDP detector support on J Series and SRX Series devices, except for the maximum number of decoder binary instances that are loaded into the process space.

To view the current policy and the corresponding detector version, use the show security

idp status detail command.

For more information, see the Junos OS Security Configuration Guide.

[Services Interfaces]

•

NAT using Junos OS Services Framework (JSF) (M Series and T Series with Multiservices PICs and MX Series with Multiservices DPCs)—The Junos OS Services

Framework (JSF) is a unified framework for Junos OS services integration. JSF Services integration will allow the option of running Junos OS services on services PICs or DPCs in any M Series, MX Series, or T Series routers. Beginning with Junos OS Release 10.4, you can use JSF to run NAT on the specified routers.

To use JSF to run NAT, you must configure the jservices-nat package at the [edit chassis

fpc slot pic slot adaptive-services service-packageextension-provider package] hierarchy

level. In addition, you must configure NAT rules and a service set with a Multiservice interface. Tocheck the configuration, use the show configurationservicesnat command. To show the run time (dynamic state) information on the interface, use the show

services sessions and show services nat pool commands.

[Services Interfaces]

•

Stateful firewall using Junos OS Services Framework (JSF) (M Series with Multiservices PICs, MX Series with Multiservices DPCs, and T Series routers)—The

Junos OS Services Framework (JSF) is a unified framework for Junos OS services integration. JSF Services integration will allow the option of running Junos OS services on services PICs or DPCs in any M Series, MX Series, or T Series routers. Beginning with Junos OS Release 10.4, you can use JSF to run stateful firewall on the specified routers.

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

To use JSF to run stateful firewall, you must configure the jservices-sfw package at the

[edit chassis fpc slot pic slot adaptive-services service-package extension-provider package] hierarchy level. In addition, you must configure stateful firewall rules and a

service set with a Multiservice interface. To check the configuration, use the show

configurationservices stateful-firewall command. To show the run time (dynamic state)

information on the interface, use the show services sessions command.

[Services Interfaces]

•

Transition of IPv4 traffic to IPv6 addresses using Dual Stack Lite (DS-Lite)—Adds support for DS-Lite, a means for transitioning IPv4 traffic to IPv6 addresses. This transition will become necessary as the supply of unique IPv4 addresses nears exhaustion. New subscriber homes are allocated IPv6 addresses and IPv6-capable equipment; DS-Lite provides a method for the private IPv4 addresses behind the IPv6 equipment to reach the IPv4 network. An IPv4 host communicateswith a NATendpoint over an IPv6 network using softwires. DS-Lite creates the IPv6 softwires that terminate on the services PIC. Packets coming out of the softwire can then have other services such as NAT applied on them.

[Services Interfaces, System Basics and Services Command Reference]

•

Round-robinallocationfor NATP addresses—Youcan now specify round-robin address allocation from NAT pools when you use NATP. In the default method of address-allocation, NAT addresses are allocated sequentially. All of the addresses in a given range must be allocated before addresses from a different range are allocated. The following example illustrates the sequential (legacy) implementation, which is still available to provide backward compatibility.

pool napt {

address-range low 9.9.99.1 high 9.9.99.3; address-range low 9.9.99.4 high 9.9.99.6; address-range low 9.9.99.8 high 9.9.99.10; address-range low 9.9.99.12 high 9.9.99.13; port {

range low 3333 high 3334;

}

In this example, for each unique source address, a new address range is used for allocationonly when there are no ports available in the previous address range.Address

9.9.99.4:3333 is picked only when all ports for addresses in the first range are exhausted.

•

The first connection is allocated NAT address 9.9.99.1:3333.

•

The second connection is allocated 9.9.99.1:3334.

•

The third connection is allocated 9.9.99.2:3333.

•

The fourth connection is allocated 9.9.99.2:3334, and so on.

To configure round-robin allocation for NAT pools, include the address-allocation

round-robin configurationstatementatthe [edit services nat pool pool-name] hierarchy

level. When you use round-robin allocation, one port is allocated from each address in a range before repeating the process for each address in the next range. After ports

JUNOS OS 10.4 Release Notes

have been allocated for all addresses in the last range, the allocation process wraps around and allocates the next unused port for addresses in the first range.

•

The first connection is allocated NAT address 9.9.99.1:3333.

•

The second connection is allocated 9.9.99.2:3333.

•

The third connection is allocated 9.9.99.3:3333.

•

The fourth connection is allocated 9.9.99.4:3333.

•

The fifth connection is allocated address 9.9.99.5:3333.

•

The sixth connection is allocated address 9.9.99.6:3333.

•

The seventh connection is allocated address 9.9.99.7:3333.

•

The eighth connection is allocated address 9.9.99.8:3333.

•

The ninth connection is allocated address 9.9.99.9:3333.

•

The tenth connection is allocated address 9.9.99.10:3333.

•

The eleventh connection is allocated address 9.9.99.11:3333.

•

The twelfth connection is allocated address 9.9.99.12:3333.

•

Wraparound occurs and the thirteenth connection is allocatedaddress9.9.99.1:3334.

[Services Interfaces]

Subscriber Access Management

•

Enhancement to the showservicesl2tp destination command—Theshowservicesl2tp

destination command has been extendedto display the lockout state of the destination

from the LAC. A destination that is reachable is not locked. An unreachable destination is locked out. L2TP makes no further attempts to connect to this destination until the timeout period (300 seconds) expires, unless the unreachable destination is the only destination in the tunnel configuration list. In that case, L2TP ignores the lockout and continues trying to connect to the destination.

[Subscriber Access]

•

Redirecting HTTP redirect requests (MX Series routers)—Enables support for HTTP traffic requests from subscribers to be aggregated from access networks onto a BRAS router, where HTTP traffic can be intercepted and redirected to a captive portal. A captive portal provides authentication and authorization services for redirected subscribers before granting access to protected servers outside of a walled garden. A walled garden defines a group of servers where access is provided to subscribers without reauthorization through a captive portal. You can use a captive portal page as the initial page a subscriber sees after logging in to a subscriber session and as a page used to receive and manage HTTP requests to unauthorized Web resources. An HTTP redirectremoteserver that resides in a walled garden behind Junos OS routers processes HTTP requests redirected to it and responds with a redirect URL to a captive portal.

New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

To configure HTTP redirect, include the captive-portal-content-delivery statement at the [edit services] hierarchy level.

[Subscriber Access]

•

Filter support for service packet counting—You can count service packets, applying them to a specific named counter (__junos-dyn-service-counter), for use by RADIUS.

To enable service packet accounting, specify the service-accounting action at the [edit

firewall family family-name filter filter-name term term-name then] hierarchy level.

[Policy Framework, Subscriber Access]

•

Support for domain maps that apply configuration options based on subscriber domain names (MX Series and M Series routers)—You use domain maps to apply

access options and session-specific parameters to subscribers whose domain name corresponds to the domain map name. You can also create a default domain map that the router uses for subscribers whose username does not include a domain name or has a non-matching domain name.

Domain maps apply subscriber-related characteristics such as profiles (access, dynamic, and tunnel), target and AAA logical system mapping, address pool usage, and PADN routing information.

You configure domain maps at the [edit access domain] hierarchy level.

[Subscriber Access]

•

L2TP LAC support for subscriber management (MX Series routers)—You can now configure an L2TP access concentrator (LAC) on MPC-equipped MX Series routers.

As part of the new L2TP LAC support, you can configure how the router selects a tunnel for a PPP subscriber from among a set of available tunnels. The default tunnel selection method is to fail over between tunnel preference levels. When a PPP user tries to log in to a domain, the router attempts to connect to a destination in that domain by means of the associated tunnel with the highest preference level. If the destination is unreachable, the router then moves to the next lower preference level and repeats the process. No configuration is required for this tunnel selection method.

You can include the fail-over-within-preference statement at the [edit services l2tp] hierarchy level to configure tunnel selection failover within a preference level. With this method, when the router tries to connect to a destination and is unsuccessful, it selects a new destination at the same preference level. If all destinations at a preference level are marked as unreachable, the router does not attempt to connect to a destination at that level. It drops to the next lower preference level to select a destination. If all destinations at all preference levels are marked as unreachable, the router chooses the destination that failed first and tries to make a connection. If the connection fails, the router rejects the PPP user session without attempting to contact the remote router.

By default, the router uses a round-robin selection process among tunnels at the same preference level. Include the weighted-load-balancing statement at the statement at the [edit servicesl2tp] hierarchy level to specify that the tunnel with the highest weight within a preference is selected until its maximum sessions limit is reached. Then the

JUNOS OS 10.4 Release Notes

tunnel with the next highest weight is selected until its limit is reached, and so on. The tunnel with the highest configured maximum sessions value has the greatest weight.

Another feature of L2TP LACs on MX Series routers is the ability to control whether the LAC sends the Calling Number AVP 22 to the LNS. The AVP value is derived from the Calling-Station-Id and identifies the interface that is connected to the customer in the access network. By default, the LAC includes this AVP in ICRQ packets it sends to the LNS. In some networks you may wish to conceal your networkaccessinformation. To prevent the LAC from sending the Calling Number AVP to the LNS, include the

disable-calling-number-avp statement at the [edit services l2tp] hierarchy level.

[Subscriber Access]

•

Support for dynamic interface sets (M120, M320, and MX Series routers)—Enables you to configure sets of subscriber interfaces in dynamic profiles. Interface sets are used for providing hierarchical scheduling. Previously, interface sets were supported for interfaces configured in the static hierarchies only.

Supported subscriber interfaces include static and dynamic demux, static and dynamic PPPoE, and static and dynamic VLAN interfaces.

To configure an interface set in a dynamic profile, include the interface-set

interface-set-name statement at the [edit dynamic-profiles interfaces] hierarchy level.

To add a subscriber interface to the set, include the interface interface-name unit

logical-unit-number statement at the [edit dynamic-profiles interfaces interface-set interface-set-name]hierarchy level. Youapplytrafficshaping and scheduling parameters

to the interface-set by including the interface-set interface-set-name and

output-traffic-control-profile profile-name statements at the static [editclass-of-service interfaces] hierarchy level.

A new Juniper Networks VSA (attribute 26-130) is now supported for the interface set name, and includes a predefined variable, $junos-interface-set-name. The VSA is supported for RADIUS Access-Accept messages only; change of authorization (CoA) requests are not supported.

[Subscriber Access]

•

Support for service session accounting statistics (MX Series routers)—You can now capture accounting statistics for subscriber service sessions. Subscriber management supports service session accounting based on service activation and deactivation, as well as interim accounting. Time-based accounting is supported for all service sessions. Time and volume-based accounting is supported for classic firewall filter and fast update firewall filter service sessions only.

To provide volume service accounting, the well-known accounting counter (junos-dyn-service-counter) must also be configured for the classic firewall filter and fast update firewall filter service. You define the counter at the [edit firewall family

family filter filter term term then] hierarchy level.

+ 186 hidden pages

Juniper JUNOS OS 10.4 - RELEASE NOTES REV 6, JUNOS OS 10.4 Release Note

Specifications and Main Features

Frequently Asked Questions

User Manual