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

Chapter 11 ZFSSA Services

Available Services

Data Services

Directory Services

Service Settings

Remote Access Services

Security Services

Minimum Needed Ports

Configuring Services Using the BUI

Viewing a Specific Service Screen

Viewing a Specific Service Screen

Enabling a Service

Disabling a Service

Defining Properties

Viewing Service Logs

Configuring Services Using the CLI

Selecting a Service

Viewing a Service's State

Enabling a Service

Disabling a Service

Setting Properties

Viewing Service Help

NFS

Properties

Kerberos Realms

Service Logs

NFS Analytics

NFS BUI and CLI Properties

Sharing a Filesystem over NFS

iSCSI Service

iSCSI Service Properties

iSCSI Service Authentication

iSCSI Service Authorization

iSCSI Service Targets and Initiators

iSCSI Troubleshooting

SMB Service

SMB Service Properties

SMB Share Properties

NFS/SMB Interoperability

SMB DFS Namespaces

SMB Microsoft Stand-alone DFS Namespace Management Tools Support Matrix

Example: Manipulating DFS Namespaces

SMB Autohome Service

Adding SMB Autohome Rules

SMB Local Groups

Adding a User to an SMB Local Group

SMB Local Accounts

SMB MMC Integration

SMB Event Viewer

SMB Share Management

SMB Users, Groups, and Connections

Listing SMB Services

Configuring SMB Using the BUI

Initial Configuration

Active Directory Configuration

Project and Share Configuration

SMB Data Service Configuration

FTP Service

FTP Properties

FTP General Settings

FTP Security Settings

FTP Logs

Configuring FTP Using the BUI

Allowing FTP Access to a share

HTTP Service

HTTP Properties

HTTP Authentication and Access Control

HTTP Logs

Configuring HTTP

Allowing HTTP access to a share

NDMP Service

NDMP Local vs. Remote Configurations

NDMP Backup Formats and Types

NDMP Back up with

NDMP Back up with

NDMP Incremental backups

NDMP Properties

NDMP Logs

Remote Replication

Shadow Migration

Shadow Migration Properties

SFTP Service

SFTP Properties

SFTP Port

SFTP Logs

Configuring SFTP

Allowing SFTP access to a share

Configuring SFTP Services for Remote Access

SRP Service

TFTP Service

TFTP Properties

Configuring TFTP

Allowing TFTP access to a share

Virus Scan Service

Virus Scan Properties

Virus Scan File Extensions

Scanning Engines

Virus Scan Logs

Configuring Virus Scan

Configuring virus scanning for a share

NIS Service

NIS Properties

NIS Logs

Configuring NIS

Adding an appliance administrator from NIS

LDAP Service

LDAP Properties

LDAP Custom Mappings

LDAP Logs

Configuring LDAP

Adding an appliance administrator

Active Directory

Active Directory Properties

Active Directory Join Domain

Active Directory Join Workgroup

Active Directory Domains and Workgroups

Active Directory LDAP Signing

Active Directory Windows Server 2012 Support

Active Directory Windows Server 2008 Support

Active Directory Windows Server 2008 Support Section A: Kerberos issue (KB951191)

Active Directory Windows Server 2008 Support Section B: NTLMv2 issue (KB957441)

Active Directory Windows Server 2008 Support Section C: Note on NTLMv2

Configuring Active Directory Using the BUI

Joining a Domain

Joining a Workgroup

Configuring Active Directory Using the CLI

Example - Configuring Active Directory Using the CLI

Identity Mapping Service

Identity Mapping Properties

Identity Mapping Rule-based Mapping

Identity Mapping Directory-based Mapping

Identity Mapping IDMU

Identity Mapping Rules

Deny Mappings

Mapping Rule Directional Symbols

Identity Mapping Mappings

Identity Mapping Logs

Identity Mapping Best Practices

Identity Mapping Concepts

Identity Mapping Case Sensitivity

Mapping Persistence

Identity Mapping Domain-Wide Rules

Ephemeral Mapping

Identity Mapping Examples

Configuring Identity Mapping

Configuring Identity Mapping

Viewing or Flushing Mappings

DNS Service

DNS Properties

Configuring DNS

DNS Logs

Active Directory and DNS

Non-DNS Resolution

DNS-Less Operation

Dynamic Routing Service

RIP and RIPng Dynamic Routing Protocols

Dynamic Routing Logs

IPMP Service

IPMP Properties

IPMP Logs

NTP Service

NTP Properties

NTP Validation

NTP Authentication

NTP BUI Clock

NTP Tips

Configuring NTP Using the BUI

BUI Clock Synchronization

Configuring NTP Using the CLI

Phone Home Service

Oracle Single Sign-On Account

Phone Home Properties

Phone Home Web Proxy

