Juniper JUNOS OS 10.4 Release note

Brand: Juniper

Model: JUNOS OS 10.4

Type: Release note

This manual is also suitable for

JUNOS OS 10.4 - S REV 6

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 Networks M 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

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

JUNOS OS 10.4 Release Notes

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

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

JUNOS OS 10.4 Release Notes

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 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 Routers on 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.4 for M 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 provider edge 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 traffic is 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 traffic is assured to have the bandwidth configured for the 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-policer statements 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;

JUNOS OS 10.4 Release Notes

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-policer and 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-number classifiers] hierarchy level. The ATM interface must 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.

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

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;

}

JUNOS OS 10.4 Release Notes

[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—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. 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.

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

To specify ATM children within 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.

JUNOS OS 10.4 Release Notes

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

external server (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.

Class of service (CoS) enables enhanced egress queuing, buffering, and traffic shaping.

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.

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

The SONET/SDH OC48/STM 16 PIC supports CoS features similar to those in IQ2E

PICs, in terms of behavior and configuration statements. 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 traffic that 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. Transit statistics are not accounted separately

because the IQ2 and IQ2E PICs cannot differentiate between transit and

local statistics.

JUNOS OS 10.4 Release Notes

[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.

Interoperability with interfaces from other 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 following restrictions

on commit:

•

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

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

•

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)—Provides a 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).

JUNOS OS 10.4 Release Notes

Once the control queue feature is disabled, then the Layer 2 and Layer 3 control packets

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.

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

Response Tag ElementCLI CommandRequest Tag Element

NONErequest dhcpv6 server reconfigure<request-

dhcpv6-server-

reconfigure-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

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

get_amt_tunnel_information

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

get_rps_chassis_information

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

get_bios_version_information

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

congestion-

notification-

information>

get_cos_congestion_notification_information

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

get_firewall_log_information

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

get_interface_information

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

identifier-origin-

information> get_isis_context_

identifier_origin_information

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

get_isis_database_information

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

get_mpls_cspf_information

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

get_authentication_pending_table

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

<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-supplypower-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

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

get_idp_policy_template_information

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

charging statistics

<get-service-border-signaling-

gateway-charging-status>

get_service_border_signaling_

gateway_charging_status

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

charging status

<get-service-bsg-denied-messages>

get_service_bsg_denied_messages

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

accounting-statistics-information>

get_services_l2tp_radius_acco

unting_statistics_information

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

get_service_softwire_statistics

_information

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

conversation_

information>

get_service_sfw_conversation

_information

<service-fwnat-flow-table-

information>

show services softwire flows<get_service_

sfw_flow_analysis_

information>

get_service_sfw_flow_analysi

s_information

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

flow_table_information>

get_service_sfw_flow_table_i nformation

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

<service-sfw-flow-analysis-information>show services stateful-firewall flow-analysis<get_service_sfw_sip_register-

information>

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

<clock-synchronization-

esmc-transmit>

show synchronous-ethernet esmc transmit<get_synchronous_ethernet_esmc_transmit>

get_synchronous_ethernet_esmc_transmit

NONEshow synchronous-ethernet

global-information

<get_synchronous_ethernet_global_information>

get_-synchronous_ethernet_global_information

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

processes_information>

get_system_resource_cleanup_

processes_information

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

get_rollback_information

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

get_dhcp_binding_information

<clock-synchronization-

clear-output>

clear synchronous-

ethernet esmc

statistics

<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

configure the 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.

[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]

JUNOS OS 10.4 Release Notes

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, multicast session 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

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

•

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

JUNOS OS 10.4 Release Notes

Page is loading ...

Juniper JUNOS OS 10.4 Release note

Brand: Juniper

Model: JUNOS OS 10.4

Type: Release note

This manual is also suitable for

JUNOS OS 10.4 - S REV 6

Download PDF

report

Juniper JUNOS OS 10.4 Release note

This manual is also suitable for

Juniper JUNOS OS 10.4 Release note

Related papers

Other documents