Jet Installation Recipe - Revision history

Jetmark at 03:11, 11 January 2008

2008-01-11T03:11:00Z

Jetmark at 03:07, 11 January 2008

2008-01-11T03:07:13Z

Jetmark at 01:07, 11 January 2008

2008-01-11T01:07:50Z

Jetmark at 01:07, 11 January 2008

2008-01-11T01:07:24Z

Jetmark at 00:39, 11 January 2008

2008-01-11T00:39:16Z

Jetmark at 00:37, 11 January 2008

2008-01-11T00:37:28Z

Jetmark at 00:34, 11 January 2008

2008-01-11T00:34:29Z

Jetmark at 04:23, 10 January 2008

2008-01-10T04:23:32Z

Jetmark at 03:40, 10 January 2008

2008-01-10T03:40:30Z

Jetmark at 03:38, 10 January 2008

2008-01-10T03:38:44Z

@@ Line 145: / Line 145: @@
 .168.205.0 255.255.255.192 192.168.100.14
 .168.174.64  255.255.255.192 192.168.100.14
-.168.204.0 255.255.255.192 192.168.100.14
+.168.104.0 255.255.255.192 192.168.100.14
 Define the subnets in the JET <FONT FACE="Courier New">defaultrouters</FONT> file
@@ Line 151: / Line 151: @@
   /opt/SUNWjet/etc/defaultrouters
 .168.174.64  255.255.255.192 192.168.174.65
-.168.204.0 255.255.255.192 192.168.204.1
+.168.104.0 255.255.255.192 192.168.104.1
 .168.205.0 255.255.255.192 192.168.205.1
@@ Line 165: / Line 165: @@
   jumphost:/ root# '''dhcpconfig -N 192.168.174.64  -m 255.255.255.192 -t 192.168.174.65'''
-  jumphost:/ root# '''dhcpconfig -N 192.168.204.0 -m 255.255.255.192 -t 192.168.204.1'''
+  jumphost:/ root# '''dhcpconfig -N 192.168.104.0 -m 255.255.255.192 -t 192.168.104.1'''
   jumphost:/ root# '''dhcpconfig -N 192.168.205.0 -m 255.255.255.192 -t 192.168.205.1'''
   jumphost:/ root# '''dhtadm -A -m PXEClient:Arch:00000:UNDI:002001 -d <nowiki>':BootFile="nbp.SUNW.i86pc":BootSrvA=192.168.100.14:'</nowiki>'''

@@ Line 181: / Line 181: @@
 Setup each host template and client config
-<DL><DD>HOSTA &nbsp; [[JET_host_hosta01|hosta01 X4200]]</DD></DL>
+<DL><DD>[[JET_host_hosta01|hosta01 X4200]]</DD></DL>
-<DL><DD>HOSTF &nbsp; [[JET_host_hostf01|hostf01 T2000]]</DD></DL>
+<DL><DD>[[JET_host_hostf01|hostf01 T2000]]</DD></DL>
 When the hosts boot up they will issue a number of SUNWfmd messages as the various machine state changes are extracted from the hardware and logged. These can be ignored as they are historical and will cease once they have been worked through.

@@ Line 181: / Line 181: @@
 Setup each host template and client config
-<DL><DD>HOSTA &nbsp; [[JET_host_hosta01|hosta01 X4200]]</DD><DL></DD><DL>
+<DL><DD>HOSTA &nbsp; [[JET_host_hosta01|hosta01 X4200]]</DD></DL>
-<DL><DD>HOSTF &nbsp; [[JET_host_hostf01|hostf01 T2000]]</DD><DL>
+<DL><DD>HOSTF &nbsp; [[JET_host_hostf01|hostf01 T2000]]</DD></DL>
 When the hosts boot up they will issue a number of SUNWfmd messages as the various machine state changes are extracted from the hardware and logged. These can be ignored as they are historical and will cease once they have been worked through.

@@ Line 181: / Line 181: @@
 Setup each host template and client config
