HP's UNIX Patch Strategy: Moving From Tru64 To HP-UX

1y ago
16 Views
2 Downloads
3.76 MB
48 Pages
Last View : 11d ago
Last Download : 3m ago
Upload by : Ophelia Arruda
Transcription

HP's UNIX PatchStrategy: Movingfrom Tru64 to HP-UXBruce HendersonHP-UX Patch Program ManagerHewlett-Packard 2004 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

Agenda1. Industry Wide Software Patching2. HP-UX Patch Strategy Overview3. HP UNIX Patching Comparison Tru64 and HP-UX2

Industry Wide SoftwarePatching

Industry WideCustomer Patching PracticesCustomer behavior varies greatly Some install changes suggested by vendor Others avoid any changes (except fixes to bugsthey have reported) Many prefer to make their own decisions aboutwhich releases and upgrades they adoptTypical to install a patch tentatively to analyze impactbefore committing as permanent part of OS4

Industry Wide - Best in Class Defect Density11i has 23.5K Function Pts, compared to industry data for 10KDelivered Defects/Function 0.2000.1350.1000.0600.0330.0150.000Avg All VendorsAvg SystemVendorsTop 1%11.0011iIBM MFApplied Software Measurement, 2nd Edition, Capers Jones5

HP-UX 11i versus Solaris 8, AIX 5.1First 15 months of shipments3500300025002000H P- U X 1 1 i1500So la ris 8**1000AIX 5 .15000Pa tche sD efe cts** Could not get AIX 5.1 defect data6

HP-UX Patch Strategy Overview

“The patch-management field has been aconservative one, slow to change. D.H.Brown Associates, Inc. (DHBA) believesthat innovation of the kind describedhere is long overdue.”White Paper: HP Improves Patch Management to Reduce SystemDowntimeD.H. Brown Associates, Inc. , March 2000

HP-UX Patch Strategy OverviewHow did HP-UX get there?9

HP-UX Patch Strategy OverviewCustomer Patch RequirementsMinimize down time for patch operationsTo provide the most stable environment possible, I want to choose exactly whichpatches I apply.Particularly in the kernel and other sensitive areas, keeppatches small.Patches should only be fixes to defects, not enhancements.Minimize system administration costBut keep patch management simple – I don’t want tospend a lot of time here.Provide me with tools to manage multiple systems – trackwhat is installed, install a golden image on multiplesystems, etc.10

HP-UX Patch Strategy OverviewKey Improvements1.Label Patches with our confidence rating 1,2 or 3 Rating 1 has gone through all labs testsRating 2 has significant customer exposure (60% fewerwarnings)Rating 3 has passed our system tests (80% fewer warnings)2.Keep patches as small as possible, but they must becumulative from the last patch.3.Use bundles to simplify proactive patch management QPK4.Enhancements can only be delivered in patches ifthey enable new hardware or add compatible minorfeatures.11

HP-UX Patch Strategy OverviewTypes of HP-UX 11iv1 Patches32% Deliver EnhancementsSW enable20%HW enable12%Core defect57%App Defect11%Software enablement includes IPV6, Virtual partitions, Processor Sets, InterruptMigration, and Compressed DumpContents of SWPack, and Support Plus – 421 total patches12

HP-UX Patch Strategy OverviewKey Improvements5.Provide more robust patch management tools andprocesses IT Resource Center (ITRC) Recommendations based upon patch ratingsComplete dependency managementNew patch assessment capability “Ideal system” concept incorporation of patch sets combination of internal and external tools removal of entitlement requirement “HP Live” access to patch support expertsMission Critical Software Change Management (MCSCM)13

