Install the Server Memory

Note: You do not need to perform the server fail-over operation at this time if continuing the installation procedure.

Access the command line of the node currently operating as primary, and initiate the graceful fail-over to the server node currently acting as secondary:

1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address, if connected to the Service Port.

Service Port IP addresses (if used):

Note: Node 2 is used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. It is the server node sold with single-node (non-HA) Workflow Director and Artico systems. This makes the server HA-ready, allowing for adding a second server node as a upgrade after initial installation.

2. Log in to the server node with the following credentials:
   • User name: stornext
   • Password: <stornext user accountpassword>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password.

3. Enter sudo rootsh to gain root user access.
4. Enter the password for the stornext user account again.

5. Confirm that the server node you are connected to is operating as the primary. Enter:

snhamgr -m status

6. Verify the output is (bold text used for clarification):

:default:primary:default:running:

This indicates the node you are connected to is running, and is set as "primary", and that the secondary node is currently "running".

7. On the node operating as the primary, initiate an HA fail-over to the node operating as the secondary.

Note: If you have NFS-HA enabled, click here for the instructions to stop NAS prior to using this command.

For CentOS7-based systems (Xcellis Foundation, aiWARE for Xcellis Embedded (DAE), Xcellis Workflow Director, and Artico (R630) systems), enter:

systemctl stop cvfs

Note: The systemctl stop cvfs command does not provide any command-line status feedback on the progress of stopping cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

Wait until the secondary node becomes the primary. (Time may vary.)

8. Verify the node has failed over. Enter:

snhamgr -m status

9. Verify the output is (bold text used for clarification):

:default:stopped:default:primary:

This indicates that the node you are connected to has "stopped" as primary, and that the node previously operating as secondary is now operating as "primary". If this is not what is shown, wait and enter the snhamgr -m status command again.

You can leave the SSH connection to this server node running if you will access this server again soon.

1. Remove attached peripheral cables.

Note: Label peripheral cables prior to removing the cables to assist with attachment after working on the server.

2. Remove power cables.

1. Push the bezel latch up and pull the left end of the bezel outward, away from the server node.
2. Detach the right end of the bezel, and remove.

Figure 1: Remove the Front Bezel

Remove the server from a rack as follows:

WARNING: Because the chassis weighs 33.08 lbs (15.01 kg), two people are required to lift it.

1. If not done previously, remove all power, Ethernet, and Fibre Channel cables from the back of the server.

Note: If not done previously, label the cables so they can be easily identified when they are connected back to the server after the replacement procedure.

2. Hold the power button in at least 20 seconds to discharge all of the condensers before opening the server.
3. If used, remove the screws under each latch with a #2 PHILLIPS® screwdriver (3) which secure the server to the front of the rack.
4. Facing the front, locate the slam latch on either side of the server (1).
5. The latches engage automatically as the system is pushed into the rack and are released by pulling up on the latches (2).

Figure 2: Unlocking the Server Node Rail Latches



6. Locate the lock levers on the sides of the inner rails (1).
7. Unlock each lever by rotating it up to its release position (2).

WARNING: Because the chassis weighs 33.08 lbs (15.01 kg), two people are required to lift it.

8. Grasp the sides of the server firmly and pull it forward until the rail standoffs are at the front of the J-slots. Lift the server up and away from the rack and place it on a level surface (3).

Figure 3: Pulling the Server Node From the Rack

1. Turn the latch release lock to the unlock position.
2. Lift the cover release latch and remove the server cover.

Figure 4: Remove the Server Cover

1. Latch release lock

2. Server cover

3. Latch

Caution: Never operate your system with the cooling shroud removed. The system can get overheated quickly, resulting in system shutdown and data loss.

Figure 5: Remove the Cooling Shroud

 

1. Cooling shroud

Hold the touch points as indicated in the image above, and lift the shroud away from the server.

Note: The following applies to both memory modules and memory module blanks.

1. Locate the appropriate memory module socket.
2. Release the memory module or blank from the socket by simultaneously pressing the ejectors on both ends of the memory module socket.

   Figure 6: Removing a Memory Module

   

   Figure 7: Removing a Memory Blank

   

   1. Memory module ( Figure 6) or memory blank (Figure 7)

   2. Memory module socket

   3. Memory module socket ejector/tab (2)

Review the following before removing or installing memory modules and memory module blanks.

WARNING: The memory modules are hot to touch for some time after the server has been powered down. Allow the memory modules to cool before handling them. Handle the memory modules by the card edges and avoid touching the components or metallic contacts on the memory module.

Caution: To ensure proper server cooling, memory module blanks must be installed in any memory socket that is not occupied. Remove memory-module blanks only if you intend to install memory modules in those sockets.

Caution: To prevent damage to the memory module or the memory-module socket during installation, do not bend or flex the memory module. In addition, do not apply pressure at the center of the memory module. Apply pressure at both ends of the memory module evenly, and make sure to insert both ends of the memory module simultaneously.

Use one of the following scenarios, based on your specific memory upgrade.

Use one of the following scenarios, based on your specific memory upgrade. For dual-server (HA) systems only, apply the memory kits as described below for BOTH server nodes.

Caution: Ensure that you fully-seat all memory DIMMs in their sockets. If DIMMs are not seated correctly, you could have unexpected errors and your memory count might not be correct after booting the server.

