Draft document – not for publication

Draft document – not for publication
IBM Systems Director 6.2 for the IBM i Environment Bob Padzieski - ATS IBM Power Systems Although the IBM Systems Director 6.2 server does not run under the IBM i operating system, it has great value as a management tool in an environment that includes IBM i systems and partitions. This session will cover what IBM Systems Director is, what it can monitor in IBM i, how IBM Systems Director Navigator integrates, the relationship to native IBM i management tools.

Agenda Systems management environment IBM Systems Director 6.2 Resources / relationships Monitoring / automating Maintenance / currency Virtualization / optimization IBM Systems Director Editions IBM Systems Director plug-ins IBM Systems Director Active Energy Manager™ IBM Systems Director VMControl™ IBM Systems Director Network Control Setting up IBM Systems Director for IBM i IBM Systems Director is an the Management product from the IBM Systems Software Stack. System Software is a strategic move within the system development labs to develop “cross-OS” functions, versus writing similar but different functions in each of our labs. You can see that there are other functional areas like energy, security, availability and virtualization. Today we will focus on IBM Systems Director core product which helps you know what you are managing, how the resources are related, what they are doing, how to keep them up today, and how to optimize your use of them. We will touch briefly on how you would set up Systems Director in the IBM i environment. We will also talk about some of the packaging and plug-ins, which are the optional extensions to the core Systems Director offering.

IT Organization Challenges
Draft document – not for publication IT Organization Challenges Thousands of “points of management” Capital and operational expenses Space and power constraints Developing diverse administration skills Legacy infrastructures Fragile and difficult to change Many specialized skills and tools required Silos: OS, hardware, technologies, facilities … Little time for planning, optimization and improvements Pressures from criticality of IT to the business These are some of the pain points expressed by customers that were used to shape IBM Systems Director. 3 3

IBM Systems Director Consolidation of Platform Management Tools Single consistent cross-platform management tool Simplified tasks via Web based interface Manage many resources from one console Integrated Physical and Virtual Management Discovery and inventory of physical and virtual resources Configuration and provisioning of platform resources Status, health and monitoring of platform resources Visualization of server resource topologies Move virtual servers between systems without disruption to running workloads Platform Update Management Simplified consistent cross-platform tools to acquire, distribute and install firmware and OS updates IBM® Systems Director Base The IBM® Systems Director Base is the foundation for platform lifecycle management. It’s primary goal is to support 3 areas: Consolidation of Platform Management Tools - Provide a single consistent cross-platform management tool, enable simplified tasks via Web based interface, and manage many systems from one console Integrated Physical and Virtual Management - Support discovery and inventory of physical and virtual resources, support configuration and provisioning of platform resources, track and display status, health, and monitoring of platform resources, enable visualization of server resource topologies, and provide support to move virtual servers between systems without disruption to running workloads Platform Update Management - delivers a simplified consistent cross-platform tools to acquire, distribute and install firmware and OS updates

IBM Systems Management Spectrum
Draft document – not for publication IBM Systems Management Spectrum Automate configuration and placement for new workloads Manage end-to-end workload availability Understand capacity Analyze and report historical performance Visualize physical and virtual resources and relationships Monitor system health Establish threshold and error alerts Update OS, software and firmware Automate incident handling Simplify deployment with virtual images Understand and control energy use within existing capacity Manage networks and storage systems Manage workloads based on service level goals Manage business service delivery Increase agility and efficiency Optimize resource utilization Deploy workloads in clouds Reduce costs App OS Image Most IT operations centers today comprise numerous systems with varying degrees of standardization and best practices, defined and maintained by multiple IT administrators. In order to simplify the management and create a repeatable, predictable infrastructure, you need to create standard building blocks. VMControl is designed to provide the tools that guide you successfully through this process. First you determine what are the best practices that meet your business needs, then define the appropriate virtual machines to be used as building blocks. The next step is to capture and catalog the images (operating systems, middleware, and software) used in the datacenter and standardize on those building blocks as well through virtual image definition. This will result in simplified deployments and easier image management. The next logical step involves pooling your standardized virtual configurations into groups that span many systems, but can be managed if they were one. IBM is delivering the tools required for each of these steps today. Starting this process now will enable you to even further simplify virtual resource management, and position your IT operations to leverage service-focused provisioning in cloud computing environments. 5

Agenda Systems management environment IBM Systems Director 6.2 Resources / relationships Monitoring / automating Maintenance / currency Virtualization / optimization IBM Systems Director Editions IBM Systems Director plug-ins IBM Systems Director Active Energy Manager™ IBM Systems Director VMControl™ IBM Systems Director Network Control Setting up IBM Systems Director for IBM i

