NIS to a diff subnet

[J Turner]

We have a subnet, 192.x.x.x
with a NIS server on it. It maps all the users directories, etc...
We have a new server on a diff subnet 10.x.x.x
I have been task with moving the NIS server from 192 to 10. Thet are two different machines and one subnet can not reach the other.
I have looked thru the forums and the docs I see reference are after login only!
Help, suggestions?

Thanks

[Steven E. Protter]

Shalom,

You need a router to insure connectivity between networks. That can be the standard Cisco router or a server with two NIC cards configured as a router.

IF there is ping, NIS will work.

SEP

[TTr]

> moving the NIS server from 192 to 10

Not sure what is being asked here. Are you moving the entire host, or are you transfering the NIS services from one host to another?

> Thet are two different machines and one subnet can not reach the other.

Which two machines can not reach each other? the old and new NIS servers or clients? How many clients do you have and what segment are they going to be in?

[J Turner]

There will be a new host for the NIS server to run on.
I am looking to propagate thru tape, tar, whatever all the configurations of the original nis server.
The two networks can NOT be joined together by router and or lan cards.

I have a new host, a new subnet, and I wish to retain the nis server dconfig as the clients will be migrated also.

[TTr · Accepted solution]

There is more than NIS that you need to propagate to the new server.

But for NIS alone you need to copy all the files that were used to create the NIS maps. Then you have to recreate the NIS server with "ypinit -s" and repoint all NIS clients to the new server.

It would be best if you temporarily attach the new server to 192 segment under a temp name and IP and do all the copying from the old server to the new. Then when you move it to the new segment, change the IP and reinitialize NIS.

[J Turner]

What else?
"There is more than NIS that you need to propagate to the new server"

What files?
"copy all the files that were used to create the NIS maps"

Thanks for your help

[J Turner]

Also, on the network I am moving the NIS server to there is already an NIS server.

[TTr]

> Also, on the network I am moving the NIS server to there is already an NIS server.

What are your plans with the two NIS servers? Are they going to be two separate NIS domains or are you going to combine them in one domain? You can keep the separate, no problem you have to keep track which hosts (clients) are in each domain.

The default NIS maps are listed in /etc/rc.config/namesvrs in the LONGNAMES_OPTIONS and in /usr/sbin/ypinit in the MASTER_MAPS and ALL_MAPS variables

Most of the files that are used to create the NIS maps are in /etc. The most commonly used maps are hosts, passwd, group and sometimes aliases. The remaining maps are carried along from their default state.

> What else?
> "There is more than NIS that you need to propagate to the new server"

You need to identify any custom configuration that was done on the old host and repeat that in the new server. It varies but areas to look into are all the startup config files in /etc/rc.config.d/*, additional software that were installed via swinstall or manually, /usr/local/*, printers etc.

[J Turner]

I need to close this thread.
I obviously do not have enough info.

Big thanks to all...