http://fibrevillage.com/storage/279-hot-add-remove-rescan-of-scsi-devices-on-linux



Hot add, remove, rescan of SCSI devices on Linux

Finding informations about SCSI devices

The first problem when working with SCSI devices might be to map informations you got from /proc/scsi/scsi to the device names the kernel uses like /dev/sda and so on.

Or you can use lsscsi utlity. Here's an example:

# lsscsi
[0:0:0:0]    disk    ATA      SEAGATE ST31000N SU0E  /dev/sda 
[0:0:1:0]    disk    ATA      SEAGATE ST31000N SU0E  /dev/sdb 
...
[1:0:1:0]    disk    ATA      SEAGATE ST31000N SU0E  /dev/sdj 
[1:0:2:0]    disk    ATA      SEAGATE ST31000N SU0E  /dev/sdk 
[1:0:3:0]    disk    ATA      HITACHI H7210CA3 A3CB  /dev/sdl 
[1:0:4:0]    disk    ATA      HITACHI HUA7210S AC5A  /dev/sdm 
...
[5:0:7:0]    disk    ATA      SEAGATE ST31000N SU0D  /dev/sdav
[6:0:0:0]    mediumx IBM      TS3500           0104  /dev/sch0
[6:0:1:0]    tape    IBM      ULT3580-TD5      0104  /dev/st0 
[6:0:2:0]    tape    IBM      ULT3580-TD5      0104  /dev/st1

You can find same info by checking /proc/scsi/scsi

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: SEAGATE ST31000N Rev: SU0E
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: ATA      Model: SEAGATE ST31000N Rev: SU0E
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi0 Channel: 00 Id: 02 Lun: 00
  Vendor: ATA      Model: SEAGATE ST31000N Rev: SU0E
  Type:   Direct-Access                    ANSI  SCSI revision: 05
...

In the example above

Host: scsi0 Channel: 00 Id: 01 Lun: 00 
is the same device of [0:0:0:0] in the output of lsscsi

Where the output

          h == hostadapter id (first one being 0)
          c == SCSI channel on hostadapter (first one being 0)
          t == ID
          l == LUN (first one being 0)

Rescan of a SCSI bus

Surely reboot a server will let the scsi device get rescanned. But this is not the prefered way. The easiest way is to rescan the whole SCSI bus which will enable the Linux kernel to detect new devices!

To issue a SCSI bus rescan you must know on which bus you've added the device. If you don't know which bus and if there are mutliple buses on the system you can rescan each bus which will be somehow annoying but will not interrupt the system. 
To initiate a SCSI bus rescan type

echo "- - -" > /sys/class/scsi_host/host<H>/scan

where H stands for the SCSI bus you want to scan.

# lsscsi
...
[1:0:0:7]    disk    IBM      1814      FAStT  1060  /dev/sdb 
[1:0:0:8]    disk    IBM      1814      FAStT  1060  /dev/sdc 
[1:0:0:10]   disk    IBM      1814      FAStT  1060  /dev/sde 
# echo "- - -" > /sys/class/scsi_host/host1/scan
# lsscsi
...
[1:0:0:7]    disk    IBM      1814      FAStT  1060  /dev/sdb 
[1:0:0:8]    disk    IBM      1814      FAStT  1060  /dev/sdc
[1:0:0:9]    disk    IBM      1814      FAStT  1060  /dev/sdd 
[1:0:0:10]   disk    IBM      1814      FAStT  1060  /dev/sde

Well done, we got /dev/sdd back.

By the way this does not only work for disks but also for SCSI CD/DVD devices.

You can still use the old way, to get sdd back

echo "scsi add-single-device 1 0 0 9" > /proc/scsi/scsi

For more devices, you have to repeat the same for all devices

Deletion of a SCSI Device

There might be the situation where you must remove a SCSI device from the system.

Easy by using

    echo 1 > /sys/class/scsi_device/h:c:t:l/device/delete
    or
    echo 1 > /sys/block/<dev>/device/delete
    where <dev> is like sda or sdb etc..

Here's an example:

# echo 1 > /sys/block/sdau/device/delete 
# lsscsi | grep sdau
#

Now you see the device sdau is gone.

In old way, this is what you would like to do

echo "scsi remove-single-device h c t l" > /proc/scsi/scsi

Add a SCSI Device back

Surely this can be done just rescan the SCSI bus that the disk seats inuse wildcard like below

    echo "- - -" > /sys/class/scsi_host/host<h>/scan

You can also do this if you know the device SCSI location h:c:t:l

    echo "c t l" >  /sys/class/scsi_host/host<h>/scan

Old way

    echo "scsi add-single-device a b c d" > /proc/scsi/scsi

Rescan of a SCSI Device

The problem of a SCSI bus rescan is, that it will only detect new devices. Can a existing or missing device be rescanned?

Sure, here is it

echo 1 > /sys/block/sdau/device/rescan 
or 
echo 1 > /sys/class/scsi_device/h:c:t:l/device/rescan

 In SAN environment, there is a easier way to manage SAN scsi devices, see Sysfs fibre channel tools