IBM Systems Director Topology
Draft document – not for publication IBM Systems Director Topology Management Console(s) Web Interface IBM System Director Server Application Logic Database IBM Systems Director Agents & Managed Systems Operating Systems, Logical Partitions Servers, Desktops, Laptops, SNMP devices, CIM devices IBM® Systems Director Topology IBM Systems Director is a three-tiered architecture consisting of: Management Console(s) web Interface IBM System Director Server which includes the Application Logic and database IBM Systems Director Agent which is code that runs on a managed system (Servers, Desktops, Laptops, SNMP devices, CIM devices) and communicates with the IBM Systems Director application The IBM Systems Director there-tier design supports thousands of managed nodes/systems. An upward integration module supports integration with higher level management applications from Tivoli, Computer Associates, Hewlett Packard, Microsoft. Three-tiered architecture Thousands of managed nodes Upward Integration modules supporting Tivoli, Computer Associates, Hewlett Packard, Microsoft

IBM Systems Director Task Sampler
Draft document – not for publication IBM Systems Director Task Sampler HMC, server and virtual servers discovery Navigation and topology Users and roles Processes Monitors Events Health Summary Scheduled tasks Automation plans Integration of the HMC and IBM i Navigator Software / firmware release management We will quickly walk through some of the key Systems Director tasks. The navigation panel in the console provide one way to get to most tasks

HMC-rooted Resource and Relationship Discovery
Draft document – not for publication HMC-rooted Resource and Relationship Discovery Discovers hardware and virtual resources via the Hardware Management Console With just a few clicks, Systems Director can perform basic discovery of HMCs and their related resources: POWER servers and their components (service processors, memory, CPUs, etc.), operating systems, LPARs and virtual I/O. You can optionally limit discovery to selected parts of the IT infrastructure. Automated discovery is especially important in virtualized environments where LPARs are frequently created, modified or delete. An up-to-the-minute view of resource relationships is important for planning, on-going maintenance and troubleshooting. Discovers physical and shared I/O

Resources and Relationships in Systems Director
Draft document – not for publication Resources and Relationships in Systems Director Managed Resources Hardware: CECs / Blades HMC / IVM / BladeCenter LPARs (Virtual Servers) OS instances – IBM i / AIX / Linux / Windows Software / firmware Networks / storage / energy Relationships Contains Runs on Installed on Group membership – static / dynamic Properties Status Monitored attributes Inventory attributes Capabilities On of the basic values of Systems Director is the ability to have a single view of all your IT physical and virtual resources and many of your facilities resources. Moreover, you can see many of the relationships between the resources in a graphical or data base format. The Systems Director inventory stores a large number of properties for most resources that can be queried, displayed and monitored.

Power Systems Management View
Draft document – not for publication Power Systems Management View There several different options a user might select for their startup pages. A “Power Systems” administrator might select the “Power Systems Management” page. It shows the overall status of all the power systems resources. Note that there are 45 resources in the graph. The four categories below show this is made up of three HMCs, three Power Systems Hosts (physical server systems), thirty-one LPARs (called “Virtual Servers”) and 8 operating system instances. There can be fewer OS instances than LPARs because a Systems Director agent may not have been enabled or discovered on each LPAR. The physical systems and LPARs were discovered automatically through the HMC inventory.

HMC Navigation View Nested relationships Customizable columns Roll-up CPU utilization Enable in HMC All shared processors Tasks / actions Select Right click Sort / search Many people like working with the Navigation views. Director comes with a set of predefined static and dynamic groups of managed resources, and users can define their own additional lists. Views of larger lists can be quickly subsetted by typing anys string in the “Search the table…” field and then clicking the “Search” button. The properties, order and width of the columns can be customized by each user using the “Column” action in the “Action” dropdown. There are over sixty properties that can be displayed in the columns in a Resource Navigation view, although not all the values are relevant for each resource type. For IT shops with many LPAR, the view in this example can often justify diving deeper into Director. It takes only three steps after installation to see how the different virtual servers (LPARS) are consuming CPU resources, and how much of the total system resources are being used. The three steps are to Discover the HMC, Request Access providing the HMC userid and password, and then Collect Inventory from the HMC. This will provide the view of all the Systems managed by the HMC, and all the Virtual Severs (LPAR) on that system. In order to see the performance information for an LPAR, you need to check “Allow performance information collection.” on the “Hardware > Processor” tab for the partition properties on the HMC. If all of the partitions on a System allow performance collection, IBM Systems Director uses a calculation provide a rolled up view of the processor utilization for that system. Note that even though the mini-graphs go from 0 – 100%, the numbers will show over 100% when you are using processors in a shared pool, and CPU used by other LPARs is not being left idle. The columns are customizable with a couple dozen different static or dynamic values for each HMC / processor / LPAR. Also note that this is an LPAR view, not an OS- instance view.

