Private Local Ip Interfaces - Oracle ZFS Storage Appliance Administration Manual

Shutting Down a Clustered Configuration (CLI)
Interface e1000g3 is assigned to 'alice' and e1000g4 is assigned to 'bob'.
■
Each interface has an address in the 172.16.27.0/24 network and can be used to provide
■
service to clients in the 172.16.64.0/22 network, reachable via 172.16.27.1.
Two routes should be created to 172.16.64.0/22 via 172.16.27.1; one should be bound to
■
e1000g3 and the other to e1000g4.
It is a good idea to assign each clustered controller an IP address used only for administration
(most likely on a dedicated management network) and to designate the interface as a private
resource. This ensures that it is possible to reach a functioning controller from the management
network even if it is in a AKCS_STRIPPED state and awaiting failback. This is important if
services such as LDAP and Active Directory are in use and require access to other network
resources when the controller is not providing service. If this is not practical, the service
processor should be attached to a reliable network and/or serial terminal concentrator so that the
controller can be managed using the system console.
If neither of these actions is taken, it is impossible to manage or monitor a newly-booted
controller until failback is completed. You may want to monitor or manage the controller that
is providing service for a particular storage pool. This is likely to be useful when you want to
modify some aspect of the storage itself such as modifying a share property or create a new
LUN. This can be done by using one of the service interfaces to perform administrative tasks or
by allocating a separate singleton interface to be used only for managing the pool to which it is
matched. In either case, the interface should be assigned to the same controller as the pool it is
used to manage.
Related Topics
"Shutting Down a Clustered Configuration (CLI)" on page 199
■

Private Local IP Interfaces

Use the following guidelines when creating private local IP interfaces:
Creating an IP interface with the same name as a private IP interface on cluster peer, results
■
in the local creation of a private IP interface.
Datalinks in use by the peer's private interfaces can not be deleted and the delete button is
■
greyed out.
IP interfaces that belong to an IPMP group must all be of the same type and belong to the
■
same controller. To create an IPMP group you must use either all singleton or all private IP
interfaces and your cluster node must be the owner of these interfaces.
The IPMP group type is set only at creation, and is determined by the type of underlying
■
links.
216 Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016