Juniper Networks Product End-of-Life

Transcription

1 Juniper Netwrks Prduct End-f-Life Plicy & Prcedure ( EOL Plicy ) Frm time t time, Juniper Netwrks may find it necessary t discntinue prducts and services fr a number f reasns, including technlgy innvatins leading t prduct enhancements and increased functinality, changes in market demand fr the prduct, r bslescence f cmpnents used t build the prduct. EOL Ntificatins (EOLN s) When a prduct mdel reaches its End f Life (EOL), Juniper Netwrks plicy is t cmmunicating imprtant milestnes in rder t help custmers understand the impact n them f prduct end f life and understand the applicable timelines and manage the prduct transitin. This cmmunicatin is handled n a prduct-by-prduct basis via an End f Life Ntificatin (EOLN), which is a specific type f Prduct Supprt Ntificatin (PSN). EOLN s are psted at Juniper s public website. (As f the date f this plicy dcument, the site is lcated at where this plicy is als psted). The EOLN will include the critical milestne dates that will ccur in the typical prduct end f life prcess. The EOLN may als cntain ther key infrmatin pertaining t Juniper Netwrks hardware and sftware prducts, such as recmmended replacement prduct(s). Rules and milestne dates specified in the EOLN fr a particular prduct may vary frm the guidelines stated belw. Variance frm the guidelines may ccur in a variety f cases, including, amng thers, where the prduct has jined the Juniper prtfli in an acquisitin where the acquired cmpany had a materially different end-f-life plicy. Nthing in this EOL Plicy shuld be cnstrued as a repudiatin f any cntractual cmmitment Juniper has made regarding end-f-life fr particular prducts r custmers. As always, a custmer s right t supprt services f any kind is cntingent upn that custmer s having a valid, unexpired supprt service cntract purchased frm Juniper Netwrks r frm a Juniper-authrized reseller r Supprt Services Specialist. EOL Guidelines Hardware Prducts and their Operating System sftware The EOLN fr any hardware prduct generally includes the fllwing infrmatin. 1. Ntificatin Date: The Ntificatin Date is the date f the EOLN. 2. LOD - Last Order Date: Typical Timing f LOD: Apprximately 180 days after date f the EOLN. Effect f LOD: Prducts: LOD is the last date n which purchase rders may be placed fr the affected prduct(s) and fr new supprt services cntracts fr thse prducts. Juniper Netwrks, Inc. 1

2 Juniper Netwrks Prduct End-f-Life Plicy & Prcedure June 2018 New Supprt Services Cntracts: After LOD, n further new cntracts fr supprt services fr the affected prduct(s) will be sld. Exceptin: Where a prduct warranty lapses after the LOD, then new supprt cntracts fr that prduct may nly be purchased fr a perid cmmencing prir t the earlier f (i) the warranty lapse date, and (ii) lapse f 12 mnths after the LOD. Supprt Cntract renewals: Custmers may purchase supprt cntract renewals after the LOD, but nly if renewal perid cmmences n the date the existing supprt cntract perid expires. In ther wrds, pst-lod, n renewal is available after a lapse f supprt service cverage. Supprt Cntract upgrades: Custmers may NOT upgrade supprt cntract levels after LOD, regardless f whether the upgrade is sught in mid cntract term r n renewal f the cntract. Fr example, after LOD, a Cre cntract may nt be upgraded t Cre Plus, Next Day r Same Day, Reinstatements: N reinstatement f supprt services cntracts will be allwed after LOD date. 3. LSV Last Sftware Versin. The Last Sftware Versin fr a prduct is the last Versin 1 f perating system sftware that will supprt the affected hardware prduct. 4. EOSE - End f Sftware Engineering supprt date. Typical Timing f EOSE: Three (3) years after LOD f the affected hardware prduct. Effect f EOSE. EOSE is the date after which Juniper is n lnger cmmitted t furnish Sftware Engineering level supprt fr the perating system sftware licensed fr the affected hardware. This means that n further Releases 1 (e.g. service r maintenance releases r patches) will be created fr the supprt f the affected hardware prduct. JTAC supprt will generally be limited t investigatin and trubleshting in an attempt t prvide slutins, cnfiguratin guidelines and wrkarunds. Additinal guidelines regarding Release EOSE fr Releases under a particular Versin f sftware prducts, including perating system sftware fr hardware prducts, are described in the sectin entitled Sftware Releases under a Particular Versin under Other EOL Rules and Guidelines belw. 5. EOHE - End f Hardware Engineering supprt date: Typical Timing f EOHE. Three (3) years after LOD. Effect f EOHE. After EOHE Juniper has n cmmitment t perfrm hardware engineering level supprt (including hardware mdificatins and hardware failure analysis) fr hardware defects. Frm EOSE date until End f Supprt ( EOS ) date (defined in item 7, belw), Hardware Replacement and Repair services will remain in place subject t partial phase-ut in accrdance with the guidelines set frth in the sectin entitled Special Guidelines fr RMA Hardware Repair/Replacement Service Level 1 A Release, is a particular image issued under a particular Versin. Fr example, Juns 12.2R1 thrugh Juns 12.2R8 are all Releases under the same Versin 12.2, whereas Juns 12.2R1 and Juns 12.3R1 are Releases under different Versins. Juniper Netwrks, Inc. 2