Topology Views Rooted in prior navigation Breadcrumb Options Depth Tree / radial Zoom Cursor types Properties Relationships Select tasks Printable IBM Systems Director provides a graphical view of navigation nodes to see relationships. The topology view starts by selecting a particular node in a navigation list, and taking a topology actions. Many different topologies views are available. This one is the basic view that started with the HMC that is now in the upper corner of the enlarged window. The breadcrumb shows the path to the selected view. The blue navigation box was moved to focus on the relationships of the HMC controlling the 8204 server, which contains multiple partitions. The relationship between a partition and its running OS instance is highlighted. If you click on any resource or relationship, you can see it’s properties in the lower right. If you right click on any resource, you get the actions available for it. If you click on the “Actions” drop down, you can change the level of detail, layout, zoon and other attributes of the topology display.

BladeCenter Chassis and Members, Blade Virtualization
Draft document – not for publication BladeCenter Chassis and Members, Blade Virtualization Nested relationships Customizable columns Context actions Hierarchical relationships are also presented in BladeCenter chassis, showing not only the processor blades, but switches as well. Virtualization for blades if via VIOS, and these relationships can be seen from the performance summary view VIOS virtualization Roll-up of CPU utilization

Creating Groups Static Geographical Functional Nested node or leaf Dynamic Property-based Nested leaf Types Managed resource Update Any Group provide an elementary way to organized the management resources that are related by customer defined reasons, or based on the properties of the resources. Wizards are available to define both static and dynamic groups. Many resource also provide and “Add to group” function on their context menu.

Resource Properties General Name Type Model IP Status Activities Inventory Rename Configuration Events Active Energy The detailed properties that can be display for a resource depend on its type.

Users and Roles IBM Systems Director users are defined in server OS or LDAP directory Access granted through host groups Roles define a set of tasks Assignment of roles defines allowed tasks and resources Users are defined to Systems Director by first being Operating System or directory defined users, and then being added to one of the four predefined “SM” groups created during Director installation. Members of the “SMUser” group can perform only basic operations. You can define roles that allow access to one or many System Director functions. You can assign roles users to control their access to resource and limit the tasks that they can perform on those resource. The OS may support LDAP or Active Directory as the user management scheme; this is supported by IBM Systems Director. For example, you can define role “iNav” that only allows access to the Director link to the IBM Systems Director Navigator functions and then grant that limited access to one or more users. The default groups are Administrator, Manager, Monitor, User and administrators can customize new groups based on these existing templates. In addition, the objects that a user (or group) can manage can be specified.

Monitoring / Automating
Draft document – not for publication Monitoring / Automating Process management Monitors Thresholds Events Health Summary Command Automation Event Actions Event Automation Plans There are many ways to us Systems Director to monitor for changes in resource properties, to display the information on various types of panels, and to automate actions based on the monitored properties.

Process Management Types Applications Jobs Subsystems Servers Actions Start / End Create process monitor Customize columns Sort on column Process Management works across all the monitored operating systems. What you see depend on the type of OS being monitored. For Windows, you can see tasks and services. For AIX & Linux, you can see processes. For IBM i, you can see jobs, subsystems and server jobs (e.g. HTTP). From the process management panel, you can create monitors to see if a process has started or ended. For example, you could monitor an IBM i job, subsystem, or even raise an event is the “solitare” process was started on a PC.

Monitors and Thresholds
Draft document – not for publication Monitors and Thresholds Monitor lists All Common Column Custom Others Thresholds Establish Activate / Deactivate Change Track Graph Dashboard The Monitors task page provides several views, such as custom, column and all. When you select view, the list presented shows the current values for the monitors and provides several tasks on a monitor, such as ediit a threshold, activate or deactivate a threshold, launch a real-time graph of the monitor values, or add s monitor graph to the Health Status page.

IBM i Resource Monitors
Draft document – not for publication IBM i Resource Monitors File File systems List of Directory Contents System Statistics User statistics NetServer™ Statistics I/O Processors Physical Disks Storage Pools Subsystems Job Queues Job Statistics Process Message Queues These are the categories of resources that can be monitored using IBM Director 5.20 or IBM Systems Director See the InfoCenter link for detailed information

IBM i Message Filter You can use a wizard to create a monitor for specific messages on particular message queues. You can even refine the filter to require specific text in the messages.

Event Log Director and user defined events Large circular log on server Set preference for console Sort, filter and search Refresh view button Create event filters from log The event log lists events both those predefined by Director and ones defined by users. Not all problems are events, and not all events are problems. You can flyover for text for details some additional details, or click on the event to see its full properties. You can use the “Event Filter” dropdown, the “Search” filter, or the columns sort capability to focus on events of interest. When an event is handled, you delete it. You can “ignore” selected events to hide their indicators until you can properly deal with them. There is an action to display ignored events.

