IBM Systems Group © 2005 IBM Corporation This presentation is intended for the education of IBM and...

IBM Systems Group

© 2005 IBM Corporation

This presentation is intended for the education of IBM and Business Partner sales personnel. It should not be distributed to customers.

IBM Director 5.10z/VM Center Extension

Wolfgang Bloem, Virtual Server DeploymentOfer Biran, Server ComplexesKlaus Liegert, Team Lead

IBM Systems Group

© 2005 IBM Corporationpage 2IBM Systems Group Field Skills & Education

Agenda

IBM Director for Linux on System z9 and zSeries Overview

Virtual Server Deployment

Server Complexes

Topology

Trouble Shooting

IBM Systems Group


IBM Director manages Linux and Virtualization on zSeries

IBM Director technologyused to manage …– 100s of Linux images on zSeries – z/VM as the pervasive virtualization

technology for zSeries servers

Objectives:

– Provide management for Linux onzSeries and z/VM according to theeServer strategy for base management

– Address base management of Linux,easy deployment of z/VM guests andLinux images, as well as managementof virtualization technology on zSeries

– Provide aggregated integration pointfor higher level management solutions from Tivoli and System Management vendors

IBM Systems Group


New „z/VM Center“ Extension

Virtual Server Deployment– Creation of virtual servers (virtual machines) under z/VM– Deployment of Linux systems into those virtual servers– From there the Linux on zSeries endpoints are managed like any

Linux endpoint

Server Complexes– On-going management of Linux guests– Coordinates z/VM side and Linux side configuration of the guests

– z/VM Resource Manager (VMRM) goals for CPU and DASD I/O– Virtual networking, based on VM Guest LAN, OSA and VSWITCH– z/VM minidisk attachments

– Control of guest configuration consistency

IBM Systems Group


Agenda



Server Complexes

Topology

Trouble Shooting

IBM Systems Group


Virtual Server Deployment TaskProvisioning of Virtual Servers and Linux guests on z/VM

Exploits the CIM model/provider implementation of ePP for z(CbC - Container Based Cloning)

Main R1 functions:– General z/VM information– Management of Virtual Server Templates– Creation, properties definition– Virtual Server creation– Management of Operating System Templates– Capture OS template from an existing guest– Applying OS template on a Virtual Server– Activate / deactivate Virtual Server

IBM Systems Group


Walkthrough: Virtual Server DeploymentIn this walkthrough you will see most of the panels and the

related functionsScenario:

– educational institution offers an online course for basic Linux administration

– VM Center is used to deploy new Linux systems when a student enrolls and decommission it when it is no longer needed

Assumption:– Linux has already been installed on a z/VM virtual server and prepared

as a master Linux system

IBM Systems Group


Walkthrough: Virtual Server Deployment (cont.)Steps performed during this scenario

– Start Virtual Server Deployment Task– View and configure z/VM Profile credentials– Register the master Linux system to z/VM Center– Create a template for the student Linux instances– Create a template for the student z/VM virtual servers– Create a z/VM virtual server from the virtual server template– Create a Linux instance on the new z/VM virtual server– View overall results

IBM Systems Group


VSD: z/VM System – the entry pointz/VM System

– Display– Edit / save– Refresh info

IBM Systems Group


VSD: z/VM Profile – configure credentialsz/VM Profile

– Display– Edit / save– Refresh– Configure z/VM

Profile credentials

IBM Systems Group


VSD: z/VM Virtual Server – register a master operating systemOperating

Systems– List available

OSs(Currently only 1 supported!)

– Refresh list– Create new OS– Register OS

IBM Systems Group


VSD: Register Operating System on Virtual ServerWizard steps

specify:– System Disks

required by the Linux OS

– Boot Disk(one of the required disks)

– Interface and IP addresses for network ports

– Host Name of master linux (without domain)

IBM Systems Group


VSD: Operating System – the master linuxOperating System

– Display• Overview• Disks• Network Ports• Relationships

– Edit / Save– Refresh info– Re-Register OS– De-Register OS

IBM Systems Group


VSD: Operating System Templates – create an operating system templateOperating System

Templates– List available

operating system templates

– Refresh list– Create new

operating system template

IBM Systems Group


VSD: Create Operating System TemplateWizard steps

specify:– Master Operating

System– Shared Disks– Template Name– Disk Pool

– Deactivate Virtual server of Master OS for cloning

IBM Systems Group


VSD: Operating System Template – the master Linux templateOperating System

Template– Display

• Overview• Exclusive Disks• Shared Disks• Network Ports• Relationships

– Edit / Save– Refresh info– Delete

IBM Systems Group


VSD: Virtual Server Templates – create a virtual server templateVirtual Server

Templates– List available

templates– Refresh list– Create new

virtual server template

IBM Systems Group


VSD: Create Virtual Server TemplateWizard steps

specify:– Instance

Specifics– Template Name

IBM Systems Group


VSD: Virtual Server Template – the educational server templateVirtual Server

Template– Display

• Overview• Settings

– Edit / Save– Copy– Delete– Refresh info

IBM Systems Group


VSD: Virtual Servers – create a virtual serverVirtual Servers

– List available virtual servers

– Refresh list– Create new

virtual server

IBM Systems Group


VSD: Create Virtual ServerWizard steps

specify:– Source Template– Instance

specifics

IBM Systems Group


VSD: Virtual Server – a first server for 'Student 01'

Virtual Server– Display

• Overview• Disks• Processors• Memory• Network Ports

– Edit / Save– Delete– Refresh info

IBM Systems Group


VSD: z/VM Virtual Server – create an operating systemOperating

Systems– List available

OSs(Currently only 1 supported!)

– Refresh list– Create new OS– Register OS

IBM Systems Group


VSD: Create Operating SystemWizard steps

specify:– Source template– IP Addresses– Disk Pool– Host Name

IBM Systems Group


VSD: Overall resultResources created

in this scenario:– Master Linux

registered– OS Template

created– Virtual server

template created– z/VM virtual

server created– Linux instance

created

IBM Systems Group


Agenda



Server Complexes

Topology

Trouble Shooting

IBM Systems Group


Server Complexes TaskOn-going management of Linux guests

Server Complex entities are introduced (in a scope of a z/VM) to control the configuration aspects of Linux guests in that z/VM

Coordinates z/VM side and Linux side configuration of the Linux guests

Control of configuration consistency– Deviation from desired configuration are shown– Apply desired configuration

Direct cloning into server complex– One step Linux guest creation and configuration according to the server

complex properties– Using the Virtual Server Deployment task infrastructure

IBM Systems Group


Server Complexes under the z/VM Center task

When dropping the z/VM Server Complexes task on a z/VM managed object the task’s window is opened

The mid pane above is organized according the association Server Complexes Membership

IBM Systems Group


The Server Complex Entity Represents a (possibly) multi-tier grouping of guests Governs the creation and configuration of included guests by persistent

properties– In each domain the properties can be defined separately for each tier, or for the

whole server complex Controls VM resource assignment (CPU and IO velocity goals)

– The goals are applied to the current group of included guests Defines virtual networking

– The virtual networking is based on z/VM guest LANs, direct OSA attachment and VSWITCH

Defines minidisk attachments– VM and Linux (up to mount point) configuration

Supports configuration scripts– 'user exits' for configuring guests placed in a server complex tier for a specific role or

any customer environment setting Comprehensive treatment of configuration errors and inconsistencies

– Status icons, check consistency operation, consistency validation before any configuration attempt

IBM Systems Group


Server Complexes Task window

There are currently a 2-tier server complex Production and a 1-tier server complex Test

Linux guests can be dragged to/from server complex tier or the Free Linux Guests frame, and get automatically configured accordingly.

An Operating System Template can be dragged into a server complex (while a Virtual Server Template and a Disk Pool are selected)) – a new Linux guest will be cloned and configured according to the server complex properties.

