Handbook/Advanced Networking: Remove obsolete CARP content

PR:		192663
Reviewed by:	emaste, jrm, Pau Amma <pauamma@gundo.com>
Differential Revision:	https://reviews.freebsd.org/D43948

1 files changed, 1 insertions, 84 deletions

diff --git a/documentation/content/en/books/handbook/advanced-networking/_index.adoc b/documentation/content/en/books/handbook/advanced-networking/_index.adoc
index a1f861079b..89281523fb 100644
--- a/documentation/content/en/books/handbook/advanced-networking/_index.adoc
+++ b/documentation/content/en/books/handbook/advanced-networking/_index.adoc
@@ -2221,7 +2221,7 @@ The backup machine has two additional CARP interfaces, one for each of the maste
 When a failure occurs, the backup server will pick up the failed master machine's IP address.
 
 [[carp-10x]]
-=== Using CARP on FreeBSD 10 and Later
+=== Using CARP
 
 Enable boot-time support for CARP by adding an entry for the [.filename]#carp.ko# kernel module in [.filename]#/boot/loader.conf#:
 
@@ -2299,89 +2299,6 @@ High availability is now enabled.
 CARP functionality can be controlled via several man:sysctl[8] variables documented in the man:carp[4] manual pages.
 Other actions can be triggered from CARP events by using man:devd[8].
 
-[[carp-9x]]
-=== Using CARP on FreeBSD 9 and Earlier
-
-The configuration for these versions of FreeBSD is similar to the one described in the previous section, except that a CARP device must first be created and referred to in the configuration.
-
-Enable boot-time support for CARP by loading the [.filename]#if_carp.ko# kernel module in [.filename]#/boot/loader.conf#:
-
-[.programlisting]
-....
-if_carp_load="YES"
-....
-
-To load the module now without rebooting:
-
-[source,shell]
-....
-# kldload carp
-....
-
-For users who prefer to use a custom kernel, include the following line in the custom kernel configuration file and compile the kernel as described in crossref:kernelconfig[kernelconfig,Configuring the FreeBSD Kernel]:
-
-[.programlisting]
-....
-device	carp
-....
-
-Next, on each host, create a CARP device:
-
-[source,shell]
-....
-# ifconfig carp0 create
-....
-
-Set the hostname, management IP address, the shared IP address, and VHID by adding the required lines to [.filename]#/etc/rc.conf#.
-Since a virtual CARP device is used instead of an alias, the actual subnet mask of `/24` is used instead of `/32`.
-Here are the entries for `hosta.example.org`:
-
-[.programlisting]
-....
-hostname="hosta.example.org"
-ifconfig_fxp0="inet 192.168.1.3 netmask 255.255.255.0"
-cloned_interfaces="carp0"
-ifconfig_carp0="vhid 1 pass testpass 192.168.1.50/24"
-....
-
-On `hostb.example.org`:
-
-[.programlisting]
-....
-hostname="hostb.example.org"
-ifconfig_fxp0="inet 192.168.1.4 netmask 255.255.255.0"
-cloned_interfaces="carp0"
-ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24"
-....
-
-The third machine, `hostc.example.org`, is configured to handle failover from either of the master hosts:
-
-[.programlisting]
-....
-hostname="hostc.example.org"
-ifconfig_fxp0="inet 192.168.1.5 netmask 255.255.255.0"
-cloned_interfaces="carp0 carp1"
-ifconfig_carp0="vhid 1 advskew 100 pass testpass 192.168.1.50/24"
-ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24"
-....
-
-[NOTE]
-====
-Preemption is disabled in the [.filename]#GENERIC# FreeBSD kernel.
-If preemption has been enabled with a custom kernel, `hostc.example.org` may not release the IP address back to the original content server.
-The administrator can force the backup server to return the IP address to the master with the command:
-
-[source,shell]
-....
-# ifconfig carp0 down && ifconfig carp0 up
-....
-
-This should be done on the [.filename]#carp# interface which corresponds to the correct host.
-====
-
-Once the configuration is complete, either restart networking or reboot each system.
-High availability is now enabled.
-
 [[network-vlan]]
 == VLANs