New disks won't show up in the SMS menu as they aren't bootable devices. once the misuse restore gets to the point where you choose the target disk you will be able to verify that the disks work.
Really without the LED code we are flying blind.
It looks from the screen shot that the tftpboot has completed so I'm going to guess that the LED code is 806, and that means that there is a network configuration issue. Can you provide us with the output of
Code:
lsnim -l server
To see if we can sport what has happened. once the tftpboot is complete the network settings from the Nim server are applied and if they are incorrect the process will fail at that point.
Hi guys,
I am trying to install a new machine via nim but it is hanging on 0608 => it should be a network issue
here the situation hoping you will be able to help:
server NIM on a subnet/IP 10.36.12.64
client on 161.43.56.25
the ping test is successful but when I launch the isntall it... (9 Replies)
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)
when I type start /SP/console... the console shows up but i cannot type anything over there. I do not understand what might be the reason for that.
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (
I pressed enter many... (8 Replies)
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)
Hello guys
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
0516-304 putlvodm: Unable to find device id 000b5f62263b70a50000000000000000 in the Device... (1 Reply)
Hi All,
I am facing very strange problem. I have created NIM server with 6.1 TL4SP3. I am having SPOT and MKsysb of the same version. I am able to install the client using this spot and mksysb. Now I got the requirement of installing the 5.3 ML11SP3 client. So using the mksysb of 5.3 ML11SP3, I... (3 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 HPUX
vxbootsetup
vxbootsetup(1M)vxbootsetup(1M)NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk
SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ]
DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a
disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must
be contiguous with only one subdisk.
The -g option may be used to specify the boot disk group.
If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to
be bootable.
If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable.
vxbootsetup requires that:
o The root volume must be named rootvol and must have a usage type of root.
o The swap volume must be named swapvol and must have a usage type of swap.
o The volumes containing /usr and /var (if any) must be named usr and var, respectively.
See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the
system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically.
If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the
disk bootable.
ARGUMENTS
medianame
Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable.
SEE ALSO disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M),
vxrootmir(1M)
Veritas Volume Manager Troubleshooting Guide
VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)