The properties of each server complex can be changed and re-applied on the included Linux guests (or on any subset of them).

A consistency check can be performed to validate the actual configuration of the included guests against the desired configuration implied by the server complex properties

IBM Systems Group


Server Complexes Walkthrough

VMRM management

Minidisk attachments

Virtual Networking

Direct cloning

Configuration scripts

These walkthroughs will cover:– Creating server complex (SC)– Editing SC properties– Applying SC properties

• By moving guests• By changing and re-apply the properties

– Configuration consistency

IBM Systems Group


SC Walkthrough : VMRM management

Assume you have Linux guests that are in production, while others are used for tests. You want to assign 70% of the CPU resources of the z/VM to the production guests and 30% to the test guests.

1: Create two server complexes, Production and Test

SC Window: Action -> New server complex…

You can set number of tiers and meaningful tier names

IBM Systems Group


SC Walkthrough : VMRM management (2)

2: Move the Linux guests from the Free Linux guests into the SCs

(drag/drop or Move to… dialog)

IBM Systems Group



3: Set the VMRM goals in the server complexes properties

Right-click on the title area of the Productionand choose Edit Properties… (or from the Action menu while it’s selected).

Click the VMRM tab, fill the values,click OK

(Importance 1 designates the highest priority of a performance goal to be maintained by VMRM)

IBM Systems Group



Progress Indication Window forthe VMRM configuration -

4: Change in role of a guest – suppose one of the guests is reassigned from test to produsction. You simply drag it from the Test SC to the Production SC – the VMRM is reconfigured.

5: Suppose you want to increase the Production CPU performance goal from 70 to 80. Change the Production SC VMRM properties, click OK and VMRM will be reconfigured.

IBM Systems Group


SC Walkthrough : Minidisk attachments

Assume that you want each production guest to have a certain Minidisk attached and mount on /var/product , and each test guest to have 2 other Minidisks attached and mount on /var/test1 and /var/test2 .

1: Edit the Production SC Properties. Click the Minidisks tab. Click Add…

IBM Systems Group


SC Walkthrough : Minidisk attachments (2)

The Minidisk line appears -

2: Click Ok – the Guest Selection Window appears:

Scobsu04 is Offline and cannot be selected for applying the Minidisk propertie. Click Yes.

IBM Systems Group



3: Progress Indication Window for the Minidisk configuration

Notes:

• Before any configuration, the current target configuration is validated against the old SC properties – inconsistency is reported (Proceed / Stop option)

• Clicking a line in the Progress window may show additional details in the lower pane - useful in case of error lines (red).

IBM Systems Group



4: scobsu04 appears now with inconsistency indication.

Right-click on it and choose Guest status… :

Note: at any time you can perform Check consistency on a server complex, to get a report and update the consistency status of all included guests.

5: Moving guests / changing Minidisk properties triggers re-configuration as in any domain.

IBM Systems Group


SC Walkthrough : Virtual Networking

Assume you want each production guest to have two network interfaces, one configured on a guest LAN, the other directly attached to an OSA, and each test guest to have one network interface configured on a different guest LAN.

1: Define the guest LANs and OSA networking properties

1.1 Action-> z/Vm Networking properties to open the z/VM Networking properties window.

1.2 There Action->Refresh from z/VM to get the existing guest LANs, OSAs, VSWITCHes

IBM Systems Group


SC Walkthrough : Virtual Networking (2)

1.3 Double-click on the guest LAN you want to use to fill its routing properties:

1.4 Fill the properties and click OK

NOTE: Here we defined a pool of 5 IP addresses starting from 9.60.60.73 , till 9.60.60.77. IP addresses for guests (and new clones) configured on this guest LAN will be taken from this pool. You can define occupied IPs (that should not be used) inside the pool's range by using the Add… button.

IBM Systems Group



1.5 In the z/VM Networking properties window now choose Action->Save and close it.

NOTE: Only guest LANs, OSAs and VSWITCHes with filled properties can be used in the Network page of Server Complexes

