BMC项目的管理方法

1、BMC项目的管理方法Module ObjectivesDescribe the phases of an implementation projectPlan the implementation process2Lesson 1: Phases of Implementation ObjectivesOverview of the implementation projectDescribe the phases of an implementation project4Overview of the Implementation ProjectDesign and PlanDeployBu

2、ild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 55Phase 1 Design and PlanIdentify business processes and prioritiesIdentify applications that support the business processes, transfer prioritiesIdentify systems where various applications reside, include dep

3、endencies, and transfer prioritiesDesign management processes, include tools and responsibilitiesUnderstand organizational constraintsUnderstand the technical environmentDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5Design and Plan6Phase 2 Build

4、 and Test PrototypeInstall Agents on systems with applications that best represent the target environmentInstall PATROL ConsolesLearn how to use the toolsDevelop configuration prototypesDevelop any new Knowledge Modules (KMs) for un-instrumented applicationsDesign and PlanDeployBuild and Test Protot

5、ypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 57Phase 3 DeployInstall the BMC Distribution Server (DS)Install the DS ClientsCreate installation packagesInstall production AgentsInstall KMsStart the Agents automaticallyVerify “vanilla” systems are operationalDeploy custom K

6、MsDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 58Phase 4 ConfigureConfigure PATROL AgentsParameters onThresholds offAgent operational parametersAccess and securitySet up console Access Control Lists (ACLs)Set up aliases/impersonat

7、ions to match Agent ACLs Set up event/alert managementDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 59Phase 5 Test, Improve, and MaintainPhase 5 lasts FOREVER! Your steady state processes are executingDuring this phase:Measure your

8、 processes Make improvementsLook for ways to improveDesign and PlanDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 510Lesson 2: Planning the ImplementationObjectivesPlan the implementation processAnalyze requirementsDefine a design solutionPerform

9、a physical mapping of the proposed design solution for different serversDefine an implementation plan12Planning the Implementation ProcessAnalysisLogical designPhysical mappingImplementation planDeployBuild and Test PrototypeConfigureTest, Improve, and MaintainPhase 1Phase 2Phase 3Phase 4Phase 5Desi

10、gn and Plan13AnalysisIdentify project stakeholdersDiagram the enterprise to be managed by BMC Performance Manager ConsoleCollect and record high-level sizing data for each management domain14Project StakeholdersIdentify the people directly involved with:Initial deployment and installation of BMC Per

11、formance Manager ConsoleBMC Performance Manager Console manages node configuration and change managementOngoing user management, availability, and performance of PATROL Central infrastructureHandling events and exception conditions raised by BMC Performance Manager Console15Diagram the EnterpriseInt

12、ernet / WANFirewallFirewallFirewallHoustonNew YorkAustin100 Mbps (all)T1 (all)IT OPS3 PC Windows users500 managed nodesSecondary IT OPS3 PC Windows users2 PC Web users40 managed nodes400 managed nodes2 causal PC Web usersMainCore, Inc. Enterprise16Location AnalysisPATROL Location Analysis WorksheetL

13、ocation Name: HoustonIs this location isolated by a network firewall? YesSpeed and reliability of LAN/WAN connectivity to this location: T1, reliableManaged Node InformationNumber of managed nodes at this location: 500KMs to be used at this location:1. KM for UNIX6.2. KM for Windows7.3. KM for Oracl

14、e8.4. KM for Event Management9.5. KM for MS Exchange (2 servers)10.17Location Analysis (Continued)Additional Infrastructure ServicesWill BMC Performance Manager Reporting aggregate data from managed nodes at this location? YesWill PATROL Agents at this location forward events to an event management

15、tool? YesIf so, indicate which event management tool: PATROL Enterprise ManagerVisualization InformationTypical number of KMs used on each managed node: 3 (OS, Oracle, KM for EM)Typical number of managed objects on each managed node: 1800 (2 * 900)Number of PATROL Central Operator Microsoft Windows

16、Edition consoles: 3Number of PATROL Central Operator Web Edition users (daily / infrequently): 0Number of concurrent PATROL Central Operator console sessions: 3Typical number of managed nodes in each Management Profile: 80Will Management Profiles include nodes at other locations? YesIf so, indicate

