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

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.
•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.
11Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

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).
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]
Copyright © 2010, Juniper Networks, Inc.12
JUNOS OS 10.4 Release Notes

Junos OS XML API and Scripting
New Junos OS XML API operational request tag elements—Table 1 on page 13 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.
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
13Copyright © 2010, Juniper Networks, Inc.
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
<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
<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>show redundant-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
<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
Copyright © 2010, Juniper Networks, Inc.14
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-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
<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]
15Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

•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]
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]
Routing Policy and Firewall Filters
•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.
Copyright © 2010, Juniper Networks, Inc.16
JUNOS OS 10.4 Release Notes

The following sample shows the new system log 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
•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]
•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,
disabling traps for passive OSPF interfaces reduces the number of notifications received
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 state changes in a passive OSPF 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]
17Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

•[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 updated to 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 local autonomous
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]
•[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.
Copyright © 2010, Juniper Networks, Inc.18
JUNOS OS 10.4 Release Notes

When you configure NAT-PT with DNS ALG support, 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.
[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 Configuration Guide. You can apply
19Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

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. You can 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
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;
}
}
}
Copyright © 2010, Juniper Networks, Inc.20
JUNOS OS 10.4 Release Notes