Front cover IBM Systems Director Management Console Introduction and Overview Documents the SDMC appliance, which uses the Systems Director user interface Discusses the differences between the HMC and SDMC Provides a practical guide to the SDMC Thomas Libor, PhD Allen Oh Lakshmikanthan Selvarajan Peter Wuestefeld ibm.
International Technical Support Organization IBM Systems Director Management Console: Introduction and Overview April 2011 SG24-7860-00
Note: Before using this information and the product it supports, read the information in “Notices” on page xix. First Edition (April 2011) This edition applies to Version 6, Release 730, Service Pack 1048A of SDMC Build Level 1. Note: This book is based on a pre-GA version of a product and may not apply when the product becomes generally available. We recommend that you consult the product documentation or follow-on versions of this IBM Redbooks publication for more current information.
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Trademarks . . . . . . .
2.3.2 VMware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.3.3 Red Hat KVM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.4 Setup wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.5 SDMC software licensing requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.5.1 SDMC hardware appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 System discovery functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.1.2 Discovery of POWER processor-based blades . . . . . . . . . . . . . . . . 81 5.1.3 Using the command-line interface. . . . . . . . . . . . . . . . . . . . . . . . . . . 82 5.1.4 Auto discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 5.1.5 IP address rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 5.
.2 Virtual Server activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 8.3 Virtual Server shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 8.4 Virtual Server management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 8.4.1 Command-line usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 8.4.2 Current Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Scheduling operations for managed systems and Virtual Servers . . . . 290 11.1.1 Schedule tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 11.1.2 Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 11.1.3 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 11.1.4 Creating the job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 11.
14.5.2 Support Files Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 14.6 Service and Support Manager command-line interface . . . . . . . . . . . . 362 14.7 Service and Support Manager tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 14.8 First Failure Data Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 14.9 Guided Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 14.9.
Figures 1-1 HMC and IVM management of POWER servers . . . . . . . . . . . . . . . . . . . . 2 1-2 SDMC administrative framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1-3 Positioning the IBM Systems Director Management Console. . . . . . . . . . . 5 1-4 SDMC: Hardware appliance structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2-1 SDMC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1 Available Power Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 6-2 Edit Power Unit page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 6-3 Bulk Power Assembly (BPA) Status page. . . . . . . . . . . . . . . . . . . . . . . . 102 6-4 Change Password page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 6-5 Initialize Frame page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-17 8-18 8-19 8-20 8-21 8-22 8-23 8-24 8-25 8-26 8-27 8-28 8-29 8-30 8-31 8-32 8-33 8-34 8-35 8-36 8-37 8-38 8-39 8-40 8-41 8-42 8-43 8-44 8-45 8-46 8-47 8-48 8-49 8-50 8-51 8-52 8-53 8-54 8-55 8-56 8-57 8-58 8-59 Create Virtual Server: Optical device and media selection . . . . . . . . . . 149 Create Virtual Server: Load Source and Console . . . . . . . . . . . . . . . . . 150 Create Virtual Server: Assign physical adapters. . . . . . . . . . . . . . . . . . 151 Activate Virtual Server: Profile option .
8-60 Select Validate from the partition page . . . . . . . . . . . . . . . . . . . . . . . . . 195 8-61 Click Validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 9-1 Systems Director Management Console: Initial users page . . . . . . . . . . 203 9-2 Initial Roles page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 9-3 Create Role wizard: Name page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-42 Snapshot manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 9-43 View Trace Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 9-44 Console Logging and Tracing Configuration . . . . . . . . . . . . . . . . . . . . . 268 9-45 Update IBM Systems Director link . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9-46 Select the SDMC appliance from the Context Chooser . . . . . . . . . . . .
14-14 14-15 14-16 14-17 14-18 14-19 xiv Manage Support Files system wide view . . . . . . . . . . . . . . . . . . . . . . 353 Support Files in the context menu of a host . . . . . . . . . . . . . . . . . . . . 354 Serviceable Problem Support Files view. . . . . . . . . . . . . . . . . . . . . . . 355 Collect Support Files page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Properties of a support file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1-1 Server firmware support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1-2 POWER6 support by SDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1-3 POWER7 support by SDMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1-4 Side-by-side comparison of terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2-1 Hardware appliance requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-19 listjobs command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 A-20 chkssmconfig command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 A-21 collectsptfile command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 A-22 cpsptfile command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 A-23 lssptfile command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples 2-1 OVF Tool CLI using an OVA file on Windows . . . . . . . . . . . . . . . . . . . . . . 24 2-2 Sample domain.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 8-1 Create Virtual Server using smcli mksyscfg . . . . . . . . . . . . . . . . . . . . . . 152 8-2 Activate a Virtual Server using smcli chsysstate . . . . . . . . . . . . . . . . . . . 156 8-3 Shutting down a Virtual Server using smcli chsysstate . . . . . . . . . . . . . .
xviii IBM Systems Director Management Console: Introduction and Overview
Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries.
Preface This IBM® Redbooks® publication positions the IBM Systems Director Management Console (SDMC) against the IBM Hardware Management Console (HMC). The IBM Systems Director Management Console provides system administrators the ability to manage IBM Power System® servers as well as IBM Power Blade servers. It is based on IBM Systems Director. This publication is designed for system administrators to use as a deskside reference when managing Virtual Servers (formerly partitions) using the SDMC.
The team who wrote this book This book was produced by a team of specialists from around the world working at the International Technical Support Organization, Poughkeepsie Center. Thomas Libor, PhD is an IT Specialist in Germany. He has 10 years of experience in Power Systems™ and AIX®. He is an IBM Certified Advanced Technical Expert for Power Systems with AIX and an IBM Certified Advanced Technical Expert for IBM System Storage® 2009.
Udo Sachs SVA Germany Now you can become a published author, too! Here's an opportunity to spotlight your skills, grow your career, and become a published author—all at the same time! Join an ITSO residency project and help write a book in your area of expertise, while honing your experience using leading-edge technologies. Your efforts will help to increase product acceptance and customer satisfaction, as you expand your network of technical contacts and relationships.
Stay connected to IBM Redbooks Find us on Facebook: http://www.facebook.com/IBMRedbooks Follow us on Twitter: http://twitter.com/ibmredbooks Look for us on LinkedIn: http://www.linkedin.com/groups?home=&gid=2130806 Explore new Redbooks publications, residencies, and workshops with the IBM Redbooks weekly newsletter: https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm Stay current on recent Redbooks publications with RSS Feeds: http://www.redbooks.ibm.com/rss.
1 Chapter 1. Overview The IBM Systems Director Management Console (SDMC) is the successor to the Hardware Management Console (HMC) and the Integrated Virtualization Manager (IVM). It supports all POWER6™ and POWER7 processor-based systems (including Power Systems blades) with the exception of the 575. In this chapter, we introduce the SDMC, show some of its history, and position it in the Power Systems environment.
1.1 Power Systems management consoles The Hardware Management Console (HMC) allows for management of Power Systems from entry level servers to high-end systems. Management of entry systems is also possible with the Integrated Virtualization Manager (IVM), a function of the Virtual I/O server. The IVM is confined to the system the Virtual I/O Server is installed on, while the Hardware Management Console can administer up to 256 LPARs.
The characteristics of those management consoles are as follows: Hardware Management Console: – Is implemented as an external, independent appliance – Administers entry level up to high-end systems – Can administer more than one managed system – Allows for more than one Virtual I/O Servers per managed system Integrated Virtualization Manager: – Runs directly on top of a Virtual I/O Server – Administers POWER processor-based blades up to entry level servers – Administers only one managed system per IVM –
See Figure 1-2 for an overview of how the SDMC is placed in an enterprise-wide administration framework.
See Figure 1-3 for a schematic overview. This figure shows where the SDMC fits into the overall view of IBM Systems Director systems management.
1.3 IVM, HMC, and SDMC support The transition will begin in the second half of 2011, as new virtualization features will be only supported by the SDMC. Systems in current installations will be supported by the Hardware Management Console as long as firmware requirements are met. See Table 1-1 for an overview of which POWER processor based systems are supported.
Note: The SDMC does not support the Power 575, POWER5 technology-based systems and POWER5 technology-based I/O towers connected to a POWER6 technology-based server. This support plan is the same plan as the support plan for the Hardware Management Console. For proper and supported function, the firmware level of managed systems and of the Hardware Management Console always had to match the Supported Code Combinations, as documented in the POWER code matrix.
The virtualization layer for the hardware appliance is fixed and cannot be changed. Installation, backup to media, and restore from media is possible as it is with the Hardware Management Console. The hardware appliance is structured as shown in Figure 1-4.
Table 1-2 POWER6 support by SDMC POWER6 models Machine types SDMC 595 9119-FHA HW APP Only 575 9125-F2A HMC Only 570 9117-MMA HW APP Only 570 9406-MMA HW APP Only 560 8234-EMA HW APP Only 550 8204-E8A HW or SW APP 550 9409-M50 HW or SW APP 520 8203-E4A HW or SW APP 520 8203-E4A HW or SW APP 520-SB 8261-E4A HW or SW APP 520 9408-M25 HW or SW APP 520 9407-M15 HW or SW APP JS22 7998-61X HW or SW APP JS12 7998-60X HW or SW APP Table 1-3 POWER7 support by SDMC POWER7
1.5 Terminology Based on the integration into IBM Systems Director, a common terminology replaces the Hardware Management Console and Integrated Virtualization Manger specific terminology. Table 1-4 shows a mapping of terminology used on the Hardware Management Console versus the terminology used in the SDMC. Terminology might change slowly, so you might see and hear old terminology mixed with new terminology for a period of time.
The command-line interface has been mostly kept the same. On the SDMC, most of the commands are just preceded by smcli. This new prefix might require changes to existing scripts that use the Hardware Management Console. Though the SDMC retains most of the features that were available in the HMC, there are a few functional differences that exist between the SDMC and the HMC.
1.6.3 Additional functions The SDMC comes with the IBM Systems Director base management functions which offers you additional capabilities to manage your heterogeneous and large homogeneous infrastructure better. These capabilities include: Automation manager Status manager Firmware and device microcode updates through the Update Manager Call home support 1.6.
1.6.7 SDMC considerations Here is the list of limitations for SDMC when compared with the HMC: The system plans feature is not available in SDMC. Replication of user data, groups data, LDAP or Kerberos configuration data, and outbound connectivity configuration data is not supported in SDMC. Management of POWER5™ technology-based systems is not supported. There is no modem or VPN support for the Call Home function. Capturing of log information using the pedbg command is less granular.
14 IBM Systems Director Management Console: Introduction and Overview
2 Chapter 2. Installation In this chapter, we describe the installation of the IBM Systems Director Management Console (SDMC). We describe in detail the requirements for the hardware and software installation, the installation of the hardware and software appliance itself, and the setup wizard. © Copyright IBM Corp. 2011. All rights reserved.
2.1 Prerequisites This section lists the requirements and pre-requisites for the hardware and software appliance. The hardware appliance is required for all midrange and high-end systems (POWER6 technology based 550 server and higher, and POWER7 technology-based 750 servers and higher). 2.1.1 Hardware appliance The hardware appliance comes preloaded on IBM x86 hardware (7042-CR6).
Guest configuration Four virtual CPUs 6 GB RAM 500 GB disk (can be thin-provisioned) Between one and four Ethernet adapters Recommendation: Although the disks in the guest configuration can be thin provisioned, we do not recommend it. There is no guarantee that the disk space is there when it is needed, which would cause problems. The supported host operating systems and hypervisors are: Red Hat Enterprise Linux (RHEL) 5.5 with KVM (kvm-83-164.el5) or later.
2.2.1 Hardware installation For the hardware appliance, you need at least one network connection to connect to the service processor of your POWER machines. To configure a private and an open network, as shown in Figure 2-1, you need at least two network connections: One in an open network over which you can reach the SDMC through a web browser, and one private network for connecting the SDMC with the service processor of your POWER machines, as shown in Figure 2-1.
2. After DVD1 is copied, the following prompt appears: Press Enter to shutdown the system. After the system is powered off, apply power and remove media from the drive to complete the installation. Follow those instructions. After the system powers down, make sure you remove the first DVD as soon as you power on the system. 3. After the system regains power, you see the following prompt: Please insert media 2 into the drive, and press Enter when ready. Insert DVD2 and press Enter. 4.
A graphical interface on the VMWare Virtual Infrastructure Client To use the CLI method of deployment for VMware, customers must install the VMware OVF Tool on a Windows or Linux machine. Download the VMware OVF Tool from the following address: http://communities.vmware.com/community/vmtn/vsphere/automationtools/ovf Note: In the below examples for the CLI installation, the thin provisioned format is selected as the format to store the virtual machines virtual disks.
2. Select File Deploy OVF Template, as shown in Figure 2-2. Figure 2-2 Deploy OVF Template from vSphere Client Chapter 2.
3. Select the Deploy from file radio button and click the Browse button. Navigate to the folder you created, highlight the OVA, and click OK. Click Next, as shown in Figure 2-3.
4. Continue through the pages until you reach the Ready to Complete page. Review the deployment settings and click Finish to start the deployment of the SDMC (Figure 2-4). Figure 2-4 Ready to Complete page: A summary of the deployment settings Steps for using the OVF Tool CLI with OVA To use the OVF Tool CLI with OVA, perform the following steps: 1. Obtain the OVA file that contains the SDMC Virtual Machine. Chapter 2.
2. Because all files and images needed are contained within the OVA, you can simply deploy the package. Note that the descriptive syntax within and including the <> should be replaced with the appropriate user-specified string: – On Linux: /usr/bin/ovftool --name=SDMC –ds= [-dm=thin] vi://:@ – On Windows (Example 2-1): “Program Files\VMware\VMware OVF Tool\ovftool.
This command extract the disk images (dvmdisk1.img, dvmdisk2.img, dvmdisk3.img,...dvmdisk7.img). 4. Create the domain XML file (or use the template, if it is present). You have to provide custom values for the following fields: – MAC addresses (mac address tag). You can use the following script to generate MAC addresses: echo -n 00:1A:64 ; for i in `seq 1 3` ; do echo -n `echo ":$RANDOM$RANDOM" | cut -n -c -3` ;done; echo \n Replace the 00:1A:64 with your preferred prefix. – Bridge name (source bridge tag).
Note: Do not use the default bridge virbr0 that is visible after installing the virtualization software. This bridge is for outbound traffic of virtual machines only; incoming connections are not allowed. There is an IBM document called Quick Start Guide for Installing and Running KVM, with a chapter on network bridging, that can be found on the IBM InfoCenter website at: http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp ?topic=/liaai/kvminstall/liaaikvminstallstart.
PAGE 545. Define VM by running the following command: virsh define .xml 6. Start VM by running the following command: virsh start VM_name Run the Setup Wizard on the KVM virtual machine console to customize the VM. Refer to 2.4, “Setup wizard” on page 28 for more details. 2.4 Setup wizard The setup wizard guides you through the installation process. You must perform the following steps: 1. Select the locale for the system (see Figure 2-5). Click OK.
– pt_br: Brazilian Portuguese – zh_CN: Simplified Chinese – zh_TW: Traditional Chinese 2. Accept the IBM Software License Agreement (Figure 2-6). Figure 2-6 IBM Software License Agreement Chapter 2.
3. After accepting the license agreement, the Welcome page of the setup wizard opens (Figure 2-7). Figure 2-7 Setup Wizard Welcome page Click Next.
4. Enter the date, time, and time zone for your location (Figure 2-8). Figure 2-8 Date and Time page Chapter 2.
5. The next four pages request the passwords for the sysadmin, root, and pe users (Figure 2-9). Figure 2-9 Setup of passwords You should change them from the default password. The meaning of the users are as follows: sysadmin The sysadmin user ID is the Systems Director administrator user ID (similar to the hscroot user on an HMC). root The root user ID is the service user ID for Systems Director. pe The pe user ID is the product engineer user ID for Systems Director (analogous to hscpe user on HMC).
square brackets ([ ]), backslash (\), colon (:), quotation mark ("), semicolon (;), and apostrophe ('). – Passwords can include special characters, but passwords must begin with an alphanumeric character. 6. Afterwards, you can optionally create additional users (Figure 2-10). You can do this step also after the setup is finished. Refer to 9.1, “User management and security” on page 198 for further information about users and roles. Figure 2-10 Creating additional users 7.
8. The last page to complete is the Agent Manager configuration page (Figure 2-11). Here you have to provide the Resource Manager user ID, the Resource Manager password, and the Agent Registration password. You can specify different passwords, but you only need to remember them if you plan to use redundant management with the agents. Information: IBM Systems Director uses a function called Agent Manager.
9. After completing the last page and clicking Next, the Summary page opens (Figure 2-12). You can always go back from here to change some or all of the values you have entered. Figure 2-12 Summary page If you are satisfied with your choices, click Finish. Chapter 2.
10.If all went well, you see the System Setup Processing page; a status of Success should be behind every listed item (Figure 2-13). Figure 2-13 System Setup Processing page If anything failed, you can view the cause by clicking the Details button.
11.After clicking Close, the SDMC boots and a startup page opens (Figure 2-14). Figure 2-14 Console starting page Chapter 2.
The startup takes up to five minutes. When the startup is finished, the Systems Director login page opens (Figure 2-15). Note: Depending on the browser you use, you eventually have to accept a HTTPS-Certificate when accessing the appliance remotely. Figure 2-15 IBM Systems Director login page You can now access the SDMC either locally through the embedded browser, or remotely through a browser using https://, or using SSH. 2.
2.5.1 SDMC hardware appliance For the SDMC hardware appliance, the customer needs to order the 7042-CR6 machine type with the SDMC feature code, including additional memory and a hard drive. When the SDMC feature code is ordered, the requisite SDMC software PIDs (5765-MCH) and SWMA PIDs (566x-MCH) are automatically appended to the order. The MCH SW and SWMA PIDs include license entitlement and support for the management server code. 2.5.
40 IBM Systems Director Management Console: Introduction and Overview
3 Chapter 3. Basic operation This chapter provides an overview of features and tasks provided by IBM Systems Director Management Console (SDMC) and describes how to perform them using the graphical user interface. © Copyright IBM Corp. 2011. All rights reserved.
3.1 Features overview The SDMC is now available as part of the IBM Systems Director platform. This configuration provides a common appearance and navigation behavior with other management solutions, such as with IBM Tivoli products. The SDMC management functions seamlessly integrates with the base management functions that come with IBM Systems Director. All platform management functions are now managed from a single management interface.
Edit host This task displays the properties of the server. The properties contain information about the processors, memory, I/O, and the capabilities of the server. This task should not be confused with the Properties task available on the context menu of the server, which displays the IBM Systems Director inventory information of the managed server. Power on and power off Use the Power On task to start a server. Use the Power Off task to shut down the server.
Collect utilization data You can set the SDMC to collect the resource utilization data for a specific server or for all the servers the SDMC manages. You can use this data to analyze trends and make resource adjustments. 3.1.2 PowerVM Virtualization management SDMC provides you with all the PowerVM Virtualization management functions for the Power Server that you want to manage.
Suspend and resume Virtual Servers You can suspend Virtual Servers to store its state on a Storage Area Network (SAN). You can re-assign all processors and memory of a suspended partition to other partitions as needed. You can resume a suspended partition to bring it back to the started state. This feature is useful for performance management and energy management of servers.
Rebuild Power Unit Use this task to rebuild the Power Unit information in the SDMC. Rebuilding the Power Unit is useful when the detailed state of the Power Unit is shown as Incomplete. Manage passwords Use the change password task to change the SDMC access password on the Power Unit. You can use the Update password task to set the admin, general, and the SDMC access passwords when the Power Unit is in the Waiting for Input state and the detailed state is Update Password-Pending Authentication.
Security and user management You can create users and roles. You can assign permissions to roles and assign the roles to the user. This task allows the user to perform only the tasks that are assigned to the roles of the user. You can create groups of managed systems and assign them to a user to restrict management of only those managed systems. You are allowed to create user accounts in Lightweight Directory Access Protocol (LDAP) server or Kerberos servers. 3.1.
Support file management SSM provides the following capabilities for managing support files such as extended error data collected along with serviceable events or system dumps: Collection of support files Transmission of support files to IBM Copying of support files to removable media devices Removal of support files from SDMC Space management of support files Dumps You can collect the following dumps using SSM: System System controller Node controller Resource controller Power SSM ta
3.2 Using the web interface SDMC provides a web interface similar to the HMC. Power on the SDMC appliance and you should see the login page of the SDMC Graphical user interface. You can also access SDMC remotely using a browser such as Firefox or Internet Explorer. For logging in remotely, open the browser and point the browser to the following URL: https://system_name system_name is the host name or IP address of the SDMC system. A login page opens (Figure 3-1). Figure 3-1 SDMC Login page Chapter 3.
Enter the user ID and password that corresponds to an authorized SDMC user and click Log in. You should see the Welcome page (Figure 3-2) after logging in successfully into the SDMC. Figure 3-2 Welcome page The Welcome page has four tabs: Resource Manage Settings Learn The Resource tab provides a dashboard of all the servers, Virtual Servers, Power Units, and operating systems that your SDMC is currently managing.
There could be other non-Power Systems that are discovered and managed by SDMC. You can see these systems in the Navigate Resources page. The Welcome page has certain columns that are not available in the Navigate Resources page. These columns hold data specific to Power resources that the SDMC is managing. The Manage tab in the Welcome page lists the various managers that are available in SDMC. You can click any of the managers to perform specific operations.
You can open multiple views or pages and have them open as tabs at the same time. You can switch between the tabs in the content area performing multiple operations at the same time. Problems and Compliance status bar This bar provides you with a quick snapshot of problems and compliance issues related to your environment. Click the number (if any) for the Problems or Compliance to view complete details about them in the Active Status view. View list This list helps you customize your navigation area.
Figure 3-3 shows a snapshot of the layout of the management tasks on the context menu of the server.
Figure 3-4 shows the other tasks that are available in the context menu of the server. Server Release Management Import Updates by FTP POWER Firmware Management Readiness Check Check for Updates... Show Needed Updates... Show Installed Updates... System Status and Health Service and Support Performance Summary Active Status Event Log Monitors Thresholds Check Eligibility Dump Settings...
Figure 3-5 shows a snapshot of the layout of the management tasks available on the context menu of the Virtual Server.
Table view The table view displays a list of resources along with their information in a table format (Figure 3-6). The various properties of the resource are displayed in the various columns of the table.
Properties view The properties view displays a list of properties and other detailed information related to the selected resource. You can access the properties view from any view by selecting a resource and selecting Action Properties. The properties view is shown in Figure 3-7. Figure 3-7 Properties view The properties view only shows the inventory information collected from the managed system or the Virtual Server.
Topology view The topology view displays the relationship among your resources. Select a resource and select Actions Topology Perspectives Basic. The Basic selection provides a topology map that shows key resources that are related to the selected resource. The topology map view shows a graphical view of your resources and their relationships. You can drill down and view the relationships among these resources and other resources in your environment. You can also view and edit resource properties.
3.3 Command-line interface The IBM Systems Director provides the systems management command-line interface, referred to as smcli, for issuing commands. You can run smcli commands locally from SDMC or remotely by accessing the SDMC using a remote access utility, such as secure shell (SSH). SDMC provides all the commands that were available in HMC. You can run the same command as in HMC, but using the smcli prefix. So the HMC command lssyscfg -r sys becomes smcli lssyscfg -r sys.
60 IBM Systems Director Management Console: Introduction and Overview
4 Chapter 4. Making the transition to the IBM Systems Director Management Console This chapter describes the various ways of how you can transition your managed systems from the Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) environment to the IBM Systems Director Management Console (SDMC) environment. © Copyright IBM Corp. 2011. All rights reserved.
4.1 Concepts Transition is a new feature that is available to transition systems from the HMC or IVM environment to the SDMC environment. This feature helps you transition one or more systems that are currently being managed by HMC or IVM to being managed by SDMC.
4.2.1 What is transitioned When you transition managed systems from IVM to SDMC, only the following information is transitioned: Managed system information. Virtual Server information is automatically retrieved from the managed system after a request access to the managed system is successful. 4.2.2 How to transition Perform the following steps to transition a managed system from IVM to SDMC: 1. Discover the managed system in SDMC using the System Discovery page. 2.
Creates default profiles based on Virtual Server current configuration read from PHYP, as IVM does not support profiles. 4.2.3 Messages By default, all success and failure messages are listed in the Event Log page. The Event Log page is available under the System Status and Health category in the navigation area. Check the Event Log page for the success or failure of the transition process.
4.3 HMC to SDMC transition This section describes how you can transition a managed system from an HMC environment to an SDMC environment. This section is applicable only when the managed systems are in a public network and SDMC is not the Dynamic Host Configuration Protocol (DHCP) server. If your managed systems are in a private network, refer to 4.4, “Transition in a private network” on page 72. 4.3.
Perform the following steps to perform an online transition: 1. Launch the transition wizard using the Common Tasks menu in the SDMC welcome page (Figure 4-1). Figure 4-1 Launch Transition wizard 2. Click Next on the Welcome page of the transition wizard. 3. Select Connect to the HMC to interactively transition to SDMC. Enter the user name, password, and the IP address or host name of the HMC and click Next.
4. You should now see a list of managed systems (Figure 4-2) that are available in the HMC that can be transitioned to your SDMC. Select the managed systems that you want to transition and click Next. Note: If the SDMC is already managing some managed systems that are being managed by the HMC currently, those managed systems will not be listed for transition. Figure 4-2 Managed systems in the Transition wizard 5. You should now see the summary page of the Transition wizard.
After successful authentication, the Access state of the managed system changes to OK. The tasks for managing the system are now available in the context menu of the system. The Virtual Servers hosted by the managed system are retrieved automatically and can be seen in the Welcome page or the Navigate Resources page. 4.3.4 Interactive transition using the command-line interface Perform the following steps to perform an online transition using the command-line interface: 1.
All serviceable events must be closed before you can execute this command. If there are any open serviceable events at the time of issuing this command, you will get a warning message and you have to close all of them before executing the command again. Note: The expdata command only exports HMC configuration information that is required for transition. The exported data cannot be used as HMC backup data. 2. Launch the transition wizard.
5. Browse to and select the exported configuration data file from step 1 (Figure 4-3). You can also select a file that is available on a connected system in the network. Click Next. Figure 4-3 Transition method using an exported data file 6. You should now see the summary page of the transition wizard. It shows you the IP address or the host name of the HMC and the managed systems that you have selected for transition. Click Finish to complete the transition. 7.
4.3.6 Offline transition using the command-line interface Perform the following steps to perform an offline transition using the command-line interface: 1. Execute the following expdata command on the HMC: expdata -f 2. Execute the impdata command using the following option in the SDMC: smcli impdata -f file Where file is the name of the file containing the HMC configuration data imported from your HMC in step 1.
The flow chart in Figure 4-4 shows a snapshot of the complete transition process. Start Transition HMC Managed Power Systems Public Network Yes Add the managed system and request access to it No Is SDMC DHCP Server? Yes Disconnect HMC from the private network • • • • • • • Connect SDMC to the private network. Configure network interface with DHCP range. Wait 20 minutes. FSPs will have changed IP addresses. FSPs will have gotten new DHCP leases from SDMC. SDMC will auto-discover them.
4.4.1 SDMC as the DHCP server Perform the following steps to perform a transition of managed systems in the private network with the SDMC as the DHCP server: 1. Disconnect the HMC from the private network. 2. Connect the SDMC to the private network. 3. Configure the network interface of the SDMC with the correct DHCP range. The IP addresses of the managed systems might change after the renewal of the DHCP leases from the SDMC. SDMC then auto-discovers the managed systems. 4.
For the second method, perform the following steps to perform a transition of the managed systems: 1. Connect the SDMC to the private network. 2. Configure the SDMC to be a DHCP client of the HMC. 3. Discover the HMC managed system using the IP address or the host name of the managed system. 4. Request access to the managed system. After successful authentication, you can start managing the systems using the tasks available on the context menu of the system.
5 Chapter 5. System management This chapter contains information about how to discover managed systems and perform life cycle management operations on the managed systems. This chapter also contains information about how to perform Capacity on Demand operations using the IBM Systems Director Management Console (SDMC). © Copyright IBM Corp. 2011. All rights reserved.
5.1 System discovery Discovery is the process by which IBM Systems Director identifies and establishes connections with the network-level resources that the SDMC can manage. You can use system discovery or advanced system discovery to identify resources within your environment, collect data about the resources, and establish connections with the resource. SDMC uses the Service Location Protocol (SLP) for discovering resources in the network.
You can launch the System Discovery tool by selecting the Common Tasks menu in the Welcome page or by clicking the System Discovery link available under Inventory in the navigation area. This should launch the System Discovery page (Figure 5-1). Figure 5-1 System Discovery page The discovered resources are displayed in the Discovered Manageable Systems table. The Discovered Manageable Systems table displays only the manageable resources that are discovered during the current discovery.
Verify Connection page The Verify Connection page validates the connection between SDMC and the system. It also ensures that the state of the system is correctly represented. You can verify the connection to your system at any time. You can launch this task from the context menu by right clicking the system and selecting Security Verify Connection. You should see the Verify Connection page (Figure 5-2).
Request Access page Use the Request Access page to request access to a system to which your SDMC has not yet authenticated. Ensure that you have the correct authorization to access the system. You can launch this task only when the Access state of the system is No Access. This task is launched automatically when you click the Access state of the system when the Access state of the system is No Access.
Configure Access page Use the Configure Access page to view the status of Remote Service Access Points (RSAP) on a selected resource. RSAP is a logical address that a system uses to route data between a remote device and the appropriate communications support. RSAP credentials incorporate both source and targeted credentials and mappings between the credentials. The Access states of individual RSAPs are used to evaluate the overall access state for the system.
5.1.2 Discovery of POWER processor-based blades A POWER processor-based blade can be managed in very much the same way that a rack-mount Power System is managed from a SDMC, that is, it is managed directly through the service processor (FSP). By default, the service processor is not available on the network. You must explicitly go into the Advanced Management Module (AMM) and enable this configuration.
The blade servers discovered directly and the blade servers that are discovered through an AMM can coexist in the SDMC environment. SDMC can manage both these blade servers at the same time. 5.1.3 Using the command-line interface You can also use the command-line interface to perform the System Discovery and Request Access tasks. To perform system discovery, run the following command: smcli discover -i The IP address of the system can be either an IPv4 or IPv6 address.
The DHCP service starts after the SDMC installation is completed. You can also manually start or stop the DHCP service by using the following commands: chnetcfg -c dhcp -s enable chnetcfg -c dhcp - disable Starts the DHCP service. Stops the DHCP service. If you removed a system from the SDMC previously, SDMC places the IP address of the removed system in a file. Any IP address in this file is not automatically discovered by SDMC.
5.2 System discovery using the HMC You can also discover and manage systems that are connected to an HMC using SDMC. To accomplish this task, perform the following steps: 1. Open the System Discovery page. 2. Provide the IP address or the host name of the HMC and choose the resource type as All. The discovery process should discover the HMC as a Hardware Management Console. 3. Request access to the discovered HMC by entering the correct credentials for the HMC.
The context menu is shown in Figure 5-4. Figure 5-4 Extended management SDMC does not directly manage the systems connected to the HMC in this setup; they are managed using the HMC user interface. If you want the SDMC to manage the system directly, you must remove the connection of the system from the HMC and discover it from SDMC.
If you want to list the systems on the SDMC that are being directly managed, use the following command: smcli lssys -w “PlatformManagerType=SDMC” 5.3 System management operations After you successfully discover system and request access, you can start managing the system. The managed systems are listed in the Resources tab of the Welcome page. You can also find the managed systems listed in the Navigate Resources page.
Figure 5-5 Edit Host page 5.3.2 Operations page The Operations page includes the tasks for server operations. Right-click the server and select Operations, where you can see the following items: Power On Power Off Change Password Update Password Power Management Launch Advanced System Management Rebuild Managed System Schedule Operations Utilization Data These tasks are similar to the ones in HMC except for Schedule Operations.
The tasks are available based on the current operating state of the managed system. The Update Password task is available only when the state of the managed system is Waiting for Input and the detailed state is Pending Authentication - Password Updates Required. 5.3.3 System Configuration page The System Configuration page includes tasks for configuring your managed system.
5.3.6 Release Management page The Release Management page includes tasks for updating the firmware level of the managed system. It includes the following tasks: Import Updates by FTP POWER Firmware Management Readiness Check Check for Updates Show Needed Updates Show Installed Updates These tasks are explained in detail in 7.1.3, “Power Firmware Management tasks” on page 126. 5.3.7 System Status and Health page This page includes tasks that provide health information about the managed system.
The tasks are explained in detail in Chapter 14, “Service and support” on page 335. 5.3.9 State mappings between HMC and SDMC Table 5-1 presents a mapping of the managed system states of HMC to SDMC. The SDMC has three states that are shown in three different columns.
5.4 Hierarchical management Hierarchical management is a feature available in IBM Systems Director that enables you to configure one IBM Systems Director to be a control point over other IBM Systems Directors. Hierarchical management enables an IBM Systems Director to act as a global server that can discover and manage one or more IBM Systems Director, referred to as domain servers.
5.4.1 Enabling hierarchical management To enable hierarchical management on the SDMC web interface that you want to act as the global server, perform the following steps: 1. Select Settings Server Preferences in the SDMC navigation area. The Server Preferences page opens (Figure 5-6). Figure 5-6 Server Preferences page 2. On the Server Preferences page, check the Enable management of multiple Systems Director Server check box and click OK.
3. Discover the domain server (another SDMC that is connected to managed systems) from the System Discovery page. The domain server is discovered as the Operating System type. 4. Request access to the discovered domain server by right-clicking the server and selecting Security Request Management Access. Note: If you see Request Access instead of Request Management Access, the domain server has not been discovered using the Representational State Transfer (REST) protocol.
5.5 Capacity on Demand Capacity on Demand (CoD) offerings allow you to dynamically activate one or more resources on your server as your business peaks dictate. You can activate inactive processors or memory units that are already installed on your server on a temporary or permanent basis. This section also includes information about how to activate Advanced Functions using SDMC. 5.5.1 Launching the CoD task You can launch the CoD task only on managed systems capable of performing CoD operations.
Right-click the managed system and select System Configuration Capacity on Demand (CoD) to launch the CoD page. The CoD page opens (Figure 5-7). You can perform all CoD operations from this page. Figure 5-7 CoD page The On Demand Type menu has two options: Capacity on Demand and Advanced Functions. 5.5.2 Capacity on Demand Select Capacity on Demand from the Select On Demand Type menu if you want to activate or deactivate CoD processors and memory on your managed system.
Processor Settings and Memory Settings are hyperlinks and clicking any of them takes you to the CoD processor settings and CoD memory settings page, respectively. These hyperlinks are enabled only if the server is CoD Processor Capable and CoD Memory Capable, respectively. The Enter CoD Code, View History Log, and View Code Information tasks are global tasks and are available at top of the table. You can launch the Enter CoD Code and View History Log tasks without selecting any CoD type.
5.5.4 CoD operations You can perform all CoD related operations from the CoD page. These operations are exactly the same as they were on the HMC. The operations include: Enter CoD Code View Code Information View History Log View Capacity Settings Stop Trial View Shared Processor Utilization Manage Chapter 5.
98 IBM Systems Director Management Console: Introduction and Overview
6 Chapter 6. Power Unit management This chapter describes how the IBM Systems Director Management Console (SDMC) handles Power Units, formerly called frames or Bulk Power Assemblies (BPAs). A Power Unit is a power assembly for processor, memory, flexible service processor (FSP), and I/O enclosures. © Copyright IBM Corp. 2011. All rights reserved.
6.1 Power Unit managment When a host is discovered, so are the Power Units. The Power Units are listed in the Resources tab of the Welcome page under the Power Units menu (Figure 6-1). You can also find the Power Units listed in the Navigate Resources page. All the managment tasks are available in the context menu of the Power Unit or in the Actions menu.
6.1.1 Edit Power Unit page You can view and edit the properties of a Power Unit using the Edit Power Unit page. Right-click a Power Unit and select Edit Power Unit to launch the Edit Power Unit page (Figure 6-2). Figure 6-2 Edit Power Unit page The only change you can make to the Power Unit from this page is to give it a new system name. Chapter 6.
6.1.2 Bulk Power Assembly (BPA) Status page You can view the state of the connection from the SDMC to side A or side B of the Power Unit by right-clicking a Power Unit and selecting Connections Bulk Power Assembly(BPA) Status. The Bulk Power Assembly(BPA) Status page opens (Figure 6-3). Figure 6-3 Bulk Power Assembly (BPA) Status page The SDMC operates normally with a Connected connection state to either side A or side B.
You have to enter the current password, then a new password, and verify it by entering it again. If you change the password, you have to update the password on any other SDMCs from which you want to access this Power Unit. 6.1.4 Initialize Frame page You can initialize a Power Unit by right-clicking a Power Unit and selecting Operations Initialize Frame. The Initialize Frame page opens (Figure 6-5).
6.1.5 Launch Advanced System Management page You can open the Advanced System Management Interface (ASMI) page for a Power Unit by right-clicking the Power Unit and selecting Operations Launch Advanced System Management (ASMI). For further instructions, refer to Chapter 13, “Advanced System Management Interface” on page 325. 6.1.6 Power Off Unowned IO Units page An unowned Power Unit can be powered off by right clicking the Power Unit and selecting Operations Power Off Unowned IO Units.
Rebuilding, or recreating, the managed frame acts much like a refresh of the frame information. Rebuilding a frame is useful when the systems state indicator of a Power Unit is shown as Incomplete, which means that the SDMC cannot gather complete resource information from the host within the Power Unit. Chapter 6.
106 IBM Systems Director Management Console: Introduction and Overview
7 Chapter 7. Firmware updates This chapter cover installing and managing firmware on Power Systems from the IBM Systems Director Management Console (SDMC). Although Power Systems are used for the examples in this chapter, the installation and update process is much the same when it is used to update other managed target systems, including the SDMC appliance itself (see 9.5, “SDMC appliance update” on page 271). © Copyright IBM Corp. 2011. All rights reserved.
7.1 Update Manager The Update Manager is the component of SDMC used to perform update installation and maintenance operations on the SDMC managed system environment. This includes the SDMC appliance itself and managed Power Systems. These operations can be accessed from the Update Manager page, which is linked from the Manage tab of the Welcome page of the SDMC GUI (Figure 7-1). Alternatively, individual update tasks can also be initiated by clicking the Action menu on the Resources page.
Chapter 10, “Update Manager”, in Implementing IBM Systems Director 6.1, SG24-7694. In this chapter, we focus on only the basic steps needed for updating and managing the Power Systems firmware and the SDMC appliance itself. However, the steps for installing and managing updates for other selected managed targets (other types of hardware, operating systems, and so on) by using the GUI are actually very similar, with only some minor differences and considerations.
7.1.1 Readiness Check page Before performing any of the installation or management operations on a system, the user should perform a Readiness Check from the SDMC. The Readiness Check page is used to detect whether the system is in a good state before a code update operation is performed. This check alleviates the trouble of starting an installation only for it to fail during the process because of an error that could have been detected before the process started.
Click the Gather Target Information button on the Readiness Check page to run the Readiness Check on the target systems (Figure 7-4). Figure 7-4 Gather Target page Chapter 7.
If the selected system pass the Readiness Check, the Readiness column shows as Passed, and the system has been validated for an update install operation (Figure 7-5). If there is a failure, the reason is displayed and the Readiness column will contain a link to the Problems tab. Figure 7-5 Readiness Check passed 7.1.
SDMC requires more update files for an image than just the .xml and .rpm files; it also requires the .dd.xml, .pd.sdd, and the .readme.txt files. User-controlled timing of an initial program load (IPL) and activation during a disruptive installation is not offered on SDMC. If the user chooses to perform an installation that is disruptive, the IPL (shutdown and reboot) and activation happens in real time during the installation process. The process does not pause for user interaction.
Getting updates The easiest way to check for and download the latest updates is to configure the Update Manager connection settings (the default is for a direct connection, but a proxy server can also be specified) and then click the Check For Updates link from the Update Manager page to auto-check and download applicable updates (Figure 7-6).
The user can then select the type of updates to check for on the Check for Updates page (Figure 7-7) and continue through the wizard to run a check for updates. Figure 7-7 Check for Updates page If the SDMC does not have access to the Internet and cannot be configured to access the IBM Fix Central site automatically, the updates can also be manually downloaded or ordered on DVD media and then imported into the SDMC.
The updates for any IBM hardware managed by the SDMC (including Power Systems and the SDMC appliance itself) can be downloaded from the IBM Fix Central website at the following address: http://www.ibm.com/support/fixcentral/ If you want to run the import operation from the command line, run the smcli importupd' command. Run smcli importupd --help to view the command’s details and examples. Run mount --help to view instructions about using the mount command.
If the USB is formatted for a vFAT file system, run the following command: mount -t vfat /dev/sda1 /mnt/usb The simplest version of importupd to run is: smcli importupd /mnt/cdrom/path/to/install/files Some common options for the importupd command are: -v Verbose output. -r Recurse to find all installable images available under the specified directory. --help Displays the importupd help text.
In the same Common tasks section, there is also a link for Import Updates by FTP, where the user can specify a remote FTP address, directory path, and login information (Figure 7-9).
Updating target systems On the Update Manager page, you can start an installation from the Show needed updates, Show all known updates, or Show update groups pages (Figure 7-10). Make sure to collect inventory on all the target systems that need to be updated before starting the update operations (if not, a message appears before the update starts that provides a button that the user can use to collect inventory before starting the update). Figure 7-10 Installation links from Updates page Chapter 7.
To update the target systems, perform the following steps: 1. To install the latest downloaded updates, start by clicking Show needed updates from the Update Manager page. The Show Needed Updates page opens and shows the Context Chooser dialog box (Figure 7-11). Select the target systems for the installation operation and click Add to add the systems to the Selected list panel on the right. Click OK after making the selections to return to the Show Needed Updates page.
2. The Show Needed Updates page opens and show the system(s) from the selected list. Click the Show Needed Updates button and a table that shows the updates needed by the selected system(s) opens and is populated with the applicable update code (Figure 7-12). Figure 7-12 Show Needed Updates page If no updates are listed in the Show Needed Updates page, click the Show all available updates link to view all updates that have been imported.
Also note the error message that appears at the top of the page stating that an inventory collection has not been completed for some of the selected systems. You need to collect inventory before performing the update process on the target servers. You can accomplish this task by going through the SDMC menus for inventory collection or by simply clicking the View and Collect Inventory button inside the error message. 3.
4. On the Systems page that opens (Figure 7-14), select the target system to which you want to apply the previously selected code update and add the system to the Selected list. Click Next. Figure 7-14 Select target systems Chapter 7.
5. The Options page shows any applicable installation options or any additional required updates (Figure 7-15). Click Next. Note: If the Options page reports that the advanced options could not be retrieved and are unavailable, simply continue with the install wizard.
6. From the Start Target Checks page, initiate readiness and concurrency checks for the selected targets. These checks can take a few minutes depending on the number of targets selected. Click Next to continue. The Target Check Results page (shown in Figure 7-16) opens and shows the results of the checks. An Information message box at the top of the page also shows the estimated time for the selected update task to complete.
7.1.3 Power Firmware Management tasks You can manage firmware on Power Systems using the Resources tab on the Welcome page of the SDMC GUI. Power Firmware Management: Definitions Before start out discussion of Power Firmware Management tasks, we need to define some terminology: 126 T/P-side An FSP has two flash sides: Temporary (T) and permanent (P). They are used in conjunction to perform a backup of a firmware level deemed to be stable and accepted by the customer.
Procedures for Power Firmware Management operations From the Resources tab on the Welcome page on the SDMC GUI, perform the following steps to perform management operations of a Power Systems firmware update: 1. Select the target system(s), and then select Release Management Power Firmware Management from the Action select button (Figure 7-17). Figure 7-17 Power Firmware Management Chapter 7.
The Power Firmware Management page opens (Figure 7-18). As with the readiness check, click Gather Target Info to gather the target information, which populates the table with the selected target system information. The Readiness state of the system must show Passed to proceed with firmware management operations.
2. After the target information is gathered, the Accept/Reject, Disruptive Activate, Synchronize, Remove and Activate, and Set Next IPL Side options are available. The availability of the tasks is side dependent, meaning that, for example, if the P side of the FSP is active, Accept will not be available, and if the if T side is active, Reject will not be available. From the Action menu, click Accept (Figure 7-19). Figure 7-19 Accept Chapter 7.
3. Click the Start Accept Task button (Figure 7-20). Figure 7-20 Start Accept Task The Task Launch dialog box opens and prompts you to run the Start Accept Task now or to schedule it for later. Click OK to run the task now and the Active and Scheduled Jobs page shows the task’s progress. The Complete status appears after the task is successfully run.
8 Chapter 8. Virtual Server operation The Virtual Server operation contains the operations for Virtual Servers. Some of these operation are done on a day-to-day basis, and some of them are done less often. The following topics are covered in this chapter: How to create a Virtual Server. How to activate a Virtual Server. How to shut down a Virtual Server. How to handle the configuration of Virtual Servers. How to do suspend and resume a Virtual Server. How to relocate a Virtual Server.
8.1 Virtual Server creation On the Hardware Management Console, Virtual Servers (formerly know as LPARs) were created using the Systems Management tab and the context menus of the server on which the Virtual Servers were created. Those menus have not changed much, but are now located on the Welcome page of the IBM Systems Director Management Console (SDMC). The new menus have the option to create virtual adapters automatically, which is supported for virtual SCSI adapters and for Fibre Channel adapters.
To create a Virtual Server, perform the following steps: 1. From the Welcome page, locate the host on which the Virtual Server will be created. Check the check box left to the host, then select Actions System Configuration Create Virtual Server (Figure 8-1). Figure 8-1 Welcome page with context menu: Create Virtual Server Chapter 8.
Figure 8-2 shows the wizard that allows you to create a Virtual Server. 2. On the Name page, the name of the server must be entered. Other information, such as Virtual Server ID (the wizard has preset the next free ID already), type of environment (AIX/Linux, IBM i, or VIOS), and settings, such as Suspend capable or Assign all resources to this Virtual Server, can be changed. The Virtual Server created will default to AIX/Linux.
3. When you are creating a Virtual Server for the Virtual I/O Server environment type, some selections will be not available (Figure 8-3). The Suspend enable and Assign all resources to this virtual server options are not available for a Virtual I/O Server environment. Figure 8-3 Create Virtual Server wizard: Virtual I/O Server Name Chapter 8.
4. To create IBM i Virtual Servers, use the Memory menu (Figure 8-4). The difference here it that an additional entry exists, that is, the Load Source/Console pane.
5. The assigned memory can be dedicated or shared (Figure 8-5). The Shared option needs the Active Memory Sharing code to be activated. This activation is only available with PowerVM Enterprise Edition. By default, 1 GB of RAM is assigned to the newly created Virtual Server. If you leave this default on, you can change the amount of memory assigned to the Virtual Server by using the Manage Virtual Server menu (Figure 8-31 on page 165). Figure 8-5 Create Virtual Server: Memory Chapter 8.
6. As shown in Figure 8-6, the default processor mode for Virtual Servers is Shared, which means that processors in a shared pool are used. The shared pool to be used is the default pool and is not shown unless more than one shared processor pool has been created beforehand. In that case, a menu is shown that allows you to select the desired shared processor pool. Note that the assignment of Entitled Capacity values is not possible anymore when creating the Virtual Server.
7. As shown in Figure 8-7, the wizard queries the available Ethernet connections of the Virtual I/O Servers. The first entry in the Virtual Ethernet tab shows a Shared Ethernet Adapter connection that is enabled for failover between Virtual I/O Servers. The second entry shows a Shared Ethernet Adapter that has been enabled for multiple VLANs. All the listed adapters are added to the Virtual Server. Additional adapters can be added by clicking the Add button.
If you would like to add a Logical Host Ethernet Adapter port to the partition, check the box next to the desired adapter listed under Host Ethernet Adapter. The validation check of Live Partition Mobility will note this setting because it is considered a physical adapter for this purpose. This configuration is different from the HMC configuration, but much easier to do because there is no additional information to enter: Just click and you are set.
The ability to add storage adapters automatically when creating a Virtual Server was added to provide legacy support. When chosen, you should rarely need to work on virtual SCSI adapters when creating a Virtual Server. This ability simplifies configuration because manual checks ensure that the correct connection information for the connecting adapter on the Virtual I/O Server was entered and is not needed anymore.
Figure 8-10 Create Virtual Server: Assign storage adapter IDs 142 IBM Systems Director Management Console: Introduction and Overview
10.The results are shown in Figure 8-11. If you decide to add another adapter to a second Virtual I/O Server, click the Add button. Figure 8-11 Create Virtual Server: Manual SCSI adapter creation Chapter 8.
11.If automatic storage adapter creation is chosen (Figure 8-12), additional choices are offered for Virtual Disks, Physical Disks and Fibre Channel disks. You can check any of the check boxes for these choices in any combination.
12.Click Next. The page shown in Figure 8-13 opens. Clicking the Create Virtual Disk button opens a page where the properties of the virtual disk to be created are set. Figure 8-13 Create Virtual Server: Create virtual disk Chapter 8.
As shown in Figure 8-14, the Virtual I/O Server, the name, the disk pool and the size must be specified for the disk to be created.
13.If automatic storage adapter creation for Physical Disks was checked, you can select available disks in all Virtual I/O Servers on the server using the page shown in Figure 8-15. Available disks are defined as disks that are not mapped to Virtual Servers and are not members of a volume group. More than one disk can be selected. If more than one disk is chosen from one Virtual I/O Server, just one virtual SCSI adapter is created.
14.If you select Fibre Channel in the page shown in Figure 8-16, then, on the Storage page, you can see the available Fibre Channel adapters on the Virtual I/O Servers, along with the number of available virtual connections for that adapter.
15.In Figure 8-17, you can select either physical or virtual optical media. A virtual optical device is chosen that contains installation media. Figure 8-17 Create Virtual Server: Optical device and media selection Chapter 8.
16.If you created an IBM i Virtual Server, an additional page is available before you get to the Summary page. This page allows you to specify the load source, the alternate load source, and to assign the console connection to the IBM i Virtual Server (Figure 8-18).
17.The last page in the Create Virtual Server Wizard, the Physical I/O Adapters page, allows you to attach physical adapters to the Virtual Server. Here, for demonstration purposes, a Fibre Channel adapter and an Ethernet adapter are assigned to the Virtual Server (Figure 8-19). Figure 8-19 Create Virtual Server: Assign physical adapters Command-line usage You use the mksyscfg command to create Virtual Servers, just as you did on the Hardware Management Console.
Example 8-1 is a sample command that is used to create an Virtual Server. Example 8-1 Create Virtual Server using smcli mksyscfg sysadmin@sdmca:~> smcli mksyscfg -r lpar -m POWER7_2-061AB2P -i name=myServer,profile_name=DefaultProfile,lpar_id=3,lpar_env=aixlinux,m in_mem=256,desired_mem=6144,max_mem=6144,mem_mode=ded,proc_mode=shared, min_proc_units=0.1,desired_proc_units=4.0,max_proc_units=4.
To activate a Virtual Server, perform the following steps: 1. Right-click the server name and select Operations Activate Profile to activate the Virtual Server with a specific profile (Figure 8-20). Figure 8-20 Activate Virtual Server: Profile option Chapter 8.
2. Select a profile. In our example, we only have the default profile, which is called DefaultProfile (Figure 8-21).
3. Click the Advanced tab and select the options for the keylock position and boot mode (Figure 8-22). Figure 8-22 Activating Virtual Serve: Keylock position and boot mode Chapter 8.
4. The Welcome page opens and shows the state and detailed state of the Virtual Server (Figure 8-23). Figure 8-23 Welcome page: State and detailed state shown after activation The smcli chsysstate command can be used to activate a Virtual Server (Example 8-2).
8.3 Virtual Server shutdown To shut down a Virtual Server, navigate to the Welcome page, right-click the name of the Virtual Server, and select Operations Shutdown (Figure 8-24). Figure 8-24 Shut down a Virtual Server Chapter 8.
The next page (Figure 8-25) shows the available options for shutting down the operations as either Delayed or Immediate. If you click Immediate, you will be asked if a battery is exchanged. If not, click No. Figure 8-25 Shutdown options If you choose to use the command line to shut down the Virtual Server, use the command shown in Example 8-3.
8.4 Virtual Server management The Manage Virtual Server menu option in the Welcome page allows you to customize existing Virtual Servers. In this page, most of the settings previously available in different menus on the Hardware Management Console have been consolidated here. Usage improvements allow for easier navigation and handling of tasks related to Virtual Server management.
To manage the Virtual Server, navigate to the Welcome page, right-click the name of the Virtual Server, and select System Configuration Manage Virtual Server (Figure 8-26).
The page with the General Settings tab opens (Figure 8-27). The settings that can be changed here are shown in boxes, either for text fields or as clickable fields; non-changeable settings appear as text. Figure 8-27 Manage Virtual Server: General Settings Note: The Apply, Reset, and Schedule buttons at the bottom of the page are disabled. These buttons are only activated after you make a change to the displayed settings. If a drop-down menu is changed, the new value of that box is shown in blue.
The Tasks button (Figure 8-28) allows you to execute the following tasks directly from the Manage Virtual Server page: Activate Current Configuration Activate Profile Console page (open and close Console page) List scheduled jobs Mobility (Migrate, Validate, and Recover) Reference Code History Save Current Configuration Figure 8-28 Tasks button in General Settings tab 162 IBM Systems Director Management Console: Introduction and Overview
The Processor page allows you to change the processor related settings of the Virtual Server, including the processor compatibility mode (Figure 8-29). Figure 8-29 Manage Virtual Server: Processor tab Chapter 8.
Note the blue values in the drop-down menu and the changed appearance of the buttons at the bottom of the page (Figure 8-30). In this case, the processor mode is set to Dedicated and the appropriate values for the Shared Processor mode are not shown anymore.
The default memory mode for Virtual Servers is Dedicated and Active Memory Expansion (AME) is enabled by default with an expansion factor of 1.0 (Figure 8-31). This mode enables the setting to be put into effect without requiring a reboot, should you need to use AME later. Figure 8-31 Manage Virtual Server: Dedicated memory settings Chapter 8.
If the memory mode is set to Shared, as shown in Figure 8-32, Advanced Memory Sharing (AMS) has to be active, as it is a PowerVM Enterprise feature and the Virtual I/O Server(s) must be configured for AMS beforehand.
On the following Network tab (Figure 8-33), you can configure virtual network adapters for the Virtual Server. You can also add ports to the Logical Host Ethernet Adapter by clicking the Add button. Figure 8-33 Manage Virtual Server: Network page Chapter 8.
If the check box right to the virtual network adapter is checked, the Edit button becomes active. Click Edit to change the properties of that network adapter (Figure 8-34).
On the Storage Adapters page (Figure 8-35), you can removed existing storage adapters if you check the check box and click Remove. Figure 8-35 Manage Virtual Server: Add Virtual Storage Adapter Chapter 8.
To add an storage adapter, click the Add button (Figure 8-35 on page 169) and enter the desired values for this adapter. A virtual SCSI adapter is added in Figure 8-36.
If you chose to add a Virtual Fibre Channel adapter, the page shown in Figure 8-37 opens. Note that the World Wide Port Names for that adapter are generated automatically, but can be changed later by running the smcli chsyscfg command. Remember that the Apply button has to be clicked to actually execute the operation. Figure 8-37 Manage Virtual Server: Create Virtual FC Storage Adapter Chapter 8.
On the Storage Devices page (Figure 8-38), three types of storage devices can be added: Virtual Disks These disks have to be created on the Virtual I/O Server beforehand to be available in the dialogue. Physical Volumes Physical Volumes have to be assigned to the Virtual I/O server beforehand and are available for selection, as shown in Figure 8-39 on page 173. Fibre Channel To add new virtual Fibre Channel adapters to the Virtual Server, click the Add button.
Figure 8-39 shows the available physical volumes on the Virtual I/O servers. We select hdisk8 on the second Virtual I/O server, P7_2_vios2(2). Figure 8-39 Manage Virtual Server: Add Physical Volume Chapter 8.
The Add Fibre Channel menu allows you to add additional Virtual Fibre Channel adapters. Because no more than one Virtual Fibre Channel adapter per physical Fibre Channel adapter per Virtual Server is supported and one Virtual Fibre Channel adapter already had been created for this Virtual Server, only three physical Fibre Channel adapters are available for mapping (Figure 8-40).
The Media Devices page lets you add media devices to the Virtual Server, that is optical devices, such as CD or DVD drives that are connected to the Virtual I/O Servers. Virtual Media refers to the Virtual Media Library on the Virtual I/O Server that is created and filled with images of CDs or DVDs that then can be made available to Virtual Servers. Figure 8-41 shows the initial Media Devices page. Figure 8-41 Manage Virtual Server: Media Devices page Chapter 8.
Figure 8-42 shows the available Physical Media devices. Click the OK button to add the device to the Virtual Server.
Clicking Add in the Virtual Media section of the Media Devices page opens a list of the available virtual media in the Virtual Media Library of the Virtual I/O Server (Figure 8-43). Figure 8-43 Manage Virtual Server: Adding virtual media Chapter 8.
The task in Figure 8-43 on page 177 creates a Virtual Optical device adapter that is called a Virtual Media Device. After creating the Virtual Media Device, clicking Modify opens a page where the media inserted into the Virtual Media device can be changed (Figure 8-44).
The last page in Manage Virtual Servers (Figure 8-45) allows you to add physical adapters to the Virtual Server. Figure 8-45 Manage Virtual Server: Physical Adapters Chapter 8.
If you click the Add button, the list of physical adapters on the server appears (Figure 8-46). The Display only available physical adapters check box is checked, excluding adapters that are already assigned to a Virtual Server, which reduces the risk of accidentally assigning a physical adapter that is already being used by another Virtual Server to this Virtual Server.
When adding the physical adapters and virtual adapters, there is a short period of time where the addition of the adapter to the Virtual Server is shown as pending (Figure 8-47). Figure 8-47 Manage Virtual Server: Physical adapter addition pending Chapter 8.
8.4.1 Command-line usage Changes to the Virtual Server configuration also can be made using the command line. Run smcli chsyscfg to accomplish this task (Example 8-4). In this example, two physical adapters are added. It is also possible to add virtual adapters. Run the man chsyscfg command for more details about this process.
On the Welcome page, navigate to the Virtual Server and right-click the Virtual Server to access the menu options for Current Configuration and Manage Profile (Figure 8-48). Figure 8-48 Current Configuration and Profile management Chapter 8.
Clicking Save Current Configuration takes you to the Save page (Figure 8-49). Here it is possible to write the Current Configuration to the default profile, thereby overwriting it. Click New Profile to enter a name for the new profile.
8.4.3 Virtual Server Profiles The Virtual Server Profile contains the configuration of the Virtual Server. When the Virtual Server is created, the first profile is also created and is called DefaultProfile. This profile contains all of the hardware resources that were configured on the Create Virtual Server page. Any changes made on the Manage Virtual Server page are not reflected in the profile unless the changes are saved.
Remember that the display of menus is context sensitive and shows only tasks and operations that are available in the current state of the Virtual Server. In Figure 8-50 on page 185, the state of the Virtual Server is Stopped. If the Virtual Server was started and remains in the Systems Management Services (SMS) menu, no Remote Monitoring and Control (RMC) connection is available (Figure 8-51). The available options in the Tasks menu change accordingly.
To access the profiles of a Virtual Server, refer to Figure 8-48 on page 183. Select System Configuration Manage Profiles to open the page shown in Figure 8-52. Figure 8-52 Manage Profiles page Click the Actions button to open a menu where the Save Current Profile entry is added (Figure 8-53). Figure 8-53 Actions menu in Manage Profiles page Chapter 8.
Click Edit to open the Logical Partition Profile Properties menu. This menu allows you to view and edit the properties of the Virtual Server (Figure 8-54). Figure 8-54 Manage Profiles: Edit Virtual Server properties 8.4.4 Server Profiles Server Profiles represent a collection of Virtual Server Profiles that are available on the physical server.
There are initially no System Profiles defined for a server. To create a System Profile, enter a name into the System Profile name field. (This step is mandatory.) Right-click the server name and click Add (Figure 8-55). Figure 8-55 Server Profile initial menu The Create Server Profile page has two panes that show the server and all the Virtual Servers defined on that server. Chapter 8.
Expand the toggle of the Virtual Server to see all the profiles of that Virtual Server. For a Virtual Server, one profile can be selected and added by clicking the Add button. Alternatively, clicking Add All adds all of the last activated profiles to the Server Profile (Figure 8-56). Make sure that the Virtual Server Profiles you add suit your needs to avoid unwanted effects when the Server Profile is activated.
Note that Virtual Servers using shared memory cannot be added to a system profile. If you attempt to add these servers, you will receive a warning (Figure 8-57). Figure 8-57 Server Profile: Warning while trying to add profiles using AMS To remove a Virtual Server Profile from this System Profile, check the check box of that Virtual Server Profile and click Remove. You can also remove all of the contents of the Server Profile by clicking Remove All.
Command-line usage A System Profile can also be defined by running smcli mksyscfg on the command line (Example 8-5). To change the Server Profile, use the chsyscfg command. Example 8-5 Creating System Profile with smcli mksyscfg sysadmin@sdmcb:~> smcli mksyscfg -r sysprof -m POWER7_2-061AB2P -i name=myServerProfile,lpar_names=myServer,profile_names=DefaultProfile 8.5 Suspend and resume Both suspend and resume operations can be done by using the SDMC.
8.5.1 Suspend a Virtual Server To perform a suspend operation on an Virtual Server, perform the following steps: 1. Select Actions Operations Suspend Operations Suspend (Figure 8-58). Figure 8-58 Select Suspend operation from Virtual Server menu Chapter 8.
2. From the Partition Suspend/Resume page (Figure 8-59), you can select Suspend to initiate the suspend operation. You can also select Validate before clicking Suspend to ensure that the Virtual Server is ready for the operation. Figure 8-59 Validate and suspend The Suspend status page shows the progress of the suspend operation and shows a successful completion. 8.5.
The Resume status page shows the progress of the resume operation and shows a success completion. 8.6 Mobility To perform partition mobility operations to move a partition from one physical server to another using the SDMC GUI, perform the following steps: 1. Select Actions Operations Mobility Validate (Figure 8-60). Figure 8-60 Select Validate from the partition page Chapter 8.
2. In the Validate page, the Migrate and View VLAN buttons should be currently disabled (Figure 8-61). Complete the applicable fields for the migration and click the Validate button to validate that the partition is ready for a partition mobility operation. Figure 8-61 Click Validate 3. After the partition has been successfully validated, return to the Validate page. The Migrate button should now be available. Click Migrate.
9 Chapter 9. IBM Systems Director Management Console management This chapter covers the various tasks involved in managing and administrating the IBM Systems Director Management Console (SDMC) hardware and software appliances. We also give a short comparison of SDMC concepts to the concepts used on the Hardware Management Console (HMC).
9.1 User management and security Virtualization means that more than one system is running on the same hardware. Often, different systems are owned by different entities, for example, finance or human resources departments. Depending on the company’s structure, security measurements may require that one user administering the Virtual Server for the finance department must not administer the Virtual Server for the human resources department, even if it is running on the same hardware or in the same pool.
Because the terminology and the structure of user and security management changes from the HMC to the SDMC, the different concepts are shown here to ease transition. User roles The user roles defined on the HMC are shown in Table 9-2. Table 9-2 User roles on the HMC and SDMC HMC user role SDMC user role hmcservicerep Function Service Representative. A service representative is an employee who is at your location to install, configure, or repair the system. hmcviewer SMMonitor, SMUser Viewer.
9.1.2 IBM Systems Director concepts Users in IBM Systems Director are users that are defined in the configured user registry. By default in IBM Systems Director, user creation and assignment to user groups are handled on the user registry level. A user registry is an entity handling users. This entity can be the local operating system of the SDMC, an LDAP server, or a Kerberos server. Each user registry has its own set of users that is independent of those on any other user registry in the network.
sysadmin This is the user designed to be the primary administrator of the SDMC. pe This is the user designed to perform the tasks of the product engineer as defined above for the HMC. Users on the SDMC can be listed by using the smcli lsuser command. In Example 9-1, this command is used to produce a full listing of user properties for the sysadmin user.
User groups The following user registry groups are employed for granting granular access permissions: smadmin (Administrator group) Members of the smadmin group are authorized for all operations. They have administrative access to IBM Systems Director and can perform all administrative tasks. These members can define the privileges available to the smmgr, smuser, and smmon groups. The privileges available to members of the smadmin group cannot be restricted.
Refer to Figure 9-1 for a display of users and their initially assigned groups after installing the SDMC. Also note that roles are assigned to groups and to users. Figure 9-1 Systems Director Management Console: Initial users page As shown in Example 9-2, user groups can be listed on the command line by using the smcli lsusergp command.
AssignedRoles: {'SMAdministrator' applied to } ImpliedRoles: Members: ccfw,sysadmin,root GroupMembership: smmgr: ObjectType: User Group DisplayName: smmgr Description: null ManagedAsGroup: false AssignedRoles: {'SMManager' applied to } ImpliedRoles: Members: pe GroupMembership: smmon: ObjectType: User Group DisplayName: smmon Description: null ManagedAsGroup: false AssignedRoles: {'SMMonitor' applied to } ImpliedRoles: Members: GroupMembership: smservicerep: ObjectType: U
Roles There are four roles that are initially defined on the SDMC: SMAdministrator The Administrator role has full authority to all tasks and commands, including security administration, product installation, and configuration. SMManager The Manager role can perform a subset of the tasks that an Administrator can perform. Typically, system administration, system health management, and configuration tasks are available.
Creating a role To create a role, perform the following steps: 1. Expand Security and click Roles. The Roles page opens (Figure 9-2).
2. Click Create to open the Roles wizard Welcome page. Clicking Next opens the Name page, where a name for this role has to be entered. Optionally, you also can give a description of this role in the Description field (Figure 9-3). Figure 9-3 Create Role wizard: Name page Chapter 9.
3. Clicking Next opens the Permissions page (Figure 9-4). You see a page with two columns, showing Available Permissions in the left column and Selected Permissions in the right column. Above the Available Permissions column, you can select either All Permissions, which gives all permissions to this role, or Selected Permissions. Any entry can be selected and added to the set of Selected Permissions by clicking Add.
4. Click the plus sign next to any role to expand it. All permissions collected in this set can be selected separately and added to Selected Permissions. Click Next to see the Summary page, which shows all the permissions for this role (Figure 9-5). Click Finish to create this role. Figure 9-5 Create Roles: Summary page To define a role using the command line, run the smcli mkrole command (Example 9-4).
Listing roles Roles can be listed using the command line by running smcli lsrole (Example 9-5). Example 9-5 Listing a role using the smcli lsrole command ssysadmin@sdmc:~> smcli lsrole -l myRole myUserRole: ObjectType: InstanceAccessRole DisplayName: myUserRole Description: IsDefaultRole: false IsSystemDefinedRole: false Permissions: AIX Management Deleting a role To delete a role in the GUI, go to the Roles page (Figure 9-2 on page 206). Check the check box left to the role and click Delete.
Groups The concept of groups in the SDMC is equivalent to that of Resource Roles in the HMC. Groups are a collection of resources that are applied to access resources, such as systems and Virtual Servers. Some groups are already predefined in the SDMC (Figure 9-6). To define permissions to a user, a role has to be created. By assigning a group to an user, the role assigned to this user defines the permissions that the user has on the group. Figure 9-6 Groups in the SDMC interface Chapter 9.
Creating a group To create a group, perform the following steps: 1. Click Navigate Resources on the left side of the Welcome page. The Groups page opens and provides a view of the existing groups (Figure 9-7). There is also a description of their properties.
2. Click Create Group to open the Welcome page of the Group Editor wizard (Figure 9-8). Figure 9-8 Group Editor Wizard: Initial page Chapter 9.
3. Enter a name for the group and, optionally, a description on the Name page and click Next. On the Type and Location page, you can set the type of the group, either as Static or Dynamic. Static groups contain systems that are selected at the time of group creation and do not change. Dynamic groups contain systems that match defined conditions, such as State. For the type, Any has to be selected. The Location of the group to be created can be either Groups or sysadmin, as shown in Figure 9-9.
4. Click Next to open the Define page, which allows for a wide selection of resources. On the left side of this page, in the Groups area, you can see a tree of entries. Entries of type All or specific resources can be selected and added to the Selected area of the page immediately by clicking Add (Figure 9-10). Figure 9-10 Group Edit Wizard: Define page with systems selected Chapter 9.
5. To select a single entry, for example, a Virtual Server, click All Systems. A list of Virtual Servers opens. Click the list and then click Add to add this Virtual Server to the Selected area (Figure 9-11).
6. Click Next, and the Summary page that lists the resources assigned to this group opens (Figure 9-12). Figure 9-12 Group Edit Wizard: Summary page Chapter 9.
After clicking Finish, the wizard closes and the new group is shown on the Groups page (Figure 9-13). Figure 9-13 Groups page with the newly created group 9.1.3 Assigning a role to a user Users, roles, and groups allow for a more granular assignment of permissions to a user.
To assign a role to a user, perform the following steps: 1. In the left pane of the Welcome page, click Users in the Security area and check the check box for the user name (Figure 9-14). Click Assign Role. Figure 9-14 Users page: Assigning a role Chapter 9.
2. The Welcome page of the Assign Role wizard opens. Click Next to open the Roles page (Figure 9-15).
3. Select the roles you want to assign to this user and click Next to open the Groups page (Figure 9-16). Multiple groups can be selected, and their resources are added to the set of resources defined for this user. Figure 9-16 Assign Role wizard: Groups Chapter 9.
4. Click Next to open the Summary page, which lists permissions and groups assigned to the user (Figure 9-17). Click Finish to assign the role to the user selected in the first step. This step authorizes the user to perform only those operations that are defined in this role on resources defined in the assigned group. Figure 9-17 Assign Role: Summary 9.1.
Authentication methods Three different authentication methods can be used with SDMC. They are: Local authentication LDAP Kerberos Note: Unlike IBM Systems Director, SDMC can create local users on the underlying operating system. Although the task in SDMC is called Create User Account, it only applies to local user accounts. LDAP and Kerberos users must exist beforehand, using the means of user creation appropriate to those authentication methods. 9.1.
Local authentication To perform local authentication, perform the following steps: 1. Log on to the SDMC as a user that has the SMAdministrator role and thus can create new users. From the Welcome page, click the Settings tab and then click Create user account (Figure 9-18).
2. A page opens where the user credentials can be specified. Refer to Figure 9-19 for the following discussion. Enter the user credentials and click OK. The following fields are required for local authentication: – User ID – Password – Verify password Note that in the annotated field the Authentication type is set to Local OS. Figure 9-19 Create User Account page Chapter 9.
Optionally, you can specify a user description (Description), an SSH session timeout (the default is 0, which means no SSH session timeout), and an password expiration (the default is 180 days). By default, the box for membership in the smuser local OS group is checked. If necessary, the group membership can be changed or added to by checking the boxes for the smadmin, smmgr, and smmon local OS groups. The mkuser command can also be used to create a user.
Users need only one user ID and password, as opposed to multiple accounts for each management server. Note: Order might matter when configuring the SDMC as an LDAP client. If LDAP authentication and authorization is switched on, all user authentication and authorization relies on it. To avoid unwanted effects, make sure that users with sufficient properties exist in LDAP beforehand. Important: You are required to gather at least the following information before configuring LDAP authentication for SDMC.
--bindpw password --loginattr uid --groupfilter '(|(objectclass=groupOfNames)(objectclass=groupOfUniqueNames))' --userfilter '(objectclass=ePerson)' --memberattr member --descattr description Note: After configuring SDMC for LDAP authentication and authorization using the cfgldap command, restart SDMC so that the changes can take effect. Use the smcli lsldap command to display information about the current LDAP configuration of the SDMC.
Another method to configure SDMC for LDAP user management is by using a GUI. In the Welcome page, select Security Tasks Configure LDAP client, as shown in Figure 9-20, to start LDAP client configuration. Figure 9-20 Configure an LDAP client After clicking the link, the Welcome page of the Configure LDAP client wizard walks you through the required steps to access information on the LDAP server.
The Welcome page of the LDAP client configuration wizard is shown in Figure 9-21. Figure 9-21 Configure LDAP client wizard After configuring the LDAP client, a user can be added to the SDMC by clicking Create user account on the Welcome page (Figure 9-18 on page 224). You must instruct the Create User Account wizard to use LDAP as the authentication method by clicking the Authentication type drop-down menu and selecting LDAP.
Figure 9-22 shows how to create a user for LDAP authentication. No other information is needed besides the user name that must already exist on the configured LDAP server, so all the other input fields are disabled. Figure 9-22 Create User Account: LDAP For command-line usage, Example 9-10 gives an example of how to use the mkuser command with LDAP authentication for the specified user.
Note: A user with LDAP authentication can be created anytime, regardless of the LDAP client configuration. However, access to the system is denied as long as the LDAP client for the SDMC is not configured. To avoid unwanted effects, make sure that the user created has sufficient privileges to access the SDMC after the LDAP client has been configured because all authentication and authorization is then switched to LDAP! Kerberos SDMC allows for Kerberos authentication.
SDMC can be configured as a Kerberos client in the GUI by clicking the Configure Kerberos client link on the Welcome page (Figure 9-23). Figure 9-23 Configure Kerberos client page Chapter 9.
After clicking the link, a wizard walks you through the required steps to complete this task (Figure 9-24).
After configuring the Kerberos client, a user can be added to the SDMC by clicking Create user account in the Welcome page (Figure 9-18 on page 224). The Create User Account wizard then must be instructed to use Kerberos as authentication method by setting the Authentication type select box to Kerberos (Figure 9-25).
Example 9-12 provides an example about how to use the mkuser command with Kerberos authentication for the specified user. Example 9-12 mkuser command with Kerberos credentials sysadmin@sdmca:~> smcli mkuser -u newUser -x usertype=kerberos User created successfully Note: A user with Kerberos authentication can be created anytime, regardless of the Kerberos client configuration. However, access to the system is denied as long as the Kerberos client for the SDMC is not configured.
Modifying user properties After the new user account has been created, its properties can be modified. To accomplish this task, expand Security in the left pane of the SDMC interface. Click Users to open the Users page (Figure 9-26. Figure 9-26 Users page Chapter 9.
Click the newly created user to open the User properties page (Figure 9-27). In this figure, the general properties of the user are shown and can be modified by clicking Edit.
All of the listed attributes can be changed except the first two, which were defined when the user was created. Figure 9-28 shows how you can change those attributes. Figure 9-28 Edit user properties: General tab It is also possible to modify the user information using the smcli chuser command (Example 9-13). This addresses another set of user attributes, namely those that can be set with the mkuser command.
Deleting users To remove a user using the command line, run smcli rmuser (Example 9-14). Example 9-14 Deleting a user with the smcli rmuser command sysadmin@sdmca:~> smcli rmuser -u newUser User deleted successfully In the GUI, there is a link at the bottom of the Welcome Settings page that explains how to remove a user. 9.2 Network configuration This section describes the network configuration of the SDMC with the GUI and the CLI and how to test the network configuration.
To take advantage of the additional security and ease of setup, implement service network communications through a private network. However, in some environments, this is not feasible because of physical wiring, floor planning, or control center considerations. In this case, the service network communications can be implemented through an open network. The same functionality is available on both types of networks, although the initial setup and configuration on an open network require more manual steps.
To view and change the network settings go to the Settings tab on the Welcome page and, under Configurations tasks, select Configure Network (Figure 9-29).
When you select it, the network configuration wizard starts (Figure 9-30). Figure 9-30 Network Configuration wizard LAN adapter In the first page, you have to select the LAN adapter you want to configure. After selecting and clicking Next, you have to decide if you will use Standard network interface or Configure System as a DHCP server. Chapter 9.
DHCP If you select Configure System as a DHCP server, you get a page where you can select a range for the DHCP server and select an address for the LAN adapter that serves as a DHCP server (Figure 9-31).
IP address If you select Standard network interface, you get a page where you can select if you want to use IPv4 or IPv6 and if the interface will be a DHCP client or have a static IP address (Figure 9-32). If you select a static IPv4 address, you can specify the IP address and the network mask. In the case of a static IPv6 address, you can give the address and a list of prefix lengths. Figure 9-32 Setting a static IP address Chapter 9.
Firewall After selecting a DHCP or static IP address, the Firewall menu opens, where you can select which ports are allowed for the interface and which are not. You can restrict for which hosts traffic over a given port is allowed. Table 9-3 provides a list of the standard ports that are available for configuration with the application that corresponds to it and if it is allowed by default. Recommendation: For the firewall settings, leave them at their defaults for the appliance.
Application Port(s) Allowed IBM Systems Director Console HTTP Access 8421:TCP No Common Agent Service(CAS) 9510:TCP Yes Agent Manager 9511:TCP,9512:TCP,9513:TCP Yes LWI Nonstop Port 9514:TCP,9515:TCP Yes Event Received Port 13991:UDP No IBM DB2® Universal Database™ databases 50000:TCP No Storage Event Port 10000:TCP No CAS Event Port 20000:TCP Yes IPC Support 14251:UDP Yes Virtual Network Computing 5901:TCP No IPC Support for Director 5.
Application Port(s) Allowed HW Server 8899:TCP Yes Distributed Replicated Block Device 7789:TCP Yes Remote Web Access (HTTP) 80:TCP Yes Remote Web Access (HTTPS) 443:TCP Yes Information Center 8091:TCP Yes After configuring the firewall, the LAN adapter page opens again, where you can choose to configure another Interface using the Select another Adapter option. If you do not want to configure another interface, click Continue Wizard.
DNS In the next page, you can specify one or more Domain Name Services (DNS) server and build a domain search order (Figure 9-34). Figure 9-34 DNS menu Summary In the last page of the wizard, you receive a summary of your selections. You can always go back and make some changes to your selections. If you are satisfied with your selection, click the Finish button. Chapter 9.
Network reconfiguration In the next page, a job is scheduled for the reconfiguration of the network (Figure 9-35). Figure 9-35 Job for network configuration You should select Run Now and click OK. You receive a notification about the scheduled job (Figure 9-36).
You can close this page by clicking close. You can see the status of the job by selecting Task Management Active and Scheduled Jobs (refer to Chapter 11, “Schedule operations” on page 289 for more information). Most network changes require a reboot of the SDMC. When you get back to Configure Network page, you see the “Recent changes require a restart to be performed” message and an exclamation mark in front of the Configure Network task when a reboot is necessary (Figure 9-37).
9.2.2 Configuring network settings using the SDMC CLI You can also view and change network settings using the SDMC CLI. Viewing network settings To view the network settings, use the lsnetcfg command. For example, to view all network settings, except the firewall settings, run the following command: lsnetcfg -n To view all the firewall settings, run the following command: lsnetcfg -f For further options, refer to the man page for lsnetcfg. Note: The lsnetcfg command has to be used without the smcli prefix.
9.2.3 Testing network connectivity The network connectivity can only be tested by using the ping command (Example 9-15); you cannot perform this function from the GUI, as you could in the HMC. Example 9-15 Testing network connectivity using ping sysadmin@sdmc2:~> ping sdmc1.itso.ibm.com PING sdmc1.itso.ibm.com (172.16.20.26) 56(84) bytes 64 bytes from sdmc1.itso.ibm.com: icmp_seq=1 ttl=64 64 bytes from sdmc1.itso.ibm.com: icmp_seq=2 ttl=64 64 bytes from sdmc1.itso.ibm.
Backup To perform the backup, perform the following steps: 1. Check if the system is a Hardware Appliance. If the system is Virtual Appliance, the backup method is different based on the hypervisor used on the host (RHEV-H Blue or VMWare). So the backup operation is permitted only when the system is a Hardware Appliance. Refer to 9.3.2, “SDMC software appliance backup and restore on VMware” on page 256 and 9.3.
Here is our example of this command: backup -l usb -Y 6. The backup command starts the IBM Systems Director in the background. 7. If you back up the system to a USB disk, remount the drive to see the backup file.
-l The location to store the backup file. If sftp is specified, the -s argument is needed to set the SFTP server. -s Specify SFTP server when -l sftp is specified. -n Specify the restore file name with the abstract path, for example, /data/backup/20101011.tar.gz. -u The user used to connect to the SFTP server. -p The password used to connect to the SFTP server. Here is our example of this command: restore -l usb -Y 4. Restart the IBM Systems Director in the background. Note: If you 9.3.
2. Select the virtual machine which want to back up, right-click it, and select Snapshot Take Snapshot (Figure 9-38). Figure 9-38 Take snapshot from vSphere client Chapter 9.
3. Enter the snapshot name and description, and create a new snapshot of the selected VM (Figure 9-39).
4. The snapshot is stored on the host. To copy it to another reliable location, select the host in the vSphere Client, and click the Summary tab in the right column. In the Datastore section, right-click the datastore1 item and select Browse Datastore… to open the Datastore Browser page (Figure 9-40). Figure 9-40 Selecting data store 5. In the Datastore Browser, download the virtual disk and the associated snapshot files to any location.
Steps for restore using the VMware vSphere Client To perform a restore using the VMware vSphere Client, perform the following steps: 1. Select the virtual machine that you want to restore using a specific snapshot. 2. Right-click the virtual machine and select Inventory Virtual Machine Snapshot Revert to Current Snapshot to restore the most current snapshot (Figure 9-41).
3. You can also select to restore from other snapshots by selecting the Snapshot Manager and choosing to restore from a specific snapshot. Select the snapshot to be restored and click the Go to button (Figure 9-42). Figure 9-42 Snapshot manager Note: The current state of the virtual machine is lost if you do not perform a snapshot of the current environment before restoring from another snapshot. 9.3.
KVM backup procedure The SDMC software appliance back up on KVM requires LVM support in the host environment. The system administrator must check if the host file system has at least 150 GB free disk space for the snapshot. To back up the SDMC software appliance on KVM, complete the following steps: 1. Check for a minimum of 150 GB of available space by running the following command: vgs -o +vg_free_count,vg_extent_count 2. List the logical volumes by running the following command: lvdisplay 3.
11.Create the SDMC /Snapshot_LV_Dir/sdmc/data/images directory by running the following command: cd /Snapshot_LV_Dir/sdmc/data/images/ 12.Compress the Snapshot_LV_Dir/sdmc/data/images/* directory and time it by running the following command: time tar -Spczf /Backup_Dir/vmidata.tar.gz * 13.List the /Backup_Dir directory by running the following command: ls -l /Backup_Dir/ 14.
ls rm -rf * 4. Extract the tarball to the images directory and time it by running the following command: time tar -zxvf /Backup_Dir/vmidata.tar.gz 5. Check the disk usage by running the following command: dfStart the virtual machine by running the following command: virsh start sdmc-pele 9.4 Problem determination This section describes the various logs available for problem determination, how to view the logs, how to configure them, and how to capture them for transmitting them to IBM. 9.4.
Log file Description /var/hsc/log/iqzdtrac.trm This log files contains information related to Common Console Framework (CCFW). This framework is part of the SDMC GUI. /var/hsc/log/hmclogger.log This log file contains generic information about all operations done using SDMC. Chapter 9.
Trace logs in GUI You can view the trace logs of the SDMC using the graphical user interface. This task is available only for the pe predefined user. The trace logs information opens a browser page. You can select the classes or you can specify the log file name to view specific log information. This interface is exactly the same as it was on HMC. You can launch this task from the Settings tab of the Welcome page.
9.4.2 IBM Systems Director logs The log files related to IBM Systems Director are located in the /opt/ibm/director/lwi/logs/. These log files are critical in determining and analyzing problems, mostly problems related to the GUI in SDMC. The available log files and their description are given in the Table 9-5. Table 9-5 IBM Systems Director logs Log file Description /opt/ibm/director/lwi/logs/trace-log-*.
SDMC allows you to configure the settings for the trace and error logs. This task is available for the users with the SMAdministrator role. Select Console Logging and Tracing under Settings in the navigation area. You should see the Console Logging and Tracing Configuration page as shown in Figure 9-44. Figure 9-44 Console Logging and Tracing Configuration Table 9-6 provides the details about the changes that you can make to logging and tracing configuration.
Setting Description Maximum number of historical files Changes the maximum number of historical or rotated log files that you want to retain in the file system. Formatter name Changes the formatter to change the format of the log information in the log file. Trace Detail Levels You can enable or disable logging for individual components or managers in SDMC and also define their trace levels.
The usage of the pedbg command is as follows: pedbg [ -d [on | off] | -c | [-c & -q [n]] | -r ] ] Where: -d on | off Controls debug tracing by restarting subsystems to start or stop internal tracing. -c Collects various logs and core files. -D data_directory Specifies the directory to which to save collected data. If this option is not specified, the current home directory is used.
Run the lsconfig -v command to obtain the UVMID: sysadmin@dd174:~> lsconfig -v vpd=*FC ???????? *N2 Tue Jan 18 19:31:05 CST 2011 *DS SDMC *TM System x3550 M3 -[7042CR6]*SE 10F39AB *MN IBM *OS Embedded Operating Systems *NA 9.3.116.174 *RM 6.730.
There are three types of SDMC appliance updates: Service pack updates Interim fix/hot fixes Upgrade/Release levels Service pack updates are cumulative, while interim fixes are not. As with the updates for other types of target systems, you need to acquire the appropriate update downloads and collect inventory on the SDMC appliance to determine the updates that should be applied.
To auto-check and download applicable updates (which is easiest if the SDMC has access to the Internet), click the Update IBM Systems Director link from either the Update Manager page or the top left side of the Welcome page (Figure 9-45). This action initiates the process to download and install the latest applicable updates; simply follow the subsequent panels. Figure 9-45 Update IBM Systems Director link Chapter 9.
If the SDMC does not have access to the internet, the manual procedures for installing and managing SDMC appliance updates are similar to using the Update Manager for Power System server update operations. The only difference is that you download the appropriate SDMC appliance updates and, within the Update Manager Install Wizard, select the SDMC appliance as the target system for the update operation (Figure 9-46).
10 Chapter 10. Command-line interface This chapter discusses the command-line interface (CLI) of the IBM Systems Director Management Console (SDMC) with regard to the Hardware Management Console (HMC) CLI.
10.1 SDMC command-line interface In the SDMC CLI there are three types of commands: IBM Systems Director appliance commands IBM Systems Director application commands Power Systems management commands The IBM Systems Director appliance commands, as the name indicates, are the commands that allow you to manage and maintain the appliance. The IBM Systems Director application commands typically allow users to discover, view, and manage resources in the Director.
Table 10-1 provides a listing of the most important IBM Systems Director appliance commands and their usage. For the syntax, refer to the man page for each command or go to the following address and select Reference Commands smcli: http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp/ Table 10-1 Listing of IBM Systems Director appliance commands IBM Systems Director appliance command Note cfgkrb This command configures Kerberos for the SDMC.
IBM Systems Director appliance command Note sendfile This command transfers a file to a remote system by using File Transfer Protocol (FTP) or secure FTP (SFTP). setloginmsg This command sets the text displayed at login. smha This command administers the high availability configuration. smhastatus This command displays the status of the high availability configuration. smstart This command starts the Director server. smstatus This commands shows the status of the Director server.
Availability/mkvsmfarm Availability/mkvsmmigratetask LEDCLI/chled LEDCLI/lsled auditing/chaudit auditing/lsaudit As you can see, the IBM Systems Director application commands have different paths. Every application command can also be called using its respective path: smcli Some application commands are identical (for example, list and lsled), but have different paths.
IBM Systems Director application command Note configureHA This command configures nodes for high availability. discover This command discovers resources. lsbundle This command lists all the available application commands. lsgp This command lists the currently defined groups. lsresources This command lists the available resources. lsrole This command lists the roles in IBM Systems Director. lssys This command lists the systems. lsuser This command lists an IBM Systems Director user.
psm/chled psm/chlparstate psm/chlparutil psm/chpwrmgmt psm/chstat psm/chsvc psm/chsyscfg psm/chsyspwd psm/chsysstate psm/chtunecfg psm/chvet psm/cpdump psm/cpsysplan psm/deploysysplan psm/dump psm/getdump psm/impdata psm/lpcfgop psm/lscod The Power Systems management commands can also be prefixed with the smcli psm keyword. Alternatively, most of the Power Systems management commands are aliased, so that they could be run directly without the smcli or smcli psm prefix as well.
The output of the Power Systems management commands on the SDMC is the same as it used to be on the HMC, as shown in Example 10-3.
HMC command Usage of command Changed bkprofdata Backs up profile data for the managed system. The -o option will be ignored by SDMC. chcod Performs Capacity on Demand operations on the managed system. No change. chhwres Changes the hardware resource configuration of the managed system. It is also used to perform dynamic logical partitioning operations. A new attribute, pend_mem_region_size, is added. chled Changes the state of an LED on the managed system.
HMC command Usage of command Changed cpdump Copies managed system dumps and managed frame dumps from the SDMC to DVD or a remote FTP site. No change. deploysysplan Deploys a managed systems partition plan from a system plan file. No change. dump Sets the system dump parameters for the managed system. No change. getdump Off loads a dump from the managed system or the managed frame to the SDMC. No change. getriotopology Shows the topology of the RIO cabling. No change.
HMC command Usage of command Changed lslock Lists which SDMC owns the lock on the managed frame. No change. lslparmigr Lists partition migration information. No change. lslparutil Lists utilization data collected for a managed system and the SDMC. The new states primary_state and detailed_state are added. These attributes are listed by default The old state attribute is displayed only when queried with the -F option. The -r hmc option is not supported.
HMC command Usage of command Changed lsvet Lists Capacity on Demand advanced functions activation information for the managed system. No change. migrlpar Performs Virtual Server migration operations. No change. mkauthkeys Manages SSH authentication keys. No change. mksyscfg Creates partitions, partition profiles, or system profiles for the managed system. No change.
HMC command Usage of command Changed rmsysconn Removes or resets a connection from the SDMC to a managed system or a managed frame. The -o remove option is no longer supported. Use the smcli rmsys command instead. rmsysplan Removes a system plan file from the system plan file directory on the SDMC. No change. rmvterm Forces the closure of a virtual terminal session for an AIX, Linux, or virtual I/O server. No change.
288 HMC command SDMC replacement chaccfg smcli chrole. chhmc chnetcfg. chhmcencr No replacement available. chhmcfs No replacement available. Done by a task. chhmcldap cfgldap. chusrtca setloginmsg. expdata No replacement available. getfile No replacement available. getupgfiles No replacement available. hmcshutdown No replacement available. hmcwin No replacement available. lshmcusr smcli lsuser. lslogon No replacement available. lsmediadev lsmediadev (Director version).
11 Chapter 11. Schedule operations In this chapter, we describe how to schedule operations for certain tasks, such as activating a system or partition using a specific profile, backing up profile data, or turning on off a managed system without operator assistance. A lot of IBM Systems Director commands can be scheduled, and schedule operations allows you to schedule a select number of Power Systems specific commands. © Copyright IBM Corp. 2011. All rights reserved.
11.1 Scheduling operations for managed systems and Virtual Servers To schedule operations for managed systems and Virtual Servers, right-click the managed system or the Virtual Server and select Operations Schedule Operations (Figure 11-1).
Power On Manage Utility CoD Modify Shared Processor Pool Modify Virtual Server Pool Assignment Modify Power Saver Mode For Virtual Servers, you get a selection list that has following task options: Activate Shutdown ChangeI/O Change Processors Move Processors Change Memory Move Memory For some of the tasks, you have further options you can specify. For example, for the Backup Profile Data task you can specify a file name (Figure 11-2).
Click OK, and the Task Launch Dialog page opens (Figure 11-3). Figure 11-3 Task Launch Dialog page Here you can schedule a job for the task, set notifications, or set further options. 11.1.1 Schedule tab On the Schedule tab, you can specify a job name and when to run the job. For the job to run, you can select between Run Now or Schedule. If you schedule it, you can select between different repeat options: 292 Once You can specify a specific date and time when to run the task.
Monthly You can specify the duration of how long the job repeats, if the job should run on weekends, and on which day of the month the job should run. Yearly You can specify the duration of how long the job repeats and if the job should run on weekends. Custom You can make your own list of dates of when the job should run. 11.1.
11.1.4 Creating the job When you have made your selections in the Task Launch Dialog page, click OK. A notification about the successful creation of your job opens (Figure 11-4). Figure 11-4 Successful creation of a job If you click Display Properties, you can see the properties of the job you just created. 11.2 Editing, deleting, and copying, and viewing the properties of a scheduled operation To edit, delete, or copy a scheduled operation, you have to go to the Active and Schedule Jobs task.
Figure 11-5 shows an overview over the scheduled, active, and completed jobs. Figure 11-5 Active and Schedule Jobs overview When you select a job, you can edit or delete it, or you can create a new job by copying the selected job. Chapter 11.
If you click a job, you can view the properties of the selected job (Figure 11-6). Figure 11-6 Job Properties page Under the General tab, you can view the status of the job and other general properties. The Targets tab shows the specified managed system(s) or Virtual Server(s) to which the job is assigned. The History tab shows when the specified job has been run and with which status. The Logs tab shows a detailed output of the job. Figure 11-7 shows the output of a successful backup of the profile data.
11.3 Automation Manager If you select the Automation Manager on the main Manage tab, you get an overview over the jobs (scheduled, completed, and failed) in the last 30 days. You see the three next jobs that will be running and you see the three most recent jobs, as shown in Figure 11-8. Figure 11-8 Automation Manager From within the Automation Manager, you can go to the Active and scheduled Jobs task, from where you can manage the jobs, as described in 11.
298 IBM Systems Director Management Console: Introduction and Overview
12 Chapter 12. High availability and redundancy Implementing IBM Systems Director Management Console (SDMC) in a high availability (HA) or a redundant setup can provide improved serviceability to the SDMC appliance and provides backup to the system in case of a disaster. © Copyright IBM Corp. 2011. All rights reserved.
12.1 Systems Director Management Console High Availability versus redundant setup Users familiar with the redundant HMC setup in their Power Systems environment can use the same setup in SDMC, as multiple SDMCs can connect to and actively manage a single managed server. Users can also implement SDMC High Availability, which provides active/passive failover capability, with one active SDMC and one passive SDMC on standby to take over in case of failure.
For an environment where the SDMC is used for agent OS management and there is a high availability requirement for that functionality, SDMC High Availability is needed. If your active SDMC fails, the passive standby SDMC automatically takes over and management functionality for the managed systems is restored in about 10 minutes. There are some extra planning, setup, and administrative steps required to implement SDMC High Availability.
For this setup, configure an SDMC (A) to point to the active agent manager running on another SDMC (B). From the GUI on SDMC A, go to the Settings category in the left pane and click Agent Manager Configuration. Click Add on the Agent Manager Configuration page, which opens and configures the agent manager using the IP address and agent manager user ID and password for SDMC B (Figure 12-2). Figure 12-2 Add an New Agent Manager 12.
Figure 12-3 shows both the software and hardware stack that of an SDMC High Availability environment. These internal software components that make up SDMC High Availability are transparent to the user and do not need to be directly configured. IBM Tivoli System Automation for Multiplatform (TSA) is used to monitor the hardware and software stack. It also provides failover and quorum capability. Data is mirrored using Distributed Replicated Block Device (DRBD).
Running the setup wizard or using CLI commands on the SDMC designated to be the primary node configures the internal High Availability components on both the primary and secondary SDMCs. Figure 12-4 shows the SDMC High Availability configuration sequence that sets up the two SDMCs in an High Availability cluster.
Primary node This is the node you use to set up high availability. It is initially the active node. When you set up a high availability cluster, the IBM Systems Director data, remote authentication configuration settings, users, and firewall settings on this node are replicated to the secondary node. Secondary node This is the node that you set up to take over if the primary node fails. It is initially the passive node, but takes over as the active node if the primary node fails.
12.2.3 SDMC High Availability processes monitored These are the processes monitored by the SDMC High Availability for a redundant takeover: Director DB2 DRBD CIM Server High Availability MQ Daemon (MQ server) High Availability Daemon (Processes MQ messages) NTP Server DHCP Server 12.2.4 Active/Passive High Availability: Log location Here are the locations of the SDMC High Availability log files: /opt/ibm/director/ha/logs/, which contains: daemon0-x.
12.3 Active/Passive High Availability: Configuration planning You need to plan the setup of SDMC High Availability, and there are several considerations and issues to be aware of in setting up and administrating this environment: Both SDMCs must be at the same code level prior to the High Availability configuration. SSH must not be blocked by the firewall during the initial High Availability configuration. Data on the secondary node is lost during the High Availability configuration.
12.3.1 Network requirements Because data is continually replicated between the two cluster nodes, carefully consider your networking topology. Figure 12-5 shows a diagram of a typical SDMC High Availability environment. Note that the SDMC provides network path redundancy through two connections to each Flexible Service Processor (FSP) of a managed system.
Replication IP address Because the replication IP address on each of the two SDMC nodes in the High Availability cluster is used to constantly synchronize data, it is important that this network connection be fast as possible. Guidelines for the replication IP address The guidelines for the replication IP address are: If possible, use a separate private network for replication between the nodes for better performance and place the two SDMCs within close range.
Choose an address that each node can reach by a single path. If there are multiple paths, it is possible that one path is down, causing the ping to fail, when the node is online. Do not use an address that either node uses, including the floating IP address. The gateway address for the SDMC is a good candidate to use as a network status IP address.
12.3.2 DHCP considerations The SDMC cannot be a DHCP client. If your network is set up so that one DHCP server is running at a time (you have one range of DHCP addresses), then both the SDMC network configurations must be identical and each network interface card (NIC) must be connected to the same networks on each node. For example, if eth0 is connected to the 192.168.1.0 network segment on the primary node, then eth0 on the secondary node must also be connected to the same segment.
Shared DHCP configuration The DHCP server is only run on the active node. Configure the first node as using DHCP server with a specific address range. Choose the first reserved address for the node. Configure the second node as a standard network configuration and choose the second reserved address for the node.
12.4.1 Configuration using SDMC High Availability setup wizard Perform the following steps: 1. Open up the IBM Systems Director Management Console GUI using a web browser and log in as the sysadmin user. In the left navigation pane, expand Settings and click High Availability Settings. The High Availability Settings page opens. Click Set Up High Availability. Figure 12-7 shows the initial page as you start the High Availability setup process.
2. The Welcome page for the High Availability setup wizard (Figure 12-8) shows the SDMC as the primary node that you are using to perform the configuration. It reminds the user of prerequisites and provides links to support documents for more information about High Availability. Click Next to begin setup.
3. In the Secondary Node setup page (Figure 12-9), enter the IP address or host name and the password for the sysadmin user on that SDMC. Click Next. Figure 12-9 Secondary Node page 4. In the Network Time Server page (not shown), specify the IP address for a network time server or choose a primary node as the time server for both nodes. Click Next. Chapter 12.
5. In the Replication IP Address page (Figure 12-10), specify the IP addresses to use for data replication between the two nodes (one on each node). Click Next.
6. If you want a network status IP address, determine an appropriate IP address and enter it into the Network Status IP address page (Figure 12-11). Click Next. Note: A good choice for this address is the SDMCs gateway IP address. Figure 12-11 Network Status IP address Chapter 12.
7. Determine the available IP address to be used as the floating IP address and enter this address at the Floating IP Address page (Figure 12-12). Click Next.
8. If you use Systems Director Common Agent Services, you must specify an agent manager IP address so that the active node can manage the agents. Figure 12-13 shows the Agent Manager IP Address page in the setup wizard. Click Next. Figure 12-13 Agent Manager IP Address page Chapter 12.
9. The final page (Figure 12-14) shows the summary of all the configuration inputs entered during the setup. Review the information and click Finish. Figure 12-14 Summary page While high availability is being configured, Systems Director is shut down on both cluster nodes. During this time, information is copied from the primary to the secondary node. The speed of your network determines how long the replication takes. To monitor the status of the configuration, perform the following steps: 1.
After the configuration completes, you can use the floating IP address to connect to the Systems Director server on the active node. 12.4.2 Steps to install High Availability using the CLI As an alternative to the graphical user interface, you can use the SDMC command-line interface to configure and administrate High Availability. To configure High Availability using the CLI, connect, using an SSH session, to the SDMC that is designated to be the primary node in the High Availability cluster.
12.5 Active/Passive High Availability: Updates For the initial release of the SDMC, you must update it by performing the following steps: 1. 2. 3. 4. The active node must be updated. A manual failover must be performed. The new active node that was previously passive must now be updated. Another manual failover must be performed. Updates only need to be downloaded once, as the update repository is mirrored between the two SDMC nodes. Both nodes should be updated in sequence in a timely fashion.
Note: You should not deviate from the above procedure, or you might reload both nodes. Currently, upgrading mirrored data imposes restrictions on when you activate the new code (although this may be changed in future releases). The Director data is at a Snapshot level that is equivalent to when you started the upgrade. Events received during the upgrade will be lost.
324 IBM Systems Director Management Console: Introduction and Overview
13 Chapter 13. Advanced System Management Interface In this chapter, we describe how to log in to the Advanced System Management Interface (ASMI) using the IBM Systems Director Management Console (SDMC). The ASMI provides a terminal interface through a standard web browser to the service processor that allows you to perform general and administrator level service tasks. The ASMI allows you to perform service functions and various system management functions.
13.1 Connecting to ASMI using the SDMC To connect to the ASMI using the SDMC, perform the following steps: 1. On the SDMC Resources tab, select the managed system to which you want to connect through ASMI. 2. Right-click the managed system name and select Operations Launch Advanced System Management (ASM) (Figure 13-1).
3. A page opens that has a drop-down menu for the service processor to which you want to connect (Figure 13-2). Figure 13-2 Selecting the Service Processor Chapter 13.
4. A new browser page opens with the login page of the ASMI (Figure 13-3). Figure 13-3 ASMI login We only give here an overview of the ASMI menu and a brief description of the functions. For further information, refer to Chapter 14, “Advanced System Management Interface”, in Hardware Management Console V7 Handbook, SG24-7491.
13.2 Connecting to ASMI using the CLI To connect to the ASMI using the SDMC command-line interface, you must have an X-Server on your local machine. Connect remotely to the SDMC command line through an SSH connection and export your display. Here is an example, with the IP of your local machine, of exporting the display: export DISPLAY=”172.16.254.
System Dump Initiates a system dump. Service Processor Dump Initiates a service processor dump. Partition Dump This function is not available when your system is connected to the SDMC. Serial Port Setup This function is not available when your system is connected to the SDMC. Modem Configuration This function is not available when your system is connected to the SDMC. Call-Home/Call-In Setup This function is not available when your system is connected to the SDMC.
Memory Serial Presence Detect Data Shows manufactures data of detected memory modules. Firmware Maintenance History Shows the history of service processor firmware updates. System Configuration System Name Lets you change the system name Configure I/O Enclosures Lets you configure I/O enclosures. Time of Day Lets you change the systems current data and time. Firmware Update Policy Lets you specify if firmware updates are allowed from the operating system when the system is managed by a SMDC.
Selective Memory Mirroring This function is not available when your system is connected to the SDMC. Acoustic Mode Control This function is not available when your system is connected to the SDMC. – Hardware Deconfiguration Deconfiguration Policies Lets you set various policies to deconfigure processors and memory in certain situations. Field Core Override This function is not available when your system is connected to the SDMC. Processor Deconfiguration Lets you deconfigure a single processor.
Network Services Network Configuration Displays and modifies the network configuration of the service processor(s). Network Access Lets you control the access to the service processor (firewall). Performance Setup Logical Memory Block Size Lets you set the logical block memory size for your system. System Memory Page Setup Lets you set up the system with larger memory pages to improve system performance.
Login Profile Change Password Lets you change the general user, administrator, and HMC access passwords. Retrieve Login Audits Lets you review the login history for the ASMI. Change Default Languages Lets you change the language that is displayed on the ASMI Welcome page prior to login and during your ASMI session if you do not choose an alternative language at the time of login. Update Installed Languages Lets you install another language on the next firmware update.
14 Chapter 14. Service and support This chapter provides information about the service and support features available on IBM Systems Director Management Console (SDMC) to handle serviceable hardware problems and provide call home facilities. © Copyright IBM Corp. 2011. All rights reserved.
14.1 Introduction Service and Support Manager (SSM) is part of IBM Systems Director and automatically detects serviceable hardware problems and collects supporting data for serviceable hardware problems that occur on your managed systems. The Electronic Service Agent tool is integrated with the Service and Support Manager and transmits serviceable hardware problems and associated support files to IBM support.
14.2 Setup wizard To set up the Service and Support Manager to report serviceable problems to IBM, you have to run the Service and Support Manager Getting Started Wizard. You can find the wizard on the Welcome to IBM Systems Director page below Serviceability tasks (Figure 14-1). Figure 14-1 Service and Support Manager Getting Started Wizard Chapter 14.
Perform the following steps: 1. Click the Service and Support Manager Getting Started Wizard link and the wizard opens (Figure 14-2). Click Next.
2. On the next page, enter your company’s contact data (Figure 14-3). Figure 14-3 Company contact page Chapter 14.
3. The fields marked by an asterisk are mandatory and must be completed before proceeding. When you click Next, the System location page opens and requires information as to where your system (the SDMC) is physical located (Figure 14-4). Figure 14-4 System location page 4. As on the page in Figure 14-3 on page 339, fields marked with an asterisk are mandatory. Complete the fields and click Next.
5. In the Connection page, you have to specify how the SDMC can connect to IBM, either through a direct Internet connection or through a proxy server (Figure 14-5). Figure 14-5 Connection page There is also a Test Connection, button that lets you test whether your SDMC has a connection to IBM. Unlike the HMC, where VPN and modem are also options, on the SDMC only SSL over an Internet connection is an option to send serviceable requests to IBM. Chapter 14.
6. When you click Next, the Authorize IBM IDs page opens (Figure 14-6). Figure 14-6 Authorize IBM IDs Here you can provide the IBM IDs that can later access the service information transmitted to IBM by the Electronic Service Agent. This step can also be done at a later point.
7. When you click Next, the Summary page opens (Figure 14-7). Figure 14-7 Summary page 8. You can always go back from here if the displayed data is not as expected. If you are satisfied with the data provided, click Finish. You can always go back to the Welcome page and start the Service and Support Manager Getting Started Wizard again. 14.3 Call Home Call Home is the utility IBM uses to automatically capture data and report errors in the SDMC.
The tasks related to the Call Home feature are available on the context menu of the monitored systems. Right-click any of the monitored systems and you can see the context menu (Figure 14-8). Figure 14-8 Service and Support context menu You can perform the following Call Home tasks from this context menu: Electronic Service Agent Send Service Information You can send the service information manually from the SDMC to IBM Support.
Support Files You can use this task to collect the support files for the monitored system. The support files can be Resource dump, System dump, Node controller dump, Power dump, or a System controller dump. You can send these support files to IBM using this task. Submit Service Request You can send a service request to IBM by briefly describing your problem and also providing details regarding the problem.
14.4 Serviceable event processing The Service and Support Manager automatically detects error conditions and reports any hardware problem that requires service to repair it. These problems are reported to you as serviceable events. The Service and Support Manager provides the management of serviceable events on the managed system and the transmission of service requests for hardware problems to IBM support.
14.4.2 Persistent storage and management of serviceable event data Service and Support Manager persists all the information that is available with the event in its database tables. SDMC provides the information for the event. This event also provides information about the location of the Extended Error Data (EED) files that have been collected on behalf of the serviceable event. SDMC also maintains a cache of information about the serviceable events.
14.4.5 User actions You can see a problems dashboard on top of the web interface that displays the number of Problems and Compliances. This dashboard shows the number of Problems and Compliance issues with the managed system. The details of the problems are listed in the Problems page. Select System Status and Health Problems to open the Problems page (Figure 14-10).
This page shows all the active problems reported for all discovered systems. Click any of the problems and you should see the properties page of the selected problem (Figure 14-11). Figure 14-11 Problems: General properties Chapter 14.
The General tab provides information from the Director Status Set of the event. The Service tab provides information about the state of the service request and maintains the information shown in the service log associated with the problem. The Recommendation tab contains a Reference link that, when clicked, opens another browser page. This page (Figure 14-12) has the Problem Explanation and Determination information along with the reference code.
You can also close a serviceable event by selecting Request Closure of a given service request, which causes the Service and Support Manager to update the service request and indicate that you have requested closure of the service request. The serviceable event then goes into a closed state. Serviceable events, including problems, are displayed on the Problems page until you delete the problem from the Problems page. 14.
System wide support files view The system wide support files view can be reached by opening the Service and Support Manager page and clicking Manage support files under Common Tasks (Figure 14-13).
After you click the link, the Manage Support Files system wide view opens (Figure 14-14). Figure 14-14 Manage Support Files system wide view Chapter 14.
Monitored system support files view The monitored system support files view can be reached by going to the Welcome page, clicking the Resources tab, right-clicking a selected host, and selecting Service and Support Support files (Figure 14-15). Figure 14-15 Support Files in the context menu of a host The Manage Support Files page opens. This page shows only the support files of the selected host; otherwise, it is identical to the Manage Support Files system wide view (Figure 14-14 on page 353).
Serviceable problem support files view The serviceable problem support files view can be reached over an active serviceable problem. If you select the Properties of a serviceable problem, you can find, on the Support Files tab, the serviceable problem support files view, which shows only the support files available for this problem (Figure 14-16). Figure 14-16 Serviceable Problem Support Files view 14.5.
Submit support files to IBM by clicking the Submit to IBM... button, or by using the Action drop-down menu. Delete support files by clicking the Delete Support Files... button, or by using the Action drop-down menu. Copy support files to media (USB) by using the Action drop-down menu. Show the properties of a support file by using the Action drop-down menu, or by clicking the support file itself.
Figure 14-17 Collect Support Files page You can only get support files from one system at a time. Specify the type of support file you want to collect on the Support Files tab of the Collect Support Files... page. Depending on the system selected, you have five kinds of support file types: Resource dump A resource dump is a nondisruptive dump that you can use to capture server firmware diagnostic data.
System dump A system dump is a dump of the hardware and server firmware content (platform) for the managed system. This task abnormally ends the managed system and all its Virtual Servers. System controller dump A system controller dump is a dump of the service processor. It should not cause any disruption to the managed system unless an unexpected error occurs. Node controller dump A node controller dump is a dump of the node controller.
There are two other tasks that can be used to remove support files The Service and Support Manager Support File Cleanup task. Support files that are transmitted successfully to IBM are deleted after a set time period (the default is 7 days). The support file space management task, which is invoked every time a dump is copied from the managed system onto the SDMC appliance.
Properties of support files On the General tab of the properties page of a support file, you can view some information about a support file (Figure 14-18), such as: Location of the support file. Type of the support file. System from which the support file originated. Time the support file was collected. Time the support file was submitted to IBM. Size of the support file.
You can see the location where the support files are saved locally. You can see the free space left for the support files. You can see and modify the time period for when the submitted support files are automatically removed by the Service and Support Manager Support File Cleanup task.
14.6 Service and Support Manager command-line interface The Service and Support Manger (SSM) provides the following SDMC commands: ssmimport Used to provide the configuration information required by the Electronic Service Agent (ESA) to allow electronic service transactions to flow between the SDMC appliance and IBM. Provides the functional equivalence of running the Service and Support Manager Setup wizard.
14.7 Service and Support Manager tasks The Service and Support Manger (SSM) defines a number of tasks (scheduled jobs) that are performed on a periodic basis. That period depends on the specific task. You can see these task in the Active and Scheduled Jobs page (Figure 14-19). Figure 14-19 Tasks in Active and Schedule Jobs page You cannot edit the tasks, but you can change the run times. The tasks are: Service and Support Manager Support file cleanup This task runs every day.
Collect Performance Data This task runs on a daily basis. It is performed for AIX partitions that have been configured and set up to collect performance measurements. The Service and Support Manager attempts to collect performance measurements data after a partition is discovered and unlocked. Performance measurement data is stored in the eService database at IBM. Electronic Service Agent Connection test This task runs once a week. It is called a Heartbeat task.
14.9 Guided Repair You can perform Guided Repair procedures from the context menu of a managed system. Right-click a server and select Service and Support. The Guided Repair tasks are listed under two menus: Hardware and FSP Failover. Guided Repair is also referred to as Repair and Verify (R&V). Here are the common Repair and Verify procedures: Add or Remove FRU Displays a list of Field Replaceable Units (FRUs) that can be added or removed from the managed system.
Problem Repair You can execute a repair from the Problem Information page, which guides you to through the procedure to replace the FRUs. You can do some of the repairs concurrently. List Running Power System Repairs (Resume Repair) Displays a list of Guided Repair processes that are currently running on the SDMC. Click a process to continue it. Currently running processes are removed if the SDMC is restarted. Identify LED Displays a list of enclosures and FRUs.
A Appendix A. Command-line reference In this appendix, we list the IBM Systems Director Management Console (SDMC) commands with their options, new ones and old ones, that are not covered by the already existing documentation. © Copyright IBM Corp. 2011. All rights reserved.
IBM Power Systems management commands This section lists the Power Systems management commands (the ones in the psm-path) not covered by the IBM HMC Command-Line specification at the time of writing. The actual HMC Command-Line specification can be found at the following address: http://www14.software.ibm.com/webapp/set2/sas/f/hmcl/resources.html For a full explanation of the command options, please see the man pages or use the -?, -h, or --help options.
Table A-3 shows information about the mk5250 command. Table A-3 mk5250 command Command mk5250 Definition Launches a 5250 console for an IBM i partition. This command launches an X Window System application, so it needs to be run locally or using an exported display.
Command rmdump Example Removing a dump file: smcli rmdump -f FSPDUMP.100072A.01000019.20040629205455 IBM Systems Director application commands This section lists the IBM Systems Director application commands (psm-path excluded) not covered by the IBM Systems Director Command-Line specification at the time of the writing of this book. The actual IBM Systems Director Command-Line specification can be found in the IBM Systems Director V6.2.
Event commands This section lists the commands for event handling. To see the options of the commands in the event path, run the list command: smcli event list Table A-7 shows information about the appleventactionplan command. Table A-7 appleventactionplan command Command appleventactionplan Definition Assigns targets to an event action plan. Syntax smcli applyeventactionplan [-s system-oid(1)...system-oid(N)] [-g group-oid(1)...
Table A-10 shows information about the listeventactions command. Table A-10 listventactions command Command listeventactions Definition Lists the event actions and the corresponding number. Syntax smcli listeventactions [-r|-report|-t|-terse] Example To list the event actions and the corresponding numbers, run: smcli listeventactions Table A-11 shows information about the listevents command. Table A-11 listevents command Command listevents Definition Lists events.
Table A-13 shows information about the listfilters command. Table A-13 listfilters command Command listfilters Definition Lists all event filters. Syntax smcli listfilters [-r|-report|-t|-terse] Example To get a list of all filters, run: smcli listfilters Scheduler commands In this section, we list the commands for the scheduler handling.
Table A-16 shows information about the getjobstatus command. Table A-16 getjobstatus command Command getjobstatus Definition Lists the status of a specified job. Syntax smcli getjobstatus Example To get the status of job number 70, run: smcli getjobstatus 70 Table A-17 shows information about the listjobactivations command. Table A-17 listjobactivations command Command listjobactivations Definition List the times a specific job was executed.
Command listjobs Example To get a listing of all jobs, run: smcli listjobs SSM commands In this section, we list the commands for the Service and Support Manager (SSM). Table A-20 shows information about the chkssmconfig command. Table A-20 chkssmconfig command Command chkssmconfig Definition Verifies whether the Service and Support Manager is configured.
Command collectsptfile Example This example illustrates how to collect a DSA support file from a system with an IP address of 8.10.115.37: smcli collectsptfile -i 8.10.115.37 -t dsa This example illustrates how to collect IBM Power Systems subsystem support files from a side A of a system with a machine type of 9406, a model number of 570, and a serial number of 1234567: smcli collectsptfile -m 9406-570*1234567 -t psd -s a Table A-22 shows information about the cpsptfile command.
Table A-23 shows information about the lssptfile command. Table A-23 lssptfile command Command lssptfile Definition Displays a list of support files located on the management server.
Table A-24 shows information about the lssvcproblem command. Table A-24 lssvcproblem command Command lssvcproblem Definition Displays a list of serviceable problems on the management server.
Command rmsptfile Example This example illustrates how to remove a single support file from the management server. In this case, the specified support file is a flexible service processor dump: smcli rmsptfile -F /dump/9119.FHA.02FD881.problem.NOPROB.pmh.NOPMH.FS PDUMP.opt.ccfw.da-ta.p.sa.FSPDUMP.02FD881.18000000 .20090602065452.gz This example illustrates how to remove two support files from the management server.
Table A-27 shows information about the submitsptfile command. Table A-27 submitsptfile command Command submitsptfile Definition Sends a support file on the management server to the service provider. Syntax smcli submitsptfile {-h | -? | -- help} [-L language] [-v] {-F file_name} [-r service_request] Example This example illustrates how to send a service processor support file to the service provider. In this case, the specified support file is a flexible service processor dump.
Command configureHA Syntax smcli configureHA --secondary-node secNode --password thePassword --primary-rep-addr primRepAddr --secondary-rep-addr secRepAddr --floating-addr "addr1,subnet1,netIfc1 [... addrN,subnetN,netIfcN]" [ --time-server timeServer | --use-primary-as-time-server ] [ --force-time-sync ] [ --agent-mgr-addr agtMgrAddr ] [ -v ] [ --tiebreaker-addr tieAddr ] Appendix A.
Command configureHA Example This example illustrates how to configure high availability using only the required options. In this example, the primary node already has a time server configured. smcli configureHA --secondary-node node2 --password abcdefgh --primary-rep-addr 10.6.6.100 --secondary-rep-addr 10.6.6.101 --floating-addr "10.6.6.200,255.255.0.
Command failover Syntax smcli failover [-v | -r ] Example This example illustrates how to start a failover to the passive node: smcli failover This example illustrates how to start a failover to the passive node and return from the command as soon as the failover task is created: smcli failover -r Table A-30 shows information about the removeHA command.
Command mkuser Example This example illustrates how to create a user named "user1". In this example, the user password must be entered when you are prompted. smcli mkuser -u user1 This example illustrates how to create a user named "user2" with the provided password. The expiration is set to 90 days, and the SSH timeout to 10 minutes. The new user will belong to the IBM Systems Director group smadmin.
Other commands In this section, we list commands not listed in the previous sections. Table A-33 shows information about the enablehierachicalmgmt command. Table A-33 enablehierachicalmgmt command Command enablehierachicalmgmt Definition Enables IBM Director for hierachical management.
Table A-35 shows information about the licensestatus command. Table A-35 licensestatus command Command licensestatus Definition Displays the license status. Syntax smcli licensestatus [-v] {-p | --product productid} {-s | --feature feature} {-c | --component component} Example To get the license status of all registered products, run: smcli licensestatus Table A-36 shows information about the printInformation command.
Table A-39 shows information about the startdiscovery command. Table A-39 startdiscovery command Command startdiscovery Definition Starts a discovery of SNMP devices. Syntax smcli startdiscovery [network mask] Table A-40 shows information about the updatelicense command. Table A-40 updatelicense command Command updatelicense Definition Updates the licenses. Syntax smcli updatelicense [-v] {-p | --product productid} {-s | --feature feature} {-c | --component component} Appendix A.
388 IBM Systems Director Management Console: Introduction and Overview
B Appendix B. IBM Systems Director base functions In this appendix, we discuss the IBM Systems Director base functions. © Copyright IBM Corp. 2011. All rights reserved.
Base functions Base functions (plug-ins) in IBM Systems Director provide core functions to manage the full life cycle of IBM servers, storage, network, and Virtual Servers. Plug-ins that provide advanced functions or functions tailored to a particular environment can be downloaded and installed on top of IBM Systems Director. The base functions include: Finding and viewing resources and resource information, including relationships and properties. Organizing logical sets of resources into groups.
Configuration Manager The Configuration Manager is used to integrate new hardware into your environment, configure systems after installation, or do one-off configurations for problem resolution. The configuration manager uses a set of well defined templates that can be applied to servers, storage, and network resources even if the resources are composed of very different technologies.
IBM Power Systems management IBM Power Systems management provides life cycle management of your IBM Power Systems, and platform managers, such as Hardware Management Console (HMC) and Integrated Virtualization Manager (IVM) platform managers, including discovery, health and status monitoring, configuration, updates, and virtualization. It also provides platform-specific functions.
C Appendix C. IBM Systems Director Management Console distribution details In this appendix, we give detailed information about the IBM Systems Director Management Console (SDMC) disk images. © Copyright IBM Corp. 2011. All rights reserved.
IBM Systems Director Management Console virtual disk images Table C-1 shows the virtual image used for SDMC. It is composed of seven virtual disks. Table C-1 Seven virtual disk images for SDMC 394 Location on RHEV-H Blue Virtual disk name Size Guest device file Description HostVGData dvmdisk1.img 50 MB /dev/hda Boot disk HostVGData dmvdisk2.img 60 GB /dev/vda OS/Application disk HostVGData dvmdisk3.img 80 GB /dev/vdb Database disk AppVGData dmvdisk4.
Abbreviations and acronyms AME Active Memory Expansion ITSO AMM Advanced Management Module International Technical Support Organization IVM Integrated Virtualization Manager KVM keyboard/video/mouse LDAP Advanced System Management Interface Lightweight Directory Access Protocol LIC Licensed Internal Code BPA Bulk Power Assembly LPAR Logical Partition BPC Bulk Power Controllers LV Logical Volume CAS Common Agent Service LVM Logical Volume Manager CCFW Common Console Framework NIC
SMS Systems Management Services SPCN System Power Control Network SSH Secure Shell SSM Service and Support Manager SWMA Software Maintenance VLAN Virtual LAN VMC Virtual Management Channel VPD Vital Product Data VPN Virtual Private Network 396 IBM Systems Director Management Console: Introduction and Overview
Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book. IBM Redbooks The following IBM Redbooks publications provide additional information about the topic in this document. Note that some publications referenced in this list might be available in softcopy only.
IBM Fix Central http://www.ibm.com/support/fixcentral/ IBM Systems Director 6.2 Information Center http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp/ IBM Systems Director home page http://www.ibm.com/systems/management/director/ KVM Installation Document http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?to pic=/liaai/kvminstall/liaaikvminstallstart.htm Linux-KVM http://www.linux-kvm.org/ Network briding for the virtualization API libvirt http://wiki.libvirt.
Index Numerics 7042-CR6 16–17 BladeCenter 81, 391 BPA See Bulk Power Assembly Bulk Power Assembly (BPA) 10, 99 status 46, 102 A accesssys command 82 activate Virtual Server 152 Active and Schedule Jobs task 294 Active Energy Manager 91 Active Memory Expansion (AME) 165 Active Memory Sharing (AMS) 45 active/passive 300 Add Fibre Channel menu 174 Add or Remove Enclosure 365 Add or Remove FRU 365 advanced functions, CoD 96 Advanced Management Module (AMM) 81 Advanced System Management Interface (ASMI) 43 acc
failover 321 impdata 68, 282 lsbundle 278 lsldap 228 lsled 59 lsnetcfg 252 lsperm 209 lsrole 205, 210 lssptfile 362 lssvcproblem 362 lssys 85 lssyscfg 59 lsuser 201, 226 lsusergp 203 mk5250 282 mksyscfg 152 mkuser 226, 231, 236 rediscover 83 removeHA 321 rmrole 210 rmsptfile 362 rmuser 240 smha 321 smhastatus 320–321 ssmimport 362 submitsptfile 362 common agent 34 Common Agent Services 300, 310, 319 confighms command 92 Configuration Manager 391 Configure Access page 80 Configure Single Sign On 93 configure
configuration 246 First Failure Data Capture (FFDC) 364 Flexible Service Processor (FSP) 308 failover 365 floating IP address 303, 305, 310, 318 frame 10, 99 FRU See Field Replaceable Unit functional differences 49 G gateway,setting 248 global server 91 group 211–212 creating 212 smadmin 202 smmgr 202 smmon 202 smservicerep 202 smuser 202 Group Editor wizard 213 GroupRead role 205 Guided Repair 365 H HA See high availability hardware appliance 7 Hardware Management Console (HMC) 1, 3, 301 as DHCP server 7
states 10 LPAR See logical partition lsbundle command 278 lsldap command 228 lsled command 59 lsnetcfg command 252 lsperm command 209 lsrole command 205, 210 lssptfile command 362 lssvcproblem command 362 lssys command 85 lssyscfg command 59 lsuser command 201, 226 lsusergp command 203 M manage Virtual Server 44, 159 managed endpoint (MEP) 10 managed system 10 capabilities 94 edit host 86 power on 87 rebuild 43 remove 80 media devices 175 memory settings 96 mk5250 command 282 mksyscfg command 152 mksysconn
rediscover command 83 redundancy 12, 299–301 relocation 10 Remote Access Manager 391 Remote Command Execution 276 Remote Monitoring and Control (RMC) 186, 346 Remote Service Access Points (RSAP) 80 Remote Virtual Terminal 276 Remove Enclosure 365 Remove FRU 365 remove managed system 80 removeHA command 321 Repair and Verify 365 replaced IBM Systems Director application commands 370 replication IP address 309, 316 Representational State Transfer (REST) 93 Request Access page 79 Request Management Access 93 r
smhastatus command 320–321 SMManager role 10, 199, 205 smmgr group 202 smmon group 202 SMMonitor role 199, 205 SMS See Systems Management Services smservicerep group 202 smuser group 202 SMUser role 10, 199, 205 software appliance 7 SSH See Secure Shell SSL 341 ssmimport command 362 state mappings 90 Status Manager 390 submitsptfile command 362 Support File Management 351 support files collecting 356 copying 359 deleting 358 general settings 360 properties 360 submitting to IBM 358 Support Files task 345 su
X x86 hardware 16–17 Index 405
406 IBM Systems Director Management Console: Introduction and Overview
IBM Systems Director Management Console: Introduction and Overview (0.5” spine) 0.475”<->0.
Back cover ® IBM Systems Director Management Console Introduction and Overview Documents the SDMC appliance, which uses the Systems Director user interface Discusses the differences between the HMC and SDMC Provides a practical guide to the SDMC ® This IBM® RedpaperRedbooks® publication positions the IBM Systems Director Management Console (SDMC) against the IBM Hardware Management Console (HMC).