Health Summary Scoreboard Dashboard System or group monitors Flyover graphs Zoom / export Navigation lists Favorites Systems w/problems Any group The Health Summary view is a customizable “dashboard” that might also be used as a startup page. It has four sections. 1. Scoreboard (upper left) – Always there by default. Shows problem and compliance issues. Both words and numbers are live links for detailed lists. 2. Problems (lower right) – Always there by default. Provides links to the System actions and to the problems. 3. Monitors (upper right) – Empty by default. Customizable per user id. Add as many individual or group resource monitors as you like. Mini-graphs have flyover support, or you can click for full screen graph. Graphs are added by going to “Monitors >> Show Monitors”, selecting a monitor, and then taking the “Add to dashboard” function. 4. Favorites (lower left) – Empty by default. An empty “Favorites” group is predefined for each users. Most resource and groups have an “Add to favorites” action. Even resources from the updates list can be added to favorites.

Scheduled Tasks and Jobs
Draft document – not for publication Scheduled Tasks and Jobs Create scheduled tasks Single instances Repetitive Create from scratch or based on existing task View previously executed task status and results Re-execute tasks Suspend / resume running tasks Works with Command Automation for running commands on individual resources or groups Command script and programs to be remotely run are defined, given a task name, and can be directly launched, scheduled, or included as an action in an automation plan. For IBM i, you can run commands in a QSHELL session that is remotely launched through the SSH port. The results that would be visible in a native QSH screen are returned to System Director and can be viewed in the log tab for a scheduled task.

Command Automation with IBM i
Draft document – not for publication Command Automation with IBM i Command Definition QSHELL Command User Profile / PW Name in System Director Run a definition Remote to QSHELL via SSH Now / scheduled System / group Use in automation plan Results High level success / fail Details in log Command Automation with IBM i is submitted via SSH to the QSHELL environment to IBM i. CL commands can be called using the “system” QSHELL command. In addition to the command string, the command definitions has the user id and password it is run under, and is saved with the name it will be known by in Systems Director. The command definitions can be submitted to a system or group of systems manually, on an automated basis, or as part of a Systems Director Event Automation Plan.

Automate Notification / Actions Based on Events
Draft document – not for publication Automate Notification / Actions Based on Events Monitoring Event thresholds Automation Monitor disk capacity If the disk is ≥85%: IBM Systems Director functions: Execute a CL command to delete temporary files Log the action Send a text message ! LPAR LPAR Here is a basic example of taking actions and sending an based on a monitoring disk capacity.

Automation Plan Events - Common
Draft document – not for publication Automation Plan Events - Common The next part of the wizard define events of interest on the target resources. When a “non-binary’ event type is selected, then the criteria values are set to the right. If multiple simple event types are defined, then if any occur, the Automation Plan will be triggered. More complex filters can be defined selecting “Advanced Event Filters” in the “Events” dropdown. An example of monitoring an IBM i message queues for specific messages is shown on the next chart.

Customizable Event Actions
Draft document – not for publication Customizable Event Actions Program and tasks Start a program on a system Start a program on the management server Start a program on the system that generated the event Start a task on a specified system Start a task on a system that generated the event Timed alarm that starts a program Events Set an event system variable Modify an event and send it Timed alarm that generates an event Logging Log to a log file on the server Mail and newsgroups Send an (Internet SMTP) Send an to a mobile phone Post to a newsgroup (NNTP) SNMP and TEC Send an SNMP inform request to an IP host Send an SNMP trap to an IP host Send an SNMP trap reliably to a NetView host Send a Tivoli Enterprise Console event Group membership Static group: add or remove the event-generating system Static group: add or remove group members You can create specific instances of these types of Event Actions.

Customized Text Message Event Action
Draft document – not for publication Customized Text Message Event Action A customization panel pops up to make a specific instance of an action type. Each custom action needs a name and can have an option description. Many event action types provide fields where substitution variables can be added. The variable provide the values for the event date, time, source, details and other event specific data. Many event creation panels also provides a button to test the event action.

Event Automation Plan Wizard
Draft document – not for publication Event Automation Plan Wizard Name / description Targets Resources Groups Events Common Existing Filter Event Actions Time range Summary and activation A wizard can be used to create and event automation plan. You provide a name for the automation plan and an optional description. Then you specify targets to monitor, the events to monitor, the even action, and any time ranges for which the automation plan is active.

HMC Tasks Integration HMC tasks can be accessed from a right-click on an HMC in the GUI Operations Configuration Users Connectivity Serviceability Updates With saved credentials, window is opened with no prompting. Systems Director integrate many tasks performed by the HMC without needing to log into the HMC. For example, you can change the resource assigned to a “Virtual Server”, buy right clicking on a partition selecting DLPAR, and then the resource you want to change. The appropriate HMC dialog box will appear without needing to explicitly log onto the HMC.

iSeries Navigator Integration
Draft document – not for publication iSeries Navigator Integration For IBM i 6.1 or i5/OS V5R4 OS resources, the user can directly access the IBM Systems Director Navigator for IBM i portlets. There are over 300 iNavigator functions enabled in thirteen task categories. Examples of these are shown in the IBM i section

