11-04-2010
Your proposed method would work however it's recommended practice to have NIM as a standalone in your environment as a MASTER / CLIENT relationship.
You won't need a separate license for your server but ensure you have the DVD available so you can create your LPP sources etc. Also to turn your existing server into a "NIM" server you will need to install the 2 required bos.nim filesets as recommended by IBM.
Here is a link that may help you in setting up your NIM: http://www.redbooks.ibm.com/abstracts/sg247296.html
Hope this helps! Let us know!
Last edited by linuxlearner17; 11-04-2010 at 12:56 PM..
Reason: Included hyperlink
10 More Discussions You Might Find Interesting
1. AIX
Hi-
I'm using NIM functionality (AIX5.3) to backup all AIX Servers but some Servers are in the DmZ and many tcpip ports (nfs, ping,etc...) should be open and... it's really a security risks!
As anyone experience about NIM Backup through Firewall?
Which tcpip ports should be open?
Could we... (1 Reply)
Discussion started by: nymus7
1 Replies
2. 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
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
Can any one help.....
How will do migration through NIM server? (4 Replies)
Discussion started by: AIXlearner
4 Replies
5. AIX
:b:Hi...
I need help to configure nim client on nim server..
can i define aix 5.3.4.0 on aix 5.3.7.0 nim server.. while i m configuring nim client on nim server its getting msg that images not same.. i need to confirm that both version should be same or not..
Thanks.. (5 Replies)
Discussion started by: sumathi.k
5 Replies
6. AIX
Guys,
We are planning to upgrade one of our NIM server to AIX 6.1 from 5.3...
Since the server itself is a NIM Server we can't perform it via NIM & I'm choosing to do CD install.. The Install method would be Upgrade installation.
Is there anything special that I need to consider before... (5 Replies)
Discussion started by: kkeng808
5 Replies
7. AIX
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)
Discussion started by: falgun6666
3 Replies
8. AIX
HELLO ALL
i have installed aix 6.2 , and install sysback 6.1 over Nim , and cinfigure it by Nim AND sysback smitty menu with create spot and lppsource and make TSM configration for that, i take image backup(installation image) successfully but when i want to restore this image , the boot cycle... (5 Replies)
Discussion started by: nancy_ghawanmeh
5 Replies
9. AIX
We are primarily a AIX shop and we will be building our first Linux server on Intel server.
I would like to know if someone has experience installing RHEL using NIM running on AIX.
I would like to know if this is possible. If yes, how will the network boot and NFS work without using 3 rd... (3 Replies)
Discussion started by: mk8570
3 Replies
10. AIX
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies
LEARN ABOUT CENTOS
bos_delete
BOS_DELETE(8) AFS Command Reference BOS_DELETE(8)
NAME
bos_delete - Deletes a server process from the BosConfig file
SYNOPSIS
bos delete -server <machine name>
-instance <server process name>+ [-cell <cell name>]
[-noauth] [-localauth] [-help]
bos d -s <machine name> -i <server process name>+
[-c <cell name>] [-n] [-l] [-h]
DESCRIPTION
The bos delete command removes the /etc/openafs/BosConfig entry for each process indicated by the -instance argument, on the server machine
named by the -server argument.
Before issuing this command, issue the bos stop command to stop the process and set its status flag in the BosConfig file to "NotRun". The
bos delete command fails with an error message if a process's status flag is "Run".
OPTIONS
-server <machine name>
Indicates the server machine on which to delete the server process entry from the /etc/openafs/BosConfig file. Identify the machine by
IP address or its host name (either fully-qualified or abbreviated unambiguously). For details, see bos(8).
-instance <server process name>+
Names each process to delete. Use the name assigned with the -instance argument to the bos create command; process names appear in the
output of the bos status command.
-cell <cell name>
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see bos(8).
-noauth
Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see
bos(8).
-localauth
Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The bos command interpreter presents the ticket
to the BOS Server during mutual authentication. Do not combine this flag with the -cell or -noauth options. For more details, see
bos(8).
-help
Prints the online help for this command. All other valid options are ignored.
EXAMPLES
The following command removes the buserver, kaserver, ptserver, and vlserver entries from the BosConfig file on "db3.abc.com", a database
server machine being decommissioned.
% bos delete -server db3.abc.com
-instance buserver kaserver ptserver vlserver
PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machine named by the -server argument, or must be logged onto a
server machine as the local superuser "root" if the -localauth flag is included.
The bos delete command cannot be run against servers which are in restricted mode.
SEE ALSO
BosConfig(5), KeyFile(5), UserList(5), bos(8), bos_create(8), bos_status(8)
COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas
Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.
OpenAFS 2012-03-26 BOS_DELETE(8)