Do+Able Products 12347 Uživatelský manuál

Procházejte online nebo si stáhněte Uživatelský manuál pro Vývojový software Do+Able Products 12347. Do+Able Products 12347 Product data Uživatelská příručka

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 57
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 0
Hardware Management Console Best Practices
- 1 -
IBM Hardware Management Console
Best Practices
Ron Barker
Minh Nguyen
Shamsundar Ashok
January 2007
Zobrazit stránku 0
1 2 3 4 5 6 ... 56 57

Shrnutí obsahu

Strany 1 - Best Practices

Hardware Management Console Best Practices - 1 - IBM Hardware Management Console Best Practices Ron Barker Minh Nguyen

Strany 2 - - 2

Hardware Management Console Best Practices - 10 - Updates can be downloaded over the Internet for workstation-based installations. The online vers

Strany 3

Hardware Management Console Best Practices - 11 - 3 Initial Configuration HMCs come with Licensed Machine Code preinstalled, but you may need to re

Strany 4

Hardware Management Console Best Practices - 12 - 3.3 Creating User IDs Additional user IDs should be created on the HMC so that not every user is

Strany 5 - 1 Overview

Hardware Management Console Best Practices - 13 - tunneling, the HMC’s IP address was exposed. At HMC V5R2, support was added for outbound, SSL soc

Strany 6 - 2 Planning

Hardware Management Console Best Practices - 14 - 4 Security Physical security of the HMC is a customer responsibility. The HMC should be located

Strany 7

Hardware Management Console Best Practices - 15 - 4.2 Secure WebSM A secure WebSM connection using Secure Socket Layer (SSL) code is also available

Strany 8

Hardware Management Console Best Practices - 16 - The following command disables all remote WebSM connections to the HMC: $ chhmc –c websm –s disa

Strany 9

Hardware Management Console Best Practices - 17 - 4.4.1 Power 5 HMC port information Port Protocol Application Enabled by Default Modification al

Strany 10

Hardware Management Console Best Practices - 18 - The firewall interface allows you to customize remote access to the HMC by IP address and network

Strany 11 - 3 Initial Configuration

Hardware Management Console Best Practices - 19 - Because the full list of HMC commands is published at the IBM HMC’s web site, we will only referen

Strany 12

Hardware Management Console Best Practices - 2 -

Strany 13

Hardware Management Console Best Practices - 20 - lssvcevents -t consoleEarliest Timestamp Description10/16/03 07:27:51 PM HSCE2175 User hscroot log

Strany 14 - 4 Security

Hardware Management Console Best Practices - 21 - # ssh hscroot@stratus mkauthkeys -a -u minh'"command=\"logssh \${SSH_ORIGINAL_CO

Strany 15

Hardware Management Console Best Practices - 22 - HMC for establishing a trusted communication channel between the HMC and the partitions on the man

Strany 16

Hardware Management Console Best Practices - 23 - 5 User Management The HMC provides a User Management facility to create and manage users, as well

Strany 17

Hardware Management Console Best Practices - 24 - To manage users employing the HMC WebSM console, a user with hmcsuperadmin authority would go to

Strany 18

Hardware Management Console Best Practices - 25 - 5.2 Task and Managed Resource Roles As mentioned in the introduction to this section, a role is a

Strany 19

Hardware Management Console Best Practices - 26 - hscroot@myhost:~> lshmcusr --filter names=hscrootname=hscroot,taskrole=hmcsuperadmin,descripti

Strany 20

Hardware Management Console Best Practices - 27 - 406-520*10007CA|IBMHSC_Partition,lpar:root/ibmhscS1_0|3*9406-520*10007CA|IBMHSC_Partition,lpar:roo

Strany 21

Hardware Management Console Best Practices - 28 - # create a resource role for a managed system and LPAR# resource type; note that the managed syste

Strany 22

Hardware Management Console Best Practices - 29 - Thus, while it is unlikely to occur, it would be a good practice to document customized roles and

Strany 23 - 5 User Management

Hardware Management Console Best Practices - 3 - Table of Contents 1 Overview...

Strany 24

Hardware Management Console Best Practices - 30 - 6 Problem Determination This section is intended to cover issues and problems that may be encount

Strany 25

Hardware Management Console Best Practices - 31 - • -c Collect trace files and (optional) stack traces of various subsystems. This initiates an in

Strany 26

Hardware Management Console Best Practices - 32 - This password is valid until the end of the calendar day for which it was issued. Hence, a passwo

Strany 27

