Sponsored Content
Full Discussion: NIM problem
Operating Systems AIX NIM problem Post 302189428 by thomn8r on Friday 25th of April 2008 05:54:55 PM
Old 04-25-2008
Did you allocate the SPOT?

Run

# lsnim -c resources hostname

Or use SMIT to look at the installation resources assigned to that system
 

10 More Discussions You Might Find Interesting

1. AIX

migrate NIM server through NIM installation

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

Nim Master Problem

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

Problem with nim installation

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

problem adding NIM client

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

Back up a client NIM from nim master

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

For NIM: NFS file system problem

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

NIM client boot problem

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

NIM : remove nim client info from the client

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

Problem in communication nim client with nim master

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

How to know NIM name from NIM client?

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
ddi_dma_alloc_handle(9F)				   Kernel Functions for Drivers 				  ddi_dma_alloc_handle(9F)

NAME
ddi_dma_alloc_handle - allocate DMA handle SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int ddi_dma_alloc_handle(dev_info_t *dip, ddi_dma_attr_t *attr, int (*callback) (caddr_t), caddr_t arg, ddi_dma_handle_t *handlep); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). PARAMETERS
dip Pointer to the device's dev_info structure. attr Pointer to a DMA attribute structure for this device (see ddi_dma_attr(9S)). callback The address of a function to call back later if resources aren't available now. The following special function addresses may also be used. DDI_DMA_SLEEP Wait until resources are available. DDI_DMA_DONTWAIT Do not wait until resources are available and do not schedule a callback. arg Argument to be passed to a callback function, if such a function is specified. handlep Pointer to the DMA handle to be initialized. DESCRIPTION
ddi_dma_alloc_handle() allocates a new DMA handle. A DMA handle is an opaque object used as a reference to subsequently allocated DMA resources. ddi_dma_alloc_handle() accepts as parameters the device information referred to by dip and the device's DMA attributes described by a ddi_dma_attr(9S) structure. A successful call to ddi_dma_alloc_handle() fills in the value pointed to by handlep. A DMA handle must only be used by the device for which it was allocated and is only valid for one I/O transaction at a time. The callback function, callback, indicates how a caller wants to handle the possibility of resources not being available. If callback is set to DDI_DMA_DONTWAIT, then the caller does not care if the allocation fails, and can handle an allocation failure appropriately. If callback is set to DDI_DMA_SLEEP, then the caller wishes to have the the allocation routines wait for resources to become available. If any other value is set, and a DMA resource allocation fails, this value is assumed to be a function to call at a later time when resources may become available. When the specified function is called, it is passed arg as an argument. The specified callback function must return either DDI_DMA_CALLBACK_RUNOUT or DDI_DMA_CALLBACK_DONE. DDI_DMA_CALLBACK_RUNOUT indicates that the callback routine attempted to allocate DMA resources but failed to do so, in which case the callback function is put back on a list to be called again later. DDI_DMA_CALL- BACK_DONE indicates either success at allocating DMA resources or the driver no longer wishes to retry. The callback function is called in interrupt context. Therefore, only system functions that are accessible from interrupt context is available. The callback function must take whatever steps necessary to protect its critical resources, data structures, queues, and so forth. When a DMA handle is no longer needed, ddi_dma_free_handle(9F) must be called to free the handle. RETURN VALUES
ddi_dma_alloc_handle() returns: DDI_SUCCESS Successfully allocated a new DMA handle. DDI_DMA_BADATTR The attributes specified in the ddi_dma_attr(9S) structure make it impossible for the system to allocate potential DMA resources. DDI_DMA_NORESOURCES No resources are available. CONTEXT
ddi_dma_alloc_handle() can be called from user, kernel, or interrupt context, except when callback is set to DDI_DMA_SLEEP, in which case it can be called from user or kernel context only. SEE ALSO
ddi_dma_addr_bind_handle(9F), ddi_dma_buf_bind_handle(9F), ddi_dma_burstsizes(9F), ddi_dma_free_handle(9F), ddi_dma_unbind_handle(9F), ddi_dma_attr(9S) Writing Device Drivers SunOS 5.10 22 Sep 1996 ddi_dma_alloc_handle(9F)
All times are GMT -4. The time now is 09:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy