Service outage Critical Yes Service operates, but at substantially reduced functionality or capacity High Yes Service operates with full functionality, but at reduced capacity Medium Yes Service operates with full functionality and capacity Low No Record the monitoring priority in the column provided in Table A-2 in the Appendix. Repeat this process for each component map created in Task 2. Task 4: Identify In-Place Monitoring and Administrative Processes Not every Operations Manager 2007 project will be a new implementation. Many organizations will have monitoring and management systems already in place, deployed in a way best suited to meet the organization’s administrative model. Before moving to Step 2, it is crucial to identify whether coexistence with existing management systems is required. Determining whether Operations Manager 2007 is expected to coexist with, or replace, these systems will affect selection of management packs and monitoring methodology in Steps 2 and 3, as well as infrastructure sizing and placement decisions in Steps 6, 7, 8, and 11. Discuss the need for coexistence and its expected duration with service owners of existing monitoring and trouble ticket systems. The results of these discussions will drive the decision about whether to replace existing systems or to plan for coexistence. are several circumstances that require coexistence: When continuous monitoring is necessary during Operations Manager 2007 deployment. During an upgrade, when systems are operating in a side-by-side configuration with elements of Microsoft Operations Manager 2007. When other System Center products are used that require interface with Operations Manager 2007 (for example, System Center Virtual Machine Manager uses the Operations Manager 2007 Reporting Server role to generate reports). When some existing monitoring systems are controlled by autonomous IT units that are not adopting Operations Manager 2007. If an integrated solution that provides a single console for help desk or other IT support functions is required. If automated ticket generation to a help desk ticketing system is required. Record the information for this task in Table A-3 “Sample Monitoring and Administrative Process Analysis” in the Appendix. Step Summary Aligning technical decisions with business requirements is a critical component of a successful project. Failure to clearly identify the functional requirements of the business
Supported Configurations document at . Record this information in Table A-12 in the Appendix. Measure the available bandwidth on these connections by requesting the average available bandwidth during peak usage periods. Record this information in Table in the Appendix. Compare the required bandwidth against the available bandwidth to determine whether additional bandwidth will be required, and record this in Table A-12 in the Appendix. Task 2: Determine Network Port Requirements The goal of this task is to map the supported firewall scenarios to the locations of the in order to identify the network ports that must be opened. The network ports required for communication depend on the placement of server roles throughout the network. To determine firewall port requirements, review server placement decisions from Steps 6 and 7 and compare them with the port requirements in Operations Manager 2007 R2 Supported Configurations at . This will establish which ports need to be opened on firewalls in the environment. Record the network port requirements in Table A-12 in the Appendix. Step Summary The goals of this step are to ensure that network connectivity between server roles and between server roles and agents is sufficient in terms of network bandwidth and that the required firewall rules are in place to allow traffic to flow as necessary. In this step, the following data was used to determine network bandwidth and network port requirements: Data collected in Step 1 on network topology and inventory of resources in scope for monitoring. Server role distribution, determined in Step 6. Database role distribution, decided in Step 7. Reporting infrastructure requirements from Step 10. The output of this step was a containing the bandwidth requirements between physical network sites as well as the network ports that must be opened through network firewalls. Table A-12 in the Appendix was used to record the information in this step. This information is used in the implementation phase of the project to identify necessary changes in network firewalls as well as any network links requiring additional network bandwidth to support the minimum requirements of Operations Manager 2007. Additional Reading Operations Manager 2007 R2 Supported Configurations: System Center Central home page: System Center Operations Manager 2007 R2 TechCenter home page:
file server No Medium Table A-2. Sample Business Service Component Map (continued) Service Dependent components Management pack Time Tracking If AD DS fails, authorization in Time Tracking is unavailable. Microsoft All user input stored here. Microsoft Failure prevents client connections. Microsoft Used in client authentication, but handled by DNS if WINS fails. Microsoft Switches are redundant. Single switch failure would not cause outage. Company X Single switch failure would have little impact. Two or more failures would cause outage. Microsoft Single server failure would have little impact. Three or more failures would cause outage. Microsoft Steps 1 and 2. Use a job aid like the one shown below to record the existing monitoring systems, monitoring gaps, and key details of administrative model. Table A-3. Sample Monitoring and Process Analysis Objective Answers/comments Identify gaps in Operations Manager 2007 functionality versus resources in-scope for monitoring. Determine if monitoring that is currently in fills functionality gaps. Identify and document the components and business services in the gap covered by existing systems. What monitoring systems are currently in place? Who uses monitoring consoles with existing systems? What product connectors are required? Where can they be obtained?
Table A-11. Sample Reporting Infrastructure Requirements (continued) Reporting Server name Data warehouses providing data Location of Reporting Server Resource requirements and form factor Report Server - 1 DW-1 Ohio 2 x 2.8 GHz, 4 GB of RAM, 2-drive RAID 1 Form factor: HP DL380 or Dell 2950 Fault tolerance: None Step 11. Use a job aid like the one shown below to record Operations Manager 2007 network bandwidth and TCP/IP port requirements. A-12. Sample Network Bandwidth and TCP/IP Port Requirements Source site Destination site Required bandwidth (k) Available bandwidth (k) NYC hub ATL branch 832 1500 NYC hub BOI branch 64 50 NYC hub PHX branch 640 3000 Table A-12. Sample Network Bandwidth and TCP/IP Port Requirements (continued) Additional bandwidth required Network port requirements Comments (optional) N 5723, 51909 Gateway server, ACS collector to NYC hub Y 5723 Gateway server to NYC hub N 5723 10 agents to management server at NYC hub Version History Version Description Date
directly responsible for or made a substantial contribution to the writing, development, and testing of this guide. Contributors: Jude Chosnyk – GrandMasters Joe Coulombe – Microsoft Charles Denny – Microsoft Michael Kaczmarek – Microsoft Robin Maher – Microsoft Fergus Stewart – Microsoft Melissa Stowe – Microsoft Pete Zerger – Studio B Productions Reviewers: Tony Chou – Microsoft Fernando Gebara Filho – Microsoft John Joyner – ClearPointe Frank Koch – Microsoft Rob Kuehfus – Microsoft René Scholten – Capgemini Vel – Microsoft Editors: Laurie Dunham – Microsoft Dave Field – Studio B Productions Ruth Preston – Volt Technical Services Pat Rytkonen – Volt Technical Services