3 Juniper Netwrks Prduct End-f-Life Plicy & Prcedure June 2018 Availability under Other EOL Rules and Guidelines belw. 6. LRD Last Renewal Date. Typical Timing f LRD. Fur (4) years after LOD. Effect f LRD. After LRD, Juniper will nt allw renewal f any supprt services cntract fr the affected prduct. In ther wrds, if a supprt cntract term lapses after the LRD, n further renewal f the supprt cntract will nrmally be granted. In any event Juniper will nt furnish supprt services after EOS (defined belw), regardless f the stated term f the supprt services cntract. 7. EOS - End f Supprt date Typical Timing f EOS. Five (5) years after LOD. Effect f EOS. After EOS, Juniper will nt be under bligatin t perfrm supprt services f any kind fr the affected hardware r the embedded perating system sftware supprting the affected prduct. Other EOL Rules and Guidelines 1. Special Guidelines fr RMA Hardware Repair/Replacement Service Level Availability Fr a prduct part number that has an EOL/LOD date prir t June 1 st 2018, the fllwing plicy applies subject t different terms specified in the applicable EOLN: RTF (Return-t-Factry) supprt generally is available until EOS. Juniper s cmmitment t furnish Same Day and Same Day Onsite replacement services generally ends tw (2) years after LOD. Juniper s cmmitment t furnish Next Day, Next Day Ship and Next Day Onsite supprt services generally ends fur (4) years after LOD. Juniper s cmmitment t furnish AR-5 repair/replacement service level t Supprt Services Specialists under PAR-type service cntracts generally ends n EOS date. If a custmer has purchased a RMA repair/replacement service level that is discntinued under this EOL plicy, the custmer shall be affrded service at the highest service level still available. Fr a prduct part number that has an EOL/LOD date n r after June 1 st 2018, the fllwing plicy applies subject t different terms specified in the applicable EOLN: RTF (Return-t-Factry), Next Day, Next Day Onsite, Same Day, Same Day Onsite, and AR-5 service levels are available until EOS. 2. Sftware Releases under a particular Versin. (This sectin cvers BOTH embedded perating system sftware fr Juniper hardware prducts AND applicatin sftware prducts hwever licensed.) A Versin is a series f Releases f a particular sftware prduct with a cmmn x.y denminatin in the first tw places f the Release identifier. A Release, n the ther hand, is a particular image issued under a particular Versin. Fr example, Juns 12.2R1 thrugh Juns 12.2R8 are all Releases under the same Versin Juniper Netwrks, Inc. 3

4 Juniper Netwrks Prduct End-f-Life Plicy & Prcedure June , whereas Juns 12.2R1 and Juns 12.3R1 are Releases under different Versins. Releases within a particular Versin generally have cmmn features and functinality. The fllwing guidelines gvern EOSE and EOS fr the sftware Releases under any particular Versin ( Release EOSE and Release EOS, respectively). End f life milestne deadlines fr Releases are nt triggered by an EOLN. Instead, a prduct-specific Prcess Supprt Ntificatin psted n Juniper s public website at r befre general availability f the first Release under the applicable sftware Versin will specify rules fr Release EOSE and Release EOS. Juniper may mdify thse rules frm time t time by psting n its public website. End-f-Life milestnes fr Releases under ne Versin d nt affect supprt cmmitments relating t Releases fr ther Versins. Typical Timing f Release EOSE. EOSE fr Releases under a particular Versin generally ranges between 9 and 36 mnths after first general availability f the initial Release under that Versin. Effect f Release EOSE. After Release EOSE Juniper will nt be under bligatin t perfrm any further sftware fixes, cde changes. N further Releases will be develped r distributed fr that Versin. Typical Timing f Release EOS. Release EOS fr Releases under a particular Versin generally ranges between 6 and 12 mnths after the EOSE date fr that Versin. Effect f Release EOS. After Release EOS Juniper will nt be under bligatin t perfrm supprt services f any kind fr any Releases under the applicable Versin. Juniper will nt be under any bligatin t keep any such Releases available fr dwnlad after Release EOS. 3. Field Replaceable Units Effect f Chassis-based EOLN n FRUs - General Rule: Subject t the paragraphs belw in this Sectin 3, the lifecycle f Field Replaceable Units (FRUs) (e.g. Physical Interface Card (PIC), Flexible PIC Cncentratr (FPC), line cards, pwer supplies and fan trays) fllw that f the chassis in which they are installed, except as expressly stated in the paragraphs belw. In ther wrds, an EOLN fr a chassis generally applies t the FRUs installed in that chassis. All aspects f the EOL plicy (LOD, EOHE, EOSE, etc.) apply t thse FRUs as installed in thse chassis as f LOD. All FRUs in the chassis will be supprted at the same service delivery level as the chassis. i. Effect f Chassis-based EOLN n FRU s supprting multiple chassis: Often, FRUs are sld fr use nt nly in the EOL d chassis, but in ne r mre additinal chassis that are NOT subject t any EOLN. In that case, thse FRUs will remain available fr purchase fr use in thse additinal chassis. Fr thse FRU s installed in nn-eol d chassis, supprt services will remain fully available. Effect f FRU-based EOLN: A FRU may be the subject f its wn separate EOLN. In that case, EOLN fr that FRU shall dictate the EOL milestnes fr that FRU. If the FRU and the chassis in which it is designed fr use are each under separate EOLN s, then in the case f incnsistency between milestnes and milestne dates, the earlier f the cnflicting milestne date will take precedence with respect t the FRU. Juniper Netwrks, Inc. 4