Update Manager Check for latest Fix Central updates IBM i CUMs and Groups Firmware HMC Systems Director Others Define fix compliance policies Display status by systems or groups Download fixes Install fixes Immediate or scheduled actions The “Check for updates” task of the Update Manager of IBM Systems Director can connect to Fix Central to download information about available fixes for most types of IBM Systems Director manage resources. This fix “metadata” includes an encoded list of pre/co-requisites as well as cover letter / read me information. Comparing what’s available to Systems Director’s inventory of can “Show needed updates” which can then be download from Fix Central, stored on the Director server, and then installed on the appropriate managed resources. You can define a compliance policies for groups of resources that specify the characteristics of the desired fixes for that type of resources. As Systems Director obtains new fix metadata from Fix Central, it can note which systems no longer meet the “fix compliance” criteria. All the actions for downloading and installing can be scheduled for regularly updating during “off-shift” times.

Maintenance / Currency
Draft document – not for publication Maintenance / Currency IBM® Systems Director 6.2 IBM Director V5.20 agents IBM i 5.4 and later Cumulative PTF package and PTF Groups IBM AIX® 5.3 TL6 SP5 and later Technology levels and service packs Linux, Novell Distribution Red Hat Enterprise Linux Hardware Management Console (HMC) - V7.3.3 SP2 and later Power Systems firmware VIOS version FP11.1 or later Migration, fix packs, service packs, and interim fixes IBM BladeCenter I/O Module Firmware Management Modules, Advanced Management Modules, and Passthrough Modules IBM System x servers running Linux or Windows, device driver and firmware updates External storage firmware Here is an overview of the types of fixes Systems Director can help you manage. Please follow the link at the bottom for more details.

Virtualization / Optimization
Draft document – not for publication Virtualization / Optimization Support for IBM i partitions Create Dynamic LPAR IBM i has limited virtualization support Systems Director at this time. It includes creating partitions for IBM i and dynamically manages the partition resources.

Agenda Systems management environment IBM Systems Director 6.2 Resources / relationships Monitoring / automating Maintenance / currency Virtualization / optimization Setting up IBM Systems Director for IBM i IBM Systems Director Editions IBM Systems Director plug-ins IBM Systems Director Active Energy Manager™ IBM Systems Director VMControl™ IBM Systems Director Network Control

IBM Systems Director Editions for Power, V6.2
Draft document – not for publication IBM Systems Director Editions for Power, V6.2 IBM Systems Director Express Edition IBM Systems Director V6.2 IBM Systems Director VMControl Express Edition for Power Systems, V2.3 IBM Systems Director Service and Support Manager V6.2 IBM Systems Director Transition Manager for HP Systems Insight Manager V6.2 IBM Systems Director Standard Edition All of Express Edition plus.. IBM Systems Director Standard Edition Installation Launchpad V6.2 IBM Systems Director Active Energy Manager™ V4.3 IBM Systems Director VMControl Standard Edition for Power Systems, V2.3 IBM Systems Director Network Control V1.2 IBM Systems Director Enterprise Edition All of Standard Edition plus… IBM Systems Director Enterprise Edition Installation Launchpad V6.2 IBM Systems Director VMControl Enterprise Edition for Power Systems, V2.3 IBM Tivoli Monitoring (ITM) V6.2.2 FP2 IBM Tivoli Monitoring (ITM) - OS Agents IBM Tivoli Monitoring (ITM) - System p Agents IBM Tivoli Monitoring for Energy Management 6.2.1 IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.2 IBM Tivoli Performance Analyzer 6.2.2 IBM Tivoli Common Reporting for Asset and Performance Management 1.3 DB2 Enterprise Server Edition 9.7 FP1

Director Plug-ins (“ala carte”)
Draft document – not for publication Director Plug-ins (“ala carte”) IBM Systems Director Active Energy Manager 4.3 Monitor functions: no charge Manage functions: per managed processor charge IBM Systems Director Service and Support Manager 6. 2 No charge (does not support Power Systems) IBM Systems Director Migration Tool Version 6.2 No charge IBM Systems Director VMControl 2.3 Express Edition: no charge Standard, Enterprise Editions: per managed processor charge (no value for IBM i) IBM Workload Partitions Manager 2.2 Per managed processor charge (no value for IBM i) IBM Systems Director Network Manager 1.2 Per server and per switch charge If the Editions package offers too much, or note enough, ala carte products and plugins can be downloaded and licensed.

IBM Systems Director Active Energy Manager
Draft document – not for publication IBM Systems Director Active Energy Manager Monitor and manage EnergyScale™ capabilities in certain POWER 6 and all POWER7 servers Power Trending Thermal Trending Effective CPU Trending Power Savings Power Capping Monitor and manage other resources using an intelligent Power Distribution Unit (PDU+) Pre-POWER6 systems Power 560 and Power 570 systems I/O drawers and storage devices Define relationships between IT and facilities equipment Exploit System Director automation for energy events The functions supported in POWER6 hardware vary by model. The Power 520 and Power 550 provide all the listed functions. The Power 570 only supports static power savings. The Power 595 supports static power savings and power trending. Most PDU+ units support power and thermal trending.