-<DL><DD>HOSTA &nbsp; [[JET_host_hosta01|hosta01 X4200]]&nbsp; &nbsp; &nbsp;[[JET_host_hostas1|hostas1 X4200]]</DD><DL></DD><DL>
+<DL><DD>HOSTA &nbsp; [[JET_host_hosta01|hosta01 X4200]]</DD><DL></DD><DL>
 <DL><DD>HOSTF &nbsp; [[JET_host_hostf01|hostf01 T2000]]</DD><DL>
 When the hosts boot up they will issue a number of SUNWfmd messages as the various machine state changes are extracted from the hardware and logged. These can be ignored as they are historical and will cease once they have been worked through.

@@ Line 3: / Line 3: @@
 This JET installation recipe steps through the exact commands needed to install JET onto a Solaris machine. In this example our jumpstart host is a X4200 running Solaris 10 8/07. It also acts as the DNS server for this particular environment.
-Most of the JET install is vanilla, you have to do these steps to make it work. The parts that introduce new steps are of course adding the DNS configs and also where we insert machine customization scripts. As well we use a <FONT FACE="Courier New">jumpstart_config.pl</FONT> script to do the hard work of tweaking the JET environment. It's written in Perl and hopefully self explanatory. It needs to be run a few times during the whole procedure, once to set up the JET server with all the mods it requires, and from then on it gets run when configuring a host as it edits the hosts templates etc. The hosts in these examples also include a few zones each and I've added a <FONT FACE="Courier New">no_zone_sysidcfg</FONT> script which will tweak the zones so that they boot up fully nstead of requiring a <FONT FACE="Courier New">zlogin -C <zone></FONT> command to be run so that all the <FONT FACE="Courier New">sysidcfg</FONT> questions can be answered. (I was surprised JET didn't do these tweaks).
+Most of the JET install is vanilla, you have to do these steps to make it work. The parts that introduce new steps are of course adding the DNS configs and also where we insert machine customization scripts. As well we use a <FONT FACE="Courier New">jumpstart_config.pl</FONT> script to do the hard work of tweaking the JET environment. It's written in Perl and hopefully self explanatory. It needs to be run a few times during the whole procedure, once to set up the JET server with all the mods it requires, and from then on it gets run when configuring a host as it edits the hosts templates etc. The hosts in these examples also include a few zones each and I've added a <FONT FACE="Courier New">no_zone_sysidcfg</FONT> script which will tweak the zones so that they boot up fully instead of requiring a <FONT FACE="Courier New">zlogin -C <zone></FONT> command to be run so that all the <FONT FACE="Courier New">sysidcfg</FONT> questions can be answered. (I was surprised JET didn't do these tweaks).
 I've altered two JET scripts slightly. The <FONT FACE="Courier New">jumpstart_config.pl</FONT> script does the mods automatically to the <FONT FACE="Courier New">/opt/SUNWjet/Products/zones/postinstall</FONT> and the <FONT FACE="Courier New">/opt/SUNWjet/Utils/S99jumpstart</FONT> JET scripts. The mods are trivial, adding a hook for the zone <FONT FACE="Courier New">sysidcfg</FONT> fixer and putting a final <FONT FACE="Courier New">init 6</FONT> on the end of the <FONT FACE="Courier New">/opt/SUNWjet/Utils/S99jumpstart</FONT> script so that the machine and zones get rebooted and come up clean.

@@ Line 7: / Line 7: @@
 I've altered two JET scripts slightly. The <FONT FACE="Courier New">jumpstart_config.pl</FONT> script does the mods automatically to the <FONT FACE="Courier New">/opt/SUNWjet/Products/zones/postinstall</FONT> and the <FONT FACE="Courier New">/opt/SUNWjet/Utils/S99jumpstart</FONT> JET scripts. The mods are trivial, adding a hook for the zone <FONT FACE="Courier New">sysidcfg</FONT> fixer and putting a final <FONT FACE="Courier New">init 6</FONT> on the end of the <FONT FACE="Courier New">/opt/SUNWjet/Utils/S99jumpstart</FONT> script so that the machine and zones get rebooted and come up clean.
-==Installation Recipie==
+==Installation Recipe==
 Get the software from the [http://www.sun.com/bigadmin/content/jet/ JET website].<BR>

←Older revision		Revision as of 00:34, 11 January 2008
Line 1:		Line 1:
	[[Documents\|Parent]]		[[Documents\|Parent]]
		+
		+	This JET installation recipe steps through the exact commands needed to install JET onto a Solaris machine. In this example our jumpstart host is a X4200 running Solaris 10 8/07. It also acts as the DNS server for this particular environment.
		+
		+	Most of the JET install is vanilla, you have to do these steps to make it work. The parts that introduce new steps are of course adding the DNS configs and also where we insert machine customization scripts. As well we use a <FONT FACE="Courier New">jumpstart_config.pl</FONT> script to do the hard work of tweaking the JET environment. It's written in Perl and hopefully self explanatory. It needs to be run a few times during the whole procedure, once to set up the JET server with all the mods it requires, and from then on it gets run when configuring a host as it edits the hosts templates etc. The hosts in these examples also include a few zones each and I've added a <FONT FACE="Courier New">no_zone_sysidcfg</FONT> script which will tweak the zones so that they boot up fully nstead of requiring a <FONT FACE="Courier New">zlogin -C <zone></FONT> command to be run so that all the <FONT FACE="Courier New">sysidcfg</FONT> questions can be answered. (I was surprised JET didn't do these tweaks).
		+
		+	I've altered two JET scripts slightly. The <FONT FACE="Courier New">jumpstart_config.pl</FONT> script does the mods automatically to the <FONT FACE="Courier New">/opt/SUNWjet/Products/zones/postinstall</FONT> and the <FONT FACE="Courier New">/opt/SUNWjet/Utils/S99jumpstart</FONT> JET scripts. The mods are trivial, adding a hook for the zone <FONT FACE="Courier New">sysidcfg</FONT> fixer and putting a final <FONT FACE="Courier New">init 6</FONT> on the end of the <FONT FACE="Courier New">/opt/SUNWjet/Utils/S99jumpstart</FONT> script so that the machine and zones get rebooted and come up clean.
		+
		+	==Installation Recipie==

	Get the software from the [http://www.sun.com/bigadmin/content/jet/ JET website].<BR>		Get the software from the [http://www.sun.com/bigadmin/content/jet/ JET website].<BR>

@@ Line 173: / Line 173: @@
 Setup each host template and client config
-<DL><DD>HOSTA &nbsp; [[Public_JET_host_hosta01|hosta01 X4200]]&nbsp; &nbsp; &nbsp;[[Public_JET_host_hostas1|hostas1 X4200]]</DD><DL></DD><DL>
+<DL><DD>HOSTA &nbsp; [[JET_host_hosta01|hosta01 X4200]]&nbsp; &nbsp; &nbsp;[[JET_host_hostas1|hostas1 X4200]]</DD><DL></DD><DL>
-<DL><DD>HOSTD &nbsp; [[Public_JET_host_hostd01|hostd01 T2000]]&nbsp; &nbsp; &nbsp;[[Public_JET_host_hostd02|hostd02 T2000]]</DD><DL>
+<DL><DD>HOSTD &nbsp; [[JET_host_hostd01|hostd01 T2000]]&nbsp; &nbsp; &nbsp;[[JET_host_hostd02|hostd02 T2000]]</DD><DL>
-<DL><DD>HOSTF &nbsp; [[Public_JET_host_hostf01|hostf01 T2000]]</DD><DL>
+<DL><DD>HOSTF &nbsp; [[JET_host_hostf01|hostf01 T2000]]</DD><DL>
 When the hosts boot up they will issue a number of SUNWfmd messages as the various machine state changes are extracted from the hardware and logged. These can be ignored as they are historical and will cease once they have been worked through.

@@ Line 20: / Line 20: @@
   jumphost:/ root# '''umask'''
 Install and run the [[Public_Jet_Config_Script|jumpstart configuration script]] to setup the jumpstart environment.
@@ Line 156: / Line 148: @@
 Setup DHCP subsystem. Will be site specific for your subnets.
   jumphost:/ root# '''dhcpconfig -D -r SUNWfiles -p /data/dhcp'''
   Created DHCP configuration file.

←Older revision		Revision as of 03:38, 10 January 2008
Line 21:		Line 21:
	22		22

−	Create the directories for JET and DHCP. Adjust ~~path names~~ for your site. Note these pathnames are used in the scripts and commands etc, so search and replace if you need to.	+	Create the directories for JET and DHCP. Adjust pathnames for your site. Note these pathnames are used in the scripts and commands etc, so search and replace if you need to.

	jumphost:/ root# '''mkdir /data/dhcp'''		jumphost:/ root# '''mkdir /data/dhcp'''