I have got the solution eventually: there were 2 routing entry in my network (ent) object. routing1 was the default, which were added when the ent object was created. routing2 were added later by me. I had to remove routing1 by issuing
Code:
nim -o change -a routing1='' my-remote-network
Now it is working.
--Trifo
Moderator's Comments:
edit by bakunin: thanks for sharing your solution, but PLEASE use CODE-tags when posting code, commands, terminal output and the like. Thank you.
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)
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)
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)
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)
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)
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)
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)
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 OPENDARWIN
networks
NETWORKS(5) Linux System Administration NETWORKS(5)NAME
networks - network name information
DESCRIPTION
The file /etc/networks is a plain ASCII file that describes known DARPA networks and symbolic names for these networks. Each line repre-
sents a network and has the following structure:
name number aliases ...
where the fields are delimited by spaces or tabs. Empty lines are ignored. The hash character (#) indicates the start of a comment: this
character, and the remaining characters up to the end of the current line, are ignored by library functions that process the file.
The field descriptions are:
name The symbolic name for the network. Network names can contain any printable characters except white-space characters or the comment
character.
number The official number for this network in numbers-and-dots notation (see inet(3)). The trailing ".0" (for the host component of the
network address) may be omitted.
aliases
Optional aliases for the network.
This file is read by the route(8) and netstat(8) utilities. Only Class A, B or C networks are supported, partitioned networks (i.e., net-
work/26 or network/28) are not supported by this facility.
FILES
/etc/networks
The networks definition file.
SEE ALSO getnetbyaddr(3), getnetbyname(3), getnetent(3), netstat(8), route(8)COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
GNU /Linux 2008-09-04 NETWORKS(5)
10-16-2018