저작자표시 비영리 변경금지

'IBM PowerLinux > REDHAT' 카테고리의 다른 글

RHV RHVM 관련  (0) 2018.08.07
Redhat Nouveau 내장그래픽카드 nvidia 드라이버 설치 삭제  (0) 2018.07.03
CentOS 7 bonding nmcli  (0) 2017.11.01
gnome login screen id  (0) 2016.08.11
Linux semaphore  (0) 2016.07.11

 

ipmitool sel clear

 

저작자표시 비영리 변경금지

'IBM PowerLinux' 카테고리의 다른 글

OpenPOWER firmware with Intelligent Platform Management Interface (IPMI) features  (0) 2018.07.23
H/W check and status check  (0) 2018.07.23
Scale-out LC System Event Log Collection Tool  (0) 2018.06.19
RHEL7: How to get started with CPU governor  (0) 2018.03.20
리눅스에서 LVM 구성 및 사용방법  (0) 2018.03.06

 

추천 https://subicura.com/2017/01/19/docker-guide-for-beginners-1.html

 

저작자표시 비영리 변경금지

 

 

 

 

 

How to disable the Nouveau driver and install the Nvidia driver in RHEL 7

 

 

 

 

 

How to uninstall proprietary "Nvidia" module and switch back to Red Hat shipped "Nouveau" module ?

 

 

 

 

 

 

How to remove Nvidia drivers and switch back to nouveau for Red Hat Enterprise Linux 7?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

저작자표시 비영리 변경금지

'IBM PowerLinux > REDHAT' 카테고리의 다른 글

RHV RHVM 관련  (0) 2018.08.07
Hot add, remove, rescan of SCSI devices on Linux  (0) 2018.07.09
CentOS 7 bonding nmcli  (0) 2017.11.01
gnome login screen id  (0) 2016.08.11
Linux semaphore  (0) 2016.07.11

requisites for installing PowerAI Vision

 

https://www.ibm.com/support/knowledgecenter/en/SSRU69_1.1.0/base/vision_install_prereq.htm

저작자표시 비영리 변경금지


https://www-304.ibm.com/support/customercare/sas/f/lopdiags/scaleOutLCdebugtool.html



Scale-out LC Service and Support

[ Last updated: 01 June 2018 ]

Start

If a Linux partition is up and running then the standard sosreport should be collected in addition to running the plc.pl data collection script.

The sosreport needs to be run by root user, the script will prompt for additional information and when complete will show the location of the output file.

To collect the data from the BMC, the plc.pl script file (contained in the plc.zip package below) should be used by the customer to collect additional data.

Back to top

Installation

For MT 8348-21C, 8335-GCA, 8335-GTA, and 8335-GTB systems:
plc.zip

For MT 8001-12C, 8001-22C, 8005-12N, 8005-22N, 7063-CR1, 9006-22P, 9006-22C, and 5104-22C systems:
plc.zip

Prerequisites

  • The Linux system used to perform the data collection must have the following tool packages installed:
    • ipmitool
    • perl
    • sshpass - For POWER8 based systems only (8001, 8005, 7063, 8348, 8335-GTA GTB GCA)
    • The Linux system must have network connectivity to the BMC.

Installation steps

  1. Copy the pic.zip package to a Linux system that has network connectivity to the BMC of the Scale-out LC server you need to collect data from.
  2. Unzip the pic.zip file into a directory of your choice.
    Note: The files generated by this script will be saved in the same directory as the script is run from.
    unzip plc.zip
  3. The directory should now contain the following directories:
    P8-ppc64le
    P8-x86_64
    P9-ppc64le
    P9-x86_64

Back to top

Usage

usage: plc.pl { -b bmc_address | -i } [-a admin_pw] [-s sysadmin_pw] [-h host -u user -p password] [-f]

Flags:

-b BMC hostname or IP address
-a BMC ADMIN password if changed from default (admin)
-s BMC sysadmin password if changed from default (superuser)
-i Interactive mode
-f Collect BMC firmware image
-h Linux host address: Only on POWER8 Systems
-u Linux host user ID: Only on POWER8 Systems
-p Linux host password: Only on POWER8 Systems

Errors

  • If sshpass is not found on the system then the plc.pl script will print "sshpass is required and not found on this system" and will exit with return code 1, for POWER8 based systems.
  • If the BMC is not reachable via ping then the plc.pl script will print, "Unable to ping bmchostname/IPaddress" and will exit with return code 2.
  • If a "command not found" error is returned when running the plc.pl command, try running the command by prepending the command with ./ so that the command is ./plc.pl

Back to top

Reference Information

This section is intended as additional reference information.

Installing Requisite Packages