Hardware Management Console Best Practices - 33 - 7310-C03 desktop model, or 7310-CR2 / 7310-CR3 rack-mount models, make sure the hyperthreading opt

Strany 28

Hardware Management Console Best Practices - 34 - • Incomplete: The HMC is unable to gather all system information from the managed system or frame.

Strany 29

Hardware Management Console Best Practices - 35 - Another observed problem has been the GUI isn’t reflecting the true managed system or frame status

Strany 30 - 6 Problem Determination

Hardware Management Console Best Practices - 36 - 7 Maintaining Licensed Internal Code Make sure you keep track of new releases, updates and emerg

Strany 31

Hardware Management Console Best Practices - 37 - 7.2 HMC Code Installation/Upgrade/Update HMC systems leave manufacturing pre-installed with the

Strany 32

Hardware Management Console Best Practices - 38 - 7.5 Update (Corrective Service) In between HMC releases, or between upgrades, there will be times

Strany 33

Hardware Management Console Best Practices - 39 - Corrective service is a cumulative maintenance release within a single version that customers can

Strany 34

Hardware Management Console Best Practices - 4 - 7.7.1 Remote command...

Strany 35

Hardware Management Console Best Practices - 40 - Temporary Fix) value associated with the interim fix or service pack when using a command such as

Strany 36

Hardware Management Console Best Practices - 41 - 7.7.2 Network Installation/Update/Backup/Restore Beginning with Version 5 Release 1.0, you can s

Strany 37

Hardware Management Console Best Practices - 42 - This file is part of the syslinux package and should be copied from /usr/lib/syslinux/ to /var/tft

Strany 38

Hardware Management Console Best Practices - 43 - File Name Location on Media Directory to copy to disk1.img Media 1: base/ /home/hmc/images/ d

Strany 39

Hardware Management Console Best Practices - 44 - F12 and select the network device as the startup device for this boot instance. NOTE: In a future

Strany 40 - 7.7.1 Remote command

Hardware Management Console Best Practices - 45 - • If you have more than one network card on your HMC, select Default if the install images resid

Strany 41 - 7.7.3 Server setup

Hardware Management Console Best Practices - 46 - specified, however the full hostname with domain should be specified. xdir Directory or File name

Strany 42

Hardware Management Console Best Practices - 47 - 7.9.3 Preparing the HMC Once the server is set up, follow the steps below to prepare the HMC. If

Strany 43

Hardware Management Console Best Practices - 48 - while HMC B may choose to contact the same server with user intervention. In addition, HMC B has m

Strany 44

Hardware Management Console Best Practices - 49 - 8 Tips for Maintaining Licensed Internal Code Make sure you keep track of new releases, updates

Strany 45 - 7.9.1 Server setup

Hardware Management Console Best Practices - 5 - 1 Overview This paper is a compilation of useful information, recommendations and best practices f

Strany 46

Hardware Management Console Best Practices - 50 - 9 Tips for Maintaining System Firmware on the Managed System The naming convention for system fir

Strany 47 - 7.9.3 Preparing the HMC

Hardware Management Console Best Practices - 51 - 9.2 Concurrent versus Disruptive Updates Starting with HMC V4R5, the behavior of the code update

Strany 48

Hardware Management Console Best Practices - 52 -

Strany 49

Hardware Management Console Best Practices - 53 - Appendix I The HMC does not have any Active Directory or LDAP support for automated user manageme

Strany 50

Hardware Management Console Best Practices - 54 - {echo "hmcusers: -o [ add | delete ] -h <list of hmchosts>"echo " -l <logi

Strany 51

Hardware Management Console Best Practices - 55 - echo "user names not specified"usagefiif [ "$op" == "add" ]; then# s

Strany 52 - - 52

Hardware Management Console Best Practices - 56 - if [ $? -eq 0 ]; thenecho "Deleted user "$u" on "$ielseecho "Failed to de

Strany 53 - Appendix I

Hardware Management Console Best Practices - 57 - © IBM Corporation 2005 IBM Corporation Systems and Technology Group

Strany 54

Hardware Management Console Best Practices - 6 - 2 Planning Planning should be done for any major change in any computing environment, including a

Strany 55

Hardware Management Console Best Practices - 7 - The number of servers each HMC can manage varies by server size and complexity. Each server partit

Strany 56

Hardware Management Console Best Practices - 8 - A server with dual HMCs would be connected to two private networks with each HMC acting as a DHCP s

Strany 57 -

Hardware Management Console Best Practices - 9 - reasons. If no laptop is available, an ASCII terminal can be used on the native serial port to acce

Komentáře k této Příručce

Žádné komentáře