The following diagram shows the memory sockets available in the Xcellis Workflow Director, Artico (R630) and Xcellis Workflow Extender (R630) systems.

Figure 8: Memory Sockets (Left Side of Motherboard)

Figure 9: Memory Sockets (Center of Motherboard)

Figure 10: Memory Sockets (Right Side of Motherboard)

Note: The following applies to both memory modules and memory module blanks.

1. Locate the appropriate memory module socket.
2. Release the memory module or blank from the socket by simultaneously pressing the ejectors on both ends of the memory module socket.

   Figure 11: Removing a Memory Module

   

   Figure 12: Removing a Memory Blank

   

   1. Memory module ( Figure 6) or memory blank (Figure 7)

   2. Memory module socket

   3. Memory module socket ejector/tab (2)

Note: The following applies to both memory modules and memory module blanks.

1. Locate the appropriate memory module socket.
2. If a memory module needs to be replaced, or a memory module blank is installed in the socket, remove it.

   Retain the removed memory module blank(s) for future use.

3. Align the edge connector of the memory module with the alignment key of the memory module socket, and insert the memory module in the socket.

   Note: The alignment key keeps you from incorrectly install the memory module in the socket.

4. Press the memory module with your thumbs until the socket levers firmly click into place.

   When the memory module is properly seated in the socket, the levers on the memory module align with the levers on the other sockets with memory modules installed.

   Figure 13: Installing a Memory Module

   

   1. Memory module (shown)

   2. Alignment key

   3. Memory module socket ejector (2)

Figure 14: Install the Cooling Shroud

 

1. Cooling shroud

Replace the cooling shroud, as indicated in the image above.

1. Align the slots on the server cover with the tabs on the chassis.
2. Press the cover release latch, and push the cover toward the front of the chassis until the latch locks into place.
3. Turn the latch release lock clockwise to the locked position.

Figure 15: Install the Server Cover

1. Latch release lock

2. Server cover

3. Latch

Install the server in a rack as follows:

1. Place the MDC Node into the rail J-slots.

WARNING: Because the chassis weighs 33.08 lbs (15.01 kg), two people are required to lift it.

Figure 16: Installing the Server in a Rack



2. Push the rail levers in on both sides of the server, and slide the server into the rack until it clicks into place.
3. If needed, install a hard-mount screw under each latch with a #2 PHILLIPS® screwdriver to secure the server Node to the front of the rack.
4. Unless this will be done later, connect Ethernet, Fibre Channel and power cables to the back of the server Node. Use the labels applied earlier to identify where these cables should be connected.

1. Attach the right end of the bezel onto the server node.
2. Attach the left side of the bezel onto the system. You should hear an audible "click" when it is installed correctly.

Figure 17: Install the Front Bezel

Note: Do not attach peripherals at this time if continuing the R630 installation procedure. Use the labels created earlier in the procedure to assist with attaching these cables.

1. Attach peripheral cables.

Note: Do not attach power cables at this time if continuing the R630 installation procedure.

2. Attach power cables.

Note: You do not need to perform the server fail-over operation at this time if continuing the installation procedure.

Access the command line of the node currently operating as primary, and initiate the graceful fail-over to the server node currently acting as secondary:

1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network, or use the Service Port IP address, if connected to the Service Port.

Service Port IP addresses (if used):

Note: Node 2 is used for installation using the StorNext Connect Install app, for both single-node and dual-node systems only. It is the server node sold with single-node (non-HA) Workflow Director and Artico systems. This makes the server HA-ready, allowing for adding a second server node as a upgrade after initial installation.

2. Log in to the server node with the following credentials:
   • User name: stornext
   • Password: <stornext user accountpassword>

     Note: password is the default password for the stornext user account. If the password has been changed, use the current password.

3. Enter sudo rootsh to gain root user access.
4. Enter the password for the stornext user account again.

5. Confirm that the server node you are connected to is operating as the primary. Enter:

snhamgr -m status

6. Verify the output is (bold text used for clarification):

:default:primary:default:running:

This indicates the node you are connected to is running, and is set as "primary", and that the secondary node is currently "running".

7. On the node operating as the primary, initiate an HA fail-over to the node operating as the secondary.

Note: If you have NFS-HA enabled, click here for the instructions to stop NAS prior to using this command.

For CentOS7-based systems (Xcellis Foundation, aiWARE for Xcellis Embedded (DAE), Xcellis Workflow Director, and Artico (R630) systems), enter:

systemctl stop cvfs

Note: The systemctl stop cvfs command does not provide any command-line status feedback on the progress of stopping cvfs operations. You will need to be patient and wait until you again have access to the command line prompt.

Wait until the secondary node becomes the primary. (Time may vary.)

8. Verify the node has failed over. Enter:

snhamgr -m status

9. Verify the output is (bold text used for clarification):

:default:stopped:default:primary:

This indicates that the node you are connected to has "stopped" as primary, and that the node previously operating as secondary is now operating as "primary". If this is not what is shown, wait and enter the snhamgr -m status command again.

You can leave the SSH connection to this server node running if you will access this server again soon.

1. Press <F2> to enter System Setup, and check the System Memory setting.

   The server should have already changed the value to reflect the installed memory. If the value is incorrect, one or more of the memory modules may not be installed properly. Ensure that the memory module is firmly seated in the memory module socket.

2. Run the System Memory Test in System Diagnostics.