Matrix MX-R5 Specifikace

Release Notes: Junos®OS Release 13.3R6for the EX Series, M Series, MX Series,PTX Series, and T Series5 May 2015ContentsIntroduction . . . . . . . . .

The new field provides a consistent means of identifying the Junos OS version, insteadof extracting that information from the list of installed subpac

•The snmp trap generated when an ipv6 BFD session goes up/down does not containthe ipv6 bfd session address. PR1018122•Junos OS implementation of RFC3

> 64 characters. The resulted jpool"_jpool_A_RULE_NAME_WHICH_IS_LONG_1234_A_TERM_ALSO_WITH_" will be usedwrongly in both terms. PR973465•

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 r

Forwarding and Sampling•When a firewall filter has one or more terms which have MX Series-only match conditionor actions, such filters will not be lis

chassisd) tried to connect using the TNP socket. SNMPD does not accept theseconnections. As a fix, in an MX-VC, we made sure that chassisd connects to

•When several PICs are set up as an aggregated Multi-services (AMS) doingload-balancing, if one PIC of the AMS bundle gets offline and then gets onlin

Uninitialized EDMEM[0x3d9565] Read (0x6db6db6d6db6db6d) fpc0 LUCHIP(0)RMC 3 Uninitialized EDMEM[0x3d81b6] Read (0x6db6db6d6db6db6d) These messagewould

interfaces xe-2/0/0 terse Interface Admin Link Proto Local Remote xe-2/0/0 up upxe-2/0/0.0 up up aenet --> ae102.0 xe-2/0/0.32767 up up aenet -->

reassigned to a template filter. This could be considered as a timing issue given it comeswith a very specific sequence of events only. PR949975•When

•When sending traffic coming on MPC and going out on DPC, the MAC entry on a PacketForwarding Engine will not be up-to-date and the frames targeted to

• Resolved Issues on page 13• Documentation Updates on page 19• Migration, Upgrade, and Downgrade Instructions on page 19• Product Compatibility on pa

•BMP is not sending a correctly formatted prefix for inet/inet6 labeled unicast BGPfamily routes. This occurs if the route resides in the inet[6].0 ta

Subscriber Access Management•MIB entries for jnxUserAAAAccessPoolRoutingInstance may not appear after deletingand re-adding an assignement pool under

General Routing•The ingress family feature (uRPF) unicast Reverse Path Forwarding check executionorder was invalidated when (FBF) Filter Based Forward

will be provided. forwarding-options { enhanced-hash-key { family mpls { +no-ether-pseudowire; } } } PR958685•In subscriber management environment, up

•In processing for fpc-resync and fab-liveness packets if error occurs while sendingpacket we do not free the packet. This causes packets buffers to l

•OpenFlow does not respond to port_down events when the echo interval timeout isset for less than 11 seconds. PR989308•The fabric performance of MPC1,

get aborted. This happens because although the MIC is removed physically but it doesnot get removed from the hardware database (HWDB), which makes the

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

•When Cisco running in an old version of PVST+, it does not carry VLAN ID in the end ofBPDU. So Juniper Networks equipment fails to responds to Topolo

•snmpwalk/snmpgetnext or "show snmp mib walk" fail when polling MPLSLSPOCTETS,MPLSLSPPACKETS, MPLSLSPINFOOCTETS or MPLSLSPINFOPACKETS. PR981

Known IssuesThis section lists the known issues in hardware and software in Junos OS Release 13.3R6for the EX Series.For the most complete and latest

•The error message 'unlink(): failed to delete .perm file: No such file or directory' waslogged when disconnecting from a Telnet session to

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 ab

•TXP with 13.1R4 might not trigger autoheal after 65535 CRC error event on inter-chassisoptical hsl2 link. Customer will need to do manual fabric plan

•The rpd process might crash when executing the command "show routeadvertising-protocol bgp <nbr>" without a table option, or with a t

•The dynamic flow control process (dfcd) might core dump when Dynamic TaskingControl Protocol (DTCP) trigger request is same for both the VLAN and DHC

Software Installation and Upgrade•Routing Engine could be brought to DB mode when rebooting after interrupteddowngrade. PR966462•By upgrade-with-confi