Note: The linux server that is going to be used for running data collection script can be running any version of Linux on any type of server. It is not related to the Scale-out LC server or the version of Linux running on the Scale-out LC server.

  • Linux distributions have their own way to search, download and install packages such as the required ipmitool and sshpass programs.
  • If using a graphical front end, an easy to use GUI utility is provided that allows you to search the Linux repository (usually on the internet unless a local repository has been set up), select, download and install the required packages and any prerequisites they may have.
  • From the command line, different Linux distributions have different command line tools. You will need to be root user to run these commands.
    For example: sudo apt-get install ipmitool

We would expect the administrator to be familiar with installing packages and files on their Linux environment.

Back to top

Managing software
Taskapt (deb) Debian, Ubuntuzypp (rpm) openSUSEyum/dnf (rpm) Fedora, CentOSurpmi (rpm) Mandriva, Mageia
Install new software from package repositoryapt-get install pkgzypper install pkgyum install pkgurpmi pkg
Install new software from package filedpkg -i pkgzypper install pkgyum localinstall pkgurpmi pkg
Update existing softwareapt-get install pkgzypper update -t package pkgyum update pkgurpmi pkg
Remove unwanted softwareapt-get remove pkgzypper remove pkgyum erase pkgurpmi pkg

Back to top

IBM OpenBMC tool

The IBM OpenBMC tool is used to interact with the new OpenBMC on the 8335-GTG, 8335-GTC, 8335-GTW, 8335-GTH, and 8335-GTX products.

Pre-requisites:

  • python 3
  • python 3 requests

For RHEL distributions:
openbmctool-1.0-4.noarch.rpm

For other operating systems:
openbmctool.zip

Note: For Windows OS support, version 1.04 or greater of the tool is needed.

RHEL

  • To install, run the following as root:
    yum install ./<rpm downloaded above>

Other operating systems

To install, complete the following:

  1. Extract the contents of the zip file.

  2. It is recommended to add a link to this file in your path.

    For example:
    ln -s -f /opt/ibm/ras/bin/openbmctool.py /usr/bin/openbmctool

  3. After extracting the contents, operating systems other than Linux will require you to add 'python' at the beginning of each command:

    For example:
    python openbmctool.py -H <bmc IP> or <bmc hostname> -U <username> -P <password> chassis power status

Execution

  1. To get help on a command:
    openbmctool -H <bmc IP> or <bmc hostname> -U <username> -P <password> chassis power -h

  2. To view log entries:
    openbmctool -H <bmc IP> or <bmc hostname> -U <username> -P <password> sel print

  3. To collect service data from the BMC:
    openbmctool -H <bmc IP> or <bmc hostname> -U <username> -P <password> collect_service_data

Back to top

Scale-out LC system VPD update tool

The Scale-out LC system VPD update tool is used to make VPD modifications to POWER Systems from the host OS of the machine.

For Ubuntu distributions: 
ophtk-lht_20160128-1.ub14.04_ppc64el.deb

For RHEL distributions:
ophtk-lht-20160128-1.el7.ppc64le.rpm

Petitboot Plugin:

Ubuntu

  • To install, run the following:
    sudo dpkg -i <deb downloaded above>
  • If you encounter a dependency error when installing the tool, run the following to install dependencies and complete the install:
    sudo apt-get -f install

RHEL

  • To install, run the following as root:
    yum install ./<rpm downloaded above>

Petitboot Plugin:

  • To install, the plugin from a usb key:
    pb-plugin install /path/to/vpdupdate-1.3.pb-plugin

Note: /path/to needs to be substituted with the actual path to the petitboot plugin. For example, pb-plugin install /var/petitboot/mnt/dev/sda/vpdupdate-1.3.pb-plugin

To install the plugin from a network location from the petitboot shell:
pb-plugin install http://mystorage.com/path/to/vpdupdate-1.3.pb-plugin

Execution

  1. To update the machine serial number:
    sudo /opt/openpower/lht/bin/updateserial <1234567>
    Note: <1234567> to be replaced with your seven character Serial Number

    2. From Petitboot shell:
    /var/lib/pb-plugins/bin/updateserial <1234567>


  2. To update the machine model:
    sudo /opt/openpower/lht/bin/updatemodel <8335-GTA>
    Note: <8335-GTA> to be replaced with your system model

    3. From Petitboot shell:
    /var/lib/pb-plugins/bin/updatemodel <8335-GTA>


  3. For MT 8001-12C, 8001-22C, 8005-12N, 8005-22N, and 7063-CR1 systems, run the following command to save changes:
    ipmitool -I lanplus - U <username> -P <password> -H <bmcIP> raw 0x3a 0x1c 

    Note: This may take about 30 seconds to complete. Run the following command to check status and continue after it returns a value of 0.
    ipmitool -I lanplus -U <username> -P <password> -H <bmcIP> raw 0x3a 0x1d

    4. For MT 8348-21C, 8335-GCA, 8335-GTA, and 8335-GTB: Reinstall or upgrade the PNOR firmware for the changes to take effect.


  4. Reboot the system to petitboot or the host OS to ensure the changes take effect.

    5. Note: For 8348-21C, to verify that is the machine type and model, you will need to look at FRU ID 2 via the GUI or ipmitool fru print 3. For all other Machine Types: To verify that is the machine type and model, you will need to look at FRU ID 3 via GUI or ipmitool fru print 3.


Back to top

SNMP Trap enablement

For MT 8348-21C, 8335-GCA, 8335-GTA, and 8335-GTB systems:

  1. Log into the BMC WebGUI
  2. From the Configuration menu, click "PEF"
  3. Click "LAN Destination"
  4. Within the displayed table, click on a row, then click Add for a new entry
  5. From the Destination type drop-down, select "SNMP Trap". Populate the Destination Address field with the IPv4 Address of the system where the SNMP client resides. Click "Save".
  6. This completes the BMC setup for sending SNMP Traps. The MIB table below can be used with your client for interpreting the traps.

For MT 8001-12C, 8001-22C, 8005-12N, 8005-22N, and 7063-CR1 systems:

  1. Log into the BMC WebGUI
  2. From the Configuration menu, click "Alerts"
  3. Within the displayed table, click on a row, then click "Modify"
  4. From the "Event Severity" drop-down, pick the level of alerts you want to receive. Populate the Destination IP field with the IPv4 Address of the system where the SNMP client resides. Click "Save".
  5. This completes the BMC setup for sending SNMP Traps. The MIB table below can be used with your client for interpreting the traps.

Back to top


저작자표시 비영리 변경금지

'IBM PowerLinux' 카테고리의 다른 글

H/W check and status check  (0) 2018.07.23
Amber off  (0) 2018.07.05
RHEL7: How to get started with CPU governor  (0) 2018.03.20
리눅스에서 LVM 구성 및 사용방법  (0) 2018.03.06
LVM home삭제후 root 증설  (0) 2018.02.14

 

 

항공권 ( G마켓 )

 

 

 

 

항공스케줄

요금규정
여정 항공편 출발 도착 비행시간 좌석등급
출국편 인천(ICN)
→후쿠오카(FUK)		 제주항공
7C1404 		2018/06/23 (토)
15:30 		2018/06/23 (토)
16:45 		01시간 15분 일반석
총 소요시간 : 01시간 15분 (총 비행시간 : 01시간 15분)
귀국편 후쿠오카(FUK)
→인천(ICN)		 제주항공
7C1401 		2018/06/25 (월)
12:45 		2018/06/25 (월)
14:10 		01시간 25분 일반석
총 소요시간 : 01시간 25분 (총 비행시간 : 01시간 25분)

 

 

 

 

6월 23일

 

 

Valie Hotel Tenjin
ヴァリエ ホテル 天神

 
 
  
orange-yellow star-3
2-8-12 Daimyou Chuo-ku, Fukuoka, Fukuoka, Japan 810-0041
〒810-0041 福岡県福岡市中央区大名2-8-12, 福岡, 福岡, 日本 810-0041
 
숙박일수 및 객실수: 객실 1개, 1박
체크인 날짜: June 23, 2018 (after 03:00 PM)
체크아웃 날짜: June 24, 2018 (before 10:00 AM)
예약 번호:
투숙객 이름:
 

고객님의 예약요금이 전액 결제 완료되었습니다.

Queen Double Room with Queen Bed - Non-Smoking KRW 134,387
포함: 봉사료 10%, 세금 8%
총 카드 결제액: KRW 134,387

 

 

6월 24일

 

 

저작자표시 비영리 변경금지

 

 

 

 

 

 

 

- 두바이 24시간 체크인 가능 -> 힐튼 계열

http://cafe.naver.com/dubaiok/5485

http://www.gtakorea.co.kr/notice/hotel_view.html?seq=600

 

두바이호텔 더블트리힐튼

https://blog.naver.com/rumigram/221214255471

https://blog.naver.com/max3502/221109021185

->오픈한지 얼마안됨

->두마이몰 5분거리

->무료셔틀이 다닌당

 

 

 

- 복귀때 5시간 이상 대기시 에미레이트 항공사에서 밀바우처 제공

https://blog.naver.com/cocxox261/220573004887

 

 

- 콘래드 워터빌라 5박 후 유상 upgrade 신청

5박 95000 * 5 포인트

저작자표시 비영리 변경금지

 

[세탁기]

 

-후보1) F19VDWC ( 19kg + 3.5kg )  - 167만원 (KB카드)

 

http://with.gsshop.com/deal/deal.gs?dealNo=29062909&NaPm=ct=jfrwbdgw|ci=33d69435a8757ee5047fd414af51464f59492685|tr=slsl|sn=1|hk=6e02ab11938a0f95a5308f75ffde9f95bbf57018&media=MA&fromWith=Y

선택 76번

 

 

-후보2) F19bfwm (19kg + 4kg) - 175만원

 

 

 

https://search.shopping.naver.com/search/all.nhn?query=F19VDWC&cat_id=&frm=NVSHATC

 

저작자표시 비영리 변경금지

 

http://www.unixwerk.eu/aix/hmc-howto.html

 