HP-UX Patch Strategy OverviewReactive and Proactive PatchingReactive Patching Solve an existingproblem Timeliness: Highest priorityReliability: Fix it the first timeChange: MinimizeRisk: Fast delivery of fix maycompromise testingFind the Best patch to fix theproblem, as quickly aspossible.Proactive Patching Preventivemaintenance Reliability: Highest priority. Useonly most stable tested patches Timeliness : Periodic activity,planned in advance, time allottedfor testing Change: Understand and evaluate Risk: Larger changes introducegreater risk, however, risk isreduced by more testing.Choose a period for proactive patching.Use standard HP recommendedsources.Timeliness vs. Risk14

HP-UX Patch Strategy OverviewSummary HP Patch strategy allows many options Small patches in most sensitive areas for reactive patchingPatch bundles for proactive patchingCustomer choice on how frequently to patch and what to patchLevels of confidence in patches (lower risk) based on customer usageand HP testing. Proactive notification of any problem patches, but most customersremove very few of them.15

HP UNIX Patching Comparison

HP UNIX patching comparisonScopeTru64Core (OS) patchesHP-UXCore patchesApplication patches17

HP UNIX patching comparisonIndividual patchesTru64HP-UXCSP (Customer SpecificPatch)Site SpecificNo equivalentGR0 (controlled release)ERP (Early Release Patch)patches are equivalent toGR at levels 2 & 3.GR (General Release)patches at level 1-3 1 – Initial release 2 – Widely distributed &used 3 – Greatest amount oftesting18

HP UNIX patching comparisonPatch InstallationSW Package InstallerTru64dupatch Install and remove all orselected patches (-install, delete)View the patch-specificdocumentation (-help)View patch tracking information(-track)Establish a baseline forsystems that have hadmanually installed system filesplaced on themNo equivalent to addingpatches to a depotHP-UXSD – SW Distributor Install and remove selectedpatches (swinstall,swremove)No equivalent to view patchspecific documentationView patch trackinginformation (swlist)No equivalent to establish abaselineAdding patches to a depot(swcopy)Network support19

HP UNIX patching comparisonPatch InstallationInstall and remove all or selected patches.Tru64dupatchHP-UXSD – SW Distributor–––Cluster awarePatch applicabilityPatch dependencies ––Patch removal, rollbackSystem inventory changes forpatchesCapturing patch activities inlog files – No knowledge of clustersPatch applicabilityPatch dependencies(11.11)Patch removal, rollbackSystem inventory changesfor patchesCapturing patch activitiesin log filesCombined product patchinstalls20

HP UNIX patching comparisonPatch InstallationViewing the Patch DocumentationTru64Select the PatchDocumentation item of themain menu,displays: Problem summariesFull descriptionsSpecial InstructionsReport identifiersRevision control stringsHP-UX1. Retrieve individual patchesusing ITRC, it displays: One line descriptionSymptomsDefect descriptionPatch filesSpecial Installation InstructionsOther information fields for Analysis SelectionSome patch documentation in theITRC can be updated after the patchis released.2. Swlist (SD) can view the original,embedded patch documentation.21

HP UNIX patching comparisonPatch InstallationCold Install OptionsHP-UXTru64 Remote installationservice (RIS) curses (text menu) pull only not integrated with cloning Install - GUI interface1. Collection of command line,RIS, and sysmon sub-menusIgnite-UX graphical & commandlinepush or pulldesigned for cloningInstall - GUIinterface1. Ignite-ux2. Integrated with SD22

HP UNIX patching comparisonPatch InstallationSW cloning modelHP-UXTru64Installation cloning Can create definition text filesto be read by installationengine to customize thesystem being installedIgnite-UX server “configfiles” Allows definition ofconfiguration options to be setas well as softwarecomponents to be loaded onclientGolden image/OS archive Mechanism to create a tarball of a system’s installationimage for re-installation orcloning23

HP UNIX patching comparisonPatch InstallationSW Update - MigrationHP-UXTru64InstallupdateSame functionsupdate-ux performs updatepreparation stepsexecutes swinstallselection & analysis of swto loadSW load & rebootClean up old information24

