Understanding the Shared Name Space
39
Understanding the Shared Name Space
The Avid NEXIS shared storage system uses several names to identify its physical and virtual
components.
Storage System Name
The Storage System Name represents all the physical Engines, and the System Director Appliance if
applicable, operating as one shared storage group. This name is displayed in the bottom of the
Management Console to distinguish one collective Avid NEXIS group from another. Clients see and
connect to the Storage System name through the Client Manager UI. You enter the Storage System
Name in the Remote Host Settings dialog box in the Client Manager if the Avid NEXIS system is not
in the same subnet as the client system (use the System Director IP address if your environment does
not use a DNS server; see
System Director Name and IP Address
Engine and Controller Names
Each Engine, and the System Director Appliance if applicable, has an Engine name. The Engine
name is used to generate the hostnames of the Controllers in that chassis. This helps associate a
particular Controller with the physical chassis it resides in.
System Director Name and IP Address
The shared storage system has one System Director, which runs either on an Engine (if no System
Director Appliance is present) or on the System Director Appliance. Specifically, the System
Director runs on one of the Controllers in the Engine or System Director Appliance.
The System Director is a service that can fail over to the redundant Controller in an Engine or System
Director Appliance, if two Controllers are present. The System Director name, therefore, can change
based on where it is running at the time:
•
In a multi-Engine configuration that does not include a System Director Appliance, the System
Director runs on the first Controller in the first configured Engine. Therefore, that Controller
name is initially also the System Director name.
•
In a configuration with a System Director Appliance, the first Controller in the System Director
Appliance runs the System Director, and its name initially becomes the System Director name.
Because the System Director service can migrate between the Controllers, the System Director uses
an IP address different from the IP addresses assigned to the Controllers. This functions as a virtual
IP address, and allows you to connect to the System Director any time, without needing to know the
IP address or hostname of the Controller currently serving the System Director process.
NTP server IP addresses
You can configure up to two. These must be entered on all Engines
in a multi-Engine configuration. For more information, see
Alternatively, enter the local time and time zone information.
Optional Information
Notes