Resolved Issues: Release 13.3R2Forwarding and Sampling•When MAC addresses move, Layer 2 address learning process (l2ald) will be calledand produces so

•PIC level "account-layer2-overhead" knob with ethernet-bridge doesn't add"Adjustment Bytes". As a workaround, configure it u

changing gigether-options of core router facing interface multiple times continuously,the Flexible PIC Concentrator (FPC) CPU utilization might increa

Infrastructure•On RE-S-1800 family of Routing Engines, after an intensive writing to SSD, theimmediate rebooting might cause SSD to corrupt. PR937774I

LACP peer devices that receive the packets to reset the LACP connections. This mightcause continuous flaps for all aggregated or multichassis aggregat

•Kernel crash might happen when a router running a Junos OS install with the fix to PR937774 is rebooted. This problem will not be observed during the

•In a highly scaled configuration, the reroute of transit RSVP LSPs can result in BGP flapdue to lack of keepalive messages being generated by the Rou

•On I-chip platforms, when forwarding table filter (FTF) is configured for a virtual privateLAN service (VPLS) routing instance, the jtree memory corr

•In current Junos OS, a PSM shows dc output value even though it is turned off by aswitch. This cosmetic bug causes miscalculation of actual usage in

Services Applications•SIP call forwarding might fail when NAT is used between parties even though the SIPALG is in use. PR839629•Junos OS Release 11.4

• 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

Aggregated Ethernet Interfaces Feature Guide for Routing Devices•The following enhancements and additions apply to the “Example: ConfiguringMultichass

[edit interfaces ae1]user@PE2# set flexible-vlan-tagginguser@PE2# set encapsulation flexible-ethernet-servicesuser@PE2# set unit 0 encapsulation vlan-

The mode statement indicates whether an MC-LAG is in active-standby modeor active-active mode. Chassis that are in the same group must be in the samem

and if the RPM server is Packet Forwarding Engine-based, the RPM client must alsobe Packet Forwarding Engine-based.•The show chassis fabric unreachabl

Resolved Issues: Release 13.3R6Firewall Filters•On EX3300 switches, if you use a wildcard mask in firewall filters, the error messageUnaligned memory

Class of Service Library for Routing Devices•The Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs and Scaling ofPer-VLAN Queuing on Non-Que

processing for all packets that use PPM and run all PPM processing on the RoutingEngine by configuring the no-delegate-processing configuration statem

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 stat

Note the use of the vlan-id all statement in the virtual-switch instance calledcustomer-c1-v1-to-v1000.Firewall Filters Feature Guide for Routing Devi

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 Chass

•The following information regarding the guidelines for configuration of IP addressesfor NAT processing applies to the "Configuring Source and De

•For a trunk port, the default limit on the maximum number of MAC addresses thatcan be learned on a trunk port is 8192. Because a trunk port can be as

Services Interfaces Configuration Guide•In the Lines of Sample DTCP Parameter File table in the “Flow-Tap Filter Operation”topic, the description for

•The following information is missing from the passive-mode-tunneling configurationstatement and the “Example: Configuring Junos VPN Site Secure on MS

3. Use the show policer | match flow statement to verify that the flow-tap filter isremoved from the router:The following sample shows how to disable

Interfaces and Chassis•On EX9200 switches, in an MC-LAG scenario , a MAC address might incorrectly pointto an inter-chassis control link (ICL) after a

port-mirroring family (inet | inet6)] hierarchy level. To configure the input packetproperties for port mirroring, you must include the input statemen

•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 val

the inline-jflow statement at the [edit forwarding-options sampling instanceinstance-name family inet output] hierarchy level).•The following informat

•RFC 5102, Information Model for IP Flow Information ExportSubscriber Management Access Network Guide•The LAC Tunnel Selection Overview, Configuring W

Use the following procedure to configure captive portal content delivery rules in servicesets:1. Define one or more rules with the rule rule-name stat

Subscriber Management Provisioning Guide•The table in the topic, “AAA Access Messages and Supported RADIUS Attributes andJuniper Networks VSAs for Jun

RelatedDocumentationNew and Changed Features on page 21•• Changes in Behavior and Syntax on page 54• Known Behavior on page 68• Known Issues on page 7