HP UNIX patching comparisonPatch InstallationPatch management on clustersTru64 Rolling Patch No-Roll PatchHP-UX No Equivalent – until11i Version 325

HP UNIX patching comparisonCollections of patches1. Tested together2. Delivered together3. Intended to be installed together26

HP UNIX patching comparisonCollections of patchesTru64HP-UXKitsBundlesBy base level, for designated OSstreamsPer OS stream for all currentlysupported EnterprisereleasesDefect Fixes Inaugural/Aggregate kits One kit per supported release One milestone CD containing alllatest base level kits Support for current kit and one back Guaranteed 1 year minimum supporton 5.1B-1 forward. IPK:Inaugural kit released at 6 weeks PKn: Aggregate kits released at 4-6month intervals based upon businessneedDefect Fixes QPK (Quality Pack)One bundle per OS versionShare Support Plus CDNo support restriction onprevious bundle version First bundle approximately 6months after release Subsequent bundles at 6month intervals27

HP UNIX patching comparisonKits Tru64Collections ofpatchesNew Core SW featuresBundles New Hardware NHD (New Hardware Device)for those requiring boot support Layered ProductsNew Hardware HWE (Hardware Enablement) Layered Products bysegment APCD (Associated ProductsCD)New Core SW features SPK (SW Pack) No equivalent HP-UXApplication Products bysegment OE (Operating Environment)Products Application Products AR (Application Release) Software Product Library28

Tru64 – standard kits29

HP-UX – standard patch bundles30

HP UNIX patching comparisonWhat is Factory Installed?Tru64Factory InstalledSoftware (FIS)1. Selected OS version2. Latest NHD3. Latest Aggregate Patch KitHP-UXFactory Ignition (IUX)1. Selected OE2. Latest HWE3. Latest QPK31

HP UNIX patching comparisonWeb servicesTru64HP-UXITRCITRC PatchDB PatchDB (all GR patches)Initially Aggregate patchkits, in the future: NHD’sand individual ERPs No equivalent CPMsupport.compaq.com Previously for Aggregatekits Has been replaced withITRC CPM (Custom PatchManager), Now PatchAssessmentsoftware.hp.com Latest version of all bundles32

ITRC Patch Database Homepage33

HP-UX Patch Strategy OverviewFor a specific fix not contained in the bundle – use the ITRC34

HP-UX Patch Strategy OverviewThe ITRC manages dependenciesPatch I askedforDependenciesOn 11i, the Software Distributor product also will warn whendependencies are not satisfied35

Find patches for a productpatches for a specified product;includes all operating systems36

HP-UX Patch AssessmentLoad systeminformationCreate profile or useexisting profileexecute theassessment37

HP-UX Patch AssessmentSetup the profile38

Find HP-UX patches in a patch setsame patch sets as found inpatch assessment profile39

HP-UX Patch Assessment - resultsChat live with anHP supportspecialistpatchrecommendationreason forrecommendation40

Tru64 Kits/ERPs/NHDs on ITRC41

Tru64 – patch browsing42

HP UNIX patching comparisonSW Support Guidelines Tru64Patches provided oncurrent kit or 1 backonly for releasesunder standardsupportGuaranteed 1 yearminimum support on5.1B-1 forwardNo specific supportlevel will be required HP-UXAll patches arecumulative customers notrequired to install aminimum supportedlevel of sw to obtainpatchesSpecific support levelno longer required toaccess toCPM/PatchAssessment43

HP UNIX patching comparisonTru64 Patch Kit Support PoliciesPrevious Policy For releases under standardsupport, Tru64 UNIXEngineering supports the latestpatch kit and one (1) back.New Policy For releases under standardsupport, Tru64 UNIX Engineeringsupports the latest patch kit andone (1) back. (No change forreleases or patch kits prior toV5.1B-1(Vail)). In addition, starting with V5.1B-1(Vail) patch kits will be supportedfor a minimum of one (1) year aftertheir release. Support for the latestpatch kit and one (1) back AND theminimum of one (1) year from thetime of release are both guaranteesfor V5.1B patch kits and V5.1-Bassociated updates (V5.1B-1,V5.1B-2, etc.) only.44

