Sponsored Content
Operating Systems AIX Setting up NIM for different networks Post 303024135 by trifo75 on Monday 1st of October 2018 07:31:57 AM
Old 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

AIX versus Networks

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

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

3. 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

4. What is on Your Mind?

Networks alternative to Internet

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

Multiple networks on same server

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

solaris routing between two networks

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

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

8. 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

9. 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
timed(8)						      System Manager's Manual							  timed(8)

NAME
timed - The network time daemon SYNOPSIS
timed [-tME] [-n | -i network] FLAGS
Specifies the names of the networks (as defined in the /etc/networks file) to be excluded from clock synchronization. Each network name that is an argument to the -i flag is added to the list of networks that the timed daemon will ignore. If the -i flag is used, timed accesses all networks to which the host is connected except for the specified networks. If neither the -i flag nor the -n flag is used, timed tries to access all the network devices connected to the local host. Do not use the -i and -n flags together. Specifies that a machine can become the time server if the master time server becomes inoperative. See the Restrictions section for more information. Overrides the input of slaves. Use the -E flag in conjunction with the -M flag. It specifies that a master timed system will not average the times of the slaves to calculate the network time. Instead, it distributes the time of its local host as the network time. This flag allows a master timed system to distribute time to a network while the network time is controlled by an outside agent (such as the Network Time Protocol (NTP)). Specifies the names of the networks (as defined in the /etc/networks file) to be included in clock synchronization. When timed is started, it gathers information about all the network devices connected to the local host. The network argument to the -n flag is the name of the network that timed should access. If the -n flag is used, only the specified networks are accessed. If neither the -n flag nor the -i flag is used, timed tries to access all the network devices connected to the local host. Do not use the -n and -i flags together. Enables tracing of messages received in /usr/adm/timed.log. DESCRIPTION
The timed daemon is not invoked at boot time by default. You can use /usr/sbin/timedsetup to configure the timed daemon. The timed daemon synchronizes the host's clock with those of other machines on the local area network that are also running the timed dae- mon. The timed daemon slows the clocks of some machines and speeds up the clocks on other machines to create an average network time. The average network time is computed from measurements of clock differences using the Internet Control Message Protocol ICMP timestamp request message. The service provided by timed is based on a master/slave (client/server) scheme. When timed is started on a machine, it asks the master timed daemon for the network time and sets the host's clock to that time. After that, the host accepts synchronization messages periodi- cally sent by the master and calls the adjtime system call to perform the needed corrections on the host's clock. The timed daemon also communicates with the date command to set the date globally, and with timedc, the timed control program. If the machine running the master ceases to function, a machine that is running the timed daemon with the -M flag becomes the new master timed daemon. Note The timed daemon is provided for compatibility. Tru64 UNIX also provides support for the Network Time Protocol through the xntpd daemon. You should use NTP for time synchronization. If you need to run both NTP and the timed daemon, you must run the timed daemon with the -E flag. If you plan to run both the timed daemon and NTP, you should also configure NTP first. RESTRICTIONS
In configurations with two or more hosts each connected to the same two or more subnetworks, only one of the host can run the timed with the -M option. FILES
Specifies the command path Contains messages traced for the timed command Contains information about the known networks RELATED INFORMATION
Commands: date(1), timedc(8), timedsetup(8) Daemons: xntpd(8) Functions: adjtime(2), gettimeofday(2) delim off timed(8)
All times are GMT -4. The time now is 01:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy