 |
|||||
|
 |
|
Power Systems Stuff Compiled by Michael Fryman @ IBM Table of Contents ASMI - Advanced System Management Interface ASMI Default logins and passwords Configuring NTP time synchronization on AIX To list all the PCI slots allocated to an LPAR To list all the PCI slots allocated to an LPAR To dynamically reallocate an adapter Alternate description for Mounting ISO images on AIX How to mount a ISO image on AIX V5.3 To Help speed up AIX filesystem mounts To mount Linux NFS shares (servers) on AIX systems (clients) Mounting w/Filesys Logging Disabled Working with Fibre Channel adapters and SAN storage How would I know if I am running a 32-bit kernel or 64-bit kernel? How do I know if I am running a uniprocessor kernel or a multiprocessor kernel? How can I change from one kernel mode to another? How would I know if my machine is capable of running AIX 5L Version 5.3? How would I know if my machine is CHRP-based? How would I know if my System p machine (hardware) is 32-bit or 64-bit? How much real memory does my machine have? How big are my disks, even fibre channel LUNs? Can my machine run the 64-bit kernel? What are the values of attributes for devices in my system? How many processors does my system have? How many hard disks does my system have and which ones are in use? How do I list information about a specific physical volume? How do I get a detailed configuration of my system? How do I find out the chip type, system name, node name, model number, and so forth? What version, release, and maintenance level of AIX is running on my system? How can I determine which fileset updates are missing from a particular AIX level? What SP (Service Pack) is installed on my system? Is a CSP (Concluding Service Pack) installed on my system? How do I create a file system? How do I change the size of a file system? How do I unmount a file system? How do I display mounted file systems? How do I remove a file system? How can I defragment a file system? Which fileset contains a particular binary? How do I display information about installed filesets on my system? How do I determine if all filesets of maintenance levels are installed on my system? How do I determine if a fix is installed on my system? How do I install an individual fix by APAR? How do I verify if filesets have required prerequisites and are completely installed? How do I determine the amount of paging space allocated and in use? How do I increase a paging space? How do I reduce a paging space? How would I know if my system is capable of using Simultaneous Multi-threading (SMT)? How would I know if SMT is enabled for my system? Is SMT supported for the 32-bit kernel? How do I enable or disable SMT? How do I get partition-specific information and statistics? How do I know if my volume group is normal, big, or scalable? How can I change the characteristics of a volume group? How do I create a logical volume? How do I increase the size of a logical volume? How do I display all logical volumes that are part of a volume group (for example, rootvg)? How do I list information about logical volumes? How do I remove a logical volume? How do I mirror a logical volume? How do I remove a copy of a logical volume? How to add a disk to a volume group? How do I find out what the maximum supported logical track group (LTG) size of my hard disk? How can I clone (make a copy of ) the rootvg? How can I display or set values for network parameters? How do I get the IP address of my machine? How do I identify the network interfaces on my server? How do I activate a network interface? How to install AIX from a Virtual Optical Device To see attributes of SEA adapter To make VIO Server and then VIO clients To make SEA adapters with failover To make and remove physical or logical backing device virtual devices Working with virtual media in VIOS Manually Creating VIOS NIM Resources To list All the managed systems attached to the HMC and some information about them Create LPAR using a SSH script To remove a terminal someone else is using How to find out what HMC(s) your AIX LPAR and system are managed by How to setup hw-raid before installing the operating system How to setup hardware raid after installing OS Start install with this command for VNC IBM Installation Toolkit for Linux Does More Than Just Install Linux Appendix A: Full HMC and System Setup Procedure HMC - identifying the network ports What if we do NOT see a DHCP request? Connecting the HMC to the Open network Confirming HMC network adapter "Media Speed" Secure connection from HMC to FSP ======== <End Table of Contents> ============================================= IBM DeveloperWorks Wikis· AIX 5.3 Installation Best Practices · AIX6 & POWER6 Hands-On Technical Demo Movies · HMC Command Line man pages PDF · Service & Support Best Practices Website
IBM Redbooks· Hardware Management Console V7 Handbook · Integrated Virtual Ethernet Adapter Technical Overview and Introduction · PowerVM Virtualization on IBM System p: Introduction and Configuration Fourth Edition · PowerVM Live Partition Mobility on IBM System p · IBM AIX Version 6.1 Differences Guide · PowerVM Virtualization on IBM System p: Managing and Monitoring · IBM System p Advanced POWER Virtualization (PowerVM) Best Practices · Advanced POWER Virtualization on IBM System p Virtual I/O Server Deployment Examples · IBM Electronic Services Support using Automation and Web Tools · Utility Capacity on Demand: What Utility CoD Is and How to Use It
Power and Planning· 7109 intelligent pdu · same as 7188 load value · no more than 80% load · so at 30amps no more than 24amps · at 60 amps line cord then no more than 48amps · 9854 30amp line cord Power Systems StuffASMI - Advanced System Management InterfaceASMI Default logins and passwordsAs soon as you login to ASMI, you are asked to change the default password. You will not be allowed to proceed unless you change the password.
The HMC access password is usually set from the HMC during initial login. If you change this password using the ASMI, the change takes effect immediately. Note: As a security measure, you are required to enter the current user’s password into the Current password for current user field. This password is not the password for the user ID you want to change.
ASMI Default IP AddressesEvery firmware service processor on a Power5 or Power6 box has 2 Ethernet interfaces used for connection to the Hardware Management Console (HMC). Immediately after the power cord is connected to the Power system, the service processor (FSP) sends a DHCP request through both interfaces. If no DHCP address is received it falls back to the default addresses: HMC1 Port: 192.168.2.147 / 255.255.255.0 HMC2 Port: 192.168.3.147 / 255.255.255.0 You can connect to ASMI webinterface through the browser.
ASMI IP Address from Operator PanelIf the default IPs for the ASMI interface are not accessible and you do not have access to any DHCPd logs which may have provided an adress you can use following procedure to determine the adress through 3 white buttons at the operation panel below the led: 1. Select function 02 2. Change "N" to "M" (for manual) 3. Select function 30 4. Change "**" to "00" and press Enter 5. See the adress of HMC1 at "00" and HMC2 at "01" 6. Select function 02 7. Change "M" back to "N" How to setup hw-raid before installing the operating systemDownload the latest Diagnostics ISO Image from: Diagnostic CD burn it onto a CD and then boot this CD. Once booted this will bring up the AIX diag which enables you to set the SCSI disk RAID settings as you like. Basically you have to modify all disks which should belong to a RAID configuration from a regular 512-byte block size to a 522-byte block size array candidate disk as only such candidate disks can be included in a RAID setting. Once the RAID settings are done, the OS will not see the single disks of the RAID setting anymore, just your RAID disks. JS22 POWER Blade Stuff
How to use SOL (Serial Over Lan)
How to Enable Serial Over LAN on the AMM1. Login to your BladeCenter Advanced Management Module: http://yourBladeCenter or https://yourBladeCenter 2. Navigate to Serial Over LAN (BladeTasks -> Serial Over LAN) 3. Enable SOL for your specific server 1. Locate the section “Serial Over LAN Status”. It should show a table of your bays and blade servers. 2. Check the server(s) for which you’d like to enable SOL 3. Click Enable Serial Over LAN link 4. Enable Serial Over LAN service by using the drop down box under Serial Over LAN Configuration 5. Click Save 6. Ensure that either Telnet or SSH is enabled. 7. To enable SSH (the more secure option) 1. Navigate to MM Control -> Security 2. Enable SSH Server using the drop down box 3. Select Save 8. To enable Telnet (the less secure option) 1. Navigate to MM Control -> Network Protocols 2. Scroll down to Telnet Protocol 3. Enable Telnet mode using the drop down box 4. Save You should be good to go. Note: SSH and Telnet can be assigned to non-standard ports in the BladeCenter. This can be checked under MM Control -> Port Assignments.
How to Connect to the Console1. SSH or Telnet into your BladeCenter 2. Set the timeout to zero (i.e. no timeout) for this session system> telnetcfg -t 0 -T system:mm[1] Set the environment variable to your blade bay number, then type console. If you don’t know your bay number, log into the BladeCenter GUI, http://yourBladeCenter. An example for connecting to the blade on bay 1: system> env -T system:blade[1] system:blade[1]> console -o or just enter this command Console login: To escape back into the BladeCenter CLI, use the escape sequence listed under SOL in the Blade Center GUI. The default sequence is ^[(. That is ESC and then Shift + ( or Ctrl + [ and then Shift + ( Remove all LPAR config info on blade (or other POWER) server using VIOS/IVM command lineNote: If you are reinstalling VIOS on the same blade and want to remove the previous logical partition information and return the blade to an original unconfigured state prior to making any configuration changes, execute the following command: The LPAR information will now be cleared on the next system restart. Special SEA setup on POWER Blade serversInstall your VIO/IVM from DVD or NIM. Then follow these steps: $ license -accept $ mkgencfg -o init $ lsdev |grep ent You can get further information about the ethernet adapters by running this command for each one. Note: On a JS43 or PS702 blade server, i.e. a “double wide” blade, you’ll have 4 built-in adapters, i.e. the “lp-hea” Logical Host Ethernet (LHEA) ports shown above. So you’d see ent0,ent1,ent2,ent3 as LHEA ports and then you’d see ent4,ent5,ent6,ent7 as virtual I/O Ethernet adapters. In fact you might well want to setup NIB (network interface backup) link aggregation on the adapters in slots P1-T6 and 2-T6 in one LNAGG (likely to be ent0 and ent2 on your VIO server), and then the adapters in slots P1-T7 and P2-T7 in the other LNAGG. So those commands would like this: $ mkvdev -lnagg ent0 -attr backup_adapter=ent2 Note: On any POWER rack-mount server (i.e. not a blade server with special attributes around the network adapters and switch modules and wiring inside the chassis) you could run this command to create a 2-adapter link aggregation and assign a third adapter as a backup adapter. To list the current ethernet adapter info like PCI slot used, default vlan, additional vlans, ieee virtual adapter (i.e. bridged), trunking info, MAC address, etc. then enter this command (my values shown are tweaked to look generic). This is important because if you want to use vlan 1,2,3 or 4 you must use the corresponding virtual adapter that has already been created. I haven’t found a way to change the default vlan ID or add additional vlan ID’s once this virtual adapter has been created. This is a painful issue if you need to add/change/delete vlans very often. If you do, currently the only option I know of is to delete the SEA adapter, delete the virtual ethernet adapter and then recreate it with the desired vlans (default and additional). So if you want to use vlan 2, use what is ent3 below, the 2nd virtual adapter: $ chhwres -r virtualio --rsubtype eth -o a --id 1 -s 10 -a port_vlan_id=9,ieee_virtual_eth=1,\"addl_vlan_ids=50,63\",is_trunk=1,trunk_priority=1 (this makes a new adapter ent6, but it doesn't tell you that) $ mkvdev -sea ent0 -vadapter ent3 -default ent3 -defaultid 2 (we use ent3 because we want to use vlan2, see notes above) $ mkvdev -sea ent1 -vadapter ent6 -default ent6 -defaultid 9 $ mkvdev -vlan ent8 -tagid 50 $ mktcpip -hostname testvio1 -inetaddr 10.100.100.125 -interface en7 -start -netmask 255.255.255.0 -gateway 10.100.100.1 -nsrvaddr 10.100.100.1 -nsrvdomain test99.xyz.org Not sure what this command to create a new vSCSI adapter is needed for at this time (came from another admin’s notes). You’d use your system drawer, model, serial number information (i.e. full location code preamble) below. You may have to run this as root (oem_setup_env). Abbreviated procedure including initial AMM commands for JS43 and PS702 double wide POWER blade servers. telnetcfg -t 0 -T system:mm[1] AIX Stuff
Using USB drives in AIXUsing USB flash drive in AIX 5.3.9 USB Flash Drive Information Requires AIX 5.3 TL9 Supports USB 2.0 devices, but only capable of USB 1.1 speeds. Write speeds are roughly .25 MB/s or 1 MB every 4 seconds. Currently can not boot from flash drives (firmware support to be added at a later date) and you cannot use a flash drive in AIX for Volume Groups, Logical Volumes, JFS or JFS2 filesystems. You can, however, use it like a CDROM filesystem (CDRFS). After insertion of flash drive into USB port, run # cfgmgr -l usb0. Device shows up in lsdev as flashdrive0. This also creates device special files /dev/flashdrive0 and /dev/rflashdrive0. Can be read/written with backup/restore, tar, cpio, dd. Note: Destroys any previous Windows formatting if any existed (FAT32, NTFS, etc.) Also, you will not be able read the contents of the flash drive on a Windows system once you have written to it from an AIX system. Example using "tar": # tar cvf /dev/flashdrive0 /tmp/myfile Example using "cpio": # find /tmp/myfile | cpio -ov > /dev/flashdrive0 (write) # cpio -itv < /dev/flashdrive0 (view or list) # cpio -iv < /dev/flashdrive0 (read or restore) ISO file system (created by mkisofs) is written to flashdrive with dd command, # dd if=myimage.iso of=/dev/flashdrive0 ISO file system can be mounted with # mount -rv cdrfs /dev/flashdrive0 /mnt
Example iso file system creation and backup to USB drive: # mkisofs -o /tmp/myimage.iso -J -R -U /myfs # dd if=myimage.iso of=/dev/flashdrive0 # mount -rv cdrfs /dev/flashdrive0 /mnt # ls -l /mnt (to view contents of /myfs)
Supported devices: Lenovo 2GB Essential Memory Key Kingston 4GB Data Traveller SanDisk 4GB Cruzer Warning: I had some issues using tar and the SanDisk 4GB. Cpio works better. Configuring NTP time synchronization on AIXThe following information outlines the steps necessary to configure a basic NTP setup between an NTP client and server on AIX 5L. On server
# lssrc -ls xntpd NOTE:Sys peer should show a valid server or 127.127.1.0. If the server is "insane", you will need to correct it by adding a server line to /etc/ntp.conf and restarting xntpd. This can be done by following these steps: # vi /etc/ntp.conf Add: # stopsrc -s xntpd # startsrc -s xntpd NOTE: If the server runs databases, use the -x flag to prevent the clock from changing in a negative direction. Enter the following: # startsrc -s xntpd -a "-x"
On client
# ntpdate -d ip.address.of.server The offset must be less than 1000 seconds for xntpd to synch. If the offset is greater than 1000 seconds, change the time manually on the client and run the ntpdate -d again. If you get the message, "no server suitable for synchronization found", verify xntpd is running on the server (see above) and that no firewalls are blocking port 123.
# vi /etc/ntp.conf (Comment out the "broadcastclient" line and add server ip.address.of.server prefer.) Leave the driftfile and tracefile at their defaults.
# startsrc -s xntpd (Use the -x flag if it is appropriate for your environment.)
# vi /etc/rc.tcpip Uncomment the following line: start /usr/sbin/xntpd "$src_running" If using the -x flag, add "-x" to the end of the line. You must include the quotes around the -x.
# lssrc -ls xntpd NOTE: Sys peer should display the IP address or name of your xntp server. This process may take up to 12 minutes. To delete all the devices allocated to an LPAR , i.e. reset all devices and start cleanTo delete all devices to prepare for reboot and rediscovery # devreset Answer “yes” and reboot the server immediately after with “shutdown -Fr” (if you dare!) or “no” if you lack confidence. (keywords for doc search: alt disk install config configuration reset clear devices ) To list all the PCI slots allocated to an LPAR# lsslot -c pci # lsslot -c pci -a
To dynamically reallocate an adapter1. Determine the PCI slot for the adapter using lsslot -c slot and get the "pciX' device name 2. Remove the device from AIX using rmdev -l pciX -R (-R to remove all the child to parent) 3. On HMC dynamically allocate the device to another 4. On the destination box, run 'cfgmgr' to configure the allocated device Mounting ISO images on AIXStarting with AIX 6.1 TL 4, AIX offers a new command to directly mount an ISO file. The loopmount command will mount any ISO image directly into the filesystem without the need to copy it into a raw LV as before. The command requires a new fileset: devices.loopback.rte 6.1.4.0. When the fileset is installed, the loopmount command is able to perform the mount of any ISO file residing in your filesystem: Example: # loopmount -i POWERHA_Std_Edition_6_1.ISO -o "-o ro -v cdrfs" /mnt Prior to the loopmount command, the only way of mounting ISO images on the AIX platform was to complete the following instructions: Obtain the size of the image. For example: # ls -al total 731594 drwxr-xr-x 2 root system 512 Aug 18 11:33 . drwxr-xr-x 6 root system 512 Aug 18 11:32 .. -rw-r--r-- 1 root system 374575104 Apr 29 02:59 fim_console_rios_aix_5.iso
Identify the nearest multiple of 128 MB that will provide enough space for the image. In the above example, the image is approximately 374 MB, so use 384 MB as an image size.
Make a logical volume of this size. Ensure that there is enough space on the physical volume. For example, hdisk0.
# mklv -y cdlv -s n -L /dev/cdlv rootvg 384M hdisk0
If the command fails, increase the volume size by a multiple of 128.
Use the dd command to create a pseudo-device. Ensure that the partition has enough space for the pseudo-device.
In the following example command, the pseudo-device is /dev/cdlv.
# dd if=/opt/software/iso/fim_console_rios_aix_5.iso of=/dev/cdlv
Note that this command may take a long time and will create two dd processes.
Mount the device like a CD-ROM in AIX. Ensure that the mount point exists.
# mount -v cdrfs -o ro /dev/cdlv /mnt/iso
Change directory into /mnt/iso.
Alternate description for Mounting ISO images on AIX
How to mount a ISO image on AIX V5.3The following instructions were cribbed from the Howto mount an ISO image in AIX UNIX
1. Create a logical volume which is large enough to hold the ISO image: 2. p520-sr4:/ # /usr/sbin/mklv -y testiso -t jfs rootvg 1 3. testiso 4. p520-sr4:/ # where:
Use the command lsvg rootvg
5. Define a read-only JFS filesystem on the logical volume: 6. p520-sr4:/ # /usr/sbin/crfs -v jfs -d testiso -m /testiso -An -pro -tn -a frag=4096 -a nbpi=4096 -a ag=8 7. Based on the parameters chosen, the new /testiso JFS file system 8. is limited to a maximum size of 134217728 (512 byte blocks) 9. 10.New File System size is 65536 11.p520-sr4:/ # where:
See here
12. Copy the contents of the ISO image to the logical volume: 13.p520-sr4:/ # /usr/bin/dd if=/tmp/bestprac.iso of=/dev/rtestiso bs=1m 14.0+1 records in. 15.0+1 records out. 16.p520-sr4:/ # where:
It may be necessary to use a block size (bs=1m) of less than a megabyte if the logical partition size is less than a megabyte. See here
17. Change the filesystem type to cdrfs: 18.p520-sr4:/ # chfs -a vfs=cdrfs /testiso 19.p520-sr4:/ #
20. Mount the filesystem: 21.p520-sr4:/ # /usr/sbin/mount /testiso 22.p520-sr4:/ # The filesystem contains the files which are in the ISO image file /tmp/bestprac.tar: p520-sr4:/ # cd /testiso p520-sr4:/testiso # ls bestprac.tar.gz p520-sr4:/testiso # 23. When the filesystem is no longer needed, unmount and remove it and then remove the testiso logical volume: 24.p520-sr4:/testiso # cd 25.p520-sr4:/ # /usr/sbin/umount /testiso 26.p520-sr4:/ # /usr/sbin/rmfs -ir /testiso 27.rmfs: Warning, all data contained on /testiso will be destroyed. 28.rmfs: Remove filesystem: /testiso? y(es) n(o)? y 29.p520-sr4:/ # /usr/sbin/rmlv testiso 30.Warning, all data contained on logical volume testiso will be destroyed. 31.rmlv: Do you wish to continue? y(es) n(o)? y 32.rmlv: Logical volume testiso is removed. 33.p520-sr4:/ # where:
Notes:
To Help speed up AIX filesystem mounts The AIX mount command has a "noatime" option. This avoids the need to update access times on files and can give you a considerable performance boost if you have lots of files being accessed. To mount Linux NFS shares (servers) on AIX systems (clients)root@cmtecanim1 on pts/0[/]# nfso -o nfs_use_reserved_ports=1 Setting nfs_use_reserved_ports to 1 root@cmtecanim1 on pts/0[/]# mount cmtecsamba10:/share/cmtec /mnt/cmtec <success!> Mounting w/Filesys Logging Disabled
# mount –o log=NULL
DISABLES metadata logging. Performance gains are very significant. NOT a general purpose feature/option.
Working with Fibre Channel adapters and SAN storage
To make changes from AL (Arbitrated Loop, which is when you’re directly attached to the SAN Controller) to Pt2Pt (Point-to-Point, when you’re attached to a SAN switch), you must first remove all child devices of fcs0, fcs1, …. Etc.
# rmdev –dl fcnet0 # rmdev –dl fc0 # rmdev –dl fscsi0 # chdev –l fcs0 –a init_link=pt2pt
Or to set it back to Arbitrated Loop # chdev –l fcs0 –a init_link=al
As you know, AIX® has a vast array of commands that enable you to do a multitude of tasks. Depending on what you need to accomplish, you use only a certain subset of these commands. These subsets differ from user to user and from need to need. However, there are a few core commands that you commonly use. You need these commands either to answer your own questions or to provide answers to the queries of the support professionals. In this article, I'll discuss some of these core commands. The intent is to provide a list that you can use as a ready reference. While the behavior of these commands should be identical in all releases of AIX, they have been only tested under AIX 5.3. Note:
How would I know if I am running a 32-bit kernel or 64-bit kernel?To display if the kernel is 32-bit enabled or 64-bit enabled, type:
How do I know if I am running a uniprocessor kernel or a multiprocessor kernel?/unix is a symbolic link to the booted kernel. To find out what kernel mode is running, enter ls -l /unix and see what file /unix it links to. The following are the three possible outputs from the ls -l /unix command and their corresponding kernels:
Note: How can I change from one kernel mode to another?During the installation process, one of the kernels, appropriate for the AIX version and the hardware in operation, is enabled by default. Let us use the method from the previous question and assume the 32-bit kernel is enabled. Let us also assume that you want to boot it up in the 64-bit kernel mode. This can be done by executing the following commands in sequence:
The /dev/hdiskxx directory is where the boot logical volume /dev/hd5 is located. To find out what xx is in hdiskxx, run the following command:
Note: How would I know if my machine is capable of running AIX 5L Version 5.3?AIX 5L Version 5.3 runs on all currently supported CHRP (Common Hardware Reference Platform)-based POWER hardware. How would I know if my machine is CHRP-based?Run the prtconf command. If it's a CHRP machine, the string chrp appears on the Model Architecture line. How would I know if my System p machine (hardware) is 32-bit or 64-bit?To display if the hardware is 32-bit or 64-bit, type:
How much real memory does my machine have?To display real memory in kilobytes (KB), type one of the following:
How big are my disks, even fibre channel LUNs?# bootinfo -s hdisk7 102400 This means you have a 100G LUN. Can my machine run the 64-bit kernel?64-bit hardware is required to run the 64-bit kernel. What are the values of attributes for devices in my system?To list the current values of the attributes for the tape device, rmt0, type:
To list the default values of the attributes for the tape device, rmt0, type:
To list the possible values of the login attribute for the TTY device, tty0, type:
To display system level attributes, type:
How many processors does my system have?To display the number of processors on your system, type:
How many hard disks does my system have and which ones are in use?To display the number of hard disks on your system, type:
How do I list information about a specific physical volume?To find details about hdisk1, for example, run the following command:
How do I get a detailed configuration of my system?Type the following:
The following options provide specific information:
For example, to display details about the tape drive, rmt0, type:
You can obtain very similar information by running the prtconf command. How do I find out the chip type, system name, node name, model number, and so forth?The uname command provides details about your system.
What version, release, and maintenance level of AIX is running on my system?Type one of the following:
How can I determine which fileset updates are missing from a particular AIX level?To determine which fileset updates are missing from 5300-04, for example, run the following command:
What SP (Service Pack) is installed on my system?To see which SP is currently installed on the system, run the oslevel -s command. Sample output for an AIX 5L Version 5.3 system, with TL4, and SP2 installed would be:
Is a CSP (Concluding Service Pack) installed on my system?To see if a CSP is currently installed on the system, run the oslevel -s command. Sample output for an AIX 5L Version 5.3 system, with TL3, and CSP installed would be:
How do I create a file system?The following command will create, within volume group testvg, a jfs file system of 10MB with mounting point /fs1:
The following command will create, within volume group testvg, a jfs2 file system of 10MB with mounting point /fs2 and having read only permissions:
How do I change the size of a file system?To increase the /usr file system size by 1000000 512-byte blocks, type:
Note: How do I mount a CD?Type the following:
How do I mount a file system?The following command will mount file system /dev/fslv02 on the /test directory:
How do I mount all default file systems (all standard file systems in the /etc/filesystems file marked by the mount=true attribute)?The following command will mount all such file systems:
How do I unmount a file system?Type the following command to unmount /test file system:
How do I display mounted file systems?Type the following command to display information about all currently mounted file systems:
How do I remove a file system?Type the following command to remove the /test file system:
How can I defragment a file system?The defragfs command can be used to improve or report the status of contiguous space within a file system. For example, to defragment the file system /home, use the following command:
Which fileset contains a particular binary?To show bos.acct contains /usr/bin/vmstat, type:
Or to show bos.perf.tools contains /usr/bin/svmon, type:
How do I display information about installed filesets on my system?Type the following:
How do I determine if all filesets of maintenance levels are installed on my system?Type the following:
How do I determine if a fix is installed on my system?To determine if IY24043 is installed, type:
How do I install an individual fix by APAR?To install APAR IY73748 from /dev/cd0, for example, enter the command:
How do I verify if filesets have required prerequisites and are completely installed?To show which filesets need to be installed or corrected, type:
How do I get a dump of the header of the loader section and the symbol entries in symbolic representation?Type the following:
How do I determine the amount of paging space allocated and in use?Type the following:
How do I increase a paging space?You can use the chps -s command to dynamically increase the size of a paging space. For example, if you want to increase the size of hd6 with 3 logical partitions, you issue the following command:
How do I reduce a paging space?You can use the chps -d command to dynamically reduce the size of a paging space. For example, if you want to decrease the size of hd6 with four logical partitions, you issue the following command:
How would I know if my system is capable of using Simultaneous Multi-threading (SMT)?Your system is capable of SMT if it's a POWER5-based system running AIX 5L Version 5.3. How would I know if SMT is enabled for my system?If you run the smtctl command without any options, it tells you if it's enabled or not. Is SMT supported for the 32-bit kernel?Yes, SMT is supported for both 32-bit and 64-bit kernel. How do I enable or disable SMT?You can enable or disable SMT by running the smtctl command. The following is the syntax:
The following options are available:
If neither the -w boot or the -w now options are specified, then the mode change is made immediately. It persists across subsequent reboots if you run the bosboot command before the next system reboot. How do I get partition-specific information and statistics?The lparstat command provides a report of partition information and utilization statistics. This command also provides a display of Hypervisor information. Volume groups and logical volumes How do I know if my volume group is normal, big, or scalable?Run the lsvg command on the volume group and look at the value for MAX PVs. The value is 32 for normal, 128 for big, and 1024 for scalable volume group. How to create a volume group?Use the following command, where spartition_size sets the number of megabytes (MB) in each physical partition where the partition_size is expressed in units of MB from 1 through 1024. (It's 1 through 131072 for AIX 5.3.) The partition_size variable must be equal to a power of 2 (for example: 1, 2, 4, 8). The default value for standard and big volume groups is the lowest value to remain within the limitation of 1016 physical partitions per physical volume. The default value for scalable volume groups is the lowest value to accommodate 2040 physical partitions per physical volume.
How can I change the characteristics of a volume group?You use the following command to change the characteristics of a volume group:
How do I create a logical volume?Type the following:
How do I increase the size of a logical volume?To increase the size of the logical volume represented by the lv05 directory by three logical partitions, for example, type:
How do I display all logical volumes that are part of a volume group (for example, rootvg)?You can display all logical volumes that are part of rootvg by typing the following command:
How do I list information about logical volumes?Run the following command to display information about the logical volume lv1:
How do I remove a logical volume?You can remove the logical volume lv7 by running the following command:
The rmlv command removes only the logical volume, but does not remove other entities, such as file systems or paging spaces that were using the logical volume. How do I mirror a logical volume?
How do I remove a copy of a logical volume?You can use the rmlvcopy command to remove copies of logical partitions of a logical volume. To reduce the number of copies of each logical partition belonging to logical volume testlv, enter:
Each logical partition in the logical volume now has at most two physical partitions. Queries about volume groupsTo show volume groups in the system, type:
To show all the characteristics of rootvg, type:
To show disks used by rootvg, type:
How to add a disk to a volume group?Type the following:
How do I find out what the maximum supported logical track group (LTG) size of my hard disk?You can use the lquerypv command with the -M flag. The output gives the LTG size in KB. For instance, the LTG size for hdisk0 in the following example is 256 KB.
You can also run the lspv command on the hard disk and look at the value for MAX REQUEST. What does syncvg command do?The syncvg command is used to synchronize stale physical partitions. It accepts names of logical volumes, physical volumes, or volume groups as parameters. For example, to synchronize the physical partitions located on physical volumes hdisk6 and hdisk7, use:
To synchronize all physical partitions from volume group testvg, use:
How do I replace a disk?
How can I clone (make a copy of ) the rootvg?You can run the alt_disk_copy command to copy the current rootvg to an alternate disk. The following example shows how to clone the rootvg to hdisk1.
How can I display or set values for network parameters?The no command sets or displays current or next boot values for network tuning parameters. How do I get the IP address of my machine?Type one of the following:
For example, type host cyclop.austin.ibm.com. How do I identify the network interfaces on my server?Either of the following two commands will display the network interfaces:
To get information about one specific network interface, for example, tr0, run the command:
How do I activate a network interface?To activate the network interface tr0, run the command:
How do I deactivate a network interface?For example, to deactivate the network interface tr0, run the command:
Working with AIO in AIXNotes on installing, verifying installation of, and setting up AIO (Asynchronous I/O) in AIX. The first thing to check is the necessary fileset. This is part of the base install, so it should be there: To make use of AIO the following fileset must be installed: bos.rte.aio To determine if this fileset is installed, enter: # lslpp -l bos.rte.aio
Presuming the fileset is installed, the notes I have say to do the following to configure AIO: Enable asynchronous IO Execute the following commands to enable asynchronous I/O: chdev -l aio0 -P -a autoconfig='available' mkdev -l aio0 lsdev -F status -t aio
lsdev -F status -t aio must return the following: Available
On the SMIT side, I think it's "# smit aio". In your note, you have "#smit aio0" (w/ the trailing zero).
You can tell how many AIO servers you have running using: To determine how many POSIX AIO Servers are currently running, type the following information on the command line: # pstat -a | grep posix_aioserver | wc -l To determine how many LEGACY AIO Servers are currently running, type the following information on the command line: # pstat -a | egrep ' aioserver' | wc -l
You can then monitor AIO (for example) using # iostat -A 1 5 The following list is a description of parameters used to monitor the AIO subsystem.
* avfc: This reports back the average fastpath request count per second for your interval. * avgc: This reports back the average global asynchronous I/O request per second of the interval you specified. * maxgc: This reports back the max global asynchronous I/O request since the last time this value was fetched. * maxfc: This reports back the maximum fastpath request count since the last time this value was fetched. * maxreqs: This is the maximum asynchronous I/O requests allowed.
NIM Server Stuff0042-008 NIMState: Request Deniedy0042-008 NIMState: Request denied method_req - These messages appear during client install when the cpuid (uname -m) of the client machine does not match the cpuid that the nim master "remembers" for this client. "lsnim -l machine | grep cpuid" on the nim master will show what uname the master retains for this client. You can change the uname value on the nim master to match the new client machine, "nim -o change -a cpuid=<newvalue> client"
Debugging NIM network connections1. On the NIM server, change bootpd's arguments to "-d -d -d" on /etc/inetd.conf. So you go from this default entry bootps dgram udp wait root /usr/sbin/bootpd bootpd /etc/bootptab to this entry bootps dgram udp wait root /usr/sbin/bootpd –d –d –d bootpd /etc/bootptab 2. # refresh -s inetd 3. in /etc/syslog.conf add "*.info /dev/console" 4. # refresh -s syslogd 5. # swcons `tty` 6. check for the bootptab messages 7. check MAC addresses. To put things back the way they were, or to “normal” 1. # swcons 2. Put entry in /etc/inetd.conf back to default 3. Put /etc/syslog.conf back to default
VIO Server StuffWorking with Virtual Opticalusing virtual optical drives in VIOS (IBM virtual I/O server), also known as: using an iso-file as virtual cd-rom for your LPAR
This requires at least VIOS 1.5.
1. first, create a logical volume in which you want the iso-files to be stored: a. mkrep -sp rootvg -size 20G b. instead of rootvg you can also use a different volume group 2. the created logical volume is mounted under /var/vio/VMLibrary a. copy your iso-files to this location or use 3. create a virtual optical drive connected to virtual scsi adapter vhost4 (the virtual scsi host for the LPAR to which you want to connect the new virtual optical drive): 4. connect an iso-file to your virtual optical drive (for example the 'vtopt0' you created with the mkvdev command in the previous step) 5. disconnect the iso-file (as if you were unloading a cd from the drive): How to install AIX from a Virtual Optical Device1. IntroductionIOS version 1.5 introduced virtual optical drives. This small article shows how to make use of this feature when installing an LPAR. This might be handy if you want to upgrade a NIM server without the need to spend a day in the datacenter or when there is no CD drive available to assign to an LPAR. 2. Getting the ISO ImageBefore we can start creating our virtual optical device we need an ISO image. Sometimes ISO images can be found on the web - in this case you can simply download the image and copy it to some space on your VIO server. But we want to install from an AIX installation DVD - the AIX 6.1 installation ISO of course cannot be found on the web - so we have to create an ISO image from our physical AIX installation CD or DVD. There are multiple ways to create ISO images. The easiest way to create an ISO image from the AIX Installation CD or DVD is to insert it in the DVD drive of a Linux box and just dump the CD/DVD to a file: linux# cat /dev/cdrom > aix61inst.iso This creates a file that can be used for the virtual optical device on the VIO server. The below examples assume that this is copied to /tmp on the VIO server.
3. Creating a DVD RepositoryWith the command lsrep we check if there is already a repository on our VIO server: padmin$ lsrep The DVD repository has not been created yet. As we see, this is not the case. Let's check available storage pools then: padmin$ lssp Pool Size(mb) Free(mb) Alloc Size(mb) BDs Type rootvg 139776 86016 128 0 LVPOOL The above output shows about 85 GB free space in the default storage pool - that should be sufficient. So we can go on creating a repository. The below command creates a repository of 8GB - enough for two DVDs: padmin$ mkrep -sp rootvg -size 8G Virtual Media Repository Created Repository created within "VMLibrary_LV" logical volume padmin$ lsrep Size(mb) Free(mb) Parent Pool Parent Size Parent Free 8158 8158 rootvg 139776 77824 4. Creating the Virtual Optical DeviceNow we are ready to load our AIX 6.1 ISO image into the repository: padmin$ mkvopt -name aix_61 -file /tmp/aix61inst.iso We check with lsrep: padmin$ lsrep Size(mb) Free(mb) Parent Pool Parent Size Parent Free 8159 951 rootvg 139776 77824 Name File Size Optical Access aix_61 3679 None rw At this point we don't need the original ISO image in /tmp anymore... padmin$ rm -f /tmp/aix61inst.iso To use the AIX CD for installing an LPAR we need to connect a virtual optical device to the virtual SCSI hostadapter (vhost3 here) of the LPAR: padmin$ mkvdev -fbo -vadapter vhost3 vtopt0 Available Now we are ready to load the AIX 6.1 DVD into the virtual drive ... padmin$ loadopt -disk aix_61 -vtd vtopt0 Checking ... padmin$ lsmap -vadapter vhost3 SVSA Physloc Client Partition ID --------------- -------------------------------------------- ------------------ vhost3 U9117.MMA.F54DD01-V3-C103 0x00000000 VTD vtopt0 Status Available LUN 0x8300000000000000 Backing device /var/vio/VMLibrary/aix_61 Physloc VTD vtscsi4 Status Available LUN 0x8100000000000000 Backing device hdisk8 Physloc U7314.G30.110FFBA-P1-C2-T1-L59 VTD vtscsi5 Status Available LUN 0x8200000000000000 Backing device hdisk9 Physloc U7314.G30.110FFBA-P1-C2-T1-L60 5. Installing an LPAR from the Virtual DVDStarting up the LPAR and entering the SMS menu we see our virtual device as a regular SCSI CD-ROM: Version EM320_076 SMS 1.7 Copyright IBM Corp. 2000,2008 All rights reserved. ------------------------------------------------------------------------------- Select Device Device Current Device Number Position Name 1. 3 Interpartition Logical LAN ( loc=U9117.MMA.F54DD01-V13-C20-T1 ) 2. - Interpartition Logical LAN ( loc=U9117.MMA.F54DD01-V13-C25-T1 ) 3. - Interpartition Logical LAN ( loc=U9117.MMA.F54DD01-V13-C30-T1 ) 4. - Interpartition Logical LAN ( loc=U9117.MMA.F54DD01-V13-C35-T1 ) 5. - SCSI CD-ROM ( loc=U9117.MMA.F54DD01-V13-C103-T1-W8300000000000000-L0 ) ------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services ------------------------------------------------------------------------------- We select the SCSI CD-ROM and start up the installation as usual.
6. Cleaning upAfter AIX is installed we can unload the AIX DVD from the virtual drive: padmin$ unloadopt -release -vtd vtopt0 To see attributes of SEA adapter$ lsdev –dev ent0 -attr To make VIO Server and then VIO clients1. Define VIOS LPAR with enough virtual Ethernet and virtual SCSI adapters for disks, cdrom, etc. 2. Install VIO server 3. Setup SEA adapters 4. Install OpenSSL and OpenSSH 5. Configure TCP/IP on the SEA adapter(s) 6. Create LV for VIO client a. # mklv –lv vioc1_rootvg
To make SEA adapters with failoverCreate SEA on VIO server 1 with failover attribute: $ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1 -attr ha_mode=auto ctl_chan=ent3 (OPTIONAL) Assign an ip address to SEA on VIOS1: $ mktcpip -hostname vio1 -interface en4 -inetaddr 9.3.5.136 -netmask 255.255.255.0 -gateway 9.3.5.41 -nsrvaddr 9.3.4.2 -nsrvdomain itsc.austin.ibm.com -start To make and remove physical or logical backing device virtual devicesTo make the device mapping # mkvdev -vdev hdisk8 -vadapter vhost5
To remove a # rmdev -dev vhost5 -recursive tsmdb_vg deleted tsmdisk1_vg deleted tsmdisk2_vg deleted vhost5 deleted
To remove a backing device mapping from a vhost adapter # rmvdev -vdev hdisk8
Then remove the device altogether # rmdev -pdev hdisk8
Working with virtual media in VIOS$ lsvopt To load a new image to the virtual DVD drive, using the –f to basically say “remove the existing one anyway, if any, and load this new image” $ loadopt -f -disk aix530009011 -vtd vtopt0 $ rmopt -vtd vtopt0
Manually Creating VIOS NIM ResourcesAfter having many problems attempting to use installios, the following steps were used to build the necessary NIM resources to allow the installation of IBM's Virtual I/O Server:
First, define shell variables pointing to the mounted CD or copied CD contents, and the destination for the NIM objects: # SRC=/junk/vios-1.2-cd # DST=/csminstall/eznim/vios-1.2
Define NIM client. Substitute appropriate client name, ethernet hardware address, interface name, cable type, subnet mask, client gateway and speed/duplex: # nim -o define -t standalone -a if1="find_net CLIENTNAME 000a0b0c0d0e ent1" \ > -a cable_type1=N/A \ > -a netboot_kernel=mp -a net_definition="ent 255.255.255.0 192.168.0.1" \ > -a net_settings1="100 half" CLIENTNAME
Define NIM mksysb: # mkdir ${DST}/mksysb # cp ${SRC}/nimol/ioserver_res/mksysb ${DST}/mksysb/installios_mksysb # nim -o define -t mksysb -a server=master -a location=${DST}/mksysb/installios_mksysb \ > installios_mksysb
Define NIM bundle: # mkdir ${DST}/bundle # cp ${SRC}/installp/ppc/en_US.bnd ${DST}/bundle # nim -o define -t installp_bundle -a server=master -a location=${DST}/bundle/en_US.bnd \ > installios_bundle
Define NIM lppsource: # mkdir ${DST}/lpp_source # gencopy -X -d ${SRC}/installp/ppc -t ${DST}/lpp_source/installios_lpp_source \ > $(/usr/bin/cat ${DST}/bundle/en_US.bnd) # nim -o define -t lpp_source -a server=master \ > -a location=${DST}/lpp_source/installios_lpp_source \ > -a source=${DST}/lpp_source/installios_lpp_source installios_lpp_source Preparing to copy install images (this will take several minutes)...
0503-114 gencopy: RPM Product cdrecord* does not exist. 0503-114 gencopy: RPM Product mkisofs* does not exist.
Now checking for missing install images... warning: 0042-265 c_mk_lpp_source: The image source "/csminstall/eznim/vios-1.2/lpp_source/installios_lpp_source" that was used to define the lpp_source is missing one or more of the following from the list of default packages: bos.64bit bos bos.acct ... warning: 0042-267 c_mk_lpp_source: The defined lpp_source does not have the "simages" attribute because one or more of the following packages are missing: bos bos.net bos.diag ...
Define NIM VIOS SPOT resource: # mkdir ${DST}/spot # nim -o define -t spot -a location=${DST}/spot -a server=master \ > -a source=installios_mksysb installios_spot
Creating SPOT in "/csminstall/eznim/vios-1.2/spot" on machine "master" from "installios_mksysb" ...
Restoring files from BOS image. This may take several minutes ...
Checking filesets and network boot images for SPOT "installios_spot". This may take several minutes ...
Define NIM bosinst: # cp ${SRC}/nimol/ioserver_res/bosinst.data ${DST}/installios_bosinst.data # nim -o define -t bosinst_data -a server=master -a location=${DST}/installios_bosinst.data \ > installios_bosinst
Configure NIM ready for client install: # nim -o bos_inst -a source=mksysb -a spot=installios_spot -a mksysb=installios_mksysb \ > -a bosinst_data=installios_bosinst -a boot_client=no CLIENTNAME warning: 0042-360 m_bos_inst: The SPOT level is older than the mksysb level. Therefore, the BOS installation may encounter problems. Update the SPOT to match the mksysb level or create a new SPOT that has the same level.
Now, the LPAR may be net booted via any method (eg. SMS via HMC).
Working with network devices$ mkvdev -sea ent2 -vadapter ent4 -default ent4 -defaultid 1 ent12 available et12 en12 $ mkvdev -sea ent3 -vadapter ent5 -default ent5 -defaultid 1
$ rmtcpip -interface en3 Working with MPIO in VIOS and Vio Clientsfscsi devices on VIOS · dyntrk=yes · fc_err_recov=fast_fail
hdisk devices on VIOS · algorithm=load_balance · reserve_policy=no_reserve · hcheck_mode=nonactive · hcheck_interval=20
vscsi devices in client · vscsi_path_to=30
hdisk devices in client · algorithm=failover · reserve_policy=no_reserve · hcheck_mode=nonactive · hcheck_interval=20
On VIOS $ chdev -dev fscsi0 -attr fc_err_recov=fast_fail dyntrk=yes -perm fscsi0 changed $ chdev -dev hdisk9 -attr reserve_policy=no_reserve hdisk9 changed $ chdev -dev hdisk9 -attr algorithm=round_robin hdisk9 changed $ chdev -dev hdisk9 -attr hcheck_interval=20 hdisk9 changed $ chdev –dev hdisk9 –attr hcheck_mode=nonactive hdisk9 changed
or in a couple lines
chdev -dev fscsi0 -attr fc_err_recov=fast_fail dyntrk=yes -perm chdev -dev fscsi1 -attr fc_err_recov=fast_fail dyntrk=yes -perm
chdev -dev hdisk5 -attr reserve_policy=no_reserve algorithm=round_robin hcheck_interval=20 hcheck_mode=nonactive chdev -dev hdisk6 -attr reserve_policy=no_reserve algorithm=round_robin hcheck_interval=20 hcheck_mode=nonactive
$ lsdev -dev hdisk9 -attr attribute value description user_settable
PCM PCM/friend/scsiscsd Path Control Module False algorithm round_robin Algorithm True dist_err_pcnt 0 Distributed Error Percentage True dist_tw_width 50 Distributed Error Sample Time True hcheck_interval 0 Health Check Interval True hcheck_mode nonactive Health Check Mode True max_transfer 0x40000 Maximum TRANSFER Size True pvid 0021768a0151feb40000000000000000 Physical volume identifier False queue_depth 3 Queue DEPTH False reserve_policy no_reserve Reserve Policy True size_in_mb 18200 Size in Megabytes False
On VIO Client $ chdev -l hdisk0 -a hcheck_interval=20 -a hcheck_mode=nonactive -P
to only look for SCSI devices on channel scsi0 # cfgmgr -l scsi0 To only look for devices on fibre channel SCSI 0 # cfgmgr -l fcs0 IVE, HEA, LHEA and VIOSUsing LHEA devices on VIOS To use the HEA or IVE Ethernet adapters built into all modern Power6 and Power7 systems for the VIOS SEA port(s), do the following. 1. Create your VIOS LPAR, but don’t worry about LHEA yet. 2. After creating theVIOS LPAR, set the server attributes for the HEA/LHEA to have the ports as promiscuous and assign it to the VIOS LPAR. This dedicates the port to that LPAR. You can’t assign other LHEA ports based on that physical port to any other LPARs. If you have 2 or 4 LHEA ports you want to assign to the VIOS to do link aggregration, then do this same setting on all LHEA ports. 3. Now go back to VIOS and create a single virtual Ethernet adapter in slot 11. Set it to the following: a. Adapter ID = 11 b. VLAN ID = 1 c. It’s of debate whether to set this adapter to required, so I leave it up to you. If you make it required you can’t remove it dynamically using DLPAR. d. Set IEEE 802.1q compatible adapter = CHECK, and add all the VLANs you know you want like 1, 16,17,18, 262, 99, 999, 399, etc., whatever. But you can only have 20 total VLANs here, so use them sparingly. e. Set “Access external network” = CHECK 4. Assume you have the following Ethernet adapters showing up in your VIOS with 2 LHEA ports assigned. $ lsdev | grep ent ent0 Available Logical Host Ethernet Port (lp-hea) ent1 Available Logical Host Ethernet Port (lp-hea) ent2 Available Virtual I/O Ethernet Adapter (l-lan) 5. On VIOS, run this command to create the link aggregated (etherchanneled, trunked, bonded) Ethernet adapter $ mkvdev –lnagg ent0 ent1 (or “mkvdev –lnagg ent0 ent1 ent2 ent3” if you have 4 ports) This will make a new Ethernet adapter and interfaces like ent3. 6. Now create the shared Ethernet adapter (SEA) on the VIOS $ mkvdev –sea ent3 –vadapter ent2 –default ent2 –defaultid 1 This will make a new Ethernet adapter and interfaces like ent4. 7. You can list your Ethernet adapters again and should see this: $ lsdev | grep ent ent0 Available Logical Host Ethernet Port (lp-hea) ent1 Available Logical Host Ethernet Port (lp-hea) ent2 Available Virtual I/O Ethernet Adapter (l-lan) ent3 Available EtherChannel / IEEE 802.3ad Link Aggregation ent4 Available Shared Ethernet Adapter 8. Now you must create a new adapter for each VLAN the VIOS is going to have an actual IP address assigned on itself. Use this command: $ mkvdev –vlan ent4 –tagid 16 ent5 Available en5 et5 $ mkvdev –vlan ent4 –tagid 262 ent6 Available en6 et6 9. You can list your Ethernet adapters again and should see this: $ lsdev | grep ent ent0 Available Logical Host Ethernet Port (lp-hea) ent1 Available Logical Host Ethernet Port (lp-hea) ent2 Available EtherChannel / IEEE 802.3ad Link Aggregation ent3 Available Shared Ethernet Adapter ent4 Available Virtual I/O Ethernet Adapter (l-lan) ent5 Available VLAN ent6 Available VLAN 10.Now you can assign IP addresses. $ mktcpip –hostname cmtecvios9 –inetaddr 10.75.16.234 –interface en5 –netmask 255.255.255.0 –gateway 10.75.16.1 For the other network interfaces I find it easier to go into the “oem_setup_env” to get root, then do “smitty tcpip” and go to further configuration to set the IP address on the subsequent interfaces. The reason for this is that the mktcpip command as the padmin account *REQUIRES* you to put the hostname, and so every time you set an IP address it wants to set the hostname.
HMC StuffHMC networkingIn p59x servers, each HMC port is connected to an internal Ethernet hub, which is in turn connected to Flexible Service Processors and Bulk Power Controllers
Configuring a switch port for 100 Mbps full duplex can create a duplex mismatch, according to Cisco's Troubleshooting Cisco Catalyst Switches to NIC Compatibility Issues
If SCAN_ERROR_CHRP errors are found in AIX errpt
To list All the managed systems attached to the HMC and some information about them
$ lssyscfg -r sys name=Server-9119-595-SN02898EB,type_model=9119-595,serial_num=02898EB,ipaddr=10.128.253 ndary=10.128.255.252,state=Operating,sys_time=10/13/2006 20:15:55,power_off_policy=1,co cod_proc_capable=1,hca_capable=1,huge_page_mem_capable=unavailable,micro_lpar_capable=1 ,5250_application_capable=0,redundant_err_path_reporting_capable=1,shared_eth_failover g_passing_capable=1,sp_failover_capable=1,vet_activation_capable=1,virtual_io_server_c 250_cpw_percent=0,max_lpars=254,max_power_ctrl_lpars=1,service_lpar_id=3,service_lpar_n ............................... ............................... ,pend_mfg_default_boot_mode=norm,sp_failover_enabled=1,sp_failover_state=Ready To list only name, Serial number, IP address and state alone,
$ lssyscfg -r sys -F name,type_model,serial_num,ipaddr,state --header name,type_model,serial_num,ipaddr,state Server-9119-595-SN02898EB,9119-595,02898EB,10.128.253.255,Operating Server-9119-595-SN02898BB,9119-595,02898BB,10.128.255.250,Operating To list all the Lpar in the managed system $ lssyscfg -r lpar -m Server-9119-595-SN02898EB lssyscfg -r lpar -m Server-9119-595-SN02898EB name=eraprci0,lpar_id=8,lpar_env=aixlinux,state=Running,resource_config=1,os_version=0. 0.0.0.0.0,logical_serial_num=02898EB8,default_profile=eraprci0,curr_profile=eraprci0, work_group_id=none,shared_proc_pool_util_auth=0,power_ctrl_lpar_ids=none,boot_mode=norm, lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0
name=eraptci0,lpar_id=7,lpar_env=aixlinux,state=Running,resource_config=1,os_version=0. 0.0.0.0.0,logical_serial_num=02898EB7,default_profile=eraptci0,curr_profile=eraptci0, work_group_id=none,shared_proc_pool_util_auth=0,power_ctrl_lpar_ids=none,boot_mode=norm, lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0
name=erep2ci0,lpar_id=6,lpar_env=aixlinux,state=Running,resource_config=1,os_version=0. 0.0.0.0.0,logical_serial_num=02898EB6,default_profile=erep2ci0,curr_profile=erep2ci0, work_group_id=none,shared_proc_pool_util_auth=0,power_ctrl_lpar_ids=none,boot_mode=norm, lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0
For nicer output, look at this: ================================================================================================== Before: ================================================================================================== hscroot@CIBERHMC1:~> lshwres -m Server-9117-570-SN10B6E3E -r proc --level lpar lpar_name=Ceridian,lpar_id=3,curr_proc_mode=ded,curr_min_procs=1,curr_procs=2,curr_max_procs=2,curr_sharing_mode=share_idle_procs,pend_proc_mode=ded,pend_min_procs=1,pend_procs=2,pend_max_procs=2,pend_sharing_mode=share_idle_procs,run_procs=2 lpar_name=Lawson,lpar_id=2,curr_proc_mode=ded,curr_min_procs=1,curr_procs=2,curr_max_procs=2,curr_sharing_mode=share_idle_procs,pend_proc_mode=ded,pend_min_procs=1,pend_procs=2,pend_max_procs=2,pend_sharing_mode=share_idle_procs,run_procs=2 lpar_name=10-B6E3E,lpar_id=1,curr_proc_mode=ded,curr_min_procs=0,curr_procs=0,curr_max_procs=0,curr_sharing_mode=share_idle_procs,pend_proc_mode=ded,pend_min_procs=0,pend_procs=0,pend_max_procs=0,pend_sharing_mode=share_idle_procs,run_procs=0
================================================================================================== After: ================================================================================================== hscroot@CIBERHMC1:~> lshwres -m Server-9117-570-SN10B6E3E -r proc --level lpar | sed 's/,/\n/g' lpar_name=Ceridian lpar_id=3 curr_proc_mode=ded curr_min_procs=1 curr_procs=2 curr_max_procs=2 curr_sharing_mode=share_idle_procs pend_proc_mode=ded pend_min_procs=1 pend_procs=2 pend_max_procs=2 pend_sharing_mode=share_idle_procs run_procs=2 lpar_name=Lawson lpar_id=2 curr_proc_mode=ded curr_min_procs=1 curr_procs=2 curr_max_procs=2 curr_sharing_mode=share_idle_procs pend_proc_mode=ded pend_min_procs=1 pend_procs=2 pend_max_procs=2 pend_sharing_mode=share_idle_procs run_procs=2 lpar_name=10-B6E3E lpar_id=1 curr_proc_mode=ded curr_min_procs=0 curr_procs=0 curr_max_procs=0 curr_sharing_mode=share_idle_procs pend_proc_mode=ded pend_min_procs=0 pend_procs=0 pend_max_procs=0 pend_sharing_mode=share_idle_procs run_procs=0
$ lssyscfg -r lpar -m Server-9119-595-SN02898EB -Fname,curr_profile,state eraprci0,eraprci0,Running eraptci0,eraptci0,Running erep2ci0,erep2ci0,Running
Let's have a look at the installed HW resources in a system and please forgive me that I didn't show you all possible queries available. Just some nice ones. hscroot@hmc-op:~> lshwres -r mem -m op720-1-SN100486A --level sys configurable_sys_mem=8192,curr_avail_sys_mem=448,pend_avail_sys_mem=448, installed_sys_mem=8192,max_capacity_sys_mem=8192,deconfig_sys_mem=0, sys_firmware_mem=576,mem_region_size=32 hscroot@hmc-op:~> lshwres -m op720-1-SN100486A -r io --rsubtype slot -F description,unit_phys_loc,bus_id,phys_loc,lpar_id Universal Serial Bus UHC Spec,U787B.001.DNW1733,2,T7,none Other Mass Storage Controller,U787B.001.DNW1733,2,T16,none PCI Fibre Channel Disk Controller,U787B.001.DNW1733,2,C3,1 PCI RAID Disk Unit Controller,U787B.001.DNW1733,2,C4,2 PCI Fibre Channel Disk Controller,U787B.001.DNW1733,2,C5,2 PCI 10/100/1000Mbps Ethernet UTP 2-port,U787B.001.DNW1733,3,T9,1 PCI RAID Disk Unit Controller,U787B.001.DNW1733,3,T14,1 PCI 10/100/1000Mbps Ethernet UTP 2-port,U787B.001.DNW1733,3,C1,2 PCI 10/100/1000Mbps Ethernet UTP 2-port,U787B.001.DNW1733,3,C2,none hscroot@hmc-op:~> lshwres -m op720-1-SN100486A -r io --rsubtype slot -F description,drc_index,lpar_id Universal Serial Bus UHC Spec,21010002,none Other Mass Storage Controller,21020002,none PCI Fibre Channel Disk Controller,21030002,1 PCI RAID Disk Unit Controller,21040002,2 PCI Fibre Channel Disk Controller,21050002,2 PCI 10/100/1000Mbps Ethernet UTP 2-port,21010003,1 PCI RAID Disk Unit Controller,21020003,1 PCI 10/100/1000Mbps Ethernet UTP 2-port,21030003,2 PCI 10/100/1000Mbps Ethernet UTP 2-port,21040003,none
Find MAC address on LPAR Ethernet adapter from HMC
hscroot@hmc-op:~> lpar_netboot -M -n -t ent "linux_test" "normal" "op710-2-SN1008B2A" # Connecting to linux_test # Connected # Checking for power off. # Power off complete. # Power on linux_test to Open Firmware. # Power on complete. # Getting adapter location codes. # Type Location Code MAC Address ent U9123.710.1008B2A-V7-C4-T1 0a67e0007004
Now you can use the MAC address in your dhcpd.conf. IMPORTANT: By the way -n means "do not really boot the LPAR" which is very important as you probably don’t want to boot/reboot your LPAR every time you want to use this command.
Create LPAR using a SSH scriptNow this example is based on a little script. In fact I am using two files - one for the configuration values and one for the remote SSH command execution.
Here's my config file:
# ----- Config File for mksyscfg ----- USERID="hscroot" HMC='hmc-570.stuttgart.de.ibm.com' SYSTEM="Server-9110-510-SN100129A"
# ----- Client LPAR default values ----- CLIENT_NAME="linux_test" # Name of the partition CLIENT_PROFIL="client_default" # Name of the profile CLIENT_ENV="aixlinux" # Operating environment CLIENT_MINMEM="512" # Minimum memory in megabyte CLIENT_DESMEM="512" # Desired memory in megabyte CLIENT_MAXMEM="512" # Maximum memory in megabyte CLIENT_PMODE="shared" # shared or ded CLIENT_SMODE="uncap" # cap or uncap CLIENT_SWEIGHT="128" # Value between 0 and 255 CLIENT_MINPU="0.1" # Min processing units CLIENT_DESPU="0.4" # Des processing units CLIENT_MAXPU="2.0" # Max processing units CLIENT_MINVP="1" # Min virtual CPU CLIENT_DESVP="2" # Des virtual CPU CLIENT_MAXVP="4" # Max virtual CPU CLIENT_VSLOT="10" # Number of virtual slots CLIENT_VETH="2/1/1//0/1" # Virtual Ethernet adapter CLIENT_VSCSI="3/client/1//4/1" # Virtual SCSI client adapter CLIENT_START="0" # Start with manages system or not CLIENT_BOOT="norm" # Boot mode = normal CLIENT_PWR="none" # Power controlling partition CLIENT_CON="0" # Connection monitoring CLIENT_IOPOOL="none" # IOPOOL
And here's the little script:
#! /bin/bash
. /home/pjuerss/files/scripts/hmc/lpar.conf
echo -n "Creating LPAR..." ssh $USERID@$HMC mksyscfg -m $SYSTEM -r lpar -i \"name=$CLIENT_NAME,\ profile_name=$CLIENT_PROFIL,lpar_env=$CLIENT_ENV,min_mem=$CLIENT_MINMEM,\ desired_mem=$CLIENT_DESMEM,max_mem=$CLIENT_MAXMEM,proc_mode=$CLIENT_PMODE,\ sharing_mode=$CLIENT_SMODE,min_proc_units=$CLIENT_MINPU,\ desired_proc_units=$CLIENT_DESPU,max_proc_units=$CLIENT_MAXPU,\ min_procs=$CLIENT_MINVP,desired_procs=$CLIENT_DESVP,max_procs=$CLIENT_MAXVP,\ uncap_weight=$CLIENT_SWEIGHT,lpar_io_pool_ids=$CLIENT_IOPOOL,\ max_virtual_slots=$CLIENT_VSLOT,auto_start=$CLIENT_START,\ boot_mode=$CLIENT_BOOT,power_ctrl_lpar_ids=$CLIENT_PWR,\ conn_monitoring=$CLIENT_CON,max_virtual_slots=$CLIENT_VSLOT,\ virtual_eth_adapters=$CLIENT_VETH,virtual_scsi_adapters=$CLIENT_VSCSI\" echo "done"
And here're both at work - by the way it takes <12 sec. to finish:
[pjuerss@ankh-morpork hmc]$ ./createLPAR.sh Creating LPAR...done {none}
And here's the output on the HMC:
{code:none} hscroot@hmc-570:~> lssyscfg -m Server-9110-510-SN100129A -r prof --filter "lpar_ids=2" name=client_default,lpar_name=linux_test,lpar_id=2,lpar_env=aixlinux,all_resourc es=0,min_mem=512,desired_mem=512,max_mem=512,proc_mode=shared,min_proc_units=0.1 ,desired_proc_units=0.4,max_proc_units=2.0,min_procs=1,desired_procs=2,max_procs =4,sharing_mode=uncap,uncap_weight=128,io_slots=none,lpar_io_pool_ids=none,max_v irtual_slots=10,"virtual_serial_adapters=1/server/1/any//any/1,0/server/1/any//a ny/1",virtual_scsi_adapters=3/client/1/VIOS1.3FP8.0/4/1,virtual_eth_adapters=2/1 /1//0/1,hca_adapters=none,boot_mode=norm,conn_monitoring=0,auto_start=0,power_ct rl_lpar_ids=none,work_group_id=none,redundant_err_path_reporting=0
Rebooting the HMC via CLI
The HMC itself can be rebooted by logging to HMC with SSH, as user hscroot, and issueing the command
$ hmcshutdown -r -t0 To shutdown a LPAR
chsysstate -r lpar -m MACHINE_NAME -o shutdown --immed --restart --id LPARID (or -n LPARNAME)
Console or virtual terminals
A menu-driven selection of attached machines and pertitions can be gotten via
vtmenu An escape sequence to leave vtmenu terminal session is:
~. To open a console terminal:
$ mkvterm -m <machine> -p <partition> This can be exited with ~~. To remove a terminal someone else is using:
$ rmvterm -m <machine> -p <partition>
List devices on a PCI bus
# lsslot -c phb PHB Name Description Device(s) PHB 1 Logical PCI Host Bridge pci0 U7879.001.DQDGTGK-P1-T14 pci3 sisscsia0 U7879.001.DQDGTGK-P1-T4 pci4 usbhc0 usbhc1 U7879.001.DQDGTGK-P1-T6 pci5 ent0 ent1 PHB 2 Logical PCI Host Bridge pci1 U7879.001.DQDGTGK-P1-C3 pci6 ent2 ent3 U7879.001.DQDGTGK-P1-C4 pci7 ent4 ent5 U7879.001.DQDGTGK-P1-C5 pci8 fcs0 PHB 3 Logical PCI Host Bridge pci2 U7879.001.DQDGTGK-P1-T12 pci10 sisscsia1 U7879.001.DQDGTGK-P1-T15 pci11 ide0 U7879.001.DQDGTGK-P1-C1 pci12 fcs1
How to find out what HMC(s) your AIX LPAR and system are managed by
AIX command# lsrsrc IBM.ManagementServer Resource Persistent Attributes for IBM.ManagementServer resource 1: Name = "10.253.1.21" Hostname = "10.253.1.21" ManagerType = "HMC" LocalHostname = "10.253.1.54" ClusterTM = "9078-160" ClusterSNum = "" ActivePeerDomain = "" NodeNameList = {"hmc01 "} resource 2: Name = "10.253.1.22" Hostname = "10. 253.1.22" ManagerType = "HMC" LocalHostname = "10.253.1.54" ClusterTM = "9078-160" ClusterSNum = "" ActivePeerDomain = "" NodeNameList = {"hmc02 "}
Name and Hostname are HMC's Name and hostname of HMC
Linux on PowerHow to setup hw-raid before installing the operating systemDownload the latest Diagnostics ISO Image from: Diagnostic CD burn it onto a CD and then boot this CD.
Once booted this will bring up the AIX diag which enables you to set the SCSI disk RAID settings as you like. Basically you have to modify all disks which should belong to a RAID configuration from a regular 512-byte block size to a 522-byte block size array candidate disk as only such candidate disks can be included in a RAID setting. Once the RAID settings are done, the OS will not see the single disks of the RAID setting anymore, just your RAID disks.
If you are using SUSE SLES9 you can also boot a CD or network, select "Boot a rescue system" and run iprconfig utility. How to setup hardware raid after installing OSUse iprconfig command. Discs are going to be formatted for Raid, so all data is lost afterwards.
1. run iprconfig 2. Select 2: Work with disk arrays 3. Select: 5. Format device for advanced function (522) 4. Select all disks you want use pressing 1, enter 5. confirm pressing c 6. Select 2: Create a disk array 7. Press 1 Create a disk array 8. Press 1 for each disk you are going to use, press enter 9. Select protection level (0, 10, 5) 10. Select stripe size (default for raid5 64k), press enter
SLES 11 installationStart install with this command for VNC:Boot: install vnc=1 vncpassword=<your_password_here> So the prompt is “boot:” and you type the “install vnc=1 vncpassword=<your_password_here>” and just pick some password to use for the VNC connection. This lets you do a full graphic install using VNC. You will later be prompted during the installation setup for which adapter and either DHCP or static IP configuration.
Doing this typical install took about 2 hours though. A long time. It was on a slow VPN network connection, and I had to create all the LVM LV’s for the various filesystems, and I was using the virtual optical DVDROM from the VIOS, so perhaps all that accounted for the slowness and length of time it took. Create PrEP partitionCreate a partition of type PREP of about 32MB to 128MB in size. Not sure what this is used for, but it definitely was needed when trying the IBM Installation Toolkit mentioned below. IBM Installation Toolkit for Linux Does More Than Just Install Linux
Does not support SLES 11 (as of 10/31/2009) Does not support LVM (as of 10/31/2009) Don't be taken in by the title -- the IBM Installation Toolkit for Linux isn't just for installing Linux. From IBM: "The IBM Installation Toolkit for Linux provides a set of tools that simplifies the installation of Linux on IBM Power Systems. The toolkit also provides IBM value-added software that you can install, so that you can take advantage of Power Systems capabilities, such as Dynamic Logical Partitioning (DLPAR). The toolkit also supports Web-based updates, providing immediate access to the latest offerings.
"The Toolkit can also be used as a rescue bootable DVD to run diagnostic tools and repair previously installed operating systems. It also provides a wealth of IBM documentation for configuring and managing Power systems.
"The Toolkit is available as a single ISO image that that you can download from this website. This image can be used to create a bootable DVD or to create a network installation server, which makes multiple and parallel Linux installations over the network possible."
While I plan on using it to install Linux, I first wanted to check out the Toolkit's other features. First, I downloaded the .iso image. As always, I prefer virtual optical instead of physical media. So I went to my virtual I/O (VIO) server and ran:
mkrep -sp datavg -size 16G
Then I ran:
oem_setup_env cd /var/vio/VMLibrary/ scp source_machine:/path/to/iso.image ./
This copied the .iso image to my VIO server so that I could assign it as a virtual optical device.
I did a DLPAR operation on my HMC to add a virtual SCSI adapter to my VIO server. Then I ran cfgdev on my VIO server so that I could see the adapter.
And then I ran:
mkvdev -fbo -vadapter vhost3 loadopt -vtd vtopt0 -disk IBM_Installation_Toolkit.iso
lsmap showed me:
vhost3
VTD vtopt0 Status Available LUN 0x8100000000000000 Backing device /var/vio/VMLibrary/IBM_Installation_Toolkit.iso Physloc
After assigning the virtual SCSI adapter to my client LPAR, I was then able to boot from this CD image.
Once I booted the machine, I got a root prompt. Then I entered:
WelcomeCenter
After accepting the license, I was presented with these options:
Install Linux Utilities Help
I went into the Utilities and saw:
Configure network Eject Media Reboot System System Diagnostics Firmware Update
The System Diagnostics has:
System Properties System Inventory Error Log Service Configuration Boot Configuration
These look like useful tools, and if I boot from this CD image I don't need to have an OS installed to run the utilities. Once I've had more time to explore them, I'll report back with more findings.
More from IBM:
"The server consolidation tool provided by the Toolkit tackles the most time-consuming and error-prone aspect of server consolidation: the migration of OS stack and user and application data. With the Toolkit, the administrator can quickly put a new server into production. The tool targets the migration and customization of LAMP stack (Linux - Apache - mySQL - Perl, Python, and PHP) and data from X86 servers running RHEL 4, RHEL5, SLES9 and SLES10 to Power Systems.
"The administrator has complete control over the installation and migration process. He chooses the level of the OS and whether additional RPMs should be installed as well as whether to migrate user accounts and data. So whether you intend to migrate one or more servers, the new server consolidation tool is sure to save you a lot of time.
"The IBM Installation Toolkit is intended for customers who want to:
Install and configure Linux on a non-virtualized Power System. Install and configure Linux on machines with previously configured Logical Partitions (virtualized machines). Install IBM RAS Tools along with Linux or on a previously installed system. Upgrade firmware level on Power Systems. Perform diagnostics or maintenance operations on previously installed systems. Improve application performance using the latest Power Systems optimizations available in the Advance Toolchain. Migrate LAMP stack from X86 RHEL and SLES servers to Power Systems. Browse and search Linux documentation included on the Toolkit ISO. "
Appendix A: Full HMC and System Setup Procedure
|
Be very careful with 
Hint: Issue the command 
| [Home] [Linux] [AIX] [Power Systems Stuff] |