04-25-2008
NIM problem
When I use NIM to reinstall a AIX 5.3 use mksysb
It shows error:
COMMAND STATUS
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
NSORDER=local,bind
Locating ttt-p630...done
Checking for resource group basic_res_grp...done
0042-001 nim: processing error encountered on "master":
0042-063 m_bos_inst: the following resource types are required
for this operation but have not yet been allocated
to "ttt-p630":
spot
10 More Discussions You Might Find Interesting
1. AIX
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)
Discussion started by: yanzhang
1 Replies
2. AIX
All,
I'm testing NIM on a 7026-m80 machine.
But everytime i want to setup the master, i get this error message...
Anyone who knows how to solve this issue? google doesn't seem to know much about it
# nim_master_setup
############################## NIM master setup... (1 Reply)
Discussion started by: kvanelshocht
1 Replies
3. AIX
Dear Frnz,
I have a strange problem with nim installation.
I am able to push the image from Nim server to the client and the Os is reinstalled successfully.But after the installation the client doesnt hold any host name or ip address.That is the host name is assigned as local host and ip is... (2 Replies)
Discussion started by: sriram.s
2 Replies
4. AIX
Hello All,
While trying to add NIM client to the NIM environment from NIM client machine, I get the following error:
1800-109
There are currently no additional SMIT screen entries available for this item. This may require installation of additional software before it can be accessed.
... (1 Reply)
Discussion started by: solaix14
1 Replies
5. AIX
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)
Discussion started by: lo-lp-kl
2 Replies
6. AIX
hello,
i am trying to export a file system so that i can mount it on NIM server and make mksysb backup of the server on that fs.
i get this message:
mount: 1831-011 access denied for s_semdev:/dr_s_zeus/mksysb/dr_s_zeus
mount: 1831-008 giving up on:
s_semdev:/dr_s_zeus/mksysb/dr_s_zeus ... (5 Replies)
Discussion started by: omonoiatis9
5 Replies
7. AIX
Hi all,
I have created VIO Server which serves 3 lpars. All of them are on VLAN ID 50.
From one lpar I installed and set up NIM master server called testAIX1.
I have created client and allocated resources to it:
testAIX1:/ > lsnim -l test_lpar
test_lpar:
class = machines
... (4 Replies)
Discussion started by: phobus
4 Replies
8. AIX
Hi.
I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ?
Tks (2 Replies)
Discussion started by: stephnane
2 Replies
9. AIX
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
10. AIX
Friend's,
I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client?
All leads to the answer would be much appreciated, many thanks!
-- Souvik (2 Replies)
Discussion started by: thisissouvik
2 Replies
LEARN ABOUT DEBIAN
bidentify
BIDENTIFY(1) General Commands Manual BIDENTIFY(1)
NAME
bidentify - Barry Project's program to identify BlackBerry handhelds
SYNOPSIS
bidentify [-B busname][-N devname][-h][-v]
DESCRIPTION
bidentify scans the USB system for available BlackBerry devices and probes each one it finds, then sends the identifying information to
stdout in a computer-friendly format.
OPTIONS
-B busname
Specify the USB bus to search for Blackberry devices on. This is the first number displayed in the output from the lsusb command,
such as 002. If the busname is numeric on your system, 2 and 002 are equal. See also the -N option, which can be used together
with this option to precisely select the device to work with.
-N devname
Specify the USB device name. This is the second number displayed in the output from the lsusb command, such as 005. If the device
name is numeric on your system, 5 and 005 are equal. See also the -B option.
-c If used with the -m option, ESN numbers will be displayed in both hex and decimal formats where possible. If -m is not used, this
option has no effect.
-m Also show the device's ESN / MEID / IMEI number. This requires desktop database access, so is an option. It will only work on
devices that have no password.
-v Dump verbose protocol data during operation.
-h, --help
Show summary of options.
RETURN STATUS
If bidentify detects a BlackBerry device, but cannot access it for some reason, it will write an error message to stderr describing the
access problem, and return a count of the number of such failed devices as the error code. A return code of 0 means there were no Black-
Berry devices found that could not be probed.
In the event of a fatal error, the message will be written to stderr, with an error code of 1.
AUTHOR
bidentify is part of the Barry project. This manual page was written by Chris Frey.
SEE ALSO
http://www.netdirect.ca/software/packages/barry
February 24, 2011 BIDENTIFY(1)