IBM Systems Group



2: Set the Production Network properties

Set the guest LAN for interface #0 and the OSA for interface #1

(Only guest LANs, OSAs and VSWITCHes with filled properties are in the drop-down lists)

Set the default gateway (type, or select from the ones defined for the selected connectin entities).

Click OK

3: Similar to the Minidisk domain

IBM Systems Group


SC Walkthrough : Direct Cloning

1: Create the Provisioning templates in the VSD task

Note: the Virtual Server Template has a "userid pattern" fields. If you plan to use the Virtual Server Template to create multiple clones, use a pattern ending with "*", e.g. "LINUX*" – this will create clones named according to the next free userids in the z/VM starting with "LINUX" – LINUX001, LINUX002… In our case we used "SCOBSU*"

IBM Systems Group


SC Walkthrough : Direct Cloning (2)

2: On the Server Complexes twindow click the Refresh button in the Provisioning resources pane.

You should see there the Virtual Server Template and the Operating System Template you created in the VSD task:

IBM Systems Group



2: Initiate a direct cloning operation

2.1 In the Provisioning Resources pane, make sure the Virtual Server Template and the Disk Pool you want to use are selected.

2.2 Drag the Operating System Template you want to use into the target server complex.(NOTE: the target SC must have a filled Network properties, as we set in the virtual networking walkthrough)

2.3 In the Number of Clones window specify the number of clones to create and click OK:

IBM Systems Group



Progress Indication window for the cloning operation -

IBM Systems Group



Here the first clone (scobsu01) was already discovered, while the second is in a virtual server state waiting to be discovered.

The SC properties (except Network) are applied on the new clone only after discovery (and access grant ! – automatic grant for level-2 if the MAP guest is a granted level-2 managed object).

You might need to manually initiate the Director discovery from the console.

IBM Systems Group



3: Opening the Connection Properties for the guest LAN we used for the cloning, we can now see in the Occupied IP list the 2 IP addresses used for the 2 clones:

IBM Systems Group


SC Walkthrough – Configuration Scripts

• Scripts can be defined to be executed on a guest entering the SC tier and/or leaving it.

• Here we defined the properties for each tier separately. This is possible for each of the domains !

• The scripts may already reside on the guests, or on the Director server

• If the script path starts with “/” it’s considered absolute path. Otherwise it’s considered relative to the Direcor data directory.

IBM Systems Group


Agenda



Server Complexes

Topology

Trouble Shooting

IBM Systems Group


IBM Director 5.10 for Linux on zSeries Landscape

Director Server

Director Console

Director Server (Linux/z+x, Win, …)

ISC Server

Director Console

(X11)

VE Console (WebBrowser)

Director Console

(Win)Desktop

z/VM MAP Director ITD

Agentz/VM management

profile

CbCProv.

Pegasus

SM RPC

zSeries Box

z/VM MAP = z/VM Manageability Access Point

CbC = Container based Cloning (Implementation of the z/VM Management Profile)z/VM

SystemMgmt

Vendors

Mgmt Servers

Managed Nodes VM

Prov.LinuxProv.

IBM

Other OS

Linux/z

CIMITDSub

DirectorITD Agent

CIMITDSub

DirectorITD Agent

Linux/z

CIMITDSub

DirectorITD Agent

CIMITDSub

DirectorITD Agent

CIMITDSub

DirectorITD Agent

z/VM (CP)

PR/SM

IBM Systems Group


Associations view:Linux on System z9 & zSeries Platform MembershipAssociation view reflecting the topology

IBM Systems Group


Agenda



Server Complexes

Topology

Trouble Shooting

IBM Systems Group


z/VM Center troubleshooting overviewCommon debugging hints

– Message prefixes– Logging activation, Log files– Timeouts

Areas of attention– OSA information is not displayed– New Linux instance has incorrect

IP address or host name– z/VM virtual server creation fails– z/VM systems management API

problems– z/VM system discovery failures– SLP Setup