NOTE: Before upgrading, back up the file system and the currently activeJunos OS configuration so that you can recover to a known, stableenvironment i

The download and installation process for Junos OS Release 13.3 is different from previousJunos OS releases.Before upgrading to 64-bit Junos OS, read

•http://hostname/pathname•scp://hostname/pathname (available only for Canada and U.S. version)The validate option validates the software package again

Routing Protocols•On an EX9200 switch with an IGMP configuration in which two receivers are joined tothe same (S,G) and IGMP immediate-leave is config

1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engineand save the configuration change to both Routing Engines.2. Install

2. After you have upgraded all routers, configure each router’s main instance loopbackaddress as the source address for multicast interfaces. Include

•All master Routing Engines in all routers run the same version of software. This isnecessary for the routing matrix to operate.•All master and backup

Upgrading from Junos OS Release 9.2 or Earlier on a Router Enabled for Both PIMand NSRJunos OS Release 9.3 introduced NSR support for PIM for IPv4 tra

[edit]user@host# set protocols pim nonstop-routing disableuser@host# activate protocols pimuser@host# commitDowngrading from Release 13.3To downgrade

RelatedDocumentationNew and Changed Features on page 21•• Changes in Behavior and Syntax on page 54• Known Behavior on page 68• Documentation Updates

Junos OS Release Notes for PTX Series Packet Transport RoutersThese release notes accompany Junos OS Release 13.3R6 for the PTX Series. Theydescribe n

provides a duplex LC connector and supports the 100GBASE-LR4 optical interfacespecification and monitoring. Starting in Junos OS Release 13.3, the “GE

Class of Service (CoS)•Support for strict-priority scheduling (PTX Series)—Beginning with Junos OS Release13.3, interfaces on PTX Series routers suppo

•Dual polarization quadrature phase shift keying (DP-QPSK) modulation andsoft-decision forward error correction (SD-FEC) for long haul and metro appli

OpenFlow•OpenFlow v1.0 running on an EX9200 switch does not respond reliably to interface upor down events within a specified time interval. Per a fix

[edit interfaces interface-name optics-options] hierarchy level. The following interfacemodule supports the SPFF-10G-CT50-ZR transceiver:PTX:•10-Gigab

You can monitor various transport features like 24-hour bins and transport states byusing the transport-monitoring statement at the [edit interfaces]

•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)

which can cause packets to be dropped even when the queue is not congested or theport is not oversubscribed.•Exporting active flow monitoring version

The only way to determine the Junos OS version running on the device is to review thelist of installed sub-packages.Junos OS Release 13.3 and Later Re

•Network Management and Monitoring on page 176•Software Installation and Upgrade on page 176Hardware•CCG configuration change does not reprogram hardw

MPLS•The problem is seen in PTX Series routers where the composite next-hops are notobserved for a given VPN mpls route and hence the show route outpu

