Juniper JUNOS OS 10.4 RELEASE NOTES Instruction Manual

Junos®OS 10.4 Release Notes
Release 10.4R1
08 December 2010
Revision 1
These release notes accompany Release 10.4R1 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
ClassofService..............................................6
InterfacesandChassis.........................................7
JunosOSXMLAPIandScripting................................13
Layer2EthernetServices......................................15
MPLSApplications...........................................16
Multicast...................................................16
Routing Policy and Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
RoutingProtocols............................................17
ServicesApplications.........................................18
SubscriberAccessManagement................................23
SystemLogging.............................................33
VPNs .....................................................34
Changes in Default Behavior and Syntax in Junos OS Release 10.4 for M
Series, MX Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 37
ClassofService.............................................37
ForwardingandSampling.....................................37
InterfacesandChassis........................................37
JunosOSXMLAPIandScripting................................39
MPLSApplication...........................................40
PlatformandInfrastructure....................................41
RoutingProtocols............................................41
Services Applications ........................................43
1Copyright © 2010, Juniper Networks, Inc.

SubscriberAccessManagement...............................44
User Interface and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
VPNs .....................................................48
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series
Routers....................................................48
CurrentSoftwareRelease.....................................48
Previous Releases ...........................................55
Errata and Changes in Documentation for Junos OS Release 10.4 for M
Series, MX Series, and T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Changes to the Junos OS Documentation Set . . . . . . . . . . . . . . . . . . . . . 66
Errata .....................................................67
Upgrade and Downgrade Instructions for Junos OS Release 10.4 for M Series,
MXSeries,andTSeriesRouters................................70
Basic Procedure for Upgrading to Release 10.4 . . . . . . . . . . . . . . . . . . . . . 71
Upgrading a Router with Redundant Routing Engines . . . . . . . . . . . . . . . 73
Upgrading Juniper Network Routers Running Draft-Rosen Multicast
VPNtoJunosOSRelease10.1...............................73
Upgrading the Software for a Routing Matrix . . . . . . . . . . . . . . . . . . . . . . 75
UpgradingUsingISSU........................................76
Upgrading from Junos OS Release 9.2 or Earlier on a Router Enabled
forBothPIMandNSR.....................................76
Upgrade Policy for Junos OS Extended End-Of-Life Releases . . . . . . . . . 77
DowngradefromRelease10.4..................................78
Junos OS Release Notes for Juniper Networks SRX Series Services Gateways
andJSeriesServicesRouters......................................79
New Features in Junos OS Release 10.4 for SRX Series Services Gateways
andJSeriesServicesRouters..................................79
SoftwareFeatures...........................................80
Hardware Features—SRX210, SRX220, and SRX240 Services
Gateways .............................................100
Hardware Features—SRX220 Services Gateway with Power Over
Ethernet ...............................................101
Hardware Features—SRX1400 Services Gateway . . . . . . . . . . . . . . . . . 104
Hardware Features—SRX3400 and SRX3600 Services Gateways . . . . 107
Advertising Bandwidth for Neighbors on a Broadcast Link Support . . . . . . . 108
Group VPN Interoperability with Cisco’s GET VPN . . . . . . . . . . . . . . . . . . . . 108
Changes in Default Behavior and Syntax in Junos OS Release 10.4 for SRX
Series Services Gateways and J Series Services Routers . . . . . . . . . . . . 109
ApplicationIdentification.....................................110
Application Layer Gateways (ALGs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
AppSecure .................................................111
Command-LineInterface(CLI).................................112
Configuration...............................................114
Dynamic VPN ..............................................115
FlowandProcessing.........................................115
Installation.................................................117
Integrated Convergence Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
InterfacesandRouting.......................................117
Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . 118
Copyright © 2010, Juniper Networks, Inc.2
JUNOS OS 10.4 Release Notes

J-Web.....................................................119
ManagementandAdministration...............................121
Multilink...................................................122
PoweroverEthernet(PoE)....................................123
Security ...................................................123
VirtualLANs(VLANs)........................................123
WirelessLAN(WLAN).......................................124
UnsupportedCLI...............................................124
Accounting-OptionsHierarchy.................................124
AX411AccessPointHierarchy..................................124
ChassisHierarchy...........................................124
Class-of-ServiceHierarchy....................................125
Ethernet-SwitchingHierarchy.................................125
FirewallHierarchy...........................................125
InterfacesCLIHierarchy......................................125
Protocols Hierarchy .........................................129
RoutingHierarchy...........................................130
Services Hierarchy..........................................130
SNMPHierarchy............................................130
SystemHierarchy............................................131
IPv6andMVPNCLI..........................................131
Known Limitations in Junos OS Release 10.4 for SRX Series Services
Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . 133
AppSecure ................................................133
ChassisCluster.............................................133
Command-LineInterface(CLI)................................134
Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . . . . . . . . . . 135
DynamicVPN..............................................135
FlowandProcessing.........................................135
Hardware .................................................136
InterfacesandRouting.......................................137
Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . 138
IPv6support...............................................139
J-Web ....................................................139
NetScreen-Remote .........................................140
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Point-to-Point Protocol over Ethernet (PPPoE) . . . . . . . . . . . . . . . . . . . 141
Security ...................................................141
SNMP.....................................................141
Switching..................................................141
Unified Threat Management (UTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
VPNs.....................................................142
WirelessLAN(WLAN).......................................142
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J
SeriesServicesRouters......................................143
Outstanding Issues In Junos OS Release 10.4 for SRX Series Services
Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . 143
Resolved Issues in Junos OS Release 10.4 for SRX Series Services
Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . 161
3Copyright © 2010, Juniper Networks, Inc.

Errata and Changes in Documentation for Junos OS Release 10.4 for SRX
Series Services Gateways and J Series Services Routers . . . . . . . . . . . . 166
Changes to the Junos OS Documentation Set . . . . . . . . . . . . . . . . . . . . 166
Errata for the Junos OS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 166
Errata for the Junos OS Hardware Documentation . . . . . . . . . . . . . . . . . 170
Hardware Requirements for Junos OS Release 10.4 for SRX Series Services
Gateways and J Series Services Routers . . . . . . . . . . . . . . . . . . . . . . . . . 174
Transceiver Compatibility for SRX Series and J Series Devices . . . . . . . . 174
Power and Heat Dissipation Requirements for J Series PIMs . . . . . . . . . 174
Supported Third-Party Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
J Series CompactFlash and Memory Requirements . . . . . . . . . . . . . . . . 175
MaximizingALGSessions........................................176
Integrated Convergence Services Not Supported . . . . . . . . . . . . . . . . . . . . . 176
Upgrade and Downgrade Instructions for Junos OS Release 10.4 for SRX
Series Services Gateways and J Series Services Routers . . . . . . . . . . . . . 177
Upgrade Policy for Junos OS Extended End-Of-Life Releases . . . . . . . . 177
Junos Software Release Notes for EX Series Switches . . . . . . . . . . . . . . . . . . . . . 178
New Features in Junos OS Release 10.4 for EX Series Switches . . . . . . . . . . 178
Hardware .................................................178
Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
ClassofService(CoS).......................................179
FibreChanneloverEthernet...................................179
High Availability ............................................179
Infrastructure ..............................................179
ManagementandRMON.....................................179
PacketFilters..............................................180
VirtualChassis.............................................180
Changes in Default Behavior and Syntax in Junos OS Release 10.4 for EX
SeriesSwitches............................................180
Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
ClassofService............................................180
Limitations in Junos OS Release 10.4 for EX Series Switches . . . . . . . . . . . . . 181
Access Control and Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
ClassofService.............................................181
FirewallFilters..............................................181
Hardware .................................................182
HighAvailability ............................................182
Infrastructure ..............................................182
Interfaces .................................................183
Outstanding Issues in Junos OS Release 10.4 for EX Series Switches . . . . . . 184
Access Control and Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Bridging, VLANs, and Spanning Trees . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
EthernetSwitching..........................................185
Firewall Filters .............................................185
Infrastructure ..............................................185
Interfaces .................................................186
J-WebInterface............................................186
SpanningTreeProtocols.....................................188
Copyright © 2010, Juniper Networks, Inc.4
JUNOS OS 10.4 Release Notes

Resolved Issues in Junos OS Release 10.4 for EX Series Switches . . . . . . . . 189
Access Control and Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Firewall Filters .............................................189
Infrastructure ..............................................189
Interfaces .................................................189
J-WebInterface............................................190
Layer2andLayer3Protocols.................................190
ManagementandRMON.....................................190
Errata in Documentation for Junos OS Release 10.4 for EX Series
Switches ..................................................191
J-WebInterface.............................................191
Upgrade and Downgrade Instructions for Junos OS Release 10.4 for EX
SeriesSwitches.............................................191
UpgradingSoftware.........................................191
Upgrade Policy for Junos OS Extended End-Of-Life Releases . . . . . . . . 193
Upgrading or Downgrading from Junos OS Release 9.4R1 for EX Series
Switches ..............................................193
Upgrading from Junos OS Release 9.3R1 to Release 10.4 for EX Series
Switches ..............................................193
Junos OS Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
DocumentationFeedback...........................................195
RequestingTechnicalSupport........................................195
RevisionHistory....................................................197
5Copyright © 2010, Juniper Networks, Inc.

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 37
•Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers on page 48
•Errata and Changes in Documentation for Junos OS Release 10.4 for M Series, MX
Series, and T Series Routers on page 66
•Upgrade and Downgrade Instructions for Junos OS Release 10.4 for M Series, MX Series,
and T Series Routers on page 70
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;
Copyright © 2010, Juniper Networks, Inc.6
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]
Interfaces and Chassis
•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
7Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

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.
To specify ATM children within a container interface, use the container-list cinstatement
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 cinstatement 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
Copyright © 2010, Juniper Networks, Inc.8
JUNOS OS 10.4 Release Notes

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.
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]
•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 communicates with a NAT endpoint
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 Interface,System Basics and Services Command Reference]
9Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

•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.
[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
Copyright © 2010, Juniper Networks, Inc.10
JUNOS OS 10.4 Release Notes