Areas of attention (cont.)– Cloned zVM Virtual Server gets

no connection to the network– Cloning of zVM Virtual Server

aborts due to not enough space– Linux guests are not associated

to a z/VM– VMRM Configuration errors– Minidisk Attachment fails– Minidisk not attached after

reboot– Multiple cloning fails due to

existing userid– Startup of Virtual Server fails

IBM Systems Group


Message prefixesMessages can be found in dialog boxes and log files

Dialog boxes might offer a 'Details' button which then gives you additional messages from the underlying infrastructure– For error reports, all messages in a dialog box are required

The following table gives an overview of the message prefixes and the components, where they have been defined

Prefix ComponentFrom TillDNZZSL DNZZSM IBM Director Server LayerDNZZIS IBM Director Infrastructure (discovery, communication)DNZZDC IBM Director Components (association)DNZZVC DNZZVD ConsoleDNZZVS DNZZVZ Service nodeDNZZMC DNZZMV z/VM Management Profile (ePP4z / CbC)DNZZSC Server Complex

IBM Systems Group


Logging activationEnable logging

– z/VM Center exploits standard IBM Director logging mechanisms

– Linux: set the following environment variables• TWG_DEBUG_CONSOLE=1• TWG_DEBUG_SERVER=1

– Windows: regeditMy Computer\HKEY_LOCAL_MACHINE\SOFTWARE\tivoli\Director\CurrentVersion

• change "LogOutput" from 0 to 1

– IBM Director: enable TWGRas• edit /opt/ibm/director/data/TWGRas.properties

– twg.ras.comps=-1twg.ras.types=-1twg.ras.size=16384twg.ras.high=1twg.sysout=1

• restart IBM Director Server

IBM Systems Group


Log filesAvailable on console, server and agent

– /opt/ibm/director/log/• *.stderr and *.stdout

– for console output & Java Stack traces– Use text editor to view content

• TWGRas.log– Main log file for debug und error logging– Use rasdump to view content– Use rasdump > log.txt to save the content in an human readable format

IBM Systems Group


Log files (cont.)Available on Cloned Systems

– /var/log/– boot.msg

> Information about personalization of cloned system (IP and hostname).

Available on Manageability Access Point (MAP)– /var/log/

– messages or local7messages> Log file of the syslog facility.> This file contains log messages from the

z/VM Management Profile Implementation (uses local7 syslog facility).> Information about personalization of cloned systems.

– zvm-mgmtslpd.log> Log messages from the z/VM management SLP about SLP service registrations.

IBM Systems Group


TimeoutsCommunication timeouts are configurable separately for

– common z/VM Center parts– VSD– SC

If a certain timeout occurs…– … for the fist time, then redo the action and see if it works. If yes - fine.– … frequently, then modify timeout constants

IBM Systems Group


Timeouts (cont.)Configuration files in: /opt/ibm/director/data

– z/VM Center : ZvmCenterConfig.properties– VSD : ZvmCenterVSDConfig.properties– SC : ZvmCenterSCConfig.properties

Timeouts are defined for each communication command separately– for VSD and z/VM Center in milliseconds (ms)– for SC in minutes

Reset to the defaults– VSD and z/VM Center: Delete the property file by hand. The files are

recovered from internal defaults, the next time they are accessed– SC: currently not possible. It is adviced to make a backup from the

original, before modifying any timeouts.

IBM Systems Group


Troubleshooting:OSA information is not displayed

This problem affects both the Virtual Server Deployment task and the Server Complexes task.

Problem– The information on OSA devices is missing in the network information

shown in z/VM Center interfaces.

Investigation– Ensure that the z/VM manageability access point administrator ID has

the required privileges to query OSA information (see “Authorizing the z/VM manageability access point administrator ID”)

IBM Systems Group


Troubleshooting:New Linux instance has incorrect IP or host nameThis problem relates to Linux instances that are created with

the Virtual Server Deployment “Create Operating System” wizard.

Problem– A newly created Linux instance does not have the host name and IP addresses

