® Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series 5 May 2015 Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Junos OS Release Notes for EX Series Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 New and Changed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Hardware . . . . . . . . . . . . . . . . . .
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Resolved Issues: Release 13.3R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Migration, Upgrade, and Downgrade Instructions . . . . . . . . . . . . . . . . . . . . . . 19 Upgrade and Downgrade Support Policy for Junos OS Releases . . . . . . . 19 Product Compatibility . . .
Software Installation and Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Subscriber Management and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Authentication and Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Class of Service (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series System Log Messages Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 System Services Administration Guide for Routing Devices . . . . . . . . . . 155 VPLS Feature Guide for Routing Devices . . . . . . . . . . . . . . . . . . . . . . . . . 155 VPWS Feature Guide for Routing Devices . . . . . . . . . . . . . . . . . . . . . . . . 155 Migration, Upgrade, and Downgrade Instructions .
Migration, Upgrade, and Downgrade Instructions . . . . . . . . . . . . . . . . . . . . . 185 Upgrading Using Unified ISSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Upgrading a Router with Redundant Routing Engines . . . . . . . . . . . . . . 186 Basic Procedure for Upgrading to Release 13.3 . . . . . . . . . . . . . . . . . . . . 186 Product Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Hardware Compatibility . . . . . . .
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Introduction ® Junos OS runs on the following Juniper Networks hardware: ACX Series, EX Series, J Series, M Series, MX Series, PTX Series, QFabric, QFX Series, SRX Series, and T Series. These release notes accompany Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series.
New and Changed Features Hardware • Extended cable manager for EX9214 switches—An extended cable manager is now available for EX9214 switches. The extended cable manager enables you to route cables away from the front of the line cards and Switch Fabric modules and provides easier access to the switch than the standard cable manager. To obtain the extended cable manager, order the MX960 Enhanced Cable Manager, ECM-MX960.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series OpenFlow • Support for OpenFlow v1.0—Starting with Junos OS Release 13.3, EX9200 switches support OpenFlow v1.0. You use the OpenFlow remote controller to control traffic in an existing network by adding, deleting, and modifying flows on switches.
Changes in Behavior and Syntax Dynamic Host Configuration Protocol • DHCP clients can send packets without Option 255 (EX9200)—On EX9200 switches, starting with Junos OS Release 13.3R5, you can override the DHCP relay agent default configuration and enable clients to send DHCP packets without Option 255. The default behavior in Junos OS is to drop packets that do not include Option 255.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series The new field provides a consistent means of identifying the Junos OS version, instead of extracting that information from the list of installed subpackages. In Junos OS Release 13.2 and earlier, the show version command does not have the Junos field in the output that displays the Junos OS version running on the device as shown in the following samples.
Known Behavior • Resolved Issues on page 13 • Documentation Updates on page 19 • Migration, Upgrade, and Downgrade Instructions on page 19 • Product Compatibility on page 20 Known Behavior This section lists known behaviors, system maximums, and limitations in hardware and software in Junos OS Release 13.3R6 for the EX Series. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Known Issues This section lists the known issues in hardware and software in Junos OS Release 13.3R6 for the EX Series. For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
Resolved Issues LACP peer devices that receive the packets to reset the LACP connections. This might cause continuous flaps for all aggregated or multichassis aggregated Ethernet interfaces. PR1034917 Network Management and Monitoring • On EX9200 switches, even if you configure an egress sampling rate for sFlow monitoring technology, the switch uses the ingress sampling rate instead.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Resolved Issues: Release 13.3R6 Firewall Filters • On EX3300 switches, if you use a wildcard mask in firewall filters, the error message Unaligned memory access by pid 87736 [dfwc] at 1000f5 PC[4adec] might be displayed at commit.
Resolved Issues Interfaces and Chassis • On EX9200 switches, in an MC-LAG scenario , a MAC address might incorrectly point to an inter-chassis control link (ICL) after a MAC move from a single-home LAG to the MC-LAG. PR1034347 Resolved Issues: Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Routing Protocols • On an EX9200 switch with an IGMP configuration in which two receivers are joined to the same (S,G) and IGMP immediate-leave is configured, when one of the receivers sends a leave message for the (S,G), the other receiver might not receive traffic for 1-2 minutes. PR979936 Resolved Issues: Release 13.3R3 Authentication and Access Control • On an EX Series switch that has both 802.
Resolved Issues OpenFlow • OpenFlow v1.0 running on an EX9200 switch does not respond reliably to interface up or down events within a specified time interval. Per a fix implemented in Junos OS Release 13.3R3.6, OpenFlow v1.0 running on an EX9200 switch responds reliably to interface up or down events if the echo interval timeout is set to 11 seconds or more.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • On an EX9200 switch that works as a DHCP relay agent, if the switch receives broadcast DHCP ACK packets sent by another DHCP relay switch, those packets might be dropped until the DHCP max-hop limit is reached.
Documentation Updates • Known Behavior on page 11 • Known Issues on page 12 • Documentation Updates on page 19 • Migration, Upgrade, and Downgrade Instructions on page 19 • Product Compatibility on page 20 Documentation Updates There are no errata or changes in Junos OS Release 13.3R6 for the EX Series switches documentation.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release. For more information about EEOL releases and to review a list of EEOL releases, see http://www.juniper.net/support/eol/junos.html .
Junos OS Release Notes for M Series Multiservice Edge Routers, MX Series 3D Universal Edge Routers, and T Series Core Routers Junos OS Release Notes for M Series Multiservice Edge Routers, MX Series 3D Universal Edge Routers, and T Series Core Routers These release notes accompany Junos OS Release 13.3R6 for the M Series, MX Series, and T Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Subscriber Management and Services (MX Series) on page 47 • VPNs on page 53 Hardware • MIC support (MX104)—Junos OS Release 13.
New and Changed Features • PPP for TCC • PPP over Frame Relay [See MPC3E on MX Series Routers Overview.] • CFP-GEN2-CGE-ER4 (MX Series, T1600, and T4000)—The CFP-GEN2-CGE-ER4 transceiver (part number: 740-049763) provides a duplex LC connector and supports the 100GBASE-ER4 optical interface specification and monitoring. Starting in Junos OS Release 13.3, the GEN2 optics have been redesigned with newer versions of internal components for reduced power consumption.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • 100-Gigabit Ethernet PIC with CFP (model numbers: PD-1CE-CFP-FPC4 and PD-1CGE-CFP)—Supported in Junos OS Releases 12.3R5, 13.2R3, 13.3R1, and later [See 100-Gigabit Ethernet 100GBASE-R Optical Interface Specifications.] • Software feature support on the MPC5E— Starting in Junos OS Release 13.
New and Changed Features • Up to 560 Gbps of full-duplex traffic for the two MIC slots • WAN-PHY mode on 10-Gigabit Ethernet interfaces on a per port basis • Two separate slots for MICs (MIC6-10G and MIC6-100G-CXP) • Two Packet Forwarding Engines for each MIC slot • Intelligent oversubscription services [See Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 MPC5E.] • Feature support on MPC6E—MPC6E supports the following software features in Junos OS Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series routers, MPC5E is housed in an adapter card. MPC5E is a fixed-configuration MPC with four built-in PICs and does not contain separate slots for Modular Interface Cards (MICs). MPC5E supports two Packet Forwarding Engines, PFEO and PFE1. PFE0 hosts PIC0 and PIC2 while PFE1 hosts PIC1 and PIC3. A maximum of two PICs can be kept powered on (PIC0 or PIC2 and PIC1 or PIC3).
New and Changed Features • Pre-forward error correction (pre-FEC)-based bit error rate (BER). Fast reroute (FRR) uses the pre-FEC BER as an indication of the condition of an OTN link To configure the OTN options for this MIC, use the set otn-options statement at the [edit interfaces interfaceType-fpc/pic/port] hierarchy level. • OTN support for 10-Gigabit Ethernet and 100-Gigabit Ethernet interfaces on MPC5E and MPC6E (MX240, MX480, MX960, MX2010, and MX2020 routers)—Junos OS Release 13.
Release Notes: Junos OS Release 13.
New and Changed Features MX Series: • 10-Gigabit Ethernet MIC with SFP+ (model number: MIC3-3D-10XGE-SFPP)—Supported in Junos OS Release 12.3R5, 13.2R3, 13.3, and later • 16-port 10-Gigabit Ethernet (model number: MPC-3D-16XGE-SFPP)—Supported in Junos OS Release 12.3R5, 13.2R3, 13.3, and later • 32-port 10-Gigabit Ethernet MPC4E (model number: MPC4E-3D-32XGE-SFPP)—Supported in Junos OS Release 12.3R5, 13.2R3, 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Padding of Ethernet Frames with VLAN. • Sending Internet Control Message Protocol (ICMP) redirect messages. • Termination or tunneling of all subscriber-based services. • To configure the hyper mode feature, use the hyper-mode statement at the [edit forwarding-options] hierarchy level. To view the changed configuration, use the show forwarding-options hyper-mode command.
New and Changed Features • [edit protocols l2circuit neighbor ip-address] if the switching is done over a Layer 2 circuit. • [edit protocols connections remote-interface-switch remote-if-sw] if the switching is done over a remote interface switch. • [edit protocols connections interface-switch local-if-switch] if the switching is done using a local switch. • Support for IPv6 traffic over IPsec tunnels on MS-MICs and MS-MPCs (MX Series)—Starting with Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series (CoS) hierarchical schedulers can be configured on MPC5E interfaces. This feature is supported on egress only.
New and Changed Features High Availability (HA) and Resiliency • MX Series Virtual Chassis support for multichassis link aggregation (MX Series routers with MPCs)—Starting in Junos OS Release 13.3, an MX Series Virtual Chassis supports configuration of multichassis link aggregation (MC-LAG). MC-LAG enables a device to form a logical link aggregation group interface with two or more other devices.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Services to be synchronized statefully include: • Stateful firewall • NAT (NAPT44 and APP only) Both IPv4 and IPv6 sessions are synchronized. Synchronization occurs for long-lived flows as defined by a configurable synchronization threshold. [See Inter-Chassis High Availability for MS-MIC and MS-MPC.
New and Changed Features slave line card crashes or all of the streams on that line card lose their timing packets, another slave line card takes over if it has been primed to do so. • Increased Layer 3 forwarding capabilities for MPCs and Multiservices DPCs through FIB localization (MX Series)—Starting in Junos OS Release 13.3, forwarding information base (FIB) localization characterizes the Packet Forwarding Engines in a router into two types: FIB-Remote and FIB-Local.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Support for ATM virtual connection multiplexing and LLC encapsulation (MX Series)—Starting in Junos OS Release 13.3, ATM virtual connection (VC) multiplexing and logical link control (LLC) encapsulation are supported on the Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP.
New and Changed Features • Support for GPS external clock interface on the SCBE (MX240, MX480, and MX960)—Starting with Junos OS Release 13.3, you can configure the Enhanced SCB—SCBE—external clock interface to a GPS timing source, which enables you to select a GPS external source as the chassis clock source.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • License support to activate ports (MX104)—Starting with Junos OS Release 13.3, license support has been extended for activating the ports on MX104 3D Universal Edge Routers. MX104 routers have four built-in ports. By default, in the absence of any valid licenses, all four built-in ports are deactivated. The upgrade license model with the feature IDs is described in Table 1 on page 38.
New and Changed Features • Pseudowire logical interface device MAC address configuration (MX Series)—Starting in Junos OS Release 13.3, you can configure a MAC address for a pseudowire logical interface device that is used for subscriber interfaces over point-to-point MPLS pseudowires. This feature enables you to specify the MAC address of your choice in situations in which network constraints require the use of an explicit MAC address. [See Configuring a Pseudowire Subscriber Logical Interface Device.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series [edit interfaces interface-name optics-options] hierarchy level. The following interface module supports the SPFF-10G-CT50-ZR transceiver: MX Series: • 16-port 10-Gigabit Ethernet MPC (model number: MPC-3D-16XGE-SFPP)—Supported in Junos OS Release 12.3R6, 13.2R3, 13.3R2, 14.1, and later.
New and Changed Features IPv6 • New forwarding-class-accounting statement (MX Series)—Starting in Junos OS Release 13.3R3, new forwarding class accounting statistics can be enabled at the [edit interfaces interface-name] and [edit interfaces interface-name unit interface-unit-number] hierarchy levels. These statistics replace the need to use firewall filters for gathering accounting statistics. Statistics can be gathered in ingress, egress, or both directions.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series request that other BGP VPLS PE routers insert a control word between the label stack and the MPLS payload. Multicast • IGMP and PIM snooping support (MPC3E and MPC4E on MX240, MX480, and MX960)—Starting with Junos OS Release 13.3, IGMP snooping and PIM snooping are supported on the MX240, MX480, and MX960 and with Modular Port Concentrators (MPC) MPC3E and MPC4E.
New and Changed Features OpenFlow • Support for OpenFlow v1.0 (MX80, MX240, MX480, and MX960)—Starting with Junos OS Release 13.3, the MX80, MX240, MX480, and MX960 routers support OpenFlow v1.0. OpenFlow enables you to control traffic in an existing network using a remote controller by adding, deleting, and modifying flows on a switch.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Routing Policy and Firewall Filters • Using a firewall filter to prevent or allow datagram fragmentation (MX Series)—Starting in Junos OS Release 13.3, you can define a firewall filter term to prevent or allow datagram fragmentation by setting or clearing the Don’t Fragment flag in the IPv4 header of packets that are matched by the filter.
New and Changed Features interface-name] hierarchy level. There is no new configuration option available if the firewall filter term action is set to next-ip, meaning that if the next-ip is down, traffic is still dropped. The action configured at this level only becomes active if the next-interface is down and the ARP on the interface is cleared. If not configured, the default action is to drop the packet. Routing Protocols • Support for BMP version 3—Starting in Junos OS Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Services Applications • Enabling Layer 2 Protocol Tunneling (L2PT) support for VLAN Spanning Tree Protocol (VSTP) and per-VSTP (MX Series routers with MPC/MICs) —Starting in Junos OS Release 13.3, this feature enables L2PT support for VSTP/PVSTP. [See layer2-control.] You can also enable rewriting of the MAC address for an interface using the enable-all-ifl option. [See mac-rewrite.
New and Changed Features | address ipv6-address) statement at the [edit services rpm probe owner test test-name] hierarchy level. You can also define the RPM client or the source that sents RPM probes to contain an IPv6 address. To specify the IPv6 protocol-related settings and the source IPv6 address of the client from which the RPM probes are sent, include the inet6-options source-address ipv6-address statement at the [edit services rpm probe owner test test-name] hierarchy level.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • RADIUS logical line identifier (MX Series)—Starting in Junos OS Release 13.3, service providers can use a virtual port feature, known as the logical line ID (LLID), to maintain a reliable and up-to-date customer database for those subscribers who move from one physical line to another. The LLID, which is based on the subscriber's user name and circuit ID, is mapped to the subscriber's physical line.
New and Changed Features underlying interfaces. In earlier Junos OS releases, PPPoE subscriber session lockout identified and filtered subscriber sessions only by their unique MAC source address. ACI-based or MAC-based PPPoE subscriber session lockout prevents a failed or short-lived PPPoE subscriber session from reconnecting to the router for a default or configurable time period.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series is provided to the client using DHCPv6-PD, the RADIUS interim accounting message includes the delegated prefix (IA_PD, such as /56). The address-change-immediate-update statement is now effective for any address allocation change after an Acct-Start message is issued (for IPv6NCP and DHCPv6).
New and Changed Features [See ANCP Topology Discovery and Traffic Reporting Overview.] • Support for ANCP generic response messages and result codes (MX Series)—Starting in Junos OS Release 13.3, the ANCP agent supports receipt of generic response messages. Upon receipt, the router generates a system log, increments the generic message counters, and increments the result code counters.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series You can filter on the user, the domain, or both. You can use a wildcard (*) at the beginning or end of each term, as in the following examples: tom@example.com, tom*, *tom, *ample.com, tom@ex*, tom*@*example.com. You cannot filter results using a wildcard in the middle of the user or domain, as in the following examples: tom*25@example.com, tom125@ex*.com.
New and Changed Features VPNs • Enhanced multicast VPNs traceoptions statement (M Series, MX Series, and T Series)—Starting in Junos OS Release 13.3, the multicast VPNs traceoptions statement has been enhanced starting in Junos OS Release 13.3. This statement can now be configured at the [edit protocols mpvn] hierarchy level. In addition, the following traceoption flags have been added: cmcast-join, inter-as-ad, intra-as-ad, leaf-ad, mdt-safi-ad, source-active, spmsi-ad, tunnel, and umh.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Resolved Issues on page 80 • Documentation Updates on page 135 • Migration, Upgrade, and Downgrade Instructions on page 156 • Product Compatibility on page 165 Changes in Behavior and Syntax This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands from Junos OS Release 13.3R6 for the M Series, MX Series, and T Series.
Changes in Behavior and Syntax High Availability (HA) and Resiliency • New redundancy failover CLI statement (M, MX, T, TX Matrix Plus)—Starting in Junos OS Release13.3R6, the chassis redundancy failover not-on-disk-underperform statement prevents gstatd from causing failovers in the case of slow disks on the Routing Engine. See not-on-disk-underperform and Preventing Graceful Restart in the Case of Slow Disks.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • filter-action protocol group—The following packet types are available for unclassified firewall filter action packets, which are sent to the host because of reject terms in firewall filters: • aggregate—Aggregate of all unclassified filter action packets. • filter-v4—Unclassified IPv4 filter action packets. • filter-v6—Unclassified IPv6 filter action packets.
Changes in Behavior and Syntax only for interfaces with inet address families and on MX Series routers with MPCs. When you disable ARP policers per interface, the packets are continued to be policed by the distributed DoS (DDoS) ARP policer. The maximum rate of is 10000 pps per FPC. [See Applying Policers.] IPv6 • Support for interim logging with NAT64 Starting with Junos OS Release 11.4R11, interim-logging is supported with NAT64 on microkernel (MS-DPC) platforms.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series LSPs. To enable the polling and display of transit LSP statistics, include the transit-statistics-polling statement at the [edit protocols mpls statistics] hierarchy level. You cannot enable transit LSP statistics collection if MPLS statistics collection is disabled with the no-transit-statistics statement at the [edit protocols mpls statistics] hierarchy level.
Changes in Behavior and Syntax Network Management and Monitoring • Support of new system log by SNMP for notifying target addition (M Series, MX Series, and T Series)—Beginning with Junos OS Release 13.3, when a new trap target configuration is added to the agent, SNMP raises a new system log SNMPD_TRAP_TARGET_ADD_NOTICE. The user can configure an event policy for this system log event to raise a notification of the new trap target addition.
Release Notes: Junos OS Release 13.
Changes in Behavior and Syntax by the destination-prefix statement in the then statement. Starting in Junos OS Release 13.3, this restriction is enforced. [edit services nat] rule rule-name { term term-name { from { destination-address-range low minimum-value high maximum-value ; destination-prefix-list list-name ; } then { destination-prefix destination-prefix; } } } • Change in running RPM traceoptions—Starting in Junos OS Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series NOTE: The header-integrity-check option that is supported on MS-MICs and MS-MPCs to verify the packet header for anomalies in IP, TCP, UDP, and ICMP information and flag such anomalies and errors has a functionality that is opposite to the functionality caused by passive mode tunneling.
Changes in Behavior and Syntax MSVCS_LOG_SESSION_CLOSE system log messages are modified to toggle the order of the destination IPv4 address and destination port address displayed in the log messages be consistent and uniform with the formats of the session open and close logs of MS-DPCs.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Configuration support to prevent the LACP MC-LAG system ID from reverting to the default LACP system ID on ICCP failure—Beginning in Junos OS Release 13.
Changes in Behavior and Syntax You can determine whether direct-connect is configured for particular interfaces by issuing the show interfaces or show pppoe underlying-interfaces command. • ANCP agent behavior for invalid generic response messages (MX Series)—Starting in Junos OS Release 13.3, when the ANCP agent receives an incorrect or unexpected generic response message from an ANCP neighbor, it immediately drops the packet, generates a system log notice message, and takes no further action.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series You can configure the router to collect time statistics, or both volume and time statistics, for the service accounting sessions being managed by AAA. To configure the collection of statistical details that are time-based only, include the statistics time statement at the [edit access profile profile-name service accounting] hierarchy level.
Changes in Behavior and Syntax you no longer have to configure a tunnel profile on the LAC. In earlier releases, tunnel switching failed when you did not also configure the LAC, even when the RADIUS attributes were present.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series containing adjacent repetition operators or adjacent bounded repetitions. Junos OS uses regular expressions in several places within the CLI. Exploitation of this vulnerability can cause the Routing Engine to crash, leading to a partial denial of service. Repeated exploitation can result in an extended partial outage of services provided by the routing protocol process (rpd).
Known Behavior General Routing • In MX2020 routers and T Series routers, memory usage of the device increases when auto-64-bit statement is issued. High Availability (HA) and Resiliency • The MPC5E, MPC5EQ, and MP6E cards do not support unified ISSU on an MX Series Virtual Chassis.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series statistics you want to clear. When you reset firewall statistics to zero, you also zero the counters reported to RADIUS.
Known Issues • Services Applications on page 78 • Software Installation and Upgrade on page 79 • User Interface and Configuration on page 79 • VPNs on page 79 Authentication and Access Control • The syslog message "UI_OPEN_TIMEOUT: Timeout connecting to peer" might appear if "show version detail" command is executed. This log is a cosmetic log and could be ignored. PR895320 Class of Service (CoS) • COSD errors are seen while Routing Engine switchover without GRES enabled.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series RPD. Those garbage interfaces will result KRT queue stack issue upon later lsi re-configuration. PR912861 • Periodic "show subscribers" CLI requests during the GRES recovery (on a scaled system) might lead to spawning of too many subinfo processes.
Known Issues • On M Series, MX Series, T Series platform with DHCP relay configured, the router might keep filling a specific partition "/var/mfs/sdb" with files named log.XXXX and this would eventually cause DHCP relay fail. PR1017642 • This issue only affects OC-48 MICs. If an SFP is inserted into an OC-48 MIC port that has been disabled the SFP will not show up in a >show chassis hardware command. The issue is fixed with a patch. Contact JTAC to find out which version is best for you.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • In Ethernet OAM connectivity-fault-management, Junos OS default encodes MAID(MD name and MA name) in character format. Currently only 43 octets are supported in Junos OS for the MD + MA name. Junos OS needs to support maximum length of 44 octets for MAID per the standards. PR997834 • When IEEE 802.
Known Issues for seq 1, return code: Egress-ok, time: 3993729.963 ms <--- Local transmit time: 2013-04-29 12:05:06 IST 873.491 ms Remote receive time: 2013-04-29 12:05:06 IST 3994603.454 <---- This is a cosmetic issue and current software limitation. PR891734 • Although NSR does not support mplsoamd and it does not run on backup Routing Engine, backup rpd is attempting to do task_connect to mplsoamd. This behavior causes periodical message popping up on backup Routing Engine.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Wrong source IP is used when responding to traceroute in L3VPN setup. This is not an indication of traffic taking wrong link. PR883701 • On all high-end MX Series devices, when a router is acting as an NTP broadcast server, broadcast addresses must be in the default routing instance.
Known Issues • The Priority code point (PCP) and Drop eligible indicator (DEI) bit in 802.1Q header are preserved while packet gets routed within the same Packet Forwarding Engine. The expected behavior is resetting the PCP and DEI bit when the packet is routed. PR1036756 • Observation domain ID in exported flow records is wrong in Hyperion and snorkel line card. PR1066319 Routing Protocols • It is necessary that the MSDP peer local-address matches the PIM RP address on routers that are RP.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series very high and the host path and interface network control queues can get congested. Refer to KB29553 for more information and mitigation. PR945215 • In rare cases, rpd may write a core file with signature "rt_notbest_sanity: Path selection failure on ..." The core is 'soft', which means there should be no impact to traffic or routing protocols.
Known Issues Software Installation and Upgrade • Filesystem corruption might lead to routing engine boot up failure. This problem is observed when directory structure on hard disk (or SSD) is inconsistent. Such a failure should not result in boot up problem normally, but due to the software bug the affected Junos OS releases mount /var filesystem incorrectly. The affected platforms are M/T/MX/TX.
Release Notes: Junos OS Release 13.
Resolved Issues General Routing • On MX Series platform with Enhanced DPCs equipped, after router rebooted, the IRB broadcast channel is not enabled, all the broadcast packets that are received in the IRB interface will get dropped. Also when ping is given the below L2Channel error increases as ping packets are sent: user@router>show interfaces ge-*/*/* extensive | match channel L3 incompletes: 0, L2 channel errors: 10, L2 mismatch timeouts: 0.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • On MX Series platforms with ADPC FPCs, M120, or M7i/M10i with Enhanced CFEB, each VPLS LSI interface flapping triggers a memory leak in jtree segment 0. There is no memory leak in FPC heap 0 memory.
Resolved Issues • On MX Series platform with one of the following protocols configuration, flapping the protocols will trigger the Composite Next-hop change operation. In rare condition, since it is not proper programmed, the FPC might crash. This is a day-1 issue. - LDP MPLS - Point-to-multipoint LSP - RSVP - Static LSPs. PR1045794 • Once default route 0.0.0.0/0 is added, deleted or changed, the PFEMAN thread running on the MPC/FPC5 needs more than 600 mseconds to program such changes.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Interfaces and Chassis • Refer to the following topology. If we set interface ge-1/0/8 disable, interface xe-2/0/0 and xe-2/1/0 become down status because "asynchronous-notification" feature. However after 3 or 4 seconds, ether OAM detects link-fault status changed to good. And then, interface xe-2/0/0 and xe-2/1/0 change link status from down to up. The conditions are the following. 1.
Resolved Issues error=301 Nov 16 12:19:21 jtac-host jpppd: Profile: PPPoE-1-QoS variable: $junos-cos-shaping-rate value: failed semantic check PR1042247 • clear interfaces interface-set statistics all fails due to memory limitation. PR1045683 • On MX Series routers (platforms) with Enhanced Switch Control Board (SCBE), when the fan tray is inserted or pulled out, the chassisd process might crash. PR1048021 • When Inherit is part of lower logical interface Unit, VRRPD parses it before Active.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • When node-protection is enabled for a specified LSP and optimize-timer for a node-protecting bypass LSP is configured on router, the bypass route might get-optimized in such a way that it traverses through the very node that the bypass is trying to protect during re-optimization. As a consequence, the node-protecting bypass LSP only provide link protection instead of node protection.
Resolved Issues • A Packet Forwarding Engine memory leak is seen when multicast receivers are connected in a bridge domain where IGMP snooping is enabled and IGMP messages exchanged between the multicast receivers and the layer 3 IRB (Integrated Routing and Bridging) interface. PR1027473 • Aggregated Ethernet interface does not send PPPoE client echo reply when ae interface bundle spans multiple FPC(s).
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series command "show route advertising-protocol bgp " might crash the routing protocol process (rpd). This is very corner issue and hardly to be experienced. PR1028390 • When BGP is doing path selection with default behavior, soft-asserts requests are introduced.
Resolved Issues Routing Policy and Firewall Filters • In the BGP environment, if operator "!" exists in the regex for as-path, the commit operation fails. PR1040719 Services Applications • Added support to bring up Tunnel-switched sessions when tunnel-group is not configured at LTS and tunnel attributes are returned from RADIUS.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series the rpd might crash due to trying to reset an internal variable which is already reset during route addition for the new local VC connection. PR1053887 Resolved Issues: Release 13.3R5 Class of Service (CoS) • Sometimes MX Series might respond with "no such instance" of the second OID when two CoS OIDs in the single SNMP packet.
Resolved Issues General Routing • "show services accounting usage" does not populate cpu utilization for XLP based cards . Please use "show services service-sets cpu-usage". PR864104 • Leak in /mfs/var/sdb/iflstatsDB.db. PR924761 • In this scenario the CPCD (captive-portal-content-delivery) is configured for HTTP-REDIRECT for Subscriber Management clients using MS-DPC.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series level to suit your deployment needs. The rate at which syslog messages can be sent to the Routing Engine is 10,000 logs per second.
Resolved Issues command is configured prior to the upgrade.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series MS-MPC PICs pointing to two eth interfaces connect to CB0 and CB1 separately might be wrongly created. Then if pull out RE0/CB0, the MS-PIC would still select the eth interface connects to CB0, which results in loss of connectivity because that path is not available anymore.
Resolved Issues • VRRP daemon (vrrpd) memory leak might be observed in "show system processes extensive" when VRRP is set with routing-instance and then change any configuration. PR1022400 • On M120, when two type 1 FPCs are sharing the same FEB and they are both carrying core facing interface, with vrf-table-label/no-tunnel-service configuration, the LSI interfaces might be removed incorrect on a working FPC when the other is set to offline.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series have the sum of te-metric of IGP with highest credibility at each hop in ERO. This has been corrected and the cspf-metric will be sum of te-metric of current credibility at each hop. PR1021593 • When RSVP label-switched-path (LSP) optimize is enabled, RSVP LSP might stay down after a graceful Routing Engine mastership switchover (GRES).
Resolved Issues • Micro BFD sessions are used to monitor the status of individual LAG member links. When micro BFD configurations are added after the LAG bundle configuration in separate commit, the micro BFD sessions for all the member links might remain in "Down" state. PR1006809 • On TX Matrix Plus routers or TX Matrix Plus routers with 3D SIBs, all the incoming interfaces on an FPC are deactivated when none of the fabric planes are functional. By default, the interfaces remain activated.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series case, the corresponding L2 nexthop to the L3 IRB nexthop is a DISCARD nexthop and will cause the FPC to crash. PR1026124 • When receiving traffic coming on MPC and going out on DPC, an Ethernet frame with known DMAC will be flooded to the whole bridge domain after flapping the link which the given MAC is learnt for more than 32 times.
Resolved Issues Routing Protocols • Prefixes that are marked with two or more route target communities (matching multiple configured targets configured in policies) will be using more CPU resources. The time it takes to process this kind of prefixes depends on the number of VRFs and the number of routes that are sharing this particularity. This can lead to prolonged CPU utilization in rpd.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • The snmp trap generated when an ipv6 BFD session goes up/down does not contain the ipv6 bfd session address. PR1018122 • Junos OS implementation of RFC3107 uses unspecified label (0x000000) when sending route with label withdrawn message. This means Junos OS sends 0x000000 instead of 0x800000 for label withdrawn, which is inconsistent with RFC3107.
Resolved Issues > 64 characters. The resulted jpool "_jpool_A_RULE_NAME_WHICH_IS_LONG_1234_A_TERM_ALSO_WITH_" will be used wrongly in both terms. PR973465 • In L2TP scenario, when the LNS is flooded by high rate L2TP messages from LAC, the CPU on Routing Engine might keep too busy to bring up new sessions. PR990081 • Softwire tunnel count management is inconsistent and incorrect, thus the output of "show service softwire statistics" might be incorrect.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Type 5. One of the checks PIM makes is to determine if it is the local RP for the S,G. During a re-configuration period where any commit is done, PIM re-evaluates whether it is a local RP. It waits until all the configuration is read and all the interfaces have come up before making this determination.
Resolved Issues Forwarding and Sampling • When a firewall filter has one or more terms which have MX Series-only match condition or actions, such filters will not be listed during SNMP query. This behavior is seen typically after Routing Engine reboot/upgrade/master-ship switch.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series chassisd) tried to connect using the TNP socket. SNMPD does not accept these connections. As a fix, in an MX-VC, we made sure that chassisd connects to all processes which run on the protocol master using internal socket while the chassisd process on the protocol backup and protocol lincecard connect connect using TNP socket.
Resolved Issues • When several PICs are set up as an aggregated Multi-services (AMS) doing load-balancing, if one PIC of the AMS bundle gets offline and then gets online, 30 to 40 seconds momentary traffic loss might be seen. PR1005665 • Ingress queuing is not supported on MPC5 (With Q-MPC) when Optical Transport Network (OTN) is enabled. Enabling ingress queuing with OTN would lead to line card crash.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Uninitialized EDMEM[0x3d9565] Read (0x6db6db6d6db6db6d) fpc0 LUCHIP(0) RMC 3 Uninitialized EDMEM[0x3d81b6] Read (0x6db6db6d6db6db6d) These message would be transient in nature. PR990023 • In the demux interfaces over aggregated Ethernet (AE) environment with targeted-distribution configuration. The index of AE interface is confused when the index is more than 100.
Resolved Issues interfaces xe-2/0/0 terse Interface Admin Link Proto Local Remote xe-2/0/0 up up xe-2/0/0.0 up up aenet --> ae102.0 xe-2/0/0.32767 up up aenet --> ae102.32767 This issue would be seen when associated aggregated Ethernet bundle is configured for vlan-tagging. To clear this condition, the affected interface should be deactivated and activated using CLI commands.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series reassigned to a template filter. This could be considered as a timing issue given it comes with a very specific sequence of events only. PR949975 • When a port being used for port mirroring goes down due to an external factor, such as a fiber cut or the remote side rebooting, the FPC CPU may rise to 100% for 4 minutes and then followed by a reboot of the FPC with a reason of "pfeman watchdog expired".
Resolved Issues • When sending traffic coming on MPC and going out on DPC, the MAC entry on a Packet Forwarding Engine will not be up-to-date and the frames targeted to a known MAC address will be flooded across the bridge domain.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • BMP is not sending a correctly formatted prefix for inet/inet6 labeled unicast BGP family routes. This occurs if the route resides in the inet[6].0 table, and not if the route resides in the inet[6].3 table. PR996374 • There are two scenarios that the rpd might crash. The first scenario is when all BGP peers flap with bgp route target proxy configured.
Resolved Issues Subscriber Access Management • MIB entries for jnxUserAAAAccessPoolRoutingInstance may not appear after deleting and re-adding an assignement pool under a routing instance. PR998967 VPNs • In the Rosen MVPN environment, some data would pass intermittently over the default MDT even after hitting threshold to switch to data MDT. PR999019 • Serving site B is not receiving all the traffic from serving site A when traffic is reduced from the exceeded cmcast limit.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series General Routing • The ingress family feature (uRPF) unicast Reverse Path Forwarding check execution order was invalidated when (FBF) Filter Based Forwarding was enabled on MX Series routers with MPCs or MICs. This solution repositions uRPF just prior to Filter Based Forwaarding (FBF), so that both actions are compatible and applicable. This applies to both IPv4 and IPv6.
Resolved Issues will be provided. forwarding-options { enhanced-hash-key { family mpls { + no-ether-pseudowire; } } } PR958685 • In subscriber management environment, upgrade Junos OS to specific version (include 12.3R6 13.2R4 13.3R2) via ISSU might make subsequence subscribers fail to connect with following error: "jdhcpd_profile_request: Add Profile dhcp request failed for client in state LOCAL_SERVER_STATE_WAIT_AUTH_REQ: error = 301".
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • In processing for fpc-resync and fab-liveness packets if error occurs while sending packet we do not free the packet. This causes packets buffers to leak and eventually the packet heap runs out of memory. PR973892 • You cannot configure an MTU value on family inet greater than 1496 if there is a trunk port configured on the interface; if you configure an MTU greater than 1496, a commit error occurs.
Resolved Issues • OpenFlow does not respond to port_down events when the echo interval timeout is set for less than 11 seconds. PR989308 • The fabric performance of MPC1, MPC2, or 16xXE MPC in 'increased-bandwidth' mode on an MX960 populated with SCBE's will be less compared to redundant mode due to XF1 ASIC scheduling bugs. PR993787 • Under normal circumstances, the Maximum Receive Unit (MRU) value is set to MTU size + 8 bytes (e.g. MTU=9102, MRU=9102+8=9110).
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series get aborted. This happens because although the MIC is removed physically but it does not get removed from the hardware database (HWDB), which makes the chassis mistakenly try to offline the already removed MIC during unified ISSU and in turn cause the upgrade failure. PR923569 • Queue stats counters for AE interface will become invalid after deactivating ifl on the AE interface.
Resolved Issues ae0 of switch C 4. enable iccp link of router A. (Please wait until iccp status up.) 5. enable ae0 of switch C 6. enable ae0 of router A. PR982713 • When upgrading to 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • When Cisco running in an old version of PVST+, it does not carry VLAN ID in the end of BPDU. So Juniper Networks equipment fails to responds to Topology Change Notification ACK packet when it interoperates with Cisco equipment. After the fix, Juniper equipment will read the VLAN ID information from Ethernet header.
Resolved Issues • snmpwalk/snmpgetnext or "show snmp mib walk" fail when polling MPLSLSPOCTETS, MPLSLSPPACKETS, MPLSLSPINFOOCTETS or MPLSLSPINFOPACKETS. PR981061 • LSP metric modification leads to Constrained Shortest Path First(CSPF) computation and resignaling. It should update RSVP routes directly. PR985099 • In the MPLS environment with "egress-protection" configuration, there is a direct LDP session between primary PE and protector.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • The error message 'unlink(): failed to delete .perm file: No such file or directory' was logged when disconnecting from a Telnet session to the router. PR876508 • When the instance have vlan-id all and adding interface unit with "vlan-tags outer X inner Y" to this instance, traffic from ALL instance VLANs is leaking over that unit tagged with outer tag X and each VLANs own inner tag A,B.C,.....
Resolved Issues GREEN. That's problem. * NOTE: Junos OS doesn't support FT double-fault scenario. (MX2020 needs minimum 3 FTs.) If FT#2 gets in trouble in above case(i.e.,FT double-fault), the user should see serious cooling-trouble on SFMs within 1 minute. PR957395 • Unable to modify dynamic configuration database after first commit. PR959450 • When we set "traffic-manager mode ingress-and-egress" on "MIC-3D-40GE-TX (3D 40x 1GE(LAN) RJ45)", we cannot use ingress queue correctly on PIC2 and PIC3.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • TXP with 13.1R4 might not trigger autoheal after 65535 CRC error event on inter-chassis optical hsl2 link. Customer will need to do manual fabric plane reset to recover the faulty SIBs after the 65535 CRC error event. PR988886 • NPC core /../src/pfe/ukern/cpu-ppc/ppc603e_panic.c:68.
Resolved Issues • The rpd process might crash when executing the command "show route advertising-protocol bgp " without a table option, or with a table that is not advertised by BGP.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • The dynamic flow control process (dfcd) might core dump when Dynamic Tasking Control Protocol (DTCP) trigger request is same for both the VLAN and DHCP subscriber. PR962810 • Message type for if_msg_ifl_channel_delete should be lower severity and not an error.
Resolved Issues Software Installation and Upgrade • Routing Engine could be brought to DB mode when rebooting after interrupted downgrade. PR966462 • By upgrade-with-config, user can specify a configuration to be applied on upgrade, but the configuration file will not be loaded post upgrading. As a result, router will bring up with old configuration. PR983291 Subscriber Access Management • In early Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Resolved Issues: Release 13.3R2 Forwarding and Sampling • When MAC addresses move, Layer 2 address learning process (l2ald) will be called and produces some other child processes. The child processes cannot be terminated. Then maximum process limitation is reached and the Routing Engine is locked up.
Resolved Issues • PIC level "account-layer2-overhead" knob with ethernet-bridge doesn't add "Adjustment Bytes". As a workaround, configure it under interface level. PR946131 • Egress multicast statistics display incorrectly after flapping of ae member links on M320 or T Series FPC (M320 non-E3 FPC and T Series non-ES FPC). PR946760 • With scaled configuration of ATM VCs (~4000 VCs) on a single MIC-3D-8OC3-2OC12-ATM ATM MIC, the MIC might crash. The crash is not seen with lower scale (i.e.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series changing gigether-options of core router facing interface multiple times continuously, the Flexible PIC Concentrator (FPC) CPU utilization might increase to 100%, and then FPC might crash.
Resolved Issues Infrastructure • On RE-S-1800 family of Routing Engines, after an intensive writing to SSD, the immediate rebooting might cause SSD to corrupt. PR937774 Interfaces and Chassis • The Packet Forwarding Engine alarms raised by PFEMAN thread using cmalarm api calls will not be transmitted to the Routing Engine. As impact, these alarms will not reflect on the Routing Engine. There is no impact on functionality, otherwise.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • Kernel crash might happen when a router running a Junos OS install with the fix to PR 937774 is rebooted. This problem will not be observed during the upgrade to this install. It occurs late enough in the shutdown procedure that it shouldn't interfere with normal operation.
Resolved Issues • In a highly scaled configuration, the reroute of transit RSVP LSPs can result in BGP flap due to lack of keepalive messages being generated by the Routing Engine. PR946030 • The RSVP bandwidth of the aggregated Ethernet (AE) bundle does not adjust properly when a member link is added to AE interface, and at the same time an IP address is removed from this AE bundle.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • On I-chip platforms, when forwarding table filter (FTF) is configured for a virtual private LAN service (VPLS) routing instance, the jtree memory corruption might occur if the routing table attached by FTF is destroyed.
Resolved Issues • In current Junos OS, a PSM shows dc output value even though it is turned off by a switch. This cosmetic bug causes miscalculation of actual usage in 'show chassis power'. PR960865 • Upon the deletion of a routing-instance and subsequent commit, error logs are generated from each Type 1 - 3(non E3) based FPC. These logs are cosmetic and can be ignored.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Services Applications • SIP call forwarding might fail when NAT is used between parties even though the SIP ALG is in use. PR839629 • Junos OS Release 11.4 introduced the IKEv2 support and a stricter check on IKE/IPsec SAs proposal parameters. PR843893 • DNS multiple queries A and AAAA might cause the Service-PIC to restart.
Documentation Updates • Changes in Behavior and Syntax on page 54 • Known Behavior on page 68 • Known Issues on page 70 • Documentation Updates on page 135 • Migration, Upgrade, and Downgrade Instructions on page 156 • Product Compatibility on page 165 Documentation Updates This section lists the errata and changes in Junos OS Release 13.3R6 documentation for the M Series, MX Series, and T Series.
Release Notes: Junos OS Release 13.
Documentation Updates [edit interfaces ae1] user@PE2# set flexible-vlan-tagging user@PE2# set encapsulation flexible-ethernet-services user@PE2# set unit 0 encapsulation vlan-bridge user@PE2# set unit 0 vlan-id-range 100-110 user@PE2# set unit 0 multi-chassis-protection 100.100.100.1 interface ge-1/0/4.0 5. Configure LACP on the aggregated Ethernet bundles.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series The mode statement indicates whether an MC-LAG is in active-standby mode or active-active mode. Chassis that are in the same group must be in the same mode. 7. Configure a domain that includes the set of logical ports. [edit bridge-domains bd0] user@PE2# set domain-type bridge user@PE2# set vlan-id all user@PE2# set service-id 20 user@PE2# set interface ae0.0 user@PE2# set interface ae1.
Documentation Updates and if the RPM server is Packet Forwarding Engine-based, the RPM client must also be Packet Forwarding Engine-based. • The show chassis fabric unreachable-destinations command is incorrectly mentioned as supported on MX240, MX480, and MX960 routers from Junos OS Release 11.4R2 and Junos OS Release 12.1. The Supported Platforms section of this topic also incorrectly state MX240, MX480, and MX960 routers as supported routers for this command.
Release Notes: Junos OS Release 13.
Documentation Updates processing for all packets that use PPM and run all PPM processing on the Routing Engine by configuring the no-delegate-processing configuration statement at the [edit routing-options ppm] hierarchy level.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series flexible-vlan-tagging; unit 1 { encapsulation vlan-vpls; family bridge { interface-mode trunk; vlan-id-list 1-1000; # Note the use of the VLAN id list statement. } } } interfaces ge-3/0/0 { encapsulation flexible-ethernet-services; flexible-vlan-tagging; family bridge { unit 1 { encapsulation vlan-vpls; interface-mode trunk; vlan-id-list 1-1000; # Note the use of the VLAN id list statement.
Documentation Updates Note the use of the vlan-id all statement in the virtual-switch instance called customer-c1-v1-to-v1000.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series For example, if you issue the set chassis member 0 fpc slot 1 power off statement, only the MPC installed in slot 1 of member ID 0 in the Virtual Chassis is powered off. • Statements included at the [edit chassis fpc slot slot-number] hierarchy level apply to the MPCs (FPCs) in the specified slot number on each member router in the Virtual Chassis.
Documentation Updates • The following information regarding the guidelines for configuration of IP addresses for NAT processing applies to the "Configuring Source and Destination Addresses Network Address Translation Overview " section of the "Network Address Translation Rules Overiew" topic: The addresses that are specified as valid in the inet.0 routing table and not supported for NAT translation are orlonger match filter types. You cannot specify any regions within such address prefixes in a NAT pool.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • • For a trunk port, the default limit on the maximum number of MAC addresses that can be learned on a trunk port is 8192.
Documentation Updates Services Interfaces Configuration Guide • In the Lines of Sample DTCP Parameter File table in the “Flow-Tap Filter Operation” topic, the description for the Seq:10 command contained in the DTCP file incorrectly states that the router looks for a newer sequence number before accepting and implementing new parameters, and that any configuration attempt with an older sequence number is rejected by the dynamic flow capture process.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • The following information is missing from the passive-mode-tunneling configuration statement and the “Example: Configuring Junos VPN Site Secure on MS MIC and MS-MPC” topic: Passive module tunneling is not supported on MS-MICs and MS-MPCs.
Documentation Updates 3. Use the show policer | match flow statement to verify that the flow-tap filter is removed from the router: The following sample shows how to disable mirroring for a specific subscriber by using the CRITERIA-ID. DELETE DTCP/0.7 Csource-ID: dtcp1 CRITERIA-ID: 2 Flags: STATIC Seq: 10 Authentication-Info: 7e84ae871b12f2da023b038774115bb8d955f17e DTCP/0.7 200 OK SEQ: 10 CRITERIA-COUNT: 1 TIMESTAMP: 2011-02-13 16:00:02.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series port-mirroring family (inet | inet6)] hierarchy level. To configure the input packet properties for port mirroring, you must include the input statement at the [edit forwarding-options port-mirroring] hierarchy level.
Documentation Updates • For an IPv6 address prefix, the length is 16 and the value displayed is 15. • For a subnet mask of an IPv6 address prefix, the length is 32 and the value displayed is 31. • For a range of IPv6 address prefixes, the length is 32 and the value displayed is 31. The value of the id-data-presentation field denotes the IPv4 address or IPv6 prefix details.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series the inline-jflow statement at the [edit forwarding-options sampling instance instance-name family inet output] hierarchy level).
Documentation Updates • RFC 5102, Information Model for IP Flow Information Export Subscriber Management Access Network Guide • The LAC Tunnel Selection Overview, Configuring Weighted Load Balancing for LAC Tunnel Sessions and weighted-load-balancing (L2TP LAC) topics in the Junos OS Broadband Subscriber Management and Services Library incorrectly describe how weighted load balancing works on an L2TP LAC.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Use the following procedure to configure captive portal content delivery rules in service sets: 1. Define one or more rules with the rule rule-name statement at the [edit services captive-portal-content-delivery] hierarchy level.
Documentation Updates Subscriber Management Provisioning Guide • The table in the topic, “AAA Access Messages and Supported RADIUS Attributes and Juniper Networks VSAs for Junos OS” incorrectly indicates that VSA 26-1 (Virtual-Router) supports CoA Request messages. VSA 26-1 does not support CoA Request messages. System Log Messages Reference • The formats of the MSVCS_LOG_SESSION_OPEN and MSVCS_LOG_SESSION_CLOSE system log messages in the "MSVCS System Log Messages" chapter are incorrectly specified.
Release Notes: Junos OS Release 13.
Migration, Upgrade, and Downgrade Instructions NOTE: Before upgrading, back up the file system and the currently active Junos OS configuration so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command: user@host> request system snapshot The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series The download and installation process for Junos OS Release 13.3 is different from previous Junos OS releases. Before upgrading to 64-bit Junos OS, read the instruction on the following pages: • To check Routing Engine compatibility, see Supported Routing Engines by Router. • To read the upgrade instructions, see Upgrading to 64-bit Junos OS. 1.
Migration, Upgrade, and Downgrade Instructions • http://hostname/pathname • scp://hostname/pathname (available only for Canada and U.S. version) The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series 1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines. 2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine. 3.
Migration, Upgrade, and Downgrade Instructions 2. After you have upgraded all routers, configure each router’s main instance loopback address as the source address for multicast interfaces. Include the default-vpn-source interface-name loopback-interface-name] statement at the [edit protocols pim] hierarchy level. 3. After you have configured the router’s main loopback address on each PE router, delete the multicast VPN loopback address (lo0.x) from all routers.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • All master Routing Engines in all routers run the same version of software. This is necessary for the routing matrix to operate. • All master and backup Routing Engines run the same version of software before beginning the upgrade procedure. Different versions of the Junos OS can have incompatible message formats especially if you turn on GRES.
Migration, Upgrade, and Downgrade Instructions Upgrading from Junos OS Release 9.2 or Earlier on a Router Enabled for Both PIM and NSR Junos OS Release 9.3 introduced NSR support for PIM for IPv4 traffic. However, the following PIM features are not currently supported with NSR.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series [edit] user@host# set protocols pim nonstop-routing disable user@host# activate protocols pim user@host# commit Downgrading from Release 13.3 To downgrade from Release 13.3 to another supported release, follow the procedure for upgrading, but replace the 13.3 jinstall package with one that corresponds to the appropriate release. NOTE: You cannot downgrade more than three releases.
Product Compatibility Related Documentation • New and Changed Features on page 21 • Changes in Behavior and Syntax on page 54 • Known Behavior on page 68 • Documentation Updates on page 135 • Product Compatibility on page 165 Product Compatibility • Hardware Compatibility on page 165 Hardware Compatibility To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guide and the Interface Module Reference
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Junos OS Release Notes for PTX Series Packet Transport Routers These release notes accompany Junos OS Release 13.3R6 for the PTX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software. You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at http://www.juniper.net/techpubs/software/junos/.
New and Changed Features provides a duplex LC connector and supports the 100GBASE-LR4 optical interface specification and monitoring. Starting in Junos OS Release 13.3, the “GEN2” optics have been redesigned with newer versions of internal components for reduced power consumption. The following interface module supports the CFP-GEN2-CGE-ER4 and CFP-GEN2-100GBASE-LR4 transceivers. For more information about interface modules, see the Interface Module Reference for your router.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Class of Service (CoS) • Support for strict-priority scheduling (PTX Series)—Beginning with Junos OS Release 13.3, interfaces on PTX Series routers support strict-priority scheduling. Configured queues are processed in strict-priority order.
New and Changed Features • Dual polarization quadrature phase shift keying (DP-QPSK) modulation and soft-decision forward error correction (SD-FEC) for long haul and metro applications You can use SNMP to manage the PIC based on RFC 3591, Managed Objects for the Optical Interface Type. [See 100-Gigabit Ethernet OTN Options Configuration Overview.] • Pre-FEC BER fast reroute (PTX3000)—Starting in Junos OS Release 13.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series [edit interfaces interface-name optics-options] hierarchy level. The following interface module supports the SPFF-10G-CT50-ZR transceiver: PTX: • 10-Gigabit Ethernet LAN/WAN OTN PIC with SFP+ (model number: P1-PTX-24-10G-W-SFPP)—Supported in Junos OS Release 13.2R3, 13.
New and Changed Features You can monitor various transport features like 24-hour bins and transport states by using the transport-monitoring statement at the [edit interfaces] hierarchy level. • Support for active flow monitoring version 9 (PTX3000 routers with CSE2000)—Starting with Junos OS Release 13.3R4, Carrier-Grade Service Engine (CSE2000) supports active flow monitoring version 9 on PTX3000 routers. The CSE2000 is tethered to a PTX3000 router to enable active flow monitoring version 9.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series • The PTX5000 does not support nonstop active routing in Junos OS Release 13.3. • The PTX5000 does not support unified in-service software upgrade (ISSU) in Junos OS Release 13.3. Software Installation and Upgrade • Unified ISSU support for the 100-Gbps DWDM OTN PIC (PTX5000)—Starting in Junos OS Release 13.
Changes in Behavior and Syntax which can cause packets to be dropped even when the queue is not congested or the port is not oversubscribed. • Exporting active flow monitoring version 9 packets from CSE2000 to PTX Series routers—Starting with Junos OS Release 13.3R4, active flow monitoring version 9 records created by CSE2000 are sent back to PTX Series Routers on the 10-Gigabit Ethernet interface. The PTX Series routers then forward the version 9 flow records to the version 9 flow server.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series The only way to determine the Junos OS version running on the device is to review the list of installed sub-packages. Junos OS Release 13.2 and Earlier Releases Without the Junos Field Junos OS Release 13.3 and Later Releases With the Junos Field user@host> show version Hostname: lab Model: ptx5000 JUNOS Base OS boot [12.3R2.5] JUNOS Base OS Software Suite [12.3R2.
Known Issues • Network Management and Monitoring on page 176 • Software Installation and Upgrade on page 176 Hardware • CCG configuration change does not reprogram hardware automatically. PR896226 General Routing • "rnh_get_forwarding_nh: RNH type 1 unexpected" kernel error messages observed.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series MPLS • The problem is seen in PTX Series routers where the composite next-hops are not observed for a given VPN mpls route and hence the show route output command gives a truncated value which results in script failure. This may be due to default disabled l3vpn-cnh in case of transit l3vpn router on PTX Series platform.
Resolved Issues Resolved Issues: Release 13.3R6 General Routing • On PTX Series routers with MPLS environment (30k transit LSP), large number of MPLS interfaces (in this case, 200 interfaces) are configured with 0 or 1 MPLS labels. When these interfaces flap, the FPC kernel memory usage might leak.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series configured, when primary clock is added back it should not fall back to primary, it should stay in secondary. But here it is falling back to Primary clock. PR1052549 • When the port on 24x 10GE(LWO) SFP+ (which never went link up since the PIC is onlined) is configured as CLI loopback, the ports will receive framing error during until the interface gets physically linked up. (i.e.
Resolved Issues • PCS statistics counter is now displayed for PTX 100GE interfaces in the following: cli > monitor interface PR1030819 Infrastructure • SNMP socket sequence error log. PR986613 Interfaces and Chassis • Interface statistic information is wrong for IPV6. This is expected behavior because ipv6 transit stat is not supported yet.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series MPLS • On PTX Series platform working as LSP ingress router, the MPLS auto-bandwidth feature might cause FPC to wedge condition with all interfaces down. PR1005339 Network Management and Monitoring • This PR fixes the issue where output ifIndex was being exported as 0. Unless there is a critical business need, we do not plan to backport the fix to releases earlier than 14.1.
Resolved Issues IPv6 • On PTX Series platform, when receiving high rate ipv4/ipv6/mpls packets with TTL equals 1, the ICMP TTL expired messages are sent back to the sender not according with the ICMP rate limit settings. PR893129 • PTX Series drops packets containing same source and destination IP due to LAND attack check.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series to avoid the problem, but it is rare and backup RPD will restart and the system will recover without intervention. PR830057 • While performing GRES, the following error message appears: Feb 24 21:23:57 striker1 license-check[1555]: LIBJNX_REPLICATE_RCP_ERROR: rcp -T re0:/config/license_revoked.db /config/license_revoked.db.new : rcp: /config/license_revoked.
Resolved Issues • Adding AE configuration and child interface configuration as two separate commits: a. Add AE interface configuration, without adding child interface configuration. b. Commit. c. Add the child interface configuration (et interface configurations) for the AE interface. d. Commit. PR901744 MPLS • In an RSVP P2MP crossover/pass-through scenario, more than one sub-LSP can use the same PHOP and NHOP.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Multicast • Starting in Junos OS Release 13.2, PTX Series routers accept traffic from remote sources to enable the remote source to be learned and advertised by MSDP so that receivers in other MSDP areas can join the source. To configure this feature, use the accept-remote-source configuration statement at the [edit protocols pim interface interface-name] hierarchy level.
Documentation Updates • Product Compatibility on page 188 Documentation Updates This section lists the errata and changes in Junos OS Release 13.3R6 documentation for the PTX Series. • Network Management Administration Guide for Routing Devices on page 185 • VPWS Feature Guide for Routing Devices on page 185 Network Management Administration Guide for Routing Devices • The syntax of the filter-interfaces statement in the “SNMP Configuration Statement” section is incorrect.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Upgrading Using Unified ISSU Unified in-service software upgrade (ISSU) enables you to upgrade between two different Junos OS releases with no disruption on the control plane and with minimal disruption of traffic. Unified in-service software upgrade is only supported by dual Routing Engine platforms. In addition, graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) must be enabled.
Migration, Upgrade, and Downgrade Instructions NOTE: We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process. The download and installation process for Junos OS Release 13.3 is different from previous Junos OS releases. 1. Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage: http://www.juniper.net/support/downloads/ 2.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series All other customers, use the following command: user@host> request system software add validate reboot source/jinstall-13.3R61-export-signed.tgz Replace the source with one of the following values: • /pathname—For a software package that is installed from a local directory on the router.
Product Compatibility Hardware Compatibility To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guide and the Interface Module Reference for the product.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Third-Party Components This product includes third-party components. To obtain a complete list of third-party components, see Copyright and Trademark Information. For a list of open source attributes for this Junos OS release, see Open Source: Source Files and Attributions.
Requesting Technical Support • Product warranties—For product warranty information, visit http://www.juniper.net/support/warranty/. • JTAC Hours of Operation —The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: • Find CSC offerings: http://www.
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series Revision History 5 May 2015—Revision 4, Junos OS Release 13.3R6– EX Series, M Series, MX Series, PTX Series, and T Series. 16 April 2015—Revision 3, Junos OS Release 13.3R6– EX Series, M Series, MX Series, PTX Series, and T Series. 9 April 2015—Revision 2, Junos OS Release 13.3R6– EX Series, M Series, MX Series, PTX Series, and T Series. 2 April 2015—Revision 1, Junos OS Release 13.
Requesting Technical Support 26 June 2014—Revision 6, Junos OS Release 13.3R2– EX Series, M Series, MX Series, PTX Series, and T Series. 29 May 2014—Revision 5, Junos OS Release 13.3R2– EX Series, M Series, MX Series, PTX Series, and T Series. 20 May 2014—Revision 4, Junos OS Release 13.3R2– EX Series, M Series, MX Series, PTX Series, and T Series. 12 May 2014—Revision 3, Junos OS Release 13.3R2– EX Series, M Series, MX Series, PTX Series, and T Series. 9 May 2014—Revision 2, Junos OS Release 13.
