I have been trying to restore a VIO server from NIM using the nim_resource.tar file created from the same VIO lpar. The restoration goes fine and after 99% I get the following error
Code:
0516-304 putlvodm: Unable to find device id 000b5f62263b70a50000000000000000 in the Device Configuration Database.
Then the server reboot and stops at the below screen.
Code:
--------------------------------------------------------------------------
Welcome to the Virtual I/O Server.
boot image timestamp: 19:21 12/01
The current time and date: 19:22:01 12/01/2009
number of processors: 2 size of memory: 2176MB
boot device: /pci@800000020000200/pci1014,02BD@1/sas/disk@40200:2
kernel size: 15063830; 64 bit kernel
--------------------------------------------------------------------------
Ever happened to anyone?
Thanks
Bala
Last edited by zaxxon; 02-17-2010 at 05:57 AM..
Reason: use code tags please, ty
I try to migrate a NIM server from one server to another.
I try to do a mksysb on NIM server
restore the NIM server's mksysb to a client through NIM installation
shutdown NIM server
start newly installed client as NIM server
Does anyone do this before? who can give me some suggestion? (1 Reply)
Hi Friends,
I've a hard question to ask. I have a NIM server running on AIX 5.3. Now my requirement is that , " From This NIM Server i would like to take the Image of Linux servers ". I mean that using NIM server i should be able to backup / restore the linux Servers.
In Simple terms... (3 Replies)
Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Hello everyone
Im trying to backup a nim client from nim master but I got this message
COMMAND STATUS
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
0042-001 nim:... (2 Replies)
Hi,
I've recently implemented a NIM backup procedure for 2 virtual AIX5.3 environments running on a JS22 blade server. The images transfer to an old p620 box connected to some old SSA storage, each server backs up a mksysb and a savevg image. Now seeing as this method should be replacing our... (3 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hello Gurus,
I have a couple of questions, I'm trying to do a mksysb restore from backup and it has just hung at the start.
RS/6000 Firmware
Version TCP05287
(c) Copyright IBM Corp. 2000 All rights reserved.
-------------------------------------------------------------------------------... (8 Replies)
Hi Guys,
We normally have a backup and restore nightly on our Prod machines. We do this via customized script and all unattended. The dilemma that I'm having is the disabling of the cron after the restore.
I created a nim script to disable the cron after the restore has been completed. But... (6 Replies)
Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Discussion started by: omonoiatis9
0 Replies
LEARN ABOUT XFREE86
installboot
installboot(1M)installboot(1M)NAME
installboot - install bootblocks in a disk partition
SYNOPSIS
installboot bootblk raw-disk-device
The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.
The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
found using the -i option of uname(1).
The installboot utility is a SPARC only program. It is not supported on the architecture. users should use installgrub(1M) instead.
bootblk The name of the bootblock code.
raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is read-
able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.
Example 1: Installing UFS Boot Block
To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:
example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
/dev/rdsk/c1t0d0s0
/usr/platform/platform-name/lib/fs/ufs
directory where ufs boot objects reside.
/platform/platform-name/ufsboot
second level program to boot from a disk or CD
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)WARNINGS
The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.
11 Apr 2005 installboot(1M)