This documents contains the most important HMC commands. It covers both, the old power4 commands (up to HMC Version 3) and the new power5 style commands (HMC Version 4-6). A lot of nice commands still available for version 3 (power4) are removed from newer releases. One example of these nice commands is lslpars and it's not available for HMC version 4 and higher. The real reason behind it is that IBM wants to force us to use the web based tools wsm and WebSM or the new HMC browser GUI. This documents helps you to survive with the HMC commands in case working with the web based tools is not feasible.

In the examples below we call a whole power frame (aka Managed System) pserver. We call an LPAR mylpar. If an example output shows more than one LPAR name we enumerate it. LPAR Profiles are shown as myprofile. You have to replace these names with your object names.

If you use power6 systems, you need the new HMC version7. Although the GUI has changed from wsm to a browser based service, the commandline remains compatible. You can just use the power5 examples for power6, power7, and power8. However, additional features have been implemented.with HMC version 7.

 

Contents

HMC Management

  1. HMC Version
  2. Network configuration of the HMC
  3. Reboot the HMC
  4. How to change the HMC password (of user hscroot)
  5. How to add an SSH key for remote access
  6. Show Available Filesystem Space

LPAR Management: Status Information

  1. LPAR Status
  2. Show Status and LED/LCD Display of an LPAR
  3. Show Status and LED/LCD Display of a Systems Running in FullPartitionMode
  4. Overview LPAR IDs
  5. Overview Connection State
  6. Show a List of all I/O Adapters
  7. Overview DLPAR status

LPAR Management: Operations

  1. Soft Reset of an LPAR
  2. Soft Reset of a Systems Running in FullPartitionMode
  3. Hard Reset of an LPAR
  4. Hard Reset of a Systems Running in FullPartitionMode
  5. Virtual Console
  6. Activation of an LPAR
  7. How to boot an LPAR into SMS Menu
  8. How to Power on a System Running in FullPartitionMode
  9. Bring the key switch to position NORMAL

LPAR Configuation

  1. Change an LPAR's Name
  2. Rename a Managed System
  3. DLPAR: Increase the Number of Processing Units of an LPAR
  4. DLPAR: Increase the Amount of Memory of an LPAR

Operations in an Virtualized Environment

  1. Make virtual WWPNs visible to the SAN
  2. Show all virtual WWPNs assigned to an LPAR
  3. Logout virtual WWPNs from the SAN

 

HMC Management

1. HMC Version

hscroot@hmc> lshmc -V
 Version: 3
 Release: 3.2
HMC Build level 20040827.1

power4 HMCs could never show a version higher 3.x - HMC version 4.x and higher are only for power5 systems. Power6 systems need HMCs version 7.x.

 

2. Network configuration of the HMC

hscroot@hmc> lshmc -n

 

3. Reboot the HMC

power4 + power5/6/7: 

hscroot@hmc> hmcshutdown -t now -r

 

 

4. How to change the HMC password (of user hscroot)

power4 + power5/6/7: 

hscroot@hmc> chhmcusr -u hscroot -t passwd
Enter the new password:
Retype the new password:

 

 

5. How to add an SSH key for remote access

  • for hscroot

    power5/6/7: 

    hscroot@hmc> mkauthkeys -a "public key"
    Use the public key found in the users .ssh directory for public key (i.e. the contents of the file ~/.ssh/id_rsa.pub).

     

  • for other users

    power5/6/7: 

    hscroot@hmc> mkauthkeys -u user -a "public key"

     

    6. Show Available Filesystem Space

    power5/6/7: 

    hscroot@hmc> monhmc -r disk -n 0
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda2             16121184   4958484  10343788  33% /
udev                    517300       156    517144   1% /dev
/dev/sda3              6040320   1341736   4391744  24% /var
/dev/sda7              8056524    154132   7493140   3% /dump
/dev/sda8             38669964    203056  36502564   1% /extra

    It's just the same as you would expect from the UNIX command df.

     

    LPAR Management: Status Information

    1. LPAR Status

    That's how you get an overview of all systems controlled by your HMC:

    power4: 

    hscroot@hmc> lslpars

     

    power5/6/7: 

    hscroot@hmc> lssyscfg -r sys -F name:serial_num:state
pserver1:656D24A:Operating
pserver2:656FFFF:Operating

    The format string 'lpar_id:name:serial_num:state' also tells you the serial number of the systems. You can omit the field 'serial_num' if you don't need to know.
    However, for every system from the list above you get the LPAR overview as shown below: 

    hscroot@hmc> lssyscfg -m pserver -r lpar -F name:state

    Example: 

    hscroot@hmc> lssyscfg -m pserver1 -r lpar -F name:state
mylpar1:Running
mylpar2:Running
mylpar3:Not Activated

    Don't know where to start? Find all managed systems and LPARs with a query: 

    hscroot@hmc> for m in $(lssyscfg -r sys -F name); do printf "\n=== $m ===\n" ; \
                                                     lssyscfg -r lpar -m $m -F lpar_id:name:state | sort -n ; done
