JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle® ZFS Storage Appliance Administration Guide
Oracle Technology Network
Library
PDF
Print View
Feedback
search filter icon
search icon

Document Information

Using This Documentation

Chapter 1 Oracle ZFS Storage Appliance Overview

Chapter 2 Status

Chapter 3 Initial Configuration

Chapter 4 Network Configuration

Chapter 5 Storage Configuration

Chapter 6 Storage Area Network Configuration

Chapter 7 User Configuration

Chapter 8 Setting ZFSSA Preferences

Chapter 9 Alert Configuration

Chapter 10 Cluster Configuration

Cluster Features and Benefits

Cluster Disadvantages

Cluster Terminology

Understanding Clustering

Cluster Interconnect I/O

Understanding Cluster Resource Management

Cluster Takeover and Failback

Configuration Changes in a Clustered Environment

Clustering Considerations for Storage

Clustering Considerations for Networking

Private Local IP Interfaces

Clustering Considerations for Infiniband

Clustering Redundant Path Scenarios

Preventing 'Split-Brain' Conditions

Estimating and Reducing Takeover Impact

Cluster Configuration Using the BUI

Configuring Clustering

Unconfiguring Clustering

Configuring Clustering Using the CLI

Shutting Down a Clustered Configuration

Shutdown the Stand-by Head

Unconfiguring Clustering

Cluster Node Cabling

ZS3-2 Cluster Cabling

ZS3-4 and 7x20 Cluster Cabling

Storage Shelf Cabling

Cluster Configuration BUI Page

Chapter 11 ZFSSA Services

Chapter 12 Shares, Projects, and Schema

Chapter 13 Replication

Chapter 14 Shadow Migration

Chapter 15 CLI Scripting

Chapter 16 Maintenance Workflows

Chapter 17 Integration

Index

Shutting Down a Clustered Configuration

  1. Verify the cluster state, using the following CLI commands:
             nas-7420-1a:> configuration cluster
             nas-7420-1a:configuration cluster> show
    
  2. The following is an example of the cluster properties: state indicates the status of the head where you ran the command; peer_state indicates the status of the other head.
             state = AKCS_OWNER
             description = Active (takeover completed)
             peer_asn = 365ed33c-3b9d-c533-9349-8014e9da0408
             peer_hostname = nas-7420-1b
             peer_state = AKCS_STRIPPED
             peer_description = Ready (waiting for failback)
    
  3. Use the following table to verify the node status.
    This Node
    Other Node
    Condition
    AKCS_CLUSTERED
    AKCS_CLUSTERED
    Both nodes are running in normal condition.
    AKCS_OWNER
    AKCS_STRIPPED
    This node has all the resources and is in active node. The other node is in stand-by and has no resources.
    AKCS_OWNER
    rebooting
    Another node is rebooting and this node has all resources.
    AKCS_OWNER
    unknown
    This node does not know the partner.

    Note -  If the status of the heads DOES NOT agree, the cluster may be experiencing a problem. Contact Oracle Support before proceeding.