Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION, Руководство администратора, Страница: 30 / 184

30 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
Š
Ensure that eDirectory and your clusters are stable before implementing BCC.
Š
Engage Novell Consulting.
Š
Engage a consulting group from your SAN vendor.
Š
The cluster node that hosts the Identity Manager driver should have a full read/write
eDirectory
TM
replica with the following containers in the replica:
Š
Driver set container
Š Cluster container
Š
(Parent) container where the servers reside
Š Landing zone container
Š
User object container
Š Ensure that you have full read/write replicas of the entire tree at each data center.
3.3 LAN Connectivity Guidelines
The primary objective of LAN connectivity in a cluster is to provide uninterrupted heartbeat
communications. Use the guidelines in this section to design the LAN connectivity for each of the
peer clusters in the business continuity cluster:
Š Section 3.3.1, “VLAN,” on page 30
Š
Section 3.3.2, “Channel Bonding,” on page 30
Š Section 3.3.3, “IP Addresses,” on page 31
Š
Section 3.3.4, “Name Resolution,” on page 31
Š Section 3.3.5, “IP Addresses for BCC-Enabled Cluster Resources,” on page 31
3.3.1 VLAN
Use a dedicated VLAN (virtual local area network) for each cluster.
The cluster protocol is non-routable, so you cannot direct communications to specific IP addresses.
Using a VLAN for the cluster nodes provides a protected environment for the heartbeat process and
ensures that heartbeat packets are exchanged only between the nodes of a given cluster.
When using a VLAN, no foreign host can interfere with the heartbeat. For example, it avoids
broadcast storms that slow traffic and result in false split-brain abends.
3.3.2 Channel Bonding
Use channel bonding for adapters for LAN fault tolerance. Channel bonding combines Ethernet
interfaces on a host computer for redundancy or increased throughput. It helps increase the
availability of an individual cluster node, which helps avoid or reduce the occurrences of failover
caused by slow LAN traffic. For information, see
/usr/src/linux/Documentation/
bonding.txt
.
When configuring Spanning Tree Protocol (STP), ensure that Portfast is enabled, or consider Rapid
Spanning Tree. The default settings for STP inhibit the heartbeat for over 30 seconds whenever there
is a change in link status. Test your STP configuration with Novell Cluster Services
TM
running to
make sure that a node is not cast out of the cluster when a broken link is restored.