LRC needs upgrading to ESHs or LRC/ESH fails

About this section

This section describes how to perform the following tasks:

Reasons for upgrading an LRC

If your cluster has disk shelves that have LRC modules and you add a DS14/DS14mk2 FC disk shelf that has ESH modules, you need to replace the LRC modules with ESH modules in the existing DS14 disk shelves.

This section describes how to upgrade your LRC modules to ESH modules. It also describes how to hot-swap a failed LRC or ESH module.

Upgrading LRC modules to ESH modules

To upgrade your DS14/DS14mk2 FC disk shelves with LRC modules into disk shelves with ESH modules, complete the following steps.

Step	Action
1	If the cluster is a...	Then...
	Standard cluster, mirrored cluster, nonswitched MetroCluster, or switched MetroCluster	Take over the partner filer's disk shelves by entering the following command on the local filer: `cf takeover` Go to Step 2.
	Fabric Attached MetroCluster	Go to Step 2.
2	Note the terminate switch position of the LRC you are replacing. The new ESH module must be set to the same setting as the old LRC.
3	While grounded, unplug the cabling from the partner filer's disk shelves. Note the cable locations, especially if your cluster is a Fiber Attached MetroCluster.
4	Remove the Channel A loop LRCs of the partner's disk shelves and replace them with ESH modules.
5	Recable the disk shelves to their original locations before the ESH installation.
6	Check the operation of the new ESH modules by entering the following command from the local node console: environ shelf Result The local filer reports the status of the modified shelves as good.
7	If a cluster takeover...	Then...
	Was performed in Step 1	Return control of the partner filer's disk shelves by entering the following command: `cf giveback` Repeat Steps 2 through 6 for the Channel B loop.
	Was not performed in Step 1	Repeat Steps 2 through 6 for the Channel B loop.
8	Repeat Steps 1 through 7 for the local filer.
9	Test the configuration, as described in Step 5: Checking and testing cluster configuration.

Hot-swapping a single LRC/ESH module

You can hot-swap an LRC or ESH module in a cluster. To hot-swap a single LRC/ESH module that belongs to the partner node, complete the following steps.

Step	Action
1	If your system is...	Then...
	Setup as a fabric MetroCluster	Go to Step 2.
	Not setup as a fabric MetroCluster	Take over the partner filer's disk shelves by entering the following command on the local filer: cf takeover
2	Note the terminate switch position of the LRC, or terminate and loop speed switches of the ESH you are replacing. The new LRC/ESH module must be set to the same settings as the old LRC/ESH.
3	While grounded, unplug the cabling from the target LRC/ESH module, then remove the module.
4	Slide the replacement LRC/ESH module into the slot at the rear of the disk shelf and push the levers of the CAM mechanism into place.
5	Reconnect the cabling to the replacement LRC/ESH.
6	If cf takeover was...	Then...
7	Performed in Step 1.	Return control of the partner filer's disk shelves by entering the following command: cf giveback
8	Not performed in Step 1.	Test the replacement LRC/ESH module, as described in Testing the LRC/ESH modules.

Testing the LRC/ESH modules

To test your LRC/ESH modules, complete the following steps on both nodes.

Step	Action
1	Verify that all disk shelves with ESH modules are functioning properly by entering the following command: environ shelf Results The system reports the modules as good.
2	Verify that you can create and retrieve files on both nodes for each licensed protocol.
3	Verify that there are no missing disks by entering the following command: vol status -r Result Local disks displayed on the local node should be displayed as partner disks on the partner node, and vice-versa.

Step

Action

Verify that all disk shelves with ESH modules are functioning properly by entering the following command:

environ shelf

Results

The system reports the modules as good.

Verify that you can create and retrieve files on both nodes for each licensed protocol.

Verify that there are no missing disks by entering the following command:

vol status -r

Result

Local disks displayed on the local node should be displayed as partner disks on the partner node, and vice-versa.