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

Network Configuration Page

Devices

Datalinks

Network Interfaces

Network IP MultiPathing (IPMP)

Network Performance and Availability

Network Routing Configuration

Network Routing Entries

Network Routing Properties

Network Configuration Using the BUI

Network Configuration Page

Network Addresses

Network Routing Page

Network Configuration Using the CLI

Network Configuration Tasks Using the BUI

Creating a single port interface

Modifying an interface

Creating a single port interface, drag-and-drop

Creating an LACP aggregated link interface

Creating an IPMP group using probe-based and link-state failure detection

Creating an IPMP group using link-state only failure detection

Extending an LACP aggregation

Extending an IPMP group

Creating an InfiniBand partition datalink and interface

Creating a VNIC without a VLAN ID for clustered controllers

Creating VNICs with the same VLAN ID for clustered controllers

Adding a static route

Deleting a static route

Network Configuration Tasks Using the CLI

Adding a static route

Deleting a static route

Changing the multihoming property to strict

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

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

Network Configuration Page

In ZFSSA model, network devices represent the available hardware - they have no configurable settings. Datalinks are a layer 2 entity, and must be created to apply settings such as LACP to these network devices. Interfaces are a layer 3 entity containing the IP settings, which they make available via a datalink. This model has separated network interface settings into two parts - datalinks for layer 2 settings, and interfaces for layer 3 settings.

Figure 4-1  Network Configuration Window

image:Network configuration

An example of a single IP address on a single port (common configuration) is:

Table 4-1  Example - Single IP Address on a Single Port
Devices
Datalink
Interface
igb0
datalink1
deimos (192.168.2.80/22)

The following configuration is for a 3-way link aggregation:

Table 4-2  Example - Configuration for a 3-way Link Aggregation
Devices
Datalink
Interface
igb1, igb2, igb3
aggr1 (LACP aggregation)
phobos (192.168.2.81/22)

The datalink entity (which we named "aggr1") groups the network devices in a configurable way (LACP aggregation policy). The interface entity (which we named "phobos") provides configurable IP address settings, which it makes available on the network via the datalink. The network devices (named "igb1", "igb2", ..., by the system) have no direct settings. Datalinks are required to complete the network configuration, whether they apply specific settings to the network devices or not.