os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reworded sentences to avoid second person usage, some grammar fixes,

Browse source 
other linguistic improvements.

Reviewed by:	trhodes
This commit is contained in:
Christian Brueffer 2007-04-29 15:56:58 +00:00
parent 64189a66fb
commit 8ea2d4dd24
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30117
1 changed files with 16 additions and 15 deletions

31
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -4700,13 +4700,13 @@ route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"</programlisting>
<para>One use of <acronym>CARP</acronym>, as noted above, is for
server availability. This example will provide fail over support
for three hosts, both with unique <acronym>IP</acronym>
addresses and provide the same web content. These machines will
for three hosts, all with unique <acronym>IP</acronym>
addresses and providing the same web content. These machines will
act in conjunction with a Round Robin <acronym>DNS</acronym>
configuration. The fail over machine will have two additional
<acronym>CARP</acronym> interfaces, one for each of the content
server's <acronym>IP</acronym>s. When a failure occurs, the
fail over server should pick up failed machine's
fail over server should pick up the failed machine's
<acronym>IP</acronym> address. This means the failure should
go completely unnoticed to the user. The fail over server
requires identical content and services as the other content
@ -4716,11 +4716,11 @@ route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"</programlisting>
than their issued hostnames and <acronym>VHID</acronym>s.
This example calls these machines
<hostid>hosta.example.org</hostid> and
<hostid>hostb.example.org</hostid> respectively. Begin their
<acronym>CARP</acronym> configuration by adding the required
lines to <filename>rc.conf</filename>. For
<hostid>hostb.example.org</hostid> respectively. First, the
required lines for a <acronym>CARP</acronym> configuration have
to be added to <filename>rc.conf</filename>. For
<hostid>hosta.example.org</hostid>, the
<filename>rc.conf</filename> file contains the following
<filename>rc.conf</filename> file should contain the following
lines:</para>
<programlisting>hostname="hosta.example.org"
@ -4728,8 +4728,8 @@ ifconfig_fxp0="inet 192.168.1.3 netmask 255.255.255.0"
cloned_interfaces="carp0"
ifconfig_carp0="vhid 1 pass testpast 192.168.1.50/24"</programlisting>
<para>And on <hostid>hostb.example.org</hostid> has the following
lines in <filename>rc.conf</filename>:</para>
<para>On <hostid>hostb.example.org</hostid> the following lines
should be in <filename>rc.conf</filename>:</para>
<programlisting>hostname="hostb.example.org"
ifconfig_fxp0="inet 192.168.1.4 netmask 255.255.255.0"
@ -4737,17 +4737,18 @@ cloned_interfaces="carp0"
ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24"</programlisting>
<note>
<para>It is very important the passwords are identical, the
<para>It is very important that the passwords, specified by the
<option>pass</option> option to <command>ifconfig</command>, are identical. The
<devicename>carp</devicename> devices will only listen to
and accept advertisements from machines with the correct
password. The <acronym>VHID</acronym> must also be different
for each machine.</para>
</note>
<para>Prepare the third machine,
<hostid>provider.example.org</hostid>, so that it may handle
<para>The third machine,
<hostid>provider.example.org</hostid>, should be prepared so that it may handle
fail over from either host. This machine will require two
<devicename>carp</devicename> devices, one to handle each of
<devicename>carp</devicename> devices, one to handle each
host. The appropriate <filename>rc.conf</filename>
configuration lines will be similar to the following:</para>
@ -4779,8 +4780,8 @@ ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24"</programlistin
</note>
<para>At this point, <acronym>CARP</acronym> should be completely
enabled and available for testing. Either restart networking
or reboot the machines and test.</para>
enabled and available for testing. For testing, either networking has
to be restarted to the machines need to be rebooted.</para>
<para>More information is always available in the &man.carp.4;
manual page.</para>