Please login or register. December 15, 2019, 08:58:24 PM

Author Topic: Restoring standalone mksysb to vio client  (Read 18997 times)

0 Members and 1 Guest are viewing this topic.

Achmea

  • New Member
  • *
  • Posts: 3
  • Karma: +0/-0
Restoring standalone mksysb to vio client
« on: July 03, 2007, 08:14:48 AM »
Hi there,

Does anybody have experience with restoring en mksysb from a standalone system(7026-6h0 AIX 5.3 ML4) to a VIO-client(9110-51A)
both systems configured with 2 CPU's 2GB of memory.
only difference
the standalone has rootvg on internal scsi disks
and the VIO-client is getting the disks through the VIO-server which are basically SAN disks.

after i restore the image(with v-scsi device drivers) and boot the VIO-client
i get a process LED code 0554(on HMC) and the details show a FRU CALLOUT UNKNOWN BOOTDISK.

I tried booting with a spot and changing the bosboot and bootlist,

also tried with a customized image.data and an new ODM, non of this worked.

Hope someone can help me with this problem.

Greetings
Mark de Jong

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1195
  • Karma: +0/-0
Re: Restoring standalone mksysb to vio client
« Reply #1 on: July 03, 2007, 12:24:47 PM »
I do not see any reason for it to not be working. On a 9110-51A I have a client partition running with only virtual resources.

# oslevel -s
5300-03-00
# lslpp -L devices.vdevice.\*
  Fileset                      Level  State  Type  Description (Uninstaller)
  ----------------------------------------------------------------------------
  devices.vdevice.IBM.l-lan.rte
                            5.3.0.30    C     F    Virtual I/O Ethernet Software
  devices.vdevice.IBM.v-scsi.rte
                            5.3.0.30    C     F    Virtual SCSI Client Support
  devices.vdevice.hvterm1.rte
                            5.3.0.30    C     F    Virtual Terminal Devices

I guess you need to verify that the devices.vdevices.* filesets are installed.
If for some reason you cannot get them installed into the partition you might try adding the filesets to the 7026 system, and making a new mksysb.

Michael

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1195
  • Karma: +0/-0
Re: Restoring standalone mksysb to vio client
« Reply #2 on: July 03, 2007, 12:30:24 PM »
As an extra hint....
From /sbin/rc.boot the following code is what is hanging.

Quote
                        ${SHOWLED} 0x511 "DEV CFG 1 END"

                        dvc=`bootinfo -b`
                        if [ ! "${dvc}" ]; then
                                loopled 0x554 "UNKNOWN BOOTDISK"
                        fi

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1195
  • Karma: +0/-0
Re: Restoring standalone mksysb to vio client
« Reply #3 on: July 03, 2007, 12:36:17 PM »
And finally, a question: how the disks are being exported to the client. Is the client expected to see them via MPIO (and if so, is the VIO server configured for this?).

If they are, you should also verify that AIX mpio software is installed, and PCM software from other vendors is NOT installed. Too many PCM packages is know to cause problems.

A test would be to just install a simple client (rte install) and check how the newly installed client sees it's disks, and compare that with your clone-based partition.

Achmea

  • New Member
  • *
  • Posts: 3
  • Karma: +0/-0
Re: Restoring standalone mksysb to vio client
« Reply #4 on: July 03, 2007, 12:49:06 PM »
i checked the standalone.

i was missing the vdevice drivers for l-lan and hvterm1
i installed them there now,
# lslpp -L *mpio*
  Fileset                      Level  State  Type  Description (Uninstaller)
  ----------------------------------------------------------------------------
  devices.common.IBM.mpio.rte
                            5.3.0.42    C     F    MPIO Disk Path Control Module
  devices.fcp.disk.Hitachi.array.mpio.rte
                             5.4.0.1    C     F    AIX MPIO Support for Hitachi
                                                   Disk Arrays(Update)


# lslpp -L devices.vdevice.\*
  Fileset                      Level  State  Type  Description (Uninstaller)
  ----------------------------------------------------------------------------
  devices.vdevice.IBM.l-lan.rte
                            5.3.0.30    C     F    Virtual I/O Ethernet Software
  devices.vdevice.IBM.v-scsi.rte
                            5.3.0.41    C     F    Virtual SCSI Client Support
  devices.vdevice.hvterm1.rte
                            5.3.0.40    C     F    Virtual Terminal Devices



making a new mksysb now, then i'll try again.

we got several VIO-clients working perfectly here with SAN disk for rootvg,
but this only works with a new install,
this is the first time we tried from a standalone to a vioclient with mksysb.

# lscfg -l hdisk0
  hdisk0           U9110.51A.063DE2F-V3-C4-T1-L810000000000  Virtual SCSI Disk Drive


this is how a normal VIO-client sees a hdd over here.

Achmea

  • New Member
  • *
  • Posts: 3
  • Karma: +0/-0
Re: Restoring standalone mksysb to vio client
« Reply #5 on: July 03, 2007, 01:57:52 PM »
I just installed the system and it works.

i added the lppsource with NIM aswell,

it installed 4 additional packages, including something that included chrp.lpar and some others.

it boots now, and seems to be completely working.

thanks for the help.