17、which other locations: Austin, New YorkTypical number of managed objects in each Management Profile: 144.000 (1800 * 80)Estimated total number of concurrent managed objects: 432.000 (144.000 * 3)18Location Analysis (Continued)19Analysis ToolsStakeholder Roster WorksheetStakeholder Roster Worksheet.d

18、ocLocation Analysis WorksheetPATROL Location Analysis Worksheet.doc20Logical DesignLocation of PATROL Central infrastructure servicesNumber of services needed21RTcloud Logical DesignAgent Cloud500 managed nodesRTserverRTserver Console CloudConsole ServerRTserverRTserverPCWebBrowser UsersPCWin UsersM

19、ainCore, Inc. Houston Location22RTserver Design ConsiderationsDesign a self-contained RTcloud for each location with 50 or more managed nodesNo RTcloud should include more than 500-700 managed nodesTypically, an RTcloud will need no more than two RTservers (a primary and a backup)RTservers should be

20、 geographically close to the client computers they supportPlace RTservers on the same side of a firewall as their connected clients23RTserver Design Considerations (Continued)24RTserver Design Considerations (Continued)25Visualization DesignWhich PATROL Central console is appropriate?Which locations

21、 need PATROL Console Servers?Is one PATROL Console Server enough?26Which PATROL Central Console is Appropriate?PATROL Central Operator Microsoft Windows EditionVisualize larger numbers of managed nodesPATROL Central Operator Web EditionNo more than 200 managed nodesLimit profiles to fewer than 100 m

22、anaged nodes27Which Locations Need PATROL Console Servers?Location with the highest concentration of managed nodesLocation with console users28Which Locations Need PATROL Console Servers? (Continued)29Is One PATROL Console Server Enough?Number of concurrent console sessionsMax. 25 (32-bit)Max. 100 (

23、64-bit)Number of managed objects in concurrent Management ProfilesMax. 3 million (32-bit)Max. 10 million (64-bit)30Is One PATROL Console Server Enough? (Continued)31PATROL Console Server Failover ConsiderationsTwo ways to provide redundancyInstall on high-availability cluster hardwareStore the confi

24、guration files on a shared diskDefine a cluster failover packageInstall a secondary PATROL Console Server on a separate nodeUse the online backup feature to periodically snapshot data from the primary PATROL Console Server32PATROL Console Server Failover Considerations (Continued)33PATROL Central Op

25、erator Web Edition PlacementInstall PATROL Central Operator Web Edition on the same node as the PATROL Console ServerAllow no more than 20 concurrent browser sessionsOnly one instance of PATROL Central Operator Web Edition may be installed on any single node34Visualization Performance Considerations

26、PATROL Agent managed nodes should always be configured to preload the KMs used to manage themProduction managed nodes should be configured to run only preloaded KMs35Visualization Performance Considerations (Continued)36Centralized Customization ManagementThe PATROL Configuration Manager (PCM) is a

27、GUI-based tool used to define and distribute BMC Performance Manager Console configuration settings from a central location to some or all managed nodes.The PCM can be used to manage configuration options, such as:Preloading KMsPoll timesDisabling selected application classes37Centralized Customizat

28、ion Management (Continued)38Designing for BPM Console Management/Upgrade/PatchingUse PATROL Infrastructure Monitor to ensure the health of PATROL Central infrastructureUse the DS to centralize BMC Performance Manager Console deployment to managed nodes39Designing for BPM Console Management/Upgrade/P

29、atching (Continued)40Physical MappingAssign PATROL Central infrastructure components to specific servers41Single Server EnvironmentsSingle server hostingAn RTserverPATROL Console ServerPATROL Central Operator Web EditionManage an environment of up to 3 million managed objects in a single RTcloud (wi

30、th no more than 700 Agents)42Single Server RequirementsSmall Single-Server(Up to 500,000 managed objects)ResourceRecommendationProcessorLinux and Windows Dual Processor Intel Pentium III at 800 MHzSolaris Dual Processor SUN 420R UltraSPARC II at 450 MHzAIX Dual Processor IBM pSeries POWER 3 II at 37

31、5 MHzServer Memory1 GBDisk Space300 MBMedium Single-Server(Up to 3 million managed objects)ResourceRecommendationProcessorLinux and Windows Quad Processor Intel Pentium III at 900 MHzSolaris Quad Processor SUN V480/880 at 900 MHzAIX Quad Processor IBM pSeries POWER 4 at 1000 MHzServer Memory4 GBDisk