=== pserver1 ===
1:mylpar1:Running
2:mylpar2:Running
3:mylpar3:Not Activated

=== pserver2 ===
2:mylpar12:Running
3:mylpar13:Running

     

    2. Show Status and LED/LCD Display of an LPAR

    power4: 

    hscroot@hmc> lssyscfg -r lpar -m pserver -n mylpar

     

    power5/6/7: 

    
hscroot@hmc> lsrefcode -m pserver -r lpar --filter "lpar_names=mylpar" -F lpar_name:refcode

    You can even see the history of LED codes. Just use -n <NUM> for the last NUM codes. For example, if you want to see the last 5 LED codes of an LPAR type 

    hscroot@hmc> lsrefcode -m pserver -r lpar --filter "lpar_names=mylpar"  -n 5 -F lpar_name:refcode
mylpar:
mylpar:0c33
mylpar:
mylpar:0539
mylpar:0538

    ... and for the status LEDs: 

    hscroot@hmc> lsled -m pserver -r sa -t virtuallpar --filter ""lpar_names=mylpar""

     

     

    3. Show Status and LED/LCD Display of a Systems Running in FullPartitionMode

    power4: 

    hscroot@hmc> lssyscfg -r sys -n pserver

     

     

    4. Overview LPAR IDs

    power5/6/7: 

    hscroot@hmc> lssyscfg -r lpar -m pserver -F lpar_id:name:serial_num:state | sort -n
1:vioserver1:Running
2:vioserver2:Running
3:mylpar1:Not Activated
4:mylpar2:Running
5:mylpar3:Running
6:mylpar4:Running
7:mylpar5:Running
8:mylpar6:Running
9:mylpar7:Running
10:mylpar8:Not Activated

     

     

    5. Overview Connection State

    Are all service processors connected to my HMC?

    power5/6/7: 

    hscroot@hmc> lssysconn -r all -F type_model_serial_num:ipaddr:state | sort
9117-570*65AE18C:172.16.255.253:Connected
9117-570*65AE18C:172.16.254.255:Connected
9117-570*65AE2AC:172.16.255.254:Connected
9117-570*65AE2AC:172.16.254.254:Connected
9117-570*650D70D:172.16.255.252:Connected
9117-570*650D70D:172.16.253.255:Connected
9117-570*650D71D:172.16.254.253:Connected
9117-570*650D71D:172.16.255.251:Connected
9131-52A*065F7BB:172.16.253.254:Connected
9131-52A*065F8BA:172.16.254.252:Connected

    The link to the name of the managed system is the serial number - not the IP address! The IP addresses listed above are mounted on the service processor's private NIC and managed by the integrated DHCP server of the HMC.

     

    6. Show a List of All I/O Adapters

    The command below will show a list of all adapters physically plugged into a Managed System:

    power5/6/7: 

    hscroot@hmc> lshwres -r io -m pserver --rsubtype slot --filter -F lpar_name:drc_name:description
null:U78C0.001.DBJC357-P2-C8-T5:Universal Serial Bus UHC Spec
mylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Bus
null:U78C0.001.DBJC357-P2-C2:Fibre Channel Serial Bus
vios2:U78C0.001.DBJC357-P2-T3:RAID Controller
vios2:U78C0.001.DBJC357-P2-C8-T7:Generic XT-Compatable Serial Controller
vios2:U78C0.001.DBJC357-P2-C5:Fibre Channel Serial Bus
vios2:U78C0.001.DBJC357-P2-C6:Ethernet controller
vios2:U78C0.001.DBJC357-P2-C9-T2:PCI-E SAS Controller
vios2:U78C0.001.DBJC357-P2-C9-T1:PCI-E SAS Controller
null:U78C0.001.DBJC373-P2-C8-T5:Universal Serial Bus UHC Spec
mylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus
null:U78C0.001.DBJC373-P2-C2:Fibre Channel Serial Bus
vios1:U78C0.001.DBJC373-P2-T3:RAID Controller
vios1:U78C0.001.DBJC373-P2-C8-T7:Generic XT-Compatable Serial Controller
vios1:U78C0.001.DBJC373-P2-C5:Fibre Channel Serial Bus
vios1:U78C0.001.DBJC373-P2-C6:Ethernet controller
vios1:U78C0.001.DBJC373-P2-C9-T2:PCI-E SAS Controller
vios1:U78C0.001.DBJC373-P2-C9-T1:PCI-E SAS Controller

    A leading "none" indicates that the adapter is not assigned to an LPAR. To show a list of all I/O adapters owned by a specific LPAR use the "--filter" modifier:

    power5/6/7: 

    hscroot@hmc> lshwres -r io -m pserver --rsubtype slot -F lpar_name:drc_name:description --filter "lpar_names=mylpar1"
