Tag Archives: IBM

Aix

IBM AIX LPAR & VIO Commands

March 24, 2014 admin Leave a comment

Sorry for unstructured post….

mkvdev -vdev hdisk1 -vadapter vhost0 -dev rootvgos

mkvdev -vdev Client3_OSLV -vadapter vhost0 -dev Client3_rootvg

mkvdev -vdev Client4_OSLV -vadapter vhost1 -dev Client4_rootvg

mkvdev -vdev Client3_dataLV -vadapter vhost0 -dev Client3_datavg

mkvdev -vdev Client4_dataLV -vadapter vhost1 -dev Client4_datavg

lsmap -vadapter vhost0

rmvdev -vtd rootvgos

loadopt -f -vtd vtopt0 -disk nimserver.vol1

unloadopt -vtd vtopt0

mkvg -s 1024 -y datavg hdisk1

mklv -t jfs2 -y data01lv datavg 510

mklv -t jfs2 -y data02lv datavg 510

crfs -v jfs2 -d data01lv -m /data01 -A yes

crfs -v jfs2 -d data02lv -m /data02 -A yes

chown -R oracle:dba /data01

chown -R oracle:dba /data02

chmod -R 775 /data01

chmod -R 775 /data02

mklv -t jfs2 -y LPAR3_OSLV rootvg 400

mkvg -s 1024 -y lparosvg hdisk1

mklv -t jfs2 -y LPAR3_OSLV lparosvg 30

mklv -t jfs2 -y LPAR4_OSLV lparosvg 30

mklv -t jfs2 -y LPAR5_OSLV lparosvg 30

mklv -t jfs2 -y LPAR6_OSLV lparosvg 30

mklv -t jfs2 -y LPAR7_OSLV lparosvg 30

mklv -t jfs2 -y LPAR8_OSLV lparosvg 30

mklv -t jfs2 -y LPAR9_OSLV lparosvg 30

mklv -t jfs2 -y LPAR10_OSLV lparosvg 30

mkvdev -vdev LPAR3_OSLV -vadapter vhost0 -dev LPAR3_OS

mkvdev -vdev LPAR4_OSLV -vadapter vhost1 -dev LPAR4_OS

mkvdev -vdev LPAR5_OSLV -vadapter vhost2 -dev LPAR5_OS

mkvdev -vdev LPAR6_OSLV -vadapter vhost3 -dev LPAR6_OS

mkvdev -vdev LPAR7_OSLV -vadapter vhost4 -dev LPAR7_OS

mkvdev -vdev LPAR8_OSLV -vadapter vhost5 -dev LPAR8_OS

mkvdev -vdev LPAR9_OSLV -vadapter vhost6 -dev LPAR9_OS

mkvdev -vdev LPAR10_OSLV -vadapter vhost7 -dev LPAR10_OS

rmvdev -vtd LPAR3_OS

rmvdev -vtd LPAR4_OS

rmvdev -vtd LPAR5_OS

rmvdev -vtd LPAR6_OS

rmvdev -vtd LPAR7_OS

rmvdev -vtd LPAR8_OS

rmvdev -vtd LPAR9_OS

rmvdev -vtd LPAR10_OS

mklv -t jfs2 -y LPAR3_OSLV lparosvg 50

mklv -t jfs2 -y LPAR4_OSLV lparosvg 50

mklv -t jfs2 -y LPAR5_OSLV lparosvg 50

mklv -t jfs2 -y LPAR6_OSLV lparosvg 50

mklv -t jfs2 -y LPAR7_OSLV lparosvg 50

mklv -t jfs2 -y LPAR8_OSLV lparosvg 50

mklv -t jfs2 -y LPAR9_OSLV lparosvg 50

mklv -t jfs2 -y LPAR10_OSLV lparosvg 50

rmdev -dl en0

rmdev -dl et0

rmdev -dl ent0

rmdev -dl en1

rmdev -dl et1

rmdev -dl ent1

rmdev -dl en2

rmdev -dl et2

rmdev -dl ent2

rmdev -dl en3

rmdev -dl et3

rmdev -dl ent3

rmdev -dl en4

rmdev -dl et4

rmdev -dl ent4

rmdev -dl en5

rmdev -dl et5

rmdev -dl ent5

rmdev -dl en6

rmdev -dl et6

rmdev -dl ent6

rmdev -dl en7

rmdev -dl et7

rmdev -dl ent7

rmdev -dl en8

rmdev -dl et8

rmdev -dl ent8

rmdev -dl en9

rmdev -dl et9

rmdev -dl ent9

rmdev -dl en10

rmdev -dl et10

rmdev -dl ent10

rmdev -dl en11

rmdev -dl et11

rmdev -dl ent11

rmdev -dl en9

rmdev -dl et9

rmdev -dl ent9

mkvdev -vdev LPAR3_OSLV -vadapter vhost0 -dev LPAR3_OS

mkvdev -sea ent0 -vadapter ent4 -default ent4 -defaultid 1 -attr ha_mode=auto ctl_chan=ent5

netstat -v | grep Speed

mkvdev -lnagg ent0 ent4

mkvdev -sea ent10 -vadapter ent8 -default ent8 -defaultid 1

rmfs /dev/fsfslv00

rmfs /dev/fsfslv01

rmfs /dev/fslv00

rmfs /dev/fsfslv03

ntpdate -d 10.0.50.14

lsnports

vfcmap -vadapter vfchost0 -fcp fcs0

vfcmap -vadapter vfchost1 -fcp fcs0

vfcmap -vadapter vfchost2 -fcp fcs0

vfcmap -vadapter vfchost3 -fcp fcs0

vfcmap -vadapter vfchost4 -fcp fcs0

vfcmap -vadapter vfchost5 -fcp fcs0

vfcmap -vadapter vfchost6 -fcp fcs0

vfcmap -vadapter vfchost7 -fcp fcs0

vfcmap -vadapter vfchost8 -fcp fcs2

vfcmap -vadapter vfchost9 -fcp fcs2

vfcmap -vadapter vfchost10 -fcp fcs2

vfcmap -vadapter vfchost11 -fcp fcs2

vfcmap -vadapter vfchost12 -fcp fcs2

vfcmap -vadapter vfchost13 -fcp fcs2

vfcmap -vadapter vfchost14 -fcp fcs2

vfcmap -vadapter vfchost15 -fcp fcs2

ls -ltr /etc/init.ohasd