Active Energy Manager Trend Data
Draft document – not for publication Active Energy Manager Trend Data Energy trends in upper chart Data are averages over intervals Input & output power Maximums, averages & minimums Power caps Energy events at points in time Temperature data in lower chart Data are point-in-time values Plotted against left axis Effective CPU speed in lower chart May exceed 100% This chart show the trend data for a Power750 system. The upper chart has the energy values. The green and blue lines show the input and output power to the processor drawer. The yellow lines relate to power capping, which is used to dynamically limit the energy used by the system. Since the processor drawer includes fans, power supplies and other hardware, there are some minimums noted on the graph. The minimum guaranteed cap is calculated purely from reduced use of the power by the CPU. The minimum power cap is calculated base on the assumption that if fans, power supplies, etc energy consumption follows the CPU reduction, there is a minimum amount of energy just to keep the drawer “running”. The chart also shows any Active Energy related events that can be monitored by Systems Director with actions taken through Event Automation Plans. This is the lower portion of the chart shows two scales. The pink and blue data points are the exhaust and ambient (input) air temperature for the processors plotted against the left scale. The gold line represent the effect of power savings and capping on CPU clocking, and is a percentage plotted against the right scale. The chart show a period when dynamic power savings favoring power was turned on. Shortly after the processor started to slow its clock, a workload with heavy processor demand occurred. The effective CPU actually ran at 109% of rated speed when more processing power was needed for a short period for a heavy processor workload.

IBM Systems Director VMControl
Draft document – not for publication IBM Systems Director VMControl Virtual servers Create, delete, manage and relocate Performance summary PowerVM, z/VM ,VMware, Microsoft, Xen Virtual appliances Partition description and software image Import, capture, manage and deploy System pools Consolidation of resources and workloads into distinct and manageable groups Targets for virtual appliances Monitoring the health of the resources and the status of the workloads Manage by adding hosts or additional storage space Editions Express, Standard and Enterprise

IBM Systems Director Network Control
Draft document – not for publication IBM Systems Director Network Control Basic lifecycle management of network switches Network system discovery and inventory View network problems and events Establish network monitors, thresholds and automation plans Integration of vendor-based device management tools Network diagnostics (ping, traceroute) Virtual Switch VLAN configuration Network device topology collection and visualization (virtual and physical) View systems according to VLAN View systems by subnet Converged Ethernet network device support (FCoCEE) via native support and vendor tools Benefits * Reduces network management costs by consolidating all management functions into a single product * Improves productivity and service levels by simplifying and streamlining management tasks * Increases asset utilization through more efficient management * Provides higher bandwidth and converged fabrics eliminating server, storage and network sprawl

Sample of Supported Network Devices
Draft document – not for publication Sample of Supported Network Devices IBM BladeCenter supported switches and Blade NICs Brocade® Converged Ethernet network switches (FCoCEE), Ethernet switches and routers QLogic® converged network adapters Cisco® FCoCEE and Ethernet switches Juniper® Ethernet switches, routers and appliances Virtual switch discovery and inventory for: VMware ESXi and ESX4 PowerVM RHEV-H

Setting Up IBM Systems Director for IBM i
Draft document – not for publication Setting Up IBM Systems Director for IBM i Decide on a server Power LPAR – AIX or Linux X86 – Windows or Linux Review supported hardware Decide on type of agent for each IBM i instances Agentless “Level 0” SSH – 5733SC1 Platform agent “Level 1” CIMOM – 57nnUME Common Agent “Level 2” Director 5.20 Agent – 5722DA1 (V5R3, V5R4, IBM i 6.1) IBM Systems Director 6.2 Common Agent for IBM i (IBM i 6.1, 7.1)

Power Systems Server Resource Requirements
Draft document – not for publication Power Systems Server Resource Requirements Small: Less than 500 Common-Agent managed systems. DB is Apache Derby Medium: Between 500 and 1000 Common-Agent managed systems DB is IBM DB2 Large: Between 1000 and 5000 Common-Agent managed systems Sizing is general and minimum, presumes DB server runs on Director Server

Recommended Hardware for Large Environments
Configuration Recommended hardware requirements Processor Memory Disk storage x86 (Windows/Linux) 4 cores, 64–bit processor and OS 12 GB 16 GB POWER (AIX/Linux) 4 processors, POWER5, POWER6 or POWER7 or for partitioned systems: - Entitlement = 4 - Uncapped - Virtual processors = 8 - Weight = Default System z (Linux) 4 processors, IBM System z9 or above Performance Tuning and Scaling Guide for IBM Systems Director 6.2

