<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NIS master server upgrade in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696220#M586754</link>
    <description>Yes.. at step 3, it would be ..say your domain name is "engineer"&lt;BR /&gt;&lt;BR /&gt;# domainname engineer&lt;BR /&gt;# ypinit -m                       &lt;BR /&gt;=&amp;gt; Build and install the NIS DB. It'll create the DB in /var/yp/engineer&lt;BR /&gt;&lt;BR /&gt;Now start the NIS master or reboot the server.</description>
    <pubDate>Wed, 03 Apr 2002 21:51:51 GMT</pubDate>
    <dc:creator>S.K. Chan</dc:creator>
    <dc:date>2002-04-03T21:51:51Z</dc:date>
    <item>
      <title>NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696213#M586747</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am planning to upgrade the OS (cold install) of one of my NIS master server from 10.20 to 11.0. There is no NIS slave servers, but with clients. Please advice about the best and easy way to do this. Also about the important things that I need to take care about !&lt;BR /&gt;&lt;BR /&gt;Thanks in advance !&lt;BR /&gt;Shiju</description>
      <pubDate>Wed, 03 Apr 2002 16:10:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696213#M586747</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-04-03T16:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696214#M586748</link>
      <description>I had upgrade the OS of my NIS master server from 10.20 to 11.0 and I dont have problems.&lt;BR /&gt;After the upgrade, repush all maps.&lt;BR /&gt;&lt;BR /&gt;Frank.</description>
      <pubDate>Wed, 03 Apr 2002 16:15:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696214#M586748</guid>
      <dc:creator>Francois Bariselle_3</dc:creator>
      <dc:date>2002-04-03T16:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696215#M586749</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;You have violated one of the most fundamental rules of NIS - always have slave servers. You don't indicate what functions NIS are doing for your clients but whatever they are (hostname resolution, passwd, group, automount maps, services, ...) they are down for the interim. If I were doing this, I wouuld first create an NIS slave server so that the clients can continue to function normally. You can then safely upgrade your NIS master. As for what you need to save, /etc/passwd, /etc/group, /etc/services, /etc/hosts, and the master versions of any other maps like automount maps. If you have modified your yp makefile then you need a copy of it as well.&lt;BR /&gt;&lt;BR /&gt;After you finish your upgrade, you also need to enable a new slave server so that the failure of the master doesn't harm you.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 03 Apr 2002 16:38:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696215#M586749</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-04-03T16:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696216#M586750</link>
      <description>I know you will have very good backup. &lt;BR /&gt;Make sure you have your make file. All the original map files. Is your new nis server going to be same name/IP? if not all slaves will be configure again.&lt;BR /&gt;&lt;BR /&gt;Sachin</description>
      <pubDate>Wed, 03 Apr 2002 16:38:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696216#M586750</guid>
      <dc:creator>Sachin Patel</dc:creator>
      <dc:date>2002-04-03T16:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696217#M586751</link>
      <description>Thanks to all.&lt;BR /&gt;&lt;BR /&gt;Clay,&lt;BR /&gt;&lt;BR /&gt;Thanks for the help. I know it's a violation about the salve server; but this is a test site and not a big network. The actual NIS functions include passwd, group, services and automount maps. I am aware about the down time, but they wouldn't mind it. My concern is about the best upgrade step( creating fresh/new maps from the ASCII files OR preserving the old map files OR any other methods ). Also about any changes needs to do in the clients.&lt;BR /&gt;&lt;BR /&gt;Sachin,&lt;BR /&gt;&lt;BR /&gt;I will be using the same IP and hostnames.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Shiju&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 03 Apr 2002 17:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696217#M586751</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-04-03T17:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696218#M586752</link>
      <description>If you did not add any additional maps on top of the existing(default) maps that NIS manages, then this should be a straight forward migration. These are the default files that are manage by NIS. If you look at /var/yp/ypmake file in your existing NIS master you should be able to figure 'em out.&lt;BR /&gt;/etc/mail/aliases&lt;BR /&gt;/etc/auto_master&lt;BR /&gt;/etc/group&lt;BR /&gt;/etc/hosts&lt;BR /&gt;/etc/netgroup&lt;BR /&gt;/etc/netid&lt;BR /&gt;/etc/networks&lt;BR /&gt;/etc/passwd&lt;BR /&gt;/etc/protocols&lt;BR /&gt;/etc/publickey&lt;BR /&gt;/etc/rpc&lt;BR /&gt;/etc/services&lt;BR /&gt;/etc/vhe_list&lt;BR /&gt;/etc/ethers&lt;BR /&gt;/etc/netmasks&lt;BR /&gt;You need to determine yourself which files are currently managed by NIS and those are the ones you need to copy across to the 11.x system. Another thing to watch out for is /etc/rc.config.d/namesvrs. Any customized settings here needs to be used when you setup the new NIS master. So basically the process would look like ..&lt;BR /&gt;On server&lt;BR /&gt;---------&lt;BR /&gt;1) Edit /etc/rc.config.d/namesvrs.&lt;BR /&gt;2) Copy the "/etc/xxxx" files over.&lt;BR /&gt;3) Enable and start NIS master.&lt;BR /&gt;On clients&lt;BR /&gt;----------&lt;BR /&gt;1) Just restart nis.client will do.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 03 Apr 2002 21:16:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696218#M586752</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-04-03T21:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696219#M586753</link>
      <description>Thanks for the inputs !&lt;BR /&gt;&lt;BR /&gt;Chan, &lt;BR /&gt;&lt;BR /&gt;This is what I planned. So in the list you provided, the step 3) would be 'ypinit -m' and that will create the new maps on the server. Any other suggestions ?&lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;Shiju</description>
      <pubDate>Wed, 03 Apr 2002 21:47:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696219#M586753</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-04-03T21:47:28Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696220#M586754</link>
      <description>Yes.. at step 3, it would be ..say your domain name is "engineer"&lt;BR /&gt;&lt;BR /&gt;# domainname engineer&lt;BR /&gt;# ypinit -m                       &lt;BR /&gt;=&amp;gt; Build and install the NIS DB. It'll create the DB in /var/yp/engineer&lt;BR /&gt;&lt;BR /&gt;Now start the NIS master or reboot the server.</description>
      <pubDate>Wed, 03 Apr 2002 21:51:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696220#M586754</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-04-03T21:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: NIS master server upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696221#M586755</link>
      <description>...and just to add again, it really is trivial &lt;BR /&gt;to create a slave server and requires zero &lt;BR /&gt;maintenance, so no matter how small your net is&lt;BR /&gt;there is no good reason not to have one. (even&lt;BR /&gt;with only two systems I'd make one a master, and one a slave)&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Sun, 07 Apr 2002 09:14:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nis-master-server-upgrade/m-p/2696221#M586755</guid>
      <dc:creator>Steve Edmunds</dc:creator>
      <dc:date>2002-04-07T09:14:25Z</dc:date>
    </item>
  </channel>
</rss>

