08-04-2014
Well, first off, the network IDs have to be unique, i. e. "subnet_1", "subnet_2", etc.. I suppose that was only a typo on your part.
To answer your question: yes, you will have to create separate NIM-networks for this. No, you won't have to configure 3 IP-aliases for your master.
The reason for this is: NIM operates using NFS (for "normal" package installations), bootp (for mksysb-installs) and tftp. All these protocols have to be - obviously - allowed by all the firewalls you might have in between your NIM-server and the prospective clients. In addition the NIM-server needs the standard gateway to each network to be able to act as a "bootp relay agent".
bootp (see RFC951, RFC1542 and others) works with broadcasts from (in respect of IP-numbers) anonymous interfaces and such packets would be dropped at the nearest router. Therefore bootp would not work over network boundaries. a "bootp relay agent" is a router which will take such a packet and forward it to a certain bootp-server and the same way tunnel its answer back to the client, so that bootp works in routed internetworks too.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. 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
2. AIX
Hi,
I want to know what are steps required to create nim master in aix?
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
3. AIX
Hi,
I want to know how to create nim master in AIX 5.3.
Regards,
Manoj (0 Replies)
Discussion started by: manoj.solaris
0 Replies
4. AIX
Hello All,
I believe my NIM master is fine. lsnim and cat /etc/niminfo gives me the right output. While doing "lsnim" on a client machine, I get ksh:lsnim:"not found".
Please someone be nice enough to explain what are the steps to verify the master and client connectivity to do all the NIM... (3 Replies)
Discussion started by: solaix14
3 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
Guys, I need your help
I got a requirement from a cUstomer asking for a specific design
He wants to use the NIM Master as one single mgmt server and access the nodes maintained by it there by the accounting is in one single server for all the nodes
Note:- Direct login to the nodes will... (3 Replies)
Discussion started by: kkeng808
3 Replies
7. 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
8. AIX
Iam attempting to add a client to NIM however the new client has a different subnet than master 10... & 193... , I've established from redbooks that it should be possible but can't find anything that states how?
Does anyone use nim in this way? (5 Replies)
Discussion started by: gefa
5 Replies
9. AIX
hi Admins,
How can I check the NIM master hostname/IP name from NIM client ? I don't see any option that I can try with nimclient command.
Let me know..
Thanks, (5 Replies)
Discussion started by: snchaudhari2
5 Replies
10. 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
bprelay(8) System Manager's Manual bprelay(8)
NAME
bprelay - BOOTP relay agent
SYNOPSIS
/usr/sbin/bprelay [-f] [-d n] [-h hopcount] [-i interface,interface...] [-t minutes] [-w seconds] server...
OPTIONS
Foreground mode. In this mode, bprelay does not run as a daemon. All messages are written to stdout and stderr, although warnings and
errors are still sent to syslog(3). Without this option, bprelay listens on all interfaces on which the underlying protocol supports
broadcasting. With this option, bprelay listens only to those interfaces specified. Any non-existent or invalid interface name are
ignored. Sets debug level to the numeric value n. Larger values of n provides more debugging information. Instructs bprelay to not for-
ward packets if the value of the hops field in the BOOTP packet exceeds hopcount. Instructs bprelay to terminate if minutes have passed
without any packets being received. This option is only honored if bprelay was started from inetd(8). Instructs bprelay to not forward
packets until the secs field in the BOOTP packet header exceeds this value.
DESCRIPTION
The bprelay daemon forwards DHCP or BOOTP packets to the specified list of servers (server). Servers may be identified either by their IP
addresses or by their names. The bprelay agent normally runs as a daemon process, and may be started either from the shell command line
interface or by inetd(8).
The purpose of bprelay is to provide the same service as that found in router hardware, but to run on UNIX workstations. The bprelay agent
listens for DHCP/BOOTP packets on each of the interfaces specified in the command line, and relays each packet to the servers specified.
As a rule, bprelay forwards each and every packet to every server specified, but it omits servers whose IP address is found to be on the
same IP network as the receiving interface since those servers will presumably hear the original broadcast.
RESTRICTIONS
Non-standard subnet masks for all networks administered by bprelay, must be available either through /etc/netmasks or NIS.
SEE ALSO
Commands: inetd(8), joinc(8)
System calls: syslog(3)
RFC1497, RFC1542, RFC1534
bprelay(8)