Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010 Release Note
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. JUNOS 10.1 - S 5-13-2010
  6. Release note
Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010 Release Note

Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010 Release Note

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Juniper Networks® JUNOS® 10.1 Software
Release Notes
Release 10.1R2
13 May 2010
Revision 1
Contents
These release notes accompany Release 10.1R2 of the JUNOS Software. They describe
device documentation and known problems with the software. JUNOS Software 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 Software
Documentation Web page, which is located at
http://www.juniper.net/techpubs/software/junos.
Routers .....................................................................................................6
Series Routers ....................................................................................6
Class of Service ..................................................................................6
High Availability ...............................................................................12
Interfaces and Chassis ......................................................................12
JUNOS XML API and Scripting ..........................................................18
MPLS Applications ............................................................................21
Multiplay ..........................................................................................22
Routing Policy and Firewall Filters ....................................................23
Routing Protocols .............................................................................24
Services Applications ........................................................................27
Subscriber Access Management .......................................................27
System Logging ................................................................................36
1

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOS 10.1 - RELEASE NOTES 5-13-2010 and is the answer not in the manual?

Questions and answers

Related Manuals for Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010

Summary of Contents for Juniper JUNOS 10.1 - RELEASE NOTES 5-13-2010

  • Page 1: Table Of Contents

    These release notes accompany Release 10.1R2 of the JUNOS Software. They describe device documentation and known problems with the software. JUNOS Software 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.
  • Page 2 Upgrading from JUNOS Release 9.2 or Earlier on a Router Enabled for Both PIM and NSR ..............95 Downgrade from Release 10.1 ............96 JUNOS Software Release Notes for Juniper Networks SRX Series Services Gateways and J Series Services Routers ..........98 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers ............98...
  • Page 3 Security ..................126 Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers ..........126 [accounting-options] Hierarchy ............126 AX411 Access Point ...............126 Chassis Cluster ................126 Command-Line Interface (CLI) ............128 Dynamic VPN .................128 Flow and Processing ...............129 Hardware ..................129 Interfaces and Routing ..............130 Intrusion Detection and Prevention (IDP) ........133...
  • Page 4 JUNOS 10.1 Software Release Notes Maximizing ALG Sessions ..............181 Using Dual Chassis Cluster Control Links: Upgrade Instructions for the Second Routing Engine ..............182 Upgrade and Downgrade Instructions for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers ....183 JUNOS Software Release Notes for EX Series Switches ........184 New Features in JUNOS Release 10.1 for EX Series Switches ....184 Hardware ..................184...
  • Page 5 Upgrade and Downgrade Issues for JUNOS Release 10.1 for EX Series Switches ..................198 Upgrading or Downgrading from JUNOS Release 9.4R1 for EX Series Switches ..................198 Upgrading from JUNOS Release 9.3R1 to Release 10.1 for EX Series Switches ..................199 Upgrading from JUNOS Release 9.2 to Release 10.1 for EX Series Switches ..................199 Downgrading from JUNOS Release 10.1 to Release 9.2 for EX4200 Switches ..................200...

  • Page 6: Junos Software Release Notes For Juniper Networks M Series Multiservice Edge Routers, Mx Series Ethernet Service Routers, And T Series Core Routers

    [edit interfaces] [Class of Service] JUNOS Software Release Notes for Juniper Networks M Series Multiservice Edge Routers, MX Series Ethernet Service Routers, and T Series Core Routers...
  • Page 7 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Distribute excess bandwidth among different services for a subscriber (MX Series routers with Trio MPC/MIC interfaces) Service providers often use tiered services that must carry excess bandwidth as traffic patterns vary. By default, excess bandwidth between a configured guaranteed rate and shaping rate is shared equally among all queues, which might not be optimal for all subscribers to a service.
  • Page 8 JUNOS 10.1 Software Release Notes statement at the link-protection [edit interfaces aex aggregated-ether-options link-protection] hierarchy level. To display the active, primary, and backup link for an aggregated Ethernet interface, use the operational mode command show interfaces redundancy aex [Class of Service, Network Interfaces] Re-marking of MVPN GRE encapsulation DCSP at ASBR (MX Series routers with Trio MPC/MIC interfaces) Enables you to configure DSCP marking for GRE encapsulated packets that aligns with the service provider core CoS policy...
  • Page 9 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers GMRP GVRP LACP PVST xSTP The Layer 3 protocols supporting the preclassifier are: IGMP IPv4/IPv6 ICMP IPv4/IPv6 ISIS IPv4/IPv6 OSPF IPv4/IPv6 PIM IPv4 Router Alert IPv4/IPv6 RSVP IPv4/IPv6 VRRP The Layer 4 protocols supporting the preclassifier are:...
  • Page 10 JUNOS 10.1 Software Release Notes Flexible Ethernet encapsulation (JUNOS Release 10.0R2) Graceful Routing Engine switchover (GRES) (JUNOS Release 10.0R2) Ingress differentiated (JUNOS Release 10.0R2) Differentiated Services code point rewrite (DSCP) (JUNOS Release 10.0R2) Intelligent oversubscription (JUNOS Release 10.0R2) Integrated routing and bridging (IRB) (JUNOS Release 10.1R1) Intermediate System-to-Intermediate System (IS-IS) (JUNOS Release 10.0R2) Internet Group Management Protocol (IGMP) (excludes snooping) (JUNOS Release 10.0R2)
  • Page 11 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Shaping at the queue level Scheduling of queues based on weighted round-robin (WRR) per priority class Tricolor marking Weighted random early detection (WRED) QoS per virtual LAN (VLAN): (JUNOS Release 10.0R2) Accounting, filtering, and policing IEEE 802.1p rewrite Classification...

  • Page 12: High Availability

    JUNOS 10.1 Software Release Notes IEEE 802.1ak-2007 MVRP (MX Series routers) The Multiple VLAN Registration Protocol (MVRP) is a standards-based Layer 2 network protocol used among switches to dynamically share and update VLAN information with other bridges. VLAN information exchanged includes: The set of VLANs that currently have active members The ports through which the active members can be reached To operate MVRP, edge ports should have the static VLAN configuration.
  • Page 13 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers New 20-port Gigabit Ethernet MIC with SFP (model number MIC-3D-20GE-SFP) Supported on MX Series routers. For a list of supported MPCs, see the MX Series Line Card Guide. New Modular Port Concentrators (MPCs) and Modular Interface Cards (MICs) Supported on MX Series platforms.
  • Page 14 JUNOS 10.1 Software Release Notes (and so on) is not supported. Use the offline procedures to upgrade and integrate the remaining T1600 routers into the routing matrix. [TX Matrix Plus Hardware, System Basics and Services Command Reference] Per-unit scheduling for GRE tunnels using IQ2 PICs (M7i, M10i, M120, and M320 routers with E3 FPC) Supports enhanced IQ2 PIC and IQ2E PIC performance, adding all functionality of tunnel PICs.
  • Page 15 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Two new AC power supply modules in chassis The JUNOS Software now supports two new AC power supply modules on T640 and T1600 routers: AC Power Entry Module 10kW US and AC Power Entry Module 10kW EMEA (for U.S.
  • Page 16 JUNOS 10.1 Software Release Notes There are two ways to verify the sampled packets. The first is to include the file sampled statement at the [edit forwarding-options sampling traceoptions] hierarchy level and the statement at the local dump [edit forwarding-options family inet output flow-server server] hierarchy level, and check the sampled...
  • Page 17 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers cau4-fpc/pic/port:unit partition partition-number interface-type t1] [edit interfaces cau4-fpc/pic/port:unit partition partition-number interface-type ct1] hierarchy level. The JUNOS Software does not allow combined configurations of E1 and E3 interfaces together under a CAU4 interface.

  • Page 18: Junos Xml Api And Scripting

    JUNOS 10.1 Software Release Notes JUNOS XML API and Scripting New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers...
  • Page 19 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers New JUNOS XML API operational request tag elements Table 1 on page 19 lists the JUNOS Extensible Markup Language (XML) operational request tag elements that are new in JUNOS Release 10.1, along with the corresponding CLI command and response tag element for each one.
  • Page 20 JUNOS 10.1 Software Release Notes Table 1: JUNOS XML Tag Elements and CLI Command Equivalents New in JUNOS 10.1 (continued) Request Tag Element CLI Command Response Tag Element <get-mvrp-registration-state> show mvrp registration-state <mvrp-registration-information> get_mvrp_registration_state <get-mvrp-interface-statistics> show mvrp statistics <mvrp-interface-statistics> get_mvrp_interface_statistics <get-idp-subscriber-policy-list>...

  • Page 21: Mpls Applications

    New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers [JUNOS XML API Operational Reference] MPLS Applications Static LSPs at the ingress router You can now configure a named static LSP at the ingress router. This feature allows you to configure multiple static LSPs between two specific routers.

  • Page 22: Multiplay

    JUNOS 10.1 Software Release Notes [MPLS] Static LSP revert timer You can now configure a revert timer for ingress and transit static LSPs. After traffic has been switched to a bypass static LSP, it is typically switched back to the primary static LSP when it comes back up. There is a configurable delay in the time (called the revert timer) between when the primary static LSP comes up and when traffic is reverted back to it from the bypass static LSP.

  • Page 23: Routing Policy And Firewall Filters

    New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Integrated Multi-Services Gateway (IMSG) failed call reporting Provides more extensive statistics on failed calls through improved command output. show You can use the following existing command to display statistics on failed calls: show services border-signaling-gateway calls-failed gateway gateway-name [Multiplay Solutions, System Basics Command Reference] Integrated Multi-Services Gateway (IMSG) media release Enables the IMSG...

  • Page 24: Routing Protocols

    By default, the tracking bit is set to 1 and PIM join suppression is disabled. This is the default behavior for JUNOS Release 10.0 and earlier for Juniper Networks routers. With join suppression disabled (T-bit=1), a downstream receiving router will send join messages even if it receives identical joins for the same upstream router, as long as no other router in the network has join suppression enabled.
  • Page 25 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers specified by the timer. This is a random timer with value ranges between 0 to Max Override Interval. The timer is reset each time join suppression is triggered, and the defer period is dependent on other settings in the LAN prune delay, including propagation-delay and override-interval.
  • Page 26 JUNOS 10.1 Software Release Notes hierarchy level on all PE routers group-address source source-address pim-ssm] participating in the MVPN. Include the threshold-rate statement and specify zero as the threshold value at the [edit routing-instances routing-instance-name provider-tunnel selective group group-address source source-address] hierarchy level on all PE routers participating in the MVPN.

  • Page 27: Services Applications

    New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Services Applications FlowTapLite enhancements Extend support for interception of IPv6 packets on MX Series, M120, and M320 routers. For IPv6, the global filter taps packets from the default IPv6 routing table and does not tap packets from other VRFs.
  • Page 28 JUNOS 10.1 Software Release Notes JUNOS subscriber access scaling values (M120, M320, and MX Series routers) Table 2 on page 28 lists the DHCP, PPP, and PPPoE scaling values supported for subscriber access in this release of M120, M320, and MX Series routers.
  • Page 29 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers In this case, each subscriber connection consumes two logical interfaces: one for the VLAN logical interface and one for the pp0 logical interface. The M120, M320, and MX Series routers support a maximum of 2000 different dynamic profiles per chassis.
  • Page 30 JUNOS 10.1 Software Release Notes To enable IPv6 addressing for a static VLAN subscriber interface, include the statement at the family inet6 [edit dynamic profiles profile-name interfaces interface-name unit logical-unit-number] hierarchy level. To enable IPv6 addressing for a demux subscriber interface, include the family inet6 statement at the...
  • Page 31 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Attribute Number Attribute Name 26-129 IPv6-NdRa-Prefix 26-151 IPv6-Acct-Input-Octets 26-152 IPv6-Acct-Output-Octets 26-153 IPv6-Acct-Input-Packets 26-154 IPv6-Acct-Output-Packets 26-155 IPv6-Acct-Input-Gigawords 26-156 IPv6-Acct-Output-Gigawords 26-157 IPv6-NdRa-Pool-Name You can monitor IPv6 statistics by issuing the show subscribers show commands.
  • Page 32 JUNOS 10.1 Software Release Notes interfaces pp0 { unit $junos-interface-unit { keepalives interval seconds; no-keepalives; pppoe-options { underlying-interface "$junos-underlying-interface"; server; ppp-options { chap; pap; family inet { unnumbered-address interface-name; address address; service { input { service-set service-set-name <service-filter filter-name>; output { service-set service-set-name <service-filter filter-name>;...
  • Page 33 (retailers). In a Juniper Networks subscriber access network, you accomplish Layer 3 partitioning through the use of logical systems (LSs) and routing instances. Logical systems enable you to divide a physical router into separate, distinct, logical administrative domains.
  • Page 34 JUNOS 10.1 Software Release Notes When configuring PPPoE Layer 3 wholesale for a subscriber access network, keep the following in mind: PPPoE Layer 3 wholesaling supports the use of only the default logical system using multiple routing instances. Each routing instance must contain a loopback with one or more addresses to be used for the unnumbered interface.
  • Page 35 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers level), the statements do not support any additional chap configuration options, including the passive statement. PPP dynamic interfaces are supported only on PPPoE interfaces ( ) for this interface pp0 release.

  • Page 36: System Logging

    JUNOS 10.1 Software Release Notes For information about how to configure subscriber secure policy traffic mirroring, see the Subscriber Access Configuration Guide. [Subscriber Access] Support for PPP/PPPoE subscriber interfaces on the Trio MPC/MIC family of products (MX Series routers) Enables you to configure PPP/PPPoE subscriber interfaces that are running over the Trio MPC/MIC family of products when used on MX Series routers.
  • Page 37 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers FCD Describes messages with the FCD prefix. They are generated by the Fibre Channel process (fcd) which connects servers to disks and tape devices in a storage area network. GPRSD Describes messages with the GPRSD prefix.

  • Page 38: User Interface And Configuration

    JUNOS 10.1 Software Release Notes RPD_RA_DYN_CFG_SES_ID_MISMATCH RPD_RT_CFG_BR_CONFLICT The following system log messages are no longer documented: DFWD_CONFIG_FW_UNSUPPORTED LLDPD_PARSE_ARGS LLDPD_PARSE_BAD_SWITCH LLDPD_PARSE_CMD_ARG LLDPD_PARSE_CMD_EXTRA LLDPD_PARSE_USAGE LPDFD_DYN_SDB_OPEN_FAILED User Interface and Configuration Enhanced support for up to 64 ECMP next hops for load balancing on M10i routers with Enhanced CFEB, M320, M120, MX Series, and T Series Core routers The JUNOS Software supports configurations of 16, 32, or 64 equal-cost multipath (ECMP) next hops for RSVP and LDP LSPs on M10i routers with an...
  • Page 39 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers The enhanced ECMP limit of up to 64 ECMP next hops is also applicable for Layer 3 VPNs, Layer 2 VPNs, Layer 2 circuits, and VPLS services that resolve over an MPLS route, because the available ECMP paths in the MPLS route can also be used by such traffic.
  • Page 40 JUNOS 10.1 Software Release Notes login { class class-name { access-start HHMM; access-end HHMM; To configure user access on specific days of the week for a specified duration, include the , and statements. allowed-days access-start access-end [edit system] login { class class-name { allowed-days days-of-the-week;...
  • Page 41 New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers interfaces on which it might run. However, in a subscriber access network, static configuration of the router advertisement protocol becomes impractical because the number of interfaces that potentially need the router advertisement protocol increases substantially.

  • Page 42: Changes In Default Behavior And Syntax In Junos Release 10.1 For M Series, Mx Series, And T Series Routers

    JUNOS 10.1 Software Release Notes Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Class of Service Forwarding class to queue number maps not supported on Multiservices link services intelligent queuing (LSQ) interfaces If you configure a forwarding class map associating a forwarding class with a queue number, these maps are not supported on Multiservices link services intelligent queuing ( ) interfaces.
  • Page 43 Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers interface. If you do not configure a bandwidth for the logical interface, it is automatically set to the bandwidth configured for the physical interface. [Network Interfaces] Support for line-rate mode on 10-port 10-Gigabit Oversubscribed Ethernet (OSE) PIC (T640, T1600, TX Matrix Plus platforms)
  • Page 44 JUNOS 10.1 Software Release Notes [Network Interfaces] Commit-time warning messages at the hierarchy level are [edit interfaces] now system logged CLI commit-time warnings displayed for configuration at [edit interfaces] hierarchy level have been removed and are now logged as system log messages. This change is applicable to JUNOS Release 10.1R1 and later, 10.0R2, and 9.3R4.
  • Page 45 Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers [System Basics Command Reference] Modification to the output of the show interfaces extensive command output For IQ2E interfaces, the command output no show interfaces extensive longer displays the schedulers...

  • Page 46: Layer 2 Ethernet Services

    JUNOS 10.1 Software Release Notes [System Basics Command Reference] Layer 2 Ethernet Services Modification to the output of the show dhcp (relay or server) binding commands The output of the show dhcp server binding summary command, command, and the show dhcp relay binding summary show dhcpv6 server binding command has been modified to include the number of clients in the init...

  • Page 47: Multiplay

    Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Multiplay Border gateway function (BGF) improved efficiency and scalability through use of service interface pools You can now use service interface pools to improve the maintainability and scalability of your service set configurations.

  • Page 48: Services Applications

    JUNOS 10.1 Software Release Notes Increase in limit to external paths accepted for BGP route target filtering You can now specify for BGP to accept up to 256 external paths for route target filtering. Previously, the maximum number that you could configure was 16. The default value remains one (1).
  • Page 49 Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Default idle timeout value for UDP- and TCP-based applications Upon identification by AppID, the default idle timeout value is set to 30 seconds for UDP-based applications and 1 hour for TCP-based applications.

  • Page 50: Subscriber Access Management

    JUNOS 10.1 Software Release Notes new-transaction-input-policies [policy-and-policy-set-names] new-transaction-output-policies [policy-and-policy-set-names] [Services Interfaces, System Basics and Services Command Reference] Requirement for client-to-servicer and server-to-client signatures For certain applications that have signatures for both client-to-server and server-to-client directions, APPID (DAA) needs to see the data packets in both directions on the same session to finish the identification process.

  • Page 51: User Interface And Configuration

    Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers RADIUS interim accounting When subscriber management receives the RADIUS Acct-Interim-Interval attribute (attribute 85), RADIUS interim accounting is performed based on the value in the attribute. The router uses the following guidelines: Attribute value is within the acceptable range (10 to 1440 minutes) Accounting is updated at the specified interval.

  • Page 52: Vpns

    JUNOS 10.1 Software Release Notes [System Basics] VPNs Mirroring IRB packets as Layer 2 packets (MX Series router) If you associate an IRB with the bridge domain (or VPLS routing instance), and also configure within the bridge domain (or VPLS routing instance) a forwarding table filter with port-mirror port-mirror-instance action, then the IRB packet is mirrored as...
  • Page 53 Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers The M Series routing platforms continue to support only inet traffic for Layer 2.5 VPNs. [Network Interfaces, Translational Cross-Connect and Layer 2.5 VPNs Feature Guide, VPNs] New configuration statement for removing dynamically learned MAC addresses from the MAC address database Media access control (MAC) flush...

  • Page 54: Issues In Junos Release 10.1 For M Series, Mx Series, And T Series Routers

    JUNOS 10.1 Software Release Notes edge (NPE) router goes down, causing the multitenant unit switch to switch to the this NPE router. NOTE: This option has a similar effect in a VPLS multihoming environment with multiple multitenant unit switches connected to NPE routers, where both multitenant unit switches have pseudowires that terminate in a mesh group with local-switching configured.
  • Page 55 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers applied to the new logical interface. To resolve this problem, deactivate and activate the interface portion of the class-of-service configuration. [PR/485872] On an Ichip-based platform for strict high priority queue (SHQ), the buffer size allocated by the Packet Forwarding Engine is capped by the tx-rate.
  • Page 56 Juniper Networks default setting. As a workaround, do not issue the command. [PR/274399] On the Juniper Control System (JCS) platform, the control and management traffic for all Routing Engines shares the same physical link on the same switch module.
  • Page 57 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers If a firewall command is followed by the command in a very quick show clear succession, there is a possibility that the show command will time out. If the command is issued after a few seconds (5 seconds ideally), this issue will show not be seen.
  • Page 58 JUNOS 10.1 Software Release Notes Layer 2 Ethernet Services DHCP packets may not be processed on an auto-sensed VLAN interface if the DHCP configuration for the interface is performed after the auto-sensed VLAN interface is instantiated. As a workaround, clear the auto-sensed VLAN interface(s) after the DHCP configuration is made for the interface(s).
  • Page 59 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Internet Control Message Protocol (ICMP) cannot be forwarded out of the LS interface from a remote PE router that is in the VRF table. As a workaround, include the statement at the vrf-table-label...
  • Page 60 JUNOS 10.1 Software Release Notes ifd 153; does not exist IFRT: 'IFD Ether autonegotiation config' (opcode 163) failed The message has no operational impact. When the backup CFEB becomes the active CFEB, the message will not display. [PR/400774] On M7i routers, kernel panic may occur during route changes. [PR/439420] In some cases, the alarms displayed in FPM and the alarms shown using the show chassis alarms sfc 0 command mismatch.
  • Page 61 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers learn-vlan-1p-priority learn-vlan-1p-priority-except learn-vlan-id learn-vlan-id-except user-vlan-1p-priority user-vlan-1p-priority-except user-vlan-id user-vlan-id-except VPLS flood FTF and input FTF Simple filters Filter action 'then ipsec-sa' Filter action 'then next-hop-group' Mac-filter output accounting and output policing [PR/466990] On some M, MX, and T Series routers, when a family CCC filter is applied on multiple interfaces that belong to different L2VPN routing instances, packet loss...
  • Page 62 IS-IS may remove the preferred LSP NH. For example, IS-IS could remove an HIPRI LSP. [PR/485748] The Juniper Networks rendezvous point (RP) does not process PIM Register messages from a first-hop router in an IPv6 embedded RP group when the Register message does not have the null-bit set.
  • Page 63 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers the commit process is complete. This behavior occurs whether you have a list or regular expressions (for example, regular-expression [sip:88824.* sip:88821.* sip:88822.sip:88823.*]), or you group regular expressions using the | symbol (for example, "sip:88821.*|sip:88822.*|sip:88823.*|sip:88824.*").
  • Page 64 JUNOS 10.1 Software Release Notes Also, the commands do not clearly request system reboot request system halt fail but do not return the CLI prompt either. [PR/64899] The JUNOScript perl module for NETCONF does not support configuration-text. [PR/82004] "Local Password:" is prompted even though the authentication order has the password configured.
  • Page 65 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers On J-Web, the error message: “Fatal error: Allowed memory size..." displays when the Interfaces tab is selected. This message also displays when the Interfaces tab under Class-of-Service is selected. [PR/495825] The group inherited configuration under the hierarchy level does interface-range...
  • Page 66 JUNOS 10.1 Software Release Notes When the high priority queue number is changed under the class-of-service configuration while traffic is on. [PR/489049: This issue has been resolved.] The type-of-service (ToS) bits get truncated for IPv6 packets on a service PIC. [PR/510193: This issue has been resolved.] Forwarding and Sampling While the JUNOS Software adopts random as its sampling algorithm, the...
  • Page 67 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers In some cases during the periodic error status monitoring, error messages such as “Wi seg ucode discards in fabric stream” may be displayed on adjacent streams. These messages are cosmetic and can be ignored. [PR/481344: This issue has been resolved.] When loopback is configured on t3 under ct3, t1 under ct1, or e1 under ce1, no error syslog message is logged.
  • Page 68 JUNOS 10.1 Software Release Notes The yellow marking for the three-color-policers is incorrect. Even after the excess burst buffer is full, the yellow counters continue to increment at the same rate as the green buffers. [PR/504192: This issue has been resolved.] As a result of an incorrect configuration for the DDR memory controller, errors might be reported when a Trio-based MPC or MX80 boots.
  • Page 69 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers This is a cosmetic issue and has no impact on the router. [PR/500824: This issue has been resolved.] The SIP domain names encoded in the DHCPv6 attributes do not conform to RFC 3319.
  • Page 70 JUNOS 10.1 Software Release Notes Platform and Infrastructure When certain FPCs (T1600-FPC4-ES, T640-FPC4-1P-ES, T640-FPC1-ES, T640-FPC2-ES, and T640-FPC3-ES) receive corrupted cells via high-speed links, they might unnecessarily reboot and report the following system log error message: "Unrecoverable Error: Flist gtop bit toggled !." No reset is needed to recover from this condition.
  • Page 71 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers the Packet Forwarding Engine does not receive the expected sequence, and the FPC will crash. [PR/499315: This issue has been resolved.] On IQ2 PICs, when copy-plp is enabled under class of service, the DCU provides the wrong statistics.
  • Page 72 JUNOS 10.1 Software Release Notes In an NSR configuration, the backup Routing Engine can lose the connection to the active Routing Engine during a configuration commit. The problem occurs more often when the configuration includes a large number of routing instances. This is caused by the routing protocol process on the backup Routing Engine leaking file descriptors during commit synchronization.

  • Page 73: Previous Releases

    Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers When using a NAT DCE RPC ALG on a services PIC, the PIC might crash while processing the binding request. [PR/510997: This issue has been resolved.] Route changes might not be updated in the PIC meta-db in cases where the route messages that the PIC receives signify a change in the next-hop index.
  • Page 74 JUNOS 10.1 Software Release Notes Class of Service On the Qchip, the shaping accuracy is affected by the configured logical interface shaping rate. [PR/79319: This issue has been resolved.] The DHCP traffic may stop being processed for some subscribers under heavy login and logout conditions when the 802.1 classifiers are in use.
  • Page 75 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers workaround, deactivate the configured filter group. [PR/503609: This issue has been resolved.] After configuring a three-color-policer, a dfwc core file is generated. [PR/509742: This issue has been resolved.] High Availability On an ISSU upgrade from JUNOS Release 9.3 to any of the current higher releases, the ATM logical interfaces will flap.
  • Page 76 JUNOS 10.1 Software Release Notes Under certain conditions, when aggregate interfaces are used and the member links are located on more that one FPC, multicast traffic will not use one or more of the aggregate child links. This can happen after an FPC reboot. If the aggregate member links are located on the same FPC, this problem is not triggered.
  • Page 77 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers workaround, configure both sides in the link-discovery mode as “active.” [PR/490886: This issue has been resolved.] On the IEEE 802.1ag CFM, when the loss threshold is configured to 256, it displays a '0.' [PR/491422: This issue has been resolved.] Whenever the system gets busy, the master Routing Engine might relinquish mastership and take the line cards offline soon after.
  • Page 78 JUNOS 10.1 Software Release Notes The configured TTL set for GRE traffic is set properly for locally generated Routing Engine packets, but is not set properly for transit packets. [PR/502087: This issue has been resolved.] In JUNOS Release 10.0, if the MX-MPCs power up while the A-DPCs are offline, and if ISSU is performed, the MPCs will crash.
  • Page 79 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Network Management Under certain SNMP conditions, the following log message is displayed: M10i-RE0 pfed: PFED_NOTIF_GLOBAL_STAT_UNKNOWN: Unknown global notification stat: transit options/ttl-exceeded (re-injected) M10i-RE0 pfed: PFED_NOTIF_STAT_UNKNOWN: Unknown notification type stat: Unknown This log message might also be displayed during the installation of AI Scripts (version 2.1R2 or above) on the router.
  • Page 80 JUNOS 10.1 Software Release Notes Under some circumstances where LDP is enabled, a memory leak might occur where the routing protocol process does not free up memory. [PR/493885: This issue has been resolved.] An incorrectly changed LDP session authentication key causes the LDP session to fail, and the LDP/IGP syncronization feature stops working.
  • Page 81 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers When an aggregated SONET with a Cisco High-Level Data Link Control (HDLC) encapsulation is configured, a member link may not be marked as linkdown in the Packet Forwarding Engine if the remote end of the link is disabled. [PR/472677: This issue has been resolved.] The output of the command does not show the entire demux interface...
  • Page 82 JUNOS 10.1 Software Release Notes The L2RW does not report an error when the required L2_pgm length is longer than what the hardware can support. [PR/501318: This issue has been resolved.] On an ichip platform, when the downstream multicast member link flaps, the Packet Forwarding Engine rarely has a chance to fail multicast next-hop handling.
  • Page 83 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers router to drop the first PIM hello message to its neighbor. [PR/482903: This issue has been resolved.] Whenever a graceful Routing Engine switchover (GRES) is performed, the BMP header for the consequent updates may become corrupted until the BMP session is deactivated and activated.
  • Page 84 JUNOS 10.1 Software Release Notes The routing protocol process might crash if the router receives a flow route with a rate-limit bandwidth is less than 1000 bps. [PR/508715: This issue has been resolved.] In route reflector and ASBR VPN scenarios, the routing protocol process might crash when changes occur to a prefix in the primary table at the same time as BGP tries to send out updates via the secondary table.
  • Page 85 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers User Interface and Configuration The wildcard apply groups do not work properly in JUNOS Release 9.1 and above. [PR/425355: This issue has been resolved.] When jcs:syslog() is used in an event script, messages do not appear until another system application sends a syslog message.

  • Page 86: Errata And Changes In Documentation For Junos Software Release 10.1 For M Series, Mx Series, And T Series Routers

    JUNOS 10.1 Software Release Notes Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers on page 86 Upgrade and Downgrade Instructions for JUNOS Release 10.1 for M Series, MX Series, and T Series Routers on page 89 Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers Changes to the JUNOS Documentation Set...
  • Page 87 Errata and Changes in Documentation for JUNOS Software Release 10.1 for M Series, MX Series, and T Series Routers configured. Some LSPs with smaller allocated bandwidths receive more traffic than the ones configured with higher bandwidths. Traffic distribution does not strictly comply with the configured bandwidth allocation.
  • Page 88 JUNOS 10.1 Software Release Notes The Subscriber Access Configuration Guide and the System Basics Configuration Guide contain information about the statement. This override-nas-information statement does not appear in the CLI and is not supported. [Subscriber Access, System Basics] When you modify dynamic CoS parameters with a RADIUS change of authorization (CoA) message, the JUNOS Software accepts invalid configurations.

  • Page 89: Series, Mx Series, And T Series Routers

    Upgrade and Downgrade Instructions for JUNOS Release 10.1 for M Series, MX Series, and T Series Routers User Interface and Configuration show system statistics bridge command displays system statistics on MX Series routers. [System Basics Command Reference] VPNs mac-tlv-receive mac-tlv-send statements were removed from Release 10.0 of the JUNOS Software and are no longer visible in the [edit logical-systems...

  • Page 90: Basic Procedure For Upgrading To Release 10.1

    JUNOS 10.1 Software Release Notes Basic Procedure for Upgrading to Release 10.1 In order to upgrade to JUNOS 10.0 or later, you must be running JUNOS 9.0S2, 9.1S1, 9.2R4, 9.3R3, 9.4R3, 9.5R1, or later minor versions, or you must specify the no-validate option on the request system software install command.
  • Page 91 States and Canada) (all other customers) https://www.juniper.net/support/csc/swdist-ww/ Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives. Download the software to a local host. Copy the software to the routing platform or to your internal software distribution site.

  • Page 92: Upgrading A Router With Redundant Routing Engines

    JUNOS 10.1 Software Release Notes Adding the command reboots the router after the upgrade is validated reboot and installed. When the reboot is complete, the router displays the login prompt. The loading process can take 5 to 10 minutes. Rebooting occurs only if the upgrade is successful. NOTE: After you install a JUNOS 10.1 Release jinstall package, you cannot issue the...
  • Page 93 VPN network, you had to perform additional configuration. Remove that configuration from both the Juniper Networks routers and the other vendors’ routers. This configuration should be on Juniper Networks routers and on the other vendors’...

  • Page 94: Upgrading The Software For A Routing Matrix

    JUNOS 10.1 Software Release Notes For more information about configuring the draft-rosen Multicast VPN feature, see the JUNOS Multicast Configuration Guide. Upgrading the Software for a Routing Matrix A routing matrix can use either a TX Matrix router as the switch-card chassis (SCC) or a TX Matrix Plus router as the switch-fabric chassis (SFC).

  • Page 95: Upgrading Using Issu

    Upgrade and Downgrade Instructions for JUNOS Release 10.1 for M Series, MX Series, and T Series Routers To upgrade the software for a routing matrix, perform the following steps: Disable graceful Routing Engine switchover (GRES) on the master Routing Engine (re0) and save the configuration change to both Routing Engines.

  • Page 96: Downgrade From Release 10.1

    JUNOS 10.1 Software Release Notes enabled, use the standard reboot or ISSU procedures described in the other sections of these instructions. Because the statement was not available in JUNOS Release nonstop-routing disable 9.2 and earlier, if both NSR and an incompatible PIM feature are enabled on a router to be upgraded from JUNOS Release 9.2 or earlier to a later release, you must disable PIM before the upgrade and reenable it after the router is running the upgraded JUNOS Software and you have entered the...
  • Page 97 Upgrade and Downgrade Instructions for JUNOS Release 10.1 for M Series, MX Series, and T Series Routers New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers Related Topics on page 6 Changes in Default Behavior and Syntax in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers on page 42 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers on page 54...

  • Page 98: Junos Software Release Notes For Juniper Networks Srx Series Services Gateways And J Series Services Routers

    Software Features on page 99 Hardware Features on page 117 JUNOS Software Release Notes for Juniper Networks SRX Series Services Gateways and J Series Services Routers...

  • Page 99: Software Features

    New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Software Features Application Layer Gateways (ALGs) DNS ALG This feature is supported on SRX3400, SRX3600, SRX5600, and SRX5800 devices in addition to existing support on SRX100, SRX210, SRX240, SRX650.
  • Page 100 JUNOS 10.1 Software Release Notes SQL ALG This feature is now supported on SRX3400, SRX3600, and SRX5600, and SRX5800 devices in addition to existing support on SRX100, SRX210, SRX240, SRX650, and J Series devices. Enabling the Structured Query Language (SQL) ALG on an SRX Series or J Series device allows SQL*Net traffic in SQL redirect mode to traverse an SRX Series device by creating a TCP pinhole.
  • Page 101 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers to have a LAG link configured and 802.3ad enabled for each redundant Ethernet interface LAG on both nodes so that the aggregate links will be recognized. Standalone link aggregation group interfaces ( ) are supported on clustered devices but cannot be added to redundant Ethernet interfaces.
  • Page 102 RTP packets and direct them to a higher priority queue in order to achieve better voice quality when packet traffic is congested. Juniper Networks devices provide classification, priority queuing, and other kinds of CoS configuration under the Class-of-Service configuration hierarchy.
  • Page 103 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers The DOCSIS Mini-PIM is supported on the following SRX Series Services Gateways: SRX210 SRX240 The DOCSIS Mini-PIM has the following key features: Provides high data transfer rates of over 150 Mbps downstream Supports four downstream and four upstream channel bonding Supports quality of service (QoS) Provides interoperability with any DOCSIS-compliant cable modem...
  • Page 104 JUNOS 10.1 Software Release Notes ATM QoS (supported only when the VDSL2 Mini-PIM is operating in ADSL2 mode) MLPPP (supported only when the VDSL2 Mini-PIM is operating in ADSL2 mode) MTU size of 1500 bytes (maximum) Support for maximum of 10 PVCs (only in ADSL/ADSL2/ADSL2+ mode) Dying gasp support (ADSL and VDSL2 mode) Online insertion and removal (hot swap) for SRX650 GPIMs Online insertion and removal (OIR) functionality is supported on CPU-based and CPU-less...
  • Page 105 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers devices, however, you apply BA classifiers and rewrite rules only to logical interfaces configured with the configuration statement. family bridge You configure shapers and schedulers on transparent mode devices in the same way as on devices operating in Layer 3 mode.
  • Page 106 The TLVs leverage this information from parameters that have already been configured in the Juniper Networks JUNOS Software. LLDP-MED goes one step further, exchanging IP-telephony messages between the device and the IP telephone. These TLV messages provide detailed information on PoE policy.
  • Page 107 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Intrusion Detection and Prevention (IDP) IDP in an active/active chassis cluster This feature is supported on SRX3400, SRX3600, SRX5600, and SRX5800 devices. Intrusion Detection and Prevention (IDP) can now monitor traffic on active/active chassis clusters.
  • Page 108 JUNOS 10.1 Software Release Notes [JUNOS Software CLI Reference, JUNOS Software Security Configuration Guide] New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers...
  • Page 109 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Manual BIOS upgrade using JUNOS CLI New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers...
  • Page 110 JUNOS 10.1 Software Release Notes This feature is supported on SRX100, SRX210, SRX240, and SRX650 devices. For branch SRX Series devices, BIOS is made up of U-boot and JUNOS loader. Apart from this SRX240 and SRX650 also have U-shell binary as part of the BIOS. On SRX100, SRX210 and SRX240, there is support of Backup BIOS which constitutes a backup copy of U-boot in addition to the active copy from which the system generally boots up.
  • Page 111 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Adding jloader-srxsme... Available space: 427640 require: 2674 Mounted jloader-srxsme package on /dev/md5... Saving state for rollback ... root> show version Model: srx240h JUNOS Software Release [10.2B3] JUNOS BIOS Software Suite [10.2B3] NOTE: Installing the jloader-srxsme package puts the necessary images under directory/boot.
  • Page 112 JUNOS 10.1 Software Release Notes Verifying that images for upgrade are installed command can be used to get version of images show system firmware available for upgrade. The available version is printed under column Available version . The user needs to verify that the correct version of BIOS images available for upgrade.
  • Page 113 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers BIOS upgrade Active BIOS: Initiate the upgrade using the request system firmware upgade re bios command. root> request system firmware upgrade re bios Part Type Current Available...
  • Page 114 JUNOS 10.1 Software Release Notes Monitor the status of upgrade using the command. show system firmware root> show system firmware Part Type Current Available Status version version Routing Engine 0 RE BIOS Routing Engine 0 RE BIOS Backup 1 PROGRAMMING Routing Engine 0 RE FPGA 12.3.0...
  • Page 115 New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers To support the credit-based flow control extensions described in [RFC–4938], PPPoE peers can now grant each other forwarding credits. The grantee can forward traffic to the peer only when it has a sufficient number of credits to do so.
  • Page 116 JUNOS 10.1 Software Release Notes pp0.1000 Index 71 State: Down, Session ID: 1, Service name: None, Configured AC name: None, Session AC name: None, Remote MAC address: 00:00:00:00:00:00, Auto-reconnect timeout: Never, Idle timeout: Never, Underlying interface: ge-0/0/1.0 Index 70 PADG Credits: enabled Dynamic bandwidth: enabled Virtual LANs (VLANs) Flexible Ethernet services This feature is supported on SRX210, SRX240,...

  • Page 117: Hardware Features

    3 Mbps. The SRX210 device has a 3G ExpressCard slot on the back panel. The SRX210 device supports the Juniper Networks wireless modems listed in Table 6 on page 117. Table 6: Juniper Networks Wireless Modems Supported by the SRX210 Device Wireless Cards Release Supported EXPCD-3G-HSPA-T- 3G UMTS ExpressCard for GSM and UMTS Networks, JUNOS Release 10.1.

  • Page 118: Application Layer Gateways (Algs)

    JUNOS 10.1 Software Release Notes Application Layer Gateways (ALGs) The following CLI commands have been removed as part of RPC ALG data structure cleanup: clear security alg msrpc portmap clear security alg sunrpc portmap show security alg msrpc portmap show security alg sunrpc portmap show security alg msrpc object-id-map CLI command has a chassis cluster node option to permit the output to be restricted to a particular node or to query...

  • Page 119: Command-Line Interface (Cli)

    Changes In Default Behavior and Syntax in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Command-Line Interface (CLI) Changes In Default Behavior and Syntax in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers...
  • Page 120 JUNOS 10.1 Software Release Notes On AX411 Access Points, the possible completions available for the CLI command set wlan access-point < ap_name > radio < radio_num > radio-options channel have changed from previous Implementations. number ? Now this CLI command displays the following possible completions: Example 1: user@host# set wlan access-point ap6 radio 1 radio-options channel number ? Possible completions:...
  • Page 121 Changes In Default Behavior and Syntax in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers The output of this CLI command on SRX Series devices differs from previous implementations on other devices. Note the following sample output: show security monitoring fpc 0 FPC 0 PIC 0...

  • Page 122: Configuration

    JUNOS 10.1 Software Release Notes On SRX Series devices, the show system storage partitions command now displays the partitioning scheme details on SRX Series devices. Example 1: show system storage partitions (dual root partitioning) user@host# show system storage partitions Boot Media: internal (da0) Active Partition: da0s2a Backup Partition: da0s1a Currently booted from: active (da0s2a)

  • Page 123: Flow And Processing

    Changes In Default Behavior and Syntax in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX100, SRX210, SRX240 and, SRX650 devices, the current JUNOS Software default configuration is inconsistent with the one in Secure Services Gateways, thus causing problems when users migrate to SRX Series devices.

  • Page 124: Interfaces And Routing

    JUNOS 10.1 Software Release Notes Remove link-layer-overhead from [ls-0/0/0 unit 0] , if configured. If the LFI forwarding class is mapped to no-fragmentation fragmentation-map and the configuration hierarchy is enabled on in JUNOS Release lsq-0/0/0 10.1, then interleave-fragments under [ls-0/0/0 unit 0] Adjust classifier configured for LFI on lsq-0/0/0 under...

  • Page 125: J-Web

    Changes In Default Behavior and Syntax in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers source address, and destination address is blocked. For more information, see the JUNOS Software CLI Reference. On SRX3400 and SRX3600 devices in Layer 2 and Layer 3 integrated mode, mode, 30 percent to 40 percent of the logs created in IDP are not exited from IDP.

  • Page 126: Security

    JUNOS 10.1 Software Release Notes save reset Once the system is booted from the USB storage device, take a snapshot on the external CompactFlash using the request system snapshot media external command. NOTE: Once the snapshot has been taken on the external CompactFlash, we recommend you to set the at the U-boot prompt.
  • Page 127 Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers , and All multicast protocols pd-0/0/0 pe/0/0/0 mt-0/0/0 lt-0/0/0 Real-time performance monitoring (RPM) WXC Integrated Services Module (WXC ISM 200) ISDN BRI Layer 2 Ethernet switching The factory default configuration for SRX100, SRX210, and SRX240 devices automatically enables Layer 2 Ethernet switching.

  • Page 128: Command-Line Interface (Cli)

    JUNOS 10.1 Software Release Notes J Series devices have the following limitations: A Fast Ethernet port from a 4-port Ethernet PIM cannot be used as a fabric link port in a chassis cluster. On SRX3400, SRX3600, SRX5600, and SRX5800 devices, in-service software upgrade (ISSU) does not support version downgrading.

  • Page 129: Flow And Processing

    Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Flow and Processing Maximum concurrent SSH, Telnet, and Web sessions—On SRX210, SRX240, and SRX650 devices, the maximum number of concurrent sessions is as follows: Sessions SRX210 SRX240...

  • Page 130: Interfaces And Routing

    JUNOS 10.1 Software Release Notes Color-aware mode of a three-color-policer Filter-specific policer Forwarding class as action of a policer Logical interface policer Logical interface three-color policer Logical interface bandwidth policer Packet loss priority as action of a policer Packet loss priority as action of a three-color-policer On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the following features are not supported by a firewall filter: Policer action...
  • Page 131 Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers 15 seconds, during which the LED for the RJ-45 port might go up and down intermittently. Similarly when the RJ-45 medium is active and an SFP link is brought up, the interface will transition to the SFP medium, and this transition could also take a few seconds.
  • Page 132 JUNOS 10.1 Software Release Notes set protocols pim apply-groups group apply-groups-except group family inet 6 set protocols pim apply-groups group apply-groups-except group disable family inet 6 set protocols pim assert-timeout timeout-value family inet6 set protocols pim disable apply-groups group family inet 6 set protocols pim disable apply-groups-except group family inet 6 set protocols pim disable export export-join-policy family inet 6 set protocols pim disable dr-election-on-p2p family inet 6...

  • Page 133: Intrusion Detection And Prevention (Idp)

    Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Intrusion Detection and Prevention (IDP) On SRX3400, SRX3600, SRX5600, and SRX5800 devices, application-level distributed denial-of-service (application-level DDoS) detection does not work if two rules with different application-level DDoS applications process traffic going to a single destination application server.

  • Page 134: J-Web

    JUNOS 10.1 Software Release Notes On SRX Series devices, the following IDP policies are supported: DMZ_Services DNS_Service File_Server Getting_Started IDP_Default Recommended Web_Server IDP deployed in both active/active and active/passive chassis clusters has the following limitations: No inspection of sessions that fail over or fail back. The IP address action table is not synchronized across nodes.

  • Page 135: Netscreen-Remote

    Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers NetScreen-Remote On SRX Series devices, NetScreen-Remote is not supported in JUNOS Release 10.1. Network Address Translation (NAT) On SRX3400, SRX3600, SRX5600, and SRX5800 devices, IKE negotiations involving NAT traversal do not work if the IKE peer is behind a NAT device that will change the source IP address of the IKE packets during the negotiation.

  • Page 136: Performance

    J Series devices now support IDP and UTM functionality. Under heavy network traffic in a few areas of functionality, such as NAT and IPsec VPN, performance is still being improved to reach the high levels to which Juniper Networks is consistently committed.

  • Page 137: Issues In Junos Release 10.1 For Srx Series Services Gateways And J Series Services Routers

    Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Related Topics Series Services Routers on page 98 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers on page 137 Errata and Changes in Documentation for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers on page 163...
  • Page 138 JUNOS 10.1 Software Release Notes Authentication On J Series devices, your attempt to log in to the router from a management device through FTP or Telnet might fail if you type your username and password in quick succession before the prompt is displayed, in some operating systems. As a workaround, type your username and password after getting the prompts.
  • Page 139 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On J Series devices, when you commit a configuration for a node belonging to a chassis cluster, all the redundancy groups might fail over to node 0. If graceful protocol restart is not configured, the failover can destabilize routing protocol adjacencies and disrupt traffic forwarding.
  • Page 140 JUNOS 10.1 Software Release Notes caused by a failure of the SNMP walk on the backup (secondary) node. As a workaround, use a master-only IP address across the cluster so that you can query a single IP address and that IP address will always be the master for redundancy group 0.
  • Page 141 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX5600 devices, low-impact in-service software upgrade (ISSU) chassis cluster upgrade does not succeed with the option when no-old-master-upgrade you upgrade from JUNOS Release 9.6R2 to JUNOS Release 10.1. [PR/471235] On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the secondary node displays incorrect interface status after a low-impact in-service software upgrade (ISSU) from JUNOS Release 9.6R2 to JUNOS Release 10.1R1.
  • Page 142 JUNOS 10.1 Software Release Notes Enhanced Switching On J Series devices, if the access port is tagged with the same VLAN that is configured at the port, the access port accepts tagged packets and determines the MAC. [PR/302635] Flow and Processing On J Series devices, even when forwarding options are set to drop packets for the ISO protocol family, the device forms End System-to-Intermediate System (ES-IS) adjacencies and transmits packets because ES-IS packets are Layer 2...
  • Page 143 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX650 devices, the uplinks to the CPU can be exhausted and the system can be limited to 2.5 GB throughput traffic when the device is using similar kinds of source MAC addresses.
  • Page 144 JUNOS 10.1 Software Release Notes On SRX240 PoE and J Series devices, packet drops are seen on the interface when transit traffic with a frame length of 128 bytes is sent. [PR/455714] On SRX5600 and SRX5800 devices, system log messages are not generated when CPU utilization returns to normal.
  • Page 145 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers slots 2 to 4 or 6 to 8, connecting to the 20-gigabit connector in slots 2 or 6, respectively. [PR/444511] On SRX5600 devices, during a Routing Engine reboot when processes are being shut down, a rare race condition occurs that can lead to a Routing Engine kernel crash.
  • Page 146 JUNOS 10.1 Software Release Notes The peer call server configuration for the media gateway page in J-Web does not correctly display the port number field when TCP is used as the transport. [PR/445734] When you click the trunk-group field in J-Web, the configured trunk values are not displayed.
  • Page 147 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX and J Series devices, the RPM operation will not work for the probe-type tcp-ping when the probe is configured with the option destination-interface. [PR/424925] On SRX650 devices, the following loopback features are not implemented for T1/E1 GPIMs:...
  • Page 148 JUNOS 10.1 Software Release Notes On SRX3400, SRX3600, SRX5600, and SRX5800 devices, when you configure the SAP listen option using the command in the CLI, listening protocol sap listen fails in both sparse and sparse-dense modes. [PR/441833] On J Series devices, one member link goes down in a Multilink (ML) bundle during bidirectional traffic with Multilink Frame Relay (MFR).
  • Page 149 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX210 High Memory devices, IGMP v2 JOINS messages are dropped on an integrated routing and bridging (IRB) interface. As a workaround, enable IGMP snooping to use IGMP over IRB interfaces. [PR/492564] On SRX100 and SRX210 devices, every time the VDSL2 PIM is restarted in the ADSL mode, the first packet passing through the PIM will be dropped.
  • Page 150 JUNOS 10.1 Software Release Notes On SRX3400, SRX3600, SRX5600 and SRX5800 devices, if you want to change to dedicated mode, the configuration of the security forwarding-process application-services maximize-idp-sessions command should be done right before rebooting the device. This should be done to avoid recompiling IDP policies during every commit.
  • Page 151 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers J-Web On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the LEDs on the Routing Engine and PICs are not shown as green when they are up and online on the J-Web Chassis View.
  • Page 152 JUNOS 10.1 Software Release Notes On SRX100 devices, in J-Web users can configure the scheduler without entering any stop date. The device submits the scheduler successfully, but the submitted value is not displayed on the screen or saved in the device. [PR/439636] On SRX100, SRX210, SRX240, and SRX650 devices, in J-Web the associated classifiers for a logical interface might not be mapped properly dscp...
  • Page 153 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX5600 devices, when the system is in an unstable state (for example SPU reboot), NFS might generate files under the directory, residual.nfs /var/tmp which can occupy the disk space for a very long time. As a workaround, run the request sys storage cleanup command to clean up when the system has low disk space.
  • Page 154 JUNOS 10.1 Software Release Notes For source NAT, the ip address displayed in log should be 4.0.0.0->0.0.0.0. [PR/505454] Power over Ethernet (PoE) On SRX240 and SRX210 devices, the output of the PoE operational commands takes roughly 20 seconds to reflect a new configuration or a change in status of the ports.
  • Page 155 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers not get affected after Routing Engine failover if the Infranet Controller auth table mapping action is configured as . [PR/416843] always provision auth table On SRX3400, SRX3600, SRX5600, and SRX5800 devices, you should not configure rulebase-DDoS rules that have two different application-DDoS objects to run on one destination service because the traffic destined to one application server can encounter more than one rule.
  • Page 156 JUNOS 10.1 Software Release Notes USB Modem On SRX210, SRX100, SRX240, and SRX650 devices, when you restart fwdd at the dial-out side, the umd interface goes down and the call never gets connected. As a workaround, disable the dialer interface and restart the forwarding daemon. Enable the dialer interface when the forwarding daemon is up and running.
  • Page 157 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Virtual LANs (VLANs) On SRX650 devices, when VLAN tagging is configured and traffic is sent, the output of show interfaces ge-0/0/1 media detail VLAN tagged frame count is not shown.

  • Page 158: Resolved Issues In Junos Release 10.1 For Srx Series Services Gateways And J Series Services Routers

    JUNOS 10.1 Software Release Notes WXC Integrated Services Module When two J Series devices with WXC Integrated Services Modules (WXC ISM 200s) installed are configured as peers, traceroute fails if redirect-wx is configured on both peers. [PR/227958] On J6350 devices, JUNOS Software does not support policy-based VPN with WXC Integrated Services Modules (WXC ISM 200s).
  • Page 159 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Flow and Processing On SRX210 devices, the lowest rate ATM CoS PCR supported was 64 Kbps. The ping operation did not reach an ATM interface with a PCR lower than 64 Kbps. [PR/470994: This issue has been resolved.] On SRX3400, SRX3600, SRX5600, and SRX5800 devices, in Layer 2 mode, IGMP and multicast were supported only on the 224.X.X.X address.
  • Page 160 JUNOS 10.1 Software Release Notes The SRX210 device allowed the FXS 2 port to be configured as a station and as an FXS trunk concurrently. In this case, the system did not display a commit error. [PR/473561: This issue has been resolved.] For SIP trunk to FXO trunk calls routed through the peer call server, the SRX Series device removed the called party number in the SIP INVITE messages.
  • Page 161 Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers On SRX100, SRX210, SRX240, SRX650, and J Series devices, in J-Web configuration for the routing feature, when you entered double quotation marks in the text boxes that accepted characters (for example, protocol name, file name, and description), then you could not delete the data with double quotation marks through J-Web.
  • Page 162 JUNOS 10.1 Software Release Notes Management and Administration On SRX5600 and SRX5800 devices, the simple filter did not work after reboot of the new primary node. [PR/486181: This issue has been resolved.] Network Address Translation (NAT) On SRX210 and SRX240 devices, source NAT using interface IP address on the interface was not working.

  • Page 163: Errata And Changes In Documentation For Junos Release 10.1 For Srx Series Services Gateways And J Series Services Routers

    Errata and Changes in Documentation for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers VPNs On SRX5600 devices, the IKE authentication method displayed an unknown message on the dial-up VPN. [PR/393939: This issue has been resolved.] New Features in JUNOS Release 10.1 for SRX Series Services Gateways and J Related Topics Series Services Routers on page 98...

  • Page 164: Cli Reference

    JUNOS 10.1 Software Release Notes [edit security screen ids-option untrust-screen] CLI Reference The “Services Configuration Statement Hierarchy” section in the JUNOS® Software CLI Reference refers to the JUNOS Services Interfaces Configuration Guide, which has the following error in the sections “Data Size” and “Configuring the Probe”: The minimum data size required by the UDP timestamp probe is identified as 44 bytes.

  • Page 165: Hardware Documentation

    Errata and Changes in Documentation for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers services feature instead. For more information, see “Configuring Selective Stateless Packet-Based Services” in the JUNOS Software Administration Guide. For a J Series Services Router, if the buffer size percentage is set to zero for T1 interfaces, traffic does not pass.

  • Page 166: Installing Software Packages

    JUNOS 10.1 Software Release Notes Installing Software Packages The current SRX210 documentation does not include the following information: On SRX210 devices, the hierarchy is hosted in a separate partition (instead /var of the root partition). If JUNOS Software installation fails as a result of insufficient space: Use the command to delete temporary files.

  • Page 167: Integrated Convergence Services

    Errata and Changes in Documentation for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers To install the software image on the specified boot media: Go to the Loader prompt. For more information on accessing the Loader prompt, see “Accessing the Loader Prompt”...

  • Page 168: Intrusion Detection And Prevention (Idp)

    JUNOS 10.1 Software Release Notes Intrusion Detection and Prevention (IDP) The JUNOS Software Security Configuration Guide does not state that custom attacks and custom attack groups in IDP policies can now be configured and installed even when a valid license and signature database are not installed on the device.
  • Page 169 Errata and Changes in Documentation for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers user@host# set security idp security-package automatic download-timeout Range: 1 – 60 seconds Default: 1 second The JUNOS Software CLI Reference incorrectly states the show security idp status clear security idp status logs, whereas the logs should be as follows:...

  • Page 170: J-Web

    JUNOS 10.1 Software Release Notes J-Web The following information pertains to SRX Series and J Series devices: J-Web security package update Help page The J-Web Security Package Update Help page does not contain information about download status. J-Web pages for stateless firewall filters There is no documentation describing the J-Web pages for stateless firewall filters.

  • Page 171: Transceiver Compatibility For Srx Series And J Series Devices

    SRX Series and J Series interface modules. Different transceiver types (long-range, short-range, copper, and so on) can be used together on multiport SFP interface modules as long as they are provided by Juniper Networks. We cannot guarantee that the interface module will operate correctly if third-party transceivers are used.

  • Page 172: J Series Compactflash And Memory Requirements

    JUNOS 10.1 Software Release Notes Table 7: Supported Storage Devices on the J Series Services Routers Manufacturer Storage Capacity Third-Party Part Number SanDisk Cruzer Mini 2.0 256 MB SDCZ2-256-A10 SanDisk 512 MB SDCZ3-512-A10 SanDisk 1024 MB SDCZ7-1024-A10 Kingston 512 MB DTI/512KR Kingston 1024 MB...

  • Page 173: Dual-Root Partitioning Scheme Documentation For Srx Series Services Gateways

    Dual-Root Partitioning Scheme Documentation for SRX Series Services Gateways Upgrade and Downgrade Instructions for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers on page 183 Errata and Changes in Documentation for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers on page 163 Dual-Root Partitioning Scheme Documentation for SRX Series Services Gateways Dual-Root Partitioning Scheme...
  • Page 174 JUNOS 10.1 Software Release Notes SRX650 devices boot from the following storage media (in order of priority): Internal CompactFlash card (default; always present) External CompactFlash card (alternate) USB storage device (alternate) With the dual-root partitioning scheme, the SRX Series device first tries to boot the JUNOS Software from the primary root partition and then from the backup root partition on the default storage media.
  • Page 175 Dual-Root Partitioning Scheme Documentation for SRX Series Services Gateways The following upgrade methods format the internal media before installation: Installation from the boot loader using a TFTP server Installation from the boot loader using a USB storage device Installation from the CLI using the special partition option (available in JUNOS Release 10.1)
  • Page 176 JUNOS 10.1 Software Release Notes Each of the aforementioned methods of installing JUNOS 10.1 with dual-root partitioning is described in detail in the following sections: Installing from the Boot Loader Using a TFTP Server on page 176 Installing from the Boot Loader Using a USB Storage Device on page 176 Installing from the CLI Using the partition Option on page 177 Upgrading the Boot Loader on page 177 Installing from the Boot Loader Using a TFTP Server...
  • Page 177 Dual-Root Partitioning Scheme Documentation for SRX Series Services Gateways Format a USB storage device in MS-DOS format. Copy the JUNOS Software image onto the USB storage device. Plug the USB storage device into the SRX Series device. Stop the device at the loader prompt and issue the following command: loader>...
  • Page 178 JUNOS 10.1 Software Release Notes Installing JUNOS Release 9.6 or Earlier Release on Systems with Dual-Root Partitioning JUNOS Release 9.6 and earlier is not compatible with the dual-root partitioning scheme. These releases can only be installed if the media is reformatted with single-root partitioning.
  • Page 179 Dual-Root Partitioning Scheme Documentation for SRX Series Services Gateways Reinstalling the Single-Root Partition Release Using USB To reinstall JUNOS Software from the boot loader using a USB storage device: Format a USB storage device in MS-DOS format. Copy the JUNOS Software image onto the USB storage device. Plug the USB storage device into the SRX Series device.
  • Page 180 JUNOS 10.1 Software Release Notes Because the system is left with only one functional root partition, you should immediately restore the primary JUNOS Software image. This can be done by installing a new image using the CLI or J-Web. The newly installed image will become the primary image, and the device will boot from it on the next reboot.

  • Page 181: Maximizing Alg Sessions

    Maximizing ALG Sessions NOTE: Any removable media that has been formatted with dual-root partitioning will not be recognized correctly by the show system snapshot CLI command on systems that have single-root partitioning. Intermixing dual-root and single-root formatted media on the same system is strongly discouraged. partition Option with the request system software add Command A new option is available with the...

  • Page 182: Using Dual Chassis Cluster Control Links: Upgrade Instructions For The Second Routing Engine

    JUNOS 10.1 Software Release Notes You can configure maximum ALG sessions as follows: security { forwarding-process { application-services { maximize-alg-sessions; You must reboot the device (and its peer in the chassis cluster) for the configuration to take effect. Using Dual Chassis Cluster Control Links: Upgrade Instructions for the Second Routing Engine A second Routing Engine is required for each device in a cluster if you are using the dual control links feature (SRX5000 line only).

  • Page 183: Upgrade And Downgrade Instructions For Junos Release 10.1 For Srx Series Services Gateways And J Series Services Routers

    Upgrade and Downgrade Instructions for JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers Refers to the installation media downloaded into the /var/tmp installMedia directory. For example, install-media-srx5000-10.1R1-domestic.tgz The following code example can be used to write the image that you copied to the master Routing Engine (RE0) in step 1 onto the USB storage device: dd if=install-media-srx5000-10.1R1-domestic.tgz of=/dev/da0 bs=64k Log out as root or superuser:...

  • Page 184: Junos Software Release Notes For Ex Series Switches

    JUNOS 10.1 Software Release Notes For additional upgrade and download information, see the JUNOS Software Administration Guide and the JUNOS Software Migration Guide. JUNOS Software Release Notes for EX Series Switches New Features in JUNOS Release 10.1 for EX Series Switches on page 184 Changes in Default Behavior and Syntax in JUNOS Release 10.1 for EX Series Switches on page 187 Limitations in JUNOS Release 10.1 for EX Series Switches on page 188...

  • Page 185: Access Control And Port Security

    New Features in JUNOS Release 10.1 for EX Series Switches pluggable (SFP) transceivers for use with fiber connections and copper connections. For information about software features supported on the EX2200 switch, see EX Series Switch Software Features Overview The following optical interfaces are supported on the EX2200 switch: EX-SFP-1GE-T (1000BASE-T, 100 m) EX-SFP-1GE-SX (1000BASE-SX, 220 m, 275 m, 500 m, or 550 m) EX-SFP-1GE-LX (1000BASE-LX, 10 km)

  • Page 186: Class Of Service (Cos)

    JUNOS 10.1 Software Release Notes Class of Service (CoS) Port shaping and queue shaping Port shaping and queue shaping (the shaping-rate configuration statement) is now available on EX8200 switches. Infrastructure IPv6 support on EX8200 switches EX8200 switches now support configuration of IPv6 addresses.

  • Page 187: Mpls

    Changes in Default Behavior and Syntax in JUNOS Release 10.1 for EX Series Switches MPLS MPLS enhancements On EX3200 and EX4200 switches, MPLS supports class of service (CoS), IP over MPLS, and fast reroute to reroute the label-switched path in cases of link failure. Packet Filters IPv6 support for firewall filters on EX3200 and EX4200 switches On EX3200 and EX4200 switches, you can apply match conditions to IPv6 traffic on Layer...

  • Page 188: Layer 2 And Layer 3 Protocols

    JUNOS 10.1 Software Release Notes Layer 2 and Layer 3 Protocols EX Series switches now support the show multicast rpf instance instance-name command. option is not available in the command because it is not show pfe route supported on EX Series switches. Infrastructure On EX Series switches, the statement in the...

  • Page 189: Access Control And Security

    Limitations in JUNOS Release 10.1 for EX Series Switches Access Control and Security When you have configured more than 1024 supplicants on a single interface, 802.1X authentication might not work as expected and the 802.1X process dot1xd ) might fail. Class of Service On EX8200 switches, classification of packets using ingress firewall filter rules with forwarding-class and loss-priority configurations does not rewrite the DSCP...

  • Page 190: Interfaces

    JUNOS 10.1 Software Release Notes You can issue show snmp mib walk dot3StatsTable show snmp mib walk dot3PauseTable , and show snmp mib walk dot3ControlTable commands to display the output at the table level. When you issue the command, the switch halts instead request system power-off of turning off power.

  • Page 191: Outstanding Issues In Junos Release 10.1 For Ex Series Switches

    Outstanding Issues in JUNOS Release 10.1 for EX Series Switches EX Series switches do not support IPv6 interface statistics. Therefore, all values in the output of the command always display show snmp mib walk ipv6IfStatsTable a count of 0. show interface detail | extensive command might display double counting of packets or bytes for the transit statistics and traffic statistics counters.

  • Page 192: Class Of Service

    JUNOS 10.1 Software Release Notes On EX Series switches, in a scaled environment with more than 4000 VLANs, MVRP advertisements might not be sent intermittently when the VLAN membership is modified. [PR/475701] Class of Service On EX2200 switches, CoS port-shaping can yield different shaping results on uplink ports than on normal network ports when the same shaping rate is used.

  • Page 193: Interfaces

    Outstanding Issues in JUNOS Release 10.1 for EX Series Switches On EX2200 switches, the MIB OID indicates that IPv6 is supported ipv6Forwarding even though IPv6 is not supported. The value of the ipv6Forwarding.0 MIB object is 1. [PR/473128] If you attempt to set the time zone to on a switch with dual Routing Europe/Berlin Engines, the...

  • Page 194: Resolved Issues In Junos Release 10.1 For Ex Series Switches

    JUNOS 10.1 Software Release Notes In the J-Web interface, the dashboard does not display the uplink ports when transceivers are not plugged into the ports. [PR/477549] An IPv4 static route configured using the CLI might not be displayed when you select in the J-Web interface.

  • Page 195: Class Of Service

    Resolved Issues in JUNOS Release 10.1 for EX Series Switches workaround, restart the forwarding ( ) process. [PR/473454: This issue has pfem been resolved.] When MVRP and VSTP are enabled together on EX Series switches, convergence does not occur between MVRP and VSTP. [PR/477019: This issue has been resolved.] On EX3200 and EX4200 switches, when MVRP dynamic VLAN creation is disabled, deregistration of VLANs on trunk interfaces does not occur even after...

  • Page 196: Hardware

    JUNOS 10.1 Software Release Notes Hardware On 48-port SFP line cards used in EX8200 switches, do not install a transceiver in the first or last port on the bottom row (ports 1 and 47). Transceivers installed in these ports are difficult to remove. As a workaround, you can remove the transceiver by using a small flathead screwdriver or other tool to lift the lock on the transceiver.

  • Page 197: J-Web Interface

    Resolved Issues in JUNOS Release 10.1 for EX Series Switches J-Web Interface In the J-Web interface, the Edit MSTI window in the Spanning Tree Configuration page might not display details of an uncommitted interface configuration. [PR/433506: This issue has been resolved.] In the J-Web interface, the menu on the left side of the J-Web pages and contents of the J-Web pages might disappear when you double-click the Troubleshoot tab.

  • Page 198: Errata In Documentation For Junos Release 10.1 For Ex Series Switches

    JUNOS 10.1 Software Release Notes Errata in Documentation for JUNOS Release 10.1 for EX Series Switches There are no outstanding documentation issues in this release. New Features in JUNOS Release 10.1 for EX Series Switches on page 184 Related Topics Changes in Default Behavior and Syntax in JUNOS Release 10.1 for EX Series Switches on page 187 Limitations in JUNOS Release 10.1 for EX Series Switches on page 188...

  • Page 199: Upgrading From Junos Release 9.3R1 To Release 10.1 For Ex Series Switches

    Upgrade and Downgrade Issues for JUNOS Release 10.1 for EX Series Switches changes you have made using JUNOS Release 9.3 or earlier are not retained. The switch restores the last topology change you have made using JUNOS Release 9.4. Upgrading from JUNOS Release 9.3R1 to Release 10.1 for EX Series Switches If you are upgrading from JUNOS Release 9.3R1 and have voice over IP (VoIP) enabled on a private VLAN (PVLAN), you must remove this configuration before upgrading,...

  • Page 200: Downgrading From Junos Release 10.1 To Release 9.2 For Ex4200

    JUNOS 10.1 Software Release Notes If the MSTP configuration contains a VLAN (under protocols mstp msti msti-id that does not exist on the switch and you try to commit the configuration, the commit will fail. Remove the VLAN from the MSTP configuration before you perform an upgrade.
  • Page 201 Upgrade and Downgrade Issues for JUNOS Release 10.1 for EX Series Switches Resolved Issues in JUNOS Release 10.1 for EX Series Switches on page 194 Errata in Documentation for JUNOS Release 10.1 for EX Series Switches on page 198 Upgrade and Downgrade Issues for JUNOS Release 10.1 for EX Series Switches...

  • Page 202: Junos Documentation And Release Notes

    If the information in the latest release notes differs from the information in the documentation, follow the JUNOS Release Notes. To obtain the most current version of all Juniper Networks® technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/...
  • Page 203 CLI before contacting support: user@host> request support information | save filename To provide a core file to Juniper Networks for analysis, compress the file with the gzip utility, rename the file to include your company name, and copy it to .

  • Page 204: Revision History

    Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

This manual is also suitable for:

Junos 10.1

Table of Contents