5 Special Repair/Replacement Rules fr FRU s subject t FRU-based r Chassis-based EOLN: After LOD fr a FRU, in lieu f repairing r replacing an RMA d defective FRU with a same mdel (that is, same SKU #) Juniper may (but is nt bliged t) replace the RMA d FRU with a new r refurbished FRU with substantially similar functinality t that f the RMA d FRU. Juniper Netwrks reserves the right t charge custmer the price difference fr the replacement FRU if the replacement FRU prvides significant imprvements t perfrmance, capability r capacity ver that f the defective FRU. Furthermre, use f any such replacement FRU may require that custmer install a different sftware Release r Versin than that currently used by the custmer, and als may require that the custmer purchase peripheral enhancements t render the enhanced FRU fully functinal. If the affected FRU is replaced by a similar versin, the replaced FRU will be cvered by the existing supprt services cntract. Transitin Rules and Mdificatins f EOL Plicy This revisin f the End-f-Life Plicy and Prcedures takes effect n psting at Juniper s public website, subject t the fllwing exceptins and limitatins: i. This revisin shall nt affect express prduct end-f-life cmmitments under valid, unexpired written agreements t the extent thse cmmitments are incnsistent with the End-f-Life Plicy. ii. This revisin shall nt affect Juniper s End-f-Life cmmitments with respect t prduct fr which Juniper has already issued an EOLN prir t the psting f this revisin. iii. Finally, this End-f-Life Plicy and Prcedure revisin shall nt affect Juniper s bligatins under the current term f any services cntract that has been rdered and accepted prir t the psting f this revisin. As prvided in Juniper s End User Supprt Agreement, Juniper may at any time further mdify this End-f-Life Plicy and Prcedure by psting a new revisin n the Juniper public website; prvided, hwever, that n such mdificatin shall affect the Juniper Netwrks bligatins under the then-current term f any Juniper Netwrks Services Cntract rdered and accepted prir t the effective date f such mdificatin. Abut Juniper Netwrks Juniper Netwrks is in the business f netwrk innvatin. Frm devices t data centers, frm cnsumers t clud prviders, Juniper Netwrks delivers the sftware, silicn and systems that transfrm the experience and ecnmics f netwrking. The cmpany serves custmers and partners wrldwide. Additinal infrmatin can be fund at Crprate and Sales Headquarters Juniper Netwrks, Inc Nrth Mathilda Avenue Sunnyvale, CA USA Phne: 888.JUNIPER ( ) r Fax: APAC and EMEA Headquarters Juniper Netwrks Internatinal B.V. Being Avenue PZ Schiphl-Rijk Amsterdam, The Netherlands Phne: Fax: T purchase Juniper Netwrks slutins, please cntact yur Juniper Netwrks representative at r authrized reseller Cpyright 2015 Juniper Netwrks, Inc. All rights reserved. Juniper Netwrks, the Juniper Netwrks lg, Juns, NetScreen, and ScreenOS are registered trademarks f Juniper Netwrks, Inc. in the United States and ther cuntries. All ther trademarks, service marks, registered marks, r registered service marks are the prperty f their respective wners. Juniper Netwrks assumes n respnsibility fr any inaccuracies in this dcument. Juniper Netwrks reserves the right t change, mdify, transfer, r therwise revise this publicatin withut ntice June 1 st 2018 Juniper Netwrks, Inc. 5