HP’s UNIX Patch StrategyWhen You do Move to HP-UXWhat is the Right Approach?Scheduled,norm alm aintenanceon yoursystembackupsystemNewSystem hBase?yesGo toAcquiring andInstalling theQuality Patchand HardwareEnablem entBundlesNeed to addindividualpatches?st heisEa proacApyesGo toAcquiring andInstallingIndividualPatchesrexMo mpleConoAddingnewHardwareto YourSystem ?Best Practice45

HP’s UNIX Patch StrategySummaryHP has track record of innovation Listening to our customersResponding with improved solutions46

Co-produced by:

HP-UX Patch Strategy Overview Key Improvements 5. Provide more robust patch management tools and processes IT Resource Center (ITRC) Recommendations based upon patch ratings Complete dependency management New patch assessment capability "Ideal system" concept incorporation of patch sets

Related Documents:

Unix 101: Introduction to UNIX (i.e. Unix for Windows Users) Mark Kegel September 7, 2005 1 Introduction to UNIX (i.e. Unix for Windows Users) The cold hard truth · this course is NOT sponsored by the CS dept. · you will not receive any credit at all introduce ourselv

P a t c h M a n a g e m e n t 157 Chapter 5 - Patch Management Sadjadi et al. Chapter 5 - Patch Management 8. Missing Manual: The number of approved patches missing that must be installed manually.These patches cannot be processed by Patch Management Automatic Update, Patch Management Initial Update, Patch Management Machine Update, or Patch Management Patch Update.

HP-UX Patch Strategy Overview Key Improvements 5. Provide more robust patch management tools and processes - IT Resource Center (ITRC) Recommendations based upon patch ratings Complete dependency management New patch assessment capability - "Ideal system" concept - incorporation of patch sets - combination of internal .

UNIX and POSIX APIs: The POSIX APIs, The UNIX and POSIX Development Environment, API Common Characteristics. UNIT – 2 6 Hours UNIX Files: File Types, The UNIX and POSIX File System, The UNIX and POSIX File Attributes, Inodes in UNIX

PATCH PANEL LABELS A patch panel is a device or unit featuring a number of jacks, usually of the same or similar type, for the connecting and routing of circuits for monitoring, interconnecting, and testing circuits. Patch panels are commonly used in computer networking, recording studios, radio and television.File Size: 2MBPage Count: 9Explore furtherHow to Troubleshoot Patch Panel Connections?www.fiber-optic-transceiver-mo How to Label Patch Cables - YouTubewww.youtube.comProper Cable Labeling Guidelines FS Communitycommunity.fs.comWhat's a reliable way to test patch panel . - Server Faultserverfault.comPatch panel and cabling documentation - Cisco Communitycommunity.cisco.comRecommended to you b

Unix was originally developed in 1969 by a group of AT&T employees Ken Thompson, Dennis Ritchie, Douglas McIlroy, and Joe Ossanna at Bell Labs. There are various Unix variants available in the market. Solaris Unix, AIX, HP Unix and BSD are a few examples. Linux is also a flavor of Unix which is freely available.

This is a standard UNIX command interview question asked by everybody and I guess everybody knows its answer as well. By using nslookup command in UNIX, you can read more about Convert IP Address to hostname in Unix here. I hope this UNIX command interview questions and answers would be useful for quick glance before going for any UNIX or Java job interview.

The mission of The American Board of Radiology is to serve patients, the public, and the medical profession by certifying that its diplomates have acquired, demonstrated, and maintained a requisite standard of knowledge, skill and understanding essential to the practice of diagnostic radiology, radiation oncology and radiologic physics Six Competencies 1. Professional & Medical Knowledge 2 .