Oracle ZFS Storage Appliance Administration Manual page 215

Hide thumbs Also See for ZFS Storage Appliance:
Table of Contents

Advertisement

Shutting Down a Clustered Configuration (CLI)
should be used. A comprehensive approach to availability requires the correct configuration of
the network and a network-wide plan for redundancy.
FIGURE 17
Clustering for Networking
Network interfaces can be configured as either singleton or private resources, provided they
have a static IP configuration. Interfaces configured using DHCP must be private and using
DHCP in clusters is discouraged. When configured as a singleton resource, all datalinks and
devices used to construct an interface can be active on only one controller at a time. Likewise,
corresponding devices on each controller must be attached to the same networks in order
for service to be provided in a failed-over state. An example of this is shown in the previous
diagram.
For a cluster to operate correctly when you construct network interfaces from devices and
datalinks, it is essential that each singleton interface has a device using the same identifier and
capabilities available on both controllers. Since device identifiers depend on the device type
and the order in which they are first detected by the appliance, clustered controllers MUST
have identical hardware installed. Each slot in both controllers must be populated with identical
hardware and slots must be populated in the same order on both controllers. Your qualified
Oracle reseller or service representative can assist in planning hardware upgrades that meet
these requirements.
A route is always bound explicitly to a single network interface. Routes are represented within
the resource manager as symbiotes and can become active only when the interfaces to which
they are bound are operational. Therefore, a route bound to an interface which is currently
in standby mode (exported) has no effect until the interface is activated during the takeover
process. This is important when two pools are configured and are made available to a common
subnet. If a subnet is home to a router that is used by the appliances to reach one or more other
networks, a separate route (for example, a second default route), must be configured and bound
to each of the active and standby interfaces attached to that subnet.
Example:
Configuring the Appliance
215

Advertisement

Table of Contents
loading

Table of Contents