tag:blogger.com,1999:blog-9847050620222441322024-03-12T19:23:39.313-07:00Puny GeekLitmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-984705062022244132.post-36302188795471938502013-03-04T08:21:00.004-08:002013-03-04T08:24:11.863-08:00The long and winding road (AKA Installing a Windows 2008 R2 SQL Cluster) - Part 5<h2>
Installing the second node in the SQL cluster </h2>
now on to the second node. Mount sql installation disc, run setup and this time choose <strong>add node to a sql server failover cluster</strong><br />
the installation process is much simpler, you will have to choose to
which cluster add this node, you should be ok with default values here<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8JyOilvk-Yn7W1afWYDxUfKmrsekBFQAPy8VJ03LNPRQdlfSPVbE5c2151AJeJjSrtOY4UDol0B1YDYM5iqgL42JV1I92p2TytnIUwJr5wUq-Xzz387wJQVTL1QXM5sTPe_ekPyHPS00/s1600/81-install+sql+secondary1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8JyOilvk-Yn7W1afWYDxUfKmrsekBFQAPy8VJ03LNPRQdlfSPVbE5c2151AJeJjSrtOY4UDol0B1YDYM5iqgL42JV1I92p2TytnIUwJr5wUq-Xzz387wJQVTL1QXM5sTPe_ekPyHPS00/s1600/81-install+sql+secondary1.png" height="158" width="400" /></a></div>
<br />
next, you will need to specify with which users to run sql services,
even here you should be ok with default values, you will need just to
type the password of the accounts you chose earlier<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZStCudqZJXINeW7-FkIWCCFrfZONBd4__0v0TunzlE-rE4fKGOi5DY4j_wY-U4pfbOUjVGLoP8zvp5TMSlUj_o8gB-128X4mrzDDmnt1uzI1_MKhRjTrBD6DRpSnxGUIEo-pYuWNXLpc/s1600/82-install+sql+secondary2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhZStCudqZJXINeW7-FkIWCCFrfZONBd4__0v0TunzlE-rE4fKGOi5DY4j_wY-U4pfbOUjVGLoP8zvp5TMSlUj_o8gB-128X4mrzDDmnt1uzI1_MKhRjTrBD6DRpSnxGUIEo-pYuWNXLpc/s1600/82-install+sql+secondary2.png" height="152" width="400" /></a></div>
<br />
that's it, after clicking next a couple of times, installation will start<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6gYii4jExAO0F6gYPKqG4eux65LXEm8gb7ktk9VyWIxu1vVroRSzCepU5Cxq3QA2leJ57IzRPBSodDfWK_roxrq_wL2d3gVl3VC_ETTXuMkduey4yyP_EewpSr8ptBG13bcw5t6spPbU/s1600/83-install+sql+secondary3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6gYii4jExAO0F6gYPKqG4eux65LXEm8gb7ktk9VyWIxu1vVroRSzCepU5Cxq3QA2leJ57IzRPBSodDfWK_roxrq_wL2d3gVl3VC_ETTXuMkduey4yyP_EewpSr8ptBG13bcw5t6spPbU/s1600/83-install+sql+secondary3.png" height="153" width="400" /></a></div>
<br />
and you are done. Now if you open the <strong>Failover Cluster Manager</strong> tool and connect to this cluster, you will see your clustered SQL server and you can start installing your db.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhMdgi6HA3z-8hDHkgd_2_WFfK5ujo6a4ZNdjKhrOnZNDtDHQJpXsYRHqn-lC25KwzPP39Y374xRd5M5wdoNoIxFGs77ZVjNRTVfZld4UtPOE8ND3eSTGgD5QxVEgjh3aFDrQHRekw8UcM/s1600/final-sql+cluster+configured.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhMdgi6HA3z-8hDHkgd_2_WFfK5ujo6a4ZNdjKhrOnZNDtDHQJpXsYRHqn-lC25KwzPP39Y374xRd5M5wdoNoIxFGs77ZVjNRTVfZld4UtPOE8ND3eSTGgD5QxVEgjh3aFDrQHRekw8UcM/s1600/final-sql+cluster+configured.png" height="426" width="640" /></a></div>
<br />
<br />
<br />
<br />
<br />Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-33833152112596220822013-03-04T08:19:00.005-08:002013-03-04T08:24:03.195-08:00The long and winding road (AKA Installing a Windows 2008 R2 SQL Cluster) - Part 4<h2>
Installing a one-node SQL cluster</h2>
To install SQL, we will need to install it on both nodes of the cluster,
but the option to choose when installing, changes slightly.<br />
<br />
Check in the failover cluster manager what active node of the cluster, you can do so by looking at the value of the <strong>current host server</strong> in the main page. Go to that machine, mount the SQL 2008 R2 iso and start installation<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxyxwtbi3ObnhoSEl0EWRsYWRVA0G0lwZRkUH_5EHtCjekgU1kr4_JOXxW6VBHTy3lJEUW9-fBm3VBuEiBGPMxNqgKdIwrx4gR3caL5MP3-74NFavY0eFcuEYXp7bpAhR_o1v4z92Nv3M/s1600/70-install+sql.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxyxwtbi3ObnhoSEl0EWRsYWRVA0G0lwZRkUH_5EHtCjekgU1kr4_JOXxW6VBHTy3lJEUW9-fBm3VBuEiBGPMxNqgKdIwrx4gR3caL5MP3-74NFavY0eFcuEYXp7bpAhR_o1v4z92Nv3M/s1600/70-install+sql.png" height="150" width="400" /></a></div>
<br />
<br />
on this node, you will need to choose the option <strong>new SQL server failover cluster installation</strong>. When we are going to install sql to the secondary cluster node, you will choose <strong>add node to a sql server failover cluster</strong>, very simple.<br />
SQL Setup will run some checks that you should pass, click ok and move on.<br />
You will need to enter a product key, which is already specified in
the installation package you downloaded from msdn, no need to hunt for
it. You accept license agreement and install setup files, just click ok.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkWHgDC9jkgfhvg0avKWrM-CrGADWkjPOcMWrkKXOYtIXJoQVn0NAlkTsnNBpUnA2dZiNZfwb5PHQcVrEhgw10xHQPwhgY8McoOuLxANB6o5aVTEFbYYuT7PDCYC-LfOZ23Wnq3xL7GEY/s1600/71-install+sql2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgkWHgDC9jkgfhvg0avKWrM-CrGADWkjPOcMWrkKXOYtIXJoQVn0NAlkTsnNBpUnA2dZiNZfwb5PHQcVrEhgw10xHQPwhgY8McoOuLxANB6o5aVTEFbYYuT7PDCYC-LfOZ23Wnq3xL7GEY/s1600/71-install+sql2.png" height="271" width="400" /></a></div>
<br />
even if you did everything by the book there are still a couple of
warnings, nothing to worry about. Go on and click next where you will be
asked which features you want install<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfLYo2nBjoMchB_iDHFDoR21fqztFIIfpQVnJfPugv2IsHRVuZQyIYHQldVHJhagXRgqYBHJKx667aOU7cqCnhgyffkLZHQAvdtTEDHN6yyxhflCZprAeGpWhF-jNDD2FFv8S9HyBx8gY/s1600/72-install+sql3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfLYo2nBjoMchB_iDHFDoR21fqztFIIfpQVnJfPugv2IsHRVuZQyIYHQldVHJhagXRgqYBHJKx667aOU7cqCnhgyffkLZHQAvdtTEDHN6yyxhflCZprAeGpWhF-jNDD2FFv8S9HyBx8gY/s1600/72-install+sql3.png" height="273" width="400" /></a></div>
<br />
next you will be asked to specify a network name for the sql server and
you can choose if to install the default instance or a named one. The
instance root directory needs to remain on C, do not change the location
to the shared disks.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJrO5-no1HgYCU6MryUmHGCH5Le1D5WkS5Ld6bdhRJXTknHRejpttZ3JPHpiNpuwS_yjRRV5ZaInyuUb0eY1CwOmdhoWqFZvTg3DrkFhRdcuqjIjrYxyvfrSJ699AeIV1AH9t_3jbp0GE/s1600/73-install+sql4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJrO5-no1HgYCU6MryUmHGCH5Le1D5WkS5Ld6bdhRJXTknHRejpttZ3JPHpiNpuwS_yjRRV5ZaInyuUb0eY1CwOmdhoWqFZvTg3DrkFhRdcuqjIjrYxyvfrSJ699AeIV1AH9t_3jbp0GE/s1600/73-install+sql4.png" height="270" width="400" /></a></div>
<br />
after a couple of clicks, you will get to this page where you can choose
the sql server cluster resource group. Although as you can see there
are a couple of red dots that seem to point to errors, leave the default
and click next<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5QATAVAhIxw7xRfbNKwY9FIauOVs5WmO6p9hPE155jDFlpQIVO9ZPLlBHDwwd4d8_iLLxS_v33g6N_ydats4U-xCDbtazf94qmm6qV4Q_knhY8MiwNgCtjaPBZwffd_fFMNdWsmqr5dY/s1600/74-install+sql5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5QATAVAhIxw7xRfbNKwY9FIauOVs5WmO6p9hPE155jDFlpQIVO9ZPLlBHDwwd4d8_iLLxS_v33g6N_ydats4U-xCDbtazf94qmm6qV4Q_knhY8MiwNgCtjaPBZwffd_fFMNdWsmqr5dY/s1600/74-install+sql5.png" height="203" width="400" /></a></div>
<br />
you will be asked on which shared disk to install the sql server
resource cluster group, you have only one available, so nothing to
choose here<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwDAs1aKyxV4CbtZjk-c0VeGXFY9dLiLvCuy7kFYR27PbPO8SgYrxRDXdlJuHciVAO0JwPjusCVzKrME1C3mnvztYSz-nGmab_gKdO-ccp5hWEADOGC52QJAWkbxitdiFQNePFKr3EYqs/s1600/75-install+sql6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhwDAs1aKyxV4CbtZjk-c0VeGXFY9dLiLvCuy7kFYR27PbPO8SgYrxRDXdlJuHciVAO0JwPjusCVzKrME1C3mnvztYSz-nGmab_gKdO-ccp5hWEADOGC52QJAWkbxitdiFQNePFKr3EYqs/s1600/75-install+sql6.png" height="202" width="400" /></a></div>
<br />
at this point you will be asked for an ip to assign to the sql cluster. We chose initially 10.1.2.5<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgioHSeYTUOdh-PzOyLDkgYeyH0Epvp-FjOOAsSTYTNfJltbA5kTjdzY0RO-jhHXCneyYqzntoRqKwlkx-4hbYVpq8y56UyAwphQVEY4ZegGLaogVRFB8_Y7q5LbdFRML9qRYhFF0ixnoQ/s1600/76-install+sql7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgioHSeYTUOdh-PzOyLDkgYeyH0Epvp-FjOOAsSTYTNfJltbA5kTjdzY0RO-jhHXCneyYqzntoRqKwlkx-4hbYVpq8y56UyAwphQVEY4ZegGLaogVRFB8_Y7q5LbdFRML9qRYhFF0ixnoQ/s1600/76-install+sql7.png" height="201" width="400" /></a></div>
<br />
next you will need to choose security policy, leave default and choose simply next.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZI6DAj-2lMGb5JWVEcBdryrFgBUUg8i94h8qcDLYcHxMeJi9q6GA8so9LyjsU3zoRARLlDoKzgNw7445ShkHQBgDtorj0856mYCBojN24i-NyjI1u5zY0TR8mZT4NX3ECRYBtDgFBLfE/s1600/77-install+sql8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZI6DAj-2lMGb5JWVEcBdryrFgBUUg8i94h8qcDLYcHxMeJi9q6GA8so9LyjsU3zoRARLlDoKzgNw7445ShkHQBgDtorj0856mYCBojN24i-NyjI1u5zY0TR8mZT4NX3ECRYBtDgFBLfE/s1600/77-install+sql8.png" height="200" width="400" /></a></div>
<br />
next, it's time to define with which users should run SQL services. It
is recommended to use domain users, and that is where those two users
created earlier on the domain controller come handy. You also have to
specify the password you chose for them.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3CrO1w_9vg2mCiCvLpBkyZipxh_LWtvtE6AtWQCAnHUMXlVI8Tndplhfu6tvIA0ytQRBUw4qwy_CX07_zGLnVf7__tUKjbZuzpWx2Yss6vs-q020OLn7gCKmqSlBHZq-_eVsdsrSHYXg/s1600/78-install+sql9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi3CrO1w_9vg2mCiCvLpBkyZipxh_LWtvtE6AtWQCAnHUMXlVI8Tndplhfu6tvIA0ytQRBUw4qwy_CX07_zGLnVf7__tUKjbZuzpWx2Yss6vs-q020OLn7gCKmqSlBHZq-_eVsdsrSHYXg/s1600/78-install+sql9.png" height="200" width="400" /></a></div>
<br />
next you can choose whether to adopt sql or mixed authentication and define administrators<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTUm2_n231P9yieihvjlYzQzVMnoZNODNlkgKif5-PAhgzFbiLXFlB1_ew8rD-feYMr5xdMAtDgBxwL4qwRe9FCe435FDUWeau6-0BABqcGVCiXwnYe4KKZ9iG-zt1ZPK5pyrst0iSRQI/s1600/79-install+sql10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTUm2_n231P9yieihvjlYzQzVMnoZNODNlkgKif5-PAhgzFbiLXFlB1_ew8rD-feYMr5xdMAtDgBxwL4qwRe9FCe435FDUWeau6-0BABqcGVCiXwnYe4KKZ9iG-zt1ZPK5pyrst0iSRQI/s1600/79-install+sql10.png" height="268" width="400" /></a></div>
<br />
The next screens are not very interesting you can just choose default settings and click next, until installation ends<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8YTDdyzaZVf9NBs3Fp1NbA1l3KN90UJeyX65bNrzNj9m7_XlzJnroW4_cO-Lto1xvJK8d5nwdGB-Ixvk_e4TVtEkbhGk7Ygg6JB6R9-GnuWxPLKB-dN70ZeALsHalEWSn90fkDkhCGkU/s1600/80-install+sql11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8YTDdyzaZVf9NBs3Fp1NbA1l3KN90UJeyX65bNrzNj9m7_XlzJnroW4_cO-Lto1xvJK8d5nwdGB-Ixvk_e4TVtEkbhGk7Ygg6JB6R9-GnuWxPLKB-dN70ZeALsHalEWSn90fkDkhCGkU/s1600/80-install+sql11.png" height="215" width="400" /></a></div>
<br />
<br />
congratulations, you installed a one-node sql cluster!! now onto last part<br />
<br />
<br />
<br />
<br />Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-25420876838313716522013-03-04T08:16:00.004-08:002013-03-04T08:23:50.960-08:00The long and winding road (AKA Installing a Windows 2008 R2 SQL Cluster) - Part 3<br />
<h2>
Changing the binding order of NICs on cluster members</h2>
At this point you should have a domain controller up and running, the
two cluster members still in the workgroup and you should have installed
and configured Freenas.<br />
<br />
As next step, you can join the cluster members to the domain you just
created, I won't explain how to do it, all you need is the domain
administrator password you set up previously.<br />
<br />
There is one additional step that needs to be done before installing
the cluster. Cluster members have two NICs. The public one, meaning the
one on Vmnet5 in my case, needs to be the first one in the list of
interfaces. To do so:<br />
<br />
Click on <strong>Start</strong>, right-click on <strong>Network</strong> and select <strong>properties</strong>. This brings you to the <strong>Network and sharing center</strong> window<br />
<br />
click on <strong>Change adapter settings</strong>. in this new window press the <strong>ALT</strong> key, this brings up this drop-down menu. You need to select <strong>Advanced/advanced settings</strong><br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgn18HaOkQRjRtYk7oi83d77cM2u1nSjGsENgu5XcfAtFR7MsUIhuRBWdpJk86VMRmeGBK3x0_ygP_Hzkm5uKEy50ZA6wkgtgduQcE8Huiy3IE-OoaqdT_zuJt3UIXVym1-bsXNlW9PHmI/s1600/51-ordine+interfacce+1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgn18HaOkQRjRtYk7oi83d77cM2u1nSjGsENgu5XcfAtFR7MsUIhuRBWdpJk86VMRmeGBK3x0_ygP_Hzkm5uKEy50ZA6wkgtgduQcE8Huiy3IE-OoaqdT_zuJt3UIXVym1-bsXNlW9PHmI/s1600/51-ordine+interfacce+1.png" height="128" width="400" /></a></div>
<br />
In the window that opens, you can change the order of the interfaces and put the one on Vmnet5 at the top.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGbNsFhscBqL9ufUOdQVL-Dh50RT8RVdzmjyOAJtv4lq3lrMmfOD-D_oEKb9_xSoWrYEcEZUqyuM7de6farYYj3ryeb6bJEHDqWTfsTLS_bxUBfYAbYdBMpPx_5giZtiITPbge4_1I8Ko/s1600/52-ordine+interfacce+2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGbNsFhscBqL9ufUOdQVL-Dh50RT8RVdzmjyOAJtv4lq3lrMmfOD-D_oEKb9_xSoWrYEcEZUqyuM7de6farYYj3ryeb6bJEHDqWTfsTLS_bxUBfYAbYdBMpPx_5giZtiITPbge4_1I8Ko/s1600/52-ordine+interfacce+2.png" height="350" width="400" /></a></div>
<br />
<br />
NOTE: This needs to be done on both cluster members.<br />
<br />
<br />
<h2>
Connecting to the shared drives</h2>
On one of the cluster members, click <strong>start/administrative tools/iSCSI initiator</strong>, you will get this warning<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhby4omlYW3yRcSKqVZ0wwhYlBEaxrUEn6iwKR-UicFUU4-RGyDlDL9VZHS0JPftNXZuuPbj6tFV8uZzuvB0bYBdKm0ChoEVDWJNUU28y4gwwZhtkeGyVQol-1COZ4EHIGJ_weC2xNlVVs/s1600/53-connectingtofreenas1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhby4omlYW3yRcSKqVZ0wwhYlBEaxrUEn6iwKR-UicFUU4-RGyDlDL9VZHS0JPftNXZuuPbj6tFV8uZzuvB0bYBdKm0ChoEVDWJNUU28y4gwwZhtkeGyVQol-1COZ4EHIGJ_weC2xNlVVs/s1600/53-connectingtofreenas1.png" height="156" width="400" /></a></div>
<br />
go ahead and start the service, after that you will get to this window<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi63ETW8LC-Q95BboWN-ADZw_aSE5manGBQX51S5qRnT5AQlRhJTReMw_ue8HPlcFx_CCRKN2uEd1eswI6bAMEtClycCZxDBi5l-2NMnVNzFK7ivq6MTaUvOmai11BHLrycoLeogmfp_B8/s1600/54-connectingtofreenas2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi63ETW8LC-Q95BboWN-ADZw_aSE5manGBQX51S5qRnT5AQlRhJTReMw_ue8HPlcFx_CCRKN2uEd1eswI6bAMEtClycCZxDBi5l-2NMnVNzFK7ivq6MTaUvOmai11BHLrycoLeogmfp_B8/s1600/54-connectingtofreenas2.png" height="400" width="362" /></a></div>
<br />
type the ip of freenas as shown in picture and click <strong>quick connect</strong><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBngF1XadNYT891G2MalLR6nA3rReWEMH-QOHLvBDnS1Tp6rvkJyFBwl6DZZb0BmFsojh4j_YIyQbT9M648QfVq9EM4x-_cw1dHaXat5HHW-YtX6pbk3DF62OjsCDGJqa00_MgdC1hfak/s1600/55-connectingtofreenas3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBngF1XadNYT891G2MalLR6nA3rReWEMH-QOHLvBDnS1Tp6rvkJyFBwl6DZZb0BmFsojh4j_YIyQbT9M648QfVq9EM4x-_cw1dHaXat5HHW-YtX6pbk3DF62OjsCDGJqa00_MgdC1hfak/s1600/55-connectingtofreenas3.png" height="400" width="357" /></a></div>
<br />
<br />
The windows machine connects to the Freenas server via iSCSI and shows you the two available disks.<br />
Now connect to both one by one, the status of them changes from "inactive" to "connected", now you can click done.<br />
<br />
Goto the <strong>volumes and devices</strong> tab and click <strong>auto-configure</strong>, here is how it will look after you do so<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgME5Neu77HHTxFPj2IKjd9i71dmXNWTuxxMLbCdy0fu_dckYUHQ7wyzMOWsvLrqEtiqYvSaXoeyea3-lHdT6Qqhk7S7MI6OSh6u-uRfRVYDfZzLnKmXkU0bPDvFe2iuKM6hNVPYWsMOH0/s1600/56-connectingtofreenas4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgME5Neu77HHTxFPj2IKjd9i71dmXNWTuxxMLbCdy0fu_dckYUHQ7wyzMOWsvLrqEtiqYvSaXoeyea3-lHdT6Qqhk7S7MI6OSh6u-uRfRVYDfZzLnKmXkU0bPDvFe2iuKM6hNVPYWsMOH0/s1600/56-connectingtofreenas4.png" height="400" width="352" /></a> </div>
<br />
<br />
Clicking the Auto Configure button will make sure that at reboot the server will reconnect to the two shared drives.<br />
Now we need to format the new two drives and give it a name, so head over to the disk management tool (<strong>start/right-click computer/manage/storage/disk management</strong>)<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhHYNLh_LiMyvYcFJpkMduuTID2V73BHDpXliTamGTj2eDUucV4M5hn0TioEWGeLPmKcXrcoFZOWRPAmip-MD8Xj-BhdGk2BIwPu81maN3agBcHqosL7TauRQMKpOPxdqa1eZfOk5MHH6Y/s1600/57-connectingtofreenas5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhHYNLh_LiMyvYcFJpkMduuTID2V73BHDpXliTamGTj2eDUucV4M5hn0TioEWGeLPmKcXrcoFZOWRPAmip-MD8Xj-BhdGk2BIwPu81maN3agBcHqosL7TauRQMKpOPxdqa1eZfOk5MHH6Y/s1600/57-connectingtofreenas5.png" height="335" width="400" /></a></div>
<br />
the disks are available although offline and not formatted. Right-click on disk1 and select <strong>online</strong><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOqJXv-YmbHw3TgOe3plDZPTRUjSV2BBktBJ0N5sdrO_SUUcNSbrkH3NS51O8Mm4tIJRYzrstMDLOstwpLJvBUPXzMZQcVvSsnupaJr0a8P1UjErZmaFrcOvVIdM8oO4LE18Zmp6KLuaA/s1600/58-connectingtofreenas6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjOqJXv-YmbHw3TgOe3plDZPTRUjSV2BBktBJ0N5sdrO_SUUcNSbrkH3NS51O8Mm4tIJRYzrstMDLOstwpLJvBUPXzMZQcVvSsnupaJr0a8P1UjErZmaFrcOvVIdM8oO4LE18Zmp6KLuaA/s1600/58-connectingtofreenas6.png" height="167" width="400" /></a></div>
<br />
right-click again on disk1 and select <strong>initialize disk</strong>, leave further options as default<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiee50zIoETI4vVOfXctubja2gNIGlld5jYqj9CJZRzaQPh6NOMDjXSDKfrSxcput0PFaRXtXkU_ztfbRw62tOT7zuCPLbUCB2JHNyA5gxcS0e9JG7Y780TRFrKm3ZKUVYLJfvenFOXvtE/s1600/59-connectingtofreenas7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiee50zIoETI4vVOfXctubja2gNIGlld5jYqj9CJZRzaQPh6NOMDjXSDKfrSxcput0PFaRXtXkU_ztfbRw62tOT7zuCPLbUCB2JHNyA5gxcS0e9JG7Y780TRFrKm3ZKUVYLJfvenFOXvtE/s1600/59-connectingtofreenas7.png" height="186" width="400" /></a></div>
<br />
now you can format the disk and assign a drive letter to it. I left all
options as default. Repeat for disk 2. if you want you can also rename
the disks here. Here is how it will look after it is done.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhF12vnJdFQFz1j38Ru-qEppPVFlVvO2Tr1AIW9EzkIIuJsCvp1qI97opKL9W-yGxv66K6ScUy3vi6HvS1UhvmKLIs_HLJ6WK3XdFbqAt3ommROatrIefQLJdM3rdtvuDOpKpalSv_HX3E/s1600/60-connectingtofreenas8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhF12vnJdFQFz1j38Ru-qEppPVFlVvO2Tr1AIW9EzkIIuJsCvp1qI97opKL9W-yGxv66K6ScUy3vi6HvS1UhvmKLIs_HLJ6WK3XdFbqAt3ommROatrIefQLJdM3rdtvuDOpKpalSv_HX3E/s1600/60-connectingtofreenas8.png" height="191" width="400" /></a></div>
<br />
<br />
You will need to bring the disks offline now and repeat the steps with
Iscsi initiator and disk management tool on the other cluster machine.
In the case of the disk management tool, you will just need to bring the
disks online and they should get a drive letter automatically and be
ready to be used.<br />
<br />
<br />
<br />
<h2>
Installing and configuring the cluster</h2>
At this point your
cluster members should be in the domain, share two disks installed on a
nas and everything should be ready to install the clustering software
(not the sql cluster, we are not there yet).<br />
<br />
On both cluster members, click on <strong>start/right-click on computer/select manage/select features/add features and select failover clustering</strong><br />
<strong><br /></strong>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRuyKQdDwAqexWlRa_Yn_k4DDEf8xRfYrURgfEhqP_A8fwrVsE8WlUMOSWi6jxjdbvqYDLjtGPyoavm_DUrsmytA_dmOT7DSedBTRO-XpWCjlm3wDuvBEg-OnNU0eGUNASUy0fAo0goYA/s1600/61-configuringcluster1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRuyKQdDwAqexWlRa_Yn_k4DDEf8xRfYrURgfEhqP_A8fwrVsE8WlUMOSWi6jxjdbvqYDLjtGPyoavm_DUrsmytA_dmOT7DSedBTRO-XpWCjlm3wDuvBEg-OnNU0eGUNASUy0fAo0goYA/s1600/61-configuringcluster1.png" height="293" width="400" /></a></div>
<br />
click next and go on with the installation.<br />
<br />
You will need to logoff at this point and login again on one of the
cluster members because to access the failover cluster manager tool, you
need to be logged in with a valid domain account. Administrator will
do.<br />
<br />
On one of the cluster members, click <strong>start/administrative tools/failover cluster manager</strong><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiVJrpaQq0OZ2G7r1y4RmjQFUy99DSAsGmJmTg2f4FKcyxuSvXl8iEmqP8l6GwpgQHEMlJhoV5x_cKgssB_9l61kjUwh8lGOwUYYOyR_Rd8tLju67z9yROfkHnHiFwvlJ0AnupZi-w55DM/s1600/62-configuringcluster2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiVJrpaQq0OZ2G7r1y4RmjQFUy99DSAsGmJmTg2f4FKcyxuSvXl8iEmqP8l6GwpgQHEMlJhoV5x_cKgssB_9l61kjUwh8lGOwUYYOyR_Rd8tLju67z9yROfkHnHiFwvlJ0AnupZi-w55DM/s1600/62-configuringcluster2.png" height="320" width="400" /></a></div>
<br />
first thing we will need to do is validate the configuration, so click
on the appropriate link, add cluster members and run all the tests.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6b_Ma0yzQmdmtajVIPJXUP-1su578IV9wjFvToW5O9qSXSPYBeBNYqHTpfQv6gv17L9JD20pZvg0y12aR5queqqfNMWfkX_R2sF14uumiOsS2RY2R9VjZzfIbLB8PjSrYeGFCR1Zcyj0/s1600/63-configuringcluster3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6b_Ma0yzQmdmtajVIPJXUP-1su578IV9wjFvToW5O9qSXSPYBeBNYqHTpfQv6gv17L9JD20pZvg0y12aR5queqqfNMWfkX_R2sF14uumiOsS2RY2R9VjZzfIbLB8PjSrYeGFCR1Zcyj0/s1600/63-configuringcluster3.png" height="275" width="400" /></a></div>
<br />
<br />
NOTE: you might get an error stating that "open remote registry
failed" when you add the two nodes. In this case, try to add the nodes
one by one. I'm not sure where this error comes from, t happened to me
when I tried to add both members at the same time by browsing the AD
computer group.<br />
the tests will run for a few minutes, after which if you did everything correct you will get here.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEheXOZbHgz602VtXYtSByzzQ1QtwGLM8SUl5Jv3qRqRYeXwrYPR1d0o1xNxtJ6pQ1x-yv7-tySyON__IcJcJdQxrk7Vv1PRJpV2NxHKx0oqBXjPY86BZnDjHZ-p-KgR3OqZLnKxWKw36iY/s1600/64-configuringcluster4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEheXOZbHgz602VtXYtSByzzQ1QtwGLM8SUl5Jv3qRqRYeXwrYPR1d0o1xNxtJ6pQ1x-yv7-tySyON__IcJcJdQxrk7Vv1PRJpV2NxHKx0oqBXjPY86BZnDjHZ-p-KgR3OqZLnKxWKw36iY/s1600/64-configuringcluster4.png" height="277" width="400" /></a></div>
<br />
<br />
you can view the report if you want. now you can click on create a
cluster. you will need to select servers as you did during validation.<br />
<br />
you will need to assign a name to the cluster and an ip address for
management. Remember that the public network is on vmnet5. After that
you will just need to click next a couple of times and wait a couple of
minutes.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLjldn0d_rOaP7-weByIJ_eefYk6rXmeyZmAyECYUqlLJ72KVzpbO6uySmVOm-Dx2z9I7TD5RHYaMAZ73HiJ6GpNh1ws8tnaUISC_kP1Ro2mhUAFuZlN2RyqR0at4aQrRYwUUgi8u3oxA/s1600/65-configuringcluster5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhLjldn0d_rOaP7-weByIJ_eefYk6rXmeyZmAyECYUqlLJ72KVzpbO6uySmVOm-Dx2z9I7TD5RHYaMAZ73HiJ6GpNh1ws8tnaUISC_kP1Ro2mhUAFuZlN2RyqR0at4aQrRYwUUgi8u3oxA/s1600/65-configuringcluster5.png" height="265" width="400" /></a></div>
<br />
going forward, you will be asked to click next a couple of times and get to this screen when the cluster is installed<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvMCgKNdAl7hqxMpUittaggDHeH1NmEiEGc7EcIJ7_jjg6e_Oymi9Q6jXU2Lrtie1Z7g__EfJOM38ybv6cGuEDwZq-grIGSR1Vmhw71H9PuteCzDf47-71q2H1uzECCbd7kfx8JRfOXQY/s1600/66-configuringcluster6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvMCgKNdAl7hqxMpUittaggDHeH1NmEiEGc7EcIJ7_jjg6e_Oymi9Q6jXU2Lrtie1Z7g__EfJOM38ybv6cGuEDwZq-grIGSR1Vmhw71H9PuteCzDf47-71q2H1uzECCbd7kfx8JRfOXQY/s1600/66-configuringcluster6.png" height="201" width="400" /></a></div>
<br />
after that, when you open the failover clustering tool and connect to the cluster you created, you will see this<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGuIuJIobxwNtTJvBTJTTNnQTDBYpvjWF3deym_GgcGT7zQh1LkxfVHeTq4OlXOr7Qk6Herv3JYvHB1cnITLQzr1cyItmUEROBaudrPK_DNLUIvMqdCnhQz0GPsoXXWPSlpKyHUOHi6ZM/s1600/67-configuringcluster7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhGuIuJIobxwNtTJvBTJTTNnQTDBYpvjWF3deym_GgcGT7zQh1LkxfVHeTq4OlXOr7Qk6Herv3JYvHB1cnITLQzr1cyItmUEROBaudrPK_DNLUIvMqdCnhQz0GPsoXXWPSlpKyHUOHi6ZM/s1600/67-configuringcluster7.png" height="245" width="400" /></a></div>
<br />
here you can failover the active node (current host server) and check
the status of everything. Congratulations! You are now the happy owner
of a cluster.<br />
<br />
<h2>
Last steps before installing sql (almost there)</h2>
Before installing SQL, there is still two things that need to be done
<br />
<ul>
<li>
On the domain controller, create two regular domain users that will be used to run SQL services, I called mine <strong>sqlserver</strong> and <strong>sqlagent</strong>.
I won't go into details on this task, should be pretty straight forward
using the appropriate administrative tool (hint, it is called <strong>active directory users and computers</strong> and it is under <strong>administrative tools</strong>)</li>
<li>
On the two cluster machines, install .NET framework 3.5 SP1.</li>
</ul>
Fortunately, this last part can be done through the <strong>Add Features</strong> page, no need to hunt down installation packages.<br />
Click on <strong>Start, right-click on Computer </strong>and choose <strong>manage</strong>. Scroll down to the features section and click on <strong>Add Features.</strong><br />
You don't need to install the whole package, otherwise you will be
asked to install IIS too, just select the same as in the picture.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhr8O-bLZ-VntJ6-xDF49JIu7gsch6Sri8YoQei_hHxgeAm-5XMJ4H5PEZURiV6ytc9qXLUu8eCzHGh4Z5q0QBpaNQs9d5NfQFs1P9t3b1SkbAZbqtRFqlUkDVKyZU7jyz5Oe30iz0uq6Q/s1600/68-install+net+framework+1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhr8O-bLZ-VntJ6-xDF49JIu7gsch6Sri8YoQei_hHxgeAm-5XMJ4H5PEZURiV6ytc9qXLUu8eCzHGh4Z5q0QBpaNQs9d5NfQFs1P9t3b1SkbAZbqtRFqlUkDVKyZU7jyz5Oe30iz0uq6Q/s1600/68-install+net+framework+1.png" height="286" width="400" /></a></div>
<br />
Click next a couple of times.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNEWrg3rGOKJOxif3kbi3-mfiS5yQz_FwdwcsCDTrGhhEMF51vJrL87k_HHon0cD-Puh1pNs5sB1j-VTaQM3G46UcVvkAjoeSEIR0uxVaRepIZiS6OHgEUuGSaaXZWiQGb9KekFEFO17M/s1600/69-install+net+framework+2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNEWrg3rGOKJOxif3kbi3-mfiS5yQz_FwdwcsCDTrGhhEMF51vJrL87k_HHon0cD-Puh1pNs5sB1j-VTaQM3G46UcVvkAjoeSEIR0uxVaRepIZiS6OHgEUuGSaaXZWiQGb9KekFEFO17M/s1600/69-install+net+framework+2.png" height="118" width="400" /></a></div>
<br />
there, you are ready to install SQL. On to the next part<br />
<br />Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com1tag:blogger.com,1999:blog-984705062022244132.post-72774977912551493092013-03-04T08:12:00.002-08:002013-03-04T08:23:41.070-08:00The long and winding road (AKA Installing a Windows 2008 R2 SQL Cluster) - Part 2<br />
Let's put aside for a bit our Windows machines and install Freenas.
Freenas manages the shared disk that the cluster will use to host SQL's
DBs.
<br />
<br />
You need to create a new virtual machine for it and mount the iso you downloaded earlier<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlxpYOHvVLM7gyG7glgJrkhhlDv2H564llqSxbSUsjcJOV-KW6Ls4AcNydXAwuT6nfYPAh6DsMv1GH8BE4Zc-Rjp3YhaXATb7JP7_e8-Zm5mmNH1dHqWfYKmUqw81kjrjlaQl9p_7m5ag/s1600/23-freenas1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlxpYOHvVLM7gyG7glgJrkhhlDv2H564llqSxbSUsjcJOV-KW6Ls4AcNydXAwuT6nfYPAh6DsMv1GH8BE4Zc-Rjp3YhaXATb7JP7_e8-Zm5mmNH1dHqWfYKmUqw81kjrjlaQl9p_7m5ag/s1600/23-freenas1.png" height="361" width="400" /></a></div>
<br />
In the next menu, as guest OS choose <strong>Other/Freebsd 64-bit</strong><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_3n2aYP1dTv4QsyAreAQyeC3Yh0H6LgJOxL_E1x7tl2ni-Kegb1Insa0swk1ERLf_aIrpJuIKxOTqJuc2x5Cd3joUoB4_Ow8uW6F_KwjvqOZQMoWjjaDrb0Z1gQj8RF9i3LLsJv3yF04/s1600/24-freenas2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi_3n2aYP1dTv4QsyAreAQyeC3Yh0H6LgJOxL_E1x7tl2ni-Kegb1Insa0swk1ERLf_aIrpJuIKxOTqJuc2x5Cd3joUoB4_Ow8uW6F_KwjvqOZQMoWjjaDrb0Z1gQj8RF9i3LLsJv3yF04/s1600/24-freenas2.png" height="267" width="400" /></a></div>
<br />
Assign 1 GB of RAM to the machine<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjINBOLyXeYFSAPtvWSLVXUZxpmdz4AfFtNPhms60mCXxeidRTTqNh6zFg7nGzVcaIZoVzj80sOnokWLFSh1bow81GVYhJCnXD2pF_Tfiia_4-03zCf5dDwA14htRs1uWZoQnaEYQY-lJY/s1600/25-freenas3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjINBOLyXeYFSAPtvWSLVXUZxpmdz4AfFtNPhms60mCXxeidRTTqNh6zFg7nGzVcaIZoVzj80sOnokWLFSh1bow81GVYhJCnXD2pF_Tfiia_4-03zCf5dDwA14htRs1uWZoQnaEYQY-lJY/s1600/25-freenas3.png" height="330" width="400" /></a></div>
<br />
Regarding network configuration, we don't really care about it at this
point. If you select NAT, the first time the machine boots it will get
an ip address through DHCP, otherwise the DHCP requests will time out
but you will be able to configure the machine through Vmware's console
connection. In any case, we will put it later into the correct virtual
network and assign the correct IP address to it. In my case, I set it to
<strong>use host-only networking</strong><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUklYuCfQZmy4ZOCufhIx71sQGYrvl6FQo71eGNYLLrszEbqWTzl8miQOkmwqROaP521sFAe6qmIRtXLM6S1Ddkk01GpcZeTLE35ZdJL78RmYbQdyiVuJSXyXnBot4stBijxQ6f7N8wV8/s1600/26-freenas4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUklYuCfQZmy4ZOCufhIx71sQGYrvl6FQo71eGNYLLrszEbqWTzl8miQOkmwqROaP521sFAe6qmIRtXLM6S1Ddkk01GpcZeTLE35ZdJL78RmYbQdyiVuJSXyXnBot4stBijxQ6f7N8wV8/s1600/26-freenas4.png" height="276" width="400" /></a></div>
<br />
We will assign a disk size of 2GB. This disk will be used for the
Freenas OS, we will need additional disks for storage. They will be
added at a later point.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7AN5l1qJ_r7jnc08tXh5At0nZEB8CsxNIT0Gyhnm5io-NSA-SaT39ZYJrKVd8B9L5WlQxayGwC5xogTrizJ3_UeEW9bm6lbW-7LDOSSdkKAmri-6KeITaYHaPrXVSoq6O86F9HoDVZuY/s1600/27-freenas5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj7AN5l1qJ_r7jnc08tXh5At0nZEB8CsxNIT0Gyhnm5io-NSA-SaT39ZYJrKVd8B9L5WlQxayGwC5xogTrizJ3_UeEW9bm6lbW-7LDOSSdkKAmri-6KeITaYHaPrXVSoq6O86F9HoDVZuY/s1600/27-freenas5.png" height="361" width="400" /></a></div>
<br />
Before finishing the setup process, we will have the chance to change
virtual network in which to put the NIC and put it in the cluster
internal network.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZw06Tic45nwp0tJf_A75BCdcB84leKWJmreoZMS4XvnekSJouxytR_DyHNHhbjqY54DwqnbbJf1kTyhejQdSC-NGJlHcs_W1PqClYw4DBoeXYwOj5PhKpgWRV9jQL-TIDmtFEy9c7Hv8/s1600/28-freenas6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZw06Tic45nwp0tJf_A75BCdcB84leKWJmreoZMS4XvnekSJouxytR_DyHNHhbjqY54DwqnbbJf1kTyhejQdSC-NGJlHcs_W1PqClYw4DBoeXYwOj5PhKpgWRV9jQL-TIDmtFEy9c7Hv8/s1600/28-freenas6.png" height="187" width="400" /></a></div>
<br />
When you boot the machine and reach this screen don't do anything, it will automatically boot the default option, which is fine<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhXGuE4ucTPStJTv_5x9gUY65BQVaGKSFJefrkK7099pBhktauZOiTJOahw_OFGeZOoklDPRN0TB_xQzMajQaYUY1uJleY0BOmUOI8FtdWhU2e5P3kcpy_SrGrUjkzWtwBjMj6atGRYkvU/s1600/29-freenas7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhXGuE4ucTPStJTv_5x9gUY65BQVaGKSFJefrkK7099pBhktauZOiTJOahw_OFGeZOoklDPRN0TB_xQzMajQaYUY1uJleY0BOmUOI8FtdWhU2e5P3kcpy_SrGrUjkzWtwBjMj6atGRYkvU/s1600/29-freenas7.png" height="196" width="400" /></a></div>
<br />
To install Freenas, choose the first option<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAoKA2xyOBg470pelGUJO7Ftm6cink3K5SojmMF_HEKjfpsCl3yCiEJlqTDJhgyesLqmyoFtLBGkb-QA7Zhjt8f16dQkHZ1DFJhIExGUSFw0E7r4SIIg9UeXPlOMwq1GCUIL8vrTrbd-4/s1600/30-freenas8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAoKA2xyOBg470pelGUJO7Ftm6cink3K5SojmMF_HEKjfpsCl3yCiEJlqTDJhgyesLqmyoFtLBGkb-QA7Zhjt8f16dQkHZ1DFJhIExGUSFw0E7r4SIIg9UeXPlOMwq1GCUIL8vrTrbd-4/s1600/30-freenas8.png" height="120" width="400" /></a></div>
<br />
Right now we have only a disk connected to this machine and we will install Freenas on that one<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilLo03Ob-T2j6C655TRCyVOK7C7jCqru_clqwIrs0asz7XMBLEd40LUA1JBusBPo2J8XxLTSeqGX7geMu8CGz-SbtLcpKgV2YqVLlhVlHlVd5rGC0gmq3AF6UTfeSsAgCTBOHdmGqxlw4/s1600/31-freenas9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEilLo03Ob-T2j6C655TRCyVOK7C7jCqru_clqwIrs0asz7XMBLEd40LUA1JBusBPo2J8XxLTSeqGX7geMu8CGz-SbtLcpKgV2YqVLlhVlHlVd5rGC0gmq3AF6UTfeSsAgCTBOHdmGqxlw4/s1600/31-freenas9.png" height="111" width="400" /></a></div>
<br />
We will receive a warning that we can safely ignore<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWZ38XdnQitoVPn2i_J8lfFxjBUdeqFyQ6L2J-e4o2NcZSK6o71KEeNE031f7QRPXvt0tLvCoTy2VSHI7RGaxuLFRb4XMDjJDhlQneVwt2AmrsP0wkZyxFsKHJHcjexaxLNLLOXzrazow/s1600/32-freenas10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWZ38XdnQitoVPn2i_J8lfFxjBUdeqFyQ6L2J-e4o2NcZSK6o71KEeNE031f7QRPXvt0tLvCoTy2VSHI7RGaxuLFRb4XMDjJDhlQneVwt2AmrsP0wkZyxFsKHJHcjexaxLNLLOXzrazow/s1600/32-freenas10.png" height="128" width="400" /></a></div>
<br />
When the installation process finishes, you will get this message. I suggest you shutdown <strong>and</strong> <strong>then</strong>
remove the CDROM. I had all sort of interesting errors when I tried to
do it the way that this message seems to suggest or rebooted with the cd
still in.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgGNsVl8tzbQVBc-0GxbnaGwznHjh2yGDVmua8U4suKFiKkXlttfUWKKNOwDov3q52HwiQktTCroNSvNON981xcm-qFOyfWAvLwMgbkWR9HCCU5iQylRxfgh6rSmvDT1RwBtozmGbjdcPg/s1600/33-freenas11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgGNsVl8tzbQVBc-0GxbnaGwznHjh2yGDVmua8U4suKFiKkXlttfUWKKNOwDov3q52HwiQktTCroNSvNON981xcm-qFOyfWAvLwMgbkWR9HCCU5iQylRxfgh6rSmvDT1RwBtozmGbjdcPg/s1600/33-freenas11.png" height="61" width="400" /></a></div>
<br />
As I was saying earlier, when you reboot, the OS will try to get an ip
from DHCP, so it will take a bit before you get to the configuration
menu. Here you can set up the network interface, which is the only thing
we care at this point.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjILb4hF31tdZ6Ri8TTD2pE2SpukvAa0Li1YQCJo7sgJOy3Gm8eIjSD7NUXYDJF940oomtE7CWVbuGE3spGS78HdFD4SSIvhprhOTOD71PzaHim8uYN5grY0hU-xvHcKs6OjFbOmrrvBi0/s1600/34-freenas12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjILb4hF31tdZ6Ri8TTD2pE2SpukvAa0Li1YQCJo7sgJOy3Gm8eIjSD7NUXYDJF940oomtE7CWVbuGE3spGS78HdFD4SSIvhprhOTOD71PzaHim8uYN5grY0hU-xvHcKs6OjFbOmrrvBi0/s1600/34-freenas12.png" height="275" width="400" /></a></div>
<br />
Here you can see all the options I chose to configure the IP. After that you will be able to reach the LMI through the address <strong>http://10.1.1.3</strong> from one of the 2 cluster machines<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjPBISiDw8ny4nZbPQpTqkwLUgBoBzwZizIUAptxd37WmYN59jL8XYgV4X2zl8R2nyAG0HI8HImIqfd6EfD-e01-3SgXuACk2dsle-LppLK2P5O7PLDdob4VRCl0KmxBEqz1x1C_SfkzAQ/s1600/35-freenas13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjPBISiDw8ny4nZbPQpTqkwLUgBoBzwZizIUAptxd37WmYN59jL8XYgV4X2zl8R2nyAG0HI8HImIqfd6EfD-e01-3SgXuACk2dsle-LppLK2P5O7PLDdob4VRCl0KmxBEqz1x1C_SfkzAQ/s1600/35-freenas13.png" height="273" width="400" /></a></div>
<br />
The welcome from the LMI, by default there is no password authentication enabled.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjsPq5l1Rva_YPUDUbpGBB2y7kz-lCPfAYZa1ppm0NJG7Xu7Rhv_rh5AWkzj-uEoRtBkUVjsm1lglz_7i_IZdX8pzxPcHuHb80BCSdXEXs-vBL29Z9hRkAGFbU-p-FEQrhrBn3sBkG23AQ/s1600/36-freenas14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjsPq5l1Rva_YPUDUbpGBB2y7kz-lCPfAYZa1ppm0NJG7Xu7Rhv_rh5AWkzj-uEoRtBkUVjsm1lglz_7i_IZdX8pzxPcHuHb80BCSdXEXs-vBL29Z9hRkAGFbU-p-FEQrhrBn3sBkG23AQ/s1600/36-freenas14.png" height="228" width="400" /></a></div>
<br />
At this point we will go back the virtual machine settings and add 2
additional disks to it. You don't need to shutdown the machine to do so,
just head over to settings and add two SCSI disks, a small 4GB one and a
bigger where you will install your DBs. I'll make mine 10GB.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhM1yXlEWSeheVSpSGPv4CGLgZTrdFa07LGD7SA77gy1QzMeVbOStIxBUZXrAvFXltwydNjqquVi534O7k8O69ahKFTgRiqhuHeU1eq6nzTIcYZNHS6uM3WwNljGEYkH8v2zTxNKAM-SQw/s1600/37-freenas15.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhM1yXlEWSeheVSpSGPv4CGLgZTrdFa07LGD7SA77gy1QzMeVbOStIxBUZXrAvFXltwydNjqquVi534O7k8O69ahKFTgRiqhuHeU1eq6nzTIcYZNHS6uM3WwNljGEYkH8v2zTxNKAM-SQw/s1600/37-freenas15.png" height="191" width="400" /></a></div>
<br />
If you go back to the console connection, you will notice that Freenas
will automatically detect the change. You can see here my two disks,
called da1 (4Gb) and da2 (10gb).<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTX77V_Owx_8rYJ-6NUSVnvXH1bt6BAMVDTidaY1QaSFKVMkFewttNgqSJDE-c8CjNhrZvwXGvDuY_BBPqOjbdtMwcLPdiYeb6jW5T6mgYaQmlOQiVrocmhmMJ4BbAtl7BR9YKS9Sx0k0/s1600/38-freenas16.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTX77V_Owx_8rYJ-6NUSVnvXH1bt6BAMVDTidaY1QaSFKVMkFewttNgqSJDE-c8CjNhrZvwXGvDuY_BBPqOjbdtMwcLPdiYeb6jW5T6mgYaQmlOQiVrocmhmMJ4BbAtl7BR9YKS9Sx0k0/s1600/38-freenas16.png" height="251" width="400" /></a></div>
<br />
Let's go back to the LMI and click on the <strong>Storage</strong> button on the ribbon at the top of the LMI. This will open this tab where we will create two volumes, one called <strong>quorum</strong> and one called <strong>storage</strong>.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhC6X2grzVdoRuD0qt9aFJ4IIJKOXYxPsXocQGiLG45XAGqHwmiii3V1kCOWVba3nfOyOmF_LU9rgGV2f2hBVnO0omMv-QB1qLceh4v1wvVkadHflBwtIydwpqdEtasIT8xlxgBiV3J4aY/s1600/39-freenas17-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhC6X2grzVdoRuD0qt9aFJ4IIJKOXYxPsXocQGiLG45XAGqHwmiii3V1kCOWVba3nfOyOmF_LU9rgGV2f2hBVnO0omMv-QB1qLceh4v1wvVkadHflBwtIydwpqdEtasIT8xlxgBiV3J4aY/s1600/39-freenas17-2.png" height="216" width="400" /></a></div>
<br />
The quorum volume is used by the cluster for internal operations.
Details are cloudy and complicated. The only things you need to know is
that it cannot be used as shared storage and that it does not need to be
very big. Click on the <strong>Create Volume</strong> button and choose these options for the two disks.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgATnE_V0LrRtMrxgWPdo3hAM7P_QGMdWE2OPDDUEKmHW3mXJJTj-TkOiVXmtKn6-hhAmtdzwBwArXoXhpYn-tl1OemLXplhClasxKjofO3f3na35vUXByEzD9YcHO6N62zGYCX_4IuIBI/s1600/40-freenas18+%25282%2529.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgATnE_V0LrRtMrxgWPdo3hAM7P_QGMdWE2OPDDUEKmHW3mXJJTj-TkOiVXmtKn6-hhAmtdzwBwArXoXhpYn-tl1OemLXplhClasxKjofO3f3na35vUXByEzD9YcHO6N62zGYCX_4IuIBI/s1600/40-freenas18+%25282%2529.png" height="360" width="400" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgXd8oLa3ZxuqLdPQSpw3N0CcXWgTuy5mjz_8Dojq4-yp1cQkGMSsHZ3zx1Ef_y4fn7gbYJTYOGLOtB60TBpk87ZyEfrJBXR4SgR0t91uKlUi7LOrhRwSnlLV7ja2pm74hGt4wMO_21d8/s1600/41-freenas19+%25282%2529.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgXd8oLa3ZxuqLdPQSpw3N0CcXWgTuy5mjz_8Dojq4-yp1cQkGMSsHZ3zx1Ef_y4fn7gbYJTYOGLOtB60TBpk87ZyEfrJBXR4SgR0t91uKlUi7LOrhRwSnlLV7ja2pm74hGt4wMO_21d8/s1600/41-freenas19+%25282%2529.png" height="346" width="400" /></a></div>
<br />
Here is how the storage tab will look after you created the two volumes.
You can notice that Freenas reserves 2GB of space on each volume for
its management.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghFhQKqCFgmyjJ7XLFFnUw30y-ReL-Sbuh2bwSV7sDm6EQ_O1Fz1-v5uJrKxgiQdpDaekTQxAsPLCCdx-w3cYMD5V0NKOOzxVigpTNB6DhmMmafFp6HYhH62c5lSgcMFsKdHRxcxt6EdM/s1600/42-freenas20-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEghFhQKqCFgmyjJ7XLFFnUw30y-ReL-Sbuh2bwSV7sDm6EQ_O1Fz1-v5uJrKxgiQdpDaekTQxAsPLCCdx-w3cYMD5V0NKOOzxVigpTNB6DhmMmafFp6HYhH62c5lSgcMFsKdHRxcxt6EdM/s1600/42-freenas20-2.png" height="207" width="400" /></a></div>
<br />
Now that we created our the volumes that will be used by the cluster, we
need to configure Freenas so that it knows how the cluster members will
connect to it. We will use <a href="http://en.wikipedia.org/wiki/Iscsi" target="_blank">iSCSI</a> for that. Click on the <strong>Services</strong>
button, scroll at the bottom of the list and enable iSCSI. After doing
this, click on the little monkey wrench icon close to it to define the
connection parameters.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhm_xXdz5sy1uWS668joE4MtNAqXEkJfzBHbs4nz3YgcUJKvebMozffcD9W6fswu0RDRT5Qgu4Hs_LhvSa8KwQRHJXFzzczi8QeLrGdsYHm24xeGegpY0Y9qurcbrol8N0mP0Ow1B1Kg9I/s1600/43-freenas21-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhm_xXdz5sy1uWS668joE4MtNAqXEkJfzBHbs4nz3YgcUJKvebMozffcD9W6fswu0RDRT5Qgu4Hs_LhvSa8KwQRHJXFzzczi8QeLrGdsYHm24xeGegpY0Y9qurcbrol8N0mP0Ow1B1Kg9I/s1600/43-freenas21-2.png" height="268" width="400" /></a></div>
<br />
<br />
There are several options in the tab, like extents, associated targets
and so on. It's a pity that there is no wizard, you will need to
configure them one by one.<br />
<br />
The first one that needs to be configured is <strong>Portals</strong>.
This will tell Freenas on which IP it should listen for incoming
connections. You will need to create a rule like the one in this picture
with the IP of the Freenas server and the port on which to listen,
which by default is TCP 3260. Click <strong>Add Portal</strong> to create the rule<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvZVgI4yk1XKA5UzuH7SlfDIE-NVxy_fwbx4usibv-rDu6FD7O5dsNQ4nbCJbLzP_4pSe1CQjzDQrM0Al38Xltzl56FQtksGcnQIyVYCYMW_abCLyr1AT5VxTK4CwpEpp1lzI9_-ylSrg/s1600/44-freenas22-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvZVgI4yk1XKA5UzuH7SlfDIE-NVxy_fwbx4usibv-rDu6FD7O5dsNQ4nbCJbLzP_4pSe1CQjzDQrM0Al38Xltzl56FQtksGcnQIyVYCYMW_abCLyr1AT5VxTK4CwpEpp1lzI9_-ylSrg/s1600/44-freenas22-2.png" height="140" width="400" /></a></div>
<br />
<br />
Next you will need to define who can connect to the volumes you created earlier. To do so, click on the <strong>Authorized Initiator</strong> button and create a rule with these parameters<br />
<ul>
<li>
Initiators: <strong>ALL</strong><br />
</li>
<li>
Authorized Network: <strong>10.1.1.0/24</strong> or whatever your cluster internal network is<br />
</li>
</ul>
This will allow access to the NAS from the whole cluster internal network<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDNS6JYZhJ4tbGHI4wFrXP9dEqAUUfw9EjMPRd2ZJWEOkYEWBhXXlpvHJm-Qt_zza9Xc9WknyR93Pirpen_JckSCrC9_R7HGtIuQOohmZxQBatvJ-RVsvjNj91PGQqCahvPA_fVKAkPPg/s1600/45-freenas23-3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjDNS6JYZhJ4tbGHI4wFrXP9dEqAUUfw9EjMPRd2ZJWEOkYEWBhXXlpvHJm-Qt_zza9Xc9WknyR93Pirpen_JckSCrC9_R7HGtIuQOohmZxQBatvJ-RVsvjNj91PGQqCahvPA_fVKAkPPg/s1600/45-freenas23-3.png" height="133" width="400" /></a></div>
<br />
<br />
Now that we defined who can connect, we need to define what they can connect to. Click on the <strong>Targets</strong> button and create two rules, one for each of the disks. The parameters to use in the first rule will be<br />
<ul>
<li>
Target Name: quorum</li>
<li>
Target Alias: quorum</li>
<li>
Type: Disk</li>
<li>
Portal Group ID: 1</li>
<li>
Initiator Group ID: 1</li>
</ul>
The name and alias can be whatever you like. The type is pretty
self-explanatory. Portal group and initiator group IDs refer to the two
rules we defined earlier. The second target rule for the storage disk
will be the same, except for the target and alias names. The rest of the
options that you see here can be left as default.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjP68OngLvHN_GNfIbCNuIarXnnta-eNaw3FkJK3zJ8yYIJP8t3OVL0-hnOonaqTJ6ZCuw7AkPZVSNK_42EMht0_pD7pda4HHt6empkCynAloBtZ8-RQrduIFaWrmCK5NCz8uJ8O3qIP-I/s1600/46-freenas24+%25282%2529.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjP68OngLvHN_GNfIbCNuIarXnnta-eNaw3FkJK3zJ8yYIJP8t3OVL0-hnOonaqTJ6ZCuw7AkPZVSNK_42EMht0_pD7pda4HHt6empkCynAloBtZ8-RQrduIFaWrmCK5NCz8uJ8O3qIP-I/s1600/46-freenas24+%25282%2529.png" height="400" width="367" /></a></div>
<br />
<br />
Now that we created targets, we need to map them to some disks. To do so, click on <strong>Extents</strong> and create two rules:<br />
<ul>
<li>
Extent Name: <strong>extent0</strong></li>
<li>
Path to the extent: <strong>/mnt/quorum/quorum</strong></li>
<li>
Extent size: <strong>1GB</strong></li>
</ul>
<br />
<ul>
<li>
Extent Name: <strong>extent1</strong></li>
<li>
Path to the extent: <strong>/mnt/storage/storage</strong></li>
<li>
Extent size: <strong>7GB</strong></li>
</ul>
NOTE: you will need to partially type the path, since the file named
quorum in the folder named quorum does not exist and will be created
when you create the extent. The path which is required here is to a
filename, not a folder. The sizes specified here are slightly less than
the space available on the volumes for simplicity, if you want to
specify thousands of MB instead of GB, you can do it. Just hover close
to the box with the mouse and you will see the available keywords.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0oqWYOgAMtvHtUay2tOlVV6MjD7gWAhkE4VcNN3ddgn8gBFj6s2q9rUGNH0mPyLL-GzGCPm-AkxMU5Aw1aGlNEPm1-vkpMRLTOS_H0yQjEFhuD24FlA1g13NsZWaf2xIbDvULaCwDiM4/s1600/47-freenas25+%25282%2529.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh0oqWYOgAMtvHtUay2tOlVV6MjD7gWAhkE4VcNN3ddgn8gBFj6s2q9rUGNH0mPyLL-GzGCPm-AkxMU5Aw1aGlNEPm1-vkpMRLTOS_H0yQjEFhuD24FlA1g13NsZWaf2xIbDvULaCwDiM4/s1600/47-freenas25+%25282%2529.png" height="241" width="400" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjj_xVFAmhJ1BowcMi6wTGQWUgxaoVyEcCvLDn5v1JkAl54EKAXf_nGxav9DUEM_ovR6X2ipQ9IRwx86_IrmTPnQhY88e3SqeWEfFffQLQ59ZH5YTLwzBlIOQnKF04lewyQt7tnTvEbmls/s1600/48-freenas26.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjj_xVFAmhJ1BowcMi6wTGQWUgxaoVyEcCvLDn5v1JkAl54EKAXf_nGxav9DUEM_ovR6X2ipQ9IRwx86_IrmTPnQhY88e3SqeWEfFffQLQ59ZH5YTLwzBlIOQnKF04lewyQt7tnTvEbmls/s1600/48-freenas26.png" height="241" width="400" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxHKL8oUUO5AepVm8S88sqOFj6E3Zzl0xP4J6LKmAjU5y0apgx8Nb_jmT5lHWNCe6YM5Axg5Dv1wGy8w9OB76V0fM_QFrO3GJm-jwtiLkOT5C3xD20yJ8kU23fGrhyWNTo0LVqLSNbVdY/s1600/49-freenas27-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhxHKL8oUUO5AepVm8S88sqOFj6E3Zzl0xP4J6LKmAjU5y0apgx8Nb_jmT5lHWNCe6YM5Axg5Dv1wGy8w9OB76V0fM_QFrO3GJm-jwtiLkOT5C3xD20yJ8kU23fGrhyWNTo0LVqLSNbVdY/s1600/49-freenas27-2.png" height="182" width="400" /></a></div>
<br />
Now we need to map Targets and Extents. Click on <strong>Associated Targets</strong> and create two rules that do exactly this:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiq_Y9uBJNjj4aq__EcG7JhUH37Wv-w6ifD75iHMpMtsJ5FbhDmlAJGjph03Q8LIn18Mw1q3VNsjW5H-ap97KF44l0e3v-HTetNGiRTXHjoxc2rVQbyIUrEWbt1sbwzEHS3zkJbuS0JpNY/s1600/50-freenas28-2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiq_Y9uBJNjj4aq__EcG7JhUH37Wv-w6ifD75iHMpMtsJ5FbhDmlAJGjph03Q8LIn18Mw1q3VNsjW5H-ap97KF44l0e3v-HTetNGiRTXHjoxc2rVQbyIUrEWbt1sbwzEHS3zkJbuS0JpNY/s1600/50-freenas28-2.png" height="181" width="400" /></a></div>
<br />
<br />
<br />
That's it, we are done on Freenas. No need to save or whatever. Disks are ready to be accessed remotely from cluster members.<br />
<br />
Head for your cluster members and connect via iSCSI to the remote drives. See part 3 on how to do it<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-88217920890608286832013-03-04T07:56:00.003-08:002013-03-04T08:23:32.395-08:00The long and winding road (AKA Installing a Windows 2008 R2 SQL Cluster) - Part1<div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
In this article, we'll talk about what we need, we'll install all the Windows machines needed and the domain controller as well. We'll talk about IP addressing plan as well.<br />
<br />
You will need the following ISOs:<br />
<ul>
<li>
Windows Server 2008 R2 with Service Pack 1 (x64) - DVD (filename en_windows_server_2008_r2_with_sp1_x64_dvd_617601.iso)<br />
</li>
<li>
SQL Server 2008 R2 Enterprise (x86, x64, ia64) - DVD (filename
en_sql_server_2008_r2_enterprise_x86_x64_ia64_dvd_520517.iso)<br />
</li>
<li>
FreeNAS-8.0.3-RELEASE-p1-x64.iso<br />
</li>
</ul>
You can get the first two from <a href="http://msdn.microsoft.com/en-us/subscriptions">MSDN</a>, the third one from the <a href="http://www.freenas.org/" target="_blank">Freenas website</a>.<br />
<br />
You will need three Windows 2008 licenses, two for the datacenter
edition, one for the enterprise edition.<br />
<br />
You can get these too from the <a href="http://msdn.microsoft.com/en-us/subscriptions" target="_blank">MSDN</a> website. I guess you could use other versions of Windows 2008 R2 as well.<br />
<br />
The virtual lab will be composed of 4 machines:<br />
<ul>
<li>One domain controller
installed on windows 2008 enterprise</li>
<li>Two cluster members on windows
2008 datacenter. </li>
<li>A fourth machine will be used to install the NAS that
the cluster members share.</li>
</ul>
<br />
You will need to setup two virtual networks, one for the management of
the cluster and to make the cluster reachable from other machines, the
second network will be used for replication/communication between
cluster members and the NAS.<br />
<br />
The hardware requirements for the virtual machines are as follows<br />
<br />
Domain Controller and cluster members<br />
<ul>
<li>
RAM: 2GB</li>
<li>
HD: 40GB</li>
<li>
2 NIC</li>
</ul>
Freenas<br />
<ul>
<li>
RAM: 1GB</li>
<li>
HD1: 2GB (this will be used to install the OS)</li>
<li>
HD2: 4GB (this will be used as the quorum disk of the cluster)</li>
<li>
HD3: 4GB at least (2.5GB are reserved by the OS, the rest will be
used as storage)</li>
<li>
1 NIC</li>
</ul>
As virtualization software, I used VMWare workstation 7. The whole lab
runs pretty smoothly on a Lenovo W510 laptop, as long as you have at least 12GB of RAM
and the new i7 CPUs.<br />
<br />
<h2>
Installing the domain controller and the cluster members</h2>
I won't spend much time on this topic, we should all be able to install
windows on a virtual machine. The only thing to keep in mind is that we
might want to update the VMs before installing the cluster and/or the
domain controller software. To do so, the machines will need access to
the internet, at least in this initial phase. After Installing the
windows updates, we can move the NICs of the machines to some other
virtual network. I'll just put here a couple of pictures of the menus
during the installation of the VM, where the installation options we
need diverge from the standard options. <br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_bJhdfhu0sTUR43vFg_QXK6uhvsbtBtrYb_CS2F1LUrjPgEqtFQbF6U1yveD5MLWJ83dRYaY-NlE8a0GaiL9E86AByMr8jy0Z3HQf88PdrUJJQT1QYXvM8JpWs2CgBct6p36EQFJVBuA/s1600/New+virtual+machine+wizard+-+guest+os+installation+-+1.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_bJhdfhu0sTUR43vFg_QXK6uhvsbtBtrYb_CS2F1LUrjPgEqtFQbF6U1yveD5MLWJ83dRYaY-NlE8a0GaiL9E86AByMr8jy0Z3HQf88PdrUJJQT1QYXvM8JpWs2CgBct6p36EQFJVBuA/s1600/New+virtual+machine+wizard+-+guest+os+installation+-+1.png" height="360" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><br /></td></tr>
</tbody></table>
we choose the ISO with the Windows 2008 R2 software<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
</div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJMePqjOIwc16fEH4oQUOKkg_VVn3EERrYGNEO2rADIt-ZQbfZp3gOW5sG3gKg9I0LoaWjCvCecujIS9VQ6LA-lGv47UzN4ZmotnaQbpjq8umvCKQ5YKW1qv599rPoAbhtrxfu_i7i1DA/s1600/2-New+virtual+machine+wizard+-+memory+for+the+vm+-+3.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiJMePqjOIwc16fEH4oQUOKkg_VVn3EERrYGNEO2rADIt-ZQbfZp3gOW5sG3gKg9I0LoaWjCvCecujIS9VQ6LA-lGv47UzN4ZmotnaQbpjq8umvCKQ5YKW1qv599rPoAbhtrxfu_i7i1DA/s1600/2-New+virtual+machine+wizard+-+memory+for+the+vm+-+3.png" height="361" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><br /></td></tr>
</tbody></table>
The machines will need 2GB of RAM<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhnJRaySXbOk4YBDI-V5xT6FW20UflLtsxietk3wg82R4jYUEj_GB_mdgX7ySPH620FyH73XtYsH_nL6_D7V6kB4tqIJYhw-8YFwct3sczHvm-4Bz6lCkpAdj3oPoxVY639pdSyV2KVAA4/s1600/3-New+virtual+machine+wizard+-+network+configuration+%2528initial%2529+-+4.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhnJRaySXbOk4YBDI-V5xT6FW20UflLtsxietk3wg82R4jYUEj_GB_mdgX7ySPH620FyH73XtYsH_nL6_D7V6kB4tqIJYhw-8YFwct3sczHvm-4Bz6lCkpAdj3oPoxVY639pdSyV2KVAA4/s1600/3-New+virtual+machine+wizard+-+network+configuration+%2528initial%2529+-+4.png" height="361" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><br /></td></tr>
</tbody></table>
We will set initially the NIC to NAT, so that we can download Windows updates and activate the machines<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0zXQmfJzBkTQ5VNWKpvICsAXFS8KW8G0kfTTuwp9pTle5mBU5BL6hW0Cqeq-b67g_nWtBQ6unZAB3r_rN86VEmpZKTPqnS6HkWWsQdB1fB9qr5oz_2Cy8xXAxM8pEiaJZ76GDwJzFybE/s1600/4-New+virtual+machine+wizard+-+ready+to+create+virtual+machine+-+6.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0zXQmfJzBkTQ5VNWKpvICsAXFS8KW8G0kfTTuwp9pTle5mBU5BL6hW0Cqeq-b67g_nWtBQ6unZAB3r_rN86VEmpZKTPqnS6HkWWsQdB1fB9qr5oz_2Cy8xXAxM8pEiaJZ76GDwJzFybE/s1600/4-New+virtual+machine+wizard+-+ready+to+create+virtual+machine+-+6.png" height="361" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><br /></td></tr>
</tbody></table>
<br />
Before creating the VM, remember to add another NIC, by clicking the "customize hardware" button<br />
<br />
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUOraMxpI2e8qYe5OFZVH5W9vQ9sIhDXW6409X6-IHMr_R9FiMp2FY8PLJF4cmv4uFHw0C2Dg1aSYXKbLa2hELvmkpA0K_BOGUFyhOFrQpqNVfxCxT0F9Bwhudbqx2MaMI-SuYjuhGN0o/s1600/5-New+virtual+machine+wizard+-+add+additional+nic+and+put+it+on+hostonly+network+-+7.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjUOraMxpI2e8qYe5OFZVH5W9vQ9sIhDXW6409X6-IHMr_R9FiMp2FY8PLJF4cmv4uFHw0C2Dg1aSYXKbLa2hELvmkpA0K_BOGUFyhOFrQpqNVfxCxT0F9Bwhudbqx2MaMI-SuYjuhGN0o/s1600/5-New+virtual+machine+wizard+-+add+additional+nic+and+put+it+on+hostonly+network+-+7.png" height="346" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;"><br /></td></tr>
</tbody></table>
<div>
The second interface can be put on an internal network for now, since the primary one is the one that will be used to download updates.<br />
<br /></div>
<div>
NOTE: you will not need to install 3 windows machines from scratch,
but just 2: one datacenter for the cluster members and one enterprise
for the domain controller. The second cluster machine can be cloned from
the first one. You will just need to clone it after you updated it and
before activating it. By using two different license keys, the two
machines will be different.</div>
<div>
The high-level procedure to install the 3 machines is<br />
<ol>
<li>
install from scratch the DC on windows 2008 enterprise version</li>
<li>
update it to the latest version and activate it</li>
<li>
install from scratch one cluster member on windows 2008 datacenter version</li>
<li>
update it to the latest version and clone it</li>
<li>
activate both cluster member machines with different license keys</li>
</ol>
<div>
<br /></div>
</div>
<div>
<h2>
Assigning IP addresses to the Windows machines</h2>
At this point, you should have three windows machines up and running, updated to the latest windows update and activated.
You should assign ip addresses to your systems and put their
interfaces into the correct virtual network.<br />
For this lab, I used 2
internal networks for the NAS and the SQL cluster members. The DC had one leg on one of the internal
networks and the other one was NATted by vmware, so that it could still
have internet access. Here is a schema for the lab, you see that you
will have to come up with an addressing schema for the two networks and
choose ip addresses for all of the interfaces, the only exception being
the external interface of the DC/App server, which will receive it from
DHCP. On top of the physical interfaces, you should reserve another 2 IP
addresses on "Virtual network1" for the VIP of the cluster and for the
VIP of the SQL server.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEge_1EKOc7KqpoDIK-yS13HChtGDjbqVyokdKXiNTWk-yYz-_AOaIDrr0GftWebdM6H9VC6CQovWCDBzdSq1tzZFeJ7mUi5rOy_u-9rqgOjaz51PKXdTPW6TdHQwXoHRnIJFCdWXWflExg/s1600/6-Schema+di+rete.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEge_1EKOc7KqpoDIK-yS13HChtGDjbqVyokdKXiNTWk-yYz-_AOaIDrr0GftWebdM6H9VC6CQovWCDBzdSq1tzZFeJ7mUi5rOy_u-9rqgOjaz51PKXdTPW6TdHQwXoHRnIJFCdWXWflExg/s1600/6-Schema+di+rete.jpg" height="384" width="640" /></a></div>
<br />
<br />
So the breakdown of IPs needed is<br />
<br />
Virtual network1 -----> 5 IPs needed<br />
Virtual network2 --------> 3 IPs needed<br />
<br />
In my case, I chose the following IP addresses, you can come up with your addressing plan, if you prefer<br />
<br />
<div class="separator" style="clear: both; text-align: left;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsFoa1yRN9jknSL69aF7Ne765nsoNBYeE_kRnKIb_GYwkubE406K2IJUegR2UXaG4PgSJtRVWKuL1QYI2-NlByroeC9h2mKwgWzJIbU-WzWGHpbgfnWLGz0qe9FCHjVmocVpPgiZegTEA/s1600/7-ip+addressing+schema.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhsFoa1yRN9jknSL69aF7Ne765nsoNBYeE_kRnKIb_GYwkubE406K2IJUegR2UXaG4PgSJtRVWKuL1QYI2-NlByroeC9h2mKwgWzJIbU-WzWGHpbgfnWLGz0qe9FCHjVmocVpPgiZegTEA/s1600/7-ip+addressing+schema.jpg" height="241" width="640" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<br />
<h2>
Create firewall rules so that the three windows machines can communicate with each other</h2>
Now your machines have an IP address, but they still cannot
communicate with each other. Windows 2008 R2 comes out of the box with
firewall blocking inbound connections, so if you want your boxes to
communicate correctly, you will need to create firewall rules that allow
communication on these networks. The simplest way to do it is to create
some rules that allow inbound communication from any host on the two
virtual networks we created.<br />
Click on Start and in the search box type <strong>wf.msc</strong>, this will bring you to the firewall console. We will create a single inbound rule allowing any ip address on the two networks.<br />
Click on Inbound Rules and select as an action "New Rule"., this will bring this window<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTidqdSP3NMXKb2blWvzdu4bXEOWy0ebMkxz9FzY_chadVNRP9MtlCYiFaJ4P10OHGO1RnrUTs37rsxaLqqjPoftLHVewaRqmHE6P5f8nF0iP7j4fMqfJZX4d2DTsnkLm1CRWhwD_1nFM/s1600/8-fw2008+-+custom+rule+-+1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTidqdSP3NMXKb2blWvzdu4bXEOWy0ebMkxz9FzY_chadVNRP9MtlCYiFaJ4P10OHGO1RnrUTs37rsxaLqqjPoftLHVewaRqmHE6P5f8nF0iP7j4fMqfJZX4d2DTsnkLm1CRWhwD_1nFM/s1600/8-fw2008+-+custom+rule+-+1.png" height="361" width="640" /></a></div>
<br />
As Rule type, we will create custom rule, so that we can specify whole
networks and all ports. The next couple of screens can be left with
default values.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjj24_1pdkV7b4-IH7n_ligd9kDOZg91jTZqlMqBGSZpSMi9gWjanHU2V7N8b8ww2J3LBfr9W7IarHr3l2kyUdWa5o8TKlZbHXOJGFmvJaizvjNW_52hdLadlq_QFGSYOCsSK_ajutCsfk/s1600/9-fw2008+-+scope+-+2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjj24_1pdkV7b4-IH7n_ligd9kDOZg91jTZqlMqBGSZpSMi9gWjanHU2V7N8b8ww2J3LBfr9W7IarHr3l2kyUdWa5o8TKlZbHXOJGFmvJaizvjNW_52hdLadlq_QFGSYOCsSK_ajutCsfk/s1600/9-fw2008+-+scope+-+2.png" height="352" width="640" /></a></div>
<br />
In the scope window, as remote addresses we will specify the networks we agreed upon for virtual network1 and 2.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOHkSPL0-C5AbB_EZ3sJnTK_JgYi8OODAHO9BTdv8Bfvx0Lt_8eM_N0T1S7yuMZqUZ556uiOM3EgscLL6MsbNqjhB3k7YYFFhNT1073bT44_EOJFZzj_kncZe9gvgA8xiANAJ-kgGUyI0/s1600/10-fw2008+-+action+-+3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhOHkSPL0-C5AbB_EZ3sJnTK_JgYi8OODAHO9BTdv8Bfvx0Lt_8eM_N0T1S7yuMZqUZ556uiOM3EgscLL6MsbNqjhB3k7YYFFhNT1073bT44_EOJFZzj_kncZe9gvgA8xiANAJ-kgGUyI0/s1600/10-fw2008+-+action+-+3.png" height="266" width="640" /></a></div>
<br />
<br />
In the Action window, we will need to make sure that allow connection
is selected. The rest of the options can be left as default, you need
to specify a rule name.<br />
<br />
Create this rule on all of the windows machines.<br />
<br />
NOTE: On the domain controller, since it has no NIC on the
VMnet6/Virtual Network 2, there is no need to specify in the scope the
network 10.1.1.0/24<br />
After creating the rules on all of the windows machines, you can test
that everything is working fine by running pings between the hosts.<br />
<br />
<br />
<br />
<h2>
Installing the domain controller</h2>
At this point, networking should be set up and the three windows
machines should be able to ping each other. Next step is installing the
domain controller.<br />
<br />
Click on Start and type <strong>dcpromo</strong>. Installation of the Active Directory software begins.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbc96M_bUIyNpcxycIj7QevnaEAiq4sexxdgalMi1Y9-sO96ZojCeCkzZWCQGBCoXOcvJ0Z5zqgmDKa6pTcmT6o_ij4jA64X0JZgl0Pum3iLbId7HvczRhYex0qfldsl44V0CKv2gZmgk/s1600/11-dc-3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbc96M_bUIyNpcxycIj7QevnaEAiq4sexxdgalMi1Y9-sO96ZojCeCkzZWCQGBCoXOcvJ0Z5zqgmDKa6pTcmT6o_ij4jA64X0JZgl0Pum3iLbId7HvczRhYex0qfldsl44V0CKv2gZmgk/s1600/11-dc-3.png" height="270" width="400" /></a></div>
<br />
after a few minutes you should get to this window.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnjc58iSQ7Xn57fOQ7zMtWrW9XVPnhR60-amM3ND5wl5IKmJzxPHkl9tQnD8fPrWDMdg_6phXX820BhloIhtDNy8s2lSICrQZnutlagpWgCJpqQhq26maAatJANHZVNEdUA-4MjjV9Pfc/s1600/12dc-4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnjc58iSQ7Xn57fOQ7zMtWrW9XVPnhR60-amM3ND5wl5IKmJzxPHkl9tQnD8fPrWDMdg_6phXX820BhloIhtDNy8s2lSICrQZnutlagpWgCJpqQhq26maAatJANHZVNEdUA-4MjjV9Pfc/s1600/12dc-4.png" height="291" width="400" /></a></div>
<br />
Clicking next will bring you to this warning, which can be ignored.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiC9kMg9ZFMzrEQuMtO80Gnwqq0Vglzqp36_n2rxwry3oifVqthAxZrLYKVwryH2HE64isChEY2cnCj85lANqEZny8oKG7MgoM9T-HAbRUc-ECkVXoMjG6zrJ0B1sDWO2IAllOEPCxT8Tk/s1600/13-dc-5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiC9kMg9ZFMzrEQuMtO80Gnwqq0Vglzqp36_n2rxwry3oifVqthAxZrLYKVwryH2HE64isChEY2cnCj85lANqEZny8oKG7MgoM9T-HAbRUc-ECkVXoMjG6zrJ0B1sDWO2IAllOEPCxT8Tk/s1600/13-dc-5.png" height="262" width="400" /></a></div>
<br />
Here we have the first important choice which is about which kind of domain we want to to create. We will <strong>create a new domain in a new forest</strong>.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmEEfviGuKfg1Fv9G6ykkIKEQbjzQg6H-eXraro_NbqoEVZRDfWgk7arxLe42AcybfbSuW4lAo2CoTq9dv5EvyTtIiQVYkBJCFFEMDrCGypZ1XPZ8qJ57D8Svj4IlvpmIbuDw8leTyITg/s1600/14-dc-6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmEEfviGuKfg1Fv9G6ykkIKEQbjzQg6H-eXraro_NbqoEVZRDfWgk7arxLe42AcybfbSuW4lAo2CoTq9dv5EvyTtIiQVYkBJCFFEMDrCGypZ1XPZ8qJ57D8Svj4IlvpmIbuDw8leTyITg/s1600/14-dc-6.png" height="160" width="400" /></a></div>
<br />
<br />
Next you will need to choose a domain name, I chose <strong>mysqlcluster.local</strong><br />
The software will do a couple of checks to verify that the domain name
or netbios names you chose are not in use and then you will get here<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlxa33VIr_G6Oqb_HBGOa0aCZdWTh7zSFlqMzgu_zxVzxs0u4exN1jjkB9K_7787L0Ycc2oQzYYwzmcwhHSo0AOs2NlZHyEKNRZxjztc_AbqBrOQWBWqqCBB54PaunCOKOYTSOdRlWp_s/s1600/15-dc-7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlxa33VIr_G6Oqb_HBGOa0aCZdWTh7zSFlqMzgu_zxVzxs0u4exN1jjkB9K_7787L0Ycc2oQzYYwzmcwhHSo0AOs2NlZHyEKNRZxjztc_AbqBrOQWBWqqCBB54PaunCOKOYTSOdRlWp_s/s1600/15-dc-7.png" height="286" width="400" /></a></div>
<br />
here you need to choose the compatibility level of your domain with
other domains. Since we do not plan to install other domains or join
this domain to an existing forest, we can choose windows server 2008 R2
as the forest functional level. Next the software will examine your DNS
configuration and bring you to this screen<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh21cP8bjhPyceppbuVg2NSYcTvPmPMRX37C3xOYT01zISKRLcDXQjeXMWvkPPeSy14ggVqr9qcPYQ4nvQO_BREvnayRkxpEXyOj_zoGJJjwBAhO_htfp6FHo4wGF74FpYqxqZDvSanGic/s1600/16-dc-8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh21cP8bjhPyceppbuVg2NSYcTvPmPMRX37C3xOYT01zISKRLcDXQjeXMWvkPPeSy14ggVqr9qcPYQ4nvQO_BREvnayRkxpEXyOj_zoGJJjwBAhO_htfp6FHo4wGF74FpYqxqZDvSanGic/s1600/16-dc-8.png" height="296" width="400" /></a></div>
<br />
Here you will be requested to install DNS software on the DC. After
doing so, the DC can act as the DNS for the cluster members. It will
resolve names in the domain and send unknown DNS requests further up
along the chain of DNSes you configured on it.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjYesvanvT73Y-lewbbd7uW_pD7DLKF6tqnEbpEhMWq02DuOWeluAMAoYmnUrTSXrJOu4Mqj9ggaH5P70-MfiS6jFgo8ky7l-76yhPm3m0v7p80CJpZbnL0vZMYH82je2lJ_NNDLYDXw2w/s1600/17-dc-9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjYesvanvT73Y-lewbbd7uW_pD7DLKF6tqnEbpEhMWq02DuOWeluAMAoYmnUrTSXrJOu4Mqj9ggaH5P70-MfiS6jFgo8ky7l-76yhPm3m0v7p80CJpZbnL0vZMYH82je2lJ_NNDLYDXw2w/s1600/17-dc-9.png" height="207" width="400" /></a></div>
<br />
You will receive a warning that your DC has an IP assigned by DHCP on
one interface, you can safely ignore this error and choose <strong>Yes, the computer will use an IP address automatically assigned by a DHCP server</strong><br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhN2O4EpxbAaZjRjAkLdIePn5c2S8rQVfxJae7CHjoMF8PS9_IShyphenhyphen_1XMEbl_Vh5OB2iaVuchO_tzcULzY2On0iBT7npPcaIPLTRUwUS1bmCwvYZC88HO-f1oDm9njvHJOQyUc6KgkjVdY/s1600/18-dc-10.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhN2O4EpxbAaZjRjAkLdIePn5c2S8rQVfxJae7CHjoMF8PS9_IShyphenhyphen_1XMEbl_Vh5OB2iaVuchO_tzcULzY2On0iBT7npPcaIPLTRUwUS1bmCwvYZC88HO-f1oDm9njvHJOQyUc6KgkjVdY/s1600/18-dc-10.png" height="221" width="400" /></a></div>
<br />
Another warning we don't care about, since we do not intend to integrate this DNS in an existing DNS structure. Just click <strong>Yes</strong> and move on<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhjWsDuZb8H5X4ynnaJP6JTGMXbs6U6IGcdvezxlU6Mbl2xSlllWcrTXqKZOGL0J7xq-CkwWWdfep2qzaXNQgnpO8QaCvry3hmXJPIrqmVtOAdEk1UF0fe1A0XNYC4Psegk8S6dN13e5Ko/s1600/19-dc-11.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhjWsDuZb8H5X4ynnaJP6JTGMXbs6U6IGcdvezxlU6Mbl2xSlllWcrTXqKZOGL0J7xq-CkwWWdfep2qzaXNQgnpO8QaCvry3hmXJPIrqmVtOAdEk1UF0fe1A0XNYC4Psegk8S6dN13e5Ko/s1600/19-dc-11.png" height="273" width="400" /></a></div>
<br />
Next you will need to select where to save some files which are used by
AD. Although, I understand, it is recommended to put these files on
different volumes, we will leave the default values and click next<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-yinbeJpeDauL7Ffyq9FwHgKHSAE0s52VEH7f_fifYG-8tkloElwvFCQxrq0jHXrsQOG69xRs736-zQXQPfTBdQsl4YVWhvF3SrbxDbrnOW2CvCg6YJk2rcMyVvZ_NlSWTuVTWBfb5KU/s1600/20-dc-12.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-yinbeJpeDauL7Ffyq9FwHgKHSAE0s52VEH7f_fifYG-8tkloElwvFCQxrq0jHXrsQOG69xRs736-zQXQPfTBdQsl4YVWhvF3SrbxDbrnOW2CvCg6YJk2rcMyVvZ_NlSWTuVTWBfb5KU/s1600/20-dc-12.png" height="215" width="400" /></a></div>
<br />
<br />
Here you can choose your domain administrator password. For
simplicity, I used the same password for all of the accounts of the
cluster.<br />
<br />
NOTE: Once you create the DC, you won't be able to use local users
anymore to login on the DC, just domain credentials, so be sure to save
this.<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj23qKh1NZNvzzJHEaLXZcKk0Qk1QrHqvo_KBJRoCJg7pgZfUp1FfAYwFYcUraUuZl8zyGiZflotXfAhARegRdvKBCjtnIcfHDWlYHxQ5SAOsLGdHGMf6-E3eH9WZDPxo-RNBF7AUxL7JA/s1600/21-dc-13.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj23qKh1NZNvzzJHEaLXZcKk0Qk1QrHqvo_KBJRoCJg7pgZfUp1FfAYwFYcUraUuZl8zyGiZflotXfAhARegRdvKBCjtnIcfHDWlYHxQ5SAOsLGdHGMf6-E3eH9WZDPxo-RNBF7AUxL7JA/s1600/21-dc-13.png" height="301" width="400" /></a></div>
<br />
Almost there, summary screen<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtL6mt6aDMgKtmoYFL50DRmxLYSBQGdwLXXRg5JizX27eNmOEHf1IPyclYTC5Wdwc-8pa2MwnWypsJHh7JwSoKn4vsUeNHK4WTsxiIb008kukew-beTUAlf0njFXYFWpOryAKznQJ11_I/s1600/22-dc-14.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgtL6mt6aDMgKtmoYFL50DRmxLYSBQGdwLXXRg5JizX27eNmOEHf1IPyclYTC5Wdwc-8pa2MwnWypsJHh7JwSoKn4vsUeNHK4WTsxiIb008kukew-beTUAlf0njFXYFWpOryAKznQJ11_I/s1600/22-dc-14.png" height="386" width="400" /></a></div>
<br />
installation begins. After a few minutes you will be asked to reboot the
DC and that's it, you've successfully installed a domain!<br />
<br />
onto part 2!<br />
<br /></div>
Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-90586234284993089172013-03-04T07:52:00.004-08:002013-03-04T08:27:17.486-08:00The long and winding road (AKA Installing a Windows 2008 R2 SQL Cluster) - Intro<br />
As a few of you may have already discovered, installing a SQL cluster, even in a lab environment, even with little or no security added to it, is no small feat. Googling information is a painful and steep process, if you are pretty new to clusters like I was when I wrote this guide. You may find bits of information here and there, but to understand the full picture and putting it all together is hard.<br />
<br />
I spent more or less one week trying to understand how to install a SQL cluster before succeeding and decided to write a fully illustrated guide on how to do it to setup a lab where you can experiment.<br />
<br />
I have to add a disclaimer as well:<br />
The configuration described in this guide is not fit for running some mission-critical app in a production environment, it is to be used to create a small personal lab to experiment with clustering. Such clusters should be created by certified professionals, since if there is one thing that writing this guide taught me is that clusters are hard to create, to maintain and there is plenty of things that can go wrong.<br />
Having said that, I'm not responsible for any problem, damage, loss of data this configuration might cause. You have been warned, now have fun experimenting.<br />
<br />
<br />
The guide is a big one, I had to split it in several posts. Here is a description of the single parts of it.<br />
<div>
<br /></div>
<br />
<a href="http://punygeek.blogspot.com/2013/03/the-long-and-winding-road-aka_4.html">Part 1</a><br />
<br />
where you will find the list of what you need, a description of what we are going to do, requirements for virtual machines, the ip addressing plan and instructions on how to install a domain controller<br />
<br />
<a href="http://punygeek.blogspot.com/2013/03/the-long-and-winding-road-aka_3161.html">Part 2</a><br />
<br />
where you will learn how to install Freenas and how to configure it to create the disk space, shared among cluster members, that will host your clustered db<br />
<br />
<a href="http://punygeek.blogspot.com/2013/03/the-long-and-winding-road-aka_9982.html">Part 3</a><br />
<br />
where you will connect the shared disk to the cluster members through iSCSI, install your cluster and learn about the last things to do before actually installing SQL server<br />
<br />
<a href="http://punygeek.blogspot.com/2013/03/the-long-and-winding-road-aka_2373.html">Part 4</a><br />
<br />
where you will create a one-node SQL cluster<br />
<br />
<a href="http://punygeek.blogspot.com/2013/03/the-long-and-winding-road-aka_8301.html">Part 5</a><br />
<br />
where you will add an additional SQL node to your SQL cluster. Voila'.<br />
<div>
<br /></div>
Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-73359755638490395072012-11-28T14:14:00.001-08:002012-11-28T14:15:57.630-08:00Ubuntu 12.10: Configuring Kismet to work with Centrino Advanced-N 6200 wireless NICA good guide to configure Kismet can be found here:<br />
<br />
<a href="http://emmanueltoko.blogspot.be/2010/10/kismet-how-to.html">http://emmanueltoko.blogspot.be/2010/10/kismet-how-to.html</a><br />
<br />
the only problem being that my wireless NIC reports "iwlwifi" as the driver. Kismet won't start when configuring this value, It will die with this error:<br />
<br />
<br />
Launching kismet_server: //usr/bin/kismet_server<br />
Suid priv-dropping disabled. This may not be secure.<br />
No specific sources given to be enabled, all will be enabled.<br />
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)<br />
Enabling channel hopping.<br />
Enabling channel splitting.<br />
FATAL: Unknown capture source type 'iwlwifi' in source 'iwlwifi,wlan0,addme'<br />
Done.<br />
<div>
<br /></div>
<div>
the trick to make this work is to use "iwl4965" as the driver in the Kismet.conf file. Ex.:</div>
<div>
<br /></div>
<div>
source=iwl4965,wlan0,test</div>
<div>
<br /></div>
<div>
after doing so, Kismet works. Have fun.</div>
Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-75619142522180189852012-10-20T07:50:00.000-07:002012-10-20T07:50:49.091-07:00Ubuntu 12.04 - How to solve "The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present" error at bootThis error comes up when your swap partition cannot be mounted for some reason. Your system will run and for modern systems with lots of RAM, this should not be a problem at all, but you might want to reactivate swap. If you do, it's better you do it the right way, not only by enabling swap, but also making sure that it gets encrypted, like the rest of your home directory.<br />
The way to do it is the following, commands or files are in bold:<br />
<br />
<ul>
<li><b>sudo swapoff -a</b> (turns off swap)</li>
<li>comment existing swap configuration in <b>/etc/crypttab</b><br />ex.<br />cryptswap1 /dev/sdb8 /dev/urandom swap,cipher=aes-cbc-essiv:sha256<br /></li>
<li>comment existing swap configuration in <b>/etc/fstab</b><br /><br />ex.<br />/dev/mapper/cryptswap1 none swap sw 0 0<br /></li>
<li>re-format swap partition with gparted as linux-swap</li>
<li><b>sudo mkswap /dev/sdXX</b> (create new swap, XX depends on your system and is the partition you formatted earlier, in my case it was sdb8)</li>
<li>mark somewhere the UUID value that the previous command returns<br /><br />ex.<br />Setting up swapspace version 1, size = 4208636 KiB<br />no label, UUID=<b>06a9be15-d05b-466d-bfe3-a086bb9cdba0</b><br /></li>
<li>update <b>/etc/initramfs-tools/conf.d/resume</b> with the new UUID<br /><br />ex.<br />RESUME=UUID=<b>06a9be15-d05b-466d-bfe3-a086bb9cdba0</b><br /></li>
<li><b>sudo update-initramfs -u</b> (update initramfs)</li>
<li><b>sudo swapon /dev/sdXX</b> (enable swap, XX depends on your setup)</li>
<li><b>sudo ecryptfs-setup-swap</b> (encrypt swap)</li>
</ul>
<div>
now you can check that swap is on by using the commands </div>
<div>
<b><br /></b></div>
<div>
<b>free -m</b></div>
<div>
<div>
total used free shared buffers cached</div>
<div>
Mem: 11950 6662 5287 0 126 4002</div>
<div>
-/+ buffers/cache: 2533 9416</div>
<div>
Swap: 4109 0 4109</div>
</div>
<div>
<br /></div>
<div>
or </div>
<div>
<br /></div>
<div>
<b>swapon -s</b></div>
<div>
<div>
Filename<span class="Apple-tab-span" style="white-space: pre;"> </span> Type<span class="Apple-tab-span" style="white-space: pre;"> </span>Size<span class="Apple-tab-span" style="white-space: pre;"> </span> Used<span class="Apple-tab-span" style="white-space: pre;"> </span>Priority</div>
<div>
/dev/mapper/cryptswap1 partition<span class="Apple-tab-span" style="white-space: pre;"> </span> 4208636<span class="Apple-tab-span" style="white-space: pre;"> </span>0<span class="Apple-tab-span" style="white-space: pre;"> </span>-1</div>
</div>
<div>
<br /></div>
Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com14tag:blogger.com,1999:blog-984705062022244132.post-70303623734705544552012-09-30T00:43:00.002-07:002012-09-30T00:48:55.350-07:00Disable automatic "Sleep" function right after installing a new Windows 7 machine<br />
<div>
Right after installing Windows, you usually have a lot of other stuff to do, like upgrading drivers, installing Windows updates and installing new software. The "Sleep" function might interfere with all of that.</div>
<div>
<br /></div>
<div>
<ul>
<li>Open Control Panel</li>
<li>Select System and Security/Hardware and Sound/Power Options</li>
<li>On the left, click on "Choose what closing the lid does"</li>
<li>Set both "When I close the lid: options to "Do nothing"</li>
</ul>
<div>
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFUO7OM3pnZxv25pnFDXUog9SgklzaomSHYe8eTz7UNWLMLQXmOtMolTA3cyIKFtBt6fG8QQzQ_JiJj2oq6MyqSdiAg4SeQ9nQpaxVjQHRVvHWM9S9IeAPyJaTeNJJRI3PIeUiT4lhh_8/s1600/power1.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="131" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjFUO7OM3pnZxv25pnFDXUog9SgklzaomSHYe8eTz7UNWLMLQXmOtMolTA3cyIKFtBt6fG8QQzQ_JiJj2oq6MyqSdiAg4SeQ9nQpaxVjQHRVvHWM9S9IeAPyJaTeNJJRI3PIeUiT4lhh_8/s400/power1.jpg" width="400" /></a></div>
<br />
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<br /></div>
<div>
<ul>
<li>Go back to "Power Options" and select "Change when the computer sleeps"</li>
<li>Set both "Put the computer to sleep" options to "Never"</li>
</ul>
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8mSboQJclmB0faX19fzhkFuj-L_4V0sTS4RCsnbR_hwlkCvtsjLQ0JuFolfKfjnE4f4U2OILADj-xLSzWOjE-jqYdf9QZXUoJiYPKfbtZWgSmshyphenhyphenYI1hpSJOfcsqtitEH1qIDuHQz944/s1600/power2.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="128" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8mSboQJclmB0faX19fzhkFuj-L_4V0sTS4RCsnbR_hwlkCvtsjLQ0JuFolfKfjnE4f4U2OILADj-xLSzWOjE-jqYdf9QZXUoJiYPKfbtZWgSmshyphenhyphenYI1hpSJOfcsqtitEH1qIDuHQz944/s400/power2.jpg" width="400" /></a></div>
<div>
<br /></div>
</div>
Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-10984178199926508082012-07-06T10:58:00.001-07:002012-07-06T10:58:26.748-07:00How to fix checksum errors in a capture fileOn Ubuntu, checksum errors inside packet capture files can be fixed with tcprewrite, which is part of the tcpreplay package. The command to use is<br />
<br />
<ul>
<li>tcprewrite -C -i inputfile -o outputfile</li>
</ul>Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-23039189177404594132012-07-04T01:25:00.003-07:002012-07-06T00:57:23.649-07:00How to reset Ultraedit's window positionI frequently switch from dual monitor to single monitor and back. Ultraedit 11 will save the last window position and this can be a problem when your last Ultraedit window was opened in a screen that is not there anymore. To reset it, you need to<br />
<br />
<ul>
<li><span style="background-color: white;">open uedit32.INI</span></li>
<li><span style="background-color: white;">delete the line </span><b style="background-color: white;">WindowPos=<series of numbers></b></li>
<li><span style="background-color: white;">reopen Ultraedit</span></li>
</ul>
<br />
<b><br /></b>Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0tag:blogger.com,1999:blog-984705062022244132.post-59973756483640664392012-07-04T01:16:00.000-07:002012-07-04T01:16:55.341-07:00WelcomeHi,<br />
I'm glad you are here and I hope you enjoy it. I'm out of my twenties, live in Europe, work in the computer security area, am a dad of 3 and have to confess that am a geek and have been for a long time. This blog will contain useful tricks, things I learn when trying to subdue my computer to do what I intend it to do and the occasional technology rant. I hope you'll find it useful.Litmushttp://www.blogger.com/profile/11902496661812649477noreply@blogger.com0