Registering the Appliance

Registering the Appliance Using the BUI

Registering the Appliance Using the CLI

Changing Account Information

Phone Home Status

Phone Home State

Phone Home Logs

REST

RESTful API

Service Tags

Service Tag Properties

SMTP Service

SMTP Properties

SMTP Logs

SNMP Service

SNMP Properties

SNMP MIBs

Sun FM MIB

Sun AK MIB

Confinguring SNMP

Configuring SNMP to Serve Appliance Status

Configuring SNMP to Send Traps

Syslog Service

Syslog Properties

Classic Syslog: RFC 3164

Updated Syslog: RFC 5424

SYSLOG Message Format

SYSLOG Alert Message Format

Receiver Configuration Examples

Configuring a Solaris Receiver

Configuring a Linux Receiver

System Identity

System Identity Properties

System Identity Logs

SSH Service

SSH Properties

SSH Logs

Configuring SSH

Disabling root SSH access

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

SYSLOG Message Format

The Syslog protocol itself does not define the format of the message payload, leaving it up to the sender to include any kind of structured data or unstructured human-readable string that is appropriate. Sun Storage appliances use the syslog subsystem tag ak to indicate a structured, parseable message payload, described next. Other subsystem tags indicate arbitrary human-readable text, but administrators should consider these string forms unstable and subject to change without notice or removal in future releases of the Sun Storage software.

Table 11-53  SYSLOG Message Formats
Facility
Tag Name
Description
daemon
ak
Generic tag for appliance subsystems. All alerts will be tagged ak, indicating a SUNW-MSG-ID follows.
daemon
idmap
Identity Mapping service for POSIX and Windows identity conversion.
daemon
smbd
SMB Data Protocol for accessing shares.

SYSLOG Alert Message Format

If an alert is configured with the Send Syslog Message action, it will produce a syslog message payload containing localized text consisting of the following standard fields. Each field will be prefixed with the field name in CAPITAL letters followed by a colon and whitespace character.

Table 11-54  SYSLOG Alert Message Formats
Field Name
Description
SUNW-MSG-ID
The stable Sun Fault Message Identifier associated with the alert. Each system condition and fault diagnosis that produces an administrator alert is assigned a persistent, unique identifier in Sun's Fault Message catalog. These identifiers can be easily read over the phone or scribbled down in your notebook, and link to a corresponding knowledge article found at sun.com/msg/.
TYPE
The type of condition. This will be one of the labels: Fault, indicating a hardware component or connector failure; Defect indicating a software defect or misconfiguration; Alert, indicating a condition not associated with a fault or defect, such as the completion of a backup activity or remote replication.
VER
The version of this encoding format itself. This description corresponds to version "1" of the SUNW-MSG-ID format. If a "1" is present in the VER field, parsing code may assume that all of the subsequent fields will be present. Parsing code should be written to handle or ignore additional fields if a decimal integer greater than one is specified.
SEVERITY
The severity of the condition associated with the problem that triggered the alert. The list of severities is shown below.
EVENT-TIME
The time corresponding to this event. The time will be in the form "Day Mon DD HH:MM:SS YYYY" in UTC. For example: Fri Aug 14 21:34:22 2009.
PLATFORM
The platform identifier for the appliance. This field is for Oracle Service use only.
CSN
The chassis serial number of the appliance.
HOSTNAME
The canonical name of the appliance as defined by the System Identity configuration.
SOURCE
The subsystem within the appliance software that emitted the event. This field is for Oracle Service use only.
REV
The internal revision of the subsystem. This field is for Oracle Service use only.
EVENT-ID
The Universally Unique Identifier (UUID) associated with this event. Oracle's Fault Management system associates a UUID with each alert and fault diagnosis such that administrators can gather and correlated multiple messages associated with a single condition, and detect duplicate messages. Oracle Service personnel can use the EVENT-ID to retrieve additional postmortem information associated with the problem that may help Oracle respond to the issue.
DESC
Description of the condition associated with the event.
AUTO-RESPONSE
The automated response to the problem, if any, by the Fault Management software included in the system. Automated responses include capabilities such as proactively offlining faulty disks, DRAM memory chips, and processor cores.
REC-ACTION
The recommended service action. This will include a brief summary of the recommended action, but administrators should consult the knowledge article and this documentation for information on the complete repair procedure.

The SEVERITY field will be set to one of the following values:

Table 11-55  SYSLOG Severity Fields
Severity
Syslog Level
Description
Minor
LOG_WARNING
A condition occurred that does not currently impair service, but the condition needs to be corrected before it becomes more severe.
Major
LOG_ERR
A condition occurred that does impair service but not seriously.
Critical
LOG_CRIT
A condition occurred that seriously impairs service and requires immediate correction.