you specified in the “Create Operating System” wizard.

Investigation– Examine /var/log/local7messages or /var/log/messages and search for

personalization logs for possible reasons.– If no log statement can be found, the Linux instance on which the new Linux

instance was based on might not have been prepared as a master Linux instance. In the “Create Operating System” wizard you specified an operating system template. To find out the source of the template, select the operating system template in the Provisioning Resources tree and then click the Relationship table. The source of the template must have been set up as described in “Preparing a master Linux system”.

IBM Systems Group


Troubleshooting:z/VM virtual server creation fails – part I

This problem relates to the Virtual Server Deployment task.

Problem– An attempt to create a z/VM virtual server returns errors DNZZVS323E,

DNZZSM365E, and DNZZMS473E with rc=444 and reason=12.

Investigation– In the “Create z/VM Virtual Server” wizard, you might have specified a

password for the z/VM virtual server that does not conform to the password policies at your installation. Retry creating the z/VM virtual server with a password that adheres to the password policies.

IBM Systems Group


Troubleshooting:z/VM virtual server creation fails – part II

This problem relates to the Virtual Server Deployment task.

Problem– During the creation of a zVM virtual server a timeout situation occurres

Investigation– Connection to zVM might be interrupted. Check if VSMSERVE is

running end start it if neccessary– DATAMOVE machine still covered by a DIRMAINT active workunit

which has been created earlier but failed and wasn’t recovered correctly.

IBM Systems Group


Troubleshooting:z/VM systems management API problemsProblems for the Virtual Server Deployment task and the

Server Complexes task can result from z/VM systems management API problems.

Problem– Error messages point to problems with the z/VM systems management

API

Investigation– The z/VM Center extension task logs z/VM systems management API

information to the syslog daemon. For SUSE LINUX Enterprise Server 9 for IBM System z9, zSeries and S/390 the log file to examine is the system log. For Red Hat Enterprise Linux AS, version 4.0, for IBM System z9, zSeries and S/390 the log to examine resides in /var/log/messages.

IBM Systems Group


Troubleshooting:z/VM system discovery failures


Problem– A z/VM managed object could not be discovered automatically.

Investigation– Check ‘Discovery Preferences’. Broadcast and Multicast must be

enabled in the ‘General Discovery’ settings.– Check z/VM System discovery settings if the settings are suitable for

your network environment.– If the problem cannot be solved proceed with SLP setup

troubleshooting, or create a z/VM managed object manually (‘Add z/VM systems’).

IBM Systems Group


Troubleshooting:SLP Setup – Problem

This problem affects the discovery infrastructure ofz/VM systems.

Problem– A z/VM managed object could not be discovered automatically using

SLP, because of one of the following main reasons:

• Network communication problems between IBM Director Server and MAP• SLP service agent is not running on the MAP• z/VM management SLP service could not be registered

IBM Systems Group


Troubleshooting:SLP Setup – Investigation (part I)SLP setup investigation:

– Do IBM Director Server and MAP reside in the same network?• If not then please ensure that SLP multicast packets are not blocked by

routers or firewalls.• If yes then please ensure broadcast and multicast is not disabled.

– Is the IBM SLP service agent (SA) running on the MAP?• To check whether the SLP SA is running, execute: ps aux |grep slp_srvreg• You can start / stop the SLP SA with: /etc/init.d/ibmsa start|stop

• Ensure that only one SLP SA is running on the MAP system, check it withnetstat –anp |grep 427, and look if another process is listening.

• If an OpenSLP service agent or directory agent is running then it should be stopped, executing: /etc/init.d/slpd stop

IBM Systems Group


Troubleshooting:SLP Setup – Investigation (part II)SLP setup investigation:

– Check-List for the z/VM management SLP service:

• Try to discover the z/VM management SLP service:– cd /opt/ibm/director/bin– ./slp_query --type=management-software.IBM:zvm-management-agent-https