mylpar1:U78C0.001.DBJC357-P2-C1:Fibre Channel Serial Bus
mylpar1:U78C0.001.DBJC373-P2-C1:Fibre Channel Serial Bus

     

    7. Overview DLPAR status

    power5/6/7: 

    hscroot@hmc> lspartition -dlpar
<#0> Partition:<6*9117-MMB*656D24A, mylpar1.unixwerk.de, 111.111.15.66>
       Active:<0>, OS:<AIX, 5.3, 5300-09-08-1036>, DCaps:<0x0>, CmdCaps:<0x0, 0x0>, PinnedMem:<512>
<#1> Partition:<2*9117-MMB*656D24A, vios1.unixwerk.de, 111.111.15.65>
       Active:<1>, OS:<AIX, 6.1, 6100-06-00-0000>, DCaps:<0x4f9f>, CmdCaps:<0x1b, 0x1b>, PinnedMem:<520>
<#2> Partition:<1*9117-MMB*656D24A, vios2.unixwerk.de, 111.111.15.64>
       Active:<1>, OS:<AIX, 6.1, 6100-06-00-0000>, DCaps:<0x4f9f>, CmdCaps:<0x1b, 0x1b>, PinnedMem:<518>
<#3> Partition:<3*9117-570*656FFFF, mylpar2.unixwerk.de, 111.111.226.4>
       Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<1707>
<#4> Partition:<1*9117-570*656FFFF, mylpar3.unixwerk.de, 111.111.226.2>
       Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<884>
<#5> Partition:<1*9133-55A*650D71D, mylpar7.unixwerk.de, 111.111.0.26>
       Active:<1>, OS:<AIX, 5.3, 5300-09-03-0918>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<406>
<#6> Partition:<4*9117-570*656FFFF, mylpar4.unixwerk.de, 111.111.226.5>
       Active:<1>, OS:<AIX, 5.3, 5300-09-04-0920>, DCaps:<0x2f>, CmdCaps:<0xb, 0xb>, PinnedMem:<967>

    A value <1> for Active: should be fine.

     

    LPAR Management: Operations

    1. Soft Reset of an LPAR

    power4: 

    hscroot@hmc> chsysstate -m pserver -r lpar -n mylpar -o reset

     

    power5/6/7: 

    hscroot@hmc> chsysstate -r lpar -m pserver -o shutdown -n mylpar

     

     

    2. Soft Reset of a System Running in FullPartitionMode

    power4: 

    hscroot@hmc> chsysstate -n pserver -r sys -o reset

     

     

    3. Hard Reset of an LPAR

    power4: 

    hscroot@hmc> chsysstate -m pserver -r lpar -n mylpar -o off

     

    power5/6/7: 

    hscroot@hmc> chsysstate -r lpar -m pseries -o shutdown -n mylpar --immed

     

     

    4. Hard Reset of a System Running in FullPartitionMode

    power4: 

    hscroot@hmc> chsysstate -n pserver -r sys -o off

     

     

    5. Virtual Console

    That's how you get a connection to an LPAR's serial console:

    power4 + power5/6/7: 

    hscroot@hmc> mkvterm -m pserver -p mylpar

    If your system is running in FullSystemPartition-Mode you connect with a command like this:

    power4: 

    hscroot@hmc> mkvterm -m pserver

    You can escape from the console connection by typing ~~. (twice tilde followed by a dot)

    If you cannot connect to the serial console and you get an error message instead: 

    All available virtual terminal sessions have been opened and are in use. 
To force a new open session, perform a Close Terminal Session operation
which frees up the session.

    there is still another active connection to this console. You can close this connection with:

    power4 + power5/6/7: 

    hscroot@hmc> rmvterm -m pserver -p mylpar

    If you're not sure which managed system belongs to an LPAR you could walk through the vtmenu: 

    hscroot@hmc> vtmenu
 Retrieving name of managed system(s) . . . 

 ----------------------------------------------------------
  Managed Systems:
 ----------------------------------------------------------
   1) pserver1
   2) pserver2
   3) pserver3

 Enter Number of Managed System.   (q to quit): 1

 ----------------------------------------------------------
  Partitions On Managed System:  pserver1
 ----------------------------------------------------------
   1)    mylpar1                              Running
   2)    mylpar2                              Running
   3)    mylpar3                              Running
   4)    mylpar4                              Running
   5)    mylpar5                              Running


 Enter Number of Running Partition (q to quit):

    Just enter a number and you will be connected to the console of the corresponding LPAR.

     

    6. Activation of an LPAR

    power4: 

    hscroot@hmc> chsysstate -r lpar -m pserver -o on [ -f myprofile ] -n mylpar

     

    power5/6/7: 

    hscroot@hmc> chsysstate -r lpar -m pserver -o on -f myprofile -n mylpar

     

     

    7. How to Boot an LPAR into SMS Menu

    power4:

    You have to create an additional profile. In this profile set the boot mode to 'sms'. We call the profile mysmsprofile. Then start the LPAR with this profile: 

    hscroot@hmc> chsysstate -r lpar -m pserver -o on -f mysmsprofile -n mylpar

     

    power5/6/7:

    With new HMCs a special profile is not any longer needed. The profile's boot mode can be overwirtten with -b: 

    hscroot@hmc> chsysstate -r lpar -m pserver -o on -f myprofile -b sms -n mylpar

    The same way the LPAR can be bootet into the Open Firmware prompt (Bootmode: 'of'): 

    hscroot@hmc> chsysstate -r lpar -m pserver -o on -f myprofile -b of -n mylpar

     

     

    8. How to Power on a System Running in FullPartitionMode

    power4: 

    hscroot@hmc> chsysstate -o on -r sys -n pserver -c full

     

     

    9. Bring the key switch to position NORMAL

    This might be necessary on some power5 HMCs when an LPAR does not properly boot after issuing the power on command above. You might see a message like this: 

    0514-440 cfgcon: failed to create log file: check path name, permissions, and available space

    When seeing this you can only access diag mode or boot the LPAR in singleuser mode. This command sets the key switch back to normal position:

    power5/6/7: 

    hscroot@hmc> chsysstate -r lpar -o chkey -k norm -n mylpar -m pserver

     

     

    LPAR Configuration

    1. Change an LPAR's Name

    Let's say we have these five LPARs defined on a managed system: 

    hscroot@hmc> lssyscfg -r lpar -m pserver -F lpar_id:name:state