Resolved Issues: Release 13.3R6General Routing•On PTX Series routers with MPLS environment (30k transit LSP), large number ofMPLS interfaces (in this

configured, when primary clock is added back it should not fall back to primary, it shouldstay in secondary. But here it is falling back to Primary cl

•PCS statistics counter is now displayed for PTX 100GE interfaces in the following: cli> monitor interface <intf> PR1030819Infrastructure•SNM

•On an EX9200 switch that works as a DHCP relay agent, if the switch receives broadcastDHCP ACK packets sent by another DHCP relay switch, those packe

MPLS•On PTX Series platform working as LSP ingress router, the MPLS auto-bandwidthfeature might cause FPC to wedge condition with all interfaces down.

IPv6•On PTX Series platform, when receiving high rate ipv4/ipv6/mpls packets with TTLequals 1, the ICMP TTL expired messages are sent back to the send

to avoid the problem, but it is rare and backup RPD will restart and the system willrecover without intervention. PR830057•While performing GRES, the

•Adding AE configuration and child interface configuration as two separate commits:a. Add AE interface configuration, without adding child interface c

Multicast•Starting in Junos OS Release 13.2, PTX Series routers accept traffic from remote sourcesto enable the remote source to be learned and advert

• Product Compatibility on page 188Documentation UpdatesThis section lists the errata and changes in Junos OS Release 13.3R6 documentation forthe PTX

Upgrading Using Unified ISSUUnified in-service software upgrade (ISSU) enables you to upgrade between two differentJunos OS releases with no disruptio

NOTE: We recommend that you upgrade all software packages out of bandusing the console because in-band connections are lost during the upgradeprocess.

All other customers, use the following command:user@host> request system software add validate rebootsource/jinstall-13.3R61-export-signed.tgzRepla

Hardware CompatibilityTo obtain information about the components that are supported on the devices, andspecial compatibility guidelines with the relea

• Known Behavior on page 11• Known Issues on page 12• Documentation Updates on page 19• Migration, Upgrade, and Downgrade Instructions on page 19• Pro

Third-Party ComponentsThis product includes third-party components. To obtain a complete list of third-partycomponents, see Copyright and Trademark In

•Product warranties—For product warranty information, visithttp://www.juniper.net/support/warranty/.•JTAC Hours of Operation —The JTAC centers have re

Revision History5 May 2015—Revision 4, Junos OS Release 13.3R6– EX Series, M Series, MX Series, PTXSeries, and T Series.16 April 2015—Revision 3, Juno

26 June 2014—Revision 6, Junos OS Release 13.3R2– EX Series, M Series, MX Series, PTXSeries, and T Series.29 May 2014—Revision 5, Junos OS Release 13.

Resolved Issues: Release 13.3R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Documentation Updates . . . . . . . . . . . . . .

To upgrade or downgrade from a non-EEOL release to a release more than three releasesbefore or after, first upgrade to the next EEOL release and then

Junos OS Release Notes for M Series Multiservice Edge Routers, MX Series3D UniversalEdge Routers, and T Series Core RoutersThese release notes accompa

•Subscriber Management and Services (MX Series) on page 47•VPNs on page 53Hardware•MIC support (MX104)—Junos OS Release 13.3 and later releases extend

•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-ER4transce

•100-Gigabit Ethernet PIC with CFP (model numbers: PD-1CE-CFP-FPC4 andPD-1CGE-CFP)—Supported in Junos OS Releases 12.3R5, 13.2R3, 13.3R1, and later[Se

•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

routers, MPC5E is housed in an adapter card. MPC5E is a fixed-configuration MPC withfour built-in PICs and does not contain separate slots for Modular

•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

•Fiber-optic small form-factor pluggable (SFP) transceivers:•1000BASE-LH (model number: SFP-1GE-LH)•1000BASE-LX (model number: SFP-1GE-LX)•1000BASE-SX

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, andlater•16-port 10

Software Installation and Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Subscriber Management and Services . . . . . . . . . . .

•Padding of Ethernet Frames with VLAN.•Sending Internet Control Message Protocol (ICMP) redirect messages.•Termination or tunneling of all subscriber-

•[edit protocols l2circuit neighbor ip-address] if the switching is done over a Layer 2circuit.•[edit protocols connections remote-interface-switch re

(CoS) hierarchical schedulers can be configured on MPC5E interfaces. This feature issupported on egress only.You can use hierarchical schedulers to de

High Availability (HA) and Resiliency•MX Series Virtual Chassis support for multichassis link aggregation (MX Seriesrouters with MPCs)—Starting in Jun

Services to be synchronized statefully include:•Stateful firewall•NAT (NAPT44 and APP only)Both IPv4 and IPv6 sessions are synchronized.Synchronizatio

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

•Support for ATM virtual connection multiplexing and LLC encapsulation (MXSeries)—Starting in Junos OS Release 13.3, ATM virtual connection (VC) multi

•Support for GPS external clock interface on the SCBE (MX240, MX480, andMX960)—Starting with Junos OS Release 13.3, you can configure the EnhancedSCB—

•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

•Pseudowire logical interface device MAC address configuration (MX Series)—Startingin Junos OS Release 13.3, you can configure a MAC address for a pse

System Log Messages Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155System Services Administration Guide for Routing Devices

[edit interfaces interface-name optics-options] hierarchy level. The following interfacemodule supports the SPFF-10G-CT50-ZR transceiver:MX Series:•16

IPv6•New forwarding-class-accounting statement (MX Series)—Starting in Junos OS Release13.3R3, new forwarding class accounting statistics can be enabl

request that other BGP VPLS PE routers insert a control word between the label stackand the MPLS payload.Multicast•IGMP and PIM snooping support (MPC3

OpenFlow•Support for OpenFlow v1.0 (MX80, MX240, MX480, and MX960)—Starting withJunos OS Release 13.3, the MX80, MX240, MX480, and MX960 routers suppo

Routing Policy and Firewall Filters•Using a firewall filter to prevent or allow datagram fragmentation (MXSeries)—Starting in Junos OS Release 13.3, y

interface-name] hierarchy level. There is no new configuration option available if thefirewall filter term action is set to next-ip, meaning that if t

Services Applications•Enabling Layer 2 Protocol Tunneling (L2PT) support for VLAN Spanning Tree Protocol(VSTP) and per-VSTP (MX Series routers with MP

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

•RADIUS logical line identifier (MX Series)—Starting in Junos OS Release 13.3, serviceproviders can use a virtual port feature, known as the logical l

underlying interfaces. In earlier Junos OS releases, PPPoE subscriber session lockoutidentified and filtered subscriber sessions only by their unique

Migration, Upgrade, and Downgrade Instructions . . . . . . . . . . . . . . . . . . . . . 185Upgrading Using Unified ISSU . . . . . . . . . . . . . . .

is provided to the client using DHCPv6-PD, the RADIUS interim accounting messageincludes the delegated prefix (IA_PD, such as /56). Theaddress-change-

[See ANCP Topology Discovery and Traffic Reporting Overview.]•Support for ANCP generic response messages and result codes (MX Series)—Startingin Junos

You can filter on the user, the domain, or both. You can use a wildcard (*) at thebeginning or end of each term, as in the following examples: tom@exa

VPNs•Enhanced multicast VPNs traceoptions statement (M Series, MX Series, and TSeries)—Starting in Junos OS Release 13.3, the multicast VPNs traceopti

• Resolved Issues on page 80• Documentation Updates on page 135• Migration, Upgrade, and Downgrade Instructions on page 156• Product Compatibility on

High Availability (HA) and Resiliency•New redundancy failover CLI statement (M, MX, T, TX Matrix Plus)—Starting in JunosOS Release13.3R6, the chassis

•filter-action protocol group—The following packet types are available for unclassifiedfirewall filter action packets, which are sent to the host beca

only for interfaces with inet address families and on MX Series routers with MPCs.When you disable ARP policers per interface, the packets are continu

LSPs. To enable the polling and display of transit LSP statistics, include thetransit-statistics-polling statement at the [edit protocols mpls statist

Network Management and Monitoring•Support of new system log by SNMP for notifying target addition (M Series, MXSeries, and T Series)—Beginning with Ju

IntroductionJunos OS runs on the following Juniper Networks®hardware: ACX Series, EX Series, JSeries, M Series, MX Series, PTX Series, QFabric, QFX Se

Security•Packet types added for DDoS protection L2TP policers (MX Series with MPCs, T4000with FPC5)—The following eight packet types have been added t

by the destination-prefix statement in the then statement. Starting in Junos OS Release13.3, this restriction is enforced.[edit services nat]rule rule

NOTE: The header-integrity-check option that is supported on MS-MICsand MS-MPCs to verify the packet header for anomalies in IP, TCP, UDP,and ICMP inf

MSVCS_LOG_SESSION_CLOSE system log messages are modified to toggle the orderof the destination IPv4 address and destination port address displayed in

•Configuration support to prevent the LACP MC-LAG system ID from reverting to thedefault LACP system ID on ICCP failure—Beginning in Junos OS Release

You can determine whether direct-connect is configured for particular interfaces byissuing the show interfaces or show pppoe underlying-interfaces com

You can configure the router to collect time statistics, or both volume and time statistics,for the service accounting sessions being managed by AAA.

you no longer have to configure a tunnel profile on the LAC. In earlier releases, tunnelswitching failed when you did not also configure the LAC, even

containing adjacent repetition operators or adjacent bounded repetitions. Junos OSuses regular expressions in several places within the CLI. Exploitat

General Routing•In MX2020 routers and T Series routers, memory usage of the device increases whenauto-64-bit statement is issued.High Availability (HA

Hardware•Extended cable manager for EX9214 switches—An extended cable manager is nowavailable for EX9214 switches. The extended cable manager enables

statistics you want to clear. When you reset firewall statistics to zero, you also zerothe counters reported to RADIUS.•On the MX Series, subscriber m

•Services Applications on page 78•Software Installation and Upgrade on page 79•User Interface and Configuration on page 79•VPNs on page 79Authenticati

RPD. Those garbage interfaces will result KRT queue stack issue upon later lsire-configuration. PR912861•Periodic "show subscribers" CLI req

•On M Series, MX Series, T Series platform with DHCP relay configured, the router mightkeep filling a specific partition "/var/mfs/sdb" with

•In Ethernet OAM connectivity-fault-management, Junos OS default encodes MAID(MDname and MA name) in character format. Currently only 43 octets are su

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

•Wrong source IP is used when responding to traceroute in L3VPN setup. This is not anindication of traffic taking wrong link. PR883701•On all high-end

•The Priority code point (PCP) and Drop eligible indicator (DEI) bit in 802.1Q header arepreserved while packet gets routed within the same Packet For

very high and the host path and interface network control queues can get congested.Refer to KB29553 for more information and mitigation. PR945215•In r

Software Installation and Upgrade•Filesystem corruption might lead to routing engine boot up failure. This problem isobserved when directory structure

OpenFlow•Support for OpenFlow v1.0—Starting with Junos OS Release 13.3, EX9200 switchessupport OpenFlow v1.0. You use the OpenFlow remote controller t

RelatedDocumentationNew and Changed Features on page 21•• Changes in Behavior and Syntax on page 54• Known Behavior on page 68• Resolved Issues on pag

General Routing•On MX Series platform with Enhanced DPCs equipped, after router rebooted, the IRBbroadcast channel is not enabled, all the broadcast p

•On MX Series platforms with ADPC FPCs, M120, or M7i/M10i with Enhanced CFEB, eachVPLS LSI interface flapping triggers a memory leak in jtree segment

•On MX Series platform with one of the following protocols configuration, flapping theprotocols will trigger the Composite Next-hop change operation.

Interfaces and Chassis•Refer to the following topology. If we set interface ge-1/0/8 disable, interface xe-2/0/0and xe-2/1/0 become down status becaus

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 interfac

•When node-protection is enabled for a specified LSP and optimize-timer for anode-protecting bypass LSP is configured on router, the bypass route migh

•A Packet Forwarding Engine memory leak is seen when multicast receivers areconnected in a bridge domain where IGMP snooping is enabled and IGMP messa

command "show route advertising-protocol bgp <peer-addr>" might crash the routingprotocol process (rpd). This is very corner issue and

Routing Policy and Firewall Filters•In the BGP environment, if operator "!" exists in the regex for as-path, the commitoperation fails. PR10

Dynamic Host Configuration Protocol•DHCP clients can send packets without Option 255 (EX9200)—On EX9200 switches,starting with Junos OS Release 13.3R5

the rpd might crash due to trying to reset an internal variable which is already resetduring route addition for the new local VC connection. PR1053887

General Routing•"show services accounting usage" does not populate cpu utilization for XLP basedcards . Please use "show services servi

level to suit your deployment needs. The rate at which syslog messages can be sentto the Routing Engine is 10,000 logs per second. PR1001201•With NSR

command is configured prior to the upgrade. This PR reverses the above change andallows hash-key command to be ignored on unsupported platforms: show

MS-MPC PICs pointing to two eth interfaces connect to CB0 and CB1 separately mightbe wrongly created. Then if pull out RE0/CB0, the MS-PIC would still

•VRRP daemon (vrrpd) memory leak might be observed in "show system processesextensive" when VRRP is set with routing-instance and then chang

have the sum of te-metric of IGP with highest credibility at each hop in ERO. This hasbeen corrected and the cspf-metric will be sum of te-metric of c

•Micro BFD sessions are used to monitor the status of individual LAG member links.When micro BFD configurations are added after the LAG bundle configu

case, the corresponding L2 nexthop to the L3 IRB nexthop is a DISCARD nexthop andwill cause the FPC to crash. PR1026124•When receiving traffic coming

Routing Protocols•Prefixes that are marked with two or more route target communities (matching multipleconfigured targets configured in policies) will