• If no service could be found then check the z/VM management SLP daemon:– The daemon can be started/stopped with: /etc/init.d/zvm-mgmtslp start|stop– Look into /var/log/zvm-mgmtslpd.log whether the SLP service could be

registered with an SLP service agent.

IBM Systems Group


Troubleshooting:new cloned zVM Virtual Server gets no connection to the network.

This problem affects the Virtual Server Deployment task.

Problem

– The new cloned virtual server cannot be reached within the expected network or ping is not working.

Investigation– Check your network specification for the clone. It must be in the same

subnet as your master Linux.– Check your master Linux.

• A correct network specification must be included in the master system directory entry (OSA address included? / NICDEF definition included?)

• VSWITCH used but new user has not been granted

IBM Systems Group


Troubleshooting:cloning of zVM Virtual Server aborts due to not enough space.


Problem– Disk space seems not to be enough, although it does pretend to be.

Investigation– Check your z/VM diskpool. The overall free space might be enough

but the consecutive one is not.

IBM Systems Group


Troubleshooting:Linux guests are not associated to a z/VM

This problem affects the Server Complexes task.

Problem– In z/VM Server Complexes Association, Linux guests are not shown

under the z/VM (not associated). These guests will not be included in the server complexes task window.

Investigation– Check that cpint is installed on the Linux guest

• 'modprobe cpint' (or 'modprobe cpint_mod' or 'cpint_load‘) followed by 'hcp q userid' on guest – should return UID at VMNAME

– If it is a level-2 system, check that the zSeriesAgentExt.s390.rpm is installed.

IBM Systems Group


Troubleshooting:VMRM Configuration errors


Problem– Errors when trying to apply VMRM configuration

Investigation– Check that all the VMRM setup steps were done, in particular:

• Authorization of the MAP VMAPI userid to the VMRM file pool and configuration file

• In case the default VMRM file pool and configuration file are not used:– Authorization of the VMSERVE machine to the VMRM file pool and

configuration file– Specifying the non-default configuration file in CimVm.properties on the MAP

Linux.

IBM Systems Group


Troubleshooting:Minidisk Attachment fails

This problem affects the Virtual Server Deployment task and the Server Complexes task.

Problem– Failure in applying minidisk attachments

Investigation– Usually the error message tells the reason (used VDEV, minidisk not

exist etc.)– The minidisk might be protected by a security manager (e.g. RACF)

IBM Systems Group


Troubleshooting:Minidisk not attached after reboot


Problem– Minidisks that were attached by applying server complex minidisk properties,

are not attached to the guest anymore after the guest was rebooted.

Investigation– Check that the zVMPersonalization.s390.rpm is installed correctly

• rpm -q zVMPersonalization• /etc/init.d/personalize exists and ‘chkconfig --list personalize' should be 'on' for

runlevel 2,3,4,5)

– Check that the appropriate lines are in /etc/sc_fstab , each line is for a minidisk with the format:• devNum partNum mountPoint fsType mountOptions

IBM Systems Group


Troubleshooting:Multiple cloning fails due to existing userid


Problem– The second cloning of multiple cloning operation fails due to existing

userid.

Investigation– Check that the used Virtual Server Template has a value ending with

“*” in the userid pattern field (using a pattern like "LINUX*" will create clones named according to the next free userids in the z/VM, starting with "LINUX" – LINUX001, LINUX002… ).

– Otherwise, the exact same userid is tried also for the second clone.

IBM Systems Group


Troubleshooting:Startup of Virtual Server failsThis problem affects both the Virtual Server Deployment task

and the Server Complexes task.

Problem:– After cloning the new virtual server doesn't start

Investigation:– if using a security manager (e.g. RACF) the new virtual server hasn't

been defined to it.All potential newly created virtual server names must be defined to the security manager in advance.

– Personalization didn't work correctly. Check log on new virtual server

Date post:	29-Jan-2016
Category:	Documents
Upload:	charlene-greer
View:	212 times
Download:	0 times

IBM Systems Group © 2005 IBM Corporation This presentation is intended for the education of IBM and...

Documents