Linux on Power for the Systems Director Server
Draft document – not for publication Linux on Power for the Systems Director Server Redbook: “Implementing POWER Linux on IBM System i Platform” IBM Systems Director for Linux on Power Systems Planning, Installation, and Configuration Guide Verify network access to IBM service / support Download and install required RPMs for Linux on Power Systems Open firewall for ports required by IBM Systems Director Download / run Systems Director installation images Consider hosting in an *NWS Save / restore in a *SAVF for POC work

Operating system and software requirements
Draft document – not for publication Operating system and software requirements Supported operating systems Virtualization software supported by IBM Systems Director Virtualization software supported on Agentless-managed systems Supported Web browsers Supported screen readers Supported database applications

Virtualization Software for IBM Systems Director 6.2
Draft document – not for publication Virtualization Software for IBM Systems Director 6.2 Hardware Management Console (HMC) Version 7 R3.3.0 SP2, PTF MH01146 Version 7 R3.4.0 and SPs Version 7 R3.5.0 SP1 Version 7 R7.1.0 and R7.1.1 Power Systems Firmware POWER5, POWER6, and POWER7 Integrated Virtualization Manager (IVM) Version and later fix packs Version , fix pack 20.1 and later fix packs IBM Systems Director VMControl requires a minimum version of Version and later Virtual I/O Server

Functions by Agent level for IBM i
Draft document – not for publication Functions by Agent level for IBM i Agentless Ability to distribute the IBM Systems Director agent Access to IBM Systems Director Navigator for IBM i functions Software inventory Systems Director support for IBM i Group and Cumulative PTFs Issue remote commands Platform Agent Common Information Model (CIM) events and monitoring Hardware inventory Basic Resource Monitors and Events Common agent File Transfer Full Resource Monitors and Events Problems (Hardware Status) Process Management Genevent API

Common Agents for IBM i PREPARE !!! Consult the Systems Director information center article titled “Using IBM i resources with an IBM Systems Director Server” Install all the latest Cumulative PTF package and Group PTFs Decide between legacy IBM Director Agent 5.20 or IBM Systems Director Common Agent Services 6.1.2 Understand the prerequisites for each Legacy agent may not be supported on future releases of IBM i PREPARE again !!! Look at the planning and installation information center articles for the selected agent Install and start See the following charts for installation notes

Installing the IBM Director Agent 5.20 on IBM i
Draft document – not for publication Installing the IBM Director Agent 5.20 on IBM i Download the agent for IBM i Select IBM Director for IBM i Provide ibm.com user id and password View / accept license agreements Select IBM Director Agent for i5/OS (dir5.20.2_agent_i5OS.zip) Transfer to system and install IBM Director 5.20 information center Download and apply PTFs Go to the Support and Downloads web-site “Search all of support” for "5722DA1" to find PTFs Go to Fix Central for “i” Select “IBM i …”, OS level, and “Individual fixes” Use fix numbers found from search with normal PTF load and apply processes

Manual installation of the Common Agent Services on IBM i
Draft document – not for publication Manual installation of the Common Agent Services on IBM i Verify the prerequisite IBM i products Download the CAS Select the “Manual Installation …Download version 6.2” link in the “IBM Systems Director Common or Platform Agents” section at the middle of the page Provide ibm.com user id and password View / accept license agreements Select “IBM Systems Director 6.2 Common Agent for IBM i” (SysDir6_2_0_Common_Agent_IBM_i.zip ) Transfer to system and install Transfer files in zip package to an IBM i directory Change to the directory in the QSHELL envirionment Issue an ./installAgent.sh Wait patiently for the QSHELL prompt (>) to before exiting

Starting a the Common Agent
Draft document – not for publication Starting a the Common Agent See the “Using IBM i resources with an IBM Systems Director Server” web site for details Start SSH strtcpsvr *sshd (for IBM i 6.1 and later) Start SLP strtcpsvr *slp Start CIMOM strtcpsvr *cimom Start collection services if using monitors Start the Director Server Agent or Common Agent Services (CAS) Director Agent: strtcpsvr *director CAS: strtcpsvr server (*HTTP) httpsvr(CAS)

Agenda Systems management environment IBM Systems Director 6.2 Resources / relationships Monitoring / automating Maintenance / currency Virtualization / optimization Setting up IBM Systems Director for IBM i IBM Systems Director Editions IBM Systems Director plug-ins IBM Systems Director Active Energy Manager™ IBM Systems Director VMControl™ IBM Systems Director Network Control

IBM Systems Director Information Center
Draft document – not for publication IBM Systems Director Information Center

Reference Charts IBM i Resource Monitors details Creating a Resource Monitors

i5/OS Resource Monitors
Draft document – not for publication i5/OS Resource Monitors File File systems List of Directory Contents System Statistics User statistics NetServer™ Statistics I/O Processors Physical Disks Storage Pools Subsystems Job Queues Job Statistics Process These are the categories of resources that can be monitored using IBM Director 5.20 or IBM Systems Director See the InfoCenter link for detailed information