ls -l /etc/rc.d/rc2.d/*ohasd

ls -l /etc/ohasd

rm -rf /etc/rc.d/rc2.d/K19ohasd

rm -rf /etc/rc.d/rc2.d/S96ohasd

rm -rf /etc/init.ohasd

rmitab “h1”

rm /etc/ohasd

errclear 0

mv /etc/log/HostIdFile.txt /etc/log/HostIdFile.txt.old

errclear 0

cat /etc/log/HostIdFile.txt

lsfs

rmfs /dev/fslv00

lsfs

mkrep -sp rootvg -size 8G

cd /var/vio/VMLibrary/

Etherchannel with SEA

DanielJMartin | Mar 21 2012 | Comments (2) | Visits (4030)

0 people like this

inShare

Configuring your SEA with Etherchannel.

First check the shared virtual ethernet adapters you have –

netstat -v | grep Speed

mkvdev -lnagg ent0 ent4

# lsmap -all -net

SVEA Physloc

—— ——————————————–

ent3 U9117.MMB.101697P-V1-C2-T1

SEA NO SHARED ETHERNET ADAPTER FOUND

Then we need to check what adapters we can use, now in our case we will be using the first 2 adapters from a dual port 1Gb card –

# lsdev -type adapter

name status description

ent0 Available 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003)

ent1 Available 2-Port 10/100/1000 Base-TX PCI-Express Adapter (14104003)

Then we need to create the Etherchannel device –

# mkvdev -lnagg ent0 ent1

ent2 Available

This creates the device in standard mode, though you can switch it over to round robin –

# chdev -l ent2 -a mode=round_robin

Then we can create a SEA “bridge” between the physical Etherchannel device ent2 and the virtual ent3

# mkvdev -sea ent2 -vadapter ent3 -default ent3 -defaultid 1

main: 86 Recived SEA events bytes 163

ent9 Available

Once that is done, you can set-up initial TCP/IP config (en9 is the interface for the SEA ent9)

# mktcpip -hostname <vio-name> -inetaddr <ip-address> -interface en9 -start -netmask <subnet> -gateway <gateway-ip>

Now your server ready to go.

Enter Number of Running Partition (q to quit): 10

Opening Virtual Terminal On Partition VIO-Server2 . . .

Open in progress

Open Completed.

0 > show-devs

000000c95568: /ibm,serial

000000c96690: /chosen

000000c969c0: /packages

000000c96ab8: /disassembler

000000c9ce90: /assembler

000000cc76a0: /dev-tree

000000cc7e60: /lpevents

000000ccec08: /fabric-mgr

000000ce51f8: /deblocker

000000ce6330: /disk-label

000000ceb528: /tape-label

000000cec240: /obp-tftp

000000cfd688: /ipv4

000000d045e8: /ipv6

000000d0bec8: /udp

000000d12d10: /tcp

000000d1a150: /ping

000000d21f18: /bootp

000000d2b580: /dhcp

000000d37728: /tftp

000000d41ab0: /iscsi

000000d49270: /gscsi

000000d4ede0: /disk

000000d50c70: /tape

000000d527d8: /iptest

000000d582f8: /prep-boot

000000d58b88: /fat-files

000000d5af30: /iso-13346-files

000000d647d8: /gen-iso-13346-files

000000d6d6a8: /utilities

000000d9abc8: /trace

000000da7388: /net

000000daf358: /iso-9660-files

000000db07a0: /boot-mgr

000000dc1960: /chrp-loader

000000dc1b40: /pe-loader

000000dc2630: /elf-loader

000000dc5e68: /nls-support

000000dc6c60: /cas

000000dc9790: /terminal-emulator

000000dc9888: /dynamic-reconfig

000000ea2e00: /gui

000000ec5010: /iscsi

000000ed7888: /post

000000caf6c8: /options

000000cb1068: /cpus

000000cb6c88: /PowerPC,POWER7@0

000000cb80b0: /l2-cache@200a

000000cb84a8: /l3-cache@310a

000000cb8bf0: /memory@0

000000cc1ed0: /ibm,dynamic-reconfiguration-memory

000000cc25a8: /aliases

000000ce3c18: /openprom

000000dc9e80: /event-sources

000000dcbc80: /epow-events

000000dcbdf0: /interrupt-controller@0

000000dcd860: /interrupt-controller@800000025000202

000000dd1df0: /interrupt-controller@800000025000205

000000dd6380: /rtas

000000ddfd90: /vdevice

000000de6350: /vty@30000000

000000de7b38: /l-lan@3000000c

000000df02b0: /v-scsi-host@30000020

000000df0ea8: /vfc-server@30000022

000000df1dc8: /v-scsi-host@3000002a

000000df29c0: /vfc-server@3000002c

000000df38e0: /v-scsi-host@30000034

000000df44d8: /vfc-server@30000036

000000df53f8: /v-scsi-host@3000003e

000000df5ff0: /vfc-server@30000040

000000df6f10: /v-scsi-host@30000048

000000df7b08: /vfc-server@3000004a

000000df8a28: /v-scsi-host@30000052

000000df9620: /vfc-server@30000054

000000dfa540: /v-scsi-host@3000005c

000000dfb138: /vfc-server@3000005e

000000dfc058: /v-scsi-host@30000066

000000dfcc50: /vfc-server@30000068

000000e033a0: /IBM,sp@4000

000000e04310: /rtc@4001

000000e04c20: /nvram@4002

000000e04f10: /gscsi@4004

000000e05808: /disk

000000e14ba8: /pci@800000020000202

000000e32798: /fibre-channel@0

000000e47448: /fp

000000e47fa8: /disk

000000e49b48: /tape

000000e4afc8: /fibre-channel@0,1

000000e5fc78: /fp

000000e607d8: /disk

000000e62378: /tape

000000e21900: /pci@800000020000205

000000e63888: /ethernet@0

000000e72708: /ethernet@0,1

000000e81588: /ethernet@0,2

000000e90408: /ethernet@0,3

0 > 000000e32798 to active-package ok

0 > pwd /pci@800000020000202/fibre-channel@0 ok

0 > ” /pci@800000020000202/fibre-channel@0″select-dev bad quoted string ok

0 > show-settings show-settings, unknown word ok

0 > ok

0 > ioinfo

!!! IOINFO: FOR IBM INTERNAL USE ONLY !!!

This tool gives you information about SCSI,IDE,SATA,SAS,and USB devices attached to the system

Select a tool from the following

1. SCSIINFO

2. IDEINFO

3. SATAINFO

4. SASINFO

5. USBINFO

6. FCINFO

7. VSCSIINFO

q – quit/exit

==> 6

FCINFO Main Menu

Select a FC Node from the following list:

# Location Code Pathname

—————————————————————

1. U78AB.001.WZSJZK6-P1-C3-T1 /pci@800000020000202/fibre-channel@0

2. U78AB.001.WZSJZK6-P1-C3-T2 /pci@800000020000202/fibre-channel@0,1

q – Quit/Exit

==> 1

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0

FC Node WorldWidePortName: 10000090fa42fb1a

—————————————————————–

1. List Attached FC Devices

2. Select a FC Device

3. Enable/Disable FC Adapter Debug flags

q – Quit/Exit

==> 2

NO FC DEVICES FOUND

Hit a key to continue…

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0

FC Node WorldWidePortName: 10000090fa42fb1a

—————————————————————–

1. List Attached FC Devices

2. Select a FC Device

3. Enable/Disable FC Adapter Debug flags

q – Quit/Exit

==> 1

NO FC DEVICES FOUND

Hit a key to continue…

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0

FC Node WorldWidePortName: 10000090fa42fb1a

—————————————————————–

1. List Attached FC Devices

2. Select a FC Device

3. Enable/Disable FC Adapter Debug flags

q – Quit/Exit

==> q

FCINFO Main Menu

Select a FC Node from the following list:

# Location Code Pathname

—————————————————————

1. U78AB.001.WZSJZK6-P1-C3-T1 /pci@800000020000202/fibre-channel@0

2. U78AB.001.WZSJZK6-P1-C3-T2 /pci@800000020000202/fibre-channel@0,1

q – Quit/Exit

==> 2

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0,1

FC Node WorldWidePortName: 10000090fa42fb1b

—————————————————————–

1. List Attached FC Devices

2. Select a FC Device

3. Enable/Disable FC Adapter Debug flags

q – Quit/Exit

==>

Lost connection to the Managed System…

Attempting to reconnect

The open failed.

-The session may already be open on another management console

-The server may not be ready to accept connections.

Attempts to open the session failed. Please close the terminal and retry the open at a later time.

If the problem persists, Please contact IBM support.

VIO1_82_Client3_fcs0

VNX5300_SPB0_UNIT2_VIO1_82_Client3_fcs0

VNX5300_SPB1_UNIT2_VIO2_82_Client3_fcs0

VNX5300_SPA0_UNIT2_VIO1_82_Client3_fcs0

VNX5300_SPA1_UNIT2_VIO2_82_Client3_fcs0

VNX5300_SPB0_UNIT2_VIO1_82_Client4_fcs0

VNX5300_SPB1_UNIT2_VIO2_82_Client4_fcs0

VNX5300_SPA0_UNIT2_VIO1_82_Client4_fcs0

VNX5300_SPA1_UNIT2_VIO2_82_Client4_fcs0

# lsdev -c adapter

ent0 Available 03-00 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)

ent1 Available 03-01 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)

ent2 Available 03-02 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)

ent3 Available 03-03 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)

ent4 Available Virtual I/O Ethernet Adapter (l-lan)

ent5 Available Virtual I/O Ethernet Adapter (l-lan)

ent6 Available Shared Ethernet Adapter

fcs0 Available 04-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)

fcs1 Available 04-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)

pkcs11 Available PKCS#11 Device

sissas0 Available 00-00 PCIe x4 Planar 3Gb SAS RAID Adapter

sissas1 Available 02-00 PCIe x4 Internal 3Gb SAS RAID Adapter

usbhc0 Available 05-08 USB Host Controller (33103500)

usbhc1 Available 05-09 USB Host Controller (33103500)

usbhc2 Available 05-0a USB Enhanced Host Controller (3310e000)

vfchost0 Available Virtual FC Server Adapter

vfchost1 Available Virtual FC Server Adapter

vfchost2 Available Virtual FC Server Adapter

vfchost3 Available Virtual FC Server Adapter

vfchost4 Available Virtual FC Server Adapter

vfchost5 Available Virtual FC Server Adapter

vfchost6 Available Virtual FC Server Adapter

vfchost7 Available Virtual FC Server Adapter

vhost0 Available Virtual SCSI Server Adapter

vhost1 Available Virtual SCSI Server Adapter

vhost2 Available Virtual SCSI Server Adapter

vhost3 Available Virtual SCSI Server Adapter

vhost4 Available Virtual SCSI Server Adapter

vhost5 Available Virtual SCSI Server Adapter

vhost6 Available Virtual SCSI Server Adapter

vhost7 Available Virtual SCSI Server Adapter

vsa0 Available LPAR Virtual Serial Adapter

# hostname

nimserver

# lscfg -vpl fcs* | grep Z8

Device Specific.(Z8)……..C050760714500000

Device Specific.(Z8)……..C050760714500002

# hostname

AIXLPAR4-104-112

# lscfg -vpl fcs* | grep Z8

Device Specific.(Z8)……..C050760714500006

Device Specific.(Z8)……..C050760714500004

hostname

lscfg -vpl fcs* | grep Z8 | cut -d . -f10 | sed ‘s/../&:/g;s/:$//’

lscfg -vpl fcs* | grep Z8 | cut -d . -f10 | sed ‘s/../&:/g;s/:$//’;hostname

C0:50:76:07:14:50:00:00

C0:50:76:07:14:50:00:02

nimserver

C0:50:76:07:14:50:00:1E

C0:50:76:07:14:50:00:1C

AIXLPAR10-104-118

C0:50:76:07:14:50:00:18

C0:50:76:07:14:50:00:1A

AIXLPAR9-104-117

C0:50:76:07:14:50:00:16

C0:50:76:07:14:50:00:14

AIXLPAR8-104-116

C0:50:76:07:14:50:00:10

C0:50:76:07:14:50:00:12

AIXLPAR7-104-115

C0:50:76:07:14:50:00:0E

C0:50:76:07:14:50:00:0C

AIXLPAR6-104-114

C0:50:76:07:14:50:00:08

C0:50:76:07:14:50:00:0A

AIXLPAR5-104-113

C0:50:76:07:14:50:00:06

C0:50:76:07:14:50:00:04

AIXLPAR4-104-112

C0:50:76:07:14:50:00:00

C0:50:76:07:14:50:00:02

nimserver

lsdev -c adapter

lscfg -vpl fcs0

lscfg -vpl vfchost1

vfchost1 U8231.E2D.06C83FT-V1-C43 Virtual FC Server Adapter

Hardware Location Code……U8231.E2D.06C83FT-V1-C43

PLATFORM SPECIFIC

Name: vfc-server

Node: vfc-server@3000002b

Device Type: fcp

Physical Location: U8231.E2D.06C83FT-V1-C43

# exit

$ vfcmap -vadpater vfchost1 -fcp fcs0

Option flag is not valid.

Usage: vfcmap -vadapter VFCServerAdapter -fcp [FCPName]

lsnports

vfcmap -vadapter vfchost0 -fcp fcs0

vfcmap -vadapter vfchost1 -fcp fcs0

vfcmap -vadapter vfchost2 -fcp fcs0

vfcmap -vadapter vfchost3 -fcp fcs0

vfcmap -vadapter vfchost4 -fcp fcs0

vfcmap -vadapter vfchost5 -fcp fcs0

vfcmap -vadapter vfchost6 -fcp fcs0

vfcmap -vadapter vfchost7 -fcp fcs0

vfcmap -vadapter vfchost8 -fcp fcs2

vfcmap -vadapter vfchost9 -fcp fcs2

vfcmap -vadapter vfchost10 -fcp fcs2

vfcmap -vadapter vfchost11 -fcp fcs2

vfcmap -vadapter vfchost12 -fcp fcs2

vfcmap -vadapter vfchost13 -fcp fcs2

vfcmap -vadapter vfchost14 -fcp fcs2

vfcmap -vadapter vfchost15 -fcp fcs2

$ cfgdev

# lscfg -vpl ent4

ent4 U8231.E2D.06C83FT-V1-C11-T1 Virtual I/O Ethernet Adapter (l-lan)

Network Address………….D26D148F6F0B

Displayable Message………Virtual I/O Ethernet Adapter (l-lan)

Hardware Location Code……U8231.E2D.06C83FT-V1-C11-T1

PLATFORM SPECIFIC

Name: l-lan

Node: l-lan@3000000b

Device Type: network

Physical Location: U8231.E2D.06C83FT-V1-C11-T1

# lscfg -vpl ent5

ent5 U8231.E2D.06C83FT-V1-C12-T1 Virtual I/O Ethernet Adapter (l-lan)

Network Address………….D26D148F6F0C

Displayable Message………Virtual I/O Ethernet Adapter (l-lan)

Hardware Location Code……U8231.E2D.06C83FT-V1-C12-T1

PLATFORM SPECIFIC

Name: l-lan

Node: l-lan@3000000c

Device Type: network

Physical Location: U8231.E2D.06C83FT-V1-C12-T1

# scp 10.1.50.101:/data03/Unix-Software-Repository/AIX/IBM-ISO/AIX7.1TL02/* .

The authenticity of host ‘10.1.50.101 (10.1.50.101)’ can’t be established.

RSA key fingerprint is f7:9d:58:29:9c:1e:13:44:b3:a7:d5:b4:57:d7:21:c8.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added ‘10.1.50.101’ (RSA) to the list of known hosts.

root@10.1.50.101’s password:

Permission denied, please try again.

root@10.1.50.101’s password:

AIX_7.1_TL02_02_DVD1.iso 100% 3658MB 42.0MB/s 01:27

AIX_7.1_TL02_02_DVD2.iso 100% 2601MB 45.6MB/s 00:57

# exit

$ mkvdev -fbo -vadapter vhost

$ lsmap -all

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost0 U8231.E2D.06C83FT-V1-C31 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost1 U8231.E2D.06C83FT-V1-C41 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost2 U8231.E2D.06C83FT-V1-C51 0x0000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost3 U8231.E2D.06C83FT-V1-C61 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost4 U8231.E2D.06C83FT-V1-C71 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost5 U8231.E2D.06C83FT-V1-C81 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost6 U8231.E2D.06C83FT-V1-C91 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost7 U8231.E2D.06C83FT-V1-C101 0x00000000

VTD NO VIRTUAL TARGET DEVICE FOUND

$ mkvdev -fbo -vadapter vhost0

vtopt0 Available

$ lsmap -vadapter vhost0

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost0 U8231.E2D.06C83FT-V1-C31 0x00000000

VTD vtopt0

Status Available

LUN 0x8100000000000000

Backing device

Physloc

Mirrored N/A

$ lsrep

Size(mb) Free(mb) Parent Pool Parent Size Parent Free

8158 1899 rootvg 544768 506880

Name File Size Optical Access

AIX_7.1_TL02_02_DVD1.iso 3658 None rw

AIX_7.1_TL02_02_DVD2.iso 2601 None rw

$ loadopt -vtd vtopt0 -disk AIX_7.1_TL02_02_DVD1.iso

$ lsmap -vadapter vhost0

SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost0 U8231.E2D.06C83FT-V1-C31 0x00000000

VTD vtopt0

Status Available

LUN 0x8100000000000000

Backing device /var/vio/VMLibrary/AIX_7.1_TL02_02_DVD1.iso

Physloc

Mirrored N/A

$ lspv

NAME PVID VG STATUS

hdisk0 00f8c83f2effbda1 rootvg active

hdisk1 none None

$ mkvdev -vdev hdisk1 -vadapter vhost0 -dev rootvgos

rootvgos Available

Please reboot the client partition to see the newly added disk.

$ lsmap -vadapter vhost0

SVSA Physloc SVSA Physloc Client Partition ID

————— ——————————————– ——————

vhost0 U8231.E2D.06C83FT-V1-C31 0x00000003

VTD rootvgos

Status Available

LUN 0x8200000000000000

Backing device hdisk1

Physloc U78AB.001.WZSJZK6-P1-C18-T1-LFF0100-L0

Mirrored false

VTD vtopt0

Status Available

LUN 0x8100000000000000

Backing device /var/vio/VMLibrary/AIX_7.1_TL02_02_DVD1.iso

Physloc

Mirrored N/A

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

1 = SMS Menu 5 = Default Boot List

8 = Open Firmware Prompt 6 = Stored Boot List

Memory Keyboard Network SCSI Speaker ok

0 > ok

0 > ininfo ininfo, unknown word ok

0 > IOINFO

!!! IOINFO: FOR IBM INTERNAL USE ONLY !!!

This tool gives you information about SCSI,IDE,SATA,SAS,and USB devices attached to t

q – Quit/Exit

==> 1

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0

FC Node WorldWidePortName: 10000090fa42f3cc

—————————————————————–

1. List Attached FC Devices

2. Select a FC Device

3. Enable/Disable FC Adapter Debug flags

q – Quit/Exit

==> 2

NO FC DEVICES FOUND

Hit a key to continue…

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0

FC Node WorldWidePortName: 10000090fa42f3cc

FCINFO Main Menu

Select a FC Node from the following list:

# Location Code Pathname

—————————————————————

1. U78AB.001.WZSJZJ5-P1-C3-T1 /pci@800000020000202/fibre-channel@0

2. U78AB.001.WZSJZJ5-P1-C3-T2 /pci@800000020000202/fibre-channel@0,1

q – Quit/Exit

==> 2

Cannot Init Link.

FC Node Menu

FC Node String: /pci@800000020000202/fibre-channel@0,1

FC Node WorldWidePortName: 10000090fa42f3cd

—————————————————————–

1. List Attached FC Devices

2. Select a FC Device

3. Enable/Disable FC Adapter Debug flags

q – Quit/Exit

==> 2

Aix

IBM VIOS CDROM – DVDROM (Virtual Optical Device)

January 14, 2014 admin Leave a comment

CDROM – DVDROM (Virtual Optical Device):

Any optical device equipped on the Virtual I/O Server partition (either CD-ROM, DVD-ROM, or DVD-RAM) can be virtualized and assigned at any logical partition, one at a time, using the same virtual SCSI adapter provided to virtual disks. Virtual optical devices can be used to install the operating system and, if DVD-RAM, to make backups.

Creating Virtual Optical Device:

1. On VIO Server create SCSI Server Adapter. This adapter is set to Any client partition can connect.
This dedicated adapter for the virtual optical device helps to make things easier from a system management point of view.

2. On client LPAR: create SCSI client adapter, mapping the id with the server adapter (above)

3. cfgdev (on vio) will bring up a new vhostX
cfgmgr (on client) will bring up a new vscsiX

4. On VIO Server create optical device:

-for using physical CDs and DVDs, create an optical device
$ mkvdev -vdev cd0 -vadapter vhost4 -dev vcd
vcd Available

$ lsdev -virtual
…
vcd Available Virtual Target Device – Optical Media

–for file backed (iso images) optical device
$ mkvdev -fbo -vadapter vhost1
vtopt0 Available

$lsdev -virtual
…
vtopt0 Available Virtual Target Device – File-backed Optical

(copy the iso image to /var/vio/VMLibrary, ‘lsrep’ will show media repository content)
(lssp -> mkrep -sp rootvg -size 4G <–this will create media repository)
(creating an iso image: mkvopt -name <filename>.iso -dev cd0 -ro)

load the image into the vtopt0 device: loadopt -vtd vtopt0 -disk dvd.1022A4_OBETA_710.iso
(lsmap -all will show it)

or you can check it:
padmin@vios1 : /home/padmin # lsvopt
VTD Media Size(mb)
vtopt0 AIX_7100-00-01_DVD_1_of_2_102010.iso 3206

if later another disk is needed, you can unload an image with this command: unloadopt -vtd vtopt0
if we don’t need the image anymore at all we can remove it from the repository: rmvopt -name AIX_7100-00-01.iso

5. On client LPAR cfgmgr and create CDROM filesystem
In the AIX client partition run the cfgmgr command to assign the virtual optical drive to it. If the drive is already assigned to another partition you will get an error message and you will have to release the drive from the partition holding it.

create mount point: mkdir /cdrom

create cdrom filesystem: smitty fs -> add cdrom filesystems:
device name: cd0
mount point: /cdrom
mount automatically

mount the filesystem: mount -v cdrfs -r /dev/cd0 /cdrom

Aix

How to create Etherchannel with SEA VIO in IBM

January 14, 2014 admin Leave a comment

Configuring your SEA with Etherchannel.

First check the shared virtual ethernet adapters you have –

$ lsmap -all -net
SVEA Physloc
—— ——————————————–
ent8 U8231.E2D.06C83BT-V1-C11-T1

SEA                   ent11
Backing device        ent10
Status                Available
Physloc

SVEA Physloc
—— ——————————————–
ent9 U8231.E2D.06C83BT-V1-C12-T1

SEA NO SHARED ETHERNET ADAPTER FOUND

Then we need to check what adapters we can use, now in our case we will be using the first 2 adapters from a dual port 1Gb card –

$ lsdev -type adapter
name             status      description
ent0             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent1             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent2             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent3             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent4             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent5             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent6             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent7             Available   4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
ent8             Available   Virtual I/O Ethernet Adapter (l-lan)
ent9             Available   Virtual I/O Ethernet Adapter (l-lan)
ent10            Available   EtherChannel / IEEE 802.3ad Link Aggregation
ent11            Available   Shared Ethernet Adapter
fcs0             Available   8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs1             Available   8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs2             Available   8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs3             Available   8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
pkcs11           Available   PKCS#11 Device
sissas0          Available   PCIe x4 Planar 3Gb SAS RAID Adapter
sissas1          Available   PCIe x4 Internal 3Gb SAS RAID Adapter
usbhc0           Available   USB Host Controller (33103500)
usbhc1           Available   USB Host Controller (33103500)
usbhc2           Available   USB Enhanced Host Controller (3310e000)
vfchost0         Available   Virtual FC Server Adapter
vfchost1         Available   Virtual FC Server Adapter
vfchost2         Available   Virtual FC Server Adapter
vfchost3         Available   Virtual FC Server Adapter
vfchost4         Available   Virtual FC Server Adapter
vfchost5         Available   Virtual FC Server Adapter
vfchost6         Available   Virtual FC Server Adapter
vfchost7         Available   Virtual FC Server Adapter
vfchost8         Available   Virtual FC Server Adapter
vfchost9         Available   Virtual FC Server Adapter
vfchost10        Available   Virtual FC Server Adapter
vfchost11        Available   Virtual FC Server Adapter
vfchost12        Available   Virtual FC Server Adapter
vfchost13        Available   Virtual FC Server Adapter
vfchost14        Available   Virtual FC Server Adapter
vfchost15        Available   Virtual FC Server Adapter
vhost0           Available   Virtual SCSI Server Adapter
vhost1           Available   Virtual SCSI Server Adapter
vhost2           Available   Virtual SCSI Server Adapter
vhost3           Available   Virtual SCSI Server Adapter
vhost4           Available   Virtual SCSI Server Adapter
vhost5           Available   Virtual SCSI Server Adapter
vhost6           Available   Virtual SCSI Server Adapter
vhost7           Available   Virtual SCSI Server Adapter
vsa0             Available   LPAR Virtual Serial Adapter
$

Then we need to create the Etherchannel device –

# mkvdev -lnagg ent0 ent4

ent10 Available

This creates the device in standard mode, though you can switch it over to round robin –

# chdev -l ent10 -a mode=round_robin

Then we can create a SEA “bridge” between the physical Etherchannel device ent2 and the virtual ent3

# mkvdev -sea ent10 -vadapter ent8 -default ent8 -defaultid 1

ent11 Available

Once that is done, you can set-up initial TCP/IP config (en11 is the interface for the SEA ent11)

# mktcpip -hostname <vio-name> -inetaddr <ip-address> -interface en11 -start -netmask <subnet> -gateway <gateway-ip>

Now your server ready to go.

Aix

How to change adapter properties of the SEA VIO IBM

January 14, 2014 admin Leave a comment

Overview

One of the problems that one can often run into is that you need to change some characterstic on the ethernet adapter that you are using for the SEA. One example is that you need to change the speed from say autonegotiate to 100 full duplex. If you simply go to the root user with oem_setup_env and try to make the change, you will likely get this error.

# lsattr -El ent0 -a media_speed
media_speed 100_Full_Duplex Media speed True

# chdev -l ‘ent0′ -a media_speed=’Auto_Negotiation’
Method error (/usr/lib/methods/chgent):
0514-062 Cannot perform the requested function because the
specified device is busy.

It is likely that when you setup the SEA that you configured the TCP/IP address on the SEA as directed in the virtualization Redbook or the white papers on this topic.

Procedure

Note that you will lose network access from any clients that are dependent on this SEA unless you already have setup SEA failover or client network interface backup.

Follow these steps to first unconfigure and remove the SEA, then make the changes and reconfigure.

Set the backspace key if it’s not working

stty erase (hit backspace key) then hit enter
looks like
stty erase ^?

View the ethernet virtual adapters as padmin

$ lsdev | grep ent
ent0       Available 10/100/1000 Base-TX PCI-X Adapter (14106902)
ent1       Available Virtual I/O Ethernet Adapter (l-lan)
ent2       Available Virtual I/O Ethernet Adapter (l-lan)
ent3      Available Virtual I/O Ethernet Adapter (l-lan)
ent4       Available Shared Ethernet Adapter

Become root user

$ oem_setup_env
#

Check to see if the IP address is configured on the SEA

If it is configured, then it will return an inet address as shown here:
# ifconfig en4
en4: flags=e080863,80
inet 9.19.51.159 netmask 0xffffff00 broadcast 9.19.51.255
tcp_sendspace 131072 tcp_recvspace 65536

If it is not configured, then you will get this:
# ifconfig en4
en4: flags=e080822,80

If it is configured, then you will need to unconfigure it. Normally if this was a physical adapter, I would simply remove the adapter, but if you try to do that will the SEA, you will get errors if my memory serves me right, yet it may be worth trying first. If you do this, you will need to remove the en interface, the et interface, and finally the ent interface.

At this point you can use your favorite way to remove the IP from the interface. Once you have done that, you no longer will have network access directly to the VIO server, but will need to go through the HMC console terminal. If you had setup the IP address on the virtual adapter in a dual VIO system, this would not be a problem.

If nothing else works, or if the only interface that has an IP address is the SEA, then type

rmtcpip -f interface ent4

This will remove the TCPIP address. To check, rerun the ifconfig command from earlier. Once this address is removed, then you should be able to remove the SEA.

Type exit to go back to padmin
Remove the SEA device

# exit
$ rmdev -dev ent4 -recursive

This should remove cleanly and if it doesn’t it is debug time. Assuming that it is removed, then go back to root.

$ oem_setup_env

Make sure that en4 and et4 have also been removed (Adjust the 4 for the number of your adapter

# rmdev -dl en4
# rmdev -dl et4
# rmdev -dl ent4

Now take the physical adapter down. In this case it is the ent0 adapter so:

# ifconfig en0 down
# ifconfig en0 detach

Now you should be able to change the ent0 adapter through smit or with chdev as shown here:

# chdev -l ‘ent0′ -a media_speed=’Auto_Negotiation’

Now I’m a little foggy on if you need to ifconfig en0 attach and up. I think you may not do this unless the mkvdev command fails
Return to padmin and recreate the SEA adapter with mkvdev

# exit
$ mkvdev -sea ent2 -vadapter ent0 -default ent0 -defaultid 1 \
-attr ha_mode=auto ctl_chan=ent1
ent4 Available
en4

Then readd the IP information either with mktcpip or smitty tcpip Here I recommend putting the address on a separate client virtual ethernet adapter so you don’t have to rmtcpip the next time. You can do DLPAR to add this to the partition and run cfgmgr before the mktcpip step

mktcpip -hostname fsvio3 -inetaddr 9.19.51.160 -interface en4 -start -netmask 255.255.255.0
-gateway 9.19.51.6 -nsrvdomain dfw.ibm.com -nsrvaddr 9.0.7.1

Test by pinging something outside the box.

Aix, Uncategorized

How to Upgrade IBM Power server firmware fixes through AIX or Linux without an HMC

May 14, 2013 admin Leave a comment

Installing server firmware fixes through the operating system is a disruptive process. You will need to restart the system.

Notes:

If your system is managed by an HMC, you must apply server firmware through the HMC. For details, see Managed system updates in Updates.
If you have a System i® model running IBM® i, you must either apply server firmware through an HMC or through an IBM i logical partition. If you have a POWER6® Power Systems™ server that is managed by an HMC, you must use the HMC.
By default, the server firmware is installed on the temporary side only after the existing contents of the temporary side are permanently installed on the permanent side. (This process is performed automatically when you install a server firmware fix.)
If you are unable to start your AIX or Linux operating system or server, refer to Obtaining fixes through AIX or Linux when you are unable to start the system.

Perform Steps 1 through 6 to get server firmware fixes through AIX or Linux when you do not have an HMC.

Step 1. View existing firmware levels for AIX or Linux

The Advanced System Management Interface (ASMI) is the user interface to access the server firmware. You can also use the AIX or Linux operating system to view the firmware levels.

Select from the following options:
- To use the ASMI (AIX or Linux): On the ASMI Welcome pane, view the existing level of server firmware in the upper-right corner below the copyright statement, for example, EM310_006.
- To use the AIX command prompt (you must have AIX diagnostics installed on your server), continue with step 2.
- To use the Linux command prompt, continue with step 4.
At an AIX command prompt, enter the following command:
```
lsmcode
```
The existing levels of server firmware are displayed. For example, you might see output similar to the following:
```
DISPLAY MICROCODE LEVEL                                                   802811
IBM,8231-E1C

The current permanent system firmware image is AL740_088
The current temporary system firmware image is AL740_088
The system is currently booted from the temporary firmware image.

Use Enter to continue.
```
Notes:
- The permanent level is also known as the backup level.
- The temporary level is also known as the installed level.
- The system was booted from the temporary side, so at this time, the temporary level is also the activated level.
Continue with Step 2. View or download the firmware fix.
To view existing levels of server firmware for Linux, you must have the following service tools installed on your server:
- Platform Enablement Library – librtas-xxxxx.rpm
- Service Aids – ppc64-utils-xxxxx.rpm
- Hardware Inventory – lsvpd-xxxxx.rpm
where xxxxx represents a specific version of the RPM file.

Note: If you do not have the service tools on your server, refer to Obtaining service and productivity tools for Linux.

After the service tools are installed on the server running Linux, enter the following at a Linux command prompt:

lsmcode

The existing level of server firmware is displayed. For example, you might see output similar to the following:

Version of system firmware is: AL740_088 (t)  AL740_088 (p)  AL740_088 (t)

The following table provides descriptions for each of the server firmware levels displayed in the output.

Table 1. Server firmware levels
Server firmware levels displayed
AL740_088 (t)	AL740_088 (p)	AL740_088 (t)
The installed level.Also known as the temporary level.	The backup level.Also known as the permanent level.	The activated level.The level on which the server is currently running.

Continue with the next step.

Step 2. View or download the firmware fix

Follow this procedure to view or download the firmware fix. You can download the fix directly to your server, or you can download it to a computer with an Internet connection and create a fix CD that you apply on the server. If necessary, contact service and support to order the fix on CD. You can also download the firmware fix to a computer that has a network connection to your server and use FTP to download the firmware fix from the computer to the server.

Note: If you plan to create a CD, you will need a CD burner and software.

From a computer or server with an Internet connection, go to the Fix Central Web site at http://www.ibm.com/support/fixcentral/.
Choose from the following options:
1. If you have a System p® server, select System p in the Product Group list.
2. If you have a POWER6 Power Systems server, select Power in the Product Group list.
Select Firmware and HMC in the Product list.
If prompted, select POWER5 and POWER6 class in the Processor type list.
Select your Machine Type-Model and click Continue.
Follow the on-screen prompts to download the fix file.
Select from the following options:
- If you downloaded the RPM file to your server, continue with Step 3. View and unpack the RPM file that contains the server firmware.
- If you downloaded the RPM file to a different computer and used FTP to download the RPM file to your server, continue with Step 3. View and unpack the RPM file that contains the server firmware.
  Note: Select binary mode before using FTP to download the RPM file from a different computer to your server.
- If you want to create a CD containing the RPM file, follow the instructions for your CD program and then continue with Step 3. View and unpack the RPM file that contains the server firmware.

Step 3. View and unpack the RPM file that contains the server firmware

If you created a CD with the RPM file, you will need to view and unpack the RPM file that contains the server firmware.

Select from the following options:
- If you created a CD with the RPM file, continue with the next step.
- If you downloaded the RPM file to your server from the Fix Central Web site at http://www.ibm.com/support/fixcentral/ or by using the FTP method, continue with step 6.
Insert the CD that contains the RPM file into the media drive on your server.
To mount the CD, select from the following options (you need root user authority):
- If you are working on an AIX system, enter the following at an AIX command prompt:
```
mount /dev/cd0 /mnt
```
- If you are working on a Linux system, enter one of the following commands at a Linux command prompt:
```
mount -t iso9660 /dev/cdrom /mnt 
```
  or
```
mount -t iso9660 /dev/dvdrom /mnt
```
Select from the following options:
- If the mount was successful, continue with step 6.
- If the mount was unsuccessful, continue with the next step.
If you received the message,
mount: 0506-324 Cannot mount /dev/cd0 on /mnt, perform the following steps to mount the CD:
1. Enter the command:
```
/usr/sbin/mount -v 'cdrfs' -f'' -p'' -r'' /dev/cd0 /mnt
```
  The quotation marks following the f, p, and r are two single quotation marks with no space between them.
  
  Note: If you prefer, you can use the System Management Interface Tool (SMIT) to mount the CD.
2. Continue with the next step.
To view the RPM file name, enter the following command at the AIX or Linux command prompt:
- If the RPM file is on CD, type:
```
ls /mnt
```
- If the RPM file is on the server, type:
```
ls /tmp/fwupdate
```
The name of the RPM file is displayed. For example, you might see output similar to the following:
```
01EM3xx_yyy_zzz.rpm
```
To unpack the RPM file, enter one of the following commands at the AIX or Linux command prompt:
- If you want to unpack from a CD, enter:
```
rpm -Uvh --ignoreos /mnt/filename.rpm
```
- If you want to unpack from the server’s hard drive, enter:
```
rpm -Uvh --ignoreos /tmp/fwupdate/filename.rpm
```
  where filename is the name of the RPM file that contains the server firmware. For example, 01EM3xx_yyy_zzz.rpm.
  
  Note: When you unpack the RPM file, the server firmware fix file is saved in the /tmp/fwupdate directory on the server’s hard drive in the following format: 01EM3xx_yyy_zzz.img.
Continue with the next step.

Step 4. Apply server firmware fixes through AIX or Linux to the temporary side of the service processor

Important:

Do not interrupt this process after you begin.
Do not attempt to log into the ASMI, or use any of the ASMI’s functions, while a firmware installation is in progress.

Ensure you are starting the system from the temporary side of the service processor; the firmware installation will fail if the system has booted from the permanent side. To learn which side you are starting from, and how to change to the other side if necessary, refer to Working with the temporary and permanent side of the service processor.
To use the update_flash command (AIX or Linux) to install the server firmware, continue with step 3.
Note: If you have AIX installed, you can choose to use the AIX diagnostics to install the fix. However, if you plan to install the fix from CD, you will need to obtain the Microcode Updates Files & Discovery Tool CD to use the AIX diagnostics.
You will need the server firmware fix file name in the next step. To view the name, enter the following at an AIX or Linux command prompt:
Note: To perform this step, you must have root user authority.
```
ls /tmp/fwupdate
```
The name of the server firmware fix file is displayed. For example, you might see output similar to the following:
```
01EM3xx_yyy_zzz.img
```

To install the server firmware fix, select from the following options:

If you are updating AIX, enter the following at an AIX command prompt:
```
cd /tmp/fwupdate
/usr/lpp/diagnostics/bin/update_flash -f fwlevel
```

# rpm -Uvh --ignoreos 01AL740_100_042.rpm
01AL740_100_042             ##################################################
# cd /tmp/fwupdate
# ls
01AL740_100_042.img
# /usr/lpp/diagnostics/bin/update_flash -f 01AL740_100_042
Error in opening the file 01AL740_100_042
#  /usr/lpp/diagnostics/bin/update_flash -f 01AL740_100_042.img
The image is valid and would update the temporary image to AL740_100.
The new firmware level for the permanent image would be AL740_088.

The current permanent system firmware image is AL740_088.
The current temporary system firmware image is AL740_088.

***** WARNING: Continuing will reboot the system! *****

Do you wish to continue?
Enter 1=Yes or 2=No
1

SHUTDOWN PROGRAM
Tue May 14 10:08:53 IST 2013
0513-044 The sshd Subsystem was requested to stop.

Wait for 'Rebooting...' before stopping.
Error reporting has stopped.
Advanced Accounting has stopped...
Process accounting has stopped.
nfs_clean: Stopping NFS/NIS Daemons
0513-004 The Subsystem or Group, nfsd, is currently inoperative.
0513-044 The biod Subsystem was requested to stop.
0513-044 The rpc.lockd Subsystem was requested to stop.
0513-044 The rpc.statd Subsystem was requested to stop.
0513-004 The Subsystem or Group, gssd, is currently inoperative.
0513-004 The Subsystem or Group, nfsrgyd, is currently inoperative.
0513-004 The Subsystem or Group, rpc.mountd, is currently inoperative.
0513-004 The Subsystem or Group, ypserv, is currently inoperative.
0513-004 The Subsystem or Group, ypbind, is currently inoperative.
0513-004 The Subsystem or Group, yppasswdd, is currently inoperative.
0513-004 The Subsystem or Group, ypupdated, is currently inoperative.
0513-004 The Subsystem or Group, nis_cachemgr, is currently inoperative.
0513-004 The Subsystem or Group, rpc.nisd, is currently inoperative.
0513-004 The Subsystem or Group, rpc.nispasswdd, is currently inoperative.
0513-044 The qdaemon Subsystem was requested to stop.
0513-044 The writesrv Subsystem was requested to stop.
0513-044 The clcomd Subsystem was requested to stop.
0513-044 The lldpd Subsystem was requested to stop.
0513-044 The ecpvdpd Subsystem was requested to stop.
0513-044 The ctrmc Subsystem was requested to stop.
0513-044 The IBM.ServiceRM Subsystem was requested to stop.
0513-044 The IBM.MgmtDomainRM Subsystem was requested to stop.
0513-044 The IBM.DRM Subsystem was requested to stop.
0513-044 The cas_agent Subsystem was requested to stop.
All processes currently running will now be killed...
Unmounting the file systems...
umount: 0506-349 Cannot unmount /dev/hd10opt: The requested resource is busy.
umount: 0506-349 Cannot unmount /dev/hd1: The requested resource is busy.

where fwlevel is the specific file name of the server firmware fix, such as 01EM3xx_yyy_zzz.img

If you are updating Linux, enter the following at a Linux command prompt:
```
cd /tmp/fwupdate
/usr/sbin/update_flash -f fwlevel
```
where fwlevel is the specific file name of the server firmware fix, such as 01EM3xx_yyy_zzz.img

During the server firmware installation process, reference codes CA2799FD and CA2799FF are alternately displayed on the control panel. After the installation is complete, the system is automatically powered off and powered on.

Note: If you receive a message stating:
This partition does not have the authority to perform the requested function, see Message regarding a server that was previously managed by an HMC.

Continue with the next step.

Step 5. Verify that the fix installed correctly

Select from the following options:
- To use the AIX or Linux command prompt (the operating system must be running and the diagnostics must be available), continue with the next step.
- To use the ASMI, view the level of server firmware displayed in the upper-right corner below the copyright statement on the ASMI Welcome pane; for example, EM310_006. If the level of server firmware displayed is not the level that you installed, refer to step 4.
Enter the following at a command prompt:
```
lsmcode
```
The existing levels of server firmware are displayed. For example, you might see output similar to the following:
```
DISPLAY MICROCODE LEVEL                                                   802811
IBM,8231-E1C

The current permanent system firmware image is AL740_088
The current temporary system firmware image is AL740_100
The system is currently booted from the temporary firmware image.

Use Enter to continue.
```
Notes:
- The permanent level is also known as the backup level.
- The temporary level is also known as the installed level.
- The system was booted from the temporary side, so at this time, the temporary level is also the activated level.
Verify that the level of server firmware displayed is the level that you installed.
If the level of server firmware displayed is not the level that you installed, perform the following steps:
1. Retry the fix procedure. If you created a CD or DVD for this procedure, use a new media.
2. If the problem persists, contact your next level of support.

Aix

Boot the IBM Aix system into Service mode

July 24, 2012 admin Leave a comment

This document describes how to boot the system into Service mode (also known as Maintenance mode) to install the machine, restore an operating system backup, or perform maintenance on the rootvg volume group.

The information in this document applies to AIX Versions 3.x, 4.x and 5.x.

Booting microchannel systems into Service mode Booting PCI-based systems into Service mode PCI machine-specific information Accessing rootvg and mounting file systems
Related documentation

——————————————————————————–

Booting microchannel systems into Service mode

To boot microchannel systems into Service mode, turn the key to the Maintenance position and press the yellow reset button twice. You must boot from bootable media, such as an installation CD-ROM, installation tape, or a bootable backup tape made via the mksysb command or the Sysback product of the correct level for this machine.

For AIX Version 3.2, you may use bootable bosboot diskettes. To boot from these, insert the first bosboot diskette into the diskette drive. When you see LED c07, insert the next diskette, which is usually the display extensions diskette. After this diskette is read, you should receive a menu prompting you for the installation diskette.

For information on accessing your rootvg volume group, see the section entitled “Accessing rootvg and mounting file systems”.

The preceding discussion assumes that the Service mode bootlist has not been modified from the default bootlist. If the bootlist has been modified, it must be reset such that one of the boot media types from the preceding selections is before the standard boot media, such asthe hard disk.

If the machine is an SMP model (7012-Gxx, 7013-Jxx, and 7015-Rxx) and the Autoservice IPL flag is disabled, then a menu like the following will display when it is booting in Service mode:

MAINTENANCE MENU (Rev. 04.03)
0> DISPLAY CONFIGURATION
1> DISPLAY BUMP ERROR LOG
2> ENABLE SERVICE CONSOLE
3> DISABLE SERVICE CONSOLE
4> RESET
5> POWER OFF
6> SYSTEM BOOT
7> OFF-LINE TESTS
8> SET PARAMETERS
9> SET NATIONAL LANGUAGE
SELECT:

You can boot these machines into Service mode or even Normal mode with the Fast IPL Flag set. If you do not, the machine can take anywhere from 30 to 60 minutes to boot up. There are a few ways to set the Fast IPL Flag for these machines.

NOTE: The console must be an ASCII type and connected to the S1 port of the system. Graphic monitors will not work.

Use the following instructions to boot SMP machines into service with Fast IPL set.

Insert the bootable media of the same OS Level. Use the mksysb/cd-rom command.
Turn off the machine by pressing the white button on front.
Turn the key to the Wrench or Service position.
The LCD should read STAND-BY.
Press the Enter key on the console.
A greater-than prompt (>) should display on the monitor.
Type in sbb followed by the Enter key.
The menu Stand By Menu should now display.
Select 1 Set Flags. This will take you to another set of menus.
Select 6 Fast IPL. This should change to enable after it is selected.
Enter x to exit the second set of menus.
Enter x to exit the first menu.
At a blank screen, press the Enter key to obtain the greater-than prompt (>).
Type in the word power followed by the Enter key.
Turn the machine back on. It should start to boot up. A prompt may display asking
if you want to update the firmware. Do not respond; let it continue.
Now you may be at the Maintenance Menu with 10 options displayed, 0 through 9. If
that is the case, select option 6, System Boot. This will take you to another
menu. Select option 0, Boot from the list.
The Standard Maintenance Menu should display. System recovery and maintenance
can be completed from here.
After system recovery and maintenance has been performed, the system is ready to
be rebooted into Normal mode. Enter the command mpcfg -cf 11 1 at the command
line prompt, then press Enter. This will set the Fast IPL Flag. The system is
ready to reboot.
Turn the key back to the OK/Normal position.
Enter shutdown -Fr, followed by the Enter key.

——————————————————————————–

Booting PCI-based systems into Service mode

When booting a PowerPC into Service mode, cd0 or rmt0 must be before the hdisk in the bootlist. If not, change the bootlist at boot time. On some models, you can set the machine to use a default bootlist that includes both cd0 and rmt0. If a bootable CD or tape is in the CD-ROM or tape drive, the machine will boot from this device.

For most of the newer PCI-based models, selecting the default bootlist, with a bootable tape or CD loaded in the machine, causes the system to automatically boot from that device. Generally, the next menu on the screen asks the administrator to define the system console.

For all machines discussed here, if you are using a graphical terminal, you will use a function key such as F5. If you are using an ASCII terminal, use an equivalent number key such as 5. Use the numbers across the top of the keyboard, not the numbers on the numeric keypad. On ASCII terminals, the icons may not be displayed on the screen; the number can be pressed between the second and third beeps, the second beep being a series of three clicks.

——————————————————————————–

PCI machine-specific information
The following systems all use the F5 or 5 key to read from the default boot list, which is written into the system firmware:

MODEL       7017       7024       7025       7026       7043       7137
——-   ——-    ——-    ——-    ——-    ——-    ——-
TYPE      S70        E20        F30        H10        43P-140    F3L
S7A        E30        F40        H50        43P-150
S80                   F50        H70        43P-240
B80        43P-260

On these machines, use 5 (on the keyboard, not the keypad) if you are using an ASCII terminal. On a locally attached graphics console, use the F5 function key. The F5 or 5 key must be pressed just after the keyboard icon or message is displayed on the console. If you have either a 7026-M80, 7026-H80 or a 7025-F80, then the 5 key will be the default whether you have an ascii or graphics console.

The following systems use the F1 key to enter System Management Services mode (SMS):

MODEL       6040       7042       7247       7249
——-   ——-    ——-    ——-    ——-
TYPE        620        850        82x        860

You should be in an Easy-Setup menu. Select the Start Up menu. Clear the current bootlist settings and then select the CD-ROM for choice 1 and hdd (the hard disk) for choice 2. Select OK. Insert the CD-ROM and select the EXIT icon. The machine should now boot from the CD-ROM.

The following systems use the F2 key to enter SMS:

MODEL         6015       6050       6070       7020       7248
——-     ——-    ——-    ——-    ——-    ——-
TYPE          440        830        850        40P        43P

Select Select Boot Device from the initial menu on the screen, and then select Restore Default Settings from the list. Press the Esc key to exit all the menus, and then reboot the machine. The system should boot from your bootable media.

For information on accessing the rootvg volume group, see the next section in this document.

——————————————————————————–

Accessing rootvg and mounting file systems
For AIX Version 3, choose the limited function maintenance shell (option 5 for AIX 3.1, option 4 for AIX 3.2).

If you only have one disk on the system, then hdisk0 will be used in the execution of the getrootfs or /etc/continue commands, which follow. If you have more than one disk, determine which disk contains the boot logical volume in this manner:

AIX 3.2.4 or AIX 3.2.5:

Run getrootfs; the output will indicate which disk contains the hd5 logical volume.

AIX 3.1 to AIX 3.2.3e:

Run lqueryvg -Ltp hdisk# for each hdisk. You can obtain a listing of these with the command lsdev -Cc disk. Repeat this command until you get output similar to the following:

00005264feb3631c.2 hd5 1

If more than one disk contains this output, use any disk when running getrootfs.
Now, access the rootvg volume group by running one of the following commands, using the disk you obtained in the preceding step:

AIX 3.1:                     /etc/continue hdisk#
AIX 3.2.0-3.2.3e:            getrootfs -f hdisk#
AIX 3.2.4-3.2.5:             getrootfs hdisk#

NOTE: If you want to leave the primary OS file systems (/, /usr, /tmp, and /var) unmounted after this command has completed, to run fsck, for instance, place a space and the letters sh after the hdisk in the preceding command. For example:

getrootfs hdisk0 sh

For AIX Versions 4 and 5, choose Start Maintenance Mode for System Recovery , option 3. The next screen will be called Maintenance; select option 1, Access a Root Volume Group. At the next screen, type 0 to continue, and select the appropriate volume group by typing the number next to it. A screen like the following will display.
Example:

Access a Root Volume Group

Type the number for a volume group to display the logical volume information and press Enter.

1) Volume Group 0073656f2608e46a contains these disks:
hdisk0 2063 04-C0-00-4,0

Once a volume group has been selected, information will be displayed about that volume group.

Example:

Volume Group Information
——————————————————————————
Volume Group ID 0073656f2608e46a includes the following logical volumes:
hd6 hd5 hd8 hd4 hd2 hd9var
hd3 hd1
——————————————————————————

Type the number of your choice and press Enter.

1) Access this Volume Group and start a shell
2) Access this Volume Group and start a shell before mounting filesystems
99) Previous Menu

If the logical volumes listed do not include logical volumes like hd4, hd2, hd3, and so on, you may have selected the wrong volume group. Press 99 to back up one screen and select again.

Now you may select one of two options: Access this volume group and start a shell , option 1, or Access this volume group and start a shell before mounting file systems , option 2. Option 2 allows you to perform file system maintenance on /, /usr, /tmp, and /var before mounting them.

NOTE: If you intend to use SMIT or vi, set your terminal type in preparation for editing the file. xx stands for a terminal type such as lft, ibm3151, or vt100.

TERM=<xx>
export TERM

Errors from these steps may indicate failed or corrupt disks in rootvg. These problems should
be corrected. For additional assistance, contact your vendor, your local branch office, or your AIX support center.

——————————————————————————–

Related documentation
For more in-depth coverage of this subject, the following IBM publication is recommended:
AIX Version 4.3 System Management Guide: Operating System and Devices
AIX Version 5.1 System Management Guide: Operating System and Devices

IBM documentation can also be accessed online through the following URL:
http://www.rs6000.ibm.com/resource/aix_resource/Pubs/index.html

Similar documents can be accessed through the following URL:
http://techsupport.services.ibm.com/server/support?view=pSeries