Locking Cluster Management Interfaces (CLI)
After initial configuration, clustered controllers are in an active-active state. When a failover occurs, an active controller takes over all non-private interfaces, and the peer controller becomes passive and inaccessible by its BUI and CLI. To maintain access to a controller regardless of its state, lock its management interface to make it private. The following procedure locks the management interface on each clustered controller.
 | Caution - Failure to configure locked management interfaces on clustered controllers may lead to longer than necessary fault diagnosis and resolution times. |
-
On the first controller, go to configuration cluster
resources and select the management interface for the first
controller, prefacing it with net/.
controller-a:> configuration cluster resources select net/igb0
-
Lock the interface by setting the type to private:
configuration cluster resources (uncommitted)> set type=private configuration cluster resources (uncommitted)> commit
-
On the second controller, go to configuration cluster
resources and select the management interface for the second
controller, prefacing it with net/.
controller-b:> configuration cluster resources select net/igb1
-
Lock the interface by setting the type to private:
configuration cluster resources (uncommitted)> set type=private configuration cluster resources (uncommitted)> commit
Related Topics
-
To upgrade the software, see Upgrading the Software in Oracle ZFS Storage Appliance Customer Service Manual.