File Monitors Directory Directory exists Last modified Directory attributes Directory owner Directory size (bytes) Object type File Checksum File exists File attributes File owner File size (bytes) Notes: 1. File-monitor attributes can be files or directories. 2. For compatible file-system types, the “Directory exists” or “File exists” attribute (depending on which is applicable) is always valid data. 3. If there are additional directories, additional subelements are displayed. 4. A directory can contain hundreds of subelements. If it does, a directory might take 5 seconds or longer to open. 5. QSYS.LIB can contain thousands of subelements. If a timeout occurs, reopening the directory after a timeout increases the timeout value, and may increase the timeout value sufficiently for the operation to complete. An example of the details for files and directories

Process Current active processes Maximum running at once Maximum running yesterday New executions counted Times failed to start Time started Time stopped Total execution time Yesterday's execution time Yesterday's new executions Notes: 1. The number of applications or executable files that a process monitor checks can vary. The IBM® Director user configures the processes that are monitored using the Process Monitor task in IBM Director Console. Each of the process-monitor attributes is displayed for each executable file that is monitored An example of the details for files and directories

I/O processors IOP Twinaxial Use % IOP X.25 Use % Primary IOP Use % IOP Operational Status 0 = The status field does not apply to this resource or could not be determined. 1 = Operational; the resource is operational. 2 = Inoperative; the resource is not operational. 3 = Not detected; the presence of the resource could not be detected. Auxiliary IOP Use % IOP All Comm. Use % IOP Disk Use % IOP LAN Use % IOP Memory Free (KB) IOP Optical Use % IOP SDLC Use % IOP System Function Use % IOP Tape Use %

Job Queues & Job Statistics
Draft document – not for publication Job Queues & Job Statistics Job Queue Status 0 = Released; the queue is released. 1 = Held; the queue is held. Jobs in Queue Batch Jobs Ended, Output Waiting Batch Jobs Ending Batch Jobs Held on Job Queue Batch Jobs Held while Running Batch Jobs on Held Job Queue Batch Jobs on Unassigned Job Queue Batch Jobs Running Batch Jobs Waiting for Messages Batch Jobs Waiting to Run Jobs on System

Physical Disks Disk Read Commands/Minute Disk Read Kbytes/Minute Disk Write Commands/Minute Disk Write Kbytes/Minute Disk Processor Utilization % Disk Mirroring Status 0 = Not mirrored 1 = Active 2 = Resuming 3 = Suspended Disk Arm Utilization % Disk Space Free (MB) Disk Space Used % Disk Average Queue Length Disk Operational Status 0 = The status field does not apply to this resource or could not be determined. 1 = Operational; the resource is operational. 2 = Inoperative; the resource is not operational. 3 = Not detected; the presence of the resource could not be detected.

NetServer™ Statistics
Draft document – not for publication NetServer™ Statistics Average Response Time (Milliseconds) File Opens/Minute Kbytes Received per Minute Kbytes Sent per Minute Password Violations Print Jobs Queued/Minute Session Starts/Minute

Storage Pools Active to Ineligible (Transitions/Minute) Active to Wait (Transitions/Minute) Database Faults per Second Database Pages per Second Non-database Faults per Second Non-database Pages per Second Wait to Ineligible (Transitions/Minute)

System and User Statistics
Draft document – not for publication System and User Statistics CPU Utilization % Current Temp Storage Used (MB) Max Temp Storage Used (MB) Permanent Addresses Used % System ASP Used % Temporary Addresses Used % Users Disconnected Users Signed Off, Output Waiting Users Signed On Users Suspended by Group Jobs Users Suspended by System Request

Roll Your Own Monitors Management Central Job Process Monitors e.g. Job CPU utilization Application events Director Genevent command in QSH /type:"event_type" /text:"event_description" /dest:protocol::server_address /sev:{FATAL, CRITICAL, MINOR, WARNING, HARMLESS, or UNKNOWN}

Creating a Common Agent Monitor (1 of 6)
Draft document – not for publication Creating a Common Agent Monitor (1 of 6)

Trademarks AIX®, IBM®, iSeries®, BladeCenter® , DS4000®, EnergyScale, IBM® Systems Director Active Energy Manager, i5/OS®, Netcool®, Power®, POWER®, POWER5™, POWER6™, POWER7™, Power Systems, Power Systems Software, System x®, Tivoli®, zSeries®, and z/VM® Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States. The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. For a complete list of IBM Trademarks, see The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. * All other products may be trademarks or registered trademarks of their respective companies. Notes: Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

Draft document – not for publication

Similar presentations

Presentation on theme: "Draft document – not for publication"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Draft document – not for publication

Similar presentations

Presentation on theme: "Draft document – not for publication"— Presentation transcript:

Similar presentations

About project

Feedback