1:vios1:Running
2:vios2:Running
3:barney:Running
4:mylpar2:Running
5:mylpar3:Running

    Now we want to change the name of LPAR 3 from barney to mylpar1:

    power5/6/7: 

    hscroot@hmc> chsyscfg -r lpar -m pserver -i "name=barney,new_name=mylpar1"

    We check and see that the name of LPAR 3 indeed has changed to mylpar1: 

    hscroot@hmc> lssyscfg -r lpar -m pserver -F lpar_id:name:state
1:vios1:Running
2:vios2:Running
3:mylpar1:Running
4:mylpar2:Running
5:mylpar3:Running

     

    2. Rename a Managed System

    This would change the name of the manages system pserver to pserver1:

    power5/6/7: 

    hscroot@hmc> chsyscfg -r sys -m pserver -i "new_name=pserver1"

     

    3. DLPAR: Increase the Number of Processing Units of an LPAR

    To assign 8 additonal processing units to an LPAR run the following command:

    power5/6/7: 

    hscroot@hmc> chhwres -r proc -m pserver -o a -p mylpar --procunits 8

     

    4. DLPAR: Increase the Amount of Memory of an LPAR

    To assign 1 GB additonal memory to an LPAR run the following command:

    power5/6/7: 

    hscroot@hmc> chhwres -r proc -m pserver -o a -p mylpar -q 1024

     

     

     

    Operationen in einer virtualisierten Umgebung

    HMC Version 7 can run operations on Virtual I/O Servers.

    1. Make virtual WWPNs visible to the SAN

    The below command would login all virtual adapters of the LPAR with ID 12 to the SAN:

    HMC Version 7 

    hscroot@hmc> chnportlogin -o login -m pserver --id 12

     

    2. Show all virtual WWPNs assigned to an LPAR

    e.g. for an LPAR with ID 12, type

    HMC Version 7 

    hscroot@hmc> lsnportlogin -m pserver --filter "lpar_ids=12"
lpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=51,wwpn=c050726660a0002c,wwpn_status=1,logged_in=vios,wwpn_status_reason=null
lpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=51,wwpn=c050726660a0002d,wwpn_status=1,logged_in=vios,wwpn_status_reason=null
lpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=52,wwpn=c050726660a0002e,wwpn_status=1,logged_in=vios,wwpn_status_reason=null
lpar_name=mylpar,lpar_id=12,profile_name=default,slot_num=52,wwpn=c050726660a0002f,wwpn_status=1,logged_in=vios,wwpn_status_reason=null

    You can also list the status of more than one LPAR in one go:

    HMC Version 7 

    hscroot@hmc> lsnportlogin -m pserver --filter "\"lpar_ids=12,13\""

     

    3. Logout virtual WWPNs from the SAN

    HMC Version 7 

    hscroot@hmc> chnportlogin -o logout -m pserver --id 12

    •  

    저작자표시 비영리 변경금지

    + Recent posts

    티스토리툴바

     

    Hilton Fukuoka Sea Hawk

     

    24, Jun. 2018 – 25, Jun. 2018

    Your Room Information:
    DOUBLE HILTON GUESTROOM
    Rooms:   1
    Guests:  2  Adults
    Check In:  Jun 24 3:00 PM
    Check Out:  Jun 25 12:00 PM

     

     

    Your Plan Information:
    HONORS ADV PURCHASE
    Rate per  night :  12495.00   JPY
    Total for Stay per Room
    Rate: 12,495.00   JPY
    Service Charge : 1,624.00   JPY
    Taxes: 1,129.55   JPY
    Total: 15,248.55   JPY
    Total for Stay : 15,248.55   JPY