32、 Space2 GB43RTserver HardwareOne RTserver(Up to 750 RTclients)ResourceRecommendationProcessorLinux and Windows Single Processor Intel Pentium 4 at 1.4 GHzSolaris Single Processor SUN UltraSPARC IIe at 500 MHzAIX Single Processor IBM pSeries POWER 3-II at 500 MHzServer Memory1 GBDisk Space300 MBTwo t

33、o Four RTservers(Up to 2000 total RTclients)ResourceRecommendationProcessorLinux Dual Processor / Intel Pentium 4 at 1400 MHz Solaris Single Processor / SUN V210 UltraSPARC IIIi at 1 GHz or Dual Processor / SUN 280R UltraSPARC III at 750 MHzAIX Single Processor / IBM pSeries POWER 4 at 1200 MHz or D

34、ual Processor / IBM pSeries POWER 3 II at 375 MHzWindows No more than two RTserversServer Memory1 GBDisk Space300 MB44PATROL Console Server HardwareMedium PATROL Console Server(Up to 3 million managed objects)ResourceRecommendationProcessorLinux and Windows Dual Processor Intel Pentium 4 at 2000 MHz

35、Solaris Dual Processor SUN V240 UltraSPARC IIIi at 1 GHzAIX Dual Processor IBM pSeries POWER 4 at 1200 MHzServer Memory4 GBDisk Space2 GBLarge PATROL Console Server(Up to 10 million managed objects)ResourceRecommendationProcessorLinux Quad Processor Intel/HP Itanium 2 at 900 MHzSolaris Quad Processo

36、r SUN V480/880 at 900 MHzAIX Quad Processor IBM pSeries POWER 4 at 1200 MHzWindows Cannot be hostedServer Memory6 GBDisk Space4 GB45PATROL Central Operator Microsoft Windows Edition HardwareResourceRecommendationSmall Profiles (up to 100 managed agents)ProcessorSingle ProcessorIntel Pentium III at 5

37、00 MHzMemory128 MBMedium Profiles (up to 500 managed agents)ProcessorSingle ProcessorIntel Pentium III at 700 MHzMemory512 MBLarge Profiles (up to 1200 managed agents)ProcessorSingle ProcessorIntel Pentium III at 700 MHzMemory1 GB46Co-Hosting BMC Performance Manager Console ComponentsAll infrastruct

38、ure components can coexistA Common Connect client can be installed with PATROL Console Server and RTserverPlace PATROL Console Server and RTserver on a dedicated hostNever install PATROL Console Server or RTserver with:PATROL End-to-End Response Timer version 1.1.03 and earlierPATROL Central Alerts

39、Web Edition (specific to version 7.1.00 only)47Implementation PlanInstall the DSPerform the following steps for every RT cloud, one cloud at a time:Install RTserversInstall PATROL Agents on all managed nodesUse the PCM to configure all PATROL AgentsInstall the PATROL Console Server and configure it

40、to service the required RTcloudsConfigure the PATROL Console Server for usersUse PATROL Central Administrator to set user rights/permissions48BaseliningA specification or product that:Has been formally reviewed and agreed uponThereafter serves as the basis for further developmentCan be changed only

41、through formal change control proceduresA document or a set of such documents formally designated and fixed at a specific time during the life cycle of a configuration itemAny agreement or result designated and fixed at a given time, from which changes require justification and approval. IEEE STD 61

42、0.12-199049Baseline in BMC Performance Manager ConsoleA defined set of Agent configuration variables, both thresholds and Agent setup Used to configure a PATROL Agent for a certain type of machine50How to Get a Baseline?Review the Service Level Agreements, align the monitoring plan with the business

43、 Divide the application classes into two groups:InterestedNot interested Check parameters of interested application classes and sort intofour groupsPre-load interested KMs, disable non-interested onesInstall/Activate the parameter turn off all alertsSet History Retention Period to a minimum of 7 day

44、sCollect data measurements for a predefined period of time to get statisticsSet the thresholds based on normalized data collected in your environment and what has been agreed on in your SLA51Parameter GroupsGroup 1Parameters that are important for your SLA or machine performanceThey need to have a high frequency and an alarm1 and alarm2These are paramet