10-01-2018
Setting up NIM for different networks
Hi,
I am struggling setting up a NIM master to serve hosts on a network that is not directly accessible through the "master"-s default interface. I now that I need to set up network definitions and maybe NIM routes, but got confused.
The master has 2 interfaces:
* en0 holding the address which is belonging to its hostname, therefore the AIX default gateway is using that interface (let's call this Network-master1)
* en1 holding IP address from another network. Hosts from this network are enabled to communicate with hosts from my target network, but that communication needs a static route to be set up in the OS - as the default gw routes in a wrong direction. (Let's cal this Network-master2)
And there is another network, holding the to-be-clients - Let's call this Network-client
Every object is served from the master. If I understand correctly, I only need NIM routes is some objects are served from different nodes, thus I would not need this. Is that right?
I tried to set up a second install interface for the master, but as it is part of Network-master2 and not Network-client, I was unable to make NIM to set bootp server address to its second interface IP. It always put "sa=IP.ON.FIRST.INTERFACE" and therefore the client is unable to get its boot package.
Now I am stuck. Can you please help me?
Best regards,
--Trifo
9 More Discussions You Might Find Interesting
1. AIX
HI folks,
Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 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
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
4. What is on Your Mind?
I've read about BITNET, CompuServe... CompuServe was probably not a network but an online service. Are (were) there any other networks alternative to Internet? Does anyone have experience with them? Do they still exist, is it possible to access them over Internet? There seems not to be another way... (13 Replies)
Discussion started by: Action
13 Replies
5. Solaris
If I have 2 interfaces in a server on the same subnet/network does Solaris automatically choose to route packets destined for this network out the first interface. I.e if ce0 and ce1 were on same network ce0 would be chosen as it's first interface? (5 Replies)
Discussion started by: Actuator
5 Replies
6. Solaris
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
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
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
9. 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 OSF1
nis_intro
nis_intro(7) Miscellaneous Information Manual nis_intro(7)
NAME
nis_intro - Network Information Service (NIS) introductory information
DESCRIPTION
The Network Information Service (NIS) is a distributed name service that allows participating hosts to share access to a common set of sys-
tem and network files. NIS allows the system administrator to manage these shared files on a single system.
NIS is intended for use in a secure environment only, where gateways do not allow outside Internet access to the NIS protocol.
NIS Maps
Information distributed by NIS is stored in database files called maps. Most of the NIS maps represent files that were traditionally
stored in the /etc directory. These files include the following: aliases group hosts netgroups networks passwd protocols rpc services
In a secure environment, you can run NIS in a secure mode, thereby creating secure and nonsecure versions of the NIS maps. See the Secu-
rity guide for more information.
You can also use NIS to distribute files used by Automount or AutoFS, or to distribute other user-defined files.
Each NIS map contains a set of keys and associated values. For example, as keys, the hosts map contains all host names on a network, and
as values, the corresponding Internet addresses. Each NIS map has a map name, used by programs to access data in the map.
NIS Domains
A named set of NIS maps is called a domain. A system's "domain name" or "NIS domain" corresponds to the set of NIS maps that the system
can access. You can think of an NIS domain as a set of systems that share the same set of NIS maps.
A system's domain name is set at the time the system is booted by the /sbin/init.d/nis script using an entry in the /etc/rc.config.common
file. System administrators can use the nissetup script to place entries in this file. The nissetup script is described in the Network
Administration manual.
You can determine your system's NIS domain using the domainname command. Refer to domainname(1). A domain name is required for retrieving
data from an NIS database.
NIS Client-Server Model
NIS follows the client-server model of distributed services. There are two types of NIS servers - master and slave. The master server
stores the master copy of the NIS maps for its domain; these are the only NIS maps that can be modified. Each domain has only one master
server.
Slave servers store copies of the master server's NIS maps. NIS slave servers can be spread throughout a network. Whenever an NIS map is
updated on the master server, the master propagates the changes to each slave server in its domain. If the master is unavailable for any
reason, the slave servers continue to make the NIS maps available to the NIS clients.
Clients are all of the systems that can access NIS maps. When a client requires NIS information, it makes a remote procedure call (RPC) to
one of the NIS servers to obtain the information.
NIS Data Storage
The data in NIS maps is stored as databases in dbm/ndbm, btree, or hash format.
For example, the NIS map for the /etc/hosts file in the domain market might be stored in these dbm/ndbm files: /var/yp/mar-
ket/hosts.byaddr.dir
/var/yp/market/hosts.byaddr.pag
/var/yp/market/hosts.byname.dir
/var/yp/market/hosts.byname.pag
The makedbm command takes an ASCII file such as /etc/hosts and converts it into dbm/ndbm files suitable for use by NIS. However, system
administrators use the Makefile script in the /var/yp directory to create NIS map files and specify file format. The Makefile script then
calls makedbm.
Refer to the Network Administration manual for details on the Makefile script, specifying different formats, and other NIS management
information.
RELATED INFORMATION
Commands: domainname(1), svcsetup(8), ypbind(8), yppasswdd(8), ypserv(8), ypxfr(8)
Files: svc.conf(4)
Network Administration delim off
nis_intro(7)