terminating魅族mx

JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeries18August2016ContentsIntroduction3JunosOSReleaseNotesforMXSeries3DUniversalEdgeRoutersandTSeriesCoreRouters3NewandChangedFeatures3Hardware4GeneralRouting5Management6Multicast6NetworkManagementandMonitoring7PlatformandInfrastructure7SubscriberManagementandServices(MXSeries)9VPNs9ChangesinBehaviorandSyntax9SubscriberManagementandServices(MXSeries)10VPNs10KnownBehavior10GeneralRouting11KnownIssues13GeneralRouting14InterfacesandChassis15Layer2Features15MPLS15NetworkManagementandMonitoring16PlatformandInfrastructure16RoutingProtocols17ServicesApplications17SubscriberManagementandServices(MXSeries)18UserInterfaceandConfiguration18ResolvedIssues19ResolvedIssues:15.
1F319ResolvedIssues:15.
1F228DocumentationUpdates381Copyright2016,JuniperNetworks,Inc.
Migration,Upgrade,andDowngradeInstructions38BasicProcedureforUpgradingtoRelease15.
1F339UpgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD10.
x)41UpgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD6.
1).
.
.
42UpgradeandDowngradeSupportPolicyforJunosOSReleases44UpgradingaRouterwithRedundantRoutingEngines44UpgradingtheSoftwareforaRoutingMatrix45UpgradingUsingUnifiedISSU46DowngradingfromRelease15.
146ProductCompatibility47HardwareCompatibility47JunosOSReleaseNotesforPTXSeriesPacketTransportRouters48NewandChangedFeatures48Hardware48GeneralRouting49InterfacesandChassis50Management50ChangesinBehaviorandSyntax50KnownBehavior51GeneralRouting51KnownIssues53GeneralRouting53InterfacesandChassis53MPLS54PlatformandInfrastructure54RoutingProtocols54ResolvedIssues54ResolvedIssues:15.
1F354ResolvedIssues:15.
1F257DocumentationUpdates58Migration,Upgrade,andDowngradeInstructions59UpgradingUsingUnifiedISSU59UpgradingaRouterwithRedundantRoutingEngines59BasicProcedureforUpgradingtoRelease15.
1F359ProductCompatibility63HardwareCompatibility63Third-PartyComponents64FindingMoreInformation64DocumentationFeedback64RequestingTechnicalSupport65Self-HelpOnlineToolsandResources65OpeningaCasewithJTAC65RevisionHistory66Copyright2016,JuniperNetworks,Inc.
2JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesIntroductionJunosOSrunsonthefollowingJuniperNetworkshardware:ACXSeries,EXSeries,MSeries,MXSeries,PTXSeries,QFabricsystems,QFXSeries,SRXSeries,TSeries,andJunosFusion.
ThesereleasenotesaccompanyJunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeries.
Theydescribenewandchangedfeatures,limitations,andknownandresolvedproblemsinthehardwareandsoftware.
JunosOSReleaseNotesforMXSeries3DUniversalEdgeRoutersandTSeriesCoreRoutersThesereleasenotesaccompanyJunosOSRelease15.
1F3fortheMXSeriesandTSeries.
Theydescribenewandchangedfeatures,limitations,andknownandresolvedproblemsinthehardwareandsoftware.
YoucanalsofindthesereleasenotesontheJuniperNetworksJunosOSDocumentationwebpage,locatedathttp://www.
juniper.
net/techpubs/software/junos/.
CAUTION:Thisreleaseintroducessomebehaviorchangestotheunifiedin-servicesoftwareupgrade(ISSU)functionalityforMXSeriesandTSeriesrouters.
WedonotrecommendusingunifiedISSUtoupgradefromanearlierJunosOSreleasetoJunosOSRelease15.
1.
NewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10KnownIssuesonpage13ResolvedIssuesonpage19DocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47NewandChangedFeaturesThissectiondescribesthenewfeaturesandenhancementstoexistingfeaturesinJunosOSRelease15.
1F3fortheMXSeries.
Hardwareonpage4GeneralRoutingonpage5Managementonpage6Multicastonpage6NetworkManagementandMonitoringonpage73Copyright2016,JuniperNetworks,Inc.
IntroductionPlatformandInfrastructureonpage7SubscriberManagementandServices(MXSeries)onpage9VPNsonpage9HardwareNewRoutingEngineRE-S-X6-64G(MX240,MX480,andMX960)—StartinginJunosOSRelease15.
1F4,theRoutingEngineRE-S-X6-64GissupportedonMX240,MX480,andMX960routers.
ThisRoutingEnginehasanincreasedcomputingcapabilityandscalabilitytosupporttherapidriseinthedataplanecapacity.
TheRoutingEngineisbasedonamodularvirtualizedarchitectureandleveragesthehardware-assistedvirtualizationcapabilities.
NOTE:Subscriberservicesandvirtual-chassissupportisnotavailableinJunosOS15.
1Fxreleases.
TheRoutingEnginehasa64-bitCPUandsupportsa64-bitkerneland64-bitapplications.
Withitsmulticorecapabilities,theRoutingEnginesupportssymmetricmultiprocessingintheJunosOSkernelandhostedapplications.
NOTE:TheRoutingEngineRE-S-X6-64GissupportedonlyonSCBE2,anditisnotcompatiblewiththeSCBortheSCBE.
Newrate-selectableMPCMPC7E-MRATE(MX2020,MX2010,MX960,MX480,andMX240)—StartinginJunosOSRelease15.
1F4,therate-selectableMPCMPC7E(Multi-Rate)(modelnumber:MPC7E-MRATE)issupportedonMX2020,MX2010,MX960,MX480,andMX240routers.
ThemainfeaturesoftheMPC7E-MRATEMPCarethefollowing:Line-ratethroughputofupto480GbpsonMX240,MX480,andMX960routers.
Line-ratethroughputofupto400GbpsontheMX2000lineofrouters.
Twelveportsthatcaneachbeconfiguredasa40-GigabitEthernetportorasfour10-GigabitEthernetportsbyusingabreakoutcable.
Theportssupportquadsmall-formfactorpluggableplus(QSFP+)transceivers.
Fourports—0/2,0/5,1/2,and1/5—outofthetwelveportscanbeconfiguredas100-GigabitEthernetports.
Youcanconfiguredifferentcombinationsofportspeedsaslongastheaggregatecapacitypergroupofsixportslabeled0/0through0/5doesnotexceed240Gbps.
Similarly,aggregatecapacitypergroupoftheothersixportslabeled1/0through1/5mustnotexceed240Gbps.
NOTE:TousetheMPC7E-MRATEMPC,youmustdownloadandinstalltheJunosContinuitysoftwarepackageforJunosOSRelease15.
1F4.
Copyright2016,JuniperNetworks,Inc.
4JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesGeneralRoutingSupportforvirtualizationonRE-S-X6-64G(MX240,MX480,MX960,MX2010,andMX2020)—TheRoutingEngineRE-S-X6-64Gsupportsvirtualizationforthefollowingplatforms:MX240,MX480,andMX960—JunosOSRelease15.
1F3andlaterMX2010andMX2020—JunosOSRelease15.
1F5andlaterVirtualizationenablestheroutertosupportmultipleinstancesofJunosOSandotheroperatingsystemsonthesameRoutingEngine.
However,forJunosOSRelease15.
1F3,oneinstanceofJunosOS,whichrunsasaguestoperatingsystem,islaunchedbydefault.
Theuserneedstologintothisinstanceforoperationsandmanagement.
WithvirtualizationoftheRoutingEngine,JunosOSsupportsnewrequestandshowcommandsassociatedwithhostandhypervisorprocesses.
Thecommandsarerelatedto:Reboot,halt,andpowermanagementforthehostSoftwareupgradeforthehostDisksnapshotforthehostSupportforthecombinedoperationofSynchronousEthernetandPrecisionTimeProtocolorhybridmode(MX104)—AcombinedoperationofSynchronousEthernetandPrecisionTimeProtocol(PTP),alsoknownashybridmode,issupportedontheMX104routers.
Inhybridmode,theSynchronousEthernetequipmentclock(EEC)derivesthefrequencyfromSynchronousEthernetandthephaseandtimeofdayfromPTP(alsoknownasIEEE1588v2)fortimesynchronization.
SynchronousEthernetandPTPprovidefrequencyandphasesynchronization;however,theaccuracyintheorderofnanosecondsisdifficulttoachievethrougheitherPTPorSynchronousEthernet,andtheydonotsupportalargenumberofnetworkhops.
Hybridmoderesolvestheseissuesbyextendingthenumberofnetworkhopsandalsoprovidestheclocksynchronizationaccuracyintheorderoftensofnanoseconds.
Toconfigurehybridmode,includethehybridsynchronous-ethernet-mappingclock-sourceip-addressinterfaceinterface-name1statementatthe[editprotocolsptpslave]hierarchylevel.
TosettheEthernetSynchronizationMessageChannel(ESMC)fromthePTPclockclass,includetheconvert-clock-class-to-quality-levelstatementatthe[editprotocolsptpslave]hierarchylevel.
TooverridethedefaultPTPclockclasstoESMCmapping,includetheclock-class-to-quality-level-mappingquality-levelql-valueclock-classclock-class-valuestatementatthe[editprotocolsptpslave]hierarchylevel,whereclock-classindicatesthecurrentstateoftheclockandthequality-levelindicatestheclocktype.
NotethatiftheselectedSynchronousEthernetreferencefails,theroutercontinuestoworkinPTPmode.
Youcanusetheshowptphybridstatusoperationalcommandtofindthecurrentoperatingmode.
5Copyright2016,JuniperNetworks,Inc.
NewandChangedFeaturesNOTE:ToswitchbetweenthePTPandSynchronousEthernetmodes,youmustfirstdeactivatetheconfigurationforthecurrentmodeandthencommittheconfiguration.
Waitfor30seconds,configurethenewmodeanditsrelatedparameters,andthencommittheconfiguration.
Hybridmodeisnotsupportedonintegratedroutingandbridging(IRB)andaggregatedEthernetinterfacesconfiguredonMX104routers.
Unifiedin-servicesoftwareupgrade(unifiedISSU)isnotsupportedwhenclocksynchronizationisconfiguredforhybridmodeonMX104routers.
SupportforPTPoverIRBinterfaces(MX104)—StartinginJunosOSRelease15.
1F5,MX104routerssupportPrecisionTimeProtocol(PTP)overintegratedroutingandbridging(IRB)interfaces.
InreleasesbeforeJunosOSRelease15.
1F5,MX104routerssupportPTPoverphysicalEthernetinterfacesonly.
ManagementRoutertelemetrydataforhardwareandsoftware(MXSeries)—StartinginJunosOSRelease15.
1F3,youcanconfigureMXSeriesrouterstoexporttelemetrydatafromsupportedinterfacehardware.
LinecardsensordatasuchasinterfaceRSVPTELSPeventsaresentdirectlytoconfiguredcollectionpointswithoutinvolvingpolling.
Youconfigureallparametersatthe[editservicesanalytics]hierarchylevel.
YoucanconfiguretheexactinterfacesandLSPsforexportstatisticsusingregularexpressionresourcefiltermatches.
SupportedMPChardwareonMXSeriesroutersisMPC1throughMPC6E.
MulticastProtectionagainstlabelspoofingorerrantlabelinjectionacrossASBRs(MSeries,MXSeries,andTSeries)—StartingwithJunosOSRelease15.
1F2,youcanuseregularBGPimplicitandexplicitexportpoliciestorestrictVPNASBRpeerrouteadvertisementtoagivenroutinginstance.
ThisisespeciallyusefulinthecontextofInter-ASVPNOption-BASBRsbecauseitpreventsapeerASBRinaneighboringASfromspoofingorunintentionallyinjectingaVPNlabelintendedforadifferentpeerASorintra-ASintotheprotectedAS.
Inotherwords,serviceproviderscanconfigureacommonASBRsoitdoesnotacceptMPLSpacketsfromapeerASBRunlessthelabelhasbeenexplicitlyadvertisedtothecommonASBR.
Twonewcommandsareintroducedtoprovidethisprotection:mpls-forwardingatthe[editrouting-instancesnameinstance-typempls-forwarding]hierarchylevelandforwarding-contextatthe[editprotocolsbgpgroupgroup-nameneighboraddress],hierarchylevel.
SAFI129NLRIcompliancewithRFC6514(MXSeries)—StartingwithJunosOSRelease15.
1F2,theNLRIformatavailableforBGPVPNmulticastischangingfromthedefactoformatofSAFI128toSAFI129asdefinedinRFC6514.
SAFI128useslength,label,prefix.
SAFI129useslength,prefix.
Copyright2016,JuniperNetworks,Inc.
6JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesTouseSAFI129,enabletherfc6514-compliant-safi129statementatanyofthefollowinghierarchylevels:[editprotocolsbgp],[editprotocolsbgpgroupgroup-name],or[editprotocolsbgpgroupgroup-nameneighboraddress].
Latencyfairnessoptimizedmulticast(MXSeries)—StartingwithJunosOSRelease15.
1F3,youcanreducelatencyinthemulticastpacketdeliverybyoptimizingmulticastpacketssenttothePacketForwardingEngines.
Youcanachievethisbyenablingtheingressorlocal-latency-fairnessoptioninthemulticast-replicationconfigurationstatementatthe[editforwarding-options]hierarchylevel.
Themulticast-replicationstatementissupportedonlyonplatformswiththeenhanced-ipmodeenabled.
ThisfeatureisnotsupportedinVPLSnetworksandLayer2bridging.
NetworkManagementandMonitoringSNMPsupportforfabricqueuedepth,WANqueuedepth,andfabriccounter(MX240,MX480,MX960,MX2010,andMX2020)—StartingwithRelease15.
1F3,JunosOSprovidesSNMPsupportforWANqueuedepth,fabricqueuedepth,andfabriccounter.
ThefollowingSNMPMIBtablesincludetheassociatedobjects:jnxCosQstatTabletablejnxCosIngressQstatTabletablejnxFabricMibtableInaddition,thisfeaturesupportsthefollowingtrapsforthePacketForwardingEngineresourcemonitoringMIBs:jnxPfeMemoryTrapVarsjnxPfeMemoryNotificationsSupportforTimingMIBonMX104router—StartinginJunosOSRelease15.
1F5,MX1043DUniversalEdgeRoutersupportsthetimingfeature.
Anewenterprise-specificMIB,TimingFeatureDefect/EventNotificationMIB,hasbeenaddedtosupportthisfeature.
Thetrapnotificationsaredisabledbydefault.
ToenableSNMPtrapnotificationsfortimingeventsanddefects,includethetiming-eventsstatementatthe[editsnmptrap-grouptrap-groupobjectcategories]hierarchylevel.
PlatformandInfrastructureVirtualMXSeriesrouter(vMX)—StartinginJunosOSRelease15.
1F3,youcandeployvMXroutersonx86servers.
vMXsupportsmostofthefeaturesavailableonMXSeriesroutersandallowsyoutoleverageJunosOStoprovideaquickandflexibledeployment.
vMXprovidesthefollowingbenefits:Optimizescarrier-graderoutingforthex86environmentSimplifiesoperationsbyconsistencywithMXSeriesroutersIntroducesnewserviceswithoutreconfigurationofcurrentinfrastructurePerformancemodeisdefaultforchassis(vMX)—StartinginJunosOSRelease15.
1F5,performancemodeisenabledbydefaultforthechassis.
PerformancemodeneedsmorevCPUsandmemorytorunathigherbandwidth,whilelitemodeneedsfewer7Copyright2016,JuniperNetworks,Inc.
NewandChangedFeaturesvCPUsandmemorytorunatlowerbandwidth.
Youenablelitemodebyconfiguringthelite-modeoptionatthe[editchassisfpc0]hierarchylevel.
Copyright2016,JuniperNetworks,Inc.
8JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesSubscriberManagementandServices(MXSeries)NewsupportforFramed-IP-Netmaskforaccess-internalroutes(MXSeries)—StartinginJunosOSRelease15.
1F3,themaskvaluereturnedbyRADIUSintheFramed-IP-NetmaskattributeduringPPPnegotiationisconsideredforapplicationtotheaccess-internalrouteforthesubscribersession.
Inearlierreleases,theattributemaskisignoredanda/32netmaskisalwaysapplied,withtheconsequencethattheaddressissettothevalueoftheFramed-IP-AddressattributereturnedbyRADIUS.
Now,whentheSDB_FRAMED_PROTOCOLattributeisequaltoAUTHD_FRAMED_PROTOCOL_PPP,thevalueofSDB_USER_IP_MASKissetto255.
255.
255.
255bydefault.
ThisvalueisoverriddenbytheFramed-IP-Netmaskvalue,ifpresent.
TheIPNetmaskfieldintheoutputoftheshowsubscriberscommandnowdisplaysthedefaultvalueof255.
255.
255.
255ortheactualvalueofFramed-IP-NetmaskonlywhentheSDB_FRAMED_PROTOCOLattributeisequaltoAUTHD_FRAMED_PROTOCOL_PPP.
VPNsVPLSdynamicprofilesnotsupportedwith64-bitrpd(MXSeries)—StartingwithJunosOSRelease15.
1F3,virtualprivateLANservice(VPLS)dynamicprofilesarenotsupportedwiththe64-bitmoderoutingprotocolprocess(rpd).
Anewsystemlogerror(RPD_DYN_CFG_64RPD_UNSUPPORTED)isdisplayedwhenthisconditionoccursindicatingthatrpdfailedtonotifythedynamicconfigurationclientsaboutitsavailabilitytoprocessthedynamicconfigurationrequests.
ToenabletheVPLSdynamicprofilesconfigurationanduse32-bitmode,configurerpdbyusingthesetsystemprocessroutingforce-32-bitcommandintheCLI.
RelatedDocumentationChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10KnownIssuesonpage13ResolvedIssuesonpage19DocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47ChangesinBehaviorandSyntaxThissectionliststhechangesinbehaviorofJunosOSfeaturesandchangesinthesyntaxofJunosOSstatementsandcommandsfromJunosOSRelease15.
1F3fortheMXSeriesandTSeries.
SubscriberManagementandServices(MXSeries)onpage10VPNsonpage109Copyright2016,JuniperNetworks,Inc.
ChangesinBehaviorandSyntaxSubscriberManagementandServices(MXSeries)NOTE:Althoughpresentinthecode,thesubscribermanagementfeaturesarenotsupportedinJunosOSRelease15.
1F3.
DocumentationforsubscribermanagementfeaturesisincludedintheJunosOSRelease15.
1documentationset.
LocalDNSconfigurationsavailablewhenauthenticationorderissettonone(MXSeries)—StartinginJunosOSRelease15.
1F2,subscribersgettheDNSserveraddresseswhenbothofthefollowingaretrue:Theauthenticationorderissettononeatthe[editaccessprofileprofile-nameauthentication-order]hierarchylevel.
ADNSserveraddressisconfiguredlocallyintheaccessprofilewiththedomain-name-server,domain-name-server-inet,ordomain-name-server-inet6statementatthe[editaccessprofileprofile-name]hierarchylevel.
Inearlierreleases,subscribersgetanIPaddressinthissituation,butnottheDNSserveraddresses.
VPNsClearallInternetkeyexchange(IKE),trafficencryptionkey(TEK),keyencryptionkey(KEK),andsecurityassociations(SAs)forgroupVPN(MXSeries)—Theclearsecuritygroup-vpnmembergroupCLIcommandhasbeenintroducedintheRelease15.
1F3ofJunosOSforMXSeriesrouterstoclearallInternetkeyexchange(IKE),trafficencryptionkey(TEK),keyencryption,andkey(KEK)securityassociations(SAs)foragroupVPN.
user@host>clearsecuritygroup-vpnmembergroupRelatedDocumentationNewandChangedFeaturesonpage3KnownBehavioronpage10KnownIssuesonpage13ResolvedIssuesonpage19DocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47KnownBehaviorThissectioncontainstheknownbehavior,systemmaximums,andlimitationsinhardwareandsoftwareinJunosOSRelease15.
1F3fortheMXSeriesandTSeries.
GeneralRoutingonpage11Copyright2016,JuniperNetworks,Inc.
10JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesGeneralRoutingThefollowingrequestcommandsarenotavailablefortheRoutingEngineRE-S-X6-64GontheMX240,MX480,MX960,MX2010,andMX2020:requestsystemhaltrequestsystempartitionrequestsystempoweroffrequestsystempoweronThescopeoffunctionalityofthefollowingcommandsislimitedtoJunosOSguestlevel:requestsystemrebootrequestsystemsnapshotrequestsystemsoftwareaddrequestsystemzeroizeYoucanusethefollowingequivalentrequestvmhostcommandstoachievethefunctionality:requestvmhostcleanuprequestvmhostfile-copyrequestvmhosthaltrequestvmhosthard-disk-testrequestvmhostpower-offrequestvmhostpower-onrequestvmhostrebootrequestvmhostsnapshotrequestvmhostsoftwareabortrequestvmhostsoftwareaddrequestvmhostsoftwarein-service-upgraderequestvmhostsoftwarerollbackrequestvmhostzeroizeTheoutputofthefollowingshowcommandsaremodifiedfortheRoutingEngineRE-S-X6-64G:showchassisenvironmentrouting-engineshowchassishardwareshowchassishardwareextensive11Copyright2016,JuniperNetworks,Inc.
KnownBehaviorshowchassisrouting-engineshowsystemsoftwareThefollowingnewshowcommandsareintroducedfortheRoutingEngineRE-S-X6-64G:showvmhostbridgeshowvmhostcrashshowvmhosthardwareshowvmhostinformationshowvmhostlogsshowvmhostnetstatshowvmhostprocessesshowvmhostresource-usageshowvmhostsnapshotshowvmhoststatusshowvmhostuptimeshowvmhostversionThefollowingnewconfigurationstatementsareintroducedfortheRoutingEngineRE-S-X6-64G:editsystemprocessesapp-engine-virtual-machine-management-serviceeditvmhostDuringdeletionandrestorationofscaledconfigurationsonMX240,MX480,MX960,MX2010,andMX2020,errormessagesrelatedtonexthopsaredisplayed.
Theconfigurationofthesmartdprocess,whichmonitorsthestatusofthediskonthehostOSofMX240,MX480,MX960,MX2010,andMX2020,isnotdeletedcompletelyevenafteryoudeletetheconfiguration.
Whenyouconfigurethesmartcheckfeature,smartdcontinuestouseparametersthatwereconfiguredpreviously.
Therefore,whileenablingsmartcheck,remembertoconfigurethethresholdvaluesforsmartdinsteadofretainingthedefaultvaluesthatwerepreviouslyconfigured.
FIFOhandlesofSSD-monitoringsmartdarenotclearedonthehostOSaftermultiplecommitsorchecks.
SmartdstopsworkingwhentheFIFOlimitreachesamaximum.
Therefore,werecommendthatyoudonotchangesmartdconfigurationstoooftenandperformSSDsmartchecksafterlongintervalsoftime.
WhentheFIFOlimitreachesamaximum,rebootthehostOS.
InadualRoutingEnginesystem,whileJunosOShasjuststartedbootinginthemasterRoutingEngine,thebackupRoutingEnginemightbepowered-offifitisremovedandreinserted.
Asaworkaround,pluginthebackupRoutingEngineaftermasterRoutingEngineisrunningstableandalltheFPCsareinoperationalstate.
IftheotherRoutingEngineCopyright2016,JuniperNetworks,Inc.
12JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesgetspowered-offaccidentally,issuethecommandsrequestchassiscbslotnumberpoweroffandrequestchassiscbslotnumberpowerontoturnthepowerontheRoutingEngine.
TheslotnumbersignifiestheRoutingEnginethathastobepowered-on.
DuringgracefulRoutingEngineswitchover(GRES)onMX240,MX480,MX960,MX2010,andMX2020,the802.
1xdaemoncrashesifthenumberoflogicalinterfacesconfiguredisequalto64,000ormore.
Afterthecrash,thedaemonrestartsandresumesnormaloperations.
RelatedDocumentationNewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownIssuesonpage13ResolvedIssuesonpage19DocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47KnownIssuesThissectionliststheknownissuesinhardwareandsoftwareinJunosOSRelease15.
1F3fortheMXSeriesandTSeries.
ForthemostcompleteandlatestinformationaboutknownJunosOSdefects,usetheJuniperNetworksonlineJunosProblemReportSearchapplication.
GeneralRoutingonpage14InterfacesandChassisonpage15Layer2Featuresonpage15MPLSonpage15NetworkManagementandMonitoringonpage16PlatformandInfrastructureonpage16RoutingProtocolsonpage17ServicesApplicationsonpage17SubscriberManagementandServices(MXSeries)onpage18UserInterfaceandConfigurationonpage1813Copyright2016,JuniperNetworks,Inc.
KnownIssuesGeneralRoutingAPEdevicerunningEVPNIRBwithanIGPconfiguredinaVRFassociatedwiththeEVPNinstancewillbeunabletoestablishanIGPadjacencywithaCEdeviceattachedtoaremotePE.
TheIGPinstancerunningintheVRFonthePEmaybeabletodiscovertheIGPinstancerunningontheremoteCEthroughbroadcastormulticasttraffic,butwillbeunabletosendunicasttrafficdirectlytotheremoteCE.
PR977945OnMXSeriesplatformwithIPsec,NATorRTMserviceconfiguredonMS-MPCorMS-MICinsertedinanXMchipbasedMPC,ifthepacketundergoesfragmentationoverthemultiservice(ms)interfaceandthelastfragmentisverysmall(thelastfragmentpacketlengthislessthan120bytes),theMPCmaycrashandrebootduetothepacketlengthcalculationdefect.
Asaworkaround,wecandisablefragmentationoverthemsinterface.
PR1025824IfprecisiontimersandtraceoptionsareenabledforBGP,thenbothmain-threadandprecisiontimerspthreadtrytorotatethesametracefilewithouttakinganylocks.
Asaresult,allthestatuscommandsforrpdandkrtmaybetimedout.
PR1044141OntheMXSeriesandTSerieswithBGPconfiguredtocarryflow-specificationroute,incaseofdeletingafiltertermandpolicer,thenaddingthesametermandpolicerback(itusuallyhappensinraceconditionwhenadding/deleting/addingtheflowroutes),sinceconfirmationfromdfwdforthedeletingpolicermightnotbereceivedbeforeattemptingtoaddthesamepolicer,therpdwouldskipsendinganaddoperationforittodfwd.
Asaresult,whenthefiltertermissenttodfwdandtellsittoattachtothepolicer,dfwdhadalreadydeletedthepolicer,andsincerpdskippedre-addingit,dfwdwillrejecttheattachfilterwithpolicernotfounderrorandrpdwillcrash.
PR1052887TerminatingasignalPPPoEsessionmightcauseallclientsinthisVLANtobedeleted.
PR1081361TherpdprocessmightcrashonbothmasterandbackupRoutingEngineswhenaroutinginstanceisdeletedfromconfigurationiftheroutinginstanceiscleanedupbeforetheinterfacedeleteisreceivedfromdevicecontroldaemon(dcd).
Thisisararetimingissue.
PR1083655OnXL-basedcardssuchasMPC5/MPC6,PPEthreadtimeouterrors(resultinginPPEtrapfiles)canbetriggeredwhentheFPCallocatesillegalmemoryspacefortheforwardingstateofrouteroperations.
-Incertaincases,thiscanresultinpacketlossdependingonhowmanypacketsusethisforwardingstate.
PR1100357Whenthenullpointerofjbufisaccessed(jbuf,thatis,amessagebufferisallocatedonlywhenthepacketisreadytoprocess.
ThebufferisfreedafterthepacketcompletesALGhandlingisaccessed),forexample,whenusingtheMicrosoftRemoteProcedureCall(MSRPC)(asobserved,issuemayalsohappenonSunMicrosystemsRPC)Application-levelgateway(ALG)withNAT(statefulfirewallisusedasapartoftheservicechain),ifthetrafficmatchingconfigureduniversaluniqueidentifier(UUID)isarrivedontheALG,themspmand(whichmanagestheMultiservicePIC)crashoccurs.
PR1100821Copyright2016,JuniperNetworks,Inc.
14JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesIffpcofflineconfigurationstatementisconfiguredafterthepresenceofnon-recoverablefaults,thenofflineactionwillnotbeperformed.
PR1103185Thecommands"showigmpinterface"and"showmldinterface"maysometimesresultinmemorycorruptionandgenerateacorefileofsmg-servicedaemon.
PR1120484InterfacesandChassisChapLocal-namedefaultsto8characters.
Shouldbe32.
PR996760ThefollowinglogcanbeseenonOTNcapablepicsaftereachcommit,whichindicatesincorrectstatsTLVsetting.
Noserviceimpactfound.
/kernel:ge-1/1/0:UnknownTLVtype356/kernel:ge-1/1/0:UnknownTLVtype361/kernel:ge-1/1/0:gettlvppfeid0xe-0/2/0:gettlvppfeid0xe-0/3/0:gettlvppfeid0xe-1/2/0:gettlvppfeid0xe-1/3/0:gettlvppfeid0xe-2/0/0:gettlvppfeid0xe-2/1/0:gettlvppfeid0xe-2/2/0:gettlvppfeid0xe-2/3/0:gettlvppfeid0xe-5/1/0:gettlvppfeid0xe-5/1/1:gettlvppfeid0xe-5/1/2:gettlvppfeid0xe-5/1/3:gettlvppfeid0xe-5/1/4:gettlvppfeid0xe-5/1/5:gettlvppfeid0xe-5/1/6:gettlvppfeid0xe-5/1/7:gettlvppfeid0xe-5/1/8:gettlvppfeid0xe-5/1/9:gettlvppfeid0.
PR1057594Duringscalinglogin/logoutdifferenttypesofsubscribers(e.
g.
17K)onLACrouter,theremightbesomeL2TPLACsubscribersstuckinterminatingstateandnevergetcleared,blockingnewsessionsfromestablishingonthesameinterface.
PR1094470OnPB-2OC12-ATM2-SMIRPIC,port0andport1areconfiguredwithclocksourceasexternal.
IfLossofsignal(LOS)isinsertedonport0,theport0willdown.
Theexpectedbehaviorisclockbeingusedfromport1.
Butinthiscase,port0downwillresultinport1flappingandreportingSONETphaselockloop(PLL)errors.
PR1098540Layer2FeaturesWhen"input-vlan-map"with"push"operationisenabledfordual-taggedinterfacesin"enhanced-ip"mode,thereisaprobabilitythatthebroadcast,unknownunicast,andmulticast(BUM)trafficmaybeblackholedonsomeofthechildinterfacesoftheegressAggregatedEthernet(AE)interfaces.
PR1078617WhenaDHCPrelayrequestisreceivedwiththebroadcastbitsetviaaVTEPinterface,theOFFERbackfromtheDHCPserverwillnotbesentbacktotheclientovertheVxLANinterface.
UnicastoffersoverVxLANandbothbroadcastandunicastoffersovernativeVLANinterfacesworkfine.
PR1126909MPLSRSVPgracefulrestartdoesnotfunctionforLSPsthathaveaforwardingadjacency(FA)label-switchedpath(LSP)asanexthop.
PR60256InJunosOSRelease14.
1andlater,the"load-balance-label-capability"configurationstatementisintroducedtoenabletheroutertopushandpoptheload-balancinglabel,whichcausesLDPandRSVPtoadvertisetheentropylabelTLVtoneighboringrouters.
TheMXSeriesandtheT4000havethecapabilityanditisreflectedintheirdefaultforwarding-optionsconfiguration.
However,thereisasoftwaredefectinthewaywhich15Copyright2016,JuniperNetworks,Inc.
KnownIssuesEntropyLabelCapability(ELC)TLVisencodedintheLDPlabelmappingmessage.
ItmightcausetheLDPsessionbetweenrouterstogodown.
PR1065338Whenlocalbandwidthaccountingforinactive/adaptivestandbypathfiguresthatthereisnotenoughbandwidthtofititinanalreadyfulllinkandbringsitdown,CSPFwillnotberetriedonthepathunlessthereissomechangeinTEdatabase.
PR1129602NetworkManagementandMonitoringWhenafirewallfilterhasoneormoretermswhichhaveMXSeries-onlymatchconditionoractions,suchfilterswillnotbelistedduringSNMPquery.
ThisbehaviorisseentypicallyafterRoutingEnginereboot/upgrade/master-shipswitch.
Restartingmib2dprocesswillcausetolearntheseMXSeries-onlyfilters:cli>restartmib-processAftermib2drestart,SNMPmibwalkoffirewallOIDswill:-listalltheOIDscorrespondingthisMXSeries-onlyfilter-countcorrectlyasconfiguredinthefilterNow,despitetheSNMPmibwalkforfirewallOIDslistsallOIDsandappropriatevalues,messageslogswillreportthefollowinglogsforeveryinterfacethathasthisMXSeries-onlyfilterapplied.
>Jul815:52:09galway-re0mib2d[4616]:%DAEMON-3-MIB2D_RTSLIB_READ_FAILURE:get_counter_list:failedinreadingcounternamesae33.
1009-i:288(Nosuchfileordirectory)>Jul815:52:09galway-re0mib2d[4616]:%DAEMON-3-MIB2D_RTSLIB_READ_FAILURE:get_counter_list:failedinreadingcounternamesae31.
1004-i:257(Nosuchfileordirectory)>Jul815:52:09galway-re0mib2d[4616]:%DAEMON-3-MIB2D_RTSLIB_READ_FAILURE:get_counter_list:failedinreadingcounternamesae33.
1010-i:289(Nosuchfileordirectory)>Jul815:52:09galway-re0mib2d[4616]:%DAEMON-3-MIB2D_RTSLIB_READ_FAILURE:get_counter_list:failedinreadingcounternamesae31.
1004-i:257(Nosuchfileordirectory)Theabove2issuesareaddressedinthisPRfix.
PR988566SNMPD'sResponsetimecalculationwasseenasaveryhigh(-)tivevalue,intheoutputof"showsnmpstatisticsextensive".
PR1112521PlatformandInfrastructureBadudpchecksumforincomingDHCPv6packetsasshowninmonitortrafficinterfaceoutput.
TheUDPpacketprocessingisnormal.
Thisisamonitortrafficissueassystemdecodeschecksum=0000.
PR948058OnMXSeries-basedplatform,whenusinginlineTwo-WayActiveMeasurementProtocol(TWAMP)server(theserveraddressistheinlineserviceinterfaceaddress),becausetheTWAMPservermayincorrectlycalculatethepacketchecksum,thepacketmaygetdroppedontheTWAMPclient.
PR1042132OnMXSeriesrouters,whenusingFPCwithfeatureinlinesamplingactivated,memorypartitionerrormessagesandmemoryleakmightbeobservedontheFPC.
Insomecases,thisissueonlyaffectssamplerouterecordsbutnotregularPacketForwardingEngineroutesornext-hops.
However,intheextremecase,itisalsopossibletocausethePacketForwardingEnginetofailtoinstallroutesintoforwardingnexthops,andhencetrafficdrops.
OnMXSeriesrouters,whenusingFPCs,orT4korTXP-3Drouters,whenusingFPC-3DFPCs,JunosOSRelease13.
3R5andRelease14.
1R4areexposed.
JunosOSRelease14.
2R1andlaterarenotexposed.
PR1071289Copyright2016,JuniperNetworks,Inc.
16JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesLMEMisaninternalmemoryinLU/XLASICchip.
IthasprivateandsharedregionsforPacketProcessingEngines.
LMEMdataerrorsareveryrareeventscausedbyenvironmentalfactors(thisisnotcreatedbysoftware).
Duetoasoftwaredefect,anerrorinthesharedLMEMregionwillresultincorruptionofcriticaldatastructuresofPacketProcessingEnginesthatcausesunpredictablecommunicationofLU/XLASICchipwithMQ/XMASICchip.
TheseeventswillcorruptthestateinMQ/XMandleadtoaMQ/XMwedge.
TheMQ/XMwedgewouldcausefabricblackholeandfinallyrebootthelinecard.
PR1082932OnMXSeries-basedplatform,whenthetypeoftheIPv6trafficisnon-TCPornon-UDP(forexample,nextheaderfieldisGREorNoNextHeaderforIPv6),ifthetrafficrateishigh(forinstance,higherthan3.
5Mpps),thepacketre-orderingmayoccur.
PR1098776Afterchanginganoutervlan-tags,theiflisgettingprogrammedwithincorrectstpstate(discarding),sothetrafficisgettingdropped.
PR1121564RoutingProtocolsContinuoussoftcore-dumpmaybeobservedduetobgp-path-selectioncode.
RPDforksachildandthechildassertstoproduceacore-dump.
Theproblemiswithroute-ordering.
Anditisauto-correctedaftercollectingthissoft-assert-coredump,withoutanyimpacttotraffic/service.
PR815146Inrarecases,rpdmaywriteacorefilewithsignature"rt_notbest_sanity:Pathselectionfailureon.
.
.
"Thecoreis'soft',whichmeansthereshouldbenoimpacttotrafficorroutingprotocols.
PR946415TherearetwoissuesinthePR:(1)Inmulticastenvironment,incominginterfacelist(IIF)listhasonlyRPFinterface.
Designatedforwarder(DF)winnersarenotaddedinthelistinbackupRoutingEngine.
(2)"Numberofdownstreaminterfaces"inshowpimjoinextensiveisnotaccountingPseudo-VXLANinterface.
PR1082362WhentheIS-ISconfigurationhasbeenremoved,theIS-ISLSDBcontentsgetflushed.
Ifatthesametimeofthisdeletionprocess,thereisanSPFexecution(thatis,trytoaccessthedatastructuresatsametimewhen/afractionofsecondsafterfreeingitscontent),routingprotocolprocess(rpd)crashoccurs.
PR1103631ServicesApplicationsThecauseofthekmdcrashisnotknown.
ThisisnotduetoSA(SecurityAssociations)memorycorruption.
ThecodelookslikeSAisgettingfreedwithoutclearingthetableentry.
PR1036023IntheNATenvironment,thejnxNatSrcPoolNameOIDisnotimplementedinjnxSrcNatStatsTable.
PR1039112InsomecasesafterunifiedISSUupgrade/GRESswitch/jl2tpdrestart,ifthesubscriberisterminatedduringtheunifiedISSU/GRES/restartprocess,jl2tpdmaygenerateacorefile.
PR110944717Copyright2016,JuniperNetworks,Inc.
KnownIssuesSubscriberManagementandServices(MXSeries)Insubscribermanagementenvironment,subscriberlogin/logoutcausesmultipledaemonstointeractviaInter-ProcessCommunication(IPC).
A32-bitcounter"Currenttime"isusedinternallyforthistypeofcommunicationtocollectstatslikeelapsedtime.
Theerrorlogmessage,suchas"invalidcurrent(31902492),baseline(4287968879),time(0)",mightbeobservedwhen"Currenttime"isoverflowingandholdinganinvalidtime.
PR1079507Insubscribermanagementenvironmentwiththreeormoreradius-serversconnectedtoanMXSeriesrouter,whenAAAsendsarequesttooneradius-server,ifthatparticularrequestandallretriestimeout,AAArecordsthetime.
Forthenextrequest,AAAincorrectlyusestherecordedtimeandmarksthattheradius-serverdownevenbeforetryingtosendouttherequest.
PR1091157UserInterfaceandConfigurationUserneedstowaituntilthepageiscompletelyloadedbeforenavigatingawayfromthecurrentpage.
PR567756UsingtheInternetExplorer7browser,whiledeletingauserfromtheConfigure>SystemProperties>UserManagement>UserspageontheJ-Webinterface,thesystemisnotshowingwarningmessage,whereasintheFirefoxbrowsererrormessagesareshown.
PR595932IfyouaccesstheJ-WebinterfaceusingtheMicrosoftInternetWebbrowserversion7,ontheBGPConfigurationpage(Configure>Routing>BGP),allflagsmightbeshownintheConfiguredFlagslist(intheEditGlobalSettingswindow,ontheTraceOptionstab)eventhoughtheflagsarenotconfigured.
Asaworkaround,usetheMozillaFirefoxWebbrowser.
PR603669OntheJ-Webinterface,nexthopcolumninMonitor>Routing>RouteInformationdisplaysonlytheinterfaceaddressandthecorrespondingIPaddressismissing.
Thetitleofthefirstcolumndisplays"staticrouteaddress"insteadof"DestinationAddress.
"PR684552OntheJ-Webinterface,Configure>Routing>OSPF>Add>InterfaceTabisshowingonlythefollowingthreeinterfacesbydefault:-pfh-0/0/0.
16383-lo0.
0-lo0.
16385Toovercomethisissueandtoconfigurethedesiredinterfacestoassociatedospfarea-range,performthefollowingoperationontheCLI:-setprotocolsospfarea10.
1.
2.
5area-range12.
25.
0.
0/16-setprotocolsospfarea10.
1.
2.
5interfacefe-0/3/1.
PR814171Whenentering"restartr"incompletecommandinCLI,eventhoughtherearemultipleoptionsavailable,command"restartrouting"isexecutedfinally.
Itshouldthrowanerrorlike"error:invaliddaemon:r".
PR1075746RelatedDocumentationNewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10ResolvedIssuesonpage19Copyright2016,JuniperNetworks,Inc.
18JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesDocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47ResolvedIssuesThissectionliststheissuesfixedinJunosOSRelease15.
1F3fortheMXSeriesandTSeries.
ForthemostcompleteandlatestinformationaboutknownJunosOSdefects,usetheJuniperNetworksonlineJunosProblemReportSearchapplication.
ResolvedIssues:15.
1F3onpage19ResolvedIssues:15.
1F2onpage28ResolvedIssues:15.
1F3GeneralRoutingonpage19Infrastructureonpage23InterfacesandChassisonpage24Layer2Featuresonpage24MPLSonpage25NetworkManagementandMonitoringonpage25PlatformandInfrastructureonpage25RoutingProtocolsonpage28SoftwareInstallationandUpgradeonpage28VPNsonpage28GeneralRoutingInMXVirtualChassis(MX-VC)environment,iftheprivatelocalnexthopsandroutespointingtoprivatelocalnexthopsaresenttoPacketForwardingEnginefromthemasterRoutingEngineandnotsenttothebackupRoutingEngine,thenaRoutingEngineswitchoverhappens.
NowasthenewmasterRoutingEnginedoesnotknowaboutsuchnexthopsandroutes,theyarenotcleanedup.
WhenanexthopwithsameindexisaddedonnewmasterRoutingEngineandsenttoPacketForwardingEngine,thePacketForwardingEnginemightcrashduetoastalenexthop.
PR951420InaLayer3wholesaleconfiguration,DHCPv6advertisemessagesmightbesentoutwithsourceMACallzerosifthesubscriberisterminatedonthedemuxinterfaceinanon-defaultroutinginstance.
Forsubscribersondefaultinstance,thereisnosuchissueobserved.
PR972603Earliertheoutputof"showagentsensors|displayxml"usedtoshowsensordetailsandtheattachedserverandexport-profiledetailsatthesamelevelinxmloutput.
Thisisconfusingsincetherearemultiplesensordatalistedforthiscommandandallwillbeshownwithsameindentation.
Afterthischange,theoutputof"showagentsensors|displayxml"willbeshownasthefollowingwitheachtagcoveringasingle19Copyright2016,JuniperNetworks,Inc.
ResolvedIssuessensor'sxmldata.
root@Router#runshowagentsensors|displayxmlname-of-sensor-hereresource-pathscope-idresource-filter-namestreaming-server-namescope-idremote-addressremote-portexport-profile-namereporting-intervallocal-addresslocal-porttimeticksserver-export-formattransportcode-pointforwarding-class.
.
.
PR1037064UponBFDflappingonaggregateinterfaces,theLookupchip(XL)mightsendillegalpacketstothecenterchip(XMCHIP)andcompromisepacketforwardingandanFPCrestartisneededtorecoverfromthiscondition.
IfFabricpathsideisaffected,thefabrichealingprocesswillinitiatethisprocessautomaticallytorecoverfromsuchconditions.
OnlyMPC5EorMPC6Eareexposedtothisproblem.
PR1067234Copyright2016,JuniperNetworks,Inc.
20JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesWhenVMXisdeployed,initiallythereisnomanagementportconfiguration,soconfigurationneedstobeappliedbyserialconsole.
TheconsoleforVMXissetto9600baudrate.
Withthisrate,onlyasmallnumberofconfigurationlinescanbepastedatatime.
PR1068152ICMPecho_replytrafficwithapplicationslikeIPsecwillnotworkwiththeMS-MICandMS-MPCcardsinanasymmetrictrafficenvironmentsincethesecardsemployastatefulfirewallbydefault.
ThepacketwillbedroppedattheStatefulFirewallsinceitseesanICMPReplythathasnomatchingsession.
PR1072180RemnantroutesseeninoldmasterRoutingEngineafterRoutingEngineswitchoverinnonGRESscenario.
PR1075404InatwomemberMXSeriesVirtualChassis(MXVC)environment,when"setvirtual-chassisno-split-detection"isconfigured,ifsplitmasterconditionhappens,whichiscausedbysplitevents(i.
e.
lossofalladjacenciesbylinkfailure,FPCrestarts,chassispower-down,RoutingEnginereboots,etc),thenoncetheVCPadjacencyisformedagain,thecurrentdesigncouldnotdeterminethebestchassistowintheprotocolmastershipelectionproperly.
Instead,onlythefinalelectionstep(thatis,choosethememberdevicewiththelowestMACaddress)isusedtoelectthemasterdevice(protocolmasteroftheVC,orVC-M).
PR1090388TheOpenSSLprojecthaspublishedasetofsecurityadvisoriesforvulnerabilitiesresolvedintheOpenSSLlibraryinJuneandJuly2015.
JunosOSisaffectedbyoneormoreofthesevulnerabilities.
RefertoJSA10694formoreinformation.
PR1095598HighlatencymightbeobservedwhencontinuousIPv6pingsaresenttoVMXplatform.
PR1096403Whenrouteconvergenceoccurred,thenewgatewayaddressisnotupdatedcorrectlyininline-jflowroute-recordtable(route-recordtableisusedbysampling),andthesamplingtrafficforwardingmightbeaffected,butnormalroutingwouldbenotaffected.
PR1097408Someofthenewrevisions(forexample,REV30,REV31)oftheMICscannotcomeupwithNG-MPC2orNG-MPC3linecard.
WecanchecktheMICversionbyCLIcommand"showchassishardwaredetail|no-more".
root@user>showchassishardwaredetail|no-moreHardwareinventory:ItemVersionPartnumberSerialnumberDescription.
.
FPC2REV14750-054901CADJ3871MPC3ENGPQ&FlexQCPUREV11711-045719CADN5465RMPCPMBMIC0REV30750-028392CAEB92033D20x1GE(LAN)SFPPR1100073AfterJunosOSRelease13.
3R1,IPCMONinfrastructureisaddedtodebugIPCsbetweenPFEMANandtheRoutingEngine.
Whenconvergenceoccurs,stringprocessingofIPCMOMwilltakeaddedtime.
Thentheslowconvergencewillbeseen.
Itisaperformanceissue,anditisvisibleinscaledscenario(forexample,morethan100Kroutes).
Asaworkaround,executethecommand"setpfeipclogfilterclear"todisableIPCloggingonallFPCs.
PR1100851Inbroadbandedge(BBE)environments,forexample,iftheinterface-setiscreatedcorrespondingtoSVLAN,thenmultiplelogoutsandloginswillcreateanewinterface-setindex.
Whentheinterface-setindexrangegoesabove65535,executingCLIcommand"showinterfacesinterface-setqueueegress"willcause100%CPUusage.
Asa21Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesworkaround,wecanusethespecifiedinterface-setnameinsteadofusingthewildcard.
PR1101648Non-queuingMPC5Emightcrashcontinuouslyifrate-limitundertransmit-rateforschedulerisapplied.
Asaworkaround,donotconfigurerate-limitandusefirewallpolicerforforwarding-classinstead.
MPC5EQisnotexposed.
PR1104495AvulnerabilityinOpenSSHmayallowaremotenetworkbasedattackertoeffectivelybypassrestrictionsonnumberofauthenticationattempts,asdefinedbyMaxAuthTriessettingsonJunos.
Thismayenablebruteforcepasswordattackstogainaccesstothedevice.
Background:ThePAM(PluggableAuthenticationModules)libraryprovidesaflexibleframeworkforuserauthenticationandsessionsetup/teardown.
Itisusednotonlyinthebasesystem,butalsobyalargenumberofthird-partyapplications.
Variousauthenticationmethods(UNIX,LDAP,Kerberosetc.
)areimplementedinmoduleswhichareloadedandexecutedaccordingtopredefined,namedpolicies.
Thesepoliciesaredefinedin/etc/pam.
conf,/etc/pam.
d/,/usr/local/etc/pam.
confor/usr/local/etc/pam.
d/.
ThePAMAPIisadefactoindustrystandardwhichhasbeenimplementedbyseveralparties.
FreeBSDusestheOpenPAMimplementation.
ThisissueisassignedCVE-2015-5600.
PR1106752OnMXSeriesplatformwith"subscriber-management"enabled,whilehigh-scaledsubscribers(forexample,126Kdual-stackDHCPv4/v6subscribersoverVLANdemux)login/logoutathighrate,MPCsandMICsthatholdsubscribersmightcrashafterthebbe-smgdprocessrestarts.
PR1109280InthescenariothatthepowergetsremovedfromtheMS-MPC,buttheRoutingEngineisstillonline(forexample,onMX960platformwithhigh-capacitypowersuppliesthatsplitintotwoseparatepowerzones,whenthepowerzonefortheMS-MPClinecardlosespowerbyswitchingoffthePEMthatsupportstheMS-MPCsituatedslot),ifthepowergoesback(forexample,switchonthePEM),theMS-MPCmightbeseenas"Unresponsive"(checkedviaCLIcommand"showchassisfpc")andnotcomingupbackonlineduetofailureofreadingmemory.
PR1112716OnMX-VCwithheartbeatconnection,ifitisinascaledsubscribersenvironment,whenpowerdownbothVCMRoutingEngines,theremightbeadelay(minutes)forbackupchassistobemasterandduringwhichtime,trafficblackholemightbeseen.
PR1115026Nodecrementttldoesnotworkforincomingv6trafficovermplsipv4core.
PR1115203ForMPC6EwithCFP2,therewasaraceconditionbetweentheInterruptserviceroutineandtheperiodic,asaresultinterfaceup/downwillnothappenforlaseroff/on.
PR1115989OnandMXSeriesplatforms,the10GTunableSFP/SFP+cannotbetunedinJunosOSRelease15.
1R2.
PR1117242TherpdprocessmightcrashwhenexecutingCLIcommand"showevpndatabase"withthecombinationof"vlan-id"and"mac-address".
PR1119301Copyright2016,JuniperNetworks,Inc.
22JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesInfrastructureOnlythefollowingdirectoriesandfilesarepreservedwhenupgradingfromabuildpriortoRelease15.
1toRelease15.
1(FreeBSD10).
config//etc/localtime/var/db//var/etc/master.
passwd/var/etc/inetd.
conf/var/etc/pam.
conf/var/etc/resolv.
conf/var/etc/syslog.
conf/var/etc/localtime/var/etc/exports/var/etc/extensions.
allow/var/preserve//var/tmp/baseline-config.
conf/var/tmp/preinstall_boot_loader.
confAnythingelsenotlistedaboveisdeleted/formattedduringtheupgradetothefreebsd10versionofJunosOS.
PR959012When"showversiondetail"CLIcommandhasbeenexecuted,itwillcallaseparategstatdprocesswithparameter"-vvX".
Becausethegstatdcouldnotrecognizetheseparameters,itwillrunoncewithoutanyparameterthenexit.
Inresultof"showversiondetail",followinginformationcouldbeseen:user@mx960>showversiondetailHostname:mx960Model:mx960Junos:13.
3R6-S3JUNOSBaseOSboot[13.
3R6-S3]JUNOSBaseOSSoftwareSuite[13.
3R6-S3]JUNOSKernelSoftwareSuite[13.
3R6-S3]JUNOSCryptoSoftwareSuite[13.
3R6-S3]file:illegaloption--vusage:gstatd[-N]gstatd:illegaloption--vusage:gstatd[-N]Atthesametime,loglineslikefollowingmightberecordedinsyslog:Aug2517:43:35mx960file:gstatdisstarting.
Aug2517:43:35mx960file:re-initialisinggstatdAug2517:43:35mx960mgd[14304]:UI_CHILD_START:Startingchild'/usr/sbin/gstatd'Aug2517:43:35mx960gstatd:gstatdisstarting.
Aug2517:43:35mx960gstatd:re-initialisinggstatdAug2517:43:35mx960gstatd:Monitoringad2Aug2517:43:35mx960gstatd:switchoverenabledAug2517:43:35mx960gstatd:readthreshold=1000.
00Aug2517:43:35mx960gstatd:writethreshold=1000.
00Aug2517:43:35mx960gstatd:samplinginterval=1Aug2517:43:35mx960gstatd:averagedover=30Aug2517:43:35mx960mgd[14304]:UI_CHILD_STATUS:Cleanupchild'/usr/sbin/gstatd',PID14363,status0x4000Aug2517:43:35mx960mgd[14304]:UI_CHILD_EXITED:Childexited:PID14363,status64,command'/usr/sbin/gstatd'PR1078702OnMXSeriesplatformwithJunosOSRelease15.
1R1orabove,whileacoredumpisinprogress,ifwetrytoaccessthedumpdirectory,duetothedeadlockdefect,thesystemmighthangandcrash.
Asaworkaround,weshouldnotaccessthe"/var/crash"directorytillthecoredumpiscomplete.
PR1087082OndualRoutingEngineplatform,ifGRESisconfigured(triggeredby"on-disk-failure"),whenadiskI/OfailureoccursonthemasterRoutingEngineduetohardwareissue(forexample,SSDfailure),thegracefulRoutingEngineswitchovermightnotbetriggeredimmediatelyafterinitialIOfailurehasbeendetected.
Asaresult,RoutingEnginemightenterastateinwhichitrespondstolocalpingsandinterfacesremainup,butnootherprocessesareresponding.
PR1102978Withscaledconfigurationortherearememoryleaks,ifthevirtualmemoryisrunningverylow,thekernelmightcrashandthedevicewillgoindbpromptcontinuouslyduetoarecursionissue.
PR1117548showroutevpn-localizationcommanddoesnotshowanyoutput,butifxmlformatrequestedthenxmloutputofthesamecommandworks.
PR112528023Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesInterfacesandChassisOnMXSeriesrouter,thephysicalorlogicalinterfaces(ifd/ifl)mightbecreatedandmarkedUPbeforeresettingFPCs'fabricplanesarebroughtupandreadytoforwardtraffic.
Asaresult,trafficmightbeblack-holedduringthetimewindow.
Thiswindowoftrafficblack-holeisparticularlongifthechassisisheavilypopulatedwithline-cards,forexample,therouterhaslargescaleofconfiguration(routesorsubscribers),andcoupledwithalotofFPCreset,suchasuponanodepowerup/reset.
PR918324WhenissuingaCFMLTRfromCE,linkstatereply,receivedfromMXSeries,actingasMHFdoesnotcontainReplyEgressTLVifingressandingresslogicalinterfacearelocatedonthesameIFD.
PR1044589Duringsubscriberlogin/logoutthefollowingerrorlogmightoccuronthedeviceconfiguredwithGRES/NSR.
/kernel:if_process_obj_index:ZerolengthTLV!
/kernel:if_pfe:ZerolengthTLV(pp0.
1073751222).
PR1058958ForJunosOSRelease13.
3R1andlaterreleases,aftermultiple(e.
g.
26)iterationsofgracefulRoutingEngineswitchover(GRES),theTNPaddressofmanagementinterfacemightbedeletedincorrectlyduringswitchover,whichleadstoallFPCstobeoffline.
PR1060764Trapmessagesdonotgetloggedonlogicalinterface(ifl)afterdeleting"no-traps"configurationstatement,inspiteofsettingexplicit"traps".
PR1087913OnMX240orMX480platformwithatleasttwoDCmodules(PN:740-027736)equipped,whenshuttingdownoneofthePEMsandthenturningitonagain,evenwhenthePEMisfunctioning,the"PEMFanFail"alarmmightbeobservedonthedeviceduetosoftwarelogicbug.
ThereisnowaytocleartheALARM_REASON_PS_FAN_FAILforI2C_ID_ENH_CALYPSO_DC_PEMonceithasbeenraised.
PR1106998OnallJunosOSplatforms,ifthe"HDD/var"slice(forexample,"/dev/ad1s1f"dependingonthetypeofRoutingEngine)isnotmounted(forexample,labelmissing,filesystemcorruptedbeyondrepair,HDD/SDDisremovedfromthebootlist,etc),thesystemmaybuildemergency"/var/",however,noalarmortrapisgeneratedduetotheincorrectoperationoftheata-controller.
Althoughthebootmessagesmaypresentthelogs,itmaynotbesufficientenoughtoidentifytheissuebeforeencounteringotherproblems(forexample,JunosOSupgradefailureandtheRoutingEnginemayhanginarecoveryshell).
Inaddition,asamethodtocheckwhereRoutingEngineisrunningfrom,amanualcheckcouldbedoneasbelow,user@re0>showsystemstorage|match"/var$"/dev/ad2s1f34G18G13G57%/varshowsystemstorage|match"/var$"PR1112580Layer2FeaturesWithDynamicHostConfigurationProtocol(DHCP)maintainsubscriberfeatureenabled,whenthesubscriber'sincominginterfaceindexischanged,forexample,theinterfacesgoawayandcomebackafterchangingtheMTUconfigurationofinterface,theexistingsubscribersmaygetdroppedandnewsubscribersfailinconnection.
PR1059999ForPVSTP/VSTPprotocols,whenMXSeriesrouterinter-operateswithCiscodevice,duetotheincompatibleBPDUformat(thereareadditional8BytesaftertherequiredCopyright2016,JuniperNetworks,Inc.
24JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesPVIDTLVintheBPDUforCiscodevice),theMXSeriesroutermightdroptheseBPDUs.
PR1120688MPLSOndualRoutingEngineplatformwithGRES,thekernelsynchronizationprocess(ksyncd)maycrashonthebackupRoutingEnginewhenaddingofroutepointingtoindirectnexthoponsystem.
PR1102724FromJunosOSRelease13.
2R1andlater,inMPLSL3VPNscenario,when"l3vpn-composite-nexthop"configurationstatementisenabledonaPErouterandaninterfacestyleservicesetisattachedtotheingressinterface,theL3VPNpacketswiththeMPLSlabelswillbesenttotheservicecardanddropped.
Asaworkaround,weshoulddisable"l3vpn-composite-nexthop".
PR1109948If"optimize-timer"isconfiguredunderP2MPbranchLSP,thisbranchLSPwillnotbere-establishediflinkflaponegressnode.
If"optimize-timer"isconfiguredatprotocols/mplslevel,issuecouldbeavoided.
PR1113634NetworkManagementandMonitoringInrarecases,whenthemib2dprocessattemptsconnectionwiththesnmpdprocessandtherearependingrequestswaitingtobefinished,themib2dprocessmightcrashandtheCPUutilizationishigharoundthesametimeasthecrashhappens.
PR1076643WhiletherouterisrebootingandSNMPpollingisnotstopped,SNMPrequestsmightlandonmib2dprocessbeforeRoutingEngineprotocolmastershipisresolved,causingthemib2dprocesscrash.
PR1114001PlatformandInfrastructureIntheNetworkTimeProtocol(NTP)configuration,ifthespecifiedsourceipaddressisnotincurrentrouting-instance,therouterwilluseprimaryaddressofinterface(whichwillbeusedtosendpacket)assourceaddress,ClientrouterswilltreattheNTPpacketsasincorrectpackets,andthenNTPsynchronizationfails.
PR872609OnMXSeriesbasedlinecard,whenGREkeepalivepacketsarereceivedonaPacketForwardingEnginethatisdifferentfromthetunnelinterfacehosted,thekeepalivemessagewillapplythefirewallfilterconfiguredondefaultinstanceloopbackinterface.
PR934654Whenthe'enhanced-hash-keyservices-loadbalancing'featureisusedbyMXSeriesbasedlinecards,loadbalancingflowsacrossmultipleservicePICsviathesource-addressacrossdoesnotworkwheninternalBGP(IBGP)isusedtosteertraffictotheinsideservice-interface.
Forexampletheoperatorwillseeonthestatefulfirewallthatthesamesource-addresshasflowsacrossmultipleserviceinterfaces.
PR1034770IfwithbothMPC/MSDPCandothertypeofDPCsequipped,forlocalswitchingatmeshgrouplevel,splithorizononPWinterfaceswillnotworkandthiswouldcausepacketstoloopbacktosamePWinterface.
PR1084130TheMIBcounteror"showpfestatisticstraffic"showsjunkPPSandinvalidtotaltrafficoutputcounter.
PR108451525Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesOnMXSeriesplatform,ifingress"multicast-replication"isconfigured,thethroughputofthemulticastmaygetreducedduetounnecessarythreadsduringPacketForwardingEngineoperation.
Inaddition,onlytheperformanceofmulticasttrafficmaygetinfluenced(someofthemulticastpacketsmaygetdroppedonthePacketForwardingEngine)bytheissue.
ThisPRhasfixed/enhancedtheperformance.
NowtheperformancelimitshouldonlybecappedbyfabricbandwidthiningressPacketForwardingEngine.
Inaddition,beforethisfix,therewasalimitationthatVPLS/Bridgingcan'trunwithingress-replicationfeatureasitsBUMtrafficcan'tbehandledbyingress-replicationfeature.
ThisPRremovedthatlimitationaswell.
NowBUMtrafficforVPLS/Bridgingisfollowingnormalmulticastreplicationpathevenwithingress-replicationfeature.
PR1089489In64-bitJunosOSenvironment,theRepresentationalStateTransfer(REST)APIfailstostartwhenconfiguredwith"setsystemservicesrest.
.
.
".
PR1097266OnMXSeriesplatform,ifingress"multicast-replication"isconfigured,thethroughputofthemulticastmaygetreducedduetounnecessarythreadsduringPacketForwardingEngineoperation.
Inaddition,onlytheperformanceofmulticasttrafficmaygetinfluenced(someofthemulticastpacketsmaygetdroppedonthePacketForwardingEngine)bytheissue.
PR1098489OnMXSeries-basedplatform,beforecreatinganewunilistnexthop,thereisachecktoseeifthereareatleast512kDoubleWords(DWs)free.
So,eventheattemptingnexthoprequiresonlyasmallamountofmemory(forexample,showconfigurationsystemradius-server.
.
source-address10.
1.
1.
1;root@user>showchassishardwaredetail|no-moreHardwareinventory:ItemVersionPartnumberSerialnumberDescription.
.
FPC2REV14750-054901CADJ3871MPC3ENGPQ&FlexQCPUREV11711-045719CADN5465RMPCPMBMIC0REV30750-028392CAEB92033D20x1GE(LAN)SFPFanTray0REV05740-014971TP5127FanTrayFanTray1REV05740-014971TP5103FanTray.
PR1100073Non-queuingMPC5Emightcrashcontinuouslyifrate-limitundertransmit-rateforschedulerisapplied.
Asaworkaround,donotconfigurerate-limitandusefirewallpolicerforforwarding-classinstead.
MPC5EQisnotexposed.
PR1104495InfrastructureArebootisneededif"chassisnetworkservicesenhanced-ip"isconfiguredonMXSeriesUniversalEdge3DRoutersoronT4000Routerswithtype5FPCs.
Withoutthereboot,performingunifiedISSUmightcausethenewmasterRoutingEnginetocrashandgotothedb>prompt.
PR1013262Theissuewasthegstatdfor64bitwasnotgettingtothecorrectpathinthecodeandduetothatgstatprocesswasfailingtostart.
PR1074084InterfacesandChassisOndualRoutingEnginesplatforms,asaHighAvailability(HA)method,masterRoutingEngineshouldrelinquishmastershipwhenbothRoutingEngine-to-PacketForwardingEngineandRoutingEngine-to-other-RoutingEngineinterfacesaredown(thiscanbeachievedonlywhenGRESisenabled).
ButnowondualRoutingEnginesplatformsexceptM10iandM20,masterRoutingEnginedoesnotrelinquishthemastershipinsuchconditions,evenexecutingCLI"requestchassisrouting-enginemasteracquire"onbackupRoutingEnginecannothelp.
Insuchconditions,noFPCcanbeonlinewithouttheconnectiontomasterRoutingEngine.
Withthefix,thebackupRoutingEnginewilltakeupthemastershipautomaticallyifboththeinternallinkinterfacesaredown.
PR878227OnEthernetPICswithlongerholddowntimerconfigured,flappinginterfacewithintheholdtimemightcausetrafficlosslongerthantheholdperiod.
PR1040229WhenconfiguringtheVirtualRouterRedundancyProtocol(VRRP)onaninterfacewhichisincludedinarouting-instanceviaapplyinggroupssetting,ifchangesaremadetotheinterface,theVRRPprocess(vrrpd)memoryleakmightbeobservedonthedevice.
PR104900731Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesInVirtualRouterRedundancyProtocol(VRRP)environment,afterrestartingtheFPC,duetotheRouterAdvertisement(RA)deletionisbeingincorrectlysenttoroutingprotocolprocess(rpd)byVRRPprocess,theICMPv6maynotbeactivatedonthecorrespondinginterfacesontherouterthatisactingasthemaster.
Inthiscase,noRAmessagecouldbesentout.
PR1051227The"showchassisnetwork-services"commandmightnotshowthecorrectconfiguredvaluewhenexecutedonthebackupRoutingEngine.
ThiscommandshouldonlybeexecutedonthemasterRoutingEngine.
PR1054915OnDPConlychassis,aftersoftwareupgradeornotgracefulRoutingEngineswitchover,EthernetOAMrelatedLAGbundlesmightnotcomeupduetotheLinkFaultManagement(LFM)packetsarriveonAEinterfaceinsteadofphysicallinkinterface.
PR1054922Tworedundantlogicaltunnels(rlt)interfacesareconfiguredwithstatement"per-unit-mac-disable"enabled.
Afterconfiguringthesecondone,thefirstrltinterfacegoesdown.
rlt0{logical-tunnel-options{per-unit-mac-disable;PR1055005TheCLIdescriptionofthenew100-GigabitMetroDWDMOTNPIC(PTX-2-100G-WDM-M)isdifferentfromtheexisting100-GigabitDWDMOTNPIC(P1-PTX-2-100G-WDM).
The100-GigabitMetroDWDMOTNPIC'stransceiverisidentifiedasOTN-100G-MintheoutputfromtheshowchassishardwareCLIcommandandthecabletypeisidentifiedas100GMETROintheoutputfromtheshowchassispicCLIcommand.
PR1055325Thereisamismatchinmacstatistics,fewframesgounaccounted.
Thisisaday-1issuewiththesoftwarefetchingofmacstatistics.
Thesnapandclearbitsweresettogetheronpm3393chipdriversoftware,soitusedtohappenthatevenbeforethecopyofstatstoshadowregistershappened,clearwashappeningwhichusedtogounaccounted.
Nowrollovermechanismhasbeenimplementedandtestedfor2continuousdaysandeverythingisfine.
PR1056232When"setchassislcc0offline"isusedonSCCandcommitted,theconfigurationgetssyncedonLCC.
However,when"deletechassislcc0offline"isusedonSCC,weneedtodocommittwotimesonSCCinordertosynctheconfigurationonLCCbeingbroughtonline.
PR1058994Inmultichassislinkaggregationgroups(MC-LAGs)environment,theMC-LAGpeershavetheMACandportinformationandcanforwardthetrafficappropriately.
IfasingleVLANonICLinterfaceismodifiedtoadifferentVLAN,andthentheadministratorrollsbacktheVLANconfigurationtotheoriginalone,theremoteMACmightbestuckinthe"Pending"stateandnotbeinstalledinthebridgeMAC-table,whichcausesthetrafficforwardingtobeaffected.
PR1059453WhentheMaximumReceiveUnit(mru)valueisnotsetundergroup-profileppp-optionshierarchy,adefaultvalue(1492)willbeused.
Ifmruvalueisset,thenewvaluewilltakeeffect.
Butiftheconfiguredmruvalueisdeletedfromthegroupprofile,themruvalueremainstheconfiguredoneandfailstofallbacktothedefaultone.
PR1059720OnMXSeriesrouters,INETMTU(PPPpayloadMTU,thatisIPheaderplusdataexcludinganyL2overhead)isbeingsettolowestMRUofeitherMX(localdevice)orpeer.
ThisbehaviorisnotinlinewithERXbehavior,whichissettomin(localMTU,peerCopyright2016,JuniperNetworks,Inc.
32JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesMRU).
Thismightcausethepacketdropsinthecustomernetworkinthedownstreampath.
PR1061155Inconnectivityfaultmanagement(CFM)environment,ifanAEinterfaceisincludedinMEPinterfaces,andifthereisanotherAEinterfaceconfiguredwithoutanychildlink(eventhisAEisnotparticipatinginOAM),theCFMsessionsmightnotcomeupafterRoutingEnginerestartorswitchover.
PR1063962Errormessageiscontinuouslyloggedeverysecondafteraparticularcopper-SFP[P/N:740-013111]ispluggedintoadisabledportonMIC.
*****errormessage****mic_sfp_phy_program_phy:ge-FailtoinitPHYlinkmic_periodic_raw:MIC(*/*)-ErrorinPHYperiodicfunctionPQ3_IIC(WR):notargetackonbyte0(waitspins2)PQ3_IIC(WR):I/Oerror(i2c_stat=0xa3,i2c_ctl[1]=0xb0,bus_addr=0x56)mic_i2c_reg_set-writefailswithbus86reg29mic_sfp_phy_write:MIC(*/*)-FailedtowriteSFPPHYlink0,loc29mic_sfp_phy_mdio_sgmii_lnk_op:Failedtowrite:ifd=140ge-*/*/*,phy_addr:0,phy_reg:29ala88e1111_reg_write:Failed(20)towriteregister:phy_addr0x0,reg0x1dFailsinfunctionala88e1111_link_initPR1066951Toensurethattherouterorswitchisreachableformanagementpurposeswhileitbootsoriftheroutingprotocolprocessfailstostartproperly,wecanconfigureabackuprouter,whichisarouterthatisdirectlyconnectedtothelocalrouterorswitch(thatis,onthesamesubnet)throughitsprivatemanagementinterface(forexample,fxp0orme0).
WhenabackuprouterrunningIPv6andastaticroutetoreachthemanagementnetworkareconfigured,someinvalidIPv6routesareaddedtodefaultforwarding-tableonthemasterorthebackupRoutingEngine.
PR1100981Layer2FeaturesBGPpeerconfiguredbetweentworoutersoverlt(logicaltunnel)interface,ifdeactivatingandactivatingscaledconfigurationafewtimes,inrarecondition,theltinterfacemightrejectalltheARPreplypackets,andhencetheARPresolutiondoesnothappenoverthisinterface.
Thus,theunicastroutesarenotinthecorrectstates,andpingtosuchanltinterfacewillfail.
PR1059662LACPpartnersystemIDisshownincorrectlywhentheAEmemberlinkisconnectedtoadifferentdevice,whichmightmisguidewhiletroubleshootingtheLAGissues.
PR1075436TheEnhancedLAGfeatureisenabledinnetwork-serviceenhanced-ipmode,butitisnotsupportedinenhanced-ethernetmode.
PR1087982MPLSTheentropylabelvalueallocatedattimesfallsinthereservedmplslabelrange(0-15).
Thelabelvalueiscalculatedbasedonloadbalancinginformationandhenceonlycertainmplsflowsmayencounterthisissue.
PR1014263WithBGPlabeled-unicastegressprotectionenabledinaLayer3VPN,theprotectednodeadvertisesprimaryBGPlabeledunicastroutesthatneedprotection.
Whenthereisnext-hopchangeforalabeledroute,forexample,deactivating/activatingegress-protectionconfigurationstatementorroutechurn,thememorymightbeexhaustedwhichleadstotherpdprocesscrash.
PR106184033Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesWhenfast-reroute,node-link-protection,orlink-protectionisconfigured,ifaSharedRiskLinkGroup(SRLG)isassociatedwithalinkusedbyanLSPingressingatarouter,thenondeletingtheSRLGconfigurationfromtherouter,theSRLGentrystillstaysintheSRLGtableevenafterthere-optimizationofthisLSP.
PR1061988WhenCSPFcomputesthepathfornode-protectedbypass,itconsidersonlytheSRLGgroupconfiguredonnext-hopinterfacealongtheprimarypath.
Howeveritdoesn'tconsidertheSRLGgrouponnext-to-next-hopinterfacetoadequatelyprovidediversepathbetweenprimaryandnode-protectedbypass.
PR1068197WhenaprimaryLSPgetsre-routedduetobettermetric,Link/NodeprotectionforthisLSPisexpectedtocomeupwithin7secondsprovidedthebypass-lspprotectingthenext-hoplink/nodeisalreadyavailable.
Howeverinsomecornercases,theLink/Nodeprotectionforre-routedprimaryLSPwillnotcomeupwithin7secondsevenwithbypass-lspavailability.
ThePRfixesthisissueandreducesthedelayofassociatingbypass-lspwithprimary-lspfrom7secondsto2seconds.
PR1072781InMPLSenvironment,ifoneofminimum-signaling-bandwidth/merging-bandwidth/splitting-bandwidth/maximum-signaling-bandwidthisconfigured,orderivedasvalue0,theroutingprotocolprocess(rpd)maycrashwhenlsp-splittingorlsp-merging(forexample,whenthetrafficcomesup/down)occurs.
Asaworkaround,duetothelogicoftheconfigurationstatement,noneofthefollowingconfigurationstatementscouldbeconfiguredorderivedaszero,-merging-bandwidth-minimum-signaling-bandwidth-splitting-bandwidth-maximum-signaling-bandwidthPR1074472NetworkManagementandMonitoringSNMPqueriesforLAGMIBtableswhileLAGchildinterfaceisflappingmaycausemib2dtogrowinsizeandeventuallycrashwithacorefile.
Mib2dwillrestartandrecoverbyitself.
PR1062177ThetextstringoftheSNMPobject"system.
sysDescr.
0"doesnotincludetheJunosOSversionofthedeviceanddisplaystheversionoftheFreeBSDkernelrunningontheRoutingEngineinstead.
PR1073232PlatformandInfrastructureRecurringlocalmemory(LMEM)dataerrorsmaycauselookupchiponMXSerieswithFPCwedgeandeventuallyFPCcrash.
PR1033660Ifseveralaggregatesareconfiguredwithshared-bandwidth-policerandthoseaggregatessharethesamePacketForwardingEngineforchildmemberlinksandonememberlinksflaps,alltrafficmightgetpolicedanddropped.
Thetrafficdroppedmightnotbeonthebundlewhosechildmemberlinkflapped.
PR1035845DuetoadefectintheJunosOSsoftware,whenatelnetuserexperiencessomeundefinednetworkdisconnect,.
permand.
envfilesunder/var/runareleftbehind.
Thisscenariohappensonlyundercertainunknownungracefulnetworkdisconnects.
Whenconsiderablenumberof.
perm/.
envfilesgetaccumulatedunder/var/run,issueisseenwithtelnetusers,thattheyarenotabletoperformpermittedoperationsontherouter,post-login.
PR1047609Copyright2016,JuniperNetworks,Inc.
34JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesForaRoutingMatrix,ifdifferentRoutingEnginemodelsareusedonswitch-cardchassis(SCC)/switch-fabricchassis(SFC)andline-cardchassis(LCC)(forexample,RE-1600onSCC/SFCandRE-DUO-C1800onLCC),wheretheout-of-band(OoB)managementinterfacesarenameddifferently(forexample,fxp0onSCC/SFCRoutingEngineandem0onLCCRoutingEngine),thentheOoBmanagementinterfaceconfigurationforLCCRoutingEnginewillnotbepropagatedfromSCC/SFCRoutingEngineduringcommit.
PR1050743WithVLANmanipulationconfiguredforEthernetServices,incorrectframelengthmightbeusedforegresspolicingonMXSeriesrouterswithMPCs/MICs.
Currently,theframelengthcalculationisinconsistentfordifferenttraffictopology:1.
Incasetrafficcrossedthefabric,theframelengthpriortooutputVLANmanipulationisused;2.
Incaseoflocaltraffic,theframelengthpriortoinputVLANmanipulationisused.
ActuallythelengthafteroutputVLANmanipulationshouldalwaysbeused.
PR1064496Whenperformingunifiedin-servicesoftwareupgrade(ISSU)onMXSeriesrouterswithunsupportedMICs(forexample,"MIC-3D-8OC3OC12-4OC48")equipped,theMPCmightcrashduringthefield-replaceableunit(FRU)upgradeprocess.
Forexample,unifiedISSUissupportedonlybytheMICslistedhereonJunosOSRelease14.
2:MIC-3D-20GE-SFPMIC-3D-2XGE-XFPMIC-3D-4XGE-XFPMIC-3D-40GE-TXMIC-3D-8OC3-2OC12-ATMMIC3-3D-2X40GE-QSFPPMIC3-3D-10XGE-SFPPMIC3-3D-1X100GE-CXPMIC3-3D-1X100GE-CFP.
PR1065731Firewallfilterswhichhaveaprefix-actioncan'tbeconfiguredunder[editlogical-systemfirewallfamilyinet]becausethePacketForwardingEnginewon'tbeprogrammedforthefilter.
PR1067482Ifwithabout1MroutesonMXSeriesrouter,theremightbemorethan1second(about1.
3s)packetsdarkwindowduringunifiedISSU.
PR1070217VPLSfilterappliedunderforwarding-optionsmightdropVPLSframeunexpectedlywhenitiscomingfromanlt-interface.
PR1071340Ifport-mirroringandVRRPoverae-irbisconfiguredinabridge-domain,enablingtheDistributedPeriodicPacketManagementProcess(ppmd)forVRRPinthisBDmightcausetheVRRPtoflap.
PR1071341Wheninline-samplingisenabled,inraceconditions,ifpacketgetscorruptedandthecorruptedpacketlengthshows0,thismaycause"PPE_xErrorsthreadtimeouterror"andeventuallycauseMPCcardtocrash.
PR1072136VRRPadvertisementsmightbedroppedafterenabledelegate-processingonthelogicaltunnel(lt)interface.
ItwouldresultinVRRPmasterstateobservedonbothrouters.
PR1073090WhenanMXSerieschassisnetwork-servicesis"enhanced-ip"andanAEwith"familybridge"configurationisfirstcommitted,thereisapossibilitythatanincorrectforwardingpathmaybeinstalledcausingtrafficloss.
PR1081999Issueisspecificto64-bitRPDandconfig-groupswildcardconfigurationspecificallyasinthefollowingcase:setgroupsTESTrouting-instancesrouting-optionsmulticastforwarding-cachefamilyinetthresholdsuppress200setrouting-instancesvrf1apply-groupsTESTsetrouting-instancesvrf1routing-optionsmulticastforwarding-cachefamilyinetthresholdsuppress600Withthisdaemon(rpd)reads35Copyright2016,JuniperNetworks,Inc.
ResolvedIssuessuppressedvalue"200"(thatis,comingfromgroups)insteadofreadingvalue"600"fromforeground,andcustomerseesunexpectedbehaviorwithrespecttothreshold-suppress.
Workaround:Theycanreplacewildcardwithactualrouting-instancenameasinthefollowingexample:setgroupsTESTrouting-instancesvrf1routing-optionsmulticastforwarding-cachefamilyinetthresholdsuppress200setrouting-instancesvrf1apply-groupsTESTsetrouting-instancesvrf1routing-optionsmulticastforwarding-cachefamilyinetthresholdsuppress600PR1089994RoutingProtocolsDeletionofarouting-instancemayleadtoaroutingdaemoncrash.
Thismayhappeniftherouting-instanceRoutingInformationBase(RIB)isreferencedinanactivepolicy-optionconfiguration.
Asaworkaround,whendeactivatingtherouting-instance,allassociatedconfigurationsusingtheroute-tablenamesintherouting-instanceshouldalsobedeactivated.
PR1057431InPIMenvironment,BootstrapRouter(BSR)canbeusedonlybetweenPIMv2enableddevices.
WhendeactivatingalltheinterfaceswhicharerunningPIMbootstrap,thesystemchangestooperateinPIMv1.
Atthistime,alltheinformationlearnedabout/fromthecurrentBSRshouldbecleaned,butactually,BSRstateisnotcleaned.
Iftheinterfacewhichwastheprevious"electedBSR"isactivated,BSRstateisPIM_BSR_ELECTED(shouldbecleanedpreviously)andthesystemassumestheBSRtimerisstillhere.
WhenthesystemtriestoaccessthenullBSRtimer,therpdprocessmightcrash.
PR1062133IfwithalargenumberofmulticastsourcesforasamemulticastgroupinPIMdensemode,therpdprocessmightcrashafterRoutingEngineswitchover.
PR1069805Forthepimnbrwhichisnotdirectlyconnected(thatis,nbronunnumberedinterface,orp2pinterfacewithdifferentsubnet),pimjoinisnotabletofindthecorrectupstreamnbrwhichresultsinjoinnotpropagatingtotheupstreamnbr.
showcommandforpimjoinshowsupstreamnbr"unknown".
Issueispresentinthe15.
1R1release.
PR1069896InProtocolIndependentMulticast(PIM)sparsemodeenvironment,iftherouterisbeingusedastherendezvouspoint(RP)andalsothelasthoprouter,whenthe(*,G)entryispresentontheRPandadiscardmulticastroute(forexample,duetoreceivingmulticasttrafficfromanon-RPFinterface)isalreadyexisted,ifthe(S,G)entryislearnedafterreceivingsource-active(SA)oftheMulticastSourceDiscoveryProtocol(MSDP),theSPTcutovermayfailtobetriggered.
Thereisnotrafficimpactasreceiversstillcangetthetrafficdueto(*,G)route.
PR1073773Inmulti-topologiesIS-ISscenario,thereishugedifferencebetweenestimatedfreebytesandactualfreebyteswhengeneratingLSPwithIPv6prefix.
ItmightcauseLSPfragmentexhaustion.
PR1074891WithMulticastSourceDiscoveryProtocol(MSDP)andnonstopactiverouting(NSR)configuredontheProtocolIndependentMulticast(PIM)sparse-moderendezvouspoint(RP),therpdprocessmightpermanentlygetstuckwhenmulticasttrafficreceivedshortlyafterRoutingEnginesswitchover.
PR10833851.
Configuretheospfandospf3inallrouters2.
Configurenodeprotection3.
Checkfor22.
1.
1.
0anybackupispresent4.
Enablepplfaall5.
Checkfor22.
1.
1.
0anypplfabackupispresentthroughr2.
Wearenotseeinganypplfabackupfor22.
1.
1.
0.
PR1085029Copyright2016,JuniperNetworks,Inc.
36JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesServicesApplicationsThesession-limit-per-prefixfeaturefortheMXSeriesDS-LiteserverdoesnottakeSoftwireflowintoaccountwhencalculatingtheflowlimit.
PR1023439OnMXSeriesroutersandTSeriesrouterswithMultiservices100,Multiservices400,orMultiservices500PICswith"dump-on-flow-control"configured,ifprolongedflowcontrolfailure,thecoredumpfilemightgeneratefailure.
PR1039340OnMXSeriesroutersthatareactingasLNStoprovidetunnelendpoints,itisobservedthattheservice-interfacesarenotusableifaMICcorrespondingtothemisnotphysicallyinstalledontheFPC.
IfonlythoseserviceinterfacesthatbelongtotheremovedPICareaddedtoservice-device-pool,thisresultsinnoLNSsubscribersbeingabletologin.
NotethatoncetheMICisinsertedintotheFPC,thefeaturescouldbeused.
PR1063024WhenconfiguringRADIUSauthenticationforLayer2TunnelingProtocol(L2TP),theRADIUSservercannotberecognizedbecausethesourceaddressisnotbeingreadcorrectly.
Asaresult,theL2TPsessioncannotbeestablished.
PR1064817ThetriggerforthecrashiswhentheMS-DPCsServicePICisinalowmemoryzoneanditreceivestwoSYNmessagesfromthethesameclientIPwithinaveryshorttimegapinbetweenthetwoSYNs.
Sothisraceconditionistiedtorunningoutofmemory,failingtoallocatingatimerforaconversation,andhavingrapidSYNsonaTCPconnectionwherethesecondTCPSYNismatchedonflowwhichisbeingdeletedduetoafailedtimerallocationforthat.
Thisscenarioisverydifficulttohitandshouldnotbeseeninproductionoften.
PR1069006ServicePICdaemon(spd)mightcrashwithcore-dumpsduetoCGNATpool'ssnmp-trap-thresholdsconfiguration.
PR1070370Earlieroutputfrom"showservicel2tptunnel"willnotdisplaytunnelswithnosessions.
Thisbehaviorhavebeenchanged,nowemptytunnelsarealsodisplayedinthiscommand.
PR1071923SoftwareInstallationandUpgradeAdd"on"argumentto"requestsystemsoftwarevalidate"toallowvalidationonaremotehost/RoutingEnginerunningJunosOS.
PR1066150UserInterfaceandConfigurationDuetoachangeinanexistingPR,groupnamesintheconfigurationmustbeastringofalphanumericals,dashes,orunderscores.
Thereisnoworkaroundotherthanfollowingthegroupnameinstructions.
PR1087051VPNsInthel2circuitenvironment,whenl2cktconfigurationhasbackup-neighbor,theflow-labeloperationisblockedattheconfigurationlevel.
PR1056777OndualRoutingEngines,ifmvpnprotocolitselfisnotconfigured,andnonstopactiveroutingisenabled,theshowcommand"showtaskreplication"onthemasterRoutingEnginewilllisttheMVPNprotocoleventhoughitisnotconfigured.
Otherthanthe37Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesmisleadingshowoutputwhichmaybeslightlyconfusingtotheuser/customer,thereisnofunctionalimpactduetothisissueassuch.
Thereisnoworkaroundavailable.
PR1078305RelatedDocumentationNewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10KnownIssuesonpage13DocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47DocumentationUpdatesTherearenoerrataorchangesinJunosOSRelease15.
1F3documentationfortheMXSeriesandTSeries.
RelatedDocumentationNewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10KnownIssuesonpage13ResolvedIssuesonpage19Migration,Upgrade,andDowngradeInstructionsonpage38ProductCompatibilityonpage47Migration,Upgrade,andDowngradeInstructionsThissectioncontainstheproceduretoupgradeJunosOS,andtheupgradeanddowngradepoliciesforJunosOSfortheMXSeriesandTSeries.
UpgradingordowngradingJunosOScantakeseveralminutes,dependingonthesizeandconfigurationofthenetwork.
StartingwithJunosOSRelease15.
1,insomeofthedevices,FreeBSD10.
xistheunderlyingOSforJunosOSinsteadofFreeBSD6.
1.
Thisfeatureincludesasimplifiedpackagenamingsystemthatdropsthedomesticandworld-widenamingconvention.
However,insomeoftherouters,FreeBSD6.
1remainstheunderlyingOSforJunosOS.
FormoredetailsaboutFreeBSD10.
x,seeUnderstandingJunosOSwithUpgradedFreeBSD.
NOTE:InJunosOSRelease15.
1,JunosOS(FreeBSD10.
x)isnotavailabletocustomersinBelarus,Kazakhstan,andRussia.
CustomersinthesecountriesneedtousetheexistingJunosOS(FreeBSD6.
1).
Copyright2016,JuniperNetworks,Inc.
38JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesCAUTION:Thisreleaseintroducessomebehaviorchangestotheunifiedin-servicesoftwareupgrade(ISSU)functionalityforMXSeriesroutersandTSeriesrouters.
WedonotrecommendusingunifiedISSUtoupgradefromanearlierJunosOSreleasetoJunosOSRelease15.
1.
Therequestsystemsoftwarevalidatein-service-upgradecommand,whichallowsthedetectionofanycompatibilityissuesbeforeactuallyissuingtherequestsystemsoftwarein-service-upgradecommandtoinitiateunifiedISSU,isnotsupportedinJunosOSRelease15.
1whileupgradingfromearlierJunosOSreleases.
ThefollowingtableshowsdetailedinformationaboutwhichJunosOScanbeusedonwhichproducts:FreeBSD10.
x-basedJunosOSFreeBSD6.
1-basedJunosOSPlatformNOYESMX80,MX104YESYESMX240,MX480,MX960,MX2010,MX2020NOYEST640,T1600,T4000,TXMatrix,TXMatrixPlusBasicProcedureforUpgradingtoRelease15.
1F3onpage39UpgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD10.
x)onpage41UpgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD6.
1)onpage42UpgradeandDowngradeSupportPolicyforJunosOSReleasesonpage44UpgradingaRouterwithRedundantRoutingEnginesonpage44UpgradingtheSoftwareforaRoutingMatrixonpage45UpgradingUsingUnifiedISSUonpage46DowngradingfromRelease15.
1onpage46BasicProcedureforUpgradingtoRelease15.
1F3WhenupgradingordowngradingJunosOS,alwaysusethejinstallpackage.
Useotherpackages(suchasthejbundlepackage)onlywhensoinstructedbyaJuniperNetworkssupportrepresentative.
Forinformationaboutthecontentsofthejinstallpackageanddetailsoftheinstallationprocess,seetheInstallationandUpgradeGuideandUpgradingJunosOSwithUpgradedFreeBSD.
39Copyright2016,JuniperNetworks,Inc.
Migration,Upgrade,andDowngradeInstructionsNOTE:Beforeupgrading,backupthefilesystemandthecurrentlyactiveJunosOSconfigurationsothatyoucanrecovertoaknown,stableenvironmentincasetheupgradeisunsuccessful.
Issuethefollowingcommand:user@host>requestsystemsnapshotTheinstallationprocessrebuildsthefilesystemandcompletelyreinstallsJunosOS.
Configurationinformationfromtheprevioussoftwareinstallationisretained,butthecontentsoflogfilesmightbeerased.
Storedfilesontheroutingplatform,suchasconfigurationtemplatesandshellscripts(theonlyexceptionsarethejuniper.
confandsshfiles)mightberemoved.
Topreservethestoredfiles,copythemtoanothersystembeforeupgradingordowngradingtheroutingplatform.
Formoreinformation,seetheJunosOSAdministrationLibraryforRoutingDevices.
Copyright2016,JuniperNetworks,Inc.
40JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesUpgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD10.
x)Productsimpacted:MX240,MX480,MX960,MX2010,andMX2020.
NOTE:ThissectiondoesnotapplytocustomersinBelarus,Kazakhstan,andRussia.
Customersinthesecountriesneedtorefertothenextsection.
TodownloadandinstallfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD10.
x):1.
UsingaWebbrowser,navigatetotheAllJunosPlatformssoftwaredownloadURLontheJuniperNetworkswebpage:http://www.
juniper.
net/support/downloads/2.
SelectthenameoftheJunosOSplatformforthesoftwarethatyouwanttodownload.
3.
Selectthereleasenumber(thenumberofthesoftwareversionthatyouwanttodownload)fromtheReleasedrop-downlisttotherightoftheDownloadSoftwarepage.
4.
SelecttheSoftwaretab.
5.
IntheInstallPackagesectionoftheSoftwaretab,selectthesoftwarepackagefortherelease.
6.
LogintotheJuniperNetworksauthenticationsystemusingtheusername(generallyyoure-mailaddress)andpasswordsuppliedbyaJuniperNetworksrepresentative.
7.
ReviewandaccepttheEndUserLicenseAgreement.
8.
Downloadthesoftwaretoalocalhost.
9.
Copythesoftwaretotheroutingplatformortoyourinternalsoftwaredistributionsite.
10.
Installthenewjinstallpackageontheroutingplatform.
NOTE:Werecommendthatyouupgradeallsoftwarepackagesoutofbandusingtheconsolebecausein-bandconnectionsarelostduringtheupgradeprocess.
For32-bitRoutingEngineversion:user@host>requestsystemsoftwareaddno-validaterebootsource/junos-install-mx-x86-32-15.
1F3.
11-signed.
tgzFor64-bitRoutingEngineversion:user@host>requestsystemsoftwareaddno-validaterebootsource/junos-install-mx-x86-64-15.
1F3.
11-signed.
tgzReplacesourcewithoneofthefollowingvalues:/pathname—Forasoftwarepackagethatisinstalledfromalocaldirectoryontherouter.
41Copyright2016,JuniperNetworks,Inc.
Migration,Upgrade,andDowngradeInstructionsForsoftwarepackagesthataredownloadedandinstalledfromaremotelocation:ftp://hostname/pathnamehttp://hostname/pathnamescp://hostname/pathname(availableonlyforCanadaandU.
S.
version)DonotusethevalidateoptionwhileupgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD10.
x).
Thisisbecauseprogramsinthejunos-upgrade-xpackagearebuiltbasedonFreeBSD10.
x,andJunosOS(FreeBSD6.
1)wouldnotbeabletoruntheseprograms.
Youmustruntheno-validateoption.
Theno-validatestatementdisablesthevalidationprocedureandallowsyoutouseanimportpolicyinstead.
Usetherebootcommandtoreboottherouteraftertheupgradeisvalidatedandinstalled.
Whentherebootiscomplete,therouterdisplaystheloginprompt.
Theloadingprocesscantake5to10minutes.
Rebootingoccursonlyiftheupgradeissuccessful.
NOTE:YouneedtoinstalltheJunosOSsoftwarepackageandhostsoftwarepackageontherouterswiththeRE-MX-X6RoutingEngine.
ForupgradingthehostOSonrouterswithRE-MX-X6RoutingEngine,usethejunos-vmhost-install-x.
tgzimageandspecifythenameoftheregularpackageintherequestvmhostsoftwareaddcommand.
FormoreinformationseeVMHostInstallationtopicinInstallationandUpgradeGuide.
NOTE:AfteryouinstallaJunosOSRelease15.
1F3jinstallpackage,youcannotissuetherequestsystemsoftwarerollbackcommandtoreturntothepreviouslyinstalledJunosOS(FreeBSD6.
1)software.
Instead,youmustissuetherequestsystemsoftwareaddno-validatecommandandspecifythejinstallpackagethatcorrespondstothepreviouslyinstalledsoftware.
NOTE:MostoftheexistingrequestsystemcommandsarenotsupportedonrouterswithRE-MX-X6RoutingEngines.
SeetheVMHostSoftwareAdministrativeCommandsintheInstallationandUpgradeGuideUpgradingfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD6.
1)Productsimpacted:AllTSeriesroutersandtheMX80andMX104.
NOTE:CustomersinBelarus,Kazakhstan,andRussiamustusethefollowingprocedureforallMXSeriesroutersrunningJunosOSRelease15.
1.
TodownloadandinstallfromJunosOS(FreeBSD6.
1)toJunosOS(FreeBSD6.
1):Copyright2016,JuniperNetworks,Inc.
42JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeries1.
UsingaWebbrowser,navigatetotheAllJunosPlatformssoftwaredownloadURLontheJuniperNetworkswebpage:http://www.
juniper.
net/support/downloads/2.
SelectthenameoftheJunosOSplatformforthesoftwarethatyouwanttodownload.
3.
Selectthereleasenumber(thenumberofthesoftwareversionthatyouwanttodownload)fromtheReleasedrop-downlisttotherightoftheDownloadSoftwarepage.
4.
SelecttheSoftwaretab.
5.
IntheInstallPackagesectionoftheSoftwaretab,selectthesoftwarepackagefortherelease.
6.
LogintotheJuniperNetworksauthenticationsystemusingtheusername(generallyyoure-mailaddress)andpasswordsuppliedbyaJuniperNetworksrepresentative.
7.
ReviewandaccepttheEndUserLicenseAgreement.
8.
Downloadthesoftwaretoalocalhost.
9.
Copythesoftwaretotheroutingplatformortoyourinternalsoftwaredistributionsite.
10.
Installthenewjinstallpackageontheroutingplatform.
NOTE:Werecommendthatyouupgradeallsoftwarepackagesoutofbandusingtheconsolebecausein-bandconnectionsarelostduringtheupgradeprocess.
CustomersintheUnitedStatesandCanada,usethefollowingcommand:user@host>requestsystemsoftwareaddvalidaterebootsource/jinstall-15.
1F311-domestic-signed.
tgzAllothercustomers,usethefollowingcommand:user@host>requestsystemsoftwareaddvalidaterebootsource/jinstall-15.
1F311-export-signed.
tgzReplacesourcewithoneofthefollowingvalues:/pathname—Forasoftwarepackagethatisinstalledfromalocaldirectoryontherouter.
Forsoftwarepackagesthataredownloadedandinstalledfromaremotelocation:ftp://hostname/pathnamehttp://hostname/pathnamescp://hostname/pathname(availableonlyforCanadaandU.
S.
version)Thevalidateoptionvalidatesthesoftwarepackageagainstthecurrentconfigurationasaprerequisitetoaddingthesoftwarepackagetoensurethattherouterreboots43Copyright2016,JuniperNetworks,Inc.
Migration,Upgrade,andDowngradeInstructionssuccessfully.
Thisisthedefaultbehaviorwhenthesoftwarepackagebeingaddedisadifferentrelease.
Usetherebootcommandtoreboottherouteraftertheupgradeisvalidatedandinstalled.
Whentherebootiscomplete,therouterdisplaystheloginprompt.
Theloadingprocesscantake5to10minutes.
Rebootingoccursonlyiftheupgradeissuccessful.
NOTE:AfteryouinstallaJunosOSRelease15.
1F3jinstallpackage,youcannotissuetherequestsystemsoftwarerollbackcommandtoreturntothepreviouslyinstalledsoftware.
Instead,youmustissuetherequestsystemsoftwareaddvalidatecommandandspecifythejinstallpackagethatcorrespondstothepreviouslyinstalledsoftware.
UpgradeandDowngradeSupportPolicyforJunosOSReleasesSupportforupgradesanddowngradesthatspanmorethanthreeJunosOSreleasesatatimeisnotprovided,exceptforreleasesthataredesignatedasExtendedEnd-of-Life(EEOL)releases.
EEOLreleasesprovidedirectupgradeanddowngradepaths—youcanupgradedirectlyfromoneEEOLreleasetothenextEEOLreleaseeventhoughEEOLreleasesgenerallyoccurinincrementsbeyondthreereleases.
YoucanupgradeordowngradetotheEEOLreleasethatoccursdirectlybeforeorafterthecurrentlyinstalledEEOLrelease,ortotwoEEOLreleasesbeforeorafter.
Forexample,JunosOSReleases10.
0,10.
4,and11.
4areEEOLreleases.
YoucanupgradefromJunosOSRelease10.
0toRelease10.
4orevenfromJunosOSRelease10.
0toRelease11.
4.
However,youcannotupgradedirectlyfromanon-EEOLreleasethatismorethanthreereleasesaheadorbehind.
Forexample,youcannotdirectlyupgradefromJunosOSRelease10.
3(anon-EEOLrelease)toJunosOSRelease11.
4ordirectlydowngradefromJunosOSRelease11.
4toJunosOSRelease10.
3.
Toupgradeordowngradefromanon-EEOLreleasetoareleasemorethanthreereleasesbeforeorafter,firstupgradetothenextEEOLreleaseandthenupgradeordowngradefromthatEEOLreleasetoyourtargetrelease.
FormoreinformationonEEOLreleasesandtoreviewalistofEEOLreleases,seehttp://www.
juniper.
net/support/eol/junos.
html.
UpgradingaRouterwithRedundantRoutingEnginesIftherouterhastwoRoutingEngines,performthefollowingJunosOSinstallationoneachRoutingEngineseparatelytoavoiddisruptingnetworkoperation:1.
DisablegracefulRoutingEngineswitchover(GRES)onthemasterRoutingEngine,andsavetheconfigurationchangetobothRoutingEngines.
2.
InstallthenewJunosOSreleaseonthebackupRoutingEnginewhilekeepingthecurrentlyrunningsoftwareversiononthemasterRoutingEngine.
Copyright2016,JuniperNetworks,Inc.
44JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeries3.
AftermakingsurethatthenewsoftwareversionisrunningcorrectlyonthebackupRoutingEngine,switchovertothebackupRoutingEnginetoactivatethenewsoftware.
4.
InstallthenewsoftwareontheoriginalmasterRoutingEnginethatisnowactiveasthebackupRoutingEngine.
Forthedetailedprocedure,seetheInstallationandUpgradeGuide.
UpgradingtheSoftwareforaRoutingMatrixAroutingmatrixcanbeeitheraTXMatrixrouterastheswitch-cardchassis(SCC)oraTXMatrixPlusrouterastheswitch-fabricchassis(SFC).
Bydefault,whenyouupgradesoftwareforaTXMatrixrouteroraTXMatrixPlusrouter,thenewimageisloadedontotheTXMatrixorTXMatrixPlusrouter(specifiedintheJunosOSCLIbyusingthesccorsfcoption)anddistributedtoallline-cardchassis(LCCs)intheroutingmatrix(specifiedintheJunosOSCLIbyusingthelccoption).
Toavoidnetworkdisruptionduringtheupgrade,ensurethefollowingconditionsbeforebeginningtheupgradeprocess:AminimumoffreediskspaceandDRAMoneachRoutingEngine.
ThesoftwareupgradewillfailonanyRoutingEnginewithouttherequiredamountoffreediskspaceandDRAM.
TodeterminetheamountofdiskspacecurrentlyavailableonallRoutingEnginesoftheroutingmatrix,usetheCLIshowsystemstoragecommand.
TodeterminetheamountofDRAMcurrentlyavailableonalltheRoutingEnginesintheroutingmatrix,usetheCLIshowchassisrouting-enginecommand.
ThemasterRoutingEnginesoftheTXMatrixorTXMatrixPlusrouter(SCCorSFC)andallLCCsconnectedtotheSCCorSFCareallre0orareallre1.
ThebackupRoutingEnginesoftheTXMatrixorTXMatrixPlusrouter(SCCorSFC)andallLCCsconnectedtotheSCCorSFCareallre1orareallre0.
AllmasterRoutingEnginesinallroutersrunthesameversionofsoftware.
Thisisnecessaryfortheroutingmatrixtooperate.
AllmasterandbackupRoutingEnginesrunthesameversionofsoftwarebeforebeginningtheupgradeprocedure.
DifferentversionsofJunosOScanhaveincompatiblemessageformatsespeciallyifyouturnonGRES.
Becausethestepsintheprocessincludechangingmastership,runningthesameversionofsoftwareisrecommended.
ForaroutingmatrixwithaTXMatrixrouter,thesameRoutingEnginemodelisusedwithinaTXMatrixrouter(SCC)andwithinaT640router(LCC)ofaroutingmatrix.
Forexample,aroutingmatrixwithanSCCusingtwoRE-A-2000sandanLCCusingtwoRE-1600sissupported.
However,anSCCoranLCCwithtwodifferentRoutingEnginemodelsisnotsupported.
WesuggestthatallRoutingEnginesbethesamemodelthroughoutallroutersintheroutingmatrix.
TodeterminetheRoutingEnginetype,usetheCLIshowchassishardware|matchroutingcommand.
ForaroutingmatrixwithaTXMatrixPlusrouter,theSFCcontainstwomodelRE-DUO-C2600-16GRoutingEngines,andeachLCCcontainstwomodelRE-DUO-C1800-8GorRE-DUO-C1800-16GRoutingEngines.
45Copyright2016,JuniperNetworks,Inc.
Migration,Upgrade,andDowngradeInstructionsBESTPRACTICE:MakesurethatallmasterRoutingEnginesarere0andallbackupRoutingEnginesarere1(orviceversa).
Forthepurposesofthisdocument,themasterRoutingEngineisre0andthebackupRoutingEngineisre1.
Toupgradethesoftwareforaroutingmatrix:1.
DisablegracefulRoutingEngineswitchover(GRES)onthemasterRoutingEngine(re0),andsavetheconfigurationchangetobothRoutingEngines.
2.
InstallthenewJunosOSreleaseonthebackupRoutingEngine(re1)whilekeepingthecurrentlyrunningsoftwareversiononthemasterRoutingEngine(re0).
3.
LoadthenewJunosOSonthebackupRoutingEngine.
4.
AftermakingsurethatthenewsoftwareversionisrunningcorrectlyonthebackupRoutingEngine(re1),switchmastershipbacktotheoriginalmasterRoutingEngine(re0)toactivatethenewsoftware.
5.
InstallthenewsoftwareonthenewbackupRoutingEngine(re0).
Forthedetailedprocedure,seetheRoutingMatrixwithaTXMatrixRouterDeploymentGuideortheRoutingMatrixwithaTXMatrixPlusRouterDeploymentGuide.
UpgradingUsingUnifiedISSUCAUTION:Thisreleaseintroducessomebehaviorchangestotheunifiedin-servicesoftwareupgrade(ISSU)functionalityforMXSeriesroutersandTSeriesrouters.
WedonotrecommendusingunifiedISSUtoupgradefromanearlierJunosOSreleasetoJunosOSRelease15.
1.
Unifiedin-servicesoftwareupgrade(ISSU)enablesyoutoupgradebetweentwodifferentJunosOSreleaseswithnodisruptiononthecontrolplaneandwithminimaldisruptionoftraffic.
UnifiedISSUisonlysupportedbydualRoutingEngineplatforms.
Inaddition,gracefulRoutingEngineswitchover(GRES)andnonstopactiverouting(NSR)mustbeenabled.
ForadditionalinformationaboutusingunifiedISSU,seetheHighAvailabilityFeatureGuideforRoutingDevices.
DowngradingfromRelease15.
1TodowngradefromRelease15.
1toanothersupportedrelease,followtheprocedureforupgrading,butreplacethe15.
1jinstallpackagewithonethatcorrespondstotheappropriaterelease.
Copyright2016,JuniperNetworks,Inc.
46JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesNOTE:Youcannotdowngrademorethanthreereleases.
Forexample,ifyourroutingplatformisrunningJunosOSRelease11.
4,youcandowngradethesoftwaretoRelease10.
4directly,butnottoRelease10.
3orearlier;asaworkaround,youcanfirstdowngradetoRelease10.
4andthendowngradetoRelease10.
3.
Formoreinformation,seetheInstallationandUpgradeGuide.
RelatedDocumentationNewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10KnownIssuesonpage13ResolvedIssuesonpage19DocumentationUpdatesonpage38ProductCompatibilityonpage47ProductCompatibilityHardwareCompatibilityonpage47HardwareCompatibilityToobtaininformationaboutthecomponentsthataresupportedonthedevices,andspecialcompatibilityguidelineswiththerelease,seetheHardwareGuideandtheInterfaceModuleReferencefortheproduct.
TodeterminethefeaturessupportedonMXSeriesdevicesinthisrelease,usetheJuniperNetworksFeatureExplorer,aWeb-basedapplicationthathelpsyoutoexploreandcompareJunosOSfeatureinformationtofindtherightsoftwarereleaseandhardwareplatformforyournetwork.
FindFeatureExplorerat:http://pathfinder.
juniper.
net/feature-explorer/RelatedDocumentationNewandChangedFeaturesonpage3ChangesinBehaviorandSyntaxonpage9KnownBehavioronpage10KnownIssuesonpage13ResolvedIssuesonpage19DocumentationUpdatesonpage38Migration,Upgrade,andDowngradeInstructionsonpage3847Copyright2016,JuniperNetworks,Inc.
ProductCompatibilityJunosOSReleaseNotesforPTXSeriesPacketTransportRoutersThesereleasenotesaccompanyJunosOSRelease15.
1F3forthePTXSeries.
Theydescribenewandchangedfeatures,limitations,andknownandresolvedproblemsinthehardwareandsoftware.
YoucanalsofindthesereleasenotesontheJuniperNetworksJunosOSDocumentationwebpage,locatedathttp://www.
juniper.
net/techpubs/software/junos/.
CAUTION:Thisreleaseintroducessomebehaviorchangestotheunifiedin-servicesoftwareupgrade(ISSU)functionalityforPTXSeriesrouters.
WedonotrecommendusingunifiedISSUtoupgradefromanearlierJunosOSreleasetoJunosOSRelease15.
1.
NewandChangedFeaturesonpage48ChangesinBehaviorandSyntaxonpage50KnownBehavioronpage51KnownIssuesonpage53ResolvedIssuesonpage54DocumentationUpdatesonpage58Migration,Upgrade,andDowngradeInstructionsonpage59ProductCompatibilityonpage63NewandChangedFeaturesThissectiondescribesthenewfeaturesandenhancementstoexistingfeaturesinJunosOSRelease15.
1F3forthePTXSeries.
Hardwareonpage48GeneralRoutingonpage49InterfacesandChassisonpage50Managementonpage50HardwareNewRoutingEngineRE-PTX-X8-64G(PTX5000)—StartinginJunosOSRelease15.
1F4,theRoutingEngineRE-PTX-X8-64GissupportedonPTX5000routers.
ThisRoutingEnginehasanincreasedcomputingcapabilityandscalabilitytosupporttherapidriseinthedataplanecapacity.
TheRoutingEngineisbasedonamodularvirtualizedarchitectureandleveragesthehardware-assistedvirtualizationcapabilities.
TheRoutingEnginehasa64-bitCPUandsupportsa64-bitkerneland64-bitapplications.
Withitsmulticorecapabilities,theRoutingEnginesupportssymmetricmultiprocessingintheJunosOSkernelandhostedapplications.
Copyright2016,JuniperNetworks,Inc.
48JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesNOTE:TheRoutingEngineRE-PTX-X8-64GissupportedonlyonthenewControlBoardCB2-PTX.
NewControlBoardsupport(PTX5000)—StartingwithRelease15.
1F4,JunosOSsupportstheRoutingEngineRE-PTX-X8-64GwithanenhancedControlBoard(CB)onPTX5000routers.
TheCBsupportschassismanagementand16additional10-GigabitEthernetportswithsmallform-factorpluggableplustransceivers(SFP+)onthefrontpaneloftheroutertosupportmultichassisapplications.
TheenhancedCBconsistsofthefollowingcomponents:EthernetswitchusedforintermodulecommunicationPCIExpressbustoconnecttotheRoutingEnginePCIExpressswitchtoconnecttotheSIBsSwitchProcessorMezzanineBoard(SPMB)Highcapacitysingle-phaseACPDU(PTX5000)—InJunosOSRelease15.
1F3,asingle-phaseACpowerdistributionunit(PDU)—PDU2-PTX-AC-SP—isintroducedtoprovidepowertothePTX5000chassis.
ThePDUprovidesasingle-phaseACinputconnectionfromthecustomer'sACsource,anI/Ointerfacetothepowersupplymodules(PSMs),andaDCpowerconnectiontothesystemmidplane.
ThePDUispoweredbyeithereight30-Aoreight20-Asingle-phasesources.
EachoftheeightPSMsconnectedtotheACPDUreceivessingle-phaseinput.
GeneralRoutingSupportforvirtualizationonRE-PTX-X8-64G(PTX5000)—StartingwithJunosOSRelease15.
1F3,theRoutingEngineRE-PTX-X8-64GforPTX5000supportsvirtualization.
VirtualizationenablestheroutertosupportmultipleinstancesofJunosOSandotheroperatingsystemsonthesameRoutingEngine.
However,forJunosOSRelease15.
1F3,oneinstanceofJunosOS,whichrunsasaguestoperatingsystem,islaunchedbydefault.
Theuserneedstologintothisinstanceforoperationsandmanagement.
WithvirtualizationoftheRoutingEngine,JunosOSsupportsnewrequestandshowcommandsassociatedwithhostandhypervisorprocesses.
Thecommandsarerelatedto:Reboot,halt,andpowermanagementforthehostSoftwareupgradeforthehost49Copyright2016,JuniperNetworks,Inc.
NewandChangedFeaturesDisksnapshotforthehostInterfacesandChassisSupportforincludingLOCAL-FAULTandREMOTE-FAULTinformation(PTXSeries)—StartinginJunosOSRelease15.
1F3,PTXSeriesroutersaddtheabilitytodisplayLOCAL-FAULTandREMOTE-FAULTinformationintheoutputoftheshowinterfaceset-fpc/pic/portcommand.
ManagementRoutertelemetrydataforhardwareandsoftware(PTXSeries)—StartinginJunosOSRelease15.
1F3,youcanconfigurePTXSeriesrouterstoexporttelemetrydatafromsupportedinterfacehardware.
LinecardsensordatasuchasinterfaceRSVPTELSPeventsaresentdirectlytoconfiguredcollectionpointswithoutinvolvingpolling.
Allparametersareconfiguredatthe[editservicesanalytics]hierarchylevel.
YoucanconfiguretheexactinterfacesandLSPsforexportstatisticsusingregularexpressionresourcefiltermatches.
SupportedFPChardwareonPTXSeriesroutersislimitedtoFPC3.
ThePTXSeriesFPC2hardwareisnotsupported.
RelatedDocumentationChangesinBehaviorandSyntaxonpage50KnownBehavioronpage51KnownIssuesonpage53ResolvedIssuesonpage54DocumentationUpdatesonpage58Migration,Upgrade,andDowngradeInstructionsonpage59ProductCompatibilityonpage63ChangesinBehaviorandSyntaxTherearenochangesindefaultbehaviorandsyntaxinJunosOSRelease15.
1F3forthePTXSeries.
RelatedDocumentationNewandChangedFeaturesonpage48KnownBehavioronpage51KnownIssuesonpage53ResolvedIssuesonpage54DocumentationUpdatesonpage58Migration,Upgrade,andDowngradeInstructionsonpage59ProductCompatibilityonpage63Copyright2016,JuniperNetworks,Inc.
50JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesKnownBehaviorThissectioncontainstheknownbehavior,systemmaximums,andlimitationsinhardwareandsoftwareinJunosOSRelease15.
1F3forthePTXSeries.
ForthemostcompleteandlatestinformationaboutknownJunosOSdefects,usetheJuniperNetworksonlineJunosProblemReportSearchapplication.
GeneralRoutingonpage51GeneralRoutingThefollowingrequestcommandsarenotavailablefortheRoutingEngineRE-PTX-X8-64GonthePTX5000:requestsystemhaltrequestsystempartitionrequestsystempoweroffrequestsystempoweronThescopeoffunctionalityofthefollowingcommandsislimitedtoJunosOSguestlevel:requestsystemrebootrequestsystemsnapshotrequestsystemsoftwareaddrequestsystemzeroizeYoucanusethefollowingequivalentrequestvmhostcommandstoachievethefunctionality:requestvmhostcleanuprequestvmhostfile-copyrequestvmhosthaltrequestvmhosthard-disk-testrequestvmhostpower-offrequestvmhostpower-onrequestvmhostrebootrequestvmhostsnapshotrequestvmhostsoftwareabortrequestvmhostsoftwareaddrequestvmhostsoftwarein-service-upgrade51Copyright2016,JuniperNetworks,Inc.
KnownBehaviorrequestvmhostsoftwarerollbackrequestvmhostzeroizeTheoutputoffollowingshowcommandsaremodifiedfortheRoutingEngineRE-PTX-X8-64G:showchassisenvironmentrouting-engineshowchassishardwareshowchassishardwareextensiveshowchassisrouting-engineshowsystemsoftwareThefollowingnewshowcommandsareintroducedfortheRoutingEngineRE-PTX-X8-64G:showvmhostbridgeshowvmhostcrashshowvmhosthardwareshowvmhostinformationshowvmhostlogsshowvmhostnetstatshowvmhostprocessesshowvmhostresource-usageshowvmhostsnapshotshowvmhoststatusshowvmhostuptimeshowvmhostversionThefollowingnewconfigurationstatementsareintroducedfortheRoutingEngineRE-PTX-X8-64G:editvmhosteditsystemprocessesapp-engine-virtual-machine-management-serviceRelatedDocumentationNewandChangedFeaturesonpage48ChangesinBehaviorandSyntaxonpage50KnownIssuesonpage53ResolvedIssuesonpage54DocumentationUpdatesonpage58Migration,Upgrade,andDowngradeInstructionsonpage59Copyright2016,JuniperNetworks,Inc.
52JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesProductCompatibilityonpage63KnownIssuesThissectionliststheknownissuesinhardwareandsoftwareinJunosOSRelease15.
1F3forthePTXSeries.
ForthemostcompleteandlatestinformationaboutknownJunosOSdefects,usetheJuniperNetworksonlineJunosProblemReportSearchapplication.
GeneralRoutingonpage53InterfacesandChassisonpage53MPLSonpage54PlatformandInfrastructureonpage54RoutingProtocolsonpage54GeneralRoutingPTXSeriesdoesnotsupportthequeuingPICsbutbydefaultJunosOSwillprogramchassisschedulermapwhichwillgeneratethefollowinglogs:"fpc2COS(cos_chassis_scheduler_pre_add_action:2140):chassisschduleripcreceivedfornonqpicifdet-2/1/3withindex131/kernel:GENCFG:op8(COSBLOB)failed;err5(Invalid)Fix:AddingchecktostopsendingchassisschedulermaponPTXplatform.
"Fix:AddingchecktostopsendingchassisschedulermaponPTXSeriesplatform.
PR910985InterfacesandChassisOnPTXSeriesrouters,TXopticalthresholdvalueisshownincorrectlyfortheinterfacesinthePICP1-PTX-2-100G-WDM.
ThisPRwillfixonlytheTXpowerissuereportedinthe2x100GDWDMOTNPIC.
PR1084963OnPTXSeriesplatform"cfp_lh_update_1sec_pm_varreceived"messagesareperiodicallyloggedwithWarninglevel.
Theseverityofthismessagehasbeenrevised.
PR108959253Copyright2016,JuniperNetworks,Inc.
KnownIssuesMPLSFromJunosOSRelease14.
1onwards,the"load-balance-label-capability"configurationstatementisintroducedtoenabletheroutertopushandpoptheload-balancinglabel,whichcausesLDPandRSVPtoadvertisetheentropylabelTLVtoneighboringrouters.
PTXSeriesroutershavethiscapability,anditisreflectedintheirdefaultforwarding-optionsconfiguration.
However,thereisasoftwaredefectinthewayEntropyLabelCapability(ELC)TLVisencodedintheLDPlabel-mappingmessage.
ItmightcausetheLDPsessionbetweenrouterstogodown.
PR1065338PlatformandInfrastructureTheMIBcounteror"showpfestatisticstraffic"showsjunkPPSandinvalidtotaltrafficoutputcounter.
PR1084515RoutingProtocolsOnshmlogunsupportedplatforms(forexample,PTXSeriesplatform),thefollowingmessagemightbeseenafteraconfigurationchange:PTX-re0rpd[42030]shmlognotinitializedforPIM-notprovisionedinplatformmanifestfile.
Themessagedoesnotindicateanerror,itjustindicatesthatshmlogisnotsupportedonthePTXSeriesplatform.
TheseverityoftheloghasbeenreducedtoINFO.
PR1065055RelatedDocumentationNewandChangedFeaturesonpage48ChangesinBehaviorandSyntaxonpage50KnownBehavioronpage51ResolvedIssuesonpage54DocumentationUpdatesonpage58Migration,Upgrade,andDowngradeInstructionsonpage59ProductCompatibilityonpage63ResolvedIssuesThissectionliststheissuesfixedinJunosOSRelease15.
1F3forthePTXSeries.
TheidentifierfollowingthedescriptionisthetrackingnumberintheJuniperNetworksProblemReport(PR)trackingsystem.
ResolvedIssues:15.
1F3onpage54ResolvedIssues:15.
1F2onpage57ResolvedIssues:15.
1F3GeneralRoutingonpage55Infrastructureonpage56InterfacesandChassisonpage56Copyright2016,JuniperNetworks,Inc.
54JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesMPLSonpage56NetworkManagementandMonitoringonpage56PlatformandInfrastructureonpage57RoutingProtocolsonpage57SoftwareInstallationandUpgradeonpage57GeneralRoutingWhenaswitchoverisdonefromoneRoutingEnginetotheother,ingraceful-switchoverredundancymode,thereisabriefperiodearlyinthetransitionoftheSIBtoonlinestate,duringwhichunsolicited(notcorrespondingtoanattemptbytheCPUtoaccesstheSIBviaPCIe)errorsarereceivedatthedownstreamPCIeportontheCBtotheSIB.
Thefixistomutethegenerationofsucherrorsduringthisbriefperiodoftheswitchover.
PR1068237Theconfiguredbuffer-sizewillnottakeeffectuntileither"transmit-rate"or"excess-rate"isconfigured.
PR1072179TunableSFP+opticsarenotsupportedonP1-PTX-24-10G-W-SFPPPICinJunosOSRelease15.
1R1.
OnTunableOpticsinthisPIC,withJunosOSRelease15.
1R1,thewavelengthwillnotbeconfigurableandthetunableparameterswillnotbecorrectlydisplayedintheCLI.
PR1081992TheFPConPTXSeriesroutermightcrashandrebootwhenthePacketForwardingEngineishandlingafatalerror.
Whentheerrorhappened,"TQCHIP0:Fatalerrorpqt_min_free_cntiszero"logmessageisseen.
PR1084259OnPTXSeriesplatformwithexternalclocksynchronizationinterfaceconfigured,whenbothBITSexternalclocksaredisconnectedatthesametime,the100GbE-LR4FINISARinterfacemightflap.
Thislinkflapissueisnarroweddowntotheoperationofdata-pathFIFOwithinCFP.
WhenboththeBITSclocksaredisconnected,thereferenceclockjumpsto"free-running"mode.
Thistransitionleadstoaphaseshiftinreferenceclock.
Duetothisphaseshift,thedataratesintoandoutoftheFIFOwilltemporarilynotmatch,leadingtoaFIFOover-runorunder-runcondition.
Thisover-runorunder-runconditionforcesaFIFOreset,andtheoutputsignalisdistorted.
Sothefar-endinterfacedetects'local-fault',thenreturns'remote-fault'backtothenear-end,hencealinkflap.
AfterchangeforthisPR:-UserneedstomanuallyconfigureFPCrecoveredclockportforeachclockputinto"chassissynchronizationsource".
-OnlyoneclockofeachFPCcanbeputinto"chassissynchronizationsource".
PR1091228OnPTXSeriesplatform,iftherearescaledconfigurations(forexample,5000routesandeachofthemwith64ECMPpathsconfigured)onasingleinterfaceandL2rewriteprofileisappliedfortheinterface,theFPCmaycrashwhendeactivatingandthenactivatingtheCoSconfigurationoftheinterface.
PR1096958OnPTXSeriesplatform,SIBtemperature-thresholdconfigurationcannotbechangedforoff-linedSIBs.
PR1097355WhenthePTXSeriesonlyhasbits-aandbits-basconfiguredclocksources(andthereisnointerfaceonFPCconfiguredasclocksouce),anditislosingsignalfrombothofbits-aandbits-bsimultaneously,clocksyncstatewillgotoFREERUNmode55Copyright2016,JuniperNetworks,Inc.
ResolvedIssuesimmediately.
Thisisunexpectedbehavior.
AfterthefixofthisPR,clocksyncstatewillstayHOLDOVER,thenwillgotoFREERUNmodeafterthetimeout.
PR1099516StartingwithJunosOSRelease14.
1,EntropyLabelCapabilityisenabledby-defaultonallJuniperNetworksPTXSeriesrouters.
OnPTXSeriestransitLSRsthatcarryLSPswithEntropyLabelCapability,packetlosscanbeobservedduetodataerrorswhenoneormorelabeledrouteentriesarenotproperlyremovedfromthehashtable(ie.
followingLSPoptimizationorMBBevent)becausethe'stale'entriesarepointingtocorruptedroutememory.
Asaresult,whentheMPLSlabelthat'sassociatedwiththe'stale'entryisre-used,dataerrorsareseenforpacketsusingthecorrespondinglabel.
PR1100637OnPTXSeriesplatform,whenyankingoutFPCorSIBungracefully(forexample,pullingthelinecardoutofthechassisunintentionallywhenthelinecardiscarryingthetraffic),theremightbesmallprobabilitythatitcanimpactanyoftheFPCswithGrantScheduler(GS)andRequestTable(RT).
Fatalinterruptoccurred.
PR1105079SupposewehavexmldplspsandAEmemberswithychildmembers.
Thenthescalesupportedis4x*yrequestsystemsnapshotNOTE:TheinstallationprocessrebuildsthefilesystemandcompletelyreinstallsJunosOS.
Configurationinformationfromtheprevioussoftwareinstallationisretained,butthecontentsoflogfilesmightbeerased.
Storedfilesontherouter,suchasconfigurationtemplatesandshellscripts(theonlyexceptionsarethejuniper.
confandsshfiles),mightberemoved.
Topreservethestoredfiles,copythemtoanothersystembeforeupgradingordowngradingtheroutingplatform.
Formoreinformation,seetheJunosOSAdministrationLibraryforRoutingDevices.
Copyright2016,JuniperNetworks,Inc.
60JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesNOTE:Werecommendthatyouupgradeallsoftwarepackagesoutofbandusingtheconsolebecausein-bandconnectionsarelostduringtheupgradeprocess.
ThedownloadandinstallationprocessforJunosOSRelease15.
1F3isdifferentfrompreviousJunosOSreleases.
1.
UsingaWebbrowser,navigatetotheAllJunosPlatformssoftwaredownloadURLontheJuniperNetworkswebpage:http://www.
juniper.
net/support/downloads/2.
SelectthenameoftheJunosOSplatformforthesoftwarethatyouwanttodownload.
3.
Selectthereleasenumber(thenumberofthesoftwareversionthatyouwanttodownload)fromtheReleasedrop-downlisttotherightoftheDownloadSoftwarepage.
4.
SelecttheSoftwaretab.
5.
IntheInstallPackagesectionoftheSoftwaretab,selectthesoftwarepackagefortherelease.
6.
LogintotheJuniperNetworksauthenticationsystemusingtheusername(generallyyoure-mailaddress)andpasswordsuppliedbyJuniperNetworksrepresentatives.
7.
ReviewandaccepttheEndUserLicenseAgreement.
8.
Downloadthesoftwaretoalocalhost.
9.
Copythesoftwaretotheroutingplatformortoyourinternalsoftwaredistributionsite.
10.
Installthenewjinstallpackageontherouter.
NOTE:AfteryouinstallaJunosOSRelease15.
1F3jinstallpackage,youcannotissuetherequestsystemsoftwarerollbackcommandtoreturntothepreviouslyinstalledsoftware.
Insteadyoumustissuetherequestsystemsoftwareaddvalidatecommandandspecifythejinstallpackagethatcorrespondstothepreviouslyinstalledsoftware.
Thevalidateoptionvalidatesthesoftwarepackageagainstthecurrentconfigurationasaprerequisitetoaddingthesoftwarepackagetoensurethattherouterrebootssuccessfully.
Thisisthedefaultbehaviorwhenthesoftwarepackagebeingaddedisadifferentrelease.
Addingtherebootcommandrebootstherouteraftertheupgradeisvalidatedandinstalled.
Whentherebootiscomplete,therouterdisplaystheloginprompt.
Theloadingprocesscantake5to10minutes.
Rebootingoccursonlyiftheupgradeissuccessful.
CustomersintheUnitedStatesandCanada,usethefollowingcommand:user@host>requestsystemsoftwareaddvalidaterebootsource/jinstall-15.
1F311-domestic-signed.
tgz61Copyright2016,JuniperNetworks,Inc.
Migration,Upgrade,andDowngradeInstructionsAllothercustomers,usethefollowingcommand:user@host>requestsystemsoftwareaddvalidaterebootsource/jinstall-15.
1F311-export-signed.
tgzReplacethesourcewithoneofthefollowingvalues:/pathname—Forasoftwarepackagethatisinstalledfromalocaldirectoryontherouter.
Forsoftwarepackagesthataredownloadedandinstalledfromaremotelocation:ftp://hostname/pathnamehttp://hostname/pathnamescp://hostname/pathname(availableonlyforCanadaandU.
S.
version)Thevalidateoptionvalidatesthesoftwarepackageagainstthecurrentconfigurationasaprerequisitetoaddingthesoftwarepackagetoensurethattherouterrebootssuccessfully.
Thisisthedefaultbehaviorwhenthesoftwarepackagebeingaddedisadifferentrelease.
Addingtherebootcommandrebootstherouteraftertheupgradeisvalidatedandinstalled.
Whentherebootiscomplete,therouterdisplaystheloginprompt.
Theloadingprocesscantake5to10minutes.
Rebootingoccursonlyiftheupgradeissuccessful.
NOTE:YouneedtoinstalltheJunosOSsoftwarepackageandhostsoftwarepackageontherouterswithRE-PTX-X8RoutingEngine.
ForupgradingthehostOSonrouterswithRE-MX-X6RoutingEngine,usethejunos-vmhost-install-x.
tgzimageandspecifythenameoftheregularpackageintherequestvmhostsoftwareaddcommand.
FormoreinformationseeVMHostInstallationtopicintheInstallationandUpgradeGuide.
NOTE:AfteryouinstallaJunosOSRelease15.
1F3jinstallpackage,youcannotissuetherequestsystemsoftwarerollbackcommandtoreturntothepreviouslyinstalledsoftware.
Insteadyoumustissuetherequestsystemsoftwareaddvalidatecommandandspecifythejinstallpackagethatcorrespondstothepreviouslyinstalledsoftware.
NOTE:MostoftheexistingrequestsystemcommandsarenotsupportedonrouterswithRE-PTX-X8RoutingEngine.
SeetheVMHostSoftwareAdministrativeCommandsintheInstallationandUpgradeGuideRelatedDocumentationNewandChangedFeaturesonpage48ChangesinBehaviorandSyntaxonpage50Copyright2016,JuniperNetworks,Inc.
62JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesKnownBehavioronpage51KnownIssuesonpage53ResolvedIssuesonpage54DocumentationUpdatesonpage58ProductCompatibilityonpage63ProductCompatibilityHardwareCompatibilityonpage63HardwareCompatibilityToobtaininformationaboutthecomponentsthataresupportedonthedevices,andspecialcompatibilityguidelineswiththerelease,seetheHardwareGuideandtheInterfaceModuleReferencefortheproduct.
TodeterminethefeaturessupportedonPTXSeriesdevicesinthisrelease,usetheJuniperNetworksFeatureExplorer,aWeb-basedapplicationthathelpsyoutoexploreandcompareJunosOSfeatureinformationtofindtherightsoftwarereleaseandhardwareplatformforyournetwork.
FindFeatureExplorerat:http://pathfinder.
juniper.
net/feature-explorer/RelatedDocumentationNewandChangedFeaturesonpage48ChangesinBehaviorandSyntaxonpage50KnownBehavioronpage51KnownIssuesonpage53ResolvedIssuesonpage54DocumentationUpdatesonpage58Migration,Upgrade,andDowngradeInstructionsonpage5963Copyright2016,JuniperNetworks,Inc.
ProductCompatibilityThird-PartyComponentsThisproductincludesthird-partycomponents.
Toobtainacompletelistofthird-partycomponents,seeOverviewforRoutingDevices.
ForalistofopensourceattributesforthisJunosOSrelease,seeOpenSource:SourceFilesandAttributions.
FindingMoreInformationForthelatest,mostcompleteinformationaboutknownandresolvedissueswithJunosOS,seetheJuniperNetworksProblemReportSearchapplicationat:http://prsearch.
juniper.
net.
JuniperNetworksFeatureExplorerisaWeb-basedapplicationthathelpsyoutoexploreandcompareJunosOSfeatureinformationtofindthecorrectsoftwarereleaseandhardwareplatformforyournetwork.
FindFeatureExplorerat:http://pathfinder.
juniper.
net/feature-explorer/.
JuniperNetworksContentExplorerisaWeb-basedapplicationthathelpsyouexploreJuniperNetworkstechnicaldocumentationbyproduct,task,andsoftwarerelease,anddownloaddocumentationinPDFformat.
FindContentExplorerat:http://www.
juniper.
net/techpubs/content-applications/content-explorer/.
DocumentationFeedbackWeencourageyoutoprovidefeedback,comments,andsuggestionssothatwecanimprovethedocumentation.
Youcanprovidefeedbackbyusingeitherofthefollowingmethods:Onlinefeedbackratingsystem—OnanypageattheJuniperNetworksTechnicalDocumentationsiteathttp://www.
juniper.
net/techpubs/index.
html,simplyclickthestarstoratethecontent,andusethepop-upformtoprovideuswithinformationaboutyourexperience.
Alternately,youcanusetheonlinefeedbackformathttp://www.
juniper.
net/techpubs/feedback/.
E-mail—Sendyourcommentstotechpubs-comments@juniper.
net.
Includethedocumentortopicname,URLorpagenumber,andsoftwareversion(ifapplicable).
Copyright2016,JuniperNetworks,Inc.
64JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeriesRequestingTechnicalSupportTechnicalproductsupportisavailablethroughtheJuniperNetworksTechnicalAssistanceCenter(JTAC).
IfyouareacustomerwithanactiveJ-CareorJNASCsupportcontract,orarecoveredunderwarranty,andneedpostsalestechnicalsupport,youcanaccessourtoolsandresourcesonlineoropenacasewithJTAC.
JTACpolicies—ForacompleteunderstandingofourJTACproceduresandpolicies,reviewtheJTACUserGuidelocatedathttp://www.
juniper.
net/us/en/local/pdf/resource-guides/7100059-en.
pdf.
Productwarranties—Forproductwarrantyinformation,visithttp://www.
juniper.
net/support/warranty/.
JTACHoursofOperation—TheJTACcentershaveresourcesavailable24hoursaday,7daysaweek,365daysayear.
Self-HelpOnlineToolsandResourcesForquickandeasyproblemresolution,JuniperNetworkshasdesignedanonlineself-serviceportalcalledtheCustomerSupportCenter(CSC)thatprovidesyouwiththefollowingfeatures:FindCSCofferings:http://www.
juniper.
net/customers/support/Searchforknownbugs:http://www2.
juniper.
net/kb/Findproductdocumentation:http://www.
juniper.
net/techpubs/FindsolutionsandanswerquestionsusingourKnowledgeBase:http://kb.
juniper.
net/Downloadthelatestversionsofsoftwareandreviewreleasenotes:http://www.
juniper.
net/customers/csc/software/Searchtechnicalbulletinsforrelevanthardwareandsoftwarenotifications:http://kb.
juniper.
net/InfoCenter/JoinandparticipateintheJuniperNetworksCommunityForum:http://www.
juniper.
net/company/communities/OpenacaseonlineintheCSCCaseManagementtool:http://www.
juniper.
net/cm/Toverifyserviceentitlementbyproductserialnumber,useourSerialNumberEntitlement(SNE)toollocatedathttps://tools.
juniper.
net/SerialNumberEntitlementSearch/.
OpeningaCasewithJTACYoucanopenacasewithJTAContheWeborbytelephone.
UsetheCaseManagementtoolintheCSCathttp://www.
juniper.
net/cm/.
Call1-888-314-JTAC(1-888-314-5822toll-freeintheUSA,Canada,andMexico).
Forinternationalordirect-dialoptionsincountrieswithouttoll-freenumbers,visitusathttp://www.
juniper.
net/support/requesting-support.
html.
65Copyright2016,JuniperNetworks,Inc.
RequestingTechnicalSupportIfyouarereportingahardwareorsoftwareproblem,issuethefollowingcommandfromtheCLIbeforecontactingsupport:user@host>requestsupportinformation|savefilenameToprovideacorefiletoJuniperNetworksforanalysis,compressthefilewiththegziputility,renamethefiletoincludeyourcompanyname,andcopyittoftp.
juniper.
net/pub/incoming.
Thensendthefilename,alongwithsoftwareversioninformation(theoutputoftheshowversioncommand)andtheconfiguration,tosupport@juniper.
net.
Fordocumentationissues,filloutthebugreportformlocatedathttps://www.
juniper.
net/cgi-bin/docbugreport/.
RevisionHistory18August2016—Revision7,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
21April2016—Revision6,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
11February2016—Revision5,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
10December2015—Revision4,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
19November2015—Revision3,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
5November2015—Revision2,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
29October2015—Revision1,JunosOSRelease15.
1F3–MXSeries,PTXSeries,andTSeries.
Copyright2016,JuniperNetworks,Inc.
Allrightsreserved.
JuniperNetworks,Junos,Steel-BeltedRadius,NetScreen,andScreenOSareregisteredtrademarksofJuniperNetworks,Inc.
intheUnitedStatesandothercountries.
TheJuniperNetworksLogo,theJunoslogo,andJunosEaretrademarksofJuniperNetworks,Inc.
Allothertrademarks,servicemarks,registeredtrademarks,orregisteredservicemarksarethepropertyoftheirrespectiveowners.
JuniperNetworksassumesnoresponsibilityforanyinaccuraciesinthisdocument.
JuniperNetworksreservestherighttochange,modify,transfer,orotherwiserevisethispublicationwithoutnotice.
Copyright2016,JuniperNetworks,Inc.
66JunosOSRelease15.
1F3fortheMXSeries,PTXSeries,andTSeries