Using Virtual IP Addresses with BCC 1.2
F
167
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
F
Using Virtual IP Addresses with
BCC 1.2
One deployment consideration is how the client computers reconnect to services when cluster
resources fail over to a peer cluster in the disaster recovery location. Typically, the disaster recovery
site is a geographically dispersed site in a different network subnet, which forces the cluster
resources to use a different IP address range. In Novell
®
Business Continuity Cluster (BCC) 1.2 or
later, you can configure BCC to use virtual IP addresses for BCC-enabled resources as an alternate
approach to assigning secondary IP addresses to resources.
Section F.1, “Understanding Internal Virtual IP Networks,” on page 167
Section F.2, “Virtual IP Address Benefits,” on page 168
Section F.3, “Planning a Virtual IP Network Implementation,” on page 169
Section F.4, “Configuring a Virtual Router with OSPF,” on page 171
Section F.5, “Configuring Virtual IP Addresses,” on page 172
F.1 Understanding Internal Virtual IP Networks
To use virtual IP addresses, you set up an internal virtual IP network on each cluster node. The
network consists of the following:
Section F.1.1, “Virtual Adapter,” on page 167
Section F.1.2, “Host Mask,” on page 167
Section F.1.3, “Internal Router,” on page 167
F.1.1 Virtual Adapter
A virtual adapter is a software-based adapter. A virtual adapter behaves like a conventional loopback
interface with external visibility. LAN routers can maintain accurate information on available routes
to the virtual adapter destination. The last hop on a router path to cluster resources occurs inside the
cluster node itself. A cluster resource’s IP address is bound to the virtual adapter instead of to a
physical adapter.
F.1.2 Host Mask
Virtual adapters support configuring virtual IP addresses with a host mask. The mask treats each
resource as a separate network segment. This allows each cluster resource to have its own entry in
the routing table of the internal router on the cluster node where it resides.
F.1.3 Internal Router
An internal router is a software-based router that runs on the operating system in a cluster node. On
Linux, the internal router is set up with the open source Quagga Routing Software Suite. For
information about configuring and using Quagga, see the
Quagga Routing Software Suite
Documentation Web site (http://www.quagga.net/docs.php)
.
Содержание BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION
Страница 4: ...4 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 36: ...36 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 56: ...56 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 64: ...64 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 70: ...70 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 132: ...132 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 146: ...146 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 152: ...152 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 166: ...166 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 174: ...174 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 176: ...176 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 184: ...184 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...