For an XtremIO X2 dual X-Brick cluster configuration without a physical XMS installed, the total number of power connectors required in a customer rack is 8. This is based on the system specifications which state that a 2 Brick Cluster requires 16 x IEC C14 power sockets1. Since the physical XMS would typically require additional power sockets, and it is not included in this configuration, the total number of power connectors needed would be less than the specified 16.

Here's the breakdown:

Each X-Brick in a dual X-Brick configuration would require power for its controllers and DAEs.

The InfiniBand switches included in a multi X-Brick system would also require power.

Without the physical XMS, which would normally need its own power connectors, the total comes down to 8 connectors required for the dual X-Brick setup1.

When configuring Linux hosts to support XtremIO storage, it is recommended to set the LUN queue depth to 64. This setting helps to optimize the performance of the host when communicating with the XtremIO storage system.

Access Host Configuration: Log into the Linux host that will be connected to the XtremIO storage.

Modify HBA Parameters: Locate the HBA (Host Bus Adapter) parameters within the host's configuration files.

Set Queue Depth: Adjust the queue depth parameter for the HBA to 64. This can typically be done by editing the options.conf file or similar, depending on the HBA driver in use.

Apply Changes: Save the changes and reload the HBA driver or reboot the host to apply the new configuration.

Verify Configuration: Confirm that the new queue depth setting is active and functioning as expected.

The likely cause of the issue where the e-mail server is not receiving expected notifications for major severity issues is that event handlers have not been defined. Event handlers in the XtremIO system are responsible for triggering actions, such as sending email notifications, when certain events or conditions are met. If these handlers are not properly defined, the system will not know to send out notifications upon the occurrence of specified events1.

To resolve this issue, the storage administration team should:

Access the XtremIO web interface.

Navigate to the event handlers section.

Define new event handlers or verify that existing ones are correctly configured to trigger email notifications for major severity issues.

Ensure that the event handlers are linked to the correct alert definitions that correspond to major severity issues.

Test the event handlers to confirm that notifications are being sent as expected.

To create an iSCSI portal using the XtremIO X2 XMS WebUI, an administrator would start the configuration process in the ''Configuration'' section. Here's how the process typically unfolds:

Log into XMS WebUI: The administrator logs into the XtremIO Management Server (XMS) Web User Interface (WebUI).

Navigate to Configuration: Within the WebUI, the administrator navigates to the ''Configuration'' tab. This section contains settings and options for managing and configuring the storage array.

Access iSCSI Options: Under the ''Configuration'' tab, the administrator locates the options for iSCSI settings. This may involve expanding menus or selecting specific sub-options related to iSCSI.

Create iSCSI Portal: Once in the iSCSI settings area, the administrator can create a new iSCSI portal. This involves specifying details such as IP addresses, port numbers, and access controls.

Save and Apply: After entering all necessary information, the administrator saves the configuration and applies it to make the iSCSI portal active.

Verify Connectivity: Finally, the administrator verifies that the iSCSI portal is functioning correctly by connecting to it from an iSCSI initiator.

For detailed instructions and best practices, always refer to the official Dell XtremIO Deploy Achievement document1. This document provides comprehensive guidance on all aspects of setting up and managing XtremIO X2 arrays, including the creation of iSCSI portals.